Created attachment 405854 [details] Segfault backtrace I am unable to calibrate my Wacom Cintiq 13HD tablet within the Gnome Control Center. Clicking on "Calibrate.." will result in a segfault. > gnome-control-c[2916]: segfault at 2bf18ec8348 ip 00007f74fbb26bac sp 00007ffcc8193b20 error 4 in libclutter-1.0.so.0.2202.0[7f74fba95000+14b000]
Created attachment 405856 [details] emerge --info
I don't have a way of testing this because I don't have a cintiq (or other tablet with integrated display). So to figure out the crash, you need to give some more information. 1. What versions of clutter, gnome-control-center, libwacom and with what USE flags? 2. The backtrace at the moment is not useful because debugging symbols were disabled. Those "??" are referring to functions - but to which ones? Therefore, please rebuild the following packages with "-ggdb" in CFLAGS/CXXFLAGS and "splitdebug" in FEATURES: glib, gtk+, clutter, gnome-control-center, gnome-settings-daemon, gnome-desktop, libwacom And then get a new backtrace for all threads ("thread apply all bt full") from the segfault. Please see https://wiki.gentoo.org/wiki/Project:Quality_Assurance/Backtraces for more information.
Created attachment 405866 [details] package versions
Created attachment 405868 [details] backtrace with debug symbols
Sorry if I haven't provided enough informations before.
Thanks. An upstream developer who really understands the code needs to look at this; I can't figure out what is happening in the chain of signals and callbacks. But it seems suspicious to me that the clutter clock and the stylus's gdk_device have the same memory address... Please rebuild dconf and clutter-gtk with "-ggdb" in CFLAGS/CXXFLAGS and "splitdebug" in FEATURES, and get a new backtrace to get rid of the last "??". Then create a new bug in upstream bugzilla: https://bugzilla.gnome.org/enter_bug.cgi?product=gnome-control-center&component=Wacom&version=3.16.x attach the new backtrace and add gnome@gentoo.org to CC list. (I am asking you to do it because upstream developers may need you to run some tests to help diagnose the bug - and you are the person with the cintiq.)
To provide the attachment in upstream report it will be better if you simply paste it as a comment or in the main report instead of attaching it, that way they can detect possible duplicated bugs and backtraces :) (an interesting feature of their bugzilla ;) Thanks
This was solved in upstream side some time ago
