MX Linux Forum

junoluna wrote: Tue Oct 22, 2019 7:57 am I have only recently started using MX linux and like it so much that I have put it on 4 laptops in the house. (this after a long time away from linux but finally reaching my wit's end with windows)... tried 4 or 5 other distros before stumbling on this one thanks top bigdaddy linux's distro challenge show.

Anyway ... given that MX 18 is working very well across the board, is there any need to upgrade at this stage?...

anyway ... i guess what i am saying is i don't want to do anything else ever again so is it ok to stick rather than twist?......

GuiGuy wrote: Tue Oct 22, 2019 9:45 am Please explain the name "patito feo".... .

GuiGuy wrote: Tue Oct 22, 2019 9:45 am Please explain the name "patito feo".... .

junoluna wrote: Tue Oct 22, 2019 7:57 am Anyway ... given that MX 18 is working very well across the board, is there any need to upgrade at this stage?
I would prefer to wait til I start to break stuff (probably not long)

Eadwine Rose wrote: Tue Oct 22, 2019 10:43 am Interesting little something I just discovered on screen tearing with the default nvidia driver and compositors.

I have this youtube video that I test with: https://www.youtube.com/watch?v=5xkNy9gfKOg
Putting that full screen and then moving the mouse over it clearly shows if I have screen tearing or not.


When I have the compositor on Xfwm everything is fine.
If I change it to Compton I get tearing.
Change it back to Xfwm and all is fine again.

Code: Select all

System:    Host: eadwineMX19 Kernel: 4.19.0-6-amd64 x86_64 bits: 64 compiler: gcc v: 8.3.0 
           parameters: BOOT_IMAGE=/boot/vmlinuz-4.19.0-6-amd64 
           root=UUID=c7f614c9-c448-4560-93c2-9e9748b4ae8f ro quiet 
           Desktop: Xfce 4.14.1 tk: Gtk 3.24.5 info: xfce4-panel wm: xfwm4 dm: LightDM 1.26.0 
           Distro: MX-19_x64 patito feo October 21  2019 base: Debian GNU/Linux 10 (buster) 
Machine:   Type: Desktop Mobo: ASUSTeK model: TUF B450-PLUS GAMING v: Rev X.0x serial: <filter> 
           UEFI: American Megatrends v: 1607 date: 06/17/2019 
Battery:   Device-1: hidpp_battery_0 model: Logitech MX Ergo Multi-Device Trackball 
           serial: <filter> charge: 100% (should be ignored) rechargeable: yes 
           status: Discharging 
CPU:       Topology: 8-Core model: AMD Ryzen 7 2700 bits: 64 type: MT MCP arch: Zen+ 
           family: 17 (23) model-id: 8 stepping: 2 microcode: 800820C L2 cache: 4096 KiB 
           flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm 
           bogomips: 102192 
           Speed: 1376 MHz min/max: 1550/3200 MHz boost: enabled Core speeds (MHz): 1: 1378 
           2: 1441 3: 1477 4: 1545 5: 1383 6: 1387 7: 1547 8: 1546 9: 1377 10: 1546 11: 1379 
           12: 1378 13: 1546 14: 1546 15: 1547 16: 1544 
           Vulnerabilities: Type: l1tf status: Not affected 
           Type: mds status: Not affected 
           Type: meltdown status: Not affected 
           Type: spec_store_bypass 
           mitigation: Speculative Store Bypass disabled via prctl and seccomp 
           Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization 
           Type: spectre_v2 
           mitigation: Full AMD retpoline, IBPB: conditional, STIBP: disabled, RSB filling 
Graphics:  Device-1: NVIDIA GP107 [GeForce GTX 1050 Ti] vendor: ASUSTeK driver: nvidia v: 418.74 
           bus ID: 08:00.0 chip ID: 10de:1c82 
           Display: x11 server: X.Org 1.20.4 driver: nvidia 
           unloaded: fbdev,modesetting,nouveau,vesa alternate: nv 
           resolution: 1920x1080~60Hz, 1920x1080~60Hz 
           OpenGL: renderer: GeForce GTX 1050 Ti/PCIe/SSE2 v: 4.6.0 NVIDIA 418.74 
           direct render: Yes 
Audio:     Device-1: Conexant Systems CX23887/8 PCIe Broadcast Audio and Video Decoder with 3D 
           Comb 
           vendor: Hauppauge works driver: cx23885 v: 0.0.4 bus ID: 07:00.0 chip ID: 14f1:8880 
           Device-2: NVIDIA GP107GL High Definition Audio vendor: ASUSTeK driver: snd_hda_intel 
           v: kernel bus ID: 08:00.1 chip ID: 10de:0fb9 
           Device-3: AMD Family 17h HD Audio vendor: ASUSTeK driver: snd_hda_intel v: kernel 
           bus ID: 0a:00.3 chip ID: 1022:1457 
           Device-4: Logitech QuickCam E 3500 type: USB driver: snd-usb-audio,uvcvideo 
           bus ID: 3-1:2 chip ID: 046d:09a4 serial: <filter> 
           Sound Server: ALSA v: k4.19.0-6-amd64 
Network:   Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: ASUSTeK 
           driver: r8169 v: kernel port: f000 bus ID: 03:00.0 chip ID: 10ec:8168 
           IF: eth0 state: up speed: 1000 Mbps duplex: full mac: <filter> 
           Device-2: Ralink MT7601U Wireless Adapter type: USB driver: mt7601u bus ID: 1-1:2 
           chip ID: 148f:7601 serial: <filter> 
           IF: wlan0 state: down mac: <filter> 
Drives:    Local Storage: total: 1.82 TiB used: 72.97 GiB (3.9%) 
           ID-1: /dev/sda vendor: Samsung model: SSD 860 EVO 250GB size: 232.89 GiB block size: 
           physical: 512 B logical: 512 B speed: 6.0 Gb/s serial: <filter> rev: 2B6Q scheme: GPT 
           ID-2: /dev/sdb vendor: Samsung model: SSD 860 EVO 250GB size: 232.89 GiB block size: 
           physical: 512 B logical: 512 B speed: 6.0 Gb/s serial: <filter> rev: 2B6Q scheme: GPT 
           ID-3: /dev/sdc vendor: Samsung model: SSD 860 EVO 250GB size: 232.89 GiB block size: 
           physical: 512 B logical: 512 B speed: 6.0 Gb/s serial: <filter> rev: 3B6Q scheme: GPT 
           ID-4: /dev/sdd type: USB vendor: Seagate model: BUP Slim RD size: 931.51 GiB 
           block size: physical: 4096 B logical: 512 B serial: <filter> rev: 0109 scheme: MBR 
           ID-5: /dev/sde vendor: Samsung model: SSD 860 EVO 250GB size: 232.89 GiB block size: 
           physical: 512 B logical: 512 B speed: 6.0 Gb/s serial: <filter> rev: 3B6Q scheme: GPT 
Partition: ID-1: / raw size: 58.59 GiB size: 57.42 GiB (98.00%) used: 5.90 GiB (10.3%) fs: ext4 
           dev: /dev/sdc1 
           ID-2: /home raw size: 166.48 GiB size: 162.87 GiB (97.83%) used: 150.4 MiB (0.1%) 
           fs: ext4 dev: /dev/sdc3 
           ID-3: swap-1 size: 7.81 GiB used: 0 KiB (0.0%) fs: swap swappiness: 15 (default 60) 
           cache pressure: 100 (default) dev: /dev/sdc2 
Sensors:   System Temperatures: cpu: 33.9 C mobo: 27.0 C gpu: nvidia temp: 35 C 
           Fan Speeds (RPM): cpu: 532 mobo: 168750 fan-2: fan-3: 0 fan-4: 757 fan-6: 0 
           gpu: nvidia fan: 25% 
           Voltages: 12v: N/A 5v: N/A 3.3v: 3.36 vbat: 3.27 
Repos:     No active apt repos in: /etc/apt/sources.list 
           Active apt repos in: /etc/apt/sources.list.d/antix.list 
           1: deb http://iso.mxrepo.com/antix/buster buster main
           Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list 
           1: deb http://deb.debian.org/debian buster-updates main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/debian.list 
           1: deb http://deb.debian.org/debian buster main contrib non-free
           2: deb http://deb.debian.org/debian-security buster/updates main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/mx.list 
           1: deb http://mxrepo.com/mx/repo/ buster main non-free
           No active apt repos in: /etc/apt/sources.list.d/various.list 
Info:      Processes: 343 Uptime: 5m Memory: 31.41 GiB used: 1.12 GiB (3.6%) Init: SysVinit 
           v: 2.93 runlevel: 5 default: 5 Compilers: gcc: 8.3.0 alt: 8 Shell: bash v: 5.0.3 
           running in: quick-system-in inxi: 3.0.36 

darknetmatrix wrote: Tue Oct 22, 2019 11:23 am MX19 is supported until ...?

Iguana77 wrote: Tue Oct 22, 2019 12:10 pm The new MX-19 is working desperately on me. My PC will explode :) CPU is constantly around 50%. I'm going back to LInux MInt

