Description of problem: I have two monitors. #1 a 1920x1200 and #2 a 1280x1024. #2 is configured to the right-bottom of #1. On KDE login as desktop is loading I get a bar of corruption/garbage across the bottom of #2 monitor. The height of this bar appears to be the exact difference in height between my two monitors (1200-1024=176). Once I'm logged in the corruption disappears and all is well. If I configure #2 to be right-top there is no corruption. Version-Release number of selected component (if applicable): Fedora 19, up to date How reproducible: every time Steps to Reproduce: 1.Configure a display to the right bottom of main display, that is smaller then main display. 2.login KDE session. 3.See screen corruption as KDE loads. Actual results: corrupt screen Expected results: normal screen Additional info:
What graphics driver?
nouveau. IIRC nvidia proprietary driver had the same issue.
..GeForce 560Ti graphics card
Hi, That's a bug in ksplashx which is not developed for quite a while. It doesn't handle the screen resolution being changed while it's running. I recommend using a QML screen splash if this is an issue for you, it's already fixed in them. Try for example the one named "Fusion" from the "Get New Themes..." menu in settings. All of the Fedora splash screens are using the legacy engine unfortunately. Please report back if using QML splash fixes the issue for you Thank you, Martin
Ok I tried the QML Fusion splash. Bug still exists, though the random garbage is gone. Instead now I can see the properly rendered desktop and windows underneath. I will attach a photo.
Created attachment 832895 [details] screenshot bar at bottom = difference in height between my two monitors..?
Thanks, I thought I had already fixed this upstream, will look in which branches the fix landed after all.
Hi, I just read the code and tested the splashscreen and albeit it doesn't work perfect, it works. There is a slight delay when KScreen kicks in, the screen goes black for a small moment but after that, the splash is again on both screens. If it actually doesn't do even that for you, there's a problem somewhere else, it could be Qt not noticing the desktop layout change or your graphics driver not informing the graphics stack about it... However, I'm not sure how to debug that. Maybe something will come to my mind over time.
Hi, yes the splash is on both screens. But it is offset vertically on monitor 2. Maybe I didn't explain well. Here are two screen shots of monitor configuration (attached). With first configuration (monitor 2 is top-right corner aligned with monitor 1) there is no rendering bug. With the second configuration (monitor 2 is bottom-right of monitor 1) I get the bug. I marked the bug serverity LOW because it isn't a big deal to me.
Created attachment 841323 [details] screenshot working monitor config
Created attachment 841324 [details] screenshot buggy monitor config
Hi John, I know what you're seeing - it's caused by your screen's resolution being changed while the splash is displayed. I understand it's a bit annoying. The first config is fine because it's the default configuration - no change is taking place. Anyway, on my system, it works - in the moment the resolution is changed, the screen goes black for a while but then the splash continues with the new good resolution. It's possible your machine is not fast enough to actually take care of displaying the splash somewhere else... or it's too fast and the splash ends while the change is taking place, who knows. :) I know it's annoying but it will hopefully be fixed when we switch to SDDM and add support for usage of KScreen profiles to it. :) Cheers, Martin
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.
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 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.