Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 481436 - kde 4.11 with two speparate screens without xinerama does not work
Summary: kde 4.11 with two speparate screens without xinerama does not work
Status: RESOLVED INVALID
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] KDE (show other bugs)
Hardware: AMD64 Linux
: Normal normal
Assignee: Gentoo KDE team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-08-17 10:01 UTC by Mario Bachmann
Modified: 2013-09-11 10:38 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Mario Bachmann 2013-08-17 10:01:30 UTC
I have two separate screens in my xorg.conf:

Section "ServerLayout"
    Identifier     "einer"
    Screen      0  "Screen_27" 0 0      #vorher:1920 0
    Screen      1  "Screen_24" LeftOf "Screen_27"
    Option         "Xinerama" "0"
EndSection

kde 4.11.0 does not like it.

Reproducible: Always

Steps to Reproduce:
1. upgrade from kde 4.10.5 to 4.11.0
2. use xorg.conf with two separate screens
3. try to use the second screen
Actual Results:  
With kde-base/kde-meta-4.11.0 i can move the mouse to Screen_24, but when I start programs (from the menu configured in kde 4.10.5), there are no borders. 

I tried a fresh ~/.kde4, but then I found no way to start a program on Screen_24. I even cannot configure the desktop. 

Expected Results:  
I expect useful behaviour like in the previous version. With kde-base/kde-meta-4.10.5 it worked. I configured both screens in kde. I can move the mouse between the screens, but no windows. I like this setup, because the displays have different dpi. 

When I change xinerama to true in xorg.conf, I have a big screen and it seems to work, but i prefer the "two separate screens"-setting.
Comment 1 Michael Palimaka (kensington) gentoo-dev 2013-08-20 13:05:57 UTC
Please report upstream, then link back here.
Comment 2 Mario Bachmann 2013-09-11 09:29:55 UTC
This bug is not a bug, it's a feature. Please close the bug report.