gtk-window-decorator crashed with SIGSEGV in g_datalist_id_set_data_full()

Bug #1038520 reported by Shajahan
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
compiz (Ubuntu)
New
Undecided
Unassigned

Bug Description

Version : 12.10
Bug Details: VLC behaves weird on opening launching from side bar.

Steps to reproduce:
1. Open VLC from the side bar.
2. Right click in VLC screen to play.
3. There you go VLC crashes.

ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: compiz-gnome 1:0.9.8+bzr3249-0ubuntu4
ProcVersionSignature: Ubuntu 3.5.0-10.10-generic 3.5.1
Uname: Linux 3.5.0-10-generic i686
NonfreeKernelModules: wl
ApportVersion: 2.4-0ubuntu8
Architecture: i386
Date: Sat Aug 18 23:41:29 2012
ExecutablePath: /usr/bin/gtk-window-decorator
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 (20120423)
ProcCmdline: /usr/bin/gtk-window-decorator
ProcEnviron:
 PATH=(custom, user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0xb6e03277 <g_datalist_id_set_data_full+167>: mov (%ecx),%edi
 PC (0xb6e03277) ok
 source "(%ecx)" (0xaaaaaaa8) not located in a known VMA region (needed readable region)!
 destination "%edi" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: compiz
StacktraceTop:
 g_datalist_id_set_data_full () from /lib/i386-linux-gnu/libglib-2.0.so.0
 ?? () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
 ?? () from /usr/lib/i386-linux-gnu/libgtk-x11-2.0.so.0
 ?? () from /usr/lib/i386-linux-gnu/libgtk-x11-2.0.so.0
 g_object_unref () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
Title: gtk-window-decorator crashed with SIGSEGV in g_datalist_id_set_data_full()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm lpadmin sambashare sudo

Revision history for this message
Shajahan (shajahan-pts) wrote :
Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1021612, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.

visibility: private → public
tags: removed: need-i386-retrace
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.