MX-21 RC1 feedback (Xfce)

[dolphin_oracle]

Small thing, but panel opacity can't be set. Whatever I do, it stays 100% opaque. Compositing is turned on in Window Manager Tweaks.

Please post your Quick System Info so we can identify if it’s something system specific.

Code: Select all

System:    Host: <filter> Kernel: 5.10.0-8-amd64 x86_64 bits: 64 compiler: N/A 
           parameters: BOOT_IMAGE=/vmlinuz-5.10.0-8-amd64 
           root=UUID=<filter> ro quiet splash 
           init=/lib/systemd/systemd 
           Desktop: Xfce 4.16.0 tk: Gtk 3.24.24 info: xfce4-panel wm: xfwm4 dm: LightDM 1.26.0 
           Distro: MX-21_rc1_x64 Wildflower October 5  2021 base: Debian GNU/Linux 11 (bullseye) 
Machine:   Type: Virtualbox System: innotek product: VirtualBox v: 1.2 serial: <filter> 
           Chassis: Oracle Corporation type: 1 serial: <filter> 
           Mobo: Oracle model: VirtualBox v: 1.2 serial: <filter> BIOS: innotek v: VirtualBox 
           date: 12/01/2006 
CPU:       Topology: Dual Core model: AMD A8-6500T APU with Radeon HD Graphics bits: 64 
           type: MCP arch: Piledriver family: 15 (21) model-id: 13 (19) stepping: 1 
           microcode: 6000626 L2 cache: 2048 KiB 
           flags: avx lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 bogomips: 8441 
           Speed: 2110 MHz min/max: N/A Core speeds (MHz): 1: 2110 2: 2110 
           Vulnerabilities: Type: itlb_multihit status: Not affected 
           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, STIBP: disabled, RSB filling 
           Type: srbds status: Not affected 
           Type: tsx_async_abort status: Not affected 
Graphics:  Device-1: VMware SVGA II Adapter driver: vmwgfx v: 2.18.0.0 bus ID: 00:02.0 
           chip ID: 15ad:0405 
           Display: x11 server: X.Org 1.20.11 driver: vmware unloaded: fbdev,modesetting,vesa 
           resolution: 1920x1080~60Hz 
           OpenGL: renderer: llvmpipe (LLVM 11.0.1 256 bits) v: 4.5 Mesa 20.3.5 compat-v: 3.1 
           direct render: Yes 
Audio:     Device-1: Intel 82801AA AC97 Audio vendor: Dell driver: snd_intel8x0 v: kernel 
           bus ID: 00:05.0 chip ID: 8086:2415 
           Sound Server: ALSA v: k5.10.0-8-amd64 
Network:   Device-1: Intel 82540EM Gigabit Ethernet driver: e1000 v: kernel port: d020 
           bus ID: 00:03.0 chip ID: 8086:100e 
           IF: eth0 state: up speed: 1000 Mbps duplex: full mac: <filter> 
           Device-2: Intel 82371AB/EB/MB PIIX4 ACPI type: network bridge driver: piix4_smbus 
           v: N/A port: d200 bus ID: 00:07.0 chip ID: 8086:7113 
Drives:    Local Storage: total: 118.97 GiB used: 819.21 GiB (688.6%) 
           ID-1: /dev/sda vendor: VirtualBox model: VBOX HARDDISK size: 118.97 GiB block size: 
           physical: 512 B logical: 512 B speed: 3.0 Gb/s serial: <filter> rev: 1.0 scheme: MBR 
Partition: ID-1: / raw size: 24.41 GiB size: 23.86 GiB (97.74%) used: 5.83 GiB (24.4%) fs: ext4 
           dev: /dev/sda2 
           ID-2: /boot raw size: 1.95 GiB size: 1.89 GiB (96.54%) used: 101.4 MiB (5.3%) 
           fs: ext4 dev: /dev/sda3 
           ID-3: /home raw size: 86.36 GiB size: 84.45 GiB (97.79%) used: 2.39 GiB (2.8%) 
           fs: ext4 dev: /dev/sda4 
           ID-4: swap-1 size: 6.25 GiB used: 0 KiB (0.0%) fs: swap swappiness: 15 (default 60) 
           cache pressure: 100 (default) dev: /dev/sda1 
Sensors:   Message: No sensors data was found. Is sensors configured? 
Repos:     No active apt repos in: /etc/apt/sources.list 
           Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list 
           1: deb http://deb.debian.org/debian bullseye-updates main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/debian.list 
           1: deb http://deb.debian.org/debian bullseye main contrib non-free
           2: deb http://security.debian.org/debian-security bullseye-security main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/mx.list 
           1: deb http://ftp.halifax.rwth-aachen.de/mxlinux/packages/mx/repo/ bullseye main non-free
