September 2022 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1189826] New: Severe screen flickering with kernel 5.13.12-1-default and i915
by bugzilla_noreply＠suse.com 12 Mar '23

12 Mar '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1189826 Bug ID: 1189826 Summary: Severe screen flickering with kernel 5.13.12-1-default and i915 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Major Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: javier(a)opensuse.org QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- My laptop's screen flickers so much with 5.13.12 that it renders my laptop unusable. One workaround is to close and open the lid. After resuming, it works fine - there is no flickering. Booting up from the KDE Live image works fine. I have used the same Tumbleweed version (20210820) as the one I have installed on my laptop. The only difference is that I have an encrypted /home partition on my laptop's SSD. Tested kernels: 5.10.16-1.3: OK 5.11.4-1.3: NON-OK 5.12.12-1: NON-OK 5.13.12-1: NON-OK KDE Plasma 5.22.4 KDE Frameworks 5.85.0 Qt 5.15.2 See the attachments for more details. -- You are receiving this mail because: You are on the CC list for the bug.

1 18

[Bug 1084017] New: YaST in Leap 15 fails to set boot flags correctly
by bugzilla_noreply＠novell.com 10 Mar '23

10 Mar '23

http://bugzilla.suse.com/show_bug.cgi?id=1084017 Bug ID: 1084017 Summary: YaST in Leap 15 fails to set boot flags correctly Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.0 Hardware: x86-64 OS: Other Status: NEW Severity: Major Priority: P5 - None Component: YaST2 Assignee: yast2-maintainers(a)suse.de Reporter: Larry.Finger(a)lwfinger.net QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- Created attachment 762755 --> http://bugzilla.suse.com/attachment.cgi?id=762755&action=edit Compressed YaST2 logs My system has a GPT partitioning scheme and does not use EFI. I also put the boot block at the start of the active partition, and have generic boot code in the MBR. The active partition is indicated with the legacy_boot flag. A partial df for the system is: Filesystem 1K-blocks Used Available Use% Mounted on /dev/sda3 60213124 9954072 47170668 18% / /dev/sda6 53826316 32795236 20576144 62% /var/tmp /dev/sda7 51255784 20631016 28050216 43% /TW /dev/sda4 60344404 22760752 36522788 39% /Leap42.3 /dev/sda5 711705020 393141448 282387980 59% /home tmpfs 809360 20 809340 1% /run/user/1000 Looking at the partitions with parted: GNU Parted 3.2 Using /dev/sda Welcome to GNU Parted! Type 'help' to view a list of commands. (parted) print Model: ATA Samsung SSD 850 (scsi) Disk /dev/sda: 1024GB Sector size (logical/physical): 512B/512B Partition Table: gpt Disk Flags: pmbr_boot Number Start End Size File system Name Flags 1 1049kB 9437kB 8389kB bios_grub 2 9437kB 16.8GB 16.8GB linux-swap(v1) swap 3 16.8GB 79.7GB 62.9GB ext4 4 79.7GB 143GB 62.9GB ext4 msftdata 5 143GB 883GB 741GB ext4 msftdata 6 883GB 939GB 56.1GB ext4 msftdata 8 939GB 971GB 31.5GB ext4 7 971GB 1024GB 53.5GB ext4 legacy_boot, msftdata (parted) quit In this case, partition number 7 will be booted. Running YaST => System => Boot Loader changes nothing. If I want the automatic boot to choose Leap 15.0, I need to manually toggle the legacy_boot flag on partitions 7 and 3. Attached is a compressed copy of the /var/log/YaST2/ directory. -- You are receiving this mail because: You are on the CC list for the bug.

2 15

[Bug 1201088] New: GCC 13: ceph package fails
by bugzilla_noreply＠suse.com 10 Mar '23

10 Mar '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1201088 Bug ID: 1201088 Summary: GCC 13: ceph package fails Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: screening-team-bugs(a)suse.de Reporter: martin.liska(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- The package fails due to: [ 183s] /home/abuild/rpmbuild/BUILD/ceph-16.2.9-158-gd93952c7eea/src/rocksdb/db/compaction/compaction_iteration_stats.h:23:3: error: 'uint64_t' does not name a type [ 183s] 23 | uint64_t total_filter_time = 0; [ 183s] | ^~~~~~~~ [ 183s] /home/abuild/rpmbuild/BUILD/ceph-16.2.9-158-gd93952c7eea/src/rocksdb/db/compaction/compaction_iteration_stats.h:9:1: note: 'uint64_t' is defined in header '<cstdint>'; did you forget to '#include <cstdint>'? [ 183s] 8 | #include "rocksdb/rocksdb_namespace.h" [ 183s] +++ |+#include <cstdint> as documented here: https://gcc.gnu.org/gcc-13/porting_to.html#header-dep-changes please report it to upstream. One can build with gcc13 with: osc build --alternative-project devel:gcc:next -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1027519] New: Xen: Missing upstream bug fixes
by bugzilla_noreply＠novell.com 09 Mar '23

