drivel crashed with SIGFPE in g_cclosure_marshal_VOID__BOXED()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
drivel (Ubuntu) |
Invalid
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: drivel
Blogger 1.0 account
ProblemType: Crash
DistroRelease: Ubuntu 10.04
Package: drivel 3.0.0-2
ProcVersionSign
Uname: Linux 2.6.32-21-generic i686
Architecture: i386
CheckboxSubmission: 04800874e8e4cef
CheckboxSystem: d00f84de8a55581
Date: Fri Apr 16 19:13:54 2010
ExecutablePath: /usr/bin/drivel
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
ProcCmdline: drivel
ProcEnviron:
PATH=(custom, user)
LANG=en_GB.utf8
SHELL=/bin/bash
Signal: 8
SourcePackage: drivel
StacktraceTop:
?? ()
g_cclosure_
g_closure_invoke () from /usr/lib/
?? () from /usr/lib/
g_signal_
Title: drivel crashed with SIGFPE in g_cclosure_
UserGroups: adm admin cdrom dialout libvirtd lpadmin plugdev sambashare src
Lots of irrelevant content, one incomplete stracktrace that only puts the blame on libsoup2.4 or some server response chunk. Once again, no effort to get this reported upstream where I might actually be able to do something with it, not even a Debian bug report or a notification to me that the bug even existed.
As it's described as Blogger 1.0, I can only assume this is a useless duplicate of an old upstream bug which IS fixed in 3.0.1-1. Closing.