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 592620 - Empathy crashes when closing contact map window
Empathy crashes when closing contact map window
Status: RESOLVED DUPLICATE of bug 590692
Product: empathy
Classification: Core
Component: Geolocation
2.27.x
Other Linux
: Normal normal
: ---
Assigned To: empathy-maint
Depends on:
Blocks:
 
 
Reported: 2009-08-21 20:06 UTC by Michael Monreal
Modified: 2009-08-22 03:13 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Michael Monreal 2009-08-21 20:06:17 UTC
Empathy crashes when closing the contact map window:

$ empathy
** (empathy:14621): DEBUG: mission_control_get_presence_actual: MC not running.
** (empathy:14621): DEBUG: mission_control_get_presence_message_actual: MC not running.
** (empathy:14621): DEBUG: mission_control_get_tpconnection: MC not running.
** (empathy:14621): DEBUG: mission_control_get_connection_status: MC not running.
** (empathy:14621): DEBUG: mission_control_get_presence_actual: MC not running.
The program 'empathy' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadWindow (invalid Window parameter)'.
  (Details: serial 2819 error_code 3 request_code 10 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.)
Comment 1 Pierre-Luc Beaudoin 2009-08-22 03:13:25 UTC
Thanks for taking the time to report this.  This is an infortunate bug in Clutter 1.0.  I report the issue on their bugzilla.  I am going to mark this bug as duplicate as the libchamplain bug we are using to track this issue.

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