October 2024 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1232046] New: PC Freezes When Coming Out of Sleep
by bugzilla_noreply＠suse.com 22 Oct '24

22 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1232046 Bug ID: 1232046 Summary: PC Freezes When Coming Out of Sleep Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Major Priority: P5 - None Component: Basesystem Assignee: screening-team-bugs(a)suse.de Reporter: adamska156(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Operating System: openSUSE Tumbleweed 20241018 KDE Plasma Version: 6.2.1 KDE Frameworks Version: 6.7.0 Qt Version: 6.8.0 Kernel Version: 6.11.3-1-default (64-bit) Graphics Platform: Wayland Processors: 16 × AMD Ryzen 7 7700X 8-Core Processor Memory: 31.0 GiB of RAM Graphics Processor: AMD Radeon RX 5700 XT Manufacturer: Micro-Star International Co., Ltd. Product Name: MS-7D78 System Version: 1.0 When PC comes out of sleep, as soon as the kscreenlocker pops up the entire system freezes and becomes unresponsive. I'm unsure how to trace this issue. I've looked through logs and don't see anything but I don't know what to look for. This issue has been occuring for 2 or 3 weeks. -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1231506] plasma-powerdevil fails to start: undefined symbol: ddca_stop_watch_displays
by bugzilla_noreply＠suse.com 22 Oct '24

22 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1231506 https://bugzilla.suse.com/show_bug.cgi?id=1231506#c2 --- Comment #2 from Alex Debus <postix(a)posteo.eu> --- ``` > rpm -qif /lib64/libddcutil.so.5 Name : libddcutil5 Version : 2.1.4 Release : 1.1 Architecture: x86_64 Install Date: Thu 23 May 2024 12:13:46 PM CEST Group : System/Libraries Size : 936743 License : GPL-2.0-or-later Signature : RSA/SHA512, Thu 16 May 2024 05:34:06 PM CEST, Key ID 35a2f86e29b700a4 Source RPM : ddcutil-2.1.4-1.1.src.rpm Build Date : Wed 15 May 2024 08:58:39 AM CEST Build Host : reproducible Packager : https://bugs.opensuse.org Vendor : openSUSE URL : https://github.com/rockowitz/ddcutil Summary : Shared library to query and update monitor settings Description : Shared library version of ddcutil, exposing a C API. ddcutil communicates with monitors implementing MCCS (Monitor Control Command Set), using either the DDC/CI protocol on the I2C bus or as a Human Interface Device on USB. Distribution: openSUSE Tumbleweed ``` ``` > zypper info libddcutil5 Loading repository data... Reading installed packages... Information for package libddcutil5: ------------------------------------ Repository : Base:TumbleWeed Name : libddcutil5 Version : 2.1.4-1.1 Arch : x86_64 Vendor : openSUSE Installed Size : 914.8 KiB Installed : Yes (automatically) Status : up-to-date Source package : ddcutil-2.1.4-1.1.src Upstream URL : https://github.com/rockowitz/ddcutil Summary : Shared library to query and update monitor settings Description : Shared library version of ddcutil, exposing a C API. ddcutil communicates with monitors implementing MCCS (Monitor Control Command Set), using either the DDC/CI protocol on the I2C bus or as a Human Interface Device on USB. ``` -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1198684] grub2: install on ESP?
by bugzilla_noreply＠suse.com 22 Oct '24

22 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1198684 Jan Engelhardt <jengelh(a)inai.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jengelh(a)inai.de -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1218455] New: kernel: NOHZ tick-stop error: local softirq work is pending
by bugzilla_noreply＠suse.com 22 Oct '24

22 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1218455 Bug ID: 1218455 Summary: kernel: NOHZ tick-stop error: local softirq work is pending 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: opensuse(a)mike.franken.de QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Starting with kernel 6.6.6 (and continuing with 6.6.7) I get kernel: NOHZ tick-stop error: local softirq work is pending, handler #08!!! a few times within one or two minutes and during this time performance is degraded heavily. This happens about every two days, so it is not that much of a problem, but a bit annoying. system is: Operating System: openSUSE Tumbleweed 20231226 KDE Plasma Version: 5.27.10 KDE Frameworks Version: 5.113.0 Qt Version: 5.15.11 Kernel Version: 6.6.7-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 12

[Bug 1231595] New: Encrypted root file system fsck error is difficult to recover
by bugzilla_noreply＠suse.com 22 Oct '24

