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 623245 - Crash when unlocking screen
Crash when unlocking screen
Status: RESOLVED DUPLICATE of bug 623235
Product: mutter
Classification: Core
Component: general
git master
Other Linux
: Normal normal
: ---
Assigned To: mutter-maint
mutter-maint
Depends on:
Blocks:
 
 
Reported: 2010-06-30 21:06 UTC by Milan Bouchet-Valat
Modified: 2010-06-30 21:08 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Milan Bouchet-Valat 2010-06-30 21:06:32 UTC 
This week I'm experiencing a new crash when coming back from a locked screen. It can reproduce it about two times, and after that it seems to disappear.

From the trace it seems to be closely tied with the i915 driver, but I've not upgraded Xorg this week, and the bug has appeared very recently. Maybe a change in clutter triggered this? Hard to tell where the real bug is.

Graphic card: Intel 915GM/GMS/910GML
Xorg 7.5, libgl1-mesa-dri 7.9.0~git20100318.

The printed abort message is consistently:
Unexpected X error: BadDamage (invalid Damage parameter) serial 238111 error_code 165 request_code 152 minor_code 3)


Program received signal SIGABRT, Aborted.
0xb77f6430 in __kernel_vsyscall ()
(gdb) ba

+ Trace 222653

  • #0 __kernel_vsyscall
  • #1 *__GI_raise
    at ../nptl/sysdeps/unix/sysv/linux/raise.c line 64
  • #2 *__GI_abort
    at abort.c line 92
  • #3 meta_bug
  • #4 x_error_handler
    at core/errors.c line 211
  • #5 _XError
    from /usr/lib/libX11.so.6
  • #6 ??
    from /usr/lib/libX11.so.6
  • #7 _XReply
    from /usr/lib/libX11.so.6
  • #8 ??
    from /usr/lib/libGL.so.1
  • #9 ??
    from /usr/lib/libGL.so.1
  • #10 ??
    from /usr/lib/dri/i915_dri.so
  • #11 ??
    from /usr/lib/dri/i915_dri.so
  • #12 ??
    from /usr/lib/dri/i915_dri.so
  • #13 ??
    from /usr/lib/dri/i915_dri.so
  • #14 ??
    from /usr/lib/dri/i915_dri.so
  • #15 cogl_clear
    at ./cogl.c line 192
  • #16 clutter_stage_paint
    at ./clutter-stage.c line 304
  • #17 g_cclosure_marshal_VOID__VOID
    at gmarshal.c line 79
  • #18 g_type_class_meta_marshal
    at gclosure.c line 878
  • #19 g_closure_invoke
    at gclosure.c line 767
  • #20 signal_emit_unlocked_R
    at gsignal.c line 3291
  • #21 g_signal_emit_valist
    at gsignal.c line 2984
  • #22 g_signal_emit
    at gsignal.c line 3041
  • #23 clutter_actor_paint
    at ./clutter-actor.c line 2560
  • #24 clutter_stage_glx_redraw
    at clutter-stage-glx.c line 548
  • #25 clutter_backend_glx_redraw
    at clutter-backend-glx.c line 777
  • #26 _clutter_backend_redraw
    at ./clutter-backend.c line 324
  • #27 _clutter_do_redraw
    at ./clutter-main.c line 304
  • #28 _clutter_stage_do_update
    at ./clutter-stage.c line 651
  • #29 clutter_clock_dispatch
    at ./clutter-master-clock.c line 373
  • #30 g_main_dispatch
    at gmain.c line 2044
  • #31 g_main_context_dispatch
    at gmain.c line 2597
  • #32 g_main_context_iterate
    at gmain.c line 2675
  • #33 g_main_loop_run
    at gmain.c line 2883
  • #34 main
    at core/main.c line 725 






Comment 1


Owen Taylor





          2010-06-30 21:08:45 UTC
        



There's a pseudo-patch in bug 623235 that I think should fix the problem.

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