Bug 176407 - Only first monitor used on multiple graphic card dual monitor setup
Summary: Only first monitor used on multiple graphic card dual monitor setup
Status: RESOLVED DUPLICATE of bug 167290
Alias: None
Product: kwin
Classification: Plasma
Component: general (show other bugs)
Version: unspecified
Platform: Compiled Sources Linux
: NOR normal
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-11-29 05:45 UTC by Öyvind Saether
Modified: 2008-11-29 05:48 UTC (History)
0 users

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 Öyvind Saether 2008-11-29 05:45:34 UTC
Version:            (using Devel)
OS:                Linux
Installed from:    Compiled sources

KDE 4.1.80.

I have two graphics cards.

00:10.0 VGA compatible controller: nVidia Corporation NV34 [GeForce FX 5200] (rev a1)
01:00.0 VGA compatible controller: nVidia Corporation NV34 [GeForce FX 5200] (rev a1)

Each graphic card has one monitor attached.

(==) Log file: "/var/log/Xorg.0.log", Time: Sat Nov 29 05:24:20 2008
(==) Using config file: "/etc/X11/xorg.conf"
(==) ServerLayout "deadbabecafe.xiando.com Xorg X11 Config"
(**) |-->Screen "AGPCRT" (0)
(**) |   |-->Monitor "Iiyama"
(**) |   |-->Device "nvidiaapgcrt"
(**) |-->Screen "PCI" (1)
(**) |   |-->Monitor "tv"
(**) |   |-->Device "nvidiapci"
(**) |-->Input Device "Mouse0"
(**) |-->Input Device "Keyboard0"

KDE4/Kwin only handles the first (AGP-attached) monitor and completely ignores the second display. No window manager starts there (I can put things there with "DISPLAY=:0.1 aterm" for example, but can't move/resize/anything the windows since there is no WM), no desktop is displayed, no nothing. The cursor turns into the X (where X is started and nothing is running) when I move the cursor to this monitor (actually a TV).

This setup works flawlessly (and has for years) with KDE 3.x, xfce4, fluxbox, etc. It's a kwin/KDE problem.
Comment 1 lucas 2008-11-29 05:48:01 UTC

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