gedit crashed with SIGSEGV in gedit_multi_notebook_get_active_tab()

Bug #1180665 reported by Tim on 2013-05-16
84
This bug affects 10 people
Affects Status Importance Assigned to Milestone
gedit
New
Medium
gedit (Ubuntu)
High
Unassigned

Bug Description

crashed with about 5 tabs open

ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: gedit 3.8.0-0ubuntu1~raring1 [origin: LP-PPA-gnome3-team-gnome3]
ProcVersionSignature: Ubuntu 3.9.0-1.5-generic 3.9.1
Uname: Linux 3.9.0-1-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.10.1-0ubuntu1
Architecture: amd64
Date: Thu May 16 12:26:21 2013
ExecutablePath: /usr/bin/gedit
ExecutableTimestamp: 1367295250
InstallationDate: Installed on 2012-09-23 (235 days ago)
InstallationMedia: Ubuntu GNOME Remix 12.10 "Quantal Quetzal" - Alpha amd64(20120922)
MarkForUpload: True
ProcCmdline: gedit
ProcCwd: /home/darkness
ProcEnviron:
 LANGUAGE=en_AU:en
 PATH=(custom, user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_AU.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x460076 <gedit_multi_notebook_get_active_tab+22>: cmp %rax,(%rdx)
 PC (0x00460076) ok
 source "%rax" ok
 destination "(%rdx)" (0xaaaaaaaaaaaaaaaa) not located in a known VMA region (needed writable region)!
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: gedit
StacktraceTop:
 gedit_multi_notebook_get_active_tab ()
 ?? ()
 selection_received (widget=0x1e09dd0, selection_data=0x7fffd9d55a70, time=<optimised out>) at /build/buildd/gtk+3.0-3.8.2/./gtk/gtkclipboard.c:939
 g_closure_invoke (closure=0x1fbe0e0, return_value=0x0, n_param_values=3, param_values=0x7fffd9d55720, invocation_hint=0x7fffd9d556c0) at /build/buildd/glib2.0-2.37.0/./gobject/gclosure.c:777
 signal_emit_unlocked_R (node=node@entry=0x19c8db0, detail=detail@entry=0, instance=instance@entry=0x1e09dd0, emission_return=emission_return@entry=0x0, instance_and_params=instance_and_params@entry=0x7fffd9d55720) at /build/buildd/glib2.0-2.37.0/./gobject/gsignal.c:3584
Title: gedit crashed with SIGSEGV in gedit_multi_notebook_get_active_tab()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo

Tim (darkxst) wrote :
information type: Private → Public
tags: removed: need-amd64-retrace
Launchpad Janitor (janitor) wrote :

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

Changed in gedit (Ubuntu):
status: New → Confirmed
tags: added: need-amd64-retrace
tags: removed: need-amd64-retrace
Tim (darkxst) wrote :

I'm pretty certain this happened when one of the files that was open in gedit, got deleted from disk.

Changed in gedit (Ubuntu):
importance: Undecided → High
status: Confirmed → Triaged
Changed in hundredpapercuts:
assignee: nobody → Paper Cuts Ninja (papercuts-ninja)
status: New → Confirmed
summary: - gedit crashed with SIGSEGV in gedit_multi_notebook_get_active_tab()
+ gedit SIGSEGV in gedit_multi_notebook_get_active_tab()
Changed in gedit:
importance: Unknown → Medium
status: Unknown → New

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please answer these questions:

* Is this reproducible?
* If so, what specific steps should we take to recreate this bug?

This will help us to find and resolve the problem.

Changed in gedit (Ubuntu):
status: Triaged → Incomplete
Changed in hundredpapercuts:
status: Confirmed → Incomplete
assignee: Papercuts Ninja (papercuts-ninja) → nobody
Changed in gedit (Ubuntu):
status: Incomplete → Triaged
Changed in hundredpapercuts:
status: Incomplete → Triaged
importance: Undecided → High
assignee: nobody → Papercuts Ninja (papercuts-ninja)
Changed in hundredpapercuts:
importance: High → Medium
Changed in hundredpapercuts:
importance: Medium → High
assignee: Papercuts Ninjas (papercuts-ninja) → nobody
summary: - gedit SIGSEGV in gedit_multi_notebook_get_active_tab()
+ gedit crashed with SIGSEGV in gedit_multi_notebook_get_active_tab()
affects: hundredpapercuts → ubuntu
no longer affects: ubuntu
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.