I can confirm this, sushi crashes under GNOME+Wayland. ABRT fails to generate a backtrace, it claims it is "unusable".

I have the same bug on Fedora 24 + Wayland (shushi does work with X11).

There are two upstream bugs open for this:
https://bugzilla.gnome.org/show_bug.cgi?id=766750
https://bugzilla.gnome.org/show_bug.cgi?id=766750

Since it doesn't look like sushi is getting much attention upstream, I don't think it will grow Wayland support in time for Fedora 25 (in which Wayland is going to be the default).

Therefor, we have two options of handling this going forward - and they are not mutually exclusive:
1) We can patch sushi's startup script to make it use XWayland. While this is suboptimal, it will probably mean sushi will keep working, but I haven't tested that yet.

2) We can remove sushi from the default installation, since it's clearly not getting much attention upstream.

Regardless of what the Workstation WG decides to do, I think this should be a Fedora 25 Final blocker bug, according to the following criteria: https://fedoraproject.org/wiki/Fedora_25_Final_Release_Criteria#Default_application_functionality

Sorry, I accidentally linked to the same upstream bug twice. Here's the second one:

https://bugzilla.gnome.org/show_bug.cgi?id=712618

Proposed as a Blocker for 25-final by Fedora user elad using the blocker tracking app because:

 https://fedoraproject.org/wiki/Fedora_25_Final_Release_Criteria#Default_application_functionality

sushi is arguably a "default application" or at least a part of it, and it will not function properly on Fedora 25 if Fedora 25 defaults to Wayland.

I should have tested this before making noise about it. It seems to be working correctly for me on Wayland with fully-up-to-date Fedora 24.

Removing blocker proposal and closing. If you think I'm mistaken please feel free to reopen the bug or comment here asking me to reopen it.

The only crash I *am* seeing with sushi on Wayland right now is gstreamer related, and only happens for video files when gstreamer1-vaapi is installed. Since totem crashes the same way, this is not a sushi bug but rather a gstreamer1-vaapi bug.

What kind of file types have you been trying to preview that triggered this crash?

I'm really sorry for the noise. Reopening.

It seems that my laptop was NOT running wayland when I tested this (even though I told it to, weird). I tested again and yeah, it's *definitely* not working, it shows an empty window instead of a preview.

I'm restoring proposal to make this a blocker bug too, reason specified in comment 5 still stands:

>  https://fedoraproject.org/wiki/Fedora_25_Final_Release_Criteria#Default_application_functionality
> 
> sushi is arguably a "default application" or at least a part of it, and it
> will not function properly on Fedora 25 if Fedora 25 defaults to Wayland.

I tested this with sushi-3.20.0-1.fc25 on a text file and an image, and while it does not crash, it only shows a grey window instead of showing the actual contents.

This is not arguably an application that "can be launched using the standard graphical mechanism of a release-blocking desktop", OTOH it can be launched from nautilus simply by pressing a space, so some people might consider it a part of basic functionality of nautilus.

Discussed during the 2016-08-29 blocker review meeting: [1]

The decision to classify this bug as a RejectedBlocker was made as this functionality is not considered basic or integral for default-installed applications.

[1] https://meetbot.fedoraproject.org/fedora-blocker-review/2016-08-29/f25-blocker-review.2016-08-29-16.00.txt

I guess un-blocking WaylandRelated was an error, so I'm undoing it.

(In reply to Christian Stadelmann from comment #10)
> I guess un-blocking WaylandRelated was an error, so I'm undoing it.

error → mistake

this should be fixed in sushi 3.21.91

(In reply to Matthias Clasen from comment #12)
> this should be fixed in sushi 3.21.91

Yes, it is. I'd close the bug but I can't (permissions/owner)

Confirmed fixed. Closing.