gnome-shell crashed with SIGSEGV in meta_window_move_frame()

Bug #1051541 reported by Sparhawk
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
gnome-shell (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Just tried gnome-shell for the first time in the last two days. It's crashing like crazy for me. Freezing up every 20 minutes, then I have to change to tty1 and kill it. This is just one bug of many! (N.B. I haven't restarted yet, and I feel like I've got more crashes since I killed gnome-shell and restarted it via tty1. So perhaps it'd be not quite so severe if I just restarted.)

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: gnome-shell 3.4.1-0ubuntu2
ProcVersionSignature: Ubuntu 3.2.0-30.48-generic 3.2.27
Uname: Linux 3.2.0-30-generic x86_64
ApportVersion: 2.0.1-0ubuntu13
Architecture: amd64
Date: Sun Sep 16 20:34:04 2012
ExecutablePath: /usr/bin/gnome-shell
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
ProcCmdline: gnome-shell
SegvAnalysis:
 Segfault happened at: 0x7f68657e9e67 <meta_window_move_frame+71>: add 0x28(%rax),%ecx
 PC (0x7f68657e9e67) ok
 source "0x28(%rax)" (0x00000028) not located in a known VMA region (needed readable region)!
 destination "%ecx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gnome-shell
StacktraceTop:
 meta_window_move_frame () from /usr/lib/libmutter.so.0
 ?? () from /usr/lib/libmutter.so.0
 ?? () from /usr/lib/libmutter.so.0
 meta_display_process_key_event () from /usr/lib/libmutter.so.0
 ?? () from /usr/lib/libmutter.so.0
Title: gnome-shell crashed with SIGSEGV in meta_window_move_frame()
UpgradeStatus: Upgraded to precise on 2012-04-29 (140 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
Sparhawk (sparhawkthesecond) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 meta_window_move_frame (window=0x449a820, user_op=1, root_x_nw=0, root_y_nw=<optimized out>) at core/window.c:5121
 handle_move_to_corner_backend (window=0x449a820, xchange=1, ychange=0, to_right=0, to_bottom=0, display=<optimized out>, screen=<optimized out>, dummy=<optimized out>) at core/keybindings.c:2668
 process_event (bindings=<optimized out>, n_bindings=<optimized out>, display=0x3403b60, screen=0x25021c0, window=0x449a820, event=0x7fff0655d2a0, on_window=1, keysym=<optimized out>) at core/keybindings.c:1441
 meta_display_process_key_event (display=0x3403b60, window=0x449a820, event=0x7fff0655d2a0) at core/keybindings.c:1683
 event_callback (event=0x7fff0655d2a0, data=0x3403b60) at core/display.c:1795

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : StacktraceSource.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in gnome-shell (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Revision history for this message
Sparhawk (sparhawkthesecond) wrote :

Ok, so it seems like I can crash this at will by pressing ctrl+alt+<keypad number>, in an attempt to place a window. I'm not even sure where this shortcut is defined, so I'm not sure the actual function of this keystroke. I checked System Settings, and dconf editor (org.gnome.desktop.wm.keybindings and org.gnome.mutter.keybindings), but it appeared this keybinding was not defined anywhere!

Jeremy Bícha (jbicha)
visibility: private → public
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in gnome-shell (Ubuntu):
status: New → Confirmed
Revision history for this message
Jeremy Bícha (jbicha) wrote :

Thank you for reporting this bug to Ubuntu. Ubuntu 12.04 LTS reached End of
Life in April. See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases

Please upgrade to Ubuntu 16.04 LTS and re-test. If the bug is still
reproducible, increase the verbosity of the steps to recreate it so we
can try again.

I apologize that we are not always to respond to bug reports promptly.
Do feel free to report any other bugs you may find.

Changed in gnome-shell (Ubuntu):
status: Confirmed → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.