January 2023 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1199941] New: kmozillahelper uses up all X clients given enough logout/login cycles
by bugzilla_noreply＠suse.com 04 Jan '23

04 Jan '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1199941 Bug ID: 1199941 Summary: kmozillahelper uses up all X clients given enough logout/login cycles Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.4 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Firefox Assignee: factory-mozilla(a)lists.opensuse.org Reporter: marix(a)marix.org QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- A couple days ago I ran into the issue of applications no longer starting reliably on my openSUSE Leap 15.4 system. Launching applications like "glxinfo" or "xlsclients" would fail with the error message `Maximum number of clients reached: unable to open display ":0"`. In searching for the error message I came across https://unix.stackexchange.com/questions/250920/debugging-maximum-number-of…. Using the method described there to get the application using up the most x client connections, I found that kmozillahelper was using up more than 170 of them. Closing Firefox and one `killall kmozillahelper` later I could reliably start applications again. While my immediate problem is gone, it seems that there seems to be a leak of kmozillahelper process instances when restoring a KDE session after having logged out with an open Firefox. I.e., on third login after the killall, a `ps aux | grep kmozillahelper` will produce the following: marix 5109 0.0 0.1 413872 44192 ? Sl 11:10 0:00 /usr/lib/mozilla/kmozillahelper -session 10ca646469000165348143300000027740024_1653489712_189016 marix 5144 0.0 0.1 413872 44184 ? Sl 11:10 0:00 /usr/lib/mozilla/kmozillahelper -session 10ca646469000165348930800000285810021_1653489712_189016 marix 6070 0.2 0.1 416140 46532 ? Sl 11:10 0:00 /usr/lib/mozilla/kmozillahelper Stopping Firefox will kill the process that does not have a -session argument. However, if I logout without closing Firefox first, the next login will show four kmozillahelper processes of which three have a with -session. The two already existing in the current session, and a third one with a new sessionid. As the session-id-less process instance is properly cleaned up if Firefox is closed during a session, the problem can be worked around by closing Firefox before logging out. However, this kind of contradicts the point of having resumable sessions. -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1206684] Segmentation fault with zypper-1.14.58-1.2.aarch64
by bugzilla_noreply＠suse.com 04 Jan '23

04 Jan '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1206684 Guillaume GARDET <guillaume.gardet(a)arm.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Component|libzypp |Development Assignee|zypp-maintainers(a)suse.de |screening-team-bugs(a)suse.de -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1206684] Segmentation fault with zypper-1.14.58-1.2.aarch64
by bugzilla_noreply＠suse.com 04 Jan '23

04 Jan '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1206684 http://bugzilla.opensuse.org/show_bug.cgi?id=1206684#c7 Guillaume GARDET <guillaume.gardet(a)arm.com> changed: What |Removed |Added ---------------------------------------------------------------------------- See Also| |https://gcc.gnu.org/bugzill | |a/show_bug.cgi?id=107678 --- Comment #7 from Guillaume GARDET <guillaume.gardet(a)arm.com> --- Upstream bug is https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107678 V2 of patches is: https://gcc.gnu.org/pipermail/gcc-patches/2023-January/609356.html -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1206674] No network (wicked) after 23-12-2022 updates
by bugzilla_noreply＠suse.com 04 Jan '23

