This bug seems to keep disappearing and reappearing in Jaunty (just now
it disappeared on a reboot staying in the default kernel), suggesting it
was not fixed there after all but has some intermittent cause.
This also means that one liveCD test doesn't prove it fixed in Karmic,
though I am leaving
The title says [upstream], but there is no link to the qa.openoffice.org
bug tracker and I can't find this bug there. Does the "OpenOffice"
project within Launchpad count as sending it upstream, or am I supposed
to submit it to qa.openoffice.org myself?
--
[upstream] [impress] Black first slide
** Attachment added: "BootDmesg.txt"
http://launchpadlibrarian.net/32724028/BootDmesg.txt
** Attachment added: "CurrentDmesg.txt"
http://launchpadlibrarian.net/32724029/CurrentDmesg.txt
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/32724030/Dependencies.txt
** A
Public bug reported:
My system no longer automounts USB memory sticks (ie nothing appears on
the desktop, Nautilus window, or /media directory). lsusb does find the
stick, and 3 entries appear in /dev: usbdev2.n_ep00, usbdev2.n_ep01 and
usbdev2.n_ep81, where "n" is a number which changes each tim
Now also fixed in Jaunty (despite the absence of changes to the linux
package).
--
[regression] USB sticks not automounted
https://bugs.launchpad.net/bugs/438944
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing lis
The bug has now reappeared in Jaunty (first noticed yesterday, 16th).
--
[regression] USB sticks not automounted
https://bugs.launchpad.net/bugs/438944
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-b
The bug is not present in mainline 2.6.28.10. It also was definitely
not present a few days before being reported, so must be a recent
change.
With 2.6.31-11.36 (the Karmic kernel, but leaving the rest of the system
unchanged) or 2.6.32-1 Oct daily, the system hangs during startup, but
the instru
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
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
"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
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
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
> 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
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
('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
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
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 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
('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:
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
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
** 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
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
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
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
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
('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
('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
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
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
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
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
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
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
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++
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
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
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
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: #
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
** 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
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
More tests, again within Saucy, but this time with the graphical update-manager:
-Update installs cleanly over 2.6.0 or non-broken 2.10.0 and works.
-Over broken 2.10.0 (i.e. after a failed upgrade), update-manager tells the
user to run apt-get install -f; this fixes the problem whether or not -pr
Did you delete the nvidia libopenCL* from both
/usr/lib/nvidia-319-updates and /usr/lib32/nvidia-319-updates, and are
they still absent (an update of nvidia-319-updates might have put them
back)? Does the problem persist after restarting the machine?
My setup of copying libOpenCL.so.1.0.0 to /usr
This is partially fixed in Trusty (nvidia-graphics-drivers-331): nvidia-
libopencl1-331 is now a separate package which the main driver only
Recommends:, so co-installing ocl-icd-libopencl1 and nvidia-331 is now
allowed, but as virtual packages aren't versioned, pyopencl will still
think nvidia-lib
Comments in the linked question suggest this was fixed in 2.4 (current
Ubuntu has 2.10), so I am closing this as fixed.
If you still have this problem in the current version, please reopen the
bug (click Fix Released and change back to New), and specify what
location/scenery triggers it.
** Chang
As Natty is no longer supported and I cannot reproduce this bug in
Saucy, I am closing it; I apologise for the lack of an earlier response.
If you still experience this bug in Saucy, please reopen it (click
Invalid and change it back to New), and if possible, specify how to
trigger the bug.
** Ch
and frei0r was fixed by the sync from Debian of 1.1.22git20091109-1.4,
so closing this bug
** Changed in: frei0r (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/bu
BIOS: it's the same machine as bug 1244312 (and became an issue when I
was testing that bug).
(Is there a different way to bring up the GRUB menu on UEFI? If so, it
should probably be documented...)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribe
No longer present in 13.10.
** Changed in: deja-dup (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/1204526
Title:
"Backup location does not exist" after suspen
Also a fix for upstream bug 1117 ( http://code.google.com/p/flightgear-
bugs/issues/detail?id=1117&q=2090&colspec=ID%20Type%20Status%20Priority%20Summary%20Aircraft%20Milestone
), another format string security bug.
Note that neither of these fixes have been tested.
** Patch added: "flightgear_bu
The original report doesn't say so but it looks like
SGSocketUDP::readline is vulnerable as well: the attached fixes both.
(I kept the negative-length check but consider it mostly pointless: if
you can't assume length is the correct length of buf, it's impossible to
prevent an overflow.)
** Patch
Sorry, stray bracket.
** Patch removed: "simgear_CVE2012_2091.patch"
https://bugs.launchpad.net/ubuntu/+source/flightgear/+bug/1077624/+attachment/3806302/+files/simgear_CVE2012_2091.patch
** Patch added: "simgear_CVE2012_2091.patch"
https://bugs.launchpad.net/ubuntu/+source/flightgear/+b
Did you apply the security patches (Debian bug http://bugs.debian.org
/cgi-bin/bugreport.cgi?bug=669025 ), and if not is there a reason you
can't? Both Ubuntu's and Debian's 2.10 source look unpatched.
** Bug watch added: Debian Bug tracker #669025
http://bugs.debian.org/cgi-bin/bugreport.cgi?
** Patch removed: "simgear_CVE2012_2091.patch"
https://bugs.launchpad.net/ubuntu/+source/simgear/+bug/1077624/+attachment/3806309/+files/simgear_CVE2012_2091.patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launch
Sorry...my previous patch had an off-by-one error. Corrected patch
attached.
** Patch added: "simgear_CVE2012_2091.patch"
https://bugs.launchpad.net/ubuntu/+source/simgear/+bug/1077624/+attachment/3808144/+files/simgear_CVE2012_2091.patch
--
You received this bug notification because you ar
It appears that my "fixes both", which I meant as "2091 for both read()
and readline()", has been misinterpreted as "both 2090 and 2091", with
the result that Saikrishna's simgear 2090 patch was not applied; my
flightgear patch for upstream issue 1117 wasn't applied either.
I.e. there should be th
The fixed packages in Debian are flightgear 2.10.0-2 and simgear
2.10.0-3, both currently in the build queue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1077624
Title:
FFe: Update Flightgear to v
Created attachment 96611
Xorg log 3.14rc-Mar-26
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1243557
Title:
10de:1056 [Dell Latitude E6520] [NVS 4200M] X freeze, "unhandled
status 0x0080"
To
Created attachment 96610
kernel log 3.14rc-Mar-26
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1243557
Title:
10de:1056 [Dell Latitude E6520] [NVS 4200M] X freeze, "unhandled
status 0x0080"
This bug still exists in 3.14rc commit
f217c44ebd41ce7369d2df07622b2839479183b0 (26 Mar Linus' tree, Ubuntu
userspace; as the nouveau/master branch hasn't been used for 5 months,
should we stop suggesting that people test with it?).
Is there anything else I can do to help? I will probably only ha
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.
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
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
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
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
I have the same bug in Maverick, Intel 965GM graphics on the internal
monitor, desktop effects off.
It did not occur in Lucid (there I had bug 623561 instead).
** Changed in: gnome-screensaver (Ubuntu)
Status: Invalid => New
--
You received this bug notification because you are a member
Sorry, it seems I wasn't paying attention; this bug has gone, the
problem I have now is the desktop reappearing before the unlock dialog
when the screensaver is active (bug 390989).
** Changed in: gnome-screensaver (Ubuntu)
Status: New => Fix Released
--
You received this bug notification
Reappeared today, same lack of anything useful in the logs.
** Changed in: gnome-screensaver (Ubuntu)
Status: Fix Released => New
--
Unlock dialog sometimes triggers without screensaver active
https://bugs.launchpad.net/bugs/623561
You received this bug notification because you are a memb
Public bug reported:
Binary package hint: clamav
Some files trigger the following error message when scanned; all the
ones I've identified so far are PDFs, and trigger it repeatably, but as
these messages are not logged, I am not sure if this is the only file
type they occur on.
The example file
--
[regression] Bytecode/JIT errors when scanning some PDFs
https://bugs.launchpad.net/bugs/683548
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.ubuntu.com
https://lists.ubuntu.com/mailma
The full workaround sequence is the one I posted in the updated
description, not the comments. (There's no such package as just
"nouveau", so sudo apt-get remove nouveau won't do anything, and the
drivers dialog does a remove not the here-required purge.)
I also have the "nouveau W[ PFIFO][:
Public bug reported:
(If you can't see this version yet, it's probably because it's only just
been uploaded to Debian. simgear, flightgear and fgrun will follow
shortly: do you prefer one bug or separate ones?)
No Ubuntu changes in Trusty, and the Ubuntu fix in Saucy is already in
Debian.
** Aff
** Also affects: simgear (Ubuntu)
Importance: Undecided
Status: New
** Summary changed:
- Please sync flightgear-data 3.0.0-1 (universe) from Debian sid (main)
+ Please sync flightgear-data 3.0.0-1 (universe) and simgear 3.0.0-1 (universe)
from Debian sid (main)
** Description changed
** Summary changed:
- Please sync flightgear-data 3.0.0-1 (universe) and simgear 3.0.0-1 (universe)
from Debian sid (main)
+ Please sync flightgear-data 3.0.0-1 (universe), simgear 3.0.0-1 (universe),
flightgear 3.0.0-1 (universe) and fgrun 3.0.0-1 (universe) from Debian sid
(main)
** Descript
** Attachment added: "fgrun build log (I didn't bother setting the version
number for this test, but this is the same source that became 3.0.0-1)"
https://bugs.launchpad.net/ubuntu/+source/fgrun/+bug/1282142/+attachment/3987146/+files/fgrun_3.0.0%7Egit20140130%2B80f6df0-1_amd64.build
--
You
Fixed in 3.0.0 (in Trusty).
** Changed in: flightgear (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/793599
Title:
Gnome-screensaver shouldn't act
Partially fixed in 3.0.0 (Trusty): the Dash entry now has an icon, but
the running program doesn't, as openscenegraph doesn't provide a way to
set one; this has long been known upstream
(http://forum.openscenegraph.org/viewtopic.php?t=1789; the suggested fix
there doesn't work), but is not yet fixe
We suspect this is because one or both of the symlinks the prerm script
removes are already removed, probably by a failed or interrupted
previous removal/upgrade; if so, it is fixed in 3.0.0-1 (in Trusty).
If the package works other than this message, it should be OK to ignore
it until Trusty is r
The path settings you refer to are not defaults in fgrun itself, but
settings the user previously entered, which the package management
system isn't allowed to touch as they are stored in the user's home
directory.
3.0.0 (in Trusty) does add (correct) default paths, but these only
appear when ther
** 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 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
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
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
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
** 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:
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
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
Public bug reported:
After upgrading to 13.10, the login screen was in reduced resolution,
and after logging in I got a black screen with an error box that monitor
setup had tried and failed to find a supported resolution (can't
remember the exact wording), also in reduced resolution.
The text tt
** Attachment added: "apt-term.log"
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1243158/+attachment/3887303/+files/apt-term.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/b
This also happens on 13.04 -> 13.10 (on the first attempt and without
the debconf message).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1174093
Title:
disable screensaver locking at start
** Tags removed: i386
** Tags added: patch-accepted-debian saucy
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1174205
Title:
Using pyopencl doesn't work and spits our ImportError
To manage notific
Confirmed that on 13.10 this also affects amd64 (probably because the
Conflicts: mentioned above caused ocl-icd-libopencl1 to be removed), and
that it can be fixed by deleting the nvidia libopenCL.so* files and
installing the ocl-icd-libopencl1 ones (I manually copied them to
/usr/local/lib and ran
Public bug reported:
With the Nouveau driver selected, my system freezes within a few minutes
of boot if on battery, but only on heavy graphics load (flightgear in
maximized window) if on mains. The mouse pointer still moves, but
neither the keyboard LEDs nor Alt+SysRq+b reboot work: the only way
Possibly relevant: this machine had ocl-icd-libopencl1 installed, and
nvidia-319 Conflicts: with that. If that is the problem, removing
libopencl1 from nvidia-319 (as already proposed to fix bug 1174205)
would also fix this bug.
** Tags added: patch-accepted-debian
--
You received this bug noti
Public bug reported:
Since upgrading to 13.10, attempting to restart (with either "shutdown
-r now" or the system menu item) hangs with a "reboot: restarting
system" message instead of actually rebooting, but shutting down still
turns the system off.
ProblemType: Bug
DistroRelease: Ubuntu 13.10
P
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1244312/+attachment/3890846/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1244312
apport information
** Attachment added: "RfKill.txt"
https://bugs.launchpad.net/bugs/1244312/+attachment/3890851/+files/RfKill.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1244312
Title:
[r
101 - 200 of 423 matches
Mail list logo