09 Mar '23

http://bugzilla.suse.com/show_bug.cgi?id=1027519 Bug ID: 1027519 Summary: Xen: Missing upstream bug fixes Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Xen Assignee: xen-bugs(a)suse.de Reporter: carnold(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- There are upstream patches fixing bugs needed for this version of Xen. -- You are receiving this mail because: You are on the CC list for the bug.

2 293

[Bug 1203080] New: git-send-email: perl-TermReadLine-Gnu: Bad file descriptor during global destruction
by bugzilla_noreply＠suse.com 09 Mar '23

09 Mar '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1203080 Bug ID: 1203080 Summary: git-send-email: perl-TermReadLine-Gnu: Bad file descriptor during global destruction Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.4 Hardware: Other OS: Other Status: NEW Severity: Minor Priority: P5 - None Component: Development Assignee: screening-team-bugs(a)suse.de Reporter: ddiss(a)suse.com QA Contact: qa-bugs(a)suse.de CC: coolo(a)suse.com, ncutler(a)suse.com, tina.mueller(a)suse.com Found By: --- Blocker: --- git-send-email 2.35.3 on Leap 15.4 spits out a page full of warnings after a patch is successfully sent. E.g. > git send-email -1 ... Send this email? ([y]es|[n]o|[e]dit|[q]uit|[a]ll): y ... Result: 250 Warning: unable to close filehandle properly: Bad file descriptor during global destruction. Warning: unable to close filehandle properly: Bad file descriptor during global destruction. Warning: unable to close filehandle properly: Bad file descriptor during global destruction. Warning: unable to close filehandle properly: Bad file descriptor during global destruction. Warning: unable to close filehandle properly: Bad file descriptor during global destruction. Warning: unable to close filehandle properly: Bad file descriptor during global destruction. Warning: unable to close filehandle properly: Bad file descriptor during global destruction. Warning: unable to close filehandle properly: Bad file descriptor during global destruction. Warning: unable to close filehandle properly: Bad file descriptor during global destruction. Warning: unable to close filehandle properly: Bad file descriptor during global destruction. Warning: unable to close filehandle properly: Bad file descriptor during global destruction. Warning: unable to close filehandle properly: Bad file descriptor during global destruction. Warning: unable to close filehandle properly: Bad file descriptor during global destruction. Warning: unable to close filehandle properly: Bad file descriptor during global destruction. Warning: unable to close filehandle properly: Bad file descriptor during global destruction. Warning: unable to close filehandle properly: Bad file descriptor during global destruction. As mentioned, the patch is sent successfully, hence the minor severity. Searching around lead me to https://github.com/netdisco/netdisco/wiki/Troubleshooting#perl-termreadline… which states: > certain versions of this package can make netdisco-deploy error out with: > Warning: unable to close filehandle properly: Bad file descriptor during global destruction. > upgrading to a newer version (1.35) should fix the problem. I upgraded the Leap 15.4 perl-TermReadLine-Gnu-1.20 package to perl-Term-ReadLine-Gnu-1.42-lp154 from obs devel:languages:perl and sure enough the warning disappeared (the patch is also still successfully sent). @Tina, Coolo and Nathan: would you be open to updating the Leap 15.4 / SLE15-SP4 perl-TermReadLine-Gnu-1.20 package to perl-Term-ReadLine-Gnu-1.42? -- You are receiving this mail because: You are on the CC list for the bug.

1 8

[Bug 1192409] New: /usr/lib/systemd/system/lircd.service may not have ProtectClock=true
by bugzilla_noreply＠suse.com 08 Mar '23

08 Mar '23

https://bugzilla.suse.com/show_bug.cgi?id=1192409 Bug ID: 1192409 Summary: /usr/lib/systemd/system/lircd.service may not have ProtectClock=true Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: screening-team-bugs(a)suse.de Reporter: opensuse(a)mike.franken.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- With one of the last Tumbleweed snapshots some (all?) systemd service files got new options according to https://en.opensuse.org/openSUSE:Security_Features#Systemd_hardening_effort. But /usr/lib/systemd/system/lircd.service may not have set ProtectClock=true, because otherwise the daemon is not able to open the remote device: lircd-0.10.1[852]: Info: initializing '/dev/input/imon_remote' lircd-0.10.1[852]: Info: Using device: /dev/input/imon_remote lircd-0.10.1[852]: Error: unable to open '/dev/input/imon_remote' lircd-0.10.1[852]: Warning: Failed to initialize hardware lircd[852]: lircd-0.10.1[852]: Error: unable to open '/dev/input/imon_remote' lircd-0.10.1[852]: Error: unable to open '/dev/input/imon_remote' Without ProtectClock=true lircd works as expected. -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1202185] New: XSane crashes immediately
by bugzilla_noreply＠suse.com 08 Mar '23

