September 2023 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1215590] New: Showing the "Authentication Required" root prompt not immediately after clicking "Install" or "Update" in GNOME software is possibly fundamentally insecure
by bugzilla_noreply＠suse.com 05 Dec '23

05 Dec '23

https://bugzilla.suse.com/show_bug.cgi?id=1215590 Bug ID: 1215590 Summary: Showing the "Authentication Required" root prompt not immediately after clicking "Install" or "Update" in GNOME software is possibly fundamentally insecure Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.5 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Security Assignee: security-team(a)suse.de Reporter: el(a)horse64.org QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Showing the "Authentication Required" root prompt not immediately after clicking "Install" or "Update" in GNOME software seems to me like it is fundamentally insecure, and I would argue it destroys all security benefits this prompt might possibly bring. The problem is that you're essentially training the user to just consent to this prompt no matter what horrible malicious actor might be showing it, since it contains zero information allowing the user to verify it was triggered by a legitimate source. I also can't think of any way you could possibly provide that information, since even if you showed the process id and name, another process could just name itself "gnome-software" and the user isn't going to remember the process id. As a consequence, the only somewhat reliable mechanism the user has for verifying that this prompt is legitimate and not a bad actor is that the prompt showed right after they triggered an action that is actually intended. This however appears to be destroyed by delaying this prompt until the download or whatever preparation steps are complete, rather than as instant as possible after clicking the "Install" or "Update" button in GNOME software. (Because I assume nobody will be just keeping the GNOME software window and stare at it to check that the prompt happened right after some progress bar reached 100%, at least I certainly don't.) -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1214169] New: cloud-init fails to install with "/usr/lib/rpm/fdupes_wrapper: No such file or directory"
by bugzilla_noreply＠suse.com 04 Dec '23

04 Dec '23

https://bugzilla.suse.com/show_bug.cgi?id=1214169 Bug ID: 1214169 Summary: cloud-init fails to install with "/usr/lib/rpm/fdupes_wrapper: No such file or directory" Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: carsten.tschense(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Updating cloud-init on MicroOS fails with (1/1) Installing: cloud-init-23.1-2.1.aarch64 [........ /var/tmp/rpm-tmp.JzYOr4: line 4: /usr/lib/rpm/fdupes_wrapper: No such file or directory warning: %post(cloud-init-23.1-2.1.aarch64) scriptlet failed, exit status 127 .done] -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1213796] New: java-20-openjdk fails to compile in 2034
by bugzilla_noreply＠suse.com 04 Dec '23

04 Dec '23

https://bugzilla.suse.com/show_bug.cgi?id=1213796 Bug ID: 1213796 Summary: java-20-openjdk fails to compile in 2034 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Java Assignee: java-maintainers(a)suse.de Reporter: bwiedemann(a)suse.com QA Contact: qa-bugs(a)suse.de CC: fstrba(a)suse.com Target Milestone: --- Found By: --- Blocker: --- While working on reproducible builds for openSUSE, I found that our java-20-openjdk package fails to compile in 2034 to reproduce: osc co openSUSE:Factory/java-20-openjdk && cd $_ osc build --clean --noservice -j1 --vm-type=kvm \ --build-opt=--vm-custom-opt="-rtc base=2034-02-02T00:00:00" \ standard x86_64 [ 284s] /usr/lib64/jvm/java/bin/java -XX:+UseSerialGC -Xms32M -Xmx512M -XX:TieredStopAtLevel=1 -Duser.language=en -Duser.country=US -XX:+UnlockDiagnosticVMOptions -XX:-VerifySharedSpaces -XX:SharedArchiveFile=/home/abuild/rpmbuild/BUILD/jdk20u-jdk-20.0.1-9/build/configure-support/classes.jsa -Xshare:auto -cp /home/abuild/rpmbuild/BUILD/jdk20u-jdk-20.0.1-9/build/buildtools/jdk_tools_classes build.tools.generatecharacter.CharacterName /home/abuild/rpmbuild/BUILD/jdk20u-jdk-20.0.1-9/src/java.base/share/data/unicodedata/UnicodeData.txt /home/abuild/rpmbuild/BUILD/jdk20u-jdk-20.0.1-9/build/jdk/modules/java.base/java/lang/uniName.dat [ 284s] /usr/bin/rm -f /home/abuild/rpmbuild/BUILD/jdk20u-jdk-20.0.1-9/build/jdk/modules/java.base/java/util/currency.data [ 284s] /usr/lib64/jvm/java/bin/java -XX:+UseSerialGC -Xms32M -Xmx512M -XX:TieredStopAtLevel=1 -Duser.language=en -Duser.country=US -XX:+UnlockDiagnosticVMOptions -XX:-VerifySharedSpaces -XX:SharedArchiveFile=/home/abuild/rpmbuild/BUILD/jdk20u-jdk-20.0.1-9/build/configure-support/classes.jsa -Xshare:auto -cp /home/abuild/rpmbuild/BUILD/jdk20u-jdk-20.0.1-9/build/buildtools/jdk_tools_classes build.tools.generatecurrencydata.GenerateCurrencyData -o /home/abuild/rpmbuild/BUILD/jdk20u-jdk-20.0.1-9/build/jdk/modules/java.base/java/util/currency.data.tmp -i /home/abuild/rpmbuild/BUILD/jdk20u-jdk-20.0.1-9/src/java.base/share/data/currency/CurrencyData.properties [ 285s] Error: time is more than 10 years from present: 1672527600000 [ 285s] java.lang.RuntimeException: time is more than 10 years from present: 1672527600000 [ 285s] at build.tools.generatecurrencydata.GenerateCurrencyData.makeSpecialCaseEntry(GenerateCurrencyData.java:315) [ 285s] at build.tools.generatecurrencydata.GenerateCurrencyData.buildMainAndSpecialCaseTables(GenerateCurrencyData.java:254) [ 285s] at build.tools.generatecurrencydata.GenerateCurrencyData.main(GenerateCurrencyData.java:185) [ 285s] gmake[3]: *** [Gendata.gmk:55: /home/abuild/rpmbuild/BUILD/jdk20u-jdk-20.0.1-9/build/jdk/modules/java.base/java/util/currency.data] Error 1 [ 285s] gmake[2]: *** [make/Main.gmk:147: java.base-gendata] Error 2 -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1215179] New: /run/lock no longer belongs to the "lock" group; it is now in "root"
by bugzilla_noreply＠suse.com 30 Nov '23

30 Nov '23

https://bugzilla.suse.com/show_bug.cgi?id=1215179 Bug ID: 1215179 Summary: /run/lock no longer belongs to the "lock" group; it is now in "root" Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: aarch64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: screening-team-bugs(a)suse.de Reporter: David(a)WalkerStreet.info QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Sometime in the past few weeks, the ownership of /var/lock in Tumbleweed changed from root:lock to root:root, breaking OpenHAB3's ability to create lock files within that directory, unless it's given membership in the root group by adding "SupplementaryGroups=root" in its systemd .service configuration (which isn't the best security strategy). This problem is very similar to bug #552095, which was reported nearly 14 years ago and later resolved, although in a way that doesn't apply to my use case. What this change deliberate? If not, could it be reversed? If it can't be reversed, suggestions for a workaround would be appreciated. -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1213339] New: Segmentation fault when setting up database with sqlite3 gda-control-center-6.0
by bugzilla_noreply＠suse.com 27 Nov '23

27 Nov '23

https://bugzilla.suse.com/show_bug.cgi?id=1213339 Bug ID: 1213339 Summary: Segmentation fault when setting up database with sqlite3 gda-control-center-6.0 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: vojta.kottas(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:109.0) Gecko/20100101 Firefox/115.0 Build Identifier: When setting up a sqlite database using gda-control-center-6.0 as a test in a folder (/tmp/test_db in my case), the gui crashed and the command line showed that a segmentation fault had occurred. This issue does not happen on other distros. Reproducible: Always Steps to Reproduce: 1. Run gda-control-center-6.0 2. Set up database with sqlite Actual Results: Segmentation fault Expected Results: A database is set up in the specified folder. This all came from me trying to install the Pano extension, which upon install crashed the gnome-shell. I tracked the issue to this github issue: https://github.com/oae/gnome-shell-pano/issues/178 Which further tracks the issue down to a problem with the sqlite3 package on openSUSE. -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1212958] New: evolution hogging CP?U
by bugzilla_noreply＠suse.com 27 Nov '23

27 Nov '23

https://bugzilla.suse.com/show_bug.cgi?id=1212958 Bug ID: 1212958 Summary: evolution hogging CP?U Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.4 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: X11 Applications Assignee: screening-team-bugs(a)suse.de Reporter: msuchanek(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- When evolution is open fan keeps spinning. It order of magnitude more cpu time than 3 browsers each with number of tabs open together. -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1215364] New: makedumpfile update for Linux 6.6 kernel using radix mm
by bugzilla_noreply＠suse.com 27 Nov '23

27 Nov '23

https://bugzilla.suse.com/show_bug.cgi?id=1215364 Bug ID: 1215364 Summary: makedumpfile update for Linux 6.6 kernel using radix mm Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: PowerPC-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: screening-team-bugs(a)suse.de Reporter: msuchanek(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Since commit 368a0590d954: (powerpc/book3s64/vmemmap: switch radix to use a different vmemmap handling function) makedumpfile is not compatible with kernels using radix mm. Makedumpfile should be updated when upstream implements a fix. -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1214249] New: rsync crashes when built with glibc-2.38
by bugzilla_noreply＠suse.com 23 Nov '23

23 Nov '23

