gedit crashes due to "traps: gedit[5161] trap int3 ip:7f0a11d7ed30 sp:7fff54f67a90 error:0"

Bug #1422090 reported by Karl-Philipp Richter
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
gedit (Ubuntu)
Invalid
High
Unassigned

Bug Description

`gedit` simply crahes. `/var/log/syslog` contains

    [ 4193.197206] traps: gedit[5161] trap int3 ip:7f0a11d7ed30 sp:7fff54f67a90 error:0

ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: gedit 3.10.4-0ubuntu6
Uname: Linux 3.19.0-031900-generic x86_64
ApportVersion: 2.14.7-0ubuntu8.1
Architecture: amd64
CurrentDesktop: Unity
Date: Sun Feb 15 10:35:08 2015
EcryptfsInUse: Yes
InstallationDate: Installed on 2015-01-26 (19 days ago)
InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
SourcePackage: gedit
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
Karl-Philipp Richter (krichter722) wrote :
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
Changed in gedit (Ubuntu):
importance: Undecided → High
Revision history for this message
Michael Tate (mtate) wrote :

Ubuntu 14.10
3.16.0-23-generic #31-Ubuntu SMP

FYI:

I uninstalled gedit 3.10.4, and installed
  gedit_3.8.3-0ubuntu3_amd64.deb
and
  gedit-common_3.8.3-0ubuntu3_all.deb
from those packages.

I'm still seeing the error, "traps: gedit[PROC] trap int3 ip:hexxxxxxxxxx sp:hexxxxxxxxxx error:0" in dmesg. Going to try an yet older package.

Revision history for this message
Sebastien Bacher (seb128) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. However, your crash report is either missing or challenging to deal with as a ".crash" file. Please follow these instructions to have apport report a new bug about your crash that can be dealt with by the automatic retracer.

If you are running the Ubuntu Stable Release you might need to enable apport in /etc/default/apport and restart.

Now open your file manager, navigate to your /var/crash directory and open the crash report you wish to submit.
If this fails you will have to open a terminal and file your report with 'ubuntu-bug /var/crash/_my_crash_report.crash' where _my_crash_report.crash is the crash you would like to report. If you get an error that you aren't allowed to access this report you will have to file it with 'sudo ubuntu-bug /var/crash/_my_crash_report.crash'.

I'm closing this bug report since the process outlined above will automatically open a new bug report which can then dealt with more efficiently. Thanks in advance for your cooperation and understanding.

Changed in gedit (Ubuntu):
status: Confirmed → Invalid
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.