Can't launch KDE after updates 11.2

Hello all. I’m having some issues. I’ve installed via milestone 2 live USB to an external USB HDD on my eeePC, then added these two repos


http://download.opensuse.org/factory/repo/oss/
http://download.opensuse.org/factory/repo/non-oss/

at standard priority and disabled the other oss / non-oss ones. Thus far KDE 4.3 loads correctly. I then did a zypper up / dup (tried both on separate install attempts), which pulls in lots of packages, and removes these;


The following packages are going to be REMOVED:
  babl-0_0 libpulsecore9 pth qlogic-firmware yast2-storage-lib 

KDE now won’t launch - the login screen disappears, KDE kursor appears, bar creeps along the loading screen, then everything goes black, normal cursor reappears, and I’m dropped back to the login screen. I can load IceWM, so I can still pull in packages - tried putting those packages back, but some don’t seem to exist, and some seem to be installed anyway (possibly after later updates). Same thing happens on reinstall - and I can’t get gnome to work either. :frowning: Anyone got any advice?


/etc/X11/xim: Checking whether an input method should be started.
sourcing /etc/sysconfig/language to get the value of INPUT_METHOD
INPUT_METHOD is not set or empty (no user selected input method).
Trying to start a default input method for the locale en_GB.UTF-8 ...
There is no default input method for the current locale.
Dummy input method "none" (do not use any fancy input method by default)
startkde: Starting up...
kdeinit4: preparing to launch /usr/lib/libkdeinit4_klauncher.so
kdeinit4: preparing to launch /usr/lib/libkdeinit4_kded4.so
kdeinit4: preparing to launch /usr/lib/libkdeinit4_kbuildsycoca4.so
kbuildsycoca4 running...
kdeinit4: preparing to launch /usr/lib/libkdeinit4_kbuildsycoca4.so
kbuildsycoca4 running...
kdeinit4: preparing to launch /usr/lib/libkdeinit4_kconf_update.so
Invalid D-BUS member name 'idle-hint' found in interface 'org.freedesktop.ConsoleKit.Session' while parsing introspection
Invalid D-BUS member name 'is-local' found in interface 'org.freedesktop.ConsoleKit.Session' while parsing introspection
Invalid D-BUS member name 'x11-display-device' found in interface 'org.freedesktop.ConsoleKit.Session' while parsing introspection
Invalid D-BUS member name 'x11-display' found in interface 'org.freedesktop.ConsoleKit.Session' while parsing introspection
Invalid D-BUS member name 'display-device' found in interface 'org.freedesktop.ConsoleKit.Session' while parsing introspection
Invalid D-BUS member name 'remote-host-name' found in interface 'org.freedesktop.ConsoleKit.Session' while parsing introspection
Invalid D-BUS member name 'session-type' found in interface 'org.freedesktop.ConsoleKit.Session' while parsing introspection
Invalid D-BUS member name 'unix-user' found in interface 'org.freedesktop.ConsoleKit.Session' while parsing introspection
X Error: XSyncBadAlarm 154
  Extension:    144 (Uknown extension)
  Minor opcode: 11 (Unknown request)
  Resource id:  0x0
kdeinit4: preparing to launch /usr/lib/libkdeinit4_kcminit_startup.so
X Error: XSyncBadAlarm 154
  Extension:    144 (Uknown extension)
  Minor opcode: 11 (Unknown request)
  Resource id:  0x0
kdeinit4: preparing to launch /usr/lib/libkdeinit4_ksmserver.so
<unknown program name>(4876)/ KStartupInfo::createNewStartupId: creating:  "linux-ubqm;1245889881;263751;4876_TIME0" : "unnamed app"
kephald starting up 
XRANDR error base:  164 
RRInput mask is set!! 
RandRScreen::loadSettings - adding mode:  61 1024 x 600 
RandRScreen::loadSettings - adding mode:  62 1024 x 600 
RandRScreen::loadSettings - adding mode:  63 1024 x 600 
RandRScreen::loadSettings - adding mode:  64 800 x 600 
RandRScreen::loadSettings - adding mode:  65 800 x 600 
RandRScreen::loadSettings - adding mode:  66 640 x 480 
RandRScreen::loadSettings - adding crtc:  57 
RandRScreen::loadSettings - adding crtc:  58 
RandRScreen::loadSettings - adding output:  59 
Setting CRTC 0 on output "VGA" (previous 0 ) 
RandRScreen::loadSettings - adding output:  60 
Setting CRTC 58 on output "LVDS" (previous 0 ) 
CRTC outputs: (60) 
Output name: "LVDS" 
Output refresh rate: 60 
Output rect: QRect(0,0 1024x600) 
Output rotation: 1 
XRandROutputs::init 
  added output  59 
got a valid edid block... 
vendor code: "HSD" 
product id: 1001 
serial number: 16762 
  added output  60 
output: "LVDS" QRect(0,0 1024x600) 0 false false 
output: "VGA" QRect(0,0 0x0) 0 false false 
load xml 
connected: 1 
looking for current "LVDS" 
known "*" has score: 0.125 
screen: 0 QRect(0,0 1024x600) 
looking for a matching configuration... 
connected: 1 
looking for current "LVDS" 
known "*" has score: 0.125 
found outputs, known: false 
connected: 1 
looking for current "LVDS" 
known "*" has score: 0.125 
activate external configuration!! 
registered the service: true 
screens registered on the bus: true 
outputs registered on the bus: true 
configurations registered on the bus: true 
Qt-subapplication: Fatal IO error: client killed
kcminit_startup: Fatal IO error: client killed
kded4: Fatal IO error: client killed
kdeinit4: Fatal IO error: client killed
kdeinit4: sending SIGHUP to children.
klauncher: Exiting on signal 1
kwin: Fatal IO error: client killed
kdeinit4: sending SIGTERM to children.
kdeinit4: Exit.
Unexpected response from KInit (response = 0).
startkde: Could not start ksmserver. Check your installation.

Update - sax2 -r -m 0=vesa lets me back into KDE4.

I’d still like to know what’s causing this if anyone has any insight, but I suppose it may just be a case of waiting till the drivers settle down. Thanks.

AFAIK moving to Factory updates the X-server, since what you did helped I suspect the xorg-packages (maybe some post process?)

Hmmm… You may well be right.

Sadly, we’ll never know, because Fedora 11 murdered Suse in its sleep. Sibling rivalry, eh? :slight_smile: They really mucked up the installer this time, and it’s done something so funky to my partition table that Suse can’t find /home. I’m sure it could be fixed… but starting afresh with the next milestone sounds like the better plan.

Cheers!

[Which makes me curious… how do the freezes work around here? Are there likely to be a big slew of updates just before the milestone? Or was what I was running - in glorious VESA - probably more or less milestone 3?]

Upon reinstallation, this seems to be fixed. Cheers.