bug 424099 has the crash *before* applying my proposed e-i fix, so it will not help me here. I need the crash with my fix in place, so that I can follow the backtrace. I checked the build logs, and the fix is indeed being applied.
One thing you can do: please verify if under /var/crash you have *any* files matching the pattern '*evolution-indicator*'. If you do:
1. please remove these files;
2. run 'sudo force_start=1 /etc/init.d/apport restart' to enable apport crash triggering on Jaunty;
3. repeat the error. Apport should trigger, and offer to report the bug. Please do so, and give me the bug number.
Additionally, if you want to try local debugging: the easiest way would be, after the crash (and after submitting the new bug), to run 'sudo apport-retrace -g /var/crash/<whatever is the crash file name>'. This will open GDB, and you can then execute:
bug 424099 has the crash *before* applying my proposed e-i fix, so it will not help me here. I need the crash with my fix in place, so that I can follow the backtrace. I checked the build logs, and the fix is indeed being applied.
One thing you can do: please verify if under /var/crash you have *any* files matching the pattern '*evolution- indicator* '. If you do:
1. please remove these files;
2. run 'sudo force_start=1 /etc/init.d/apport restart' to enable apport crash triggering on Jaunty;
3. repeat the error. Apport should trigger, and offer to report the bug. Please do so, and give me the bug number.
Additionally, if you want to try local debugging: the easiest way would be, after the crash (and after submitting the new bug), to run 'sudo apport-retrace -g /var/crash/ <whatever is the crash file name>'. This will open GDB, and you can then execute:
bt full
and
thread apply all bt full
and give me the output.
Thank you.