October 2024 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1231361] New: Leap16 ISO torrent is not registered with tracker
by bugzilla_noreply＠suse.com 07 Oct '24

07 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1231361 Bug ID: 1231361 Summary: Leap16 ISO torrent is not registered with tracker Classification: openSUSE Product: openSUSE Distribution Version: Leap 16.0 Hardware: x86-64 OS: Linux Status: NEW Severity: Normal Priority: P5 - None Component: Release Notes Assignee: lukas.kucharczyk(a)suse.com Reporter: jengelh(a)inai.de QA Contact: lubos.kocman(a)suse.com Target Milestone: --- Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:130.0) Gecko/20100101 Firefox/130.0 Build Identifier: Unable to download ISO file through torrent protocol. Reproducible: Always Steps to Reproduce: 1. goto https://get.opensuse.org/leap/16.0/ 2. at the dropdown button for "Intel or AMD 64-bit desktops, laptops, and servers (x86_64)", pick "torrent file"; alternatively, wget https://download.opensuse.org/distribution/leap/16.0/installer/iso/agama-in… 3. use that .torrent file with aria2c or rtorrent Actual Results: $ aria2c agama-installer-Leap.x86_64-openSUSE.iso.torrent 10/07 23:37:48 [NOTICE] Downloading 1 item(s) 10/07 23:37:48 [NOTICE] IPv4 DHT: listening on UDP port 6885 10/07 23:37:48 [NOTICE] IPv4 BitTorrent: listening on TCP port 6958 10/07 23:37:48 [NOTICE] IPv6 BitTorrent: listening on TCP port 6958 [#e71e6b 0B/604MiB(0%) CN:0 SD:0 DL:0B] 10/07 23:37:49 [ERROR] GID#9ac38b5dfb9e2846 - Tracker request http://tracker.opensuse.org:6969/announce?info_hash=%5Ee%E7%02y%90%CA%E6%A0… failed Exception: [DefaultBtAnnounce.cc:303] errorCode=1 Tracker returned failure reason: torrent not found *** Download Progress Summary as of Mon Oct 7 23:38:48 2024 *** ======================================================================================================================================= [#e71e6b 0B/604MiB(0%) CN:0 SD:0 DL:0B] FILE: /home/ej/VirtualBox VMs/agama-installer-Leap.x86_64-9.0.0-openSUSE-Build40.1.iso --------------------------------------------------------------------------------------------------------------------------------------- The error message is similar when using /usr/bin/rtorrent instead of aria2c: torrent not found. Expected Results: Produce me my ISO file. OS: openSUSE Tumbleweed 20241005 amd64 aria2-1.37.0-1.3.x86_64 rtorrent-0.10.0-1.1.x86_64 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1230891] Difficult to update mesa with Packman repo installed on Slowroll
by bugzilla_noreply＠suse.com 07 Oct '24

07 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1230891 https://bugzilla.suse.com/show_bug.cgi?id=1230891#c10 --- Comment #10 from ks so <kepasi(a)proton.me> --- (In reply to Michael Andres from comment #8) > (In reply to Stefan Hundhammer from comment #2) > > @sndirsch, @zypp-maintainers: Any good idea to continue here? > > A solver testcase will tell which repos are used, which packages are > installed, which are available and why the dup raises a conflict. > > Please run > > zypper dup --debug-solver > > Then pack the testcase directory together with the/var/log/zypper.log and > attach it to the bugreport. > > > ## > > cd /tmp > > tar cvjf zypper-testcase.bz2 /var/log/zypper.solverTestCase /var/log/zypper.log > > In case the testcase exceeds the 10MB limit for bugzilla uploads, you can > use 'split' to divide the file into smaller pieces: > > > cd /tmp > > split -b 10M --additional-suffix=-zypper-testcase.bz2 zypper-testcase.bz2 > > The created pieces will be named: > > > xaa-zypper-testcase.bz2 > > xab-zypper-testcase.bz2 > > xac-... Hi, can't execute it: localhost:/tmp> tar cvjf zypper-testcase.bz2 /var/log/zypper.solverTestCase /var/log/zypper.log tar: Eliminando la `/' inicial de los nombres /var/log/zypper.solverTestCase/ tar: /var/log/zypper.solverTestCase/y2log: No se puede efectuar open: Permiso denegado /var/log/zypper.solverTestCase/packman.repo.gz tar: Eliminando la `/' inicial de los objetivos de los enlaces /var/log/zypper.solverTestCase/repo-non-oss.repo.gz /var/log/zypper.solverTestCase/repo-openh264.repo.gz /var/log/zypper.solverTestCase/repo-oss.repo.gz /var/log/zypper.solverTestCase/repo-update.repo.gz /var/log/zypper.solverTestCase/(a)System.repo.gz /var/log/zypper.solverTestCase/solver.result /var/log/zypper.solverTestCase/testcase.t /var/log/zypper.solverTestCase/zypp-autoinst.yaml /var/log/zypper.solverTestCase/zypp-modalias.yaml /var/log/zypper.solverTestCase/zypp-control.yaml tar: /var/log/zypper.log: No se puede efectuar open: Permiso denegado tar: Se sale con estado de fallo debido a errores anteriores -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1230891] Difficult to update mesa with Packman repo installed on Slowroll
by bugzilla_noreply＠suse.com 07 Oct '24

