February 2023 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1172465] New: transactional-update.timer fires immediately at first boot
by bugzilla_noreply＠suse.com 07 Mar '23

07 Mar '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1172465 Bug ID: 1172465 Summary: transactional-update.timer fires immediately at first boot Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: MicroOS Assignee: kubic-bugs(a)opensuse.org Reporter: lnussel(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- openSUSE-MicroOS.armv7l-16.0.0-RaspberryPi2-Snapshot20200528.raw Booted and wondered why systemd-analyze wouldn't show me results. Turns out transactional-update.timer was started immediately at first boot. Maybe related to missing rtc on rpi? So the time warp caused by chrony catching up triggered it? # systemctl status transactional-update.timer * transactional-update.timer - Daily update of the system Loaded: loaded (/usr/lib/systemd/system/transactional-update.timer; enabled; vendor preset: enabled) Active: active (waiting) since Thu 2020-04-23 14:15:38 UTC; 1 months 10 days ago Trigger: Thu 2020-06-04 01:38:53 UTC; 11h left Triggers: * transactional-update.service Docs: man:transactional-update(8) If so why April 23rd rather than end of May when the image was created? # l /var/lib/chrony total 0 drwxr-x--- 1 chrony chrony 0 May 2 22:23 ./ drwxr-xr-x 1 root root 268 Jun 3 13:56 ../ Can and do we want to do something about this behavior or a matter of documentation again? -- You are receiving this mail because: You are on the CC list for the bug.

1 7

[Bug 1205774] New: Kernel 6.0.8 + nvidia 525.53 crash on BUG: kernel NULL pointer dereference, #PF: supervisor instruction fetch in kernel mode
by bugzilla_noreply＠suse.com 07 Mar '23

