Bug 1001390

Created attachment 790718 [details]
File: backtrace

Created attachment 790719 [details]
File: cgroup

Created attachment 790720 [details]
File: core_backtrace

Created attachment 790721 [details]
File: dso_list

Created attachment 790722 [details]
File: environ

Created attachment 790723 [details]
File: limits

Created attachment 790724 [details]
File: maps

Created attachment 790725 [details]
File: open_fds

Created attachment 790726 [details]
File: proc_pid_status

Another user experienced a similar problem:

This happened after I installed Synology Cloud station (64 bits version) as root. (running the ./install script)
as can be downloaded here: 
http://www.synology.com/en-us/support/download/DS1812+

reporter:       libreport-2.1.10
backtrace_rating: 4
cmdline:        gnome-shell --sm-client-id 104f26451db0157e8b138295050790295100000016190000
crash_function: g_wakeup_new
executable:     /usr/bin/gnome-shell
kernel:         3.11.6-301.fc20.x86_64
package:        gnome-shell-3.10.2.1-3.fc20
reason:         gnome-shell killed by SIGTRAP
runlevel:       N 5
type:           CCpp
uid:            1000

Another user experienced a similar problem:

Minimized virt-manager window. Computer locked up (mouse was active, but could not bring focus to windows. Keyboard did not function). After some amount of time-~2minutes or so-an ABRT gnome-shell error message popped up.

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

This is happening anywhere from 2-6 times per day. Even a workaround would be nice...

This issue was resolved by running virt-manager as the logged-in local user (as opposed to starting virt-manager as root while logged into another user account locally).

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.