Iguana77 wrote: Tue Oct 22, 2019 12:10 pm The new MX-19 is working desperately on me. My PC will explode :) CPU is constantly around 50%. I'm going back to LInux MInt

asqwerth wrote: Tue Oct 22, 2019 12:46 pm I'm suspect it's related to his hybrid graphics question, which no one has helped solve yet.

https://forum.mxlinux.org/viewtopic.php ... id#p535112

Eadwine Rose wrote: Tue Oct 22, 2019 12:28 pm

Iguana77 wrote: Tue Oct 22, 2019 12:10 pm The new MX-19 is working desperately on me. My PC will explode :) CPU is constantly around 50%. I'm going back to LInux MInt

You give up easy. What does top say?

Iguana77 wrote: Tue Oct 22, 2019 12:54 pm There is nothing to say support here on the forum for us beginners is very weak. I don't know how to solve problem and not get the right help

old_guy wrote: Tue Oct 22, 2019 1:13 pm I just tried adding some .png files that I used in MX 18 to /usr/share/backgrounds and to /usr/share/icons and can not select them to use as backgrounds or icons.
Earl

Iguana77 wrote: Tue Oct 22, 2019 12:54 pm

Eadwine Rose wrote: Tue Oct 22, 2019 12:28 pm

Iguana77 wrote: Tue Oct 22, 2019 12:10 pm The new MX-19 is working desperately on me. My PC will explode :) CPU is constantly around 50%. I'm going back to LInux MInt

