Hello,
I have the same problem as does Paolo (in
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=594741 ).
When I ran vnc4server from the command line and connect
through the Java viewer applet, again the gnome panel
is not clickable. So same story, regardless whether I use remote
session (sesman) or Xvnc directly.
This is also running under vnc4server, version 4.1.1+X4.3.0-31.
One peculiarity:
Whenever I kill the VNC X server (either the sesman-created or
the directly created one), and check what is still running under
my user, I find three left over processes:
gnome-panel --sm-client-id default1
/usr/lib/libgconf2-4/gconfd-2 14
/usr/lib/bonobo-activation/bonobo-activation-server --ac-activate
--ior-output-f...
Why would gnome-panel continue to run, when the X server
it was associated with no longer exists?
There are also a lot of error messages in $HOME/.xsession-errors ,
repeated over and over again while the session was running:
** (nm-applet:17390): WARNING **: <WARN> nma_dbus_init(): could not
acquire its service. dbus_bus_acquire_service() says:
'Connection ":1.35" is not allowed to own the service
"org.freedesktop.NetworkManagerInfo" due to security policies
in the configuration file'
To get rid of those, I edited /etc/dbus-1/system.d/nm-applet.conf
--- nm-applet.conf~ 2009-12-16 16:16:51.000000000 +0100
+++ nm-applet.conf 2011-01-21 16:56:01.000000000 +0100
@@ -34,10 +34,11 @@
send_member="updateNetworkInfo"/>
</policy>
<policy context="default">
- <deny own="org.freedesktop.NetworkManagerInfo"/>
+ <!-- changed by Andreas Krüger -->
+ <allow own="org.freedesktop.NetworkManagerInfo"/>
- <deny send_destination="org.freedesktop.NetworkManagerInfo"/>
- <deny send_interface="org.freedesktop.NetworkManagerInfo"/>
+ <allow send_destination="org.freedesktop.NetworkManagerInfo"/>
+ <allow send_interface="org.freedesktop.NetworkManagerInfo"/>
</policy>
<limit name="max_replies_per_connection">512</limit>
That resulted in fewer .xsession-errors, but did not solve
the underlying problem. When sifting through the issues in
.xsession-errors, for example, xkeyboard extensions not being
available, more dbus, and one that particularly stuck out:
The program 'gnome-settings-daemon' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadWindow (invalid Window parameter)'.
(Details: serial 2410 error_code 3 request_code 20 minor_code 0)
(Note to programmers: normally, X errors are reported asynchronously;
that is, you will receive the error a while after causing it.
To debug your program, run it with the --sync command line
option to change this behavior. You can then get a meaningful
backtrace from your debugger if you break on the gdk_x_error() function.)
Finally, I pulled the emergency break and switched from Gnome to Xfce.
As that user, I do not care what is configured for local sessions, so:
echo exec xfce4-session > $HOME/.xsession
This is a viable workaround for me.
Regards, and thank you for providing fine software,
Andreas
--
Dr. Andreas Krüger, Senior Developer
Tel. (+49) (211) 280 69-1132
[email protected]
DV-RATIO NORDWEST GmbH, Habsburgerstraße 12, 40547 Düsseldorf, Germany
für
Hewlett-Packard GmbH H Herrenberger Str. 140 71034 Böblingen www.hp.com/de
Geschäftsführer: Volker Smid (Vorsitzender), Michael Eberhardt, Thorsten
Herrmann,
Martin Kinne, Heiko Meyer, Ernst Reichart, Rainer Sterk
Vorsitzender des Aufsichtsrates: Jörg Menno Harms
Sitz der Gesellschaft: Böblingen S Amtsgericht Stuttgart HRB 244081
WEEE-Reg.-Nr. DE 30409072