https://bugzilla.suse.com/show_bug.cgi?id=1214249 Bug ID: 1214249 Summary: rsync crashes when built with glibc-2.38 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: david.anes(a)suse.com Reporter: jslaby(a)suse.com QA Contact: qa-bugs(a)suse.de CC: pmonrealgonzalez(a)suse.com, schwab(a)suse.com Target Milestone: --- Found By: --- Blocker: --- rsync crashes in vim-plugins' build: https://build.opensuse.org/package/live_build_log/editors/vim-plugins/openS… I believe it's due to glibc-2.38 update. If I update glibc to 2.38 only, rsync-3.2.7-3.1 does not crash. As soon as I update to rsync-3.2.7-3.2 (I believe the one rebuilt against this very new glibc), I see: $ rsync -FFXHav '--filter=merge global-rsync-filter' Align-37-43/ xxx sending incremental file list *** buffer overflow detected ***: terminated rsync: connection unexpectedly closed (0 bytes received so far) [Receiver] rsync error: error in rsync protocol data stream (code 12) at io.c(231) [Receiver=3.2.7] Neúspěšně ukončen (SIGABRT) (core dumped [obraz paměti uložen]) gdb says: > #3 0x00007f2a31226917 in __GI_abort () at abort.c:79 > #4 0x00007f2a312277e3 in __libc_message (fmt=fmt@entry=0x7f2a313b030c "*** %s ***: terminated\n") at ../sysdeps/posix/libc_fatal.c:150 > #5 0x00007f2a31327bdb in __GI___fortify_fail (msg=msg@entry=0x7f2a313b02f3 "buffer overflow detected") at fortify_fail.c:24 > #6 0x00007f2a31327506 in __GI___chk_fail () at chk_fail.c:28 > #7 0x00007f2a31329279 in __strlcpy_chk (s1=<optimized out>, s2=<optimized out>, n=<optimized out>, s1len=<optimized out>) at strlcpy_chk.c:28 > 27 if (__glibc_unlikely (s1len < n)) > 28 __chk_fail (); > #8 0x0000559d0acf778a in strlcpy (__n=4096, __src=0x7ffece39ae20 "xslaby/pokus/Align-37-43/", __dest=0x559d0ad61886 <dirbuf.lto_priv+6> "") > at /usr/include/bits/string_fortified.h:156 > 156 return __strlcpy_chk (__dest, __src, __n, __glibc_objsize (__dest)); How does it come __glibc_objsize(dirbuf.lto_priv+6) is less than 4096? > #9 setup_merge_file (mergelist_num=mergelist_num@entry=0, ex=ex@entry=0x559d0bf84b40, lp=lp@entry=0x559d0bf84b90) at /usr/src/debug/rsync-3.2.7/exclude.c:737 737 strlcpy(y, save, MAXPATHLEN); > #10 0x0000559d0acf7d94 in push_local_filters (dir=dir@entry=0x7ffece39c000 ".", dirlen=dirlen@entry=1) at /usr/src/debug/rsync-3.2.7/exclude.c:806 > #11 0x0000559d0acf8259 in change_local_filter_dir (dname=0x7ffece39c000 ".", dlen=1, dir_depth=0) at /usr/src/debug/rsync-3.2.7/exclude.c:899 > #12 0x0000559d0acef91c in send_file_list (f=4, argc=0, argv=0x559d0bf84898) at /usr/src/debug/rsync-3.2.7/flist.c:2453 > #13 0x0000559d0ad07d4b in client_run (f_in=f_in@entry=5, f_out=f_out@entry=4, pid=pid@entry=6659, argc=argc@entry=1, argv=argv@entry=0x559d0bf84890) > at /usr/src/debug/rsync-3.2.7/main.c:1315 > #14 0x0000559d0ace2bdb in start_client (argv=0x559d0bf84890, argc=1) at /usr/src/debug/rsync-3.2.7/main.c:1613 > #15 main (argc=<optimized out>, argv=<optimized out>) at /usr/src/debug/rsync-3.2.7/main.c:1873 -- You are receiving this mail because: You are on the CC list for the bug.

1 14

[Bug 1214845] New: libvirtError: Unable to find 'memory' cgroups controller mount
by bugzilla_noreply＠suse.com 21 Nov '23

21 Nov '23

https://bugzilla.suse.com/show_bug.cgi?id=1214845 Bug ID: 1214845 Summary: libvirtError: Unable to find 'memory' cgroups controller mount Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Virtualization:Other Assignee: virt-bugs(a)suse.de Reporter: chrisvte(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- After I updated to kernel 6.4.11-1-default, every time I booted a LXC I was getting this error: “libvirtError: internal error: Unable to find ‘memory’ cgroups controller mount” I replicated the installation in a minipc (Intel N5105) and it worked perfectly, so I did a new installation in the first computer (AMD Ryzen 5600G) and, again, I got the same error of the beginning. I tried in other two computers (AMD Ryzen 5900X and Intel i5-1135G7) and I got the same error. If I added “systemd.unified_cgroup_hierarchy=0” to the boot line, the error went away, but it was really unstable (containers stopped working after a while). I usually install the tools of virtualization through Yast (KVM Server and KVM tools). After that I install a few more packages: libvirt-client, libvirt-daemon, libvirt-daemon-lxc, libvirt-daemon-driver-lxc, system-user-libvirt-dbus. Finally, I add the user to groups libvirt, qemu and kvm. Reboot and run. The details of the error using Virt-Manager: Traceback (most recent call last): File "/usr/share/virt-manager/virtManager/asyncjob.py", line 72, in cb_wrapper callback(asyncjob, *args, **kwargs) File "/usr/share/virt-manager/virtManager/asyncjob.py", line 108, in tmpcb callback(*args, **kwargs) File "/usr/share/virt-manager/virtManager/object/libvirtobject.py", line 57, in newfn ret = fn(self, *args, **kwargs) ^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/share/virt-manager/virtManager/object/domain.py", line 1425, in startup self._backend.create() File "/usr/lib64/python3.11/site-packages/libvirt.py", line 1373, in create raise libvirtError('virDomainCreate() failed') libvirt.libvirtError: Unable to find 'memory' cgroups controller mount And using command line: # virsh -d 0 -c lxc:// start 101-PiHole start: domain(optdata): 101-PiHole start: found option <domain>: 101-PiHole start: <domain> trying as domain NAME error: Failed to start domain '101-PiHole' error: internal error: Unable to find 'memory' cgroups controller mount About the system: # mount | grep cgroup cgroup2 on /sys/fs/cgroup type cgroup2 (rw,nosuid,nodev,noexec,relatime,nsdelegate,memory_recursiveprot) # uname -a Linux 6.4.11-1-default #1 SMP PREEMPT_DYNAMIC Thu Aug 17 04:57:43 UTC 2023 (2a5b3f6) x86_64 x86_64 x86_64 GNU/Linux -- You are receiving this mail because: You are on the CC list for the bug.

1 9

[Bug 1214406] New: [kubeadm1.27] Multiple Issues before `kubeadm init` runs successfully
by bugzilla_noreply＠suse.com 21 Nov '23

21 Nov '23

https://bugzilla.suse.com/show_bug.cgi?id=1214406 Bug ID: 1214406 Summary: [kubeadm1.27] Multiple Issues before `kubeadm init` runs successfully Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: All OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Containers Assignee: priyanka.saggu(a)suse.com Reporter: eich(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: Development Blocker: --- 1. The Kubernetes package on TW seems to require cri-o as runtime dependency, however, it requires containerd. Thus, - cri-o should not be installed as a dependency - containerd had to be installed enabled and started (containerd doesn't have an rccontainerd link) 2. kubelet.service does not start: It complains about the option `--container-runtime` not being known. This option is pulled in from /etc/sysconfig/kubelet. It needs to be deleted from this file. It is not clear who has created this file and which package owns it. The rpm database does not know it. Since it is pulled in by ..../systemd/system/kubelet.service.d/10-kubeadm.conf I suspect it comes from kubernetes1.27-kubeadem but it's hard to tell where it is created - at least not in a post-install script. It would be good if the file was '%ghost' in the %files section of the package it originates from. The same is true for the environment file /var/lib/kubelet/kubeadm-flags.env which is written by `kubeadm init`. 3. 'kubeadm init' checks if the kubelet service is enabled. 4. Moreover, it requires a reboot to start all dependent services and load all required kernel modules: - br_netfilter needs to be loaded - containerd needs to be started This was fine for kubic these packages were originally meant for as this had transactional updates and required a reboot. On a 'regular' system where this is not the case, these modules should probably be loaded and services be started from a 'postinstall' script. -- You are receiving this mail because: You are on the CC list for the bug.

1 15

[Bug 1214403] New: Bluetooth stack will often choose a really poor codec (mono, audibly low bitrate) when on different distribution it was fine
by bugzilla_noreply＠suse.com 21 Nov '23

21 Nov '23

https://bugzilla.suse.com/show_bug.cgi?id=1214403 Bug ID: 1214403 Summary: Bluetooth stack will often choose a really poor codec (mono, audibly low bitrate) when on different distribution it was fine Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.5 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Sound Assignee: tiwai(a)suse.com Reporter: el(a)horse64.org QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- OpenSUSE's bluetooth and audio stack will often choose a really poor codec (mono, audibly low bitrate) with my Anker Soundcore Life Q30 headphones when on different distribution it was fine. Also, randomly shooting down pulseaudio and bluetoothd and disconnecting and reconnecting will fix it at some point, but possibly lead to other issues down the line like things no longer properly reconnecting on their own, it's a total mess. Since this worked on a different Linux distribution with the same hardware, this seems to be some sort of problem specifically with how the bluetooth and audio stack is configured on OpenSUSE and not e.g. a hardware or radio interference problem. I'm seeing this on the GNOME desktop, which I also used previously with the other distribution. Also, switching through all codec choices in pavucontrol doesn't fix it, which makes this even more annoying. -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1213608] New: "./Inkscape-0e150ed-x86_64.AppImage --appimage-mount" behaves strangely
by bugzilla_noreply＠suse.com 20 Nov '23

20 Nov '23

https://bugzilla.suse.com/show_bug.cgi?id=1213608 Bug ID: 1213608 Summary: "./Inkscape-0e150ed-x86_64.AppImage --appimage-mount" behaves strangely Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.4 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: screening-team-bugs(a)suse.de Reporter: Ulrich.Windl(a)rz.uni-regensburg.de QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Trying the new Inkscape 1.3 as appimage, I used "./Inkscape-0e150ed-x86_64.AppImage --appimage-mount" to mount the image as root, and that seems to succeed with message "/tmp/.mount_InkscaYEqRgu". However when I try to access that directory from another terminal I only get "permission denied, even for "ls -d": > ll /tmp/.mount_InkscaYEqRgu ls: cannot access '/tmp/.mount_InkscaYEqRgu': Permission denied > ll -d /tmp/.mount_InkscaYEqRgu ls: cannot access '/tmp/.mount_InkscaYEqRgu': Permission denied Oddly, the directory exists, because I can access it as root: # ll /tmp/.mount_InkscaYEqRgu insgesamt 100 -rwxr-xr-x 1 root root 3075 21. Jul 14:26 AppRun -rw-r--r-- 1 root root 40270 21. Jul 14:27 .DirIcon drwxr-xr-x 5 root root 0 26. Mai 16:05 etc drwxr-xr-x 4 root root 0 8. Jul 2021 lib drwxr-xr-x 2 root root 0 21. Jul 14:27 lib64 -rw-r--r-- 1 root root 19274 21. Jul 14:27 org.inkscape.Inkscape.desktop -rw-r--r-- 1 root root 40270 21. Jul 14:26 org.inkscape.Inkscape.png drwxr-xr-x 6 root root 0 8. Jul 2021 usr The problem seems to be this (from stace): statx(AT_FDCWD, "/tmp/.mount_InkscaYEqRgu", AT_STATX_SYNC_AS_STAT|AT_SYMLINK_NOFOLLOW, STATX_MODE|STATX_NLINK|STATX_UID|STATX_GID|STATX_MTIME|STATX_SIZE, 0x7fff110a3fb0) = -1 EACCES (Permission denied) When trying to use the appimage as non-root, it won't work either: > ./Inkscape-0e150ed-x86_64.AppImage fuse: failed to exec fusermount: Permission denied Cannot mount AppImage, please check your FUSE setup. You might still be able to extract the contents of this AppImage if you run it with the --appimage-extract option. See https://github.com/AppImage/AppImageKit/wiki/FUSE for more information open dir error: No such file or directory -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1214192] New: totem DVD source is required to play but is not installed
by bugzilla_noreply＠suse.com 20 Nov '23

20 Nov '23