You give up easy. What does top say?

There is nothing to say support here on the forum for us beginners is very weak. I don't know how to solve problem and not get the right help

Eadwine Rose wrote: Tue Oct 22, 2019 1:32 pm Windows wireless drivers and HPLIP Toolbox (that one I noticed before) are without icons. Cross checked on Papyrus and it's the same there.

snapshot.jpg

qwertz wrote: Tue Oct 22, 2019 1:54 pm I just made a clean install with MX Linux 19. When my monitor wakes up from sleep it always opens the display settings dialog: https://ibb.co/wpk671Z

How can I fix it?

Please explain the name "patito feo".... .

m_pav wrote: Tue Oct 22, 2019 2:28 pm Debian Buster and all upstream packages for usbutils no longer include the user mode tool to manually download the latest daily snapshots of USB device vendors.

I used to run both update-usbids and update-pciids before creating a snapshot to ensure it was made with the most up to date databases for each type. The update-usbids will be sorely missed

Jerry3904 wrote: Tue Oct 22, 2019 2:01 pm Did you set up a Profile in Display > Advanced? If not, give that a try (read the Help if not clear how to do that).

Iguana77 wrote: Tue Oct 22, 2019 12:52 pm

asqwerth wrote: Tue Oct 22, 2019 12:46 pm I'm suspect it's related to his hybrid graphics question, which no one has helped solve yet.

https://forum.mxlinux.org/viewtopic.php ... id#p535112

My memory is very high not CPU. Sorry for mistake.

NevilsStation wrote: Tue Oct 22, 2019 6:23 pm There are 12 files here https://sourceforge.net/projects/mx-linux/files/Final/

I don't see a .txt or .doc that explains what they are.

Jerry3904 wrote: Tue Oct 22, 2019 5:33 pm Doesn't look like it is anywhere, but there are solutions on the web such as this you might try:

https://www.linuxuprising.com/2018/05/f ... -1804.html

Jerry3904 wrote: Tue Oct 22, 2019 5:39 pm Hooray. Can you please give us some specifics about how you did that and what the result was exactly?

do7ob wrote: Wed Oct 23, 2019 2:43 pm I am running mx19 in frugal mode, I have ecryptfs folders mountable manually so it was a bit scary to see my scripts fail because ecryptfs has been booted off debian (apparently pulled because of a systemd compatibility issue... systemd “never finished, never complete, but tracking progress of technology” actually means "linux is too stable compatible and documented, we would rather get back to the windows days of planned obsolescence for hw and sw").

But the ecryptfs module is still built for the kernel, so just get the source debs from the sid source package (v. 111-4), and debuild, seems to work all right.

Lupin wrote: Wed Oct 23, 2019 2:14 pm some minor visual glitches/bugs mainly in notification area

asqwerth wrote: Wed Oct 23, 2019 4:05 pm Running the live USB. For some reason, the new icon for Windows Wireless Drivers doesn't show up in the XFCE Settings Manager.


Screenshot.png



It does show up in Whisker menu.


Screenshot-1.png



For what it's worth, the .desktop file has this line for icon:

Icon=ndisgtk.png

This restricts the icon to only the png version of the icon, and the new icon is a SVG file.

