KDE4 Crashing on startup (VNC)

F

freakdog

I am going CRAAAAAZY here...

I am experiencing a problem where plasma desktop crashes on startup. I updated to latest ports to kdebase4-workspace-4.3.0_2 and am still experiencing it. I have set my locale settings correctly. I just updated python from 2.5 to 2.6 and am running 7.2-RELEASE-p3. Installed kde 3.5 and kde 4.3.0.

I have added the following to my etc/rc.conf

Code: 
dbus_enable="YES"
hald_enable="YES"

I try to start kde4 and I get a crash in plasma desktop on startup. It appears to be the
I am using tightvnc to start my session.
My log from tightvnc looks like this. I have bolded what I believe are the relevant parts.


Thanks!


Code: 
24/08/09 11:15:16 Xvnc version TightVNC-1.3.10
24/08/09 11:15:16 Copyright (C) 2000-2009 TightVNC Group
24/08/09 11:15:16 Copyright (C) 1999 AT&T Laboratories Cambridge
24/08/09 11:15:16 All Rights Reserved.
24/08/09 11:15:16 See [url]http://www.tightvnc.com/[/url] for information on TightVNC
24/08/09 11:15:16 Desktop name 'X' (xxx.xxx:66)
24/08/09 11:15:16 Protocol versions supported: 3.3, 3.7, 3.8, 3.7t, 3.8t
24/08/09 11:15:16 Listening for VNC connections on TCP port 5966
24/08/09 11:15:16 Listening for HTTP connections on TCP port 5866
24/08/09 11:15:16   URL [url]http://xxx.xxx:5866[/url]
vncconfig: not found
kbuildsycoca4 running...
startkde: Starting up...
kdeinit4: preparing to launch /usr/local/kde4/lib/libkdeinit4_klauncher.so
kdeinit4: preparing to launch /usr/local/kde4/lib/libkdeinit4_kded4.so
Xlib:  extension "Generic Event Extension" missing on display ":66.0".
kdeinit4: preparing to launch /usr/local/kde4/lib/libkdeinit4_kbuildsycoca4.so
kbuildsycoca4 running...
kdeinit4: preparing to launch /usr/local/kde4/lib/libkdeinit4_kbuildsycoca4.so
kbuildsycoca4 running...
kdeinit4: preparing to launch /usr/local/kde4/lib/libkdeinit4_kconf_update.so
Xlib:  extension "Generic Event Extension" missing on display ":66.0".
QDBusObjectPath: invalid path ""
Xlib:  extension "MIT-SCREEN-SAVER" missing on display ":66.0".
Xlib:  extension "RANDR" missing on display ":66.0".
Xlib:  extension "MIT-SCREEN-SAVER" missing on display ":66.0".
kdeinit4: preparing to launch /usr/local/kde4/lib/libkdeinit4_kcminit_startup.so
Xlib:  extension "Generic Event Extension" missing on display ":66.0".
kdeinit4: preparing to launch /usr/local/kde4/lib/libkdeinit4_ksmserver.so
<unknown program name>(24683)/ KStartupInfo::createNewStartupId: creating:  "lgordon.dyndns.org;1251137735;733327;24683_TIME0" : "unnamed app"
Xlib:  extension "Generic Event Extension" missing on display ":66.0".
Xlib:  extension "Generic Event Extension" missing on display ":66.0".
kephald starting up 
adding an output 0 with geom:  QRect(0,0 1280x1000) 
output: "SCREEN-0" QRect(0,0 1280x1000) 0 true true 
load xml 
connected: 1 
looking for current "SCREEN-0" 
known "*" has score: 0.125 
screen: 0 QRect(0,0 1280x1000) 
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 
Xlib:  extension "Generic Event Extension" missing on display ":66.0".
Xlib:  extension "Generic Event Extension" missing on display ":66.0".
kdeinit4: preparing to launch /usr/local/kde4/lib/libkdeinit4_kglobalaccel.so
Xlib:  extension "Generic Event Extension" missing on display ":66.0".
QPainter::setCompositionMode: PorterDuff modes not supported on device
kdeinit4: preparing to launch /usr/local/kde4/lib/libkdeinit4_plasma-desktop.so
kdeinit4: preparing to launch /usr/local/kde4/bin/knotify4
Xlib:  extension "Generic Event Extension" missing on display ":66.0".
[B]QDBusObjectPath: invalid path ""[/B]
Xlib:  extension "Generic Event Extension" missing on display ":66.0".
QPainter::setCompositionMode: PorterDuff modes not supported on device
QPainter::setCompositionMode: PorterDuff modes not supported on device
QPainter::setCompositionMode: PorterDuff modes not supported on device
QPainter::setCompositionMode: PorterDuff modes not supported on device
QLayout: Attempting to add QLayout "" to QWidget "", which already has a layout
[B]Invalid D-BUS interface name 'org.kde.plasma-desktop.PlasmaApp' found while parsing introspection
KCrash: Application 'plasma-desktop' crashing...[/B]
 
