Logged In: NO

Errata corrige: qt-4.3.4
Sorry

Logged In: YES
user_id=21420
Originator: NO

Is this really Qt-4.3.4 or 4.2?

I'm not sure if we're using 4.3-specific features, but we certainly haven't tested on 4.2 in ages.

Logged In: NO

$ /opt/qt4/bin/qmake -v
QMake version 2.01a
Using Qt version 4.3.4 in /opt/qt4/lib

Logged In: YES
user_id=851435
Originator: NO

What graphics card are you using there? Someone else has reported issues using Gentoo and savage dri drivers I think. They are getting a segfault at about the same point and it looks like it is due to a bug in the opengl stack of the driver that we are triggering.I am planning to go through our code and see if I can spot where we are doing something non-standard.

It would help to know what card you are using, drivers, xorg version. A backtrace would be even better if you have it built with symbols? I think we do have some kind of issue with opengl and triggering bugs in some drivers though. I am using the open source radeon driver here and it works fine on Gentoo/AMD64.

Logged In: NO

You are right, I'm using a "Savage" Card with dri support loaded.
My xorg server is the 1.3 release, the default one shipped in slack-12.
Tomorrow I'm going to try avogadro on my other slack-12 box, equipped with an nvidia gf6200 and property driver.
I'll take you up to date
....sorry for my english

Logged In: NO

Yeah, on my slackware 12 equiupped with nvidia gf6200 and closed driver (xorg server 1.3) avogadro works perfectly

Logged In: YES
user_id=851435
Originator: NO

I have been debugging our initialisation code and I think that this happens when we try our GL context. The GLX extension should give us the closest subset of features we request that it is capable of delivering and it seems to segfault instead. If you have a build with symbols it would be extremely useful to get a backtrace. Could you run Avogadro in gdb and get us a backtrace? This should help me see exactly where it is failing and possibly add in compatibility code.

Logged In: NO

Is this what you need?

$ gdb avogadro
GNU gdb 6.6
Copyright (C) 2006 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB. Type "show warranty" for details.
This GDB was configured as "i486-slackware-linux"...
Using host libthread_db library "/lib/libthread_db.so.1".
(gdb) run
Starting program: /usr/bin/avogadro
[Thread debugging using libthread_db enabled]
[New Thread -1226733872 (LWP 5937)]
Locale: "it_IT"
Found Tool: "AutoOptimization" - "Automatic Optimization Tool"
Found Tool: "AutoRotate" - "Auto Rotation Tool"
Found Tool: "Bond Centric Manipulate" - "Bond Centric Manipulation Tool"
Found Tool: "Measure" - "Click to Measure Tool"
_fragments.size() = 5
Found Tool: "Draw" - "Draws Things"
Found Tool: "Manipulate" - "Manipulation Tool"
Found Tool: "Navigate" - "Navigation Tool"
Found Tool: "Select/Rotate" - "Selection and Rotation Tool"

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread -1226733872 (LWP 5937)]
0xb69101e9 in savageGetLock () from /usr/lib/xorg/modules/dri/savage_dri.so
(gdb)
(gdb) bt

0 0xb69101e9 in savageGetLock () from /usr/lib/xorg/modules/dri/savage_dri.so

1 0xb6935115 in savageFlushCmdBuf () from /usr/lib/xorg/modules/dri/savage_dri.so

2 0xb690f47b in ?? () from /usr/lib/xorg/modules/dri/savage_dri.so

3 0x0849daa8 in ?? ()

4 0x00000001 in ?? ()

5 0xbfb984a8 in ?? ()

6 0xb7197680 in ?? () from /usr/lib/libGL.so.1

7 0x08152d60 in ?? ()

8 0x080e3420 in ?? ()

9 0xbfb984b8 in ?? ()

10 0xb690c0ae in ?? () from /usr/lib/xorg/modules/dri/savage_dri.so

11 0x08152d60 in ?? ()

12 0x00400072 in ?? ()

13 0xbfb984b8 in ?? ()

14 0x08154120 in ?? ()

15 0x080e3420 in ?? ()

16 0x08154120 in ?? ()

17 0xbfb984e8 in ?? ()

18 0xb715f205 in ?? () from /usr/lib/libGL.so.1

19 0x080e3420 in ?? ()

20 0x00000000 in ?? ()

(gdb)

Thanks for your job

Logged In: YES
user_id=851435
Originator: NO

I think we trigger a bug in the savage driver and I have no idea how to work around this one. If anyone has any ideas on this one I would love to hear them - I have had several reports of savage drivers causing Avogadro to segfault.

This is more a can't fix issue but that is not available. This is a driver issue, and unless anyone can point out a workaround I do not think there is anything that we can do other than hope the driver is fixed some day. Other than that recommending a better graphics card as we make extensive use of OpenGL and require a functional OpenGL enabled graphics driver.