SRU: vmware-user doesn't autostart
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
VMWare tools |
Unknown
|
Unknown
|
|||
open-vm-tools (Ubuntu) |
Fix Released
|
Low
|
Unassigned | ||
Intrepid |
Invalid
|
Undecided
|
Unassigned |
Bug Description
The version of open-vm-tools in Intrepid includes a vmware-user.desktop file that is intended to automatically start vmware-user on login, but it doesn’t work because the file is missing the line Type=Application.
This line is already present in the Jaunty package. The attached debdiff (comment 2) adds a dpatch to add this line for Intrepid. This allows vmware-user to autostart correctly.
This debdiff also fixes bug #289921 “network interface does not come up after installing open-vm-tools” and bug #306835 “vvmware-guestd crashing”, and descriptions of the corresponding patches are posted there.
The patched package has been in my PPA for four weeks, and confirmed working by three other users. Risk of regression is low, especially given that these three bugs essentially prevent the current Intrepid package from being useful in any way.
===
Binary package hint: open-vm-toolbox
There's a small bug in the vmware-user.desktop file supplied with the open-vm-toolbox package such that the application doesn't automatically start when a new X11 session is started. The details can be found in the upstream bug repository: http://
The fix is trivial: add the line "Type=Application" to vmware-user.desktop (it doesn't matter where).
This is a bug in Intrepid, but not in Jaunty (I believe Jaunty resynced to upstream and picked up the upstream fix for the bug).
adar@adar-
Description: Ubuntu 8.10
Release: 8.10
adar@adar-
open-vm-toolbox:
Installed: 2008.08.
Candidate: 2008.08.
Version table:
*** 2008.08.
500 http://
100 /var/lib/
Changed in open-vm-tools: | |
importance: | Undecided → Low |
description: | updated |
Changed in open-vm-tools (Ubuntu Intrepid): | |
status: | New → Confirmed |
Changed in open-vm-tools (Ubuntu): | |
status: | Confirmed → Fix Released |
Bug was confirmed upstream and fixed in code refresh 2008.11.18