xfce4-appfinder crashed with SIGSEGV in g_type_check_instance_cast()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
xfce4-appfinder (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
1) Xubuntu 12.10 i386 Beta2 9-26-2012
2) xfce4-appfinder 4.10.0-1
3) I did not expect the application finder to crash while doing the Xubuntu post-installation testcase.
4) I was on step (2. Open Ubuntu Software Center and install applications you would like to use, Ensure the applications are installed correctly and appear in the applications menu) of the Xubuntu post-installation testcase I had installed two applications from the Ubuntu Software Center Bleachbit and Htop. My next step was checking to see if the apps appeared in the applications menu and yes these two apps were there. I launched the Application Finder from the bottom panel (panel 1) to see if the apps were there. I had left the Ubuntu Software Center open but minimized to the top panel at this point the application finder crashed.
ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: xfce4-appfinder 4.10.0-1
ProcVersionSign
Uname: Linux 3.5.0-15-generic i686
ApportVersion: 2.5.2-0ubuntu4
Architecture: i386
Date: Wed Sep 26 22:18:24 2012
ExecutablePath: /usr/bin/
InstallationMedia: Xubuntu 12.10 "Quantal Quetzal" - Beta i386 (20120926)
ProcCmdline: xfce4-appfinder
SegvAnalysis:
Segfault happened at: 0xb6f98bbe <g_type_
PC (0xb6f98bbe) ok
source "(%edx)" (0xaaaaaaaa) not located in a known VMA region (needed readable region)!
destination "%eax" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: xfce4-appfinder
StacktraceTop:
g_type_
?? ()
g_cclosure_
?? () from /usr/lib/
g_signal_
Title: xfce4-appfinder crashed with SIGSEGV in g_type_
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 #1030302, 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.