https://bugzilla.suse.com/show_bug.cgi?id=1214192 Bug ID: 1214192 Summary: totem DVD source is required to play but is not installed Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.5 Hardware: x86-64 OS: openSUSE Leap 15.5 Status: NEW Severity: Normal Priority: P5 - None Component: X11 Applications Assignee: screening-team-bugs(a)suse.de Reporter: batpul(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- On 15.5 totem says it cannot play DVDs: "DVD source is required to play but is not installed" and it offers to install additional software which then fails. This is now installed: libdvdcss2-1.4.3+3-lp155.10.1.x86_64 libdvdnav4-6.1.1-bp155.2.13.x86_64 libdvdread4-6.0.0-150000.3.2.1.x86_64 libtotem-plparser-mini18-3.26.6-150400.2.9.x86_64 libtotem-plparser18-3.26.6-150400.2.9.x86_64 totem-3.38.2-150400.2.12.x86_64 totem-lang-3.38.2-150400.2.12.noarch totem-pl-parser-3.26.6-150400.2.9.x86_64 totem-pl-parser-lang-3.26.6-150400.2.9.noarch totem-plugins-3.38.2-150400.2.12.x86_64 PackageKit-gstreamer-plugin-1.2.4-150400.3.6.1.x86_64 gstreamer-1.20-plugin-openh264-1.20.3-1.sle150500.2.x86_64 gstreamer-1.22.0-150500.3.2.3.x86_64 gstreamer-lang-1.22.0-150500.3.2.3.noarch gstreamer-libnice-0.1.21-150500.1.1.x86_64 gstreamer-plugin-cluttergst3-3.0.27-150400.1.11.x86_64 gstreamer-plugin-pipewire-0.3.64-150500.1.2.x86_64 gstreamer-plugins-bad-1.22.0-lp155.2.8.x86_64 gstreamer-plugins-bad-lang-1.22.0-lp155.2.8.noarch gstreamer-plugins-base-1.22.0-150500.3.3.1.x86_64 gstreamer-plugins-base-lang-1.22.0-150500.3.3.1.noarch gstreamer-plugins-farstream-0.2.9+4-150400.1.12.x86_64 gstreamer-plugins-good-1.22.0-150500.4.3.1.x86_64 gstreamer-plugins-good-gtk-1.22.0-150500.4.3.1.x86_64 gstreamer-plugins-good-lang-1.22.0-150500.4.3.1.noarch gstreamer-plugins-libav-1.22.0-bp155.1.5.x86_64 gstreamer-plugins-rs-0.10.1+git20230213.9cd68ff-150500.2.16.x86_64 gstreamer-plugins-ugly-1.22.0-150500.3.3.1.x86_64 gstreamer-plugins-ugly-lang-1.22.0-150500.3.3.1.noarch gstreamer-utils-1.22.0-150500.3.2.3.x86_64 libgstreamer-1_0-0-1.22.0-150500.3.2.3.x86_64 -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1215482] New: polkit: permissions of /usr/share/polkit-1/rules.d
by bugzilla_noreply＠suse.com 20 Nov '23

20 Nov '23

https://bugzilla.suse.com/show_bug.cgi?id=1215482 Bug ID: 1215482 Summary: polkit: permissions of /usr/share/polkit-1/rules.d Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: meissner(a)suse.com Reporter: lnussel(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- /usr/share/polkit-1/rules.d is 0750 root:polkit. As the content comes from the OS vendor, there's nothing secret about it. So changing to 755 root:root should be fine. That would avoid having gid!=0 stuff in /usr -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1214913] New: jhead deletes EXIF data
by bugzilla_noreply＠suse.com 13 Nov '23

13 Nov '23

https://bugzilla.suse.com/show_bug.cgi?id=1214913 Bug ID: 1214913 Summary: jhead deletes EXIF data Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.5 Hardware: x86-64 OS: openSUSE Leap 15.5 Status: NEW Severity: Major Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: bob(a)vickers.simplyms.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 869225 --> https://bugzilla.suse.com/attachment.cgi?id=869225&action=edit Image before rotation jhead version 3.06.0.1-bp155.4.6 deletes EXIF data when rotating images. $ exiftool rotated.jpg | wc -l 92 $ jhead -autorot rotated.jpg Nonfatal Error : 'rotated.jpg' Command has invalid characters. $ exiftool rotated.jpg | wc -l 23 I found a report for this bug on an Debian site: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1023303 -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1213702] New: VUL-0: CVE-2023-38285: modsecurity: DoS Vulnerability in Four Transformations
by bugzilla_noreply＠suse.com 13 Nov '23

13 Nov '23

https://bugzilla.suse.com/show_bug.cgi?id=1213702 Bug ID: 1213702 Summary: VUL-0: CVE-2023-38285: modsecurity: DoS Vulnerability in Four Transformations Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.5 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Apache Assignee: apache-bugs(a)suse.de Reporter: gianluca.gabrielli(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Vulnerability Details Included in ModSecurity functionality are dozens of transformation actions which support altering the representation of values so that further processing can be done on the modified values. This may be either more convenient to work with, or less prone to rule evasion. The ModSecurity team was recently alerted to a possible DoS issue in four of these transformations in ModSecurity v3. Thanks to the reporter for the investigation and for responsibly disclosing the issue. The affected transformations are: removeWhitespace, removeNull, replaceNull, and removeCommentsChar. The affected transformations were functionally correct. However, the implemented solutions would be inefficient if a malicious user were to submit a specially crafted HTTP request that triggered worst-case performance. The most dramatic delays can typically be prevented through common configuration items such as SecRequestBodyNoFilesLimit with the default value of 131072 suggested in modsecurity.conf-recommended. However, even with this limit in place, a dozen or more executions of these transformations could result in multiple seconds of delay for a single HTTP transaction. If a large enough number of such malicious requests are running simultaneously, this could render the webserver unable to respond to legitimate requests in a timely manner. Mitigation For installations where immediate upgrade to the new version of the software is impractical, some mitigation possibilities are available. The nature of the issue results in large values causing a much greater effect on resources than numerous smaller values. A separate ModSecurity rule could be included to limit the size of each value to be processed, but still allow legitimate content to be processed unimpeded. For example, if there are many rules with the affected transformations executing against the ARGS collection, a rule such as the following could be included before other phase 2 rules: SecRule ARGS "@gt 16000" "id:1,phase:2,t:length,deny,status:403,msg:’ARG exceeds length limit'" Optionally, combined with further reducing the configured value for SecRequestBodyNoFilesLimit, potential delays precipitated by worst-case input can be significantly reduced. References https://www.trustwave.com/en-us/resources/blogs/spiderlabs-blog/modsecurity… https://github.com/SpiderLabs/ModSecurity/commit/ab5658f2d4cfa5126db256cf3f… -- You are receiving this mail because: You are on the CC list for the bug.

1 7

[Bug 1215647] New: [aarch64][LenovoX13s] Need to install DTB on ESP since NO ACPI support for Linux on X13s
by bugzilla_noreply＠suse.com 10 Nov '23

10 Nov '23

https://bugzilla.suse.com/show_bug.cgi?id=1215647 Bug ID: 1215647 Summary: [aarch64][LenovoX13s] Need to install DTB on ESP since NO ACPI support for Linux on X13s Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: aarch64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: chester.lin(a)suse.com Reporter: chester.lin(a)suse.com QA Contact: qa-bugs(a)suse.de CC: afaerber(a)suse.com, guillaume.gardet(a)arm.com, ivan.ivanov(a)suse.com, jlee(a)suse.com, mbenes(a)suse.com, mbrugger(a)suse.com Target Milestone: --- Found By: --- Blocker: --- Plan to submit a new package arm64laptop-firmware-dt in hardware:boot and then openSUSE:Factory, which installs sc8280xp-lenovo-thinkpad-x13s.dtb on ESP since the Lenovo X13s' ACPI doesn't support Linux and its UEFI FW has to preload the DTB file from ESP and then apply some runtime DT overlays before booting to grub2 and then Linux. Without preloading the DTB, the system wouldn't boot since the UEFI FW does not contain a default DTB. -- You are receiving this mail because: You are on the CC list for the bug.

1 7

[Bug 1215341] New: devel:gcc/binutils: devel subpackage should depend on zstd-devel
by bugzilla_noreply＠suse.com 09 Nov '23

09 Nov '23

https://bugzilla.suse.com/show_bug.cgi?id=1215341 Bug ID: 1215341 Summary: devel:gcc/binutils: devel subpackage should depend on zstd-devel Classification: openSUSE Product: openSUSE.org Version: unspecified Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: 3rd party software Assignee: matz(a)suse.com Reporter: stefan.bruens(a)rwth-aachen.de QA Contact: screening-team-bugs(a)suse.de CC: rguenther(a)suse.com Target Milestone: --- Found By: --- Blocker: --- As zstd compression is enabled for current distribution versions, the devel package should also pull in zstd-devel ``` %if %{suse_version} > 1500 BuildRequires: libzstd-devel %endif ``` -> ``` %package devel ... %if %{suse_version} > 1500 Requires: libzstd-devel %endif ``` -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1215699] New: drbd: fix build error against kernel v6.5.4
by bugzilla_noreply＠suse.com 08 Nov '23

08 Nov '23

https://bugzilla.suse.com/show_bug.cgi?id=1215699 Bug ID: 1215699 Summary: drbd: fix build error against kernel v6.5.4 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Major Priority: P5 - None Component: High Availability Assignee: ha-bugs(a)suse.de Reporter: heming.zhao(a)suse.com QA Contact: qa-bugs(a)suse.de CC: qa-bugs(a)suse.de, zzhou(a)suse.com Depends on: 1206791 Target Milestone: --- Found By: --- Blocker: --- some KAPIs changed and was blocking drbd building for kernel v6.4.5. create this bug for passing build drbd on v6.4.5 -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1215617] New: GNOME Software shows failed to build result for 362301da643102b9f38477387e2193e57abaa590
by bugzilla_noreply＠suse.com 06 Nov '23

06 Nov '23

https://bugzilla.suse.com/show_bug.cgi?id=1215617 Bug ID: 1215617 Summary: GNOME Software shows failed to build result for 362301da643102b9f38477387e2193e57abaa590 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: GNOME Assignee: gnome-bugs(a)suse.de Reporter: philip.raets(a)telenet.be QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- After upgrading tumbleweed 20230920, GNOME software on each login shows the following warning: failed to build result for 362301da643102b9f38477387e2193e57abaa590 according to https://github.com/fwupd/fwupd/issues/6101 it is an issue with fwupd and needs to be updated. In Tumbleweed the version of fwupd is 1.8.17. Is there an option that we can get the latest version? Thanks, Philip -- You are receiving this mail because: You are on the CC list for the bug.

1 6

[Bug 1214988] New: btrfs-cleaner hangs and: watchdog: BUG: soft lockup - CPU#8 stuck for
by bugzilla_noreply＠suse.com 06 Nov '23

06 Nov '23

