Bug 163028

Summary: on the fly computed images on powerpc look totally ugly - seems to be an endianess problem
Product: [Unmaintained] kdelibs Reporter: Fabrice Flore-Thebault <themroc>
Component: kdeuiAssignee: kdelibs bugs <kdelibs-bugs>
Status: RESOLVED DUPLICATE    
Severity: normal CC: andresbajotierra, ephemient, majinsniper
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: Compiled Sources   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:
Attachments: Capture of my desktop

Description Fabrice Flore-Thebault 2008-06-01 21:41:38 UTC
Version:           4.0.80 in Debian Experimental (using Devel)
Installed from:    Compiled sources
OS:                Linux

All computed images, and specially all icons modified when no mouse is over, looks ugly on a Ibook (Linux/powerpc). For example the K Menu logo, which should be blue, looks somewhat orange-brown, the bug of KBugBuster is blue, the earth of Iceweasel is red ... It seems to be an endianess problem, possibly as in bug 131549.
Comment 1 Fabrice Flore-Thebault 2008-06-01 21:51:39 UTC
Created attachment 25049 [details]
Capture of my desktop
Comment 2 Majin Sniper 2008-09-02 21:11:16 UTC
I can confirm this, I am using KDE on Linux/PPC here as well. The messed up colors look exactly the same here. Oxygen Icons in yellow aren't really beautiful ;-).

This appears not to be distribution specific, occurs in Gentoo (installed from kdesvn-portage overlay; KDE 4.1) as well as on openSUSE 11.0 (I think I have 4.1 there, too).
Comment 3 Daniel Lin 2009-02-15 07:36:43 UTC
I'm running KDE 4.2.0 on Debian/ppc, and I see the same color oddities, in Plasma buttons and taskbar, Konqueror images, occasionally KWin decorations, and hover-icons in all applications' menus.  There's a good chance it's a Qt bug: http://www.qtsoftware.com/developer/task-tracker/index_html?method=entry&id=196152
Comment 4 Dario Andres 2009-05-10 01:04:49 UTC
This is a Qt4 bug.The fix will be included on Qt4.5.2
Marking as duplicate of bug 155753
Thanks

*** This bug has been marked as a duplicate of bug 155753 ***