drivel crashed with SIGFPE in g_closure_invoke()

[Aydar Khabibullin]

I just started drivel and then it crashed

ProblemType: Crash
DistroRelease: Ubuntu 10.04
Package: drivel 3.0.0-2
ProcVersionSignature: Ubuntu 2.6.32-19.28-generic 2.6.32.10+drm33.1
Uname: Linux 2.6.32-19-generic x86_64
Architecture: amd64
Date: Sat Apr 3 01:47:11 2010
ExecutablePath: /usr/bin/drivel
InstallationMedia: Xubuntu 10.04 "Lucid Lynx" - Alpha amd64 (20100224.1)
ProcCmdline: drivel
ProcEnviron:
 LANG=en_US.utf8
 SHELL=/bin/bash
Signal: 8
SourcePackage: drivel
StacktraceTop:
 ?? ()
 g_closure_invoke ()
 ?? () from /usr/lib/libgobject-2.0.so.0
 g_signal_emit_valist ()
 g_signal_emit () from /usr/lib/libgobject-2.0.so.0
Title: drivel crashed with SIGFPE in g_closure_invoke()
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

[Apport retracing service (apport)]

StacktraceTop:
 got_chunk_cb (msg=0x7b82f0, chunk=0x8ab210,
 g_closure_invoke ()
 ?? () from /usr/lib/libgobject-2.0.so.0
 g_signal_emit_valist ()
 g_signal_emit () from /usr/lib/libgobject-2.0.so.0

[Charlie Kravetz (cjkgeek)]

 Thank you for taking the time to report this bug and helping to make Ubuntu better. Please try to obtain a backtrace following the instructions at http://wiki.ubuntu.com/DebuggingProgramCrash and upload the backtrace (as an attachment) to the bug report. This will greatly help us in tracking down your problem.

Processing this report in order to get sufficient information for the developers failed (it does not generate an useful symbolic stack trace). This might be caused by some outdated packages which were installed on your system at the time of the report. Please upgrade your system to the latest package versions.

Thank you for your understanding, and sorry for the inconvenience!

[Charlie Kravetz (cjkgeek)]

Thank you for taking the time to report this bug and helping to make Ubuntu better.

However, processing it in order to get sufficient information for the developers failed (it does not generate an useful symbolic stack trace). This might be caused by some outdated packages which were installed on your system at the time of the report. Please upgrade your system to the latest package versions. If you still encounter the crash, please file a new report.

Thank you for your understanding, and sorry for the inconvenience!

[Jean-Baptiste (jean-baptiste-lab)]

Hi,

I've also seen this crash right after logging to a Blogger site. I've fixed the code for this error, I'm couldn't find a reference to this bug in the upstream bug tracker.
I've published my fixed package in my PPA, see https://launchpad.net/~jean-baptiste-lab/+archive/ppa

JB