October 2021 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1186875] New: GNOME PackageKit updater (gpk-update-viewer) default window size makes no sense and it does not remember custom window sizes
by bugzilla_noreply＠suse.com 08 Oct '21

08 Oct '21

https://bugzilla.suse.com/show_bug.cgi?id=1186875 Bug ID: 1186875 Summary: GNOME PackageKit updater (gpk-update-viewer) default window size makes no sense and it does not remember custom window sizes Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.3 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: GNOME Assignee: gnome-bugs(a)suse.de Reporter: sknorr(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- gpk-update-viewer is installed by default on openSUSE GNOME systems and periodically shows notifications about package updates. Unfortunately, it does have a tons of weird UI bugs that not only make the software feel unfinished but also make the desktop itself feel unpolished. One of them is the utterly weird window sizing behavior. You might say that is just an enhancement request, except it is pretty maddening. * By default, gpk-update-viewer always runs in full-screen mode. Given the content displayed in the window, that is unnecessarily large. Package names are displayed on the far left, package sizes on the far right. * If you go out of full-screen mode, e.g. by pressing Super+arrow-down, you get a window that is so small that basically no content fits in it. Also not useful. * Ok, so you manually resize the window to a useful size, i.e. a long, fairly narrow window, as is known from the old Ubuntu updater [1]. However, the next time you start gpk-package-viewer, it starts in full-screen mode again and if you press Super+arrow-down it resizes to a uselessly small size again. None of this is appropriate behavior for a default system component that users periodically have to interact with and which can't be uninstalled without also uninstalling important GNOME patterns. Please update to the following behavior: * Start gpk-update-viewer with a useful, non-fullscreen size. E.g. w=600 x h=800 (lower height on small screens). * Remember user-configured screen sizes on next start. [1] https://www.cyberciti.biz/media/new/faq/2006/05/ubuntu-update-02.jpg -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1171164] AUDIT-TASK: permissions: %_libexecdir changes from /usr/lib to /usr/libexec, affects multiple entries
by bugzilla_noreply＠suse.com 08 Oct '21

08 Oct '21

https://bugzilla.suse.com/show_bug.cgi?id=1171164 https://bugzilla.suse.com/show_bug.cgi?id=1171164#c45 Matthias Gerstner <matthias.gerstner(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |RESOLVED Resolution|--- |FIXED --- Comment #45 from Matthias Gerstner <matthias.gerstner(a)suse.com> --- I think we have this mostly under control now. One of the last unmigrated packages was mgetty with faxq-helper. I submitted a buildsystem patch to the package a while ago and the change is effective now. Closing this bug as fixed. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1189495] %autopatch rpm macro does not work
by bugzilla_noreply＠suse.com 08 Oct '21

08 Oct '21

https://bugzilla.suse.com/show_bug.cgi?id=1189495 https://bugzilla.suse.com/show_bug.cgi?id=1189495#c1 --- Comment #1 from Michael Schr�der <mls(a)suse.com> --- I think this is something for rpm-config-SUSE. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1186875] GNOME PackageKit updater (gpk-update-viewer) default window size makes no sense and it does not remember custom window sizes
by bugzilla_noreply＠suse.com 08 Oct '21

08 Oct '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1186875 http://bugzilla.opensuse.org/show_bug.cgi?id=1186875#c2 Roi C. <pureacetone(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |CONFIRMED CC| |pureacetone(a)gmail.com --- Comment #2 from Roi C. <pureacetone(a)gmail.com> --- It was reported to gnome-packagekit mantainers here: https://gitlab.gnome.org/GNOME/gnome-packagekit/-/issues/3 It should be reported that it still happens in version 3.32 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1190387] New: rpmlint: wrong warning for missing Requires
by bugzilla_noreply＠suse.com 08 Oct '21

08 Oct '21

https://bugzilla.suse.com/show_bug.cgi?id=1190387 Bug ID: 1190387 Summary: rpmlint: wrong warning for missing Requires Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Development Assignee: screening-team-bugs(a)suse.de Reporter: kukuk(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- pam-devel.x86_64: W: missing-dependency-on pam*/pam-libs/libpam* = 1.5.2 But pam-devel has as requires: "pam = 1.5.2" -- You are receiving this mail because: You are on the CC list for the bug.

1 6

[Bug 1191351] Fix missing methods for software installation process
by bugzilla_noreply＠suse.com 08 Oct '21

08 Oct '21

https://bugzilla.suse.com/show_bug.cgi?id=1191351 Knut Alejandro Anderssen Gonz�lez <kanderssen(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- URL| |https://trello.com/c/NnO0Ay | |Zm Assignee|yast2-maintainers(a)suse.de |yast-internal(a)suse.de -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1191347] Yast2 Disk masks all systemd x.mount units
by bugzilla_noreply＠suse.com 08 Oct '21

08 Oct '21

