vino is not activated for gdm (itself)
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
vino (Ubuntu) |
Invalid
|
Wishlist
|
Unassigned |
Bug Description
Binary package hint: vino
Vino will not work after the upgrade karmic/lucid for the gdm session itself. Changes to the default configuration, which will fix that, are lost after the upgrade.
I regard this to be a bug, because remote graphical login should be possible on a modern distribution. Former settings should be respected in the upgrade process as well.
There is an old step-by-step tutorial on how to enable vino for gdm. Please consider, if that configuration change will still be acceptable for the lucid release. (No code, just config).
http://
Will this chance impose a security threat because of vino probably running with root privileges?
If not, please consider inclusion of the changes.
The missing gdm.conf settings may probably be substituted by adding the following lines to schema
<schema>
<
<
<
</schema>
Please check this.
KillInitClients is documented in http://
ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: vino 2.28.2-0ubuntu2
ProcVersionSign
Uname: Linux 2.6.32-21-generic i686
NonfreeKernelMo
Architecture: i386
Date: Fri Apr 23 00:15:28 2010
ProcEnviron:
SHELL=/bin/bash
PATH=(custom, user)
LANG=de_AT.UTF-8
LANGUAGE=german
SourcePackage: vino
Changed in vino (Ubuntu): | |
importance: | Undecided → Wishlist |
That version is no more supported