[Kalzium] Kalzium molecule viewer

Alexandr Goncearenco neksa at neksa.net
Sat May 26 15:33:57 CEST 2007


On Saturday 26 May 2007, Benoît Jacob wrote:
> On Saturday 26 May 2007 14:04:25 Alexandr Goncearenco wrote:
> > Can Kalzium Moleculeviewer be used as a KPart?
>
> It already is a KPart, and Carsten just told me today that it even
> integrates in Konqueror.

Oh thanks, that's a very good news!
I'll try that.

> Can you upgrade to the latest Xorg and Mesa (6.5.3) ? If the bug still
> shows, please file a bug report either at Mesa or at dri-devel (i'm not
> sure what's more appropriate). In that case, if you want, I can also try to
> see if it's possible to modify our source code so that we don't hit this
> driver bug. If you'd like me to do that, I need a backtrace, so run kalzium
> in gdb and when the assert fails use the bt command.

Thanks, Benoit,

that's definitely radeon driver's or ati Mesa problem. Avogadro

in GLWidget::initializeGL():
glEnable( GL_LIGHTING );

triggers this error. So I do not think it can be easily resolved by commenting 
something out in Avogadro.

that's the backtrace you asked:
............
#4  0xb5ade42b in __assert_fail () from /lib/i686/cmov/libc.so.6
#5  0xb4fb45f7 in radeonUpdateSpecular (ctx=0x8cba4f0) at radeon_state.c:750
#6  0xb4fb610b in radeonEnable (ctx=0x8cba4f0, cap=2896, state=1 '\001') at 
radeon_state.c:1876
#7  0xb51006aa in _mesa_Enable (cap=2896) at main/enable.c:997
#8  0xb686df1c in Avogadro::GLWidget::initializeGL (this=0x8c3c540) 
at /home/kde-devel/kde/src/KDE/kdeedu/kalzium/libavogadro-kalzium/src/glwidget.cpp:212
#9  0xb68a48c7 in QGLWidget::glInit (this=0x8c3c540) at qgl.cpp:3062
.............

Some investigation in dri-devel tells that the assertion is bogus (!) and can 
be removed.
http://www.mail-archive.com/dri-devel%40lists.sourceforge.net/msg15082.html

I will try Mesa 6.5.3-1 from debian experimental, which is there since May'21. 
And an updated 2.6.21 kernel. I'll report success here, if you wish. 

Can I enable software rendering for Avagadro somehow, while leaving the whole 
system intact? 
(I just wish to stick to debian unstable builds of main libs as much as 
possible).

Alexander


More information about the Kalzium mailing list