xfdesktop crashed with SIGSEGV in g_closure_invoke()

Bug #757859 reported by Ron Steed
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
xfdesktop4 (Ubuntu)
New
Undecided
Unassigned

Bug Description

Binary package hint: xfdesktop4

Opened Firefox 4.0 and when to a new page and a long pause happened and then the crash dialog came up.

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: xfdesktop4 4.8.1-1ubuntu2
ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2
Uname: Linux 2.6.38-8-generic i686
NonfreeKernelModules: nvidia
Architecture: i386
Date: Mon Apr 11 12:15:40 2011
ExecutablePath: /usr/bin/xfdesktop
InstallationMedia: Xubuntu 11.04 "Natty Narwhal" - Beta i386 (20110330)
ProcCmdline: xfdesktop
ProcEnviron:
 LANGUAGE=en_US:en
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x267ae7: mov (%esi),%edx
 PC (0x00267ae7) ok
 source "(%esi)" (0x00000035) not located in a known VMA region (needed readable region)!
 destination "%edx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: xfdesktop4
StacktraceTop:
 ?? ()
 ?? () from /usr/lib/libgtk-x11-2.0.so.0
 g_closure_invoke () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
 ?? () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
 g_signal_emit_valist () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
Title: xfdesktop crashed with SIGSEGV in g_closure_invoke()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
Ron Steed (ronsteed) 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 Ubuntu better. This particular crash has already been reported and is a duplicate of bug #724816, 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.