Bug 188017

Summary: Video colours inverted after digiKam started
Product: [Applications] digikam Reporter: Mathias Lindner <monoceros84>
Component: Preview-VideoAssignee: Digikam Developers <digikam-bugs-null>
Status: RESOLVED FIXED    
Severity: normal    
Priority: NOR    
Version: 0.10.0   
Target Milestone: ---   
Platform: Ubuntu   
OS: Linux   
Latest Commit: Version Fixed In: 1.0.0

Description Mathias Lindner 2009-03-24 18:34:37 UTC 
Version:           0.10 (using KDE 4.2.0)
OS:                Linux
Installed from:    Ubuntu Packages

Each time digiKam was started - and no matter if it's still running or already quit - every video in every player shows inverted colours. This is until X is re-started by system re-start or by hitting Ctrl-Alt-Back. Before digiKam is started everything is fine.

I am running Ubuntu with Gnome, Nvidia graphics card and all new updates, drivers and kernel.
I have tried MPlayer, VLC and Totem with different video types (AVI, MPG, OGG, WMV).
Comment 1 caulier.gilles 2009-03-24 21:10:36 UTC 
digiKam use Phonon player from KDE core. not VLC, mplayer, and Totem... I think it's based on xine core.

It's not digiKam at all. all is delegate to Phonon to play with video files.

Gilles Caulier
Comment 2 Mathias Lindner 2009-03-24 22:51:42 UTC 
Yes, but after I have started digiKam none of my video players is working anymore with correct colours. I don't talk about playing videos directly in digiKam...
Comment 3 caulier.gilles 2009-03-24 22:54:44 UTC 
yes, but when you start digiKam, Phonon component is initialized. Thi sload xine libraries which can have some problem on your system.

Try to play with xine frontend to see if it's reproducible.

Gilles Caulier
Comment 4 Andi Clemens 2009-07-02 22:58:41 UTC 
What about this one?

To sum it up: Before starting digiKam, try using another video player first.
As Gilles mentioned, we don't implement our own video player here, we use Phonon.
So if digiKam fails, all the other KDE players (dragon player, kmplayer, etc) should have failed, too.
Comment 5 Mathias Lindner 2009-07-03 01:06:34 UTC 
This one is solved. There was a patch of Phonon and now it's working perfectly...