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.

Similar Messages

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]

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.

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.

[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)

[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)

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)

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

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

Hal gnome-power-manager hibernate scripts

Hi All,
I'm having issues hibernating to disk using gnome-power-manager. My user is in the "power" group and I can suspend from a terminal using "sudo hibernate". However, when I attempt to hibernate with gnome-power-manager, i recive an error "Hal failed to hibernate - please see FAQ". When I run g-p-m with no-daemon, it gives an "unspecified error: failed to hibernate". I have the necessary hibernate scripts in /usr/share/hal/scripts (is this the default dir?) and the hal-system-power-hibernate looks as follows:
#!/bin/bash
POWERSAVED_SUSPEND2DISK="dbus-send --system --dest=com.novell.powersave \
--print-reply /com/novell/powersave \
com.novell.powersave.action.SuspendToDisk"
unsupported() {
echo org.freedesktop.Hal.Device.SystemPowerManagement.NotSupported >&2
echo No hibernate script found >&2
exit 1
if [ -x "/usr/sbin/hibernate" ] ; then
echo "wtf"
hibernate
RET=$?
else
unsupported
fi
#Refresh devices as a resume can do funny things
for type in button battery ac_adapter
do
devices=`hal-find-by-capability --capability $type`
for device in $devices
do
dbus-send --system --print-reply --dest=org.freedesktop.Hal \
$device org.freedesktop.Hal.Device.Rescan
done
done
exit $RET
Please let me know what I'm missing or what necessary config files need to be tweaked.

Does suspend to RAM work with gnome-power-manager? On my system I installed powersave from unstable, which is the daemon used by SuSE to do suspend to RAM and suspend to disk.

Gnome-network-manager problems

Hello all,
I'm trying to use gnome-network-manager to connect to my wifi as it is WEP enabled and I don't know how to get it working in 'network'.
I followed this tutorial: http://wiki.archlinux.org/index.php/NetworkManager
However, when I reboot under those settings, I can't connect to anything, including ethernet.
Is there a problem in the wiki or is there a workaround that hasn't been posted there yet? I'm utterly confused as to why it will not work.
Also, if you need me to paste any code from any file, can you also tell me an easy way to copy/paste between aterm and Opera as I haven't found a way to do that yet.
Thank you very much for any help.
Matt

[matt@myhost ~]$ iwconfig
lo no wireless extensions.
eth0 no wireless extensions.
eth1 IEEE 802.11g ESSID:"3KR98"
Mode:Managed Frequency:2.427 GHz Access Point: 00:18:01:E0:43:1A
Bit Rate:54 Mb/s Tx-Power=20 dBm Sensitivity=8/0
Retry limit:7 RTS thr:off Fragment thr:off
Power Management:off
Link Quality=21/100 Signal level=-72 dBm Noise level=-87 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:76 Missed beacon:31
[matt@myhost ~]$ ifconfig
eth0 Link encap:Ethernet HWaddr 00:0F:B0:A1:71:02
inet addr:192.168.1.2 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::20f:b0ff:fea1:7102/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:82717 errors:300 dropped:592 overruns:300 frame:0
TX packets:61302 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:79395572 (75.7 Mb) TX bytes:9179527 (8.7 Mb)
Interrupt:22 Base address:0x6800
eth1 Link encap:Ethernet HWaddr 00:13:CE:6A:FE:C1
inet addr:192.168.1.2 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::213:ceff:fe6a:fec1/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:309 errors:0 dropped:76 overruns:0 frame:0
TX packets:41 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:2420181 (2.3 Mb) TX bytes:2012 (1.9 Kb)
Interrupt:23 Base address:0x4000 Memory:bc005000-bc005fff
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:232 errors:0 dropped:0 overruns:0 frame:0
TX packets:232 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:20464 (19.9 Kb) TX bytes:20464 (19.9 Kb)
ill post output of disabling gnome-net-manager in a bit (i have to reboot and save it as a file first).
also, im running fluxbox, not gnome, so could that be part of the problem? am i missing something flux specific?

Gnome file manager problem

lately I've noticed that in the Gnome file manager when I go to a directory with images in it, 4 will show up and all the rest don't and the cursor is in a waiting mode that it can't get out of.
What causes this and how can it correct it?
Last edited by vinoman2 (2009-11-07 15:00:38)

Thanks, I later rebooted and that fixed the problem. It was only in one directory.
I just moved a image to a folder and it did it again. I ran nautilus in the terminal and it only opened nautilus.
Is this a bug in Gnome? It seems to happen every time I want to move an image into a folder.
Is there a way to fix this?
Last edited by vinoman2 (2009-11-07 15:02:37)

Gnome-volume-manager and plugdev

I'm trying to work out some kinks in gnome-volume-manager0--namely, that I cannot unmount disks as a regular user. Everything I have found says that a user must be a member of the plugdev group for such things to work, so I looked around and found that I should be able to add myself to the plugdev groups like so:
usermod -G plugdev isez2001
But upon giving this command, I receive an error saying that the plugdev group is unknown.
Do I have to create the plugdev group myself? If so, why? It really seems like something that should be made to just work.

Alright, I'm a member of the storage group already.
Upon further investigation, I find that my USB flash drive is autmounted in /media under the group "root," and my DVD drive automounts under the group "-1".
I am unable to unmount either of these as a normal user.
Is there something I should do that will make disks mount under the storage group?

Solaris Volume Manager Problem

After installing Solaris 10 on a SunFire V880 and mirroring the boot disk, I am unable to boot from one disk. The boot process looks like this:
Rebooting with command: boot
Boot device: /pci@8,600000/SUNW,qlc@2/fp@0,0/disk@w21000000870e36cb,0:a File and args:
SunOS Release 5.10 Version Generic 64-bit
Copyright 1983-2005 Sun Microsystems, Inc. All rights reserved.
Use is subject to license terms.
WARNING: md: d32: (Unavailable) needs maintenance
WARNING: Error writing ufs log state
WARNING: ufs log for / changed state to Error
WARNING: Please umount(1M) / and run fsck(1M)
WARNING: Failed to install "hpc3130" driver.
WARNING: Failed to install "todds1287" driver.
WARNING: Failed to install "mc-us3" driver.
WARNING: Failed to install "ssc050" driver.
WARNING: cannot find ssc050_get_port_bit
panic[cpu3]/thread=180e000: mod_hold_stub: Couldn't load stub module misc/strplumb
000000000180b8a0 genunix:mod_hold_stub+1f0 (0, 185b800, 18a81c0, 30000d00c90, 1816f80, 0)
%l0-3: 00000000011cdcd8 0000000000000004 0000000001852874 0000000000000000
%l4-7: 0000000000000000 000000000185284c 0000000001852800 0000000000000000
000000000180b950 unix:stubs_common_code+30 (0, 989680, 180fc00, 1810c00, 1f407f, 18aa800)
%l0-3: 000000000180b219 000000000180b2f1 000000b1fe000000 0000000000000064
%l4-7: 0000000000000000 0000000001816f90 0000000000000064 0000000000000064
000000000180ba20 genunix:main+e0 (1813c98, 0, 1834340, 18a8000, 0, 1813800)
%l0-3: 000000000180e000 0000000000000001 000000000180c000 0000000001835200
%l4-7: 0000000070002000 0000000000000000 000000000181ba48 0000000000000000
syncing file systems... done
skipping system dump - no dump device configured
rebooting...
Resetting ...
The same procedure works without problem in Solaris 09 9/04.
Any help would be greatly appreciated!

I am seeing a similar issue with my system.
Initially I had a mirrored Solaris 9 configuration (disk0/disk1).
I had user live_upgrade to successfullyt upgrade disk1 of the mirror. After the upgrade I had tested the os several times, booting Solaris 9 and 10.
Once this was successful, I used the Solaris 10 media to create a fresh install of Solaris 10 on disk0. Now, the solaris 10 fresh install disk0 will boot successfully, however, disk1 fails as you describe.
I have tried fsck, which does not find any issues, removed the metadevices from vfstab and ensured logging is not set, but all to no avail.

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.

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

Dbus/hal/gnome-volume-manager problem

Similar Messages

Maybe you are looking for