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 700473 - gnome-base/gnome-control-center-3.6.3 segfaults at libclutter-1.0.so
gnome-base/gnome-control-center-3.6.3 segfaults at libclutter-1.0.so
Status: RESOLVED DUPLICATE of bug 692707
Product: clutter
Classification: Platform
Component: general
unspecified
Other Linux
: Normal normal
: ---
Assigned To: clutter-maint
clutter-maint
Depends on:
Blocks:
 
 
Reported: 2013-05-16 16:56 UTC by Justin
Modified: 2013-05-17 10:46 UTC
See Also:
GNOME target: ---
GNOME version: 3.5/3.6


Attachments
Full abrt report (91.16 KB, text/plain)
2013-05-16 16:56 UTC, Justin
Details

Description Justin 2013-05-16 16:56:25 UTC
Created attachment 244434 [details]
Full abrt report

Just starting it makes it segfault

Program received signal SIGSEGV, Segmentation fault.
translate_valuator_class (class=0x6df570, device=0x4c6870, xdisplay=0x488a90) at ./x11/clutter-device-manager-xi2.c:101
101	./x11/clutter-device-manager-xi2.c: No such file or directory.
(gdb) bt
  • #0 translate_valuator_class
    at ./x11/clutter-device-manager-xi2.c line 101
  • #1 translate_device_classes
    at ./x11/clutter-device-manager-xi2.c line 154
  • #2 create_device
    at ./x11/clutter-device-manager-xi2.c line 295
  • #3 add_device
    at ./x11/clutter-device-manager-xi2.c line 315
  • #4 clutter_device_manager_xi2_constructed
    at ./x11/clutter-device-manager-xi2.c line 1375
  • #5 g_object_newv
    at gobject.c line 1747
  • #6 g_object_new_valist
    at gobject.c line 1836
  • #7 g_object_new
    at gobject.c line 1551
  • #8 clutter_backend_x11_create_device_manager
    at ./x11/clutter-backend-x11.c line 254
  • #9 _clutter_backend_x11_events_init
    at ./x11/clutter-backend-x11.c line 502
  • #10 clutter_init_real
    at ./clutter-main.c line 1632
  • #11 post_parse_hook
    at ./clutter-main.c line 1818
  • #12 g_option_context_parse
    at goption.c line 2001
  • #13 clutter_parse_args
    at ./clutter-main.c line 2054
  • #14 clutter_init
    at ./clutter-main.c line 2116
  • #15 cheese_gtk_init
    at libcheese/cheese-gtk.c line 58
  • #16 g_io_module_load
    at um-user-module.c line 38
  • #17 g_io_module_load_module
    at giomodule.c line 307
  • #18 g_type_module_use
    at gtypemodule.c line 256
  • #19 g_io_modules_load_all_in_directory_with_scope
    at giomodule.c line 589
  • #20 g_io_modules_load_all_in_directory
    at giomodule.c line 628
  • #21 load_panel_plugins
    at gnome-control-center.c line 882
  • #22 gnome_control_center_init
    at gnome-control-center.c line 1391
  • #23 g_type_create_instance
    at gtype.c line 1890
  • #24 g_object_constructor
    at gobject.c line 1855
  • #25 g_object_newv
    at gobject.c line 1638
  • #26 g_object_new
    at gobject.c line 1548
  • #27 gnome_control_center_new
    at gnome-control-center.c line 1408
  • #28 main
    at control-center.c line 250

Comment 1 Justin 2013-05-16 16:57:22 UTC
clutter version 1.12.2 was used.
Comment 2 Emmanuele Bassi (:ebassi) 2013-05-17 10:23:28 UTC
given the stack trace, I think this is a dupe of bug 692707 — which has been fixed in Git for Clutter 1.14 (current stable); the fix has been backported to 1.12, but it has not been released in a tarball.

*** This bug has been marked as a duplicate of bug 692707 ***
Comment 3 Justin 2013-05-17 10:41:18 UTC
(In reply to comment #2)
> given the stack trace, I think this is a dupe of bug 692707 — which has been
> fixed in Git for Clutter 1.14 (current stable); the fix has been backported to
> 1.12, but it has not been released in a tarball.

Could you please point me to the backport commit? I would like to fix it in our package.
Currently 1.14 is not released for general use on Gentoo, as out gnome maintainers still optimizing the upgrade path to 3.8.
Comment 4 Justin 2013-05-17 10:42:12 UTC
I found the commit. It was in the other bug.