gedit crashed with signal 5 in _XReply()

Bug #1050183 reported by gothicboy
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gedit (Ubuntu)
New
Undecided
Unassigned

Bug Description

gedit was already opened. It crashed when I tried opening another txt document

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: Thu Sep 13 07:33:32 2012
ExecutablePath: /usr/bin/gedit
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 (20120423)
ProcCmdline: gedit
ProcEnviron:
 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: No upgrade log present (probably fresh install)
UserGroups: adm cdrom debian-tor dip lpadmin plugdev sambashare sudo
XsessionErrors:
 (gedit:4344): Gdk-ERROR **: The program 'gedit' received an X Window System error.
 The error was 'BadWindow (invalid Window parameter)'.
   (Details: serial 251 error_code 3 request_code 18 minor_code 0)
 (gedit:5557): GLib-CRITICAL **: the GVariant format string `(u)' has a type of `(u)' but the given value has a type of `(s)'
 (gedit:5557): GLib-CRITICAL **: g_variant_get: assertion `valid_format_string (format_string, TRUE, value)' failed

Revision history for this message
gothicboy (victor84ro) 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 #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.

visibility: private → public
tags: removed: need-i386-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.