Just stumbled upon the same issue in raring as well.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/453267
Title:
vlc assert failure: vlc:
/build/buildd/libdvdnav-4.1.3/src/vm/vm.c:1074: play_Cell:
An easier option than rebuilding a system package with all kinds of
dependencies might be to tell PyCURL what version of SSL to use, like
described here:
https://bugs.launchpad.net/ubuntu/+source/pycurl/+bug/926548/comments/24
Hope that helps,
Guy
--
You received this bug notification because
I've just stumbled upon this bug report searching for the evil
pycurl.error: (35, 'gnutls_handshake() failed: GnuTLS internal error.')
I found a solution by telling cURL what version of SSL to use:
connection.setopt(pycurl.SSLVERSION, pycurl.SSLVERSION_SSLv3)
This is where I found this gem:
http
This problem apparently affects people on (newer) Ubuntu versions,
particularly when running proprietary graphics drivers. I can confirm it
to affect Ubuntu Precise on 32 and 64 bit with NVIDIA drivers.
There has recently been some bug hunting on the Visual Python mailing
list and John Zelle has f
Just retested on another box. Result is positive.
Also I've now gone and also reinstalled python-visual, and guess what,
it works as well. There must've been some things "wrong" after all the
tinkering to get python-visual working under karmic last year.
So: Thumbs up for the fix!
--
[SRU, 9.10
Václav, of course, I might have gotten something wrong, but I've just
tried it again. I've used the nz.archive.ubuntu.com mirror, and this
time I have downloaded the package manually:
gkl...@it041227:~$ wget
http://nz.archive.ubuntu.com/ubuntu/pool/main/b/boost1.38/libboost-python1.38.0_1.38.0-6u
I have just tested the libboost-python1.38.0 in version 1.38.0-6ubuntu6.1 from
karmic-proposed.
(Beware, some mirrors don't have this package, yet. It took some checking first
...)
Unfortunately, it seems like the error is still there:
$ ipython
Python 2.6.4 (r264:75706, Dec 7 2009, 18:45:15)
It would be interesting to see whether anybody has tested this bug on
libboost1.40.0 from lucid, yet.
Is it still (going to be) an issue, or is it resolved on 1.40.0?
If so, then this bug would just "grow out". If not, then severe action
is required in order to prevent another "broken" release on
@teonghan: Two things on that:
* This should be a problem of the python-visual package, rather than the boost
packages.
* python-visual should then probably also depend on libgtkglextmm-x11-1.2-0,
it should (AFAIK)
*never* depend on a "*-dev" package, which should just contain headers for
I have just given the proposed bug fix a spin by using the packages from
ppa:ajmitch. At least all the samples from python-visual that I've tried
did work properly, now. Well done! I think we've got a go here!
--
libboost-python1.38 issues with __doc__ property in Python >= 2.6.3
https://bugs.lau
** Changed in: python-visual (Ubuntu)
Status: New => Confirmed
--
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.
--
ubunt
New bug opened for this in the more suitable area for boost1.38:
https://bugs.launchpad.net/ubuntu/+source/boost1.38/+bug/457688
--
python2.6 (python-visual) crashed with SIGSEGV in __cxa_allocate_exception()
https://bugs.launchpad.net/bugs/408663
You received this bug notification because you a
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/34119340/Dependencies.txt
--
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 su
Public bug reported:
Python >= 2.6.3 has changed the way the __doc__ property is implemented.
Boost.Python 1.38 does not account for this, yet, leading to many errors
executing Python code using the Boost implemented bindings.
An example trying to use a sample from python-visual:
g...@mountpaku:
Further collaborative investigation has shown that Python >= 2.6.3 has
implemented the __doc__ property differently. Many projects that are
binding native libraries to Python through Boost.Python are suffering
from this. Apparently there is a patch in the SVN version of
Boost.Python that addresses
Further collaborative investigation has shown that Python >= 2.6.3 has
implemented the __doc__ property differently. Many projects that are
binding native libraries to Python through Boost.Python are suffering
from this. Apparently there is a patch in the SVN version of
Boost.Python that addresses
Trying to track down the problem further I've hit some leads that seem to
indicate that there seem to be quite some problems on Ubuntu Karmic with
Boost.Python (version 1.38.0-6ubuntu6). The PySide team has had also some
similar problems, as well as someone else. Here's a thread on the Py++ mail
In an attempt to narrow down the problem with the python-visual 5.11
source package I have taken the python-visual 5.12 source package from
Debian Sid, modified it's build rules (particularly to use libboost 1.38
rather 1.39) and built a package of it.
Unfortunately the effect is the same as descr
I was the one who has backported the 5.11 karmic package to jaunty back
then. Now being with one box on a kubuntu karmic beta gives me quite a
headache as well.
I'm getting the same results, both when I'm installing the distribution
provided binary package as well as when I'm using the dpkg-buildp
An easy fix that would be worth putting into the package distribution:
Just remove the two Python packages, as all that's needed is found in
the module lcms.py anyway. The dualism in the name space (package and
module of same name) overshadow each other and hinder a seamless
working. So, these dir
Public bug reported:
OpenCV 1.0.0-6.1 requires libdc1394-13 (-dev) for the build, however
libdc1394-22 (-dev) is required through a chain of dependencies from
libavcodec (-dev).
Therefore OpenCV's build in Intrepid is configured as following,
disabling IEEE 1394 camera capturing:
Video I/O -
another workaround:
* Install GCC 4.2
* export GCCXML_COMPILER=gcc-4.2
* now GCCXML should use gcc-4.2 instead, and things should work again
--
gccxml regression: fails to parse stdio.h
https://bugs.launchpad.net/bugs/293807
You received this bug notification because you are a member of Ubuntu
Maybe this helps. I have created some instructions on how to patch
GCCXML to handle the stdio.h bug, and recompiled a Debian package. More
information can be found here, although it is only a workaround:
http://www.kloss-familie.de/moin/Root/PatchingGccXml
--
gccxml regression: fails to parse st
I second the motion of getting GCCXML working out of the box with at
least the usual libraries as stdio. Adding a dummy is fine as long as it
is your "own" code, but it can create bigger problems on third party
code. Could a dummy like that one be added to the other macros
mentioned?
Where would t
I think this is a duplicate/still existent issue of #81567
--
[Hardy] skencil.py crashed with SIGSEGV in free()
https://bugs.launchpad.net/bugs/176652
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubu
I think this is a duplicate of #81567
--
skencil aborted
https://bugs.launchpad.net/bugs/175205
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mail
One of the (former) coders of Skencil (Tobias Hilbricht) told me that
Skencil depends on execution with Python 2.4, however Python 2.5 is the
default for quite a few versions of Ubuntu already. But even executing
it with python2.4 does lead to the crash. Apparently Skencil's
development is somewhat
Oleksandr Moskalenko (Debian lcms package maintainer) has just uploaded
a package into Debian/unstable that has the expected "import lcms"
behaviour. This will now have to make it into Ubuntu ...
** Changed in: lcms (Ubuntu)
Status: Invalid => Confirmed
--
python-liblcms: python bindings
The import at least works on self compiled binaries "properly" (as in
the usual way).
And shouldn't imports work homogeneously in the Python language
environment. I believe that's one of the reasons why it is so popular.
--
python-liblcms: python bindings defective
https://bugs.launchpad.net/bug
Public bug reported:
Binary package hint: python-liblcms
* installing liblcms1 and python-liblcms
* the module "lcms" from the python bindings to LittleCMS are available, but
they do not seem to contain any bindings to the actual liblcms1 library
* try the following in the interactive python int
I've also have had problems with the 2.6.20.15.27 (-generic) that came
with the now stable Feisty on my laptop. The Prism54 based PCMCIA card
(Netgear WG511) just wouldn't work with the modules provided by the
kernel (prism54pci, prism54common, and prism54usb). What finally did
work was baking my o
31 matches
Mail list logo
