Description of problem: Using most recent updates gnome shell user theme extension fails to load. Looking glass suggests this is due to incompatible versions between gnome shell and the extension/and or gjs version. No further updates available at this time. Version-Release number of selected component (if applicable): Name : gnome-shell-extensions-common Arch : noarch Version : 3.0.1 Release : 1.f016b9git.fc15 Name : gnome-shell-extensions-user-theme Arch : noarch Version : 3.0.1 Release : 1.f016b9git.fc15 Name : gnome-shell Arch : x86_64 Version : 3.0.0.2 Release : 2.fc15 How reproducible: Load gnome shell, no extensions are loaded.
Thanks for your bug report. The latest version of extensions were built for the 3.0.1 version of GNOME Shell. You should first update gnome-shell and then reload it. The extensions should be so available again.
Anyway I'll fix the package to avoid such a situation in the future.
How can I update gnome-shell, it says there are no updates available? Is there a way to force it to check? Thanks, J
You could try to update your yum metadatas by cleaning them: yum clean all Then try to launch an update of your system.
That appears to have not made any difference: $ yum clean all $ yum update Did little, and trying install gnome-shell still told me it was at the most recent version, 3.0.0.2... Any other ideas? J
Judging from this https://admin.fedoraproject.org/updates/mutter-3.0.1-1.fc15,gnome-shell-3.0.1-2.fc15?_csrf_token=dd2e136147228d82a74f6edda74ffabfb523c070 I'm guessing it hasn't been pushed to release yet? J
(In reply to comment #6) > Judging from this > https://admin.fedoraproject.org/updates/mutter-3.0.1-1.fc15,gnome-shell-3.0.1-2.fc15?_csrf_token=dd2e136147228d82a74f6edda74ffabfb523c070 > I'm guessing it hasn't been pushed to release yet? It seems the package gnome-shell-3.0.1-1.fc15 was retired from updates-testing. Some people who regularly update their F15 have this version of GS installed. The others should wait the availability of gnome-shell-3.0.1-2.fc15.
*** This bug has been marked as a duplicate of bug 708230 ***