Created attachment 864149 [details] where is the oxygen theme? Description of problem: After today's update (17. February 2014). The KDE style is suddenly messed up (very ugly) and moving windows creates tearing (VSync issues). It seems like the oxygen widget style is suddenly missing, even though yum says it's installed. Version-Release number of selected component (if applicable): KDE Development Platform: 4.11.5 How reproducible: Permanent. Steps to Reproduce: 1. Update your system. Actual results: Everything looks ugly. Expected results: Everything should continue look as it did before. Additional info: Composite still works (nvidia drivers). How is it possible that composite works and VSync doesn't? I rebooted: did not help. Turning composite off and on again helps for the VSync problems but not even forcing kde-style-oxygen to be reinstalled helps to cure the extreme ugliness of the widget style. What is really absurd is, that Gtk applications (e.g. Gimp) still use the oxygen style!
I now installed QtCurve and use Ozone, which is less horrible than all the other options but still ugly. What happened to Oxygen?
And now the plasma desktop shell is as crashy as it was under Fedora 16. I think I used QtCurve there as well. I'm not sure. I want my oxygen again. :(
Kevin Kofler told me in IRC to rename/delete .config/Trolltech.conf and it fixed the style problems. The VSync issues remain. Restarting composite seem to fix it only sometimes.
The Trolltech.conf issue is already filed as bug #1030534, with the workaround being what I gave you, so let's focus on the VSync issue here. What exact packages were updated in that update? It was clearly not KDE if you're still running 4.11.5.
I guess asking a KDE application what version it is after an update might not be the best idea. yum on the other hand says: $ LANG=C yum info kde-workspace Loaded plugins: auto-update-debuginfo, langpacks, refresh-packagekit Installed Packages Name : kde-workspace Arch : x86_64 Version : 4.11.6 Release : 2.fc20 Size : 33 M Repo : installed From repo : updates Summary : KDE Workspace URL : https://projects.kde.org/projects/kde/kde-workspace And that is what I saw in the updates. (kde workspace; there also was more but I cant remember exactly - is there a way to find out what was installed recently?)
/var/log/yum.log
The last few lines (tell me if you need more): Feb 16 00:21:59 Updated: tortoisehg-2.11-1.fc20.noarch Feb 17 03:52:27 Installed: evtest-1.30-5.fc20.x86_64 Feb 17 14:41:09 Updated: libkworkspace-4.11.6-2.fc20.x86_64 Feb 17 14:41:10 Updated: ksysguard-libs-4.11.6-2.fc20.x86_64 Feb 17 14:41:10 Updated: rpm-libs-4.11.2-1.fc20.x86_64 Feb 17 14:41:11 Updated: rpm-4.11.2-1.fc20.x86_64 Feb 17 14:41:12 Updated: rpm-build-libs-4.11.2-1.fc20.x86_64 Feb 17 14:41:12 Updated: kgreeter-plugins-4.11.6-2.fc20.x86_64 Feb 17 14:41:12 Updated: kde-style-oxygen-4.11.6-2.fc20.x86_64 Feb 17 14:41:13 Updated: ksysguardd-4.11.6-2.fc20.x86_64 Feb 17 14:41:14 Updated: kcm_colors-4.11.6-2.fc20.x86_64 Feb 17 14:41:14 Updated: kde-workspace-libs-4.11.6-2.fc20.x86_64 Feb 17 14:41:17 Updated: kde-workspace-4.11.6-2.fc20.x86_64 Feb 17 14:41:17 Updated: kwin-gles-libs-4.11.6-2.fc20.x86_64 Feb 17 14:41:18 Updated: kde-workspace-devel-4.11.6-2.fc20.x86_64 Feb 17 14:41:18 Updated: plasma-scriptengine-python-4.11.6-2.fc20.x86_64 Feb 17 14:41:19 Updated: ksysguard-4.11.6-2.fc20.x86_64 Feb 17 14:41:19 Updated: kdm-4.11.6-2.fc20.x86_64 Feb 17 14:41:20 Updated: rpm-python-4.11.2-1.fc20.x86_64 Feb 17 14:41:20 Updated: rpm-build-4.11.2-1.fc20.x86_64 Feb 17 14:41:21 Updated: 1:libusb-0.1.5-3.fc20.x86_64 Feb 17 14:41:21 Updated: 1:akmod-nvidia-331.38-6.fc20.4.x86_64 Feb 17 14:41:22 Updated: celt-0.11.3-1.fc20.x86_64 Feb 17 14:41:22 Updated: gupnp-igd-0.2.3-1.fc20.x86_64 Feb 17 16:28:51 Installed: kde-style-oxygen-4.11.6-2.fc20.x86_64 Feb 17 16:31:11 Installed: 1:akmod-nvidia-331.38-6.fc20.4.x86_64 Feb 17 16:43:32 Installed: qtcurve-kde4-1.8.14-3.fc20.x86_64 Feb 17 16:43:32 Installed: kde-style-skulpture-0.2.4-7.fc20.x86_64 Feb 17 16:43:32 Installed: kde-style-phase-4.11.5-1.fc20.x86_64 Feb 17 16:44:18 Erased: kde-style-skulpture-0.2.4-7.fc20.x86_64 Feb 17 16:44:19 Erased: kde-style-phase-4.11.5-1.fc20.x86_64 Feb 17 16:57:31 Installed: gtkmm30-3.10.1-1.fc20.x86_64 Feb 17 16:57:31 Installed: libcanberra-gtk3-0.30-4.fc20.x86_64 Feb 17 16:57:32 Installed: pavucontrol-2.0-4.fc20.x86_64
Note that starting with "Feb 17 16:28:51 Installed: kde-style-oxygen-4.11.6-2.fc20.x86_64" is where I tried to fix the oxygen bugs.
Primary culprit: Feb 17 16:31:11 Installed: 1:akmod-nvidia-331.38-6.fc20.4.x86_64
No this is also *after* the VSync problems happened. I did a "yum reinstall akmod-nvidia" because I feared something in the update did ruin anything with the driver. I just guessed at this point.
Either way, it's best to go upstream with this either nvidia or bugs.kde.org
Ok. (I guess KDE will tell me to update my KDE and try again. So I'll wait for the update to KDE 4.12.x in Fedora.)
> No this is also *after* the VSync problems happened. I did a "yum reinstall > akmod-nvidia" because I feared something in the update did ruin anything with > the driver. I just guessed at this point. But it got updated during the update that broke things for you: Feb 17 14:41:21 Updated: 1:akmod-nvidia-331.38-6.fc20.4.x86_64 > Ok. (I guess KDE will tell me to update my KDE and try again. So I'll wait for > the update to KDE 4.12.x in Fedora.) I don't think 4.12.x is going to change anything, this is clearly not a KDE bug, but a driver regression. It needs to be reported to NVidia. (As for the problem with loading the Oxygen style, see bug #1030534.)