gnome-font-viewer crashed with signal 5 in _XEventsQueued()

Bug #1845362 reported by Paul White on 2019-09-25
This bug affects 18 people
Affects Status Importance Assigned to Milestone
gnome-font-viewer (Debian)
gnome-font-viewer (Ubuntu)

Bug Description

Reproducible crash (tested on Ubuntu and Xubuntu) or freezing of application during ISO testing of a live-session.

Application will crash if there is an attempt to close it or scroll through fonts. On one occasion my laptop was rendered unusable when Firefox was launched while trying to report the crash to Launchpad.

After the bug report has been sent gnome-font-viewer will freeze when automatically restarted. No fonts are displayed.

Work around
gnome-font-viewer appears to start correctly when started from the command line of my Ubuntu 20.04 installation. Then subsequent attempts to start the program succeed when started from the dock or the Application Overview.

I have found that this work around wasn't necessary when using Xubuntu 20.04.

ProblemType: Crash
DistroRelease: Ubuntu 19.10
Package: gnome-font-viewer 3.34.0-1
ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8
Uname: Linux 5.3.0-10-generic x86_64
ApportVersion: 2.20.11-0ubuntu7
Architecture: amd64
CasperVersion: 1.416
CurrentDesktop: XFCE
Date: Wed Sep 25 17:34:17 2019
ExecutablePath: /usr/bin/gnome-font-viewer
LiveMediaBuild: Xubuntu 19.10 "Eoan Ermine" - Beta amd64 (20190925)
ProcCmdline: gnome-font-viewer
 PATH=(custom, no user)
Signal: 5
SourcePackage: gnome-font-viewer
 ?? () from /lib/x86_64-linux-gnu/
 ?? () from /lib/x86_64-linux-gnu/
 _XEventsQueued () from /lib/x86_64-linux-gnu/
 XPending () from /lib/x86_64-linux-gnu/
 ?? () from /lib/x86_64-linux-gnu/
Title: gnome-font-viewer crashed with signal 5 in _XEventsQueued()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Paul White (paulw2u) wrote :

 ?? () from /tmp/apport_sandbox_huw3az6o/usr/lib/x86_64-linux-gnu/
 g_log_writer_default () from /tmp/apport_sandbox_huw3az6o/usr/lib/x86_64-linux-gnu/
 g_log_structured_array () from /tmp/apport_sandbox_huw3az6o/usr/lib/x86_64-linux-gnu/
 g_log_structured_standard () from /tmp/apport_sandbox_huw3az6o/usr/lib/x86_64-linux-gnu/
 ?? ()

Changed in gnome-font-viewer (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Ubuntu QA Website (ubuntuqa) wrote :

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:

tags: added: iso-testing
Paul White (paulw2u) on 2019-09-25
information type: Private → Public
Paul White (paulw2u) on 2019-09-26
description: updated
Launchpad Janitor (janitor) wrote :

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

Changed in gnome-font-viewer (Ubuntu):
status: New → Confirmed
Layke (layke1123) wrote :

For what it's worth, when I first tried to use the font app by launching through the launcher, I consistently got freezes described as above. Launched it directly by invoking it on command line, and then haven't had a problem again since then, either via the launcher or command line.

Paul White (paulw2u) wrote :

Further to comment #8, I can confirm that invoking gnome-font-viewer from the command line allows the program to start normally when invoked from either the dock or the Application overview. This is with my Eoan installation which has now been upgraded to the development version of Focal. As the reporter of the bug I'll update the bug description to reflect this work around.

description: updated
tags: added: focal
Paul White (paulw2u) on 2019-12-27
description: updated
Hector Fiel (hfiel) wrote :

I also can replicate the bug on a clean Ubuntu 20.04 install.

Regarding the workaround, on the first launch from console it crashes, and subsequent invocations both from console or launcher work properly.

(gnome-font-viewer:9580): Gdk-ERROR **: 13:46:51.807: The program 'gnome-font-viewer' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadShmSeg (invalid shared segment parameter)'.
  (Details: serial 1935 error_code 128 request_code 130 (MIT-SHM) minor_code 5)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the GDK_SYNCHRONIZE environment
   variable to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)
Trace/breakpoint trap (core dumped)

Sebastien Bacher (seb128) wrote :

@Hector, what steps do you use to trigger the issue? Could you get a backtrace using
$ GDK_SYNCHRONIZE=1 gdb gnome-font-viewer

Nate (nlortz) wrote :

I am brand new to linux. Just purchased a System76 laptop that shipped to me with PopOS 20.04 installed. In checking out the new system, I can confirm this bug exists there too (makes sense, given the ubuntu base).

Launching the Fonts app from their launcher bring the app up, but that's as far as it goes. It becomes immediately unresponsive and the window cannot be closed.
I am only able to exit by ending the process. Repeated a couple times with the same results.

I googled the issue and found this thread.

Going from the posts above, I launched the 'gnome-font-viewer' from the command line.
In doing so, the app launched, and appears to be fully functional. Subsequent launches both from the command line, and the gui launcher now, are also functional.

The first launch from the command line did generate the error message below however. Since I've never used linux, I don't know what it means, but maybe it'll help.

Gtk-Message: 17:33:41: Failed to load module "appmenu-gtk-module"

Sebastien Bacher (seb128) wrote :

Indeed it seems to have issue while generating the thumbnails, after a few starts/having those done then it's working better

Changed in gnome-font-viewer (Ubuntu):
importance: Medium → High
Changed in gnome-font-viewer (Debian):
status: Unknown → New
Luis (mantelitos) wrote :

Hi, I was able to solve the problem using the debugging options of the same gnome-font-viewer package. In my case, I think I started to have a problem after installing the lxqt and xfce desktops, which I believe had different font management daemons from gnome. After uninstalling all the desktops and dependencies for some reason the problem did not disappear. I finally found the solution by looking in the help file for gnome-font-viewer, typing in the terminal:

$ gnome-font-viewer --gdk-debug =

I hope I helped, greetings!


Thanks. I think you mean `--gtk-debug`, though, not 'gdk'. Also: if one has the problem, must one *always* run the viewer in that way, and what does running it in that way do?

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

Related blueprints

Remote bug watches

Bug watches keep track of this bug in other bug trackers.