07 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1230891 https://bugzilla.suse.com/show_bug.cgi?id=1230891#c9 --- Comment #9 from ks so <kepasi(a)proton.me> --- (In reply to Stefan Hundhammer from comment #6) > Notice that in comment #0 it says > > openSUSE Tumbleweed-Slowroll 20240901 > > For my Slowroll, I have: > > >> % sudo zypper lr --url | grep packman > >> > >> 5 | ftp.gwdg.de-Essentials | Packman Essentials Repo | Yes | (r ) Yes | Yes | > >> https://ftp.gwdg.de/pub/linux/misc/packman/suse/openSUSE_Slowroll/Essential… > > > @bug reporter: please paste the output of this command from your machine. > You might have the wrong url; openSUSE_Tumbleweed instead of > openSUSE_Slowroll. The differences in package versions between them are very > subtle. @localhost:~> sudo zypper lr --url [sudo] contraseña para root: Prioridades del repositorio en vigor: (Consulte 'zypper lr -P' para obtener más información) 70 (prioridad aumentada) : 1 repositorio 80 (prioridad aumentada) : 1 repositorio 99 (prioridad por defecto) : 3 repositorios # | Alias | Name | Enabled | GPG Check | Refresh | URI --+---------------------+---------------------------------+---------+-----------+---------+--------------------------------------------------------------------------------------------- 1 | openSUSE-20240803-0 | openSUSE-20240803-0 | No | ---- | ---- | hd:/?device=/dev/disk/by-id/usb-Kingston_DataTraveler_2.0_08606E6D418ABDB1B717002C-0:0-part2 2 | packman | Packman | Sí | (r ) Sí | Sí | https://ftp.fau.de/packman//suse/openSUSE_Slowroll/ 3 | repo-debug | openSUSE-Slowroll-Debug | No | ---- | ---- | http://download.opensuse.org/debug/slowroll/repo/oss/ 4 | repo-non-oss | openSUSE-Slowroll-Non-Oss | Sí | (r ) Sí | Sí | http://download.opensuse.org/slowroll/repo/non-oss/ 5 | repo-openh264 | Open H.264 Codec (openSUSE Tu-> | Sí | (r ) Sí | Sí | http://codecs.opensuse.org/openh264/openSUSE_Tumbleweed 6 | repo-oss | openSUSE-Slowroll-Oss | Sí | (r ) Sí | Sí | http://download.opensuse.org/slowroll/repo/oss/ 7 | repo-source | openSUSE-Slowroll-Source | No | ---- | ---- | http://download.opensuse.org/source/slowroll/repo/oss/ 8 | repo-update | openSUSE-Slowroll-Update | Sí | (r ) Sí | Sí | http://download.opensuse.org/update/slowroll/repo/oss/ -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1231289] New: libbullet may be built both with double precision and without
by bugzilla_noreply＠suse.com 07 Oct '24

