Compiz crushes while starting IEP

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Run the executable

What is the expected output? What do you see instead?
When extract files from archive and then run the executable, I expect IEP to 
start. Instead, the empty window frame appears and start blinking until I force 
IEP to close. Then an error about the crush of Compiz appears and the system 
partly freezes until I restart the x-server with Ctrl+Alt+Backspace.

What version of the product are you using? On what operating system?
v. 3.1.1 for linux 32 bit system

Please provide any additional information below.
I had the same problem with the previous version.

Original issue reported on code.google.com by o.pischa...@gmail.com on 13 Jan 2013 at 4:16

[GoogleCodeExporter]

I'm going to throw a few ideas at you. Maybe we get lucky. 

Since Compiz is OpenGl based, maybe Qt needs its QtOpenGl library. The easiest 
way to test this is to download Pyzo distro (which comes with all PySide/Qt 
libs) and run the pyzo executable (which launches IEP): 
http://pyzo.org/downloads.html

Maybe setting the Qt theme will help? In "~/.iep/fonfig.ssdf" in the "view" 
section, can you set "qtstyle = 'Cleanlooks'".

Original comment by almar.klein@gmail.com on 15 Jan 2013 at 1:24

• Changed state: Accepted

[GoogleCodeExporter]

Hello!

Sorry for the delay. These two did not work. The problem is the same.

Do you have more suggestions?

I do not know if this helps but there is something wrong with my gtk. The 
Matplotlib graphs have not worked until I changed "gtk" to "qt4" in .matplotlib

Regards,
Alexandr

Original comment by o.pischa...@gmail.com on 23 Jan 2013 at 7:50

[GoogleCodeExporter]

More suggestions then :)  I don't expect your GTK problems to be a problem, 
since IEP runs on Qt.

The following requires changing some of the source code. In "help > about" get 
the IEP source directory.

In __init__.py, in the function startIep(), comment the line:
QtGui.QApplication.setDesktopSettingsAware(True)

In iepcore/main.py, you can try playing around with (or disable) the code 
around the paintEvent and paintNow methods.

In codeeditor/qt.py you can give PyQt4 preference over PySide.

Good luck :)

Original comment by almar.klein@gmail.com on 23 Jan 2013 at 9:06

[GoogleCodeExporter]

I did not understand where is the "help -> about" which you mention?

Original comment by o.pischa...@gmail.com on 30 Jan 2013 at 6:40

[GoogleCodeExporter]

I meant in the IEP menu, but that's not really possible if IEP wont start :)

In the executable there's a directory called "source". There's the IEP source 
code which you can modify to hopefully fix this.

Original comment by almar.klein@gmail.com on 31 Jan 2013 at 6:05

[GoogleCodeExporter]

I have found this already. :)
I tried to do the mentioned above: comment in __init.py__, disabled in main.py, 
and changed the order in qt.py. It still does not work. Actually, nothing has 
changed - the problem remains.

Original comment by o.pischa...@gmail.com on 31 Jan 2013 at 8:55

[GoogleCodeExporter]

Going at it from the other side ...

Could you try to run a minimal PySide example? (something like 
http://qt-project.org/wiki/Hello-World-in-PySide) You can run it with PySide by 
running the python executable that comes with Pyzo.

If the example does not work, the problem is related to PySide. If it does, 
there's something wrong in IEP. 

Original comment by almar.klein@gmail.com on 31 Jan 2013 at 9:32

[GoogleCodeExporter]

Hello again!
The example does not work. I have installed the PySide but it still does not 
work. What can I do now?

Original comment by o.pischa...@gmail.com on 15 Feb 2013 at 5:00

[GoogleCodeExporter]

You mean the example suffers from the same problem? Then I propose you file a 
bug report with PySide.

As for IEP, you can also run it with PyQt4, you may need to make a small change 
in iep/codeeditor/qt.py to give pyqt4 preference over PySide.

Original comment by almar.klein@gmail.com on 16 Feb 2013 at 8:20

[GoogleCodeExporter]

As part of migrating our code repositories from Googlecode
to Bitbucket, all IEP issues are now tracked at 
https://bitbucket.org/iep-project/iep/issues

To view this issue, use this link (with X replaced by the issue number):
https://bitbucket.org/iep-project/iep/issue/X

Issues on Bitbucket can be created by anyone. Commenting on issues requires 
login via Bitbucket, Google, Twitter or Github.

Original comment by almar.klein@gmail.com on 11 Jun 2013 at 2:40

• Changed state: Moved