September 2023 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1215548] New: new coreutils-systemd breaks "uptime"
by bugzilla_noreply＠suse.com 07 Feb '24

07 Feb '24

https://bugzilla.suse.com/show_bug.cgi?id=1215548 Bug ID: 1215548 Summary: new coreutils-systemd breaks "uptime" Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: aarch64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: screening-team-bugs(a)suse.de Reporter: seife(a)novell.slipkontur.de QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- The new coreutils-systemd's "uptime" command reports wrong values: wrong, newer system: raspi4c:~ # grep VERSION_ID /etc/os-release VERSION_ID="20230910" raspi4c:~ # rpm -qf `which uptime` coreutils-systemd-9.4-1.1.aarch64 raspi4c:~ # uptime 06:28:33 up 4 days 21:40, 1 user, load average: 0.16, 0.16, 0.11 raspi4c:~ # cat /proc/uptime 136079.24 225710.69 correct, older system: raspi4a:~ # grep VERSION_ID /etc/os-release VERSION_ID="20230904" raspi4a:~ # rpm -qf `which uptime` coreutils-9.3-1.2.aarch64 raspi4a:~ # uptime 06:28:51 up 1 day 13:48, 1 user, load average: 0.09, 0.16, 0.12 raspi4a:~ # cat /proc/uptime 136093.86 92370.61 These are raspberry pi4's which don't have a realtime clock, so the system clock is wrong on boot. The broken version does not consult the kernel: raspi4c:~ # strace -e file uptime execve("/usr/bin/uptime", ["uptime"], 0xffffe61bb560 /* 48 vars */) = 0 faccessat(AT_FDCWD, "/etc/ld.so.preload", R_OK) = -1 ENOENT (No such file or directory) openat(AT_FDCWD, "/etc/ld.so.cache", O_RDONLY|O_CLOEXEC) = 3 newfstatat(3, "", {st_mode=S_IFREG|0644, st_size=26215, ...}, AT_EMPTY_PATH) = 0 openat(AT_FDCWD, "/lib64/libc.so.6", O_RDONLY|O_CLOEXEC) = 3 newfstatat(3, "", {st_mode=S_IFREG|0755, st_size=2515928, ...}, AT_EMPTY_PATH) = 0 openat(AT_FDCWD, "/usr/lib/locale/locale-archive", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory) openat(AT_FDCWD, "/usr/share/locale/locale.alias", O_RDONLY|O_CLOEXEC) = 3 newfstatat(3, "", {st_mode=S_IFREG|0644, st_size=2940, ...}, AT_EMPTY_PATH) = 0 openat(AT_FDCWD, "/usr/lib/locale/de_DE.utf8/LC_CTYPE", O_RDONLY|O_CLOEXEC) = 3 newfstatat(3, "", {st_mode=S_IFREG|0644, st_size=357744, ...}, AT_EMPTY_PATH) = 0 openat(AT_FDCWD, "/usr/lib64/gconv/gconv-modules.cache", O_RDONLY|O_CLOEXEC) = 3 newfstatat(3, "", {st_mode=S_IFREG|0644, st_size=27012, ...}, AT_EMPTY_PATH) = 0 faccessat(AT_FDCWD, "/var/run/utmpx", F_OK) = -1 ENOENT (No such file or directory) openat(AT_FDCWD, "/var/run/utmp", O_RDONLY|O_CLOEXEC) = 3 openat(AT_FDCWD, "/etc/localtime", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory) newfstatat(1, "", {st_mode=S_IFCHR|0620, st_rdev=makedev(0x88, 0x1), ...}, AT_EMPTY_PATH) = 0 06:30:05 up 4 days 21:41, 1 user, load average: 0.20, 0.18, 0.11 +++ exited with 0 +++ The working version does: raspi4a:~ # strace -e file uptime execve("/usr/bin/uptime", ["uptime"], 0xffffe5952d00 /* 48 vars */) = 0 faccessat(AT_FDCWD, "/etc/ld.so.preload", R_OK) = -1 ENOENT (No such file or directory) openat(AT_FDCWD, "/etc/ld.so.cache", O_RDONLY|O_CLOEXEC) = 3 newfstatat(3, "", {st_mode=S_IFREG|0644, st_size=23327, ...}, AT_EMPTY_PATH) = 0 openat(AT_FDCWD, "/lib64/libc.so.6", O_RDONLY|O_CLOEXEC) = 3 newfstatat(3, "", {st_mode=S_IFREG|0755, st_size=2515928, ...}, AT_EMPTY_PATH) = 0 openat(AT_FDCWD, "/usr/lib/locale/locale-archive", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory) openat(AT_FDCWD, "/usr/share/locale/locale.alias", O_RDONLY|O_CLOEXEC) = 3 newfstatat(3, "", {st_mode=S_IFREG|0644, st_size=2940, ...}, AT_EMPTY_PATH) = 0 openat(AT_FDCWD, "/usr/lib/locale/de_DE.utf8/LC_CTYPE", O_RDONLY|O_CLOEXEC) = 3 newfstatat(3, "", {st_mode=S_IFREG|0644, st_size=357744, ...}, AT_EMPTY_PATH) = 0 openat(AT_FDCWD, "/usr/lib64/gconv/gconv-modules.cache", O_RDONLY|O_CLOEXEC) = 3 newfstatat(3, "", {st_mode=S_IFREG|0644, st_size=27012, ...}, AT_EMPTY_PATH) = 0 faccessat(AT_FDCWD, "/var/run/utmpx", F_OK) = -1 ENOENT (No such file or directory) openat(AT_FDCWD, "/var/run/utmp", O_RDONLY|O_CLOEXEC) = 3 openat(AT_FDCWD, "/proc/uptime", O_RDONLY) = 3 newfstatat(3, "", {st_mode=S_IFREG|0444, st_size=0, ...}, AT_EMPTY_PATH) = 0 openat(AT_FDCWD, "/etc/localtime", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory) newfstatat(1, "", {st_mode=S_IFCHR|0620, st_rdev=makedev(0x88, 0x2), ...}, AT_EMPTY_PATH) = 0 06:30:40 up 1 day 13:49, 1 user, load average: 0.10, 0.15, 0.12 +++ exited with 0 +++ -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1215361] New: "uptime" is dumping core
by bugzilla_noreply＠suse.com 06 Feb '24

