Importing Debian's tzdata 2024b-1 is probably not a good way to do this,
as it also changes to a newer format that saves space but breaks
python3-dateutil and hence several other packages:
https://ubuntu-archive-team.ubuntu.com/proposed-migration/update_excuses.html#tzdata
https://bugs.debian.org/
5.2.1 was included in Ubuntu 24.04.
** Changed in: lxml (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2060811
Title:
FFe updating lxml to the 5
I tested this again, this time in Ubuntu and with enough logging to
confirm that GLPK is being run, and still can't reproduce this bug:
https://launchpadlibrarian.net/742301254/buildlog_ubuntu-oracular-
amd64.snakemake_7.32.4-4+ppa1_BUILDING.txt.gz
(search for test_glpk_solver; it's listed as 'fa
** Changed in: statsmodels (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2043284
Title:
fails to build with Cython 3.0.x
To manage notification
This has been done.
** Changed in: cython (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2064928
Title:
Please merge cython 3.0.10+dfsg-5 from Debian unst
This blocks the pandas 2.2 transition, as that breaks older statsmodels
versions.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2064928
Title:
Please merge cython 3.0.10+dfsg-5 from Debian unstable
** Summary changed:
- FTBFS - test_attach_to_pid* fails
+ test_attach_to_pid* fails
** Description changed:
+ (Edit: now only 3, and no longer an FTBFS but that's because the failure
+ is being ignored)
+
On Ubuntu, but not the same package in Debian, all 5 variants of
test_attach_to_pid* f
Fixed in -proposed, but Ubuntu's Cython is too old to build that
version.
** Changed in: statsmodels (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2043284
"this change will need minor changes in two depending packages."
probably refers to the packages that do use lxml-html-clean now needing
to either stop doing so or explicitly depend on it
(https://bugs.debian.org/1068349).
This has been done in nbconvert (and hence documentation builds of e.g.
pan
Public bug reported:
(Caution: I'm the maintainer of statsmodels but not cython3, and have
*not* checked whether this would actually work.)
statsmodels 0.14.2 is currently unable to build because it build-depends
on cython3 (>= 3.0.10~), which Debian has but Ubuntu has not.
The Ubuntu change (Dr
This may have been fixed: in Debian, snakemake still passes its tests if
glpk-utils is installed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1928940
Title:
snakemake fails with glpk-utils install
Public bug reported:
Please sync pandas from Debian, overriding Ubuntu changes.
The only Ubuntu change is to disable tests to allow building with Python
3.10, which is no longer necessary as they now pass with that version.
debian/changelog:
pandas (1.3.5+dfsg-1) unstable; urgency=medium
* U
Fixed in beignet 1.3.2-8 (but I suggest using intel-opencl-icd instead).
** Changed in: beignet (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1905340
Upstream beignet is dead, and replaced by intel-opencl-icd.
I also don't have that hardware. I've sent a request for testing, but nobody
has replied yet:
https://lists.freedesktop.org/archives/beignet/2020-November/date.html
I don't intend to enable them by default without testing, because I
co
"error, type is 4592, error status is -5" is a rather generic error:
those codes are CL_OUT_OF_RESOURCES (on the GPU) during
CL_COMMAND_NDRANGE_KERNEL (a normal OpenCL computation). The other
error message ("Input/output error") doesn't match, so this probably
_isn't_ 100639 ("Device or resource b
Please try running the tests (install the beignet-dev package, then
/usr/lib/x86_64-linux-gnu/beignet/utest_run ).
If this doesn't trigger the bug, do you have a way to do so that doesn't
require non-Ubuntu software?
** Changed in: beignet (Ubuntu)
Status: New => Incomplete
--
You receiv
It's _mostly_ fixed, but not completely: two variants of varmax
test_bse_oim, and test_pickle_fit_sarimax, still fail.
It's no longer a build failure as the affected tests are xfailed.
** Changed in: statsmodels (Ubuntu)
Status: Fix Released => New
--
You received this bug notification
flightgear 2019.1 was removed because it didn't build with the new
openscenegraph (bug 1883713).
flightgear 2020.1 was then uploaded, which fixed this bug but FTBFS on
s390x (Debian https://bugs.debian.org/963201). Because of this, it is
held in -proposed (https://people.canonical.com/~ubuntu-arc
What package(s) were you trying to update, and what metapackage did it
tell you to install? This may be logged in /var/log/apt/history.log
and/or /var/log/apt/term.log: please copy and paste the exact message.
** Changed in: pandas (Ubuntu)
Status: New => Incomplete
--
You received this
The python-xarray version in -proposed appears to already have these
fixes, but it's instead broken because it expects a newer dask
(test_dask), and on arm*, by long-standing numpy bug
https://bugs.debian.org/877754 (test_datetime_reduce).
The dask version in -proposed appears to fix its pandas 0.
On the pandas autopkgtest failures:
cnvkit, python-feather-format, python-skbio, and q2-types (plus its rdep
q2-cutadapt) are the expected ones, that the package has explicit Breaks
for.
dask, python-xarray and snakemake are unexpected. (They weren't seen in
Debian experimental because the first
This bug should now be fixed.
(It seems to be intermittent / environment-dependent: it didn't happen
on 0.10.1-1.)
** Summary changed:
- Sync statsmodels 0.10.1-2 (universe) from Debian experimental (main)
+ Sync statsmodels 0.10.1-3 (universe) from Debian experimental (main)
** Changed in: sta
Cancel this request - package FTBFS on armhf.
** Changed in: statsmodels (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1851892
Title:
Sync statsmodels 0.10.1-
Public bug reported:
(only just uploaded, so you might not see it yet)
This is in experimental because it removes Python 2 support before
Debian-unstable's rules allow; this is not an issue here as the Ubuntu
version has already dropped it.
Overriding the Ubuntu changes, as they are no longer ne
Debian experimental's pandas 0.25 passes its tests with python3.8. (It
also no longer requires any of the current pandas' Ubuntu changes.)
Warning: pandas 0.23 -> 0.25 is an API change which breaks cnvkit,
python-feather-format, python-skbio, q2-types.
** Changed in: pandas (Ubuntu)
Statu
pandas will probably need an upgrade to upstream 0.25: see
https://bugs.debian.org/931557 for progress on that.
** Bug watch added: Debian Bug tracker #931557
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=931557
** Changed in: pandas (Ubuntu)
Status: New => In Progress
--
You rece
Public bug reported:
Test log:
https://autopkgtest.ubuntu.com/packages/statsmodels/disco/armhf
(This is probably *not* a regression: upstream tests weren't run in
0.8.0-7.)
As noted in the changelog, I attempted to disable this feature on armhf
as I'd rather have an explicit error than silent no
('Fix Released' = 'fixed in current development, i.e. disco'. If you
think this should also be fixed in bionic, see
https://wiki.ubuntu.com/StableReleaseUpdates )
The -lib is missing because pandas failed to build at all on bionic
armhf, with what looks like a crashing test:
https://launchpad.net
('invalid' = 'not our (pandas') bug')
As noted in the linked upstream bug, this only affects Python 2 (python-
pandas), not current Python 3 (python3-pandas).
** Changed in: pandas (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubu
Fixed in Disco (0.23.3) and probably earlier.
** Changed in: pandas (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1728393
Title:
python-pandas 0.17.1-3ub
** Summary changed:
- Please let beignet out of -proposed
+ Please let beignet (soon to be 1.3.2-6) out of -proposed
** Description changed:
- beignet is an Intel-specific package with an arch:all transitional dummy
- package. Hence, its autopkgtests have never actually passed on non-x86.
- (Th
Public bug reported:
beignet is an Intel-specific package with an arch:all transitional dummy
package. Hence, its autopkgtests have never actually passed on non-x86.
(They should probably be uninstallable rather than failing when run, but
that would still count as failing.)
However, debci/britne
Additional information (note in particular that Intel consider the
graphics development branch at https://cgit.freedesktop.org/drm-tip, not
the integration branch at kernel.org, to be the appropriate "latest
upstream" to test against):
https://01.org/linuxgraphics/documentation/how-report-bugs
An
('invalid' = 'not beignet's bug' - I do agree it is *a* bug)
The kernel code that reads these numbers from the device
(https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/drivers/gpu/drm/i915/intel_device_info.c#n434)
does explicitly support the 47 EU case (any one of the 48 fa
Further information may be available in the files (readable only by
root, the 0 may be different if you have more than one graphics device):
/sys/kernel/debug/dri/0/i915_capabilities
/sys/kernel/debug/dri/0/i915_sseu_status
** Summary changed:
- Performance degraded in Cosmic
+ [regression] Wron
> I suppose the question now is why did teh code get 48 in Bionic, but only get
> 24 in Cosmic?
Agreed; I'll look into this later.
> And how to report the bug in the build logic for finding python...
Here is enough. (It's probably in beignet, not dpkg-buildpackage, and not new:
packages for dis
Well spotted - BOINC "GFLOPS peak" is the theoretical 8 * compute units
* max clock (not an actual speed measurement), and matches the 24
compute units clinfo reports, not the 48 compute units this GPU is
supposed to have.
Beignet can take this value from an internal hardcoded list (in
src/cl_devi
Was this report sent from the affected system? as it says the CPU is an
i5-2500K, which is too old for beignet. (It shouldn't crash, but won't
be running the computations, so the slowdown is probably from some other
package.)
Please post the output of clinfo (from the clinfo package).
** Change
pandas and statsmodels are now available on s390x. (Also, the gnocchi
packages no longer depend on them.)
('Fix released' means 'fixed in current development'. If you are
requesting a fix in Xenial, https://wiki.ubuntu.com/UbuntuBackports but
be aware the pandas API changes often enough that a p
There are actually three separate issues here, but as (a) is already
known and (b) is not a bug, I define this bug to be (c).
To understand them, it is necessary to know that OpenCL computations are
asynchronous: a clmath expression like "aCL=bCL+cCL" places this
operation in a CommandQueue and re
** Patch added: "eventchain-memory-leak.patch"
https://bugs.launchpad.net/ubuntu/+source/pyopencl/+bug/1354086/+attachment/5164304/+files/eventchain-memory-leak.patch
** Changed in: beignet (Ubuntu)
Status: New => In Progress
--
You received this bug notification because you are a mem
It would have eventually, if you'd run more iterations: each iteration
leaks ~450 bytes before
https://cgit.freedesktop.org/beignet/commit/?id=7ae1517cfc373847f168ffb3e41b635861af19c7
but ~20,000 bytes after. I suspect the reason for this is that events
no longer release exec_data.gpgpu on complet
The bug is technically in your code: as you never call clReleaseEvent
(waiting on an event doesn't release it), you leak an event object per
iteration. I suspect the beignet change exposed this bug by greatly
increasing the effective size of an event object, but don't yet know
how.
There is a C++
Current llvm-toolchain-* packages do have versioned symbols (since
3.8.1-22 / 3.9.1-8 / 4.0-5: https://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=849098), but this 3.8 has not been backported.
Note that loading the *same* LLVM version twice can also crash, for a
different reason: https://bugs.debi
Memory consumption rises over a run, by ~2GB by the failure point. The
exact number of iterations before failure depends on the beignet version
but not the matrix size.
git bisect finds that this was introduced by
https://cgit.freedesktop.org/beignet/commit/?id=7ae1517cfc373847f168ffb3e41b635861
It has now been successfully built.
** Changed in: theano (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1777302
Title:
Please sync theano 1.0.2+dfsg-1 (u
Public bug reported:
(If your build servers don't update immediately you might need to wait a
bit - sphinx 1.7.5-1 had a bug that made this FTBFS (Debian #901662),
and 1.7.5-2 has only been available for ~7 hours.)
The Ubuntu change is now part of the Debian package (the second point
below).
the
The underlying issue is not new; I don't know whether it's got worse per
test or the test suite has just got longer. See the linked Debian bug
for further analysis.
This will probably make it build (by splitting up the test suite, i.e.
it doesn't solve the underlying problem) but I haven't had ti
** Bug watch added: Debian Bug tracker #898126
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=898126
** Also affects: theano (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=898126
Importance: Unknown
Status: Unknown
--
You received this bug notification because
Looks like it's a cumulative memory leak: over the python2 tests, memory
usage increases by ~6GB. (Measured by occasionally looking at System
Monitor, so I know it's more than one step, but not whether it's a few
bad tests or a smaller amount on every test.) This is then freed when
the python2 te
Public bug reported:
The build logs show 16 tests running out of memory on arm64 [0] and 57
on ppc64el [1].
How much is too much, and is it a set maximum or dependent on what else
the buildd is doing? A first attempt at running the same tests locally
(Debian amd64, python3) gave ~300MB memory us
('invalid' as in 'not our (theano's) bug')
Where did you obtain nvidia-381 (Ubuntu itself went straight from -375
to -384)? the Nvidia website? a PPA?
nvidia-graphics-drivers-384 is now available in xenial-updates: is that
any better?
(libcudata.so.8 is probably a different library, not the file
Public bug reported:
Please sync beignet 1.3.1-1 (universe) from Debian unstable (main)
The only Ubuntu change (use LLVM 3.9 instead of mesa's 4.0) is now
included in the Debian package.
beignet (1.3.1-1) unstable; urgency=medium
* New upstream release.
* Drop patches applied upstream, refr
I use Debian now, where (spyder 2.3.1, Cinnamon desktop) it appears to
be fixed.
If anyone who is using Ubuntu does still see it, please reopen this bug.
** Changed in: spyder (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bu
Switching to llvm-dev/libclang-dev (which are 4.0) does fix this crash
bug, and the other error message went away after installing dbus-x11 in
the chroot, but I don't know this application well enough to do more
general testing.
(You have the wrong bug number in the changelog.)
--
You received t
Rebuilding kdevelop against LLVM 4.0 (via the obvious change to
debian/control) avoids this crash; it still fails to create the project
(with "please see the Version Control toolview" even though I left
Version Control at the default None), but I suspect that's an unrelated
"doesn't really work in
Public bug reported:
On creating a new project, kdevelop shows an "Unable to load the project
file" error box, then crashes when this is OKd. The backtrace suggests
this is https://bugs.debian.org/846410 , reappearing because Ubuntu mesa
is now LLVM 4.0:
Thread 1 "kdevelop" received signal SIGSE
** Patch added: "beignet_llvm-39-only.patch"
https://bugs.launchpad.net/ubuntu/+source/beignet/+bug/1668024/+attachment/4827061/+files/beignet_llvm-39-only.patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpa
Debian beignet automatically uses the same LLVM version as mesa, to
avoid crashing when OpenCL and OpenGL are used together (as LLVM lacks
symbol versioning - https://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=848368#46 ). Ubuntu -proposed mesa now uses LLVM
4.0, which beignet isn't compatible wit
Public bug reported:
Bug fix upload, has a freeze exception in Debian:
beignet (1.3.0-2) unstable; urgency=medium
* Statically link to LLVM to allow installation together with
mesa-opencl-icd (workaround for #852746).
* Disable OpenCL 2.0 on i386, as it is likely to crash.
(Closes: #
The Debian package of 1.2.1 is in Alioth awaiting sponsorship; once
uploaded there it will automatically be imported to Ubuntu zesty
(current development), but not existing releases.
This might work in 16.04, but has *not* been tested:
git clone https://anonscm.debian.org/cgit/pkg-opencl/beignet.
pocl was already in Ubuntu, but was unbuildable in 16.04
(https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=799322). This has
now been fixed, but too late for 16.04.
If your hardware supports it, mesa-opencl-icd or beignet-opencl-icd is
likely to be faster.
** Summary changed:
- [needs-packagin
I can't reproduce this (stellarium + an OpenCL-using Python script).
What hardware are you using? ( xrandr --listproviders ; lspci -nn | grep -e
"\[03..\]:" )
Does OpenCL work?
Does the bug only happen if beignet is being used at the time, or is it enough
for it to be installed?
--
You receive
Public bug reported:
Downgrading cmake to 3.2 reopened https://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=802826 (can't find Python 3.5): python3.5.diff
only fixes FindPythonLibs, not FindPythonInterp.
This makes at least beignet FTBFS:
-- Could NOT find PythonInterp (missing: PYTHON_EXECUTABLE)
I no longer have the affected hardware.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1333417
Title:
[regression] [Dell Latitude E6520] [NVS 4200M] Hangs on resume from
suspend
To manage notifica
*** This bug is a security vulnerability ***
Public security bug reported:
These packages contain bug fixes, including 2 security fixes (
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=780712
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=780716 ).
None of these packages have any real Ubun
** Attachment added: "flightgear_3.4.0_testlogs.txt"
https://bugs.launchpad.net/ubuntu/+source/flightgear/+bug/1443528/+attachment/4374116/+files/flightgear_3.4.0_testlogs.txt
** Also affects: flightgear-data (Ubuntu)
Importance: Undecided
Status: New
** Also affects: simgear (Ubunt
This version was intended as a normal "unstable" upload (not really
experimental, but also not intended to be synced under freeze): while
the new upstream happens to be a bug fix release, the packaging changes
aren't so restricted.
However, I'm not aware of it causing any problems in Debian, so if
The default path has now been corrected, so closing this.
If your system continues to offer the old path, it may be a saved
setting.
** Changed in: fgo (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
** Changed in: fgo (Ubuntu)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/904231
Title:
Typo in desktop file
To manage notifications about this bug go to:
Please install the debugging symbols and post a backtrace, as follows
(in a terminal):
$ sudo apt-get install libsimgearcore3.0.0-dbg libsimgearscene3.0.0-dbg gdb
[3.0.0 is the version in official 14.04; 3.4.0 if you are using the PPA]
$ gdb fgfs
(gdb) set pagination 0
(gdb) run
[wait for the cras
As nobody has been able to test this in flightgear, assuming it's the
same really-in-mesa problem. (It's also likely that this hardware
wouldn't run flightgear at a usable speed anyway.)
** Changed in: flightgear (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notificatio
Public bug reported:
Bug fix upload:
beignet (1.0.1-3) experimental; urgency=medium
[ Rebecca N. Palmer ]
* Fix two crashes on unsupported hardware. (Closes: #779213)
* Fix buffer overflow in error handling.
* Enable multiarch.
[ Andreas Beckmann ]
* Ensure proper removal of the pr
> there's probably more work to be done for the openscenegraph
migration?
ossim, osgearth and openwalnut need rebuilding (but probably no actual
changes, given Debian's experience).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
http
That confirms that the problem is on the first line (i.e. LIBOSG_SHARE
is being set to the empty string), but means it isn't related to the
presence or absence of a multiarch suffix.
The version numbers that end up in LIBOSG_VERSION appear to be only
packages that are in the base/build-essential s
Thanks.
The connection to libcitygml is that libopenscenegraph100 and all its
dependencies (including ones that are themselves OK, such as these
packages) can't leave -proposed yet, because doing so would break the
old libcitygml: https://wiki.ubuntu.com/ProposedMigration
I have posted some sugge
dholbach's test builds appear to have been without -proposed as they
used libopenscenegraph99, which isn't multiarch (the
libopenscenegraph100 in -proposed is), but I don't have any other theory
for where the 19 comes from.
If it is multiarch-related, the fix would be to replace the
libopenscenegr
A guess at what's going on: the first line of gencontrol is failing to
find libopenscenegraph100 (possibly because the grep pattern assumes
dpkg --get-selections will include the :arch suffix; does it do that if
multiarch isn't on?), and the second line is hence extracting the
version numbers of _e
I can't reproduce this problem: on my system (dpkg-buildpackage -b with
fakeroot, in amd64 vivid+vivid-proposed chroot on Debian kernel) it
builds successfully (log attached).
I also don't see where the "19 1" can be coming from (unlike the "0~rc1"
in the vaguely similar https://bugs.debian.org/cg
The libcitygml breakage has already been fixed in Debian (as
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=763047 ), so syncing
that package and rebuilding openscenegraph's other dependencies should
fix that problem.
** Bug watch added: Debian Bug tracker #763047
http://bugs.debian.org/cgi-
That's not the version of simgear I asked for: we're skipping over 3.2
and going straight to 3.4, but due to NEW queue delays this is only in
Debian git, not Debian main archive.
The install failure looks like you built it on a system with -proposed
enabled then tried to install it with -proposed
Public bug reported:
Please upload simgear 3.4.0-0~exp1 from Debian git
https://anonscm.debian.org/cgit/collab-maint/simgear.git/commit/?h=experimental&id=ab844aa5e0578e6d2116cf4bc2c845876fbe11c3
(*not* the older 3.4.0~git20150211+eff3df-0~exp1 in the Debian NEW
queue, which is the reason this ca
1.0.1-2 now in Debian.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1421109
Title:
Sync beignet 1.0.1-2 (universe) from Debian experimental (main)
To manage notifications about this bug go to:
htt
Assigning a bug to yourself means intending to fix it, which given that
you "can;t do anything" was probably not what you meant.
If your system does not work, please file a new bug stating exactly what
is wrong: https://help.ubuntu.com/community/ReportingBugs
If you are looking for general help w
That's basically the same fix I just pushed to Alioth as 1.0.1-2.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1421109
Title:
Sync beignet 1.0.1-1 (universe) from Debian experimental (main)
To man
Public bug reported:
This version has only just cleared NEW, so it may not be on your mirror
yet.
** Affects: beignet (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bu
Public bug reported:
New upstream release
http://lists.alioth.debian.org/pipermail/pkg-opencl-devel/Week-of-Mon-20150209/000610.html
https://launchpad.net/~ginggs/+archive/ubuntu/testing/+sourcepub/4770940/+listing-archive-extra
** Affects: vdpauinfo (Ubuntu)
Importance: Undecided
Public bug reported:
Debian has switched to a new implementation of clinfo; please import
this to Ubuntu.
http://lists.alioth.debian.org/pipermail/pkg-opencl-devel/Week-of-Mon-20150209/000610.html
https://launchpad.net/~ginggs/+archive/ubuntu/testing/+sourcepub/4770941/+listing-archive-extra
**
** Summary changed:
- [i5-3230] Crash/hang/graphical artifacts in pyopencl
+ [i5-3230] Tight pyopencl.clmath loops cause out-of-memory system hang
** Description changed:
- pyopencl is partly or wholly unusable on an Intel i5-3230 integrated
- GPU:
+ In beignet (not pocl), tight loops involving
The original bug (which I no longer have the hardware from) was on BIOS;
should the EFI problem be a separate bug?
Does changing the timeout settings to always-show (see above) work on
EFI?
> I need the GRUB menu because I need to add 'nomodeset'
There's a GRUB_CMDLINE_LINUX parameter in /etc/de
This is probably a hardware (disk or memory) problem, not a bug (the log
contains "dpkg-deb (subproceso): descomprimiendo el miembro del archivo:
error de lzma: los datos comprimidos están corrompidos" = "dpkg-deb
(subprocess): decompressing archive member: lzma error: compressed data
is corrupt");
Sorry, upstream explicitly don't want bug reports for cards older than
nv30 (yours is nv18, current is ~nv120):
http://nouveau.freedesktop.org/wiki/MesaDrivers/
Changing the error message (at
http://sources.debian.net/src/mesa/10.3.2-1/src/mesa/drivers/dri/nouveau/nv10_render.c/#L104
) to somethin
The error occurs because nv10 (the driver used for this card) declares
VBO support (extension GL_ARB_vertex_buffer_object) but only supports
VBOs of int8, int16 and float (not double) types, and the application is
trying to draw data of type double. Given that the double type is part
of the OpenGL
(Sorry about the repeated questions: that's the nature of debugging a
problem that only happens on hardware I don't have.)
That looks like either a bad GLcontext (at the error location it is only
looking at this internal structure, not the objects to be drawn), or an
attempt to use VBO (an OpenGL
> stellarium:
> ../../../../../../../src/mesa/drivers/dri/nouveau/nv10_render.c:104:
> get_hw_format: Assertion `0' failed.
That also appears to mean "invalid format", so is probably the same bug.
> For whatever it's worth, I did the routine you described. The Stellarium
> startup screen appear
This is not a bug: the OpenGL 4.x Reference documents the OpenGL 4 core
context, which does not include the deprecated functions such as
glBegin.
These functions are still available in OpenGL 4 compatibility contexts
and are documented at https://www.opengl.org/sdk/docs/man2/ , but be
aware that t
This was because prior to 1.2-svn26009 the package used an explicit list
of what files to include ( http://sources.debian.net/src/khronos-opencl-
headers/1.2-2013.06.28-2~bpo70%2B1/debian/rules/#L14 ) which did not
include cl_egl.h; this has now been fixed.
As this package has no dependencies, ins
The log contains "dpkg-deb (subprocess): decompressing archive member:
lzma error: compressed data is corrupt", which suggests this is a
hardware (disk or memory) problem, not a bug; hence, I am closing it.
"sudo apt-get clean" then retrying the install should fix the package,
but be aware that th
The log contains "dpkg-deb (subprocess): decompressing archive member:
lzma error: compressed data is corrupt", which suggests this is a
hardware (disk or memory) problem, not a bug; hence, I am closing it.
"sudo apt-get clean" then retrying the install should fix the package,
but be aware that th
This isn't a flightgear bug, it's an apt/ubuntu-release-upgrader bug,
and according to #8 is already fixed (in later releases, obviously this
won't help 12.04 -> 14.04).
Removing flightgear and reinstalling it after the upgrade should be fine
as a workaround, since flightgear would be being upgrad
1 - 100 of 423 matches
Mail list logo
