Sorry, but I think you have missed to understand what happened here... There is no .crash file to be sent because apport has nothing to send automatically, because it never detected an error, because the session has crashed so completely, even apport was halt.
I am on lucid, fully up-to-date, not yet stable release, soon to be released, and apport is always on (and can get a bit annoying trying to send errors all the time anyway). I had to restart the session with ctrl+alt+bkspc every time, and apport never even mentioned something to be sent, thats why there is no .crash file. This seems to me not only a real bug, but a perfectly valid one, since the crash was so major that the trustworthy systems we have learned to rely on (apport) to help the development of Ubuntu haven't even blinked. I will try to locate a relevant file in the /var/crash, but have in mind it might not be there, which does not automatically means that nothing went wrong and that is not a valid bug report. Em Ter, 2010-04-06 às 12:23 +0000, Pedro Villavicencio escreveu: > Thank you for taking the time to report this bug and helping to make > Ubuntu better. However, your crash report is either missing or > challenging to deal with as a ".crash" file. Please follow these > instructions to have apport report a new bug about your crash that can > be dealt with by the automatic retracer. > > If you are running the Ubuntu Stable Release you might need to enable > apport in /etc/default/apport and restart. > > If you are using Ubuntu with the Gnome desktop environment - launch nautilus > and navigate to your /var/crash directory and double click on the crash > report you wish to submit. > If you are using Kubuntu or Xubuntu you can file the crash using > /usr/share/apport/apport-qt --crash-file=/var/crash/_my_crash_report.crash in > a terminal - where _my_crash_report.crash is the crash you would like to > report. > > I'm closing this bug report since the process outlined above will > automatically open a new bug report which can then dealt with more > efficiently. Thanks in advance for your cooperation and understanding. > > ** Changed in: evolution (Ubuntu) > Importance: Undecided => Medium > > ** Changed in: evolution (Ubuntu) > Status: New => Invalid > -- Fábio Leitão ..-. .- -... .. --- .-.. . .. - .- --- ...-.- -- evolution calendar cranshed when adding task on a particular time https://bugs.launchpad.net/bugs/555539 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
