GNOME Bugzilla – Bug 793312
gnome-clocks sometimes crashes when used from gnome-shell search.
Last modified: 2018-02-23 17:28:49 UTC
half the time when searching from gnome-shell for a city, the spawned gnome-clocks process crashes:
+ Trace 238384
Thread 1 (Thread 0x7fdbe9018f40 (LWP 25155))
I don't know how long this has been happening since I don't always look at /var/lib/systemd/coredump/ and there was no visible indication of the crash. For example, searching for "London" always showed a result regardless of whether there was a crash or not.
dmesg says: [83492.379192] gnome-clocks[8971]: segfault at 0 ip 00007f493f0a7d7f sp 00007ffeabff85a0 error 4 in libgweather-3.so.15.0.0[7f493f08f000+24000] [83493.980150] gnome-clocks[9020]: segfault at 0 ip 00007f9e00ccdd7f sp 00007ffd907cb8f0 error 4 in libgweather-3.so.15.0.0[7f9e00cb5000+24000] So I guess this is due to upgrading from libgweather 3.26 to 3.27.
Created attachment 368722 [details] [review] Proposed workaround gweather_location_serialize is currenty not ready to serialize cities without children weather stations eg: Warangal Skip those until we either get better serialization handling of those in libgweather or we change how we produce the data for the search provider interface https://bugzilla.redhat.com/show_bug.cgi?id=1546666
https://bugzilla.gnome.org/show_bug.cgi?id=793697 for the libgweather side of the breakage
Review of attachment 368722 [details] [review]: thanks
Pushed to master - commit 9ba5fba