https://bugzilla.suse.com/show_bug.cgi?id=1214988 Bug ID: 1214988 Summary: btrfs-cleaner hangs and: watchdog: BUG: soft lockup - CPU#8 stuck for Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.5 Hardware: x86-64 OS: openSUSE Leap 15.5 Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: screening-team-bugs(a)suse.de Reporter: diego.ercolani(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- In my system I use btrfs and sometimes I have this entry in journal: Sep 05 09:52:53 pc-diego kernel: watchdog: BUG: soft lockup - CPU#8 stuck for 26s! [btrfs-cleaner:2833] Sep 05 09:52:53 pc-diego kernel: Modules linked in: rpcsec_gss_krb5 nfsv4 dns_resolver nfs fscache netfs rfcomm tcp_diag inet_diag af_packet 8021q garp m> Sep 05 09:52:53 pc-diego kernel: platform_profile syscopyarea rfkill mdio_devres sysfillrect snd sysimgblt irqbypass video pcspkr efi_pstore(N) wmi_bmof> Sep 05 09:52:53 pc-diego kernel: Supported: No, Proprietary and Unsupported modules are loaded Sep 05 09:52:53 pc-diego kernel: CPU: 8 PID: 2833 Comm: btrfs-cleaner Tainted: P OE X N 5.14.21-150500.55.19-default #1 SLE15-SP5 a29285bac85> Sep 05 09:52:53 pc-diego kernel: Hardware name: System manufacturer System Product Name/PRIME B450M-A, BIOS 3002 03/10/2021 Sep 05 09:52:53 pc-diego kernel: RIP: 0010:generic_bin_search.constprop.31+0xc4/0x190 [btrfs] Sep 05 09:52:53 pc-diego kernel: Code: 92 52 36 e9 48 c1 ff 06 48 c1 e7 0c 48 01 f8 49 8b 7d 00 48 01 d7 81 e7 ff 0f 00 00 48 8d 3c 38 4c 89 fe e8 9e f7 > Sep 05 09:52:53 pc-diego kernel: RSP: 0018:ffffb672c8063b00 EFLAGS: 00000286 Sep 05 09:52:53 pc-diego kernel: RAX: 00000000ffffffff RBX: 0000000000000033 RCX: 000000000000006c Sep 05 09:52:53 pc-diego kernel: RDX: 00000000000009f6 RSI: ffffb672c8063bef RDI: ffff99a90581b560 Sep 05 09:52:53 pc-diego kernel: RBP: 0000000000000036 R08: ffffb672c8063b98 R09: 0000000000000000 Sep 05 09:52:53 pc-diego kernel: R10: 0000000000000001 R11: ffff99a850d23e78 R12: 0000000000000031 Sep 05 09:52:53 pc-diego kernel: R13: ffff99a850d23e00 R14: 0000000000000019 R15: ffffb672c8063bef Sep 05 09:52:53 pc-diego kernel: FS: 0000000000000000(0000) GS:ffff99b2bec00000(0000) knlGS:0000000000000000 Sep 05 09:52:53 pc-diego kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Sep 05 09:52:53 pc-diego kernel: CR2: 00007f6ae7b3c000 CR3: 0000000ba9a10000 CR4: 00000000003506e0 Sep 05 09:52:53 pc-diego kernel: Call Trace: Sep 05 09:52:53 pc-diego kernel: <TASK> Sep 05 09:52:53 pc-diego kernel: btrfs_search_slot+0x400/0x920 [btrfs 0bea397a25b504ffddb94375cf1ffcaec85fa26b] Sep 05 09:52:53 pc-diego kernel: btrfs_lookup_file_extent+0x4a/0x70 [btrfs 0bea397a25b504ffddb94375cf1ffcaec85fa26b] Sep 05 09:52:53 pc-diego kernel: btrfs_get_extent+0x141/0x870 [btrfs 0bea397a25b504ffddb94375cf1ffcaec85fa26b] Sep 05 09:52:53 pc-diego kernel: ? __x86_return_thunk+0x5/0x6 Sep 05 09:52:53 pc-diego kernel: ? lock_extent_bits+0x4a/0xa0 [btrfs 0bea397a25b504ffddb94375cf1ffcaec85fa26b] Sep 05 09:52:53 pc-diego kernel: defrag_lookup_extent+0xcf/0x120 [btrfs 0bea397a25b504ffddb94375cf1ffcaec85fa26b] Sep 05 09:52:53 pc-diego kernel: btrfs_defrag_file+0x90a/0x1230 [btrfs 0bea397a25b504ffddb94375cf1ffcaec85fa26b] Sep 05 09:52:53 pc-diego kernel: ? __x86_return_thunk+0x5/0x6 Sep 05 09:52:53 pc-diego kernel: ? __x86_return_thunk+0x5/0x6 Sep 05 09:52:53 pc-diego kernel: ? btrfs_iget_path+0x67/0x700 [btrfs 0bea397a25b504ffddb94375cf1ffcaec85fa26b] Sep 05 09:52:53 pc-diego kernel: ? btrfs_get_root_ref+0x18d/0x310 [btrfs 0bea397a25b504ffddb94375cf1ffcaec85fa26b] Sep 05 09:52:53 pc-diego kernel: ? btrfs_run_defrag_inodes+0x27c/0x360 [btrfs 0bea397a25b504ffddb94375cf1ffcaec85fa26b] Sep 05 09:52:53 pc-diego kernel: ? __x86_return_thunk+0x5/0x6 Sep 05 09:52:53 pc-diego kernel: btrfs_run_defrag_inodes+0x221/0x360 [btrfs 0bea397a25b504ffddb94375cf1ffcaec85fa26b] Sep 05 09:52:53 pc-diego kernel: cleaner_kthread+0xec/0x130 [btrfs 0bea397a25b504ffddb94375cf1ffcaec85fa26b] Sep 05 09:52:53 pc-diego kernel: ? csum_one_extent_buffer+0x110/0x110 [btrfs 0bea397a25b504ffddb94375cf1ffcaec85fa26b] Sep 05 09:52:53 pc-diego kernel: kthread+0x156/0x180 Sep 05 09:52:53 pc-diego kernel: ? set_kthread_struct+0x50/0x50 Sep 05 09:52:53 pc-diego kernel: ret_from_fork+0x22/0x30 Sep 05 09:52:53 pc-diego kernel: </TASK> I think the problem is related on some issue on a btrfs filesystem but I don't know on wich as every "btrfs scrub" finish correctly: pc-diego:~ # mount | grep btrfs /dev/mapper/raid-rootfs on / type btrfs (rw,relatime,compress=zlib:3,space_cache,subvolid=256,subvol=/@) /dev/mapper/raid-usr on /usr type btrfs (rw,relatime,compress=zstd:9,space_cache,autodefrag,subvolid=5,subvol=/) /dev/mapper/raid-usr on /usr/local type btrfs (rw,relatime,compress=zstd:9,space_cache,autodefrag,subvolid=257,subvol=/local) /dev/mapper/raid-rootfs on /root type btrfs (rw,relatime,compress=zlib:3,space_cache,subvolid=260,subvol=/@/root) /dev/mapper/raid-rootfs on /srv type btrfs (rw,relatime,compress=zlib:3,space_cache,subvolid=259,subvol=/@/srv) /dev/mapper/raid-rootfs on /var type btrfs (rw,relatime,compress=zlib:3,space_cache,subvolid=257,subvol=/@/var) /dev/mapper/raid-boot on /boot type btrfs (rw,relatime,space_cache,subvolid=5,subvol=/) /dev/sdc1 on /M2 type btrfs (rw,relatime,compress=zlib:3,ssd,space_cache,subvolid=5,subvol=/) /dev/mapper/nonraid-var_lib_systemd_coredump on /var/lib/systemd/coredump type btrfs (rw,relatime,compress=zlib:3,space_cache,subvolid=5,subvol=/) /dev/mapper/nonraid-openwrt on /opt/openwrt type btrfs (rw,relatime,compress=zlib:3,space_cache,subvolid=5,subvol=/) /dev/mapper/nonraid-OVA on /dati/OVA type btrfs (rw,relatime,compress=zlib:9,space_cache,subvolid=5,subvol=/) /dev/mapper/raid-ISO on /dati/ISO type btrfs (rw,relatime,compress=zlib:3,space_cache,autodefrag,subvolid=5,subvol=/) /dev/mapper/nonraid-akonadi_data on /home/SSISNET/diego/.local/share/akonadi type btrfs (rw,noatime,compress=zstd:9,space_cache,subvolid=5,subvol=/) /dev/mapper/nonraid-var_tmp on /var/tmp type btrfs (rw,relatime,compress=zlib:3,space_cache,subvolid=5,subvol=/) /dev/mapper/nonraid-NextCloud on /home/SSISNET/diego/Nextcloud type btrfs (rw,noatime,compress=zlib:3,space_cache,subvolid=5,subvol=/) /dev/mapper/raid-virtualmachines on /dati/virtualmachines type btrfs (rw,relatime,compress=zstd:3,space_cache,subvolid=5,subvol=/) /dev/mapper/nonraid-tmp on /tmp type btrfs (rw,relatime,compress=zlib:3,space_cache,subvolid=5,subvol=/) /dev/mapper/raid-samba on /dati/samba type btrfs (rw,relatime,compress=zlib:3,space_cache,autodefrag,subvolid=5,subvol=/) /dev/mapper/nonraid-baloo on /home/SSISNET/diego/.local/share/baloo type btrfs (rw,relatime,compress=zstd:3,space_cache,subvolid=5,subvol=/) /dev/mapper/nonraid-var_log on /var/log type btrfs (rw,relatime,compress=zstd:3,space_cache=v2,autodefrag,subvolid=5,subvol=/) /dev/mapper/nonraid-var_cache on /var/cache type btrfs (rw,relatime,compress=zstd:3,space_cache,subvolid=5,subvol=/) /dev/bcache0 on /dati/virtualmachines/nonraid/bcache type btrfs (rw,noatime,compress=zlib:3,ssd,space_cache,subvolid=5,subvol=/) the processlist is full of btrfs-cleaner but I don't know how to undestand which partition raise the problem: pc-diego:~ # ps axuww | grep btrfs-cleaner root 1049 0.0 0.0 0 0 ? S 09:46 0:00 [btrfs-cleaner] root 1104 0.0 0.0 0 0 ? S 09:46 0:00 [btrfs-cleaner] root 1251 0.0 0.0 0 0 ? S 09:46 0:00 [btrfs-cleaner] root 1554 0.0 0.0 0 0 ? S 09:46 0:00 [btrfs-cleaner] root 2178 0.0 0.0 0 0 ? S 09:46 0:00 [btrfs-cleaner] root 2283 0.0 0.0 0 0 ? S 09:46 0:00 [btrfs-cleaner] root 2371 0.0 0.0 0 0 ? S 09:46 0:00 [btrfs-cleaner] root 2479 0.0 0.0 0 0 ? S 09:46 0:00 [btrfs-cleaner] root 2538 0.0 0.0 0 0 ? S 09:46 0:00 [btrfs-cleaner] root 2638 0.0 0.0 0 0 ? S 09:46 0:00 [btrfs-cleaner] root 2696 0.0 0.0 0 0 ? S 09:46 0:00 [btrfs-cleaner] root 2756 0.0 0.0 0 0 ? S 09:46 0:00 [btrfs-cleaner] root 2779 0.0 0.0 0 0 ? S 09:46 0:00 [btrfs-cleaner] root 2797 0.0 0.0 0 0 ? S 09:46 0:00 [btrfs-cleaner] root 2815 0.0 0.0 0 0 ? S 09:46 0:00 [btrfs-cleaner] root 2833 4.0 0.0 0 0 ? S 09:46 4:09 [btrfs-cleaner] root 2852 0.0 0.0 0 0 ? S 09:46 0:00 [btrfs-cleaner] root 2901 0.0 0.0 0 0 ? S 09:46 0:00 [btrfs-cleaner] ah, by the way, qcroups are off: pc-diego:~ # snapper get-config | grep QGROUP QGROUP | pc-diego:~ # mount | grep btrfs | cut -f 3 -d " " | while read a; do btrfs qgroup show $a; done ERROR: can't list qgroups: quotas not enabled ERROR: can't list qgroups: quotas not enabled ERROR: can't list qgroups: quotas not enabled ERROR: can't list qgroups: quotas not enabled ERROR: can't list qgroups: quotas not enabled ERROR: can't list qgroups: quotas not enabled ERROR: can't list qgroups: quotas not enabled ERROR: can't list qgroups: quotas not enabled ERROR: can't list qgroups: quotas not enabled ERROR: can't list qgroups: quotas not enabled ERROR: can't list qgroups: quotas not enabled ERROR: can't list qgroups: quotas not enabled ERROR: can't list qgroups: quotas not enabled ERROR: can't list qgroups: quotas not enabled ERROR: can't list qgroups: quotas not enabled ERROR: can't list qgroups: quotas not enabled ERROR: can't list qgroups: quotas not enabled ERROR: can't list qgroups: quotas not enabled ERROR: can't list qgroups: quotas not enabled ERROR: can't list qgroups: quotas not enabled ERROR: can't list qgroups: quotas not enabled ERROR: can't list qgroups: quotas not enabled -- You are receiving this mail because: You are on the CC list for the bug.

