After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 781509 - GNOME Shell crashes frequently when GNOME Weather is installed
GNOME Shell crashes frequently when GNOME Weather is installed
Status: RESOLVED OBSOLETE
Product: gnome-shell
Classification: Core
Component: general
3.24.x
Other Linux
: Normal major
: ---
Assigned To: gnome-shell-maint
gnome-shell-maint
: 781913 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2017-04-19 18:42 UTC by Peter Y. Chuang
Modified: 2021-07-05 14:13 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
coredumpctl gdb (1.11 KB, text/plain)
2017-04-20 18:25 UTC, Peter Y. Chuang
Details
coredumpctl info (1.11 KB, text/plain)
2017-04-20 18:26 UTC, Peter Y. Chuang
Details
coredumpctl gdb (6.59 KB, text/plain)
2017-04-20 18:37 UTC, Peter Y. Chuang
Details

Description Peter Y. Chuang 2017-04-19 18:42:46 UTC
GNOME Shell crashes frequently when GNOME Weather is installed. Running journalctl reveals the following coredump at the time when the Shell crashes:

systemd-coredump[2067]: Process 1595 (gnome-shell) of user 1000 dumped core.
                                              
                        Stack trace of thread 1595:
                        #0  0x00007f75deaf0a10 gweather_location_get_timezone (lib
                        #1  0x00007f763a9e31c8 ffi_call_unix64 (libffi.so.6)
                        #2  0x00007f763a9e2c2a ffi_call (libffi.so.6)
                        #3  0x00007f76413b378f n/a (libgjs.so.0)
                        #4  0x00007f76413b4e44 n/a (libgjs.so.0)
                        #5  0x00007f7641d8d6db n/a (n/a)


I am on Arch Linux and Wayland with the latest libgweather and gnome-weather built from source. This behaviour occurs in two of my machines. Toggling Location setting does not appear to affect the behaviour.
Comment 1 Florian Müllner 2017-04-19 19:00:14 UTC
Can you get a backtrace with debug symbols installed?
Comment 2 Peter Y. Chuang 2017-04-20 11:54:31 UTC
I am sorry, but I'm not sure how to do that. I'd appreciate if you point me to the instruction on how to do that. Thank you.

