calling GLX 1.3 function "glXCreatePixmap" when GLX 1.3 is not supported

This warning is new in mesa http://cgit.freedesktop.org/mesa/mesa/commit/?h=mesa_7_6_branch&id=1f309c40b8065b8729fce631540c66e4b50b84df but has been applied both to the 7.5 and 7.6 branches.

I think compiz does not check for GLX version, it just probes for the functions it wants to use.

I have sent a patch upstream to make mesa more forgiving.

Patch went upstream http://cgit.freedesktop.org/mesa/mesa/commit/?h=mesa_7_5_branch&id=e8573033058a13bd39a0b85f48b6db64b04c65e0 so it should trickle in with the next mesa snapshot/release.

But compiz _is_ broken in this regard.

I fail to see how compiz is doing anything wrong here. We don't check for the GLX version but we do check to see if that function exists before trying to use it.

From #dri-devel last night:
<tormod> idr, did you see the patch I posted for your GLX 1.3 warnings?
<idr> tormod: I did.
 tormod: Thank you for reminding me. I was going to commit that today.
<tormod> great. what should the "buggy" applications do btw? for instance compiz does not care about glx version and justs probes for the functions that it needs
<idr> If the GLX version is not 1.3 or greater, it should not call those functions.
<idr> tormod: I don't know what you mean by "probes for the functions that it needs".
 tormod: The only probe is to call glXQueryVersion.
 tormod: Or glXQueryExtensionsString.
<tormod> sorry I don't know how this works, but I had a glance at the compiz code and it checks for these functions
 and since the messages appear, it is obviously using them :) and it works
<tormod> compiz uses glXQueryExtensionsString, but also some getProcAddress ("glXCreatePixmap") magic (http://cgit.compiz.org/compiz/core/tree/plugins/opengl/src/screen.cpp)
<idr> tormod: That magic is 100% wrong.
 tormod: On the standard libGL, glXGetProcAddress *ALWAYS* returns a pointer to something.
 tormod: Even if you call 'glXGetProcAddress("baconisyummytoeat");'.
<MostAwesomeDude> Well, bacon *is* delicious.
<idr> true dat!
<tormod> :) but if compiz was doing things correct (TM) it would just not run on r300 then?
<idr> tormod: It was doing things correct, it would continue to run when non-essential functionality was not available.
 tormod: Can it just not possibly run without some GLX 1.3 exclusive functionality? I doubt it.
<tormod> yes I guess it would
<idr> It obviously does since we don't support GLX 1.3! :)
<tormod> but it uses those GLX 1.3 functions with success?
<idr> Given all the bug reports that we've had from compiz and Wine calling GLX 1.3 functions that eventually result in either crashes or incorrect results, no.
 Which is why I added the warning.
<tormod> so compiz _is_ buggy? news at 11
<idr> Many of the GLX 1.3 functions are identical to functions added by extensions (e.g., GLX_SGIX_fbconfig) that we do support.
 Calling the GLX 1.3 versions just dumps into the extension functions.
 Those cases happen to work by dumb luck.
<tormod> thanks for the explanations!

GLX_EXT_texture_from_pixmap requires GLX 1.3 and only works with glXCreatePixmap. GLX_EXT_texture_from_pixmap existing should be all the test we need to know glXCreatePixmap is safe to use. If we did what you suggest compiz would not work at all on r300 and older ati cards.

I am not sure what you mean "I suggest" but I guess, yes, it is not supposed to work since the r300 driver does not support GLX 1.3. However, it works "by dumb luck".

Upstream (mesa) seems pretty clear about the glXGetProcAddress probing being wrong. Anyway, this is an upstream (compiz) issue so I don't think any Ubuntu action is needed.

Further upstream discussion:

<Amaranth> So, for now I think compiz should just ignore this warning :)
<Amaranth> and WINE will ignore it even if you don't want them to :/
<idr> Amaranth: The bad part is that systems where this really doesn't work won't give you a warning. You'll just get a protocol error.
<Amaranth> idr: But surely tfp won't exist there?
<idr> Amaranth: Ah, that is almost certainly true.
<Amaranth> So unless we get GLX_mesa_i_cant_believe_its_not_glx13 compiz is doing all it can to make sure it doesn't use something that doesn't exist while still working on systems where it can work

