Summary: | Digikam cannot autodetect camera when gvfs-gdu-volume-monitor is running | ||
---|---|---|---|
Product: | [Applications] digikam | Reporter: | Oleg Atamanenko <oleg.atamanenko+kde> |
Component: | Import-Gphoto2 | Assignee: | Digikam Developers <digikam-bugs-null> |
Status: | RESOLVED WORKSFORME | ||
Severity: | normal | CC: | caulier.gilles, kde-bugzilla, rdieter |
Priority: | NOR | ||
Version: | 1.1.0 | ||
Target Milestone: | --- | ||
Platform: | Ubuntu | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Oleg Atamanenko
2010-02-25 17:45:42 UTC
Part 1 of this fix appears to be improving the error message, to include a hint that the device is already in use / mounted already. (Launchpad bug: https://launchpad.net/bugs/288470) I guess we are talking about a gphoto2 camera here. That means "mount" and "umount" is not the term, rather "connected via USB with libgphoto2". So this gnome process takes any connected camera and opens it with libgphoto2? The question is: Does libgphoto2, when trying to connect to a camera already opened by another process, give us any hint at the actual problem? I'll check behaviour of libgphoto2 and post results here later. Oleg, What's news about this file ? Gilles Caulier I switched to Arch and I can't reproduce the issue because I don't have gnome or gvfs installed. |