The issue also happens outside of libavg, as this discussion shows:
http://ubuntuforums.org/showthread.php?t=762228
--
SETRANS + libavg = SIGSEGV on Hardy
https://bugs.launchpad.net/bugs/237156
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubu
It's definitely that bug. The coresponding ubuntu bug is
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/259219.
--
Please update libavg to 1.0.1
https://bugs.launchpad.net/bugs/474004
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Sigh. That's a bug in boost.python:
https://www.libavg.de/wiki/index.php/Libavg_on_Ubuntu#9.10_boost.python_Bug.
Also known as Ubuntu bug #457688.
--
Please update libavg to 1.0.1
https://bugs.launchpad.net/bugs/474004
You received this bug notification because you are a member of Ubuntu
Bugs, w
Re: the segfault - can you post a stack trace?
Re: #include in FBO.cpp - I've added it to the file upstream so it'll be
in the next release. Probably a gcc version issue.
Re: testplayer - there's an environment variable, AVG_CONSOLE_TEST,
which, if set, _should_ prevent tests that open a window f
Ok, the libColorNode stuff looks like a libavg bug. Sorry for that, I'll
fix it before the next release. Since this library is only used to test
the plugin mechanism, I think we can just disable the libColorNode build
and the corresponding test for now.
--
Please update libavg to 0.9.0
https://bu
Hi,
I've fought with the libColorNode.so stuff for a while now, and I can
get it to install to the place everything else is installed by applying
the following patch:
Index: src/test/plugin/Makefile.am
===
--- src/test/plugin/Makefil
Send any patches that should be applied upstream to me. I'm the
maintainer :-).
--
Please update libavg to 0.9.0
https://bugs.launchpad.net/bugs/474004
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-b
There are at least two bugs being discussed here in parallel.
The segfault in comment #4 is fixed upstream (svn rev. 2384, 2007-10-31
probably fixes it. I additionally committed a change today (libavg rev. 4549)
that makes these lines of code conform to the C++ standard.)
The segfault in comment
** Changed in: mesa (Ubuntu)
Status: Incomplete => Confirmed
--
Broken TLS support in libGL.so
https://bugs.launchpad.net/bugs/259219
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.u
Changing the status to confirmed. This is not a bug that appears on some
machines. It's easily reproducable on all machines with intel graphics
and Jonathan's original description sums up what's happening quite
nicely.
--
Broken TLS support in libGL.so
https://bugs.launchpad.net/bugs/259219
You r
I've commited a fix upstream (libavg svn rev. 4550).
--
libavg FTBFS: python LOCALMODLIBS causes -lssl link failure
https://bugs.launchpad.net/bugs/512861
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubunt
Some context for Alex' comment:
- http://mail.datenhain.de/pipermail/libavg-users/2010-February/000402.html
- Possibly relevant:
https://bugs.launchpad.net/ubuntu/+source/ia32-libs/+bug/211698
--
Please update libavg to 0.9.0
https://bugs.launchpad.net/bugs/474004
You received this bug notificat
I see two issues with the current situation:
1. The fact that all Ubuntu packages using the ffmpeg libraries are
under the GPL is not stated explicitly anywhere. That can cause
inadvertent license breaches.
2. There is no way to use the gstreamer (or libavg etc.) package under
the LGPL using the
I can confirm that the ppa fixes the bug for libavg.
--
libboost-python1.38 issues with __doc__ property in Python >= 2.6.3
https://bugs.launchpad.net/bugs/457688
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing li
The segfault doesn't appear under 9.10, so - Fabrice, it would be great
if you could try renaming the NONE property.
--
Please update libavg to 0.9.0
https://bugs.launchpad.net/bugs/474004
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
That's a possibility. I'm testing on i386, and I don't know anyone
that's running libavg on an amd64.
--
Please update libavg to 0.9.0
https://bugs.launchpad.net/bugs/474004
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
This bug should be reopened.
See
https://www.libavg.de/wiki/index.php/Known_Linux_Installation_Issues#glibc_invalid_pointer
for a description of the bug as it appears in libavg.
Here's an lspci of a user's machine (Ubuntu 9.10). I'll see if I can get
the user to submit the rest of the info you re
Note that there's a new libavg version available upstream (1.8.0) that
is compatible with current libav.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1253071
Title:
block migration & demote to prop
As per my last comment, the various bugs here have been fixed and the
fixes are in the current Ubuntu libavg package.
** Changed in: libavg (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubun
I've reproduced this and checked a fix in upstream (svn rev. 6715). A
patch is attached.
** Patch added: "ati-segfault-on-startup-fix.diff"
https://bugs.launchpad.net/ubuntu/+source/libavg/+bug/815922/+attachment/2512133/+files/ati-segfault-on-startup-fix.diff
--
You received this bug notifi
*** This bug is a duplicate of bug 587430 ***
https://bugs.launchpad.net/bugs/587430
** This bug has been marked a duplicate of bug 587430
package python-libavg 0.8.0-5ubuntu4 failed to install/upgrade: el
subproceso script post-installation instalado devolvió el código de salida de
error
Note that while the Debian libavg package is outdated, buggy and a leaf
package, the Ubuntu package is up-to-date, maintained and not a leaf
package. In short: A completely different thing. There is no reason to
remove it.
--
You received this bug notification because you are a member of Ubuntu
B
I'm attaching a minimal piece of code that reproduces the error.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/259219
Title:
Broken TLS support in libGL.so
--
ubuntu-bugs mailing list
ubuntu-bugs@
** Attachment added: "ldpreload_crash.zip"
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/259219/+attachment/1879449/+files/ldpreload_crash.zip
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/25
Removed unneeded files from reproducer
** Attachment added: "ldpreload_crash.zip"
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/259219/+attachment/1879456/+files/ldpreload_crash.zip
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ub
Ok, so your graphics setup looks absolutely sane - sorry for asking :-).
Since I have no way of reproducing this bug (No one here has the
hardware), I'm going to need your help to isolate the cause.
Unfortunately, the backtrace is broken as well. When you're in gdb, can
you do
(gdb) info threads
Can you do two things:
- Attach the output of glxinfo to the bug.
- See if the error still happens if you use the classic desktop without effects.
Thanks,
Uli
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.
27 matches
Mail list logo
