pcmanfm crashed with SIGSEGV in gtk_widget_queue_resize()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
pcmanfm (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Hi, am from India. Am using Ubuntu 12.04 alpha release, this happens when I use the Safely Remove Option only on my new Moserbaer USB Flash drive 4GB called Nimble. This does not happen on my old Kingston Datatraveler 120 4GB nor on Transcend 2GB.
1) Ubuntu Release 12.04 (precise), Kernel Linux 3.2.0-3-generic, GNOME 3.2.1
2) pcmanfm 0.9.10-0ubuntu1
3) I expected Nothing to happen
4) Instead I got a Crash error report
ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: pcmanfm 0.9.10-0ubuntu1
ProcVersionSign
Uname: Linux 3.2.0-3-generic i686
ApportVersion: 1.90-0ubuntu1
Architecture: i386
Config_
CrashCounter: 1
Date: Thu Dec 8 23:14:59 2011
ExecutablePath: /usr/bin/pcmanfm
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1)
Pref_Config_
[Preferred Applications]
WebBrowser=
MailClient=
ProcCmdline: pcmanfm
ProcEnviron:
LANGUAGE=en_IN:en
PATH=(custom, no user)
LANG=en_IN
SHELL=/bin/bash
SegvAnalysis:
Segfault happened at: 0x1ba600: mov (%esi),%edi
PC (0x001ba600) ok
source "(%esi)" (0xaaaaaaaa) not located in a known VMA region (needed readable region)!
destination "%edi" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: pcmanfm
StacktraceTop:
?? () from /usr/lib/
?? () from /usr/lib/
?? () from /usr/lib/
gtk_widget_
?? () from /usr/lib/
Title: pcmanfm crashed with SIGSEGV in gtk_widget_
UpgradeStatus: Upgraded to precise on 2011-12-03 (5 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
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 #846220, 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.