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

Bug #1845362 reported by Paul White
138
This bug affects 26 people
Affects Status Importance Assigned to Milestone
gnome-font-viewer (Debian)
New
Unknown
gnome-font-viewer (Ubuntu)
High
Unassigned

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
ProcEnviron:
 LANGUAGE=en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=C.UTF-8
 SHELL=/bin/bash
Signal: 5
SourcePackage: gnome-font-viewer
StacktraceTop:
 ?? () from /lib/x86_64-linux-gnu/libX11.so.6
 ?? () from /lib/x86_64-linux-gnu/libX11.so.6
 _XEventsQueued () from /lib/x86_64-linux-gnu/libX11.so.6
 XPending () from /lib/x86_64-linux-gnu/libX11.so.6
 ?? () from /lib/x86_64-linux-gnu/libgdk-3.so.0
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
separator:

Revision history for this message
Paul White (paulw2u) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 ?? () from /tmp/apport_sandbox_huw3az6o/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.6200.0
 g_log_writer_default () from /tmp/apport_sandbox_huw3az6o/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.6200.0
 g_log_structured_array () from /tmp/apport_sandbox_huw3az6o/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.6200.0
 g_log_structured_standard () from /tmp/apport_sandbox_huw3az6o/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.6200.0
 ?? ()

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 gnome-font-viewer (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Revision history for this message
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:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1845362

tags: added: iso-testing
Paul White (paulw2u)
information type: Private → Public
Paul White (paulw2u)
description: updated
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in gnome-font-viewer (Ubuntu):
status: New → Confirmed
Revision history for this message
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.

Revision history for this message
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)
description: updated
Revision history for this message
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)
----

Revision history for this message
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
?

Revision history for this message
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"

Revision history for this message
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
Revision history for this message
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!

Revision history for this message
ALinuxUser (buntulongername-new) wrote :

@Luis

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?

Revision history for this message
corrado venturini (corradoventu) wrote :

Same problem on Ubuntu 21.04. started gnome-font-viewer from terminal the window opens but is unresponsive. closing it I have the crash and a message:
corrado@corrado-n8-hh-0101:~$ gnome-font-viewer

(gnome-font-viewer:4532): Gdk-ERROR **: 08:22:36.317: The program 'gnome-font-viewer' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadIDChoice (invalid resource ID chosen for this connection)'.
  (Details: serial 1502 error_code 14 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)
corrado@corrado-n8-hh-0101:~$

corrado@corrado-n8-hh-0101:~$ apt policy gnome-font-viewer
gnome-font-viewer:
  Installed: 3.34.0-2
  Candidate: 3.34.0-2
  Version table:
 *** 3.34.0-2 500
        500 http://archive.ubuntu.com/ubuntu hirsute/main amd64 Packages
        100 /var/lib/dpkg/status
corrado@corrado-n8-hh-0101:~$ inxi -SCGx
System: Host: corrado-n8-hh-0101 Kernel: 5.8.0-25-generic x86_64 bits: 64 compiler: gcc v: 10.2.0
           Desktop: GNOME 3.38.2 Distro: Ubuntu 21.04 (Hirsute Hippo)
CPU: Info: Quad Core model: Intel Core i5-1035G1 bits: 64 type: MT MCP arch: Ice Lake rev: 5
           L2 cache: 6 MiB
           flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 19046
           Speed: 813 MHz min/max: 400/1000 MHz Core speeds (MHz): 1: 813 2: 998 3: 989 4: 997 5: 966
           6: 980 7: 954 8: 974
Graphics: Device-1: Intel Iris Plus Graphics G1 vendor: Dell driver: i915 v: kernel bus ID: 00:02.0
           Device-2: Realtek Integrated_Webcam_HD type: USB driver: uvcvideo bus ID: 1-6:3
           Display: x11 server: X.Org 1.20.9 driver: modesetting unloaded: fbdev,vesa
           resolution: 1920x1080~60Hz
           OpenGL: renderer: Mesa Intel UHD Graphics (ICL GT1) v: 4.6 Mesa 20.2.6 direct render: Yes
corrado@corrado-n8-hh-0101:~$

Revision history for this message
Veron Rado (junket) wrote :

Same issue for me. gnome-font-viewer froze after launching, either by using Fonts app or command line.
The fix by Luis (mantelitos) in post #14 above works for me. Except one small tweak, remove the space before the "="

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

Once it had launched that way it now launches using the regular Fonts app and plain command line ways too.

Thanks for posting your workaround Luis.

Ubuntu 20.04 LTS
GNOME Fonts 3.34.0

Revision history for this message
Brian Murray (brian-murray) wrote :

I was able to recreate this when running the "Try Ubuntu" environment on an Impish daily build from 20210922. I reported the crash report in bug 1944736 which was marked as a duplicate of bug 1373069.

tags: added: rls-ii-incoming
Revision history for this message
Sebastien Bacher (seb128) wrote :

Triaging as rls-ii-notfixing, the font viewer isn't an essential software and while it would be nice to fix the issue we don't believe it's a release blocker

tags: added: rls-ii-notfixing
removed: rls-ii-incoming
Revision history for this message
Akbarkhon Variskhanov (kbar) wrote (last edit ):

I know that it was set to rls-ii-notfixing but I just want to report that it appears in Jammy as well (build 20211104).

I'm including this bug in my test result with the "Passed" flag.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Related blueprints

Remote bug watches

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