07 Mar '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1205774 Bug ID: 1205774 Summary: Kernel 6.0.8 + nvidia 525.53 crash on BUG: kernel NULL pointer dereference, #PF: supervisor instruction fetch in kernel mode Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Major Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: bruno(a)ioda-net.ch QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 863125 --> http://bugzilla.opensuse.org/attachment.cgi?id=863125&action=edit Last kernel 6.0.8 boot and crash Hello I need help to find the root cause of crashes (complete freeze of the workstation). Since the introduction of kernel 6.0.8 and latest nvidia 525.53 I constantly face complete machine freeze, when I'm using my external monitors. nov 25 16:05:34 qt-kt kernel: BUG: kernel NULL pointer dereference, address: 0000000000000000 nov 25 16:05:34 qt-kt kernel: #PF: supervisor instruction fetch in kernel mode nov 25 16:05:34 qt-kt kernel: #PF: error_code(0x0010) - not-present page nov 25 16:05:34 qt-kt kernel: PGD 0 P4D 0 nov 25 16:05:34 qt-kt kernel: Oops: 0010 [#1] PREEMPT SMP PTI nov 25 16:05:34 qt-kt kernel: CPU: 3 PID: 1004 Comm: nvidia-modeset/ Tainted: P OE 6.0.8-1-default #1 openSUSE Tumbleweed 9d20364b934f5aab0a9bdf84e8f45cfdfae39dab nov 25 16:05:34 qt-kt kernel: Hardware name: Dell Inc. Precision 7510/0YH43H, BIOS 1.29.3 09/18/2022 nov 25 16:05:34 qt-kt kernel: RIP: 0010:0x0 nov 25 16:05:34 qt-kt kernel: Code: Unable to access opcode bytes at RIP 0xffffffffffffffd6. nov 25 16:05:34 qt-kt kernel: RSP: 0018:ffffadc300703c90 EFLAGS: 00010207 nov 25 16:05:34 qt-kt kernel: RAX: 0000000000000000 RBX: ffff9b2996c75378 RCX: 0000000000000004 nov 25 16:05:34 qt-kt kernel: RDX: 0000000000000010 RSI: ffff9b2996c75378 RDI: ffffadc300703a10 nov 25 16:05:34 qt-kt kernel: RBP: ffff9b292ef8b560 R08: 0000000000000000 R09: 0000000000000040 nov 25 16:05:34 qt-kt kernel: R10: ffff9b2886b28008 R11: ffffadc300703c00 R12: 0000000000000000 nov 25 16:05:34 qt-kt kernel: R13: 0000000000000000 R14: ffffffffc4fbee70 R15: ffffffffc4eb7580 nov 25 16:05:34 qt-kt kernel: FS: 0000000000000000(0000) GS:ffff9b37c44c0000(0000) knlGS:0000000000000000 nov 25 16:05:34 qt-kt kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 nov 25 16:05:34 qt-kt kernel: CR2: ffffffffffffffd6 CR3: 000000075be10001 CR4: 00000000003706e0 nov 25 16:05:34 qt-kt kernel: DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 nov 25 16:05:34 qt-kt kernel: DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 nov 25 16:05:34 qt-kt kernel: Call Trace: nov 25 16:05:34 qt-kt kernel: <TASK> nov 25 16:05:34 qt-kt kernel: _nv001281kms+0x194/0x1a0 [nvidia_modeset 4cdb9c16932eaf3d76d37eaaf2544a31bf3316d8] nov 25 16:05:34 qt-kt kernel: ? _nv001274kms+0x9a/0xd0 [nvidia_modeset 4cdb9c16932eaf3d76d37eaaf2544a31bf3316d8] nov 25 16:05:34 qt-kt kernel: ? _nv001466kms+0x172/0x180 [nvidia_modeset 4cdb9c16932eaf3d76d37eaaf2544a31bf3316d8] nov 25 16:05:34 qt-kt kernel: ? _nv001149kms+0xf3/0xa50 [nvidia_modeset 4cdb9c16932eaf3d76d37eaaf2544a31bf3316d8] nov 25 16:05:34 qt-kt kernel: ? schedule+0x5a/0xd0 nov 25 16:05:34 qt-kt kernel: ? schedule_timeout+0x10e/0x150 nov 25 16:05:34 qt-kt kernel: ? nvkms_sema_up+0x10/0x10 [nvidia_modeset 4cdb9c16932eaf3d76d37eaaf2544a31bf3316d8] nov 25 16:05:34 qt-kt kernel: ? __down_common+0x10b/0x1e0 nov 25 16:05:34 qt-kt kernel: ? nvkms_sema_up+0x10/0x10 [nvidia_modeset 4cdb9c16932eaf3d76d37eaaf2544a31bf3316d8] nov 25 16:05:34 qt-kt kernel: ? _nv002457kms+0x2d/0x70 [nvidia_modeset 4cdb9c16932eaf3d76d37eaaf2544a31bf3316d8] nov 25 16:05:34 qt-kt kernel: ? nvkms_kthread_q_callback+0x88/0xf0 [nvidia_modeset 4cdb9c16932eaf3d76d37eaaf2544a31bf3316d8] nov 25 16:05:34 qt-kt kernel: ? _main_loop+0x77/0x130 [nvidia_modeset 4cdb9c16932eaf3d76d37eaaf2544a31bf3316d8] nov 25 16:05:34 qt-kt kernel: ? kthread+0xd7/0x100 nov 25 16:05:34 qt-kt kernel: ? kthread_complete_and_exit+0x20/0x20 nov 25 16:05:34 qt-kt kernel: ? ret_from_fork+0x1f/0x30 nov 25 16:05:34 qt-kt kernel: </TASK> nov 25 16:05:34 qt-kt kernel: Modules linked in: rfcomm snd_seq_dummy snd_hrtimer snd_seq nf_nat_sip nft_objref af_packet nf_conntrack_sip nft_fib_inet nft_fib_ipv4 nft_fib_ipv6 nft_fib nft_reject_inet nf_reject_ipv4 nf_reject_ipv6 nft_reject nft_ct n> nov 25 16:05:34 qt-kt kernel: processor_thermal_device_pci_legacy irqbypass iwlwifi processor_thermal_device pcspkr ledtrig_audio processor_thermal_rfim snd_usbmidi_lib efi_pstore snd_intel_sdw_acpi sparse_keymap processor_thermal_mbox cdc_wdm videob> nov 25 16:05:34 qt-kt kernel: fuse configfs dmi_sysfs ip_tables x_tables cmac algif_hash algif_skcipher af_alg hid_logitech_hidpp hid_logitech_dj hid_generic dm_crypt usbhid essiv authenc trusted asn1_encoder tee bnep btusb btrtl btbcm btintel btmtk > nov 25 16:05:34 qt-kt kernel: CR2: 0000000000000000 nov 25 16:05:34 qt-kt kernel: ---[ end trace 0000000000000000 ]--- Most of the time this happen after resuming the screens, the primary one get on, but the second is always in suspend mode, I have to open neither display settings in plasma or nvidia-settings to set on the second monitor (displayport slave link) after switching off and on the monitor. -- You are receiving this mail because: You are on the CC list for the bug.

