pcmanfm crashed with SIGSEGV in gtk_widget_get_toplevel()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
pcmanfm (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Didn't give me much info; just said a program has crashed. I haven't had a lot of luck with any linux distro for my hp pavilion G7, mainly because of display driver issues with pre 3.2 kernels. I have tried other distros with 3.2 or later kernels, however, and still encountered numerous problems. So far, Ubuntu is the only one that works reasonably well, other than giving me these program crash notifications frequently and hanging during boot on occasion.
If this is going to be read by Ubuntu designers, it would be great if Ubuntu had more dialogue windows that popped up to let you know what's going on so you don't just think the computer has frozen when it's just applying updates, etc.
ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: pcmanfm 0.9.10-0ubuntu1
ProcVersionSign
Uname: Linux 3.2.0-16-generic x86_64
ApportVersion: 1.91-0ubuntu1
Architecture: amd64
Config_
Date: Thu Feb 16 16:07:32 2012
ExecutablePath: /usr/bin/pcmanfm
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (20111129.1)
Pref_Config_
[Preferred Applications]
WebBrowser=
MailClient=
ProcCmdline: pcmanfm --desktop --profile LXDE
ProcEnviron:
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
SegvAnalysis:
Segfault happened at: 0x7fba627b5213 <gtk_widget_
PC (0x7fba627b5213) ok
source "0x58(%rbx)" (0xaaaaaaaaaaaa
destination "%rax" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: pcmanfm
StacktraceTop:
gtk_widget_
?? () from /usr/lib/
gtk_widget_
gtk_widget_
gtk_widget_
Title: pcmanfm crashed with SIGSEGV in gtk_widget_
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
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.