22 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1231595 Bug ID: 1231595 Summary: Encrypted root file system fsck error is difficult to recover Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Enhancement Priority: P5 - None Component: Basesystem Assignee: screening-team-bugs(a)suse.de Reporter: opensuse(a)halobates.de QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- On a system with encrypted root file system I had a corruption in the ext4 orphan list that dropped the initrd into the recovery shell when trying to mount sysroot. I had to recover by cat /proc/cmdline e2fsck UUID=<copy root uuid from cmdline> While I was able to do that it was a very cumbersome procedure to copy the UUID exactly and was non obvious and difficult for the user. It would be good if the initrd detected such a case and offers to run fsck by itself. -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1231798] libvirt requires iptables even with prefer_nftables set
by bugzilla_noreply＠suse.com 22 Oct '24

22 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1231798 https://bugzilla.suse.com/show_bug.cgi?id=1231798#c6 --- Comment #6 from OBSbugzilla Bot <bwiedemann+obsbugzillabot(a)suse.com> --- This is an autogenerated message for OBS integration: This bug (1231798) was mentioned in https://build.opensuse.org/request/show/1217084 Factory / libvirt -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1231323] core dump (Segmentation fault) when ending repository management
by bugzilla_noreply＠suse.com 22 Oct '24

22 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1231323 https://bugzilla.suse.com/show_bug.cgi?id=1231323#c19 --- Comment #19 from Stefan Hundhammer <shundhammer(a)suse.com> --- Looks like this uses a pointer that is now invalid: https://github.com/yast/yast-pkg-bindings/blob/master/src/YRepo.cc#L42 try { _maccess->release(); } -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1231323] core dump (Segmentation fault) when ending repository management
by bugzilla_noreply＠suse.com 22 Oct '24

22 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1231323 https://bugzilla.suse.com/show_bug.cgi?id=1231323#c18 --- Comment #18 from Stefan Hundhammer <shundhammer(a)suse.com> --- The last log lines (with debug logging): >> 17:51:15 <0> [Pkg] Y2CCPkg.cc(~Y2CCPkg):64 ~Y2CCPkg >> 17:51:15 <1> [Pkg] PkgModule.cc(unregisterZyppLogger):117 Closing down ZYPP logger >> 17:51:15 <1> [Pkg] PkgModule.cc(unregisterZyppLogger):122 ZYPP logger closed down. >> 17:51:15 <0> [Pkg] PkgModule.cc(destroy):96 Deleting PkgModule object... >> 17:51:15 <0> [Pkg] Callbacks.cc(~CallbackHandler):1925 Deleting callback handler >> 17:51:15 <1> [Pkg] PkgFunctions.cc(~PkgFunctions):152 Releasing the repo manager... >> 17:51:15 <1> [Pkg] PkgFunctions.cc(~PkgFunctions):159 Releasing the zypp pointer... >> 17:51:15 <1> [Pkg] PkgFunctions.cc(~PkgFunctions):161 Zypp pointer released. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1232020] New: Typo in neovim treesitter config with markdown_inline
by bugzilla_noreply＠suse.com 22 Oct '24