06 Feb '24

https://bugzilla.suse.com/show_bug.cgi?id=1215361 Bug ID: 1215361 Summary: "uptime" is dumping core Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: screening-team-bugs(a)suse.de Reporter: nwr10cst-oslnx(a)yahoo.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:109.0) Gecko/20100101 Firefox/115.0 Build Identifier: I just updated to 20230913. This was an update from 20230910. From before the update: twleap:support 1% uname -a Linux twleap 6.4.12-1-default #1 SMP PREEMPT_DYNAMIC Fri Aug 25 08:26:31 UTC 2023 (f5aa89b) x86_64 x86_64 x86_64 GNU/Linux twleap:support 2% uptime 16:23:44 up 0:01, 5 users, load average: 0.67, 0.43, 0.17 twleap:support 3% exit Script done on 2023-09-14 16:23:46-05:00 [COMMAND_EXIT_CODE="0"] From after the update (and a reboot): wleap:rickert 1% uname -a Linux twleap 6.5.2-1-default #1 SMP PREEMPT_DYNAMIC Fri Sep 8 07:32:27 UTC 2023 (fdde566) x86_64 x86_64 x86_64 GNU/Linux twleap:rickert 2% uptime Segmentation fault (core dumped) twleap:rickert 3% exit Script done on 2023-09-14 16:44:50-05:00 [COMMAND_EXIT_CODE="139"] This was in a KVM virtual machine. However, I had already seen the problem on another system (a bare metal install), which is why I knew to get the output before the update on the VM. Apologies if this is a duplicate. The search in bugzilla did not give me anything, and is possibly broken. Reproducible: Always -- You are receiving this mail because: You are on the CC list for the bug.

1 7

[Bug 1215427] New: GCC13 fails to compile some packages with error: unrecognizable insn
by bugzilla_noreply＠suse.com 30 Jan '24

30 Jan '24

