Bug 189088 - Layout problems in unlock dialog
Summary: Layout problems in unlock dialog
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kscreensaver
Classification: Unmaintained
Component: general (show other bugs)
Version: unspecified
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: kscreensaver bugs tracking
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-04-08 05:33 UTC by Christoph Bartoschek
Modified: 2018-09-04 04:06 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:

Attachments
Snapshot showing the problem (32.40 KB, image/png)
2009-04-08 05:33 UTC, Christoph Bartoschek 		Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Christoph Bartoschek 2009-04-08 05:33:33 UTC 
Created attachment 32693 [details]
Snapshot showing the problem

Version:            (using KDE 4.2.2)
OS:                Linux
Installed from:    SuSE RPMs

The unlock dialog is not properly aligned. The user name and the password should 
be aligned. See the snapshot.
Comment 1 Oswald Buddenhagen 2009-04-09 08:23:15 UTC 
hmm. technically, the widgets *are* properly aligned ... just that the label has no inherent frame like the line edit does. :o
an undecorated line edit instead of a label would probably work better.
Comment 2 Christoph Feck 2010-10-19 15:48:21 UTC 
You could use a readOnly() line edit.
Comment 3 Martin Flöser 2015-01-23 13:20:39 UTC 
The screen locker architecture changed with Plasma 5. The classic screen savers are no longer supported. The 4.x series won't see any further feature development, so this bug report won't be implemented as it doesn't apply to our current version any more.

I want to thank you for your bug report and for helping improving the quality of our software and I'm sorry that we were not able to provide a fix before we retired the affected component.
Comment 4 Andrew Crouthamel 2018-09-04 04:06:03 UTC 
Hello! Sorry to be the bearer of bad news, but this project has been unmaintained for many years and I will be closing this bug. Please re-test and file a new bug with kscreenlocker if the issue persists.