Created attachment 1675211 [details]
File: backtrace

Created attachment 1675212 [details]
File: core_backtrace

Created attachment 1675213 [details]
File: cpuinfo

Created attachment 1675214 [details]
File: dso_list

Created attachment 1675215 [details]
File: environ

Created attachment 1675216 [details]
File: exploitable

Created attachment 1675217 [details]
File: limits

Created attachment 1675218 [details]
File: maps

Created attachment 1675219 [details]
File: mountinfo

Created attachment 1675220 [details]
File: open_fds

Created attachment 1675221 [details]
File: proc_pid_status

Created attachment 1675222 [details]
File: var_log_messages

*** Bug 1820225 has been marked as a duplicate of this bug. ***

Similar problem has been detected:

I don't know how this could be related to "gnome-clocks", but I unmounted an USB drive using the gnome file manager.

reporter:       libreport-2.12.0
backtrace_rating: 4
cgroup:         0::/user.slice/user-1000.slice/user/dbus\x2d:1.2\x2dorg.gnome.clocks.slice/dbus-:1.2-org.gnome.clocks
cmdline:        /usr/bin/gnome-clocks --gapplication-service
crash_function: g_date_time_to_instant
executable:     /usr/bin/gnome-clocks
journald_cursor: s=d38b93ba28474c37856e3c65b0f2917c;i=2753e;b=39c1a699071d408e89b763959fcf24d0;m=1921c5bb3;t=5a26894e4220e;x=47dd9e587f6c1df
kernel:         5.6.0-300.fc32.x86_64
package:        gnome-clocks-3.36.0-1.fc32
reason:         gnome-clocks killed by SIGSEGV
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1000

*** Bug 1820935 has been marked as a duplicate of this bug. ***

*** Bug 1821520 has been marked as a duplicate of this bug. ***

*** Bug 1821699 has been marked as a duplicate of this bug. ***

Similar problem has been detected:

I was trying to run Google Chrome. It normally started, but I realized that the crash of Gnome Clocks was reported.

reporter:       libreport-2.12.0
backtrace_rating: 4
cgroup:         0::/user.slice/user-1000.slice/user/dbus\x2d:1.2\x2dorg.gnome.clocks.slice/dbus-:1.2-org.gnome.clocks
cmdline:        /usr/bin/gnome-clocks --gapplication-service
crash_function: g_date_time_to_instant
executable:     /usr/bin/gnome-clocks
journald_cursor: s=94b470708c89455c91a6eeab5b47e292;i=10fabb;b=3e7c3befd0334fa998f8fe9616a5bc32;m=594cce9cda;t=5a2b50b385b15;x=ae9dfa9986975155
kernel:         5.6.0-0.rc7.git0.2.fc32.x86_64
package:        gnome-clocks-3.36.0-1.fc32
reason:         gnome-clocks killed by SIGSEGV
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1000
xsession_errors:

Similar problem has been detected:

gnome-clocks quit unexpectedly, though I did not notice anything unusual on my desktop. Everything looked normal.

reporter:       libreport-2.12.0
backtrace_rating: 4
cmdline:        /usr/bin/gnome-clocks --gapplication-service
crash_function: g_date_time_to_instant
executable:     /usr/bin/gnome-clocks
journald_cursor: s=3493b6f5d7024643850497f58ae0b4ad;i=6b0e5;b=87a111d53788497a9ec764308cda02e4;m=a19c20a8;t=5a2c3ec325a8b;x=34a6e6184fc65fea
kernel:         5.6.2-301.fc32.x86_64
package:        gnome-clocks-3.36.0-1.fc32
reason:         gnome-clocks killed by SIGSEGV
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1000

*** Bug 1822700 has been marked as a duplicate of this bug. ***

*** Bug 1823009 has been marked as a duplicate of this bug. ***

*** Bug 1823073 has been marked as a duplicate of this bug. ***

*** Bug 1823681 has been marked as a duplicate of this bug. ***

Looking at the backtraces for this and the duplicate bug reports, so far we only have full backtraces from users living very far north, in which case the sunrise/sunset calculation goes wrong, resulting in this crash. That's now fixed upstream.

