April 2020 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1165646] [Build 20200303] cracklib "password is too simple" pop-up is not shown in yast2-firstboot module in GNOME
by bugzilla_noreply＠novell.com 02 Apr '20

02 Apr '20

http://bugzilla.suse.com/show_bug.cgi?id=1165646 http://bugzilla.suse.com/show_bug.cgi?id=1165646#c6 --- Comment #6 from Stefan Hundhammer <shundhammer(a)suse.com> --- It is also possible that Wayland is not yet running at that time, so the YaST start scripts will start an X server. Since this is no longer running from the inst-sys, it is possible that icewm is simply not available because the package is not installed. In that case we should probably require the icewm package from the yast2-firstboot package. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1165646] [Build 20200303] cracklib "password is too simple" pop-up is not shown in yast2-firstboot module in GNOME
by bugzilla_noreply＠novell.com 02 Apr '20

02 Apr '20

http://bugzilla.suse.com/show_bug.cgi?id=1165646 http://bugzilla.suse.com/show_bug.cgi?id=1165646#c5 --- Comment #5 from Stefan Hundhammer <shundhammer(a)suse.com> --- With the help of @snwint we found out that at least during installation, the YaST start scripts at some point call /usr/lib/YaST2/bin/testX which also tries to start the "icewm" window manager. We don't know yet if this is also what the start scripts starting yast-firstboot do (but I guess they do). When I run this testX in a running Xfce4 environment, I get an error testX: could not run windowmanager fatal IO error 2 (No such file or directory) on X server ":0.0" -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1165646] [Build 20200303] cracklib "password is too simple" pop-up is not shown in yast2-firstboot module in GNOME
by bugzilla_noreply＠novell.com 02 Apr '20

02 Apr '20

http://bugzilla.suse.com/show_bug.cgi?id=1165646 http://bugzilla.suse.com/show_bug.cgi?id=1165646#c4 --- Comment #4 from Stefan Hundhammer <shundhammer(a)suse.com> --- If this happens only in yast-firstboot on GNOME, this might be a problem with Wayland and the window manager that we try to use here. So this works with KDE? And how about Xfce? -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1165646] [Build 20200303] cracklib "password is too simple" pop-up is not shown in yast2-firstboot module in GNOME
by bugzilla_noreply＠novell.com 02 Apr '20

02 Apr '20

http://bugzilla.suse.com/show_bug.cgi?id=1165646 http://bugzilla.suse.com/show_bug.cgi?id=1165646#c3 --- Comment #3 from Stefan Hundhammer <shundhammer(a)suse.com> --- When I look at that screenshot, it appears to me that there is no window manager running: There is just the pure Qt window, no window manager decorations (no WM borders, no window title, no window buttons, nothing). Since this does not seem to affect all installations, I think it is safe to assume that the window manager is on the installation media in principle and that it normally works; but it might have crashed in this scenario (or never started at all). It is hard to guess from outside of that machine why that might have happened. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1161666] spice-gtk lacks desktop file and icon
by bugzilla_noreply＠novell.com 02 Apr '20

02 Apr '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1161666 http://bugzilla.opensuse.org/show_bug.cgi?id=1161666#c2 Dominique Leuenberger <dimstar(a)opensuse.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |WONTFIX --- Comment #2 from Dominique Leuenberger <dimstar(a)opensuse.org> --- I agree with Stefan here. The README.md (installed as part of spice-gtk) contains: * **spicy** a gtk test client. The recommended client for end user is [virt-viewer] -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1162353] purge-kernels-service not automaticxally installed
by bugzilla_noreply＠novell.com 02 Apr '20

02 Apr '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1162353 http://bugzilla.opensuse.org/show_bug.cgi?id=1162353#c6 Dominique Leuenberger <dimstar(a)opensuse.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #6 from Dominique Leuenberger <dimstar(a)opensuse.org> --- purge-kernels-service has since been enabled as a requirement on the base pattern, meaning it is part of every installed system -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1166407] New: AppArmor profiles should be sub-packages of the application they protect
by bugzilla_noreply＠novell.com 02 Apr '20

