Teemu Ikonen writes ("Re: Bug#426581: meshlab - anyone still working on this"): > Thanks for the review. I fixed the problems you found except these: > > After I built it (on lenny), I ran meshlab from an xterm. It opened > > an entirely blank override-redirect pale grey window covering the top > > left area of my display, as well as the main window. What is that > > blank window for ? Can it be got rid of ? > > I cannot repeat this.
What is your window manager ? See my mail just sent for more information about this. > Edit / Vertex painting works here. The shaders crash here as well, but > AFAIK they need hardware support to work, which I do not have here. > Meshlab should check if GL_ARB_vertex_shader and > GL_ARB_fragment_shader extensions are available, before trying to use > them. I don't have time to start fixing this, or other upstream bugs. > Paolo, can you help here? Well, I don't think these are release-critical bugs. However I have discovered one thing that we in Debian ought to consider release-critical: I have discovered that the program prompted me that a new version had been released. This is presumably achieved by contacting some upstream server to check. Paulo, is that correct ? I'm afraid that it is not acceptable for a program packaged for Debian to phone home like this and that feature must be disabled before we upload it even to unstable. > > If I run the program with --help or -h, it tries to open them as > > files. It ought at least to bomb out with a message saying please > > refer to the meshlab wiki (with a URL). > > Upstream. If I provide a patch will you incorporate it in your package ? I can do it as a bzr branch or an emailed diff, whichever you prefer. I think this is quite important. The behaviour atm is rather poor if you're trying just to figure out how to run the program. > I updated the package and put it to again to > http://esko.osmas.info/~tmx/meshlab/ > but as there are still problems (mainly with the shaders), maybe the > package is not quite ready yet. I haven't looked at this yet but I think we're definitely getting there. If you can fix it so it doesn't phone home I'll upload it. (The lib3ds package whose new upstream version I NMU'd has just migrated to testing and I haven't yet heard an objection from its maintainer.) Thanks, Ian. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]