GNOME Bugzilla – Bug 641969
X Window System error BadRequest
Last modified: 2012-08-12 13:03:07 UTC
When Evolutions mailer component is first time activated after Evolution was newly startet causes an X Window System error. $ evolution -c calendar (evolution:6372): evolution-network-manager-WARNING **: The name org.freedesktop.NetworkManager was not provided by any .service files (evolution:6372): GLib-GObject-WARNING **: value "-14,000000" of type `gdouble' is invalid or out of range for property `minimum-width' of type `gdouble' (evolution:6372): GLib-GObject-WARNING **: value "-14,000000" of type `gdouble' is invalid or out of range for property `minimum-width' of type `gdouble' (evolution:6372): GLib-GObject-WARNING **: value "-14,000000" of type `gdouble' is invalid or out of range for property `minimum-width' of type `gdouble' (evolution:6372): GLib-GObject-WARNING **: value "-14,000000" of type `gdouble' is invalid or out of range for property `minimum-width' of type `gdouble' (evolution:6372): GLib-GObject-WARNING **: value "-14,000000" of type `gdouble' is invalid or out of range for property `minimum-width' of type `gdouble' (evolution:6372): GLib-GObject-WARNING **: value "-14,000000" of type `gdouble' is invalid or out of range for property `minimum-width' of type `gdouble' (evolution:6372): GLib-GObject-WARNING **: value "-14,000000" of type `gdouble' is invalid or out of range for property `minimum-width' of type `gdouble' (evolution:6372): GLib-GObject-WARNING **: value "-14,000000" of type `gdouble' is invalid or out of range for property `minimum-width' of type `gdouble' (evolution:6372): GLib-GObject-WARNING **: value "-14,000000" of type `gdouble' is invalid or out of range for property `minimum-width' of type `gdouble' The program 'evolution' received an X Window System error. This probably reflects a bug in the program. The error was 'BadRequest (invalid request code or no such operation)'. (Details: serial 3033 error_code 1 request_code 0 minor_code 0) (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 --sync command line option to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.) $ gdb evolution GNU gdb (GDB) 7.2-debian Copyright (C) 2010 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-linux-gnu". For bug reporting instructions, please see: <http://www.gnu.org/software/gdb/bugs/>... Reading symbols from /usr/bin/evolution...Reading symbols from /usr/lib/debug/usr/bin/evolution...done. done. (gdb) break gdk_x_error Function "gdk_x_error" not defined. Make breakpoint pending on future shared library load? (y or [n]) y Breakpoint 1 (gdk_x_error) pending. (gdb) run -c calendar --sync Starting program: /usr/bin/evolution -c calendar --sync [Thread debugging using libthread_db enabled] [New Thread 0x7fffe29eb700 (LWP 6568)] [New Thread 0x7fffe21ea700 (LWP 6569)] [New Thread 0x7fffe15cf700 (LWP 6570)] [New Thread 0x7fffe0dce700 (LWP 6571)] [New Thread 0x7fffe05cd700 (LWP 6572)] [New Thread 0x7fffdfdcc700 (LWP 6573)] [New Thread 0x7fffdf5cb700 (LWP 6574)] (evolution:6565): evolution-network-manager-WARNING **: The name org.freedesktop.NetworkManager was not provided by any .service files [Thread 0x7fffe05cd700 (LWP 6572) exited] [New Thread 0x7fffe05cd700 (LWP 6575)] [New Thread 0x7fffd3195700 (LWP 6576)] [New Thread 0x7fffd2994700 (LWP 6577)] [New Thread 0x7fffcbfff700 (LWP 6578)] [New Thread 0x7fffd156c700 (LWP 6580)] [Thread 0x7fffd156c700 (LWP 6580) exited] [Thread 0x7fffcbfff700 (LWP 6578) exited] [Thread 0x7fffd2994700 (LWP 6577) exited] [Thread 0x7fffd3195700 (LWP 6576) exited] (evolution:6565): GLib-GObject-WARNING **: value "-14,000000" of type `gdouble' is invalid or out of range for property `minimum-width' of type `gdouble' (evolution:6565): GLib-GObject-WARNING **: value "-14,000000" of type `gdouble' is invalid or out of range for property `minimum-width' of type `gdouble' (evolution:6565): GLib-GObject-WARNING **: value "-14,000000" of type `gdouble' is invalid or out of range for property `minimum-width' of type `gdouble' (evolution:6565): GLib-GObject-WARNING **: value "-14,000000" of type `gdouble' is invalid or out of range for property `minimum-width' of type `gdouble' (evolution:6565): GLib-GObject-WARNING **: value "-14,000000" of type `gdouble' is invalid or out of range for property `minimum-width' of type `gdouble' (evolution:6565): GLib-GObject-WARNING **: value "-14,000000" of type `gdouble' is invalid or out of range for property `minimum-width' of type `gdouble' (evolution:6565): GLib-GObject-WARNING **: value "-14,000000" of type `gdouble' is invalid or out of range for property `minimum-width' of type `gdouble' (evolution:6565): GLib-GObject-WARNING **: value "-14,000000" of type `gdouble' is invalid or out of range for property `minimum-width' of type `gdouble' (evolution:6565): GLib-GObject-WARNING **: value "-14,000000" of type `gdouble' is invalid or out of range for property `minimum-width' of type `gdouble' evolution: ../../src/xcb_io.c:140: dequeue_pending_request: Zusicherung »req == dpy->xcb->pending_requests« nicht erfüllt. Program received signal SIGABRT, Aborted.
+ Trace 225918
Thread 140736957568768 (LWP 6575)
A debugging session is active. Inferior 1 [process 6565] will be killed. Quit anyway? (y or n) y $ All this happens while while/before drawing the small month view calendar at the bottom left, the big day view in the center and the task list at the right. I'm using Evolution 2.30.3-5 Debian package. This bug is related to Bug #641152. The deadlock happend at exactly the time and with exactly the conditions as this reported bug. Since I've updated Xorg and the Nvidia drivers, the deadlock does not happen any more. Therefore I could investigate the problem in more detail.
Damn, been glad too early, the deadlock now happened again, so nothing solved.
Is this still an issue in 3.4.3 or 3.2.3?
didn't see for a while now