September 2021 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1190740] Race condition when linking to LLVM on s390x
by bugzilla_noreply＠suse.com 26 Sep '21

26 Sep '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1190740 http://bugzilla.opensuse.org/show_bug.cgi?id=1190740#c10 --- Comment #10 from Sarah Kriesch <ada.lovelace(a)gmx.de> --- (In reply to Reinhard Max from comment #9) > None of the PostgreSQL packages on openSUSE or SLE has a constraints file. Then SUSE has got larger VMs as a default for building packages. The smallest openSUSE building instances have got 4GB of memory. I have to say, that there is an open bug report because of the double memory usage with GCC on the mainframe: https://bugzilla.opensuse.org/show_bug.cgi?id=1188441 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1181700] Feature: Support graphical installation for s390x guests using qemu's virtio-gpu gfx emulation
by bugzilla_noreply＠suse.com 26 Sep '21

26 Sep '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1181700 Sarah Kriesch <ada.lovelace(a)gmx.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |ada.lovelace(a)gmx.de -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1190881] New: Sound test works OK with KDE plasmoid "Volume", but fails with KDE System Settings
by bugzilla_noreply＠suse.com 26 Sep '21

26 Sep '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1190881 Bug ID: 1190881 Summary: Sound test works OK with KDE plasmoid "Volume", but fails with KDE System Settings Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.2 Hardware: x86-64 OS: Linux Status: NEW Severity: Normal Priority: P5 - None Component: KDE Workspace (Plasma) Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: kaykaykay123(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Using onboard Realtek ALC1220 front output at the back of motherboard and monitor speakers connected with HDMI cable. With YaST sound settings: test sound doesn't work at all. With KDE plasmoid "Volume" (icon "speaker" at system tray) sound test works OK. With "KDE System Settings" sound test uses HDMI output no matter what I choose in Audio -> Advanced -> Output. Testing with running systemsettings5 from Konsole, changing output device and clicking "Front Left" and "Front Right" buttons results in: :~> LANG=C systemsettings5 kf5.kservice.sycoca: Parse error in "/home/lins/.config/menus/applications-merged/xdg-desktop-menu-dummy.menu" , line 1 , col 1 : "unexpected end of file" kf5.kservice.services: The desktop entry file "/usr/share/applications/org.gnome.ChromeGnomeShell.desktop" has Type= "Application" but no Exec line kf5.kservice.sycoca: Invalid Service : "/usr/share/applications/org.gnome.ChromeGnomeShell.desktop" kf5.kservice.services: The desktop entry file "/usr/share/applications/qemu.desktop" has Type= "Application" but no Exec line kf5.kservice.sycoca: Invalid Service : "/usr/share/applications/qemu.desktop" org.kde.plasma.pulseaudio: No object for name "alsa_output.pci-0000_08_00.6.analog-stereo.monitor" org.kde.plasma.pulseaudio: No object for name "alsa_output.pci-0000_08_00.6.analog-stereo.monitor" org.kde.plasma.pulseaudio: No object for name "alsa_output.pci-0000_08_00.6.analog-stereo" org.kde.plasma.pulseaudio: No object for name "alsa_output.pci-0000_08_00.6.analog-stereo.monitor" org.kde.plasma.pulseaudio: No object for name "alsa_output.pci-0000_08_00.6.analog-stereo.monitor" -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1165535] New: System lockup under memory pressure using encrypted swap on SSD (failed command: WRITE FPDMA QUEUED)
by bugzilla_noreply＠novell.com 26 Sep '21

