vncserver, krfb broken with kde 4.2, Intrepid (critical)
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
KDE Network |
Fix Released
|
Medium
|
|||
kdenetwork (Ubuntu) |
Fix Released
|
Medium
|
Unassigned |
Bug Description
Binary package hint: kdebase
After upgrading to kde 4.2, vncserver stopped working. This is a critical bug in my workplace, were we rely heavily on vnc.
Krfb also does not work. I can initiate a vncserver connection in response to a krfb invitation, but the vncviewer display is fuzzy, with double letters for all text. Clicking in the vncviewer window causes multi-colored screen corruption which makse the window completely unviewable.
This bug has been replication on two hosts:
Kubuntu 8.10 X86_64, KDE 4.2, and an identically-
roberts@
Linux lilly 2.6.27-11-generic #1 SMP Thu Jan 29 19:24:39 UTC 2009 i686 GNU/Linux
Here is my xstartup file:
roberts@
#!/bin/sh
# Uncomment the following two lines for normal desktop:
# unset SESSION_MANAGER
# exec /etc/X11/
#[ -x /etc/vnc/xstartup ] && exec /etc/vnc/xstartup
#[ -r $HOME/.Xresources ] && xrdb $HOME/.Xresources
#xsetroot -solid grey
#vncconfig -iconic &
#xterm -geometry 80x2
Here is the vncserver log:
roberts@
Couldn't open RGB_DB '/etc/X11/rgb'
Xvnc Free Edition 4.1.1
Copyright (C) 2002-2005 RealVNC Ltd.
See http://
Underlying X server release 70000000, The X.Org Foundation
Tue Mar 10 13:12:38 2009
vncext: VNC extension running!
vncext: Listening for VNC connections on port 5901
vncext: created VNC server for screen 0
error opening security policy file /etc/X11/
Could not init font path element /usr/share/
t!
Could not init font path element /usr/share/
!
Could not init font path element /usr/share/
t!
kdostartupconfi
startkde: Starting up...
kdeinit4: preparing to launch /usr/lib/
klauncher(18696) kdemain: Waiting for already running klauncher to exit.
klauncher(18696) kdemain: Waiting for already running klauncher to exit.
klauncher(18696) kdemain: Another instance of klauncher is already running!
kdeinit4: Communication error with launcher. Exiting!
kdeinit4_wrapper: Warning: connect(
1) failed: : Connection refused
Could not register with D-BUS. Aborting.
startkde: Shutting down...
kdeinit4_wrapper: Warning: connect(
1) failed: : Connection refused
Error: Can not contact kdeinit4!
startkde: Running shutdown scripts...
startkde: Done.
Changed in kdenetwork: | |
status: | Unknown → Confirmed |
Changed in kdenetwork (Ubuntu): | |
status: | Confirmed → Triaged |
importance: | Undecided → Medium |
Changed in kdenetwork: | |
status: | Confirmed → Fix Released |
Changed in kdenetwork: | |
importance: | Unknown → Medium |
Folks,
Has anybody reviewed this yet? My group at work relies heavily on vnc, and this bug will prevent us from upgrading until vncserver works with Intrepid and beyond, and KDE4. I've seen lots of chatter on the various lists about this problem, but no activity as of yet on the buglist here.
Thanks,
--Doug