Info:      Processes: 195 Uptime: 7m Memory: 3.02 GiB used: 1.10 GiB (36.4%) Init: systemd 
           v: 247 runlevel: 5 default: 5 Compilers: gcc: 10.2.1 alt: 10 Shell: quick-system-in 
           running in: quick-system-in inxi: 3.0.36 

I amended my earlier post saying that after a reboot, the panel opacity is now working as intended. Sorry to cause confusion - but on 19.4 or earlier, and in the beta versions of 21, changes took effect immediately, I assume it may be a tiny glitch which will be ironed out before final release.

they xfce dev that takes care of the panel is slightly hard to work with, but there is a bug report filed at Xfce on this issue. I set up a automatic restart of the panel when the panel preferences are called up from inside MX-Tweak, but I suspect that almost no one pulls up the preferences that way.

[hebelwirkung]

Please post your Quick System Info so we can identify if it’s something system specific.

Code: Select all

System:    Host: <filter> Kernel: 5.10.0-8-amd64 x86_64 bits: 64 compiler: N/A 
           parameters: BOOT_IMAGE=/vmlinuz-5.10.0-8-amd64 
           root=UUID=<filter> ro quiet splash 
           init=/lib/systemd/systemd 
           Desktop: Xfce 4.16.0 tk: Gtk 3.24.24 info: xfce4-panel wm: xfwm4 dm: LightDM 1.26.0 
           Distro: MX-21_rc1_x64 Wildflower October 5  2021 base: Debian GNU/Linux 11 (bullseye) 
Machine:   Type: Virtualbox System: innotek product: VirtualBox v: 1.2 serial: <filter> 
           Chassis: Oracle Corporation type: 1 serial: <filter> 
           Mobo: Oracle model: VirtualBox v: 1.2 serial: <filter> BIOS: innotek v: VirtualBox 
           date: 12/01/2006 
CPU:       Topology: Dual Core model: AMD A8-6500T APU with Radeon HD Graphics bits: 64 
           type: MCP arch: Piledriver family: 15 (21) model-id: 13 (19) stepping: 1 
           microcode: 6000626 L2 cache: 2048 KiB 
           flags: avx lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 bogomips: 8441 
           Speed: 2110 MHz min/max: N/A Core speeds (MHz): 1: 2110 2: 2110 
           Vulnerabilities: Type: itlb_multihit status: Not affected 
           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, STIBP: disabled, RSB filling 
           Type: srbds status: Not affected 
           Type: tsx_async_abort status: Not affected 
Graphics:  Device-1: VMware SVGA II Adapter driver: vmwgfx v: 2.18.0.0 bus ID: 00:02.0 
           chip ID: 15ad:0405 
           Display: x11 server: X.Org 1.20.11 driver: vmware unloaded: fbdev,modesetting,vesa 
           resolution: 1920x1080~60Hz 
           OpenGL: renderer: llvmpipe (LLVM 11.0.1 256 bits) v: 4.5 Mesa 20.3.5 compat-v: 3.1 
           direct render: Yes 
Audio:     Device-1: Intel 82801AA AC97 Audio vendor: Dell driver: snd_intel8x0 v: kernel 
           bus ID: 00:05.0 chip ID: 8086:2415 
           Sound Server: ALSA v: k5.10.0-8-amd64 
Network:   Device-1: Intel 82540EM Gigabit Ethernet driver: e1000 v: kernel port: d020 
           bus ID: 00:03.0 chip ID: 8086:100e 
           IF: eth0 state: up speed: 1000 Mbps duplex: full mac: <filter> 
           Device-2: Intel 82371AB/EB/MB PIIX4 ACPI type: network bridge driver: piix4_smbus 
           v: N/A port: d200 bus ID: 00:07.0 chip ID: 8086:7113 
Drives:    Local Storage: total: 118.97 GiB used: 819.21 GiB (688.6%) 
           ID-1: /dev/sda vendor: VirtualBox model: VBOX HARDDISK size: 118.97 GiB block size: 
           physical: 512 B logical: 512 B speed: 3.0 Gb/s serial: <filter> rev: 1.0 scheme: MBR 
Partition: ID-1: / raw size: 24.41 GiB size: 23.86 GiB (97.74%) used: 5.83 GiB (24.4%) fs: ext4 
           dev: /dev/sda2 
           ID-2: /boot raw size: 1.95 GiB size: 1.89 GiB (96.54%) used: 101.4 MiB (5.3%) 
           fs: ext4 dev: /dev/sda3 
           ID-3: /home raw size: 86.36 GiB size: 84.45 GiB (97.79%) used: 2.39 GiB (2.8%) 
           fs: ext4 dev: /dev/sda4 
           ID-4: swap-1 size: 6.25 GiB used: 0 KiB (0.0%) fs: swap swappiness: 15 (default 60) 
           cache pressure: 100 (default) dev: /dev/sda1 