1 10

[Bug 1215178] New: qt6-base-6.4.2-150500.3+ leads to qt6-creator hang
by bugzilla_noreply＠suse.com 01 Nov '23

01 Nov '23

https://bugzilla.suse.com/show_bug.cgi?id=1215178 Bug ID: 1215178 Summary: qt6-base-6.4.2-150500.3+ leads to qt6-creator hang Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.5 Hardware: x86-64 OS: openSUSE Leap 15.5 Status: NEW Severity: Major Priority: P5 - None Component: Maintenance Assignee: maintenance(a)opensuse.org Reporter: andrey.v.novikoff(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- With the current revision of libQt6Gui6-6.4.2-150500.3.7.4 from the official openSUSE repos, the qt6-creator-9.0.2 hangs when showing the Issues pane and consumes all memory in an infinite loop. The bug is the same as described on https://bugreports.qt.io/browse/QTCREATORBUG-28593 and connected with https://bugreports.qt.io/browse/QTBUG-109474 This is a regression in Qt6Gui cased by patch https://codereview.qt-project.org/c/qt/qtbase/+/435080 for Qt-6.5 branch. As per changelog, this patch was also applied to the qt6-base-6.4.2 from the "Updates from SUSE Linux Enterprise 15" repository (source file `0002-QTextLayout-fix-maximumWidth-for-a-text-containing-line.patch`). Thus, the problem appears now in Qt-6.4 branch including qt6-creator hang. Downgrading libQt6Gui6-6.4.2 to the original revision of libQt6Gui6-6.4.2-150500.1.14 from the Main OpenSUSE repository do resolves the issue with Qt6-creator. The problematic qt6base patch 435080 was superseded in the upstream via https://codereview.qt-project.org/c/qt/qtbase/+/453906 . Hope, this can be backported to the 6.4.2 as well. Or, the bad 435080 patch can be just removed altogether. -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1213048] New: telegram-desktop cannot start
by bugzilla_noreply＠suse.com 31 Oct '23

31 Oct '23

https://bugzilla.suse.com/show_bug.cgi?id=1213048 Bug ID: 1213048 Summary: telegram-desktop cannot start Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.5 Hardware: 64bit OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Xfce Assignee: bnc-team-xfce(a)forge.provo.novell.com Reporter: diegops(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Fresh 15.5 with XFCE. telegram-desktop 4.7.1 diego@localhost:~$ telegram-desktop Cannot connect to server socket err = No existe el fichero o el directorio Cannot connect to server request channel jack server is not running or cannot be started JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock QPainter::begin: Paint device returned engine == 0, type: 2 QWidget::render: Cannot render with an inactive painter Abortado (`core' generado) diego@localhost:~$ -- You are receiving this mail because: You are on the CC list for the bug.

1 21

[Bug 1215137] New: Firefox all tabs list issues on KDE Wayland - full list not displaying/not scrollable, cannot move tabs in list
by bugzilla_noreply＠suse.com 31 Oct '23

31 Oct '23

https://bugzilla.suse.com/show_bug.cgi?id=1215137 Bug ID: 1215137 Summary: Firefox all tabs list issues on KDE Wayland - full list not displaying/not scrollable, cannot move tabs in list Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Firefox Assignee: factory-mozilla(a)lists.opensuse.org Reporter: pallaswept(a)proton.me QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Please see https://bugzilla.mozilla.org/show_bug.cgi?id=1851503 and https://bugzilla.mozilla.org/show_bug.cgi?id=1851505 I initially files these as firefox bugs but it turns out they are specific to OpenSUSE KDE Wayland. OS KDE X11, Ubuntu 23.04 wayland, OpenSUSE IceWM are not effected. -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 1215090] New: go1.20,go1.21: Go toolchain packages missing src/cmd/vendor/github.com/google/pprof/internal/driver/html/
by bugzilla_noreply＠suse.com 31 Oct '23

31 Oct '23

https://bugzilla.suse.com/show_bug.cgi?id=1215090 Bug ID: 1215090 Summary: go1.20,go1.21: Go toolchain packages missing src/cmd/vendor/github.com/google/pprof/internal/driver /html/ Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Development Assignee: screening-team-bugs(a)suse.de Reporter: jkowalczyk(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Include the missing directory src/cmd/vendor/github.com/google/pprof/internal/driver/html/ in our go1.1x toolchain packages. This will fix failing builds with applications that directly import runtime/pprof e.g. kubeconform which failed to build with the following error: /usr/lib64/go/1.21/src/cmd/vendor/github.com/google/pprof/internal/driv er/webhtml.go:26:12: pattern html: no matching files found Upstream Go sources vendor certain tools including the pprof profiler [1]. pprof has an asset directory pprof/internal/driver/html containing only html templates used by the pprof viewer and no Go source code. Our go packaging tries to be conservative in what we include in the RPM, and with our find/glob patterns this directory has never been included in the packaging. The issue was first reported with go1.21. However, the last vendoring update was for go1.20, so we will include the fix in go1.20 packaging as well: bb917bd 2022-11-22 09:39 cmd/vendor: update vendored github.com/google/pprof for Go 1.20 release [1] https://github.com/google/pprof -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 1214640] New: Dependency issue with WebKit2GTK in patch:openSUSE-SLE-15.4-2023-3419-1.noarch
by bugzilla_noreply＠suse.com 31 Oct '23

31 Oct '23

https://bugzilla.suse.com/show_bug.cgi?id=1214640 Bug ID: 1214640 Summary: Dependency issue with WebKit2GTK in patch:openSUSE-SLE-15.4-2023-3419-1.noarch Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.4 Hardware: x86-64 OS: openSUSE Leap 15.4 Status: NEW Severity: Normal Priority: P5 - None Component: Maintenance Assignee: maintenance(a)opensuse.org Reporter: technik(a)expeedo.de QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Since 2023-08-25, you fails on my machines by a dependency issue. Output: --------------------------------------------------------------------- running daily cronjob scripts SCRIPT: opensuse.org-online_update exited with RETURNCODE = 4. SCRIPT: output (stdout && stderr) follows Problem: the installed WebKit2GTK-4.1-lang-2.38.6-150400.4.42.4.noarch requires 'WebKit2GTK-4.1 = 2.38.6', but this requirement cannot be provided not installable providers: libwebkit2gtk-4_1-0-2.36.0-150400.2.13.x86_64[download.opensuse.org-oss] libwebkit2gtk-4_1-0-2.36.3-150400.4.3.1.x86_64[repo-sle-update] libwebkit2gtk-4_1-0-2.36.4-150400.4.6.2.x86_64[repo-sle-update] libwebkit2gtk-4_1-0-2.36.5-150400.4.9.1.x86_64[repo-sle-update] libwebkit2gtk-4_1-0-2.36.7-150400.4.12.1.x86_64[repo-sle-update] libwebkit2gtk-4_1-0-2.36.8-150400.4.15.1.x86_64[repo-sle-update] libwebkit2gtk-4_1-0-2.38.2-150400.4.22.1.x86_64[repo-sle-update] libwebkit2gtk-4_1-0-2.38.3-150400.4.25.1.x86_64[repo-sle-update] libwebkit2gtk-4_1-0-2.38.5-150400.4.34.2.x86_64[repo-sle-update] libwebkit2gtk-4_1-0-2.38.6-150400.4.39.1.x86_64[repo-sle-update] Solution 1: Following actions will be done: deinstallation of WebKit2GTK-4.1-lang-2.38.6-150400.4.42.4.noarch deinstallation of WebKit2GTK-4.0-lang-2.38.6-150400.4.42.4.noarch Solution 2: do not install patch:openSUSE-SLE-15.4-2023-3419-1.noarch Solution 3: break WebKit2GTK-4.1-lang-2.38.6-150400.4.42.4.noarch by ignoring some of its dependencies Choose from above solutions by number or cancel [1/2/3/c/d/?] (c): c SCRIPT: opensuse.org-online_update ------- END OF OUTPUT A manual "zypper up" installed updates for the "injected-bundles" packages, but that didn't resolve the issue. Current package state: bender:~ # zypper se -is "webkit2" Repository-Daten werden geladen... Installierte Pakete werden gelesen... S | Name | Type | Version | Arch | Repository ---+---------------------------------+-------+----------------------+--------+------------------------------------------------------------- i | libwebkit2gtk-4_0-37 | Paket | 2.38.6-150400.4.42.4 | x86_64 | Update repository with updates from SUSE Linux Enterprise 15 i | libwebkit2gtk-4_1-0 | Paket | 2.38.6-150400.4.42.4 | x86_64 | Update repository with updates from SUSE Linux Enterprise 15 i+ | WebKit2GTK-4.0-lang | Paket | 2.38.6-150400.4.42.4 | noarch | Update repository with updates from SUSE Linux Enterprise 15 i | WebKit2GTK-4.1-lang | Paket | 2.38.6-150400.4.42.4 | noarch | Update repository with updates from SUSE Linux Enterprise 15 i | webkit2gtk-4_0-injected-bundles | Paket | 2.40.5-150400.4.45.3 | x86_64 | Update repository with updates from SUSE Linux Enterprise 15 i | webkit2gtk-4_1-injected-bundles | Paket | 2.40.5-150400.4.45.3 | x86_64 | Update repository with updates from SUSE Linux Enterprise 15 -- You are receiving this mail because: You are on the CC list for the bug.

1 8

[Bug 1214411] New: Intel HD5500 handled by i915 hangs for seconds freezing the desktop interaction
by bugzilla_noreply＠suse.com 31 Oct '23

31 Oct '23

https://bugzilla.suse.com/show_bug.cgi?id=1214411 Bug ID: 1214411 Summary: Intel HD5500 handled by i915 hangs for seconds freezing the desktop interaction Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: ilgaz(a)ilgaz.gen.tr QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 868888 --> https://bugzilla.suse.com/attachment.cgi?id=868888&action=edit dmesg with firmware_class.dyndbg=+p I noticed my GPU which is Intel HD5500 (part of i5-5200U) hangs for several seconds and resumes. I am not physically using this laptop recently and I started to notice the hangs in 6.4.x kernel. I have the following set for VM "GPU" sharing as kernel parameters. It isn't very critical ATM and I can disable them if needed. acpi_osi=! quiet security=apparmor intel_iommu=on firmware_class.dyndbg=+p i915.enable_gvt=1 kvm.ignore_msrs=1 iommu=pt i915.modeset=1 allow_unsafe_interrupts=1 i915.enable_guc=0 acpi_osi parameter is required to boot this system, already reported to Linux kernel -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1214820] New: Menu text and items missing from Okular
by bugzilla_noreply＠suse.com 31 Oct '23

31 Oct '23

