GNOME Bugzilla – Bug 329450
Crash on IM switch ... (was already reported earlier)
Last modified: 2007-01-27 00:02:12 UTC
Distribution: Debian 3.1 (sarge) Package: gnome-terminal Severity: Normal Version: GNOME2.12.2 2.12.0 Gnome-Distributor: Debian Synopsis: Crash on IM switch ... (was already reported earlier) Bugzilla-Product: gnome-terminal Bugzilla-Component: general Bugzilla-Version: 2.12.0 BugBuddy-GnomeVersion: 2.0 (2.12.0) Description: Description of the crash: Steps to reproduce the crash: 1. 2. 3. Expected Results: How often does this happen? Always! Additional Information: Debugging Information: Backtrace was generated from '/usr/bin/gnome-terminal' (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 -1225406784 (LWP 16240)] [New Thread -1235616848 (LWP 16243)] 0xffffe410 in __kernel_vsyscall ()
+ Trace 65813
Thread 1 (Thread -1225406784 (LWP 16240))
------- Bug created by bug-buddy at 2006-02-01 12:00 ------- Unknown version 2.12.0 in product gnome-terminal. Setting version to "2.12.x".
*** Bug 329466 has been marked as a duplicate of this bug. ***
This has got fixed a little while ago on HEAD. Revision 17218 - (view) (download) (as text) - [select for diffs] Modified Fri Jan 26 13:31:35 2007 UTC (10 hours, 7 minutes ago) by mitch File length: 52117 byte(s) Diff to previous 16648 2007-01-26 Michael Natterer <mitch@imendio.com> * modules/input/gtkimcontextxim.c (gtk_im_context_xim_finalize): destroy the XIM only if it exists. While the code does look safe in general, there can be corner cases where the "reconnecting" boolean being FALSE does not correspond to the XIM being allocated (fix taken from maemo-gtk). Moving to gtk+, so that they ffeel compelled to fix this in the stable branch too ;-)
Fixed in both branches now.