reassign 250919 kde
thanks
On Tue, May 25, 2004 at 10:35:59PM +0200, Jan L�hr wrote:
> package: xserver-xfree86
> version: 4.3.0.dfsg1-1
>
> Greetings,
>
> I'm not sure wheter this is a xserver bug, but for me it is not possible to
> draw a connection to the correct package.
I can perhaps help with that.
[...]
> startkde: Starting up...
> /usr/bin/x-session-manager: line 157: 5242 Segmentation fault kreadconfig --file kpersonalizerrc --group General --key FirstLogin --default true --type bool
> /usr/bin/x-session-manager: line 160: 5243 Segmentation fault ksplash --nodcop
> /usr/bin/x-session-manager: line 164: 5244 Segmentation fault LD_BIND_NOW=true kdeinit +kcminit +knotify
> startkde: Could not start kdeinit. Check your installation.
> Warning: connect() failed: : No such file or directory
> /usr/bin/x-session-manager: line 181: 5246 Segmentation fault kwrapper ksmserver $KDEWM
> startkde: Shutting down...
> Warning: connect() failed: : No such file or directory
> Error: Can't contact kdeinit!
> startkde: Running shutdown scripts...
> startkde: Done.
The X server is not crashing. It is exiting cleanly and deliberately
because it could not start a client.
Please see the Debian X FAQ.
http://necrotic.deadbeast.net/xsf/XFree86/trunk/debian/local/FAQ
*) How can I tell if it's the X server crashing, or my X session exiting
abnormally?
Generally, when the X server has no more clients to manage, it will exit
immediately. This can look a lot like a "crash" to the uninitiated, especially
when the clients themselves crash.
It's easy to determine whether the X server itself works. As root, simply run
the command "X". If that brings up the little root window weave and the X
cursor, then *you do not have a fatal X server configuration problem*. The X
server is working. Use CTRL-ALT-BACKSPACE to kill it.
Alternatively, if you're using a display manager and you can see the greeter
(login screen), then the X server is running: *you do not have a fatal X server
configuration problem*. Most failures after that point are client-side
problems. (Yes, there are bugs in the X server that can cause it spontaneously
crash, but if the X server "crashes" immediately upon logging in to your X
session, it's probably a client side problem.)
If the X server doesn't start with the command "X", but you get a message like
"Server already active for display 0", then you're probably already running X
somewhere. See the "The X server log says there was an error opening my 'core
pointer'..." question above for more information on how to deal with this.
Alternatively, if you're using a display manager and you can see the
greeter (login screen), then the X server is running: *you do not have a
fatal X server configuration problem*. Most failures after that point
are client-side problems. (Yes, there are bugs in the X server that can
cause it spontaneously crash, but if the X server "crashes" immediately
upon logging in to your X session, it's probably a client side problem.)
No idea which exact KDE package is the problem; with multiple clients
segfaulting, it could be a library problem.
Reassigning to "kde".
--
G. Branden Robinson | The last time the Republican Party
Debian GNU/Linux | was on the right side of a social
branden@debian.org | issue, Abe Lincoln was president.
http://people.debian.org/~branden/ | -- Kirk Tofte
Attachment:
signature.asc
Description: Digital signature