1 23

[Bug 1207468] New: GCC 13: virtualbox package fails
by bugzilla_noreply＠suse.com 07 Mar '23

07 Mar '23

https://bugzilla.suse.com/show_bug.cgi?id=1207468 Bug ID: 1207468 Summary: GCC 13: virtualbox package fails 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.liska(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Fails here: https://build.opensuse.org/package/live_build_log/openSUSE:Factory:Staging:… due to: [ 242s] /home/abuild/rpmbuild/BUILD/VirtualBox-7.0.4/src/libs/dxvk-native-1.9.2a/src/util/util_bit.h:36:22: error: 'uint32_t' has not been declared [ 242s] 36 | T extract(T value, uint32_t fst, uint32_t lst) { [ 242s] | ^~~~~~~~ [ 242s] /home/abuild/rpmbuild/BUILD/VirtualBox-7.0.4/src/libs/dxvk-native-1.9.2a/src/util/util_bit.h:36:36: error: 'uint32_t' has not been declared [ 242s] 36 | T extract(T value, uint32_t fst, uint32_t lst) { [ 242s] | ^~~~~~~~ [ 242s] /home/abuild/rpmbuild/BUILD/VirtualBox-7.0.4/src/libs/dxvk-native-1.9.2a/src/util/util_bit.h:40:10: error: 'uint32_t' does not name a type [ 242s] 40 | inline uint32_t popcntStep(uint32_t n, uint32_t mask, uint32_t shift) { please include the missing header file: https://gcc.gnu.org/gcc-13/porting_to.html#header-dep-changes -- You are receiving this mail because: You are on the CC list for the bug.

1 11

[Bug 1195850] New: installation hooks are not working
by bugzilla_noreply＠suse.com 07 Mar '23

