Created attachment 55043 [details] Debug output Version: unspecified (using KDE 4.5.4) OS: Linux OpenShot is a video editor program written in pygtk, and crashes when I try to start it. I'm attaching debug output and GDB trace. Reproducible: Didn't try KDE 4.5.4, oxygen-gtk 1.0 git branch (89f26), openshot 1.2.2, pygtk 2.22.0
Created attachment 55044 [details] GDB trace of the crash
Mentioned line in trace is: _palette.setColor( Palette::Active, Palette::SelectedText, ColorUtils::Rgba::fromKdeOption( _kdeGlobals.getValue( "[Colors:Selection]", "ForegroundNormal" ) ) );
could you try to argb blacklist the application ? (see README for details) Not sure it will do the trick though.
(In reply to comment #3) > could you try to argb blacklist the application ? (see README for details) > Not sure it will do the trick though. I've added openshot and it works now. Thank you.
whats the name of the application you added ? (so that we add it in official sources) ? openshot ? Thanks in adv.
(In reply to comment #5) > whats the name of the application you added ? (so that we add it in official > sources) ? openshot ? Yes, I've added this line: disable:openshot Actually, 'openshot' is a python file and in ps output, python is the process runs this application but adding openshot just worked. > Thanks in adv.
Oh also, sylpheed[1] is another application starts to work after adding to blacklist. Can you also add disable:sylpheed to blacklist? [1] http://sylpheed.sraoss.jp/en/
Created attachment 55047 [details] Jamin application screenshot Jamin[1] does not work well with oxygen-gtk and disabling it in argb file fixes the rendering issue. Can you add disable:jamin line to blacklist? [1] http://jamin.sourceforge.net/en/about.html
Hmm.. i think we'd better have a dedicated bug for people to post there apps to blacklist. BTW, an issue similar to one with jamin is in GIMP when compositing manager is working - selection in the drawing area has transparent lines instead of black. At least GIMP 2.4.
Please post other apps to blacklist to bug 260640 so that we wouldn't have many bugs for similar issue.
*** This bug has been marked as a duplicate of bug 260640 ***