pidgin crashed with SIGSEGV in IA__gtk_text_buffer_end_user_action()

[Andrew Conkling]

Binary package hint: pidgin

Perhaps a dupe of bug #123831? I had one conversation open, was just closing it.

ProblemType: Crash
Architecture: i386
Date: Mon Jul 23 22:28:41 2007
DistroRelease: Ubuntu 7.10
ExecutablePath: /usr/bin/pidgin
NonfreeKernelModules: cdrom
Package: pidgin 1:2.0.2-0ubuntu1
PackageArchitecture: i386
ProcCmdline: pidgin
ProcCwd: /home/andrew
ProcEnviron:
 LANGUAGE=en_US.UTF-8
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=en_US.UTF-8
 SHELL=/bin/zsh
Signal: 11
SourcePackage: pidgin
StacktraceTop:
 IA__gtk_text_buffer_end_user_action (buffer=0xaaaaaaaa)
 gtk_imhtml_clipboard_get (clipboard=0x86a76e0,
 gtk_window_class_intern_init (klass=0x8844180)
 IA__gtk_marshal_VOID__POINTER_UINT (closure=0xb7ea9e1c,
 g_closure_invoke () from /usr/lib/libgobject-2.0.so.0
Title: pidgin crashed with SIGSEGV in IA__gtk_text_buffer_end_user_action()
Uname: Linux SnappyLappy 2.6.22-8-generic #1 SMP Thu Jul 12 15:59:45 GMT 2007 i686 GNU/Linux
UserGroups: adm admin audio cdrom dialout dip floppy lpadmin netdev plugdev powerdev scanner video

[Apport retracing service (apport)]

StacktraceTop:IA__gtk_text_buffer_end_user_action (buffer=0xaaaaaaaa) at /build/buildd/gtk+2.0-2.11.6/gtk/gtktextbuffer.c:4069
gtk_imhtml_clipboard_get (clipboard=0x86a76e0, selection_data=0xbfa3e49c, info=1, imhtml=0x842b188) at ../../pidgin/gtkimhtml.c:884
gtk_window_class_intern_init (klass=0x8844180) at /build/buildd/gtk+2.0-2.11.6/gtk/gtkwindow.c:756
IA__gtk_marshal_VOID__POINTER_UINT (closure=0xb7ea9e1c, return_value=0x0, n_param_values=4, param_values=0xbfa3e19c, invocation_hint=0xbfa3e07c,
IA__g_closure_invoke (closure=0x86e33f8, return_value=0x0, n_param_values=4, param_values=0xbfa3e19c, invocation_hint=0xbfa3e07c)

[Jérôme Guelfucci (jerome-guelfucci-deactivatedaccount)]

Thank you for your bug report. Have you been able to reproduce this with an up to date Ubuntu system ?

[Andrew Conkling (andrewski)]

No, this bug only occurred for me once.

[Jérôme Guelfucci (jerome-guelfucci-deactivatedaccount)]

Marking this as fixed then, thank you.