/ / In desperation I blew away ~/.gconf/desktop/gnome/shell and interface with
the user logged out.
/ / That seemed to fix it.
I also got this problem a few minutes ago and found this bug with google and
after reading what Derek wrote I browsed ~/.gconf/desktop/ to find three files
with unusual names:
~/.gconf/desktop/%gconf.xml
~/.gconf/desktop/gnome/%gconf.xml
~/.gconf/desktop/gnome/shell/%gconf.xml
~/.gconf/desktop/gnome/shell/window/%gconf.xml
I removed the '%' prefix, rebooted and it now works like a charm.
The first I did after rebooting and lofing in was to check ~/.gconf/desktop/
again, and none of the four '%'-prefixed files were present. But after opening
Firefox and gedit,
~/.gconf/desktop/%gconf.xml
and
~/.gconf/desktop/gnome/%gconf.xml
had been auto-magically generated.
All files were empty except
~/.gconf/desktop/gnome/shell/window/%gconf.xml
which contained theme settings:
<?xml version="1.0"?>
<gconf>
<entry name="theme" mtime="1319236779" type="string">
<stringvalue>Esco</stringvalue>
</entry>
</gconf>
Maybe the real bug is that somewhere in the binary circus some process
adds a '%'-prefix on gconf files?
Hope this helps.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/844937
Title:
gnome-shell crashed with SIGABRT in g_assertion_message()
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/844937/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
