Ubuntu Intrepid is End-of-life and no longer supported. I am closing the
bug task for Intrepid (it is still open for other versions of Ubuntu).
** Changed in: gvfs (Ubuntu Intrepid)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs
** Changed in: gvfs (Ubuntu Intrepid)
Status: Invalid => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/258083
Title:
F-Spot - Error connecting to camera. "Could not lock the devic
I think that the issue is caused by a deadlock somewhere in the driver
for communicating with the camera and not caused by the application
(FSpot, Nautilus) using the connection to the camera.
If I connect the camera, I get asked if I want to start FSpot.
When I ignore the dialog or click "Cancel
I have the same issue with a "KODAK EASYSHARE MINI Camera M200" camera
on ubuntu 10.0.4 LTS (Lucid Lynx).
Accessing with nautilus sometimes works, but then copying all photos to hard
disk will result in a hang after some files have been copied slowly with some
bursts where speed is high, later s
Same problem here in Karmic and/or F-Spot.
Just for the record, there seems to be two parallel Bugs being investigated:-
1.
Bug #331681 in linux (Ubuntu): "Error initializing camera ...
Error initializing camera: -60: Could not lock the device ... but i get
an error on connecting t
This bug has appeared in my Karmic Koala release, I haven't seen this up until
last week but it seems to be a show stopper.
I connect my camera and immediately get the message "Error connecting to camera
Received error "Bad parameters" while connecting to camera." This is a Kodak
easyshare C18
Same here, Ubuntu 10.4 beta2 + Canon EOS 350D = "Could not lock the
device"
--
F-Spot - Error connecting to camera. "Could not lock the device"
https://bugs.launchpad.net/bugs/258083
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
u
Hello,
I also have this bug in Karmic Koala (all updates). This appears to
be an error between FSpot and Gnome. If I manually unmount the camera
BEFORE launching FSpot, all is working. FSpot needs to be patched to
have an umount script just prior to initialising.
- CH
--
F-Spot - Error con
This is probably the wrong place for the above post... then again, it
implies that this entire bug is in the wrong place. Any suggestions on
where to post my bug report would be welcomed. Maybe gvfs?
--
F-Spot - Error connecting to camera. "Could not lock the device"
https://bugs.launchpad.ne
This is also a problem in Google's Picasa version 3.0.5744-02 (this is
the testing version which uses wine) with a Kodak EasyShare C813 camera.
Picasa is default application to use to open multimedia folders, and
therefore the symptoms are:
Connect camera via USB cable and turn on.
Receive error
Thanks for the reply Brian.
Yes...Nautilus is launched when I click on "Select Folders" from the
drop down list. I was mistaken.
Interestingly, I receive a third (3rd) error message when I click on
"NIKON DSC COOLPIX P5100-PTP"
Could not mount NIKON DSC COOLPIX P5100-PTP
Error initializing camer
I have no trouble importing from a folder. I click on "import" , the
import window comes up and I select from "Import Source", "Select
Folder". the drop down box shows no camera and I click on "select
folder" again and nautilus pops up so I can choose the source folder. Is
that not what happens for
The version of F-Spot in post #32 is 0.6.1.5.
I have not found a way to change the camera to work from PTP mode to
another mode (e.g., MTP).
Regards,
--
F-Spot - Error connecting to camera. "Could not lock the device"
https://bugs.launchpad.net/bugs/258083
You received this bug notification be
I have the following error in 9.10 running on Dell Mini 10v
"Error connecting to camera. Received error "Could not lock the device"
while connecting to camera".
I receive the above error when taking the following steps.
1. Connect camera (Nikon P5100) via USB to the laptop
2. Turn on the camera
I had this issue. My Canon A70 would not connect and gave an error (Bad
parameters). I changed my Nautilus configuration so instead of
automatically opening F-spot, Nautilus would ask me what I wanted to do
(Edit | Preferences | Media tab). This solved the race condition where
F-spot and the Nautil
Oh, and if it's any use, here is my fspot log file.
** Attachment added: "F-spot log file."
http://launchpadlibrarian.net/32630370/f-spot.txt
--
F-Spot - Error connecting to camera. "Could not lock the device"
https://bugs.launchpad.net/bugs/258083
You received this bug notification because
I recently upgraded to the latest stable f-spot 0.6.2 (compiled from
source) in order to get the facebook plugin to work. I am running
ubuntu jaunty, I previously did not have this bug, but now I do, it
affects both my cameras (Cannon EOS 350D and iphone). Once I manually
dismount the device, fsp
The next error is thrown at me:
"Error connecting to camera. Received error "Could not lock the device" while
connecting to the camera."
So this bug is still valid for me.
gvfs-mount -l gives:
Volume(0): Canon, Inc. Canon Digital Camera
Type: GProxyVolume (GProxyVolumeMonitorGPhoto2)
Mount(
Brian, this is unrelated to this bug report. Can you please file a new
bug report against libgphoto2 about this, with providing this f-spot
log? thanks!
--
F-Spot - Error connecting to camera. "Could not lock the device"
https://bugs.launchpad.net/bugs/258083
You received this bug notification b
Nikon CoolPix 2500
Intrepid
TiBook G4
I'm having the same problem. I had no problem in Hardy but Intrepid is a
disaster in this and other ways.
The workaround doesn't work. I tried downgrading to f-spot - 0.5.0.3-0ubuntu2
from f-spot - 0.5.0.3-0ubuntu4 and that didn't make any difference. All t
This bug was fixed in the package f-spot - 0.5.0.3-0ubuntu2
---
f-spot (0.5.0.3-0ubuntu2) intrepid; urgency=low
* Add gvfs-bin dependency, so that the gvfs umounting in
f-spot-import-gphoto.dpatch can actually work. Otherwise F-Spot fails with
"Cannot lock device" on import.
You're my heroes - Fspot works now for me
--
F-Spot - Error connecting to camera. "Could not lock the device"
https://bugs.launchpad.net/bugs/258083
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bug
On Tue, Oct 21, 2008 at 18:43, Martin Pitt <[EMAIL PROTECTED]> wrote:
> Ah, that would be it. Thanks!
Installing gvfs-bin worked for me, too.
--
F-Spot - Error connecting to camera. "Could not lock the device"
https://bugs.launchpad.net/bugs/258083
You received this bug notification because you
I uploaded a fixed package which adds the gvfs-bin dependency. Waiting
in unapproved queue now (will be accepted after the Release candidate
goes out).
** Changed in: f-spot (Ubuntu Intrepid)
Status: In Progress => Fix Committed
--
F-Spot - Error connecting to camera. "Could not lock the
Ah, that would be it. Thanks!
** Changed in: f-spot (Ubuntu)
Status: Incomplete => In Progress
--
F-Spot - Error connecting to camera. "Could not lock the device"
https://bugs.launchpad.net/bugs/258083
You received this bug notification because you are a member of Ubuntu
Bugs, which is s
ok, I did the install and viola! it all works, I think the dependencies
are incorrect and that package is not being installed.
--
F-Spot - Error connecting to camera. "Could not lock the device"
https://bugs.launchpad.net/bugs/258083
You received this bug notification because you are a member of
for a cannon power shot sd850 is
I connected it and got the failed to lock message, I ignored all popups etc and
opened a terminal and typed the following
[EMAIL PROTECTED]:~$ gvfs-mount -l
The program 'gvfs-mount' is currently not installed. You can install it by
typing:
sudo apt-get install g
Pierre-Antoine, thanks. But that actually looks fine, and you confirmed
that it works for you.
So, obviously the debug output I asked above is only actually useful if
it does *not* work, i. e. f-spot complains about a locking error, or
presents you with a device selection dialog instead of the thu
Martin, I did as you asked with my iPhone, and it worked. I attach the
output of both commands.
However, the bug seems to have been fixed with the update to f-spot
0.5.0.3-0ubuntu1.
** Attachment added: "iphone.txt"
http://launchpadlibrarian.net/18765371/iphone.txt
--
F-Spot - Error connecti
For the record, the bug fix is discussed at
http://bugzilla.gnome.org/show_bug.cgi?id=551803 .
So apparently the current fix in Intrepid does not work for some cases.
Please do the following:
- plug in your camera
- ignore or close the dialog that pops up asking you for which action to take
(F-S
Set status to new...seems like the fix is not there
** Changed in: f-spot (Ubuntu)
Status: Fix Released => New
--
F-Spot - Error connecting to camera. "Could not lock the device"
https://bugs.launchpad.net/bugs/258083
You received this bug notification because you are a member of Ubuntu
I'm experiencing this problem with Intrepid and a Canon EOS Digital
Rebel XSi.
--
F-Spot - Error connecting to camera. "Could not lock the device"
https://bugs.launchpad.net/bugs/258083
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
I still have the bug under Intrepid with two cameras (FUJIFILM FinePix F30 and
iPhone).
How come the bug is marked as "Fix released", while many people seem to
experience it?
--
F-Spot - Error connecting to camera. "Could not lock the device"
https://bugs.launchpad.net/bugs/258083
You received
great it woas fixed in f-spot (0.4.4-1ubuntu4) and after this intrepid
was migrated to 0.5.0.2-0ubuntu4 . seems like somebody forgot to send
this bug upstream?
--
F-Spot - Error connecting to camera. "Could not lock the device"
https://bugs.launchpad.net/bugs/258083
You received this bug notific
Fails for "cannon power shot sd850 is" in PTP
In usb mass storage mode it works via the desktop icon that pops up
--
F-Spot - Error connecting to camera. "Could not lock the device"
https://bugs.launchpad.net/bugs/258083
You received this bug notification because you are a member of Ubuntu
Bugs
Still present in Intrepid beta as of 3 Oct.
I'm trying to connect a Sony Cyber-shot DSC-S700 using PTP, and have the same
error. The workaround of unmounting the drive first is working.
If I use the "USB mass storage" mode, it is working fine.
--
F-Spot - Error connecting to camera. "Could not
This bug was fixed in the package f-spot - 0.4.4-1ubuntu4
---
f-spot (0.4.4-1ubuntu4) intrepid; urgency=low
* Add ubuntu_import_fuse.dpatch: Import from the gvfs fuse path instead of
libgphoto URL, so that we can import from libghoto handled cameras which
nautilus already au
I fixed that particular bug. It still sucks, it's awfully slow and you
don't get the target directory dialog either, but that has to do for the
beta, I'm afraid.
Package uploaded, waiting in unapproved.
** Changed in: f-spot (Ubuntu)
Assignee: Ubuntu Desktop Bugs (desktop-bugs) => Martin Pit
Internal notekeeping: above GNOME patch is unrelated; it just provides
an optimized workflow for apps which understand gvfs, it doesn't
magically fix the URLs that f-spot-import %u gets and can't interpret.
--
F-Spot - Error connecting to camera. "Could not lock the device"
https://bugs.launchpa
I have this same problem with canon 400D and 350D.
--
F-Spot - Error connecting to camera. "Could not lock the device"
https://bugs.launchpad.net/bugs/258083
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
u
http://bugzilla.gnome.org/show_bug.cgi?id=530654 might be related, or
even fix the problem.
--
F-Spot - Error connecting to camera. "Could not lock the device"
https://bugs.launchpad.net/bugs/258083
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed t
Current status: I fixed fuse to not depend on users being in the "fuse"
group again. Seb and I agreed that with this, the best solution would be
to keep gvfs mount it, and use %f instead of %u in the f-spot-import
desktop file.
However, the remaining problem is that f-spot --import /path does not
** Changed in: f-spot (Ubuntu)
Target: None => ubuntu-8.10-beta
** Changed in: f-spot (Ubuntu)
Assignee: (unassigned) => Ubuntu Desktop Bugs (desktop-bugs)
--
F-Spot - Error connecting to camera. "Could not lock the device"
https://bugs.launchpad.net/bugs/258083
You received this bu
I'm having this same problem, with the same camera model.
--
F-Spot - Error connecting to camera. "Could not lock the device"
https://bugs.launchpad.net/bugs/258083
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
thank you for your bug report, that's an f-spot issue, it should either
unmount the device or use the gvfs uri to download the photo directly
** Changed in: f-spot (Ubuntu)
Sourcepackagename: gvfs => f-spot
Importance: Undecided => Medium
Status: New => Confirmed
--
F-Spot - Error conn
45 matches
Mail list logo