02 Apr '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1166407 Bug ID: 1166407 Summary: AppArmor profiles should be sub-packages of the application they protect Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.1 Hardware: All OS: Other Status: NEW Severity: Enhancement Priority: P5 - None Component: AppArmor Assignee: suse-beta(a)cboltz.de Reporter: philippe.andersson(a)iba-group.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- All default AppArmor profiles are currently provided as part of package 'apparmor-profiles'. That's all well and good as long as only official SUSE-provided packages are installed for the applications protected by AppArmor. When you start installing 3rd-party packages for the same application, that system breaks down, because the 3rd-party build of the application may not have the exact same requirements, meaning its startup may get blocked by AppArmor. The workaround we put in place was to use the mechanism of include files (in '/etc/apparmor.d/local/') to cover the extra access rights needed. But it would be much cleaner if the 3rd-party vendor could provide their own AppArmor profiles as a sub-package of their application. In the current situation, that's not possible, as they would need to overwrite a (set of) file(s) provided by another package. Case in point: the Samba 4 packages built by SerNet GmbH. Their daemons are prevented from starting by the following (default OpenSUSE) profiles: - /etc/apparmor.d/usr.sbin.nmbd - /etc/apparmor.d/usr.sbin.smbd - /etc/apparmor.d/usr.sbin.smbldap-useradd - /etc/apparmor.d/usr.sbin.winbindd I guess a possible alternative solution (through perhaps less flexible) would be to remove local include files "placeholders" from '/etc/apparmor.d/local/' (while keeping the '#include' directive in the master file). This way, 3rd-party vendors could safely package files destined to land below 'local/' (but the drawback, if I understand correctly, is that permissions granted in the master file could not easily be revoked by the included file if needed). -- You are receiving this mail because: You are on the CC list for the bug.

1 10

[Bug 1165193] New: "at-bus-launcher not responding" error when trying to shut down?
by bugzilla_noreply＠novell.com 02 Apr '20

02 Apr '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1165193 Bug ID: 1165193 Summary: "at-bus-launcher not responding" error when trying to shut down? Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Macintosh OS: SUSE Other Status: NEW Severity: Normal Priority: P5 - None Component: Patterns Assignee: dimstar(a)opensuse.org Reporter: non.space.1(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:73.0) Gecko/20100101 Firefox/73.0 Build Identifier: I get an error window when I try to suspend or shut down from GUI desktop, causing a several minute delay before the command is issued or done. Reproducible: Always Steps to Reproduce: 1.click shut down 2.window opens to confirm shut down 3.error window opens saying " "at-bus-launcher not responding" Actual Results: Takes a couple minutes for computer to shut down. Expected Results: shut down -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1167321] New: gnome-keyring does not autostart with sddm
by bugzilla_noreply＠novell.com 02 Apr '20

02 Apr '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1167321 Bug ID: 1167321 Summary: gnome-keyring does not autostart with sddm Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.2 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: GNOME Assignee: gnome-bugs(a)suse.de Reporter: cornelis(a)solcon.nl QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- According to the changelog of gnome-keyring gnome-keyring should autostart with sddm, but this is not the case. The relevant line I have in common-session-pc is: session optional pam_gnome_keyring.so auto_start only_if=gdm,gdm-password,lxdm,lightdm If I add "sddm" to this, it is working. The spec does have a line that includes "sddm", but somehow it is not written that way. The spec includes the following comment: ### # WARNING: when changing the pam-config calls in the scriptlets, please also # update them in baselibs.conf. # pam-config checks if the pam module is available for 32bit too if pam-32bit # is installed, so the call here might fail until gnome-keyring-pam-32bit gets # installed (see bnc#728586). ### I have the 32bit package installed and the baselibs.conf is not updated to include "sddm", which is probably the problem. -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1166981] System settings --> Themes broken in Cinnamon 4.2.3
by bugzilla_noreply＠novell.com 02 Apr '20

02 Apr '20

http://bugzilla.suse.com/show_bug.cgi?id=1166981 http://bugzilla.suse.com/show_bug.cgi?id=1166981#c5 --- Comment #5 from Swamp Workflow Management <swamp(a)suse.de> --- This is an autogenerated message for OBS integration: This bug (1166981) was mentioned in https://build.opensuse.org/request/show/790821 Factory / cinnamon -- You are receiving this mail because: You are on the CC list for the bug.

1 0