Bug 1471188

Created attachment 1298458 [details]
File: backtrace

Created attachment 1298459 [details]
File: cgroup

Created attachment 1298460 [details]
File: core_backtrace

Created attachment 1298461 [details]
File: cpuinfo

Created attachment 1298462 [details]
File: dso_list

Created attachment 1298463 [details]
File: environ

Created attachment 1298464 [details]
File: limits

Created attachment 1298465 [details]
File: maps

Created attachment 1298466 [details]
File: open_fds

Created attachment 1298467 [details]
File: proc_pid_status

Created attachment 1298468 [details]
File: var_log_messages

*** Bug 1471415 has been marked as a duplicate of this bug. ***

Similar problem has been detected:

The problem was when i login on the user, at boot pc

reporter:       libreport-2.9.1
backtrace_rating: 4
cmdline:        /usr/bin/gnome-shell
crash_function: array_free
executable:     /usr/bin/gnome-shell
journald_cursor: s=39d122d0b6824d0987c967e97edb2424;i=12dcc;b=079273b07ddd41bba609d9239bd5791b;m=253fae1;t=55758302ec6e4;x=c5185fe420e99a31
kernel:         4.11.11-300.fc26.x86_64
package:        gnome-shell-3.24.3-1.fc26
reason:         gnome-shell killed by signal 6
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1000

Similar problem has been detected:

Gnome Shell crashed after I changed my wallpaper. After the crash, I was not able to login from GDM again. I tried wayland and X, both fail.
I have to use ctrl+alt+F2 to go to a terminal, do gsettings reset org.gnome.desktop.backgroud picture.url. Then the login is successful.

reporter:       libreport-2.9.1
backtrace_rating: 4
cmdline:        /usr/bin/gnome-shell
crash_function: array_free
executable:     /usr/bin/gnome-shell
journald_cursor: s=6583cd0f56354dfe9730f68ecc54a814;i=2f003;b=f2c24c7047d84db486f916c776957e83;m=a962ba9;t=55ee219a9bf42;x=92a3a0d2d7787a10
kernel:         4.13.13-200.fc26.x86_64
package:        gnome-shell-3.24.3-2.fc26
reason:         gnome-shell killed by SIGABRT
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1000

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

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 26 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 26 changed to end-of-life (EOL) status on 2018-05-29. Fedora 26
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.