GNOME Bugzilla – Bug 377212
crash in Passwords and Encryption Keys: When creating a new PGP ...
Last modified: 2006-11-29 01:39:07 UTC
What were you doing when the application crashed? When creating a new PGP key, this crash happens if the passphrase is more than 15 characters long... it's a phrase, not a word... remember! Distribution: Slackware Slackware 11.0.0 Gnome Release: 2.16.1 2006-11-02 (Dropline GNOME) BugBuddy Version: 2.16.0 Memory status: size: 33378304 vsize: 0 resident: 33378304 share: 0 rss: 14471168 rss_rlim: 0 CPU usage: start_time: 1163980845 rtime: 0 utime: 48 stime: 0 cutime:46 cstime: 0 timeout: 2 it_real_value: 0 frequency: 0 Backtrace was generated from '/usr/bin/seahorse' (no debugging symbols found) Using host libthread_db library "/lib/tls/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1226733888 (LWP 9229)] 0xb727704e in __waitpid_nocancel () from /lib/tls/libpthread.so.0
+ Trace 87842
Thread 1 (Thread -1226733888 (LWP 9229))
Thanks for taking the time to report this bug. Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so. Thanks in advance!
I'm not really sure which packages I need to allow this to generate the debugging info you need... perhaps you can advise. BTW, I have tested this on both my boxes, one is a brand new fresh install of slackware 11/Dropline 2.16.1 and the other has been upgraded since slackware 8 and is also running the same release... Luckily this problem is 100% repeatable on both... (In reply to comment #0) > What were you doing when the application crashed? > When creating a new PGP key, this crash happens if the passphrase is more than > 15 characters long... it's a phrase, not a word... remember! > > > Distribution: Slackware Slackware 11.0.0 > Gnome Release: 2.16.1 2006-11-02 (Dropline GNOME) > BugBuddy Version: 2.16.0 > > Memory status: size: 33378304 vsize: 0 resident: 33378304 share: 0 rss: > 14471168 rss_rlim: 0 > CPU usage: start_time: 1163980845 rtime: 0 utime: 48 stime: 0 cutime:46 cstime: > 0 timeout: 2 it_real_value: 0 frequency: 0 > > Backtrace was generated from '/usr/bin/seahorse' > > (no debugging symbols found) > Using host libthread_db library "/lib/tls/libthread_db.so.1". > (no debugging symbols found) > [Thread debugging using libthread_db enabled] > [New Thread -1226733888 (LWP 9229)] > 0xb727704e in __waitpid_nocancel () from /lib/tls/libpthread.so.0 > #0 0xb727704e in __waitpid_nocancel () from /lib/tls/libpthread.so.0 > #1 0xb7f541a8 in libgnomeui_module_info_get () > from /usr/lib/libgnomeui-2.so.0 > #2 <signal handler called> > #3 0xb7165847 in raise () from /lib/tls/libc.so.6 > #4 0xb71670d9 in abort () from /lib/tls/libc.so.6 > #5 0xb72aee83 in g_logv () from /usr/lib/libglib-2.0.so.0 > #6 0x00000005 in ?? () > > Thread 1 (Thread -1226733888 (LWP 9229)): > #0 0xb727704e in __waitpid_nocancel () from /lib/tls/libpthread.so.0 > No symbol table info available. > #1 0xb7f541a8 in libgnomeui_module_info_get () > from /usr/lib/libgnomeui-2.so.0 > No symbol table info available. > #2 <signal handler called> > No symbol table info available. > #3 0xb7165847 in raise () from /lib/tls/libc.so.6 > No symbol table info available. > #4 0xb71670d9 in abort () from /lib/tls/libc.so.6 > No symbol table info available. > #5 0xb72aee83 in g_logv () from /usr/lib/libglib-2.0.so.0 > No symbol table info available. > #6 0x00000005 in ?? () > No symbol table info available. > #0 0xb727704e in __waitpid_nocancel () from /lib/tls/libpthread.so.0 >
(In reply to comment #2) > I'm not really sure which packages I need to allow this to generate the > debugging info you need... perhaps you can advise. > > BTW, I have tested this on both my boxes, one is a brand new fresh install of > slackware 11/Dropline 2.16.1 and the other has been upgraded since slackware 8 > and is also running the same release... On Slackware, you either need to compile seahorse from source with the --prefix=/usr --enable-debug flags. Please add the command line output to the stack trace. > Luckily this problem is 100% repeatable on both... I'm running CVS HEAD on Slack 11.0 DLG 2.16 and couldn't repeat the bug consistently enough to create the stack trace.
Hello again... I tested on a 100% fresh install in vmware, and I discovered that the problem happens only when run by a non-root user, and the debug output below does seem to point to the cause... hope this helps... test@slacker:~$ /usr/bin/seahorse ** (process:2524): WARNING **: can't lock memory: Cannot allocate memory WARNING: not using secure memory for passwords ** Message: init gpgme version 1.0.3 [multi-operation 0x08115A60] start [multi-operation 0x08115A60] adding part: 0x08100390 [multi-operation 0x08115A60] part complete (1): 0x08100390/(null) [multi-operation 0x08115A60] complete [multi-operation 0x08115A60] start [multi-operation 0x08115A60] adding part: 0x08100348 [multi-operation 0x08115A60] part complete (1): 0x08100348/(null) [multi-operation 0x08115A60] complete [multi-operation 0x08115AF0] start [multi-operation 0x08115AF0] adding part: 0x08115A60 [multi-operation 0x08115AF0] part complete (1): 0x08115A60/(null) [multi-operation 0x08115AF0] complete [multi-operation 0x08115AF0] start [multi-operation 0x08115AF0] adding part: 0x080EC000 [multi-operation 0x08115AF0] part complete (1): 0x080EC000/(null) [multi-operation 0x08115AF0] complete ** (process:2524): ERROR (recursed) **: file seahorse-secure-memory.c: line 114 (g_realloc): assertion failed: (seahorse_secure_memory_check (mem)) aborting...
Fixed in the development version. The fix will be available in the next major release. Thank you for your bug report. *** This bug has been marked as a duplicate of 371666 ***