public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Grant <emailgrant@gmail.com>
To: Gentoo mailing list <gentoo-user@lists.gentoo.org>
Subject: [gentoo-user] Re: Advice needed regarding udisks
Date: Sat, 17 Aug 2013 00:57:29 -0700	[thread overview]
Message-ID: <CAN0CFw3hWA=dmFpT9v5Ys6TmWXnCeKaZixT9LG_OMJTNgg81rg@mail.gmail.com> (raw)
In-Reply-To: <CAN0CFw35yAFaW_xhrq84RYB=bdgiBcjxKz4aQQMs7F4+MN4msQ@mail.gmail.com>

This is actually a portage question.  How can I install udisks-2 in a
way that will fix this problem?  I'm confused by how to handle the
slotting behavior.

- Grant


On Fri, Aug 16, 2013 at 6:09 AM, Grant <emailgrant@gmail.com> wrote:
> I'm having a problem detaching a USB camera from a desktop.  I found a
> Ubuntu bug for the problem which states that it is a bug in udisks-1
> which won't be fixed upstream and the solution is to upgrade to Ubuntu
> 12.10 which uses udisks-2.  Can anyone recommend a good course of
> action for me here?
>
> Here is the problem:
>
> # udisks --detach /dev/sdb
> Detach failed: Error detaching: helper exited with exit code 1:
> Detaching device /dev/sdb
> USB device: /sys/devices/pci0000:00/0000:00:02.0/usb2/2-6)
> SYNCHRONIZE CACHE: FAILED: No such file or directory
> (Continuing despite SYNCHRONIZE CACHE failure.)
> STOP UNIT: FAILED: No such file or directory
>
> Here is a pretend emerge of udisks:
>
> # emerge -pv udisks
> [ebuild  N     ] sys-apps/gptfdisk-0.8.6  USE="icu ncurses -static" 0 kB
> [ebuild  NS    ] sys-fs/udisks-2.1.0:2 [1.0.4-r5:0] USE="gptfdisk
> introspection -cryptsetup -debug (-selinux) -systemd" 0 kB
>
> Here is the Ubuntu bug describing the problem (comments 81, 82, 85):
>
> https://bugs.launchpad.net/ubuntu/+source/udisks/+bug/466575
>
> - Grant


  reply	other threads:[~2013-08-17  7:57 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-16 13:09 [gentoo-user] Advice needed regarding udisks Grant
2013-08-17  7:57 ` Grant [this message]
2013-08-17  8:33   ` [gentoo-user] " Alan McKinnon
2013-08-17 18:03     ` Grant
2013-08-17 18:15       ` Canek Peláez Valdés
2013-08-17 19:00         ` Grant
2013-08-17 19:20           ` Canek Peláez Valdés
2013-08-17 19:28           ` Alan McKinnon
2013-08-18  7:33             ` Grant
2013-08-18  9:21               ` Alan McKinnon
2013-08-18  9:50                 ` Grant
2013-08-18 17:46                   ` Jonathan Callen
2013-08-19  7:17                     ` Grant
2013-08-19  7:25                       ` Alan McKinnon
2013-08-19  8:25                         ` Grant
2013-08-19  9:05                           ` Alan McKinnon
2013-08-19  9:43                             ` Grant
2013-08-19  9:49                               ` Alan McKinnon
2013-08-19  7:28                       ` Canek Peláez Valdés
2013-08-23  5:48             ` Grant
2013-08-20  5:40           ` Samuli Suominen
2013-08-20  6:21             ` Grant
2013-08-23 15:15               ` Samuli Suominen
2013-08-24  5:39                 ` Grant
2013-08-24 11:20                   ` Samuli Suominen
2013-08-24 12:43                     ` Grant
2013-08-24 13:14                       ` Marc Joliet
2013-08-24 14:44                         ` Grant
2013-08-17 18:22       ` Alan McKinnon

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAN0CFw3hWA=dmFpT9v5Ys6TmWXnCeKaZixT9LG_OMJTNgg81rg@mail.gmail.com' \
    --to=emailgrant@gmail.com \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox