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 > > to work fine (communication-wise) even though the error gets thrown. > > > > From what I can see, this might be expected behavior of the program > > because /usr/share/doc/mumble/Readme.Linux discusses using LD_PRELOAD or > > the 'mumble- overlay' program (which is shipped with the 'mumble' > > package) in the case where the OpenGL overlay is desired -- but it's > > /not/ required. > > erm ... that talks about preloading *libmumble* to run a *3rd party game* > not about needing to preload the *system libGL* just to be able to run > *mumble itself* ... > > Notice the difference?
No, that's /not/ what the bug stated. Regardless of the error to the console, Mumble /is/ starting. Mumble does not /require/ libGL to run (and I would very much like to keep it that way), even though it perhaps /can/ use it in /some/ circumstances -- however the Mumble 3D overlay doesn't seem to come up in any of the 3D games for Linux that I've tried so far, so I'm not sure how useful that particular feature is for Debian. > <hint> One and only one of those things is not clearly insane </> > > > What's going > > > > on is that Mumble is designed with 3D gaming in mind, and the overlay is > > for showing a list of people in the channel and who is actively speaking > > while you're playing a game; but this overlay and the plugins for the > > overlay (for particular games) are only needed in a 3D game, and not > > otherwise. > > No, what's going on is that it's apparently failed to link to a library > that it requires. Not /required/ -- no. > > So I thank you for pointing this out because it's interesting, but I'm > > not sure if it's actually a bug. ;-) Let me know what you think. > > I'm pretty sure that everybody else is 100% certain that this is a bug. > > If there is any open question there at all it is whether the bug is RC, > which for "application fails to start at all due to missing library dep" > I wouldn't have thought would be very controversial either ... > > But this seems to be new(ly reported) for the upload you prepared, and > it's still not clear yet why it is new and who it effects. So yes, > you will need to investigate that further. It's most certainly not > "expected behaviour" for a Debian package. This issue is /not/ related to my "349"-2.1 NMU upload. The "348"-1 package that's in Wheezy right now and the "349"-2 package both exhibit exactly this same behavior. If bugs are reported that you think are related to the "349"-2.1 NMU then I'd appreciate it if you'd forward them to me so I can look at them. And when you do, I'd really appreciate it if you'd use some common curteousy. -- Chris -- Chris Knadle chris.kna...@coredump.us -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
