Gnome-volume-manager can't automount removable media any more

Strange, I don't know why, it worked perfectly, but now it lost functionability. Anyone with any suggestion? Thanks in advance.

Similar Messages

[SOLVED]gnome-volume-manager / hal 0.5.10 - can't deactivate automount

http://wiki.archlinux.org/index.php/HAL
I've created /etc/hal/policy/preferences.fdi
<?xml version="1.0" encoding="UTF-8"?>
<deviceinfo version="0.2">
<device>
<match key="storage.hotpluggable" bool="false">
<match key="storage.removable" bool="false">
<merge key="storage.automount_enabled_hint" type="bool">false</merge>
</match>
</match>
</device>
</deviceinfo>
The article say "Policies" may be deprecated in hal 0.5.10. I doubt that, but i dont know what is deprecated though.
I did check the documentation out, and everything i did still seems to be valid.
http://people.freedesktop.org/~david/ha … ies-volume
Does gnome-volume-manager honor this setting in gnome 2.20?
Last edited by pelle.k (2008-02-04 20:12:51)

It would seem i solved it myself.
First of all, gnome-volume-manager need to be recompiled with a patch i found (ubuntu gutsy); http://patches.ubuntu.com/by-release/ex … hint.patch
Why this isn't included by default in gnome-volume-manager is beyond me!? You bad, bad, gnome devs!
Replace the PKGBUILD when building from ABS.
# Contributor: Link Dupont <[email protected]>
pkgname=gnome-volume-manager
pkgver=2.17.0
pkgrel=3
pkgdesc="GNOME daemon to auto-mount and manage media devices"
arch=(i686 x86_64)
license=('GPL')
url=http://www.gnome.org/
depends=('libgnomeui>=2.20.0' 'libnotify>=0.4.4' 'gnome-mount>=0.6')
makedepends=('nautilus>=2.20.0' 'perlxml' 'pkgconfig')
install=gnome-volume-manager.install
groups=('gnome-extra')
source=(http://ftp.gnome.org/pub/GNOME/sources/${pkgname}/2.17/${pkgname}-${pkgver}.tar.bz2
gvm-mount-async.patch
gvm-check-local.patch
http://patches.ubuntu.com/by-release/extracted/ubuntu/g/gnome-volume-manager/2.17.0-2ubuntu2/02_honour_automount_enabled_hint.patch)
md5sums=('104cec26e721e0bba69debd392367195'
'534b8b9633148bd975b2b9b518c41fb4'
'cb45810b2adb95d39e1272470f10a21a'
'7288a9dc57df321d6a379c9b6a7caaff')
build() {
cd ${startdir}/src/${pkgname}-${pkgver}
patch -Np0 -i ${startdir}/src/gvm-mount-async.patch || return 1
patch -Np0 -i ${startdir}/src/gvm-check-local.patch || return 1
patch -Np1 -i ${startdir}/src/02_honour_automount_enabled_hint.patch || return 1
./configure --prefix=/usr --sysconfdir=/etc \
--localstatedir=/var
make || return 1
make GCONF_DISABLE_MAKEFILE_SCHEMA_INSTALL=1 DESTDIR=${startdir}/pkg install
mkdir -p ${startdir}/pkg/usr/share/gconf/schemas
gconf-merge-schema ${startdir}/pkg/usr/share/gconf/schemas/${pkgname}.schemas ${startdir}/pkg/etc/gconf/schemas/*.schemas
rm -f ${startdir}/pkg/etc/gconf/schemas/*.schemas
Also, this is my /etc/hal/fdi/policy/preferences.fdi
<match key="storage.hotpluggable" bool="false">
<match key="storage.removable" bool="false">
<merge key="storage.automount_enabled_hint" type="bool">false</merge>
</match>
</match>
If you compare that to my first version, you'll note that it is *not* enclosed in <deviceinfo> and <device> tags, simply because that wouldn't work. Don't ask me why. i'm by no means a HAL expert...
Last edited by pelle.k (2008-02-04 20:12:00)

Gnome-volume-manager doesn't work, nor another automounter

Hi there,
I have installed gnome-volume-manager but it apparentely does not work. I've followed the instructions from the FAQ - Arch Linux, and I have tried also recompiling it with --enable-automounting. I have tried also having Nautilus opened at the same time but it didn't work. My WM is IceWM.
//ivman works for the cdrom but not for usb devices. And I don't like AutoFS.
Last edited by jmcejuela (2009-04-10 15:06:34)

I had this problem and it was related to ConsoleKit not being initialized properly. I was using SLIM as login manager and had to add ck-launch-session to my .xinitrc when starting the gnome session.
Last edited by iBertus (2009-04-10 17:21:33)

[SOLVED] gnome-volume-manager is lazy

Until some update that I missed all was fine. I boot, my volumes are mounted, I can see them in ROX (my main file management program).
I insert a CD/DVD/whatever, its mounted and its all in /media/.:D
But now it just does nothing, until I start Nautilus, then everything gets mounted.
I close Nautilus, and it doesnt mount anything again.
gnome-volume-manager process is up and running after login before running nautilus and after closing it too.
How can I make it behave nicely without the nuisance that Nautilus is?
Oh and Im running Openbox as the window manager in Gnome, Nautilus desktop handling disabled.
Last edited by Hohoho (2008-05-28 20:21:12)

i had the same problem.
i looked in the changelog and it appears that from now on the automount function is disabled upstream because that function is to be handled by the nautilus ( http://ftp.gnome.org/pub/GNOME/sources/ … .3.changes ). For me it is a problem because i use openbox and thunar, so you just have to recompile the package with the option: "--enable-automount" .
info from:
~/Desktop/gnome-volume-manager-2.22.3 $ ./configure --help
then start it ( after recompiling with abs, for example ), but look that the path changed, now in my autostart file for openbox i have:
/usr/lib/gnome-volume-manager/gnome-volume-manager --sm-disable --daemon=yes &
hope it helps you, because this annoyed me for a long time and this is the only easy way to mount my partitions easily
Last edited by Diaz (2008-05-28 20:04:56)

Dbus/hal/gnome-volume-manager problem

I've got hal and dbus running but it doesnt even seem that gnome-volume-manager is started. I added it to my gnome session but that didnt seem to do the trick. I'm trying to be able to just plug in my usb key and ipod and have them automount. It works if I restart hal or run gnome-volume-manager from the command line but then work work again unless I restart that stuff again. Here is a cut from my fstab:
/dev/sda1 /mnt/usb auto user,noauto 0 0
/dev/sda2 /mnt/ipod auto user,noauto 0 0

Hi lhoerste,
I had this problem with automount as well. The way I fixed it was adding
dbus hal to daemons line in /etc/rc.conf. You probably did this already.
Next, when you are in the gnome desktop, stick in a cd. Nothing happens right?
Now go to preferences=>removable drives and media (I think this is what it is called. I'm not sitting infront of my computer at the moment). Then make sure that the checkboxes pertaining to "mount automatically" are checked.
Close window.
Now your cd should automount and appear on the desktop. Eject the cd by right clicking on the icon and choosing eject.
Now, restart and ***make sure you save settings*** before leaving.
Get back into the gnome desktop and plug your cd back in. It should automount now.
This is how I got automount to work for me.

Mounting drives on a udev+hal+gnome-volume-manager setup

Hi,
I set up Arch Linux on a friends computer. The setup seems to work, for example gnome-cd is started when one inserts an Audio CD. However, everything that involves mounting does not work. The error message given by gnome-volume-manager is
mount: wrong fs type, bad option, bad superblock on /dev/sda1,
or too many mounted file systems
* /bin/mount has sid set, 755, owner and file group are root
* udev is set up correctly, so /dev/hdc for example does have write rights for the group disk, and the user is member of that group.
What could be wrong?

The problem was mainly about mounting, and not about /dev/sda or /dev/hdc. We found the solution:
The "mount" binary in Arch's current is confused by the entry "managed" that hal puts in /etc/fstab. You can correct this by
a) Adding a policy file in /usr/share/hal/fdi/95userpolicy named, for example, local.fdi that hinders hal from doing so:
<?xml version="1.0" encoding="ISO-8859-1"?> 
<deviceinfo version="0.2">

<device>
<match key="info.udi" string="/org/freedesktop/Hal/devices/computer">
<merge key="storage.policy.default.managed_keyword.primary" type="string">user</merge>
</match>
</device>
</deviceinfo>
Then restart hal by typing
/etc/rc.d/hal restart
as root
b) Patching "mount" as described in Arch Linux bug #1930.[/code]

Suggestion for dbus, hal. new gnome-volume-manager-version.

Heya,
I just installed dbus, hall from cvs and gnome-volume-manager from tarball and have some suggestions:
dbus:
the default during configure seems to be to detect if you have the necessary things installed and based on that enable a component.
To disbale qt-bindings add:
--disable-qt
to configure, else it will try to compile the qt-bindings and without a libGL.la it won't work ... (and this isn't in the Mesa package or wasn't anyway as far as I can tell).
hal:
could you add the option "--enable-fstab-sync" to configure in the new versions? It seems to be usefull . It can be it wasn't available earlier ...
gnome-volume-manager:
I just upgraded to 0.9.9 If anyone wants to have the binary just tell me where to upload.
greetz,
Michel

Michel wrote:
Heya,
I just installed dbus, hall from cvs and gnome-volume-manager from tarball and have some suggestions:
dbus:
the default during configure seems to be to detect if you have the necessary things installed and based on that enable a component.
To disbale qt-bindings add:
--disable-qt
to configure, else it will try to compile the qt-bindings and without a libGL.la it won't work ... (and this isn't in the Mesa package or wasn't anyway as far as I can tell).
there are solutions on this forum to fix the libGL.la. this file will be included with future builds of xorg/xfree86. NVIDIA drivers should also provide this file. this file is only an issue for building.
file a bug report feature report to add this build option to the package
hal:
could you add the option "--enable-fstab-sync" to configure in the new versions? It seems to be usefull . It can be it wasn't available earlier ...
if this package is in one of the three official repos file a feature request.
gnome-volume-manager:
I just upgraded to 0.9.9 If anyone wants to have the binary just tell me where to upload.
if a package has just fallen out of date up to about two week leave time for the maintainer to upgrade it . you can flage the package out of date via the web page. this is way better than offering it to people or uploading it somewhere.
the flag otu of date feature is always a better option to cluttering the list with update requests and the bug tracker is the best way to convey your wanted build changes. alot of the developers do not frequent this forum but all are member of the bug tracker notification system.

Gnome-volume-manager freezes xfce4 on logout

Hi there,
I configured gnome-volume-manager to automatically mount drives (esp. usbsticks and so on) and it is working quite smoothly.
But one side effect is bothering me a little:
As suggested in a gnome-volume-manager HowTo, the volume manager is loaded on startx in the following form
<.xinitrc>
exec startxfce4 & exec gnome-volume-manager
</.xinitrc>
as soon as I try to quit my Xfce session the session hangs and will not terminate properly, i.e. logfoff-screen appears but session is not ended.
I waited for quite a while (about an hour :shock: )...
As I didn't change too much over the last few days, I quickly found out that the gnome-volume-manager is the culprit. As soon as the 'exec gnome-volume-manager' part is removed, Xfce will shut down normally.
Has anyone else encountered this side effect? Is there a solution?
Greez and Thx
Bernhard

JGC wrote:I wouldn't start gnome-volume-manager that way, I would configure xfce4 to add gnome-volume-manager to the session when it starts up. Putting it in your .xinitrc makes xfce4 unaware of gnome-volume-manager.
Sounds logical.
It was the way described in the HOwTo, though. That's why I started the volume-manager like this. I would have preferred a more general approach, starting the gnome-volume-manager someplace more general (and not separately for each user)
I guess the correct place would be somewhere in ~/.config/xfce4??
I would have thought maybe the xinitrc that resides there... (Maybe along with xftaskbar4...)
Or is there a more suitable file??
Greez
bernhard

Firewire and gnome-volume-manager

I have a firewire scanner, when hotplugged, nothing happens in gnome. I have 'run when scanner is plugged' checked, but I get nothing.
Does gnome-volume-manager work with firewire devices? or is it just my scanner? (Canon 2540 photo)

I don't know about scanners, but my firefire external HD is recognised perfectly by gnome-volume-manager. So it does listen for firewire devices. Maybe you'll need to add something to udev to make gnome-volume-manager know it's a scanner?
I have a scsi scanner, so I won't try hotplugging it

Hal/Dbus/gnome-volume-manager mount permission problem

Hello,
I have hal/dbus/gnome-volume-manager installed (of course I use gnome as DE).
I need help in configuring the permissions for automatically mounted disk/partitions.
When I connect an external USB HDD having 1 NTFS and 1 partition, these partitions are auto-mounted and the desktop icons appear for the both.
As a normal user I am able to read/write FAT partition (I think, not because I have configured anything properly, but because FAT does not support permissions on filesystem), but I am not even able to read (browse) NTFS filesystem (ERORR: You do not have permission...).
Yes, I have NTFS filesystm support enabled, because I am able to access that same NTFS partition as root.

Well, Thanks for the reply but I had not put any static entry in fstab for this external USB HDD.
Anyway, I figured out something (havn't tested it yet)
When an external USB HDD is attached ... depending storage.policy and volume.policy rules in /usr/share/hal .. the hal daemon (hald) calls fstab-sync with appropriate parameters.
fstab-sync, then, generates /etc/fstab enteries automatically (with comment=managed keyword).
I have added a user policy so that umask and gid value is set correctly. I'll test is as soon as I'll get time.
In the meanwhile if anybody have any other suggestions, please post it here.

My ipod touch can´t play some music any more

my ipod touch can´t play some music any more. iTunes don´t transfer it to my ipod touch but the capacity is taken. Can someone help me please?

My problem is a bit different, but I suspect not really unrelated. With very few exceptions, my entire music library on my iPod Touch is mixed up since updating to iOS 5. Albums display with incorrect album artwork, and contents of the albums is a jumbled mix of unrelated songs (could be any song from my library). And they won't play. The library is fine on my computer.
I removed all of the music from the iPod, then re-synched it with no improvement.
I also removed all apps other than those that come with the iOS, thinking it may be an incompatibility. Also no improvement.
My next attempt was going to be restoring to original settings, but it sounds like folks have tried that with no luck.
I hope Apple is reading these posts and looks into what sounds like a myriad of issues with the new iOS!

Hello, in december 2014 a bouth photoshop elements and know, sinds i downloaded something else from adobe, i can't get on it any more, i have only a trial version and in 30 days i need to pay. How is this possibel?

Hello, in december 2014 a bouth photoshop elements and know, sinds I downloaded something else from adobe, I can't get on it any more, I have a trial version now and in 30 days I have to pay for it. How is this possible?

Unfortunately, only Adobe customer service can assist you with your issue. These are user forums; you are not addressing Adobe here.
Click on the link below, and after that click on "Still need Help? Contact us."
Then on the next page, click Chat
There is also a phone option. 1 (800) 833-6687
http://helpx.adobe.com/contact.html?step=PHXS_downloading-installing-setting-up_licensing- activation

Why can I not import pictures any more? Lightroom says "Your Lightroom 5 64-bit does not work correctly"

Why can I not import pictures any more?
Lightroom says "Your Lightroom 5 64-bit does not work correctly"
Technical informations:
PC with Windows 7 64-bit, Lightroom 5.7.1 64-bit installed.
What I have done:
I downloaded the newest LR 5.71 and installed it again - mode repair; without success
I checked my PC with Norton 360: full scanning and optimizing registry
I restarted the PC and than I installed the LR 5.7 again - repair
Trouble 1:
Two days ago I could work with my LR 5 and to import pictures from a SD was no problem. Now I can start LR 5 and I can watch/modify pictures, but as soon as I try to import new pictures LR 5 stops and gives the message "your LR 5 64-bit does not work correctly - searching for solution". I have not changed anything in my computer since lasttime LR 5 worked properly, only the registry was optimized by Norton 360.
Trouble 2:
I live in Switzerland and my language ist German. I dit not find a place where I can present my problem in German, e.g. a phone number oder email-address oder german-chat. My English is to week for a discussion for computer problems and do understand it.
Help:
I would very appreciate if anybody can help me, either to trouble 1 or to trouble 2. Thanks.

Sehen Sie diesen Beitrag:
Photoshop CS4 & Lightroom 2.6 X64 funktionieren nicht mehr
Wacom Tablet-Treiber-Problem?

Why when I tried to update itunes it crashed and now I get a MSVCR80.dll was not found and can not start my itunes any more

Why when I tried to update itunes it crashed and now I get a MSVCR80.dll was not found and can not start my itunes any more?

Solving the iTunes Installation Problems in Windows
1. Apple has posted their solution here: iTunes 11.1.4 for Windows- Unable to install or open - MSVCR80 issue.
2. If the Apple article does not fully resolve the problem for you, then try Troubleshooting issues with iTunes for Windows updates - MSVCR80.

Help, my googlemaps can not use the gps any more after updated the software.

hello
i am fresh here
about a month ago i got a 9630 from bell
at first the googlemap works well, but a few days ago i updated the software(9630AMEA_PBr4.7.1_rel77_PL4.1.0.40_A4.7.1.40_Bell_Mobility_Inc)
since then it can't use the gps any more.
it always say "your current location is temporarily unavailable. gps temporarily unaviliable "
thank you very much if any buddy can help me

Go into your OPtions, then advanced options, applications and highlite google maps, menu button, edit permissions. make sure they are set to "allow". this will typically solve it. also go into your GPS settings (under options) and make sure its set to "location On".
Try these and you should be back up and running.

Gnome-volume-manager can't automount removable media any more

Similar Messages

Maybe you are looking for