Bug 1047267

Created attachment 843306 [details]
File: backtrace

Created attachment 843307 [details]
File: cgroup

Created attachment 843308 [details]
File: core_backtrace

Created attachment 843309 [details]
File: dso_list

Created attachment 843310 [details]
File: environ

Created attachment 843311 [details]
File: exploitable

Created attachment 843312 [details]
File: limits

Created attachment 843313 [details]
File: maps

Created attachment 843314 [details]
File: open_fds

Created attachment 843315 [details]
File: proc_pid_status

Created attachment 843316 [details]
File: var_log_messages

Another user experienced a similar problem:

System refusing to connect to external Bluetooth mouse (HP x4000b) after restart; prior to restart Kernel was upgraded to 3.13.6-200 and installed akmod-VirtualBox to resolve error with loading systemd-modules-load.service.  System is running on baremetal, not in VM.

Initial setup for bluetooth mouse autoconnect:

1.    bluetoothctl  >>  'trust', 'pair', 'connect' to mouse
2.    create udev rule:  echo ACTION=="add", KERNEL=="hci0", RUN+="/usr/bin/hciconfig hci0 up" > /etc/udev/rules.d/10-local.conf

    This setup has worked successfully to reconnect the mouse to the bluetooth card on the PC, until now.  Tried to reconnect to the mouse using step1 (bluetoothctl) w/out success.

reporter:       libreport-2.2.0
backtrace_rating: 4
cmdline:        /usr/bin/gnome-shell
crash_function: af_face_globals_is_digit
executable:     /usr/bin/gnome-shell
kernel:         3.13.6-200.fc20.x86_64
package:        gnome-shell-3.10.4-1.fc20
reason:         gnome-shell killed by SIGSEGV
runlevel:       N 5
type:           CCpp
uid:            1000

I realize my preoccupation with solving the bluetooth issue clouded my judgement of this segfault. I have no clue why this occurred, other than guessing; maybe a change in BIOS option, maybe something with akmod/nvidia.  Regardless, disregard previous comment.

Another user experienced a similar problem:

Started GNOME Shell with some apps set to autoload on start.

reporter:       libreport-2.1.12
backtrace_rating: 4
cmdline:        /usr/bin/gnome-shell
crash_function: af_face_globals_is_digit
executable:     /usr/bin/gnome-shell
kernel:         3.13.5-200.fc20.x86_64
package:        gnome-shell-3.10.4-1.fc20
reason:         gnome-shell killed by SIGSEGV
runlevel:       N 5
type:           CCpp
uid:            1000

Another user experienced a similar problem:

Logged into GNOME Shell

reporter:       libreport-2.2.0
backtrace_rating: 4
cmdline:        /usr/bin/gnome-shell
crash_function: af_face_globals_is_digit
executable:     /usr/bin/gnome-shell
kernel:         3.13.6-200.fc20.x86_64
package:        gnome-shell-3.10.4-1.fc20
reason:         gnome-shell killed by SIGSEGV
runlevel:       N 5
type:           CCpp
uid:            1000

Another user experienced a similar problem:

I am unsure as to how this happened.

I suspect screen sharing with Skype. If so, then it's not a Fedora problem.

The other possibility is the addition of rabbitvcs, and the rabbitvcs-nautilus plugin. This should change icons in Nautilus to indicate SVN status, but it currently does not work (see rabbitvcs web site for those issues). Again, this is not a Fedora issue, but the way Gnome developers have decided to proceed.

reporter:       libreport-2.2.1
backtrace_rating: 4
cmdline:        /usr/bin/gnome-shell
crash_function: af_face_globals_is_digit
executable:     /usr/bin/gnome-shell
kernel:         3.13.9-200.fc20.x86_64
package:        gnome-shell-3.10.4-2.fc20
reason:         gnome-shell killed by SIGSEGV
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.