Bug 1146197

Created attachment 940864 [details]
File: backtrace

Created attachment 940865 [details]
File: cgroup

Created attachment 940866 [details]
File: core_backtrace

Created attachment 940867 [details]
File: dso_list

Created attachment 940868 [details]
File: environ

Created attachment 940869 [details]
File: exploitable

Created attachment 940870 [details]
File: limits

Created attachment 940871 [details]
File: maps

Created attachment 940872 [details]
File: open_fds

Created attachment 940873 [details]
File: proc_pid_status

Created attachment 940874 [details]
File: var_log_messages

Another user experienced a similar problem:

crash reported after lohhing on to my user account.

reporter:       libreport-2.2.3
backtrace_rating: 4
cmdline:        /usr/bin/gnome-shell
executable:     /usr/bin/gnome-shell
kernel:         3.16.6-200.fc20.x86_64
package:        gnome-shell-3.10.4-8.fc20
reason:         gnome-shell killed by SIGSEGV
runlevel:       N 5
type:           CCpp
uid:            1000

Created attachment 951426 [details]
Logs from my crash if it helps.

Let me know if anyone needs more information.
Thanks, Devon

Occurs every time in guest OS when I switching between several VM in gnome-boxes.

Created attachment 960499 [details]
screenshot of htop (many gnome-shell processes on guest machine strange....)

This message is a reminder that Fedora 21 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 21. 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 '21'.

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 21 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.

Fedora 21 changed to end-of-life (EOL) status on 2015-12-01. Fedora 21 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.

Please could we reopen this?  I have been redirected here by ABRT.  I am running Fedora 28 x86_64.

--- Running report_uReport ---
('report_uReport' completed successfully)

--- Running analyze_CCpp ---
Ok to upload core dump? (It may contain sensitive data). If your answer is 'No', a stack trace will be generated locally. (It may download a huge amount of data). 'YES'
Querying server settings
Retrace server can not be used, because the crash is too large. Try local retracing.
The size of your crash is 1.5 GiB, but the retrace server only accepts crashes smaller or equal to 1.2 GiB.
Do you want to generate a stack trace locally? (It may download a huge amount of data but reporting can't continue without stack trace). 'YES'
Analyzing coredump 'coredump'
Missing build id: libnvidia-glcore.so.390.77
Missing build id: libnvidia-tls.so.390.77
Missing build id: libGLX_nvidia.so.0
Missing build id: libnvidia-egl-wayland.so.1
Missing build id: libnvidia-glsi.so.390.77
Missing build id: libEGL_nvidia.so.0
All debuginfo files are available
Generating backtrace
Backtrace is generated and saved, 84515 bytes

--- Running analyze_BodhiUpdates ---
Looking for similar problems in bugzilla
Duplicate bugzilla bug '#1146197' was found
Searching for updates
No updates for this package found

Created attachment 1477887 [details]
output from coredumpctl gdb

Abrt reports, the same crash on Fedora 31.
It will happens on every logout/shut down.

This message is a reminder that Fedora 31 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 31 on 2020-11-24.
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 '31'.

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 31 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.

Fedora 31 changed to end-of-life (EOL) status on 2020-11-24. Fedora 31 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.