Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 134496 - Dbus AccessDenied error
Summary: Dbus AccessDenied error
Status: RESOLVED INVALID
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] GNOME (show other bugs)
Hardware: All Linux
: High normal (vote)
Assignee: Project Gentopia
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-05-27 03:37 UTC by Hyunsik Choi
Modified: 2006-05-27 20:31 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Hyunsik Choi 2006-05-27 03:37:40 UTC
My programs versions are following:
 * gnome-volume-manager-1.5.15-r1
 * gnome-mount-0.4-r3
 * hal-0.5.7-r2
 * udev-090

My problem is that cdrom do not automatically mount. Maybe, other devices, such as usb, digital camera, so do. My account belongs to plugdev, cdrom, and so on. However, there is the problem.

Therefore, I tried to mount through gnome-mount manually.
------------------------------------------------------------------------
c0d3h4ck@disys18 ~ $ gnome-mount -vtd /dev/hdc
gnome-mount 0.4
** (gnome-mount:15109): DEBUG: Mounting /org/freedesktop/Hal/devices/volume_label_Gentoo_Linux_2006_0_x86_LiveCD with mount_point='Gentoo Linux 2006.0 x86 LiveCD', fstype='', num_options=1
** (gnome-mount:15109): DEBUG:   option='uid=1000'
 
** (gnome-mount:15109): WARNING **: Mount failed for /org/freedesktop/Hal/devices/volume_label_Gentoo_Linux_2006_0_x86_LiveCD
org.freedesktop.DBus.Error.AccessDenied : A security policy in place prevents this sender from sending this message to this recipient, see message bus configuration file (rejected message had interface "org.freedesktop.Hal.Device.Volume" member "Mount" error name "(unset)" destination "org.freedesktop.Hal")
------------------------------------------------------------------------

Finally, I found why gnome-mount don't mount cdrom automatically. I investigated  /etc/dbus-1/system.d/hal.conf.

There are a policy that allow plugdev group to access 'Hal.Device.Volume'. However, it do not work well. Hence, I added a policy that I describe at below.

  <policy user="c0d3h4ck">
    <allow send_interface="org.freedesktop.Hal.Device.SystemPowerManagement"/>
    <allow send_interface="org.freedesktop.Hal.Device.LaptopPanel"/>
    <allow send_interface="org.freedesktop.Hal.Device.Volume"/>
    <allow send_interface="org.freedesktop.Hal.Device.Volume.Crypto"/>
  </policy>

After I added the policy, I restarted dbus, and then I could mount cdrom in gnome. Although above solution is not regular, the policy that I added states that dbus or hal has some problem.

Thanks you for your time.
Comment 1 Hyunsik Choi 2006-05-27 03:41:02 UTC
I missed emerge --info.

--------------------------------------------------------------------------
disys18 system.d # emerge --info
Portage 2.1_rc2-r3 (default-linux/amd64/2006.0, gcc-4.1.1, glibc-2.4-r3, 2.6.16-gentoo-r8 x86_64)
=================================================================
System uname: 2.6.16-gentoo-r8 x86_64 AMD Athlon(tm) 64 X2 Dual Core Processor 4400+
Gentoo Base System version 1.12.0
dev-lang/python:     2.3.5-r2, 2.4.3-r1
dev-python/pycrypto: 2.0.1-r5
dev-util/ccache:     [Not Present]
dev-util/confcache:  [Not Present]
sys-apps/sandbox:    1.2.18.1
sys-devel/autoconf:  2.13, 2.59-r7
sys-devel/automake:  1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6-r2
sys-devel/binutils:  2.16.1-r2
sys-devel/libtool:   1.5.22
virtual/os-headers:  2.6.11-r3
ACCEPT_KEYWORDS="amd64 ~amd64"
AUTOCLEAN="yes"
CBUILD="x86_64-pc-linux-gnu"
CFLAGS="-march=athlon64 -O3 -pipe"
CHOST="x86_64-pc-linux-gnu"
CONFIG_PROTECT="/etc /usr/kde/3.5/env /usr/kde/3.5/share/config /usr/kde/3.5/shutdown /usr/lib64/mozilla/defaults/pref /usr/share/X11/xkb /usr/share/config"
CONFIG_PROTECT_MASK="/etc/gconf /etc/revdep-rebuild /etc/terminfo /etc/texmf/web2c /etc/env.d"
CXXFLAGS="-march=athlon64 -O3 -pipe"
DISTDIR="/usr/portage/distfiles"
FEATURES="autoconfig distlocks metadata-transfer sandbox sfperms strict"
GENTOO_MIRRORS="http://ftp.gentoo.or.kr http://distfiles.gentoo.org http://www.ibiblio.org/pub/Linux/distributions/gentoo"
LC_ALL="en_US.UTF-8"
LINGUAS="en ko"
MAKEOPTS="-j3"
PKGDIR="/usr/portage/packages"
PORTAGE_RSYNC_OPTS=""
PORTAGE_TMPDIR="/var/tmp"
PORTDIR="/usr/portage"
PORTDIR_OVERLAY="/usr/local/portage"
SYNC="rsync://rsync.gentoo.org/gentoo-portage"
USE="amd64 X acpi alsa avi bash-completion berkdb bitmap-fonts cairo cdr cjk cli crypt cscope cups dbus doc dri dvd dvdr eds emacs emboss encode firefox flac foomaticdb gif glitz gnome gpm gstreamer gtk gtk2 hal imlib ipv6 isdnlog jpeg lzw lzw-tiff mad mp3 mpeg ncurses nls nptl ogg opengl pam pcre pdflib perl png ppds pppd python quicktime readline reflection samba sdl session smp spell spl ssl svg tcpd theora threads tiff truetype truetype-fonts type1-fonts unicode usb vorbis xinerama xorg xpm xv zlib elibc_glibc input_devices_keyboard input_devices_mouse kernel_linux linguas_en linguas_ko userland_GNU video_cards_nvidia"
Unset:  CTARGET, EMERGE_DEFAULT_OPTS, INSTALL_MASK, LANG, LDFLAGS, PORTAGE_RSYNC_EXTRA_OPTS
Comment 2 John N. Laliberte (RETIRED) gentoo-dev 2006-05-27 05:33:18 UTC
do you have cdrom specified in fstab?
Comment 3 Hyunsik Choi 2006-05-27 08:26:01 UTC
In regardless of fstab, I heard that gnome-volume-manager can mount cdrom by depending on hal. Therefore, I removed cdrom entry in fstab.
Comment 4 Doug Goldstein (RETIRED) gentoo-dev 2006-05-27 20:27:54 UTC
Reassigning to Gentopia since we handle HAL
Comment 5 Doug Goldstein (RETIRED) gentoo-dev 2006-05-27 20:31:44 UTC
Closing bug as invalid. The correct thing to do is to add your user to the "plugdev" group.

The "plugdev" group is universally used and is the proper group to be in. The other option is to use pam_console support. (required for NetworkManager) or to use "touch /var/run/console/$user in" /etc/conf.d/local.start if you have a single user system...

This little annoyance will be fixed once PolicyKit comes to Portage but unfortunately it's waaaaaaay too much of a moving target to make it to Portage right now