January 2024 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1219056] New: ASUS Expertbook B5302F - system doesn't sleep properly, no s0 residency in s2idle
by bugzilla_noreply＠suse.com 05 Feb '24

05 Feb '24

https://bugzilla.suse.com/show_bug.cgi?id=1219056 Bug ID: 1219056 Summary: ASUS Expertbook B5302F - system doesn't sleep properly, no s0 residency in s2idle Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: davor.virag(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:121.0) Gecko/20100101 Firefox/121.0 Build Identifier: I'm using Intel's S0ixSelftestTool (https://github.com/intel/S0ixSelftestTool/) as I was getting seemingly high battery drain in sleep. According to the logs, it can get the CPU into PC10 state, but the logs state: "Your system supports S0ix substates, but did not achieve the shallowest s0i2.0" I have tried "powertop --calibrate" and "powertop --auto-tune", but the s0 self-etst logs still look the same Reproducible: Always Steps to Reproduce: 1. Run "s0ix-selftest-tool.sh -s" 2. Check for s0 residency Actual Results: CPU Core C7 residency after S2idle is: 98.34 GFX RC6 residency after S2idle is: CPU Package C-state 2 residency after S2idle is: 2.79 CPU Package C-state 3 residency after S2idle is: 2.26 CPU Package C-state 8 residency after S2idle is: 0.21 CPU Package C-state 9 residency after S2idle is: 1.33 CPU Package C-state 10 residency after S2idle is: 88.21 S0ix residency after S2idle is: 0.00 Your system supports S0ix substates, but did not achieve the shallowest s0i2.0 Here is the S0ix substates status: Substate Residency S0i2.0 0 S0i3.0 0 (...) Did not detect the potential blockers from substate_requirements, need to check substate_status_registers file for the advanced debug. (...) Your system south port controller power gating state is OK after 30 seconds runtime check. Expected Results: Residency in one of the s0 states -- You are receiving this mail because: You are on the CC list for the bug.

1 7

[Bug 1218578] New: Unable to install OpenMW due to missing dependencies
by bugzilla_noreply＠suse.com 05 Feb '24

05 Feb '24

https://bugzilla.suse.com/show_bug.cgi?id=1218578 Bug ID: 1218578 Summary: Unable to install OpenMW due to missing dependencies Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: the-ill-sheep(a)atemicon.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- When trying to install OpenMW on Tumbleweed the following error appears: Problem: nothing provides 'libboost_program_options.so.1.83.0()(64bit)' needed by the to be installed openmw-0.48.0-1.4.x86_64 Solution 1: do not install openmw-0.48.0-1.4.x86_64 Solution 2: break openmw-0.48.0-1.4.x86_64 by ignoring some of its dependencies Choose from above solutions by number or cancel [1/2/c/d/?] (c): -- You are receiving this mail because: You are on the CC list for the bug.

1 6

[Bug 1219206] New: wezterm not starting
by bugzilla_noreply＠suse.com 05 Feb '24

05 Feb '24

https://bugzilla.suse.com/show_bug.cgi?id=1219206 Bug ID: 1219206 Summary: wezterm not starting Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: mvetter(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- ``` $ zypper in wezterm $ wezterm wezterm 06:05:19.451 ERROR wezterm_gui > running message loop: process_queued_xcb: poll_for_queued_event: X(Match(RequestError { response_type: 0, error_code: 8, sequence: 254, bad_value: 17825801, minor_opcode: 4, major_opcode: 149, pad: 1 }), None); t ``` -- You are receiving this mail because: You are on the CC list for the bug.

1 8

[Bug 1218666] New: sg3_utils: udev rules: spurious warning about .SCSI_ID_SERIAL_SRC
by bugzilla_noreply＠suse.com 05 Feb '24

05 Feb '24

https://bugzilla.suse.com/show_bug.cgi?id=1218666 Bug ID: 1218666 Summary: sg3_utils: udev rules: spurious warning about .SCSI_ID_SERIAL_SRC Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: screening-team-bugs(a)suse.de Reporter: martin.wilck(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Lots of warnings during boot: 55-scsi-sg3_id.rules[15445]: WARNING: SCSI device loop0 has no device ID, consider changing .SCSI_ID_SERIAL_SRC in 00-scsi-sg3_config.rules -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1217921] New: CPE ID in /etc/os-release adheres to superseded standard.
by bugzilla_noreply＠suse.com 02 Feb '24