04 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1206674 https://bugzilla.suse.com/show_bug.cgi?id=1206674#c4 --- Comment #4 from Alessandro Sturniolo <alessandro.sturniolo(a)gmail.com> --- (In reply to Andrei Borzenkov from comment #3) > (In reply to Alessandro Sturniolo from comment #0) > > > > Today (23-12-2022) I have updated my system, and after reboot (there was a > > new kernel version), network no longer worked. > > > > You updated from what snapshot exactly? What was the previous version of > wicked? What packages were updated? I don't know. I do a zypper dup, almost once a week. From the logs, on 23-12-2022 I've updated following packages: CoreFreq-1.93.1-41.5.x86_64 CoreFreq-1.93.1-41.6.x86_64 CoreFreq-kmp-default-1.92.4_k6.0.10_1-39.2.x86_64 CoreFreq-kmp-default-1.93.1_k6.0.12_1-41.5.x86_64 CoreFreq-kmp-default-1.93.1_k6.0.12_1-41.6.x86_64 MozillaFirefox-107.0.1-1.1.x86_64 MozillaFirefox-108.0.1-1.1.x86_64 avahi-0.8-21.1.x86_64 avahi-0.8-22.1.x86_64 cairomm1_0-devel-1.12.2-3.22.x86_64 cairomm1_0-devel-1.12.2-4.1.x86_64 chromium-108.0.5359.124-1.1.x86_64 chromium-108.0.5359.124-2.1.x86_64 colord-1.4.6-204.13.x86_64 colord-1.4.6-204.14.x86_64 colord-color-profiles-1.4.6-204.13.x86_64 colord-color-profiles-1.4.6-204.14.x86_64 cpp13-13.0.0+git197351-1.1.x86_64 cpp13-13.0.0+git197351-2.1.x86_64 dxvk-1.10.2-74.243.x86_64 dxvk-1.10.2-74.244.x86_64 dxvk-32bit-1.10.2-74.243.x86_64 dxvk-32bit-1.10.2-74.245.x86_64 enchant-1-backends-1.6.1-5.15.x86_64 enchant-1-backends-1.6.1-6.1.x86_64 ethtool-6.0-1.1.x86_64 ethtool-6.1-1.1.x86_64 gcc13-13.0.0+git197351-1.1.x86_64 gcc13-13.0.0+git197351-2.1.x86_64 gcc13-32bit-13.0.0+git197351-1.1.x86_64 gcc13-32bit-13.0.0+git197351-2.1.x86_64 gcc13-fortran-13.0.0+git197351-1.1.x86_64 gcc13-fortran-13.0.0+git197351-2.1.x86_64 gcc13-fortran-32bit-13.0.0+git197351-1.1.x86_64 gcc13-fortran-32bit-13.0.0+git197351-2.1.x86_64 gcc13-locale-13.0.0+git197351-1.1.x86_64 gcc13-locale-13.0.0+git197351-2.1.x86_64 gdk-pixbuf-loader-libopenraw-0.3.1-54.105.x86_64 gdk-pixbuf-loader-libopenraw-0.3.1-54.106.x86_64 gio-branding-openSUSE-42.1-18.1.noarch gio-branding-openSUSE-42.1-19.1.noarch glibc-2.36-8.1.x86_64 glibc-2.36-9.1.x86_64 glibc-32bit-2.36-8.1.x86_64 glibc-32bit-2.36-9.1.x86_64 glibc-devel-2.36-8.1.x86_64 glibc-devel-2.36-9.1.x86_64 glibc-devel-32bit-2.36-8.1.x86_64 glibc-devel-32bit-2.36-9.1.x86_64 glibc-extra-2.36-8.1.x86_64 glibc-extra-2.36-9.1.x86_64 glibc-i18ndata-2.36-8.1.noarch glibc-i18ndata-2.36-9.1.noarch glibc-info-2.36-8.1.noarch glibc-info-2.36-9.1.noarch glibc-locale-2.36-8.1.x86_64 glibc-locale-2.36-9.1.x86_64 glibc-locale-base-2.36-8.1.x86_64 glibc-locale-base-2.36-9.1.x86_64 glibc-locale-base-32bit-2.36-8.1.x86_64 glibc-locale-base-32bit-2.36-9.1.x86_64 glibc-profile-2.36-8.1.x86_64 glibc-profile-2.36-9.1.x86_64 glibc-profile-32bit-2.36-8.1.x86_64 glibc-profile-32bit-2.36-9.1.x86_64 imlib2-1.10.0-1.1.x86_64 imlib2-1.9.1-2.1.x86_64 imlib2-filters-1.10.0-1.1.x86_64 imlib2-filters-1.9.1-2.1.x86_64 imlib2-loaders-1.10.0-1.1.x86_64 imlib2-loaders-1.9.1-2.1.x86_64 kbd-2.4.0-10.2.x86_64 kbd-2.4.0-10.3.x86_64 kbd-legacy-2.4.0-10.2.noarch kbd-legacy-2.4.0-10.3.noarch kernel-default-6.0.10-1.1.x86_64 kernel-default-6.1.0-1.1.x86_64 kernel-default-devel-6.0.10-1.1.x86_64 kernel-default-devel-6.1.0-1.1.x86_64 kernel-devel-6.0.10-1.1.noarch kernel-devel-6.1.0-1.1.noarch kernel-docs-6.0.12-1.1.noarch kernel-docs-6.1.0-1.1.noarch kernel-macros-6.0.12-1.1.noarch kernel-macros-6.1.0-1.1.noarch kernel-source-6.0.10-1.1.noarch kernel-source-6.1.0-1.1.noarch kernel-syms-6.0.10-1.1.x86_64 kernel-syms-6.1.0-1.1.x86_64 libImlib2-1-1.10.0-1.1.x86_64 libImlib2-1-1.9.1-2.1.x86_64 libart_lgpl-devel-2.3.21-24.7.x86_64 libart_lgpl-devel-2.3.21-25.1.x86_64 libart_lgpl_2-2-2.3.21-24.7.x86_64 libart_lgpl_2-2-2.3.21-25.1.x86_64 libasan8-13.0.0+git197351-1.1.x86_64 libasan8-13.0.0+git197351-2.1.x86_64 libasan8-32bit-13.0.0+git197351-1.1.x86_64 libasan8-32bit-13.0.0+git197351-2.1.x86_64 libatomic1-13.0.0+git197351-1.1.x86_64 libatomic1-13.0.0+git197351-2.1.x86_64 libatomic1-32bit-13.0.0+git197351-1.1.x86_64 libatomic1-32bit-13.0.0+git197351-2.1.x86_64 libavahi-client3-0.8-21.1.x86_64 libavahi-client3-0.8-22.1.x86_64 libavahi-client3-32bit-0.8-21.1.x86_64 libavahi-client3-32bit-0.8-22.1.x86_64 libavahi-common3-0.8-21.1.x86_64 libavahi-common3-0.8-22.1.x86_64 libavahi-common3-32bit-0.8-21.1.x86_64 libavahi-common3-32bit-0.8-22.1.x86_64 libavahi-core7-0.8-21.1.x86_64 libavahi-core7-0.8-22.1.x86_64 libavahi-devel-0.8-21.1.x86_64 libavahi-devel-0.8-22.1.x86_64 libavahi-glib1-0.8-21.1.x86_64 libavahi-glib1-0.8-22.1.x86_64 libavahi-libevent1-0.8-21.1.x86_64 libavahi-libevent1-0.8-22.1.x86_64 libcairomm-1_0-1-1.12.2-3.22.x86_64 libcairomm-1_0-1-1.12.2-4.1.x86_64 libcloudproviders0-0.3.1-2.11.x86_64 libcloudproviders0-0.3.1-3.1.x86_64 libcolorhug2-1.4.6-204.13.x86_64 libcolorhug2-1.4.6-204.14.x86_64 libdns_sd-0.8-21.1.x86_64 libdns_sd-0.8-22.1.x86_64 libenchant1-1.6.1-5.15.x86_64 libenchant1-1.6.1-6.1.x86_64 libgcc_s1-13.0.0+git197351-1.1.x86_64 libgcc_s1-13.0.0+git197351-2.1.x86_64 libgcc_s1-32bit-13.0.0+git197351-1.1.x86_64 libgcc_s1-32bit-13.0.0+git197351-2.1.x86_64 libgfortran5-13.0.0+git197351-1.1.x86_64 libgfortran5-13.0.0+git197351-2.1.x86_64 libgfortran5-32bit-13.0.0+git197351-1.1.x86_64 libgfortran5-32bit-13.0.0+git197351-2.1.x86_64 libglade-2_0-0-2.6.4-27.9.x86_64 libglade-2_0-0-2.6.4-28.1.x86_64 libgmic3-3.1.6-28.10.x86_64 libgmic3-3.1.6-29.1.x86_64 libgomp1-13.0.0+git197351-1.1.x86_64 libgomp1-13.0.0+git197351-2.1.x86_64 libgomp1-32bit-13.0.0+git197351-1.1.x86_64 libgomp1-32bit-13.0.0+git197351-2.1.x86_64 libgtop-2_0-11-2.40.0-3.6.x86_64 libgtop-2_0-11-2.40.0-4.1.x86_64 libgtop-lang-2.40.0-3.6.noarch libgtop-lang-2.40.0-4.1.noarch libhdf5-200-1.12.2-199.17.x86_64 libhdf5-200-1.12.2-199.19.x86_64 libhdf5_cpp200-1.12.2-199.17.x86_64 libhdf5_cpp200-1.12.2-199.19.x86_64 libhdf5_fortran200-1.12.2-199.17.x86_64 libhdf5_fortran200-1.12.2-199.19.x86_64 libhdf5_hl200-1.12.2-199.17.x86_64 libhdf5_hl200-1.12.2-199.19.x86_64 libhdf5_hl_cpp200-1.12.2-199.17.x86_64 libhdf5_hl_cpp200-1.12.2-199.19.x86_64 libhdf5hl_fortran200-1.12.2-199.17.x86_64 libhdf5hl_fortran200-1.12.2-199.19.x86_64 libhwasan0-13.0.0+git197351-1.1.x86_64 libhwasan0-13.0.0+git197351-2.1.x86_64 libitm1-13.0.0+git197351-1.1.x86_64 libitm1-13.0.0+git197351-2.1.x86_64 libitm1-32bit-13.0.0+git197351-1.1.x86_64 libitm1-32bit-13.0.0+git197351-2.1.x86_64 liblsan0-13.0.0+git197351-1.1.x86_64 liblsan0-13.0.0+git197351-2.1.x86_64 liblzma5-32bit-5.2.10-1.1.x86_64 liblzma5-32bit-5.2.8-2.1.x86_64 liblzma5-5.2.10-1.1.x86_64 liblzma5-5.2.8-2.1.x86_64 libmbedcrypto7-2.28.1-1.1.x86_64 libmbedcrypto7-2.28.2-1.1.x86_64 libmbedtls14-2.28.1-1.1.x86_64 libmbedtls14-2.28.2-1.1.x86_64 libmbedx509-1-2.28.1-1.1.x86_64 libmbedx509-1-2.28.2-1.1.x86_64 libmpc3-1.3.0-1.1.x86_64 libmpc3-1.3.1-1.1.x86_64 libnm0-1.40.6-1.1.x86_64 libnm0-1.40.8-1.1.x86_64 libnm0-32bit-1.40.6-1.1.x86_64 libnm0-32bit-1.40.8-1.1.x86_64 libobjc4-13.0.0+git197351-1.1.x86_64 libobjc4-13.0.0+git197351-2.1.x86_64 libosip2-15-5.3.0-1.4.x86_64 libosip2-15-5.3.1-1.1.x86_64 libosip2-devel-5.3.0-1.4.x86_64 libosip2-devel-5.3.1-1.1.x86_64 libpangomm-1_4-1-2.46.3-1.1.x86_64 libpangomm-1_4-1-2.46.3-2.1.x86_64 libpcre2-16-0-10.42-2.1.x86_64 libpcre2-16-0-10.42-3.1.x86_64 libpcre2-16-0-32bit-10.42-2.1.x86_64 libpcre2-16-0-32bit-10.42-3.1.x86_64 libpcre2-32-0-10.42-2.1.x86_64 libpcre2-32-0-10.42-3.1.x86_64 libpcre2-8-0-10.42-2.1.x86_64 libpcre2-8-0-10.42-3.1.x86_64 libpcre2-8-0-32bit-10.42-71.1.x86_64 libpcre2-8-0-32bit-10.42-73.1.x86_64 libpcre2-posix3-10.42-2.1.x86_64 libpcre2-posix3-10.42-3.1.x86_64 libquadmath0-13.0.0+git197351-1.1.x86_64 libquadmath0-13.0.0+git197351-2.1.x86_64 libquadmath0-32bit-13.0.0+git197351-1.1.x86_64 libquadmath0-32bit-13.0.0+git197351-2.1.x86_64 librpmbuild9-4.18.0-1.1.x86_64 librpmbuild9-4.18.0-2.1.x86_64 libtsan2-13.0.0+git197351-1.1.x86_64 libtsan2-13.0.0+git197351-2.1.x86_64 libubsan1-13.0.0+git197351-1.1.x86_64 libubsan1-13.0.0+git197351-2.1.x86_64 libubsan1-32bit-13.0.0+git197351-1.1.x86_64 libubsan1-32bit-13.0.0+git197351-2.1.x86_64 libvlc5-3.0.18-6.2.x86_64 libvlc5-3.0.18-7.1.x86_64 libvlccore9-3.0.18-6.2.x86_64 libvlccore9-3.0.18-7.1.x86_64 lutris-0.5.12-77.7.noarch lutris-0.5.12-77.8.noarch lutris-0.5.12-77.9.noarch nodejs19-19.3.0-20.1.x86_64 nodejs19-19.3.0-20.2.x86_64 npm19-19.3.0-20.1.x86_64 npm19-19.3.0-20.2.x86_64 nscd-2.36-8.1.x86_64 nscd-2.36-9.1.x86_64 openSUSE-release-20221220-2007.1.x86_64 openSUSE-release-20221222-2010.1.x86_64 openSUSE-release-ftp-20221220-2007.1.x86_64 openSUSE-release-ftp-20221222-2010.1.x86_64 pangomm1_4-devel-2.46.3-1.1.x86_64 pangomm1_4-devel-2.46.3-2.1.x86_64 patch-2.7.6-72.d_t.182.x86_64 patch-2.7.6-72.d_t.184.x86_64 pcre2-devel-10.42-2.1.x86_64 pcre2-devel-10.42-3.1.x86_64 perf-6.0.12-78.21.x86_64 perf-6.1.0-78.22.x86_64 perf-gtk-6.0.12-78.21.x86_64 perf-gtk-6.1.0-78.22.x86_64 python310-rpm-4.18.0-1.1.x86_64 python310-rpm-4.18.0-2.1.x86_64 python38-rpm-4.18.0-1.1.x86_64 python38-rpm-4.18.0-2.1.x86_64 rpm-32bit-4.18.0-1.1.x86_64 rpm-32bit-4.18.0-2.1.x86_64 rpm-4.18.0-1.1.x86_64 rpm-4.18.0-2.1.x86_64 rpm-build-4.18.0-1.1.x86_64 rpm-build-4.18.0-2.1.x86_64 rpm-build-perl-4.18.0-1.1.x86_64 rpm-build-perl-4.18.0-2.1.x86_64 rpmlint-2.4.0+git20221209.975098b-1.7.noarch rpmlint-2.4.0+git20221209.975098b-1.9.noarch supertuxkart-data-1.4-79.4.noarch supertuxkart-data-1.4-79.5.noarch typelib-1_0-NM-1_0-1.40.6-1.1.x86_64 typelib-1_0-NM-1_0-1.40.8-1.1.x86_64 v4l2loopback-utils-0.12.7-1.12.noarch v4l2loopback-utils-0.12.7-1.13.noarch virtualbox-kmp-default-7.0.4_k6.0.10_1-2.1.x86_64 virtualbox-kmp-default-7.0.4_k6.1.0_1-2.3.x86_64 vlc-3.0.18-6.2.x86_64 vlc-3.0.18-7.1.x86_64 vlc-codec-gstreamer-3.0.18-6.2.x86_64 vlc-codec-gstreamer-3.0.18-7.1.x86_64 vlc-codecs-3.0.18-6.2.x86_64 vlc-codecs-3.0.18-7.1.x86_64 vlc-lang-3.0.18-6.2.noarch vlc-lang-3.0.18-7.1.noarch vlc-noX-3.0.18-6.2.x86_64 vlc-noX-3.0.18-7.1.x86_64 vlc-opencv-3.0.18-6.2.x86_64 vlc-opencv-3.0.18-7.1.x86_64 vlc-qt-3.0.18-6.2.x86_64 vlc-qt-3.0.18-7.1.x86_64 xz-5.2.10-1.1.x86_64 xz-5.2.8-2.1.x86_64 xz-devel-5.2.10-1.1.x86_64 xz-devel-5.2.8-2.1.x86_64 xz-lang-5.2.10-1.1.noarch xz-lang-5.2.8-2.1.noarch and as you can see, wicked is not in the list (and neither udev o systemd). Instead there is a new kernel. > I suspect the problem is not wicked (at least, directly) but missing event > or notification. So the reason could be kernel or udev/systemd. It would be > extremely helpful if you could identify what package exactly caused this > regression. > > Get the list of packages that were updated; revert to previous snapshot; > update each package individually and check whether you observe this problem. I'm not on BTRFS, nor LVM (my system was installed about 11 years ago with ext4... and never formatted or reinstalled), so I think I cannot rollback to a previous snapshot. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1206758] xhci_hcd periodically not ready on resume
by bugzilla_noreply＠suse.com 04 Jan '23

