Bug 378578 – crash in Clipboard Text Encryption: Typing my PGP key for de...

After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.

Bug 378578 - crash in Clipboard Text Encryption: Typing my PGP key for de...


Summary:	crash in Clipboard Text Encryption: Typing my PGP key for de...


Status:	RESOLVED DUPLICATE of bug 371666

Product:	seahorse
Classification:	Applications
Component:	Applet
Version:	unspecified
Hardware:	Other All

Importance:	High critical
Target Milestone:	1.0.0
Assigned To:	Seahorse Maintainer
QA Contact:	Seahorse Maintainer

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2006-11-23 18:46 UTC by poeffie2
Modified:	2006-11-29 01:42 UTC

See Also:
GNOME target:	---
GNOME version:	2.15/2.16

Description poeffie2 2006-11-23 18:46:52 UTC

What were you doing when the application crashed?
Typing my PGP key for decrypting a message.


Distribution: Ubuntu 6.10 (edgy)
Gnome Release: 2.16.1 2006-10-02 (Ubuntu)
BugBuddy Version: 2.16.0

Memory status: size: 32964608 vsize: 0 resident: 32964608 share: 0 rss: 14544896 rss_rlim: 0
CPU usage: start_time: 1164308935 rtime: 0 utime: 58 stime: 0 cutime:54 cstime: 0 timeout: 4 it_real_value: 0 frequency: 0

Backtrace was generated from '/usr/libexec/seahorse-applet'

(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1226024768 (LWP 26025)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 88847

Thread 1 (Thread -1226024768 (LWP 26025))

#0 __kernel_vsyscall
#1 __waitpid_nocancel
from /lib/tls/i686/cmov/libpthread.so.0
#2 gnome_gtk_module_info_get
from /usr/lib/libgnomeui-2.so.0
#3 <signal handler called>
#4 ??
#5 ??
#6 ??
#7 ??
#8 g_closure_unref
from /usr/lib/libgobject-2.0.so.0
#9 g_cclosure_marshal_VOID__BOXED
from /usr/lib/libgobject-2.0.so.0
#10 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#11 g_signal_chain_from_overridden
from /usr/lib/libgobject-2.0.so.0
#12 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#13 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#14 _gtk_clipboard_handle_event
from /usr/lib/libgtk-x11-2.0.so.0
#15 gtk_main_do_event
from /usr/lib/libgtk-x11-2.0.so.0
#16 _gdk_events_init
from /usr/lib/libgdk-x11-2.0.so.0
#17 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#18 g_main_context_check
from /usr/lib/libglib-2.0.so.0
#19 g_main_loop_run
from /usr/lib/libglib-2.0.so.0
#20 bonobo_main
from /usr/lib/libbonobo-2.so.0
#21 bonobo_generic_factory_main_timeout
from /usr/lib/libbonobo-2.so.0
#22 bonobo_generic_factory_main
from /usr/lib/libbonobo-2.so.0
#23 panel_applet_factory_main_closure
from /usr/lib/libpanel-applet-2.so.0
#24 panel_applet_factory_main
from /usr/lib/libpanel-applet-2.so.0
#25 ??
#26 _IO_stdin_used
#27 ??
#28 ??
#29 ??
#0 __kernel_vsyscall

Comment 1 Stef Walter 2006-11-29 01:42:20 UTC

I believe this is fixed in our latest development version. This will become 0.9.8 in a few days. If you end up trying 0.9.8 and that does not fix the problem, then please feel free to reopen this bug report.

*** This bug has been marked as a duplicate of 371666 ***