Bug 335528 - Xinerama problems with an external monitor (Dell 2007WFP) on a Dell D620 Laptop
Summary: Xinerama problems with an external monitor (Dell 2007WFP) on a Dell D620 Laptop
Status: RESOLVED WONTFIX
Alias: None
Product: openSUSE 10.3
Classification: openSUSE
Component: YaST2 (show other bugs)
Version: Final
Hardware: x86 openSUSE 10.3
: P5 - None : Normal (vote)
Target Milestone: ---
Assignee: E-mail List
QA Contact: Jiri Srain
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: randr-tracker
  Show dependency tree / graph
 
Reported: 2007-10-21 13:02 UTC by Alessandro Bellina
Modified: 2008-03-26 21:25 UTC (History)
0 users

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 Alessandro Bellina 2007-10-21 13:02:21 UTC 
Xinerama won't create the right xorg.conf for my monitor arrangement. I have two monitors, one LCD outside and the other from the laptop. If I use Xinerama to try to "extend" the desktop only one monitor gets added. I have been able to get around that manually by adding the laptop monitor to my devices in xorg.conf and switching the screen resolutions around.
Comment 1 Matej Horvath 2007-10-22 13:04:32 UTC 
Please attach your yast logs (http://en.opensuse.org/YaST/Bugs), output of 'hwinfo --monitor --gfxcard' and the wrong and correct xorg.conf .
Comment 2 Alessandro Bellina 2007-10-22 13:28:17 UTC 
Matej, I messed around with it so much that I basically totally corrupted the X11 server and just had to reinstall the operating system. I installed Ubuntu however because I heard good things about it but I haven't tried the multiple screen setup again. They use Xinerama I belive, should I just post my logs and hwinfo output here? or should I take that to the Ubuntu wiki if I have problems?
Comment 3 Matej Horvath 2007-10-26 07:40:05 UTC 
Since you don't have the opensuse logs and config files, we won't be able to figure out where was the problem. Therefore I have to close this bug as WONTFIX. But feel free to reopen it, in case you can provide the needed information.