gedit crashed with signal 5 in _XReply()

[Domen Vrankar]

Ubuntu 12.10 beta 1, gnome-shell

I've had three files opened (one with 15k+ lines that was saved, one with a bit less than 10k lines that was a new file - never saved and one smaller file) from local hard drive.
Then I opened filezilla, connected to a remote server and opened the file for viewing/editing with right mouse button.
File hasn't opened so I went into gnome-shell activitis menu and at that point gedit crashed.
After I reopened gedit and tried to reproduce the bug the file opened without a problem so I wasn't able to reproduce it.

ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: gedit 3.5.2-0ubuntu1
ProcVersionSignature: Ubuntu 3.5.0-14.16-generic 3.5.3
Uname: Linux 3.5.0-14-generic i686
ApportVersion: 2.5.1-0ubuntu7
Architecture: i386
Date: Wed Sep 12 15:11:48 2012
ExecutablePath: /usr/bin/gedit
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012)
ProcCmdline: gedit /home/username/Downloads/SKYPE/_log2/exception.log
ProcEnviron:
 LANGUAGE=en_US:en
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
Signal: 5
SourcePackage: gedit
StacktraceTop:
 ?? () from /usr/lib/i386-linux-gnu/libX11.so.6
 ?? () from /usr/lib/i386-linux-gnu/libX11.so.6
 _XReply () from /usr/lib/i386-linux-gnu/libX11.so.6
 XInternAtom () from /usr/lib/i386-linux-gnu/libX11.so.6
 gdk_x11_atom_to_xatom_for_display () from /usr/lib/i386-linux-gnu/libgdk-3.so.0
Title: gedit crashed with signal 5 in _XReply()
UpgradeStatus: Upgraded to quantal on 2012-09-06 (6 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

[Apport retracing service (apport)]

Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1047985, so 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. Please continue to report any other bugs you may find.