metacity crashed with SIGABRT in raise()

Bug #745619 reported by zerocoolre
84
This bug affects 15 people
Affects Status Importance Assigned to Milestone
metacity (Ubuntu)
Expired
Medium
Unassigned

Bug Description

Binary package hint: metacity

No

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: metacity 1:2.30.3-0ubuntu7
ProcVersionSignature: Ubuntu 2.6.38-7.39-generic 2.6.38
Uname: Linux 2.6.38-7-generic x86_64
Architecture: amd64
Date: Wed Mar 30 17:09:00 2011
ExecutablePath: /usr/bin/metacity
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Alpha amd64 (20110302)
ProcCmdline: metacity
ProcEnviron:
 LANG=ru_RU.UTF-8
 SHELL=/bin/false
 PATH=(custom, no user)
Signal: 6
SourcePackage: metacity
StacktraceTop:
 raise () from /lib/x86_64-linux-gnu/libc.so.6
 abort () from /lib/x86_64-linux-gnu/libc.so.6
 g_assertion_message () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? ()
 ?? ()
Title: metacity crashed with SIGABRT in raise()
UpgradeStatus: Upgraded to natty on 2011-03-28 (1 days ago)
UserGroups:

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

StacktraceTop:
 raise (sig=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64
 abort () at abort.c:92
 g_assertion_message (domain=<value optimized out>, file=<value optimized out>, line=<value optimized out>, func=0x463510 "meta_rectangle_edge_aligns", message=0x7f1da99436cd "code should not be reached") at /build/buildd/glib2.0-2.28.4/./glib/gtestutils.c:1358
 meta_rectangle_edge_aligns (rect=<value optimized out>, edge=<value optimized out>) at core/boxes.c:1161
 apply_edge_resistance (old_pos=979, new_pos=986, old_rect=0x7fff1252dbc0, new_rect=0x7fff1252dba0, edges=0x2243540, resistance_data=<value optimized out>, xdir=0, keyboard_op=0, window=<value optimized out>, timeout_func=<value optimized out>) at core/edge-resistance.c:391

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in metacity (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Revision history for this message
Marc Deslauriers (mdeslaur) wrote :

Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find.

security vulnerability: yes → no
visibility: private → public
Colan Schwartz (colan)
Changed in metacity (Ubuntu):
status: New → Confirmed
Revision history for this message
Pedro Villavicencio (pedro) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please answer these questions:
1. Is this reproducible?
2. If so, what specific steps should we take to recreate this bug? Be as detailed as possible.
This will help us to find and resolve the problem.

Changed in metacity (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Pedro Villavicencio (pedro) wrote :

We're closing this bug since it is has been some time with no response from the original reporter. However, if the issue still exists please feel free to reopen with the requested information. Also, if you could, please test against the latest development version of Ubuntu, since this confirms the bug is one we may be able to pass upstream for help.

Changed in metacity (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

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