Bug 1036662

Created attachment 831553 [details]
File: backtrace

Created attachment 831554 [details]
File: cgroup

Created attachment 831555 [details]
File: core_backtrace

Created attachment 831556 [details]
File: dso_list

Created attachment 831557 [details]
File: environ

Created attachment 831558 [details]
File: limits

Created attachment 831559 [details]
File: maps

Created attachment 831561 [details]
File: open_fds

Created attachment 831562 [details]
File: proc_pid_status

Created attachment 831563 [details]
File: var_log_messages

Another user experienced a similar problem:

I have this problem everytime I close the lid of the laptop to suspend it. Everytime I resume the suspend process Gnome Shell doesn't start properly. If it starts both screen lightness and sound are to 0 and I get a chance to report this problem. If it doesn't start I only get a random number of '\0's in /var/log/messages.

Using Fedora 20 upgraded from a Fedora 18 on a Thinkpad E330.
Kernel: 3.12.7-300.fc20.x86_64

reporter:       libreport-2.1.11
backtrace_rating: 4
cmdline:        /usr/bin/gnome-shell
crash_function: _g_log_abort
executable:     /usr/bin/gnome-shell
kernel:         3.12.7-300.fc20.x86_64
package:        gnome-shell-3.10.2.1-3.fc20
reason:         gnome-shell killed by SIGABRT
runlevel:       N 5
type:           CCpp
uid:            1000

This time the screensaver hadn't kicked in after resume.  Potential security issue, since a working session is exposed on resume.

Almost half of the times when resuming the screensaver doesn't kick in.

Another user experienced a similar problem:

Crash reporter showed up after reboot.  New Fedora 20 install - I installed the "Gnome Desktop" from the 64bit netinstall. Ran an update today, then "sudo yum groupinstall 'Cinnamon Desktop'". The group install finished, but when the screen locked after a timeout, I couldn't log back in with my password. Rebooted, logged into cinnamon session and the crash reporter appeared. 

reporter:       libreport-2.1.11
backtrace_rating: 4
cmdline:        /usr/bin/gnome-shell
crash_function: _g_log_abort
executable:     /usr/bin/gnome-shell
kernel:         3.12.8-300.fc20.x86_64
package:        gnome-shell-3.10.3-2.fc20
reason:         gnome-shell killed by SIGABRT
runlevel:       unknown
type:           CCpp
uid:            1000

Today gnome-shell hasn't started properly after the resume. I had a virtual terminal opened (Ctrl-Alt-F2 to ensure I use the proper term) with an htop running an saw a load of 64+. Had to kill gdm manually in order to be able to login again.

Happens with gnome-shell-3.10.3-8.fc20.x86_64 as well.

Just happened resuming from standby on gnome-shell-3.10.4-1.fc20.x86_64.

Created attachment 879819 [details]
/var/log/messages output on a crash

Yesterday closed the lid to suspend the system. Today gnome-shell won't start again, rebooted the system, opened /var/log/messages and extracted the failures. Quite interesting I'd say.

Created attachment 884229 [details]
/var/log/system log after a crash

Happened again, new log.

Another user experienced a similar problem:

Closed the lid of the laptop to go somewhere else. Opened it and everything was failing.

reporter:       libreport-2.2.3
backtrace_rating: 4
cmdline:        /usr/bin/gnome-shell
crash_function: _g_log_abort
executable:     /usr/bin/gnome-shell
kernel:         3.18.7-100.fc20.x86_64
package:        gnome-shell-3.10.4-9.fc20
reason:         gnome-shell killed by SIGABRT
runlevel:       N 5
type:           CCpp
uid:            1000

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

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 20 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 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 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.