https://bugzilla.suse.com/show_bug.cgi?id=1214820 Bug ID: 1214820 Summary: Menu text and items missing from Okular Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: KDE Applications Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: ilgaz(a)ilgaz.gen.tr QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 869162 --> https://bugzilla.suse.com/attachment.cgi?id=869162&action=edit Screenshot showing Okular menus Hello. I have started to see missing menu text (says No Text) and items such as "Print" on Okular's drop down menus. Operating System: openSUSE Tumbleweed 20230828 KDE Plasma Version: 5.27.7 KDE Frameworks Version: 5.109.0 Qt Version: 5.15.10 Kernel Version: 6.4.11-1-default (64-bit) Graphics Platform: Wayland Processors: 2 × Intel® Core™2 Duo CPU P7350 @ 2.00GHz Memory: 7.5 GiB of RAM Graphics Processor: NVAC Manufacturer: Apple Inc. Product Name: MacBook5,1 System Version: 1.0 locale is: LANG=en_GB.UTF-8 okular-lang is installed. I am a frequent user of Okular (daily). I can provide additoonal details&make tests. -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1215404] New: SDDM displays blank screen with 100% CPU load or corrupt screen
by bugzilla_noreply＠suse.com 31 Oct '23

31 Oct '23

https://bugzilla.suse.com/show_bug.cgi?id=1215404 Bug ID: 1215404 Summary: SDDM displays blank screen with 100% CPU load or corrupt screen Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: X11 Applications Assignee: screening-team-bugs(a)suse.de Reporter: ilgaz(a)ilgaz.gen.tr QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 869556 --> https://bugzilla.suse.com/attachment.cgi?id=869556&action=edit journalctl -b while SDDM displaying corrupt screen. I used SDDM here with my nouveau (mcp79, nv9400) for years on this Macbook 5.1 . I started seeing corrupt fonts (totally unreadable) or 100% CPU load from sddm-greeter with black screen. I am attaching output of journalctl -b taken when it was happening. -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1215487] New: add support for nsswitch.conf dropins
by bugzilla_noreply＠suse.com 31 Oct '23

31 Oct '23

https://bugzilla.suse.com/show_bug.cgi?id=1215487 Bug ID: 1215487 Summary: add support for nsswitch.conf dropins Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Enhancement Priority: P5 - None Component: Basesystem Assignee: schwab(a)suse.com Reporter: lnussel(a)suse.com QA Contact: qa-bugs(a)suse.de CC: RBrownCCB(a)opensuse.org Target Milestone: --- Found By: --- Blocker: --- nsswitch.conf is a rather monolithic file at the moment. It's not possible to extend specific entries. To modify it, one has to copy the whole file to /etc and edit it there. That doesn't fly for OS vendors that need to ship any OS files in /usr. We'd need a more flexible solution that allows to have snippets in both /etc and /usr to extend settings. Off the bat I could think of something like this: usr └── etc └── nsswitch.conf.d ├── hosts │ ├── 10-mymachines │ ├── 20-resolved │ ├── 50-files │ └── 60-dns └── passwd ├── 10-compat └── 20-systemd # head usr/etc/nsswitch.conf.d/*/* ==> usr/etc/nsswitch.conf.d/hosts/10-mymachines <== mymachines ==> usr/etc/nsswitch.conf.d/hosts/20-resolved <== resolve [!UNAVAIL=return] ==> usr/etc/nsswitch.conf.d/hosts/50-files <== files ==> usr/etc/nsswitch.conf.d/hosts/60-dns <== dns ==> usr/etc/nsswitch.conf.d/passwd/10-compat <== compat ==> usr/etc/nsswitch.conf.d/passwd/20-systemd <== systemd -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1215268] New: [TRACKERBUG][aarch64][Lenovo-X13s] Some workaround patches for the current kernel support on X13s
by bugzilla_noreply＠suse.com 31 Oct '23

31 Oct '23

https://bugzilla.suse.com/show_bug.cgi?id=1215268 Bug ID: 1215268 Summary: [TRACKERBUG][aarch64][Lenovo-X13s] Some workaround patches for the current kernel support on X13s Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: aarch64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: chester.lin(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- This is a tracer bug, which offers some information about the missing patches required by enabling openSUSE on Lenovo X13s [aarch64 laptop]. In summary, X13s needs the following reviewing patches to be backported in the current stable tree [v6.5]: Link: https://lore.kernel.org/lkml/072b3df6-09fb-98a8-2b58-41dfcabd98c0@gmail.com… This series adds basic support for the QSEECOM interface used to communicate with secure applications running in the TrustZone on certain Qualcomm devices. In addition to that, it also provides a driver for "uefisecapp", the secure application managing access to UEFI variables on such platforms. .... <snip> ..... Maximilian Luz (3): lib/ucs2_string: Add UCS-2 strscpy function firmware: qcom_scm: Add support for Qualcomm Secure Execution Environment SCM interface firmware: Add support for Qualcomm UEFI Secure Application -- You are receiving this mail because: You are on the CC list for the bug.

1 8

[Bug 1213156] New: systemd-xdg-autostart-generator cannot start several existing desktop files in Leap 15.5
by bugzilla_noreply＠suse.com 30 Oct '23

30 Oct '23

https://bugzilla.suse.com/show_bug.cgi?id=1213156 Bug ID: 1213156 Summary: systemd-xdg-autostart-generator cannot start several existing desktop files in Leap 15.5 Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.5 Hardware: Other OS: Other Status: NEW Severity: Major Priority: P5 - None Component: Basesystem Assignee: screening-team-bugs(a)suse.de Reporter: ftake(a)geeko.jp QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- This report is created in order to summarize related report caused by the same issues of systemd-xdg-autostart-generator in 15.5. systemd-xdg-autostart-generator is a mechanism to start XDG autostart (e.g., /etc/xdg/autostart) instead of desktop environments. In Leap 15.5, KDE plasma started to use this mechanism. However, due to the following problems, xdg-autostart-generator cannot start desktop files derived from Leap 15.4. Some essential services including IBus does not work in 15.5 (#1211977). * systemd-xdg-autostart-generator inappropriately ignores desktop files with X-GNOME-Autostart-Phase (#1201728) [1] * systemd-xdg-autostart-generator cannot start process that forks another process [2, 3, 4] [1] https://github.com/systemd/systemd/issues/18791 (resolved) [2] https://bugs.kde.org/show_bug.cgi?id=433299 [3] https://github.com/systemd/systemd/pull/20813 (merged) [4] https://github.com/systemd/systemd/issues/27919 (unresolved) FYI: Upstream bug tracker related xdg-autostart https://github.com/systemd/systemd/labels/xdg-autostart Some other fixes also might be necessary for 15.5 -- You are receiving this mail because: You are on the CC list for the bug.

1 18

[Bug 1215274] New: python-python-rpm-spec: DoS on carefully crafted RPM spec files
by bugzilla_noreply＠suse.com 30 Oct '23

30 Oct '23

https://bugzilla.suse.com/show_bug.cgi?id=1215274 Bug ID: 1215274 Summary: python-python-rpm-spec: DoS on carefully crafted RPM spec files Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Python Assignee: python-maintainers(a)suse.com Reporter: martin.schreiner(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 869468 --> https://bugzilla.suse.com/attachment.cgi?id=869468&action=edit patch file fixing the issue Currently, it's possible to trick replace_macros() to never return, causing a DoS to software using this library with carefully crafted spec files. The offending code in replace_macros() may be found here: https://github.com/bkircher/python-rpm-spec/blob/ef0f2daa77d49480446423abef… Upstream issue, reported by David Anes, who also contributed the patch we're submitting: https://github.com/bkircher/python-rpm-spec/issues/61 -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1215461] New: guestfs-tools unable to determine guest arch
by bugzilla_noreply＠suse.com 26 Oct '23

26 Oct '23

https://bugzilla.suse.com/show_bug.cgi?id=1215461 Bug ID: 1215461 Summary: guestfs-tools unable to determine guest arch Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.5 Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Virtualization:Tools Assignee: virt-bugs(a)suse.de Reporter: seroton10(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 869581 --> https://bugzilla.suse.com/attachment.cgi?id=869581&action=edit Debugging output from running the failing virt-sysprep command I use the virt-sysprep command to prepare OS image files (qemu2 format) for use as KVM images. One preparation task is to define the salt minion name, by adding the argument --run-command 'echo -e "# vi:filetype=yaml\nid: $MINION_ID" >/etc/salt/minion.d/id.conf' to the virt-sysprep command. When running the virt-sysprep command, I get the following error: virt-sysprep: error: host cpu (x86_64) and guest arch (unknown) are not compatible, so you cannot use command line options that involve running commands in the guest. Use --firstboot scripts instead. If reporting bugs, run virt-sysprep with debugging enabled and include the complete output: virt-sysprep -v -x [...] However, it used to work flawlessly until recently, so some sort of regression has occurred. I guess the problem is that virt-sysprep is no longer able to identify the architecture of the guest OS in the image file. The image contains a standard Leap 15.5 server installation for amd64, the same arch as the host system. Unfortunately, I can't pinpoint exactly when this issue started occurring, but I last used the tool successfully on 2023-09-01. -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 1215486] New: qemu 8.1, missing pipewire backend packet
by bugzilla_noreply＠suse.com 25 Oct '23

25 Oct '23

https://bugzilla.suse.com/show_bug.cgi?id=1215486 Bug ID: 1215486 Summary: qemu 8.1, missing pipewire backend packet Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: epistemepromeneur(a)free.fr QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- There is a new feature with QEMU 8.1. Now there is a pipewire backend. We can invoke pipewire with -audiodev pipewire,id= but you don't supply any qemu-audio-pipewire packet with QEMU 8.1 -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1215374] New: Improve the error message in Dolphin's Share page
by bugzilla_noreply＠suse.com 22 Oct '23

22 Oct '23

https://bugzilla.suse.com/show_bug.cgi?id=1215374 Bug ID: 1215374 Summary: Improve the error message in Dolphin's Share page Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Enhancement Priority: P5 - None Component: KDE Applications Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: unblended_icing552(a)simplelogin.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 869528 --> https://bugzilla.suse.com/attachment.cgi?id=869528&action=edit Dolphin usershares broken out of the box Dolphin's samba usershares integration does not work out of the box: ``` This folder can't be shared because '/var/lib/samba/usershares' does not exist. This error is caused by your distribution not setting up Samba sharing properly. You can fix it yourself by creating that folder manually. Then close and re-open this window. ``` This is misleading and users would probably look up the internet for workarounds or hacks (that are likely not even written for openSUSE), when in fact it can be enabled graphically in YaST2 -> Samba Server -> Allow Users to Share their Directories. The error message should be changed to reflect the existence of YaST2 and better yet, add a button to directly open YaST2 Samba Server. -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1215089] New: [Suggestion] Add usbmuxd package to the install image
by bugzilla_noreply＠suse.com 19 Oct '23

19 Oct '23

https://bugzilla.suse.com/show_bug.cgi?id=1215089 Bug ID: 1215089 Summary: [Suggestion] Add usbmuxd package to the install image Classification: openSUSE Product: openSUSE Aeon Version: Current Hardware: iPhone OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Installation Assignee: rbrown(a)suse.com Reporter: dfloch4list(a)wanadoo.fr QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:109.0) Gecko/20100101 Firefox/117.0 Build Identifier: On a Macbook Air 6.1, packman repo is needed to install broadcom-wl and broadcom-wl-kmp-default packages to manage the wifi card. In case of no wired internet available, the addition of usbmuxd package from the actual installer allow to use an iPhone in thetering mode to make this additions on line. Add Reproducible: Always Steps to Reproduce: 1.Install Aeon via current micros os image 2.Try to share connection from an iPhone (ios 15.7) connected via usb Actual Results: No connection available Expected Results: Use the iPhone connection for internet access -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1213467] New: Google Earth flatpak Non-Responsive
by bugzilla_noreply＠suse.com 19 Oct '23