https://bugzilla.suse.com/show_bug.cgi?id=1215427 Bug ID: 1215427 Summary: GCC13 fails to compile some packages with error: unrecognizable insn Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: aarch64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Development Assignee: screening-team-bugs(a)suse.de Reporter: guillaume.gardet(a)arm.com QA Contact: qa-bugs(a)suse.de CC: afaerber(a)suse.com, dmueller(a)suse.com, rguenther(a)suse.com Target Milestone: --- Found By: --- Blocker: --- In openSUSE:Factory:ARM:Rings:1-MinimalX we have 3 packages failing the same way: fcitx libcamera Mesa:drivers Maybe related to gcc13 update? https://build.opensuse.org/request/show/1110686 The error log from Mesa:drivers is: [ 1828s] ../src/gallium/frontends/nine/nine_state.c: In function ‘nine_update_state’: [ 1828s] ../src/gallium/frontends/nine/nine_state.c:1316:1: error: unrecognizable insn: [ 1828s] 1316 | } [ 1828s] | ^ [ 1828s] (insn 10725 4838 4840 277 (parallel [ [ 1828s] (set (mem/c:SI (plus:DI (reg/f:DI 29 x29) [ 1828s] (const_int -260 [0xfffffffffffffefc])) [143 %sfp+-260 S4 A32]) [ 1828s] (reg:SI 0 x0 [orig:800 _1297 ] [800])) [ 1828s] (set (mem/c:SI (plus:DI (reg/f:DI 29 x29) [ 1828s] (const_int -256 [0xffffffffffffff00])) [143 %sfp+-256 S4 A32]) [ 1828s] (reg:SI 0 x0 [orig:800 _1297 ] [800])) [ 1828s] ]) "../src/util/bitscan.h":219:22 discrim 1 -1 [ 1828s] (expr_list:REG_DEAD (reg:SI 0 x0 [orig:800 _1297 ] [800]) [ 1828s] (nil))) [ 1828s] during RTL pass: cprop_hardreg [ 1828s] ../src/gallium/frontends/nine/nine_state.c:1316:1: internal compiler error: in extract_insn, at recog.cc:2791 [ 1828s] 0xb8d633 internal_error(char const*, ...) [ 1828s] ???:0 [ 1828s] 0xb83a0b fancy_abort(char const*, int, char const*) [ 1828s] ???:0 [ 1828s] 0x77e717 _fatal_insn(char const*, rtx_def const*, char const*, int, char const*) [ 1828s] ???:0 [ 1828s] 0x77e753 _fatal_insn_not_found(rtx_def const*, char const*, int, char const*) [ 1828s] ???:0 [ 1828s] 0x102b27b extract_insn(rtx_insn*) [ 1828s] ???:0 [ 1828s] Please submit a full bug report, with preprocessed source (by using -freport-bug). [ 1828s] Please include the complete backtrace with any bug report. [ 1828s] See <https://bugs.opensuse.org/> for instructions. [ 1828s] make: *** [/tmp/cc1ZTVEw.mk:47: /tmp/cclOD5f9.ltrans15.ltrans.o] Error 1 [ 1828s] make: *** Waiting for unfinished jobs.... [ 1828s] lto-wrapper: fatal error: make returned 2 exit status [ 1828s] compilation terminated. [ 1828s] /usr/lib64/gcc/aarch64-suse-linux/13/../../../../aarch64-suse-linux/bin/ld: error: lto-wrapper failed [ 1828s] collect2: error: ld returned 1 exit status -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1214049] New: USB audio dies after idle
by bugzilla_noreply＠suse.com 30 Jan '24

30 Jan '24

https://bugzilla.suse.com/show_bug.cgi?id=1214049 Bug ID: 1214049 Summary: USB audio dies after idle Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.4 Hardware: Other OS: openSUSE Leap 15.4 Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: aaron.w2(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 868666 --> https://bugzilla.suse.com/attachment.cgi?id=868666&action=edit lsusb -v output After a recent kernel update within the past week or so I have been experiencing a problem where if audio is stopped for a while it will never restart when using a USB HID audio device. In the logs I see the following: usb_set_interface failed (-19) I have swapped the cable and that made no difference. Note that if audio is constantly active it will continue to work without issues. [33346.442012] usb 7-4: New USB device found, idVendor=1852, idProduct=7022, bcdDevice= 0.01 [33346.442023] usb 7-4: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [33346.442027] usb 7-4: Product: DigiHug USB Audio [33346.442031] usb 7-4: Manufacturer: GFEC ASSP [33346.529561] input: GFEC ASSP DigiHug USB Audio as /devices/pci0000:40/0000:40:07.1/0000:45:00.3/usb7/7-4/7-4:1.0/0003:1852:7022.001B/input/input54 [33346.586066] hid-generic 0003:1852:7022.001B: input,hidraw11: USB HID v1.00 Device [GFEC ASSP DigiHug USB Audio] on usb-0000:45:00.3-4/input0 [33360.314128] usb 3-1.3.1: reset high-speed USB device number 36 using xhci_hcd Note that the audio recovers if I unplug and reconnect the audio device. It does not matter which application is generating the audio. The USB audio device is also plugged directly into a motherboard USB port and not a hub. Desktop is running KDE factory. Kernel is 5.14.21-150400.24.74-default #1 SMP PREEMPT_DYNAMIC I have a lot of USB devices connected. -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1215538] New: systemd-sysusers fails when upgrading packages on WSL with Failed to take /etc/passwd lock
by bugzilla_noreply＠suse.com 29 Jan '24

