• Bug#266007: general: "Unable to resolve GL/GLX symbols message when sta

    From Wolfgang Roemer@1:229/2 to All on Mon Aug 16 11:30:12 2004
    XPost: linux.debian.devel
    From: [email protected]

    Package: general
    Severity: serious
    Justification: Unknown


    Since upgrading my debian system on Aug. 16th, applications that use
    OpenGL don't start anymore with the "Unable to resolve GL/GLX symbols" message. Direct rendering is enabled and works well with glxgears for example.
    The problem seems to be related to applications using Qt.

    Special on my system is the usage of the proprietary nvidia driver for
    XFree86.

    -- System Information:
    Debian Release: 3.1
    APT prefers unstable
    APT policy: (500, 'unstable'), (500, 'testing')
    Architecture: i386 (i686)
    Kernel: Linux 2.6.5
    Locale: LANG=C, LC_CTYPE=C


    --
    To UNSUBSCRIBE, email to [email protected]
    with a subject of "unsubscribe". Trouble? Contact [email protected]

    --- SoupGate-Win32 v1.05
    * Origin: you cannot sedate... all the things you hate (1:229/2)
  • From Ben Burton@1:229/2 to All on Mon Aug 16 12:30:12 2004
    XPost: linux.debian.devel
    From: [email protected]

    reassign 266007 libqt3c102-mt
    thanks mate

    Hi. This appears to be the same issue as #264928.

    The fix is to upgrade your libqt3c102-mt to version 3:3.3.3-1, where
    this was fixed by the Qt maintainer. If you can't upgrade just yet,
    installing xlibmesa-dev is a workaround solution.

    Ben.



    --
    To UNSUBSCRIBE, email to [email protected]
    with a subject of "unsubscribe". Trouble? Contact [email protected]

    --- SoupGate-Win32 v1.05
    * Origin: you cannot sedate... all the things you hate (1:229/2)
  • From Wolfgang Roemer@1:229/2 to you on Mon Aug 16 14:00:14 2004
    From: [email protected]

    Hello Ben,

    I use already Version 3:3.3.3.1 of the libqt3c102-mt!?!?

    WR

    On Monday 16 August 2004 12:07, you wrote:
    reassign 266007 libqt3c102-mt
    thanks mate

    Hi. This appears to be the same issue as #264928.

    The fix is to upgrade your libqt3c102-mt to version 3:3.3.3-1, where
    this was fixed by the Qt maintainer. If you can't upgrade just yet, installing xlibmesa-dev is a workaround solution.

    Ben.

    -------------------------------------------------------


    --
    To UNSUBSCRIBE, email to [email protected]
    with a subject of "unsubscribe". Trouble? Contact [email protected]

    --- SoupGate-Win32 v1.05
    * Origin: you cannot sedate... all the things you hate (1:229/2)
  • From Wolfgang Roemer@1:229/2 to Ben Burton on Mon Aug 16 17:10:11 2004
    From: [email protected]

    Hello Ben,

    to be more precise:

    I did not have any OpenGL problems with the older qt-3:3.3.2. The problem started to occur with the new qt version!

    I had a look at the "solution" that was proposed for Qt in the bug you mentioned (#26492 ): The so-called solution makes everything worse: Instead
    of search for a libGL, Qt will now search explicitly for a library called libGL.so.1 which would be /usr/X11R6/lib/libGL.so.1.2 of the xlibmesa-gl package. So if that package is installed Qt will find a mesa lib explicitly searching for the DRI extension resulting in a "extension XFree86-DRI missing on display ..." message if a NVIDIA proprietary driver is installed.

    In fact I don't know exactly which change in the new Qt libary version 3:3.3.3 is responsible for the misbehaviour. I can just say for sure, that the
    problem wasn't there with the Qt 3:3.3.2 because I develop with OpenGL all
    day and it worked well for me since I got my computer. It is of course
    possible that the problem does not come from the Qt library alone because the last apt-get upgrade this morning (Monday, Aug. 16th) caused several packages to be upgraded (e.g. a lot of stuff from KDE 3.3.0)

    WR

    On Monday 16 August 2004 12:07, Ben Burton wrote:
    reassign 266007 libqt3c102-mt
    thanks mate

    Hi. This appears to be the same issue as #264928.

    The fix is to upgrade your libqt3c102-mt to version 3:3.3.3-1, where
    this was fixed by the Qt maintainer. If you can't upgrade just yet, installing xlibmesa-dev is a workaround solution.

    Ben.


    --
    To UNSUBSCRIBE, email to [email protected]
    with a subject of "unsubscribe". Trouble? Contact [email protected]

    --- SoupGate-Win32 v1.05
    * Origin: you cannot sedate... all the things you hate (1:229/2)
  • From Ben Burton@1:229/2 to All on Tue Aug 17 10:00:16 2004
    From: [email protected]

    Hi,

    I had a look at the "solution" that was proposed for Qt in the bug you mentioned (#26492 ): The so-called solution makes everything worse: Instead of search for a libGL, Qt will now search explicitly for a library called libGL.so.1 which would be /usr/X11R6/lib/libGL.so.1.2 of the xlibmesa-gl package. So if that package is installed Qt will find a mesa lib explicitly searching for the DRI extension resulting in a "extension XFree86-DRI missing on display ..." message if a NVIDIA proprietary driver is installed.

    I don't know enough about GL internals or how it works with proprietary
    drivers to have any further (useful) comments to make. So I'm afraid I
    must leave this to the Qt and/or GL people.

    Ben.



    --
    To UNSUBSCRIBE, email to [email protected]
    with a subject of "unsubscribe". Trouble? Contact [email protected]

    --- SoupGate-Win32 v1.05
    * Origin: you cannot sedate... all the things you hate (1:229/2)