Yast won't start.

difficilus · #1 (**permalink**) 03-Nov-2009, 14:00

11.1 installed, Kernel is 11.1-2.6.27.29.0.1, Gnome desktop. Unable to get Yast to start. Asks for root password and after entering password nothing happens. I was able to start Yast in Gnome Terminal but I think that I'm not up to the task yet. Have made some rather telling mistakes while having fun with 11.1. Tried to install and then remove KDE. Tried to remove Pulse Audio (that was not a lot of fun ... seems Gnome is rather attached to it). It appears that I have damaged many little things while playing around. Sound, scanner, printer all need work to get functional again. Messed up the bootloader (fixed). Yast started giving some error messages in seperate window but seemed to still be working okay until reboot. Now no response when implementing an instance. Reinstall it? If so best way? Looking forward to the 11.2 final BTW.

caf4926 · #2 (**permalink**) 03-Nov-2009, 14:02

Try typing yast2 in a su terminal
Report error that log there

difficilus · #3 (**permalink**) 03-Nov-2009, 14:09

Useful information methinks.

Yast2 command in terminal generated many copies of this error:

** (y2controlcenter-gnome:6568): WARNING **: error accessing /desktop/gnome/applications/main-menu/upgrade_package_command [Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See GConf configuration system for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.)]

caf4926 · #4 (**permalink**) 03-Nov-2009, 14:16

In a su terminal do this:

Code:

zypper ref

then

Code:

zypper up

Does it update anything? Reboot and try yast again.

difficilus · #5 (**permalink**) 03-Nov-2009, 14:20

Command : gconftool-2 -R /desktop/gnome returns the same error message. Related to bootloader? Boot from root, mbr, extended partition, etc. maybe?

difficilus · #6 (**permalink**) 03-Nov-2009, 14:25

zypper ref
Retrieving repository 'Packman Repository' metadata [done]
Building repository 'Packman Repository' cache [done]
Repository 'openSUSE-11.1-Non-Oss' is up to date.
Repository 'openSUSE-11.1-Oss' is up to date.
Repository 'openSUSE-11.1-Update' is up to date.
All repositories have been refreshed.

zypper up
gstreamer-0_10-plugins-good gstreamer-0_10-plugins-good-doc
gstreamer-0_10-plugins-good-extra gstreamer-0_10-plugins-good-lang
gstreamer-0_10-plugins-ugly gstreamer-0_10-plugins-ugly-lang gstreamer-0_10-utils
gstreamer-utils gtkhtml2-devel gtkhtml2-lang hplip hplip-hpcups kernel-pae
kernel-pae-base kernel-pae-extra ladspa libavcodec52 libavdevice52 libavformat52
libavutil50 libfaad2 libfarsight2_0 libffmpeg0 libggi2 libgstbasevideo-0_10-0
libgstinterfaces-0_10-0 libgstphotography-0_10-0 libgstreamer-0_10-0
libktoblzcheck1 libmp4v2 libmtp8 libmtp-hal libofx4 libpostproc51 libswscale0 libucil1
libunicap1 libvlc2 libvlccore2 libxine1 libxine1-aa libxine1-arts libxine1-codecs
libxine1-directfb libxine1-esd libxine1-gnome-vfs libxine1-jack libxine1-pulse
libxine1-sdl MPlayer ogmrip python-gstreamer-0_10 timezone timezone-java transcode vlc
vlc-gnome vlc-noX vlc-qt

The following NEW packages are going to be installed:
libgstsignalprocessor-0_10-0 liblash1 libogmrip1 libslv2-9 libx264-72 libx264-78

The following package is going to be REMOVED:
lash-libs

Overall download size: 79.6 M. After the operation, additional 4.9 M will be used.
Continue? [YES/no]:

caf4926 · #7 (**permalink**) 03-Nov-2009, 14:28

Type Yes and after it finishes, reboot

difficilus · #8 (**permalink**) 03-Nov-2009, 15:00

Losts of package updates including Kernel. Yast still won't start in gui at all. In terminal as su yast2 opens window after root password entered but this error message appears:

An error occurred while loading or saving configuration information for GNOME SuperUser. Some of your configuration settings may not work properly.

details: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See GConf configuration system for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.)
Same message in terminal.