Yast - Software Management keep crashing on packages installation/update

monavi · September 15, 2021, 1:58am

Hi all, I’m using leap 15.3 as VM on Parallels.

At the moment I am unable to update and/or install new packages. This happens on both GUI and CLI.

After I select all packages I need, the next window, that one with the two progress bars, after like 1-2 seconds closes itself with no feedback.

I tried all these commands, as root:

zypper clean -a
rpmdb --rebuilddb

------

All repositories have been cleaned up.

or

zypper cc -a
zypper ref
zypper dup

-------

All repositories have been cleaned up.
Retrieving repository 'Non-OSS' metadata ......................................................................................................................................................................................................................................................................................[done]
Building repository 'Non-OSS' cache ...........................................................................................................................................................................................................................................................................................[done]
Retrieving repository 'Update Non-OSS' metadata ...............................................................................................................................................................................................................................................................................[done]
Building repository 'Update Non-OSS' cache ....................................................................................................................................................................................................................................................................................[done]
Retrieving repository 'OSS' metadata ..........................................................................................................................................................................................................................................................................................[done]
Building repository 'OSS' cache ...............................................................................................................................................................................................................................................................................................[done]
Retrieving repository 'Update' metadata .......................................................................................................................................................................................................................................................................................[done]
Building repository 'Update' cache ............................................................................................................................................................................................................................................................................................[done]
All repositories have been refreshed.
Loading repository data...
Reading installed packages...
Warning: You are about to do a distribution upgrade with all enabled repositories. Make sure these repositories are compatible before you continue. See 'man zypper' for more information about this command.
Computing distribution upgrade...
Nothing to do.

Then I opened the yast log, and these are the latest row right before the crash

2021-09-15 01:38:02 <1> OpenSuse(6031) [librpmDb] librpmDb.cc(blockAccess):316 Block access
2021-09-15 01:38:02 <1> OpenSuse(6031) [librpmDb] RpmDb.cc(closeDatabase):373 closeDatabase: RpmDb'()']
2021-09-15 01:38:02 <1> OpenSuse(6031) [zypp] TargetImpl.cc(~TargetImpl):927 Targets closed
2021-09-15 01:38:02 <1> OpenSuse(6031) [librpmDb] RpmDb.cc(~RpmDb):240 ~RpmDb()
2021-09-15 01:38:02 <1> OpenSuse(6031) [librpmDb] RpmDb.cc(~RpmDb):243 ~RpmDb() end
2021-09-15 01:38:02 <1> OpenSuse(6031) [Pkg] PkgFunctions.cc(~PkgFunctions):161 Zypp pointer released
2021-09-15 01:38:02 <1> OpenSuse(6031) [zypp++] MediaSetAccess.cc(release):487 Releasing all media IDs held by this MediaSetAccess
2021-09-15 01:38:02 <1> OpenSuse(6031) [zypp++] MediaSetAccess.cc(release):487 Releasing all media IDs held by this MediaSetAccess
2021-09-15 01:38:02 <1> OpenSuse(6031) [zypp++] MediaSetAccess.cc(release):487 Releasing all media IDs held by this MediaSetAccess
2021-09-15 01:38:02 <1> OpenSuse(6031) [zypp++] MediaSetAccess.cc(release):487 Releasing all media IDs held by this MediaSetAccess
2021-09-15 01:38:02 <1> OpenSuse(6031) [zypp++] MediaSetAccess.cc(release):487 Releasing all media IDs held by this MediaSetAccess
2021-09-15 01:38:02 <2> OpenSuse(6031) [qt-ui] YQUI.cc(qMessageHandler):652 <libqt-warning> QObject::~QObject: Timers cannot be stopped from another thread
2021-09-15 01:38:02 <1> OpenSuse(6031) [Y2Ruby] binary/YRuby.cc(~YRuby):117 Shutting down ruby interpreter.

These are my repos

# | Alias              | Name           | Enabled | GPG Check | Refresh | URI
--+--------------------+----------------+---------+-----------+---------+-----------------------------------------------------------------------------
1 | non-oss            | Non-OSS        | Yes     | (r ) Yes  | Yes     | http://download.opensuse.org/distribution/leap/15.3/repo/non-oss/
2 | non-oss_1          | Update Non-OSS | Yes     | (r ) Yes  | Yes     | http://download.opensuse.org/update/leap/15.3/non-oss/
3 | openSUSE_Leap_15.3 | snappy         | No      | ----      | ----    | https://download.opensuse.org/repositories/system:/snappy/openSUSE_Leap_15.3
4 | oss                | OSS            | Yes     | (r ) Yes  | Yes     | http://download.opensuse.org/distribution/leap/15.3/repo/oss/
5 | oss_1              | Update         | Yes     | (r ) Yes  | Yes     | http://download.opensuse.org/update/leap/15.3/oss/

