View previous topic :: View next topic |
Author |
Message |
steffmeister n00b
Joined: 18 Feb 2006 Posts: 37 Location: Doppel, Austria
|
Posted: Fri Mar 03, 2006 9:32 am Post subject: [SOLVED] gnome-volume-manger: couldn't execute pmount |
|
|
hi
there may exist a similar thread, but i didn't want to read all those threads, if there is a similiar please post me a link...
and here comes to problem:
when i plug in a usb stick, gnome-volume-manager (and hal...) seems to recognize it, nautilus gives me a nice icon, but it does not mount when i click on it because of 'couldn't execute pmount'...
so i tried entering 'pmount /dev/sda1' (sda1 is the usb stick!) and the stick gets mountet and i can access it...
why doesn't it work from nautilus and how can i fix this??
i have gnome 2.12 and kernel 2.6.15 installed...
mfg steff.
Last edited by steffmeister on Mon Mar 06, 2006 1:11 pm; edited 1 time in total |
|
Back to top |
|
|
Mickael Advocate
Joined: 05 Sep 2005 Posts: 2387 Location: ~Belfort! - France - EU
|
Posted: Fri Mar 03, 2006 9:48 am Post subject: |
|
|
Add your user inside the plugdev group. |
|
Back to top |
|
|
steffmeister n00b
Joined: 18 Feb 2006 Posts: 37 Location: Doppel, Austria
|
Posted: Fri Mar 03, 2006 5:44 pm Post subject: |
|
|
thx for the quick answer but i am already in the plugdev group:
Code: | steff@steff ~ $ groups
wheel floppy audio cdrom video games usb users plugdev
steff@steff ~ $
|
here is a output from gnome-volume-manager, it may help (some of the messages are in german, though (i tried to translate it)...
Code: | steff@steff ~ $ gnome-volume-manager
manager.c/607: setting[0]: bool: autobrowse = 0
manager.c/607: setting[1]: bool: autoburn = 0
manager.c/594: setting[2]: string: autoburn_audio_cd_command = nautilus --no-desktop burn:
manager.c/594: setting[3]: string: autoburn_data_cd_command = nautilus --no-desktop burn:
manager.c/607: setting[4]: bool: autoipod = 0
manager.c/594: setting[5]: string: autoipod_command =
manager.c/607: setting[6]: bool: automount_drives = 1
manager.c/607: setting[7]: bool: automount_media = 1
manager.c/607: setting[8]: bool: autophoto = 0
manager.c/594: setting[9]: string: autophoto_command =
manager.c/607: setting[10]: bool: autopalmsync = 0
manager.c/594: setting[11]: string: autopalmsync_command = gpilotd-control-applet
manager.c/607: setting[12]: bool: autoplay_cda = 1
manager.c/594: setting[13]: string: autoplay_cda_command = totem %d
manager.c/607: setting[14]: bool: autoplay_dvd = 1
manager.c/594: setting[15]: string: autoplay_dvd_command = totem %d
manager.c/607: setting[16]: bool: autoplay_vcd = 1
manager.c/594: setting[17]: string: autoplay_vcd_command = totem %d
manager.c/607: setting[18]: bool: autopocketpc = 0
manager.c/594: setting[19]: string: autopocketpc_command = multisync
manager.c/607: setting[20]: bool: autoprinter = 0
manager.c/594: setting[21]: string: autoprinter_command = gnome-printer-add hal://%h
manager.c/607: setting[22]: bool: autorun = 0
manager.c/594: setting[23]: string: autorun_path = .autorun:autorun:autorun.sh
manager.c/594: setting[24]: string: eject_command = /bin/eject %d
manager.c/594: setting[25]: string: mount_command =
manager.c/594: setting[26]: string: unmount_command =
manager.c/2241: mount_all: mounting /dev/sda1
manager.c/1330: mounting /org/freedesktop/Hal/devices/volume_uuid_BC61_7EBF...
manager.c/753: executing command: pmount-hal /org/freedesktop/Hal/devices/volume_uuid_BC61_7EBF
manager.c/2241: mount_all: mounting /dev/hda5
manager.c/1330: mounting /org/freedesktop/Hal/devices/volume_uuid_1a804c60_61f9_4c82_aeb8_cdccf5fbdf95...
manager.c/753: executing command: pmount-hal /org/freedesktop/Hal/devices/volume_uuid_1a804c60_61f9_4c82_aeb8_cdccf5fbdf95
manager.c/2241: mount_all: mounting /dev/hda8
manager.c/1330: mounting /org/freedesktop/Hal/devices/volume_uuid_b472057b_a58c_4ead_96d7_3ebba3f1fd7d...
manager.c/753: executing command: pmount-hal /org/freedesktop/Hal/devices/volume_uuid_b472057b_a58c_4ead_96d7_3ebba3f1fd7d
manager.c/2241: mount_all: mounting /dev/hdb1
manager.c/1330: mounting /org/freedesktop/Hal/devices/volume_uuid_8626_37D6...
manager.c/753: executing command: pmount-hal /org/freedesktop/Hal/devices/volume_uuid_8626_37D6
manager.c/2241: mount_all: mounting /dev/hdb5
manager.c/1330: mounting /org/freedesktop/Hal/devices/volume_uuid_1337e329_fa7c_4a2b_8a22_65421ea8ed70...
manager.c/753: executing command: pmount-hal /org/freedesktop/Hal/devices/volume_uuid_1337e329_fa7c_4a2b_8a22_65421ea8ed70
manager.c/2241: mount_all: mounting /dev/hdb6
manager.c/1330: mounting /org/freedesktop/Hal/devices/volume_uuid_e14742ae_3eb2_4928_98fd_fd66db33ad5f...
manager.c/753: executing command: pmount-hal /org/freedesktop/Hal/devices/volume_uuid_e14742ae_3eb2_4928_98fd_fd66db33ad5f
Warning: device /dev/hda5 is already handled by /etc/fstab, supplied label is ignored
mount: Laut mtab ist /dev/hda5 schon auf / eingehängt
mount ist fehlgeschlagen
Error: could not execute pmount
Error: device /dev/hda8 is not removable
Error: could not execute pmount
Error: device /dev/hdb1 is not removable
Error: could not execute pmount
Error: device /dev/hdb5 is not removable
Error: could not execute pmount
Error: device /dev/hdb6 is not removable
Error: could not execute pmount
mount: Falscher Dateisystemtyp, ungültige Optionen, der
Superblock von /dev/sda1 ist beschädigt oder es sind
zu viele Dateisysteme eingehängt
Error: could not execute pmount |
the last but one message is complaining about wrong fs type, invalid options, the "superblock" of /dev/sda1 may be damaged or too many fs are mounted...
this:
mount: Laut mtab ist /dev/hda5 schon auf / eingehängt
mount ist fehlgeschlagen
means that /dev/hda5 is already mounted at / and that the mount failed...
as already said: "pmount /dev/sda1" just works.... |
|
Back to top |
|
|
steffmeister n00b
Joined: 18 Feb 2006 Posts: 37 Location: Doppel, Austria
|
Posted: Sat Mar 04, 2006 9:29 pm Post subject: |
|
|
and this might also be interesting:
works... oke i told you about that three times, but heres now the interesting part:
Code: | pmount-hal /dev/sda1 |
does NOT work, and i think gnome-volume-manager executes pmount-hal...
can someone tell me whats the difference between pmount-hal and ordinary pmount?? and why does pmount-hal not work..? |
|
Back to top |
|
|
steffmeister n00b
Joined: 18 Feb 2006 Posts: 37 Location: Doppel, Austria
|
Posted: Mon Mar 06, 2006 1:10 pm Post subject: |
|
|
alright, i finally did it...
my problem was that the default encoding vor fat drives seems to be utf8, utf8 wasn't compiled in the kernel nor as a module...
i compiled it in and everything works.... |
|
Back to top |
|
|
massysett Apprentice
Joined: 06 Jan 2006 Posts: 296 Location: Silver Spring, Maryland USA
|
Posted: Wed Apr 26, 2006 11:37 pm Post subject: |
|
|
steffmeister wrote: | alright, i finally did it...
my problem was that the default encoding vor fat drives seems to be utf8, utf8 wasn't compiled in the kernel nor as a module...
i compiled it in and everything works.... |
Don't know how you figured that out, but thank you! I had a similar problem: ivman would automount my flash drive fine, but only if it was running systemwide. The per-user ivman would not automount the drive--so I couldn't unmount it without becoming root. I compiled the utf-8 module, and now it works. _________________ Draft Windows-to-Linux Guide |
|
Back to top |
|
|
swigrid Tux's lil' helper
Joined: 25 Aug 2005 Posts: 124
|
Posted: Mon Dec 11, 2006 12:21 am Post subject: |
|
|
hi there,
i have similar problem, but compile utf8 as module didn't help me. my default codepage for FAT is 850 and iocharset is iso8859-1. |
|
Back to top |
|
|
|