Bug 374581

Summary:	browse missing icons on hover the image
Product:	[Applications] gwenview	Reporter:	Ferdinand Gassauer <gassauer>
Component:	general	Assignee:	Gwenview Bugs <gwenview-bugs-null>
Status:	RESOLVED FIXED
Severity:	normal	CC:	bugseforuns, mtmkls, myriam, nate
Priority:	NOR
Version First Reported In:	Git (add output of "git log -1 --oneline" to description)
Target Milestone:	---
Platform:	Ubuntu
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:
Attachments:	shows 4 emtpy boxes

Description Ferdinand Gassauer 2017-01-05 08:57:36 UTC

Created attachment 103209 [details]
shows 4 emtpy boxes

instead of seeing icons I see only 4 empty boxes above the image

compiled from source as gwenview for ubuntu 16.04 is broken.
6aea804 Use KStandardAction::DeleteFile instead of manually created action

commit 6aea80451f98dbda6f27c0eabc7acb1b97a7df4b
Author: Albert Astals Cid <aacid@kde.org>
Date:   Thu Dec 29 18:37:18 2016 +0100

    Use KStandardAction::DeleteFile instead of manually created action
    
    Less code and along with https://git.reviewboard.kde.org/r/129299/ makes the ambiguous Shift+Delete go away
    
    REVIEW: 129717

Comment 1 Christoph Feck 2017-08-02 19:09:10 UTC

*** Bug 383059 has been marked as a duplicate of this bug. ***

Comment 2 Nate Graham 2017-09-08 17:44:04 UTC

*** Bug 383059 has been marked as a duplicate of this bug. ***

Comment 3 Nate Graham 2017-09-08 17:46:32 UTC

This seems to be fixed now.

Comment 4 Ferdinand Gassauer 2017-09-09 03:31:00 UTC

just compiled gwenview using the zip file from today, the "boxes" are still empty

Comment 5 Christoph Feck 2017-09-20 12:49:55 UTC

Does it work when you run Gwenview from a shell using:

XDG_CURRENT_DESKTOP=KDE gwenview

Comment 6 Ferdinand Gassauer 2017-09-21 03:59:04 UTC

unfortunatley not

Comment 7 Nate Graham 2017-09-27 18:47:23 UTC

Nobody can reproduce this in KDE Neon when compiled from latest sources. It's most likely an issue with your environment somehow. I know for a fact that it's resolved in Kubuntu 17.04 at least, so if you can upgrade to that, this should be fixed.

Comment 8 Ferdinand Gassauer 2017-09-28 05:47:56 UTC

version 17.11.70 does not have this error any more