Comment 4 for bug 2026789

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

I'm now thinking the screen freeze was:

[ 198.184944] semiauto gnome-shell[2341]: Failed to allocate onscreen framebuffer for /dev/dri/card1: Failed to create dumb drm buffer: Cannot allocate memory
[ 198.209428] semiauto gnome-shell[2341]: Failed to allocate onscreen framebuffer for /dev/dri/card1: Failed to create dumb drm buffer: Cannot allocate memory
...
[ 199.493073] semiauto gnome-shell[2341]: meta_frame_native_release: assertion '!frame_native->kms_update' failed
[ 199.494175] semiauto gnome-shell[2341]: (../clutter/clutter/clutter-frame-clock.c:425):clutter_frame_clock_notify_presented: code should not be reached
[ 199.494260] semiauto gnome-shell[2341]: (../clutter/clutter/clutter-frame-clock.c:425):clutter_frame_clock_notify_presented: code should not be reached
[ 199.527787] semiauto gnome-shell[2341]: (../clutter/clutter/clutter-frame-clock.c:425):clutter_frame_clock_notify_presented: code should not be reached

from bug 2026790. Because I can reproduce that perfectly by modifying code.