May 2021 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1184399] purge-kernels.service might conflict with other background services using zypper as well
by bugzilla_noreply＠suse.com 04 May '21

04 May '21

https://bugzilla.suse.com/show_bug.cgi?id=1184399 https://bugzilla.suse.com/show_bug.cgi?id=1184399#c4 Michal Suchanek <msuchanek(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Component|Other |libzypp Assignee|msuchanek(a)suse.com |zypp-maintainers(a)suse.de --- Comment #4 from Michal Suchanek <msuchanek(a)suse.com> --- A purge-kernel-service with a workaround can be found here. https://build.opensuse.org/package/rdiff/home:michals/purge-kernels-service… Hopefully we can get some support from zypper so that this can be implemented as a self-contained service file again. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1184948] New: [Build 20210417] Upgrade from 15.x: wrong logo in g-c-c
by bugzilla_noreply＠suse.com 04 May '21

04 May '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1184948 Bug ID: 1184948 Summary: [Build 20210417] Upgrade from 15.x: wrong logo in g-c-c Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other URL: https://openqa.opensuse.org/tests/1704585/modules/gnom e_control_center/steps/11 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: GNOME Assignee: gnome-bugs(a)suse.de Reporter: dimstar(a)opensuse.org QA Contact: qa-bugs(a)suse.de Found By: openQA Blocker: Yes ## Observation openQA test in scenario opensuse-Tumbleweed-DVD-x86_64-upgrade_Leap_15.1_gnome@64bit fails in [gnome_control_center](https://openqa.opensuse.org/tests/1704585/modules/gno… This seems to be limited to upgrade scenario, where the system shows the wrong logo in gnome-control-center (a blurry gnome-foot, it should be the distributor-logo, i.e. 'tumbleweed logo' in this case. ## Test suite description Maintainer: zluo Upgrade test Leap 15.1 to TW ## Reproducible Fails since (at least) Build [20210412](https://openqa.opensuse.org/tests/1697401) ## Expected result Last good: [20210410](https://openqa.opensuse.org/tests/1696339) (or more recent) ## Further details Always latest result in this scenario: [latest](https://openqa.opensuse.org/tests/latest?arch=x86_64&distri=opensus… -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1183168] postgresql13: uninstall fails due to valid script expansion
by bugzilla_noreply＠suse.com 04 May '21

04 May '21

https://bugzilla.suse.com/show_bug.cgi?id=1183168 https://bugzilla.suse.com/show_bug.cgi?id=1183168#c8 --- Comment #8 from Franck Bui <fbui(a)suse.com> --- Is there an existing convention for naming private macros ? -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1183168] postgresql13: uninstall fails due to valid script expansion
by bugzilla_noreply＠suse.com 04 May '21

04 May '21

https://bugzilla.suse.com/show_bug.cgi?id=1183168 https://bugzilla.suse.com/show_bug.cgi?id=1183168#c7 --- Comment #7 from Reinhard Max <max(a)suse.com> --- Thanks, Franc, I will do that. BTW, in RPM a macro name starting with an underscore isn't really a clear sign for it not being meant to be used by packages, think of all the builtin macros for standard directories that start with an underscore. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1185601] Black screen / no screen output after upgrading from 5.11 to 5.12
by bugzilla_noreply＠suse.com 04 May '21

04 May '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1185601 http://bugzilla.opensuse.org/show_bug.cgi?id=1185601#c12 --- Comment #12 from Wolfgang Wander <wwcsmail(a)gmail.com> --- (In reply to Takashi Iwai from comment #11) > Is this only about the laptop display (LCD)? Or are all graphics outputs > gone blank? Good call - the HDMI output on the XPS15 is working. Only the LCD (laptop display) is blank. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1185285] AUDIT-0: systemd homed
by bugzilla_noreply＠suse.com 04 May '21

04 May '21

https://bugzilla.suse.com/show_bug.cgi?id=1185285 https://bugzilla.suse.com/show_bug.cgi?id=1185285#c2 --- Comment #2 from Paolo Perego <paolo.perego(a)suse.com> --- Quick feedback on the PAM module I just finished reviewing. It seems no issues are present. The only think I'd like to mention is that the pam handle was never checked against NULL. I will double check again this issue later on, when finalizing the audit -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1183168] postgresql13: uninstall fails due to valid script expansion
by bugzilla_noreply＠suse.com 04 May '21

04 May '21

https://bugzilla.suse.com/show_bug.cgi?id=1183168 https://bugzilla.suse.com/show_bug.cgi?id=1183168#c6 Franck Bui <fbui(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(fbui(a)suse.com) | --- Comment #6 from Franck Bui <fbui(a)suse.com> --- (In reply to Reinhard Max from comment #5) > I finally got around to look into this again. The problem with > %stop_on_removal was that it stops AND disables the service, but I need to > split these two actions. Stop has to be done in the postgresqlXX-server > packages containing the actual binaries, but disable has to happen in the > postgresql-server (noarch) package that contains the service file. > > I think I can just directly call "systemctl stop" instead of using a here, > because everything else that the macro does is already being handled by my > own scripting. > > Any objections, Franck? Nope, in such (extreme) cases it seems better that you use your own recipe rather than trying to reuse and twist the macros until it fits your needs. > BTW, I am also using %_restart_on_update in the postgresqlXX-server > packages, which still exists, but probably also isn't meant to be used > directly. Are there plans to remove that one as well? I don't think %_restart_on_update will be removed but it's also not meant to be used by packages. Its content or its behavior may change in the future. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1185601] Black screen / no screen output after upgrading from 5.11 to 5.12
by bugzilla_noreply＠suse.com 04 May '21

04 May '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1185601 http://bugzilla.opensuse.org/show_bug.cgi?id=1185601#c11 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(martin.sirringhau |needinfo? |s(a)suse.com) | --- Comment #11 from Takashi Iwai <tiwai(a)suse.com> --- Is this only about the laptop display (LCD)? Or are all graphics outputs gone blank? -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1184325] nscd should not complain every few seconds about missing files because of /usr/etc
by bugzilla_noreply＠suse.com 04 May '21

04 May '21

https://bugzilla.suse.com/show_bug.cgi?id=1184325 https://bugzilla.suse.com/show_bug.cgi?id=1184325#c1 Andreas Schwab <schwab(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from Andreas Schwab <schwab(a)suse.com> --- dup *** This bug has been marked as a duplicate of bug 1163179 *** -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1163179] nscd can't monitor /etc/services after the recent netcfg update
by bugzilla_noreply＠suse.com 04 May '21

04 May '21

https://bugzilla.suse.com/show_bug.cgi?id=1163179 https://bugzilla.suse.com/show_bug.cgi?id=1163179#c16 Andreas Schwab <schwab(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mrueckert(a)suse.com --- Comment #16 from Andreas Schwab <schwab(a)suse.com> --- *** Bug 1184325 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