Created attachment 916665 [details] Skype Window Description of problem: A number of Qt based applications are no longer rendering correctly (see screenshot of Skype). Version-Release number of selected component (if applicable): How reproducible: A number of Qt Applications from 3rd partys show the issue o Google Music Manager o Skype Steps to Reproduce: 1. Load Qt based application 2. No need for step 3 - just admire the awful. 3. Actual results: Windows do not render correctly - widgets aren't drawn and mouse clicks are lost This affects Menus and Main Windows for applications. Expected results: Applications render as expected and handle input Additional info: See screenshots. Happy to debug.
Created attachment 916666 [details] Google Music Manager
This was fine prior to the last set of updates that I applied yesterday - I've tried running the apps from the command line but no debug comes out.
You mention "no longer rendering correctly" so what has changed or when did the problem start? What versions of skype/GMM do you have? I'm not seeing any issues with rendering of skype for me, it could be GPU driver specifics so can you provide the details of your graphics card and appropriate driver versions?
Thanks for the rapid reply Peter. How do I get the driver versions you need? [nick@zeus ~]$ rpm -qa | grep intel xorg-x11-drv-intel-2.21.12-2.fc19.i686 As for the other software: [nick@zeus ~]$ rpm -qa | grep skype skype-4.2.0.11-fc16.i586 [nick@zeus ~]$ rpm -qa | grep musicmanager google-musicmanager-beta-1.0.117.4968-0.i386
As mentioned - this started today on boot (I applied updates yesterday that had been pending and hadn't restarted). The graphics are builtin Intel graphics: 00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller (rev 06)
The last update to mutter was in April, most of the graphics stack around this hasn't changed since before even that so I suspect it's likely a driver change. You might want to test the latest skype (I have skype-4.3.0.37-fc16.i586) too. Can you do "rpm -qa | grep mesa" and also you might want to give the output of the last yum transaction to see if there's anything else that might be causing issues.
Created attachment 916681 [details] transaction log [nick@zeus ~]$ rpm -qa | grep mesa mesa-libwayland-egl-devel-9.2.4-1.20131128.fc19.i686 mesa-libwayland-egl-9.2.4-1.20131128.fc19.i686 mesa-libglapi-9.2.4-1.20131128.fc19.i686 mesa-libGLU-9.0.0-4.fc19.i686 mesa-libGL-9.2.4-1.20131128.fc19.i686 mesa-libGL-devel-9.2.4-1.20131128.fc19.i686 mesa-libxatracker-9.2.4-1.20131128.fc19.i686 mesa-libEGL-devel-9.2.4-1.20131128.fc19.i686 mesa-libEGL-9.2.4-1.20131128.fc19.i686 mesa-libgbm-devel-9.2.4-1.20131128.fc19.i686 mesa-libgbm-9.2.4-1.20131128.fc19.i686 mesa-filesystem-9.2.4-1.20131128.fc19.i686 mesa-dri-drivers-9.2.4-1.20131128.fc19.i686 I had a look at yum history package-list to see if that outlined anything but I'm not sure so I've just attached my log
the BZ above reports this is F-20 but the packages are F-19. Please confirm which?
(In reply to Peter Robinson from comment #8) > the BZ above reports this is F-20 but the packages are F-19. Please confirm > which? Also what kernel are you running? "uname -a; rpm -q kernel"
My mistake - I am on FC19, ticket updated accordingly Did a reinstall of the qt libraries and installed the newest version of Skype (skype.i586 0:4.3.0.37-fc16) and it still has the same issue. As requested: [nick@zeus ~]$ uname -a; rpm -q kernel Linux zeus 3.14.8-100.fc19.i686 #1 SMP Mon Jun 16 22:21:01 UTC 2014 i686 i686 i386 GNU/Linux kernel-3.14.4-100.fc19.i686 kernel-3.14.7-100.fc19.i686 kernel-3.14.8-100.fc19.i686
So it seems the only thing that has really changed is the kernel. I suggest rebooting into one of the older kernels to see if the problem goes away. This isn't a mutter issue
Just tried all previous kernels (well, two of them) and it didn't make a difference. It has to be something in the rendering path (mesa-x11, X11, Mutter/Gnomeshell or Qt). I've applied a few updates without rebooting and this is the first time something has gone wrong like this. I have just installed metacity side by side to see if it's a GL issue but that hasn't made a huge difference (menus seem to work but that could be just showing less artifacts as the apps are still broken otherwise). Can you recommend any other debugging suggestions? Is this at all related to changing the drawing loop I saw mentioned on d-d-l?
> Can you recommend any other debugging suggestions? Is this at all related to > changing the drawing loop I saw mentioned on d-d-l? You're running F-19. The last updates to the rendering stack were: mesa: 28th Nov 13 xorg-x11-server: 13th Nov 13 xorg-x11-drv-intel: 30th Jul 13 cogl: 12th Jan 13 clutter: 9th Dec 13 mutter: 9th Dec 13 qt: 8th Jun 14 So it tells me it's either a kernel issue or possibly something that has changed in QT. You can try "yum downgrade qt" to see if the version prior helps You can try the latest kernel (3.14.11) in updates testing "yum update --enablerepo=updates-testing kernel*" Otherwise I would look at Fedora 20 as F-19 is in stable not really getting updates mode
Looking at BZ https://bugzilla.redhat.com/show_bug.cgi?id=1105422 There was some updates to QT to deal with repaint bugs which could possibly be what's regressing here.
did you test if it was a QT change?
I rolled back Qt as I couldn't see any in @updates but it made no difference. I could only roll back one version but it didn't make any difference sudo yum downgrade qt4 qt qtwebkit.i686 qt-x11.i686 The updated kernel didn't help either - like I said, it feels like a rendering path issue - Qt isn't redrawing/getting dirty events properly.
> The updated kernel didn't help either - like I said, it feels like a > rendering path issue - Qt isn't redrawing/getting dirty events properly. There's lots of things in the rendering path and none of the ones in the mutter path other than the kernel have changed recently in F-19 with the last change being back in April. I'd suggest upgrading to F-20
I've since upgrade to F20 and can confirm the issue is still present. I'd really like to get this resolved as Skype is pretty much a necessity (Google Music Manager less so).
Please update the versions of all of the above, any xorg config snippets. I'm not seeing any issues with rendering of skype
Created attachment 919852 [details] Fresh reinstall of qt-x11 and skype Attached a pic of the fresh install attempting to use Skype for first time under F20.
Hey Peter - what do you mean? I can give you the result of any commands and the logs of any requested files just let me know.
Created attachment 919855 [details] xorg-log-f20
Created attachment 919856 [details] lspci -nn output f20
I've read through the comments, dont believe this has been answered yet... Can anyone verify if this is gnome3/mutter specific or not (Ie, does this same phenomenon occur outside of a gnome session) ?
Reassigning to Qt component.
To me, these screenshots look clearly like a graphics driver bug.
@kevin - why would it only be affecting certain Qt applications? I noted in IRC that this doesn't affect HipChat, Google Chrome but *does* affect Google Music Manager and skype which is odd. No Gtk applications seem to be affected - is there any output that can be used to help debug this? It happened after a reboot and applying a number of updates and I have no non-standard customisations to themes/Gtk/Xorg.
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.