zeitgeist-daemon crashed with OverflowError in call_async()

Bug #559350 reported by balaknair
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Zeitgeist Framework
Won't Fix
High
Mikkel Kamstrup Erlandsen
libzeitgeist
Fix Released
High
Michal Hruby
zeitgeist (Ubuntu)
Fix Released
Low
Unassigned

Bug Description

Binary package hint: zeitgeist

Opened Activity Journal> was browsing list of documents recently worked with, when the error message popped up stating that zeitgeist-daemon had crashed. The list of documents in the Activity Journal was still up, and still usable.

ProblemType: Crash
DistroRelease: Ubuntu 10.04
Package: zeitgeist-core 0.3.2-1
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: Fri Apr 9 21:07:20 2010
ExecutablePath: /usr/bin/zeitgeist-daemon
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Beta amd64 (20100318)
InterpreterPath: /usr/bin/python2.6
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/zeitgeist-daemon
ProcEnviron:
 SHELL=/bin/bash
 LANG=en_IN
PythonArgs: ['/usr/bin/zeitgeist-daemon']
SourcePackage: zeitgeist
Title: zeitgeist-daemon crashed with OverflowError in call_async()
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Related branches

Revision history for this message
balaknair (balaknair) wrote :
visibility: private → public
tags: removed: need-duplicate-check
Revision history for this message
Mikkel Kamstrup Erlandsen (kamstrup) wrote :

Please see this merge request from Michal in order to grok what's going on here: https://code.launchpad.net/~mhr3/libzeitgeist/various-fixes/+merge/31801

And do give a round of applause for some top notch debugging from Michal there :-D

Changed in zeitgeist:
status: New → Triaged
importance: Undecided → High
assignee: nobody → Mikkel Kamstrup Erlandsen (kamstrup)
Changed in libzeitgeist:
assignee: nobody → Michal Hruby (mhr3)
importance: Undecided → High
status: New → Triaged
Revision history for this message
Mikkel Kamstrup Erlandsen (kamstrup) wrote :

For the record: In order to close this bug in Zeitgeist (not libzg) I think we need to do as Michal suggests; wrap the monitor invocations in try-catch blocks.

Closing it in libzg is a matter of merging Michal's branch

Revision history for this message
Mikkel Kamstrup Erlandsen (kamstrup) wrote :

Looking quickly at fixinf this on the ZG side as well... I am actually afraid that this is impossible to fix inside Zeitgeist :-S

We dispatch the monitor DBus calls asynchrously, and the bug is somehow picked up very low in the stack in an async callback before it reaches Zeitgeist. Indeed I can see no Zeitgeist code in the stack trace. Also, we are actually passing in an error handler to DBus which *ought* to be invoked on errors, but apparently not, since that should simply result in a warning printed on stdout.

Changed in libzeitgeist:
status: Triaged → Fix Committed
Revision history for this message
Michal Hruby (mhr3) wrote :

@Mikkel: I'm afraid this will be different issue, the reporter states that only thing running was GAJ, and due to the date this was opened (April), it's impossible that a libzg monitor caused this. Also here's a traceback which caused the libzg bug, it's a bit more clear than this one.

Revision history for this message
Seif Lotfy (seif) wrote :

So as far as I understand here there is no way for us to fix it in Zeitgeist... I will mark this as "Won't fix" and feel free to re-open it if you disagree withe me.

Changed in zeitgeist:
status: Triaged → Won't Fix
Changed in zeitgeist (Ubuntu):
importance: Undecided → Low
Changed in libzeitgeist:
status: Fix Committed → Fix Released
Changed in zeitgeist (Ubuntu):
status: New → Fix Released
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.