October 2024 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1220088] New: Hibernate completes shuts machine off *then* machine automatically turns back on.
by bugzilla_noreply＠suse.com 14 Dec '24

14 Dec '24

https://bugzilla.suse.com/show_bug.cgi?id=1220088 Bug ID: 1220088 Summary: Hibernate completes shuts machine off *then* machine automatically turns back on. 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: pj.opensuse(a)gmx.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Hi, when hibernate is envoked from the Tumbleweed menu the hibernate feature seems to complete and shutoff the machine for 2 seconds...... Then the machine automatically powers back on. I enter the LUKS password and the machine continues to boot. I enter the user password at SDDM screen. After loading KDE I can then see that Hibernate has indeed worked. Largest issue is machine is cycling, (powering back on) after hibernation has been envoked. I have shut off all wake-on power options in the bios settings. The machine is kept very current with the latest updates. What are your thoughts on this? -Best Regards -- You are receiving this mail because: You are on the CC list for the bug.

1 25

[Bug 1228863] New: System asking for recovery key while booting a default mode encrypted Aeon system after automatic update
by bugzilla_noreply＠suse.com 13 Dec '24

13 Dec '24

https://bugzilla.suse.com/show_bug.cgi?id=1228863 Bug ID: 1228863 Summary: System asking for recovery key while booting a default mode encrypted Aeon system after automatic update Classification: openSUSE Product: openSUSE Aeon Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Transactional Update Assignee: rbrown(a)suse.com Reporter: happymab.dev(a)outlook.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- When I booted the system after the automatic update on 04 Aug 2024, the system asked for the recovery key. I booted the system using the recovery key and tried the following to fix the issue: - sudo sdbootutil update-predictions - sudo sdbootutil --ask-pin update-predictions - Clear TPM in BIOS and run sudo sdbootutil --ask-pin update-predictions None of the above actions fixed the issue. -- You are receiving this mail because: You are on the CC list for the bug.

1 31

[Bug 1230779] New: Update nvidia driver to latest 550.xxx release
by bugzilla_noreply＠suse.com 13 Dec '24

13 Dec '24

https://bugzilla.suse.com/show_bug.cgi?id=1230779 Bug ID: 1230779 Summary: Update nvidia driver to latest 550.xxx release Classification: openSUSE Product: openSUSE Tumbleweed Version: Slowroll Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: X11 3rd Party Driver Assignee: gfx-bugs(a)suse.de Reporter: sndirsch(a)suse.com QA Contact: sndirsch(a)suse.com Target Milestone: --- Found By: --- Blocker: --- Update nvidia driver to latest 550.xxx release -- You are receiving this mail because: You are on the CC list for the bug.

1 15

[Bug 1232057] New: Update nvidia driver to latest 550.127.05 release
by bugzilla_noreply＠suse.com 13 Dec '24

13 Dec '24

https://bugzilla.suse.com/show_bug.cgi?id=1232057 Bug ID: 1232057 Summary: Update nvidia driver to latest 550.127.05 release Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: X11 3rd Party Driver Assignee: gfx-bugs(a)suse.de Reporter: sndirsch(a)suse.com QA Contact: sndirsch(a)suse.com Target Milestone: --- Found By: --- Blocker: --- Update nvidia driver to latest 550.127.05 release -- You are receiving this mail because: You are on the CC list for the bug.

1 12

[Bug 1229716] New: Update nvidia driver to version 550.107.02
by bugzilla_noreply＠suse.com 13 Dec '24

13 Dec '24

https://bugzilla.suse.com/show_bug.cgi?id=1229716 Bug ID: 1229716 Summary: Update nvidia driver to version 550.107.02 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: X11 3rd Party Driver Assignee: gfx-bugs(a)suse.de Reporter: sndirsch(a)suse.com QA Contact: sndirsch(a)suse.com Target Milestone: --- Found By: --- Blocker: --- Update nvidia driver to version 550.107.02 ... -- You are receiving this mail because: You are on the CC list for the bug.

1 9

[Bug 1225688] New: [tw] [hexchat] gnome-shell The program 'hexchat' received an X Window System error when connecting to netwok
by bugzilla_noreply＠suse.com 13 Dec '24

13 Dec '24

