On Sun, 11 Nov 2012 21:46:58 +0100, Julien Cristau wrote:
> > Why would it work with the 32bit "foreign" libraries but not with the
> > "native" 64bit ones?
> Because this is not a '32bit' vs '64bit' test, it's a 'direct' vs
> 'indirect' test. No surprise that they're different. (Your 64bit libG
On Sun, Nov 11, 2012 at 17:39:31 +0100, gregor herrmann wrote:
> Now that is funny:
>
> % LIBGL_DRIVERS_PATH=/usr/lib/x86_64-linux-gnu/dri MUMBLE_OVERLAY_DEBUG=1
> mumble-overlay glxgears
>
> set
> MumbleOverlay: Mumble overlay library
On Sun, 11 Nov 2012 12:37:42 -0500, Chris Knadle wrote:
> > Why would it work with the 32bit "foreign" libraries but not with the
> > "native" 64bit ones?
> >
> > (Same with Chris' example (armagetronad): works with the 32bit libs
> > and fails the same way with 64bit.)
>
> This sort of reminds
On Sun, Nov 11, 2012 at 05:39:31PM +0100, gregor herrmann wrote:
> On Mon, 12 Nov 2012 01:08:19 +1030, Ron wrote:
>
> > > > Does glxgears actually run for you without the mumble preload?
> > > Yup, sorry for not mentioning this yesterday.
> > Ok, so it's reasonably certain to be something mumble i
On Sunday, November 11, 2012 11:39:31, gregor herrmann wrote:
> On Mon, 12 Nov 2012 01:08:19 +1030, Ron wrote:
...
> And yes, a bit searching leads to all kind of GL problems that sound
> similar.
>
>
> Now that is funny:
>
> % LIBGL_DRIVERS_PATH=/usr/lib/x86_64-linux-gnu/dri MUMBLE_OVERLAY_DEBU
On Mon, 12 Nov 2012 01:08:19 +1030, Ron wrote:
> > > Does glxgears actually run for you without the mumble preload?
> > Yup, sorry for not mentioning this yesterday.
> Ok, so it's reasonably certain to be something mumble is trying to do
> that for whatever reason your system doesn't support.
>
>
On Sun, Nov 11, 2012 at 02:42:45PM +0100, gregor herrmann wrote:
> On Sun, 11 Nov 2012 15:31:53 +1030, Ron wrote:
>
> > Does glxgears actually run for you without the mumble preload?
>
> Yup, sorry for not mentioning this yesterday.
Ok, so it's reasonably certain to be something mumble is tryin
On Sun, 11 Nov 2012 15:31:53 +1030, Ron wrote:
> > What I get is a short flicker, and the following output:
> >
> > MumbleOverlay: Mumble overlay library loaded
> > MumbleOverlay: Iterating dlsym table 0x7fdebbb70348 0x7fdebbb706f0 39
> > MumbleOverlay: Original dlsym at 0x7fdebbb71030
> > Mumble
On Sat, 10 Nov 2012 19:08:13 -0500, Chris Knadle wrote:
> > So I guess the two interesting questions remaining now are:
> >
> > - Does it actually work!
>
> It does. First time I've ever seen it work.
Cool!
> I'm attaching the quilt patch I
> used to add the -lGL dependency in overlay_gl.
On Sat, Nov 10, 2012 at 09:40:39PM +0100, gregor herrmann wrote:
> I've tried this now, both with
> MUMBLE_OVERLAY_DEBUG=1 LD_PRELOAD=/usr/lib/mumble/libmumble.so.1.2.4 glxgears
> and
> MUMBLE_OVERLAY_DEBUG=1 mumble-overlay glxgears
>
> What I get is a short flicker, and the following output:
>
On Friday, November 09, 2012 11:18:06, Ron wrote:
> On Thu, Nov 08, 2012 at 11:33:09PM -0500, Chris Knadle wrote:
...
> > The fact that the /documentation/ is wrong or that the program doesn't
> > follow what the documentation says -- yes I agree that needs fixing.
>
> That's not a fact, it's a fa
On Sat, 10 Nov 2012 13:28:28 +1030, Ron wrote:
> > On Fri, 09 Nov 2012 09:51:05 +1030, Ron wrote:
> > The term "trivial" triggered me into trying it myself.
> I'd hoped so :) I've got a small mountain of backlog still to dig through
> right now, and this still isn't anywhere near the top of it ju
severity 691535 serious
thanks
On Sat, Nov 10, 2012 at 01:28:28PM +1030, Ron wrote:
> So I guess the two interesting questions remaining now are:
>
> - Does it actually work!
> - and when do we want to upload it if it does ...
And as for the second, the best plan for -release at present would
On Sat, Nov 10, 2012 at 01:28:28PM +1030, Ron wrote:
> So I guess the two interesting questions remaining now are:
>
> - Does it actually work!
> - and when do we want to upload it if it does ...
Ok, so I just knocked up a quick and dirty test jig here for what
libmumble is doing, and it looks
On Sat, Nov 10, 2012 at 02:30:03AM +0100, gregor herrmann wrote:
> On Fri, 09 Nov 2012 09:51:05 +1030, Ron wrote:
>
> > > My impression at the moment is:
> > > - There's a bug but mumble still works, as confirmed by the submitter
> > And the fix should be trivial. libmumble uses symbols from libG
On Fri, 09 Nov 2012 09:51:05 +1030, Ron wrote:
> > My impression at the moment is:
> > - There's a bug but mumble still works, as confirmed by the submitter
> And the fix should be trivial. libmumble uses symbols from libGL but
> doesn't link to it, and so will fail unless that's fixed and it doe
On Thu, Nov 08, 2012 at 11:33:09PM -0500, Chris Knadle wrote:
> it's hard to say that the lack of 3D overlay functionality is RC.
This bug isn't reporting the lack of that functionality, it's reporting
clear evidence of a fundamentally broken build in a library we are shipping.
That library build
Ron, please keep me in the CC list.
On Thu, Nov 08, 2012 at 10:38:04PM +0100, gregor herrmann wrote:
> > My impression at the moment is:
> > - There's a bug but mumble still works, as confirmed by the submitter
>
> And the fix should be trivial. libmumble uses symbols from libGL but
> doesn't lin
On Thu, Nov 08, 2012 at 10:38:04PM +0100, gregor herrmann wrote:
> My impression at the moment is:
> - There's a bug but mumble still works, as confirmed by the submitter
And the fix should be trivial. libmumble uses symbols from libGL but
doesn't link to it, and so will fail unless that's fixed
On Thursday, November 08, 2012 10:38:04 PM gregor herrmann wrote:
> Control: found -1 1.2.3-348-g317f5a0-1
> Control: found -1 1.2.3-349-g315b5f5-2
>
> On Thu, 08 Nov 2012 13:15:33 -0500, Chris Knadle wrote:
> > On Thursday, November 08, 2012 01:57:23, Ron wrote:
> > > But this seems to be new(ly
Control: found -1 1.2.3-348-g317f5a0-1
Control: found -1 1.2.3-349-g315b5f5-2
On Thu, 08 Nov 2012 13:15:33 -0500, Chris Knadle wrote:
> On Thursday, November 08, 2012 01:57:23, Ron wrote:
> > But this seems to be new(ly reported) for the upload you prepared, and
> > it's still not clear yet why
On Thursday, November 08, 2012 13:28:07, Chris Knadle wrote:
> On Thursday, November 08, 2012 04:11:58, Daniel Kahn Gillmor wrote:
> > On 11/07/2012 07:59 PM, Chris Knadle wrote:
> > > You're correct about the error being thrown -- until now I've never
> > > noticed it because I generally start Mum
On Thursday, November 08, 2012 04:11:58, Daniel Kahn Gillmor wrote:
> On 11/07/2012 07:59 PM, Chris Knadle wrote:
> > You're correct about the error being thrown -- until now I've never
> > noticed it because I generally start Mumble graphically. Mumble seems
> > to work fine (communication-wise)
On Thursday, November 08, 2012 01:57:23, Ron wrote:
> On Wed, Nov 07, 2012 at 12:11:12PM -0500, Chris Knadle wrote:
> > Hello again, Daniel. :-)
> >
> > You're correct about the error being thrown -- until now I've never
> > noticed it because I generally start Mumble graphically. Mumble seems
>
On 11/07/2012 07:59 PM, Chris Knadle wrote:
> You're correct about the error being thrown -- until now I've never noticed
> it
> because I generally start Mumble graphically. Mumble seems to work fine
> (communication-wise) even though the error gets thrown.
>
> From what I can see, this might
On Wed, Nov 07, 2012 at 12:11:12PM -0500, Chris Knadle wrote:
> Hello again, Daniel. :-)
>
> You're correct about the error being thrown -- until now I've never noticed
> it
> because I generally start Mumble graphically. Mumble seems to work fine
> (communication-wise) even though the error
Hello again, Daniel. :-)
You're correct about the error being thrown -- until now I've never noticed it
because I generally start Mumble graphically. Mumble seems to work fine
(communication-wise) even though the error gets thrown.
From what I can see, this might be expected behavior of the p
27 matches
Mail list logo