Page 17 of 21
Re: MX-21 RC1 feedback (Xfce)
Posted: Mon Oct 11, 2021 9:38 am
by dolphin_oracle
entropyfoe wrote: Mon Oct 11, 2021 9:35 am
I got all the synaptic upgrades to the RC1 yesterday including the new kernel. 5.10-0-8 to the -9.
I accepted all upgrades. I rebooted, but it remained on the old kernel.
So, I went back to the MX 19.4 install and update-grub as root.
Then when going back to rc1, the new kernel is loaded.
I guess this is the expected behavior, right?
yes. the grub update that happens during kernel update will not affect a grub menu that is controlled by a different installation.
Re: MX-21 RC1 feedback (Xfce)
Posted: Mon Oct 11, 2021 11:20 am
by AdamK
AdamK wrote: Thu Oct 07, 2021 7:34 am
Small bug report:
Using F4 for the Drop down terminal only works on the Primary Display. Even though my cursor is on another display, the drop down appears on the primary.
Move to monitor with pointer is checked in Preferences -> Drop-down tab -> Position.
Bump.
Anyone experiencing the same?
Re: MX-21 RC1 feedback (Xfce)
Posted: Mon Oct 11, 2021 6:05 pm
by Stuart_M
AdamK wrote: Mon Oct 11, 2021 11:20 am
AdamK wrote: Thu Oct 07, 2021 7:34 am
Small bug report:
Using F4 for the Drop down terminal only works on the Primary Display. Even though my cursor is on another display, the drop down appears on the primary.
Move to monitor with pointer is checked in Preferences -> Drop-down tab -> Position.
Bump.
Anyone experiencing the same?
I thought I'd try on my dual-monitor setup and yes, the same incorrect behavior exists with me as well.
After pressing F4, the Terminal drop-down will only appear on my primary monitor regardless of which monitor my mouse pointer is on, and yes, the "Move to monitor with pointer" is enabled in the drop-down Terminal Preferences > "Drop-down" tab as shown in the below image. That setting does not have any affect, hence the problem.
Drop-down_Terminal_Preferences_drop-down_tab.png
As a side note, MX-19.4 works wonderfully well in this regard - enabling or disabling "Move to monitor with pointer" does just as it says it will.
Re: MX-21 RC1 feedback (Xfce)
Posted: Mon Oct 11, 2021 6:13 pm
by Eadwine Rose
Confirmed here as well, just tried.
Re: MX-21 RC1 feedback (Xfce)
Posted: Tue Oct 12, 2021 3:30 pm
by Sigi
May be could wireguard 1.0.20210223-1 in Stable Repo update to 1.0.20210606 / tools 1.0.20210914?
https://www.wireguard.com/install/
Re: MX-21 RC1 feedback (Xfce)
Posted: Tue Oct 12, 2021 8:34 pm
by Feuerkl1nge
I am experiencing bugs with libguestfs-tools.
As linked on
https://libguestfs.org/ I reported the bug to
https://bugzilla.redhat.com/.
I inform the MX devs here to please be aware of it.
answer on bugzilla.redhat.com
Richard W.M. Jones 2021-10-12 20:31:08 UTC
Thanks for providing the information. The libguestfs-test-tool
output certainly suggests a major problem with the package on MX Linux
(derived from Debian).
I think it's very likely that the following upstream package
should fix the problem:
https://github.com/libguestfs/libguestf ... 5100853890
It's best to inform your distribution of the problem so they
can try including this patch, but in the meantime you can try
this workaround:
echo mount > /usr/lib/x86_64-linux-gnu/guestfs/supermin.d/zz-mount
edit
Richard W.M. Jones 2021-10-12 20:31:55 UTC
> I think it's very likely that the following upstream package
patch, not package
Re: MX-21 RC1 feedback (Xfce)
Posted: Wed Oct 13, 2021 12:24 am
by SwampRabbit
Feuerkl1nge wrote: Tue Oct 12, 2021 8:34 pm
I am experiencing bugs with libguestfs-tools.
As linked on
https://libguestfs.org/ I reported the bug to
https://bugzilla.redhat.com/.
I inform the MX devs here to please be aware of it.
answer on bugzilla.redhat.com
Richard W.M. Jones 2021-10-12 20:31:08 UTC
Thanks for providing the information. The libguestfs-test-tool
output certainly suggests a major problem with the package on MX Linux
(derived from Debian).
I think it's very likely that the following upstream package
should fix the problem:
https://github.com/libguestfs/libguestf ... 5100853890
It's best to inform your distribution of the problem so they
can try including this patch, but in the meantime you can try
this workaround:
echo mount > /usr/lib/x86_64-linux-gnu/guestfs/supermin.d/zz-mount
Thanks for that!
I just checked to see if Debian added this patch to libguestfs (1:1.44.2-1) that is in Bookworm and Sid, looks like they haven't.
I see that the fix commit is on 1.46.0 master, Debian doesn't have that version yet, but....
I wonder if we can package 1.44.2 with it. Give me some time to test build 1.44.2 and create a patch.
Re: MX-21 RC1 feedback (Xfce)
Posted: Wed Oct 13, 2021 9:29 am
by hebelwirkung
I've been using RC1 since it was released and have had next to no problems; it's amazing how smoothly everything is working already (in Virtualbox anyway). The thing that grates - okay, takes a little getting used to - is the CSD in some apps, but that's XFCE and has nothing to do with MX21.
One small thing though - for the second time in a few days, my keyboard layout has set itself back from German, which I usually use, to English (US) which is what I use for my system defaults. First time this happened was overnight when I wasn't at the computer. Just now, it occurred while I was working. I had to reset it manually and reboot. German layout is active again, but oddly enough, when I checked after rebooting, the keyboard layout option for English (US), formerly displayed, has now vanished from the display. It's still in the drop down list but I'm not going to set it as an option again for now.
Code: Select all
System: Host: <filter> Kernel: 5.10.0-9-amd64 x86_64 bits: 64 compiler: N/A
parameters: BOOT_IMAGE=/vmlinuz-5.10.0-9-amd64
root=UUID=<filter> ro quiet splash
init=/lib/systemd/systemd
Desktop: Xfce 4.16.0 tk: Gtk 3.24.24 info: xfce4-panel, cairo-dock 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-9-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: 866.24 GiB (728.1%)
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: 7.88 GiB (33.0%) fs: ext4
dev: /dev/sda2
ID-2: /boot raw size: 1.95 GiB size: 1.89 GiB (96.54%) used: 183.9 MiB (9.5%)
fs: ext4 dev: /dev/sda3
ID-3: /home raw size: 86.36 GiB size: 84.45 GiB (97.79%) used: 20.32 GiB (24.1%)
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
Active apt repos in: /etc/apt/sources.list.d/vivaldi.list
1: deb http://repo.vivaldi.com/stable/deb/ stable main
Info: Processes: 209 Uptime: 2m Memory: 3.02 GiB used: 745.8 MiB (24.1%) 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
Re: MX-21 RC1 feedback (Xfce)
Posted: Wed Oct 13, 2021 11:19 am
by dolphin_oracle
hebelwirkung wrote: Wed Oct 13, 2021 9:29 am
I've been using RC1 since it was released and have had next to no problems; it's amazing how smoothly everything is working already (in Virtualbox anyway). The thing that grates - okay, takes a little getting used to - is the CSD in some apps, but that's XFCE and has nothing to do with MX21.
One small thing though - for the second time in a few days, my keyboard layout has set itself back from German, which I usually use, to English (US) which is what I use for my system defaults. First time this happened was overnight when I wasn't at the computer. Just now, it occurred while I was working. I had to reset it manually and reboot. German layout is active again, but oddly enough, when I checked after rebooting, the keyboard layout option for English (US), formerly displayed, has now vanished from the display. It's still in the drop down list but I'm not going to set it as an option again for now.
Code: Select all
System: Host: <filter> Kernel: 5.10.0-9-amd64 x86_64 bits: 64 compiler: N/A
parameters: BOOT_IMAGE=/vmlinuz-5.10.0-9-amd64
root=UUID=<filter> ro quiet splash
init=/lib/systemd/systemd
Desktop: Xfce 4.16.0 tk: Gtk 3.24.24 info: xfce4-panel, cairo-dock 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-9-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: 866.24 GiB (728.1%)
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: 7.88 GiB (33.0%) fs: ext4
dev: /dev/sda2
ID-2: /boot raw size: 1.95 GiB size: 1.89 GiB (96.54%) used: 183.9 MiB (9.5%)
fs: ext4 dev: /dev/sda3
ID-3: /home raw size: 86.36 GiB size: 84.45 GiB (97.79%) used: 20.32 GiB (24.1%)
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
Active apt repos in: /etc/apt/sources.list.d/vivaldi.list
1: deb http://repo.vivaldi.com/stable/deb/ stable main
Info: Processes: 209 Uptime: 2m Memory: 3.02 GiB used: 745.8 MiB (24.1%) 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
there is a keyboard flag switcher that should be running when more than one keyboard is defined. X also has a keycombo that will do a switch, currently set at rcontrol+rshift.
Re: MX-21 RC1 feedback (Xfce)
Posted: Wed Oct 13, 2021 2:35 pm
by hebelwirkung
dolphin_oracle wrote: Wed Oct 13, 2021 11:19 am
hebelwirkung wrote: Wed Oct 13, 2021 9:29 am
I've been using RC1 since it was released and have had next to no problems; it's amazing how smoothly everything is working already (in Virtualbox anyway). The thing that grates - okay, takes a little getting used to - is the CSD in some apps, but that's XFCE and has nothing to do with MX21.
One small thing though - for the second time in a few days, my keyboard layout has set itself back from German, which I usually use, to English (US) which is what I use for my system defaults. First time this happened was overnight when I wasn't at the computer. Just now, it occurred while I was working. I had to reset it manually and reboot. German layout is active again, but oddly enough, when I checked after rebooting, the keyboard layout option for English (US), formerly displayed, has now vanished from the display. It's still in the drop down list but I'm not going to set it as an option again for now.
Code: Select all
System: Host: <filter> Kernel: 5.10.0-9-amd64 x86_64 bits: 64 compiler: N/A
parameters: BOOT_IMAGE=/vmlinuz-5.10.0-9-amd64
root=UUID=<filter> ro quiet splash
init=/lib/systemd/systemd
Desktop: Xfce 4.16.0 tk: Gtk 3.24.24 info: xfce4-panel, cairo-dock 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-9-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: 866.24 GiB (728.1%)
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: 7.88 GiB (33.0%) fs: ext4
dev: /dev/sda2
ID-2: /boot raw size: 1.95 GiB size: 1.89 GiB (96.54%) used: 183.9 MiB (9.5%)
fs: ext4 dev: /dev/sda3
ID-3: /home raw size: 86.36 GiB size: 84.45 GiB (97.79%) used: 20.32 GiB (24.1%)
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
Active apt repos in: /etc/apt/sources.list.d/vivaldi.list
1: deb http://repo.vivaldi.com/stable/deb/ stable main
Info: Processes: 209 Uptime: 2m Memory: 3.02 GiB used: 745.8 MiB (24.1%) 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
there is a keyboard flag switcher that should be running when more than one keyboard is defined. X also has a keycombo that will do a switch, currently set at rcontrol+rshift.
Yes, I'm aware of the switcher; the thing puzzling me is that without my doing anything, a keyboard layout may suddenly switch from one to another. It's no big deal - just somewhat mysterious. The fact that now, one of my two defined keyboard settings is no longer displayed, seems odd as well. I've never had that happen with MX19. Again, it's trifling but weird :-)