Bug 789511 – gnome-font-viewer crashed with SIGSEGV in g_type_check_instance_cast()

After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.

Bug 789511 - gnome-font-viewer crashed with SIGSEGV in g_type_check_instance_cast()


Summary:	gnome-font-viewer crashed with SIGSEGV in g_type_check_instance_cast()


Status:	RESOLVED FIXED

Product:	gnome-font-viewer
Classification:	Core
Component:	general
Version:	3.26.x
Hardware:	Other Linux

Importance:	High critical
Target Milestone:	---
Assigned To:	gnome-font-viewer-maint
QA Contact:	gnome-font-viewer-maint

URL:
Whiteboard:

Duplicates:	789560 (view as bug list)
Depends on:
Blocks:

Reported:	2017-10-26 08:47 UTC by Alin Sinpalean
Modified:	2017-10-30 22:30 UTC

See Also:	https://launchpad.net/bugs/1726286
GNOME target:	---
GNOME version:	3.25/3.26

Attachments
apport crash report (219.42 KB, text/plain) 2017-10-27 11:17 UTC, Alin Sinpalean	Details

Description Alin Sinpalean 2017-10-26 08:47:53 UTC

Original Ubuntu Launchpad bug report: https://bugs.launchpad.net/ubuntu/+source/gnome-font-viewer/+bug/1726286

For me it crashes whenever I open it by double-clicking its icon anywhere Gnome Shell. For some reason it runs more reliably if I start it from a terminal.
 (I've seen it segfault once that way too, but after running a while.)

All original attachments available on Launchpad, no idea where mine are because I chose to add to the same bug rather than report a new one.

Original description:

Fresh Ubuntu 17.10 install on ASUS UX-303LA laptop, opened font viewer and after a couple of secs it has crashed

ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: gnome-font-viewer 3.26.0-1
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Mon Oct 23 10:42:14 2017
ExecutablePath: /usr/bin/gnome-font-viewer
InstallationDate: Installed on 2017-10-21 (1 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
ProcCmdline: /usr/bin/gnome-font-viewer --gapplication-service
SegvAnalysis:
 Segfault happened at: 0x7fa952064dd6 <g_type_check_instance_cast+22>:	mov (%rdi),%rdi
 PC (0x7fa952064dd6) ok
 source "(%rdi)" (0x4238317839080030) not located in a known VMA region (needed readable region)!
 destination "%rdi" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: gnome-font-viewer
StacktraceTop:
 g_type_check_instance_cast () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.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
 g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: gnome-font-viewer crashed with SIGSEGV in g_type_check_instance_cast()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Comment 1 André Klapper 2017-10-27 09:48:18 UTC

Thanks for taking the time to report this.
Without a stack trace from the crash it's very hard to determine what caused it.
Can you get us a stack trace? Please see https://wiki.gnome.org/Community/GettingInTouch/Bugzilla/GettingTraces for more information on how to do so. When pasting a stack trace in this bug report, please reset the status of this bug report from NEEDINFO to its previous status. Thanks in advance!

Comment 2 André Klapper 2017-10-27 09:49:07 UTC

...and that stacktrace should include all debug symbols.

Comment 3 Alin Sinpalean 2017-10-27 11:17:27 UTC

Created attachment 362398 [details]
apport crash report

No core dump, as file was too large with it.

Comment 4 Alin Sinpalean 2017-10-27 11:19:50 UTC

As for the status, I can only choose between NEEDINFO and RESOLVED. I'm guessing NEEDINFO is safer.

Comment 5 André Klapper 2017-10-27 12:00:22 UTC

We still need a stacktrace with debug symbols...

Comment 6 Alin Sinpalean 2017-10-27 14:10:00 UTC

Tharr you go:

(gdb) r
Starting program: /usr/bin/gnome-font-viewer 
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x7fffebb5e700 (LWP 3517)]
[New Thread 0x7fffeb35d700 (LWP 3518)]
[New Thread 0x7fffea94f700 (LWP 3519)]

(gnome-font-viewer:3513): Gtk-WARNING **: Theme parsing error: gtk.css:7:48: Junk at end of value for background-color

(gnome-font-viewer:3513): Gtk-WARNING **: Theme parsing error: gtk.css:8:0: 'trans' is not a valid property name
[New Thread 0x7fffe895e700 (LWP 3520)]

(gnome-font-viewer:3513): Gtk-CRITICAL **: gtk_widget_get_scale_factor: assertion 'GTK_IS_WIDGET (widget)' failed

Thread 1 "gnome-font-view" received signal SIGSEGV, Segmentation fault.
g_type_check_instance_cast (type_instance=0x6c612f3c090a3e74, 
    iface_type=93825002769200) at ../../../../gobject/gtype.c:4052
4052	../../../../gobject/gtype.c: No such file or directory.
(gdb) bt

+ Trace 238122

#0 g_type_check_instance_cast
at ../../../../gobject/gtype.c line 4052
#1 font_view_update_scale_factor
at ../src/font-view.c line 521
#5 <emit signal notify:scale-factor on instance 0x55555585c2c0 [GtkApplicationWindow]>
at ../../../../gobject/gsignal.c line 3447
#6 g_object_dispatch_properties_changed
at ../../../../gobject/gobject.c line 1080
#7 g_object_notify_by_spec_internal
at ../../../../gobject/gobject.c line 1173
#8 g_object_notify_by_pspec
at ../../../../gobject/gobject.c line 1283
#9 _gtk_widget_scale_changed
at ././gtk/gtkwidget.c line 10852
#10 check_scale_changed
at ././gtk/gtkwindow.c line 6839
#11 gtk_window_configure_event
at ././gtk/gtkwindow.c line 8008
#16 <emit signal ??? on instance 0x55555585c2c0 [GtkApplicationWindow]>
at ../../../../gobject/gsignal.c line 3447
#17 gtk_widget_event_internal
at ././gtk/gtkwidget.c line 7723
#18 gtk_widget_event
at ././gtk/gtkwidget.c line 7293
#19 gtk_main_do_event
at ././gtk/gtkmain.c line 1851
#20 _gdk_event_emit
at ././gdk/gdkevents.c line 73
#21 gdk_event_source_dispatch
at ././gdk/wayland/gdkeventsource.c line 124
#22 g_main_dispatch
at ../../../../glib/gmain.c line 3148
#23 g_main_context_dispatch
at ../../../../glib/gmain.c line 3813
#24 g_main_context_iterate
at ../../../../glib/gmain.c line 3886
#25 g_main_context_iteration
at ../../../../glib/gmain.c line 3947
#26 g_application_run
at ../../../../gio/gapplication.c line 2401
#27 main
at ../src/font-view.c line 938

Comment 7 Alin Sinpalean 2017-10-27 14:14:05 UTC

Also, it has nothing to do with where it's started from (Gnome Shell vs. Terminal) but rather which screen it's started on.

I have 2 screens (laptop at 200% scale and monitor at 100% scale). Launched on the external monitor it crashes immediately. Launched on the laptop screen it works just fine, unless I move it to the external and monitor and try to resize it. That's coming up as a separate bug.

Comment 8 Alin Sinpalean 2017-10-27 14:19:27 UTC

Resizing segfault submitted separately as bug 789560.

Comment 9 Cosimo Cecchi 2017-10-30 22:30:08 UTC

*** Bug 789560 has been marked as a duplicate of this bug. ***

Comment 10 Cosimo Cecchi 2017-10-30 22:30:51 UTC

Pushed a fix for this to master, thanks for reporting.