gedit crashed with SIGSEGV in gtk_style_context_get_valist()

Bug #953588 reported by Benjamin Drung
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gedit (Ubuntu)
New
Undecided
Unassigned

Bug Description

I selected a text in gedit and then gedit froze.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: gedit 3.3.7-0ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-18.29-generic 3.2.9
Uname: Linux 3.2.0-18-generic x86_64
NonfreeKernelModules: openafs
ApportVersion: 1.94.1-0ubuntu2
Architecture: amd64
Date: Mon Mar 12 23:33:44 2012
ExecutablePath: /usr/bin/gedit
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Alpha amd64 (20100921.1)
ProcCmdline: gedit /tmp/devscripts_2.11.4ubuntu1.patch
SegvAnalysis:
 Segfault happened at: 0x7f219d5ca3e7 <gtk_style_context_get_valist+215>: mov 0x30(%rax),%rdx
 PC (0x7f219d5ca3e7) ok
 source "0x30(%rax)" (0x00000030) not located in a known VMA region (needed readable region)!
 destination "%rdx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gedit
StacktraceTop:
 gtk_style_context_get_valist () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
 gtk_style_context_get () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
 gtk_style_context_set_background () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
Title: gedit crashed with SIGSEGV in gtk_style_context_get_valist()
UpgradeStatus: Upgraded to precise on 2012-03-05 (7 days ago)
UserGroups: adm admin cdrom dialout libvirtd lpadmin plugdev sambashare

Revision history for this message
Benjamin Drung (bdrung) 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 #942274, 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.

visibility: private → public
visibility: 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.