Bug 167559

Summary:	KDE4 graphic desktop on 2nd seperate screen
Product:	[Plasma] kwin	Reporter:	applejack <justlostintime>
Component:	general	Assignee:	Unassigned bugs mailing-list <unassigned-bugs>
Status:	RESOLVED DUPLICATE
Severity:	normal	CC:	andresbajotierra, frailis, jonas.vejlin, salrio74
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	openSUSE
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description applejack 2008-07-28 02:46:32 UTC

Version:            (using KDE 4.0.5)
Installed from:    SuSE RPMs
OS:                Linux

I have my xserver configured with two separate screens ie not spread across two desktops. In kde3 with Suse 10.3 this works fine I have two desktops separate, with full functionality. I can move my mouse between both, but cannot move items as it should be.

OS Suse 11

In kde4 using kwin4 the second screen is blank, and when I move the mouse pointer there it changes to an X and the screen is black.

In Kde4 using Compwiz the mouse pointer stays as a pointer but the 2nd screen is still black.

In the latest update of KDE3 and kwin3 with kde4 installed as well, the second screen displays a desktop but when I open a window the border and Title bars are missing. But everything appears to work with Compwiz as the manager.

I am using a Nvidia driver for my graphic card and the configuration was done using the nvidia Xserver configuration tool. Set to separate desktops.

Would love to get this solved as it limits usability of both versions of KDE compwiz, has some quirks... would like to get back to kwin.

Comment 1 Jonas Vejlin 2008-07-29 16:16:23 UTC

I can confirm this on debain sid/experimental. 2 screen works perfecly with kde 3 but not with kde 4.0.98. It seems like that X is started on both screens but only one of the X have a running kde 4 seesion, but I am not an expert. Though at first that it was some sittings with my computer so I reveded back to kde3. I am also using nvidia tool to change the settings and the settings works in kde 3 (had the xorg.conf saved) but not in kde 4

Comment 2 Jens Mohr 2008-08-06 20:52:11 UTC

I have the sam problem! my config is with two seperat screens on Fedora 9. Gnome works perfectly with two screens but with KDE4 i have one screen with KDE and one screen black screen with only the cursor (x). I don't use Xinerama (Option         "Xinerama" "0"). My video card is an nvidia (nVidia Corporation NV43 [GeForce 6600] (rev a2)).

Comment 3 Jonas Vejlin 2008-08-06 22:55:45 UTC

I have retested with kde 4.1.0 with the same result (Debian sid/experimental). Still the same symtom. My settings are the same for both 3.5 and 4.1 and kde 3.5 works perfect with 2 screen

Comment 4 Jonas Vejlin 2008-08-21 08:58:53 UTC

It seems that this bug is only present with nvidia's cards ;(

Comment 5 salrio74 2008-09-28 16:20:21 UTC

I have de same problem in kde 4.1.1 in ubuntu. Disabling desktop effect I can execute konqueror and other apps in de second x server, but no windows decoration.

I have a nvida graphic card.

Comment 6 Marco Frailis 2008-11-04 12:18:08 UTC

I have the same problem with kubuntu 8.10 intrepid (release version). I have the nvidia drivers  version 177 and the desktop effects disabled.

Comment 7 Jonas Vejlin 2008-11-27 18:55:39 UTC

Have someone tried to use duel or triple screen settup with kde 4 and a non nvidia driver?

Comment 8 Jordi Polo 2008-11-28 05:31:24 UTC

moved to kwin

Comment 9 Dario Andres 2008-12-12 01:45:47 UTC

Can anyone still reproduce this bug with recents KDE version? (4.1.3 / 4.2beta1 / 4.2svn)? 
Kephal (a new KDE library for managing screens/monitors) was added in KDE4.2.
Thanks :)

Comment 10 Jonas Vejlin 2008-12-12 07:10:58 UTC

It is still there in kde 4.1.3.

Comment 11 Marco Frailis 2008-12-13 12:20:53 UTC

This bug is still reproducible with KDE 4.2 beta1 and the nvidia drivers 180.11 beta.

Comment 12 lucas 2008-12-14 11:50:13 UTC

Multihead KDE is unmaintained and there you are experiencing quite a few bugs from multiple products (Black screen = Plasma, no decorations = KWin, etc).

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