Menu

#326 I can't drawing

v_0.9.0
closed
Rendering (78)
5
2012-09-12
2009-06-02
A B
No

I try to use Avogadro 0.9.4 under Ubuntu Jautny, with the debichem repository. But I can't drawing.
Tryed start in to the console, it worked. When I drawing an atom I got these line:
('paint(', <Avogadro.GLWidget object="" at="" 0x965917c="">, ')')
But I see nothing.....

Next tryed to change display types, after then I tried drawing the console line:
QPainter::begin: Cannot paint on a null pixmap
QPainter::translate: Painter not active
QPainter::end: Painter not active, aborted
QPainter::begin: Cannot paint on a null pixmap
QPainter::translate: Painter not active
QPainter::end: Painter not active, aborted
QPainter::begin: Cannot paint on a null pixmap
QPainter::translate: Painter not active
QPainter::end: Painter not active, aborted
QPainter::begin: Cannot paint on a null pixmap
QPainter::translate: Painter not active
QPainter::end: Painter not active, aborted
('paint(', <Avogadro.GLWidget object="" at="" 0x908b17c="">, ')')
Versioned config - loading.
Object::disconnect: Unexpected null parameter
GLWidget initialisation...
GLSL support enabled, OpenGL 2.0 support confirmed.
GLWidget initialised...
createObjects()
('paint(', <Avogadro.GLWidget object="" at="" 0x9085dbc="">, ')') #many line of this

After then I tried without compiz, but the problem is the same:
('paint(', <Avogadro.GLWidget object="" at="" 0x89c517c="">, ')')
OpenGL extension GL_ARB_texture_rectangle is present.
('paint(', <Avogadro.GLWidget object="" at="" 0x89c517c="">, ')')

Discussion

  • Marcus D. Hanwell

    This could be a config file issue. I would advise you to try upgrading to Avogadro 0.9.6 once it is available. In the short term you could try deleting ~/.config/SourceForge/Avogadro.conf. Otherwise it is possible that this is in fact a rendering/GL driver issue.

     
  • Geoff Hutchison

    Geoff Hutchison - 2009-06-12

    Can you confirm if this bug still exists in version 0.9.6?

    Thanks!

     
  • Marcus D. Hanwell

    Please open a new bug if this is still causing issues. I cannot reproduce it here, it may have been a packaging issue.