Hi, gnome-volume-manager refuses to start ON SYSTEM CONSOLE, although it works just fine on ltsp x-terminal connected to this host. The last version on gnome-volume-manager which worked on console was 1.5.1. Code to detect "system console" was added later, I recall. This is Gentoo in current updated state. Gnome 2.12.2, now stable. gnome-volume-manager-1.5.4
You either need pam_console on your pam, or you need to touch /var/run/console/<username>
Daniel, (In reply to comment #1) > You either need pam_console on your pam, or you need to touch > /var/run/console/<username> Can you give me any reference how to do do it right, please? Yes, pam_console is commented out in my /etc/pam.d/*. I run multiple X-terminals, and before this I used to run separate X consoles on vt-s. pam_console simply changes device permissions inappropriate way, making it single-user system. I quite don't understand why is pam_console required with gnome. Gnome uses access control based on group membership, right? Ok, I want all my users (me, me on another vt, my wife on x-terminal) be equal users of USB keys, audio, cd, etc. I see following ways to do it as you said: - use pam_console, fix /etc/security/console.perms to set proper 660 permissions on audio, floppy, etc. - comment out everything in /etc/security/console.perms, leaving only minimum required (ownership of /dev/console??? How about second user???) - touch /var/run/console/<username> Why? Should this file(s) be permanent? Will it work is I touch files for both me and the second user? Why based on username, i would prefer "console" based on the host name (I mean by location) and permission to devices be shared by username. Will appreciate any help or link how to make it properly. Thanks, Vadim
The on_console attribute needs to be set in hal/dbus for various things (such as envoking the hal mount functions) to be allowed. Since g-v-m does these types of things, it checks for the on_console attribute, and quits if it's not set. g-v-m is designed for a desktop system, not a multi-user server, and so it does not work well in multiuser environments. Work is suppsedly underway to fix these issues, but it'll be a while yet before it makes it into a release. In the mean time, the only two ways I know of to make g-v-m work is to use pam_console, or to touch (as root, and probably after every boot) /var/run/console/<username> The latter is what I do, so I can't help you with configuring pam_console. If you need multiuser automounting, you might want to investigate alternatives to g-v-m. The most obvious one is ivman, but I've never used it personally.
(In reply to comment #3) > In the mean time, the only two ways I know of to make g-v-m work is to use > pam_console, or to touch (as root, and probably after every boot) > /var/run/console/<username> The latter is what I do, so I can't help you with > configuring pam_console. Doesn't work for me :( ls -l /var/run/console/ total 0 -rw-r--r-- 1 root root 0 Feb 10 15:53 kouzminv and still: gnome-volume-manager ** (gnome-volume-manager:28558): WARNING **: manager.c/2380: not on the system console I restarted gdm/X before trying that.
Try restarting dbus. I don't remember if I had to do that or not, it's been months.
(In reply to comment #5) > Try restarting dbus. I don't remember if I had to do that or not, it's been > months. > It didn't work. After that I even changed ownership of /dev/console but still no luck. BUT thanks to you, I found the problem! It works for me on vt7, without pam_console and /var/run/console/<username> And I've been working on vt8 before. Historically I'm starting two X servers - on vt7 and vt8. My wife used to work on vt7, and me on vt8. Now my wife moved on another terminal, but I still load 2 X servers and work on the second one. Should this be considered as a bug? Why can't we load multiple X servers on the same console and have g-v-m working in each one? Thanks a lot! Vadim
This isn't a new requirement. As far as I know, every version of g-v-m has required this.
(In reply to comment #7) > This isn't a new requirement. As far as I know, every version of g-v-m has > required this. > -- Subject: gnome-volume-manager-1.5.4 requires pam_console or /var/run/console/$(whoami) -- 1) 1.5.1 and below worked for me without pam_console or /var/run/console/$(whoami), and on vt8 (the second X console) 2) 1.5.4 doesn't work for me on on vt8, even with /var/run/console/$(whoami) Didn't check it with pam_console though. 3) 1.5.4 works for me without pam_console or /var/run/console/$(whoami), but only on vt7
As far as I know, to get g-v-m to work, you need : touch /var/run/console/${whoami} at boot, by placing it for example in /etc/conf.d/local.start AND being member of the plugdev group, for hal to autorize you to mount anything. Now, do you steel have this problem, it has been 4 months ?
(In reply to comment #9) > > Now, do you steel have this problem, it has been 4 months ? > Sorry for delay, I checked it again with Gnome 2.14.1 and two gdm-started X-sessions on vt7 and vt8. On both vt7 and vt8 gnome-volume-manager starts fine and works well. Previously it refused to start on vt8 for some unknown reason ("not a system console"). g-v-m also starts fine on my ltsp-powered terminal. Close the bug now. Thanks.