I tried changing the desktop file in root to remove the suffix in the icon filepath, but still the new icon does not show up. Instead, in XFCE Settings Manager, the ancient icon found in usr/share/pixmaps in .xpm format and found in /usr/share/icons/hicolor/48x48/apps in png format show up in XFCE settings manager after I change the desktop file.

Eadwine Rose wrote: Wed Oct 23, 2019 4:07 pm I reported that way in the beginning, I guess it got overlooked in all the fray. The one for HPLIP Toolbox is also not there.

Gaer Boy wrote: Wed Oct 23, 2019 9:26 am One slight display problem - I have 3 apps open - Thunar, Thunderbird & Opera. The icon for Thunar doesn't show in the panel - it's almost the same as the background. panel-thunar.png

dolphin_oracle wrote: Wed Oct 23, 2019 7:17 pm

Eadwine Rose wrote: Wed Oct 23, 2019 4:07 pm I reported that way in the beginning, I guess it got overlooked in all the fray. The one for HPLIP Toolbox is also not there.

I can't do anything with the HP toolbox icon. its calling out a very specific icon location and I have no idea why the settings manager can't use it.

the settings manager is finicky about where icons are placed I think. Xfce seems to do interesting things with the icon names and extensions from time to time.

and many of the icon themes actually already have hplip icons (including the default papirus icon sets), they just aren't used by hplip. so if we want those to be used, then the package needs changed to have "hp_logo" as the Icon= designation in the desktop files, as well as dropping one of the hp_logo.png files into /usr/share/icons/hicolor/48x48/apps. this really needs done on the packaging level, as hplip-gui is not installed on MX by default.

the others will update soonish.

Eadwine Rose wrote: Wed Oct 23, 2019 3:11 pm It's a known problem covering many distros, not just MX. Unfortunately there is yet no fix.

oops wrote: Thu Oct 24, 2019 5:28 am First , Congratulations for the MX19 releases ...
... Just a question, why the apparmor packages are into the MX19-32 version and not into the MX19-64 version ?

Lupin wrote: Wed Oct 23, 2019 2:14 pmsome shapeshifting pixels around notification area icons appear sometimes, randomly

Huckleberry wrote: Thu Oct 24, 2019 4:13 pm It occured on mine (horizontal panel at bottom) between volume icon and network manager.. I simply removed the notification area (panel preferences), then added a new one and adjusted as I wanted.. It's ok for now ..

Another thing: If you scroll (mouse/touchpad) on the volume icon to increase / decrease the volume, it does, but doesn't display the slider unless you click on the icon.. (In fact, these are due to Xfce 4.14 , not MX itself )

Lupin wrote: Thu Oct 24, 2019 4:47 am

Eadwine Rose wrote: Wed Oct 23, 2019 3:11 pm It's a known problem covering many distros, not just MX. Unfortunately there is yet no fix.

yeah you're right.
I saw someone has reported the same virtualbox theming issue sometime around 2018 in manjaro forums. not sure if it's now fixed or not though.


EDIT: found the ticket > https://www.virtualbox.org/ticket/18258

Stevo wrote: Thu Oct 24, 2019 6:05 pm I was going to reduce swappiness on the new install, but checked it first, and it's already set at 15, instead of the 60 that most of the guides suggest the default is. Is this an MX customization, or Debian's?

Stevo wrote: Thu Oct 24, 2019 6:16 pm

Lupin wrote: Thu Oct 24, 2019 4:47 am

Eadwine Rose wrote: Wed Oct 23, 2019 3:11 pm It's a known problem covering many distros, not just MX. Unfortunately there is yet no fix.

yeah you're right.
I saw someone has reported the same virtualbox theming issue sometime around 2018 in manjaro forums. not sure if it's now fixed or not though.


EDIT: found the ticket > https://www.virtualbox.org/ticket/18258

I had the same virtualbox 6.X theme issue on my MX 19 with the a dark theme, but this setting fixes it for me (edit the menu item and use this for the command:)

VirtualBox -style fusion %U

-gtk and -qt styles don't work any longer, but maybe I'm missing a Qt package. If this solves it for everyone, we could add the fix to the wiki or the FAQs.

We also have an updated virtualbox 5.2.34 in the experimental repo that will follow the system theme, if you want to go that route.

dolphin_oracle wrote: Thu Oct 24, 2019 6:21 pm

Stevo wrote: Thu Oct 24, 2019 6:05 pm I was going to reduce swappiness on the new install, but checked it first, and it's already set at 15, instead of the 60 that most of the guides suggest the default is. Is this an MX customization, or Debian's?

that's ours.

Stevo wrote: Thu Oct 24, 2019 6:16 pm

Lupin wrote: Thu Oct 24, 2019 4:47 am

Eadwine Rose wrote: Wed Oct 23, 2019 3:11 pm It's a known problem covering many distros, not just MX. Unfortunately there is yet no fix.

