MX-19 Feedback

[dolphin_oracle]

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 ?

Because I made a mistake and left.them on the 43 bit iso.

Grr...

[Huckleberry Finn]

some shapeshifting pixels around notification area icons appear sometimes, randomly

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 )
__________________________________________________
Edit about the conky background. Other than the line: own_window_transparent yes

This line also needs to be "yes" to make it transparent:
own_window_argb_visual yes

Fixed that..

[Lupin]

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 )

I changed some of notification-area new settings this morning and I've not seen that happen so far, I hid the items that I don't use much ,like power-manger & redshift icons and also checked the "square icons", not sure though,it may happen again anytime.

these issues may get fixed in the upcoming xfce 4.16 hopefully.

[Stevo]

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]

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]

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.

[dolphin_oracle]

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.

fwiw, the same sort of fix works with digikam and a few other Qt applications with issues with the gtk2 plugin.

[asqwerth]

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.

Aha! I noticed that last night after I "upgraded" to MX19 over my MX16 installation (see: https://forum.mxlinux.org/viewtopic.php ... 84#p535884 ).

"Change swappiness" is on my post-install to-do list.

[MiVo]

I did a fresh install of MX-19, but every time I start the computer I see this:

[ 3.643202] systemd-udevd[484]: /etc/udev/rules.d/60-brother-brscan4-libsane-type1.rules:9: Unknown key 'SYSFS{idVendor}'
[ 3.643388] systemd-udevd[484]: /etc/udev/rules.d/60-brother-libsane-type1-inst.rules:14: Unknown key 'SYSFS{idVendor}'

With 18.3 I never saw this. I have a Brother All-in-one DCP-J562DW and I installed the driver software I got from the Brother site. Despite the 2 lines the printer and scanner works normally, no issues with that. Can I just ignore the lines ?

Code: Select all

System:    Host: oxygene 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=0c057d08-f440-4c00-a29d-fc4dac55a3c9 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 21  2019 base: Debian GNU/Linux 10 (buster) 
Machine:   Type: Desktop System: ASUS product: All Series v: N/A serial: <filter> 
           Mobo: ASUSTeK model: Z97-K v: Rev X.0x serial: <filter> BIOS: American Megatrends 
           v: 2308 date: 11/04/2014 
CPU:       Topology: Quad Core model: Intel Core i7-4790K bits: 64 type: MT MCP arch: Haswell 
           family: 6 model-id: 3C (60) stepping: 3 microcode: 27 L2 cache: 8192 KiB 
           flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 63968 
           Speed: 1200 MHz min/max: 800/4400 MHz Core speeds (MHz): 1: 1197 2: 1199 3: 1200 
           4: 1201 5: 1199 6: 1200 7: 1200 8: 1200 
           Vulnerabilities: Type: l1tf 
           mitigation: PTE Inversion; VMX: conditional cache flushes, SMT vulnerable 
           Type: mds mitigation: Clear CPU buffers; 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 GM206 [GeForce GTX 960] vendor: ASUSTeK driver: nvidia v: 418.74 
           bus ID: 01:00.0 chip ID: 10de:1401 
           Display: x11 server: X.Org 1.20.4 driver: nvidia 
           unloaded: fbdev,modesetting,nouveau,vesa alternate: nv resolution: 1920x1080~60Hz 
           OpenGL: renderer: GeForce GTX 960/PCIe/SSE2 v: 4.6.0 NVIDIA 418.74 direct render: Yes 
Audio:     Device-1: Intel 9 Series Family HD Audio vendor: ASUSTeK driver: snd_hda_intel 
           v: kernel bus ID: 00:1b.0 chip ID: 8086:8ca0 
           Device-2: NVIDIA GM206 High Definition Audio vendor: ASUSTeK driver: snd_hda_intel 
           v: kernel bus ID: 01:00.1 chip ID: 10de:0fba 
           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: d000 bus ID: 03:00.0 chip ID: 10ec:8168 
           IF: eth0 state: up speed: 1000 Mbps duplex: full mac: <filter> 
Drives:    Local Storage: total: 3.75 TiB used: 822.89 GiB (21.4%) 
           ID-1: /dev/sda vendor: Samsung model: SSD 850 EVO 120GB size: 111.79 GiB block size: 
           physical: 512 B logical: 512 B speed: 6.0 Gb/s serial: <filter> rev: 1B6Q scheme: MBR 
           ID-2: /dev/sdb vendor: Western Digital model: WD40EZRX-00SPEB0 size: 3.64 TiB 
           block size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s rotation: 5400 rpm 
           serial: <filter> rev: 0A80 scheme: GPT 
Partition: ID-1: / raw size: 109.76 GiB size: 107.53 GiB (97.97%) used: 11.24 GiB (10.5%) 
           fs: ext4 dev: /dev/sda1 
           ID-2: swap-1 size: 2.00 GiB used: 0 KiB (0.0%) fs: swap swappiness: 15 (default 60) 
           cache pressure: 100 (default) dev: /dev/sda2 
Sensors:   System Temperatures: cpu: 29.8 C mobo: 27.8 C gpu: nvidia temp: 47 C 
           Fan Speeds (RPM): cpu: 0 gpu: nvidia fan: 5% 
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
           Active apt repos in: /etc/apt/sources.list.d/skype-stable.list 
           1: deb [arch=amd64] https://repo.skype.com/deb stable main
           Active apt repos in: /etc/apt/sources.list.d/spotify.list 
           1: deb http://repository.spotify.com stable non-free
           Active apt repos in: /etc/apt/sources.list.d/teamviewer.list 
           1: deb http://linux.teamviewer.com/deb stable main
           No active apt repos in: /etc/apt/sources.list.d/various.list 
Info:      Processes: 239 Uptime: 16m Memory: 15.61 GiB used: 1.30 GiB (8.3%) 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 

[Lupin]

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.

thank you Stevo ! that solved the issue