02 Feb '24

https://bugzilla.suse.com/show_bug.cgi?id=1217921 Bug ID: 1217921 Summary: CPE ID in /etc/os-release adheres to superseded standard. Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: All OS: openSUSE Tumbleweed Status: NEW Severity: Enhancement Priority: P5 - None Component: Basesystem Assignee: screening-team-bugs(a)suse.de Reporter: rokejulianlockhart+1674683091(a)outlook.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 871229 --> https://bugzilla.suse.com/attachment.cgi?id=871229&action=edit os-release as of cpe:2.3:o:opensuse:tumbleweed:20231208. The Common Platform Enumeration Operating System Identifier (as hostnamectl and /etc/os-release report) format adheres to the pre-2.3 version, as its lack of version demonstrates. https://nvd.nist.gov/products/cpe/detail/34AB288B-8A0F-4C9D-9C61-6E11BC2CE0… demonstrates how it should be formatted. -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 1217711] New: [Slurm, slurmrestd] service file missing for slurmrestd
by bugzilla_noreply＠suse.com 02 Feb '24

02 Feb '24

https://bugzilla.suse.com/show_bug.cgi?id=1217711 Bug ID: 1217711 Summary: [Slurm, slurmrestd] service file missing for slurmrestd Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: All OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: eich(a)suse.com Reporter: eich(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- The service file to start slurmrestd is missing from package slurm-rest. -- You are receiving this mail because: You are on the CC list for the bug.

1 12

[Bug 1216366] New: YaST installation with sd-boot: Disabling the menu timeout is not possible
by bugzilla_noreply＠suse.com 02 Feb '24

02 Feb '24

https://bugzilla.suse.com/show_bug.cgi?id=1216366 Bug ID: 1216366 Summary: YaST installation with sd-boot: Disabling the menu timeout is not possible Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Installation Assignee: schubi(a)suse.com Reporter: fvogt(a)suse.com QA Contact: jsrain(a)suse.com CC: yast2-maintainers(a)suse.de Target Milestone: --- Found By: --- Blocker: --- To disable the timeout for the systemd-boot menu, "menu-force" needs to be used, but YaST only allows integer values for the timeout. When -1 is entered, systemd-boot prints an error message that this is an invalid value. Either YaST should explicitly support menu-force or translate -1 to menu-force internally. -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1219242] New: [Build 20240125] openQA test fails in fallocate06
by bugzilla_noreply＠suse.com 02 Feb '24

02 Feb '24

https://bugzilla.suse.com/show_bug.cgi?id=1219242 Bug ID: 1219242 Summary: [Build 20240125] openQA test fails in fallocate06 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other URL: https://openqa.opensuse.org/tests/3895229/modules/fall ocate06/steps/6 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: ana.guerrero(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: openQA Blocker: Yes ## Observation There wasn't a kernel update today but this LTP test started failing in different workers: ----snip---- # wait_serial expected: qr/### TEST fallocate06 COMPLETE >>> \d+\./u # Result: tst_device.c:293: TWARN: Failed to create test_dev.img: ENOSPC (28) tst_device.c:354: TBROK: Failed to acquire device HINT: You _MAY_ be missing kernel fixes: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?… https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?… Summary: passed 0 failed 0 broken 1 skipped 0 warnings 1 ### TEST fallocate06 COMPLETE >>> 6. ----snip---- openQA test in scenario opensuse-Tumbleweed-JeOS-for-kvm-and-xen-x86_64-jeos-ltp-syscalls@uefi_virtio-2G fails in [fallocate06](https://openqa.opensuse.org/tests/3895229/modules/fallocate06/… ## Test suite description ## Reproducible Fails since (at least) Build [20240123](https://openqa.opensuse.org/tests/3888826) ## Expected result Last good: [20240122](https://openqa.opensuse.org/tests/3886452) (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 1

[Bug 1219329] New: Firefox all tabs list issues on KDE Wayland - cannot move tabs in list
by bugzilla_noreply＠suse.com 02 Feb '24

02 Feb '24

