> Debug output attached.
Can you run with --mono-debug and attach that output ? There is a
slight chance beagled might hang after it prints the detail stacktrace
in which case just kill -9 the process afterwards.
This is probably the evolution-sharp crash that jjohnny is working on.
I forgot the
On Sat, 2008-05-03 at 23:11 +0200, Robert Trebula wrote:
> Hi,
>
> I am the reporter. It seems that somwhow I managed not to include the
> message text for the bug.
>
> So here it goes: It crashes all the time for one user (myself), it
> doesn't crash for another user (a test user).
>
> Debug o
This seems to be a problem in some of the calendars. I would vote for
rtrebula.ics one, but you can't be pretty sure, as they're processed
asyncronously. You should try to verify that calendar for a corrupted
entry, but I don't know any util you can do for that.
Please, tell me if you could send th
Hi,
I am the reporter. It seems that somwhow I managed not to include the
message text for the bug.
So here it goes: It crashes all the time for one user (myself), it
doesn't crash for another user (a test user).
Debug output attached.
Regards,
Robert
[EMAIL PROTECTED]:~$ beagled --foregroun
4 matches
Mail list logo
