GNOME Bugzilla – Bug 776669
Crashes when clicking on a blank preview box in the photos tab
Last modified: 2018-01-22 15:57:47 UTC
This is found with gnome-photos 3.22.2 The program crashes with the following steps: 1. Open the program 2. Make sure you are on the tab that says photos 3. Click on any box that doesn't have a photo previewed *make sure not to have the select an item check box checked 4. Enjoy the crash
Thanks for the bug report! (In reply to Scott Cohen from comment #0) > This is found with gnome-photos 3.22.2 > The program crashes with the following steps: > 1. Open the program > 2. Make sure you are on the tab that says photos > 3. Click on any box that doesn't have a photo previewed *make sure not to > have the select an item check box checked What do you mean by "doesn't have a photo previewed"? You mean a tile without a generated thumbnail? What kind of image was it? PNG, JPEG, something else? Do you have a backtrace? I am asking because I can't reproduce this.
(In reply to Scott Cohen from comment #0) > This is found with gnome-photos 3.22.2 > The program crashes with the following steps: > 1. Open the program > 2. Make sure you are on the tab that says photos > 3. Click on any box that doesn't have a photo previewed *make sure not to > have the select an item check box checked > 4. Enjoy the crash Hi Scott, do you still facing a problem? Can you attach the sample file?
On second thoughts, I think that this is about trying to open some MIME type that's not supported by gegl:load, or a file that's weird in some way. gegl:load has next to no error handling, so if things don't work out, it crashes. There is bug 780731 to improve the error handling. If this is about some MIME type that we deliberately don't want to / can't support in the immediate short-term, then we can adjust the queries to skip them. Like we did for EPSes (bug 790191) and GIFs (bug 762725). However, for that we really need to know the MIME type that was involved here.
Please reopen and de-duplicate if you remember the MIME type.
*** This bug has been marked as a duplicate of bug 780731 ***