wnck-applet crashed with SIGSEGV in g_closure_invoke()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
gnome-panel (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: gnome-panel
While Firefox was connecting to an internet site I right clicked the workspace selector and it crashed. I put it back on the panel OK.
Description: Ubuntu lucid (development branch)
Release: 10.04 daily update 26jan10
gnome-panel:
Installed: 1:2.29.5.1-0ubuntu2
Candidate: 1:2.29.5.1-0ubuntu2
Version table:
*** 1:2.29.5.1-0ubuntu2 0
500 http://
100 /var/lib/
ubuntu@ubuntu:~$
booted from a USB stick
I wanted to increase the number of workspaces to four but it crashed with this bug report. After re-installing the workspace selector I have been able to increase it to four. Firefow was trying to connect to a URL that was un-available.
This is my 1st bug report, I hope it helps you keep up the good work.
ProblemType: Crash
Architecture: i386
CrashCounter: 1
Date: Tue Jan 26 13:51:19 2010
DistroRelease: Ubuntu 10.04
ExecutablePath: /usr/lib/
LiveMediaBuild: Ubuntu 10.04 "Lucid Lynx" - Alpha i386 (20100126)
Package: gnome-panel 1:2.29.5.1-0ubuntu2
ProcCmdline: /usr/lib/
ProcEnviron:
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcVersionSign
SegvAnalysis:
Segfault happened at: 0x804c6f6: mov (%ebx),%eax
PC (0x0804c6f6) ok
source "(%ebx)" (0x00000000) not located in a known VMA region (needed readable region)!
destination "%eax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gnome-panel
StacktraceTop:
?? ()
?? ()
?? () from /usr/lib/
g_closure_invoke () from /usr/lib/
bonobo_
Title: wnck-applet crashed with SIGSEGV in g_closure_invoke()
Uname: Linux 2.6.32-11-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
Thank you for taking the time to report this crash and helping to make Ubuntu better. This particular crash has already been reported and is a duplicate of bug #508452, 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.