gedit crashed with SIGSEGV in gtk_action_group_get_action()

Bug #1439323 reported by Caglar Oflazoglu
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gedit (Ubuntu)
New
Undecided
Unassigned

Bug Description

big file data

ProblemType: Crash
DistroRelease: Ubuntu 15.04
Package: gedit 3.10.4-0ubuntu9
ProcVersionSignature: Ubuntu 3.19.0-10.10-generic 3.19.2
Uname: Linux 3.19.0-10-generic x86_64
ApportVersion: 2.17-0ubuntu1
Architecture: amd64
CurrentDesktop: Unity
Date: Wed Apr 1 20:21:39 2015
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/gedit
InstallationDate: Installed on 2013-08-20 (588 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
ProcCmdline: gedit /media/username/CAGLAR_HDD2/tubitak_datas/data_file/mfcc/MO1-1.mfcc
SegvAnalysis:
 Segfault happened at: 0x7fa709536aac <gtk_action_group_get_action+28>: cmp %rax,0x0(%rbp)
 PC (0x7fa709536aac) ok
 source "%rax" ok
 destination "0x0(%rbp)" (0x400000000) not located in a known VMA region (needed writable region)!
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: gedit
StacktraceTop:
 gtk_action_group_get_action () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
 ?? ()
 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
 g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: gedit crashed with SIGSEGV in gtk_action_group_get_action()
UpgradeStatus: Upgraded to vivid on 2015-04-01 (0 days ago)
UserGroups: adm cdrom dip lpadmin minidlna plugdev sambashare sudo www-data

Revision history for this message
Caglar Oflazoglu (coflazoglu) 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 #1438128, 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-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.