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 782467 - Crash: g_assertion_message_expr → st_box_layout_child_set_property → ffi_call_unix64 → ffi_call
Crash: g_assertion_message_expr → st_box_layout_child_set_property → ffi_call...
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
Depends on:
Blocks:
 
 
Reported: 2017-05-10 17:18 UTC by Jeremy Bicha
Modified: 2021-07-05 14:03 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Jeremy Bicha 2017-05-10 17:18:49 UTC 
Ubuntu has received a few 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 (6) g_assertion_message → g_assertion_message_expr → st_box_layout_child_set_property → ffi_call_unix64 → ffi_call

+ Trace 237455

  • #0 __GI_raise
    at ../sysdeps/unix/sysv/linux/raise.c line 58
  • #1 __GI_abort
    at abort.c line 89
  • #2 g_assertion_message
  • #3 g_assertion_message_expr
    at ../../../../glib/gtestutils.c line 2456
  • #4 st_box_layout_child_set_property
    at st/st-box-layout-child.c line 122
  • #5 ffi_call_unix64
    at ../src/x86/unix64.S line 76
  • #6 ffi_call
    at ../src/x86/ffi64.c line 525
  • #7 gjs_invoke_c_function
    at gi/function.cpp line 1010
  • #8 priv_from_js
    at gi/function.cpp line 71
  • #9 function_call
    at gi/function.cpp line 1330
  • #10 ??
  • #11 ??
  • #12 ??
  • #13 ??
  • #14 ??
  • #15 ??
  • #16 ??
  • #17 clutter_actor_remove_effect
    at clutter-actor.c line 17228
  • #18 _g_info_init
    at girepository/gibaseinfo.c line 116
  • #19 init_cached_function_data
    at gi/function.cpp line 1613
  • #20 ??
  • #21 ??
  • #22 ??
  • #23 ??
  • #24 ??
  • #25 ??
  • #26 ?? 






Comment 1


Jeremy Bicha





          2017-05-10 17:19:22 UTC
        



.




+
Trace
    237456






Thread 1
          (Thread 0x7f7a6231cac0 (LWP 1564))


    

  • 
#0
__GI_raise

    
                at ../sysdeps/unix/sysv/linux/raise.c
                  line
                  58

    

    • 

  • 
#1
__GI_abort

    
                at abort.c
                  line
                  89

    

    • 

  • 
#2
g_assertion_message

    • 

  • 
#3
g_assertion_message_expr

    
                at ../../../../glib/gtestutils.c
                  line
                  2456

    

    • 

  • 
#4
st_box_layout_child_set_property

    
                at st/st-box-layout-child.c
                  line
                  122

    

    • 

  • 
#5
ffi_call_unix64

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

    

    • 

  • 
#6
ffi_call

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

    

    • 

  • 
#7
gjs_invoke_c_function

    
                at gi/function.cpp
                  line
                  1010

    

    • 

  • 
#8
priv_from_js

    
                at gi/function.cpp
                  line
                  71

    

    • 

  • 
#9
function_call

    
                at gi/function.cpp
                  line
                  1330

    

    • 

  • 
#10
??

    • 

  • 
#11
??

    • 

  • 
#12
??

    • 

  • 
#13
??

    • 

  • 
#14
??

    • 

  • 
#15
??

    • 

  • 
#16
??

    • 

  • 
#17
clutter_actor_remove_effect

    
                at clutter-actor.c
                  line
                  17228

    

    • 

  • 
#18
_g_info_init

    
                at girepository/gibaseinfo.c
                  line
                  116

    

    • 

  • 
#19
init_cached_function_data

    
                at gi/function.cpp
                  line
                  1613

    

    • 

  • 
#20
??

    • 

  • 
#21
??

    • 

  • 
#22
??

    • 

  • 
#23
??

    • 

  • 
#24
??

    • 

  • 
#25
??

    • 

  • 
#26
??

    • 













Comment 2


Florian Müllner





          2017-05-10 17:58:11 UTC
        



Is there any log output for context? I'm afraid the traces are a bit of a mystery to me, as the only assertion that matches the messages would be this[0] (at least in gnome-shell/clutter), but it's unclear how that code would be triggered by st_box_layout_child_set_property() ...

[0] https://git.gnome.org//browse/gnome-shell/tree/src/st/st-bin.c#n186






Comment 3


Jeremy Bicha





          2017-05-10 18:20:40 UTC
        



Ok, there are 4 reports.
3 say that gnome-shell changed since the problem occurred: I think that means the user upgraded from gnome-shell 3.24.0 to 3.24.1 from the time the crash occurred to when it was processed on the user's machine.
The other 1 says that libgnome-desktop3 changed (gnome-desktop was upgraded from 3.24.0 to 3.24.1).

Ubuntu does not do offline updates at all (yet?)

I don't see any other useful context.

You could request access to errors.ubuntu.com if you want to look through these error reports yourself. There's a link to do that at https://launchpad.net/bugs/1688535






Comment 4


GNOME Infrastructure Team





          2021-07-05 14:03:54 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.