November 2018 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1114383] chkstat is not always called after Zypper has installed packages
by bugzilla_noreply＠novell.com 02 Nov '18

02 Nov '18

http://bugzilla.suse.com/show_bug.cgi?id=1114383 http://bugzilla.suse.com/show_bug.cgi?id=1114383#c1 Matthias Gerstner <matthias.gerstner(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |matthias.gerstner(a)suse.com Assignee|security-team(a)suse.de |fabian(a)ritter-vogt.de --- Comment #1 from Matthias Gerstner <matthias.gerstner(a)suse.com> --- Thank you for the bug report. When permissions are not updated then this is a per-package bug. The package in question needs to specify a line like: %set_permissions %{_kf5_libdir}/libexec/kcheckpass in the %post section of their RPM spec. For the case of kscreenlocker this line seems to be missing. Therefore I am assigning this bug to the kscreenlocker bug owner. If you are aware of any other packages with this behaviour then please open individual bugs for them. Actually we could also find such cases automatically via scripting ... but there is no such script implemented at the moment. I will discuss this in the security team. It maybe an area where we can improve. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1110412] Color Emoji support is disabled by Noto Emoji (monochrome) and DejaVu fonts
by bugzilla_noreply＠novell.com 02 Nov '18

02 Nov '18

http://bugzilla.suse.com/show_bug.cgi?id=1110412 http://bugzilla.suse.com/show_bug.cgi?id=1110412#c7 --- Comment #7 from Yunhe Guo <i(a)guoyunhe.me> --- (In reply to Petr Gajdos from comment #6) > Unfortunately I am some time out from font problematic, not sure how other > distros solve it. Here are some solutions on GitHub. The only working solution I tested is this: https://github.com/stove-panini/fontconfig-emoji Another related issue about DejavVu fonts: https://github.com/eosrei/twemoji-color-font/issues/21 Removing DejaVu fonts is the easiest solution. We have to balance how many users need Emoji fonts and how many users need DejaVu fonts. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1114118] New: yast2-configuration-management build failed with yast-rake update?
by bugzilla_noreply＠novell.com 02 Nov '18

02 Nov '18

http://bugzilla.suse.com/show_bug.cgi?id=1114118 Bug ID: 1114118 Summary: yast2-configuration-management build failed with yast-rake update? Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.1 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 Assignee: yast2-maintainers(a)suse.de Reporter: mlin(a)suse.com QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- fails in packaging yast2-configuration-management RPM, the error log below: [ 22s] Processing files: yast2-configuration-management-4.0.2-lp151.5.4.noarch [ 22s] error: File not found: /home/abuild/rpmbuild/BUILDROOT/yast2-configuration-management-4.0.2-lp151.5.4.x86_64/usr/share/doc/packages/yast2-configuration-management/COPYING looks like caused by yast-rake update[1] which changed COPYING file handling. [1] https://build.opensuse.org/request/show/645227 -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 1084943] NetworkManager with autoconnect enabled displays error messages
by bugzilla_noreply＠novell.com 02 Nov '18

02 Nov '18

http://bugzilla.suse.com/show_bug.cgi?id=1084943 http://bugzilla.suse.com/show_bug.cgi?id=1084943#c42 --- Comment #42 from Frank Kruger <fkrueger(a)mailbox.org> --- (In reply to Jonathan Kang from comment #41) > (In reply to Frank Kruger from comment #38) > > Isn't disabling wps by default brute force? What about those people using > > it? Since the issue seems to be due to a race between NM (asking for > > secrets) and sddm (not finished yet), as you wrote, I doubt that wps is the > > main culprit. > > Emm, you're right. Simply disabling that is not correct. The difference > between > KDE + sddm and GNOME + gdm(no issue) is that in GNOME, the first activation > of > wireless connection fails(same as KDE) but autoconnect of that connection get > blocked due to no secret until network agent registers. > > But in the logs provided in previous comments, there is no sign indicating > the autoconnect is blocked and a agent registers. This should be the reason > why > it fails. I need spent a bit more time on it. If you need additional logs, please let me know. Thanks for your efforts! -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 969159] subversion dependencies do not enforce matching password store (here: svn_kwallet)
by bugzilla_noreply＠novell.com 02 Nov '18

02 Nov '18

http://bugzilla.suse.com/show_bug.cgi?id=969159 Swamp Workflow Management <swamp(a)suse.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Whiteboard|maint:planned:update | -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 993642] apache2-mod_nss fails test suite with new mozilla-nss
by bugzilla_noreply＠novell.com 02 Nov '18

02 Nov '18

http://bugzilla.suse.com/show_bug.cgi?id=993642 Swamp Workflow Management <swamp(a)suse.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Whiteboard|ibs:running:8802:moderate | -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1026191] Add BPF into llvm target for PowerPC64 and AArch64
by bugzilla_noreply＠novell.com 02 Nov '18

02 Nov '18

http://bugzilla.suse.com/show_bug.cgi?id=1026191 Swamp Workflow Management <swamp(a)suse.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Whiteboard|ibs:running:8721:important | -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1114267] with kernel-default 4.19.0-3.1, don't start X
by bugzilla_noreply＠novell.com 02 Nov '18

02 Nov '18

http://bugzilla.suse.com/show_bug.cgi?id=1114267 http://bugzilla.suse.com/show_bug.cgi?id=1114267#c2 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED CC| |tiwai(a)suse.com Resolution|--- |INVALID --- Comment #2 from Takashi Iwai <tiwai(a)suse.com> --- OK, then let's close. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1112853] New: gnome-shell under wayland high cpu utilization
by bugzilla_noreply＠novell.com 02 Nov '18

02 Nov '18

http://bugzilla.opensuse.org/show_bug.cgi?id=1112853 Bug ID: 1112853 Summary: gnome-shell under wayland high cpu utilization Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: GNOME Assignee: bnc-team-gnome(a)forge.provo.novell.com Reporter: victor.zhestkov(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- After updating gnome-shell to 3.30 it increases cpu utilization and works with lags, mouse movement freezes sometimes. But in X11 there is no such issue. -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1084943] NetworkManager with autoconnect enabled displays error messages
by bugzilla_noreply＠novell.com 02 Nov '18

02 Nov '18

http://bugzilla.suse.com/show_bug.cgi?id=1084943 http://bugzilla.suse.com/show_bug.cgi?id=1084943#c41 --- Comment #41 from Jonathan Kang <sckang(a)suse.com> --- (In reply to Frank Kruger from comment #38) > Isn't disabling wps by default brute force? What about those people using > it? Since the issue seems to be due to a race between NM (asking for > secrets) and sddm (not finished yet), as you wrote, I doubt that wps is the > main culprit. Emm, you're right. Simply disabling that is not correct. The difference between KDE + sddm and GNOME + gdm(no issue) is that in GNOME, the first activation of wireless connection fails(same as KDE) but autoconnect of that connection get blocked due to no secret until network agent registers. But in the logs provided in previous comments, there is no sign indicating the autoconnect is blocked and a agent registers. This should be the reason why it fails. I need spent a bit more time on it. -- You are receiving this mail because: You are on the CC list for the bug.

1 0