04 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1206758 https://bugzilla.suse.com/show_bug.cgi?id=1206758#c15 --- Comment #15 from Pablo Sanchez <pablo(a)blueoakdb.com> --- (In reply to Oliver Neukum from comment #8) > It is possible that it is just not resumed without a device. Hey Oliver, Well, another excellent question. Clearly you understand how everything is supposed to work under the hood. Nice. I tried to gather more fine-grained data in the hopes it might help. If not, meh, I burned a few minutes. :p ::: Test 1 ::: 1. Connect phone and note laptop recognizes it. 2. Leave phone connected and suspend. 3. Do not disconnect phone. 4. Resume the laptop. ... Result ... Worked! ::: Test 2 ::: Same as the previous test but replace step 3 with a disconnect/reconnect: 1. Connect phone and note laptop recognizes it. 2. Leave phone connected and suspend. 3a. Disconnect phone. 3b. Wait for a few seconds. 3c. Reconnect phone 4. Resume the laptop. ... Result ... Problem tickled. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1206852] New: Add new kind of devel packages, called global
by bugzilla_noreply＠suse.com 04 Jan '23

04 Jan '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1206852 Bug ID: 1206852 Summary: Add new kind of devel packages, called global Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: openSUSE Tumbleweed Status: NEW Severity: Enhancement Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: slawek(a)lach.art.pl QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- For boost Linux adoption, allow to simply develop packages for each distribution. Zypper should accept --devel-each switch or handle virtual --devel-each packages and redirect those requests to gnu-guix. OpenSUSE should been integrated with gnu-guix by default and allow to start developing packages for most distribution. But, GUIX package manager should been adopted by more distribution firstly. GNU-GUIX is nix-based package manager for GUIX and other distributions. OpenSUSE allows to install this package manager from default distribution. OpenSUSE could gather more developers by allowing to create croos-distro packages using GNU-GUIX. When user download source package, it will install dependencies for OpenSUSE> By installing all needed packages by GUIX, user will be pretty sure, program will behaves similar on other distribution, if user install it by GUIX. It is similar than flatpak approach, but it has some advantage, like reduces space usage. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1206620] remove GraphicsMagick in favour of ImageMagick
by bugzilla_noreply＠suse.com 04 Jan '23

