Bug 695765 – Gtk+ 3.7.12 crashes apps using clutter (evolution, gnome-control-center, ...)

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 695765 - Gtk+ 3.7.12 crashes apps using clutter (evolution, gnome-control-center, ...)


Summary:	Gtk+ 3.7.12 crashes apps using clutter (evolution, gnome-control-center, ...)


Status:	RESOLVED DUPLICATE of bug 692707

Product:	clutter
Classification:	Platform
Component:	x11
Version:	1.12.x
Hardware:	Other Linux

Importance:	Normal critical
Target Milestone:	---
Assigned To:	clutter-maint
QA Contact:	clutter-maint

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2013-03-13 12:34 UTC by Maciej (Matthew) Piechotka
Modified:	2013-03-13 15:36 UTC

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

Description Maciej (Matthew) Piechotka 2013-03-13 12:34:55 UTC

Error is about integer value out of range. Gtk+ 3.6 works without problems.

Clutter 1.12.2
Clutter-gtk 1.4.2

Breakpoint 1, gdk_x_error (xdisplay=0x658190, error=0x7fffffffd690)
    at gdkmain-x11.c:266
266	in gdkmain-x11.c

+ Trace 231636

Thread 1 (Thread 0x7ffff7f7e940 (LWP 19448))

#0 gdk_x_error
at gdkmain-x11.c line 266
#1 _XError
at /var/tmp/portage/x11-libs/libX11-1.5.0-r1/work/libX11-1.5.0/src/XlibInt.c line 1583
#2 handle_error
at /var/tmp/portage/x11-libs/libX11-1.5.0-r1/work/libX11-1.5.0/src/xcb_io.c line 212
#3 _XReply
at /var/tmp/portage/x11-libs/libX11-1.5.0-r1/work/libX11-1.5.0/src/xcb_io.c line 698
#4 _xiQueryVersion
at /var/tmp/portage/x11-libs/libXi-1.7/work/libXi-1.7/src/XIQueryVersion.c line 84
#5 XIQueryVersion
at /var/tmp/portage/x11-libs/libXi-1.7/work/libXi-1.7/src/XIQueryVersion.c line 45
#6 clutter_backend_x11_create_device_manager
at ./x11/clutter-backend-x11.c line 249
#7 _clutter_backend_x11_events_init
at ./x11/clutter-backend-x11.c line 502
#8 clutter_init_real
at ./clutter-main.c line 1632
#9 post_parse_hook
at ./gtk-clutter-util.c line 107
#10 g_option_context_parse
at goption.c line 2009
#11 gtk_clutter_init_with_args
at ./gtk-clutter-util.c line 271
#12 main
at main.c line 513


Program received signal SIGTRAP, Trace/breakpoint trap.
g_logv (log_domain=0x7ffff32c5ec6 "Gdk", log_level=G_LOG_LEVEL_ERROR, 
    format=<optimized out>, args=<optimized out>) at gmessages.c:981
981	gmessages.c: No such file or directory.
A debugging session is active.

	Inferior 1 [process 19448] will be killed.

Quit anyway? (y or n)

Comment 1 Emmanuele Bassi (:ebassi) 2013-03-13 14:35:23 UTC

Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.

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

Comment 2 Emmanuele Bassi (:ebassi) 2013-03-13 14:37:32 UTC

the commit that fixed the bug is also in the clutter-1.12 branch, so it can be used as a distro patch:

commit 3c017eaf28cff89d82f868b0c7d92399884c3c47
Author: Yanko Kaneti <yaneti@declera.com>
Date:   Mon Jan 28 15:49:51 2013 +0200

    xi2: Fix access beyond array boundaries
    (cherry picked from commit 673e7c10d8c008ddf88af4746423e7897690ebe9)
    
    Signed-off-by: Emmanuele Bassi <ebassi@gnome.org>

I'll try and make a final 1.12 release along with the first 1.14 one.

Comment 3 Maciej (Matthew) Piechotka 2013-03-13 15:36:16 UTC

I got the same error even if I patched the clutter:

(gnome-control-center:1476): Gdk-ERROR **: The program 'gnome-control-center' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadValue (integer parameter out of range for operation)'.
  (Details: serial 177 error_code 2 request_code 131 minor_code 47)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the GDK_SYNCHRONIZE environment
   variable to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)

My compiler is gcc 4.7.2.