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 656572 - Call window asserts when you try to move the preview
Call window asserts when you try to move the preview
Status: RESOLVED FIXED
Product: empathy
Classification: Core
Component: VoIP
unspecified
Other Linux
: Normal normal
: ---
Assigned To: empathy-maint
Depends on:
Blocks:
 
 
Reported: 2011-08-15 13:14 UTC by Jonny Lamb
Modified: 2011-08-16 10:17 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
Get the preview position from preview_pos (1.24 KB, patch)
2011-08-16 00:07 UTC, Emilio Pozuelo Monfort 		reviewed Details | Review

Description Jonny Lamb 2011-08-15 13:14:32 UTC 
Czech it out.

Clutter-CRITICAL **: clutter_rectangle_set_border_width: assertion `CLUTTER_IS_RECTANGLE (rectangle)' failed
aborting...

Program received signal SIGABRT, Aborted.
0x00007fffed0e9415 in raise (sig=<value optimized out>) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64
64	../nptl/sysdeps/unix/sysv/linux/raise.c: No such file or directory.
	in ../nptl/sysdeps/unix/sysv/linux/raise.c
(gdb) bt

+ Trace 228097

  • #0 raise
    at ../nptl/sysdeps/unix/sysv/linux/raise.c line 64
  • #1 abort
    at abort.c line 92
  • #2 g_logv
    at /build/buildd-glib2.0_2.28.6-2-amd64-N0qtaT/glib2.0-2.28.6/./glib/gmessages.c line 557
  • #3 g_log
    at /build/buildd-glib2.0_2.28.6-2-amd64-N0qtaT/glib2.0-2.28.6/./glib/gmessages.c line 577
  • #4 empathy_call_window_highlight_preview_rectangle
    at empathy-call-window.c line 802
  • #5 empathy_call_window_preview_enter_event_cb
    at empathy-call-window.c line 906
  • #6 _clutter_marshal_BOOLEAN__BOXED
    at clutter-marshal.c line 85
  • #7 g_closure_invoke
    at /build/buildd-glib2.0_2.28.6-2-amd64-N0qtaT/glib2.0-2.28.6/./gobject/gclosure.c line 767
  • #8 signal_emit_unlocked_R
    at /build/buildd-glib2.0_2.28.6-2-amd64-N0qtaT/glib2.0-2.28.6/./gobject/gsignal.c line 3252
  • #9 g_signal_emit_valist
    at /build/buildd-glib2.0_2.28.6-2-amd64-N0qtaT/glib2.0-2.28.6/./gobject/gsignal.c line 2993
  • #10 g_signal_emit
    at /build/buildd-glib2.0_2.28.6-2-amd64-N0qtaT/glib2.0-2.28.6/./gobject/gsignal.c line 3040
  • #11 clutter_actor_event
    at ./clutter-actor.c line 8087
  • #12 emit_event
    at ./clutter-main.c line 2189
  • #13 emit_pointer_event
    at ./clutter-main.c line 2216
  • #14 _clutter_process_event_details
    at ./clutter-main.c line 2355
  • #15 _clutter_process_event
    at ./clutter-main.c line 2552
  • #16 _clutter_stage_process_queued_events
    at ./clutter-stage.c line 730
  • #17 clutter_clock_dispatch
    at ./clutter-master-clock.c line 360
  • #18 g_main_dispatch
    at /build/buildd-glib2.0_2.28.6-2-amd64-N0qtaT/glib2.0-2.28.6/./glib/gmain.c line 2440
  • #19 g_main_context_dispatch
    at /build/buildd-glib2.0_2.28.6-2-amd64-N0qtaT/glib2.0-2.28.6/./glib/gmain.c line 3013
  • #20 g_main_context_iterate
    at /build/buildd-glib2.0_2.28.6-2-amd64-N0qtaT/glib2.0-2.28.6/./glib/gmain.c line 3091
  • #21 g_main_loop_run
    at /build/buildd-glib2.0_2.28.6-2-amd64-N0qtaT/glib2.0-2.28.6/./glib/gmain.c line 3299
  • #22 gtk_main
    at /scratch/build-area/gtk+3.0-3.0.8/./gtk/gtkmain.c line 1358
  • #23 g_application_run
    at /build/buildd-glib2.0_2.28.6-2-amd64-N0qtaT/glib2.0-2.28.6/./gio/gapplication.c line 1322
  • #24 main
    at empathy-call.c line 181 






Comment 1


Jonny Lamb





          2011-08-15 13:17:38 UTC
        



This is just the first one, if you switch off G_DEBUG=fatal_warnings there are more and even a CLUTTER_IS_ACTOR assertion inside clutter_actor_show.






Comment 2


Emilio Pozuelo Monfort





          2011-08-16 00:07:43 UTC
        



Created attachment 193903 [details] [review]
Get the preview position from preview_pos

Getting it from the coordinates might fail if the system
is too slow and gives us bad coordinates.






Comment 3


Guillaume Desmottes





          2011-08-16 07:35:22 UTC
        



Review of attachment 193903 [details] [review]:

++






Comment 4


Emilio Pozuelo Monfort





          2011-08-16 10:17:33 UTC
        



This problem has been fixed in the development version. The fix will be available in the next major software release. Thank you for your bug report.