gedit crashed with SIGSEGV in gtk_style_context_get_valist()

Bug #942274 reported by Liam McDermott on 2012-02-27
This bug affects 21 people
Affects Status Importance Assigned to Milestone
gedit (Ubuntu)

Bug Description

This occurred while I was attempting to drag a tab from one gedit window to another. The tab didn't move when dragged with the mouse, instead the entire application crashed.

I've attempted to reproduce this and couldn't, so am unsure exactly what conditions cause the bug.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: gedit 3.3.4-0ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-17.27-generic 3.2.6
Uname: Linux 3.2.0-17-generic x86_64
NonfreeKernelModules: fglrx
ApportVersion: 1.93-0ubuntu2
Architecture: amd64
Date: Mon Feb 27 16:54:26 2012
ExecutablePath: /usr/bin/gedit
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (20120221)
ProcCmdline: gedit
 PATH=(custom, no user)
 Segfault happened at: 0x7f48779d33a7 <gtk_style_context_get_valist+215>: mov 0x30(%rax),%rdx
 PC (0x7f48779d33a7) 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
 gtk_style_context_get_valist () from /usr/lib/x86_64-linux-gnu/
 gtk_style_context_get () from /usr/lib/x86_64-linux-gnu/
 gtk_style_context_set_background () from /usr/lib/x86_64-linux-gnu/
 ?? () from /usr/lib/x86_64-linux-gnu/
 ?? () from /usr/lib/x86_64-linux-gnu/
Title: gedit crashed with SIGSEGV in gtk_style_context_get_valist()
UpgradeStatus: Upgraded to precise on 2012-02-26 (1 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

 gtk_style_context_get_valist (context=0x2e98200, state=GTK_STATE_FLAG_NORMAL, args=0x7ffffcab37b8) at /build/buildd/gtk+3.0-3.3.16/./gtk/gtkstylecontext.c:1529
 gtk_style_context_get (context=0x2e98200, state=GTK_STATE_FLAG_NORMAL) at /build/buildd/gtk+3.0-3.3.16/./gtk/gtkstylecontext.c:1564
 gtk_style_context_set_background (context=0x2e98200, window=0x2e92360) at /build/buildd/gtk+3.0-3.3.16/./gtk/gtkstylecontext.c:3474
 gtk_widget_real_style_updated (widget=0x1fe7790) at /build/buildd/gtk+3.0-3.3.16/./gtk/gtkwidget.c:6579
 gtk_window_style_updated (widget=0x1fe7790) at /build/buildd/gtk+3.0-3.3.16/./gtk/gtkwindow.c:5730

Changed in gedit (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
visibility: private → public
Changed in gedit (Ubuntu):
importance: Medium → Low
Launchpad Janitor (janitor) wrote :

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

Changed in gedit (Ubuntu):
status: New → Confirmed
Lockal (lockal) wrote :

Happend to me once after I dragged a file from nautilus to gedit and then tried to open the same file by double clicking.

thom (tsk) wrote :

This is how I can reproduce it (and also why it not happens most of the times):

It always happens when I start one gedit instance from nautilus and another gedit instance from a gnome-terminal window

It doesn't happen when both are started from the gnome-terminal
It doesn't happen when both are started from nautilus
it doesn't happen when one is started from the launcher and another from terminal
it doesn't happen when one is started from the launcher and another from nautilus

Ingo Gerth (igerth) wrote :

... happened when dragging text inside of gedit. Very annoying, makes programming with it nearly impossible for it crashes frequently. How can the priority only be low?

I got this when I had Gedit running maximized on my top-left workspace with multiple tabs open, then switched to my top-right workspace and used the quicklist entry for opening a new window. After the window opened blank, it went unresponsive and eventually crashed.

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