29 Jan '24

https://bugzilla.suse.com/show_bug.cgi?id=1215538 Bug ID: 1215538 Summary: systemd-sysusers fails when upgrading packages on WSL with Failed to take /etc/passwd lock Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Windows 10 Status: NEW Severity: Normal Priority: P5 - None Component: WSL Assignee: sle-ms(a)suse.de Reporter: brunopitrus(a)hotmail.com QA Contact: qa-c(a)suse.de Target Milestone: --- Found By: --- Blocker: --- When trying to upgrade a Tumbleweed installation on WSL (Windows 10 19045.3448), several core system packages are failing to install: /usr/bin/systemd-sysusers --replace=/usr/lib/sysusers.d/system-user-nobody.conf - Failed to take /etc/passwd lock: Invalid argument error: %prein(system-user-nobody-20170617-25.1.noarch) scriptlet failed, exit status 1 (0/5) Executing prein script for: system-user-nobody-20170617-25.1.noarch .................[błąd] error: system-user-nobody-20170617-25.1.noarch: install failed /usr/bin/systemd-sysusers --replace=/usr/lib/sysusers.d/system-user-man.conf - Failed to take /etc/passwd lock: Invalid argument error: %prein(system-user-man-20170617-25.1.noarch) scriptlet failed, exit status 1 (0/5) Executing prein script for: system-user-man-20170617-25.1.noarch ....................[błąd] error: system-user-man-20170617-25.1.noarch: install failed /usr/bin/systemd-sysusers --replace=/usr/lib/sysusers.d/system-user-lp.conf - Failed to take /etc/passwd lock: Invalid argument error: %prein(system-user-lp-20170617-25.1.noarch) scriptlet failed, exit status 1 (0/5) Executing prein script for: system-user-lp-20170617-25.1.noarch .....................[błąd] error: system-user-lp-20170617-25.1.noarch: install failed /usr/bin/systemd-sysusers --replace=/usr/lib/sysusers.d/system-user-games.conf - Failed to take /etc/passwd lock: Invalid argument error: %prein(system-user-games-20170617-25.1.noarch) scriptlet failed, exit status 1 (0/5) Executing prein script for: system-user-games-20170617-25.1.noarch ..................[błąd] error: system-user-games-20170617-25.1.noarch: install failed /usr/bin/systemd-sysusers --replace=/usr/lib/sysusers.d/dbus.conf - Failed to take /etc/passwd lock: Invalid argument error: %prein(dbus-1-common-1.14.8-1.3.noarch) scriptlet failed, exit status 1 (0/5) Executing prein script for: dbus-1-common-1.14.8-1.3.noarch .........................[błąd] error: dbus-1-common-1.14.8-1.3.noarch: install failed error: system-user-nobody-20170617-24.13.noarch: erase skipped error: system-user-man-20170617-24.13.noarch: erase skipped error: system-user-lp-20170617-24.13.noarch: erase skipped error: system-user-games-20170617-24.13.noarch: erase skipped error: dbus-1-common-1.14.8-1.2.noarch: erase skipped -- You are receiving this mail because: You are on the CC list for the bug.

1 8

[Bug 1214420] New: [LXQt]compton-conf / picom
by bugzilla_noreply＠suse.com 27 Jan '24

27 Jan '24

https://bugzilla.suse.com/show_bug.cgi?id=1214420 Bug ID: 1214420 Summary: [LXQt]compton-conf / picom Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: LXQt Assignee: mvetter(a)suse.com Reporter: psi089(a)gmx.de QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Problem: After installation picom did not start because it lacked a config file. lxqt-config starts compton-conf which writes to .config/compton.conf but picom is used as compositor and expects to read from .config/picom.conf Further: on manual startup picom complains about deprecated config entries that got written by the currently used tool. What is the solution? For now I just softlinked picom.conf to compton.conf, but it looks like some clean fix is needed and to make it work out of the box. -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1215062] New: Ctrl+Alt+B in lokalize no longer works
by bugzilla_noreply＠suse.com 22 Jan '24

22 Jan '24

