beagled crash on startup

Bug #88715 reported by Alex Zvoleff
This bug report is a duplicate of:  Bug #69902: Mono Crashes as Desktop Loads. Edit Remove
4
Affects Status Importance Assigned to Milestone
beagle (Ubuntu)
New
Undecided
Unassigned

Bug Description

Binary package hint: beagle

Right after restarting Gnome, beagled crashes. I am also running deskbar.

Revision history for this message
Alex Zvoleff (azvoleff) wrote :

Crash report attached.

Revision history for this message
MKersloot (micha-kovoks) wrote :

It just crashes every time I log in. Crash report available if necessary.

Packages:
beagle 0.2.9-1ubuntu3
beagle-backend-evolution 0.2.9-1ubuntu3
libbeagle0 0.2.9-1ubuntu3

Revision history for this message
dBera (dbera-web) wrote :

MKersloot, it will be helpful to figure why it crashes. Since you said it crashes every time you log in, after you log in (and after it has crashed), can you do the following in a terminal:

$ beagle-shutdown
$ beagled --fg

This will start beagle in the foreground, so any crash will leave important information why it crashes. Wait for 5-10 minutes, if it crashes copy the last 100 or so lines from the terminal and attach it here. If it doesnt crash, bad luck, from another terminal do a "beagle-shutdown" to stop beagle and go for your usual walk. If it doesnt crash, you might want to try it randomly a few more times later. Thanks.

Revision history for this message
dBera (dbera-web) wrote :

Or, you can follow the instructions given in http://beagle-project.org/Troubleshooting#Beagle_crashes_on_login
to collect the mono stacktrace. The mono stacktrace is necessary in finding out what is causing the crash.

Revision history for this message
MKersloot (micha-kovoks) wrote :

catching the errors does not reveal any useful information. It only shows there are recurrences in my calendar.
But in .beagle/Log there are several log-files, could these be from any interest (except showing some information about my computer ;-)

Revision history for this message
MKersloot (micha-kovoks) wrote :

I started with the --fg option and some tracing information appeared on the console. I could send this, but there is some information I don't want to appear on google. How to handle?

Revision history for this message
dBera (dbera-web) wrote :

MKersloot, when you say "catching the errors does not reveal any useful information. It only shows there are recurrences in my calendar" - I presume you are doing the "2>~/.beagle/crash" thing as mentioned in the wiki. I am still interested in the contents of that file because it should not contain the recurrence information but crash information. I check log files of some users - from the nature of the crash the crash does not seem to be related to any internal working of beagle. But please send them too, at least the most recent set of current-Beagle and current-IndexHelper.

Anyway, if you have some tracing information from "beagled --fg", that is awesome. Please email them to me personally at <email address hidden>

Thanks a ton.

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

Other bug subscribers

Bug attachments

Remote bug watches

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