crashes gnome-shell in Fedora 17 (gnome 3.4.0)

[jikamens]

I updated my x86_64 desktop to the Fedora 17 prerelease over the weekend. It's got gnome-shell 3.4.0.

Gnome-shell couldn't start up after the upgrade (I got the "Oops! Logout" window), because the old version of the weather extension I had installed was incompatible. Even disabling the extension wasn't good enough; I had to go and totally delete all the files. I suppose that's understandable.

However, even after I pulled the extension source code from the gnome3.4 branch and built and installed that, it still wouldn't work. Gnome-tweak-tool lets me enable the extension, but as soon as I turn it on gnome-shell crashes.

Any suggestions?

[CosminG]

Well I am on archlinux and found that this extension do not work yet with gnome 3.4. I hope will be fixed soon.

[blackjackshellac]

Crashes for me on F16 too, exactly the same behaviour as jikamens described. I suspect I have some crud left over from a previous (gnome shell 3.0) install.

[ferdnyc]

I'm running the latest gnome3.4 branch (with some VERY minor local edits, of a cosmetic nature) on my freshly-upgraded Fedora 17 release system (Gnome Shell 3.4.1), and there don't seem to be any issues with either the extension or the configurator. Hopefully this was a transient issue? Is anyone who reported problems here still experiencing them, or can this be closed?

[CosminG]

Thanks, it's working fine for me now. Could you upload the extension to https://extensions.gnome.org/ ?

[aldafu]

I can confirm the gnome3.4 branch works on F17. But only when installed into /usr, installing into ~/.local will still crash gnome-shell. I opened a different issue for that: #95

[ferdnyc]

@aldafu: I suspect that's due to the GSettings schema not getting installed properly. I build the extension installed into my home directory under $HOME/lib/gnome-shell/extensions/ (using configure --prefix=$HOME), thus the schema is installed and compiled in $HOME/share/glib-2.0/schemas. I can report that using that method works fine and causes no problems for the Shell.

[ferdnyc]

@CosminG: Regarding extensions.gnome.org, see my comments in #50 for why I think we're not quite there yet.

[jikamens]

In F17 current from the Fedora updates and updates-testing repositories, I tried both the 3.4.0 and trunk branches of the extension, and used the generic install instructions in the README file (./autogen.sh --prefix=/usr && make && sudo make install), but gnome-tweak-tool has an orange triangle with an exclamation point next to the switch for the extension, and when I over over the triangle, it says, "Extension does not support shell version", which is 3.4.1 out of updates-testing.

I don't know whether this is because the extension really doesn't support 3.4.1 yet, or because there's some turd left over from a prior installation that's confusing it.

Note, however, that I tried doing "sudo make uninstall", then restarted gnome-shell, and the extension disappeared completely from gnome-tweak-tool, then I did "sudo make install" and restarted gnome-shell again, and the extension came back in gnome-tweak-tool, again greyed out with the orange triangle. So if there is some sort of turd hanging around, it's one that "sudo make uninstall" can't figure out how to get rid of, and yet isn't enough for gnome-tweak-tool to think that the extension is installed.

[blackjackshellac]

I had to manually replace the schema xml file

cp gnome-shell-extension-weather/src/org.gnome.shell.extensions.weather.gschema.xml /usr/local/share/glib-2.0/schemas/

since that file wasn't being properly updated after doing 'sudo make install'. Not sure why. Before that, gsettings and dconf-editor showed different keys and values. It's finally working for me again in F17.

[blackjackshellac]

@jikamens it does indeed seem as if there was some kruft left over from a previous version. I did a diff of the two schemas and they differ markedly, but have the same schema version. One glaring difference was the lack of a woeid section in the old schema. Replacing the old installed version finally allowed this extension to work for me again.