19 Oct '23

https://bugzilla.suse.com/show_bug.cgi?id=1213467 Bug ID: 1213467 Summary: Google Earth flatpak Non-Responsive Classification: openSUSE Product: openSUSE Aeon Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Flatpak Assignee: rbrown(a)suse.com Reporter: jiwjrbus(a)fastmail.fm QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Google Earth flatpak, on both Aeon and TW, is not responsive when I click on the desktop icon. Supporting Info: This app works perfectly on Debian, Ubuntu, and Fedora. -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1215184] New: Add the XWayland Video Bridge package to support
by bugzilla_noreply＠suse.com 19 Oct '23

19 Oct '23

https://bugzilla.suse.com/show_bug.cgi?id=1215184 Bug ID: 1215184 Summary: Add the XWayland Video Bridge package to support Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Maintenance Assignee: screening-team-bugs(a)suse.de Reporter: pascal.german(a)yandex.ru QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- In Fedora's repositories, the XWayland VideoBridge package has already been added and it is fully used. Please add it to the main turnip for openSUSE Tumbleweed. Link to the package itself: https://invent.kde.org/system/xwaylandvideobridge -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1215821] New: Cinnamon stack is in an inconsistent state again + may want to add cjs version constraint
by bugzilla_noreply＠suse.com 19 Oct '23

19 Oct '23

https://bugzilla.suse.com/show_bug.cgi?id=1215821 Bug ID: 1215821 Summary: Cinnamon stack is in an inconsistent state again + may want to add cjs version constraint Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: X11 Applications Assignee: screening-team-bugs(a)suse.de Reporter: grasland(a)lal.in2p3.fr QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Starting yesterday and as of today (2023-09-29), the main Tumbleweed repos contain an inconsistent copy of the Cinnamon stack, with some packages at a newer version than others. This will lead to the following zypper errors: --- 4 Problems: Problem: the installed cinnamon-5.2.7-2.7.x86_64 requires 'libmuffin-clutter-0.so()(64bit)', but this requirement cannot be provided Problem: the installed cinnamon-5.2.7-2.7.x86_64 requires 'typelib(Meta) = Muffin.0', but this requirement cannot be provided Problem: the installed cinnamon-5.2.7-2.7.x86_64 requires 'libmuffin-clutter-0.so()(64bit)', but this requirement cannot be provided Problem: the installed cinnamon-metatheme-numix-3.0-1.14.noarch requires 'cinnamon >= 3.0', but this requirement cannot be provided Problem: the installed cinnamon-5.2.7-2.7.x86_64 requires 'libmuffin-clutter-0.so()(64bit)', but this requirement cannot be provided deleted providers: muffin-5.2.1-1.2.x86_64 Solution 1: Following actions will be done: deinstallation of cinnamon-5.2.7-2.7.x86_64 deinstallation of cinnamon-session-5.2.0-2.8.x86_64 deinstallation of cinnamon-session-lang-5.8.2-1.1.noarch deinstallation of patterns-cinnamon-cinnamon-202021205-2.8.x86_64 Solution 2: keep obsolete muffin-5.2.1-1.2.x86_64 Solution 3: break cinnamon-5.2.7-2.7.x86_64 by ignoring some of its dependencies Choose from above solutions by number or skip, retry or cancel [1/2/3/s/r/c/d/?] (c): 2 Problem: the installed cinnamon-5.2.7-2.7.x86_64 requires 'typelib(Meta) = Muffin.0', but this requirement cannot be provided deleted providers: typelib-1_0-Muffin-0_0-5.2.1-1.2.x86_64 Solution 1: Following actions will be done: deinstallation of patterns-cinnamon-cinnamon_basis-202021205-2.8.x86_64 deinstallation of cinnamon-session-5.2.0-2.8.x86_64 deinstallation of cinnamon-session-lang-5.8.2-1.1.noarch deinstallation of patterns-cinnamon-cinnamon-202021205-2.8.x86_64 Solution 2: keep obsolete typelib-1_0-Muffin-0_0-5.2.1-1.2.x86_64 Solution 3: break cinnamon-5.2.7-2.7.x86_64 by ignoring some of its dependencies Choose from above solutions by number or skip, retry or cancel [1/2/3/s/r/c/d/?] (c): 2 Problem: the installed cinnamon-5.2.7-2.7.x86_64 requires 'libmuffin-clutter-0.so()(64bit)', but this requirement cannot be provided deleted providers: muffin-5.2.1-1.2.x86_64 Solution 1: Following actions will be done: deinstallation of cinnamon-lang-5.8.2-1.1.noarch deinstallation of cinnamon-session-5.2.0-2.8.x86_64 deinstallation of cinnamon-session-lang-5.8.2-1.1.noarch deinstallation of patterns-cinnamon-cinnamon-202021205-2.8.x86_64 Solution 2: deinstallation of muffin-lang-5.2.1-1.2.noarch Solution 3: keep obsolete muffin-lang-5.2.1-1.2.noarch Solution 4: break cinnamon-5.2.7-2.7.x86_64 by ignoring some of its dependencies Choose from above solutions by number or skip, retry or cancel [1/2/3/4/s/r/c/d/?] (c): 3 Problem: the installed cinnamon-metatheme-numix-3.0-1.14.noarch requires 'cinnamon >= 3.0', but this requirement cannot be provided Solution 1: Following actions will be done: deinstallation of cinnamon-metatheme-numix-3.0-1.14.noarch deinstallation of cinnamon-session-5.2.0-2.8.x86_64 deinstallation of cinnamon-session-lang-5.8.2-1.1.noarch deinstallation of patterns-cinnamon-cinnamon-202021205-2.8.x86_64 Solution 2: keep obsolete libmuffin0-5.2.1-1.2.x86_64 Solution 3: break cinnamon-metatheme-numix-3.0-1.14.noarch by ignoring some of its dependencies Choose from above solutions by number or skip, retry or cancel [1/2/3/s/r/c/d/?] (c): 2 --- By itself, while not a great UX, this is viable as a transitional repository state: one should be able to just postpone the Cinnamon upgrade through the process outlined above, while waiting for all packages to be upgraded. What is not good at all, however, is that after doing so, zypper will offer to install a cjs upgrade which is incompatible with the currently installed version of Cinnamon: --- Resolving dependencies... Computing distribution upgrade... The following 4 items are locked and will not be changed by any action: Installed: libmuffin0 5.2.1-1.2 x86_64 @System openSUSE muffin 5.2.1-1.2 x86_64 @System openSUSE muffin-lang 5.2.1-1.2 noarch @System openSUSE typelib-1_0-Muffin-0_0 5.2.1-1.2 x86_64 @System openSUSE The following 3 packages are going to be upgraded: cjs 5.0.0-1.15 -> 5.8.0-1.1 x86_64 openSUSE:Tumbleweed openSUSE libcjs0 5.0.0-1.15 -> 5.8.0-1.1 x86_64 openSUSE:Tumbleweed openSUSE typelib-1_0-CjsPrivate-1_0 5.0.0-1.15 -> 5.8.0-1.1 x86_64 openSUSE:Tumbleweed openSUSE The following NEW package is going to be installed: libmozjs-102-0 102.15.1-1.1 x86_64 openSUSE:Tumbleweed openSUSE 3 packages to upgrade, 1 new. Overall download size: 4.8 MiB. Already cached: 0 B. After the operation, additional 14.0 MiB will be used. Continue? [y/n/v/...? shows all options] (y): --- This should probably be fixed by adding an appropriate dependency version constraint on the cjs packages to the cinnamon package so that the cjs upgrade is not proposed in absence of compatible Cinnamon versions. -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1215436] New: Unable to boot kernels 6.5.2 or 6.5.3 unless acpi=noirq specified
by bugzilla_noreply＠suse.com 17 Oct '23

17 Oct '23

https://bugzilla.suse.com/show_bug.cgi?id=1215436 Bug ID: 1215436 Summary: Unable to boot kernels 6.5.2 or 6.5.3 unless acpi=noirq specified Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: openSUSE Tumbleweed Status: NEW Severity: Major Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: stuart(a)stella-maris.org.uk QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 869567 --> https://bugzilla.suse.com/attachment.cgi?id=869567&action=edit dmidecode and journal output On doing a zypper dup the other day it installed kernel 6.5.2 and immediately the system failed to boot, the grub menu appeared and when the timeout expired the display went black for a while and the system then rebooted to the grub menu again. I was able to switch back to kernel 6.4.12 and my system booted normally as it has done for months on kernel 6.4.x. After trying nomodeset to no avail I tried acpi=noirq on the grub linux command and my system would the boot OK. I also tried acpi_enforce_resources=lax but again the system failed to boot.So I'm left having to run with acpi=noirq to get a working system. The CPU is an AMD Ryzen 5 3400G with Radeon Vega Graphics on an MSI B450-A PRO MAX motherboard with the latest available BIOS from July 2023. I have run dmidecode and journal -b and captured the data which is appended here. -- You are receiving this mail because: You are on the CC list for the bug.

1 33

[Bug 1215775] New: Paraview fails to start due to symbol lookup error
by bugzilla_noreply＠suse.com 16 Oct '23

16 Oct '23

https://bugzilla.suse.com/show_bug.cgi?id=1215775 Bug ID: 1215775 Summary: Paraview fails to start due to symbol lookup error Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: X11 Applications Assignee: screening-team-bugs(a)suse.de Reporter: andrea_iob(a)hotmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- When trying to start Paraview on TW 20230922 I get the following error: paraview: symbol lookup error: /lib64/libvtkRemotingServerManager-pv5.11.so.1: undefined symbol: _ZN6google8protobuf8internal17AssignDescriptorsEPFPKNS1_15DescriptorTableEvEPN4absl12lts_202301259once_flagERKNS0_8MetadataE -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1214968] New: system poweroff or restart shows the text message Failed unmounting /etc
by bugzilla_noreply＠suse.com 16 Oct '23

16 Oct '23

https://bugzilla.suse.com/show_bug.cgi?id=1214968 Bug ID: 1214968 Summary: system poweroff or restart shows the text message Failed unmounting /etc Classification: openSUSE Product: openSUSE Kalpa Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Base Assignee: sfalken(a)cloverleaf-linux.org Reporter: karlggest(a)yahoo.es QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:109.0) Gecko/20100101 Firefox/116.0 Build Identifier: Every time I halt or reboot the system red text message appears showing Failed unmounting /etc System halt or reboot normally. No effect I could see. Reproducible: Always Steps to Reproduce: 1.Press shutdown and reboot 2.Graphical sessions finish, text messages appears 3.Message Failed unmounting /etc appears Actual Results: Error message appears. Shutdown or restart continues normally. Expected Results: No error message appears -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1215160] New: "wipe" reports negative percentage in progress info for large target device
by bugzilla_noreply＠suse.com 16 Oct '23

16 Oct '23

