gnome-volume-manager doesn't run

Bug #47301 reported by Sean Middleditch
This bug report is a duplicate of:  Bug #34063: Unable to start g-v-m. Edit Remove
12
Affects Status Importance Assigned to Milestone
gnome-volume-manager (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Binary package hint: gnome-volume-manager

The gnome-volume-manager daemon won't run. If I manually run the command, the process starts and immediately exits. It is *not* crashing; it's calling exit_group(0) [as found by strace].

I haven't been able to find any configuration file or other reason why gnome-volume-manager would essentially be disabling itself like this.

Revision history for this message
Matt Mossholder (matt-mossholder) wrote :

I had this problem as well. gnome-volume-manager is exiting because it does not see a filename /var/run/console/$USER:<virtual terminal#>

This is supposed to indicate that the user owns the console. G-V-M is testing for the existance of the file, so that on multi-user systems, G-V-M only runs for the user who owns the console.

My solution was to include "auth required pam_foreground.so" in /etc/pam.d/gdm.

Revision history for this message
Sean Middleditch (elanthis) wrote :

Hmm, that should be a session module, not an auth module. I checked the differences between my machine at work and the machine with problems at home (both running Dapper) and the machine at home was indeed missing the pam_foreground settings. This is probably because of changes I made to enable Kerberos. Hence, this bug is invalid, and can be closed.

Revision history for this message
Martin Pitt (pitti) wrote :

Closing as duplicate.

Changed in gnome-volume-manager:
status: Unconfirmed → Rejected
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.