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 782465 - Crash: gnome-shell (11) gweather_location_equal → ffi_call_unix64 → ffi_call → gjs_invoke_c_function → function_call
Crash: gnome-shell (11) gweather_location_equal → ffi_call_unix64 → ffi_call ...
Status: RESOLVED OBSOLETE
Product: libgweather
Classification: Core
Component: general
3.24.x
Other Linux
: Normal major
: future
Assigned To: libgweather-maint
libgweather-maint
Depends on:
Blocks:
 
 
Reported: 2017-05-10 17:09 UTC by Jeremy Bicha
Modified: 2021-06-09 21:08 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Jeremy Bicha 2017-05-10 17:09:31 UTC 
Ubuntu has received over 25 error reports from Ubuntu 17.04 with this crash signature. The crash appears new to gnome-shell 3.24.1.

This error is one of several keeping gnome-shell 3.24.1 from reaching all Ubuntu 17.04 users because Ubuntu has a phased-update system for users who install updates using Ubuntu's update-manager tool.

gnome-shell (11) gweather_location_equal → ffi_call_unix64 → ffi_call → gjs_invoke_c_function → function_call

+ Trace 237453

  • #0 __strcmp_sse2_unaligned
    at ../sysdeps/x86_64/multiarch/strcmp-sse2-unaligned.S line 31
  • #1 gweather_location_equal
    at gweather-location.c line 1218
  • #2 ffi_call_unix64
    at ../src/x86/unix64.S line 76
  • #3 ffi_call
    at ../src/x86/ffi64.c line 525
  • #4 gjs_invoke_c_function
    at gi/function.cpp line 1021
  • #5 function_call
    at gi/function.cpp line 1341
  • #6 ??
  • #7 ??
  • #8 ??
  • #9 ??
  • #10 ??
  • #11 ??
  • #12 ??
  • #13 ?? 






Comment 1


Jeremy Bicha





          2017-05-10 17:10:04 UTC
        



.




+
Trace
    237454






Thread 12
          (Thread 0x7fa59affd700 (LWP 5583))


    

  • 
#0
syscall

    
                at ../sysdeps/unix/sysv/linux/x86_64/syscall.S
                  line
                  38

    

    • 

  • 
#1
g_cond_wait_until

    
                at ../../../../glib/gthread-posix.c
                  line
                  1442

    

    • 

  • 
#2
g_async_queue_pop_intern_unlocked

    
                at ../../../../glib/gasyncqueue.c
                  line
                  422

    

    • 

  • 
#3
g_async_queue_timeout_pop_unlocked

    
                at ../../../../glib/gasyncqueue.c
                  line
                  570

    

    • 

  • 
#4
g_thread_pool_wait_for_new_task

    
                at ../../../../glib/gthreadpool.c
                  line
                  262

    

    • 

  • 
#5
g_thread_pool_thread_proxy

    
                at ../../../../glib/gthreadpool.c
                  line
                  296

    

    • 

  • 
#6
g_thread_proxy

    
                at ../../../../glib/gthread.c
                  line
                  784

    

    • 

  • 
#7
start_thread

    
                at pthread_create.c
                  line
                  456

    

    • 

  • 
#8
clone

    
                at ../sysdeps/unix/sysv/linux/x86_64/clone.S
                  line
                  105

    

    • 



Thread 1
          (Thread 0x7fa62bab0ac0 (LWP 1497))


    

  • 
#0
__strcmp_sse2_unaligned

    
                at ../sysdeps/x86_64/multiarch/strcmp-sse2-unaligned.S
                  line
                  31

    

    • 

  • 
#1
gweather_location_equal

    
                at gweather-location.c
                  line
                  1218

    

    • 

  • 
#2
ffi_call_unix64

    
                at ../src/x86/unix64.S
                  line
                  76

    

    • 

  • 
#3
ffi_call

    
                at ../src/x86/ffi64.c
                  line
                  525

    

    • 

  • 
#4
gjs_invoke_c_function

    
                at gi/function.cpp
                  line
                  1021

    

    • 

  • 
#5
function_call

    
                at gi/function.cpp
                  line
                  1341

    

    • 

  • 
#6
??

    • 

  • 
#7
??

    • 

  • 
#8
??

    • 

  • 
#9
??

    • 

  • 
#10
??

    • 

  • 
#11
??

    • 

  • 
#12
??

    • 

  • 
#13
??

    • 













Comment 2


Florian Müllner





          2017-05-10 19:41:33 UTC
        



Sounds like one of the station_code members is garbage, but it's not immediately obvious where that might come from.






Comment 3


gnome.org





          2017-05-14 18:40:32 UTC
        



I've been getting the same thing for the past week.  Pretty much rendered my laptop unusable.  Tried to roll anything that looked vaguely related back from the recent past.  Nothing worked.

Finally, I changed my time settings location from Budapest to Berlin and I haven't crashed in over an hour.

This bug report definitely motivated the change.  Thanks for that.

I don't want to seem ungrateful but should bad data from a third party (for weather?) be crashing my entire desktop?  It's just odd to me.

If you need any more info from me, I'd be happy to help.






Comment 4


Giovanni Campagna





          2017-06-05 04:43:41 UTC
        



Chances are this was a duplicate of bug 782761. Can you test with the newly released libgweather 2.24.1?
It should hit distros soon, but I know both Ubuntu and Fedora have been carrying more or less the same patches for a while now.
At least my shell (Fedora 26, libgweather 2.24.0 + patches) hasn't crashed it.






Comment 5


GNOME Infrastructure Team





          2021-06-09 21:08:07 UTC
        



-- GitLab Migration Automatic Message --

This bug has been migrated to GNOME's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/libgweather/-/issues/138.