04 Jan '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1206620 http://bugzilla.opensuse.org/show_bug.cgi?id=1206620#c18 --- Comment #18 from Stefan Br�ns <stefan.bruens(a)rwth-aachen.de> --- (In reply to Petr Gajdos from comment #17) > (In reply to Stefan Br�ns from comment #16) > > ImageMagick has a significantly more heavy dependency chain than > > GraphicsMagick, and IIRC this will also reintroduce a build cycle. > > Which build cycle, could you elaborate with your knowledge, please? Unfortunately I don't remember any specifics. This may have been solved in the mean time as several packages no build e.g. documentation as a _multibuild flavor. > > As it is used in quite some places as build dependency all these packages > > then will be in blocked state until ImageMagick has been rebuilt. > > Perhaps yes, but I am not sure keeping GraphicsMagick for that reason only > outweigh the issues described in comment 0. I do not see many packages > requiring GraphicsMagick currently. That is why I am _considering_ > GraphicsMagick removal now. E.g. the science repo was not published for Aarch64 for 3 months as it failed to finish in time (i.e. before a new snapshot was published). This has now been solved by carefully readjusting overexaggerated _constraints, splitting package builds, and removing incorrect build dependencies. Extending the dependency chain (causing more rebuilds, and longer overall build times) will likely bring back this problem. > At least gmic fake dependency was discovered now. But yes, I have to admit > that I cannot be sure on the beginning we can get rid of GraphicsMagick > completely, no matter how sensible it sounds. I think there are more packages which actually need neither *Magick. Some packages call `(gm) convert` to create png icons from some other format, these could often also use netpbm-tools. E.g. this (repeated) invocation in the branding package could be replaced: https://github.com/openSUSE/branding/blob/c0f718d6b673ef2b1dec4e3d36857391a… - rsvg-convert raw-theme-drop/desktop-$${size}.svg -o tmp-$@.png; \ - gm convert -quality 100 -interlace None -colorspace YCbCr -sampling-factor 2x2 tmp-$@.png openSUSE/wallpapers/openSUSEdefault/contents/images/$${size}.jpg; \ - rm tmp-$@.png; \ + rsvg-convert raw-theme-drop/desktop-$${size}.svg -o /dev/stdout | \ + pngtopnm | pnmtojpeg -quality 100 -sample 1x1,2x2 > openSUSE/wallpapers/openSUSEdefault/contents/images/$${size}.jpg; -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1206846] sysfs: cannot create duplicate filename '/bus/nvmem/devices/rmem0'
by bugzilla_noreply＠suse.com 04 Jan '23