26 Sep '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1165535 Bug ID: 1165535 Summary: System lockup under memory pressure using encrypted swap on SSD (failed command: WRITE FPDMA QUEUED) Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.1 Hardware: Other OS: Other Status: NEW Severity: Major Priority: P5 - None Component: Kernel Assignee: kernel-maintainers(a)forge.provo.novell.com Reporter: Ulrich.Windl(a)rz.uni-regensburg.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- On a system that uses an SSD for /boot and encrypted swap only (the rest is on a traditional hard disk), I had the following problem: I was working normally with the system, when I decided to launch "yast2 online_update". Unfortunately the system became terribly slow (practically not responding for minutes), so I could not do anything than press the Reset-button after having waited about 30 minutes. After reboot I see "odd" ATA errors related to the SSD. However the SSD is rather new and in good condition. So I guess the issue has to do with memory pressure. Here are the logs when things started to become slow: Mar 03 10:09:57 pc dbus-daemon[2706]: [session uid=1000 pid=2706] Successfully activated service 'org.gnome.evince.Daemon' Mar 03 10:09:57 pc systemd[2686]: Starting Evince document viewer... Mar 03 10:09:57 pc systemd[2686]: Started Evince document viewer. Mar 03 10:10:13 pc kernel: ata2: log page 10h reported inactive tag 5 Mar 03 10:10:14 pc kernel: ata2.00: exception Emask 0x1 SAct 0x7fffffdf SErr 0x0 action 0x0 Mar 03 10:10:14 pc kernel: ata2.00: irq_stat 0x40000009 Mar 03 10:10:14 pc kernel: ata2.00: failed command: WRITE FPDMA QUEUED Mar 03 10:10:14 pc kernel: ata2.00: cmd 61/08:00:e0:b0:7d/00:00:00:00:00/40 tag 0 ncq dma 4096 out res 40/00:00:e0:b0:7d/00:00:00:00:00/40 Emask 0x1 (device error) Mar 03 10:10:14 pc kernel: ata2.00: status: { DRDY } Mar 03 10:10:14 pc kernel: ata2.00: failed command: WRITE FPDMA QUEUED Mar 03 10:10:14 pc kernel: ata2.00: cmd 61/08:08:e8:b0:7d/00:00:00:00:00/40 tag 1 ncq dma 4096 out res 40/00:00:e0:b0:7d/00:00:00:00:00/40 Emask 0x1 (device error) Mar 03 10:10:14 pc kernel: ata2.00: status: { DRDY } Mar 03 10:10:14 pc kernel: ata2.00: failed command: WRITE FPDMA QUEUED Mar 03 10:10:14 pc kernel: ata2.00: cmd 61/08:10:f0:b0:7d/00:00:00:00:00/40 tag 2 ncq dma 4096 out res 40/00:00:e0:b0:7d/00:00:00:00:00/40 Emask 0x1 (device error) Mar 03 10:10:14 pc kernel: ata2.00: status: { DRDY } [...] Mar 03 10:10:14 pc kernel: ata2.00: failed command: WRITE FPDMA QUEUED Mar 03 10:10:14 pc kernel: ata2.00: cmd 61/08:f0:d8:b0:7d/00:00:00:00:00/40 tag 30 ncq dma 4096 out res 40/00:00:e0:b0:7d/00:00:00:00:00/40 Emask 0x1 (device error) Mar 03 10:10:14 pc kernel: ata2.00: status: { DRDY } Mar 03 10:10:14 pc kernel: ata2.00: supports DRM functions and may not be fully accessible Mar 03 10:10:14 pc kernel: ata2.00: supports DRM functions and may not be fully accessible Mar 03 10:10:14 pc kernel: ata2.00: configured for UDMA/133 Mar 03 10:10:14 pc kernel: ata2: EH complete Mar 03 10:10:14 pc kernel: ata2.00: Enabling discard_zeroes_data Mar 03 10:10:14 pc rsyslogd[1332]: message repeated 13 times: [-- MARK --] Mar 03 10:10:14 pc rsyslogd[1332]: action 'action 1' suspended (module 'builtin:ompipe'), retry 0. There should be messages before this one giving the reason for suspension. [v8.33.1 try http://www.rsyslog.com/e/2007 ] Mar 03 10:10:14 pc rsyslogd[1332]: action 'action 1' suspended (module 'builtin:ompipe'), next retry is Tue Mar 3 10:10:44 2020, retry nbr 0. There should be messages before this one giving the reason for suspension. [v8.33.1 try http://www.rsyslog.com/e/2007 ] [...] Mar 03 10:15:48 pc /usr/lib/gdm/gdm-x-session[2700]: (II) event2 - Logitech USB-PS/2 Optical Mouse: SYN_DROPPED event - some input events have been lost. Mar 03 10:16:17 pc /usr/lib/gdm/gdm-x-session[2700]: (II) event2 - Logitech USB-PS/2 Optical Mouse: SYN_DROPPED event - some input events have been lost. [...] Mar 03 10:25:13 pc systemd-journald[30532]: Journal started Mar 03 10:25:18 pc systemd-journald[30532]: System journal (/var/log/journal/89c660865c00403a9bacef32b6828556) is 856.0M, max 819.2M, 0B free. [...] Mar 03 10:25:19 pc kernel: ata2.00: exception Emask 0x50 SAct 0x7f000007 SErr 0x800 action 0x6 frozen Mar 03 10:25:19 pc kernel: ata2.00: irq_stat 0x08000000, interface fatal error Mar 03 10:25:19 pc kernel: ata2: SError: { HostInt } Mar 03 10:25:19 pc kernel: ata2.00: failed command: WRITE FPDMA QUEUED Mar 03 10:25:19 pc kernel: ata2.00: cmd 61/c8:00:38:06:78/01:00:00:00:00/40 tag 0 ncq dma 233472 out res 40/00:c0:00:00:72/00:00:00:00:00/40 Emask 0x50 (ATA bus error) Mar 03 10:25:19 pc kernel: ata2.00: status: { DRDY } [...] Mar 03 10:25:19 pc kernel: ata2.00: failed command: WRITE FPDMA QUEUED Mar 03 10:25:19 pc kernel: ata2.00: cmd 61/40:f0:f8:00:78/05:00:00:00:00/40 tag 30 ncq dma 688128 out res 40/00:c0:00:00:72/00:00:00:00:00/40 Emask 0x50 (ATA bus error) Mar 03 10:25:19 pc kernel: ata2.00: status: { DRDY } Mar 03 10:25:19 pc kernel: ata2: hard resetting link Mar 03 10:25:19 pc kernel: ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300) Mar 03 10:25:19 pc kernel: ata2.00: supports DRM functions and may not be fully accessible Mar 03 10:25:19 pc kernel: ata2.00: supports DRM functions and may not be fully accessible Mar 03 10:25:19 pc kernel: ata2.00: configured for UDMA/133 Mar 03 10:25:19 pc kernel: ata2: EH complete Mar 03 10:25:19 pc kernel: ata2.00: Enabling discard_zeroes_data [...] Mar 03 10:25:19 pc systemd-coredump[30527]: Process 28448 (systemd-journal) of user 0 dumped core. Mar 03 10:25:19 pc systemd-coredump[30527]: Coredump diverted to /var/lib/systemd/coredump/core.systemd-journal.0.92bd8e3e91344ef998c2c08ade695cd2.28448.1583227313000000.lz4 Mar 03 10:25:19 pc systemd-coredump[30527]: Stack trace of thread 28448: Mar 03 10:25:19 pc systemd-coredump[30527]: #0 0x00007f52360114f5 journal_file_move_to_object (libsystemd-shared-234.so) Mar 03 10:25:19 pc systemd-coredump[30527]: #1 0x00007f5236012f00 n/a (libsystemd-shared-234.so) Mar 03 10:25:19 pc systemd-coredump[30527]: #2 0x00007f5236013548 n/a (libsystemd-shared-234.so) Mar 03 10:25:19 pc systemd-coredump[30527]: #3 0x00007f523601470d journal_file_append_entry (libsystemd-shared-234.so) [...] Mar 03 10:25:54 pc systemd-journald[30532]: Journal stopped Mar 03 10:26:38 pc systemd-journald[30532]: Received SIGTERM from PID 1 (systemd). Mar 03 10:26:38 pc systemd-journald[30545]: Journal started Mar 03 10:26:38 pc systemd-journald[30545]: System journal (/var/log/journal/89c660865c00403a9bacef32b6828556) is 856.0M, max 819.2M, 0B free. [...] >From this point on I did not see any more ATA errors, but the system was still unusable, so I hit Reset: Mar 03 10:55:58 pc kernel: SFW2-INext-DROP-DEFLT IN=eth0 OUT= MAC=00:22:11:dd:00:11:a0:36:9f:b2:3f:25:08:00 SRC=1.9.154.170 1.9.5.2 LEN=44 TOS=0x00 PREC=0x00 TTL=5 6 ID=52696 PROTO=TCP SPT=47944 DPT=655 WINDOW=1024 RES=0x00 SYN URGP=0 OPT (020405B4) -- Reboot -- Mar 03 11:05:24 linux-abcd kernel: Linux version 4.12.14-lp151.28.36-default (geeko@buildhost) (gcc version 7.4.1 20190905 [gcc-7-branch revision 275407] (SUSE Linux) ) #1 SMP Fri Dec 6 13:50:27 UTC 2019 (8f4a495) Final note: The IP address and related identifyable information in the log has been anonymized for privacy. -- You are receiving this mail because: You are on the CC list for the bug.