https://bugzilla.suse.com/show_bug.cgi?id=1215062 Bug ID: 1215062 Summary: Ctrl+Alt+B in lokalize no longer works Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: KDE Applications Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: freek(a)opensuse.org QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- I an using tumbleweed:20230902 and since a few days Ctrl+Alt+B in lokalize to insert exact matches in fuzzy or empty elements in a .po file no longer works. When I walk through these elements the Translation Memory shows exact translations (100%), but they are not inserted using Ctrl+Alt+B. I have to use Ctrl+1 to copy the translation from TM into the element. -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1214460] New: s390x crosscompiler does not seem functional, missing -lgcc, impeding upstream QEMU work (tcg tests)
by bugzilla_noreply＠suse.com 08 Jan '24

08 Jan '24

https://bugzilla.suse.com/show_bug.cgi?id=1214460 Bug ID: 1214460 Summary: s390x crosscompiler does not seem functional, missing -lgcc, impeding upstream QEMU work (tcg tests) Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Development Assignee: screening-team-bugs(a)suse.de Reporter: claudio.fontana(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Hello, I am trying to run the QEMU gcc tests for s390x, and these tests require a fully functional s390x crosscompiler in order to build the test code. Unfortunately, after installing the packages: zypper install cross-s390x-gcc13 cross-s390x-binutils cross-s390x-linux-glibc-devel still the libgcc seems missing: /usr/lib64/gcc/s390x-suse-linux/13/ld: cannot find -lgcc: No such file or directory This blocks the current QEMU work to fix QEMU emulation errors on S390x. -- You are receiving this mail because: You are on the CC list for the bug.

1 17

[Bug 1213477] New: Update to gutenprint 5.3 broke cups config
by bugzilla_noreply＠suse.com 05 Jan '24

05 Jan '24

https://bugzilla.suse.com/show_bug.cgi?id=1213477 Bug ID: 1213477 Summary: Update to gutenprint 5.3 broke cups config Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Printing Assignee: jsmeix(a)suse.com Reporter: dheidler(a)suse.com QA Contact: jsmeix(a)suse.com Target Milestone: --- Found By: --- Blocker: --- From cups log: E [19/Jul/2023:14:07:42 +0200] Samsung_Samsung_ML-2525W: Datei \"/usr/lib/cups/filter/rastertogutenprint.5.2\" nicht verfügbar: No such file or directory E [19/Jul/2023:14:07:42 +0200] [Job 49] Unable to start filter "rastertogutenprint.5.2" - No such file or directory. E [19/Jul/2023:14:07:42 +0200] [Job 49] Stopping job because the scheduler could not execute a filter. From cups config: <Printer Samsung_Samsung_ML-2525W> PrinterId 45 UUID urn:uuid:70334a01-d800-39ed-5a4e-5e4f45e9c01f Info Samsung Samsung ML-2525W Location MakeModel Samsung ML-2550 - CUPS+Gutenprint v5.2.15 DeviceURI socket://10.131.0.20 State Idle StateTime 1689768462 ConfigTime 1689767864 Type 8392724 Accepting Yes Shared No JobSheets none none QuotaPeriod 0 PageLimit 0 KLimit 0 OpPolicy default ErrorPolicy stop-printer Attribute marker-colors \#000000 Attribute marker-levels 50 Attribute marker-names Toner S/N:CRUM-11000311613 Attribute marker-types toner Attribute marker-change-time 1683056782 </Printer> It seems that the config was not updated breaking the printing driver as the config was still pointing to gutenprint 5.2. This should be somehow prevented - eg by not including the version number in the config or updating the config automatically. -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1215631] New: Intuos4 tablet mouse clicks non-functional with GNOME 45
by bugzilla_noreply＠suse.com 05 Jan '24

05 Jan '24

https://bugzilla.suse.com/show_bug.cgi?id=1215631 Bug ID: 1215631 Summary: Intuos4 tablet mouse clicks non-functional with GNOME 45 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Major Priority: P5 - None Component: GNOME Assignee: gnome-bugs(a)suse.de Reporter: hendersj(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Attempted to update my Tumbleweed installation to GNOME 45, and had the entire desktop crash multiple times. After getting extensions disabled and rebooting a few times, the desktop mostly stabilized, but attempting to use my mouse on my Intuos4 tablet was an exercise in futility. For the most part, mouse clicks were not recognized at all. I connected a bluetooth mouse, and that was recognized. On GNOME 44, the Wacom mouse works mostly fine (scroll wheel doesn't work in certain applications, but it's usable). Launching the wacom settings applet in gnome-settings caused the desktop to crash with the "Oh No, something went wrong" error message. I was able to roll back to GNOME 44, but would like to know what information would be useful to get this issue resolved so I can do a dup on the system. -- You are receiving this mail because: You are on the CC list for the bug.

1 3