http://bugzilla.opensuse.org/show_bug.cgi?id=1142258
http://bugzilla.opensuse.org/show_bug.cgi?id=1142258#c20
--- Comment #20 from Hadrien Grasland ---
When looking in the right place, the ~/.xsession-errors logs do contain a few
interesting differences. Here's a quick walkthrough of those.
----
+Cjs-Message: 20:54:22.829: JS LOG: GSettings key not found. schema:
org.cinnamon, key: panel-zone-icon-sizes
...
+Cjs-Message: 20:54:23.134: JS LOG: [LookingGlass/error] [Panel 1] Unable to
find zone configuration
...
+Cjs-Message: 20:54:23.231: JS LOG: GSettings key not found. schema:
org.cinnamon.theme, key: symbolic-relative-size
----
There's a bunch of messages which sound like cinnamon does not manage to load
its configuration. Perhaps the configuration migration logic for 3.8.9 -> 4.2.1
is borked? If that is the case, then this could be easily resolved by throwing
the old config away and letting cinnamon create a new one. I'll try with a new
user account later on...
----
+Cjs-Message: 20:54:23.344: JS LOG: [LookingGlass/info] Upgrading settings for
power@cinnamon.org
+Cjs-Message: 20:54:23.344: JS LOG: [LookingGlass/info] Settings successfully
upgraded for power@cinnamon.org
...
+Cjs-Message: 20:54:23.504: JS LOG: [LookingGlass/info] Upgrading settings for
window-list@cinnamon.org
+Cjs-Message: 20:54:23.505: JS LOG: [LookingGlass/info] Settings successfully
upgraded for window-list@cinnamon.org
----
...at other times, though, cinnamon seems to be auto-updating its old
configuration just fine. But then something happens:
----
+Cjs-Message: 20:54:23.675: JS LOG: [LookingGlass/info] Upgrading settings for
menu@cinnamon.org
+Cjs-Message: 20:54:23.675: JS LOG: [LookingGlass/info] Settings successfully
upgraded for menu@cinnamon.org
+Cjs-Message: 20:54:23.695: JS LOG: GSettings key not found. schema:
org.cinnamon, key: app-menu-icon-name
+Cjs-Message: 20:54:23.695: JS LOG: [LookingGlass/warning] Could not load icon
file "/usr/share/cinnamon/theme/menu-symbolic.svg" for menu button
+Cjs-Message: 20:54:23.695: JS LOG: GSettings key not found. schema:
org.cinnamon, key: app-menu-icon-name
+Cjs-Message: 20:54:23.695: JS LOG: GSettings key not found. schema:
org.cinnamon, key: app-menu-label
+Cjs-Message: 20:54:23.696: JS LOG: [LookingGlass/error]
+[menu@cinnamon.org]: Argument 'text' (type utf8) may not be null
+[menu@cinnamon.org]: Failed to evaluate 'main' function on applet:
menu@cinnamon.org/1
+Cjs-Message: 20:54:23.696: JS LOG: [LookingGlass/trace]
<----------------/Gio.js:71:26
+set_applet_label@/usr/share/cinnamon/js/ui/applet.js:879:9
+_updateIconAndLabel@/usr/share/cinnamon/applets/menu@cinnamon.org/applet.js:1235:17
+CinnamonMenuApplet@/usr/share/cinnamon/applets/menu@cinnamon.org/applet.js:926:9
+main@/usr/share/cinnamon/applets/menu@cinnamon.org/applet.js:2867:12
+createApplet@/usr/share/cinnamon/js/ui/appletManager.js:581:18
+addAppletToPanels@/usr/share/cinnamon/js/ui/appletManager.js:356:22
+finishExtensionLoad@/usr/share/cinnamon/js/ui/appletManager.js:95:14
+Extension.prototype._init/<@/usr/share/cinnamon/js/ui/extension.js:277:17
---------------->
...
+Cjs-Message: 20:54:23.696: JS LOG: [LookingGlass/error]
+[menu@cinnamon.org]: Applet menu@cinnamon.org: Could not create applet object.
+[menu@cinnamon.org]: Error importing applet.js from menu@cinnamon.org
+Cjs-Message: 20:54:23.696: JS LOG: [LookingGlass/trace]
+<----------------
+Extension.prototype._init/<@/usr/share/cinnamon/js/ui/extension.js:278:23
+---------------->
----
Here, it looks like cinnamon fails so hard at loading its own configuration
that it ends up failing to read the menu applet's label. This leads it to pass
a NULL to the menu applet's constructor, leading it to crash. Ergo, no menu.
TL;DR: So far, this sounds like a configuration migration problem. I'll try
with a new user account next to see if it works properly there.
If so, then... well, we may need to tell cinnamon users to flush their
configuration when upgrading. Thankfully, there is a built-in tool to do that:
panel right click -> Troubleshooting -> Restore default parameters.
--
You are receiving this mail because:
You are on the CC list for the bug.