After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 659917 - text labels on window overlay disappear
text labels on window overlay disappear
Status: RESOLVED DUPLICATE of bug 659835
Product: gnome-shell
Classification: Core
Component: st
3.1.x
Other Linux
: Normal normal
: ---
Assigned To: gnome-shell-maint
gnome-shell-maint
Depends on:
Blocks:
 
 
Reported: 2011-09-23 07:09 UTC by darkxst
Modified: 2011-10-24 19:16 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description darkxst 2011-09-23 07:09:34 UTC
I have been having issues with the text labels disappearing on the window overlay view. Restarting the shell fixes it for sometime, however it will re-occur sometime within the next hour to day.
Comment 1 darkxst 2011-09-25 23:14:36 UTC
Below is the error that occurs each time I open windowoverlay, once the text labels have stopped showing up.


"'
    JS ERROR: !!!   Error calling onComplete
    JS ERROR: !!!     message = '"Error invoking GConf.get_string: Configuration server couldn't be contacted: D-BUS error: Method "LookupExtended" with signature "ssb" on interface "org.gnome.GConf.Database" doesn't exist
"'
    JS ERROR: !!!     lineNumber = '0'
    JS ERROR: !!!     fileName = '"gjs_throw"'
    JS ERROR: !!!     stack = '"("Error invoking GConf.get_string: Configuration server couldn't be contacted: D-BUS error: Method \"LookupExtended\" with signature \"ssb\" on interface \"org.gnome.GConf.Database\" doesn't exist\n")@gjs_throw:0
(2151,707,391.3333333333333,283.2556719022688)@/usr/share/gnome-shell/js/ui/workspace.js:509
([object Object],[object Object],true)@/usr/share/gnome-shell/js/ui/workspace.js:1075
()@/usr/share/gnome-shell/js/ui/workspace.js:1032
()@/usr/share/gnome-shell/js/ui/tweener.js:108
_callOnFunction((function () {oldHandler.apply(eventScope, oldParams);handler(target);}),"onComplete",(void 0),[object _private_Clutter_Group],(void 0))@/usr/share/gjs-1.0/tweener/tweener.js:202
_updateTweenByIndex(0)@/usr/share/gjs-1.0/tweener/tweener.js:332
_updateTweens()@/usr/share/gjs-1.0/tweener/tweener.js:344
_onEnterFrame([object Object])@/usr/share/gjs-1.0/tweener/tweener.js:359
_emit("prepare-frame")@/usr/share/gjs-1.0/signals.js:124
(263)@/usr/share/gnome-shell/js/ui/tweener.js:244
([object _private_Clutter_Timeline],263)@/usr/share/gnome-shell/js/ui/tweener.js:220
"'
Comment 2 Florian Müllner 2011-09-26 11:26:16 UTC
(In reply to comment #1)
> "'
>     JS ERROR: !!!   Error calling onComplete
>     JS ERROR: !!!     message = '"Error invoking GConf.get_string:
> Configuration server couldn't be contacted: D-BUS error: Method
> "LookupExtended" with signature "ssb" on interface "org.gnome.GConf.Database"
> doesn't exist

Apparently your running gconf daemon is using a different IPC method than the libgconf version used by gnome-shell.

If "ldd /usr/libexec/gconfd-2 | grep -i dbus" shows any output, add the following to your .jhbuildrc-custom:

module_autogenargs['gconf']='--disable-orbit'
Comment 3 darkxst 2011-09-27 09:09:21 UTC
So I am not sure about the build options (I am using a pre-built package from Ubuntu 11.10), however just to be clear, this works fine at the start of the session (or after restarting gnome-shell). At some time later (can be anything from 1hr to 12hr's) it appears that the connection to the gconfd server crashes out.

As far as I can tell this only affects the window overlay. The key in question '/desktop/gnome/shell/windows/button_layout' can still be accessed if I use gconf via gjs. Also the button layout on the windows in normal mode is still fine.

It seems a reasonable workaround could be to catch the exception, and then assume a 'default' setting for button_layout. Except that doesn't help the real issue of why is the connection to gconfs crashing out in the first place.
Comment 4 Fabien Tassin 2011-10-24 19:13:47 UTC
I can reproduce this bug, also on Ubuntu, but i guess it's the same on Debian.

I traced it down to the dpkg "triggers" of the "gconf2" post-install hooks.
In a nutshell, when there's something new in /usr/share/GConf/gsettings/,
dpkg ends up doing a kill -HUP $(pidof gconfd-2).
Comment 5 Jasper St. Pierre (not reading bugmail) 2011-10-24 19:16:42 UTC
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.

Righto, then.

*** This bug has been marked as a duplicate of bug 659835 ***