gedit crashed with SIGSEGV in instance_get_window()

Bug #932375 reported by Bruno Girin on 2012-02-14
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gedit (Ubuntu)
gedit-valencia-plugin (Ubuntu)

Bug Description

Going through the Checkbox Unity Tests for Unity 5.4, got to test #120 and tried on gedit. When right-clicking on the gedit title bar and selecting close, the first time nothing happens, when doing it a second time, gedit crashes.

Steps to reproduce:
1. Start gedit
2. Right-click on the title bar
3. Select "Close": nothing happen
4. Right-click on the title bar again
5. Select "Close": gedit crashes

Expected behaviour
gedit closes on step 3

Actual behaviour
gedit crashes on step 5

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: gedit 3.3.3-0ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-16.25-generic 3.2.6
Uname: Linux 3.2.0-16-generic x86_64
ApportVersion: 1.91-0ubuntu1
Architecture: amd64
Date: Tue Feb 14 22:06:21 2012
ExecutablePath: /usr/bin/gedit
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta amd64 (20110901)
ProcCmdline: gedit
 PATH=(custom, no user)
 Segfault happened at: 0x7f9f15a300fb <instance_get_window+58>: mov (%rax),%rax
 PC (0x7f9f15a300fb) ok
 source "(%rax)" (0x00000001) not located in a known VMA region (needed readable region)!
 destination "%rax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gedit
 instance_get_window () from /usr/lib/gedit/plugins/
 instance_active_filename () from /usr/lib/gedit/plugins/
 instance_active_document_is_vala_file () from /usr/lib/gedit/plugins/
 ?? () from /usr/lib/gedit/plugins/
 ?? () from /usr/lib/gedit/plugins/
Title: gedit crashed with SIGSEGV in instance_get_window()
UpgradeStatus: Upgraded to precise on 2012-02-11 (3 days ago)
UserGroups: adm admin cdrom dialout libvirtd lpadmin plugdev sambashare

Bruno Girin (brunogirin) wrote :
Bruno Girin (brunogirin) on 2012-02-14
tags: added: 5.4-rc1

 instance_get_window () from /tmp/tmpd_yah4/usr/lib/gedit/plugins/
 instance_active_filename () from /tmp/tmpd_yah4/usr/lib/gedit/plugins/
 instance_active_document_is_vala_file () from /tmp/tmpd_yah4/usr/lib/gedit/plugins/
 ?? () from /tmp/tmpd_yah4/usr/lib/gedit/plugins/
 ?? () from /tmp/tmpd_yah4/usr/lib/gedit/plugins/

Changed in gedit (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Bruno Girin (brunogirin) wrote :

I added the gedit-valencia-plugin package as the retrace shows it crashed in libvalencia. In addition, the fact that it crashed in instance_active_document_is_vala_file() may be a hint: as far as I remember I did not have any document open when the crash occured.

visibility: private → public
Bruno Girin (brunogirin) wrote :

Reported in the Yorba redmine bug tracker:

Paul White (paulw2u) wrote :


We are sorry that we do not always have the capacity to review all reported bugs in a timely manner. You reported this bug some time ago and there have been many changes in Ubuntu since that time.

Ubuntu 12.04 (precise) reached end-of-life on April 28, 2017.

Do you still see a problem related to the one that you reported in a currently supported version of Ubuntu?

Please let us know if you do otherwise this bug report can be left to expire in approximately 60 days time.

Thank you for helping make Ubuntu better.

Paul White
[Ubuntu Bug Squad]

Changed in gedit (Ubuntu):
status: New → Incomplete
Changed in gedit-valencia-plugin (Ubuntu):
status: New → Incomplete
Launchpad Janitor (janitor) wrote :

[Expired for gedit-valencia-plugin (Ubuntu) because there has been no activity for 60 days.]

Changed in gedit-valencia-plugin (Ubuntu):
status: Incomplete → Expired
Launchpad Janitor (janitor) wrote :

[Expired for gedit (Ubuntu) because there has been no activity for 60 days.]

Changed in gedit (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers