[kscreenlocker] [Bug 357368] Screen is not locked when resuming from suspend after upgrading to plasma 5.5.0

2016-01-04 Thread Dave Flogeras via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=357368 --- Comment #15 from Dave Flogeras --- In case anyone else hits this, it seemed to be a Gentoo specific issue for upgraded legacy installations. You can fix it by doing the following: emerge -1a upower This should replace the old power management pac

[kscreenlocker] [Bug 357368] Screen is not locked when resuming from suspend after upgrading to plasma 5.5.0

2016-01-01 Thread Dave Flogeras via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=357368 --- Comment #14 from Dave Flogeras --- Upstream bug filed https://github.com/ConsoleKit2/ConsoleKit2/issues/56 -- You are receiving this mail because: You are watching all bug changes.

[kscreenlocker] [Bug 357368] Screen is not locked when resuming from suspend after upgrading to plasma 5.5.0

2016-01-01 Thread Kai Uwe Broulik via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=357368 --- Comment #13 from Kai Uwe Broulik --- Oh, hmm, no, this is unrelated. Yes, please file a separate bug about this. It looks like something is broken on your system. :/ -- You are receiving this mail because: You are watching all bug changes.

[kscreenlocker] [Bug 357368] Screen is not locked when resuming from suspend after upgrading to plasma 5.5.0

2016-01-01 Thread Dave Flogeras via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=357368 --- Comment #12 from Dave Flogeras --- Can do, but before I do, does this also explain the issue that plasma doesn't lock after setting a 1 minute timeout? Is that a totally different issue? Shall I file a new bug? -- You are receiving this mail bec

[kscreenlocker] [Bug 357368] Screen is not locked when resuming from suspend after upgrading to plasma 5.5.0

2016-01-01 Thread Kai Uwe Broulik via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=357368 Kai Uwe Broulik changed: What|Removed |Added Resolution|INVALID |UPSTREAM --- Comment #11 from Kai Uwe Broulik

[kscreenlocker] [Bug 357368] Screen is not locked when resuming from suspend after upgrading to plasma 5.5.0

2016-01-01 Thread Dave Flogeras via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=357368 --- Comment #10 from Dave Flogeras --- I would like to help, but would require some hand holding as I do not understand the design of the software. For instance, I see in the logind.cpp there are multiple references to falling back to Consolekit if log

[kscreenlocker] [Bug 357368] Screen is not locked when resuming from suspend after upgrading to plasma 5.5.0

2016-01-01 Thread Kai Uwe Broulik via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=357368 --- Comment #9 from Kai Uwe Broulik --- Actually I'm not sure if the screenlocker supports Consolekit 2, PowerDevil does but locking on suspend has been moved to the screen locker. Should be trivial to add, however. Patches welcome :) -- You are recei

[kscreenlocker] [Bug 357368] Screen is not locked when resuming from suspend after upgrading to plasma 5.5.0

2016-01-01 Thread Dave Flogeras via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=357368 --- Comment #8 from Dave Flogeras --- Good point. Screen locking works fine if I press CTRL-ALT-L. However, I noticed something else today which I didn't notice before because my screen usually blanks (or the machine hibernates) on this laptop before

[kscreenlocker] [Bug 357368] Screen is not locked when resuming from suspend after upgrading to plasma 5.5.0

2015-12-31 Thread Bhushan Shah via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=357368 --- Comment #7 from Bhushan Shah --- Do screen locking in general works? Or just lock screen on resume is broken? -- You are receiving this mail because: You are watching all bug changes.

[kscreenlocker] [Bug 357368] Screen is not locked when resuming from suspend after upgrading to plasma 5.5.0

2015-12-31 Thread Dave Flogeras via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=357368 --- Comment #6 from Dave Flogeras --- No, OpenRC on Gentoo does indeed use Consolekit2-1.0.0, which was pulled in when I installed plasma-5.5.0. What else could I check? -- You are receiving this mail because: You are watching all bug changes.

[kscreenlocker] [Bug 357368] Screen is not locked when resuming from suspend after upgrading to plasma 5.5.0

2015-12-31 Thread Kai Uwe Broulik via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=357368 Kai Uwe Broulik changed: What|Removed |Added Resolution|--- |INVALID Status|UNCONFIRMED

[kscreenlocker] [Bug 357368] Screen is not locked when resuming from suspend after upgrading to plasma 5.5.0

2015-12-31 Thread Dave Flogeras via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=357368 --- Comment #4 from Dave Flogeras --- I should also add that I do not use systemd on the affected systems (I use openrc), did anything change in kscreenlocker that might be affected by this? -- You are receiving this mail because: You are watching all

[kscreenlocker] [Bug 357368] Screen is not locked when resuming from suspend after upgrading to plasma 5.5.0

2015-12-31 Thread Kai Uwe Broulik via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=357368 --- Comment #3 from Kai Uwe Broulik --- KScreenlocker has indeed been split into its own separate repository. -- You are receiving this mail because: You are watching all bug changes.

[kscreenlocker] [Bug 357368] Screen is not locked when resuming from suspend after upgrading to plasma 5.5.0

2015-12-31 Thread Dave Flogeras via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=357368 --- Comment #2 from Dave Flogeras --- Hmm. Perhaps it is a Gentoo packaging issue. I have confirmed with other Gentoo folks that they do have the issue. Has anything notable changed in terms of dependencies with the 5.5.x series? I know that Gentoo

[kscreenlocker] [Bug 357368] Screen is not locked when resuming from suspend after upgrading to plasma 5.5.0

2015-12-31 Thread Kai Uwe Broulik via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=357368 Kai Uwe Broulik changed: What|Removed |Added CC||k...@privat.broulik.de --- Comment #1 from Ka