gedit hangs and eats 100% CPU

[Teo]

These steps systematically make gedit hang and eat up 100% CPU forever, 100% of the times:

- open a text file in gedit by double clicking on it in Nautilus
- open your email client (I use Thunderbird) and open a message that has a text file attachment
- from the email client, open the attachment and choose to open it in gedit
-> This opens a separate gedit window, which is in itself a bug but a separate one
- From the latest Gedit window, click on the tab corresponding to the only open file (the one from the mail attachment) and try to drag it into the other gedit window

=> You won't be able to complit the drag-n-drop: gedit will stop responding and start eating up all CPU.

Obviously, you'll be forced to kill Gedit, and if you have unsaved document you'll loose all the data. Thanks, Gedit.

Note that if you open two files from your filesystem into 2 separate Gedit window and try to drag one from one window to the other it does work. It only hangs when dragging a file that has been opened from an email attachment, or maybe also in other cases I haven't found out.

ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: gedit 3.2.3-0ubuntu0.1
ProcVersionSignature: Ubuntu 3.0.0-16.29-generic 3.0.20
Uname: Linux 3.0.0-16-generic i686
NonfreeKernelModules: nvidia
ApportVersion: 1.23-0ubuntu4
Architecture: i386
Date: Tue Mar 6 22:12:24 2012
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
ProcEnviron:
 PATH=(custom, user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: gedit
UpgradeStatus: Upgraded to oneiric on 2011-12-07 (90 days ago)

[Vadim Rutkovsky (roignac)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 880962, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find.