October 2024 - openSUSE Bugs - openSUSE Mailing Lists

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

09 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1231323 https://bugzilla.suse.com/show_bug.cgi?id=1231323#c15 Michael Andres <ma(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(zypp-maintainers@ | |suse.de) | --- Comment #15 from Michael Andres <ma(a)suse.com> --- No real clue. But the immediate end of the log is strange. No core available? ~PkgFunctions() resets the zypp_pointer and the `y2milestone("Zypp pointer released")` logline works. AFAICS `PkgFunctions pkg_functions;` is owned by `class PkgModuleFunctions`. `class PkgModule` inherits `public PkgModuleFunctions` and appears to be a singleton with `static PkgModule* instance ();` and `static void destroy();`. PkgModule::instance redirects zypp::base::LogControl::instance().setLineWriter and setLineFormater to YaSTZyppLogger / YaSTZyppFormatter and creates a new PkgModule. Wich is finally owned by the global variable to register this component creator: `Y2CCPkg g_y2ccPkg;` Now ~Y2CCPkg triggers the deletion. PkgModule::destroy deletes the PkgModule (so the PkgModuleFunctions and the PkgFunctions it owns). Thats's what you see in the log: > 16:33:35 <0> [Pkg] Y2CCPkg.cc(~Y2CCPkg):64 ~Y2CCPkg > 16:33:35 <0> [Pkg] PkgModule.cc(destroy):101 Deleting PkgModule object... > 16:33:35 <0> [Pkg] Callbacks.cc(~CallbackHandler):1925 Deleting callback handler > 16:33:35 <1> [Pkg] PkgFunctions.cc(~PkgFunctions):152 Releasing the repo manager... > 16:33:35 <1> [Pkg] PkgFunctions.cc(~PkgFunctions):159 Releasing the zypp pointer... > 16:33:35 <1> [Pkg] PkgFunctions.cc(~PkgFunctions):161 Zypp pointer released ~Y2CCPkg - as a global static variable `Y2CCPkg g_y2ccPkg` - is triggered by unloading the y2pkg libbrary. Your objects are destructed, but the zypp::base::LogControl::instance().setLineWriter and setLineFormater still refer to YaSTZyppLogger / YaSTZyppFormatter objects. If zypp now logs something it might lead to calling functions in your domain while the lib is no longer loaded. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1224070] New: Missing Ark context menu in dolphin
by bugzilla_noreply＠suse.com 09 Oct '24