freakdog said:
I updated to latest ports to kdebase4-workspace-4.3.0_2 and am still experiencing it. I have set my locale settings correctly. I just updated python from 2.5 to 2.6 and am running 7.2-RELEASE-p3. Installed kde 3.5 and kde 4.3.0.
Click to expand...
Did it work at all at some point? If so, did it work before you updated python?

In any case: check the permissions of all dot-files in your homedir (.kde4, etc). They have to be owned by your user. Try cleaning out /tmp and start with a fresh ~/.kde4, i. e. move ~/.kde4 out of the way temporarily.
 
It never worked. I had an old 4.0 version on previously. I tried deleting all the temp files as directed in another thread, but it didn't work. Also tried getting rid of all my .kde files. No dice. Tried with a newly created user. No dice.

*HELP* :)
 
Sorry, the 4.3 has consistently had this problem, but a long ago 4.0 (or 4.1) version did, but I removed it from my system.
 
freakdog said:
Sorry, the 4.3 has consistently had this problem, but a long ago 4.0 (or 4.1) version did work (to some extent), but I removed it from my system.
Click to expand...

/sorry, can't edit posts :)
 
how do you start vncserver and what does ~/.vnc/xstartup look like?

I just tested it here and it seems to work.
 
My .vnc/xstartup

Code: 
[ -r $HOME/.Xresources ] && xrdb $HOME/.Xresources
xsetroot -solid grey
PATH=/usr/local/kde4/bin:$PATH
export PATH
startkde4 &
 
This is what I see in /var/log/messages:

Code: 
Aug 24 12:12:58 xxx dbus-daemon: Rejected send message, 3 matched rules; type="method_call", sender=":1.4" (uid=1001 pid=982 comm=") interface="org.freedesktop.DBus.Introspectable" member="Introspect" error name="(unset)" requested_reply=0 destination="org.freedesktop.ConsoleKit" (uid=0 pid=884 comm="))
Aug 24 12:12:58 xxx dbus-daemon: Rejected send message, 4 matched rules; type="method_call", sender=":1.4" (uid=1001 pid=982 comm=") interface="org.freedesktop.ConsoleKit.Manager" member="GetCurrentSession" error name="(unset)" requested_reply=0 destination="org.freedesktop.ConsoleKit" (uid=0 pid=884 comm="))
Aug 24 12:13:21 xxx kernel: pid 1000 (plasma-desktop), uid 1001: exited on signal 11 (core dumped)
Aug 24 16:52:27 xxx dbus-daemon: Rejected send message, 3 matched rules; type="method_call", sender=":1.8" (uid=1001 pid=1931 comm=") interface="org.freedesktop.DBus.Introspectable" member="Introspect" error name="(unset)" requested_reply=0 destination="org.freedesktop.ConsoleKit" (uid=0 pid=884 comm="))
Aug 24 16:52:27 xxx dbus-daemon: Rejected send message, 4 matched rules; type="method_call", sender=":1.8" (uid=1001 pid=1931 comm=") interface="org.freedesktop.ConsoleKit.Manager" member="GetCurrentSession" error name="(unset)" requested_reply=0 destination="org.freedesktop.ConsoleKit" (uid=0 pid=884 comm="))
Aug 24 16:52:39 xxx kernel: pid 2002 (plasma-desktop), uid 1001: exited on signal 11 (core dumped)
Aug 24 16:52:49 xxx kernel: pid 2027 (gdb), uid 1001: exited on signal 6 (core dumped)

How do I recompile kde4 with debug symbols on so that I can produce a dump when plasma-desktop crashes?
 
It looks like there is currently a non FreeBSD specific problem with tightvnc and the 32 bit color mode. Please try to start vncserver without "-depth 32" and report back if that works.
 
Yes, set it to 16 and that fixes the problem. Looks like total garbage, but I'm assuming that's a VNC problem and not a KDE4 issue (or a little of both maybe).

Thanks!!!!
 
Indeed, as tightvnc doesn't even work with default settings in 32 bit color mode (just an xterm and twm as windows manager, no KDE4 at all).
 
So for anyone else with this problem some possible solutions appear to be:

TigerVNC (in beta) http://www.tigervnc.org/
NX: http://www.nomachine.com (/usr/ports/net/freenx)
x11vnc /usr/ports/net/x11vnc

I'm trying them out, but each has pitfalls. Good reports have been found about x11vnc, but it requires a real X desktop to be running on the server, which in my situation isn't likely feasible. Hopefully the TigerVNC folks figure out a way to bring the VNC technology to present day standards.
 
You must log in or register to reply here.
Back
Top