gedit crashed with signal 5

Bug #1056272 reported by Mike L
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gedit (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Running Quantal development branch 64 bit with the latest updates. Seems to crash when I attempt to either Open a New Window or Open a New Document from the Unity quicklist for gedit.

ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: gedit 3.5.3-0ubuntu1
Uname: Linux 3.5.4-030504-generic x86_64
ApportVersion: 2.5.2-0ubuntu4
Architecture: amd64
CrashCounter: 1
Date: Tue Sep 25 11:42:23 2012
Disassembly: => 0x7f271516bdef: Cannot access memory at address 0x7f271516bdef
ExecutablePath: /usr/bin/gedit
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120905.2)
ProcCmdline: gedit /media/username/PATRIOT/Documents/Text/Passwords.txt
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
Signal: 5
SourcePackage: gedit
Stacktrace:
 #0 0x00007f271516bdef in ?? ()
 No symbol table info available.
 Cannot access memory at address 0x7fffab12b6b0
StacktraceTop: ?? ()
ThreadStacktrace:
 .
 Thread 4 (LWP 13340):
 #0 0x00007f2714c100fe in ?? ()
 No symbol table info available.
 Cannot access memory at address 0x7f27077fdb40
Title: gedit crashed with signal 5
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers

Revision history for this message
Mike L (mikerl) wrote :
visibility: private → public
Revision history for this message
Apport retracing service (apport) wrote :

Stacktrace:
 #0 0x00007f271516bdef in ?? ()
 No symbol table info available.
 Cannot access memory at address 0x7fffab12b6b0
StacktraceSource: #0 0x00007f271516bdef in ?? ()
StacktraceTop: ?? ()
ThreadStacktrace:
 .
 Thread 4 (LWP 13340):
 #0 0x00007f2714c100fe in ?? ()
 No symbol table info available.
 Cannot access memory at address 0x7f27077fdb40

Changed in gedit (Ubuntu):
status: New → Invalid
Revision history for this message
Apport retracing service (apport) wrote : Crash report cannot be processed

Thank you for your report!

However, processing it in order to get sufficient information for the
developers failed (it does not generate a useful symbolic stack trace). This
might be caused by some outdated packages which were installed on your system
at the time of the report:

outdated debug symbol package for initscripts: package version 2.88dsf-13.10ubuntu13 dbgsym version 2.88dsf-13.10ubuntu11.1
outdated debug symbol package for libtxc-dxtn-s2tc0: package version 0~git20110809-3 dbgsym version 0~git20110809-2.1

Please upgrade your system to the latest package versions. If you still
encounter the crash, please file a new report.

Thank you for your understanding, and sorry for the inconvenience!

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.