[Bug 34063] Unable to start g-v-m

2006-03-28 Thread Martin Pitt
Public bug report changed: https://launchpad.net/malone/bugs/34063 Comment: 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,

[Bug 34063] Unable to start g-v-m

2006-03-28 Thread Gianfranco Liporace
Public bug report changed: https://launchpad.net/malone/bugs/34063 Comment: 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

[Bug 34063] Unable to start g-v-m

2006-03-28 Thread Martin Pitt
Public bug report changed: https://launchpad.net/malone/bugs/34063 Task: ubuntu gnome-volume-manager Sourcepackagename: gnome-volume-manager = libpam-foreground Assignee: Martin Pitt = Matthew Garrett Status: Needs Info = Confirmed Comment: Ah, thank you, that explains the issue.

[Bug 34063] Unable to start g-v-m

2006-03-15 Thread Gianfranco Liporace
Public bug report changed: https://launchpad.net/malone/bugs/34063 Comment: 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? --

[Bug 34063] Unable to start g-v-m

2006-03-13 Thread Gianfranco Liporace
Public bug report changed: https://launchpad.net/malone/bugs/34063 Comment: For now, i've reverted to g-v-m 1.5.13-0ubuntu3 since it is the last version that is working for me. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 34063] Unable to start g-v-m

2006-03-09 Thread Martin Pitt
Public bug report changed: https://launchpad.net/malone/bugs/34063 Task: ubuntu gnome-volume-manager Assignee: (unassigned) = Martin Pitt Status: Unconfirmed = Needs Info Comment: Are you sure that you started gnome-volume-manager with option '-n'? If so, can you please do

[Bug 34063] Unable to start g-v-m

2006-03-09 Thread Gianfranco Liporace
Public bug report changed: https://launchpad.net/malone/bugs/34063 - Changed attachments: Added: strace output for g-v-m http://librarian.launchpad.net/1680342/gvm.trace -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com

[Bug 34063] Unable to start g-v-m

2006-03-08 Thread Gianfranco Liporace
Public bug reported: https://launchpad.net/malone/bugs/34063 Affects: gnome-volume-manager (Ubuntu) Severity: Normal Priority: (none set) Status: Unconfirmed Description: Today I tried to find why automounting suddently doesn't work, so I followed the guide in the