[frameworks-kio] [Bug 350810] file open dialog freezes when browsing to /dev

[Wolfgang Bauer]

https://bugs.kde.org/show_bug.cgi?id=350810

Wolfgang Bauer  changed:

   What|Removed |Added

 Resolution|--- |UPSTREAM
 Status|UNCONFIRMED |RESOLVED

--- Comment #5 from Wolfgang Bauer  ---
(In reply to Thomas Eschenbacher from comment #4)
> I can confirm that the original bug seems to be fixed.

Ok, let's close it then, I'd say.

> Only the display is wrong, the texts of the items are all positioned
> overlapping over the preview symbols, which makes the dialog look ugly and
> the texts unreadable.

That's a completely different/unrelated problem though, and happens with all
files that do not have a proper (mimetype) icon (so the "unknown" icon is used
as fallback).
It seems the layout is done without an icon in this case, and the fallback icon
drawn on top later on.

I'm not sure if there's a bug report about that, but I remember it being
mentioned somewhere a few days ago...

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-kio] [Bug 350810] file open dialog freezes when browsing to /dev

[Thomas Eschenbacher]

https://bugs.kde.org/show_bug.cgi?id=350810

--- Comment #4 from Thomas Eschenbacher  ---
I can confirm that the original bug seems to be fixed.

Only the display is wrong, the texts of the items are all positioned
overlapping over the preview symbols, which makes the dialog look ugly and the
texts unreadable.

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-kio] [Bug 350810] file open dialog freezes when browsing to /dev

[Wolfgang Bauer]

https://bugs.kde.org/show_bug.cgi?id=350810

Wolfgang Bauer  changed:

   What|Removed |Added

 CC||wba...@tmo.at

--- Comment #3 from Wolfgang Bauer  ---
I suppose this can be closed meanwhile?

Should be fixed in Qt 5.6.0, earlier versions are not supported by KDE
Frameworks anymore, and it was an upstream problem (in Qt) anyway...

At least I cannot reproduce it on openSUSE anymore since we added the upstream
fix to our Qt 5.5.1 packages over a year ago or upgraded to 5.6.0, while it
happened reliably before.

-- 
You are receiving this mail because:
You are watching all bug changes.