04 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1206846 https://bugzilla.suse.com/show_bug.cgi?id=1206846#c1 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |seppe.hoogzaad(a)gmail.com, | |tiwai(a)suse.com Flags| |needinfo?(seppe.hoogzaad@gm | |ail.com) --- Comment #1 from Takashi Iwai <tiwai(a)suse.com> --- There are actually two kernel warnings: one is about the duplicated sysfs entry for /bus/nvmem/devices/rmem0, while another is the firmware update timeout for rpi. Are both new warnings, or only the former? In anyway, TW already moved to 6.1 kernel. Could you verify whether the issue still persists with the latest kernel or not? -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1206843] Lenovo T14s Gen3 AMD resume from sleep broken
by bugzilla_noreply＠suse.com 04 Jan '23

04 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1206843 https://bugzilla.suse.com/show_bug.cgi?id=1206843#c1 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |cgoll(a)suse.com, | |tiwai(a)suse.com Flags| |needinfo?(cgoll(a)suse.com) --- Comment #1 from Takashi Iwai <tiwai(a)suse.com> --- Could you check whether it's a regression in the update kernel(s) or it's been broken in all Leap 15.4 kernels? In anyway, please give hwinfo output from Leap 15.4 kernel. When TW kernel works, give the hwinfo output from there, too, in addition to the dmesg outputs from both cases. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1206451] New: wlan device QCNFA765 not detected
by bugzilla_noreply＠suse.com 04 Jan '23

04 Jan '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1206451 Bug ID: 1206451 Summary: wlan device QCNFA765 not detected Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.5 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: cgoll(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- The wireless network adapter Qualcomm QCNFA765 is not detected with the actual leap kernel. As workaround I am using the kernel from kernel:stable:backport (kernel-default-6.1.0-lp153.2.1.gc3232e1.x86_64) -- You are receiving this mail because: You are on the CC list for the bug.

1 15