Adding a new empty screen cause a segmentation fault <- Compiz error #18028

New Issue

Nicola Jelmorini · 2008-11-24T19:47:52+01:00

Nicola Jelmorini commented

2008-11-24 19:47:52 +01:00

%%%Hi,

I use Blender 2.48a downloaded from Blender site.
My PC system is Ubuntu Linux Intrepid (8.10) 32 bit, 2GB RAM
My graphic card is NVidia QUADRO FX 1500M

When I try to add a new empty screen, Blender exit with a Segmentation fault. The complete message is here:

Compiled with Python version 2.5.2.
Checking for installed Python... got it!
No 3Dconnexion driver is running.
error in areawinar 6 ,areawinset
error in areawinar 9 ,areawinset
Segmentation fault

Instead when I add a duplicate screen all function well.%%%

%%%Hi, I use Blender 2.48a downloaded from Blender site. My PC system is Ubuntu Linux Intrepid (8.10) 32 bit, 2GB RAM My graphic card is NVidia QUADRO FX 1500M When I try to add a new empty screen, Blender exit with a Segmentation fault. The complete message is here: ------------------------------------------------------- Compiled with Python version 2.5.2. Checking for installed Python... got it! No 3Dconnexion driver is running. error in areawinar 6 ,areawinset error in areawinar 9 ,areawinset Segmentation fault ------------------------------------------------------- Instead when I add a duplicate screen all function well.%%%

Nicola Jelmorini commented

2008-11-24 19:47:52 +01:00

Changed status to: 'Open'

Nobody commented

2008-11-24 19:47:52 +01:00

Changed status from 'Open' to: 'Archived'

Nobody closed this issue

2008-11-24 19:47:52 +01:00

Ton Roosendaal commented

2008-11-27 17:08:56 +01:00

%%%Cannot redo here, but it might depend on the .B.blend or .blend file you loaded when you add a new screen... try to pin down what exactly causes it?%%%

Nicola Jelmorini commented

2008-11-27 20:27:29 +01:00

%%%Ok, I have some news about.

I have deleted my .B.blend file, so I can run Blender with default setting.

First test:

Starting blender without options I have no window border. Even starting Blender with "-w" option I have no window border. Trying to add a new empty screen in this case function well.

Second test:

I have started blender with "-p 0 0 1000 1000" option and only in this case Blender start with window border. Trying to add a new empty screen in this case cause the segmentation fault problem.

So for now I have determined the cause of the problem, but why Blender open without window border? And why the segmentation fault problem is present only when I force window border with the "-p" option?

On my Ubuntu system I have activated the Compiz-fusion window manager. Perhaps is this the problem? YES.
I have turned off Compiz-fusion and activated the standard Metacity window manager. Now Blender start correctly with window border, and adding a new empty screen function well without segmentation fault.

Finally I can say that the problem is resolved without Compiz, but is present with Compiz.%%%

%%%Ok, I have some news about. I have deleted my .B.blend file, so I can run Blender with default setting. First test: ----------- Starting blender without options I have no window border. Even starting Blender with "-w" option I have no window border. Trying to add a new empty screen in this case function well. Second test: ------------ I have started blender with "-p 0 0 1000 1000" option and only in this case Blender start with window border. Trying to add a new empty screen in this case cause the segmentation fault problem. So for now I have determined the cause of the problem, but why Blender open without window border? And why the segmentation fault problem is present only when I force window border with the "-p" option? On my Ubuntu system I have activated the Compiz-fusion window manager. Perhaps is this the problem? YES. I have turned off Compiz-fusion and activated the standard Metacity window manager. Now Blender start correctly with window border, and adding a new empty screen function well without segmentation fault. Finally I can say that the problem is resolved without Compiz, but is present with Compiz.%%%

Ton Roosendaal commented

2008-11-28 10:19:05 +01:00

%%%thanks for testing.
Compiz is indeed conflicting with opengl sometimes, but I heard it works fine in many cases too, especially for nvidia cards.%%%

%%%thanks for testing. Compiz is indeed conflicting with opengl sometimes, but I heard it works fine in many cases too, especially for nvidia cards.%%%

Tom Musgrove commented

2010-03-21 22:31:20 +01:00

%%%This is a generic request to test your bug report and see if it is still an issue in 2.5alpha2 if so please let me know by making a comment in this report ie 'also in 2.5alpha2' and I will add it to the 2.5 bug list.%%%

Nicola Jelmorini commented

2010-03-21 23:34:13 +01:00

%%%Hi Tom,

I have tried with Blender 2.5alpha2 64bit, but this problem not happened again.
I use now Ubuntu 9.10 64bit with Compiz activated, and Blender function very well.%%%

%%%Hi Tom, I have tried with Blender 2.5alpha2 64bit, but this problem not happened again. I use now Ubuntu 9.10 64bit with Compiz activated, and Blender function very well.%%%

Sign in to join this conversation.

No Label

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

Adding a new empty screen cause a segmentation fault <- Compiz error #18028

When I try to add a new empty screen, Blender exit with a Segmentation fault. The complete message is here:

Compiled with Python version 2.5.2. Checking for installed Python... got it! No 3Dconnexion driver is running. error in areawinar 6 ,areawinset error in areawinar 9 ,areawinset Segmentation fault

First test:

Second test:

Compiled with Python version 2.5.2.
Checking for installed Python... got it!
No 3Dconnexion driver is running.
error in areawinar 6 ,areawinset
error in areawinar 9 ,areawinset
Segmentation fault