GNOME Bugzilla – Bug 563676
Changing signature crashes Evolution
Last modified: 2008-12-08 13:00:00 UTC
Steps to reproduce: 1. Go into one account, try to change signature 2. Observe the crash Stack trace: 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) handle SIG33 pass nostop noprint Signal Stop Print Pass to program Description SIG33 No No Yes Real-time event 33 (gdb) set pagination 0 (gdb) run Starting program: /usr/bin/evolution [Thread debugging using libthread_db enabled] [New Thread 0xb6324940 (LWP 10131)] evolution-shell-Message: Killing old version of evolution-data-server... ** (evolution:10131): DEBUG: mailto URL command: evolution %s ** (evolution:10131): DEBUG: mailto URL program: evolution [New Thread 0xb5a3fb90 (LWP 10158)] [Thread 0xb5a3fb90 (LWP 10158) exited] [New Thread 0xb523eb90 (LWP 10159)] [Thread 0xb523eb90 (LWP 10159) exited] [New Thread 0xb523eb90 (LWP 10160)] [New Thread 0xb5a3fb90 (LWP 10161)] [New Thread 0xb4a0ab90 (LWP 10162)] [Thread 0xb4a0ab90 (LWP 10162) exited] [New Thread 0xb4a0ab90 (LWP 10163)] [New Thread 0xb4115b90 (LWP 10164)] [New Thread 0xb3914b90 (LWP 10165)] [New Thread 0xb304eb90 (LWP 10166)] [Thread 0xb304eb90 (LWP 10166) exited] [New Thread 0xb304eb90 (LWP 10167)] [Thread 0xb3914b90 (LWP 10165) exited] [Thread 0xb523eb90 (LWP 10160) exited] [Thread 0xb5a3fb90 (LWP 10161) exited] [Thread 0xb4115b90 (LWP 10164) exited] [New Thread 0xb5a3fb90 (LWP 10183)] [New Thread 0xb4115b90 (LWP 10184)] [Thread 0xb304eb90 (LWP 10167) exited] [New Thread 0xb304eb90 (LWP 10186)] [New Thread 0xb523eb90 (LWP 10187)] [New Thread 0xb3914b90 (LWP 10190)] [Thread 0xb3914b90 (LWP 10190) exited] [Thread 0xb523eb90 (LWP 10187) exited] [New Thread 0xb523eb90 (LWP 10197)] [Thread 0xb5a3fb90 (LWP 10183) exited] (evolution:10131): Gtk-WARNING **: GtkSpinButton: setting an adjustment with non-zero page size is deprecated (evolution:10131): Gtk-WARNING **: GtkSpinButton: setting an adjustment with non-zero page size is deprecated (evolution:10131): Gtk-WARNING **: GtkSpinButton: setting an adjustment with non-zero page size is deprecated (evolution:10131): Gtk-WARNING **: GtkSpinButton: setting an adjustment with non-zero page size is deprecated (evolution:10131): Gtk-WARNING **: GtkSpinButton: setting an adjustment with non-zero page size is deprecated (evolution:10131): Gtk-WARNING **: GtkSpinButton: setting an adjustment with non-zero page size is deprecated (evolution:10131): Gtk-WARNING **: GtkSpinButton: setting an adjustment with non-zero page size is deprecated (evolution:10131): Gtk-WARNING **: GtkSpinButton: setting an adjustment with non-zero page size is deprecated (evolution:10131): Gtk-WARNING **: GtkSpinButton: setting an adjustment with non-zero page size is deprecated (evolution:10131): Gtk-WARNING **: GtkSpinButton: setting an adjustment with non-zero page size is deprecated (evolution:10131): Gtk-WARNING **: GtkSpinButton: setting an adjustment with non-zero page size is deprecated [Thread 0xb4a0ab90 (LWP 10163) exited] (evolution:10131): e-data-server-CRITICAL **: e_account_set_string: assertion `ea != NULL' failed Program received signal SIGSEGV, Segmentation fault.
+ Trace 210599
Thread 3056748864 (LWP 10131)
Thread 1 (Thread 0xb6324940 (LWP 10131))
The program is running. Exit anyway? (y or n) Other information: This problem I think started when I changed name of a signature. That made Evolution crash. Right now I cannot rename signatures either without problem.
$ apt-cache policy evolution evolution: Installed: 2.24.2-0ubuntu1 Candidate: 2.24.2-0ubuntu1 Version table: *** 2.24.2-0ubuntu1 0 500 http://se.archive.ubuntu.com intrepid-updates/main Packages 100 /var/lib/dpkg/status 2.24.1-0ubuntu2 0 500 http://se.archive.ubuntu.com intrepid/main Packages
Thanks for taking the time to report this bug. This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade. *** This bug has been marked as a duplicate of 560188 ***