April 2023 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1209655] New: gthumb crashes when accessing sub folders
by bugzilla_noreply＠suse.com 04 Apr '23

04 Apr '23

https://bugzilla.suse.com/show_bug.cgi?id=1209655 Bug ID: 1209655 Summary: gthumb crashes when accessing sub folders Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.4 Hardware: Other OS: Other Status: NEW Severity: Major Priority: P5 - None Component: GNOME Assignee: gnome-bugs(a)suse.de Reporter: heiko.rommel(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 865772 --> https://bugzilla.suse.com/attachment.cgi?id=865772&action=edit backtrace with all debuginfos installed I tried to paste selected images into a sub folder I had previously created with gthumb. As soon as I select that folder, gthumb crashes with SIGSEGV in function _gth_file_list_thumbnailer_iterate. version is gthumb-3.12.0-bp154.1.118.x86_64 from Main Repository backtrace when run from gdb is attached. -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1209895] New: Several patterns cannot be installed on microos - nothing provides 'libmutter-11.so.0
by bugzilla_noreply＠suse.com 04 Apr '23

04 Apr '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1209895 Bug ID: 1209895 Summary: Several patterns cannot be installed on microos - nothing provides 'libmutter-11.so.0 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other URL: https://openqa.opensuse.org/tests/3197822/modules/patt erns/steps/28 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Patterns Assignee: dimstar(a)opensuse.org Reporter: mloviska(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: openQA Blocker: Yes ## Observation openQA test in scenario microos-Tumbleweed-MicroOS-Image-ContainerHost-x86_64-container-host@mloviska/os-autoinst-distri-opensuse#slem_install_all_patterns@64bit fails in [patterns](https://openqa.opensuse.org/tests/3197822/modules/patterns/steps/… ## Test suite description New test case tries to install all available patterns for Microos. Tested image: openSUSE-MicroOS.x86_64-16.0.0-ContainerHost-kvm-and-xen-Snapshot20230327.qcow2 Problem: nothing provides 'libmutter-11.so.0()(64bit)' needed by the to be installed budgie-desktop-10.7+0-1.2.x86_64 Problem: nothing provides 'libmutter-11.so.0()(64bit)' needed by the to be installed budgie-desktop-10.7+0-1.2.x86_64 Problem: the to be installed pattern:microos_kde_desktop-5.0-64.1.x86_64 requires 'patterns-microos-desktop-kde', but this requirement cannot be provided Problem: the to be installed pattern:microos_ra_verifier-5.0-64.1.x86_64 requires 'patterns-microos-ra_verifier', but this requirement cannot be provided Problem: the to be installed pattern:xen_server-20210330-4.1.x86_64 requires 'patterns-server-xen_server', but this requirement cannot be provided Problem: the to be installed pattern:devel_rpm_build-20170319-11.2.x86_64 requires 'patterns-devel-base-devel_rpm_build', but this requirement cannot be provided Problem: nothing provides 'libmutter-11.so.0()(64bit)' needed by the to be installed budgie-desktop-10.7+0-1.2.x86_64 Solution 1: do not install pattern:budgie-20220527-2.2.x86_64 Solution 2: break budgie-desktop-10.7+0-1.2.x86_64 by ignoring some of its dependencies ## Reproducible Fails since (at least) Build [mloviska/os-autoinst-distri-opensuse#16735](https://openqa.opensuse.org/tes… ## Expected result Last good: (unknown) (or more recent) ## Further details Always latest result in this scenario: [latest](https://openqa.opensuse.org/tests/latest?arch=x86_64&distri=microos… -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1209741] pam session keyring creating during KDE GUI login not available to cifscreds
by bugzilla_noreply＠suse.com 04 Apr '23

04 Apr '23

https://bugzilla.suse.com/show_bug.cgi?id=1209741 https://bugzilla.suse.com/show_bug.cgi?id=1209741#c31 Fabian Vogt <fvogt(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(fabian@ritter-vog | |t.de) | --- Comment #31 from Fabian Vogt <fvogt(a)suse.com> --- (In reply to Joe S from comment #28) > Hi Franck, > > > This change has just been submitted to Factory, see comment #25. > > When I looked at the change I see pam_keyinit.so being added to > > /usr/lib/pam.d/systemd-user > > But I don't see it being removed from /etc/pam.d/sddm ( or the other ones I > suggested ). > > Since systemd-user and sddm both execute during the login process, > systemd-user with that change will create ( using revoke force ) the > keyring, but if it is left in /etc/pam.d/sddm then when that is processed > after systemd-user since sddm also uses revoke and force then it will > replace the keyring that was just created in systemd-user. > > Surely that cannot be correct ??? It is. Otherwise only systemd user services get a session keyring, but not processes started by the session itself. See comment 4. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1210029] Can't hibernate laptop Lenovo L14 Gen 3 AMD
by bugzilla_noreply＠suse.com 04 Apr '23