yeah you're right.
I saw someone has reported the same virtualbox theming issue sometime around 2018 in manjaro forums. not sure if it's now fixed or not though.


EDIT: found the ticket > https://www.virtualbox.org/ticket/18258

I had the same virtualbox 6.X theme issue on my MX 19 with the a dark theme, but this setting fixes it for me (edit the menu item and use this for the command:)

VirtualBox -style fusion %U

-gtk and -qt styles don't work any longer, but maybe I'm missing a Qt package. If this solves it for everyone, we could add the fix to the wiki or the FAQs.

We also have an updated virtualbox 5.2.34 in the experimental repo that will follow the system theme, if you want to go that route.

dolphin_oracle wrote: Thu Oct 24, 2019 6:31 am
Because I made a mistake and left.them on the 43 bit iso.

Grr...

Lupin wrote: Fri Oct 25, 2019 2:55 am

Stevo wrote: Thu Oct 24, 2019 6:16 pm

Lupin wrote: Thu Oct 24, 2019 4:47 am
yeah you're right.
I saw someone has reported the same virtualbox theming issue sometime around 2018 in manjaro forums. not sure if it's now fixed or not though.


EDIT: found the ticket > https://www.virtualbox.org/ticket/18258

I had the same virtualbox 6.X theme issue on my MX 19 with the a dark theme, but this setting fixes it for me (edit the menu item and use this for the command:)

VirtualBox -style fusion %U

-gtk and -qt styles don't work any longer, but maybe I'm missing a Qt package. If this solves it for everyone, we could add the fix to the wiki or the FAQs.

We also have an updated virtualbox 5.2.34 in the experimental repo that will follow the system theme, if you want to go that route.

thank you Stevo ! that solved the issue

Stevo wrote: Sun Oct 27, 2019 8:59 pm
Having installed qt-style-kvantum and configured it, and KDE to use it, I now find that it's also now a style option for Vbox in XFCE---so it's back to my preferred dark interface instead of glaring white.

asqwerth wrote: Mon Oct 28, 2019 5:24 am

Stevo wrote: Sun Oct 27, 2019 8:59 pm
Having installed qt-style-kvantum and configured it, and KDE to use it, I now find that it's also now a style option for Vbox in XFCE---so it's back to my preferred dark interface instead of glaring white.

So kvantum manager has a setting to sort out Vbox stying for users using XFCE?

richb wrote: Mon Oct 28, 2019 3:34 pm I guess I do not know how to use the Kvantum Manager. I load a Kvantum theme from /usr/shar/themes for example kvantum and it gives an error "Not a kvantum theme". Seems like a simple enough thing to do.

dolphin_oracle wrote: Mon Oct 28, 2019 6:05 pm that should work. usually those *.d directories grab everything in alphanumeric sequence, so numbers are good.

Stevo wrote: Mon Oct 28, 2019 3:29 pm Test a Live Session, installing VBox and qt-style-kvantum from the test repos. VBox looked OK with the default light theme, but fonts became almost impossible to read when I switched to a dark xfce theme. The Kvantum style worked out of the box, though, as well as using different Kvantum themes via Kvantum Manager--no need for KDE.

I don't see why this shouldn't also work on MX 18 with VBox 6.X.

duane wrote: Tue Oct 29, 2019 2:43 pm The only option at this point that I can find is to power down the computer by holding in the power button.

Jerry3904 wrote: Tue Oct 29, 2019 3:55 pm @fehlix: I wonder if we should look at switching back to the mx-switchuser in the meantime?

Jerry3904 wrote: Thu Oct 31, 2019 9:01 am Suspend has always been a bit flakey on my Production machine. I once solved it by switching to the Nvidia chip, another time by going to the liquorix kernel, and a third time by upgrading the kernel.

Hibernate seems (once again) not to work at all so far--but I never use it anyway.

Pierre wrote: Fri Nov 01, 2019 9:36 am for some reason the Direct Download from Sourceforge - fails NoFileFound ? ?

so, used the Torrent, instead - - worked well, downloaded in less than an Hr. ..50 seeders !.

installed into an VirtualBox - - all good.
& fell for the usual video_size_issue
& & tried to 'fix that' with Guest Additions .. . pointless, as that's not needed, anyway.
- - and GA is tricky to install, as it always needs Root permission.

finally - - started thinking - - adjust the small_screen_size in Display Properties
- - suddenly, it's Full Screen funny that

it's an Nice Release - - isn't it ?.

timkb4cq wrote: Fri Nov 01, 2019 5:01 pm Interesting. That's a clue at least.
For any who wish to try sysvinit 2.96 as well, I've just backported it from Debian Bullseye uploaded it to MX-19 Test.