https://bugzilla.suse.com/show_bug.cgi?id=1225688 Bug ID: 1225688 Summary: [tw] [hexchat] gnome-shell The program 'hexchat' received an X Window System error when connecting to netwok Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: aarch64 URL: https://openqa.opensuse.org/tests/4236088/modules/hexc hat/steps/28 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: GNOME Assignee: gnome-bugs(a)suse.de Reporter: richard.fan(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: openQA Blocker: Yes ## Description The issue is a sporadic one, but I can see the issue several times in openQA automation tests. it can be seen on both x86_64 and aarch64 platforms. Steps to reproduce the issue: 1. Upgrade the system from leap15.x to tw 2. start hexchat 3. config a nickname and connect to "Libera.Chat" Error logs like below: >May 30 09:49:37.300575 susetest gnome-shell[30709]: The program 'hexchat' received an X Window System error. >May 30 09:49:37.300575 susetest gnome-shell[30709]: This probably reflects a bug in the program. >May 30 09:49:37.307179 susetest gnome-shell[30709]: The error was 'BadWindow (invalid Window parameter)'. >May 30 09:49:37.307179 susetest gnome-shell[30709]: (Details: serial 6056 error_code 3 request_code 38 minor_code 0) >May 30 09:49:37.307179 susetest gnome-shell[30709]: (Note to programmers: normally, X errors are reported asynchronously; >May 30 09:49:37.307179 susetest gnome-shell[30709]: that is, you will receive the error a while after causing it. >May 30 09:49:37.307179 susetest gnome-shell[30709]: To debug your program, run it with the --sync command line >May 30 09:49:37.307179 susetest gnome-shell[30709]: option to change this behavior. You can then get a meaningful >May 30 09:49:37.307179 susetest gnome-shell[30709]: backtrace from your debugger if you break on the gdk_x_error() function.) Please refer to the attached log for more information. ## openQA Observation as below: openQA test in scenario opensuse-Tumbleweed-NET-aarch64-zdup-Leap-15.5-gnome@aarch64 fails in [hexchat](https://openqa.opensuse.org/tests/4236088/modules/hexchat/steps/28) ## Test suite description Maintained by qe-core ## Reproducible Fails since (at least) Build [20240529](https://openqa.opensuse.org/tests/4235968) ## Expected result Last good: (unknown) (or more recent) ## Further details Always latest result in this scenario: [latest](https://openqa.opensuse.org/tests/latest?arch=aarch64&distri=opensu… -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1232670] New: [SELinux] importctl cannot write to /var/lib/extensions
by bugzilla_noreply＠suse.com 13 Dec '24

13 Dec '24

https://bugzilla.suse.com/show_bug.cgi?id=1232670 Bug ID: 1232670 Summary: [SELinux] importctl cannot write to /var/lib/extensions 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: kukuk(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Importing sysext images with importctl does not work, since SELinux blocks writing in that directory: node122:~ # importctl pull-raw --class=sysext https://download.opensuse.org/repositories/home:/kukuk:/sysext/mkosi/gcc-20… --verify=no Enqueued transfer job 1. Press C-c to continue download in background. Pulling 'https://download.opensuse.org/repositories/home:/kukuk:/sysext/mkosi/gcc-20…', saving as 'gcc-20.2.x86-64'. Operating on image directory '/var/lib/extensions'. Failed to create /var/lib/extensions/.#verityebe0580e99f54026: Permission denied Verity integrity file could not be retrieved, proceeding without. Failed to create /var/lib/extensions/.#roothash96cdb063d430dc58: Permission denied Root hash file could not be retrieved, proceeding without. Failed to create /var/lib/extensions/.#roothash.p7s70c3902ea1954e95: Permission denied Root hash signature file could not be retrieved, proceeding without. Downloading 241.2M for https://download.opensuse.org/repositories/home:/kukuk:/sysext/mkosi/gcc-20…. Failed to create /var/lib/extensions/.#rawd292069b0f58e5ea: Permission denied Failed to retrieve image file. Exiting. type=SERVICE_START msg=audit(1730372760.872:336): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-importd comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' type=AVC msg=audit(1730372764.279:337): avc: denied { write } for pid=2413 comm="systemd-pull" name="extensions" dev="dm-0" ino=143939 scontext=system_u:system_r:systemd_importd_t:s0 tcontext=unconfined_u:object_r:var_lib_t:s0 tclass=dir permissive=0 type=AVC msg=audit(1730372764.282:338): avc: denied { write } for pid=2413 comm="systemd-pull" name="extensions" dev="dm-0" ino=143939 scontext=system_u:system_r:systemd_importd_t:s0 tcontext=unconfined_u:object_r:var_lib_t:s0 tclass=dir permissive=0 type=AVC msg=audit(1730372764.289:339): avc: denied { write } for pid=2413 comm="systemd-pull" name="extensions" dev="dm-0" ino=143939 scontext=system_u:system_r:systemd_importd_t:s0 tcontext=unconfined_u:object_r:var_lib_t:s0 tclass=dir permissive=0 type=AVC msg=audit(1730372767.479:340): avc: denied { write } for pid=2413 comm="systemd-pull" name="extensions" dev="dm-0" ino=143939 scontext=system_u:system_r:systemd_importd_t:s0 tcontext=unconfined_u:object_r:var_lib_t:s0 tclass=dir permissive=0 type=SERVICE_STOP msg=audit(1730372797.529:341): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-importd comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' -- You are receiving this mail because: You are on the CC list for the bug.