https://bugzilla.suse.com/show_bug.cgi?id=1191347 Ancor Gonzalez Sosa <ancor(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |CONFIRMED URL| |https://trello.com/c/Cs2Lig | |I1 Assignee|yast2-maintainers(a)suse.de |yast-internal(a)suse.de -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1191347] Yast2 Disk masks all systemd x.mount units
by bugzilla_noreply＠suse.com 08 Oct '21

08 Oct '21

https://bugzilla.suse.com/show_bug.cgi?id=1191347 https://bugzilla.suse.com/show_bug.cgi?id=1191347#c4 --- Comment #4 from Ancor Gonzalez Sosa <ancor(a)suse.com> --- (In reply to Ancor Gonzalez Sosa from comment #3) > > Error output: /usr/bin/systemctl --runtime unmask -- �� That's a clearly malformed command! -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1191347] Yast2 Disk masks all systemd x.mount units
by bugzilla_noreply＠suse.com 08 Oct '21

08 Oct '21

https://bugzilla.suse.com/show_bug.cgi?id=1191347 https://bugzilla.suse.com/show_bug.cgi?id=1191347#c3 --- Comment #3 from Ancor Gonzalez Sosa <ancor(a)suse.com> --- (In reply to itteam itteam from comment #2) > Created attachment 853015 [details] > y2log > > YaST2 log as requested Relevant parts. When the Partitioner starts: > y2storage/inhibitors.rb(inhibit):32 inhibit > set udev ANACONDA property > Executing "/usr/bin/udevadm control --property\=ANACONDA\=yes". > Status: 0 > > inhibitors/udisks.rb(inhibit):30 inhibit udisks > inhibit udisks failed The name org.freedesktop.UDisks was not provided by any .service files; caused by 3 sender=org.freedesktop.DBus -> dest=:1.18 serial=3 reply_serial=3 path=; interface=; member= error_name=org.freedesktop.DBus.Error.ServiceUnknown > > inhibitors/systemd_units.rb(inhibit):28 mask systemd units > Executing "/usr/lib/YaST2/bin/mask-systemd-units --mask". > Error output: /usr/bin/systemctl --runtime mask -- '\x2esnapshots.mount' 'boot-grub2-i386\x2dpc.mount' 'boot-grub2-x86_64\x2defi.mount' �� home.mount opt.mount root.mount srv.mount �� tmp.mount usr-local.mount �� var-lock.mount var-run.mount var.mount 'dev-disk-by\x2did-dm\x2dname\x2dsystem\x2dswap.swap' 'dev-disk-by\x2did-dm\x2duuid\x2dLVM\x2dPnp3nScjnUuDzX0DYgfil6F0lPEn549s3JgyVwLOp4GUeNfLLmxBU6neU7IpkVOc.swap' 'dev-disk-by\x2duuid-09c0242a\x2d58b9\x2d4867\x2dac0b\x2df9b2e20092bc.swap' 'dev-dm\x2d1.swap' 'dev-mapper-system\x2dswap.swap' dev-system-swap.swap > Error output: Invalid unit name "��" escaped as "\xe2\x97\x8f" (maybe you should use systemd-escape?). > Error output: Invalid unit name "��" escaped as "\xe2\x97\x8f" (maybe you should use systemd-escape?). > Error output: Invalid unit name "��" escaped as "\xe2\x97\x8f" (maybe you should use systemd-escape?). > Error output: Invalid unit name "��" escaped as "\xe2\x97\x8f" (maybe you should use systemd-escape?). > Error output: Invalid unit name "��" escaped as "\xe2\x97\x8f" (maybe you should use systemd-escape?). > Error output: Unit \xe2\x97\x8f.service does not exist, proceeding anyway. > Error output: Unit \xe2\x97\x8f.service does not exist, proceeding anyway. > Error output: Unit \xe2\x97\x8f.service does not exist, proceeding anyway. > Error output: Unit \xe2\x97\x8f.service does not exist, proceeding anyway. > Error output: Unit \xe2\x97\x8f.service does not exist, proceeding anyway. > Error output: Created symlink /run/systemd/system/\x2esnapshots.mount �� /dev/null. > Error output: Created symlink /run/systemd/system/boot-grub2-i386\x2dpc.mount �� /dev/null. > Error output: Created symlink /run/systemd/system/boot-grub2-x86_64\x2defi.mount �� /dev/null. > Error output: Created symlink /run/systemd/system/\xe2\x97\x8f.service �� /dev/null. > Error output: Created symlink /run/systemd/system/home.mount �� /dev/null. > Error output: Created symlink /run/systemd/system/opt.mount �� /dev/null. > Error output: Created symlink /run/systemd/system/root.mount �� /dev/null. > Error output: Created symlink /run/systemd/system/srv.mount �� /dev/null. > Error output: Created symlink /run/systemd/system/tmp.mount �� /dev/null. > Error output: Created symlink /run/systemd/system/usr-local.mount �� /dev/null. > Error output: Created symlink /run/systemd/system/var-lock.mount �� /dev/null. > Error output: Created symlink /run/systemd/system/var-run.mount �� /dev/null. > Error output: Created symlink /run/systemd/system/var.mount �� /dev/null. > Error output: Created symlink /run/systemd/system/dev-disk-by\x2did-dm\x2dname\x2dsystem\x2dswap.swap �� /dev/null. > Error output: Created symlink /run/systemd/system/dev-disk-by\x2did-dm\x2duuid\x2dLVM\x2dPnp3nScjnUuDzX0DYgfil6F0lPEn549s3JgyVwLOp4GUeNfLLmxBU6neU7IpkVOc.swap �� /dev/null. > Error output: Created symlink /run/systemd/system/dev-disk-by\x2duuid-09c0242a\x2d58b9\x2d4867\x2dac0b\x2df9b2e20092bc.swap �� /dev/null. > Error output: Created symlink /run/systemd/system/dev-dm\x2d1.swap �� /dev/null. > Error output: Created symlink /run/systemd/system/dev-mapper-system\x2dswap.swap �� /dev/null. > Error output: Created symlink /run/systemd/system/dev-system-swap.swap �� /dev/null. > Status: 0 When the Partitioner quits: > y2storage/inhibitors.rb(uninhibit):40 uninhibit > unmask systemd units > Executing "/usr/lib/YaST2/bin/mask-systemd-units --unmask". > Error output: /usr/bin/systemctl --runtime unmask -- �� > Error output: Invalid unit name "��" escaped as "\xe2\x97\x8f" (maybe you should use systemd-escape?). > Error output: Invalid unit name "��" escaped as "\xe2\x97\x8f" (maybe you should use systemd-escape?). > Error output: Invalid unit name "��" escaped as "\xe2\x97\x8f" (maybe you should use systemd-escape?). > Error output: Invalid unit name "��" escaped as "\xe2\x97\x8f" (maybe you should use systemd-escape?). > Error output: Invalid unit name "��" escaped as "\xe2\x97\x8f" (maybe you should use systemd-escape?). > Error output: Invalid unit name "��" escaped as "\xe2\x97\x8f" (maybe you should use systemd-escape?). > Error output: Invalid unit name "��" escaped as "\xe2\x97\x8f" (maybe you should use systemd-escape?). > Error output: Invalid unit name "��" escaped as "\xe2\x97\x8f" (maybe you should use systemd-escape?). > Error output: Invalid unit name "��" escaped as "\xe2\x97\x8f" (maybe you should use systemd-escape?). > Error output: Invalid unit name "��" escaped as "\xe2\x97\x8f" (maybe you should use systemd-escape?). > Error output: Invalid unit name "��" escaped as "\xe2\x97\x8f" (maybe you should use systemd-escape?). > Error output: Invalid unit name "��" escaped as "\xe2\x97\x8f" (maybe you should use systemd-escape?). > Error output: Invalid unit name "��" escaped as "\xe2\x97\x8f" (maybe you should use systemd-escape?). > Error output: Invalid unit name "��" escaped as "\xe2\x97\x8f" (maybe you should use systemd-escape?). > Error output: Invalid unit name "��" escaped as "\xe2\x97\x8f" (maybe you should use systemd-escape?). > Error output: Invalid unit name "��" escaped as "\xe2\x97\x8f" (maybe you should use systemd-escape?). > Error output: Invalid unit name "��" escaped as "\xe2\x97\x8f" (maybe you should use systemd-escape?). > Error output: Invalid unit name "��" escaped as "\xe2\x97\x8f" (maybe you should use systemd-escape?). > Error output: Invalid unit name "��" escaped as "\xe2\x97\x8f" (maybe you should use systemd-escape?). > Error output: Invalid unit name "��" escaped as "\xe2\x97\x8f" (maybe you should use systemd-escape?). > Error output: Invalid unit name "��" escaped as "\xe2\x97\x8f" (maybe you should use systemd-escape?). > Error output: Invalid unit name "��" escaped as "\xe2\x97\x8f" (maybe you should use systemd-escape?). > Error output: Invalid unit name "��" escaped as "\xe2\x97\x8f" (maybe you should use systemd-escape?). > Error output: Removed /run/systemd/system/\xe2\x97\x8f.service. > Status: 0 > > inhibitors/mdadm_auto_assembly.rb(uninhibit):41 unset udev ANACONDA property > Executing "/usr/bin/udevadm control --property\=ANACONDA\=". > Status: 0 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1190817] Error: Subprocess failed. Error: RPM failed: warning: Found BDB Packages database while attempting ndb backend: using bdb_ro backend.
by bugzilla_noreply＠suse.com 08 Oct '21

08 Oct '21

https://bugzilla.suse.com/show_bug.cgi?id=1190817 https://bugzilla.suse.com/show_bug.cgi?id=1190817#c5 --- Comment #5 from Michael Andres <ma(a)suse.com> --- @Joy Ghosh: Would you mind attaching your /var/log/zypp/history file, so we can check why you got the 'rpm-ndb' package at all. -- You are receiving this mail because: You are on the CC list for the bug.

1 0