gedit crashed with signal 5 in _XReply()

Bug #1047985 reported by Omid Mottaghi
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
gedit (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

run gedit, force it to quit! (cannot reproduce it!)

ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: gedit 3.5.2-0ubuntu1
ProcVersionSignature: Ubuntu 3.5.0-14.15-generic 3.5.3
Uname: Linux 3.5.0-14-generic i686
ApportVersion: 2.5.1-0ubuntu7
Architecture: i386
Date: Sat Sep 8 23:18:31 2012
ExecutablePath: /usr/bin/gedit
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012)
ProcCmdline: gedit
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-04 (4 days ago)
UserGroups: adm admin cdrom debian-tor dialout fuse libvirtd lpadmin plugdev sambashare

Revision history for this message
Omid Mottaghi (omidmottaghi) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 XInternAtom (dpy=0xa0ad4d0, name=name@entry=0x9e32258 "_NET_SUPPORTING_WM_CHECK", onlyIfExists=onlyIfExists@entry=0) at ../../src/IntAtom.c:181
 gdk_x11_atom_to_xatom_for_display (atom=0x85, display=0x9c943e0) at /build/buildd/gtk+3.0-3.5.16/./gdk/x11/gdkproperty-x11.c:244
 gdk_x11_atom_to_xatom_for_display (display=0x9c943e0, atom=0x85) at /build/buildd/gtk+3.0-3.5.16/./gdk/x11/gdkproperty-x11.c:221
 gdk_x11_get_xatom_by_name_for_display (display=display@entry=0x9c943e0, atom_name=atom_name@entry=0xb70a7ea0 "_NET_SUPPORTING_WM_CHECK") at /build/buildd/gtk+3.0-3.5.16/./gdk/x11/gdkproperty-x11.c:460
 get_net_supporting_wm_check (screen=screen@entry=0x9ae9160, window=193) at /build/buildd/gtk+3.0-3.5.16/./gdk/x11/gdkscreen-x11.c:1284

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : StacktraceSource.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in gedit (Ubuntu):
importance: Undecided → Medium
tags: removed: need-i386-retrace
tags: added: running-unity
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in gedit (Ubuntu):
status: New → Confirmed
Jeremy Bícha (jbicha)
visibility: private → public
Revision history for this message
jerrylamos (jerrylamos) wrote :

Reliably crashes for me. Display a file in "Files" or Pmanfm, then do gedit filename
The Display window disappears, a crash report may be generated, and the gedit filename never occurs.

leafpad filename works fine.

In previous releases, the gedit filename would open a new tab in the Display window. Instead, crash. Looking at the bug as a black box, opening the new tab is when the crash occurs.

Jerry

Revision history for this message
jerrylamos (jerrylamos) wrote :

Oh, I was running LXDE in comment #7. I can run either desktop for bug evaluations, just log on to one or the other. Last I checked that still worked. My bug with crash report is #1051976.

tags: added: bugpattern-needed
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.