07 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1231289 Bug ID: 1231289 Summary: libbullet may be built both with double precision and without Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: All OS: openSUSE Tumbleweed Status: NEW Severity: Enhancement Priority: P5 - None Component: Development Assignee: screening-team-bugs(a)suse.de Reporter: gm.ywr.gorau(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- The package libbullet3_17 from Tumbleweed:OSS provides shared objects built with #define BT_USE_DOUBLE_PRECISION. That causes link errors if we are expecting single-precicion libbullet3d. Having both variants on the same system has some advantages, for example, accurately the same results of simulation on different distributions for some simulation engine, if the scene is predefined. To give more context, here's an error from the build log: /s/Projects/limonEngine/src/AI/AIMovementGrid.cpp:277:(.text+0x2b2f): undefined reference to `btCapsuleShape::btCapsuleShape(float, float)' Considering that the binary *was* linking against libBulletCollision.so, here's the script to inspect /usr/lib64/libBulletCollision.so with radare2: radare2 /usr/lib64/libBulletCollision.so | tee outp.txt > aa > aaa > is (over 1400 lines are printed) > q In the file outp.txt we can find: 1233 0x0007a770 0x0007a770 GLOBAL FUNC 107 _ZN14btCapsuleShapeC1Edd btCapsuleShape::btCapsuleShape(double, double) So the reason of undefined reference is obvious. I propose adding /usr/lib64/libBulletCollision_dp.so with double precision, and /usr/lib64/libBullerCollision_sp.so without it. The symlink /usr/lib64/libBulletCollision.so will point to the one with DP. There are also other defines (like B3_USE_DOUBLE_PRECISION) and other libraries that may need such change. -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1212462] RAID Resync on every reboot with latest mdadm-4.1-150300.24.27.1 update
by bugzilla_noreply＠suse.com 07 Oct '24

07 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1212462 https://bugzilla.suse.com/show_bug.cgi?id=1212462#c13 --- Comment #13 from Björn Voigt <bjoernv(a)arcor.de> --- Created attachment 877785 --> https://bugzilla.suse.com/attachment.cgi?id=877785&action=edit mdmonitor log (journalctl -u mdmon(a)md127.service) I wonder about these messages: Main process exited, code=killed, status=9/KILL Failed with result 'signal'. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1231355] New: Touchpad disabling when mouse plugged in - config option missing, but it still works
by bugzilla_noreply＠suse.com 07 Oct '24

07 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1231355 Bug ID: 1231355 Summary: Touchpad disabling when mouse plugged in - config option missing, but it still works Classification: openSUSE Product: openSUSE Tumbleweed Version: Slowroll 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: rs.opensuse(a)spitzenpfeil.org QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- The config option is missing from system settings. However, if enabled in .config/touchpadrc like so, it still works: [autodisable] DisableWhenMousePluggedIn=true MouseBlacklist= Why is that? This used to be available with some synaptic package (which I have NOT installed). -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1231056] New: sof-audio-pci-intel-tgl error messages piling on system journal
by bugzilla_noreply＠suse.com 07 Oct '24

