Bug 253409 - Ignore LVDS Resolution on Notebooks if lid is closed
Summary: Ignore LVDS Resolution on Notebooks if lid is closed
Status: RESOLVED DUPLICATE of bug 48602
Alias: None
Product: kdm
Classification: Miscellaneous
Component: general (show other bugs)
Version: unspecified
Platform: Debian unstable Linux
: NOR normal
Target Milestone: ---
Assignee: kdm bugs tracker
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-10-06 18:38 UTC by info
Modified: 2010-10-06 22:30 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description info 2010-10-06 18:38:32 UTC
Version:           unspecified (using KDE 4.5.1) 
OS:                Linux

I have a Lenove Thinkpad X201 but I think this affects all noteboook users, who use an external Monitor. 

KDM should ignore the internal Monitor if the Notebook lid is closed (/proc/acpi/button/lid/LID/state), so that the maximum resolution of the external Display is set automatically.
The way it is configured now, I only get the maximum resolution, which is supported by both monitors, which makes no sense, since the internal obviously can't be used, if the lid is closed.
I set up an xrandr script in /etc/kde4/kdm/Xsetup which disables the internal display and sets the full resolution of the external one, but then the KDM Wallpaper and Elements are not centered, which looks unprofessional. 

If you need any further information, I will be happy to provide these.

Reproducible: Didn't try

Steps to Reproduce:
Boot with lid closed and external display connected

Actual Results:  
Not maximum resolution of external display

Expected Results:  
Maximum resolution on external Display

No xorg.conf used
Comment 1 Oswald Buddenhagen 2010-10-06 22:10:56 UTC
seriously ...

*** This bug has been marked as a duplicate of bug 18597 ***
Comment 2 info 2010-10-06 22:26:12 UTC
(In reply to comment #1)
Sorry, but I am not sure if the bug you posted helps here.
I have DPMS activated but this does not fix my problem. Did you read my entire post ?
Comment 3 Oswald Buddenhagen 2010-10-06 22:30:09 UTC
course i picked the wrong reference bug ...

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