Bug 243914 - Multiple monitors not detected when a 2nd "screen" exists
Summary: Multiple monitors not detected when a 2nd "screen" exists
Status: RESOLVED UNMAINTAINED
Alias: None
Product: plasma4
Classification: Plasma
Component: multiscreen (show other bugs)
Version: 4.8.3
Platform: Unlisted Binaries Linux
: NOR normal
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-07-08 06:18 UTC by Allistar
Modified: 2018-06-08 19:41 UTC (History)
3 users (show)

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 Allistar 2010-07-08 06:18:48 UTC
Version:           unspecified (using KDE 4.4.4) 
OS:                Linux

Hi all,
  I am running kde 4.4.4 on the AMD64 platform (Gentoo). I have a triple head setup with two nvidia cards, with one card providing a single TwinView screen (screen 0) spanning two LCDs and another card providing a separate x screen (screen 1) on the 3rd display. I am running KDE4 on screen 0 and e16 on screen 1. This works well, except that in the KDE control panel called "Multiple monitors" it doesn't think I have a multiple monitor setup. It instead thinks I have a single 3360x1050 display called "default". This has the result that I get just one plasma container spanning both monitors when I want two so I can have independant wallpapers and so maximising windows takes into account monitor edges.

  For now I am using compiz to provide monitor awareness when maximising etc and that works well (and feels snappier than the KWin compositing).

  The interesting thing is that if I remove reference to Screen1 in xorg.conf (essentially removing that monitor from my system) then KDE now detects that screen 0 consists of two monitors again. Adding screen 1 into the mix causes KDE to not see screen 0 as two.

  Is there a way of tricking KDE into thinking that screen 0 is made up of two monitors, or of making the "Multiple Monitors" control panel detect them?

  The only way to make it behave is to lose the 3rd monitor (and hence the second "screen") but I want it to work with 3 monitors. I'm happy to use e26 on the 3rd head, I just want KDE to work as expected on the first two heads.
Thanks,
Allistar.

Reproducible: Always

Steps to Reproduce:
- have a triple head nvidia setup with TwinView configured for the left two minitors and a separate x screen for the right monitor.
- run KDE.


Actual Results:  
KDE doesn't see the TwinView screen as two separate monitors. The "Multiple monitors" control panel doesn't see them either. Plasma spans both monitors when it should have one containment for each.

Expected Results:  
I expect KDE to "see" the TwinView screen as consisting of two monitors. Window maximising should only maximise on the one monitor, not across both.

xrandr -q returns:

Screen 0: minimum 3360 x 1050, current 3360 x 1050, maximum 3360 x 1050
default connected 3360x1050+0+0 0mm x 0mm
   3360x1050      50.0* 

This is the same whether running screen1 disabled or not, so I don't suspect it's relevant.

The xorg.conf file is generated by the nvidia-settings application, though my normal hand crafted file exhibits the same issue.

I can force compiz into seeing a different screen configuration - can I force KDE to do the same?
Comment 1 Beat Wolf 2010-07-08 10:16:44 UTC
you should also try kde 4.5 rc1 or better rc2 when it comes out, there where quite a few multiscreen fixes for kde 4.5
Comment 2 Beat Wolf 2010-10-19 17:14:46 UTC
as mentioned, please retest with at least kde 4.5
Comment 3 Allistar 2010-10-19 22:06:32 UTC
I will wait until KDE4.5 is stable on Gentoo and after upgrading I will retest this.
Comment 4 Michael 2011-07-31 21:52:59 UTC
I can confirm this very exact behavior. I had it with KDE 4.4, 4.5 and now running:

kde-4.6.3
xorg-server-1.10.2
xrand-1.3.4 (libxrand-1.3.1)
kernel 2.6.39 64bit
nvidia drivers 275.21 (happened with older versions, too.

KDE suddenly only recognized the twinview-screen as 'one' monitor, stretching the background, KDM and all other apps. Multiple screen configuration in the system settings is no longer available. Once the third screen is removed (in its 'additional xorg screen' config) and disabled, the TwinView screen is correctly recognized as two Monitors again.

Maybe the OP or anyone else has an idea dispite compitz for a workaround =S

Sincerely
Comment 5 Michael 2011-09-09 02:47:28 UTC
KDE 4.7.1 and nvidia drivers 275.21 on kernel 3.0

No imrovement, same problem. Making it *impossible* to use three screens. Inbetween plasma draws utter nonses (my screens do nto match in size, confusing plasma completely) and every now and then it crashes :-(
Comment 6 Myriam Schweingruber 2012-06-03 19:06:44 UTC
Setting status correctly.
Comment 7 Allistar 2012-06-03 21:01:18 UTC
I can confirm that this problem still happens. 

KDE version: 4.8.3
Distribution: Gentoo
xorg-server: 1.11.2-r2
xrandr: 1.3.5
kernel: 3.2.12 (x86_64)
nvidia-drivers: 295.49
Comment 8 Allistar 2012-06-04 01:30:19 UTC
I think this is a bug in xrandr or one of the libraries it calls (possibly the RANDR extension in xorg itself). If I enter the "xrandr" command from Konsole running in screen 0 (the dual monitor screen that KDE wrongly things is one large monitor) I get this:

xrandr: Failed to get size of gamma for output default
Screen 0: minimum 3360 x 1050, current 3360 x 1050, maximum 3360 x 1050
default connected 3360x1050+0+0 0mm x 0mm
   3360x1050      50.0*
Comment 9 Nate Graham 2018-06-08 19:41:18 UTC
Hello!

This bug report was filed for KDE Plasma 4, which reached end-of-support status in August 2015. KDE Plasma 5's desktop shell has been almost completely rewritten for better performance and usability, so it is likely that this bug is already resolved in Plasma 5.

Accordingly, we hope you understand why we must close this bug report. If the issue described  here is still present in KDE Plasma 5.12 or later, please feel free to open a new ticket in the "plasmashell" product after reading https://community.kde.org/Get_Involved/Bug_Reporting

If you would like to get involved in KDE's bug triaging effort so that future mass bug closes like this are less likely, please read https://community.kde.org/Get_Involved#Bug_Triaging

Thanks for your understanding!

Nate Graham