07 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1231056 Bug ID: 1231056 Summary: sof-audio-pci-intel-tgl error messages piling on system journal Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel:Drivers Assignee: kernel-bugs(a)suse.de Reporter: robertosalomon(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- System information: Operating System: openSUSE Tumbleweed 20240926 KDE Plasma Version: 6.1.5 KDE Frameworks Version: 6.6.0 Qt Version: 6.7.2 Kernel Version: 6.11.0-1-default (64-bit) Graphics Platform: X11 Processors: 24 × 12th Gen Intel® Core™ i7-12850HX Memory: 31.1 GiB of RAM Graphics Processor: NVIDIA RTX A2000 8GB Laptop GPU/PCIe/SSE2 Manufacturer: LENOVO Product Name: 21D6S16900 System Version: ThinkPad P16 Gen 1 Not sure when it started, since I only noticed it now. The following messages keep being written to the system log: Sep 27 15:56:13 treebeard kernel: sof-audio-pci-intel-tgl 0000:00:1f.3: ASoC: error at snd_soc_dai_hw_params on iDisp1 Pin: -22 This message repeats 20 times before changing to Sep 27 15:56:13 treebeard kernel: sof-audio-pci-intel-tgl 0000:00:1f.3: ASoC: error at snd_soc_dai_hw_params on iDisp2 Pin: -22 Which repeats 20 times and changes to Sep 27 15:56:13 treebeard kernel: sof-audio-pci-intel-tgl 0000:00:1f.3: ASoC: error at snd_soc_dai_hw_params on iDisp3 Pin: -22 Which also repeats for 20 times before going back to iDisp1 and continuing the cycle The driver logs the following information before entering the error message cycle: Sep 27 15:55:53 treebeard kernel: sof-audio-pci-intel-tgl 0000:00:1f.3: DSP detected with PCI class/subclass/prog-if 0x040380 Sep 27 15:55:53 treebeard kernel: sof-audio-pci-intel-tgl 0000:00:1f.3: use msi interrupt mode Sep 27 15:55:53 treebeard kernel: sof-audio-pci-intel-tgl 0000:00:1f.3: hda codecs found, mask 1 Sep 27 15:55:53 treebeard kernel: sof-audio-pci-intel-tgl 0000:00:1f.3: using HDA machine driver skl_hda_dsp_generic now Sep 27 15:55:53 treebeard kernel: sof-audio-pci-intel-tgl 0000:00:1f.3: DMICs detected in NHLT tables: 2 Sep 27 15:55:53 treebeard kernel: sof-audio-pci-intel-tgl 0000:00:1f.3: Firmware paths/files for ipc type 0: Sep 27 15:55:53 treebeard kernel: sof-audio-pci-intel-tgl 0000:00:1f.3: Firmware file: intel/sof/sof-adl-s.ri Sep 27 15:55:53 treebeard kernel: sof-audio-pci-intel-tgl 0000:00:1f.3: Topology file: intel/sof-tplg/sof-hda-generic-2ch.tplg Sep 27 15:55:53 treebeard kernel: sof-audio-pci-intel-tgl 0000:00:1f.3: Firmware info: version 2:2:0-57864 Sep 27 15:55:53 treebeard kernel: sof-audio-pci-intel-tgl 0000:00:1f.3: Firmware: ABI 3:22:1 Kernel ABI 3:23:1 Sep 27 15:55:53 treebeard kernel: sof-audio-pci-intel-tgl 0000:00:1f.3: unknown sof_ext_man header type 3 size 0x30 Sep 27 15:55:53 treebeard kernel: sof-audio-pci-intel-tgl 0000:00:1f.3: Firmware info: version 2:2:0-57864 Sep 27 15:55:53 treebeard kernel: sof-audio-pci-intel-tgl 0000:00:1f.3: Firmware: ABI 3:22:1 Kernel ABI 3:23:1 Sep 27 15:55:53 treebeard kernel: sof-audio-pci-intel-tgl 0000:00:1f.3: Topology: ABI 3:22:1 Kernel ABI 3:23:1 Sound works fine but the sheer amount of error messages on the log caught my eye. -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1231347] javapackages-tools should require which
by bugzilla_noreply＠suse.com 07 Oct '24

07 Oct '24

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

1 0

[Bug 1231354] New: [SELinux] bootctl denied { getattr ioctl open read } on removable device if system was installed on eMMC drive
by bugzilla_noreply＠suse.com 07 Oct '24