2 10

[Bug 1190766] python-rich backports requirement
by bugzilla_noreply＠suse.com 26 Sep '21

26 Sep '21

https://bugzilla.suse.com/show_bug.cgi?id=1190766 https://bugzilla.suse.com/show_bug.cgi?id=1190766#c1 Marcus Meissner <meissner(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |meissner(a)suse.com --- Comment #1 from Marcus Meissner <meissner(a)suse.com> --- i moved it to backpors 15-sp3 ... but i get dep errors: openSUSE_Backports_SLE-15-SP3_Update s390x unresolvable: nothing provides python3-commonmark >= 0.9.1 (got version 0.7.5 provided by python3-CommonMark) nothing provides python3-poetry-core -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1190877] New: ReadWritePaths is different from WorkingDirectory in strelaysrv.service
by bugzilla_noreply＠suse.com 26 Sep '21

26 Sep '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1190877 Bug ID: 1190877 Summary: ReadWritePaths is different from WorkingDirectory in strelaysrv.service Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Network Assignee: marius.kittler(a)suse.com Reporter: qydwhotmail(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- ReadWritePaths is different from WorkingDirectory, which makes the service fails to start. -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1190203] New: Installing Radicale on Leap 15.3 will not create corresponding user and group automatically
by bugzilla_noreply＠suse.com 26 Sep '21