07 Mar '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1195850 Bug ID: 1195850 Summary: installation hooks are not working 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: comes(a)naic.edu QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- I'm trying to use hooks as described here: https://github.com/yast/yast-yast2/blob/master/library/general/doc/Hooks.md What I did is to create the file "before_copy_logs_finish_00_test_hook.sh" and put it in var/lib/YaST2/hooks/installation in the 'root' image that is used at installation time (to be clear like the one that is available in: download.opensuse.org/tumbleweed/repo/oss/boot/x86_64/root At the the end of the installation process, the script before_copy_logs_finish_00_test_hook.sh is supposed to be executed, but that doesn't happen. The log /var/log/YaST2/y2log-1.gz explains why: [Ruby] modules/Hooks.rb(find_hook_files):193 Found 1 hook files: before_copy_logs_finish_00_comes_hook.sh [Ruby] modules/Hooks.rb(execute):165 Executing hook 'before_copy_logs_finish' [Ruby] modules/Hooks.rb(execute):210 Executing hook file '/var/lib/YaST2/hooks/installation/before_copy_logs_finish_00_comes_hook.sh' [bash] ShellCommand.cc(shellcommand):78 sh: /var/lib/YaST2/hooks/installation/before_copy_logs_finish_00_comes_hook.sh: No such file or directory [Ruby] modules/Hooks.rb(execute):212 Hook file 'before_copy_logs_finish_00_comes_hook.sh' failed with stderr: sh: /var/lib/YaST/hooks/installation/before_copy_logs_finish_00_comes_hook.sh: No such file or directory The installer finds the script, but when it is executed it is not there. I suspected a chroot issue and to confirm my suspicion I did the following: After the installation process started, I moved to tty2 where a shell is available. The command 'ls /var/lib/YaST2/hooks/installation' shows that the hook script is there. then I did: mkdir -p /mnt/var/lib/YaST2/hooks/installation cp /var/lib/YaST2/hooks/installation/* /mnt/var/lib/YaST2/hooks/installation and let the installation process complete. This time the hook script got executed. The solution to the problem seemd to be: 1) do not execute the hook scripts in the chroot environment or 2) make the hook scripts visible in the chroot environment I guess the correct solution is number 2. For the record, the issue exists both in Leap 15.3 and tumbleweed. Using hooks was a possible solution to fix boo#1195118 bur I guess that's not an option right now. -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1207467] New: GCC 13: webkit2gtk3 package fails
by bugzilla_noreply＠suse.com 07 Mar '23

07 Mar '23

https://bugzilla.suse.com/show_bug.cgi?id=1207467 Bug ID: 1207467 Summary: GCC 13: webkit2gtk3 package fails 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.liska(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Fails here: https://build.opensuse.org/package/live_build_log/openSUSE:Factory:Staging:… due to: [ 181s] from /home/abuild/rpmbuild/BUILD/webkitgtk-2.38.3/Source/ThirdParty/ANGLE/src/compiler/translator/TranslatorESSL.cpp:7: [ 181s] /home/abuild/rpmbuild/BUILD/webkitgtk-2.38.3/Source/ThirdParty/ANGLE/include/GLSLANG/ShaderVars.h:19:26: error: 'uint64_t' does not name a type [ 181s] 19 | using ShCompileOptions = uint64_t; [ 181s] | ^~~~~~~~ [ 181s] /home/abuild/rpmbuild/BUILD/webkitgtk-2.38.3/Source/ThirdParty/ANGLE/include/GLSLANG/ShaderVars.h:17:1: note: 'uint64_t' is defined in header '<cstdint>'; did you forget to '#include <cstdint>'? [ 181s] 16 | #include <vector> [ 181s] +++ |+#include <cstdint> [ 181s] 17 | [ 181s] /home/abuild/rpmbuild/BUILD/webkitgtk-2.38.3/Source/ThirdParty/ANGLE/include/GLSLANG/ShaderVars.h:129:70: error: 'uint32_t' has not been declared [ 181s] 129 | const sh::ShaderVariable *findField(const std::string &fullName, uint32_t *fieldIndexOut) const; [ 181s] | ^~~~~~~~ [ 181s] In file included from /home/abuild/rpmbuild/BUILD/webkitgtk-2.38.3/Source/ThirdParty/ANGLE/src/compiler/translator/InfoSink.h:12, [ 181s] from /home/abuild/rpmbuild/BUILD/webkitgtk-2.38.3/Source/ThirdParty/ANGLE/src/compiler/translator/BuiltInFunctionEmulator.h:10, [ 181s] from /home/abuild/rpmbuild/BUILD/webkitgtk-2.38.3/Source/ThirdParty/ANGLE/src/compiler/translator/Compiler.h:20: [ 181s] /home/abuild/rpmbuild/BUILD/webkitgtk-2.38.3/Source/ThirdParty/ANGLE/include/GLSLANG/ShaderLang.h:98:7: error: 'ShCompileOptions' does not name a type [ 181s] 98 | const ShCompileOptions SH_VALIDATE_LOOP_INDEXING = UINT64_C(1) << 0; Fix hint: https://gcc.gnu.org/gcc-13/porting_to.html#header-dep-changes -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1205668] New: plymouth can not popup LUKS unlock ui
by bugzilla_noreply＠suse.com 07 Mar '23

