This forum has been archived. All content is frozen. Please use KDE Discuss instead.

Startup Problem - KDE4.2

Tags: None
(comma "," separated)
waverider
Registered Member
Posts
13
Karma
0

Startup Problem - KDE4.2

Wed May 27, 2009 7:27 am
Hi,

I have a clean install of Kubuntu 9.04 64bit. AMD64 running on Asus A8V-VM motherboard. All latest updates applied from command line.

I had Kubuntu 8.04 installed on the machine and KDE3.5 worked fine.

On startup I get to the Login screen OK but once username and password are accepted the screen starts OK until the disc image appears, the next three images start to appear, but will go no further and freezes. CTRL-ALT-DEL and other keystrike combinations will not work. I assume it is an xsession problem.

The last entries in .xsession-errors are:

Error: Can not contact kdeinit4!
startkde: Running shutdown scripts...
xprop: unable to open display ':0'
xprop: unable to open display ':0'
startkde: Done.

I can login to a prompt, and can access everything OK, but as soon as I start X it starts and then stalls at the same point - just after the disc image appears.
User avatar
bcooksley
Administrator
Posts
19765
Karma
87
OS

RE: Startup Problem - KDE4.2

Wed May 27, 2009 7:56 am
Can you please paste the entire xsession-errors file for a particular login attempt? It looks like it could be DBus related.


KDE Sysadmin
[img]content/bcooksley_sig.png[/img]
waverider
Registered Member
Posts
13
Karma
0

RE: Startup Problem - KDE4.2

Wed May 27, 2009 8:53 am
bcooksley wrote:Can you please paste the entire xsession-errors file for a particular login attempt? It looks like it could be DBus related.

Thanks for the response. Unfortunately I can't - no network connection with the machine so no access to files or browser.
I just cleared the .xsession-errors file and rebooted. This time it got to the disc image and then reverted to the login screen again. The last entries in .xsession-errors are (hand typed):

XCrash:Application 'ksmserver' crashing
Warning: connetc() failed: : No such file or Directory
XCrash cannot reach kdeinit,launching directly.
Unexpected response from KInit (Response=0)
startkde:Could not start kmserver. Check your installation.
QWidget: Must construct a QApplication before a QPaintDevice
xwin: Fatal I0 error: client killed
Qt-subapplication: Fatal IO error: Client killed
Kded4:Fatal IO error: Client killed

Last edited by waverider on Wed May 27, 2009 8:56 am, edited 1 time in total.
User avatar
bcooksley
Administrator
Posts
19765
Karma
87
OS

RE: Startup Problem - KDE4.2

Wed May 27, 2009 9:04 am
KSMServer not being able to start is Fatal to a KDE session, since it is responsible for managing the session. ( KDE Session Management Server ). Can you please try under a new user?


KDE Sysadmin
[img]content/bcooksley_sig.png[/img]
waverider
Registered Member
Posts
13
Karma
0

RE: Startup Problem - KDE4.2

Wed May 27, 2009 10:01 am
bcooksley wrote:KSMServer not being able to start is Fatal to a KDE session, since it is responsible for managing the session. ( KDE Session Management Server ). Can you please try under a new user?


Yes - I have tried that:

Hangup
GOT SIGHUP
Could not connect to D-Bus server:org.freedesktop.DBus error.NoServer: Failed $ Qt-subapplication: Fatal IO error:client killed
kded4: Fatal IO error:client killed
startkde: Shutting down...
kdeinit4_wrapper: Warning: connect(home/bobd/.kde/socket-Server1/kdeinit4__0) $
Error: Can not contact kdeinit4!
startkde: Running shutdown scripts...
xprop: unable to open display ':0'
xprop: unable to open display ':0'
startkde: Done.
User avatar
bcooksley
Administrator
Posts
19765
Karma
87
OS

RE: Startup Problem - KDE4.2

Thu May 28, 2009 6:05 am
Please verify your system configuration is not damaged.
Also what is listed prior to "HANGUP" in the ~/.xsession-errors of the new user?


