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)

Similar Messages

Openbox as gnome window manager doesn't work

So, this is my first time with arch, and I have some experience with Ubuntu so I installed the gnome winow manager to start.
It looks fine but I like some themes and how openbox looks/works more. I decided saw in a wiki that you can make it the window manager for gnome, so I followed the instructions in the wiki, loged out then back in, but nothing happens. Still the same old gnome.
bash-3.2# gconftool-2 -g /desktop/gnome/session/required_components/windowmanager
openbox
bash-3.2# cat /usr/share/applications/openbox.desktop
[Desktop Entry]
Type=Application
Encoding=UTF-8
Name=OpenBox
Exec=openbox
NoDisplay=true
# name of loadable control center module
X-GNOME-WMSettingsModule=openbox
# name we put on the WM spec check window
X-GNOME-WMName=OpenBox

I believe you want it to be openbox-gnome-session
http://icculus.org/openbox/index.php/Help:GNOME/Openbox
Last edited by thayer (2009-02-02 00:22:18)

Gnome-network-manager doesn't work at all

Hello, guys!
Gnome-network-manager starts but doesn't show its icon in Notification Area.
ps -A shows that the process is running correctly.
[sergo@myhost ~]$ ps -A |grep nm
4360 pts/2 00:00:00 nm-applet
I carefully studied all solutions listed here. My DAEMONS string is
DAEMONS=(syslog-ng !hotplug !pcmcia network netfs crond alsa sensors portmap fam dbus hal dhcdbd networkmanager networkmanager-dispatcher @cups gdm)
Please help.

yes, I have done it, and nothing happen
edit : I have reinstall the software, and now it is OK, tks for the help
Last edited by serafimsaudade (2007-05-20 17:34:56)

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]

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

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

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.

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.

Volume control doesn´t work with iphone 3gs

Hi, the volume control doesn´t work with my ihpone 3gs, i´m using the apple headset, any suggestions???

´Till the moment it is, i just recently received a notification with a software update, but i tried with another 3gs with the same characteristics and it worked.

Volume control doesn't work with headphones plugged in

When I connect headphones the volume control doesn't work correctly. It should play only through the headphones, but it doesn't. In fact the volume control will bounce back and forth between operating correctly and not working correctly ... And will eventually stop the music. Frustrating!

´Till the moment it is, i just recently received a notification with a software update, but i tried with another 3gs with the same characteristics and it worked.

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

Gnome-power-manager doesn't respond to disconnecting AC power supply

"acpi" command always shows correct information, but gnome-power-manager doesn't.
When computer is initially on AC power, and then I disconnect the adapter, gnome-power-manager still says hapilly that I'm on AC power, and the battery is fully charged. It only reacts when I plug adapter back. Then everything is correct. But If i disconnect it again - it shows "AC power, fully charged" again, even regarding the fact it was "80% charged" a second ago.
WTF?

After updating the BIOS, it's more correct, but still not always (I'm running Acer Aspire One 110).
And, another strange issue - when I disconnect the AC adapter, and the power-manager detects that, it automatically locks the screen. (I have a option enabled that when the laptop is closed then the blank screen screensaver is activated, which locks the screen, but this is not the case)

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

Since the last update yesterday to firefox 4.0.1 my program "asus security protect manager" doesn't work properly. That means, that the saved keys from several websites not remembered for lock in.

since the last update yesterday to firefox 4.0.1 my program “asus security protect manager” doesn’t work properly. That means, that the saved keys from several websites not remembered for lock in.

Sorry you are having problems. First of all try Fifrefox's safemode.
*[[Troubleshoot Firefox issues using Safe Mode]]
If that works post back for further advice.
Next step, if safe mode did not work.
First: Try a clean install, (you have had a none standard version installed previously) that involves deleting the program files. Then if necessary try troubleshooting by creating and using a clean empty Firefox profile.
See
* this recent post [/questions/940399#answer-377134]
* http://kb.mozillazine.org/Standard_diagnostic_-_Firefox#Clean_reinstall
Second: try a New Profile
*http://kb.mozillazine.org/Profile_Manager#Creating_a_new_profile
* this will be an additional profile, it is still worth backing up any existing or currently working profile on a regular basis
**[[Back up and restore information in Firefox profiles]]
* Until you are absolutely confident about the repercussions I suggest
** always use an empty folder when creating a new profile
** never delete or rename profiles, just disable or remove shortcuts
** after creating a new test profile open it and check for any addons or plugins that may be have been included by default

My beats studio 2013 work fine on my ipad but the mic/ volume control doesn't work on my iphone 5

My beats studio 2013 work fine on my ipad but the mic/ volume control doesn't work on my iphone 5. Can anyone help me?

Thanks, daniel.early79!
I have an iPhone5 bought in late Dec 2012.
I've noticed on rare occassions that the volume down button some times would not respond.
Starting yesterday, the volume down button would not respond more consistently.
Sometimes a reset would fix it, sometimes a reset network would fix it, but the problem would come back.
Came across this thread, and pressing gently on the upper right hand corner fixed it!
I remember seeing some video on Youtube or iFixit that shows how to replace the power button. It appears that the volume buttons and the power buttons are tied in together on the same piece of connector. I supposed taking the iphone in and out of cases may have warped or twisted the connector inside the case ever so slightly that the sensor for the down volume button got shifted.
The down volume button works now, after doing the trick you suggested. I'll wait and see if it comes back before taking it in for warranty repair.

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

Similar Messages

Maybe you are looking for