Bug 1084599

Created attachment 882819 [details]
File: backtrace

Created attachment 882820 [details]
File: cgroup

Created attachment 882821 [details]
File: core_backtrace

Created attachment 882822 [details]
File: dso_list

Created attachment 882823 [details]
File: environ

Created attachment 882824 [details]
File: exploitable

Created attachment 882825 [details]
File: limits

Created attachment 882826 [details]
File: maps

Created attachment 882827 [details]
File: open_fds

Created attachment 882828 [details]
File: proc_pid_status

Created attachment 882829 [details]
File: var_log_messages

dmesg gives the following:

[ 8894.566913] gnome-settings-[10833]: segfault at 0 ip 00007fdddf38f03e sp 00007fffefedd090 error 4 in libgeocode-glib.so.0.0.0[7fdddf387000+e000]
[ 8899.425755] gnome-settings-[11276]: segfault at 0 ip 00007fb7e656903e sp 00007fff37debc40 error 4 in libgeocode-glib.so.0.0.0[7fb7e6561000+e000]

(In reply to Tyler Roberts from comment #0)
> Description of problem:
> Upon startup into the Gnome3 DE. Does not occur in Cinnamon. Have tried
> multiple Kernels, reinstalled @gnome and gnome-settings-daemon. Attempting
> to restart Gnome via Alt-F2 R crashes back to the "Oh No something went
> wrong screen"
> 
> Version-Release number of selected component:
> gnome-settings-daemon-3.10.2-3.fc20
> 
> Additional info:
> reporter:       libreport-2.2.0
> backtrace_rating: 4
> cmdline:        /usr/libexec/gnome-settings-daemon
> crash_function: _geocode_read_nominatim_attributes
> executable:     /usr/libexec/gnome-settings-daemon
> kernel:         3.13.6-200.fc20.x86_64
> runlevel:       N 5
> type:           CCpp
> uid:            1000
> 
> Truncated backtrace:
> Thread no. 1 (10 frames)
>  #0 _geocode_read_nominatim_attributes at geocode-reverse.c:130
>  #1 resolve_json at geocode-reverse.c:208
>  #2 on_cache_data_loaded at geocode-reverse.c:290
>  #3 g_task_return_now at gtask.c:1108
>  #4 g_task_return at gtask.c:1161
>  #5 load_contents_close_callback at gfile.c:6791
>  #6 async_ready_close_callback_wrapper at ginputstream.c:533
>  #7 g_task_return_now at gtask.c:1108
>  #8 complete_in_idle_cb at gtask.c:1117
>  #13 gtk_main at gtkmain.c:1158

Things I forgot to mention:
Fn keys no longer function after the "Oh no!" crash. Also, every time a new window is opened ,regardless of where focus is, Gnome alerts me that 'program is now available'

(In reply to Tyler Roberts from comment #0)
> Description of problem:
> Upon startup into the Gnome3 DE. Does not occur in Cinnamon. Have tried
> multiple Kernels, reinstalled @gnome and gnome-settings-daemon. Attempting
> to restart Gnome via Alt-F2 R crashes back to the "Oh No something went
> wrong screen"
> 
> Version-Release number of selected component:
> gnome-settings-daemon-3.10.2-3.fc20
> 
> Additional info:
> reporter:       libreport-2.2.0
> backtrace_rating: 4
> cmdline:        /usr/libexec/gnome-settings-daemon
> crash_function: _geocode_read_nominatim_attributes
> executable:     /usr/libexec/gnome-settings-daemon
> kernel:         3.13.6-200.fc20.x86_64
> runlevel:       N 5
> type:           CCpp
> uid:            1000
> 
> Truncated backtrace:
> Thread no. 1 (10 frames)
>  #0 _geocode_read_nominatim_attributes at geocode-reverse.c:130
>  #1 resolve_json at geocode-reverse.c:208
>  #2 on_cache_data_loaded at geocode-reverse.c:290
>  #3 g_task_return_now at gtask.c:1108
>  #4 g_task_return at gtask.c:1161
>  #5 load_contents_close_callback at gfile.c:6791
>  #6 async_ready_close_callback_wrapper at ginputstream.c:533
>  #7 g_task_return_now at gtask.c:1108
>  #8 complete_in_idle_cb at gtask.c:1117
>  #13 gtk_main at gtkmain.c:1158

This is a geocode-glib crash; reassigning.

In the mean time, you should be able to work this around by running:

  gsettings set org.gnome.desktop.datetime automatic-timezone false

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.