Sensors:   Message: No sensors data was found. Is sensors configured? 
Repos:     No active apt repos in: /etc/apt/sources.list 
           Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list 
           1: deb http://deb.debian.org/debian bullseye-updates main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/debian.list 
           1: deb http://deb.debian.org/debian bullseye main contrib non-free
           2: deb http://security.debian.org/debian-security bullseye-security main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/mx.list 
           1: deb http://ftp.halifax.rwth-aachen.de/mxlinux/packages/mx/repo/ bullseye main non-free
Info:      Processes: 195 Uptime: 7m Memory: 3.02 GiB used: 1.10 GiB (36.4%) Init: systemd 
           v: 247 runlevel: 5 default: 5 Compilers: gcc: 10.2.1 alt: 10 Shell: quick-system-in 
           running in: quick-system-in inxi: 3.0.36 

I amended my earlier post saying that after a reboot, the panel opacity is now working as intended. Sorry to cause confusion - but on 19.4 or earlier, and in the beta versions of 21, changes took effect immediately, I assume it may be a tiny glitch which will be ironed out before final release.

they xfce dev that takes care of the panel is slightly hard to work with, but there is a bug report filed at Xfce on this issue. I set up a automatic restart of the panel when the panel preferences are called up from inside MX-Tweak, but I suspect that almost no one pulls up the preferences that way.

Yes, probably most people will edit the panel via the panel menu itself. But I'm sure if you catch the panel dev at an opportune moment, he'll agree to fix this :-)

[Eadwine Rose]

When I have changed things in the panel and I select in tweak to restore the default I am still (like in B2) left with no panel at all. I have to reboot (logout login, wager works too) and then it shows up.

Restore backup panel from tweak DOES work. It takes a number of seconds, I was thinking it was a goner and then as I was about to hit the logout button it suddenly popped up. Maybe that was the programmed panel restart that kicked in?

[dolphin_oracle]

When I have changed things in the panel and I select in tweak to restore the default I am still (like in B2) left with no panel at all. I have to reboot (logout login, wager works too) and then it shows up.

Restore backup panel from tweak DOES work. It takes a number of seconds, I was thinking it was a goner and then as I was about to hit the logout button it suddenly popped up. Maybe that was the programmed panel restart that kicked in?

both should take around 7 seconds to happen. the routines are very similar but there is obviously a hiccup somewhere. could be that my restart routine is too agressive, will look at that.

[dolphin_oracle]

if you restore a panel while the preferences dialog is open, there could be strange effects.

[Eadwine Rose]

Just MX Tweak IIRC.

[dirkduplooy]

Hi, how do I do an in-place upgrade of Beta 2 to RC1? When I installed Beta 2 it was alleged it will be possible and currently, I suffer from bandwidth availability issues and it will help a lot if I can do as such. Thanks

[dolphin_oracle]

Just do regular updates. We won’t change the name of the ISO until they release final although

[dirkduplooy]

Just do regular updates. We won’t change the name of the ISO until they release final although

Hi dolphin thanks for the reply, I do the updates regulary still this is the system info:

System: Host: <filter> Kernel: 5.10.0-8-amd64 x86_64 bits: 64 compiler: N/A
parameters: BOOT_IMAGE=/boot/vmlinuz-5.10.0-8-amd64
root=UUID=<filter> ro quiet splash
Desktop: Xfce 4.16.0 tk: Gtk 3.24.24 info: xfce4-panel wm: xfwm4 dm: LightDM 1.26.0
Distro: MX-21_beta2_x64 Wildflower September 4 2021
base: Debian GNU/Linux 11 (bullseye)

[dolphin_oracle]

Just do regular updates. We won’t change the name of the ISO until they release final although

Hi dolphin thanks for the reply, I do the updates regulary still this is the system info:

System: Host: <filter> Kernel: 5.10.0-8-amd64 x86_64 bits: 64 compiler: N/A
parameters: BOOT_IMAGE=/boot/vmlinuz-5.10.0-8-amd64
root=UUID=<filter> ro quiet splash
Desktop: Xfce 4.16.0 tk: Gtk 3.24.24 info: xfce4-panel wm: xfwm4 dm: LightDM 1.26.0
Distro: MX-21_beta2_x64 Wildflower September 4 2021
base: Debian GNU/Linux 11 (bullseye)

As I said we don’t change the name till final release so that’s good.