22 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1232020 Bug ID: 1232020 Summary: Typo in neovim treesitter config with markdown_inline Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Minor Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: m.krippendorf(a)posteo.de QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- In Neovim, When I run :checkhealth, I get this warning: - ERROR Parser "markdown-inline" failed to load (path: /usr/share/nvim/runtime/parser/markdown-inline.so): /usr/share/nvim/runtime/lua/vim/treesitter/language.lua:101: 'markdown-inline' is not a valid language name The same error appearantly occured in Nix where they fixed it by changing this line: { markdown-inline = treesitter-parsers.markdown // { language = "markdown_inline"; location = "tree-sitter-markdown-inline"; }; } into this: { markdown_inline = treesitter-parsers.markdown // { language = "markdown_inline"; location = "tree-sitter-markdown-inline"; }; } Notice the - vs. _ in the first word. For reference the diff from the Nix repo: https://github.com/Sobte/nixpkgs/commit/02c6a428f5f4c1a5c90b750d6236a495e0b… -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1231323] core dump (Segmentation fault) when ending repository management
by bugzilla_noreply＠suse.com 22 Oct '24

22 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1231323 https://bugzilla.suse.com/show_bug.cgi?id=1231323#c17 --- Comment #17 from Stefan Hundhammer <shundhammer(a)suse.com> --- I tried de-registering the ZYPP logger, but that didn't help. But at least I got a real backtrace now (sadly, without debuginfo): >> Thread 1 "Zypp-main" received signal SIGSEGV, Segmentation fault. >> >> (gdb) bt >> #0 0x00007f049469ea76 in pthread_rwlock_wrlock(a)GLIBC_2.2.5 () at /lib64/libc.so.6 >> #1 0x00007f046c819559 in CRYPTO_THREAD_write_lock () at /lib64/libcrypto.so.3 >> #2 0x00007f046c847363 in RAND_get_rand_method () at /lib64/libcrypto.so.3 >> #3 0x00007f046c8487a6 in RAND_status () at /lib64/libcrypto.so.3 >> #4 0x00007f046e1c27dc in ??? () at /lib64/libcurl.so.4 >> #5 0x00007f046e15d2fd in ??? () at /lib64/libcurl.so.4 >> #6 0x00007f046e159f4f in ??? () at /lib64/libcurl.so.4 >> #7 0x00007f046e1d1a5e in ??? () at /lib64/libcurl.so.4 >> #8 0x00007f046e15b934 in curl_easy_cleanup () at /lib64/libcurl.so.4 >> #9 0x00007f046cd97b31 in ??? () at /usr/lib64/libzypp.so.1735 >> #10 0x00007f046cd78fcf in ??? () at /usr/lib64/libzypp.so.1735 >> #11 0x00007f046cd7c420 in ??? () at /usr/lib64/libzypp.so.1735 >> #12 0x00007f046ce96cb1 in zypp::MediaSetAccess::release() () at /usr/lib64/libzypp.so.1735 >> #13 0x00007f04743af4bd in YRepo::~YRepo (this=0x559388bac9d0, __in_chrg=<optimized out>) at YRepo.cc:42 >> #14 0x00007f04743af4f9 in YRepo::~YRepo (this=0x559388bac9d0, __in_chrg=<optimized out>) at YRepo.cc:48 >> #15 0x00007f047432d2a1 in boost::intrusive_ptr<YRepo>::~intrusive_ptr (this=<optimized out>, __in_chrg=<optimized out>) >> at /usr/include/boost/smart_ptr/intrusive_ptr.hpp:100 >> #16 0x00007f047432d304 in std::_Destroy_aux<false>::__destroy<boost::intrusive_ptr<YRepo>*> (__first=0x559388b4fef0, __last=0x559388b4fef8) >> at /usr/include/c++/14/bits/stl_construct.h:163 >> #17 0x00007f047432d325 in std::_Destroy<boost::intrusive_ptr<YRepo>*> (__first=<optimized out>, __last=<optimized out>) >> at /usr/include/c++/14/bits/stl_construct.h:182 >> #18 0x00007f047432d340 in std::_Destroy<boost::intrusive_ptr<YRepo>*, boost::intrusive_ptr<YRepo> > (__first=<optimized out>, __last=<optimized out>) >> at /usr/include/c++/14/bits/alloc_traits.h:981 >> #19 std::vector<boost::intrusive_ptr<YRepo>, std::allocator<boost::intrusive_ptr<YRepo> > >::~vector (this=0x559387142428, __in_chrg=<optimized out>) >> at /usr/include/c++/14/bits/stl_vector.h:735 >> #20 0x00007f047432b0a6 in PkgFunctions::~PkgFunctions (this=0x5593871423b8, __in_chrg=<optimized out>) at PkgFunctions.cc:163 >> #21 0x00007f047432687b in PkgModuleFunctions::~PkgModuleFunctions (this=0x559387142380, __in_chrg=<optimized out>) at PkgModuleFunctions.cc:48 >> #22 0x00007f0474317b5f in PkgModule::~PkgModule (this=0x559387142380, __in_chrg=<optimized out>) at PkgModule.cc:88 >> #23 0x00007f0474317e77 in PkgModule::destroy () at PkgModule.cc:97 >> #24 0x00007f0474316605 in Y2PkgComponent::destroy () at Y2PkgComponent.cc:35 >> #25 0x00007f0474316763 in Y2CCPkg::~Y2CCPkg (this=0x7f0474412e90 <g_y2ccPkg>, __in_chrg=<optimized out>) at Y2CCPkg.cc:65 >> #26 0x00007f0494643f31 in __run_exit_handlers () at /lib64/libc.so.6 >> #27 0x00007f0494644000 in exit () at /lib64/libc.so.6 >> #28 0x00007f049462a2b5 in __libc_start_call_main () at /lib64/libc.so.6 >> #29 0x00007f049462a379 in __libc_start_main_impl () at /lib64/libc.so.6 >> #30 0x000055936e556155 in _start () >> (gdb) -- You are receiving this mail because: You are on the CC list for the bug.

1 0