1 7

[Bug 1228272] New: When using systemd-boot, dracut uses wrong target file
by bugzilla_noreply＠suse.com 12 Dec '24

12 Dec '24

https://bugzilla.suse.com/show_bug.cgi?id=1228272 Bug ID: 1228272 Summary: When using systemd-boot, dracut uses wrong target file Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Bootloader Assignee: screening-team-bugs(a)suse.de Reporter: tilman.vogel(a)web.de QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- When after an upgrade, /usr/lib/module-init-tools/regenerate-initrd-posttrans runs dracut -f --kver "$kver" the generated initrd goes to /boot/efi/<somehexid>/$kver/initrd which looks right but is in fact incorrect because /boot/efi/loader/entries/<somehexid>-$kver.conf actually uses initrd /<somehexid>/$kver/initrd-$kver Note the trailing "-$kver". So, after running dracut, there are two initrds: /boot/efi/<somehexid>/$kver/initrd /boot/efi/<somehexid>/$kver/initrd-$kver of which the former is the new one but ignored and the latter is an older one which will still be used. -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1226017] New: fwupd fails TPM fw upgrade with 'Secure boot is enabled, but shim isn't installed to EFI/opensuse/shim.efi'
by bugzilla_noreply＠suse.com 12 Dec '24

12 Dec '24

https://bugzilla.suse.com/show_bug.cgi?id=1226017 Bug ID: 1226017 Summary: fwupd fails TPM fw upgrade with 'Secure boot is enabled, but shim isn't installed to EFI/opensuse/shim.efi' Classification: openSUSE Product: openSUSE Aeon Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Base Assignee: rbrown(a)suse.com Reporter: anselm.gora(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/125.0.0.0 Safari/537.36 Build Identifier: fwupd expects to find EFI/opensuse/shim.efi while on openSUSE Aeon the path is EFI/systemd/shim.efi https://github.com/fwupd/fwupd/blob/eb3d26079d7b0e6f0db70b066fcb7b31ac7bcec… fwupd seems to use os release ID but it's also a build option: https://github.com/fwupd/fwupd/blob/eb3d26079d7b0e6f0db70b066fcb7b31ac7bcec… Tumbleweed seems to patch it: https://build.opensuse.org/projects/openSUSE:Factory/packages/fwupd/files/f… Reproducible: Always -- You are receiving this mail because: You are on the CC list for the bug.

1 8

[Bug 1228797] New: python3-schema and python3-daemon not available with sle-module-pythons
by bugzilla_noreply＠suse.com 12 Dec '24

12 Dec '24

https://bugzilla.suse.com/show_bug.cgi?id=1228797 Bug ID: 1228797 Summary: python3-schema and python3-daemon not available with sle-module-pythons Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.6 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Python Assignee: python-maintainers(a)suse.com Reporter: egotthold(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- I am attempting to build cobbler-tftp here [1]. This is failing due to two dependencies not being enabled for sle-module-pythons. I would desire that sle15allpythons is used so the package builds for both 3.6 and 3.11. Both versions in Leap are available at the moment with 3.6 and are compatible with it. [1]: https://build.opensuse.org/package/show/systemsmanagement:cobbler:release34… -- You are receiving this mail because: You are on the CC list for the bug.

1 4