Resume after hibernate on KDE 4.1 reveals an unlocked session
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
KDE Base |
Fix Released
|
Medium
|
|||
kdebase-workspace (Ubuntu) |
Fix Released
|
Medium
|
Unassigned | ||
Bug Description
This problem is non-existent (the last time I checked) on KDE 3.5.9. It appears to be a KDE 4.1 related glitch.
What I expected to happen ?
When I resume after hibernate, I am usually presented with a locked screensaver, which allows me to resume my KDE session when I supply a password. This was the behavior on KDE 3.5.9.
What happened instead ?
I am presented with an unlocked session ready to go. This appears to be graphics card independent - tested it on both an ATI X1300 card as well as an Intel 915 card. Can try with an Nvidia card if requested.
$ lsb_release -rd
Description: Ubuntu 8.04.1
Release: 8.04
$ apt-cache policy kubuntu-
kubuntu-
Installed: 0.14-0ubuntu1~
Candidate: 0.14-0ubuntu1~
Version table:
*** 0.14-0ubuntu1~
500 http://
100 /var/lib/
0.14 0
500 http://
$ apt-cache policy acpi-support
acpi-support:
Installed: 0.109
Candidate: 0.109
Version table:
*** 0.109 0
500 http://
100 /var/lib/
Changed in linux: | |
importance: | Undecided → Medium |
Changed in kdebase: | |
status: | Unknown → Fix Released |
Changed in kdebase: | |
importance: | Unknown → Medium |
The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would appreciate it if you could please test this newer 2.6.27 Ubuntu kernel. There are one of two ways you should be able to test:
1) If you are comfortable installing packages on your own, the linux-image- 2.6.27- * package is currently available for you to install and test.
--or--
2) The upcoming Alpha5 for Intrepid Ibex 8.10 will contain this newer 2.6.27 Ubuntu kernel. Alpha5 is set to be released Thursday Sept 4. Please watch http:// www.ubuntu. com/testing for Alpha5 to be announced. You should then be able to test via a LiveCD.
Please let us know immediately if this newer 2.6.27 kernel resolves the bug reported here or if the issue remains. More importantly, please open a new bug report for each new bug/regression introduced by the 2.6.27 kernel and tag the bug report with 'linux-2.6.27'. Also, please specifically note if the issue does or does not appear in the 2.6.26 kernel. Thanks again, we really appreicate your help and feedback.