Unable to start g-v-m

Bug #34063 reported by Gianfranco Liporace
58
Affects Status Importance Assigned to Milestone
libpam-foreground (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Today I tried to find why automounting suddently doesn't work, so I followed the guide in the wikipage https://wiki.ubuntu.com/DebuggingRemovableDevices.
But starting g-v-m as described does nothing, since it exits immediatly to the command line and the gvm.log file is empty.

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

Are you sure that you started gnome-volume-manager with option '-n'?

If so, can you please do

  killall gnome-volume-manager
  strace -o gvm.trace gnome-volume-manager -n

and attach gvm.trace here?

Changed in gnome-volume-manager:
assignee: nobody → pitti
status: Unconfirmed → Needs Info
Revision history for this message
Gianfranco Liporace (dr.kabuto) wrote : strace output for g-v-m

killall gnome-volume-manager does nothing since there is no process running.
Attached the strace output.

Revision history for this message
Gianfranco Liporace (dr.kabuto) wrote :

For now, i've reverted to g-v-m 1.5.13-0ubuntu3 since it is the last version that is working for me.

Revision history for this message
Gianfranco Liporace (dr.kabuto) wrote :

Creating file '/var/run/console/$USER:' I got g-v-m running, but the file gets deleted at every reboot. Searching around, i found that this have to do with pam_foreground, which I can't configure myself. I'm wrong?

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

Ah, that explains a lot, thanks for tracking this down. That file is supposed to be created by libpam-foreground (which is a dependency of g-v-m). The idea of that is to not start g-v-m if you remotely log into a machine, since you do not have access to the local storage devices then. Do you do this?

Revision history for this message
Gianfranco Liporace (dr.kabuto) wrote :

No, I work as local user, i own the machine. I think the problem is, that I manually modified the common-auth and common-passwd files to have kerberos authentication, so they weren't modified when libpam-foreground were installed the firts time.
To let you know, i've put pam-foregroundso in common-session to get g-v-m working again.

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

Ah, thank you, that explains the issue. Matthew, I assume there is no chance to add the module even for a modified PAM configuration?

Changed in gnome-volume-manager:
assignee: pitti → mjg59
status: Needs Info → Confirmed
Revision history for this message
Matthew Garrett (mjg59) wrote :

We can't modify conffiles that the user has modified locally, no. I'm not sure what the best workaround is.

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

This seems to bite quite many people. Maybe libpam-foreground could show an update notification or a debconf note if the PAM configuration was modified manually?

Revision history for this message
Gregory Oschwald (osch0001) wrote : My pam.d directory

Here is the contents of my pam.d directory, as Martin requested in bug #43035.

Revision history for this message
Gregory Oschwald (osch0001) wrote :

I should also mention that everything works great after adding the following to /etc/pam.d/common-session:

session optional pam_foreground.so

Revision history for this message
IC Raibow (icrbow) wrote :

Fixed in feisty (at least).

Revision history for this message
Guy Van Sanden (gvs) wrote : Re: [Bug 34063] Re: Unable to start g-v-m

Fixed in Feisty? That's good. Any chance of an Edgy backport?
I really can't move this machine to Feisty yet (because of possible
breakage).

Revision history for this message
Daniel T Chen (crimsun) wrote :

8.10 alpha uses a different method.

Changed in libpam-foreground:
status: Confirmed → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers