[Bug 1576977] Re: Lots of GEGL-gegl-operation.c-WARNING on starting gimp
I have the identical issue under Mint 18. Google works fine, but they just fill up my console :-) They're only warnings, but it would be nice if someone could clean up the code. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gimp in Ubuntu. https://bugs.launchpad.net/bugs/1576977 Title: Lots of GEGL-gegl-operation.c-WARNING on starting gimp To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gimp/+bug/1576977/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Re: [Bug 1400470] Re: cannot download photos using shotwell via usb
On 09/07/18 17:27, SunBear wrote: > I see the following message from Shotwell 0.22.0 in Ubuntu 16.04 > every time a iPhone4s is plugged in to my computer usb: > > Shotwell Unable to fetch previews from the camera: Could not claim > the USB device (-53) > > I have to click "Ok" to remove this message before I can access > Shotwell. This warning has always appeared for a few years. Annoying. > It will be great that this warning be removed. You are very lucky that clicking OK enables you to proceed like that. This is a well-known and pervasive bug which has remained unfixed for many years, for some unknown reason. "Could not claim the USB device (-53)" means that some other process (I believe a driver of some kind) has already grabbed the device without authorization, and will not let go of it. This kind of usurpation is not really something we want in an operating system. We need to get to the bottom of it, and delete the process which is apparently jumping in where it is not wanted. I am guessing — because I cannot find any concrete information — that it is a kernel driver installed for some other, perfectly authentic, reason, which is doing this as an unwanted side-effect, so the author may be completely unaware that this is happening. I have already recommended elsewhere that the correct interim solution is for camera applications (in your case, Shotwell, but in fact almost anything that needs access to the camera, even a plain file manager) to be able (with sudo authentication) to kill the current claiming process, break the lock, and give the application the access it needs. Long term, it should be possible to identify to the user *what* process has claimed the USB device uninvited, and allow the user to kill the process permanantly (ie remove it from whatever autostart procedure it was spawned from). Until that happens, camera software usage is largely crippled. ///Peter -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to shotwell in Ubuntu. https://bugs.launchpad.net/bugs/1400470 Title: cannot download photos using shotwell via usb To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shotwell/+bug/1400470/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 861493] Re: evince doesn't print duplex on duplex-able printers
Yes, this is still a bug, and still unfixed. My new HP duplex printer works fine from lpr on the command line with the right options for double-sided, and qpdfview can also print both sides, but because the printer default for duplex is Off, Evince's drop-down is stuck on One- Sided and refuses to admit that the printer is capable of both sides. Setting the default behavior to simplex shouldn't eliminate user choice; but it does. Can someone please fix this? -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/861493 Title: evince doesn't print duplex on duplex-able printers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/861493/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1400470] Re: cannot download photos using shotwell via usb
This problem is still present: Shotwell cannot access the camera although it is aware of its existence (it is correctly listed in the LH side menu, in my case a Kodak EZ200). The recommended method of unmounting the device in a file manager seems to be bogus for many people: no device is mounted, so there's nothing to unmount. Something, somewhere, is grabbing the device when it is plugged in, and nothing seems to be able to detect *what* process is responsible. I'm attaching the syslog from when I plug it in. Perhaps someone with better usb-fu can make sense of it. ** Attachment added: "syslog of plugging in Kodak EZ200 under Mint 18" https://bugs.launchpad.net/ubuntu/+source/shotwell/+bug/1400470/+attachment/5146822/+files/ez200 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to shotwell in Ubuntu. https://bugs.launchpad.net/bugs/1400470 Title: cannot download photos using shotwell via usb To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shotwell/+bug/1400470/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 146528] Re: Alacarte crashes on open
No need to remove them. It appears to be just one file, xdg-desktop-menu-dummy.menu which is pwned by root for some stupid reason. Just sudo chown -R .config and it will work. -- Alacarte crashes on open https://bugs.launchpad.net/bugs/146528 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to alacarte in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
