drivel crashed with SIGFPE in g_cclosure_marshal_VOID__BOXED()

Bug #564850 reported by Liam
10
This bug affects 2 people
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
ProcVersionSignature: Ubuntu 2.6.32-21.31-generic 2.6.32.11+drm33.2
Uname: Linux 2.6.32-21-generic i686
Architecture: i386
CheckboxSubmission: 04800874e8e4cefd7524f0d5e8a1b2bb
CheckboxSystem: d00f84de8a555815fa1c4660280da308
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_marshal_VOID__BOXED ()
 g_closure_invoke () from /usr/lib/libgobject-2.0.so.0
 ?? () from /usr/lib/libgobject-2.0.so.0
 g_signal_emit_valist () from /usr/lib/libgobject-2.0.so.0
Title: drivel crashed with SIGFPE in g_cclosure_marshal_VOID__BOXED()
UserGroups: adm admin cdrom dialout libvirtd lpadmin plugdev sambashare src

Revision history for this message
Liam (liam-dennehy) wrote :
Revision history for this message
Neil Williams (codehelp) wrote :

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.

Changed in drivel (Ubuntu):
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.