openSUSE Bugs January 2019

bugs@lists.opensuse.org

1 participants
4246 discussions

[Bug 993011] New: [openQA] CTRL-ALT-DEL does not show the logout dialog
by bugzilla_noreply＠novell.com 26 Oct '22

26 Oct '22

http://bugzilla.opensuse.org/show_bug.cgi?id=993011 Bug ID: 993011 Summary: [openQA] CTRL-ALT-DEL does not show the logout dialog Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: KDE Workspace (Plasma) Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: dimstar(a)opensuse.org QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Seen by openQA tests, e.g. https://openqa.opensuse.org/tests/239654 After the system was upgraded from openSUSE 13.2 to Tumbleweed (20160808, first to have plasma 5.7.2), the logout dialog no longer shows when pressing ctrl-alt-del This appears on updates performed using the DVD and boot from the Network CD, but seems not to happen in the case when the system was updated using zdup. The tests had been re-run a couple times. -- You are receiving this mail because: You are on the CC list for the bug.

2 1

[Bug 941884] New: libcamgm fails test suite due to expired certificates
by bugzilla_noreply＠novell.com 26 Oct '22

26 Oct '22

http://bugzilla.opensuse.org/show_bug.cgi?id=941884 Bug ID: 941884 Summary: libcamgm fails test suite due to expired certificates Classification: openSUSE Product: openSUSE Factory Version: 201505* Hardware: Other OS: Other Status: NEW Severity: Major Priority: P5 - None Component: YaST2 Assignee: yast2-maintainers(a)suse.de Reporter: dimstar(a)opensuse.org QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- since recently, libcamgm no longer passes the test suite... the build lo ends with: [...] [ 358s] Running ListTest... [ 358s] Output doesn't match expected data: [ 358s] --- ./single.out/ListTest.out 2014-04-12 17:19:43.000000000 +0000 [ 358s] +++ ./single.out/out/ListTest.out 2015-08-16 18:11:50.226671071 +0000 [ 358s] @@ -125,7 +125,7 @@ [ 358s] country = DE [ 358s] emailAddress = suse(a)suse.de [ 358s] serial = 07 [ 358s] -status = Valid [ 358s] +status = Expired [ 358s] New Entry [ 358s] certificate = 08:40717a16174dc4d516f6fa7ee8eeb18c-1124792802 [ 358s] commonName = Full Test Certificate [ 358s] @@ -153,7 +153,7 @@ [ 358s] country = DE [ 358s] emailAddress = suse(a)suse.de [ 358s] serial = 0B [ 358s] -status = Valid [ 358s] +status = Expired [ 358s] getCertificateList successfully executed [ 358s] =================== end List tests ======================== [ 358s] DONE [ 358s] FAIL: ListTest [...] [ 364s] Running VerifyTest... [ 365s] Output doesn't match expected data: [ 365s] --- ./single.out/VerifyTest.out 2014-04-12 17:19:43.000000000 +0000 [ 365s] +++ ./single.out/out/VerifyTest.out 2015-08-16 18:11:57.086773026 +0000 [ 365s] @@ -6,10 +6,10 @@ [ 365s] 04: Verify failed: Found revoked certificate [ 365s] 05: Verify failed: Found revoked certificate [ 365s] 06: Verify failed: Found revoked certificate [ 365s] -07: Verify success [ 365s] +07: Verify failed: Found expired certificate [ 365s] 08: Verify failed: Found expired certificate [ 365s] 09: Verify failed: Found revoked certificate [ 365s] 0A: Verify failed: Found expired certificate [ 365s] -0B: Verify success [ 365s] +0B: Verify failed: Found expired certificate [ 365s] =================== end List tests ======================== [ 365s] DONE [ 365s] FAIL: VerifyTest [...] libcamgm is a dependency to yast2-ca-management, which in turn is required by yast2-auth-server (which is why a delete request for libcamgm back in May could not be fullfilled) This whole thing is a ring, packae, causing all stagings to fail, hence I mark it major -- You are receiving this mail because: You are on the CC list for the bug.

2 6

[Bug 1002565] New: can't install ruby2.2-rubygem-rhc-testsuite-1.35.3-1.5.x86_64
by bugzilla_noreply＠novell.com 26 Oct '22

26 Oct '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1002565 Bug ID: 1002565 Summary: can't install ruby2.2-rubygem-rhc-testsuite-1.35.3-1.5.x86_64 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: --- can't install ruby2.2-rubygem-rhc-testsuite-1.35.3-1.5.x86_64 zypper in ruby2.2-rubygem-rhc-testsuite-1.35.3-1.5.x86_64 Loading repository data... Reading installed packages... Resolving package dependencies... >Problem: nothing provides rubygem(ruby:2.2.0:commander) < 4.3.0 needed by ruby2.2-rubygem-rhc-1.35.3-1.5.x86_64 > Solution 1: do not install ruby2.2-rubygem-rhc-testsuite-1.35.3-1.5.x86_64 > Solution 2: break ruby2.2-rubygem-rhc-1.35.3-1.5.x86_64 by ignoring some of its dependencies -- You are receiving this mail because: You are on the CC list for the bug.

2 2

[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 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

← Newer
1
...
4
5
6
7
8
9
10
...
425
Older →

Jump to page:

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

openSUSE Bugs January 2019