KDE Sysadmin
[img]content/bcooksley_sig.png[/img]
waverider
Registered Member
Posts
13
Karma
0

RE: Startup Problem - KDE4.2

Thu May 28, 2009 9:53 am
bcooksley wrote:Please verify your system configuration is not damaged.
Also what is listed prior to "HANGUP" in the ~/.xsession-errors of the new user?

Hello - thanks for the response.
Having been frustrated for a couple of days I decided to take another approach. I did a complete reinstall but this time with Ubuntu 9.04 64bit and then installed the KDE4 desktop.

Gnome works fine - I am using this system now - so the hardware works OK. However, on using the KDE desktop, KDE does exactly the same as it did on the Kubuntu install - get to the window which shows the images and freezes, or drops back to the login screen.

This time I can get to the .xsession-errors file though. This is the file from my second attempt to log on with KDE:

/etc/gdm/Xsession: Beginning session setup...
Setting IM through im-switch for locale=en_AU.
Start IM through /etc/X11/xinit/xinput.d/all_ALL linked to /etc/X11/xinit/xinput.d/default.
startkde: Starting up...
kdeinit4: preparing to launch /usr/lib/kde4/libexec/klauncher
kdeinit4: preparing to launch /usr/bin/kded4
kdeinit4: preparing to launch /usr/bin/kbuildsycoca4
kbuildsycoca4 running...
kdeinit4: preparing to launch /usr/bin/kbuildsycoca4
kbuildsycoca4 running...
kdeinit4: preparing to launch /usr/lib/kde4/libexec/kconf_update
kded(5764) Solid::Control::ManagerBasePrivate::loadBackend: Backend loaded: "HAL-Power"
kded(5764) XSyncBasedPoller::XSyncBasedPoller: 3 0
kded(5764) XSyncBasedPoller::XSyncBasedPoller: XSync seems available and ready
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
kded(5764) XSyncBasedPoller::setUpPoller: XSync Inited
kded(5764) XSyncBasedPoller::setUpPoller: Supported, init completed
kded(5764) PowerDevilDaemon::profileFirstLoad: Profile initialization
X Error: XSyncBadAlarm 154
Extension: 144 (Uknown extension)
Minor opcode: 11 (Unknown request)
Resource id: 0x0
kded(5764) KDEDModule::setModuleName: registerObject() successful for "powerdevil"
X Error: XSyncBadAlarm 154
Extension: 144 (Uknown extension)
Minor opcode: 11 (Unknown request)
Resource id: 0x0
kdeinit4: preparing to launch /usr/bin/kcminit_startup
kdeinit4: preparing to launch /usr/bin/ksmserver
(5761)/ KStartupInfo::createNewStartupId: creating: "Server1;1243504393;423983;5761_TIME0" : "unnamed app"
kephald starting up
XRANDR error base: 164
RRInput mask is set!!
RandRScreen::loadSettings - adding mode: 115 1280 x 1024
RandRScreen::loadSettings - adding mode: 116 1280 x 1024
RandRScreen::loadSettings - adding mode: 117 1280 x 960
RandRScreen::loadSettings - adding mode: 118 1152 x 864
RandRScreen::loadSettings - adding mode: 119 1152 x 864
RandRScreen::loadSettings - adding mode: 120 1152 x 864
RandRScreen::loadSettings - adding mode: 121 1024 x 768
RandRScreen::loadSettings - adding mode: 122 1024 x 768
RandRScreen::loadSettings - adding mode: 123 1024 x 768
RandRScreen::loadSettings - adding mode: 124 832 x 624
RandRScreen::loadSettings - adding mode: 125 800 x 600
RandRScreen::loadSettings - adding mode: 126 800 x 600
RandRScreen::loadSettings - adding mode: 127 800 x 600
RandRScreen::loadSettings - adding mode: 128 800 x 600
RandRScreen::loadSettings - adding mode: 129 640 x 480
RandRScreen::loadSettings - adding mode: 130 640 x 480
RandRScreen::loadSettings - adding mode: 131 640 x 480
RandRScreen::loadSettings - adding mode: 132 640 x 480
RandRScreen::loadSettings - adding mode: 133 720 x 400
RandRScreen::loadSettings - adding crtc: 113
RandRScreen::loadSettings - adding output: 114
Setting CRTC 113 on output "default" (previous 0 )
CRTC outputs: (114)
Output name: "default"
Output refresh rate: 60
Output rect: QRect(0,0 1280x1024)
Output rotation: 1
XRandROutputs::init
added output 114
adding an output 0 with geom: QRect(0,0 1280x1024)
adding a disconnected output 1
adding a disconnected output 2
adding a disconnected output 3
output: "SCREEN-0" QRect(0,0 1280x1024) 6684773 true false
output: "SCREEN-1" QRect(0,0 0x0) 0 false false
output: "SCREEN-2" QRect(0,0 0x0) 7471104 true false
output: "SCREEN-3" QRect(0,0 0x0) 47 true false
load xml
connected: 1
looking for current "SCREEN-0"
known "*" has score: 0.125
screen: 0 QRect(0,0 1280x1024)
looking for a matching configuration...
connected: 1
looking for current "SCREEN-0"
known "*" has score: 0.125
found outputs, known: false
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
kded(5764) KDEDModule::setModuleName: registerObject() successful for "kded_kephal"
kdeinit4: Fatal IO error: client killed
kdeinit4: sending SIGHUP to children.
klauncher: Exiting on signal 1
kdeinit4: sending SIGTERM to children.
kdeinit4: Exit.
Unexpected response from KInit (response = 0).
startkde: Could not start ksmserver. Check your installation.
QSocketNotifier: Invalid socket 9 and type 'Read', disabling...
KCrash: Application 'ksmserver' crashing...
Warning: connect() failed: : No such file or directory
KCrash cannot reach kdeinit, launching directly.
QWidget: Must construct a QApplication before a QPaintDevice
kwin: Fatal IO error: client killed
QSocketNotifier: Invalid socket 14 and type 'Read', disabling...
Qt-subapplication: Fatal IO error: client killed
kded4: Fatal IO error: client killed
Error: Can't open display: :0
Could not connect to D-Bus server: org.freedesktop.DBus.Error.NoServer: Failed to connect to socket /tmp/dbus-5ynTVhDznf: Connection refused
User avatar
bcooksley
Administrator
Posts
19765
Karma
87
OS

