From kde Mon Nov 19 09:53:23 2007 From: Kevin Krammer Date: Mon, 19 Nov 2007 09:53:23 +0000 To: kde Subject: Re: [kde] Unable to start up KDE due to hanging with a black Message-Id: <200711191053.29437.kevin.krammer () gmx ! at> X-MARC-Message: https://marc.info/?l=kde&m=119546614307044 MIME-Version: 1 Content-Type: multipart/mixed; boundary="--===============1077889648==" --===============1077889648== Content-Type: multipart/signed; boundary="nextPart1404923.7XjUphSZdJ"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit --nextPart1404923.7XjUphSZdJ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Monday 19 November 2007, Phillip Pi wrote: > I assume like this: > # We only check for 255 which means that the ksmserver process could not = be > # started, any problems thereafter, e.g. ksmserver failing to initialize, > # will remain undetected. > test -n "$KDEWM" && KDEWM=3D"--windowmanager $KDEWM" > kwrapper ksmserver $KDEWM > echo $DISPLAY > /home/ant/download/display.txt > if test $? -eq 255; then > # Startup error > echo 'startkde: Could not start ksmserver. Check your installation.' > 1>&2 > xmessage -geometry 500x100 "Could not start ksmserver. Check your > installation." > fi > > If so, then: > $ more /home/ant/download/display.txt > > :0 OK, good. Just checking if it is a non-tcp connection, i.e. not=20 containing "localhost" or $HOSTNAME > > Another thing you could try is to start just xterm and then run startkde > > inside it, i.e. > > > > startx /usr/bin/xterm > > > > Should start the X server and just xterm as the only window. You'll need > > to move the mouse cursor over the window to allow keyboard input. > > That worked, but no cigar. I see KDE's splash screen loader and it > blinks at the first icon (wheel) with "Setting up interprocess > communication" like I did in Gnome. After a minute or two, this splash > screen goes away and xterm is still showing "startkde: Starting up..." At that stage it tries to start the DCOP server and a couple of other thing= s. Though starting a KDE application from outside KDE also does this and that= =20 seems to work. > Here's a strace from second attempt inside xterm: > http://pastebin.ca/783688 (looks the same). Does startkde have a debug > feature? You can run kdebugdialog and see if the entry for "ksmserver" is checked. Should output to .xsession-errors or the xterm, depending on how you start = it. > I am going to bed now, so I will try more later from your ideas. :) Lets hope we can crack it :) Cheers, Kevin =2D-=20 Kevin Krammer, KDE developer, xdg-utils developer KDE user support, developer mentoring --nextPart1404923.7XjUphSZdJ Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQBHQV0ZnKMhG6pzZJIRAqKTAJ0V36nrtqgXO7uuNyKApmXiScV34ACcCyQC yuuiBcqb6aFfFI6aoaubBnQ= =1iUW -----END PGP SIGNATURE----- --nextPart1404923.7XjUphSZdJ-- --===============1077889648== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline ___________________________________________________ This message is from the kde mailing list. Account management: https://mail.kde.org/mailman/listinfo/kde. Archives: http://lists.kde.org/. More info: http://www.kde.org/faq.html. --===============1077889648==--