Ubuntu
kdebase package

Cancelled KDM-session in vt8 doesn't return to vt7

Bug #47318 reported by jeroenl
12
Affects Status Importance Assigned to Milestone
kdebase (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Binary package hint: kdm

Using up-to-date Dapper:

I had the following problem a few minutes ago:

*I started a new session via the kde-menu
*I didn't fill in the login-details, but switched back to vt7 using the start-button in the kdm-dialog. So the kdm-session was still open on vt8.
*Back in vt7 I contineus and after a short while kdem timeout on vt8, but the screenfocus didn't return to vt7, but to an unknown unassigned vt or stayed at vt8! Trying to switch using ctrl+alt+f7 didn't work and actually those keys never work in KDM.
*So I had no change to switch to another vt, so I had do a hard reboot :-(

Jeroen

Revision history for this message
jeroenl (jeroenl) wrote :

This bug is also still present. It happened yesterday again.

Log in 2 accounts. In one of those account start a new (KDM) session. In KDM switch back to one of the other accounts (this happens when I e.g. started a new session by accident). It will switch back to that other account, but after a while, the hidden KDM-session will time-out and the screen flickrs a sec and it is switching back to one of the blank vt's. You can't switch back vt7 or vt8 because those keys are not working in Kubuntu.

Please fix this!?

Jeroen

Revision history for this message
Yuriy Kozlov (yuriy-kozlov) wrote :

Thank you for filing this bug.

I can't reproduce it on Feisty Herd 4. The screen properly returns to vt7. Could you try Edgy or Feisty and see if you have the problem?

Changed in kdebase:
status: Unconfirmed → Needs Info
Revision history for this message
Yuriy Kozlov (yuriy-kozlov) wrote :

Are you running nvidia?

On another Feisty system that uses the nvidia driver, it didn't come back to vt7. I could change back to it with ctrl+alt+f7, but the screen was frozen although I could move my mouse. This is probably related to bug 32389.

Revision history for this message
jeroenl (jeroenl) wrote :

No I'm not running nvidia.

On Edgy, it happens not very often any more and if it happens I can use the function keys now, so it's solved for 95%. Didn't test it yet on Feisty. Will migrate later this week. I will keep you informed if it happens again.

Revision history for this message
jeroenl (jeroenl) wrote :

This is still a problem in Feisty. Although it is not as critical anymore, because the ctrl+f*-keys work are working as they should. Still if a user that is not familiar with the vt's, it is still a important issue. Didn ;t check it on Gutsy though.

Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for kdebase (Ubuntu) because there has been no activity for 60 days.]

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.