Ubuntu
gnome-clocks package

Gnome-clocks segfaults

Bug #1874885 reported by Mordi on 2020-04-24

This bug report is a duplicate of: Bug #1873077: gnome-clocks crashed with SIGSEGV in g_date_time_to_timezone(). Edit Remove

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	gnome-clocks (Ubuntu)	New	Undecided	Unassigned

Bug Description

1.
Description: Ubuntu 20.04 LTS
Release: 20.04

2.
  Installed: 3.36.0-1
  Candidate: 3.36.0-1
  Version table:
*** 3.36.0-1 500
3. Expected the app to launch.
4. Segmentation fault (core dumped)

I get the following error from command line:

(org.gnome.clocks:21396): Gtk-WARNING **: 21:29:25.112: Theme parsing error: <broken file>:1:0: Failed to import: The resource at “/org/gnome/clocks/css/gnome-clocks.yaru.css” does not exist
Segmentation fault (core dumped)

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gnome-clocks 3.36.0-1
ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
Uname: Linux 5.4.0-26-generic x86_64
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Fri Apr 24 21:29:48 2020
InstallationDate: Installed on 2018-04-27 (728 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
SourcePackage: gnome-clocks
UpgradeStatus: Upgraded to focal on 2020-04-24 (0 days ago)

Tags:

Revision history for this message

Mordi (mrdc76) wrote on 2020-04-24:

Dependencies.txt Edit (21.0 KiB, text/plain; charset="utf-8")
ProcCpuinfoMinimal.txt Edit (1.2 KiB, text/plain; charset="utf-8")
ProcEnviron.txt Edit (322 bytes, text/plain; charset="utf-8")

Revision history for this message

Hans Joachim Desserud (hjd) wrote on 2020-04-26:

Thank you for taking the time to report this bug and helping to make Ubuntu better.
This particular bug has already been reported and is a duplicate of bug 1874405, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find.