How can I fix this issue? Thank you all

mrmazda · September 15, 2021, 4:37am

I suppose this could be related to two repos you are missing:

# cat /etc/zypp/repos.d/repo-backports-update.repo
[repo-backports-update]
name=Update repository of openSUSE Backports
enabled=1
autorefresh=1
baseurl=http://download.opensuse.org/update/leap/$releasever/backports/
path=/
type=rpm-md
keeppackages=0

# cat /etc/zypp/repos.d/repo-sle-update.repo
[repo-sle-update]
name=Update repository with updates from SUSE Linux Enterprise 15
enabled=1
autorefresh=1
baseurl=http://download.opensuse.org/update/leap/$releasever/sle/
path=/
type=rpm-md
keeppackages=0

If you save these two files to /etc/zypp/repos.d/ and run sudo zypper ref; sudo zypper up maybe the problem would solve itself.

I don’t know what your snappy repo is about. I never had one. Maybe something from it broke something before it was disabled.

Sauerland · September 15, 2021, 7:53am

Ps:
zypper dup is not the same as zypper up.
On Leap use only zypper up for updating your system.

But as said, 2 Repos are missing.

monavi · September 16, 2021, 12:09am

mrmazda:

I suppose this could be related to two repos you are missing:
# cat /etc/zypp/repos.d/repo-backports-update.repo
[repo-backports-update]
name=Update repository of openSUSE Backports
enabled=1
autorefresh=1
baseurl=http://download.opensuse.org/update/leap/$releasever/backports/
path=/
type=rpm-md
keeppackages=0
# cat /etc/zypp/repos.d/repo-sle-update.repo
[repo-sle-update]
name=Update repository with updates from SUSE Linux Enterprise 15
enabled=1
autorefresh=1
baseurl=http://download.opensuse.org/update/leap/$releasever/sle/
path=/
type=rpm-md
keeppackages=0
If you save these two files to /etc/zypp/repos.d/ and run sudo zypper ref; sudo zypper up maybe the problem would solve itself.

I don’t know what your snappy repo is about. I never had one. Maybe something from it broke something before it was disabled.

Thanks for your reply.

I added these two repos and now these are my repos:

# | Alias              | Name           | Enabled | GPG Check | Refresh | URI
--+--------------------+----------------+---------+-----------+---------+-----------------------------------------------------------------------------
1 | backports          | backports      | Yes     | (r ) Yes  | Yes     | http://download.opensuse.org/update/leap/15.3/backports/
2 | non-oss            | Non-OSS        | Yes     | (r ) Yes  | Yes     | http://download.opensuse.org/distribution/leap/15.3/repo/non-oss/
3 | non-oss_1          | Update Non-OSS | Yes     | (r ) Yes  | Yes     | http://download.opensuse.org/update/leap/15.3/non-oss/
4 | openSUSE_Leap_15.3 | snappy         | No      | ----      | ----    | https://download.opensuse.org/repositories/system:/snappy/openSUSE_Leap_15.3
5 | oss                | OSS            | Yes     | (r ) Yes  | Yes     | http://download.opensuse.org/distribution/leap/15.3/repo/oss/
6 | oss_1              | Update         | Yes     | (r ) Yes  | Yes     | http://download.opensuse.org/update/leap/15.3/oss/
7 | sle                | sle            | Yes     | (r ) Yes  | Yes     | http://download.opensuse.org/update/leap/15.3/sle/

I also executed ref and up.

Still yast keeps crashing, and the yast logs is still the same.

mrmazda · September 16, 2021, 3:28am

Then there should be no updating left to do. Give the system some time to acquire more updates before trying again.

Which DE are you using? Are you using Wayland? If you switch to a different DE, or to or from Wayland, does it still crash?

monavi · September 17, 2021, 1:04pm

I’m sorry, I’m not an expert of OpenSuse, so I’m not aware of what a DE or Wayland actually are

mrmazda · September 17, 2021, 7:25pm

Desktop Environment (applies to all Linux distros, not just openSUSE), e.g. KDE/Plasma, Gnome, XFCE, IceWM, etc.

DEs run on top of X. X can be either Xorg or Wayland. Whether a DE runs on Xorg or Wayland is selectable via session type selection in the login manager for Gnome and KDE/Plasma sessions.

monavi · September 18, 2021, 10:02pm

Oh cool, I learned a new thing, thanks

So I did

echo $XDG_CURRENT_DESKTOP

And the output was KDE

Should I switch to a new DE?

mrmazda · September 18, 2021, 10:42pm

To narrow down the source of your problem you need to try some different things. DEs are one thing, Wayland vs. Xorg is another. Your login manager has a list to choose from. Try them. See what happens differently. Another is to not log into the GUI, but instead to switch to a vtty to run zypper ref; zypper up.

