[Dx-packages] [Bug 1319195] Re: indicator-datetime set for 24 hours does not show 24 hour clock for "Other Locations"

2017-03-13 Thread Nelson Elhage
@paulgear, what locale is your system in? If you're in a 24-hour locale, as mentioned in #5, this bug is not present (well, to be precise, it's present in the opposite direction). -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-datet

[Dx-packages] [Bug 1319195] Re: indicator-datetime set for 24 hours does not show 24 hour clock for "Other Locations"

2017-03-12 Thread Nelson Elhage
I'm sorry, that should be `en_GB.UTF-8`. But I just tested and confirmed that workaround works. -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-datetime in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1

[Dx-packages] [Bug 1319195] Re: indicator-datetime set for 24 hours does not show 24 hour clock for "Other Locations"

2017-03-12 Thread Nelson Elhage
This is a terrible hack, but I've discovered that the applet will respect your locale, just not the preference option. So setting `export LC_TIME=en_UK.UTF-8` in your `.gnomerc` should work, assuming you have the `en_UK.UTF-8` locale installed and configured. -- You received this bug notificatio

[Dx-packages] [Bug 1292217] Re: screen lock has triggered but keyboard is still connected to the main session

2014-04-08 Thread Nelson Elhage
@seb128: I came back to my laptop after having locked it manually, and having had the lock timeout elapse. I unlocked the screen, and started using the laptop. 5-10s later the screen locked, per #1292451. I typed my password again and hit Enter, and nothing happened. Trying again, I noticed that t

[Dx-packages] [Bug 1292217] Re: lightdm screen lock has triggered but keyboard is still connected to the main session

2014-03-31 Thread Nelson Elhage
This also just affected me. Possibly-relevant detail from my environment: If I explicitly lock the screen and then also wait for a lock timeout, I somehow end up with two lock screens -- I unlock the machine, I can interact with the desktop for a few seconds, and then a second lock screen pops up.