gnome-panel crashed with SIGSEGV in g_signal_emit_valist()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
gnome-panel (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Not too sure what I'm doing here, This more or less opened up automatically and the summary was automatically generated as well.
I'm on 12.04 Beta, just updated, and I tried to install the ATI/AMD proprietary FGLRX graphics-driver (post release updates). After a restart, everything seemed fine, I logged in, and the screen was all sorts of colors and lines. After I clicked, it showed just the background. I summoned up gnome-do, checked the additional drivers. The driver was not installed, and then the error report popped up. Gnome panel reopened fine with a terminal command. Going to try the FGLRX without the post release updates, it's always worked better for me.
Thanks for your time!
ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: gnome-panel 1:3.3.91-0ubuntu1
ProcVersionSign
Uname: Linux 3.2.0-19-generic x86_64
NonfreeKernelMo
ApportVersion: 1.94.1-0ubuntu2
Architecture: amd64
Date: Sun Mar 18 16:07:15 2012
ExecutablePath: /usr/bin/
InstallationMedia: Ubuntu 10.04.4 LTS "Lucid Lynx" - Release amd64 (20120214.2)
ProcCmdline: gnome-panel
ProcEnviron:
LANG=en_US.UTF-8
SHELL=/bin/bash
SegvAnalysis:
Segfault happened at: 0x7fa1e0afb015: mov 0x78(%rax),%edx
PC (0x7fa1e0afb015) ok
source "0x78(%rax)" (0xaaaaaaaaaaaa
destination "%edx" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: gnome-panel
StacktraceTop:
?? () from /usr/lib/
?? () from /usr/lib/
?? () from /usr/lib/
g_signal_
g_signal_emit () from /usr/lib/
Title: gnome-panel crashed with SIGSEGV in g_signal_
UpgradeStatus: Upgraded to precise on 2012-03-17 (1 days ago)
UserGroups: adm admin cdrom dialout 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 #948667, 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.