May 2019 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1066408] New: Deadbeef contains an invalid appdata.xml file
by bugzilla_noreply＠novell.com 26 Oct '22

26 Oct '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1066408 Bug ID: 1066408 Summary: Deadbeef contains an invalid appdata.xml file Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: dimstar(a)opensuse.org QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- The package deadbeef ships with an appdata.xml file (to show in socftware centers), but the file is invalid. (appstream-builder:17416): As-WARNING **: ignoring description '<description><_p>DeaDBeeF (as in 0xDEADBEEF)…' from ./tmp/deadbeef-0.7.2-4.2/usr/share/appdata/deadbeef.appdata.xml: Unknown tag '_p' Seems upstream prepared the file for translation, but then did not pass it through the translation process -- You are receiving this mail because: You are on the CC list for the bug.

2 2

[Bug 1023737] New: openSUSE:Factory/golang-google-golangorg-appengine fails to build
by bugzilla_noreply＠novell.com 26 Oct '22

26 Oct '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1023737 Bug ID: 1023737 Summary: openSUSE:Factory/golang-google-golangorg-appengine fails to build Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: dimstar(a)opensuse.org QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- The package golang-google-golangorg-appengine fails to build in openSUSE:Factory. Earlier notifications by email to the bugowner and Maintainer have remained without reaction / fix. If the package is not being fixed within 2 weeks, it will be scheduled for removal from Tumbleweed -- You are receiving this mail because: You are on the CC list for the bug.

2 1

[Bug 1023734] New: openSUSE:Factory/golang-org-x-oauth2 fails to build
by bugzilla_noreply＠novell.com 26 Oct '22

26 Oct '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1023734 Bug ID: 1023734 Summary: openSUSE:Factory/golang-org-x-oauth2 fails to build Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: dimstar(a)opensuse.org QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- The package golang-org-x-oauth2 fails to build in openSUSE:Factory. Earlier notifications by email to the bugowner and Maintainer have remained without reaction / fix. If the package is not being fixed within 2 weeks, it will be scheduled for removal from Tumbleweed -- You are receiving this mail because: You are on the CC list for the bug.

2 1

[Bug 971006] New: rpmlint: no-dependency-on perl-base 5.22.1
by bugzilla_noreply＠novell.com 26 Oct '22

26 Oct '22

http://bugzilla.opensuse.org/show_bug.cgi?id=971006 Bug ID: 971006 Summary: rpmlint: no-dependency-on perl-base 5.22.1 Classification: openSUSE Product: openSUSE Tumbleweed Version: 2015* Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: dimstar(a)opensuse.org QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- rpmlint does not understand how openSUSE specifies perl dependencies and falsly reports: no-dependency-on perl-base 5.22.1 in openSUSE, we use the macro %perl_requires which translates to: Requires: perl(:MODULE_COMPAT_5.22.1) It would be great to get this recognized as dependency being satisfied -- You are receiving this mail because: You are on the CC list for the bug.

2 3

[Bug 1132118] New: Xindy does not run due to incompatible CLISP runtime
by bugzilla_noreply＠novell.com 25 Oct '22

25 Oct '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1132118 Bug ID: 1132118 Summary: Xindy does not run due to incompatible CLISP runtime Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: 64bit OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: christian-david(a)web.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- xindy does not run what can be tested with $ xindy --version xindy release: 2.5.1 xindy script version: 1.18 /usr/lib64/clisp-2.49.92/base/lisp.run: initialization file `/usr/lib64/xindy/xindy.mem' was not created by this version of CLISP runtime Same error happens if xindy is used for a “real” task. -- You are receiving this mail because: You are on the CC list for the bug.

2 13

[Bug 1041742] New: Filetriggers do not fire (reliably)
by bugzilla_noreply＠novell.com 25 Oct '22

25 Oct '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1041742 Bug ID: 1041742 Summary: Filetriggers do not fire (reliably) Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: libzypp Assignee: zypp-maintainers(a)forge.provo.novell.com Reporter: dimstar(a)opensuse.org QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- In GNOME:Next, we started experimenting with file triggers (with the goal to lower the number of bugs based on missing post scripts) As a sample, I implemented this trigger (on glib2-tools): %transfiletriggerin -n glib2-tools -- %{_datadir}/glib-2.0/schemas %{_bindir}/glib-compile-schemas %{_datadir}/glib-2.0/schemas %transfiletriggerpostun -n glib2-tools -- %{_datadir}/glib-2.0/schemas %{_bindir}/glib-compile-schemas %{_datadir}/glib-2.0/schemas The trigger is confirmed to work, but in some cases, it seems not to fire, eg on the package 'gdm' (which is currently the reason why http://download.opensuse.org/repositories/GNOME:/Medias/images/iso/?P=GNOME… fails to boot to desktop) zypper in --no-recommends gdm => the file trigger is not executed rpm -i gdm-3.24.1.rpm => the trigger actually seems to work (which is why I file it against libzypp) This currently stops us from moving forward and proposing file triggers to be more widely used (even though I think they can solve quite some packaging bugs) The packages in question for testing are all in the GNOME:Next repository (glib2 which has the trigger, it has the %glib2_gsettings_schema_post set to %nil, so packages that use it in their post script only get a dummy - once the implementation is complete, we will of course go and clean those out completely) -- You are receiving this mail because: You are on the CC list for the bug.

