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 662805 - Gnome Shell killed by Signal frequenly
Gnome Shell killed by Signal frequenly
Status: RESOLVED DUPLICATE of bug 661323
Product: gnome-shell
Classification: Core
Component: general
3.2.x
Other Linux
: Normal normal
: ---
Assigned To: gnome-shell-maint
gnome-shell-maint
Depends on:
Blocks:
 
 
Reported: 2011-10-26 21:07 UTC by Sven
Modified: 2011-10-31 17:51 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
my .xsession-errors (12.75 KB, text/plain)
2011-10-26 21:08 UTC, Sven 		Details

Description Sven 2011-10-26 21:07:54 UTC 
Since 3.2.1, Gnome Shell is (according to /var/log/messages) "killed by signal" every 30 minutes or so without an apparent reasons. I use an up2date archlinux (x64) and it seems that I'm not the only one with this problem:
https://bbs.archlinux.org/viewtopic.php?id=128150

(added .xsession-errors as attachment, let me know if you need more information)
Comment 1 Sven 2011-10-26 21:08:51 UTC 
Created attachment 200064 [details]
my .xsession-errors
Comment 2 Jasper St. Pierre (not reading bugmail) 2011-10-26 21:23:19 UTC 
Do you have any extensions installed?
Comment 3 Sven 2011-10-27 06:06:57 UTC 
I had some extensions installed, but since this problem appeared I disabled all but Pidgin IM Integration (https://github.com/kagesenshi/gnome-shell-extensions-pidgin) and the Places Status Indicator Extensions.
I disabled them both now, to see if they're causing the errors.
Comment 4 Ben Scholzen 2011-10-27 21:19:44 UTC 
I'm also affected by this bug in Gnome 3.2. There is also a bug report in Ubuntu Launchpad about it together with a stack trace. As far as I can see, it's the same source problem:

https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/867645
Comment 5 Milan Bouchet-Valat 2011-10-28 09:07:17 UTC 
The trace from the bug cited above is a failed assertion in gjs_object_instance_constructor() at gi/object.c:668:
"assertion failed: (unthreadsafe_template_for_constructor.info == NULL || strcmp(g_base_info_get_name( (GIBaseInfo*) priv->info), g_base_info_get_name( (GIBaseInfo*) unthreadsafe_template_for_construct"...

+ Trace 228928

  • #0 __GI_raise
    at ../nptl/sysdeps/unix/sysv/linux/raise.c line 64
  • #1 __GI_abort
    at abort.c line 92
  • #2 g_assertion_message
  • #3 g_assertion_message_expr
    at /build/buildd/glib2.0-2.30.0/./glib/gtestutils.c line 1436
  • #4 gjs_object_instance_constructor
    at gi/object.c line 668
  • #5 CallJSNative
    at jscntxtinlines.h line 701
  • #6 CallJSNativeConstructor
    at jscntxtinlines.h line 720
  • #7 js::InvokeConstructor
    at jsinterp.cpp line 1244
  • #8 js::Interpret
    at jsinterp.cpp line 4686
  • #9 js::RunScript
    at jsinterp.cpp line 653
  • #10 js::Invoke
    at jsinterp.cpp line 740
  • #11 js::ExternalInvoke
    at jsinterp.cpp line 863
  • #12 JS_CallFunctionValue
    at jsapi.cpp line 5145
  • #13 gjs_call_function_value
    at gjs/jsapi-util.c line 1203
  • #14 invoke_js_from_dbus
    at modules/dbus-exports.c line 324
  • #15 on_message
    at modules/dbus-exports.c line 1636
  • #16 dbus_connection_dispatch
    at ../../dbus/dbus-connection.c line 4603
  • #17 message_queue_dispatch
    at dbus-gmain.c line 90
  • #18 g_main_dispatch
    at /build/buildd/glib2.0-2.30.0/./glib/gmain.c line 2441
  • #19 g_main_context_dispatch
    at /build/buildd/glib2.0-2.30.0/./glib/gmain.c line 3011
  • #20 g_main_context_iterate
    at /build/buildd/glib2.0-2.30.0/./glib/gmain.c line 3089
  • #21 g_main_loop_run
    at /build/buildd/glib2.0-2.30.0/./glib/gmain.c line 3297
  • #22 meta_run
    at core/main.c line 555
  • #23 main
    at main.c line 571 






Comment 6


Tsu Jan





          2011-10-31 01:13:51 UTC
        



I also experienced those nasty crashes every 20 minutes with Gnome Shell 3.2.1 on Debian before downgrading to 3.0.2. I used no extension. The most pertinent lines I found in .xsession-errors were these:

....
(gnome-shell:24033): Clutter-WARNING **: Attempting to add actor of type 'ShellGenericContainer' to a container of type 'StBoxLayout', but the actor has already a parent of type 'StBoxLayout'.

(gnome-shell:24033): St-WARNING **: Actor of type 'ShellGenericContainer' is not a child of the StBoxLayout container
....






Comment 7


Jasper St. Pierre (not reading bugmail)





          2011-10-31 15:21:45 UTC
        



"Killed by signal" just means that GNOME Shell crashed. This specific backtrace is a duplicate of bug #661323.

Tsu Jan, can you file a new bug?

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






Comment 8


Tsu Jan





          2011-10-31 17:51:13 UTC
        



> Tsu Jan, can you file a new bug?

I'm not sure that what I encountered is really different from bug #661323, although I don't remember "ERROR:gi/object.c:671:gjs_object_instance_constructor: assertion failed" in xsession-error. Unfortunately I have to stick with GNOME-Shell 3.0.2 as I need a stable desktop for now.