07 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1231354 Bug ID: 1231354 Summary: [SELinux] bootctl denied { getattr ioctl open read } on removable device if system was installed on eMMC drive Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Security Assignee: security-team(a)suse.de Reporter: gerald_chen(a)foxmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- I have openSUSE Tumbleweed installed on a Surface Go 3 64G version with a eMMC drive. Using systemd-boot as bootloader and SELinux (in enforcing mode) as MAC system, sdbootutil would failed to create or delete entries in /boot/efi/loader/entries alongside the snapshots. When creating snapshsots, ausearch showed that: ``` type=AVC msg=audit(1728309122.841:590): avc: denied { read } for pid=8820 comm="bootctl" name="mmcblk0p1" dev="devtmpfs" ino=343 scontext=system_u:system_r:snapperd_t:s0 tcontext=system_u:object_r:removable_device_t:s0 tclass=blk_file permissive=0 ``` It seemed that the eMMC drive the system got installed on was mistakenly considered as a removable device. Further experiments showed that I need to allow getattr, ioctl, open and read permissions for snapperd_t on removable_device_t:blk_file. So here's the generated snapper_emmc.te: ``` module snapper_emmc 1.0; require { type snapperd_t; type removable_device_t; class blk_file { getattr ioctl open read }; } #============= snapperd_t ============== allow snapperd_t removable_device_t:blk_file { getattr ioctl open read }; ``` After applying the generated module, sdbootutil worked again to create entries for snapshots as intended. This was discussed at this forum post: https://forums.opensuse.org/t/sdbootutil-failed-to-create-new-entry-for-new… I wonder if it's possible to apply these policies if the system is detected to be installed on a eMMC drive. Best wishes, Gerald -- You are receiving this mail because: You are on the CC list for the bug.

1 0

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

