Bug 1209459

Summary: [abrt] gnome-shell: st_bin_dispose(): gnome-shell killed by SIGABRT
Product: [Fedora] Fedora Reporter: Andreas Fleig <andreasfleig>
Component: gnome-shellAssignee: Owen Taylor <otaylor>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 23CC: andreasfleig, doome, edoubrayrie, elleander86, fedora, fmuellner, hector.rufrancos.list, hinop, icywind90, jakobunt, jamescape777, jblades, martincigorraga, mkolman, nicolas.laplante, olivier.crete, otaylor, pabloganuza, richard.guenther, samuel-rhbugs, scampa.giovanni, unix.soul, youngbradley26
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/d9192ab9a2f6b750c74c54e060e7a70edcebe18a
Whiteboard: abrt_hash:46ae1e8980b0b0560405f8042d649c26d237b88c
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-12-20 13:30:09 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace
none
File: cgroup
none
File: core_backtrace
none
File: dso_list
none
File: environ
none
File: limits
none
File: maps
none
File: mountinfo
none
File: namespaces
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages none

Description Andreas Fleig 2015-04-07 12:07:46 UTC
Version-Release number of selected component:
gnome-shell-3.16.0-1.fc22

Additional info:
reporter:       libreport-2.5.0
backtrace_rating: 4
cmdline:        /usr/bin/gnome-shell
crash_function: st_bin_dispose
executable:     /usr/bin/gnome-shell
global_pid:     2338
kernel:         4.0.0-0.rc5.git4.1.fc22.x86_64
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (10 frames)
 #4 st_bin_dispose at /usr/lib64/gnome-shell/libgnome-shell.so
 #6 clutter_actor_destroy at /lib64/libclutter-1.0.so.0
 #7 ffi_call_unix64 at /lib64/libffi.so.6
 #8 ffi_call at /lib64/libffi.so.6
 #9 0x00007fcbceef249a in at /lib64/libgjs.so.0
 #11 js::Invoke(JSContext*, JS::CallArgs, js::MaybeConstruct) at /lib64/libmozjs-24.so
 #12 Interpret(JSContext*, js::RunState&) at /lib64/libmozjs-24.so
 #13 js::RunScript(JSContext*, js::RunState&) at /lib64/libmozjs-24.so
 #14 js::Invoke(JSContext*, JS::CallArgs, js::MaybeConstruct) at /lib64/libmozjs-24.so
 #15 js::Invoke(JSContext*, JS::Value const&, JS::Value const&, unsigned int, JS::Value*, JS::Value*) at /lib64/libmozjs-24.so

Comment 1 Andreas Fleig 2015-04-07 12:07:49 UTC
Created attachment 1011723 [details]
File: backtrace

Comment 2 Andreas Fleig 2015-04-07 12:07:50 UTC
Created attachment 1011724 [details]
File: cgroup

Comment 3 Andreas Fleig 2015-04-07 12:07:52 UTC
Created attachment 1011725 [details]
File: core_backtrace

Comment 4 Andreas Fleig 2015-04-07 12:07:53 UTC
Created attachment 1011726 [details]
File: dso_list

Comment 5 Andreas Fleig 2015-04-07 12:07:54 UTC
Created attachment 1011727 [details]
File: environ

Comment 6 Andreas Fleig 2015-04-07 12:07:55 UTC
Created attachment 1011728 [details]
File: limits

Comment 7 Andreas Fleig 2015-04-07 12:07:57 UTC
Created attachment 1011729 [details]
File: maps

Comment 8 Andreas Fleig 2015-04-07 12:07:58 UTC
Created attachment 1011730 [details]
File: mountinfo

Comment 9 Andreas Fleig 2015-04-07 12:07:59 UTC
Created attachment 1011731 [details]
File: namespaces

Comment 10 Andreas Fleig 2015-04-07 12:08:00 UTC
Created attachment 1011732 [details]
File: open_fds

