Yast Online Update and Software Management not working

Hello,

I have gotten OpenSuse Leap 42.1 installed, but I’m having issues with the Yast “Online Update” and “Software Management” tools. Has anyone else experienced this, or know why it is occurring?

When I start those tools they go through the normal phase of updating repository information, then they just disappear as if they had been closed. They were doing this immediately after the install, so I could not update the system using the Online Update tool that I normally use. Instead, I updated the system using whatever the name of the tool is that replaced Apper. I restarted the computer after the updates completed, and found that this problem continues. So, the problem occurs on both the initial ISO install and after being updated to the latest versions. I have tried the installation three times with different sequences of updating the system after the initial build to see if the problem was something caused by accessing the system after the initial install. None of the attempts made a difference.

The “Software Repositories” tool works OK. I ran “zypper ref -b” to force the repository database to be rebuilt in case it had been corrupted, but that didn’t make a difference.

Since the Software Management tool is not working, I have not installed any software other than that which came on the ISO and from the software update widget.

Someone may suggest that I just change to using Zypper. I consider the problem I am experiencing to be significant enough that I won’t use this version of OpenSuse until it is resolved because it indicates incompatibility with my computer, an underlying serious bug, or some other problem that may crop up elsewhere. I’ve been using OpenSuse for about 10 years, and have always used Yast for updates and software management.

This was a clean install of OpenSuse Leap 42.1, replacing an installed version of 13.2 (used the entire disk for the install). This is on a home computer, it is not used for business purposes. It is my backup computer which I use in case my main computer fails and for installing new releases. The hardware and configuration of my backup computer is identical to my main computer, having identical hardware except that the SSD is 250GB instead of the 500GB on my main computer.

From Snapper:

Snapshots
Current Configurationroot▒▒▒▒▒▒▒↓
┌────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────┐
│ID │Type │Start Date │End Date │Description │User Data │
│1 │Single │2016-01-10 09:09:36│ │first root filesystem│ │
│2 │Single │2016-01-10 09:28:32│ │after installation │important=yes │
│3 & 4 │Pre & Post│2016-01-10 09:45:51│2016-01-10 09:46:32│yast online_update │ │
│5 & 6 │Pre & Post│2016-01-10 09:46:44│2016-01-10 09:49:34│yast lan │ │
│7 & 8 │Pre & Post│2016-01-10 09:49:37│2016-01-10 09:50:39│yast online_update │ │
│9 & 10 │Pre & Post│2016-01-10 09:50:43│2016-01-10 09:51:00│yast sw_single │ │
│12 & 13│Pre & Post│2016-01-10 10:16:17│2016-01-10 10:18:07│yast users │ │
│14 & 15│Pre & Post│2016-01-10 10:18:09│2016-01-10 10:19:13│yast samba-server │ │
│16 & 17│Pre & Post│2016-01-10 10:19:37│2016-01-10 10:19:58│yast apparmor │ │
│18 & 19│Pre & Post│2016-01-10 10:20:02│2016-01-10 10:20:21│yast services-manager│ │
│20 & 21│Pre & Post│2016-01-10 10:24:29│2016-01-10 10:25:03│yast sw_single │ │
│11 & 22│Pre & Post│2016-01-10 09:51:25│2016-01-10 10:35:23│zypp(packagekitd) │important=yes │
│23 & 24│Pre & Post│2016-01-10 11:01:37│2016-01-10 11:01:51│yast ntp-client │ │
│25 & 26│Pre & Post│2016-01-10 11:01:52│2016-01-10 11:03:42│yast users │ │
│27 & 28│Pre & Post│2016-01-10 11:03:45│2016-01-10 11:04:07│yast online_update │ │
│29 & 30│Pre & Post│2016-01-10 11:04:11│2016-01-10 11:04:30│yast sw_single │ │
│31 & 32│Pre & Post│2016-01-10 11:04:34│2016-01-10 11:05:38│yast repositories │ │
│33 & 34│Pre & Post│2016-01-10 11:09:08│2016-01-10 11:09:27│yast sw_single │ │
│35 & 36│Pre & Post│2016-01-10 16:13:23│2016-01-10 16:13:45│yast sysconfig │ │
│37 │Pre │2016-01-10 16:16:19│ │yast snapper │ │
│ │

Thank you.

I am assuming you are in plasma 5 .
I’ve seen this in plasma 5 (leap42.1)
a week ago, but in xfce and enlightenment it is working.
What I did was reinstall yast2 qt. since it is the one I am using
in yast2. You have to login using icewm since it is not working in plasma5.

Yes, it is using Plasma 5.

Please pardon my ignorance, but what are “qt” and “icewm”? Would the current version of Yast2 need to be uninstalled? I assume I would need to use Zypper to install the new version of Yast2, but am not sure how to do that.

Thank you.

Hi,
In your login screen there should be an option on which DE you want to login.
In openSUSE icewm is always installed by default as a fallback when you have a problem in your main DE.
At least it always work and very helpful in helping to troubleshoot. Icewm is a windowmanager, google and you will know
what it is for a complete meaning.

When you able to login to icewm, open yast2, open the software management and in search type yast2.
Find the yast2-qt-branding-openSUSE and click it to reinstall.
Hope this help.

Did this happen on a 2 Display System?
If yes, try to open Yast----Software on the first Monitor.

Bugreport:
https://bugzilla.opensuse.org/show_bug.cgi?id=955381

I first tried what conram suggested, to reinstall yast2-qt-branding-openSUSE, but that didn’t work. I then saw Sauerland’s reply. Yes, I am using a two monitor system, and it is my habit to bring up Yast on the #2 monitor while I do other things on the #1 monitor. When I moved Yast to the #1 monitor the Software Update and Software Management tools worked.

Thank you both!

So it is the bug I reported.