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 preventing any other application from getting exclusive access. This was happening even after I temporarily added my user account to the "root" group, and after I added stuff to /etc/udev/rules.d to recognize my camera and put its USB device file in the "plugdev" group.
See http://ubuntuforums.org/showpost.php?p=7205...@postcount=4 for more on this. I killed off the running gvfs-gphoto2-volume-monitor process, and I also changed the permissions on that application's binary to make it non- executable. After doing this, I was able to mount my camera and access it from Picasa2. Another workaround might possibly be to uninstall the gphoto2 package; I haven't tried this yet. -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
