August 2021 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1189000] Cannot update nextcloud desktop
by bugzilla_noreply＠suse.com 03 Aug '21

03 Aug '21

https://bugzilla.suse.com/show_bug.cgi?id=1189000 https://bugzilla.suse.com/show_bug.cgi?id=1189000#c2 Fabian Vogt <fvogt(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |fvogt(a)suse.com --- Comment #2 from Fabian Vogt <fvogt(a)suse.com> --- Apparently that is only used for creating a .zip archive with debug logs: https://github.com/nextcloud/desktop/blob/4efe00fecaf88b587c6bcb75f1af17ba1… That could probably just be disabled. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1189001] New: firewall-applet missing dbus.mainloop.pyqt5 in python-qt5
by bugzilla_noreply＠suse.com 03 Aug '21

03 Aug '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1189001 Bug ID: 1189001 Summary: firewall-applet missing dbus.mainloop.pyqt5 in python-qt5 Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.3 Hardware: x86-64 OS: openSUSE Leap 15.3 Status: NEW Severity: Normal Priority: P5 - None Component: KDE Applications Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: spam.catcher(a)t-online.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- In Opensuse versions < 15.3, firewall-applet autostarted (by a desktop file in /etc/xdg/autostart). This file is still there, but since version 15.3 it no longer starts because of the error File "/usr/bin/firewall-applet", line 31, in <module> from dbus.mainloop.pyqt5 import DBusQtMainLoop ModuleNotFoundError: No module named 'dbus.mainloop.pyqt5' This is probably resolved by packaging a new version for Opensuse 15.3 (already there in Tumbelweed), but entails dependencies to firewalld et al. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1188980] Multiple pool entries in chrony configuration at install
by bugzilla_noreply＠suse.com 03 Aug '21

03 Aug '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1188980 Tim Serong <tserong(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tserong(a)suse.com -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1188952] yast application don't remember the password when selected to do so
by bugzilla_noreply＠suse.com 03 Aug '21

03 Aug '21

https://bugzilla.suse.com/show_bug.cgi?id=1188952 https://bugzilla.suse.com/show_bug.cgi?id=1188952#c2 --- Comment #2 from Dev Guy <devguy.ca(a)gmail.com> --- This is a bug, the option to save password is broken. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1183223] NetworkManager ignores proxy autoconfig
by bugzilla_noreply＠suse.com 03 Aug '21

03 Aug '21

https://bugzilla.suse.com/show_bug.cgi?id=1183223 https://bugzilla.suse.com/show_bug.cgi?id=1183223#c1 Jonathan Kang <songchuan.kang(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(noah(a)spacemule.ne | |t) --- Comment #1 from Jonathan Kang <songchuan.kang(a)suse.com> --- NetworkManager has been updated to 1.32.4 in Tumbleweed now. Can you confirm whether this is still failing in latest Tumbleweed? -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1188999] New: sssd service infinity loop, system never boots
by bugzilla_noreply＠suse.com 03 Aug '21

