Bug 492343 - KDE Login Green splash screen width
Summary: KDE Login Green splash screen width
Status: VERIFIED DUPLICATE of bug 458920
Alias: None
Product: openSUSE 11.1
Classification: openSUSE
Component: KDE4 Workspace (show other bugs)
Version: Final
Hardware: 64bit openSUSE 11.1
: P4 - Low : Minor (vote)
Target Milestone: ---
Assignee: E-mail List
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-04-06 07:46 UTC by Remco vd Zon
Modified: 2009-04-10 21:06 UTC (History)
1 user (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Remco vd Zon 2009-04-06 07:46:04 UTC
User-Agent:       Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.0.7) Gecko/2009022800 SUSE/3.0.7-1.1.6 Firefox/3.0.7

When you log into the KDE System with the OpenSuse defaults KDE splashscreen you will notice that the grey bar is not wide enough. This is only with 'wider' screens.

(See Actual Results and Expected results)

Reproducible: Always

Steps to Reproduce:
0. Set your screenwidth to 1920
1. Use default KDE splashscreen
2. Log in to KDE
Actual Results:  
Splashscreen nog wide enough

|                  |
|   XXXXXXXXXXXX   |
|                  |

Expected Results:  
|                  |
|XXXXXXXXXXXXXXXXXX|
|                  |
Comment 1 Forgotten User bSWU20Bh6O 2009-04-09 16:07:56 UTC
I can confirm this behavior. The gray background bar for kdm does not extend all the way to the edges. Changing the priority to p4-low.
Comment 2 Lubos Lunak 2009-04-09 18:04:46 UTC
(In reply to comment #1)
> I can confirm this behavior. The gray background bar for kdm does not extend
> all the way to the edges. Changing the priority to p4-low.

Did you really mean KDM or actually the splashscreen (in which case this is a dupe of #458920)?
Comment 3 Forgotten User bSWU20Bh6O 2009-04-10 21:06:57 UTC
No idea why I said kdm, it is the splash. Marking as duplicate of #458920

*** This bug has been marked as a duplicate of bug 458920 ***