metacity crashed with SIGABRT in XSync()

Bug #957276 reported by Sandeep Agrawal on 2012-03-16
This bug affects 2 people
Affects Status Importance Assigned to Milestone
metacity (Ubuntu)

Bug Description

I was playing around with Remmina's windowed mode, trying to move the window around, when I got this crash. This is the first time this has happened, and I am unable to reproduce it.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: metacity 1:2.34.1-1ubuntu8
ProcVersionSignature: Ubuntu 3.2.0-18.29-generic 3.2.9
Uname: Linux 3.2.0-18-generic x86_64
NonfreeKernelModules: fglrx
ApportVersion: 1.94.1-0ubuntu2
Architecture: amd64
Date: Fri Mar 16 14:06:55 2012
ExecutablePath: /usr/bin/metacity
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120301)
ProcCmdline: metacity
Signal: 6
SourcePackage: metacity
 ?? () from /usr/lib/x86_64-linux-gnu/
 ?? () from /usr/lib/x86_64-linux-gnu/
 _XReply () from /usr/lib/x86_64-linux-gnu/
 XSync () from /usr/lib/x86_64-linux-gnu/
 ?? ()
Title: metacity crashed with SIGABRT in _XReply()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Sandeep Agrawal (smartsands) wrote :
visibility: private → public

 XSync (dpy=0x1f9b630, discard=0) at ../../src/Sync.c:44
 meta_prop_get_values (display=0x2036c50, xwindow=37761843, values=0x201e700, n_values=1) at core/xprops.c:1019
 meta_window_reload_properties_from_xwindow (window=0x2161780, xwindow=37761843, properties=0x7ffff3f9a7c8, n_properties=1, initial=0) at core/window-props.c:134
 meta_window_reload_property (window=<optimized out>, property=40, initial=<optimized out>) at core/window-props.c:76
 process_property_notify (window=0x2161780, event=<optimized out>) at core/window.c:5610

Changed in metacity (Ubuntu):
importance: Undecided → Medium
summary: - metacity crashed with SIGABRT in _XReply()
+ metacity crashed with SIGABRT in XSync()
tags: removed: need-amd64-retrace
tags: added: quantal
Launchpad Janitor (janitor) wrote :

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

Changed in metacity (Ubuntu):
status: New → Confirmed
nickleus (nick-humphrey) wrote :

vinagre client works just fine:
sudo apt-get install vinagre

why was vinagre replaced with remmina?

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Duplicates of this bug

Other bug subscribers