https://bugzilla.suse.com/show_bug.cgi?id=1219329 Bug ID: 1219329 Summary: Firefox all tabs list issues on KDE Wayland - cannot move tabs in list Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: KDE Workspace (Plasma) Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: pallaswept(a)proton.me QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Short version: In Firefox, in KDE Plasma Wayland sessions on Tumbleweed, you cannot move tabs (by drag'n'drop with the mouse) in the all tabs list (the one you get when you press ctrl+shift+tab) - unless that list is longer than the window is in height. Process for reproduction of the fault on an entirely unmodified system: Obtain the latest Tumbleweed Live ISO and boot to it in a VM (or bare metal if you prefer) for testing. Log out (because it automatically logs into X11) and log in (to Plasma Wayland), start firefox, hit ctrl+t several times to create new tabs, press ctrl+shift+tab to open the all tabs list, click on one of the tabs and try to drag it, and it will fail. To observe the intended behaviour, resize the window (make it shorter) and create more tabs, until the all tabs list becomes longer than the height of the window, then repeat the process, and you will see a blue marker appear as you drag the tab, showing where it would be moved to, and releasing the mouse button will move the tab to that position. Alternatively, just try it in a Plasma X11 session, where it works fine, or a Plasma Wayland session in a different distro, where it will also work. I've had this bug filed against Firefox, but I'm now filing this against KDE Plasma because I've found that the issue also exists with the nightly Firefox, as downloaded directly from Mozilla, and not packaged by openSUSE, but it only occurs in KDE Plasma Wayland sessions and only on Tumbleweed (KDE Plasma Wayland sessions on Ubuntu and Neon live ISOs worked OK, for example, and KDE X11 on Tumbleweed was fine, too) so, Tumbleweed KDE Plasma Wayland seems to be the critical factor in this failure. I'm unsure as to whether to mark the other bug as a duplicate and close it, as I have had no word from the maintainers of that package, so I'm not entirely sure what the cause of the problem is, Plasma Wayland, or Firefox, so I don't know which of these cases should be left open. I'll be sure to clean up whenever things become clear. It would be really nice to get some help with this. As a disabled user, this is causing me some degree of physical pain, and it's been 5 months without response so far, I don't think it's normal to have a bug left unattended for such a long time? Hopefully this package's maintainers will be willing to help me.... Please! :) -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1218367] New: kalpa-firstboot crashes after fresh install
by bugzilla_noreply＠suse.com 01 Feb '24

01 Feb '24

https://bugzilla.suse.com/show_bug.cgi?id=1218367 Bug ID: 1218367 Summary: kalpa-firstboot crashes after fresh install Classification: openSUSE Product: openSUSE Kalpa Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Base Assignee: sfalken(a)cloverleaf-linux.org Reporter: vincent+suse(a)koppen.email QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 871540 --> https://bugzilla.suse.com/attachment.cgi?id=871540&action=edit fixed kalpa-firstboot Just did a fresh install of openSUSE Kalpa and the firstboot script (for installing the flatpak packages) crashed. To fix this I applied the following changes to kalpa-firstboot, see also the attached file. I tested it by copying /usr/bin/kalpa-firstboot to my home directory, edited there as below and than ran it from the terminal. >diff kalpa-firstboot /usr/bin/kalpa-firstboot >>10c10 >< qdbus-qt5 $dbusRef setLabelText "$label" >--- >> qdbus-qt5 "$dbusRef" setLabelText "$label" >12,13c12,13 >< if eval "$@"; then >< qdbus-qt5 $dbusRef value "$step" >--- >> if "$@"; then >> qdbus-qt5 "$dbusRef" Set "" value "$step" >21c21 >< run_task 2 "Adding Flathub Repository" /usr/bin/flatpak remote-add --user >--if-not-exists flathub /usr/share/kalpa/flathub.flatpakrepo >--- >> run_task 2 "Adding Flathub Repository" /usr/bin/flatpak remote-add --user >--if-not-exists flathub /usr/share/microos-desktop/flathub.flatpakrepo >30c30 >< qdbus-qt5 $dbusRef close >--- >> qdbus-qt5 "$dbusRef" close -- You are receiving this mail because: You are on the CC list for the bug.

1 7