03 Aug '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1188999 Bug ID: 1188999 Summary: sssd service infinity loop, system never boots Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: screening-team-bugs(a)suse.de Reporter: luizluca(a)tre-sc.jus.br QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Hello, I'm using tumbleweed 20210731. If sssd was configured during installation to use AD, it will loop during boot if the machine is not joined to a domain. I get no SSH (PermitRootLogin is no) nor tty login, console is spammed with sssd starting/failed messages and I can only reboot using ctrl+alt+del. I normally use autoyast stage2 to join the domain. If I'm using yast ncursers, the sssd spam really makes things harder to type as sssd.service is started before autoyast stage2 and keeps restarting while stage2 is running. I can workaround it masking sssd.service with systemd.mask=sssd.service in order to joining the domain, either from stage2 or using a local user. After that, I can reboot (without the mask) and the system will work. I could get some debug info doing: 1) masking the sssd.service using command line 2) login with root 3) masking again with systemctl mask sssd.service 4) rebooting without systemd.mask=sssd.service 5) login with root 6) systemctl unmask sssd.service 7) systemctl sart sssd.service The error seems to be when /etc/krb5.keytab is missing, empty or does not have a corresponding principal entry. ago 02 21:56:58 testeinstall-ef systemd[1]: Starting System Security Services Daemon... ago 02 21:57:02 testeinstall-ef sssd[877]: Starting up ago 02 21:57:36 testeinstall-ef sssd_be[2027]: Starting up ago 02 21:57:36 testeinstall-ef sssd_be[2026]: Starting up ago 02 21:57:37 testeinstall-ef sssd_be[2026]: krb5_kt_start_seq_get failed: Key table file '/etc/krb5.keytab' not found ... ago 02 21:57:37 testeinstall-ef sssd_be[2026]: krb5_kt_start_seq_get failed: Key table file '/etc/krb5.keytab' not found ago 02 21:57:37 testeinstall-ef sssd_be[2026]: Failed to read keytab [FILE:/etc/krb5.keytab]: No suitable principal found in keytab ago 02 21:57:38 testeinstall-ef sssd_be[2027]: krb5_kt_start_seq_get failed: Key table file '/etc/krb5.keytab' not found ... ago 02 21:57:38 testeinstall-ef sssd_be[2027]: krb5_kt_start_seq_get failed: Key table file '/etc/krb5.keytab' not found ago 02 21:57:38 testeinstall-ef sssd_be[2027]: Failed to read keytab [FILE:/etc/krb5.keytab]: No suitable principal found in keytab ago 02 21:57:38 testeinstall-ef sssd_be[2028]: Starting up ago 02 21:57:38 testeinstall-ef sssd_be[2029]: Starting up ago 02 21:57:39 testeinstall-ef sssd_be[2028]: krb5_kt_start_seq_get failed: Key table file '/etc/krb5.keytab' not found ... ago 02 21:57:39 testeinstall-ef sssd_be[2028]: krb5_kt_start_seq_get failed: Key table file '/etc/krb5.keytab' not found ago 02 21:57:39 testeinstall-ef sssd_be[2028]: Failed to read keytab [FILE:/etc/krb5.keytab]: No suitable principal found in keytab ago 02 21:57:39 testeinstall-ef sssd_be[2029]: krb5_kt_start_seq_get failed: Key table file '/etc/krb5.keytab' not found ... ago 02 21:57:39 testeinstall-ef sssd_be[2029]: krb5_kt_start_seq_get failed: Key table file '/etc/krb5.keytab' not found ago 02 21:57:39 testeinstall-ef sssd_be[2029]: Failed to read keytab [FILE:/etc/krb5.keytab]: No suitable principal found in keytab ago 02 21:57:41 testeinstall-ef sssd_be[2200]: Starting up ... ago 02 21:57:46 testeinstall-ef sssd_be[2630]: Failed to read keytab [FILE:/etc/krb5.keytab]: No suitable principal found in keytab ago 02 21:57:46 testeinstall-ef sssd[877]: Exiting the SSSD. Could not restart critical service [tre-sc.gov.br]. ago 02 21:57:46 testeinstall-ef systemd[1]: sssd.service: Main process exited, code=exited, status=1/FAILURE ago 02 21:57:46 testeinstall-ef systemd[1]: sssd.service: Failed with result 'exit-code'. ago 02 21:57:46 testeinstall-ef systemd[1]: Failed to start System Security Services Daemon. ago 02 21:57:46 testeinstall-ef systemd[1]: sssd.service: Scheduled restart job, restart counter is at 1. ago 02 21:57:46 testeinstall-ef systemd[1]: Stopped System Security Services Daemon. ago 02 21:57:46 testeinstall-ef systemd[1]: Starting System Security Services Daemon... ago 02 21:57:47 testeinstall-ef sssd[3004]: Starting up If I touch /etc/krb5.keytab, the behavior is the same but the error message will be: ago 02 23:12:22 testeinstall-ef sssd_be[4479]: krb5_kt_start_seq_get failed: Unsupported key table format version number ago 02 23:12:22 testeinstall-ef sssd_be[4479]: Failed to read keytab [FILE:/etc/krb5.keytab]: No suitable principal found in keytab If I create a dummy /etc/krb5.keytab (echo -e "\0005\0002\c" >/etc/krb5.keytab), I still get the service loop but the krb5_kt_start_seq_get error is gone: ago 02 23:14:46 testeinstall-ef sssd_be[4697]: Starting up ago 02 23:14:47 testeinstall-ef sssd_be[4698]: Failed to read keytab [FILE:/etc/krb5.keytab]: No suitable principal found in keytab ago 02 23:14:47 testeinstall-ef sssd_be[4699]: Starting up ago 02 23:14:47 testeinstall-ef sssd_be[4697]: Failed to read keytab [FILE:/etc/krb5.keytab]: No suitable principal found in keytab ago 02 23:14:47 testeinstall-ef sssd_be[4700]: Starting up It looks like sssd.service simply restart on failure but not fast enough to reach the start limits (StartLimitIntervalSec and StartLimitBurst). You can easily reproduce it (re)moving the /etc/krb5.keytab and restarting the system (or only the service if you want to debug) The real issue is that it will not allow the system to reach login targets as sssd will never fail (I stopped to count after "restart counter is at 82"). Also, it would be nice if systemd would not spam over yast ncursers autoyast stage2. stage2 should not be started while other services are still starting. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1187642] [Build 20210622-1] openQA test fails in updates_packagekit_gpk
by bugzilla_noreply＠suse.com 03 Aug '21

