Created attachment 713323 [details] Snapshot of my monitor showing the bug Description of problem: I have a dual-monitor setup here with separated screens - my FC18 desktop is attached both to a Dell Monitor (1650x1080x24, DVI, screen 0) and a Samsung PDP Monitor (1280x720x24, HDMI, screen 1). I'm running FC18 with the NVidia proprietary drivers (313.18) and had no problems whatsoever. After the latest updates for kde-workspace, the KDE screensaver will present images for both screens only on screen 0, with the images that should appear on screen 1 over screen 0. This will only happen when the screen is actually locked; when testing the screen saver on the screen locker option of systemsettings, it does just appear on screen 0. Also, when unlocking the screen, the unlock dialog will always appear on screen 0 (Dell), decentered relative to Dell monitor but actually centered relative to Samsung PDP. Sometimes I can just enter the password to unlock the screen; sometimes I must move the cursor to the location of screen 1 to unlock it. The unlock dialog never shows up on screen 1. Finally, the screen saver does not appear on screen 1; it is displayed only on the Dell monitor, showing the content of the Samsung PDP over it. The Samsung display will always show the default background of FC18. I've also tried locking the screen with a fresh ~/.kde4 profile directory, but the problem remains the same. Opening other X applications on screen 1 (such as DISPLAY=:0.1 xterm) works fine. Version-Release number of selected component (if applicable): 4.10.1-2fc18 x86_64 (Fri Mar 15 14:22:46 2013, Key ID ff01125cde7f38bd) How reproducible: always Steps to Reproduce: 1. Lock screen manually (or wait for timeout) 2. The screensaver will appear only on screen 0 twice, but not on screen 1 3. Move the mouse or press a key to unlock password Actual results: the password dialog appears, but decentered relative to the Dell monitor (screen 0) but centered relative to the Samsung PDP (screen 1). It's not always possible to unlock the screen, unless I move the cursor to the location of screen 1 (where the screen saver does not appear). Expected results: the screen saver should appear on both screens (0 and 1) instead of showing both screens combined on screen 0. And the focus should always stay on screen 0 (which is the one I use most of the time) Additional info: behavior appeared after updating kde-workspace to latest release. I'm attaching pictures since I couldn't take snap shots of the problem within the computer.
Created attachment 713324 [details] Snapshot of my monitor showing the decentered password dialog
Created attachment 713325 [details] My xorg.conf X11 configuration file
> I'm running FC18 with the NVidia proprietary drivers (313.18) Can you reproduce this with Nouveau or some other driver we ship and support?
Haven't tried Nouveau (yet). But AFAIK Nouveau's support for dual screen configurations is still experimental - contrary to NVidia's driver, which has supported it well in all releases I've tried. I'll give nouveau a try and see will see if the bug will still appear. But anyway, the version of my NVidia driver has not changed; kde-workspace has changed with the latest update, and after this update it's been broken to me.
I'm fiddling with nouveau for the last 2 hours, but up to now it's a no-go. I've set up dual screen support as per instructions available on http://en.gentoo-wiki.com/wiki/X.Org/Dual_Monitors#Single.2C_Multi-headed_Graphics_Card. When my second screen is about to be activated, I get this on Xorg.0.log: [ 5250.797] (II) Module "dri" already built-in [ 5250.797] (II) NOUVEAU(1): Loaded DRI module [ 5250.797] (EE) NOUVEAU(1): [drm] failed to set drm interface version. [ 5250.797] (EE) NOUVEAU(1): [drm] error opening the drm [ 5250.797] (EE) NOUVEAU(1): 819: [ 5250.797] (II) UnloadModule: "nouveau" [ 5250.797] (--) Depth 24 pixmap format is 32 bpp And then I will never hear again from Screen 1: [pfessel@wotan ~]$ DISPLAY=:0.1 xterm xterm: Xt error: Can't open display: :0.1 [pfessel@wotan ~]$ I've managed to get the dual-monitor setting working, but only as one virtual desktop with one screen comprising both monitors, which is not the setting I have with the NVidia drivers. My graphics board is a GT-620 which is based upon NVc1 NVidia chipset, which seems not to be fully supported yet. Unfortunately, the "Nouveau features matrix" is missing from Nouveau's wiki. :(
Created attachment 713556 [details] xorg.conf using Nouveau drivers
Created attachment 713557 [details] Xorg logfile for Nouveau
It's been ages since changing xorg.conf was last sufficient to switch between Free and proprietary drivers. You need to completely uninstall the NVidia driver to use Nouveau, in particular, remove its blacklisting of the Nouveau kernel module. In addition, modern drivers such as Nouveau work best with no xorg.conf at all. If the autodetected screen configuration does not suit you, use KDE's System Settings to reconfigure it using XRandR. (And if the default krandr does not work, try kscreen, it will become the default in Fedora 19 because it works better.)
(In reply to comment #8) > It's been ages since changing xorg.conf was last sufficient to switch > between Free and proprietary drivers. You need to completely uninstall the > NVidia driver to use Nouveau, in particular, remove its blacklisting of the > Nouveau kernel module. Been there, done that. I'm running the console on the default resolution of my monitor (1680x1050). Also: $ lsmod | grep nou nouveau 941736 3 mxm_wmi 12865 1 nouveau video 18991 1 nouveau i2c_algo_bit 13257 1 nouveau drm_kms_helper 46708 1 nouveau ttm 79629 1 nouveau drm 264680 5 ttm,drm_kms_helper,nouveau wmi 18697 2 mxm_wmi,nouveau i2c_core 38353 6 drm,i2c_piix4,drm_kms_helper,i2c_algo_bit,nouveau,videodev > In addition, modern drivers such as Nouveau work best with no xorg.conf at > all. If the autodetected screen configuration does not suit you, use KDE's > System Settings to reconfigure it using XRandR. (And if the default krandr > does not work, try kscreen, it will become the default in Fedora 19 because > it works better.) I'll give it a try, but I'm not holding my breath. From http://nouveau.freedesktop.org/wiki/MultiMonitorDesktop: > Multi-monitor desktop with Nouveau > > If you have a single graphics card (GPU) with multiple heads, it should all > just work for you with RandR 1.2 and offer full (whatever is implemented) > graphics acceleration. If you really want multiple SCREENs on a dual-head > card, there exists the experimental configuration option ZaphodHeads. On the other hand, why just don't check what has changed on KDE for 4.10 in terms of the kscreensaver code that could hit the bug? I'm really doubting that the behavior is linked to NVidia proprietary drivers - after all, the problem occurs with any screen saver I choose under KDE, not only those using OpenGL.
I've just tried using kscreen and it just doesn't do what I want to do: drive two different SCREENS (:0.0 - LCD monitor and :0.1 - plasma display panel). It always creates a unique screen (:0) comprising the workspace of the two monitors a la NVidia's TwinView. I still don't have :0.0 and :0.1 available.
Also see bug #901593.
RandR extension does not support independent screens in the sense of X11 display (HOST:DISPLAY.SCREEN).
The problem is definitely related to KDE. I've checked xfce and its screensaver (xscreensaver) works exactly as it should, one screensaver for each X screen. Also, using NVidia drivers from rpmfusion didn't change anything in regards either of xfce or KDE. Xfce's screensaver always works correctly, while KDE's does not.
The bug is also confirmed on the Intel chipset, when using a dual screen configuration and thus the problem occurs regardless of the graphic card driver in use. I'm attaching the xorg.conf for this Intel machine (a HP Pavillion 2060BR notebook) and the Xorg.0.log as well.
Created attachment 714168 [details] xorg.conf for Intel i965 chipset
Created attachment 714171 [details] Xorg.0.log for HP Pavillon 2060BR notebook (i5)
(In reply to comment #3) > > I'm running FC18 with the NVidia proprietary drivers (313.18) > > Can you reproduce this with Nouveau or some other driver we ship and support? I managed to reproduce it on an i5 notebook with an i965 (Intel) chipset with the same version of kde-workspace as reported originally. See comment #14 and attachments #714168/#714171.
This message is a reminder that Fedora 18 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 18. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '18'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 18's end of life. Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 18 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior to Fedora 18's end of life. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
This message is a notice that Fedora 19 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 19. It is Fedora's policy to close all bug reports from releases that are no longer maintained. Approximately 4 (four) weeks from now this bug will be closed as EOL if it remains open with a Fedora 'version' of '19'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 19 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '20'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 20 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.