[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde
Subject:    Re: [kde] Unable to start up KDE due to hanging with a black
From:       Phillip Pi <ant () zimage ! com>
Date:       2007-11-19 17:43:58
Message-ID: 20071119174358.GK25668 () alpha ! zimage ! com
[Download RAW message or body]

> > > 0
> 
> OK, good. Just checking if it is a non-tcp connection, i.e. not 
> containing "localhost" or $HOSTNAME

Whew. :)

 
> > > 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 things.
> Though starting a KDE application from outside KDE also does this and that 
> seems to work.

Yeah, but not startkde. ;) Is that considered an application?

 
> > 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.

Goodie. Maybe we're getting somewhere. I checked ALL options (forgot to
see if ksmserver was checked already or not -- sorry) and ran startkde
from Gnome's terminal (did this twice in two different X sessions to be
sure):

$ startkde
startkde: Starting up...
ICE default IO error handler doing an exit(), pid = 12634, errno = 95
ICE default IO error handler doing an exit(), pid = 12636, errno = 0
WARNING: DCOP communication problem!
kdeinit: Communication error with launcher. Exiting!

<<I hit my enter key a few times (was frustrated) in Gnome terminal and
it threw more messages in Gnnome terminal; I couldn't reproduce this
through startx though and I don't know if these are valid and useful 
errors to us>>

kbuildsycoca running...

kwin: unable to claim manager selection, another wm running? (try using --replace)

ASSERT: "!name.isEmpty()" in \
/build/buildd/kdelibs-3.5.8.dfsg.1/./kio/kio/kdirlister.cpp (969) add font path: \
'/home/ant/.fonts' add font path: '/usr/share/fonts'
add font path: '/usr/share/fonts/truetype'
add font path: '/usr/share/fonts/truetype/msttcorefonts'
add font path: '/usr/share/fonts/truetype/ttf-bitstream-vera'
add font path: '/usr/share/fonts/truetype/openoffice'
add font path: '/usr/share/fonts/truetype/latex-xft-fonts'
add font path: '/usr/share/fonts/truetype/freefont'
add font path: '/usr/share/fonts/truetype/ttf-dejavu'
add font path: '/usr/share/fonts/truetype/sjfonts'
add font path: '/usr/share/fonts/truetype/dustin'
add font path: '/usr/share/fonts/truetype/kochi'
add font path: '/usr/share/fonts/type1'
add font path: '/usr/share/fonts/type1/gsfonts'
add font path: '/usr/share/fonts/X11'
add font path: '/usr/share/fonts/X11/encodings'
add font path: '/usr/share/fonts/X11/util'
add font path: '/usr/share/fonts/X11/misc'
add font path: '/usr/share/fonts/X11/100dpi'
add font path: '/usr/share/fonts/X11/75dpi'
add font path: '/usr/share/fonts/X11/Type1'
loaded font VeraMoBd/8
loaded font Vera/7
xscreensaver: 09:37:02: already running on display :0.0 (window 0x2200001) from \
process 12645 (ant@ANTian).


Ooh, new valid errors (X server problem?)? Now what?

I tried startx outside of X, but didn't see these errors (same ones as 
shown before). :/ Nothing odd in Xorg.0.log:
# tail Xorg.0.log
(**) Option "Device" "/dev/psaux"
(**) Option "Emulate3Buttons" "no"
(**) Option "ZAxisMapping" "4 5"
(**) Mouse0: ZAxisMapping: buttons 4 and 5
(**) Mouse0: Buttons: 9
(**) Mouse0: Sensitivity: 1
(II) XINPUT: Adding extended input device "Mouse0" (type: MOUSE)
(II) XINPUT: Adding extended input device "Keyboard0" (type: KEYBOARD)
(--) Mouse0: PnP-detected protocol: "ExplorerPS/2"
(II) Mouse0: ps2EnableDataReporting: succeeded

 
> Lets hope we can crack it :)

Good morning (from my side)! We better. I am going to cry if I have to 
use another WM!! Gnome is driving me nuts. :(
-- 
"One day he sprained an ankle rather than crush an ant." --Les 
Miserables
  /\___/\
 / /\ /\ \       Phillip/Ant @ http://antfarm.ma.cx (Personal Web Site)
> > o   o| |         Ant's Quality Foraged Links (AQFL): http://aqfl.net
   \ _ /                 E-mail: philpi@earthlink.net or ant@zimage.com
    ( )
___________________________________________________
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.


[prev in list] [next in list] [prev in thread] [next in thread] 

Configure | About | News | Add a list | Sponsored by KoreLogic