PixInsight RC7 Crashes on FreeBSD 9.1

[d0yy]

Hi,

I have a lot of problem with the freebsd version of PixInsight.

PixInsight crashes on several processes ( HistogramTransformation, DynamicBackgroundExtraction, LRGBCombination... )

I use the latest version update

I'm a linux user, i'm on freebsd recently, I may have forgotten a few things ...

Problems in video :

http://uploadhero.co/dl/0LLeLu47

I use KDE

Asus P8Z68-V PRO
Intel Core i5 2500K
Gskill 8go DDR3
SSD M4 Crucial
GForce G210 with nvidia proprietary driver

[Juan Conejero]

Hi,

This sounds like the wrong Qt libraries are being loaded by the PixInsight Core application. How are you running PixInsight? The *only* valid way to execute the PI Core application is, assuming that you have uncompressed the installation package on your home folder:

cd ~/PixInsight/bin
./PixInsight.sh&

or, alternatively, running the PixInsight.sh launcher script from a GUI file manager (such as Dolphin on KDE 4).

Does this help you?

[d0yy]

Hi Juan,

cd ~/PixInsight/bin
./PixInsight.sh&

Well I used this method to launch PixInsight

or, alternatively, running the PixInsight.sh launcher script from a GUI file manager (such as Dolphin on KDE 4).

I also tried, same result.

[Juan Conejero]

Really strange. Could you enter the following commands:

cd ~/PixInsight/bin
export LD_LIBRARY_PATH=.:./lib
ldd ./PixInsight

and copy/paste here the output of ldd?

[d0yy]

./PixInsight:
   libSM.so.6 => /usr/local/lib/libSM.so.6 (0x801b1d000)
   libICE.so.6 => /usr/local/lib/libICE.so.6 (0x801d24000)
   libXi.so.6 => /usr/local/lib/libXi.so.6 (0x801f3e000)
   libXrender.so.1 => /usr/local/lib/libXrender.so.1 (0x80214c000)
   libXrandr.so.2 => /usr/local/lib/libXrandr.so.2 (0x802355000)
   libfreetype.so.9 => /usr/local/lib/libfreetype.so.9 (0x80255d000)
   libfontconfig.so.1 => /usr/local/lib/libfontconfig.so.1 (0x8027e6000)
   libXext.so.6 => /usr/local/lib/libXext.so.6 (0x802a19000)
   libX11.so.6 => /usr/local/lib/libX11.so.6 (0x802c2b000)
   libgthread-2.0.so.0 => /usr/local/lib/libgthread-2.0.so.0 (0x802f60000)
   libgobject-2.0.so.0 => /usr/local/lib/libgobject-2.0.so.0 (0x803164000)
   librt.so.1 => /usr/lib/librt.so.1 (0x8033ae000)
   libglib-2.0.so.0 => /usr/local/lib/libglib-2.0.so.0 (0x8035b3000)
   libthr.so.3 => /lib/libthr.so.3 (0x803895000)
   libcom_err.so.5 => /usr/lib/libcom_err.so.5 (0x803ab7000)
   libidn.so.17 => /usr/local/lib/libidn.so.17 (0x803cb9000)
   libz.so.6 => /lib/libz.so.6 (0x803eeb000)
   libQtGui.so.4 => ./lib/libQtGui.so.4 (0x8040ff000)
   libQtSvg.so.4 => ./lib/libQtSvg.so.4 (0x804e6e000)
   libQtXml.so.4 => ./lib/libQtXml.so.4 (0x8050cb000)
   libQtWebKit.so.4 => ./lib/libQtWebKit.so.4 (0x805311000)
   libQtNetwork.so.4 => ./lib/libQtNetwork.so.4 (0x806fc5000)
   libQtCore.so.4 => ./lib/libQtCore.so.4 (0x80731d000)
   libmozjs-17.0.so => ./lib/libmozjs-17.0.so (0x807834000)
   liblcms-pxi.so => ./liblcms-pxi.so (0x807da1000)
   libstdc++.so.6 => /usr/lib/libstdc++.so.6 (0x807ff7000)
   libm.so.5 => /lib/libm.so.5 (0x808307000)
   libgcc_s.so.1 => /lib/libgcc_s.so.1 (0x808528000)
   libc.so.7 => /lib/libc.so.7 (0x808735000)
   libxcb.so.2 => /usr/local/lib/libxcb.so.2 (0x808a88000)
   libXau.so.6 => /usr/local/lib/libXau.so.6 (0x808ca3000)
   libXdmcp.so.6 => /usr/local/lib/libXdmcp.so.6 (0x808ea5000)
   libpthread-stubs.so.0 => /usr/local/lib/libpthread-stubs.so.0 (0x8090aa000)
   librpcsvc.so.5 => /usr/lib/librpcsvc.so.5 (0x8092ab000)
   libbz2.so.4 => /usr/lib/libbz2.so.4 (0x8094b4000)
   libexpat.so.6 => /usr/local/lib/libexpat.so.6 (0x8096c4000)
   libintl.so.9 => /usr/local/lib/libintl.so.9 (0x8098e7000)
   libiconv.so.3 => /usr/local/lib/libiconv.so.3 (0x809af1000)
   libpcre.so.1 => /usr/local/lib/libpcre.so.1 (0x809ded000)

[Juan Conejero]

Thank you. ldd's output looks correct. After watching your video, I must say that I have never seen anything like this on Linux or FreeBSD.

Which version of FreeBSD are you running (the output of "uname -a")?

I wonder if the nvidia proprietary driver may be causing these problems. You could try selecting software compositing:

- Open KDE's System Settings.
- Open Desktop Effects.
- Go to the Advanced tab page.
- Select Compositing type = XRender
- Click Apply.

Let's see if this fixes the problem. You can revert to hardware accelerated compositing by selecting Compositing type = OpenGL again.

[d0yy]

Thank you. ldd's output looks correct. After watching your video, I must say that I have never seen anything like this on Linux or FreeBSD.

Which version of FreeBSD are you running (the output of "uname -a")?

Last version of FreeBSD

uname -a :

Code: [Select]

FreeBSD freebsd.desktop 9.1-RELEASE FreeBSD 9.1-RELEASE #0: Sun Jul 21 02:17:45 CEST 2013     root@freebsd.desktop:/usr/obj/usr/src/sys/MONNOYAU  amd64

I wonder if the nvidia proprietary driver may be causing these problems. You could try selecting software compositing:

- Open KDE's System Settings.
- Open Desktop Effects.
- Go to the Advanced tab page.
- Select Compositing type = XRender
- Click Apply.

Let's see if this fixes the problem. You can revert to hardware accelerated compositing by selecting Compositing type = OpenGL again.

I also tried, same result.

I will try with my integrated video card (intel HD3000) to see if the problem comes from the nvidia driver.

[d0yy]

I just tried with my nvidia graphics card without proprietary driver --> Same result 

[Juan Conejero]

Hi again,

Any update on this? Unfortunately, I won't have access to FreeBSD until September (next week), so I cannot check anything related to this problem. So please don't think that I'm ignoring it.