But I hit this crash too, living in the continental US, and I don't know why. I suspect there is a different reason this crash can occur. I can't reproduce, so can't get a full backtrace. If anyone living in areas with more typical sunrise/sunset is hitting this bug and able to help with getting a backtrace, that would be appreciated. The crash will be gone in the next update regardless, but we still want to know what's going wrong so we can avoid broken functionality.

Proposed as a Freeze Exception for 32-final by Fedora user catanzaro using the blocker tracking app because:

 Definitely not serious enough to be a blocker, but gnome-clocks runs as a system service on the live media and it would be nice for background services to not crash. Poor first impression for live media users.

The impact is a little uncertain and still under investigation. It seems this bug most prominently affects users who live close to or above the arctic circle, but I hit it once myself, so that can't be the only cause here.

FEDORA-2020-73dd8ea80a has been submitted as an update to Fedora 32. https://bodhi.fedoraproject.org/updates/FEDORA-2020-73dd8ea80a

Not actually sure if private bugs can be freeze exceptions, but I marked this private because the backtrace contains latitude/longitude coordinates with a high degree of precision.

you can mark the attachment private without making the entire bug private. doing so.

+1 FE since it can produce a crash notification without any user interaction in some cases. (this could actually be proposed as a blocker as a conditional violation of https://fedoraproject.org/wiki/Fedora_32_Final_Release_Criteria#SELinux_and_crash_notifications , but I'd probably be -1 to that as it doesn't sound like it's common enough).

+1 FE

Definitely +1 FE, if it is affecting more people, then I will go with +1 Blocker

+1 FE

That's +4, marking accepted.

FEDORA-FLATPAK-2020-ff41d5d838 has been submitted as an update to Fedora 32 Flatpaks. https://bodhi.fedoraproject.org/updates/FEDORA-FLATPAK-2020-ff41d5d838

FEDORA-FLATPAK-2020-ff41d5d838 has been pushed to the Fedora 32 Flatpaks testing repository.

You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-FLATPAK-2020-ff41d5d838

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

FEDORA-FLATPAK-2020-ff41d5d838 has been pushed to the Fedora 32 Flatpaks stable repository.
If problem still persists, please make note of it in this bug report.

FEDORA-2020-73dd8ea80a has been pushed to the Fedora 32 stable repository.
If problem still persists, please make note of it in this bug report.

*** Bug 1824000 has been marked as a duplicate of this bug. ***

Similar problem has been detected:

Search processed on Gnome desktop

reporter:       libreport-2.12.0
backtrace_rating: 4
cgroup:         0::/user.slice/user-1000.slice/user/dbus\x2d:1.2\x2dorg.gnome.clocks.slice/dbus-:1.2-org.gnome.clocks
cmdline:        /usr/bin/gnome-clocks --gapplication-service
crash_function: g_date_time_to_instant
executable:     /usr/bin/gnome-clocks
journald_cursor: s=41d4419690b34adda6c29d69521ddb4d;i=17d17;b=f541858485a04900b187caec4cf38e2d;m=28a4f8aa7;t=5a351b8ef84f3;x=982888a5a466482d
kernel:         5.6.4-300.fc32.x86_64
package:        gnome-clocks-3.36.0-1.fc32
reason:         gnome-clocks killed by SIGSEGV
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1000

Similar problem has been detected:

Happened randomly in background

reporter:       libreport-2.12.0
backtrace_rating: 4
cgroup:         0::/user.slice/user-1000.slice/user/dbus\x2d:1.2\x2dorg.gnome.clocks.slice/dbus-:1.2-org.gnome.clocks
cmdline:        /usr/bin/gnome-clocks --gapplication-service
crash_function: g_date_time_to_instant
executable:     /usr/bin/gnome-clocks
journald_cursor: s=ea0736aea53047739df750a3ec5562fb;i=a6bbd;b=51fec6512e844c3bb1c8432c5064c5e0;m=6ecb3724c;t=5a32aed73e131;x=e4140935fb9fbb4f
kernel:         5.6.0-300.fc32.x86_64
package:        gnome-clocks-3.36.0-1.fc32
reason:         gnome-clocks killed by SIGSEGV
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1000