latexila crashed with SIGSEGV in g_type_check_instance_is_fundamentally_a()

Bug #1449565 reported by magowiz
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
latexila (Ubuntu)
Expired
Medium
Unassigned

Bug Description

$ lsb_release -rd
Description: Ubuntu 15.04
Release: 15.04

$ LC_ALL=C apt-cache policy latexila
latexila:
  Installed: 3.14.4-0ubuntu1
  Candidate: 3.14.4-0ubuntu1
  Version table:
 *** 3.14.4-0ubuntu1 0
        500 http://it.archive.ubuntu.com/ubuntu/ vivid/universe amd64 Packages
        100 /var/lib/dpkg/status

It shouldn't crash

crashed

ProblemType: Crash
DistroRelease: Ubuntu 15.04
Package: latexila 3.14.4-0ubuntu1
ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3
Uname: Linux 3.19.0-15-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.17.2-0ubuntu1
Architecture: amd64
CurrentDesktop: GNOME
Date: Tue Apr 28 15:22:05 2015
ExecutablePath: /usr/bin/latexila
ProcCmdline: latexila
SegvAnalysis:
 Segfault happened at: 0x7f5e53d6843d <g_type_check_instance_is_fundamentally_a+13>: mov (%rax),%rax
 PC (0x7f5e53d6843d) ok
 source "(%rax)" (0x7269726566697220) not located in a known VMA region (needed readable region)!
 destination "%rax" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: latexila
StacktraceTop:
 g_type_check_instance_is_fundamentally_a () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_object_ref () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 ?? () 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: latexila crashed with SIGSEGV in g_type_check_instance_is_fundamentally_a()
UpgradeStatus: Upgraded to vivid on 2015-04-24 (4 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
magowiz (magowiz) wrote :
information type: Private → Public
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 g_type_check_instance_is_fundamentally_a (type_instance=type_instance@entry=0x7f5e585823f0, fundamental_type=fundamental_type@entry=80) at /build/buildd/glib2.0-2.44.0/./gobject/gtype.c:4028
 g_object_ref (_object=_object@entry=0x7f5e585823f0) at /build/buildd/glib2.0-2.44.0/./gobject/gobject.c:3040
 gtk_grab_notify_foreach (child=0x7f5e585823f0, data=0x7fff6a628950) at /build/buildd/gtk+3.0-3.14.12/./gtk/gtkmain.c:1961
 gtk_window_forall (container=0x7f5e575255b0, include_internals=1, callback=0x7f5e54ef2220 <gtk_grab_notify_foreach>, callback_data=0x7fff6a628950) at /build/buildd/gtk+3.0-3.14.12/./gtk/gtkwindow.c:7966
 gtk_grab_notify_foreach (child=child@entry=0x7f5e575255b0, data=data@entry=0x7fff6a628950) at /build/buildd/gtk+3.0-3.14.12/./gtk/gtkmain.c:1964

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : StacktraceSource.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in latexila (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Revision history for this message
Matthieu Baerts (matttbe) wrote :

Hello and thank you for this bug report!

Is there a way to reproduce this crash? What did you do just before the crash?

Changed in latexila (Ubuntu):
status: New → Incomplete
Revision history for this message
magowiz (magowiz) wrote :

I really don't know it was the one and only time it crashed, probably I was editing a tex file, cleaning ausiliary files or building a pdf.

Tipically with latexila I do these actions. I'm sorry I cannot give you further details.

Revision history for this message
Matthieu Baerts (matttbe) wrote :

No problem :-)
I'm not sure this stacktrace will help fixing this bug but maybe Sebastien can find something.

If you are able to reproduce this bug, feel free to give us more details.

Revision history for this message
Sébastien Wilmet (sebastien-wilmet) wrote :

Sorry for the late response. It looks like a bug in GTK+.

Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in latexila (Ubuntu):
status: Incomplete → Expired
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.