[Bug 402734] New: External Monitor Set as Primary
https://bugzilla.novell.com/show_bug.cgi?id=402734 Summary: External Monitor Set as Primary Product: openSUSE 11.0 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: SaX2 AssignedTo: sndirsch@novell.com ReportedBy: francis@opensuse.org QAContact: qa@suse.de Found By: --- When I plug in an external monitor and reconfigure SaX, it always puts the external monitor as primary instead of the laptop screen. This is pretty undesirable when you i.e. unplug the external monitor, and the icons+panel are on the other screen. Also, this didn't happen in 10.3 with the same computer and monitor. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=402734
User francis@opensuse.org added comment
https://bugzilla.novell.com/show_bug.cgi?id=402734#c1
--- Comment #1 from Francis Giannaros
https://bugzilla.novell.com/show_bug.cgi?id=402734
User sndirsch@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=402734#c2
Stefan Dirsch
https://bugzilla.novell.com/show_bug.cgi?id=402734
User francis@opensuse.org added comment
https://bugzilla.novell.com/show_bug.cgi?id=402734#c3
Francis Giannaros
https://bugzilla.novell.com/show_bug.cgi?id=402734
User sndirsch@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=402734#c4
Stefan Dirsch
https://bugzilla.novell.com/show_bug.cgi?id=402734
User francis@opensuse.org added comment
https://bugzilla.novell.com/show_bug.cgi?id=402734#c5
Francis Giannaros
https://bugzilla.novell.com/show_bug.cgi?id=402734
User sndirsch@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=402734#c6
Stefan Dirsch
https://bugzilla.novell.com/show_bug.cgi?id=402734
User stbinner@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=402734#c7
Stephan Binner
https://bugzilla.novell.com/show_bug.cgi?id=402734
User sndirsch@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=402734#c8
Stefan Dirsch
https://bugzilla.novell.com/show_bug.cgi?id=402734
User dmueller@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=402734#c9
Dirk Mueller
https://bugzilla.novell.com/show_bug.cgi?id=402734
User sndirsch@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=402734#c10
Stefan Dirsch
there is no such thing as "primary screen" anymore with xrandr 1.2. it puts the panel on the biggest screen by default.
This is exactly the issue here. Please make it at least configurable (including KDM login screen). Thanks. ==> Enhancement -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=402734
Stephan Binner
https://bugzilla.novell.com/show_bug.cgi?id=402734
User llunak@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=402734#c11
Lubos Lunak
https://bugzilla.novell.com/show_bug.cgi?id=402734
User sndirsch@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=402734#c12
Stefan Dirsch
https://bugzilla.novell.com/show_bug.cgi?id=402734
Stefan Dirsch
https://bugzilla.novell.com/show_bug.cgi?id=402734
User llunak@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=402734#c13
Lubos Lunak
https://bugzilla.novell.com/show_bug.cgi?id=402734
User sndirsch@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=402734#c14
Stefan Dirsch
https://bugzilla.novell.com/show_bug.cgi?id=402734
Stefan Dirsch
https://bugzilla.novell.com/show_bug.cgi?id=402734
User federico@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=402734#c15
Federico Mena Quintero
https://bugzilla.novell.com/show_bug.cgi?id=402734
User sndirsch@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=402734#c16
Stefan Dirsch
https://bugzilla.novell.com/show_bug.cgi?id=402734
User federico@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=402734#c17
Federico Mena Quintero
https://bugzilla.novell.com/show_bug.cgi?id=402734
User mhopf@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=402734#c18
--- Comment #18 from Matthias Hopf
https://bugzilla.novell.com/show_bug.cgi?id=402734
User federico@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=402734#c19
--- Comment #19 from Federico Mena Quintero
FWIW, RandR 1.3 will have properties that will tell you exactly the type of the outputs. I'll go into details as soon as it's actually implemented (I'm done with the spec, but implementation need some time, and all drivers have to adopt). When going for the name, please also check for "PANEL", because that's what we use for RadeonHD.
Could RadeonHD use "LVDS" just like the other drivers? If the logic to check the output names indeed has to live in the clients, I'd rather have a standard naming scheme rather than having to adjust to differences in drivers. [Otherwise someone will write another driver for another chipset and call the built-in display "foobar" - then the software will fail :) ]
Patching the Xserver is IMHO a no-go, because the order is up to the driver.
Actually, what if we let the driver return whatever it wants, but then have the hardware-independent part reorder the list of outputs? Each output/CRTC/etc. would still keep its ID, so the XRR* functions would still work as expected. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=402734
User mhopf@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=402734#c20
--- Comment #20 from Matthias Hopf
Could RadeonHD use "LVDS" just like the other drivers? If the logic to check
No. The term LVDS is a technical term and people cannot be forced to use them, IMHO it has been a bad decision by the radeon developers in the first place. Also, it's bad to use a de-facto standard for something that is (apparently) not standardized. That's exactly what the properties should be for. We recently had a poll for changing output names (for different issues). Result was that if at all they should be changed only slightly. Everybody agreed that PANEL is superior to LVDS.
the output names indeed has to live in the clients, I'd rather have a standard naming scheme rather than having to adjust to differences in drivers.
There is already none. And you're not guaranteed that there will ever be one.
[Otherwise someone will write another driver for another chipset and call the built-in display "foobar" - then the software will fail :) ]
Exactly. Never EVER use names for meta-information. Period. That's one of the lessons that should have been learned a long time ago. That said, using the name as decision maker is probably the best you can do for SLE 11 ATM :-( Depends on the release schedule whether we would have Xserver 1.6 (which would - hopefully - include standard property support), but ATM I doubt that.
Actually, what if we let the driver return whatever it wants, but then have the hardware-independent part reorder the list of outputs? Each output/CRTC/etc. would still keep its ID, so the XRR* functions would still work as expected.
In that case you're forcing a heuristics-based order upon the order the driver issued, and while the driver might have had a clue about the order, the Xserver will never have. E.g. in the radeonhd driver you can change the order of the outputs if the BIOS isn't telling you the correct order, that would no longer work if the Xserver reorders everything. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply@novell.com