03 Aug '21

https://bugzilla.suse.com/show_bug.cgi?id=1187642 https://bugzilla.suse.com/show_bug.cgi?id=1187642#c4 Jonathan Kang <songchuan.kang(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |WORKSFORME --- Comment #4 from Jonathan Kang <songchuan.kang(a)suse.com> --- (In reply to Grace Wang from comment #3) > > @Jonathan, Thanks for spending time on this ticket. > Based on the latest results on openQA, I agree with close it for now. Closing. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1187512] yast fails to convert Wi-Fi connections to ones that works in NetworkManager
by bugzilla_noreply＠suse.com 03 Aug '21

03 Aug '21

https://bugzilla.suse.com/show_bug.cgi?id=1187512 Jonathan Kang <songchuan.kang(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|songchuan.kang(a)suse.com |yast2-maintainers(a)suse.de Summary|Network Manager can't |yast fails to convert Wi-Fi |connect to complex my SSID |connections to ones that | |works in NetworkManager -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1188687] bridge, can't connect
by bugzilla_noreply＠suse.com 03 Aug '21

03 Aug '21

https://bugzilla.suse.com/show_bug.cgi?id=1188687 https://bugzilla.suse.com/show_bug.cgi?id=1188687#c10 --- Comment #10 from Jonathan Kang <songchuan.kang(a)suse.com> --- (In reply to Episteme PROMENEUR from comment #9) > I found where is the problem. > > If I use the button "connect" then plasmoid network launches the master > connection instead of the slave one. > > To launch a bridge, you must launch the slave. Lovely! btw, there is an setting called autoconnect-slaves, you can modify this to automatically connect slaves when you're activating the master connection. For more information, check out "man nm-settings". -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1185656] u-boot is unable to load DTB automatically from BTRFS partition
by bugzilla_noreply＠suse.com 03 Aug '21

03 Aug '21

https://bugzilla.suse.com/show_bug.cgi?id=1185656 https://bugzilla.suse.com/show_bug.cgi?id=1185656#c7 Wenruo Qu <wqu(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(wqu(a)suse.com) | --- Comment #7 from Wenruo Qu <wqu(a)suse.com> --- Already reviewed. It's indeed the default subvolume causing the problem. The patch should solve it properly. -- You are receiving this mail because: You are on the CC list for the bug.

1 0