gedit crashed with SIGSEGV in g_main_context_dispatch()

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

Bug Description

i've opened a binary file with gedit and it crash

ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: gedit 3.8.3-0ubuntu3
ProcVersionSignature: Ubuntu 3.11.0-1.4-generic 3.11.0-rc4
Uname: Linux 3.11.0-1-generic i686
ApportVersion: 2.12-0ubuntu3
Architecture: i386
Date: Tue Aug 13 15:02:36 2013
ExecutablePath: /usr/bin/gedit
InstallationDate: Installed on 2013-07-03 (41 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha i386 (20130702)
MarkForUpload: True
ProcCmdline: gedit /home/username/test
ProcEnviron:
 LANGUAGE=es_CO:es
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=es_CO.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x807cda6: mov 0x8(%eax),%eax
 PC (0x0807cda6) ok
 source "0x8(%eax)" (0xaaaaaab2) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: gedit
StacktraceTop:
 ?? ()
 ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
 g_main_context_dispatch () from /lib/i386-linux-gnu/libglib-2.0.so.0
 ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
 g_main_context_iteration () from /lib/i386-linux-gnu/libglib-2.0.so.0
Title: gedit crashed with SIGSEGV in g_main_context_dispatch()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lp lpadmin plugdev sambashare sudo

Revision history for this message
Don Forigua (ingforigua) 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 #952965, 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.

information type: 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.