04 Apr '23

https://bugzilla.suse.com/show_bug.cgi?id=1210029 https://bugzilla.suse.com/show_bug.cgi?id=1210029#c6 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tiwai(a)suse.com --- Comment #6 from Takashi Iwai <tiwai(a)suse.com> --- So, with the latest SLE15-SP5 kernel I provided for mt76, and switching the BIOS sleep mode to "Linux S3 hibernation", S4 works fine now? It's interesting that this BIOS item isn't found on Thinkpad T14s Gen 3 I'm testing now... -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1210071] New: yast2 crash - no qt platform plugin initialized
by bugzilla_noreply＠suse.com 04 Apr '23

04 Apr '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1210071 Bug ID: 1210071 Summary: yast2 crash - no qt platform plugin initialized Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 Assignee: yast2-maintainers(a)suse.de Reporter: f4tmike(a)web.de QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- Hi, got a fresh tumbleweed installation (no DE; the very basic because I installed hyprland) and can't start yast2 gui. It crashes after I enter the root password. y2log: 2023-04-04 06:40:31 <1> mypc(2865) [Ruby] bin/y2start(<main>):22 y2base called with ["sw_single", "qt", "-name", "YaST2", "-icon", "yast"] 18736 �� 2023-04-04 06:40:31 <1> mypc(2865) [ui-component] YUIComponentCreator.cc(createInternal):124 Creating UI component for "" 18737 �� 2023-04-04 06:40:31 <1> mypc(2865) [ui] YUI.cc(YUI):83 This is libyui 4.5.0 18738 �� 2023-04-04 06:40:31 <1> mypc(2865) [ui] YUI.cc(YUI):84 Creating UI with threads 18739 �� 2023-04-04 06:40:31 <1> mypc(2865) [qt-ui] YQUI.cc(YQUI):108 This is libyui-qt 4.5.0 18740 �� 2023-04-04 06:40:31 <2> mypc(2865) [qt-ui] YQUI.cc(qMessageHandler):654 <libqt-warning> Could not find the Qt platform plugin "wayland" in "" 18741 �� 2023-04-04 06:40:31 <1> mypc(2865) [qt-ui] YQUI.cc(qMessageHandler):645 <libqt-info> Could not load the Qt platform plugin "xcb" in "" even though it was found �� . 18742 �� 2023-04-04 06:40:31 <3> mypc(2865) [qt-ui] YQUI.cc(qMessageHandler):658 <libqt-critical>This application failed to start because no Qt platform plugin could be �� initialized. Reinstalling the application may fix this problem. 18743 �� 2023-04-04 06:40:31 <3> mypc(2865) [qt-ui] YQUI.cc(qMessageHandler):658 18744 �� 2023-04-04 06:40:31 <3> mypc(2865) [qt-ui] YQUI.cc(qMessageHandler):658 Available platform plugins are: eglfs, linuxfb, minimal, minimalegl, offscreen, vnc, xc �� b. 18745 �� 2023-04-04 06:40:31 <3> mypc(2865) [qt-ui] YQUI.cc(qMessageHandler):658 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1209923] New: YaST Partitioner produces invalid GPT (on USB drive) after removing two partitions
by bugzilla_noreply＠suse.com 04 Apr '23

