December 2021 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1193310] AUDIT-0: fwupd 1.7.2: new polkit rules to audit
by bugzilla_noreply＠suse.com 03 Dec '21

03 Dec '21

https://bugzilla.suse.com/show_bug.cgi?id=1193310 Marcus Meissner <meissner(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|fwupd 1.7.2: new polkit |AUDIT-0: fwupd 1.7.2: new |rules to audit |polkit rules to audit -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1192414] New: devel:languages:php/php7: php7-fpm doesn't come with initial config
by bugzilla_noreply＠suse.com 03 Dec '21

03 Dec '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1192414 Bug ID: 1192414 Summary: devel:languages:php/php7: php7-fpm doesn't come with initial config Classification: openSUSE Product: openSUSE.org Version: unspecified Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: 3rd party software Assignee: pgajdos(a)suse.com Reporter: i(a)guoyunhe.me QA Contact: screening-team-bugs(a)suse.de Found By: --- Blocker: --- Most openSUSE's web server packages work out-of-box. For example, you can do sudo zypper in apache2 sudo systemctl start apache2 But when it comes with php7-fpm, it will fail: sudo zypper in php7-fpm sudo systemctl start php7-fpm This is because here is no /etc/php7/fpm/php-fpm.conf I have to manually create it from the default config file: cp php-fpm.conf.default php-fpm.conf Hope that the initial config can be created when installing the package. So users can save some time. -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1193261] Leap15.3: Inkscape won´t start
by bugzilla_noreply＠suse.com 03 Dec '21

03 Dec '21

https://bugzilla.suse.com/show_bug.cgi?id=1193261 https://bugzilla.suse.com/show_bug.cgi?id=1193261#c1 Yifan Jiang <yfjiang(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED CC| |yfjiang(a)suse.com Resolution|--- |DUPLICATE --- Comment #1 from Yifan Jiang <yfjiang(a)suse.com> --- Hello Ralf, it sounds like a duplication of a bug reported slightly earlier. Let's trace it there. *** This bug has been marked as a duplicate of bug 1193183 *** -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1193183] inkscape-1.1.1-lp153.87.2 is not working
by bugzilla_noreply＠suse.com 03 Dec '21

03 Dec '21

https://bugzilla.suse.com/show_bug.cgi?id=1193183 https://bugzilla.suse.com/show_bug.cgi?id=1193183#c3 Yifan Jiang <yfjiang(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |saubernix(a)gmx.de --- Comment #3 from Yifan Jiang <yfjiang(a)suse.com> --- *** Bug 1193261 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1193183] inkscape-1.1.1-lp153.87.2 is not working
by bugzilla_noreply＠suse.com 03 Dec '21

03 Dec '21

https://bugzilla.suse.com/show_bug.cgi?id=1193183 https://bugzilla.suse.com/show_bug.cgi?id=1193183#c2 Yifan Jiang <yfjiang(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |yfjiang(a)suse.com --- Comment #2 from Yifan Jiang <yfjiang(a)suse.com> --- I feel the problem is triggered by the change of directory holding the library, and inkscape relies on rpath to define the run time library path. However, cmake used by inkscape skips RPATH in Leap, so the new path is not found. See line#39 at: https://build.opensuse.org/package/view_file/openSUSE:Leap:15.3:Update/cmak… I feel enabling the macro would make sense for inkscape now, let's see if the fix is acceptable: https://build.opensuse.org/request/show/935422 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1193172] systemd[1]: klog.service: Failed with result 'exit-code'.
by bugzilla_noreply＠suse.com 03 Dec '21

03 Dec '21

https://bugzilla.suse.com/show_bug.cgi?id=1193172 https://bugzilla.suse.com/show_bug.cgi?id=1193172#c18 Suse User <suseino(a)riseup.net> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(suseino(a)riseup.ne | |t) | --- Comment #18 from Suse User <suseino(a)riseup.net> --- Johannes, I changed my local klog.service and klogd.service to match those from the link you provided. I commented manuallly the lines which are not present in your files. Then I rebooted. Result: the error messages are gone and klog.service starts normally now. Here is the changed configuration which works: # grep -E '^#?Protect' klog*.service klog.service:ProtectSystem=full klog.service:ProtectHome=true klog.service:ProtectHostname=true klog.service:#ProtectClock=true klog.service:ProtectKernelTunables=true klog.service:ProtectKernelModules=true klog.service:#ProtectKernelLogs=true klog.service:ProtectControlGroups=true klogd.service:ProtectSystem=full klogd.service:ProtectHome=true klogd.service:ProtectHostname=true klogd.service:ProtectClock=true klogd.service:ProtectKernelTunables=true klogd.service:ProtectKernelModules=true klogd.service:#ProtectKernelLogs=true klogd.service:ProtectControlGroups=true -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1189673] New: windows:mingw:win{32|64}/mingw{32|64}-python: outdated version
by bugzilla_noreply＠suse.com 03 Dec '21

03 Dec '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1189673 Bug ID: 1189673 Summary: windows:mingw:win{32|64}/mingw{32|64}-python: outdated version 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: --- A student working with the gdb for Windows on a GSOC project mentioned that gdb is still using python 2.6.9 which has been end of life since 2013, according to https://www.python.org/dev/peps/pep-0361/#release-lifespan. The version should be updated. -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1188379] New: windows:mingw:win{32|64}/mingw{32|64}-texlive builds broken
by bugzilla_noreply＠suse.com 03 Dec '21

03 Dec '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1188379 Bug ID: 1188379 Summary: windows:mingw:win{32|64}/mingw{32|64}-texlive builds broken 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: --- After the update to mingwxx-header to version 9 the mentioned package (https://build.opensuse.org/package/show/windows:mingw:win32/mingw32-texlive) does not build anymore and should be fixed. -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1193330] Error booting a Lenovo Legion laptop with a Leap 15.3 KDE live USB stick
by bugzilla_noreply＠suse.com 03 Dec '21

03 Dec '21

https://bugzilla.suse.com/show_bug.cgi?id=1193330 https://bugzilla.suse.com/show_bug.cgi?id=1193330#c2 --- Comment #2 from Ralf Habacker <ralf.habacker(a)freenet.de> --- Created attachment 854271 --> https://bugzilla.suse.com/attachment.cgi?id=854271&action=edit Output from journalctl with mentioned debug settings -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1193354] New: Stop job for network manager never finishes, preventing system from shutting down
by bugzilla_noreply＠suse.com 03 Dec '21

03 Dec '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1193354 Bug ID: 1193354 Summary: Stop job for network manager never finishes, preventing system from shutting down Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.3 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Network Assignee: screening-team-bugs(a)suse.de Reporter: krystof186(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- When I shutdown the system (I have plymouth disabled), the last thing I see in the logs is "A stop job is running for network manager". Sometimes, the system reboots just fine without showing this message, however, if this log message shows up, then the stop job never finishes, preventing the system from shutting down forcing me to turn off the computer via hard shutdown (power button press). I don't know where the log messages are located, but I can try to get them if they are needed. -- You are receiving this mail because: You are on the CC list for the bug.

1 0