The following packages have unmet dependencies:
 sysv-rc : Depends: startpar (>= 0.62-1~)
 sysvinit-utils : Depends: lsb-base (>= 11.0.0~) but 10.2019051400 is to be installed
E: Unable to correct problems, you have held broken packages.

asqwerth wrote: Fri Nov 01, 2019 10:13 am
in the Display settings of your VM, make sure Graphics COntroller is set to VBoxSVGA (the bottommost entry in the dropdown menu). That should get you easy resizing just by resizing your VM window.

Pierre wrote: Sat Nov 02, 2019 12:15 am

asqwerth wrote: Fri Nov 01, 2019 10:13 am
in the Display settings of your VM, make sure Graphics COntroller is set to VBoxSVGA (the bottommost entry in the dropdown menu). That should get you easy resizing just by resizing your VM window.

interestingly, I'd looked in both the wiki & the manual,
- for that setting, as it's something that I'd remembered. from the last MX-18 VB test.
and couldn't find, such an reference, for some reason.

JayM wrote: Thu Oct 31, 2019 5:35 am If I have Firefox open maximized and open MXPI (windowed) then click back on the Firefox window button in the panel, MXPI stays in the foreground as though it isn't releasing focus. If I minimize MXPI, then I can switch back and forth between them via their window buttons. It doesn't always happen, but does so often, maybe one time out of ten. I seem to recall it happening before I installed the Nvidia driver too, but I'm not 100% positive about that.

Code: Select all

System:    Host: mx19-JayM Kernel: 4.19.0-6-amd64 x86_64 bits: 64 compiler: gcc v: 8.3.0 
           parameters: BOOT_IMAGE=/vmlinuz-4.19.0-6-amd64 
           root=UUID=9fb8104e-61fd-4f54-bfb7-e7d68d124ca1 ro quiet splash 
           Desktop: Xfce 4.14.1 tk: Gtk 3.24.5 info: xfce4-panel wm: xfwm4 dm: LightDM 1.26.0 
           Distro: MX-19_x64 patito feo October 15  2019 base: Debian GNU/Linux 10 (buster) 
Machine:   Type: Laptop System: Hewlett-Packard product: HP Pavilion dv6 Notebook PC 
           v: 049D210000241210000020000 serial: <filter> Chassis: type: 10 serial: <filter> 
           Mobo: Hewlett-Packard model: 3659 v: 32.25 serial: <filter> BIOS: Hewlett-Packard 
           v: F.1B date: 04/23/2010 
Battery:   ID-1: BAT0 charge: 39.7 Wh condition: 39.7/47.5 Wh (84%) volts: 12.4/10.8 
           model: Hewlett-Packard Primary type: Li-ion serial: <filter> status: Full 
CPU:       Topology: Dual Core model: Intel Core i5 M 430 bits: 64 type: MT MCP arch: Nehalem 
           family: 6 model-id: 25 (37) stepping: 2 microcode: 11 L2 cache: 3072 KiB 
           flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 18088 
           Speed: 1342 MHz min/max: 1199/2267 MHz boost: enabled Core speeds (MHz): 1: 1335 
           2: 1414 3: 1342 4: 1358 
           Vulnerabilities: Type: l1tf 
           mitigation: PTE Inversion; VMX: conditional cache flushes, SMT vulnerable 
           Type: mds 
           status: Vulnerable: Clear CPU buffers attempted, no microcode; SMT vulnerable 
           Type: meltdown mitigation: PTI 
           Type: spec_store_bypass 
           mitigation: Speculative Store Bypass disabled via prctl and seccomp 
           Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization 
           Type: spectre_v2 mitigation: Full generic retpoline, IBPB: conditional, IBRS_FW, 
           STIBP: conditional, RSB filling 
Graphics:  Device-1: NVIDIA GT216M [GeForce GT 230M] vendor: Hewlett-Packard driver: nvidia 
           v: 340.107 bus ID: 01:00.0 chip ID: 10de:0a28 
           Display: x11 server: X.Org 1.20.4 driver: nvidia resolution: 1366x768~60Hz 
           OpenGL: renderer: GeForce GT 230M/PCIe/SSE2 v: 3.3.0 NVIDIA 340.107 
           direct render: Yes 
Audio:     Device-1: Intel 5 Series/3400 Series High Definition Audio vendor: Hewlett-Packard 
           driver: snd_hda_intel v: kernel bus ID: 00:1b.0 chip ID: 8086:3b56 
           Device-2: NVIDIA GT216 HDMI Audio vendor: Hewlett-Packard driver: snd_hda_intel 
           v: kernel bus ID: 01:00.1 chip ID: 10de:0be2 
           Device-3: Philips s SAA7160 vendor: Avermedia driver: N/A bus ID: 04:00.0 
           chip ID: 1131:7160 
           Sound Server: ALSA v: k4.19.0-6-amd64 
