gnome clocks crashes with segfault upon start

Bug #1874405 reported by fcole90 on 2020-04-23
This bug affects 5 people
Affects Status Importance Assigned to Milestone
gnome-clocks (Ubuntu)

Bug Description

The application crashes immediately after starting.

$ gnome-clocks

(org.gnome.clocks:137984): Gtk-WARNING **: 11:57:15.762: Theme parsing error: <broken file>:1:0: Failed to import: The resource at “/org/gnome/clocks/css/gnome-clocks.adwaita.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-25.29-generic 5.4.30
Uname: Linux 5.4.0-25-generic x86_64
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: GNOME
Date: Thu Apr 23 11:57:35 2020
InstallationDate: Installed on 2020-04-03 (19 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401)
SourcePackage: gnome-clocks
UpgradeStatus: No upgrade log present (probably fresh install)

fcole90 (fcole90) wrote :
Launchpad Janitor (janitor) wrote :

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

Changed in gnome-clocks (Ubuntu):
status: New → Confirmed
Hans Joachim Desserud (hjd) wrote :

Note that the error message mentions different .css-files depending on the desktop environment or theme you are running.

tags: added: groovy
fcole90 (fcole90) wrote :

I wonder why it is indeed looking for a file with a theme name like `/org/gnome/clocks/css/gnome-clocks.adwaita.css`. Indeed the package contains `/org/gnome/clocks/css/gnome-clocks.css` and such file is also listed as a gresource..

fcole90 (fcole90) wrote :

I googled similar errors and I found out that this is just a warning, and likely not the cause of the segmentation fault.
An example here of a functioning gnome-clocks with the same warning:

Sebastien Bacher (seb128) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. It sounds like some part of the system has crashed. To help us find the cause of the crash please follow these steps:

1. Look in /var/crash for crash files and if found run:
    ubuntu-bug YOURFILE.crash
Then tell us the ID of the newly-created bug.

2. If step 1 failed then look at where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us.

3. If step 2 also failed then apply the workaround from bug 994921, reboot, reproduce the crash, and retry step 1.

Please take care to avoid attaching .crash files to bugs as we are unable to process them as file attachments. It would also be a security risk for yourself.

Changed in gnome-clocks (Ubuntu):
status: Confirmed → Invalid
Mordi (mrdc76) wrote :

The Id is:

kasunch (kasun-ch) wrote :

I am also having the same problem.
Inspecting the crash files revealed that the real issue is the following.

fcole90 (fcole90) on 2020-05-04
summary: - Missing resources causes segmentation fault
+ gnome clocks crashes with segfault upon start
fcole90 (fcole90) wrote :

Changed back to confirmed, as the required information is now available.

Changed in gnome-clocks (Ubuntu):
status: Invalid → Confirmed
Helio Victor (userhv) wrote : I fear a patch here that fixes all of these bugs.

Hans Joachim Desserud (hjd) wrote :

With bug 1873077 fixed in version 3.36.0-1ubuntu0.1, does anyone still get a crash at startup?

I tested on my 20.04 system, and it seems to work fine. If no one are still able to trigger a crash, I assume this was a duplicate.

Changed in gnome-clocks (Ubuntu):
status: Confirmed → Incomplete
Mordi (mrdc76) wrote :

It works for me now.

fcole90 (fcole90) wrote :

I confirm everything is working

Hans Joachim Desserud (hjd) wrote :

Thanks for retesting. Going to mark this as a duplicate of bug 1873077 then :)

Hi, `gnome-clocks --version`` shows Clocks 3.36.0 and I'm still experiencing segfault. I think that is the latest version with the fix?

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

Other bug subscribers