[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-panel-devel
Subject:    Re: [Panel-devel] Plasma + 3d Globe == crash
From:       "Aaron J. Seigo" <aseigo () kde ! org>
Date:       2007-10-28 17:22:06
Message-ID: 200710281122.07143.aseigo () kde ! org
[Download RAW message or body]

[Attachment #2 (multipart/signed)]


On Sunday 28 October 2007, Chris Howells wrote:
> Adding a 3D globe to my plasma has been crashing since I can remember. I
> finally decided to have a look yesterday. The problem is in these few
> lines of code (some extra debugging that I added is in there too:
>
> // Get OpenGL version
> QString glversionstring = QString((const char*)glGetString(GL_VERSION));
> kDebug() << "error is " << glGetError();
> kDebug() << "GLVERSIONSTRING is " << glversionstring;
> QStringList glversioninfo =
> glversionstring.left(glversionstring.indexOf(' ')).split('.');
> kDebug() << "glversioninfo has " << glversioninfo.count() ;
>
> Leads to this output
>
> plasma(17333) BlueMarble::initializeGL:
> plasma(17333) initGL: error is  0

ok, so while this shouldn't be happening (it should be built if openGL support 
isn't found?) there should probably be a line right after the glversionstring 
one like:

if (glGetError() != GL_NO_ERROR || glversionstring.isEmpty()) {
    setFailedToLaunch(true);
    return;
}

however, it's odd that the error is GL_NO_ERROR (which is always 0) and yet 
this happens =)

-- 
Aaron J. Seigo
humru othro a kohnu se
GPG Fingerprint: 8B8B 2209 0C6F 7C47 B1EA  EE75 D6B7 2EB1 A7F1 DB43

KDE core developer sponsored by Trolltech

[Attachment #5 (application/pgp-signature)]

_______________________________________________
Panel-devel mailing list
Panel-devel@kde.org
https://mail.kde.org/mailman/listinfo/panel-devel


[prev in list] [next in list] [prev in thread] [next in thread]