Description of problem: I searched for several citys in germany. 1. Olpe, no result 2. Siegen, no result 3. Köln, no result, application crashed Don't know more, sorry ^^ Version-Release number of selected component: gjs-1.42.0-1.fc21 Additional info: reporter: libreport-2.3.0 backtrace_rating: 4 cmdline: /usr/bin/gjs /usr/share/org.gnome.Weather/org.gnome.Weather.Application --gapplication-service crash_function: gtk_tree_model_iter_n_children executable: /usr/bin/gjs-console kernel: 3.17.1-302.fc21.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 gtk_tree_model_iter_n_children at gtktreemodel.c:1585 #1 gweather_location_entry_activate at location-entry.c:216 #4 g_signal_emitv at gsignal.c:3048 #5 gtk_binding_entry_activate at gtkbindings.c:637 #6 binding_activate at gtkbindings.c:1423 #7 gtk_bindings_activate_list at gtkbindings.c:1484 #8 gtk_bindings_activate_event at gtkbindings.c:1571 #9 gtk_entry_key_press at gtkentry.c:4866 #10 _gtk_marshal_BOOLEAN__BOXED at gtkmarshalers.c:85 #15 gtk_widget_event_internal at gtkwidget.c:7773
Created attachment 949192 [details] File: backtrace
Created attachment 949193 [details] File: cgroup
Created attachment 949194 [details] File: core_backtrace
Created attachment 949195 [details] File: dso_list
Created attachment 949196 [details] File: environ
Created attachment 949197 [details] File: exploitable
Created attachment 949198 [details] File: limits
Created attachment 949199 [details] File: maps
Created attachment 949200 [details] File: open_fds
Created attachment 949201 [details] File: proc_pid_status
Created attachment 949202 [details] File: var_log_messages
A fix can be found in https://bugzilla.gnome.org/show_bug.cgi?id=739899
Another user experienced a similar problem: I dont know. reporter: libreport-2.3.0 backtrace_rating: 4 cmdline: /usr/bin/gjs /usr/share/org.gnome.Weather/org.gnome.Weather.Application --gapplication-service crash_function: gtk_tree_model_iter_n_children executable: /usr/bin/gjs-console kernel: 3.17.4-301.fc21.x86_64 package: gjs-1.42.0-1.fc21 reason: gjs-console killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000
Another user experienced a similar problem: I even have not noticed there was a bug. reporter: libreport-2.3.0 backtrace_rating: 4 cmdline: /usr/bin/gjs /usr/share/org.gnome.Weather/org.gnome.Weather.Application --gapplication-service crash_function: gtk_tree_model_iter_n_children executable: /usr/bin/gjs-console kernel: 3.19.3-200.fc21.x86_64 package: gjs-1.42.0-1.fc21 reason: gjs-console killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000
This message is a reminder that Fedora 21 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 21. 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 '21'. 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 21 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 21 changed to end-of-life (EOL) status on 2015-12-01. Fedora 21 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.