gnome clocks crashes with segfault upon start

[fcole90]

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)

[Launchpad Janitor (janitor)]

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

[Hans Joachim Desserud (hjd)]

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

[fcole90 (fcole90)]

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)]

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: https://forum.manjaro.org/t/gnome-calendar-and-clocks-doesnt-work-after-3-36-upgrade/131394/12

[Sebastien Bacher (seb128)]

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 https://errors.ubuntu.com/user/ID 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.

[Mordi (mrdc76)]

The Id is:
e1b093dc9dc97953eddd0a8757c88557282a5a55850ae36fa941c8bab401d5c5408146d9924c9361d4243aa155b683c6b985a1a351f472f973ba38806ba4babb

[fcole90 (fcole90)]

I find the following links related to gnome-clocks:
1. https://errors.ubuntu.com/oops/67861316-8540-11ea-99bc-fa163e102db1
2. https://errors.ubuntu.com/oops/7133d4c0-8973-11ea-ac5e-fa163e983629

[kasunch (kasun-ch)]

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

https://bugs.launchpad.net/ubuntu/+source/gnome-clocks/+bug/1873077

[fcole90 (fcole90)]

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

[Helio Victor (userhv)]

https://bugs.launchpad.net/ubuntu/+source/gnome-clocks/+bug/1873077 I fear a patch here that fixes all of these bugs.

[Hans Joachim Desserud (hjd)]

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.

[Mordi (mrdc76)]

It works for me now.

[fcole90 (fcole90)]

I confirm everything is working

[Hans Joachim Desserud (hjd)]

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

[Nishan Singh Mann (nishan-singh-mann)]

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?