https://bugzilla.suse.com/show_bug.cgi?id=1231323 https://bugzilla.suse.com/show_bug.cgi?id=1231323#c24 Stefan Hundhammer <shundhammer@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Component|YaST2 |libzypp QA Contact|jsrain@suse.com |qa-bugs@suse.de --- Comment #24 from Stefan Hundhammer <shundhammer@suse.com> --- @lslezak just wrote on IRC: "that code has not been touched for 17 (!) years, it is strange that it started failing now, I'd also expect some other change on the libzypp side." I fully agree. @zypp-maintainers: Please continue from here. I did the tests on an up-to-date TW, and my debugging branch was branched off 'master': https://github.com/yast/yast-pkg-bindings/tree/huha-debug-yrepo The test procedure is simple: Make sure none of the community repos are present, then add them with "yast2 repositories". Once you exit the module with "OK", you'll get the crash. For the backtrace in comment #17, I watched the y2log for the PID and then attached gdb to that running process. The tricky part is that the binary name is indeed the Ruby interpreter /usr/bin/ruby.ruby3.3 because the YaST part is embedded to it. -- You are receiving this mail because: You are on the CC list for the bug.