February 2024 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1217350] New: Some Electron-based applications are unable to detect dark mode
by bugzilla_noreply＠suse.com 01 May '24

01 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1217350 Bug ID: 1217350 Summary: Some Electron-based applications are unable to detect dark mode Classification: openSUSE Product: openSUSE Aeon Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Minor Priority: P5 - None Component: Desktop Environment Assignee: rbrown(a)suse.com Reporter: ars2swim(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 870861 --> https://bugzilla.suse.com/attachment.cgi?id=870861&action=edit Visual Studio Code, though preconfigured by default with a dark theme, has a light titlebar, suggesting that Electron detects a light theme in the system. Some Electron-based applications are unable to detect that the system is running with a dark theme, despite dark mode being the default configuration for openSUSE Aeon. This can lead to a lack of UI consistency. I noticed this primarily in apps like Visual Studio Code and Signal. It's worth pointing out that this doesn't occur on every Electron app (namely, the Webcord Flatpak is able to handle theming just fine). I'll also point out that this isn't necessarily an issue with the apps alone or GNOME, because the aforementioned apps--whether packaged as a Flatpak, tarball, or run within a distrobox--do correctly use a dark theme on Ubuntu 23.10. I'm not an expert on SELinux, but it is my best guess as to why this is happening. -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1213055] New: locale problems in the default distrobox configuration
by bugzilla_noreply＠suse.com 01 May '24

01 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1213055 Bug ID: 1213055 Summary: locale problems in the default distrobox configuration Classification: openSUSE Product: openSUSE Aeon Version: Current Hardware: All OS: Other Status: NEW Severity: Minor Priority: P5 - None Component: Distrobox Assignee: rbrown(a)suse.com Reporter: shadenk30011(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/114.0.0.0 Safari/537.36 Build Identifier: When creating a new container using "distrobox-create" the container fails to display directory names properly. For example the directory named "Stažené" shows up as "'Sta'$'\305\276''en'$'\303\251'" when using ls. Reproducible: Always Steps to Reproduce: 1. Use the czech locale 2. Create a directory inside the home that uses one of the offending symbols 3. Create a new distrobox container and run "ls" Actual Results: Directory name isn't properly displayed. Expected Results: Directory name is properly displayed. A workaround is to install the "glibc-locale" package. This can be automated by adding 'container_additional_packages="glibc-locale"' into the distrobox configuration. -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1213537] New: myrb / myrs drivers cause hang on boot when using a Mylex AcceleRAID 170 (DAC960)
by bugzilla_noreply＠suse.com 30 Apr '24

30 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1213537 Bug ID: 1213537 Summary: myrb / myrs drivers cause hang on boot when using a Mylex AcceleRAID 170 (DAC960) Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.5 Hardware: x86-64 OS: openSUSE Leap 15.5 Status: NEW Severity: Major Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: medwards-suse(a)mirkwood.net QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 868350 --> https://bugzilla.suse.com/attachment.cgi?id=868350&action=edit dmesg Booting opensuse leap 15.5 fails on this machine - shortly after the myrb and myrs drivers load and detect the AcceleRAID 170 and drives connected to this card, booting simply stops. Waiting for a few minutes will let me see kernel warnings about hung processes, but booting never completes at this point. Adding modprobe.blacklist=myrb and modprobe.blacklist=myrs to the kernel commandline lets boot complete, though obviously without the AcceleRAID card in use. Once booted, I was able to enable dyndbg for these two drivers: # for d in myr{s,b}; do echo 'file drivers/scsi/${d}.c +p' > /sys/kernel/debug/dynamic_debug/control; done Loading the drivers manually caused the modprobe for myrs to hang (myrb loaded w/o issue), leading me to believe the problem lies within the myrs driver. dyndbg of myrb + myrs: drivers/scsi/myrs.c:2114 [myrs]myrs_monitor =_ "monitor tick\012" drivers/scsi/myrs.c:1822 [myrs]myrs_slave_alloc =_ "Logical device mapping %d:%d:%d -> %d\012" drivers/scsi/myrs.c:471 [myrs]myrs_get_fwstatus =_ "Sending GetHealthStatus\012" drivers/scsi/myrs.c:338 [myrs]myrs_get_pdev_info =_ "Sending GetPhysicalDeviceInfoValid for pdev %d:%d:%d\012" drivers/scsi/myrs.c:249 [myrs]myrs_get_ldev_info =_ "Sending GetLogicalDeviceInfoValid for ldev %d\012" drivers/scsi/myrs.c:189 [myrs]myrs_get_ctlr_info =_ "Sending GetControllerInfo\012" drivers/scsi/myrb.c:2445 [myrb]myrb_monitor =_ "reschedule monitor\012" drivers/scsi/myrb.c:2436 [myrb]myrb_monitor =_ "new enquiry\012" drivers/scsi/myrb.c:2432 [myrb]myrb_monitor =_ "get background init status\012" drivers/scsi/myrb.c:2427 [myrb]myrb_monitor =_ "get consistency check progress\012" drivers/scsi/myrb.c:2421 [myrb]myrb_monitor =_ "get rebuild progress\012" drivers/scsi/myrb.c:2415 [myrb]myrb_monitor =_ "get logical drive info\012" drivers/scsi/myrb.c:2409 [myrb]myrb_monitor =_ "get rebuild progress\012" drivers/scsi/myrb.c:2403 [myrb]myrb_monitor =_ "get error table\012" drivers/scsi/myrb.c:2397 [myrb]myrb_monitor =_ "get event log no %d/%d\012" drivers/scsi/myrb.c:2390 [myrb]myrb_monitor =_ "monitor tick\012" drivers/scsi/myrb.c:2360 [myrb]myrb_handle_scsi =_ "Device nonresponsive\012" drivers/scsi/myrb.c:2355 [myrb]myrb_handle_scsi =_ "Attempt to Access Beyond End of Logical Drive" drivers/scsi/myrb.c:2350 [myrb]myrb_handle_scsi =_ "Logical Drive Nonexistent or Offline" drivers/scsi/myrb.c:2331 [myrb]myrb_handle_scsi =_ "Bad Data Encountered\012" drivers/scsi/myrb.c:1699 [myrb]myrb_pdev_slave_alloc =_ "slave alloc pdev %d:%d state %x\012" drivers/scsi/myrb.c:1693 [myrb]myrb_pdev_slave_alloc =_ "device not present, skip\012" drivers/scsi/myrb.c:1687 [myrb]myrb_pdev_slave_alloc =_ "Failed to get device state, status %x\012" drivers/scsi/myrb.c:1639 [myrb]myrb_ldev_slave_alloc =_ "slave alloc ldev %d state %x\012" drivers/scsi/myrb.c:1438 [myrb]myrb_ldev_queuecommand =_ "ldev %u in state %x, skip\012" drivers/scsi/myrb.c:1414 [myrb]myrb_read_capacity =_ "Capacity %u, blocksize %u\012" See attachment for dmesg output. myrs was loaded around timestamp 16372.039529. -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1215622] New: iscsiuio - Couldn't mmap registers: Invalid argument
by bugzilla_noreply＠suse.com 30 Apr '24

30 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1215622 Bug ID: 1215622 Summary: iscsiuio - Couldn't mmap registers: Invalid argument Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.5 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: screening-team-bugs(a)suse.de Reporter: per(a)computer.org QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- When trying to set up an iscsi initiator (in yast) using a bnx2 offload engine, I wasn't getting very far, see bug#1215621. I kept getting this error: iscsiadm: Could not set host net params (err 29) I ran iscsiuio with debug level 4 and noticed the following error msg: Couldn't mmap registers: Invalid argument After some research, I rebooted the machine with "iomem=relaxed" - now it works: anton:~ # iscsiadm -m discovery -P 1 -t st -I eth4-bnx2i -p 10.42.8.10:3260 iscsiadm: Could not set host net params (err 29) iscsiadm: Connection to discovery portal 10.42.8.10 failed: operation failed but retry may succeed Target: iqn.2023-09.local.rz2:opensuse-mirror Portal: 10.42.8.10:3260,1 Iface Name: eth4-bnx2i Target: iqn.2023-09.local.rz2:webspace Portal: 10.42.8.10:3260,1 Iface Name: eth4-bnx2i -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1220569] New: No mouse pointer in noVNC when installing latest Tumbleweed using BVCP
by bugzilla_noreply＠suse.com 30 Apr '24

30 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1220569 Bug ID: 1220569 Summary: No mouse pointer in noVNC when installing latest Tumbleweed using BVCP Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Installation Assignee: yast2-maintainers(a)suse.de Reporter: roger.whittaker(a)suse.com QA Contact: jsrain(a)suse.com Target Milestone: --- Found By: --- Blocker: --- I have been using an unusual but rather nice virtualisation setup BVCP (https://bhyve.npulse.net/) which runs on FreeBSD and displays VMs using noVNC ( https://novnc.com/info.html). When installing the latest Tumbleweed the mouse pointer in the noVNC window does not move, nor does it move in a completed install. This problem does not exist with for example Leap 15.5. I do not see this with virt-install / virt-viewer on Linux, so this seems to a specific problem with Tumbleweed when using noVNC. I understand that this is an unusual use case, but maybe something has changed that might be a problem in other circumstances as well. -- You are receiving this mail because: You are on the CC list for the bug.

1 93

[Bug 1213486] New: [Build 44.3] openQA test fails in fanotify14
by bugzilla_noreply＠suse.com 30 Apr '24

30 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1213486 Bug ID: 1213486 Summary: [Build 44.3] openQA test fails in fanotify14 Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.4 Hardware: Other URL: https://openqa.opensuse.org/tests/3439183/modules/fano tify14/steps/7 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: fvogt(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: openQA Blocker: Yes ## Observation openQA test in scenario opensuse-15.4-JeOS-for-kvm-and-xen-x86_64-jeos-ltp-syscalls@64bit_virtio fails in [fanotify14](https://openqa.opensuse.org/tests/3439183/modules/fanotify14/st… ## Test suite description ## Reproducible Fails since (at least) Build [44.2](https://openqa.opensuse.org/tests/3438422) ## Expected result Last good: [44.1](https://openqa.opensuse.org/tests/3436580) (or more recent) ## Further details Always latest result in this scenario: [latest](https://openqa.opensuse.org/tests/latest?arch=x86_64&distri=opensus… -- You are receiving this mail because: You are on the CC list for the bug.

1 6

[Bug 1218327] New: AUDIT-0: dnf5: Audit dnf5daemon D-Bus files for whitelist
by bugzilla_noreply＠suse.com 30 Apr '24

30 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1218327 Bug ID: 1218327 Summary: AUDIT-0: dnf5: Audit dnf5daemon D-Bus files for whitelist Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Security Assignee: security-team(a)suse.de Reporter: ngompa13(a)gmail.com QA Contact: security-team(a)suse.de Target Milestone: --- Found By: --- Blocker: --- For my package found in OBS in system:packagemanager:dnf/dnf5 I would like a whitelisting for the following rpmlint errors: [ 520s] dnf5daemon-server.x86_64: E: dbus-file-unauthorized (Badness: 10000) /etc/dbus-1/system.d/org.rpm.dnf.v0.conf (sha256 file digest default filter:4dd26c049d6240e6640106bb8805ec958e03d9ad79eb2823152b9a92156554a9 shell filter:4dd26c049d6240e6640106bb8805ec958e03d9ad79eb2823152b9a92156554a9 xml filter:bd2c589d0cb083d7b8a7696b98e0a344b2501ecd2d91a7fe447028cb47f75210) [ 520s] dnf5daemon-server.x86_64: E: dbus-file-unauthorized (Badness: 10000) /usr/share/dbus-1/system-services/org.rpm.dnf.v0.service (sha256 file digest default filter:8dff187bd14e516fd976731fb4ab3996bb92b36dfa944733655641a6aec215e1 shell filter:8dff187bd14e516fd976731fb4ab3996bb92b36dfa944733655641a6aec215e1 xml filter:<failed-to-calculate>) [ 520s] Packaging D-Bus services requires a review and whitelisting by the SUSE [ 520s] security team. If the package is intended for inclusion in any SUSE product [ 520s] please open a bug report to request review of the package by the security [ 520s] team. Please refer to [ 520s] https://en.opensuse.org/openSUSE:Package_security_guidelines#audit_bugs for [ 520s] more information. This blocks my submit request: https://build.opensuse.org/request/show/1134536 -- You are receiving this mail because: You are on the CC list for the bug.

1 8

[Bug 1218422] New: Can't build hyprland plugins due to improper header locations
by bugzilla_noreply＠suse.com 29 Apr '24

29 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1218422 Bug ID: 1218422 Summary: Can't build hyprland plugins due to improper header locations Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Development Assignee: screening-team-bugs(a)suse.de Reporter: johndoe1352460(a)outlook.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- I cannot build the plugins for Hyprland due to the improper locations of headers. When building hyprbars for hyprland it expects <wlr/util/transform.h> but the full path of the file is /usr/include/hyprland/wlroots. I'm guessing it expects it to be /usr/include/hyprland/wlr with the pkgconfig parameter inclduing -I/usr/include/hyprland What I did to fix this issue is create a symlink /usr/include/hyprland/wlr that points to /usr/include/hyprland/wlroots and add -I${includedir}/hyprland to the cflags in /usr/share/pkgconfig/hyprland.pc After I do that the hyprbars plugin builds just fine. -- You are receiving this mail because: You are on the CC list for the bug.

1 7

[Bug 1214980] New: mozilla-nss: FTBFS because expired certificate since 2023-09-04
by bugzilla_noreply＠suse.com 29 Apr '24

29 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1214980 Bug ID: 1214980 Summary: mozilla-nss: FTBFS because expired certificate since 2023-09-04 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Firefox Assignee: factory-mozilla(a)lists.opensuse.org Reporter: ana.guerrero(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- mozilla-nss doesn't build because because expired certificate since 2023-09-04 Bernhard M. Wiedemann already made a nice report at upstream: https://bugzilla.mozilla.org/show_bug.cgi?id=1813401 A fix in progress: https://phabricator.services.mozilla.com/D185088 -- You are receiving this mail because: You are on the CC list for the bug.

1 6

[Bug 1220201] New: Firefox on Wayland - download dialog disappearing
by bugzilla_noreply＠suse.com 29 Apr '24

29 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1220201 Bug ID: 1220201 Summary: Firefox on Wayland - download dialog disappearing Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Firefox Assignee: factory-mozilla(a)lists.opensuse.org Reporter: opensuse(a)mike.franken.de QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Using Firefox on Wayland the download dialog is disappearing after chosing "save file" and before selecting the download file and directory. One can see the "enter name ..." dialog for a second, then it vanishes. On the same machine this does not happen with Xorg. There is no error or warning in the journal, i.e. for a crash. Operating System: openSUSE Tumbleweed 20240220 KDE Plasma Version: 5.27.10 KDE Frameworks Version: 5.115.0 Qt Version: 5.15.12 Kernel Version: 6.7.5-1-default (64-bit) Graphics Platform: X11 Processors: 8 × 11th Gen Intel® Core™ i7-1165G7 @ 2.80GHz Memory: 15,0 GiB of RAM Graphics Processor: Mesa Intel® Xe Graphics Manufacturer: Dell Inc. Product Name: XPS 13 9310 2-in-1 -- You are receiving this mail because: You are on the CC list for the bug.

1 2