RE: Startup Problem - KDE4.2

Fri May 29, 2009 7:16 am
This looks like one of the children of KDEInit4 has crashed, possibly kded itself. Unfortunately, I do not know much about diagnosing KDE Initialisation problems.

You could possibly try logging into KDE using the vesa driver.


KDE Sysadmin
[img]content/bcooksley_sig.png[/img]
waverider
Registered Member
Posts
13
Karma
0

RE: Startup Problem - KDE4.2

Fri May 29, 2009 8:34 am
bcooksley wrote:This looks like one of the children of KDEInit4 has crashed, possibly kded itself. Unfortunately, I do not know much about diagnosing KDE Initialisation problems.

You could possibly try logging into KDE using the vesa driver.

Thanks. it seems that it may be associated with the driver.
01:00.0 VGA compatible controller: VIA Technologies, Inc. K8M890CE/K8N890CE [Chrome 9] (rev 01)
Apparently there is some sort of problem with Chrome 9.
Where is drver information stored so that I can change it? xorg.conf appears to be a file generated by the system now ?
User avatar
bcooksley
Administrator
Posts
19765
Karma
87
OS

RE: Startup Problem - KDE4.2

Fri May 29, 2009 8:56 am
If you manually add the entries to Xorg.conf the system should follow them. If they don't you may need to ask at your distributions forums why you can't manually override it.


KDE Sysadmin
[img]content/bcooksley_sig.png[/img]


Bookmarks



Who is online

Registered users: bancha, Bing [Bot], Evergrowing, Google [Bot], lockheed, mesutakcan, mickae, Sogou [Bot]