08 Mar '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1202185 Bug ID: 1202185 Summary: XSane crashes immediately Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.4 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: aaronw(a)doofus.org QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Every time I try and start xsane it crashes. Note that my scanner works with Skanlite. > gdb xsane GNU gdb (GDB; SUSE Linux Enterprise 15) 11.1 Copyright (C) 2021 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-suse-linux". Type "show configuration" for configuration details. For bug reporting instructions, please see: <http://bugs.opensuse.org/>. Find the GDB manual and other documentation resources online at: <http://www.gnu.org/software/gdb/documentation/>. For help, type "help". Type "apropos word" to search for commands related to "word"... Reading symbols from xsane... Reading symbols from /usr/lib/debug/usr/bin/xsane-0.999-bp154.2.85.x86_64.debug... (gdb) run Starting program: /usr/bin/xsane Missing separate debuginfos, use: zypper install glibc-debuginfo-2.31-150300.37.1.x86_64 [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib64/libthread_db.so.1". [New Thread 0x7fffeb0b0700 (LWP 401985)] [Thread 0x7fffeb0b0700 (LWP 401985) exited] [New Thread 0x7fffeb0b0700 (LWP 401987)] [New Thread 0x7fffea1e6700 (LWP 401988)] [Thread 0x7fffea1e6700 (LWP 401988) exited] [Thread 0x7fffeb0b0700 (LWP 401987) exited] [New Thread 0x7fffeb0b0700 (LWP 401989)] [New Thread 0x7fffea1e6700 (LWP 401990)] [Thread 0x7fffea1e6700 (LWP 401990) exited] [Thread 0x7fffeb0b0700 (LWP 401989) exited] [New Thread 0x7fffeb0b0700 (LWP 401993)] [New Thread 0x7fffea1e6700 (LWP 401995)] [Thread 0x7fffea1e6700 (LWP 401995) exited] [New Thread 0x7fffea1e6700 (LWP 401998)] free(): invalid pointer Thread 1 "xsane" received signal SIGABRT, Aborted. 0x00007ffff53bccdb in raise () from /lib64/libc.so.6 Missing separate debuginfos, use: zypper install gtk2-theming-engine-adwaita-debuginfo-3.22.3-4.3.1.x86_64 hplip-hpijs-debuginfo-3.21.10-150400.1.9.x86_64 hplip-sane-debuginfo-3.21.10-150400.1.9.x86_64 iscan-debuginfo-2.30.4-pm153.5.3.x86_64 libXinerama1-debuginfo-1.1.3-1.22.x86_64 libatk-1_0-0-debuginfo-2.36.0-150400.2.9.x86_64 libavahi-client3-debuginfo-0.8-150400.5.73.x86_64 libavahi-common3-debuginfo-0.8-150400.5.73.x86_64 libbabl-0_1-0-debuginfo-0.1.88-150400.1.10.x86_64 libblkid1-debuginfo-2.37.2-150400.6.26.x86_64 libcanberra-gtk2-module-debuginfo-0.30-150400.13.10.x86_64 libcom_err2-debuginfo-1.46.4-150400.3.3.1.x86_64 libdatrie1-debuginfo-0.2.9-1.25.x86_64 libexiv2-26-debuginfo-0.26-6.8.1.x86_64 libexpat1-debuginfo-2.4.4-150400.3.6.9.x86_64 libfontconfig1-debuginfo-2.13.1-150400.1.4.x86_64 libfribidi0-debuginfo-1.0.10-150400.3.3.1.x86_64 libgcc_s1-debuginfo-11.3.0+git1637-150000.1.9.1.x86_64 libgdk_pixbuf-2_0-0-debuginfo-2.42.6-150400.3.8.x86_64 libgegl-0_4-0-debuginfo-0.4.34-150400.1.7.x86_64 libgexiv2-2-debuginfo-0.14.0-150400.2.10.x86_64 libgimp-2_0-0-debuginfo-2.10.30-150400.3.3.1.x86_64 libgio-2_0-0-debuginfo-2.70.4-150400.1.5.x86_64 libgmodule-2_0-0-debuginfo-2.70.4-150400.1.5.x86_64 libgnutls30-debuginfo-3.7.3-150400.4.3.6.x86_64 libgtk-2_0-0-debuginfo-2.24.33-150400.2.11.x86_64 libharfbuzz0-debuginfo-3.4.0-150400.3.3.1.x86_64 libltdl7-debuginfo-2.4.6-3.4.1.x86_64 liblzma5-debuginfo-5.2.3-150000.4.7.1.x86_64 libmount1-debuginfo-2.37.2-150400.6.26.x86_64 libnettle8-debuginfo-3.7.3-150400.2.21.x86_64 libp11-kit0-debuginfo-0.23.22-150400.1.10.x86_64 libpcre1-debuginfo-8.45-150000.20.13.1.x86_64 libpixman-1-0-debuginfo-0.40.0-150400.1.6.x86_64 libsane1-debuginfo-1.0.32-lp152.142.1.x86_64 libsnmp30-debuginfo-5.7.3-10.12.1.x86_64 libthai0-debuginfo-0.1.29-150400.1.4.x86_64 libtiff5-debuginfo-4.0.9-150000.45.11.1.x86_64 libunistring2-debuginfo-0.9.10-1.1.x86_64 libusb-1_0-0-debuginfo-1.0.24-150400.1.4.x86_64 libxcb-shm0-debuginfo-1.13-3.7.1.x86_64 libxml2-2-debuginfo-2.9.14-150400.5.7.1.x86_64 sane-backends-debuginfo-1.0.32-6.6.2.x86_64 (gdb) bt #0 0x00007ffff53bccdb in raise () at /lib64/libc.so.6 #1 0x00007ffff53be375 in abort () at /lib64/libc.so.6 #2 0x00007ffff5402b07 in __libc_message () at /lib64/libc.so.6 #3 0x00007ffff540ab8a in () at /lib64/libc.so.6 #4 0x00007ffff540ec46 in () at /lib64/libc.so.6 #5 0x000055555548ec80 in xsane_panel_build () at xsane.c:4831 #6 0x00005555554918e4 in xsane_device_dialog () at xsane.c:5332 #7 0x000055555549215d in xsane_interface (argv=<optimized out>, argc=<optimized out>) at xsane.c:6014 #8 0x0000555555423490 in main (argc=1, argv=0x7fffffffd618) at xsane.c:6250 -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1200684] New: Cannot find 'org.kde.KSplash.setStage' in object /KSplash at org.kde.KSplash
by bugzilla_noreply＠suse.com 08 Mar '23