04 Apr '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1209923 Bug ID: 1209923 Summary: YaST Partitioner produces invalid GPT (on USB drive) after removing two partitions Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Major Priority: P5 - None Component: YaST2 Assignee: yast2-maintainers(a)suse.de Reporter: opensuse.k1akb(a)slmail.me QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- I started up YaST2 Partitioner. I insert a USB drive (that contained the OpenSUSE Tumbleweed installation image, but probably irrelevant) and use the partitioner to remove the 2 existing partitions. I let the partitioner apply the modifications and close it. What happens: - in KDE, the storage/removable device mount notifications show the medium is refreshed/reloaded and shows as if the partitions still exist. (Reports on OpenSUSE Tumbleweed partition) - `sudo gdisk -l /dev/sda` reports a corrupt GPT partition. What I expected: - KDE to detect a drive without partitions, therefore nothing to mount. - YaST2 Partitioner to make the modifications such that there are no corruptions, i.e. `gdisk` reports no errors and changes are applied without surprises :-) NOTE: (obviously) I lost no valuable data (except for the OpenSUSE Tumbleweed image, of course), but I would think twice to trust YaST2 for making changes to drivers purposed for backup/long-term storage. ``` user@host ~> sudo gdisk -l /dev/sda [sudo] password for user: GPT fdisk (gdisk) version 1.0.9.1 Caution: invalid main GPT header, but valid backup; regenerating main header from backup! Warning: Invalid CRC on main header data; loaded backup partition table. Warning! Main and backup partition tables differ! Use the 'c' and 'e' options on the recovery & transformation menu to examine the two tables. Warning! Main partition table CRC mismatch! Loaded backup partition table instead of main partition table! Warning! One or more CRCs don't match. You should repair the disk! Main header: ERROR Backup header: OK Main partition table: ERROR Backup partition table: OK Partition table scan: MBR: MBR only BSD: not present APM: not present GPT: damaged Found valid MBR and corrupt GPT. Which do you want to use? (Using the GPT MAY permit recovery of GPT data.) 1 - MBR 2 - GPT 3 - Create blank GPT Your answer: ^C�� user@host ~ [SIGINT]> ``` Not sure which packages belong to YaST2 Partitioner: rpm -qa | grep yast2 ``` yast2-bootloader-4.6.0-1.1.x86_64 yast2-metapackage-handler-4.6.0-1.1.noarch yast2-online-update-frontend-4.6.1-1.1.noarch yast2-packager-4.6.0-1.1.x86_64 patterns-yast-yast2_basis-20220411-1.4.x86_64 yast2-journal-4.6.0-1.1.noarch yast2-python3-bindings-4.6.0-1.2.x86_64 yast2-sysconfig-4.6.0-1.1.noarch yast2-alternatives-4.6.0-1.1.x86_64 patterns-yast-yast2_desktop-20220411-1.4.x86_64 yast2-country-data-4.6.0-1.1.x86_64 yast2-security-4.6.0-1.1.noarch yast2-xml-4.6.0-1.2.x86_64 yast2-core-4.6.0-1.2.x86_64 yast2-printer-4.6.0-1.1.x86_64 yast2-perl-bindings-4.6.0-1.2.x86_64 yast2-users-4.6.0-1.2.x86_64 yast2-network-4.6.0-1.1.noarch yast2-update-4.6.0-1.1.x86_64 yast2-qt-branding-openSUSE-84.87.20230227-1.1.noarch yast2-apparmor-4.6.0-1.1.noarch patterns-yast-x11_yast-20220411-1.4.x86_64 yast2-ruby-bindings-4.6.1-1.2.x86_64 yast2-pkg-bindings-4.6.0-1.2.x86_64 yast2-x11-4.6.0-1.1.x86_64 yast2-theme-4.6.0-1.1.noarch yast2-control-center-qt-4.6.0-1.2.x86_64 yast2-storage-ng-4.6.2-1.1.x86_64 patterns-kde-kde_yast-20221001-2.1.noarch yast2-ycp-ui-bindings-4.6.0-1.2.x86_64 yast2-online-update-4.6.1-1.1.noarch yast2-ntp-client-4.6.0-1.1.noarch yast2-theme-breeze-4.6.0-1.1.noarch yast2-logs-4.6.1-1.1.x86_64 yast2-pam-4.6.0-1.1.noarch yast2-services-manager-4.6.0-1.1.noarch yast2-proxy-4.6.0-1.1.noarch yast2-country-4.6.0-1.1.x86_64 yast2-firewall-4.6.0-1.1.noarch yast2-trans-stats-2.19.0-17.26.noarch yast2-hardware-detection-4.6.0-1.2.x86_64 yast2-control-center-4.6.0-1.2.x86_64 yast2-vm-4.6.0-1.1.x86_64 yast2-installation-4.6.1-1.1.noarch yast2-ldap-4.6.0-1.2.x86_64 yast2-4.6.1-1.1.x86_64 yast2-snapper-4.6.0-1.1.x86_64 yast2-transfer-4.6.0-1.2.x86_64 ``` rpm -qa | grep openSUSE-release ``` openSUSE-release-appliance-custom-20230326-2183.1.x86_64 openSUSE-release-20230326-2183.1.x86_64 ``` -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1208462] NetworkManager, bridge reconnection fails
by bugzilla_noreply＠suse.com 04 Apr '23

04 Apr '23

https://bugzilla.suse.com/show_bug.cgi?id=1208462 https://bugzilla.suse.com/show_bug.cgi?id=1208462#c10 --- Comment #10 from Jonathan Kang <songchuan.kang(a)suse.com> --- There is some useful information on configuring a bridge using NM here. As Thomas mentioned, bringing up the slave device should be able to activate the master connection as well. Try this to see if it helps with your issue. * https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues/911 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1210023] New: windows:mingw:win{32|64}/mingw{32|64}-kde4-filesystem: broken support for -d option in %_mingwxx_cmake_kde4
by bugzilla_noreply＠suse.com 03 Apr '23

03 Apr '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1210023 Bug ID: 1210023 Summary: windows:mingw:win{32|64}/mingw{32|64}-kde4-filesystem: broken support for -d option in %_mingwxx_cmake_kde4 Classification: openSUSE Product: openSUSE.org Version: unspecified Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: 3rd party software Assignee: fstrba(a)suse.com Reporter: ralf.habacker(a)freenet.de QA Contact: screening-team-bugs(a)suse.de CC: fridrich.strba(a)bluewin.ch, hib(a)hiberis.nl, mkbosmans(a)gmail.com Found By: --- Blocker: --- The %_mingwxx_cmake_kde4 macro provides a -d option to specify a custom build directory, which currently does not work. The aforementioned macro uses %_mingwxx_cmake_qt4, which in turn uses %_mingwxx_cmake. In the former and latter macros, a change to the build directory occurs, which leads to the current build problems with KDE4 packages on mingw32, and can be fixed by making adjustments in both macros. -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1209611] New: windows:mingw:win{32|64}/mingw{32|64}-filesystem: Move out cmake related support to mingw{32|64}-cross-cmake
by bugzilla_noreply＠suse.com 03 Apr '23

03 Apr '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1209611 Bug ID: 1209611 Summary: windows:mingw:win{32|64}/mingw{32|64}-filesystem: Move out cmake related support to mingw{32|64}-cross-cmake Classification: openSUSE Product: openSUSE.org Version: unspecified Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: 3rd party software Assignee: fstrba(a)suse.com Reporter: ralf.habacker(a)freenet.de QA Contact: screening-team-bugs(a)suse.de CC: fridrich.strba(a)bluewin.ch, hib(a)hiberis.nl, mkbosmans(a)gmail.com Found By: --- Blocker: --- CMake support files and macros for native packages are provided by the cmake package and not by the basic filesystem. To have a better separation and less updates of the mingw{32|64}-filesystem package when improving cmake support, it would be helpful to have a separate mingw32-cross-cmake package that provides the relevant rpm macros. The condition for this is that packages that use cmake use mingw32-cross-cmake as a build dependency. This could also be set centrally via the project configuration. -- You are receiving this mail because: You are on the CC list for the bug.

1 8

[Bug 1210068] New: Leap 15.5 beta "freezes" if AC adapter is getting disconnected
by bugzilla_noreply＠suse.com 03 Apr '23

03 Apr '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1210068 Bug ID: 1210068 Summary: Leap 15.5 beta "freezes" if AC adapter is getting disconnected Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.5 Hardware: x86-64 OS: Other Status: NEW Severity: Critical Priority: P5 - None Component: Basesystem Assignee: screening-team-bugs(a)suse.de Reporter: kwizzz(a)googlemail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 866077 --> http://bugzilla.opensuse.org/attachment.cgi?id=866077&action=edit boot + running on AC power Installed latest Leap 15.5 (openSUSE-Leap-15.5-NET-x86_64-Build449.1-Media.iso). As soon as the laptop is running on battery power, it is not allowing any other processes to start (it looks like system freezes). Easy to reproduce: * boot the system with AC adapter plugged in * once system is up and running, unplug AC * wait around 1 minute Effects: * mouse pointer is still moving * new processes cannot be started anymore (e.g. starting top in Konsole or pressing M4 key to access KDE menu) * if a shell prompt is available, you can try to shutdown or reboot, but besides killing (at least) X, nothing more happens, just a ending up in a black screen * journal log is not written completely which makes it a bit tricky to collect logs This behavior can be reproduced in KDE as well as XFCE. I did not try the other options, but I'm pretty sure it's not related to a DE. Laptop runs smooth under TW as well as Leap 15.4, so I am confident that it's not a hardware failure. Tried to capture journal output into a file (journalctl -f > file), but the last minute where the issue is coming up is not logged in the file. Journal is also lost between boots. Attached: * journal showing boot and system before unplugging * journal -f when unplugging AC * screenshot of journal once system froze -- You are receiving this mail because: You are on the CC list for the bug.

1 2