The other possibility (and the one I'm more leaning toward now) is that
LibRaw doesn't recognize the .orf files. LibRaw is the library Shotwell
uses to process RAW files.
You can import a newer version of Shotwell from our PPA:
https://launchpad.net/~yorba/+archive/ppa However, I don't know if
I totally disagree.
The computer should lock automatically when idle. Instead of solving the
problem you want to get rid of the feature.
There are times when people are distracted and walk away from the
computer. If someone wanted to be malicious this would be their
opportunity. Just do a little
Yes but that idle lock feature doesn't work and cannot be trusted. It would
be like saying trust SSL but its using a NULL cipher...
--
Kristian Erik Hermansen
https://www.linkedin.com/in/kristianhermansen
https://profiles.google.com/kristian.hermansen
On Nov 4, 2013 8:55 PM, encompass
So are you proposing we get rid of the autolock functionality because we
can't solve this bug? Or is there some other solution your providing here?
On Tue, Nov 5, 2013 at 6:58 AM, Kristian Erik Hermansen
kristian.herman...@gmail.com wrote:
Yes but that idle lock feature doesn't work and
Yes. Remove it since it is a decade long bug.
--
Kristian Erik Hermansen
https://www.linkedin.com/in/kristianhermansen
https://profiles.google.com/kristian.hermansen
On Nov 4, 2013 9:20 PM, encompass encomp...@gmail.com wrote:
So are you proposing we get rid of the autolock functionality
Encompass wrote: The computer should lock automatically when idle.
Instead of solving the problem you want to get rid of the feature.
But the feature only works some of the time, and the thread here makes
it clear it isn't going to be fixed while the system uses X.
A security feature that only
Initially I was tempted to say we can't fix it because popup menus own
(grab) the keyboard and that blocks the screensaver from taking
ownership of the keyboard. But now I wonder...
Can't the screensaver just force XUngrabKeyboard before trying to grab
it? Would that work?
--
You received this
** Attachment added: image002.jpg
https://bugs.launchpad.net/bugs/49579/+attachment/3900363/+files/image002.jpg
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-screensaver in Ubuntu.
https://bugs.launchpad.net/bugs/49579
Either that and even if it doesn't work, can't we get a hack that kills
the entire X session in the event the lock is unsuccessful? Or call a
user-defined script? Those would be more useful than removing the
feature altogether.
--
You received this bug notification because you are a member of
Killing the whole login is pointless because you'd be killing that which a
locked screen is meant to protect.
Killing just the X session (client) holding the lock is unacceptable because
killing a user's apps or shell is worse than the bug itself.
If we can get the screensaver to just
Public bug reported:
In Ubuntu 13.10, most of Evince's menu items have been moved into the
gear cog on the upper right corner of the window like Nautilus, leaving
a single Help menu item on the application menu. This makes it
effectively useless with Unity's HUD, especially when the Help menu
301 - 311 of 311 matches
Mail list logo