2 28

[Bug 1093168] New: pacemaker: using service template in preun/postun
by bugzilla_noreply＠novell.com 24 Oct '22

24 Oct '22

http://bugzilla.suse.com/show_bug.cgi?id=1093168 Bug ID: 1093168 Summary: pacemaker: using service template in preun/postun Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: High Availability Assignee: ha-bugs(a)suse.de Reporter: ro(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- you can not used a service template (foo@.service) without parameter in a specfile with the %service_add/del macros: %preun cts %service_del_preun pacemaker-cts-dummyd@.service %postun cts %service_del_postun pacemaker-cts-dummyd@.service this will just result in errors during uninstall of the package: (1/1) Removing pacemaker-cts-1.1.18+20180430.b12c320f5-1.4.noarch ........[done] Additional rpm output: Failed to stop pacemaker-cts-dummyd@.service: Unit name pacemaker-cts-dummyd@.service is missing the instance name. See system logs and 'systemctl status pacemaker-cts-dummyd@.service' for details. Failed to get load state of pacemaker-cts-dummyd@.service: Unit name pacemaker-cts-dummyd@.service is neither a valid invocation ID nor unit name. -- You are receiving this mail because: You are on the CC list for the bug.

2 3

[Bug 1115512] New: pam-config does not find (nor load) pam_yubico.so
by bugzilla_noreply＠novell.com 24 Oct '22

24 Oct '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1115512 Bug ID: 1115512 Summary: pam-config does not find (nor load) pam_yubico.so Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: fred.blaise(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0 Build Identifier: After installed pam_yubico, and adding the following line in /etc/pam.d/common-auth, running `sudo pam-config --update` fails with `/etc/pam.d/common-auth-pc: Unknown module pam_yubico.so, ignored!` The module never appears in the --list-modules either. Reproducible: Always Steps to Reproduce: 1. sudo zypper in pam_yubico 2. sudo ldconfig (or reboot) 3. Amend /etc/pam.d/common-auth-pc to add pam_yubico as requirement 4. Run pam-config --update and get ignore message. Actual Results: /etc/pam.d/common-auth-pc: Unknown module pam_yubico.so, ignored! Expected Results: Module loads and I can use my yubikey with pam. -- You are receiving this mail because: You are on the CC list for the bug.

2 1

[Bug 1088177] New: Default Active Titlebar color on openSUSEdark and openSUSEdarkalternate colorchemes
by bugzilla_noreply＠novell.com 23 Oct '22

23 Oct '22

http://bugzilla.suse.com/show_bug.cgi?id=1088177 Bug ID: 1088177 Summary: Default Active Titlebar color on openSUSEdark and openSUSEdarkalternate colorchemes Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Enhancement Priority: P5 - None Component: KDE Workspace (Plasma) Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: andretiago(a)outlook.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 766009 --> http://bugzilla.suse.com/attachment.cgi?id=766009&action=edit Titlebar active color Default Active Titlebar color of openSUSEdark and openSUSEdarkalternate color schemes looks out of place and it's hard to read. https://i.imgur.com/vshYSxz.png I think the default color should be replaced -- You are receiving this mail because: You are on the CC list for the bug.

2 1

[Bug 1008674] New: Login difficulties with LightDM 1.20
by bugzilla_noreply＠novell.com 22 Oct '22

22 Oct '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1008674 Bug ID: 1008674 Summary: Login difficulties with LightDM 1.20 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: SUSE Other Status: NEW Severity: Critical Priority: P5 - None Component: Basesystem Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: Markus.Elfring(a)web.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Today I dared to update the display manager to the version “LightDM 1.20.0-1.1”. Unfortunately, I observed that the corresponding graphical login did not work as expected. The information “exist status: 1” was recorded in the systemd journal. -- You are receiving this mail because: You are on the CC list for the bug.

2 10