On another note, I notice that gnome-weather/libgweather doesn't crash GNOME Shell as frequently if Location services are turned off completely in the Privacy setting. Will need a bit more time to confirm this though.
Comment 3 Jonas Ådahl 2017-04-20 12:55:26 UTC
(In reply to Peter Y. Chuang from comment #2)
> I am sorry, but I'm not sure how to do that. I'd appreciate if you point me
> to the instruction on how to do that. Thank you.
> 

This page might be relevant for you I suspect: https://wiki.archlinux.org/index.php/Debug_-_Getting_Traces
Comment 4 Peter Y. Chuang 2017-04-20 18:25:59 UTC
Created attachment 350157 [details]
coredumpctl gdb
Comment 5 Peter Y. Chuang 2017-04-20 18:26:25 UTC
Created attachment 350158 [details]
coredumpctl info
Comment 6 Peter Y. Chuang 2017-04-20 18:32:07 UTC
Thanks @Jonas.

I'm not sure if I am doing it correctly, and forgive me if that's not what you need. I've recompiled gnome-shell with the latest commit and did a little digging with coredumpctl (see attachments).

Let me know if you need anything else.
Comment 7 Peter Y. Chuang 2017-04-20 18:37:44 UTC
Created attachment 350159 [details]
coredumpctl gdb
Comment 8 Jonas Ådahl 2017-04-21 03:04:08 UTC
It seems like Javascript calls directly into libgweather, and that its libgweather that crashes. Could you install the debug symbols for libgweather too and attach another coredumpctl gdb output?
Comment 9 Peter Y. Chuang 2017-04-21 06:44:42 UTC
This is what I've got:


  • #0 gweather_location_get_timezone
    at gweather-location.c line 932
  • #1 ffi_call_unix64
  • #2 ffi_call
  • #3 0x00007f155536881f in
  • #4 0x00007f1555369ed4 in
  • #5 0x00007f1555d446db in
  • #6 0x00007ffcd9275ec8 in
  • #7 0x00007ffcd9275df0 in
  • #8 0x0000000000000000 in

Comment 10 Peter Y. Chuang 2017-04-21 06:46:15 UTC


  • #0 __strcmp_sse2_unaligned
  • #1 gweather_location_get_timezone
    at gweather-location.c line 937
  • #2 ffi_call_unix64
  • #3 ffi_call
  • #4 0x00007f3637ff481f in
  • #5 0x00007f3637ff5ed4 in
  • #6 0x00007f36389d06db in
  • #7 0x00007fff82537d88 in
  • #8 0x00007fff82537cb0 in
  • #9 0x0000000000000000 in
  • #0 gweather_location_get_timezone
    at gweather-location.c line 936
  • #1 ffi_call_unix64
  • #2 ffi_call
  • #3 0x00007f6f2944481f in
  • #4 0x00007f6f29445ed4 in
  • #5 0x00007f6f29e206db in
  • #6 0x00007ffed6870618 in
  • #7 0x00007ffed6870540 in
  • #8 0x0000000000000000 in

Comment 11 Peter Y. Chuang 2017-04-23 10:12:41 UTC
I have been able to reproduce the same behaviour on Fedora Rawhide.
Comment 12 Florian Müllner 2017-04-24 19:24:14 UTC
Can you apply the patch from bug 780278?
Comment 13 Peter Y. Chuang 2017-04-24 19:34:14 UTC
If I'm not mistaken, the current version of libgweather on Arch Linux is built off the last commit of the master branch, so the patch you've just mentioned should have already been included. 

https://git.archlinux.org/svntogit/packages.git/tree/libgweather/repos/extra-x86_64/PKGBUILD

This is either a different bug, or that patch hasn't entirely solved whatever problem you were trying to solve.
Comment 14 Peter Y. Chuang 2017-04-25 08:57:32 UTC
The whole weather/libgweather thing can run kind of reliably after I run: 

GSETTINGS_BACKEND=dconf gsettings reset org.gnome.Weather.Application locations 
GSETTINGS_BACKEND=dconf gsettings set org.gnome.Weather.Application automatic-location false

Turning automatic location back on will start to crash things, and it seems especially crashy if "org.gnome.Weather.Application locations" isn't empty. 

However, having "org.gnome.Weather.Application locations" not empty and automatic location set to 'false' seem to have no problem.

And FYI, since I often use vpn, when automatic location in gnome-weather is on, the weather info inside the gnome-shell message tray is often not the same as in gnome-weather. E.g., if I'm physically in city A but vpn to city B, the weather in the message tray appears to be city B's, while the one inside gnome-weather is city A's, and I've been wondering if this specific use case of mine contributes to the instability in weather/libgweather/shell.
Comment 15 Florian Müllner 2017-04-27 12:40:07 UTC
I found another libgweather issue:
https://bugzilla.gnome.org/show_bug.cgi?id=781828
Comment 16 Florian Müllner 2017-04-28 20:27:12 UTC
*** Bug 781913 has been marked as a duplicate of this bug. ***
Comment 17 Florian Müllner 2017-04-28 20:28:29 UTC
Can people affected by this bug please test the libgweather patches from bug 780278 and bug 781828?
Comment 18 Peter Y. Chuang 2017-04-28 20:42:40 UTC
I've built libgweather from the latest master with the patch from bug 781828 and tried it for a day. So far it doesn't seem to make much difference.

It's stable if automatic location is off, so it's kind of usable for me, though turning on automatic location and having entries inside "org.gnome.Weather.Application locations" still crash shell almost as soon as logging in.
Comment 19 GNOME Infrastructure Team 2021-07-05 14:13:22 UTC
GNOME is going to shut down bugzilla.gnome.org in favor of  gitlab.gnome.org.
As part of that, we are mass-closing older open tickets in bugzilla.gnome.org
which have not seen updates for a longer time (resources are unfortunately
quite limited so not every ticket can get handled).

If you can still reproduce the situation described in this ticket in a recent
and supported software version, then please follow
  https://wiki.gnome.org/GettingInTouch/BugReportingGuidelines
and create a new ticket at
  https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/

Thank you for your understanding and your help.