07 Mar '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1205668 Bug ID: 1205668 Summary: plymouth can not popup LUKS unlock ui 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: hillwoodroc(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- I find this issue is caused by removing plymouth-keep-KillMode-none.patch. Rollback to the previous release package can workaround this issue. -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1179849] New: plymouth rpm output: bad invocation of systemd-sysv-convert: too few arguments
by bugzilla_noreply＠suse.com 07 Mar '23

07 Mar '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1179849 Bug ID: 1179849 Summary: plymouth rpm output: bad invocation of systemd-sysv-convert: too few arguments 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: mail(a)bernhard-voelker.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- I just saw this in the RPM output when doing 'zypper dup' today (openSUSE Tumbleweed 20201205-0 -> 20201207-0): (41/51) Installing: plymouth-0.9.5+git20200921+20778f2-4.1.x86_64 .......[done] Additional rpm output: usage: systemd-sysv-convert --apply <service> [<service> ...] Too few arguments. Please check to avoid this kind of worrying messages. -- You are receiving this mail because: You are on the CC list for the bug.

1 11

[Bug 1170344] New: Btrfsprogs 5.6 bug: kernel booting stop at "BTRFS info" output
by bugzilla_noreply＠novell.com 07 Mar '23

07 Mar '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1170344 Bug ID: 1170344 Summary: Btrfsprogs 5.6 bug: kernel booting stop at "BTRFS info" output Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Critical Priority: P5 - None Component: Basesystem Assignee: screening-team-bugs(a)suse.de Reporter: hillwoodroc(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- I Updated My PC and laptop to Tumbleweed 20200417, then these two systems could not boot, and there is not any error on screen. I tried to chroot to get the dmesg log, I got many BTRFS notices at the end. I find Btrfsprogs was updated before 10 days ago in Factory. I guess this is a bug for Btrfsprogs. -- You are receiving this mail because: You are on the CC list for the bug.

2 18

[Bug 1208762] New: Update our bugzilla instance to 5.0.x series release
by bugzilla_noreply＠suse.com 07 Mar '23

07 Mar '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1208762 Bug ID: 1208762 Summary: Update our bugzilla instance to 5.0.x series release Classification: openSUSE Product: openSUSE.org Version: unspecified Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Bugzilla Assignee: screening-team-bugs(a)suse.de Reporter: luc14n0(a)opensuse.org QA Contact: novbugzilla-bugs(a)forge.provo.novell.com Found By: --- Blocker: --- Currently our bugzilla instance seem to be sitting on the 4.4.x series release -- I can't figure out what exact version --, and missing out features, bug fixes and performance improvement, among other things, I presume. At this moment the 4.4.13 (from February 16, 2018) version is the old stable release [1], while the 5.0.6 (from February 09, 2019) is the current stable release. I know that there should be a SUSE team that purely oversees the infra side of bugzilla and another that takes care of the software itself (Legacy Application team?). Can anyone shine some light on why haven't our instance been updated to the current stable release yet? [1] https://www.bugzilla.org/releases/ -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1207056] New: systemd missing conf.d directories
by bugzilla_noreply＠suse.com 06 Mar '23

06 Mar '23

https://bugzilla.suse.com/show_bug.cgi?id=1207056 Bug ID: 1207056 Summary: systemd missing conf.d directories 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: dmueller(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- /etc/systemd/system.conf is recommending, rather than modifying it, to create a droplet in /etc/systemd/system.conf.d/ and /etc/system/user.conf.d (for /etc/systemd/user.conf). can we please ship those directories as part of the systemd package? -- You are receiving this mail because: You are on the CC list for the bug.

1 7