gedit crashed with signal 5 in _XReply()

Bug #1054542 reported by Dawid Wróbel
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gedit (Ubuntu)
New
Undecided
Unassigned

Bug Description

I attempted to open a big (~2GB) binary file by mistake and that cause gedit to crash seconds after. I could not reproduce the bug on second attempt.

ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: gedit 3.5.3-0ubuntu1
ProcVersionSignature: Ubuntu 3.5.0-15.22-generic 3.5.4
Uname: Linux 3.5.0-15-generic x86_64
ApportVersion: 2.5.2-0ubuntu4
Architecture: amd64
Date: Sat Sep 22 13:19:54 2012
ExecutablePath: /usr/bin/gedit
InstallationMedia: Kubuntu 10.10 "Maverick Meerkat" - Beta amd64 (20100902.1)
ProcCmdline: gedit
Signal: 5
SourcePackage: gedit
StacktraceTop:
 ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
 ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
 _XReply () from /usr/lib/x86_64-linux-gnu/libX11.so.6
 XInternAtom () from /usr/lib/x86_64-linux-gnu/libX11.so.6
 gdk_x11_atom_to_xatom_for_display () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
Title: gedit crashed with signal 5 in _XReply()
UpgradeStatus: Upgraded to quantal on 2012-09-14 (7 days ago)
UserGroups: adm admin cdrom debian-tor dialout lp lpadmin plugdev sambashare

Revision history for this message
Dawid Wróbel (dawidw) wrote :
Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

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 #1047431, 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.

visibility: private → public
tags: removed: need-amd64-retrace
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.