As a new user of Ubuntu 7.10 I found that the system monitor panel was
showing extreme fluctuations of cpu usage, from 20% to over 98%.
Somewhere I read about vino-session and thought about removing it to
ease the load on the cpu. But it wouldn't let me change the priority to
19. Everytime I do
There is no duplicate and the subscriber counts is low, that doesn't
qualify the bug for a stable upload, those require extra work and
usually limited to security bugs and really annoying issues
--
When remote desktop access is disabled, vino-session will still run
I think vino-session should be disabled, here's why:
1)
This happens because vino on Ubuntu (which was merged from debian)
is compiled with --enable-session. Without that flag, the process
responsible for start/stop the deamon is gnome-session.
So, there are two ways:
1) patch gnome-session
Ok, now I am sure :) I just downloaded the sources for the gnome-session
package (apt-get source gnome-session). In the file gnome-session-2.20.1
/gnome-session/ChangeLog you can read:
2.7.91
2004-08-16 Mark McLoughlin [EMAIL PROTECTED]
*
Vino in Hardy is not built with --enable-session-support flag.
** Changed in: vino (Ubuntu)
Status: Confirmed = Fix Released
--
When remote desktop access is disabled, vino-session will still run
https://bugs.launchpad.net/bugs/141160
You received this bug notification because you are a
Ok, wonderful. But what about Gutsy? Shouldn't we do the same for Gutsy
too?
--
When remote desktop access is disabled, vino-session will still run
https://bugs.launchpad.net/bugs/141160
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for
There doesn't seem to be any easy change that we can do at this stage
without breaking GConf functionality (if we start vino-session from the
capplet, we lose the possibility of sharing the desktop by tweaking
GConf values from a SSH session for example). It's probably going to
fit closer to a
The GNOME hackers are working on a new gnome-session[1], which will fix
this bug. So, i'd close this one or reassing it to other component
rather than vino.
[1] - http://svn.gnome.org/viewcvs/gnome-session/branches/new-gnome-
session/
--
When remote desktop access is disabled, vino-session will
I agree that the cleanest way is to watch the GConf key and start a
process based on its changes: it's how other GConf settings work, for
example all gnome-settings-daemon settings.
Perhaps it would be clearer to simply name the watcher vino-watcher or
vino-launcher so that users could easily
Why not just making the binary return directly when the key is set?
** Changed in: vino (Ubuntu)
Importance: Undecided = Low
Status: New = Confirmed
** Changed in: vino (Ubuntu)
Target: None = ubuntu-7.10-rc
--
When remote desktop access is disabled, vino-session will still
Just setting/unsetting a key in gconf won't start a daemon. That's what
the session bit does -- it watches the gconf key, and starts a daemon if
it's changed to true (I guess). So you'd have to log out and back in
again for the daemon to start if you changed the key manually. So gnome-
session
Em Ter, 2007-09-25 às 16:42 +, Martijn van de Streek escreveu:
Just setting/unsetting a key in gconf won't start a daemon. That's what
the session bit does -- it watches the gconf key, and starts a daemon if
it's changed to true (I guess). So you'd have to log out and back in
again for the
why do you want to patch gnome-session to special case vino-server? It
should not be registered in the session if it should not be started or
the binary should just return when the gconf key is set so the session
start it, the server look at the key and return and there is nothing
running when not
Em Ter, 2007-09-25 às 19:38 +, Sebastien Bacher escreveu:
why do you want to patch gnome-session to special case vino-server? It
should not be registered in the session if it should not be started or
the binary should just return when the gconf key is set so the session
start it, the
the preference dialog that you use to set the key to true starts the
service?
--
When remote desktop access is disabled, vino-session will still run
https://bugs.launchpad.net/bugs/141160
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for
This happens because vino on Ubuntu (which was merged from debian) is
compiled with --enable-session. Without that flag, the process
responsible for start/stop the deamon is gnome-session.
I don't know if Ubuntu developers would consider this as a bug. So,
Sebastien, it's up to you to fix or to
Jonh, what difference does it make? How vino starts if that's not by
gnome-session? Shouldn't it exit when it's disabled whatever way is used
to run it?
--
When remote desktop access is disabled, vino-session will still run
https://bugs.launchpad.net/bugs/141160
You received this bug
The server executable is /usr/lib/vino/vino-server.
It only must run when the gconf key /desktop/gnome/remote_access/enabled is
true.
So, there are two ways:
1) patch gnome-session to watch that key and run vino-server when the key is
true.
2) deploy its own 'watcher', called vino-session, by
18 matches
Mail list logo
