pcmanfm crashed with SIGSEGV in gtk_widget_get_toplevel()

Bug #921851 reported by Andres Sanchez
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
pcmanfm (Ubuntu)
New
Undecided
Unassigned

Bug Description

Updating this crash

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: pcmanfm 0.9.10-0ubuntu1
ProcVersionSignature: Ubuntu 3.0.0-15.26-generic 3.0.13
Uname: Linux 3.0.0-15-generic i686
ApportVersion: 1.91-0ubuntu1
Architecture: i386
Date: Wed Jan 25 17:07:22 2012
ExecutablePath: /usr/bin/pcmanfm
Pref_Config_System_lubuntu:
 [Preferred Applications]
 WebBrowser=firefox.desktop
 MailClient=
ProcCmdline: pcmanfm --desktop --profile lubuntu
ProcEnviron:
 LANGUAGE=es_CO:es
 LANG=es_CO.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x38476a <gtk_widget_get_toplevel+106>: mov 0x38(%esi),%eax
 PC (0x0038476a) ok
 source "0x38(%esi)" (0xaaaaaae2) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: pcmanfm
StacktraceTop:
 gtk_widget_get_toplevel () from /usr/lib/i386-linux-gnu/libgtk-x11-2.0.so.0
 ?? () from /usr/lib/i386-linux-gnu/libgtk-x11-2.0.so.0
 gtk_widget_create_pango_context () from /usr/lib/i386-linux-gnu/libgtk-x11-2.0.so.0
 gtk_widget_get_pango_context () from /usr/lib/i386-linux-gnu/libgtk-x11-2.0.so.0
 gtk_widget_create_pango_layout () from /usr/lib/i386-linux-gnu/libgtk-x11-2.0.so.0
Title: pcmanfm crashed with SIGSEGV in gtk_widget_get_toplevel()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
Andres Sanchez (afsanchez93-deactivatedaccount) wrote :
visibility: private → public
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 #838489, 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.

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.