08 Mar '23

https://bugzilla.suse.com/show_bug.cgi?id=1200684 Bug ID: 1200684 Summary: Cannot find 'org.kde.KSplash.setStage' in object /KSplash at org.kde.KSplash Classification: openSUSE Product: openSUSE Tumbleweed Version: Current 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: opensuse(a)mike.franken.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Starting with the latest Tumbleweed snapshot 20220617 I get the following messages in my journal: Cannot find 'org.kde.KSplash.setStage' in object /KSplash at org.kde.KSplash Activated service 'org.kde.KSplash' failed: Process org.kde.KSplash exited with status 1 I am not sure, if this has any impact on my system, but if not, what sense do they make? -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1048337] New: yast2-slide-show need to adjust the install path for new product builder
by bugzilla_noreply＠novell.com 08 Mar '23

08 Mar '23

http://bugzilla.suse.com/show_bug.cgi?id=1048337 Bug ID: 1048337 Summary: yast2-slide-show need to adjust the install path for new product builder Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 Assignee: yast2-maintainers(a)suse.de Reporter: mlin(a)suse.com QA Contact: jsrain(a)suse.com CC: adrian(a)suse.com Found By: --- Blocker: --- I've tested this in the staging project, I hot-patched yast2-slide-show then all files are located at /usr/lib/skelcd/CD1 for new product builder, since DATADIR is obsoleted already then new product builder doesn't have process those files. you can find testdvd build log at https://build.opensuse.org/package/live_build_log/openSUSE:Factory:Staging:… so the main question: is product builder still support slideshow? if so where is the right path it should be? -- You are receiving this mail because: You are on the CC list for the bug.

2 8

[Bug 980292] New: Yast shouldn't allow running two instances of module at once
by bugzilla_noreply＠novell.com 08 Mar '23

08 Mar '23

http://bugzilla.suse.com/show_bug.cgi?id=980292 Bug ID: 980292 Summary: Yast shouldn't allow running two instances of module at once Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 Assignee: yast2-maintainers(a)suse.de Reporter: hguo(a)suse.com QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- It's very easy to mistakenly double click on a module icon in Yast2, causing two instances of the module to be started, and there's absolutely no point in using more than one instance of any yast module. Please disallow double click on yast2, and prevent more than one instance of module to be started. -- You are receiving this mail because: You are on the CC list for the bug.

2 8