=== Ursinha is now known as Ursinha-afk
=== Ursinha-afk is now known as Ursinha
[03:22] <cprofitt> curious what to do here -- https://bugs.launchpad.net/ubuntu/+source/unity-greeter/+bug/1255558 -- this bug appears to be fixed in the beta... should I just comment or should something else be done to mark it resolved?
[03:23] <ubot2> Launchpad bug 1255558 in unity-greeter (Ubuntu) "Can't type my password after cold boot" [High,Triaged]
[03:24] <cprofitt> looks like it should potentially be marked invalid
=== Ursinha is now known as Ursinha-afk
=== Ursinha-afk is now known as Ursinha
=== Ursinha is now known as Ursinha-afk
=== Ursinha-afk is now known as Ursinha
=== Ursinha is now known as Ursinha-afk
=== Ursinha-afk is now known as Ursinha
=== Ursinha is now known as Ursinha-afk
=== Ursinha-afk is now known as Ursinha
=== dkessel_ is now known as dkessel
[17:57] <cprofitt> https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1293185
[17:57] <ubot2> Launchpad bug 1293185 in gnome-screensaver (Ubuntu) "Screen saver does not resume after interrupted but not unlocked" [Undecided,New]
[17:58] <penguin42> when you say 'unlock' screen you mean it's sitting there asking you for the password?
[18:13] <cprofitt> penguin42: yes
[18:14] <cprofitt> in past versions of Ubuntu if you hit the 'esc' key or allowed it to sit there for the same period of time as the original screen saver setting it would revert to screen saver mode
[18:14] <cprofitt> now it just sits there at the unlock/login screen
[18:27] <penguin42> cprofitt: Oddly KDE has exactly the same problem and has had for a few versions
[18:27] <cprofitt> penguin42: wonder if it is related
[18:27] <penguin42> cprofitt: Is the 'esc' now doing something else - e.g. clearing the password field but leaving the box ?
[18:27] <cprofitt> let me test
[18:27] <penguin42> cprofitt: I think in KDEs case it was an on-purpose (but annoying) change
[18:28] <cprofitt> nope... 'esc' appears to do nothing
[18:28] <penguin42> cprofitt: It's very annoying - because if you're watching the tv and accidentally nudge the mouse you have the screen light up
[18:29] <cprofitt> yep
[18:32] <penguin42> let me just see if I can reproduce it
[18:35] <penguin42> hmm, I did an explicit lock, then got the login box, then hit escape and it did disappear - but this vm is about a week out of date, let me just update it
[18:35] <cprofitt> yeah, this behavior is new for me... I just loaded a new install with yesterday's daily build
[18:46] <penguin42> cprofitt: You said wait for it to lock by itself - does this bug still happen if you trigger the lock, then hit escape, and then escape again?
[18:46] <cprofitt> penguin42: also, if I hit cntl+alt+L to lock the screen it just goes to the password screen and never blanks the screen
[18:46] <cprofitt> yes, it still appears to happen if I force the lock
[18:47] <cprofitt> physical install on an X230
[18:47] <penguin42> cprofitt: I think someone has rewritten that unlock screen - it looks different to me
[18:48] <cprofitt> yes, the unlock screen looks like the original login screen minus a user selection, etc
[18:49] <penguin42> cprofitt: That's running unity-panel-service --lockscreen-mode
[18:50] <cprofitt> so the package that is an issue is actually the unity-panel-service?
[18:50] <penguin42> yeh, I'll change it and confirm
[18:50] <cprofitt> thanks
[18:50] <cprofitt> good working with you to get to the bottom of it
[18:52] <penguin42> ooh, I think I can escape the lock
[18:53] <penguin42> yep
[18:53] <cprofitt> how?
[18:53] <penguin42> hang on, let me check what I can do, if I can do anything really nasty I need to file it as security rather than discuss
[18:54] <cprofitt> ok
[18:54] <penguin42> I can certainly shutdown - but that might be on purpose
[18:55] <penguin42> and start a guest session, that also might be on purpose
[18:56] <cprofitt> I was not able to do either of those things on mine..
[18:56] <cprofitt> but not sure how you were doing that
[18:59] <penguin42> cprofitt: OK, I can just reboot or get a guest session, which I think you could do before - so I think it's just you can't see the menu
[18:59] <cprofitt> noticed that the CPU on the test machine is running 10 degrees higher than normal too
[18:59] <penguin42> cprofitt: If you click on the 'cog' while it's locked, the cog highlights, you can then use the arrow keys to select items on the cog menu, although the menu isn't visible
[19:00] <cprofitt> ah let me try
[19:00] <cprofitt> yep
[19:01] <cprofitt> looks like some very unfinished code tbh
[19:01] <penguin42> nod possible
[19:04] <penguin42> cprofitt: Bug 1293197
[19:04] <ubot2> Launchpad bug 1293197 in unity (Ubuntu) "Cog menu active but not visible under lock" [Undecided,New] https://launchpad.net/bugs/1293197
[19:06] <cprofitt> how did you gather those files? Should we gather something similar for the screen saver bug?
[19:06] <penguin42> cprofitt: I reported it by running ubuntu-bug unity-service
[19:06] <cprofitt> k
[19:08] <cprofitt> I try that and I get the message that untiy-service does not exist... wonder if I a missing something else
[19:10] <penguin42> sorry, services
[19:10] <cprofitt> cool thanks
[19:12] <cprofitt> anyway to use ubuntu-bug to add to an existing?
[19:18] <hjd> cprofitt: apport-collect bugnumber :)
[19:19] <cprofitt> danke
[19:19] <hjd> (I think that only works if you're the one who reported the bug, but that seems to be the case here)
=== lfaraone_ is now known as lfaraone
[21:58] <Thedemon007> ubuntu have secuity issues in chromium-browser ?? version ubuntu 32.0.1700.107 debian: 32.0.1700.123 http://metadata.ftp-master.debian.org/changelogs//main/c/chromium-browser/chromium-browser_32.0.1700.123-1~deb7u1_changelog
[22:13] <Thedemon007> i open this bug https://bugs.launchpad.net/ubuntu/+source/wireshark/+bug/1290100
[22:13] <ubot2> Launchpad bug 1290100 in wireshark (Ubuntu Saucy) "[Need fake sync] a lot vulnerabilities buffer overflow crash ddos" [High,Confirmed]
[22:14] <Thedemon007> They could make a fake synchronization of debian wheezy, to precise??
=== ryanakca_ is now known as ryanakca