reassign 594741 vnc4server thanks OoO Lors de la soirée naissante du vendredi 21 janvier 2011, vers 17:23, "krueger, Andreas (Andreas Krüger, DV-RATIO)" <[email protected]> disait :
> 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. OK, this means that the bug should be in vnc4server (or in gnome-panel). > 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? Maybe it will die the next time it tries to access the X server. > ** (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> You can also add yourself to netdev group to not have this message anymore. The idea is that a remote user should not be able to play with the network. The messages in ~/.xsession-errors about this are therefore harmless. > 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.) Maybe this message would help to figure out why gnome-panel does not work. I reaffect this bug to vnc4server since it seems closer to the culprit than xrdp is. -- /* * We used to try various strange things. Let's not. */ 2.2.16 /usr/src/linux/fs/buffer.c
pgpp0Mypjy8O7.pgp
Description: PGP signature