Network:   Device-1: Broadcom Limited BCM43225 802.11b/g/n vendor: Hewlett-Packard driver: wl 
           v: kernel port: 7000 bus ID: 02:00.0 chip ID: 14e4:4357 
           IF: wlan0 state: up mac: <filter> 
           Device-2: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet 
           vendor: Hewlett-Packard driver: r8169 v: kernel port: 5000 bus ID: 03:00.0 
           chip ID: 10ec:8168 
           IF: eth0 state: down mac: <filter> 
Drives:    Local Storage: total: 465.76 GiB used: 172.83 GiB (37.1%) 
           ID-1: /dev/sda vendor: Seagate model: ST9500325AS size: 465.76 GiB block size: 
           physical: 512 B logical: 512 B speed: 3.0 Gb/s rotation: 5400 rpm serial: <filter> 
           rev: SDM1 scheme: MBR 
Partition: ID-1: / raw size: 463.21 GiB size: 454.94 GiB (98.21%) used: 172.75 GiB (38.0%) 
           fs: ext4 dev: /dev/dm-0 
           ID-2: /boot raw size: 512.0 MiB size: 487.9 MiB (95.30%) used: 79.8 MiB (16.4%) 
           fs: ext4 dev: /dev/sda1 
           ID-3: swap-1 size: 1.98 GiB used: 1.0 MiB (0.0%) fs: swap swappiness: 15 (default 60) 
           cache pressure: 100 (default) dev: /dev/dm-1 
Sensors:   System Temperatures: cpu: 52.0 C mobo: N/A gpu: nvidia temp: 66 C 
           Fan Speeds (RPM): N/A 
Repos:     No active apt repos in: /etc/apt/sources.list 
           Active apt repos in: /etc/apt/sources.list.d/antix.list 
           1: deb http://iso.mxrepo.com/antix/buster buster main
           Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list 
           1: deb http://deb.debian.org/debian buster-updates main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/debian.list 
           1: deb http://deb.debian.org/debian buster main contrib non-free
           2: deb http://deb.debian.org/debian-security buster/updates main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/mx.list 
           1: deb http://mxrepo.com/mx/repo/ buster main non-free
           No active apt repos in: /etc/apt/sources.list.d/various.list 
Info:      Processes: 238 Uptime: 9h 19m Memory: 3.78 GiB used: 1.74 GiB (46.0%) Init: SysVinit 
           v: 2.93 runlevel: 5 default: 5 Compilers: gcc: 8.3.0 alt: 8 Shell: bash v: 5.0.3 
           running in: quick-system-in inxi: 3.0.36 

sunrat wrote: Sat Nov 02, 2019 2:05 am ... Will need to tweak somehow to get bigger grab handles on windows, that's hard currently. So WIP as far as that goes...

Work on the XAppStatusIcon API is finished. Applets were added to Cinnamon, MATE and Xfce. LibAppIndicator was patched. We’ll have crisp icons in all environments in 19.3, HiDPI compatible, with support for symbolic icons and without rendering issues.

Eadwine Rose wrote: Wed Oct 23, 2019 3:11 pm It's a known problem covering many distros, not just MX. Unfortunately there is yet no fix.

tascoast wrote: Sat Nov 02, 2019 8:22 pm :
Correction: The MX Manual 3.3.4 Dual Monitors mentions finer control can be available with xrandr,
which should perhaps be written as ARandR?
:

• On MXPI the linux-headers file for the current kernel (the one in my signature) doesn't look grey. Re-installed, same .. (Also the notification when you hover on it doesn't say it's already installed)

• Same versions of SysVinit (2.96) on 18.3 and 19 on the same machine but on 19 during init, error messages :
  
  SELinux .. couldn't find /etc/... profile... blah blah..
  
  Apparmor "Are you sure you have the required privileges" (or so) .. "Failed"

• The issue I mentioned at posts:
  
  viewtopic.php?f=77&t=53476&start=120#p537346
  viewtopic.php?f=77&t=53476&start=130#p537579
  
  and also heard from some users are solved after I noticed that light-locker was not installed by default and on MXPI installed from Stable Repo, tried all, lock screen, suspend with default way (xfce4-session-...) All OK.

• And an interesting clue again related to the "shade" issue on panel: posting.php?mode=reply&f=77&t=53476#pr538487
  
  After suspend & wake up it disappears (till next boot).

