beagle-search crashes when selecting a gaim conversation

Bug #93064 reported by Andrew Conkling
14
Affects Status Importance Assigned to Milestone
beagle (Ubuntu)
Fix Released
Undecided
Kevin Kubasik

Bug Description

Binary package hint: beagle

If I get results in beagle-search for a conversation, say in Gaim, clicking on it makes beagle-search just disappear. Turns out it's crashing.

Same behavior--if not the same cause--here: http://www.mail-archive.com/dashboard-hackers%40gnome.org/msg03227.html

Unfortunately, I'm not able to reproduce a backtrace in gdb:

Program exited with code 01.
(gdb) bt
No stack.
(gdb) mono_backtrace 15
No registers.

(mono_backtrace comes from http://www.mono-project.com/Debugging#Debugging_with_GDB.)

Revision history for this message
Kevin Kubasik (kkubasik) wrote :

The solution here is not gdb, since beagle runs inside of a managed system called mono, could you just run beagle-search from the command line, and observe the crash. Then could you also attach the relivent logs from ~/.beagle/Logs ?

Changed in beagle:
status: Unconfirmed → Needs Info
Revision history for this message
Andrew Conkling (andrewski) wrote :

Well, I've been able to run Banshee through gdb with some useful results, so I had assumed the same with Beagle. (Did you see the Mono link in my original post?)

Anyhow, two file attachments are forthcoming.

Changed in beagle:
status: Needs Info → Unconfirmed
Revision history for this message
Andrew Conkling (andrewski) wrote :

Debug output on console from beagle-search.

All I did was to search for "network manager" (sans quotes) then click on an IM conversation.

Revision history for this message
Andrew Conkling (andrewski) wrote :
Revision history for this message
Andrew Conkling (andrewski) wrote :
Revision history for this message
Kevin Kubasik (kkubasik) wrote :

looks like a race case in the FS, or empty files, not much we can do beyond catch an release.

Changed in beagle:
assignee: nobody → kkubasik
status: Unconfirmed → Fix Committed
Revision history for this message
Kevin Kubasik (kkubasik) wrote :

I'm assuming that it was marked fix committed so long ago, and hasn't heard a new complaint, it was fixed.

Changed in beagle:
status: Fix Committed → Fix Released
Revision history for this message
Scott_W (d38dm8nw81k1ng) wrote :

I'm having the same problem as listed above. I assume that it's reappeared from last year. I've looked at the attached links as well and I think it's the same problem. Is there anything that can be done apart from not clicking on IM conversations?
I've attached the error output.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

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