[Bug 1113420] Re: Alt+ window menu shortcuts cannot be disabled
Linux power users tend to make heavy use of keybindings involving alt/meta and ctrl. Consequently, this is a very serious issue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1113420 Title: Alt+ window menu shortcuts cannot be disabled To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1113420/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 331681] Re: Error initializing camera: -60: Could not lock the device
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 Gnome-based distribution (Foresight Linux), which makes me wonder whether the issue could have an Ubuntu component to it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/331681 Title: Error initializing camera: -60: Could not lock the device -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 631759] Re: Error message: Unable to unmount the camera at this time
Thanks Omer. I may end up giving that a try. Actually, though, I'm thinking that gnome's device detection may be at least partly to blame. It's just frustrating that the bug referenced in my earlier post has gone unresolved (indeed unassigned) for almost 2 years, in spite of the fact that it seems to affect a significant number of users (and probably deters a number of would-be users from adopting Ubuntu as their primary distribution). Since I seem to be able to import pictures with gthumb (albeit with the error dialogs mentioned in the other post), I'll probably just use that for now. I can import with F-Spot as well, but it crashes routinely, apparently unable to handle the large (~1) number of images I'm managing... Brett S. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/631759 Title: Error message: Unable to unmount the camera at this time -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 631759] Re: Error message: Unable to unmount the camera at this time
Trying to figure out whether my bug is the same as this one... In Shotwell 0.7.2, in Ubuntu 10.10, I plug in my Kodak EasyShare C533, turn it on, and the following pops up: Error dialog (Qty. 1) Unable to mount KODAK EasyShare C533 Zoom Digital Camera Error initializating camera: -60: Could not lock the device Choose application dialog (Qty. 2) You have just inserted a medium with digital photos. Choose what application to launch. This business of duplicate choose application dialogs has been discussed on other threads: e.g., https://bugs.launchpad.net/ubuntu/+source/linux/+bug/331681 (Note that that bug, which was first reported almost 2 years ago, is confirmed, but still unassigned.) At any rate, if I choose to open Shotwell anyway, and then click on the camera icon within Shotwell, I get... Shotwell needs to unmount the camera from the filesystem in order to access it. Continue? [Cancel/Unmount] So is the behavior I'm seeing with Shotwell a result of bug 331681, or will it be fixed by the fix for the bug in this thread? Also, does the previous post imply that the fix for the bug in this thread will be seen in Shotwell 0.8.1? When is that likely to be available in the stable Ubuntu repository (i.e., available via Update Manager)? Thanks, Brett Stahlman -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/631759 Title: Error message: Unable to unmount the camera at this time -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 331681] Re: Error initializing camera: -60: Could not lock the device
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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/331681 Title: Error initializing camera: -60: Could not lock the device -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 581566] Re: udevd inotify_add_watch no such directory error for physical volumes
Installing cryptsetup fixed it for me too, but I don't really consider this to be a fix. I don't need cryptsetup, and don't like the idea that I'm loading something I don't need upon every boot to mask a bug. I notice this bug is confirmed but still unassigned. Is it considered low priority? I've just installed Ubuntu 10.04, but am considering wiping it out and switching to Debian because of this and another (login screen freeze) issue I've had since installing Ubuntu. Thanks, Brett Stahlman -- udevd inotify_add_watch no such directory error for physical volumes https://bugs.launchpad.net/bugs/581566 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
