This bug does still exist in current versions. digging google I found
the hint to try usb-2.0 ports and indeed in my case my canon 400d
refuses to work on usb-3.0 ports but I can happily connect it through
the usb-2.0 port. may be worth a try..
--
You received this bug notification because you
This bug was filed against a series that is no longer supported and so
is being marked as Won't Fix. If this issue still exists in a supported
series, please file a new bug.
This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.
** Changed in: linux (Ubuntu)
I am also suffering from this bug, but I was able to import my photos
using Shotwell. Icons for my camera (Kodak Z712 IS) and memory card
would appear on the desktop and be visible in Nautilus. What I couldn't
do was import/move/copy files using any other program than Shotwell.
Since Shotwell only
Lubuntu 10.10 Kodak Easyshare C180.
Can't download the images to the computer:
Error initializing camera: -60: No se pudo trabar el dispositivo
:~$ lsusb
Bus 002 Device 003: ID 1c9e:6061
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 005: ID 040a:05d4 Kodak Co.
windows does not have this problem
On Sat, Apr 23, 2011 at 3:17 PM, Marcelo 331...@bugs.launchpad.net wrote:
Lubuntu 10.10 Kodak Easyshare C180.
Can't download the images to the computer:
Error initializing camera: -60: No se pudo trabar el dispositivo
:~$ lsusb
Bus 002 Device 003: ID
Ubuntu 10.10 with all updates. Kodak Easyshare C813. Same problem.
I can access the camera memory on my Windowx XP running in VirtualBox
(USB-enabled version). So, I get access via the guest system, but I
can't access it on my host system. (?)
Please fix this annoying bug... eventually.
--
You
Kubuntu 10.10
PCLinuxOS-kde-2010.12
Both seem to work OK.
It looks as though the problem is more likely to be with Gnome.
So has the problem been reported to the Gnome developers? I've read
something elsewhere that leads me to suspect that my camera is handled
properly with another
I notice that this bug is still marked unassigned. It's been almost 2
years since it was first reported. I recently upgraded to Ubuntu 10.10,
and it doesn't appear to be fixed. Is there a reason why it is not being
assigned?
--
You received this bug notification because you are a member of
KODAK EasyShare Z981 Digital Camera has the same problem. After many hours of
testing, with bootable live-usb, it appears that this might not be an Ubuntu
problem.
Ubuntu 10.10
Ubuntu 10.04
PCLinuxOS-gnome-2010.12
All fail every time. Error initializing camera: -60: Could not lock the
device.
Thanks for the heads upI agree...
On Wed, 2010-12-29 at 19:32 +, Dave Stevenson wrote:
KODAK EasyShare Z981 Digital Camera has the same problem. After many hours
of testing, with bootable live-usb, it appears that this might not be an
Ubuntu problem.
Ubuntu 10.10
Ubuntu 10.04
Recent upgrade Jaunty-Karmic produced the same problems for me, camera is a
Kodak Z740. Tried the camera.app solution but no joy there either; no error
messages but just a grey-out of the application download box - and zero
downloads.
Surely someone out there, perhaps a really kind, thoughtful,
Possible upstream: https://bugzilla.gnome.org/show_bug.cgi?id=623809
** Bug watch added: GNOME Bug Tracker #623809
https://bugzilla.gnome.org/show_bug.cgi?id=623809
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Solved with some update...
There is a new bug that relates to viewing photos in nautilus or
importing them with gthumb, but gphoto2 now works so this one is case
closed.
--
Error initializing camera: -60: Could not lock the device
https://bugs.launchpad.net/bugs/331681
You received this bug
I'm sorry, but Solved with some update is hardly a case closed. This
is affecting multiple people. I'm happy for you that you are no longer
suffering from this bug, but we don't know why or what fixed it in your
case or if it's fixed for others. I have two systems where this is a
problem and two
Todd:
My camera is a HP Photosmart M437. It worked for a while but now is
rejecting me again. Thanks for the update.
ldm
MG Lawrence D. Morrell, Ph.D.
New Mexico State Guard (ret.)
Semper Fidelis! Volens et Potens!
Ubi dubium ibi libertas
You can have your own opinion, you don't get to have
odd:
My camera is a HP Photosmart M437. It worked for a while but now is
rejecting me again. Thanks for the update.
ldm
MG Lawrence D. Morrell, Ph.D.
New Mexico State Guard (ret.)
Semper Fidelis! Volens et Potens!
Ubi dubium ibi libertas
On Thu, 2010-11-18 at 15:34 +, Todd Lewis wrote:
Maverick: New version of Ubuntu, new symptoms; still not solved
I would say that a Nikon D90 is one of the key cameras in its class so
it should definitely work out of the box. I don't care about using the
CLI to get the pictures but closing down my audio player to get
pictures? That is quite
I've done another test:
1. kill gvfs-gphoto2-volume-monitor
2. launch rhythmbox -- gvfs-gphoto2-volume-monitor gets launched
3. kill gvfs-gphoto2-volume-monitor
4. play music -- does so
5. turn on camera -- watch how the rhythmbox GUI turns gray (unresponsive) and
track position stalls (music
Small addition:
Also without rhythmbox loaded I cannot get the pictures imported using
the standard Ubuntu GUI.
The work around to kill gvfs-gphoto2-volume-monitor and then use gphoto2
works for me.
--
Error initializing camera: -60: Could not lock the device
Thanks, Bart...I'll give it a try...
BG Lawrence D. Morrell, Ph.D.
New Mexico State Guard (ret.)
On Sun, 2010-09-12 at 20:08 +, Bart Kroon wrote:
Small addition:
Also without rhythmbox loaded I cannot get the pictures imported using
the standard Ubuntu GUI.
The work around
Thks you so much Sam Hauglustaine !!
I've exactly the same problem in Lucid with Digikam and my Nikon D40
Error message was : Could not lock the device
If I stop Rhythmbox, it works like a charm
--
Error initializing camera: -60: Could not lock the device
https://bugs.launchpad.net/bugs/331681
I was able to solve this issue by turning of my Nikon D90, closing Rhythmbox
and turning my camera back on.
Apparently Rhythmbox locks the device (it didn't even get mounted when it was
open).
Maybe this helps?
--
Error initializing camera: -60: Could not lock the device
I experienced this problem in Karmic. Now I am using Lucid Lynx and
seem to be experiencing something similar. I get the same error
messages: Unable to mount KODAK EasyShare CX7430 Zoom Digital Camera
Error initializing camera: -60: Could not lock the device And this:
Error Conecting to Camera
Hi nblracer,
If you could also please test the latest upstream kernel available that
would be great. It will allow additional upstream developers to examine
the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds .
Once you've tested the upstream kernel, please remove the 'needs-
I am having this same issue with a Kodak C180 on Ubuntu 9.10. I get the
Error initializing camera: -60: Could not lock the device message when
connecting the camera. I get unable to connect to device type of errors
from both F-spot as well as Digikam.
I tried the reported workaround of killing
I found this an it works fine for me:
Quick fix - run script in terminal sudo killall gvfs-gphoto2-volume-
monitor then connect the camera.
Long-term fix (Prevent the process from starting) - run script in
terminal sudo chmod -x /usr/lib/gvfs/gvfs-gphoto2-volume-monitor
Then go to System -
Couple of attachments of what happens having 'sudo killall gvfs-gphoto2
-volume-monitor', the first is what happens for each file selected to
copy, the second what happens when I give up!
BTW is anyone actively addressing this bug or can someone recommend a
replacement for f-spot that still works
Here's the second attachment ...
** Attachment added: fatal error log from f-spot on giving up failed attempts
to fetch pictures from camera.
http://launchpadlibrarian.net/35368182/f-spot-fatal-error.log
--
Error initializing camera: -60: Could not lock the device
I am thinking a certain monopolistic operating system seller has
bribed someone to bug our previously fully functional operating
system.
On Mon, Nov 2, 2009 at 6:27 AM, WallaceM wallace.max...@googlemail.com wrote:
I have tried Rich's solution of killing gvfs-gphoto2-volume-monitor and
this
I've just upgraded from the 8.04 to 9.10 (via intermediate packages) and
have hit this problem with both my Fuji camera and Samsung Phone (in
media mode) both of which worked previously.
--
Error initializing camera: -60: Could not lock the device
https://bugs.launchpad.net/bugs/331681
You
I have tried Rich's solution of killing gvfs-gphoto2-volume-monitor and
this does enable f-spot to launch the importer correctly but it then
fails to transfer any files from the phone. I can't cut and paste the
error message f-spot displays so if anyone knows where to look for it in
a log file
I have some more info about this bug. Apparently, it is not simply a
device *permissions* problem (as I had previously supposed). Rather,
there seems to be a device *locking* problem involving the gphoto2
volume monitor -- i.e., gvfs-gphoto2-volume-monitor is grabbing the
camera device and
In my case, I add the user to the root group and reboot the machine and
nothing change, the problem still persist.
--
Error initializing camera: -60: Could not lock the device
https://bugs.launchpad.net/bugs/331681
You received this bug notification because you are a member of Ubuntu
Bugs, which
I don't think downgrading to Hardy is the solution, to be honest. If the
maintainers of the repositories would be so kind as to keep legacy
version of libgphoto (and ALL Ubuntu software, while they're at it)
available for people to force the version they need, that would be the
solution. Where are
See my earlier comment #19 above. The problem appears to be a device
permissions problem; the solution is probably to update the udev
rules. Temporarily putting the user account in the root group (see my
comment #18) should confirm whether it really is a device permissions
problem or not.
--
Same problem here with a Kodak M1033, I didn't found any workaround. It
works fine in 8.04 but it don't work in 9.04
--
Error initializing camera: -60: Could not lock the device
https://bugs.launchpad.net/bugs/331681
You received this bug notification because you are a member of Ubuntu
Bugs,
mine is still broken as well. Should I downgrade to 8.04 and try again?
On Sat, Oct 10, 2009 at 12:02 PM, Christian c_prade...@yahoo.com wrote:
Same problem here with a Kodak M1033, I didn't found any workaround. It
works fine in 8.04 but it don't work in 9.04
--
Error initializing camera:
Hi,
See this work around:
http://www.korben.info/impossible-de-monter-un-appareil-photo-sur-
ubuntu-810-intrepid-ibex-la-solution.html
In short =
Apply to U9.04 and Kodak DX7590 = OK
sudo gedit /usr/share/hal/fdi/preprobe/10osvendor/20-libgphoto2.fdi
Search
same problem. this is a hugedeal breaker.
--
Error initializing camera: -60: Could not lock the device
https://bugs.launchpad.net/bugs/331681
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
I should mention one little detail: even with Camera I get all the
same error messages, which are, to be sure, annoying. However, there's
no arguing with results, and Camera is in fact extracting my photos
despite any supposed mounting problems.
Nobodie: it sounds like you may not have tried
u, yes i have the problem with a Kodak camera but obviously it is
lib related and has nothing to do with a specific application since it
errors before any application is triggered. Yes that seems to mean an
ownership problem and the kludgey stufff is kludgey so we need a good
solution. Yes
The fact that changing group membership of a user account (see my
comment #18 above) sidesteps the problem suggests to me that the
preferred solution would be to add the right udev rules (in
/lib/udev/rules.d or /etc/udev/rules.d) to create the camera's USB
device with the correct group membership
I managed to work around this bug by adding user accounts to the root
group in /etc/group.
Yes, I do know this is a nasty, odiferous kludge, with so many horrible
security implications that I can't even count them, but my elderly mom
(who really doesn't understand the difference between Windows
I installed camera.app on a Jaunty system (via a command line, using
aptitude), and even after a restart, this -60 error still happens
when a camera is connected.
--
Error initializing camera: -60: Could not lock the device
https://bugs.launchpad.net/bugs/331681
You received this bug
Hmmm... It's working great for me (which I do think is bizarre, since it
also depends on libgphoto, just like F-Spot.) I'm attaching some of the
properties items from synaptic, so that you can compare and see what may
or may not be installed or missing on your machine.
** Attachment added:
... and the installed files.
** Attachment added: synaptic properties installed files
http://launchpadlibrarian.net/28530280/camera.app-properties-installed_files
--
Error initializing camera: -60: Could not lock the device
https://bugs.launchpad.net/bugs/331681
You received this bug
As best I can tell, what you installed is absolutely identical to what I
installed.
Here is my output from aptitude show camera.app:
Package: camera.app
State: installed
Automatically installed: no
Version: 0.8.0-8build1
Priority: optional
Section: universe/graphics
Maintainer: Ubuntu MOTU
I experienced the same problem as mentioned above. but after i red
ricardisimo's comment, i was willing to give it a try by installing
camera.app package from the synaptic. And the result was very good.
Now, my Jaunty machine is able to detect nikon coolpix S51 . thanks a
lot ricardisimo for your
I have a Kodak C533 and I am also no longer able to connect my camera
(worked great up until Jaunty). I get the Error initializing camera:
-60: Could not lock the device error
--
Error initializing camera: -60: Could not lock the device
https://bugs.launchpad.net/bugs/331681
You received this
I assume the above is an extremely temporary workaround which won't
survive a reboot. Is the right solution going to involve adding
something to /lib/udev/rules.d/50-udev-default.rules or some other
/lib/udev/rules.d/* file?
--
Error initializing camera: -60: Could not lock the device
Yes, you are correct, this probably won't even survive the unplug/replug
of the device since that should destroy and recreate the devices...I
wasn't sure where to start on a more permanent solution, your idea
sounds good. I'll try it out soon.
--
Error initializing camera: -60: Could not lock
Ooops, this is not a bug on my Motozine ZN5. There are USB settings
that allow the phone to be mounted as either a camera, memory card, etc.
Changing the USB setting to memory card fixed it.
--
Error initializing camera: -60: Could not lock the device
https://bugs.launchpad.net/bugs/331681
You
I was having this problem with my Canon SX10 IS, and I fixed it thus.
The USB bus/device IDs (found through lsusb) led me to /dev/usbdev2.25*.
I checked the permissions on these files and they were root:root 660
which means my user can't access them. My user is already in the plugdev
group so I
Same problems as the others with a Kodak C533 plugged into USB, right
down to the screen shots and dmesg already mentioned. Additionally, the
internal flash memory card reader would not work properly. The drives in
the reader do not show up in Computer. I could temporarily get them to
appear by
Same as The Other James (I'm James Berg ;) ), but this time with a Kodak
EasyShare Z1275. This is really annoying!
--
Error initializing camera: -60: Could not lock the device
https://bugs.launchpad.net/bugs/331681
You received this bug notification because you are a member of Ubuntu
Bugs, which
I'm having a similar problem with a Motorola Motozine ZN5. It used to
mount the two memory cards and I could copy mp3 files etc back and
forth. Now only one drive mounts and I get the -60 error mentioned
above.
dmesg shows:
[ 126.068017] usb 1-6: new high speed USB device using ehci_hcd and
I have a Kodak EasyShare C310 showing the same error multiple times,
than finally mounting. However, I cannot seem to download any of my
pictures to my hard drive. I had a similar problem with this same camera
under both Feisty and Gutsy, evidently due to some problem with newer
versions of
Well, at the very least I have found an application that does work, and
pretty flawlessly: Camera. It is Camera under Add/Remove... but
camera.app in Synaptic. I also installed gphoto in Synaptic, because it
was recommended within libgphoto, but I don't believe that had anything
to do with this
I'm seeing the same problem (the Error initializing camera: -60: Could
not lock the device) with Jaunty Jackalope beta and a Kodak Z712 IS.
Under Intrepid Ibex, it worked like a charm.
--
Error initializing camera: -60: Could not lock the device
https://bugs.launchpad.net/bugs/331681
You
** Attachment added: Screen shots, showing the problem
http://launchpadlibrarian.net/22882862/screenShots.zip
** Attachment added: BootDmesg.txt
http://launchpadlibrarian.net/22882883/BootDmesg.txt
** Attachment added: CurrentDmesg.txt
60 matches
Mail list logo
