Yast2 Problem

English Applications
#1

Hi, I’m no longer able to open up the modules inside Yast 2.

To get into Yast2, I open a terminal, su, and call Yast2. When I click
on a module to open (Software Management, for example), the mouse
pointer turns into a ‘working in background’ state for a few seconds and
then goes back to normal.

I can still get into the Yast2 modules if I log into KDE as root, just
not as a user like I used to. How can I fix this?

–
kwikness

kwikness’s Profile: http://forums.opensuse.org/member.php?userid=21908
View this thread: http://forums.opensuse.org/showthread.php?t=407337

#2

As user open a terminal and go su
then do:

rpmdb --rebuilddb

then

zypper ref

zypper up

it may help

–
Box: Linux 2.6.27.12-170.2.5 i686 | Fedora 10 | Gnome 2.24.2 | M2N4-SLI
| AMD 64 X2 5200+ | nVidia 8500GT | 2GB RAM
Lap: openSUSE 11.1 | Celeron 550 | (KDE4.2.0)“90.1” | Intel 965 GM |
Lenovo R61e | 3GB RAM

caf4926’s Profile: http://forums.opensuse.org/member.php?userid=204
View this thread: http://forums.opensuse.org/showthread.php?t=407337

#3

Try what caf4932 suggested first. An upgrade might help.

Are you in a KDE or Gnome environment?

If KDE, try

kdesu yast2

–
deano_ferrari

deano_ferrari’s Profile: http://forums.opensuse.org/member.php?userid=122
View this thread: http://forums.opensuse.org/showthread.php?t=407337

#4

> I can still get into the Yast2 modules if I log into KDE as root, just
> not as a user like I used to. How can I fix this?

just a friendly reminder: you should never ever log into KDE as root
(or Gnome or any of the many other windows managers available)…

one reason is that just doing that often causes really strange
and difficult to pin down permission issues once you again log in as
a regular user…

maybe like the one you are faced with now.

to learn the correct way to exercise root powers pay attention to:
http://en.opensuse.org/SDB:Login_as_root

and have fun…

and just as a WILD guess: there is a hidden file in your home named
…ICEauthority, check and make sure it is owned by you (not root) and
the owner can read and write to the file…

that file sometimes gets screwy if you log into KDE as root.

oh, and check the permissions for the folder in your home named
…yast2 and the file y2controlcenterrc inside that folder…all should
be owned by you and you can read and write to them