Bug#345753: xlibosmesa4: undefined symbol: driDispatchRemapTable

2006-01-31 Thread Joerg Hessdoerfer
Hi again,

On Tuesday 31 January 2006 13:22, Michel Dänzer wrote:
> So, does running the application with
> LD_PRELOAD=/usr/lib/dri/r300_dri.so make a difference?
>

Yes, preloading r300_dri.so works. Thanks for this workaround! 

> > Also, this symbol is undefined when dri is turned off. This shouldn't be
> > the case anyway, no? IMHO, when dri is off, xlibosmesa should work just
> > fine, since it's 'off screen'.
>
> I agree. You may want to also report this upstream at
> http://bugs.freedesktop.org .
>
>

Will do.

> --
> Earthling Michel Dänzer      |     Debian (powerpc), X and DRI developer
> Libre software enthusiast    |   http://svcs.affero.net/rm.php?r=daenzer

Greetings,
Jörg
-- 
Leading SW developer  - S.E.A GmbH
Mail: [EMAIL PROTECTED]
WWW:  http://www.sea-gmbh.com



Bug#345753: xlibosmesa4: undefined symbol: driDispatchRemapTable

2006-01-31 Thread Michel Dänzer
On Mon, 2006-01-30 at 18:20 +0100, Joerg Hessdoerfer wrote:
> On Monday 30 January 2006 18:07, Michel Dänzer wrote:
> > On Tue, 2006-01-03 at 11:31 +0100, Joerg Hessdoerfer wrote:
> > > I'm running a closed-source proprietary application, which ran fine
> > > under 6.8.2. Since the update to 6.9.0, I get the following error:
> > >
> > > symbol lookup error: /usr/X11R6/lib/libOSMesa.so.4: undefined symbol:
> > > driDispatchRemapTable
> > >
> > > I'm using an ATI Mobility 9600, with the radeon driver and DRI enabled.
> >
> > Do you have the r300 DRI driver (only available in the libgl1-mesa-dri
> > package in Debian) working though, i.e. does glxinfo report direct
> > rendering as enabled?
> >
> > I'm asking because this symbol seems to be defined in the DRI drivers
> > (r300_dri.so in your case), but this may still be a bug in xlibosmesa4
> > or xlibmesa-gl.
> 
> Yes, I have. (I have to admit I used the one from libgl1-mesa-dri, as I could 
> not install the package without conflicts). But it works, as proven by 
> glxgears for example. (glxinfo also reports 'direct rendering: Yes').

So, does running the application with
LD_PRELOAD=/usr/lib/dri/r300_dri.so make a difference?


> Also, this symbol is undefined when dri is turned off. This shouldn't be the 
> case anyway, no? IMHO, when dri is off, xlibosmesa should work just fine, 
> since it's 'off screen'.

I agree. You may want to also report this upstream at
http://bugs.freedesktop.org .


-- 
Earthling Michel Dänzer  | Debian (powerpc), X and DRI developer
Libre software enthusiast|   http://svcs.affero.net/rm.php?r=daenzer



Bug#345753: xlibosmesa4: undefined symbol: driDispatchRemapTable

2006-01-30 Thread Joerg Hessdoerfer
On Monday 30 January 2006 18:07, Michel Dänzer wrote:
> On Tue, 2006-01-03 at 11:31 +0100, Joerg Hessdoerfer wrote:
> > I'm running a closed-source proprietary application, which ran fine
> > under 6.8.2. Since the update to 6.9.0, I get the following error:
> >
> > symbol lookup error: /usr/X11R6/lib/libOSMesa.so.4: undefined symbol:
> > driDispatchRemapTable
> >
> > I'm using an ATI Mobility 9600, with the radeon driver and DRI enabled.
>
> Do you have the r300 DRI driver (only available in the libgl1-mesa-dri
> package in Debian) working though, i.e. does glxinfo report direct
> rendering as enabled?
>
> I'm asking because this symbol seems to be defined in the DRI drivers
> (r300_dri.so in your case), but this may still be a bug in xlibosmesa4
> or xlibmesa-gl.

Yes, I have. (I have to admit I used the one from libgl1-mesa-dri, as I could 
not install the package without conflicts). But it works, as proven by 
glxgears for example. (glxinfo also reports 'direct rendering: Yes').

Also, this symbol is undefined when dri is turned off. This shouldn't be the 
case anyway, no? IMHO, when dri is off, xlibosmesa should work just fine, 
since it's 'off screen'.

Side note: I've seen a similar bugreport for freeBSD:
http://lists.freebsd.org/pipermail/freebsd-x11/2006-January/002541.html

This seems to indicate a more general issue with xlibosmesa.

Greetings,
Jörg
-- 
Leading SW developer  - S.E.A GmbH
Mail: [EMAIL PROTECTED]
WWW:  http://www.sea-gmbh.com



Bug#345753: xlibosmesa4: undefined symbol: driDispatchRemapTable

2006-01-30 Thread Michel Dänzer
On Tue, 2006-01-03 at 11:31 +0100, Joerg Hessdoerfer wrote: 
> 
> I'm running a closed-source proprietary application, which ran fine
> under 6.8.2. Since the update to 6.9.0, I get the following error:
> 
> symbol lookup error: /usr/X11R6/lib/libOSMesa.so.4: undefined symbol:
> driDispatchRemapTable
> 
> I'm using an ATI Mobility 9600, with the radeon driver and DRI enabled.

Do you have the r300 DRI driver (only available in the libgl1-mesa-dri
package in Debian) working though, i.e. does glxinfo report direct
rendering as enabled?

I'm asking because this symbol seems to be defined in the DRI drivers
(r300_dri.so in your case), but this may still be a bug in xlibosmesa4
or xlibmesa-gl.


-- 
Earthling Michel Dänzer  | Debian (powerpc), X and DRI developer
Libre software enthusiast|   http://svcs.affero.net/rm.php?r=daenzer



Bug#345753: xlibosmesa4: undefined symbol: driDispatchRemapTable

2006-01-03 Thread Joerg Hessdoerfer
Package: xlibosmesa4
Version: 6.9.0.dfsg.1-1
Severity: important


I'm running a closed-source proprietary application, which ran fine
under 6.8.2. Since the update to 6.9.0, I get the following error:

symbol lookup error: /usr/X11R6/lib/libOSMesa.so.4: undefined symbol:
driDispatchRemapTable

I'm using an ATI Mobility 9600, with the radeon driver and DRI enabled.

-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (990, 'unstable'), (500, 'testing')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.14-2-686
Locale: LANG=de_DE, LC_CTYPE=de_DE (charmap=ISO-8859-1)

Versions of packages xlibosmesa4 depends on:
ii  libc6 2.3.5-9GNU C Library: Shared libraries an
ii  libxext6  6.9.0.dfsg.1-1 X Window System miscellaneous exte
ii  xlibmesa-gl [libgl1]  6.9.0.dfsg.1-1 Mesa 3D graphics library [X.Org]

xlibosmesa4 recommends no packages.

-- debconf-show failed


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