GNOME Bugzilla – Bug 347226
crashes trying to GPG sign messages
Last modified: 2006-07-12 11:20:01 UTC
Steps to reproduce: 1. Write a message (new or reply) 2. Select to sign it with GPG, this has worked flawlessly before. 3. Select 'Send' and type the GPG password, select the remember password for this session box. Craaaasssh. Has to be Force Quit. Stack trace: The first part is from a freeze due to trouble restoring an email from the last crash. duncan@duncan-laptop:~$ gdb evolution GNU gdb 6.4-debian Copyright 2005 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i486-linux-gnu"...(no debugging symbols found) Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1". (gdb) run Starting program: /usr/bin/evolution (no debugging symbols found) ... (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1232200800 (LWP 7136)] (no debugging symbols found) ... (no debugging symbols found) CalDAV Eplugin starting up ... (no debugging symbols found) ... (no debugging symbols found) ---Type <return> to continue, or q <return> to quit--- (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (evolution-2.6:7136): evolution-mail-WARNING **: ignored this junk plugin: not enabled or we have already loaded one (evolution-2.6:7136): e-utils-WARNING **: Plugin 'Spamassassin junk plugin' failed to load hook 'org.gnome.evolution.mail.junk:1.0' (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (evolution-2.6:7136): camel-WARNING **: camel_exception_get_id called with NULL parameter. [New Thread -1269576784 (LWP 7141)] [New Thread -1277969488 (LWP 7142)] (no debugging symbols found) [New Thread -1286362192 (LWP 7143)] [Thread -1286362192 (LWP 7143) exited] (no debugging symbols found) [New Thread -1286362192 (LWP 7144)] [Thread -1277969488 (LWP 7142) exited] (no debugging symbols found) [New Thread -1277969488 (LWP 7148)] [New Thread -1328395344 (LWP 7149)] (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) [New Thread -1338516560 (LWP 7151)] (evolution-2.6:7136): composer-WARNING **: autosave load filename = "/home/duncan/.evolution-composer.autosave-mI72Yr" (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) [New Thread -1339429968 (LWP 7157)] (no debugging symbols found) ... (no debugging symbols found) ---Type <return> to continue, or q <return> to quit--- (no debugging symbols found) restoring draft flag 'text/plain' restoring draft flag 'pgp-sign' [New Thread -1383654480 (LWP 7187)] [Thread -1383654480 (LWP 7187) exited] thread_db_get_info: cannot get thread info: generic error (gdb) run The program being debugged has been started already. Start it from the beginning? (y or n) y Starting program: /usr/bin/evolution (no debugging symbols found) ... (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1232319584 (LWP 7222)] (no debugging symbols found) ... (no debugging symbols found) (evolution-2.6:7222): evolution-mail-WARNING **: ignored this junk plugin: not enabled or we have already loaded one (evolution-2.6:7222): e-utils-WARNING **: Plugin 'Spamassassin junk plugin' failed to load hook 'org.gnome.evolution.mail.junk:1.0' (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (evolution-2.6:7222): camel-WARNING **: camel_exception_get_id called with NULL parameter. [New Thread -1269695568 (LWP 7225)] [New Thread -1278088272 (LWP 7226)] (no debugging symbols found) [New Thread -1286480976 (LWP 7227)] [Thread -1286480976 (LWP 7227) exited] (no debugging symbols found) [Thread -1278088272 (LWP 7226) exited] [New Thread -1278088272 (LWP 7228)] (no debugging symbols found) [New Thread -1286480976 (LWP 7230)] [New Thread -1328616528 (LWP 7231)] (no debugging symbols found) (no debugging symbols found) (evolution-2.6:7222): composer-WARNING **: autosave load filename = "/home/duncan/.evolution-composer.autosave-qPAMPi" (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) [New Thread -1339425872 (LWP 7235)] [New Thread -1347818576 (LWP 7236)] (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) ---Type <return> to continue, or q <return> to quit--- (no debugging symbols found) restoring draft flag 'text/plain' restoring draft flag 'pgp-sign' [New Thread -1383793744 (LWP 7249)] [Thread -1383793744 (LWP 7249) exited] [New Thread -1383793744 (LWP 7263)] [Thread -1383793744 (LWP 7263) exited] (no debugging symbols found) (evolution-2.6:7222): camel-WARNING **: camel_exception_get_id called with NULL parameter. [New Thread -1383793744 (LWP 7264)] [Thread -1383793744 (LWP 7264) exited] [New Thread -1383793744 (LWP 7265)] [Thread -1383793744 (LWP 7265) exited] (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) [New Thread -1383793744 (LWP 7487)] [Thread -1383793744 (LWP 7487) exited] (no debugging symbols found) (no debugging symbols found) BBDB spinning up... [New Thread -1383793744 (LWP 7559)] [Thread -1383793744 (LWP 7559) exited] thread_db_get_info: cannot get thread info: generic error (gdb) Other information: Several other bugs today, maybe they're connected? 347208 347206
same here as in bug 347208 - "cannot get thread info: generic error". :-/ cannot find out what has happened here, are you able to reproduce it constantly?
Note that both bugs showing this strange gdb output are filed by the same reporter. Given that this bug never used to be an issue before (see comment 0) and the weird gdb spewage, this may be an issue either specific to Ubuntu or this particular system... Duncan, did you update your system recently?
Andre Klapper: Yes, I was reproducing it every time. Karsten Bräckelmann: Ubuntu has just shipped a new kernel. Now the problem has gone. --- I've changed it to NOT GNOME. I'll add a new backtrace if it comes back. Interesting that it happened very suddenly, and I hadn't been playing with the system at all. Strange.