26 Sep '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1190203 Bug ID: 1190203 Summary: Installing Radicale on Leap 15.3 will not create corresponding user and group automatically Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.3 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Network Assignee: screening-team-bugs(a)suse.de Reporter: qydwhotmail(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Installing Radicale on Leap 15.3 will not create radicale user and group automatically. Installing on Tumbleweed does not have this issue. -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1190874] New: grub restore only allows boot from 1 partition
by bugzilla_noreply＠suse.com 26 Sep '21

26 Sep '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1190874 Bug ID: 1190874 Summary: grub restore only allows boot from 1 partition Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: 64bit OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Bootloader Assignee: screening-team-bugs(a)suse.de Reporter: tech(a)reachthetribes.org QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- This was first brought up on this forum thread: https://forums.opensuse.org/showthread.php/560223-grub-restore-only-allows-… I have 2 partitions of equal size on my laptop, about 26gb each, ext4 format. They are both used for a root partition, the idea being to have one as a backup in case one of the tumbleweed updates totally doesn't work. This is my partition setup: Device Start End Sectors SizeType /dev/nvme0n1p1 2048 1026047 1024000 500M Microsoft basic data /dev/nvme0n1p2 1026048 55711743 54685696 26.1G Linux filesystem /dev/nvme0n1p3 55711744 110397439 54685696 26.1G Linux filesystem /dev/nvme0n1p4 110397440 1943756799 1833359360 874.2G Linux filesystem /dev/nvme0n1p5 1943756800 1953523711 9766912 4.7G Linux swap When I run the procedure to restore/install grub, here is what I do. As root in a terminal: --- > mkinitrd > grub2-mkconfig -o /boot/grub2/grub.cfg Generating grub configuration file ... Found theme: /boot/grub2/themes/openSUSE/theme.txt Found linux image: /boot/vmlinuz-5.14.5-1-default Found initrd image: /boot/initrd-5.14.5-1-default Found linux image: /boot/vmlinuz-5.14.2-1-default Found initrd image: /boot/initrd-5.14.2-1-default Warning: os-prober will be executed to detect other bootable partitions. Its output will be used to detect bootable binaries on them and create new boot entries. Found openSUSE Tumbleweed on /dev/nvme0n1p3 Adding boot menu entry for UEFI Firmware Settings ... done > grub2-install /dev/nvme0 Installing for x86_64-efi platform. Installation finished. No error reported. --- Notice what the result is in the grub configuration file. I will leave out the advanced options on both partitions because they are the same with regard to what I found: --- ### BEGIN /etc/grub.d/10_linux ### menuentry 'openSUSE Tumbleweed' --class opensuse --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-simple-ba22e191-xxxxxxxxxxxxxxxxxxx' { load_video set gfxpayload=keep insmod gzio insmod part_gpt insmod ext2 search --no-floppy --fs-uuid --set=root ba22e191-xxxxxxxxxxxxxxxxxxx echo 'Loading Linux 5.14.5-1-default ...' linuxefi /boot/vmlinuz-5.14.5-1-default root=UUID=ba22e191-xxxxxxxxxxxxxxxxxxxx splash=silent mitigations=auto quiet echo 'Loading initial ramdisk ...' initrdefi /boot/initrd-5.14.5-1-default } --- --- ### BEGIN /etc/grub.d/30_os-prober ### menuentry 'openSUSE Tumbleweed (on /dev/nvme0n1p3)' --class opensuse --class gnu-linux --class gnu --class os $menuentry_id_option 'osprober-gnulinux-simple-4efad914-xxxxxxxxxxxxxxxxxxxxxxx' { insmod part_gpt insmod ext2 search --no-floppy --fs-uuid --set=root 4efad914-xxxxxxxxxxxxxxxxxxxxxxxx linuxefi /boot/vmlinuz-5.14.2-1-default root=UUID=ba22e191-xxxxxxxxxxxxxxxxxxx splash=silent mitigations=auto quiet initrdefi /boot/initrd-5.14.2-1-default } --- See how on the 2nd menu item in grub for my 2nd root partition, the menuentry line points to the right UUID for that partition, and the search line also points to the right UUID for that partition. However, the actual boot line that begins with linuxefi points back to the other root partition, the same as in the first menu entry in grub. -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1190448] New: [boot] Generate server information file for login session takes a long time
by bugzilla_noreply＠suse.com 26 Sep '21

