GNOME Bugzilla – Bug 349324
Beagled hangs on indexing Gaim2 logs
Last modified: 2006-08-01 21:37:50 UTC
Please describe the problem: When indexing any Gaim log, Beagle will hang and you have to kill it and restart, because beagle-shutdown will not work. Steps to reproduce: 1. Launch beagled 2. Set up Gaim to log all chats 3. Start a chat so Gaim can log something 4. Try to query beagle, it will not respond 5. Launch beagle-status and you'll find that beagled is stuck on the log file Actual results: beagled hangs Expected results: beagle gives some results Does this happen every time? yes, I had to disable gaim logging and remove all logs to be able to use beagle again Other information: I'm on a Dapper clean install, using Gaim2.0 beta3 from an alienized Fedora4 .rpm, but it was the same with beta1 and beta2 compiled on Dapper.
update: it seems to hang either if ~/.gaim/log/ is empty, anyway when triggering the GaimLog backend.
Created attachment 69931 [details] beagle logs
Comment on attachment 69931 [details] beagle logs It hangs even with GaimLog denied, it seems due in some way to beagled-helper. Attached are the current- logs whith the daemon stopped responding.
update: removing "~/.beagle" seems to have fixed the problem.
From the logs it seemed that you are running more than one beagle simultaneously. Maybe some old instance of beagled or beagle-index-helper was still running when it happened.
Yeah, this doesn't have anything to do with gaim, this is the dreaded "lock timeout bug" that was fixed in 0.2.7. *** This bug has been marked as a duplicate of 340542 ***