Lupin wrote: Tue Nov 05, 2019 5:34 pm not sure if anybody has experienced this or written about it here:
when i press the mute button on my keyboard, sounds are muted well, but when i press it again to unmute , the notification is shown but the sounds are still unmuted and i have to go to settings > PulseAudio Volume Control and umute it manually there.

• Menu => Disk Manager opens "nothing". Same when logged in as "root".
  
  And on terminal:
  

  Code: Select all

  $ sudo disk-manager
  WARNING : python-notify is not installed, disable notification
  WARNING : python-notify is too old, disable notification
  Traceback (most recent call last):
    File "/usr/sbin/disk-manager", line 85, in <module>
      main(args, opts)
    File "/usr/sbin/disk-manager", line 58, in main
      app = DiskManager()
    File "/usr/lib/python2.7/dist-packages/DiskManager/DiskManager.py", line 129, in __init__
      self.setupTreeView()
    File "/usr/lib/python2.7/dist-packages/DiskManager/DiskManager.py", line 223, in setupTreeView
      "selected_order").upper()))
  AttributeError: 'module' object has no attribute 'SORT_ASCENDiNG'

• I can't see "Ownership to User" in Thunar context menu (which was handy). Yes, maybe I add manually (grabbing from 18.3) but I wish it turns back with updates..

• Root account never saves the conky. (Created a .conky there with just my fav. conky in). Even when you click "Conky Toggle " to turn it on again, it opens "Conky Manager" , then you select it again and start.. each time..

Huckleberry wrote: Wed Nov 06, 2019 4:27 pm

• Menu => Disk Manager opens "nothing". Same when logged in as "root".
  
  And on terminal:
  

  Code: Select all

  $ sudo disk-manager
  WARNING : python-notify is not installed, disable notification
  WARNING : python-notify is too old, disable notification
  Traceback (most recent call last):
    File "/usr/sbin/disk-manager", line 85, in <module>
      main(args, opts)
    File "/usr/sbin/disk-manager", line 58, in main
      app = DiskManager()
    File "/usr/lib/python2.7/dist-packages/DiskManager/DiskManager.py", line 129, in __init__
      self.setupTreeView()
    File "/usr/lib/python2.7/dist-packages/DiskManager/DiskManager.py", line 223, in setupTreeView
      "selected_order").upper()))
  AttributeError: 'module' object has no attribute 'SORT_ASCENDiNG'

• I can't see "Ownership to User" in Thunar context menu (which was handy). Yes, maybe I add manually (grabbing from 18.3) but I wish it turns back with updates..

• Root account never saves the conky. (Created a .conky there with just my fav. conky in). Even when you click "Conky Toggle " to turn it on again, it opens "Conky Manager" , then you select it again and start.. each time..

Huckleberry wrote: Thu Nov 07, 2019 1:13 pm Thank you, I will.

Meanwhile, updated 18.3 , too and it works normal for user on 18.3 ..

Huckleberry wrote: Thu Nov 07, 2019 9:06 amThe actual reason why I'm logging as "root" (normally I almost never) and mentioned "disk manager" (that one also .. I never need normally) :

In Thunar to open other partitions I need to type password ..

I'd done it on 18.3 simply, but can't remember how I changed the permissions..

[Mounting, checking, etc. of internal drives]
Identity=unix-group:admin;unix-group:storage;unix-user:USER;
Action=org.freedesktop.udisks2.filesystem-*;org.freedesktop.udisks2.drive-ata-smart*
ResultActive=yes

sunrat wrote: Thu Nov 07, 2019 5:14 pm

Huckleberry wrote: Thu Nov 07, 2019 9:06 amThe actual reason why I'm logging as "root" (normally I almost never) and mentioned "disk manager" (that one also .. I never need normally) :

In Thunar to open other partitions I need to type password ..

I'd done it on 18.3 simply, but can't remember how I changed the permissions..

You may be able to use a PolicyKit rule to enable mounting partitions as user.
Create a file:
/etc/polkit-1/localauthority/50-local.d/10-desktop.policy.pkla
with this content:

Code: Select all

[Mounting, checking, etc. of internal drives]
Identity=unix-group:admin;unix-group:storage;unix-user:USER;
Action=org.freedesktop.udisks2.filesystem-*;org.freedesktop.udisks2.drive-ata-smart*
ResultActive=yes

Change USER to your username.
You probably need to create the storage group and add your user to it.
But doesn't Disk Manager allow you to configure this?

dolphin_oracle wrote: Thu Nov 07, 2019 6:06 pm FWIW, the policy kit rule is what mx-tweak uses.

JayM wrote: Sun Nov 10, 2019 6:54 am Funny, when I opened the link the video started at around two-thirds of the way through.