GNOME Bugzilla – Bug 575004
gnome-session sometimes autostarts applications that are already running
Last modified: 2021-06-14 18:20:36 UTC
Please describe the problem: A user reported that gnome-session was consuming a lot of CPU bandwidth and logging a lot of information to disk. After looking at the users logs, it became clear that gnome-session was continually trying to restart vino-server, over and over again. That bug report can be found here: https://bugs.edge.launchpad.net/ubuntu/+source/gnome-session/+bug/340515 vino-server ships an autostart desktop file with "X-GNOME-AutoRestart=true" and "AutostartCondition=GNOME /desktop/gnome/remote_access/enabled". vino-server will also exit if there is already another instance already running. I can trigger this problem by manually running vino-server, then modifying /desktop/gnome/remote_access/enabled so that the autostart condition is met. Once I've done this, gnome-session tries to start a second instance of vino-server, which immediately exits. This then starts an infinite cycle which brings my machine virtually to its knees. The first instance of vino-server already registered with gnome-session, so I don't think it should try and start another if the autostart condition becomes satisfied. Steps to reproduce: 1. Run "gconftool-2 -s --type=bool /desktop/gnome/remote_access/enabled 0" 2. Run "/usr/lib/vino/vino-server" 3. Run "gconftool-2 -s --type=bool /desktop/gnome/remote_access/enabled 1" Actual results: gnome-session tries to start a second instance of vino-server, which immediately exits because there is one already running Expected results: gnome-session shouldn't try to start a second instance. The first instance already registered itself with gnome-session Does this happen every time? Yes Other information:
(In reply to comment #0) > A user reported that gnome-session was consuming a lot of CPU bandwidth I am said user. :) > Steps to reproduce: > 1. Run "gconftool-2 -s --type=bool /desktop/gnome/remote_access/enabled 0" > 2. Run "/usr/lib/vino/vino-server" > 3. Run "gconftool-2 -s --type=bool /desktop/gnome/remote_access/enabled 1" At least for me, step 3 is enough; I do not need to manually start vino-server to trigger this bug. Could be a difference in setup though; let me know if we need to test that differently at all.
Seems to be resolved now on 2.26.0, whether it was vino or gnome-session that fixed it I'm not sure.
Hi, I've just upgraded to Ubuntu Jaunty (GNOME 2.26.1) and noticed this bug instantly. So I guess this is not fixed after all.
Still an issue with gnome-session 2.26.1, reopening.
I can confirm it is still happening with vino 2.26.1-0ubuntu1 and gnome-session 2.26.0svn20090408-0ubuntu2 on my up-to-date Jaunty box.
And I can confirm it on OpenSolaris with gnome-session 2.27.4 and vino 2.26.2.
GNOME is going to shut down bugzilla.gnome.org in favor of gitlab.gnome.org. As part of that, we are mass-closing older open tickets in bugzilla.gnome.org which have not seen updates for a longer time (resources are unfortunately quite limited so not every ticket can get handled). If you can still reproduce the situation described in this ticket in a recent and supported software version of gnome-session, then please follow https://wiki.gnome.org/GettingInTouch/BugReportingGuidelines and create a new ticket at https://gitlab.gnome.org/GNOME/gnome-session/-/issues/ Thank you for your understanding and your help.