Software Management will not load from the YaST Control Center

English Applications
1

Hi, I have a very recent install of OpenSuse 13.1 (not tumbleweed) on x86_64 with the KDE environment installed. Today, the link to Software Management stopped working in YaST. The mouse cursor starts spinning after I click on the icon, but the application never successfully loads. I have YaST2 version 3.0.14-17.1 installed.

I would really appreciate any help that anyone can offer to track this error down. YaST doesn’t give any visible feedback, but if anyone can help point me to the right logs or give advice on how to solve this problem, you’d save me a bunch of self-inflicted head trauma. Thanks!

2

Please post your repo list.

zypper lr -d

Does it work in the text mode YaST?

sudo /sbin/yast

Do you get any error message when you run this:

su -
yast2 sw_single
3

Thanks. Repos are standard, plus the repo for the fglrx AMD display driver, that driver appears to be necessary to get more than 800x600 resolution.

| Alias | Name | Enabled | Refresh | Priority | Type | URI | Service

—±--------------------------±-----------------------------------±--------±--------±---------±-------±------------------------------------------------------------------------±-------
1 | AMD/ATI-FGLRX | AMD/ATI-FGLRX | Yes | Yes | 99 | rpm-md | http://geeko.ioda.net/mirror/amd-fglrx/openSUSE_13.1/ |
2 | openSUSE-13.1-1.10 | openSUSE-13.1-1.10 | No | No | 99 | yast2 | cd:///?devices=/dev/disk/by-id/ata-hp_DVDRAM_GU90N_M75E4UH5321,/dev/sr0 |
3 | repo-debug | openSUSE-13.1-Debug | No | Yes | 99 | NONE | http://download.opensuse.org/debug/distribution/13.1/repo/oss/ |
4 | repo-debug-update | openSUSE-13.1-Update-Debug | No | Yes | 99 | NONE | http://download.opensuse.org/debug/update/13.1/ |
5 | repo-debug-update-non-oss | openSUSE-13.1-Update-Debug-Non-Oss | No | Yes | 99 | NONE | http://download.opensuse.org/debug/update/13.1-non-oss/ |
6 | repo-non-oss | openSUSE-13.1-Non-Oss | Yes | Yes | 99 | yast2 | http://download.opensuse.org/distribution/13.1/repo/non-oss/ |
7 | repo-oss | openSUSE-13.1-Oss | Yes | Yes | 99 | yast2 | http://download.opensuse.org/distribution/13.1/repo/oss/ |
8 | repo-source | openSUSE-13.1-Source | No | Yes | 99 | NONE | http://download.opensuse.org/source/distribution/13.1/repo/oss/ |
9 | repo-update | openSUSE-13.1-Update | Yes | Yes | 99 | rpm-md | http://download.opensuse.org/update/13.1/ |
10 | repo-update-non-oss | openSUSE-13.1-Update-Non-Oss | Yes | Yes | 99 | rpm-md | http://download.opensuse.org/update/13.1-non-oss/ |

I’m not sure about the text mode YaST. The command sudo /sbin/yast doesn’t seem to do anything. It just exits immediately:
> sudo /sbin/yast
>

I don’t get any error messages when I run
su -
yast2 sw_single

I also don’t get any output, the console just goes to another input prompt:

> su -
Password:

yast2 sw_single

4

This should be ok.

But there were a few people already that added the Factory repo by mistake, and ended up with a mixture of packages that rendered YaST inoperable.

I’m not sure about the text mode YaST. The command sudo /sbin/yast doesn’t seem to do anything. It just exits immediately:

So that’s the same like when starting any module in YaST Qt.

Can you please post the last lines of /var/log/YaST2/y2log?
This should do:

tail -20 /var/log/YaST2/y2log

Hopefully we would find an error message there.

And another question:
this applies to all modules, not just the Software Management, right?

5

On 2014-08-09 13:26, haileris wrote:

> # | Alias | Name |
> Enabled | Refresh | Priority | Type | URI
> | Service
> —±--------------------------±-----------------------------------±--------±--------±---------±-------±------------------------------------------------------------------------±-------
> 1 | AMD/ATI-FGLRX | AMD/ATI-FGLRX |
> Yes | Yes | 99 | rpm-md |
> http://geeko.ioda.net/mirror/amd-fglrx/openSUSE_13.1/

A comment. When pasting computer commands and such, please use a CODE
BLOCK, so that the forum software doesn’t do silly things like
converting URLS to tiny urls, parenthesis into smileys, wrap lines, or
otherwise hide or alter the commands you entered. You get them by
clicking on the ‘#’ button in the forum editor.
See photo

For the next time :slight_smile:

–
Cheers / Saludos,

Carlos E. R.
(from 13.1 x86_64 “Bottle” at Telcontar)

6

Thank you so much! The log file had exactly what I needed. I had accidentally removed a ruby gem that YaST depends on when repairing a botched rails install. This was 100% my fault, sorry. Thank you for pointing me in the right direction.

7

Re: code blocks on the forum… will do next time, thanks for letting me know.