monavi · September 18, 2021, 11:48pm

My login manager isn’t showing me any DE, I had to change to GNOME via cli :\

By the way, on gnome, the output is not changing at all: yast keeps crashing. I recorded a video as well ( Watch yastcrash | Streamable )

Now I don’t know vtty, is it a virtual terminal? because yast crashes on terminal too

mrmazda · September 19, 2021, 12:47am

If you are in Gnome, Ctrl-Alt-F[2-6] and maybe also Ctrl-Alt-F1, which can behave differently. Gnome should be using vtty7 or maybe 1.

ddtty · September 19, 2021, 3:11pm

A possible way help to diagnose the problem.

In the root, run YAST vi command line, for example,

/sbin/yast2 sw_single

Do what had you done before.
Check that are there error messages shown up in the terminal.

monavi · September 19, 2021, 11:08pm

Ok, I did it on vtty and still it crashes, like this Watch yastcrashvtty | Streamable

DDTTY:

A possible way help to diagnose the problem.

In the root, run YAST vi command line, for example,
/sbin/yast2 sw_single
Do what had you done before.

Check that are there error messages shown up in the terminal.

Thank you for your reply. This is the output

OpenSuse:/ # /sbin/yast2 sw_single

(ruby.ruby2.5:8958): GLib-GIO-CRITICAL **: 22:58:57.087: g_dbus_connection_register_object: assertion 'G_IS_DBUS_CONNECTION (connection)' failed

(ruby.ruby2.5:8958): GLib-GIO-CRITICAL **: 22:58:57.087: g_dbus_connection_register_object: assertion 'G_IS_DBUS_CONNECTION (connection)' failed

(ruby.ruby2.5:8958): GLib-GIO-CRITICAL **: 22:58:57.087: g_dbus_connection_get_unique_name: assertion 'G_IS_DBUS_CONNECTION (connection)' failed

(ruby.ruby2.5:8958): GLib-GIO-CRITICAL **: 22:58:57.116: g_dbus_connection_register_object: assertion 'G_IS_DBUS_CONNECTION (connection)' failed

(ruby.ruby2.5:8958): GLib-GIO-CRITICAL **: 22:58:57.116: g_dbus_connection_register_object: assertion 'G_IS_DBUS_CONNECTION (connection)' failed

(ruby.ruby2.5:8958): GLib-GIO-CRITICAL **: 22:58:57.116: g_dbus_connection_get_unique_name: assertion 'G_IS_DBUS_CONNECTION (connection)' failed
OpenSuse:/ #

I recorded a video about it Watch yastcrashlog | Streamable

mrmazda · September 19, 2021, 11:46pm

I suggest to report a bug:
https://en.opensuse.org/openSUSE:Report_a_YaST_bug
https://en.opensuse.org/openSUSE:Submitting_bug_reports
https://en.opensuse.org/openSUSE:Bug_reporting_FAQ

ddtty · September 20, 2021, 4:35am

monavi:

Ok, I did it on vtty and still it crashes, like this Watch yastcrashvtty | Streamable

Thank you for your reply. This is the output

OpenSuse:/ # /sbin/yast2 sw_single

(ruby.ruby2.5:8958): GLib-GIO-CRITICAL **: 22:58:57.087: g_dbus_connection_register_object: assertion 'G_IS_DBUS_CONNECTION (connection)' failed

(ruby.ruby2.5:8958): GLib-GIO-CRITICAL **: 22:58:57.087: g_dbus_connection_register_object: assertion 'G_IS_DBUS_CONNECTION (connection)' failed

(ruby.ruby2.5:8958): GLib-GIO-CRITICAL **: 22:58:57.087: g_dbus_connection_get_unique_name: assertion 'G_IS_DBUS_CONNECTION (connection)' failed

(ruby.ruby2.5:8958): GLib-GIO-CRITICAL **: 22:58:57.116: g_dbus_connection_register_object: assertion 'G_IS_DBUS_CONNECTION (connection)' failed

(ruby.ruby2.5:8958): GLib-GIO-CRITICAL **: 22:58:57.116: g_dbus_connection_register_object: assertion 'G_IS_DBUS_CONNECTION (connection)' failed

(ruby.ruby2.5:8958): GLib-GIO-CRITICAL **: 22:58:57.116: g_dbus_connection_get_unique_name: assertion 'G_IS_DBUS_CONNECTION (connection)' failed
OpenSuse:/ #

I recorded a video about it Watch yastcrashlog | Streamable

Well~~ from your video I saw that you actually did not install/remove/update any package.
So YAST of course did not do anything and then close.
It is the same behavior for this case on my system.
What happened if you really did the install/remove/update on any package?
Any additional error/failed messages shown on the terminal?