Bug 670598 – gnome-control-center hits "assertion failed: (device->priv->styli)" in gsd_wacom_device_set_current_stylus()

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 670598 - gnome-control-center hits "assertion failed: (device->priv->styli)" in gsd_wacom_device_set_current_stylus()


Summary:	gnome-control-center hits "assertion failed: (device->priv->styli)" in gsd_wa...


Status:	RESOLVED DUPLICATE of bug 670461

Product:	gnome-control-center
Classification:	Core
Component:	Wacom
Version:	3.3.x
Hardware:	Other Linux

Importance:	Normal normal
Target Milestone:	---
Assigned To:	Peter Hutterer
QA Contact:	Control-Center Maintainers

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2012-02-22 11:27 UTC by Sebastien Bacher
Modified:	2012-02-22 19:39 UTC

See Also:
GNOME target:	---
GNOME version:	---

Description Sebastien Bacher 2012-02-22 11:27:07 UTC

The bug has been opened on https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/938549

Version: 3.3.90

Description:
"i may have clicked the wacom button with a bamboo wacom connected."

Stacktrace:
"#0  0x00007fea59a2d475 in __GI_raise (sig=<optimized out>) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64
        resultvar = 0
        pid = <optimized out>
        selftid = 2197

+ Trace 229713

#1 __GI_abort
at abort.c line 91
#2 g_assertion_message
#3 g_assertion_message_expr
at /build/buildd/glib2.0-2.31.18/./glib/gtestutils.c line 1871
#4 gsd_wacom_device_set_current_stylus
at gsd-wacom-device.c line 1416
#5 setup_property_notify
at gsd-wacom-device.c line 411
#6 gsd_wacom_device_constructor
at gsd-wacom-device.c line 1167
#7 g_object_newv
at /build/buildd/glib2.0-2.31.18/./gobject/gobject.c line 1713
#8 g_object_new_valist
at /build/buildd/glib2.0-2.31.18/./gobject/gobject.c line 1830
#9 g_object_new
at /build/buildd/glib2.0-2.31.18/./gobject/gobject.c line 1545
#10 gsd_wacom_device_new
at gsd-wacom-device.c line 1289
#11 add_known_device
at cc-wacom-panel.c line 252
#12 device_added_cb
at cc-wacom-panel.c line 277
#13 g_closure_invoke
at /build/buildd/glib2.0-2.31.18/./gobject/gclosure.c line 774
#14 signal_emit_unlocked_R
at /build/buildd/glib2.0-2.31.18/./gobject/gsignal.c line 3302
#15 g_signal_emit_valist
at /build/buildd/glib2.0-2.31.18/./gobject/gsignal.c line 3033
#16 g_signal_emit_by_name
at /build/buildd/glib2.0-2.31.18/./gobject/gsignal.c line 3127
#17 add_device
at /build/buildd/gtk+3.0-3.3.16/./gdk/x11/gdkdevicemanager-xi2.c line 334
#18 handle_hierarchy_changed
at /build/buildd/gtk+3.0-3.3.16/./gdk/x11/gdkdevicemanager-xi2.c line 594
#19 gdk_x11_device_manager_xi2_translate_event
at /build/buildd/gtk+3.0-3.3.16/./gdk/x11/gdkdevicemanager-xi2.c line 984
#20 gdk_x11_device_manager_xi2_translate_event
at /build/buildd/gtk+3.0-3.3.16/./gdk/x11/gdkdevicemanager-xi2.c line 945
#21 _gdk_x11_event_translator_translate
at /build/buildd/gtk+3.0-3.3.16/./gdk/x11/gdkeventtranslator.c line 53
#22 gdk_event_source_translate_event
at /build/buildd/gtk+3.0-3.3.16/./gdk/x11/gdkeventsource.c line 242
#23 _gdk_x11_display_queue_events
at /build/buildd/gtk+3.0-3.3.16/./gdk/x11/gdkeventsource.c line 334
#24 gdk_display_get_event
at /build/buildd/gtk+3.0-3.3.16/./gdk/gdkdisplay.c line 309
#25 gdk_event_source_dispatch
at /build/buildd/gtk+3.0-3.3.16/./gdk/x11/gdkeventsource.c line 356
#26 g_main_dispatch
at /build/buildd/glib2.0-2.31.18/./glib/gmain.c line 2510
#27 g_main_context_dispatch
at /build/buildd/glib2.0-2.31.18/./glib/gmain.c line 3047
#28 g_main_context_iterate
at /build/buildd/glib2.0-2.31.18/./glib/gmain.c line 3118

Comment 1 Sebastien Bacher 2012-02-22 11:28:19 UTC

The bug is similar to gsd bug #670461

Comment 2 Bastien Nocera 2012-02-22 18:56:32 UTC

It's the same code, so it's a dupe.

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

Comment 3 Sebastien Bacher 2012-02-22 19:39:49 UTC

right, though launchpad doesn't have a way to say that the same bug affect different component, i.e that g-c-c will need an update of the code copy to have the issue resolved...