https://bugzilla.suse.com/show_bug.cgi?id=1215160 Bug ID: 1215160 Summary: "wipe" reports negative percentage in progress info for large target device Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.5 Hardware: x86-64 OS: openSUSE Leap 15.5 Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: screening-team-bugs(a)suse.de Reporter: jo4su(a)mqzmail.eu QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:109.0) Gecko/20100101 Firefox/115.0 Build Identifier: Running "wipe" on a 1.81 TiB disk, it shows negative percentages after moving on from "0%". This suggests that the calculations for the progress information are made with an unsuitable numeric type, overflows are not detected and wipe is not ready for large files and devices. Furthermore, running to "-5%" and then checking how much data of the 1.81 was overwritten, shows that it's not just a flipped sign as the absolute value moves faster than expected, completing a percentage point equivalent to 18.4 GiB in a few seconds even though the target device's write speed in only about 110 MiB/s at best. Reproducible: Always Steps to Reproduce: 1. create or select large file or device that can be overwritten and deleted for testing (my tests: 1995527224832 bytes and 2000395780096 bytes) 2. run "wipe" on the file (I added -D to keep the file for inspection) 3. observe progress information for a minute 4. ctrl-c at -7% 5. repeat wipe with "-z" 6. ctrl-c at -5% 7. run "hexdump -C myfileordevice | head" to see how much data was zeroed Actual Results: /dev/bcache2: -2% Only 10.1 GiB, i.e. 0.5% of the 1.81 TiB device, were zeroed when "-5%" was displayed by "wipe". Expected Results: Percentage in range 0 to 100. For the 1.81 TiB device, between 83.4 GiB (4.5%) and 111.2 GiB (6%) should be zeroed if the displayed percentage just has the wrong sign. Likely, wipe cannot handle modern day file and device sizes properly as indicated by open issues on https://sourceforge.net/p/wipe/bugs/ and https://bugzilla.opensuse.org/show_bug.cgi?id=1117493 -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1215620] New: Gecko rolling edition types ümlaut"and doesn´t space following letter with space bar instead of quote
by bugzilla_noreply＠suse.com 16 Oct '23

16 Oct '23

https://bugzilla.suse.com/show_bug.cgi?id=1215620 Bug ID: 1215620 Summary: Gecko rolling edition types ümlaut"and doesn´t space following letter with space bar instead of quote Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Usability Assignee: screening-team-bugs(a)suse.de Reporter: non.space.1(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Folks: Iǘe had this posted on the Gecko Github site for some time, but problem persists in my Gecko Rolling MATE install as shown in the title, typing a quotation makes it an ümlaut"and then after the second quote, hitting space bar turns the second umlaut into a quote hash, but doesn´t add the space, as I have demonstrated in subject line and again in the body of the text. Problem has been going on for at least a month, doesn´t get resolved with upgrades . . . . I have a straight TW install, and a Leap 15.6 install on this same machine w/o this issue. Only the Gecko install seems to have the problem. Machine is ´12 Mac Pro . . . I have a newer ´20 linux laptop with a Gecko Plasma install, no problems with it. https://github.com/geckolinux/geckolinux-project/issues/518 -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1213187] New: External microphone does not work on Acer Swift SF514-52T even with snd-hda-intel model=alc255-acer
by bugzilla_noreply＠suse.com 13 Oct '23

13 Oct '23

https://bugzilla.suse.com/show_bug.cgi?id=1213187 Bug ID: 1213187 Summary: External microphone does not work on Acer Swift SF514-52T even with snd-hda-intel model=alc255-acer Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: 64bit OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Sound Assignee: tiwai(a)suse.com Reporter: 95kreaninw95(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- According to aplay -l, my device has “card 0: PCH [HDA Intel PCH], device 0: ALC255 Analog [ALC255 Analog]” as one of the playback hardware devices. By default, the external mic won't show up as an input device at all when plugged. I have to add "options snd-hda-intel model=alc255-acer" to /etc/modprobe.d/alsa-base.conf or /etc/modprobe.d/snd-hda-intel.conf. After adding "options snd-hda-intel model=alc255-acer", then reboot, my external mic shows up correctly. But it only picks up noise. I tried adding "options snd-hda-intel model=alc255-acer,dell-headset-multi", which proved to be working for some users who have the same ALC255 on Acer (https://www.reddit.com/r/openSUSE/comments/yseu43/sound_problems/), but this also doesn't work for me. I updated my Tumbleweed to the latest snapshot. -- You are receiving this mail because: You are on the CC list for the bug.

1 70

[Bug 1215556] New: [Build 20230920] gnome-control-center: Add User button not showing
by bugzilla_noreply＠suse.com 12 Oct '23

12 Oct '23

https://bugzilla.suse.com/show_bug.cgi?id=1215556 Bug ID: 1215556 Summary: [Build 20230920] gnome-control-center: Add User button not showing Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other URL: https://openqa.opensuse.org/tests/3592012/modules/chan ge_password/steps/15 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: GNOME Assignee: gnome-bugs(a)suse.de Reporter: dimstar(a)opensuse.org QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: openQA Blocker: Yes ## Observation Test runs g-c-c, unlocks the interface, but we still do not see the 'Add User' button. openQA test in scenario opensuse-Tumbleweed-DVD-x86_64-desktopapps-gnome@64bit fails in [change_password](https://openqa.opensuse.org/tests/3592012/modules/change_p… ## Test suite description ## Reproducible Fails since (at least) Build [20230920](https://openqa.opensuse.org/tests/3591088) ## Expected result Last good: [20230917](https://openqa.opensuse.org/tests/3589533) (or more recent) ## Further details Always latest result in this scenario: [latest](https://openqa.opensuse.org/tests/latest?arch=x86_64&distri=opensus… -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1214834] New: [Build 20230830] tvm failed to rebuild against libSpriv 2023.4
by bugzilla_noreply＠suse.com 12 Oct '23

12 Oct '23

https://bugzilla.suse.com/show_bug.cgi?id=1214834 Bug ID: 1214834 Summary: [Build 20230830] tvm failed to rebuild against libSpriv 2023.4 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other URL: https://openqa.opensuse.org/tests/3538969/modules/tvm/ steps/18 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: OpenStack Assignee: cloud-bugs(a)suse.de Reporter: dimstar(a)opensuse.org QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: openQA Blocker: Yes ## Observation https://build.opensuse.org/package/live_build_log/openSUSE:Factory/tvm/stan… [ 1209s] + /usr/bin/python3.9 setup.py build '--executable=/usr/bin/python3.9 -s' [ 1211s] [ 1211s] Error compiling Cython file: [ 1211s] ------------------------------------------------------------ [ 1211s] ... [ 1211s] if self.c_is_view != 0: [ 1211s] raise ValueError("to_dlpack do not work with memory views") [ 1211s] with nogil: [ 1211s] c_api_ret_code = TVMArrayToDLPack(self.chandle, &dltensor) [ 1211s] CHECK_CALL(c_api_ret_code) [ 1211s] return pycapsule.PyCapsule_New(dltensor, _c_str_dltensor, _c_dlpack_deleter) [ 1211s] ^ [ 1211s] ------------------------------------------------------------ [ 1211s] [ 1211s] tvm/_ffi/_cython/./ndarray.pxi:116:66: Cannot assign type 'void (object) except *' to 'PyCapsule_Destructor' [ 1211s] Compiling tvm/_ffi/_cython/core.pyx because it changed. [ 1211s] [1/1] Cythonizing tvm/_ffi/_cython/core.pyx [ 1211s] Traceback (most recent call last): [ 1211s] File "/home/abuild/rpmbuild/BUILD/tvm-0.11.0/python/setup.py", line 238, in <module> [ 1211s] ext_modules=config_cython(), [ 1211s] File "/home/abuild/rpmbuild/BUILD/tvm-0.11.0/python/setup.py", line 154, in config_cython [ 1211s] return cythonize(ret, compiler_directives={"language_level": 3}) [ 1211s] File "/usr/lib64/python3.9/site-packages/Cython/Build/Dependencies.py", line 1134, in cythonize [ 1211s] cythonize_one(*args) [ 1211s] File "/usr/lib64/python3.9/site-packages/Cython/Build/Dependencies.py", line 1301, in cythonize_one [ 1211s] raise CompileError(None, pyx_file) [ 1211s] Cython.Compiler.Errors.CompileError: tvm/_ffi/_cython/core.pyx [ 1211s] error: Bad exit status from /var/tmp/rpm-tmp.rVxERl (%build) [ 1211s] [ 1211s] RPM build errors: openQA test in scenario opensuse-Tumbleweed-DVD-x86_64-extra_tests_ai_ml@64bit fails in [tvm](https://openqa.opensuse.org/tests/3538969/modules/tvm/steps/18) ## Test suite description Test AI/ML software ## Reproducible Fails since (at least) Build [20230830](https://openqa.opensuse.org/tests/3538569) ## Expected result Last good: [20230828](https://openqa.opensuse.org/tests/3533967) (or more recent) ## Further details Always latest result in this scenario: [latest](https://openqa.opensuse.org/tests/latest?arch=x86_64&distri=opensus… -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1215078] New: debhelper: Initialization of state variables in list context currently forbidden
by bugzilla_noreply＠suse.com 12 Oct '23

12 Oct '23

https://bugzilla.suse.com/show_bug.cgi?id=1215078 Bug ID: 1215078 Summary: debhelper: Initialization of state variables in list context currently forbidden Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.5 Hardware: x86-64 OS: openSUSE Leap 15.5 Status: NEW Severity: Normal Priority: P5 - None Component: Development Assignee: screening-team-bugs(a)suse.de Reporter: t.lee.davidson(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Executing `dh`, and other commands, from the debhelper package produces the following, or similar, error: Initialization of state variables in list context currently forbidden at /usr/lib/perl5/vendor_perl/5.26.1/Debian/Debhelper/Dh_Lib.pm line 2100, near ");" BEGIN not safe after errors--compilation aborted at /usr/lib/perl5/vendor_perl/5.26.1/Debian/Debhelper/Dh_Lib.pm line 2885. Compilation failed in require at /usr/bin/dh line 15. BEGIN failed--compilation aborted at /usr/bin/dh line 15. https://bugzilla.opensuse.org/show_bug.cgi?id=1198346 indirectly touches on this issue but does not identify the root cause, ie. an issue with the debhelper package. As far as I know, Perl >= 5.28 is required to be able to initialize state variables in list context. -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1214409] New: bluetooth file transfer not working
by bugzilla_noreply＠suse.com 12 Oct '23

12 Oct '23

https://bugzilla.suse.com/show_bug.cgi?id=1214409 Bug ID: 1214409 Summary: bluetooth file transfer not working Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.5 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: KDE Workspace (Plasma) Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: comes(a)naic.edu QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- In Leap 15.4 I'm able to transfer files via bluetooth from my android phone to the plasma desktop. In Leap 15.5 it is not possible. After some investigation I found two different causes for such failure. 1) In order to transfer files to the desktop, the obexd daemon must be running. In Leap 15.4 such program was part of the bluez rpm. In Leap 15.5 obexd is part of the bluez-obexd rpm but such package is not installed during the plasma installation. I guess the fix should be that the package bluedevil5 should require bluez-obexd. This is a plasma bug I think. 2) Once bluez-obexd is installed, the file transfer via bluetooth still doesn't work. And that's because the obexd daemon is not running. It is supposed to be started by systemd but it is not. After I run manually /usr/lib/bluetooth/obexd then the file transfer via bluetooth to the plasma desktop works. This is either a bluez bug (incorrect systemd configuration) or a systemd bug. -- You are receiving this mail because: You are on the CC list for the bug.

1 10