Comment 11 Andreas Fleig 2015-04-07 12:08:01 UTC
Created attachment 1011733 [details]
File: proc_pid_status

Comment 12 Andreas Fleig 2015-04-07 12:08:02 UTC
Created attachment 1011734 [details]
File: var_log_messages

Comment 13 jakobunt 2015-05-27 22:11:57 UTC
Another user experienced a similar problem:

First login after update to Fedora 22

reporter:       libreport-2.5.1
backtrace_rating: 4
cmdline:        /usr/bin/gnome-shell
crash_function: st_bin_dispose
executable:     /usr/bin/gnome-shell
global_pid:     1874
kernel:         4.0.4-301.fc22.x86_64
package:        gnome-shell-3.16.2-1.fc22
reason:         gnome-shell killed by SIGABRT
runlevel:       N 5
type:           CCpp
uid:            1026

Comment 14 Hector Rufrancos 2015-06-16 11:20:14 UTC
Another user experienced a similar problem:

Thunderbird got email and called up a notification bubble. This crashed gnome-shell user theme and subsequently trying to restart gnome-shell caused it to crash.

reporter:       libreport-2.5.1
backtrace_rating: 4
cmdline:        /usr/bin/gnome-shell
crash_function: st_bin_dispose
executable:     /usr/bin/gnome-shell
global_pid:     2148
kernel:         4.0.4-303.fc22.x86_64
package:        gnome-shell-3.16.2-1.fc22
reason:         gnome-shell killed by SIGABRT
runlevel:       N 5
type:           CCpp
uid:            1000

Comment 15 Samuel Sieb 2015-09-18 22:53:46 UTC
Another user experienced a similar problem:

I think I was switching virtual desktops.

reporter:       libreport-2.6.2
backtrace_rating: 4
cmdline:        gnome-shell --sm-client-id 10be8a6de1cf08098f138336749826217200000013650000
crash_function: st_bin_dispose
executable:     /usr/bin/gnome-shell
global_pid:     1746
kernel:         4.1.6-201.fc22.x86_64
package:        gnome-shell-3.16.3-1.fc22
reason:         gnome-shell killed by SIGABRT
runlevel:       N 5
type:           CCpp
uid:            1000

Comment 16 Florian Müllner 2015-10-20 21:44:51 UTC
*** Bug 1273187 has been marked as a duplicate of this bug. ***

Comment 17 Samuel Sieb 2016-01-09 01:27:25 UTC
*** Bug 1297091 has been marked as a duplicate of this bug. ***

Comment 18 Christian Stadelmann 2016-02-20 15:35:45 UTC
This happened to me when gnome-shell was sluggish so I restarted it from Alt+F2 "r".

Comment 19 James 2016-03-22 15:00:05 UTC
Similar problem has been detected:

I came back after having my machine locked over night, unlocked it, and about right away gnome crashed and restarted automatically. Based on the applications that were up and the states that each of them were in, I have a feeling that this may have something to do with Hipchat's desktop client, but can't say for certain.

The other applications that were open:
Nylas N1
Chrome
Slack
Gnome terminal
Gedit

Though each of them was in the same state I left them in the previous night.

reporter:       libreport-2.6.4
backtrace_rating: 4
cmdline:        /usr/bin/gnome-shell
crash_function: st_bin_dispose
executable:     /usr/bin/gnome-shell
global_pid:     19813
kernel:         4.4.4-301.fc23.x86_64
package:        gnome-shell-3.18.4-1.fc23
reason:         gnome-shell killed by SIGABRT
runlevel:       N 5
type:           CCpp
uid:            1000

Comment 20 Fedora End Of Life 2016-11-24 11:39:59 UTC
This message is a reminder that Fedora 23 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 23. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '23'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 23 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 21 Fedora End Of Life 2016-12-20 13:30:09 UTC
Fedora 23 changed to end-of-life (EOL) status on 2016-12-20. Fedora 23 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.