Bug 391234 - Login screen broken if no session is selected
Summary: Login screen broken if no session is selected
Status: RESOLVED DUPLICATE of bug 390179
Alias: None
Product: openSUSE 11.0
Classification: openSUSE
Component: KDE4 Workspace (show other bugs)
Version: Beta 3
Hardware: x86-64 openSUSE 11.0
: P5 - None : Normal (vote)
Target Milestone: ---
Assignee: Dirk Mueller
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on: 269961
Blocks:
  Show dependency tree / graph
 
Reported: 2008-05-16 09:25 UTC by Jan-Christoph Bornschlegel
Modified: 2008-05-16 10:29 UTC (History)
1 user (show)

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Jan-Christoph Bornschlegel 2008-05-16 09:25:24 UTC 
I installed Beta3 / KDE from DVD, everything pretty much default except I preserved some partitions (/home et. al.). I created the same local user as before, and installed pretty much the default enabling the images.

I unchecked the autologin and the "use same passwd for admin" boxes.

At first login at rl5 I entered the jogin name and a warning popped up that the previous session type is invalid and I should pick a new one. I did so, but then all textfields behave strange and nothing but ctrl-alt-1..5 and init3/init5 helps.

The behaviour goes away forever if I pick a session type _before_ I type anything anywhere.
In subsequent logins it works fine even if I don't pick a session type.
Comment 1 Jan-Christoph Bornschlegel 2008-05-16 09:35:53 UTC 
I should mention that the preserved home directory belongs to a local user that never saw KDE4 before, so maybe some metadata required for kde4 is missing?
Some desktop symbols (logout, lock for instance) are also broken, maybe for the same reason?
Comment 2 Dirk Mueller 2008-05-16 09:49:46 UTC 

*** This bug has been marked as a duplicate of bug 390179 ***
Comment 4 Dirk Mueller 2008-05-16 10:29:35 UTC 
no, it is a general kdm bug, and the fixed package was not checked in for beta3. you're about the 10th person to report the issue ;)