26 Sep '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1190448 Bug ID: 1190448 Summary: [boot] Generate server information file for login session takes a long time Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.2 Hardware: Other OS: openSUSE Leap 15.2 Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: screening-team-bugs(a)suse.de Reporter: ndordea(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Hello, For some time, the boot process takes a long time due to the started jobs .. The longes time was seen for : Generate server information file for login session that takes more than 7 minutes to complete The last info ..... sudo journalctl -a | grep "Generate server" [sudo] password for root: Sep 13 07:16:29 <hostname> systemd[1]: Starting Generate server information file for login session... Sep 13 07:25:12 <hostname>.dom systemd[1]: Started Generate server information file for login session. Sep 13 08:16:55 <hostname>.dom systemd[1]: Starting Generate server information file for login session... Sep 13 08:21:57 <hostname>.dom systemd[1]: Started Generate server information file for login session. Sep 13 09:17:33 <hostname>.dom systemd[1]: Starting Generate server information file for login session... Sep 13 09:23:45 <hostname>.dom systemd[1]: Started Generate server information file for login session. Sep 13 10:17:39 <hostname>.dom systemd[1]: Starting Generate server information file for login session... Sep 13 10:23:28 <hostname>.dom systemd[1]: Started Generate server information file for login session. Thanks. ND -- You are receiving this mail because: You are on the CC list for the bug.

1 9

[Bug 1137569] [Build 20190605] openQA test fails in vino_screensharing_available
by bugzilla_noreply＠suse.com 25 Sep '21

25 Sep '21

https://bugzilla.suse.com/show_bug.cgi?id=1137569 https://bugzilla.suse.com/show_bug.cgi?id=1137569#c23 --- Comment #23 from openQA Review <openqa-review(a)suse.de> --- This is an autogenerated message for openQA integration by the openqa_review script: This bug is still referenced in a failing openQA test: extra_tests_on_gnome https://openqa.opensuse.org/tests/1937264 To prevent further reminder comments one of the following options should be followed: 1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted 2. The openQA job group is moved to "Released" or "EOL" (End-of-Life) 3. The bugref in the openQA scenario is removed or replaced, e.g. `label:wontfix:boo1234` -- You are receiving this mail because: You are on the CC list for the bug.

1 0