GNOME Bugzilla – Bug 542145
Evolution Mail and Calendar: After backing up with th...
Last modified: 2009-05-14 05:05:17 UTC
After backing up with the restart option Evolution reports a crash. If this is legitimate (it finds itself restarting an unterminated session) it might be worth adding a sentence to the message saying that this should only happen if the user is restarting after a backup. Or rethink the whole message.... or the strategy.... Cheers Chris. Distribution: Ubuntu 8.04 (hardy) Gnome Release: 2.22.2 2008-06-03 (Ubuntu) BugBuddy Version: 2.22.0
See also https://bugs.launchpad.net/bugs/223216
Thanks for taking the time to report this bug. Without a stack trace from the crash it's very hard to determine what caused it. Can you get us a stack trace? Please see http://live.gnome.org/GettingTraces for more information on how to do so. Thanks in advance!
Seems I can't: System-Administration-Synaptic Install evolution.dbg Open Evolution File-backup settings-Save with default file name Are you sure.... Restart is ticked, Yes Backing up .... Evolution Crash Detection Window: Evolution appears to have exited unexpectedly ... As a precautionary measure ... You can restore Choice is Ignore/Recover Select Ignore Evolution opens normally. Bug buddie not triggered. Email all seems OK. Some deletes I thought I had done are still showing as undeleted. Delete the emails (old ones on bug thread 223216) Backup again: File-Backup Settings-Save with default file name Are you sure.... Restart is ticked, Yes Backing up .... Evolution Crash Detection Window: Evolution appears to have exited unexpectedly ... As a precautionary measure ... You can restore Choice is Ignore/Recover Select Recover Evolution opens normally. Bug buddie not triggered. Email all seems OK. Some deletes I thought I had done are still showing as undeleted. Terminate this user log. Summary: Doesn't seem to have really crashed. Ignore/Recover choice seems immaterial. Bug buddy is not triggered /var/crash is empty. Cheers Chris
Please provide a gdb stacktrace then, it's also explained in the Details link on that webpage
Following the instructions: Recover trace when getting the 'crashed' message: u1@ubuntu2:~$ gdb evolution GNU gdb 6.8-debian Copyright (C) 2008 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "i486-linux-gnu"... (gdb) run Starting program: /usr/bin/evolution [Thread debugging using libthread_db enabled] [New Thread 0xb6575740 (LWP 6463)] Program exited normally. (gdb) thread apply all bt No registers. (gdb) bt No stack. (gdb) Quit (gdb) http://live.gnome.org/%5B#special-circumstances does not exist Try again but this time recover the trace at the evolution warning: 'do you want to stop evolution' message: u1@ubuntu2:~$ gdb evolution GNU gdb 6.8-debian Copyright (C) 2008 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "i486-linux-gnu"... (gdb) run Starting program: /usr/bin/evolution [Thread debugging using libthread_db enabled] [New Thread 0xb65ed740 (LWP 6618)] [New Thread 0xb4cedb90 (LWP 6626)] [New Thread 0xb44e2b90 (LWP 6627)] [Thread 0xb44e2b90 (LWP 6627) exited] [New Thread 0xb44e2b90 (LWP 6628)] [New Thread 0xb3cdfb90 (LWP 6629)] [New Thread 0xb34d5b90 (LWP 6630)] [New Thread 0xb2cd4b90 (LWP 6631)] [Thread 0xb2cd4b90 (LWP 6631) exited] [New Thread 0xb2cd4b90 (LWP 6632)] [Thread 0xb4cedb90 (LWP 6626) exited] [Thread 0xb34d5b90 (LWP 6630) exited] [Thread 0xb2cd4b90 (LWP 6632) exited] [New Thread 0xb2cd4b90 (LWP 6636)] [New Thread 0xb34d5b90 (LWP 6637)] [New Thread 0xb4cedb90 (LWP 6638)] [Thread 0xb34d5b90 (LWP 6637) exited] [Thread 0xb4cedb90 (LWP 6638) exited] [New Thread 0xb4cedb90 (LWP 6641)] [Thread 0xb3cdfb90 (LWP 6629) exited] [Thread 0xb2cd4b90 (LWP 6636) exited] [Thread 0xb4cedb90 (LWP 6641) exited] [New Thread 0xb4cedb90 (LWP 6642)] [New Thread 0xb2cd4b90 (LWP 6643)] [Thread 0xb2cd4b90 (LWP 6643) exited] [Thread 0xb4cedb90 (LWP 6642) exited] [New Thread 0xb4cedb90 (LWP 6644)] [New Thread 0xb2cd4b90 (LWP 6645)] [Thread 0xb2cd4b90 (LWP 6645) exited] [Thread 0xb4cedb90 (LWP 6644) exited] Program received signal SIGINT, Interrupt. [Switching to Thread 0xb65ed740 (LWP 6618)] 0xb7fa1410 in __kernel_vsyscall () (gdb) thread apply all bt
+ Trace 202585
Thread 1 (Thread 0xb65ed740 (LWP 6618))
Any use? I still think the 'crashed' message is suspect. Cheers Chris
> Program exited normally. This means that there was no crash. > http://live.gnome.org/%5B#special-circumstances does not exist No idea what that link is about. Providing at least a bit of context would make things a lot easier. The second trace is a bit more useful but misses a lot of symbols. can you please install debug packages for gtk2, glib, bonobo and orbit2 and provide a better trace?
Andre: 1. My route to the web page: Can you get us a stack trace? Please see http://live.gnome.org/GettingTraces GettingTraces/Details > http://live.gnome.org/GettingTraces/Details GDB for a program that is not yet running: <quote>If that does not work (meaning that you don't get any output--this may be the case in programs which are not multi-threaded), type bt instead. If you still do not have any output, read this note] about obtaining a stack trace under special circumstances. </quote> read this note > http://live.gnome.org/%5B#special-circumstances - does not exist. OK - I've just noticed the unbalanced square brackets. It's a web page error. I will report the error. I don't think it makes any difference here. The link then takes me to places that are out of my depth. 2. more debug: gtk2.dbg not in the Ubuntu Hardy repository? glib.dbg not in the Ubuntu Hardy repository? bonobo.dbg not in the Ubuntu Hardy repository? orbit2.dbg not in the Ubuntu Hardy repository? I may be getting out of my depth here too. But since the only meaningful trace so far comes at the point at which the user is asked to confirm the closure associated with the backup there is no crash at that stage. The 'crash report' is issued when Evolution restarts. So when { Evolution a) freezes all activity to make the backup, then b) closes down } it does so in a way that leaves a situation recognised as an unclean shutdown. Since restarting manually makes no difference, I have backed up without automatic restart then started Evolution in gdb to get a trace of the start: =================================================================== Restarting after a backup, trace stopped at the 'crashed' message: u1@ubuntu2:~$ gdb evolution GNU gdb 6.8-debian Copyright (C) 2008 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "i486-linux-gnu"... (gdb) run Starting program: /usr/bin/evolution [Thread debugging using libthread_db enabled] [New Thread 0xb65ee740 (LWP 6543)] [New Thread 0xb4ceeb90 (LWP 6556)] [New Thread 0xb44e3b90 (LWP 6557)] [Thread 0xb44e3b90 (LWP 6557) exited] [Thread 0xb4ceeb90 (LWP 6556) exited] [New Thread 0xb4ceeb90 (LWP 6576)] [New Thread 0xb44e3b90 (LWP 6577)] [New Thread 0xb39dcb90 (LWP 6578)] [Thread 0xb39dcb90 (LWP 6578) exited] [New Thread 0xb39dcb90 (LWP 6581)] [Thread 0xb44e3b90 (LWP 6577) exited] [Thread 0xb4ceeb90 (LWP 6576) exited] [Thread 0xb39dcb90 (LWP 6581) exited] Program received signal SIGINT, Interrupt. [Switching to Thread 0xb65ee740 (LWP 6543)] 0xb7fa2410 in __kernel_vsyscall () (gdb) thread apply all bt
+ Trace 202698
Thread 1 (Thread 0xb65ee740 (LWP 6543))
Does it help? It seems to me that the backup leads to an unclean shutdown that then generates the spurious(?) message when restarting. Does this happen to other users? Chris
(In reply to comment #7) > 2. more debug: > gtk2.dbg not in the Ubuntu Hardy repository? > glib.dbg not in the Ubuntu Hardy repository? > bonobo.dbg not in the Ubuntu Hardy repository? > orbit2.dbg not in the Ubuntu Hardy repository? the names under Ubuntu are libglib2.0-0-dbg, libgtk2.0-0-dbg, don't know for the other two ones, you probably need to find out...\ Sorry, not using Ubuntu myself, their naming conventions always confuse me.
Hi Andre. Sorry I'm so slow with all this. OK - I've installed the following: libgail-gnome-dbg (version 1.20.0-1) will be installed libglib2.0-0-dbg (version 2.16.3-1ubuntu3) will be installed libgtk2.0-0-dbg (version 2.12.9-3ubuntu4) will be installed python-dbg (version 2.5.2-0ubuntu1) will be installed python-pyorbit-dbg (version 2.14.3-2ubuntu1) will be installed python2.5-dbg (version 2.5.2-2ubuntu4) will be installed I will start evolution, do a backup with restart, and let the 'evolution crashed' message appear: Here goes: u1@ubuntu2:~$ gdb evolution GNU gdb 6.8-debian Copyright (C) 2008 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "i486-linux-gnu"... (gdb) run Starting program: /usr/bin/evolution [Thread debugging using libthread_db enabled] [New Thread 0xb655a740 (LWP 9789)] [New Thread 0xb4c5ab90 (LWP 9797)] [New Thread 0xb444fb90 (LWP 9798)] [Thread 0xb444fb90 (LWP 9798) exited] [New Thread 0xb444fb90 (LWP 9799)] [New Thread 0xb3c4cb90 (LWP 9800)] [New Thread 0xb3442b90 (LWP 9801)] [New Thread 0xb2c41b90 (LWP 9802)] [Thread 0xb2c41b90 (LWP 9802) exited] [New Thread 0xb2c41b90 (LWP 9803)] [Thread 0xb4c5ab90 (LWP 9797) exited] [Thread 0xb3442b90 (LWP 9801) exited] [Thread 0xb2c41b90 (LWP 9803) exited] [New Thread 0xb2c41b90 (LWP 9806)] [New Thread 0xb3442b90 (LWP 9807)] [New Thread 0xb4c5ab90 (LWP 9808)] [Thread 0xb3442b90 (LWP 9807) exited] [Thread 0xb4c5ab90 (LWP 9808) exited] [New Thread 0xb4c5ab90 (LWP 9811)] [Thread 0xb3c4cb90 (LWP 9800) exited] [Thread 0xb2c41b90 (LWP 9806) exited] [Thread 0xb4c5ab90 (LWP 9811) exited] [New Thread 0xb4c5ab90 (LWP 9812)] [New Thread 0xb2c41b90 (LWP 9813)] [Thread 0xb2c41b90 (LWP 9813) exited] [Thread 0xb4c5ab90 (LWP 9812) exited] [New process 9789] Executing new program: /usr/lib/evolution/2.22/evolution-backup warning: Cannot initialize thread debugging library: generic error warning: Cannot initialize thread debugging library: generic error warning: Cannot initialize thread debugging library: generic error warning: Cannot initialize thread debugging library: generic error [New process 9789] [Thread debugging using libthread_db enabled] ** Message: Backing up to the folder /home/u1/evolution-backup.tar.gz Segmentation fault u1@ubuntu2:~$ ** Message: evolution --force-shutdown Shutting down evolution-exchange-storage (Evolution Calendar Exchange backend / Evolution Addressbook Exchange backend) Shutting down evolution-data-server-2.22 (Evolution Calendar file and webcal backend / Evolution Addressbook file backend) Shutting down evolution-alarm-notify (Evolution Calendar alarm notification service) ** Message: gconftool-2 --dump /apps/evolution > $HOME/.evolution/backup-restore-gconf.xml ** Message: cd $HOME && tar cf - .evolution .camel_certs | gzip > /home/u1/evolution-backup.tar.gz tar: .camel_certs: Cannot stat: No such file or directory tar: Error exit delayed from previous errors ** Message: evolution u1@ubuntu2:~$ I tried to Ctrl-C after ** Message: evolution while the 'evolution has crashed' dialogue box was waiting for a response from me, but gdb just exited on me. Does this help? Chris
Ubuntu Hardy has just issued an update and it looks as if the problem has gone away. I will continue to check on a daily basis. I suggest we close this, to be reopened if it is reported again. The update mentioned fixing crashes due to missing files. Chris
Backup and restart worked again today without a crash. Strangely, whilst most of the dealings in the pre-backup session were properly recorded after the backup and restart, mails read in the current folder (and displayed as read when backup started) were reset to unread after the restart. I will raise it as a separate bug if it proves 'reproducible'. The crash issue seems to have been resolved elsewhere ... Chris
closing as per comment#11.