Your message dated Tue, 24 Jul 2012 09:57:12 -0300 with message-id <canvyna_fq8y5hc1ky8wqsn2qscrfyiuhs0z6+kx83oau-b2...@mail.gmail.com> and subject line Re: Bug#682604: udisks-glue: udisks-glue does not autostart with udisks has caused the Debian Bug report #682604, regarding udisks-glue: udisks-glue does not autostart with udisks to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 682604: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=682604 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: udisks-glue Version: 1.3.4-1 Severity: normal Dear Maintainer, >From various sites I have read regarding udisks-glue, I was under the impression that udisks-glue was immediately effective after installation and would always run when udisks runs. However this appears not to be the case, and in fact I must run it from the command line - 1st as root with --pidfile so that it can create the pidfile in /var/run (the daemon seems to exit however) and then as the user logged into gnome3 to get the daemon to actually run in the background. Not sure if this is a packaging issue or whether or not we just need right instructions for getting udisks-glue to autostart with udisks. Regards R -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (990, 'testing'), (600, 'stable'), (500, 'testing-proposed-updates'), (500, 'stable-updates'), (500, 'proposed-updates'), (300, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.4-trunk+illuminati-pf-amd64-hp6910p (SMP w/2 CPU cores; PREEMPT) Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8) (ignored: LC_ALL set to en_GB.utf8) Shell: /bin/sh linked to /bin/dash Versions of packages udisks-glue depends on: ii libc6 2.13-33 ii libconfuse0 2.7-4 ii libdbus-1-3 1.6.0-1 ii libdbus-glib-1-2 0.100-1 ii libglib2.0-0 2.32.3-1 ii udisks 1.0.4-7 udisks-glue recommends no packages. udisks-glue suggests no packages. -- Configuration Files: /etc/udisks-glue.conf changed: filter disks { optical = false partition_table = false usage = filesystem } match disks { automount = true automount_options = { noatime, 'gid=50', 'dmask=002', 'fmask=113' } post_mount_command = "mount-notify mounted %device_file %mount_point" post_unmount_command = "mount-notify unmounted %device_file %mount_point" } -- no debconf information
--- End Message ---
--- Begin Message ---Hi, On Tue, Jul 24, 2012 at 1:05 AM, Roger Ricardo Moore <[email protected]> wrote: > From various sites I have read regarding udisks-glue, I was under the > impression that udisks-glue was immediately effective after installation and > would always run when udisks runs. However this appears not to be the case, > and > in fact I must run it from the command line - 1st as root with --pidfile so > that it can create the pidfile in /var/run (the daemon seems to exit however) > and then as the user logged into gnome3 to get the daemon to actually run in > the background. > > Not sure if this is a packaging issue or whether or not we just need right > instructions for getting udisks-glue to autostart with udisks. Neither. Although udisks-glue can be launched as root, it's not what we recommend. From README: In most cases, you don't want to run udisks-glue as root. udisks-glue uses udisks to mount devices, and udisks uses PolicyKit to tell whether or not an user can mount a specific device. Depending on how your distribution sets up PolicyKit, you might have to add a local policy to allow you to mount devices, or maybe you can simply make sure you have a local and active ConsoleKit session (e.g., by using a display manager that is ConsoleKit-aware). If you can use udisks to mount devices (e.g. with "udisks --mount"), then udisks-glue should be able to mount devices too even if not run as root. In your case, you're probably better off configuring Gnome to launch udisks-glue when it starts your session. Regards,
--- End Message ---
