Description of problem: I installed gnome-photos for the first time then opened it. It opened to the recents tab showing some blank squares with jpg file names on them, so I clicked the first one. That went to a blank page which said something to the effect of "downloading photo from google". Nothing happened for 2 or 3 minutes, then the program crashed. Version-Release number of selected component: gnome-photos-3.18.1-1.fc23 Additional info: reporter: libreport-2.6.2 backtrace_rating: 4 cmdline: /usr/bin/gnome-photos --gapplication-service crash_function: photos_mode_controller_get_window_mode executable: /usr/bin/gnome-photos global_pid: 16809 kernel: 4.2.5-300.fc23.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 photos_mode_controller_get_window_mode at photos-mode-controller.c:185 #1 photos_embed_row_changed at photos-embed.c:490 #6 gtk_tree_model_row_inserted at gtktreemodel.c:1852 #7 gtk_list_store_insert at gtkliststore.c:1282 #8 gtk_list_store_append at gtkliststore.c:1395 #9 photos_view_model_add_item at photos-view-model.c:140 #10 photos_view_model_object_added at photos-view-model.c:319 #15 photos_item_manager_add_item at photos-item-manager.c:478 #16 photos_item_manager_item_created_executed at photos-item-manager.c:116 #17 photos_single_item_job_emit_callback at photos-single-item-job.c:67
Created attachment 1089384 [details] File: backtrace
Created attachment 1089385 [details] File: cgroup
Created attachment 1089386 [details] File: core_backtrace
Created attachment 1089387 [details] File: dso_list
Created attachment 1089388 [details] File: environ
Created attachment 1089389 [details] File: exploitable
Created attachment 1089390 [details] File: limits
Created attachment 1089391 [details] File: maps
Created attachment 1089392 [details] File: mountinfo
Created attachment 1089393 [details] File: open_fds
Created attachment 1089394 [details] File: proc_pid_status
Created attachment 1089395 [details] File: var_log_messages
Should be fixed in gnome-photos-3.18.2: https://bodhi.fedoraproject.org/updates/FEDORA-2015-2e33c48936
This message is a reminder that Fedora 23 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 23. 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 '23'. 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 23 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.
I haven't seen this reoccur on F24, and Debarshi Ray says it was fixed, so probably safe to close?
Fedora 23 changed to end-of-life (EOL) status on 2016-12-20. Fedora 23 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.