r300 does support glXCreatePixmap (otherwise they couldn't support GLX_EXT_texture_from_pixmap) so any system that has GLX_EXT_texture_from_pixmap has glXCreatePixmap so we are covered.

This bug was fixed in the package mesa - 7.6.0-1ubuntu1

---------------
mesa (7.6.0-1ubuntu1) karmic; urgency=low

  * Merge from Debian. (LP: #420803)
    Remaining Ubuntu changes:
    - debian/control
      + Change maintainer address to Ubuntu.
      + Drop lesstif-dev from Build-Depends.
      + Comment out GLw libs since it depends on lesstif-dev.
      + Require at least libdrm_2.4.12+git20090801.45078630
    - debian/rules
      + Unexport LDFLAGS (amd64 FTBFS).
      + Use --disable-glw for swx11 targets too.
      + Don't enable motif for swx11 targets.
      + Build .debs with lzma compression.
      + Serialize install phase as suggested by Julien Cristau,
        fixes amd64 FTBFS.
    - debian/patches
      + 101_ubuntu_hidden_glname.patch
      + 102_dont_vblank.patch
      + 107_glxgears_is_not_a_benchmark.patch
  * Drop patches now included upstream:
    + 108_big_endian.patch
    + 109_fix_relocation_delta_for_wm_surfaces.patch
    + 110_deassociate_drawables.patch
    + 111_dridrawable_nullptr.patch
    + 112_dont_corrupt_random_number_state.patch
  * Mesa 7.6 fixes the following Ubuntu bugs:
    + Suppress excessive warnings on unsupported GLX 1.3 calls.
      (LP: #433488)
  * See http://www.mesa3d.org/relnotes-7.6.html for more details.

 -- Bryce Harrington <email address hidden> Wed, 07 Oct 2009 14:51:41 -0700

Still no compiz in GMA 950. System got kernel panic when try to active it.

Maik, that has nothing to do with this bug report. You have to file your own bug report.

Still seeing this error on an up-to-date clean lucid install.

This is with mesa 7.7.1-1ubuntu2

You're expected to see the message once for each of the functions when running compiz but it is not an error.

I see this too:
andy@D420:~$ Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x4200027 (Bug #43348)
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
Window manager warning: Receiving a NET_CLOSE_WINDOW message for 0x4a00003 (CompizConf) without a timestamp! This means some buggy (outdated) application is on the loose!

Lucid UNR

Those messages are from metacity. You must have some other problem that compiz is detecting and so launching metacity for you instead. In any case, it isn't related to this bug.

This issue surfaced on my machine right after upgrading to Lucid. Compiz has been working perfectly on this box for years.

The following results in loss of window decorations and extreme unresponsiveness. Metacity works fine.

aaditya@u01:~$ lspci | grep VGA
00:02.0 VGA compatible controller: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (rev 03)

aaditya@u01:~$ compiz --replace
Couldn't find a perfect decorator match; trying all decorators
Starting kde4-window-decorator
WARNING: Application calling GLX 1.3 function "glXCreatePixmap" when GLX 1.3 is not supported! This is an application bug!
kde-window-decorator(9545) KWD::KDecorationPlugins::loadPlugin: kwin : path "" for "kwin3_oxygen"
/usr/bin/kde4-window-decorator: Could not enable decorations on display ":0.0"
WARNING: Application calling GLX 1.3 function "glXDestroyPixmap" when GLX 1.3 is not supported! This is an application bug!

Hello,
Here too, This issue came up on my computer just after upgrading to Lucid. Compiz has been working perfectly on this box for years.
FI: I use the free Lucid GPU driver and my graphic card is:
lspci | grep VGA
01:00.0 VGA compatible controller: ATI Technologies Inc RV730XT [Radeon HD 4670]
WARNING: Application calling GLX 1.3 function "glXCreatePixmap" when GLX 1.3 is not supported! This is an application bug!

Please file new bugs. The warning mentioned in this bug report is not a problem.

Hello, ok, it's done here:
https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/560082

I can confirm this. Same scenario. Clean install of Lucid on separate partition from HOME. Had no problem in Karmic AND if I re-install Karmic this problem goes away.

To be honest all of these different bug references have me confused so I ma not sure which one addresses my problem specifically but...
:~/Downloads$ lspci | grep VGA
00:02.0 VGA compatible controller: Intel Corporation Mobile 915GM/GMS/910GML Express Graphics Controller (rev 03)
:~/Downloads$ compiz --replace
WARNING: Application calling GLX 1.3 function "glXCreatePixmap" when GLX 1.3 is not supported! This is an application bug!
WARNING: Application calling GLX 1.3 function "glXDestroyPixmap" when GLX 1.3 is not supported! This is an application bug!

hope this frikkin works!!!