Bug 264084 - Vuze crashes on startup using oxygen-gtk
Summary: Vuze crashes on startup using oxygen-gtk
Status: CLOSED DUPLICATE of bug 260640
Alias: None
Product: Oxygen
Classification: Plasma
Component: gtk2-engine (show other bugs)
Version: unspecified
Platform: Arch Linux Linux
: NOR crash
Target Milestone: ---
Assignee: Hugo Pereira Da Costa
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-01-23 15:33 UTC by Bernhard Friedreich
Modified: 2011-07-29 23:34 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
Vuze with oxygen gtk before it crashes (no I didn't manipulate the picture - the text of the list doesn't seem to render) (252.82 KB, image/png)
2011-01-23 15:33 UTC, Bernhard Friedreich
Details
Konsole output of vuze (10.95 KB, text/plain)
2011-01-23 15:34 UTC, Bernhard Friedreich
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Bernhard Friedreich 2011-01-23 15:33:49 UTC
Created attachment 56348 [details]
Vuze with oxygen gtk before it crashes (no I didn't manipulate the picture - the text of the list doesn't seem to render)

Version:           unspecified (using KDE 4.5.95) 
OS:                Linux

Vuze crashes on startup when using oxygen-gtk compiled from git. (2011/01/23)
Vuze version: 4.6

Attached you can find a screenshot how far it is coming until it crashes (and how bad it looks) as well as the konsole output when running/crashing.

Reproducible: Always

Steps to Reproduce:
Start vuze
wait for it to crash

Actual Results:  
Vuze crashes

Expected Results:  
Vuze should not crash
Comment 1 Bernhard Friedreich 2011-01-23 15:34:25 UTC
Created attachment 56349 [details]
Konsole output of vuze
Comment 2 Hugo Pereira Da Costa 2011-01-23 15:41:04 UTC
Please have a look at bug 260640.
This is likely an "argb" issue. You'd need to blacklist the application.
Look at the README file that comes with oxygen-gtk for instructions and if it works, please
- close this report
- report back the name of the application so that we can add it to official sources

Hopefully this all ARGB mess will be fixed soon (we are working on a cure), so that one would not need to blacklist applications any more.

*** This bug has been marked as a duplicate of bug 260640 ***
Comment 3 Bernhard Friedreich 2011-01-24 01:11:39 UTC
Thanks for the fast answer :)

Sadly this doesn't fix the issue for me as neither "vuze", "azureus" or "azureus.jar" work for adding to the blacklist... maybe adding java would be required which can't be the right way...

I've resigned to set a different gtk theme which works just fine...

Any other pointers into the right direction are gladly accepted... :)
Comment 4 Ruslan Kabatsayev 2011-01-24 01:21:03 UTC
What does it print to terminal?
Comment 5 Hugo Pereira Da Costa 2011-01-24 09:28:10 UTC
1/ which version of the code do you have (1.0.0, or 1.0.1, or some more recent code from git

2/ if you have 1.0.1 or more recent, can you try in a terminal

either:
  export OXYGEN_DISABLE_ARGB_HACK=1
or
  setenv OXYGEN_ARGB_DEBUG_HACK 1
(depending on which shell you use, bash/sh or csh)

3/ run the application
- does it start ?
- is there a line saying "disable:XXX" in the terminal (at startup), and what does it say ?

Or is that what you already did before ?