09 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1224070 Bug ID: 1224070 Summary: Missing Ark context menu in dolphin Classification: openSUSE Product: openSUSE Kalpa Version: Current Hardware: Other OS: Other Status: NEW Severity: Enhancement Priority: P5 - None Component: Desktop Environment Assignee: sfalken(a)cloverleaf-linux.org Reporter: mh306602(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Because Dolphin is installed through rpm and ark through flatpak, the integration is flawed between the 2. Could be fixed by either having both be installed through rpm's or both through flatpak. -- You are receiving this mail because: You are on the CC list for the bug.

1 12

[Bug 1229908] qxl drm module issues with proxmox
by bugzilla_noreply＠suse.com 09 Oct '24

09 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1229908 https://bugzilla.suse.com/show_bug.cgi?id=1229908#c16 --- Comment #16 from Norbert Möndjen <n.moendjen(a)vodafone.de> --- (In reply to Dario Faggioli from comment #15) > (In reply to Norbert Möndjen from comment #14) > > With the actual TW installed via Netinstall I have the same problem. > > > > Just for info these are the settings for video. I must push the memory > > settings to these levels so it doesn't crash the gui. The settings should be > > even good for two 8K Displays. Still no chance. > > > Right. Can you remind me if you've tested this already with other distros? > And, if not, can you perhaps give this a try? > > E.g., knowing if this works using a recent enough Fedora as a guest, as they > ship upstream-like kernel (kind of like Tumbleweed), but any other data > point helps. > > As Stefan said, it still seems a DRM issue to me, so it'd be cool to know if > we're the only one that are failing... I have tested it with Ubuntu and Debian and also deepin. All the actual Versions. I think the modesetting driver from the kernel is failing with qlx. With virtio it works but bcos bad luck it is no option here. And anyway qlx should be working either with the xorg or the kernel. But both are failing. Greetings and nice that the bug is not forgotten. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1231448] New: Poor handling of disk with encrypted partitions; gvfs-udisks2-vo crashed with segfault in libgio-2.0.so.0.7800.6
by bugzilla_noreply＠suse.com 09 Oct '24

09 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1231448 Bug ID: 1231448 Summary: Poor handling of disk with encrypted partitions; gvfs-udisks2-vo crashed with segfault in libgio-2.0.so.0.7800.6 Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.6 Hardware: x86-64 OS: Linux Status: NEW Severity: Normal Priority: P5 - None Component: GNOME Assignee: gnome-bugs(a)suse.de Reporter: Ulrich.Windl(a)rz.uni-regensburg.de QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 877862 --> https://bugzilla.suse.com/attachment.cgi?id=877862&action=edit disks shown in the file manager I had an external GPT partitioned disk containing two LUKS2-encrypted partitions: Device Start End Sectors Size Type /dev/sda1 2048 1050623 1048576 512M EFI System /dev/sda2 1050624 3147775 2097152 1G Linux filesystem /dev/sda3 3147776 338692095 335544320 160G Linux reserved /dev/sda4 338692096 500117503 161425408 77G Linux reserved When connecting the disk, there is a popup asking for a passphrase, but it's not obvious for which partition the passphrase is required (so I tried both). After that another request for a passphrase appeared, but gvfs-udisks2-vo crashed: ct 09 22:20:13 P16-G2-1.fritz.box kernel: usb 4-2.4.1: new SuperSpeed Plus Gen 2x1 USB device number 6 using xhci_hcd Oct 09 22:20:13 P16-G2-1.fritz.box kernel: usb 4-2.4.1: New USB device found, idVendor=152d, idProduct=0562, bcdDevice=31.02 Oct 09 22:20:13 P16-G2-1.fritz.box kernel: usb 4-2.4.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 Oct 09 22:20:13 P16-G2-1.fritz.box kernel: usb 4-2.4.1: Product: USB 3.1 Storage Device Oct 09 22:20:13 P16-G2-1.fritz.box kernel: usb 4-2.4.1: Manufacturer: JMicron ... Oct 09 22:20:13 P16-G2-1.fritz.box mtp-probe[12900]: bus: 4, device: 6 was not an MTP device Oct 09 22:20:13 P16-G2-1.fritz.box boltd[2590]: probing: started [1000] Oct 09 22:20:13 P16-G2-1.fritz.box kernel: SCSI subsystem initialized Oct 09 22:20:13 P16-G2-1.fritz.box kernel: alua: device handler registered Oct 09 22:20:13 P16-G2-1.fritz.box kernel: rdac: device handler registered Oct 09 22:20:13 P16-G2-1.fritz.box kernel: emc: device handler registered Oct 09 22:20:13 P16-G2-1.fritz.box kernel: usbcore: registered new interface driver usb-storage Oct 09 22:20:13 P16-G2-1.fritz.box kernel: scsi host0: uas Oct 09 22:20:13 P16-G2-1.fritz.box kernel: usbcore: registered new interface driver uas Oct 09 22:20:13 P16-G2-1.fritz.box kernel: scsi 0:0:0:0: Direct-Access Lexar 25 6GB SSD 3102 PQ: 0 ANSI: 6 Oct 09 22:20:13 P16-G2-1.fritz.box mtp-probe[12936]: checking bus 4, device 6: "/sys/devices/pci0000:00/0000:00:1d.0/0000:20:00.0/0000:21:02.0/0000:48:00.0/usb4/4-2/4-2.4/4-2.4.1" Oct 09 22:20:13 P16-G2-1.fritz.box mtp-probe[12936]: bus: 4, device: 6 was not an MTP device Oct 09 22:20:13 P16-G2-1.fritz.box kernel: sd 0:0:0:0: Attached scsi generic sg0 type 0 Oct 09 22:20:16 P16-G2-1.fritz.box boltd[2590]: probing: timeout, done: [2944628] (2000000) Oct 09 22:20:17 P16-G2-1.fritz.box kernel: sd 0:0:0:0: [sda] 500118192 512-byte logical blocks: (256 GB/238 GiB) Oct 09 22:20:17 P16-G2-1.fritz.box kernel: sd 0:0:0:0: [sda] 4096-byte physical blocks Oct 09 22:20:17 P16-G2-1.fritz.box kernel: sd 0:0:0:0: [sda] Write Protect is off Oct 09 22:20:17 P16-G2-1.fritz.box kernel: sd 0:0:0:0: [sda] Mode Sense: 5f 00 00 08 Oct 09 22:20:17 P16-G2-1.fritz.box kernel: sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA Oct 09 22:20:17 P16-G2-1.fritz.box kernel: sd 0:0:0:0: [sda] Preferred minimum I/O size 4096 bytes Oct 09 22:20:17 P16-G2-1.fritz.box kernel: sd 0:0:0:0: [sda] Optimal transfer size 33553920 bytes not a multiple of preferred minimum block size (4096 bytes) Oct 09 22:20:17 P16-G2-1.fritz.box kernel: sda: sda1 sda2 sda3 sda4 Oct 09 22:20:17 P16-G2-1.fritz.box kernel: sd 0:0:0:0: [sda] Attached SCSI disk Oct 09 22:20:17 P16-G2-1.fritz.box boltd[2590]: probing: started [1000] Oct 09 22:20:18 P16-G2-1.fritz.box udisksd[4619]: Mounted /dev/sda2 at /run/media/windl/boot on behalf of uid 1000 Oct 09 22:20:18 P16-G2-1.fritz.box kernel: EXT4-fs (sda2): mounted filesystem 72e00765-27e7-4266-9dbf-e14c6f0d1b84 r/w with ordered data mode. Quota mode: none. Oct 09 22:20:20 P16-G2-1.fritz.box boltd[2590]: probing: timeout, done: [2991912] (2000000) Oct 09 22:21:28 P16-G2-1.fritz.box udisksd[4619]: Unlocked device /dev/sda4 as /dev/dm-3 Oct 09 22:21:28 P16-G2-1.fritz.box udisksd[4619]: Mounted /dev/dm-3 at /run/media/windl/38034dd4-fb78-4abd-a2e0-80bbe5924ef6 on behalf of uid 1000 Oct 09 22:21:28 P16-G2-1.fritz.box kernel: EXT4-fs (dm-3): mounted filesystem 38034dd4-fb78-4abd-a2e0-80bbe5924ef6 r/w with ordered data mode. Quota mode: none. Oct 09 22:22:06 P16-G2-1.fritz.box lvm[15168]: PV /dev/dm-4 online, VG qubes_dom0 is complete. Oct 09 22:22:06 P16-G2-1.fritz.box systemd[1]: Started /usr/sbin/lvm vgchange -aay --autoactivation event qubes_dom0. Oct 09 22:22:06 P16-G2-1.fritz.box gnome-shell[4422]: Unable to mount volume 172 GB Encrypted: Gio.IOErrorEnum: Operation was cancelled Oct 09 22:22:06 P16-G2-1.fritz.box systemd[4224]: gvfs-udisks2-volume-monitor.service: Main process exited, code=dumped, status=11/SEGV Oct 09 22:22:06 P16-G2-1.fritz.box systemd[4224]: gvfs-udisks2-volume-monitor.service: Failed with result 'core-dump'. Oct 09 22:22:06 P16-G2-1.fritz.box kernel: show_signal_msg: 49 callbacks suppressed Oct 09 22:22:06 P16-G2-1.fritz.box kernel: gvfs-udisks2-vo[4785]: segfault at 55f700746f6f ip 00007fb501045d0e sp 00007ffe59f04630 error 4 in libgio-2.0.so.0.7800.6[b6d0e,7fb500f8f000+1de000] likely on CPU 9 (core 16, socket 0) Oct 09 22:22:06 P16-G2-1.fritz.box kernel: Code: fe 09 00 48 8d 35 52 87 0c 00 48 8d 3d 96 b8 09 00 e8 96 ad f8 ff 31 c0 5b c3 66 90 53 48 89 fb e8 e7 fb ff ff 48 85 db 74 22 <48> 8b 13 48 85 d2 74 05 48 39 02 74 0f 48 89 c6 48 89 df e8 aa b2 Oct 09 22:22:06 P16-G2-1.fritz.box gnome-shell[4422]: Owner of volume monitor org.gtk.vfs.UDisks2VolumeMonitor disconnected from the bus; removing drives/volumes/mounts Oct 09 22:22:07 P16-G2-1.fritz.box udisksd[4619]: Unlocked device /dev/sda3 as /dev/dm-4 Oct 09 22:22:07 P16-G2-1.fritz.box kernel: device-mapper: thin: Data device (dm-7) discard unsupported: Disabling discard passdown. Oct 09 22:22:07 P16-G2-1.fritz.box systemd[1]: Started Device-mapper event daemon. Oct 09 22:22:07 P16-G2-1.fritz.box dmeventd[15204]: dmeventd ready for processing. Oct 09 22:22:07 P16-G2-1.fritz.box lvm[15204]: Monitoring thin pool qubes_dom0-root--pool-tpool. Oct 09 22:22:07 P16-G2-1.fritz.box kernel: device-mapper: thin: Data device (dm-11) discard unsupported: Disabling discard passdown. Oct 09 22:22:07 P16-G2-1.fritz.box lvm[15204]: Monitoring thin pool qubes_dom0-vm--pool-tpool. Oct 09 22:22:08 P16-G2-1.fritz.box lvm[15171]: 36 logical volume(s) in volume group "qubes_dom0" now active Oct 09 22:22:08 P16-G2-1.fritz.box systemd[1]: lvm-activate-qubes_dom0.service: Deactivated successfully. In the file manager the two encrypted partitions are not shown. -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1231165] Incorrect process exit value in xmlstarlet format when "--omit-decl" flag given
by bugzilla_noreply＠suse.com 09 Oct '24

09 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1231165 Matej Cepl <mcepl(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mcepl(a)suse.com -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1231446] Aeon-Installer.x86_64-0.1.0-Snapshot20241007 install failed due to missing systemd-bootx64.efi
by bugzilla_noreply＠suse.com 09 Oct '24

09 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1231446 https://bugzilla.suse.com/show_bug.cgi?id=1231446#c1 Richard Brown <rbrown(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |DUPLICATE Status|NEW |RESOLVED --- Comment #1 from Richard Brown <rbrown(a)suse.com> --- Already resolved *** This bug has been marked as a duplicate of bug 1231324 *** -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1231324] Error after deploy image
by bugzilla_noreply＠suse.com 09 Oct '24

09 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1231324 https://bugzilla.suse.com/show_bug.cgi?id=1231324#c9 Richard Brown <rbrown(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |shanipribadi(a)gmail.com --- Comment #9 from Richard Brown <rbrown(a)suse.com> --- *** Bug 1231446 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1231446] New: Aeon-Installer.x86_64-0.1.0-Snapshot20241007 install failed due to missing systemd-bootx64.efi
by bugzilla_noreply＠suse.com 09 Oct '24

09 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1231446 Bug ID: 1231446 Summary: Aeon-Installer.x86_64-0.1.0-Snapshot20241007 install failed due to missing systemd-bootx64.efi Classification: openSUSE Product: openSUSE Aeon Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Major Priority: P5 - None Component: Installation Assignee: rbrown(a)suse.com Reporter: shanipribadi(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:131.0) Gecko/20100101 Firefox/131.0 Build Identifier: During installation of Aeon using Aeon-Installer.x86_64-0.1.0-Snapshot20241007, installation failed while setting up FDE. # tik.log > pkexec /usr/bin/chroot /var/lib/tik/encrypt/mnt sdbootutil -vv --esp-path /boot/efi --no-variables install Installing systemd-boot with shim into /boot/efi install: cannot stat '/.snapshots/1/snapshot/usr/lib/systemd/boot/efi/systemd-bootx64.efi Reproducible: Always Steps to Reproduce: 1.download the above raw.xz file 2. extract the image 3. write to usb using balenaEtcher 4. boot usb on a laptop without tpm 2.0 5. install Actual Results: install failed. tik installer ask to submit bug report here. Expected Results: install succeeded. - This is on a laptop without TPM 2.0 (Fallback mode) opening a terminal during the failed installation and manually checking the packages shows that systemd-boot (the package that provides the missing file) is not installed. > pkexec /usr/bin/chroot /var/lib/tik/encrypt/mnt rpm -q sdbootutil sdbootutil-1+git20241004.a1bb60f-1.1.x86_64 > pkexec /usr/bin/chroot /var/lib/tik/encrypt/mnt rpm -q systemd-boot package systemd-boot is not installed -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1231443] New: VUL-0: CVE-2024-46292: modsecurity: excessive resource consumption when processing POST requests with extremely large content-lengths
by bugzilla_noreply＠suse.com 09 Oct '24

09 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1231443 Bug ID: 1231443 Summary: VUL-0: CVE-2024-46292: modsecurity: excessive resource consumption when processing POST requests with extremely large content-lengths Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.6 Hardware: Other URL: https://smash.suse.de/issue/423485/ OS: Other Status: NEW Severity: Major Priority: P5 - None Component: Security Assignee: dimstar(a)opensuse.org Reporter: smash_bz(a)suse.de QA Contact: security-team(a)suse.de CC: camila.matos(a)suse.com Target Milestone: --- Found By: Security Response Team Blocker: --- A buffer overflow in modsecurity v3.0.12 allows attackers to cause a Denial of Service (DoS) via a crafted input inserted into the name parameter. References: http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2024-46292 https://www.cve.org/CVERecord?id=CVE-2024-46292 https://github.com/owasp-modsecurity/ModSecurity/blob/v3/master/README.md https://github.com/yoloflz101/yoloflz/blob/main/README.md -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1231174] New: std::chrono::zoned_time runtime error
by bugzilla_noreply＠suse.com 09 Oct '24

09 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1231174 Bug ID: 1231174 Summary: std::chrono::zoned_time runtime error Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Development Assignee: screening-team-bugs(a)suse.de Reporter: Gerhard(a)Dr-Lorbeer.de QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 877674 --> https://bugzilla.suse.com/attachment.cgi?id=877674&action=edit Example Project summary: No timezone computation possible Latest tumbleweed. kdevelop, c++ Example: https://en.cppreference.com/w/cpp/chrono/zoned_time compile OK. run: Error: std::chrono::tzdb: cannot locate zone: Africa/Casablanca Error: std::chrono::tzdb: cannot locate zone: America/Argentina/Buenos_Aires Error: std::chrono::tzdb: cannot locate zone: America/Barbados Error: std::chrono::tzdb: cannot locate zone: America/Indiana/Petersburg Error: std::chrono::tzdb: cannot locate zone: America/Tarasco_Bar Error: std::chrono::tzdb: cannot locate zone: Antarctica/Casey Error: std::chrono::tzdb: cannot locate zone: Antarctica/Vostok Error: std::chrono::tzdb: cannot locate zone: Asia/Magadan Error: std::chrono::tzdb: cannot locate zone: Asia/Manila Error: std::chrono::tzdb: cannot locate zone: Asia/Shanghai Error: std::chrono::tzdb: cannot locate zone: Asia/Tokyo Error: std::chrono::tzdb: cannot locate zone: Atlantic/Bermuda Error: std::chrono::tzdb: cannot locate zone: Australia/Darwin Error: std::chrono::tzdb: cannot locate zone: Europe/Isle_of_Man Error: std::chrono::tzdb: cannot locate zone: Europe/Laputa Error: std::chrono::tzdb: cannot locate zone: Indian/Christmas Error: std::chrono::tzdb: cannot locate zone: Indian/Cocos Error: std::chrono::tzdb: cannot locate zone: Pacific/Galapagos -- You are receiving this mail because: You are on the CC list for the bug.

1 2