Bug 453103

Summary:	Image Thumbnails Aren't Generated
Product:	[Applications] dolphin	Reporter:	ElectronicsArchive
Component:	view-engine: general	Assignee:	Dolphin Bug Assignee <dolphin-bugs-null>
Status:	RESOLVED WORKSFORME
Severity:	normal	CC:	dolphin-bugs-null, nate
Priority:	NOR
Version First Reported In:	22.04.0
Target Milestone:	---
Platform:	Kubuntu
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description ElectronicsArchive 2022-04-27 22:20:41 UTC

SUMMARY
After I upgraded to the newest LTS version of Ubuntu / Kubuntu (22.04),
( Wiped the system, new install )
Dolphin hasn't been showing image thumbnails anymore.

I checked the '~/.xsession-errors' and only found this non-descriptive error:
'org.kde.dolphin: Failed to generate hover sequence preview #1 for file "<path>" (attempt <attempt>/3)'
( Many of times, for any images I hovered over )

STEPS TO REPRODUCE
1. Open a folder containing images 

OBSERVED RESULT
- PNG, WEBP, WEBM, JPG, GIF files have no thumbnails

EXPECTED RESULT
Image files have thumbnails

SOFTWARE/OS VERSIONS

Linux/KDE Plasma: Kubuntu 22.04  / 5.24.4
(available in About System)
KDE Plasma Version: 5.24.4
KDE Frameworks Version: 5.93.0
Qt Version: 5.15.3

ADDITIONAL INFORMATION

Comment 1 Antonio Rojas 2022-04-29 10:24:27 UTC

Is this in an NTFS volume?

Comment 2 ElectronicsArchive 2022-04-29 21:09:55 UTC

(In reply to Antonio Rojas from comment #1)
> Is this in an NTFS volume?

No, ext4.

Comment 3 ElectronicsArchive 2022-05-02 11:44:26 UTC

Out of desperation I decided to reinstall my system once again..
At least it worked out, Dolphin now seems to work.

Nonetheless the error message isn't exactly great.
It would be lovely to get a reason for it failing.

Also not having it be disabled anywhere in the UI is unfortunate.

Comment 4 Nate Graham 2022-05-03 16:36:12 UTC

If it's working now, I don't know if there's any way we can diagnose the original problem, unfortunately.

Comment 5 ElectronicsArchive 2022-05-04 01:50:14 UTC

(In reply to Nate Graham from comment #4)
> If it's working now, I don't know if there's any way we can diagnose the
> original problem, unfortunately.

Well yeah, thanks anyways~