07 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1231323 Bug ID: 1231323 Summary: core dump (Segmentation fault) when ending repository management Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.6 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 Assignee: yast2-maintainers(a)suse.de Reporter: Ulrich.Windl(a)rz.uni-regensburg.de QA Contact: jsrain(a)suse.com Target Milestone: --- Found By: --- Blocker: --- Created attachment 877760 --> https://bugzilla.suse.com/attachment.cgi?id=877760&action=edit Most of the messages on the temrinal I was removing one repository, and adding two community repositories. When confirming the changes wirth OK, I saw these messages on the terminal: # yast2 repositories WARNING: Nokogiri was built against LibXML version 2.9.14, but has dynamically loaded 2.10.3 [BUG] Segmentation fault at 0x0000000000000063 ruby 2.5.9p229 (2021-04-05 revision 67939) [x86_64-linux-gnu] -- Machine register context ------------------------------------------------ RIP: 0x00007f8a454adb92 RBP: 0x0000000000000004 RSP: 0x00007fff74790da0 RAX: 0x0000000000000001 RBX: 0x0000000000000000 RCX: 0x0000000000000007 RDX: 0x0000000000000004 RDI: 0x0000000000000000 RSI: 0x00007f8a2f74d20e R8: 0x00005576b88b4010 R9: 0x0000000000000007 R10: 0x00005576bbb5cb70 R11: 0x3a25799cc2faca26 R12: 0x0000000000000028 R13: 0x00007fff74790f60 R14: 0x0000000084210843 R15: 0x00007f8a41552ca0 EFL: 0x0000000000010206 -- C level backtrace information ------------------------------------------- /usr/lib64/libruby2.5.so.2.5(0x7f8a459ca1e5) [0x7f8a459ca1e5] /usr/lib64/libruby2.5.so.2.5(0x7f8a459ca41c) [0x7f8a459ca41c] /usr/lib64/libruby2.5.so.2.5(0x7f8a45894544) [0x7f8a45894544] /usr/lib64/libruby2.5.so.2.5(0x7f8a4595a232) [0x7f8a4595a232] /lib64/libc.so.6(0x7f8a45457980) [0x7f8a45457980] /lib64/libc.so.6(__pthread_rwlock_wrlock+0x14) [0x7f8a454adb92] /usr/lib64/libcrypto.so.3(CRYPTO_THREAD_write_lock+0xb) [0x7f8a2f674659] /usr/lib64/libcrypto.so.3(RAND_get_rand_method+0x35) [0x7f8a2f74db13] /usr/lib64/libcrypto.so.3(RAND_status+0x8) [0x7f8a2f74e5f6] /usr/lib64/libcurl.so.4(0x7f8a4153902e) [0x7f8a4153902e] /usr/lib64/libcurl.so.4(0x7f8a41539086) [0x7f8a41539086] /usr/lib64/libcurl.so.4(0x7f8a415145a1) [0x7f8a415145a1] /usr/lib64/libcurl.so.4(0x7f8a414e1b79) [0x7f8a414e1b79] /usr/lib64/libcurl.so.4(0x7f8a414d9ba9) [0x7f8a414d9ba9] /usr/lib64/libcurl.so.4(0x7f8a4152d3fb) [0x7f8a4152d3fb] /usr/lib64/libcurl.so.4(curl_easy_cleanup+0x74) [0x7f8a414e0044] /usr/lib64/libzypp.so.1735(0x7f8a34d759d1) [0x7f8a34d759d1] /usr/lib64/libzypp.so.1735(0x7f8a34d40c45) [0x7f8a34d40c45] /usr/lib64/libzypp.so.1735(0x7f8a34d493c5) [0x7f8a34d493c5] /usr/lib64/libzypp.so.1735(_ZN4zypp5media12MediaManager7releaseEjRKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE+0x4a7) [0x7f8a34da5fa7] /usr/lib64/libzypp.so.1735(_ZN4zypp14MediaSetAccess7releaseEv+0xe5) [0x7f8a34ff5085] /usr/lib64/YaST2/plugin/libpy2Pkg.so.2(_ZN5YRepoD2Ev+0x4f) [0x7f8a41b9a33f] /usr/lib64/YaST2/plugin/libpy2Pkg.so.2(_ZN5YRepoD0Ev+0x9) [0x7f8a41b9a4b9] /usr/lib64/YaST2/plugin/libpy2Pkg.so.2(_ZNSt12_Destroy_auxILb0EE9__destroyIPN5boost13intrusive_ptrI5YRepoEEEEvT_S7_+0x31) [0x7f8a41b01721] /usr/lib64/YaST2/plugin/libpy2Pkg.so.2(_ZNSt6vectorIN5boost13intrusive_ptrI5YRepoEESaIS3_EED1Ev+0x10) [0x7f8a41b01770] /usr/lib64/YaST2/plugin/libpy2Pkg.so.2(_ZN12PkgFunctionsD2Ev+0x184) [0x7f8a41afdfa4] /usr/lib64/YaST2/plugin/libpy2Pkg.so.2(_ZN18PkgModuleFunctionsD1Ev+0x2b) [0x7f8a41af907b] /usr/lib64/YaST2/plugin/libpy2Pkg.so.2(_ZN9PkgModuleD0Ev+0xe) [0x7f8a41ae79ce] /usr/lib64/YaST2/plugin/libpy2Pkg.so.2(_ZN9PkgModule7destroyEv+0xb1) [0x7f8a41ae7e51] /usr/lib64/YaST2/plugin/libpy2Pkg.so.2(_ZN7Y2CCPkgD2Ev+0x6f) [0x7f8a41ae5a0f] /lib64/libc.so.6(0x5a226) [0x7f8a4545a226] /lib64/libc.so.6(0x5a36c) [0x7f8a4545a36c] /lib64/libc.so.6(0x40ef3) [0x7f8a45440ef3] /lib64/libc.so.6(__libc_start_main+0x87) [0x7f8a45440fb5] /usr/bin/ruby.ruby2.5(_start+0x2a) [0x5576a6c639aa] -- Other runtime information ----------------------------------------------- * Process memory map: (too long for comment) [NOTE] You may have encountered a bug in the Ruby interpreter or extension libraries. Bug reports are welcome. For details: http://www.ruby-lang.org/bugreport.html terminate called after throwing an instance of 'std::system_error' what(): Invalid argument terminate called recursively terminate called recursively terminate called recursively terminate called recursively terminate called recursively terminate called recursively terminate called recursively terminate called recursively terminate called recursively terminate called recursively terminate called recursively terminate called recursively terminate called recursively terminate called recursively ... erminate called recursively terminate called recursively terminate called recursively terminate called recursively /sbin/yast2: line 468: 15714 Segmentation fault (core dumped) $ybindir/y2start $module "$@" "$SELECTED_GUI" $Y2_GEOMETRY $Y2UI_ARGS Unfortunately there was no core dump:# cat /proc/sys/kernel/core_pattern |/bin/false -- You are receiving this mail because: You are on the CC list for the bug.

1 5