This file is present in 0.8 (utopic) and later, so I am closing this
bug.
Note that due to a different bug, beignet may not work with linux 3.16 (utopic):
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=767148
Rebuilding the Vivid source package (_not_ trying to install the binary)
in Trusty
Whatever this was, it's long since fixed.
** Changed in: beignet (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/1275248
Title:
FTBFS: error: read-only
Public bug reported:
No Ubuntu changes.
** 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://bugs.launchpad.net/bugs/1393985
Title:
Please sync
Further testing found this to occur only after many clmath operations,
with the number required being fairly but not exactly repeatable, more
for smaller arrays, and being reset by exiting and restarting Python but
not by gc.collect(); this suggests a memory leak, so the problem could
be in either
Public bug reported:
pyopencl is partly or wholly unusable on an Intel i5-3230 integrated
GPU:
beignet 0.3 (trusty default):
pyopencl.elementwise.ElementwiseKernel draws dotted stripes across the screen,
and gives wrong results
pyopencl.clmath segfaults Python
beignet 0.8 (utopic source,
** Description changed:
pyopencl is partly or wholly unusable on an Intel i5-3230 integrated
GPU:
beignet 0.3 (trusty default):
pyopencl.elementwise.ElementwiseKernel draws dotted stripes across the
screen, and gives wrong results
pyopencl.clmath segfaults Python
- beignet 0.8
Public bug reported:
As opencl-icd now has a free provider (beignet), pyopencl has moved from
contrib to main in Debian; it should probably also move from multiverse
to universe in Ubuntu.
** Affects: pyopencl (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug
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[
Created attachment 101990
kernel log 3.15rc-Jun-27
This bug still exists in drm-nouveau-next (commit
242a42eadfc17448a0d5b2ffc0cb191c8b51971a) with Ubuntu 14.04 userspace.
The error message has changed to E[ PFIFO][:01:00.0] INTR
0x0080, and some of the INTR 0x0100: 0x0005
Public bug reported:
In Trusty with the Nouveau driver selected, the system hangs on resume
from suspend, sometimes showing some or all of the pre-suspend screen
contents, and sometimes a boot messages screen.
The system log shows activity after resume, and sometimes (not always) contains
the
** Description changed:
In Trusty with the Nouveau driver selected, the system hangs on resume
from suspend, sometimes showing some or all of the pre-suspend screen
contents, and sometimes a boot messages screen.
The system log shows activity after resume, and sometimes (not always)
** Attachment added: partly redrawn screen
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1333431/+attachment/4137728/+files/IMG_20140623_222930.jpg
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
In Trusty with the nvidia-331 (default) driver selected, the system
won't suspend, and won't turn the screen off when powersave activates;
the screen instead briefly blanks, flashes the Nvidia logo, then goes to
the password entry box.
On unlocking the system after this has
I've found out how /etc/modprobe.d/nvidia-331_hybrid.conf disappeared:
nvidia-331's postrm explicitly deletes it, but as it's a conffile
reinstalling nvidia-331 doesn't put it back. However, having it present
doesn't fix the main bug.
--
You received this bug notification because you are a
Found how nouveau was being loaded while blacklisted: it's in the
initramfs and nvidia-331_hybrid.conf wasn't.
This can be fixed by updating the initramfs (sudo update-initramfs -u,
assuming the kernel you are currently running is the one you want to use
nvidia-331 with), but my system also seems
The NVRM log messages stopped after reinstalling nvidia-331, but the
system continued to use nouveau, and hence to crash (bug 1243557).
modified.conffile..etc.modprobe.d.nvidia.331.hybrid.conf: [deleted]
I don't know how that (which blacklists nouveau) came to be missing, but
purging and
** Attachment added: kern.log
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/1315156/+attachment/4102693/+files/kern.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
After upgrading to Trusty, I briefly used the nouveau driver to check
whether bug 1243557 still existed; after finding that it did, I switched
back to nvidia-331.
However since then, frequently (50% but not always), the system loads
nouveau first, then fails to load
Fixed in Trusty: pyopencl now depends on a new virtual libopencl-1.2-1,
which forces selection of a libopencl1 it will work with. (opencl-icd
still needs to be chosen manually to match the hardware, but that's bug
1264844)
** Changed in: pyopencl (Ubuntu)
Status: Confirmed = Fix Released
This has since got worse: one of the signatures is with a key that used
to be in the debian-keyring package, but that key (5E0577F2) has now
been revoked.
If it is not desired to have this key installed by default, please
create an ubuntu-debug-keyring package (and perhaps have installing it
add
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
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
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
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
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
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.
**
** 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
** 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)
**
** 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
That looks vaguely like a not-fully-installed 2.10.0-2; can you post the output
of:
dpkg -l *flightgear*
dpkg -l *simgear*
ls -l /usr/share/games/flightgear
ls -l /usr/share/games/flightgear/Fonts
but it keeps getting reinstalled.
Are you sure it's being reinstalled, or is it never being
Don't sync ~git20140123, it turned out to have copyright issues
(http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=737733). This is
fixed in ~git20140204, uploaded today.
We're planning to have 3.0 final in Ubuntu 14.04, assuming it's released
on time (17 Feb).
** Summary changed:
- Sync
Upstream openscenegraph consider this probably a Qt bug
(http://lists.openscenegraph.org/pipermail/osg-users-openscenegraph.org/2014-January/065939.html),
possibly one of these:
https://bugreports.qt-project.org/browse/QTBUG-31935
https://bugreports.qt-project.org/browse/QTBUG-200
Your script, and kernel 3.13-rc7 with either the nvd9 or nvd7
firmware also gives a blank screen.
--
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
Created attachment 92127
kernel log 3.13rc+firmware
What does not in the initrd mean? The files were in
/lib/firmware/nouveau with the names the script gave them (nvd9_fuc*).
The errors with kernel 3.13-rc7 (attached) are similar:
Jan 13 22:47:57 lap14 kernel: [1.653189] nouveau [
It still doesn't find the firmware after updating the initramfs (sudo
update-initramfs -u -k all), whether it is placed at
/lib/firmware/nouveau/nvd9_fuc*, /lib/firmware/nouveau/fuc*,
/lib/firmware/kernel_version/nouveau/nvd9_fuc* or
/lib/firmware/kernel_version/nouveau/fuc*. (The script uses
Created attachment 91842
kernel log 3.13rc7 and 3.11+firmware
The 3.13-rc7 upstream kernel in Ubuntu 13.10 also sometimes crashes, but
not as often as the near-identical kernel in Trusty; this might mean the
regression is in userspace, or might be the same persistence (presumably
a left-behind
Created attachment 91782
Ubuntu 14.04 (Linux 3.13.0) log
This bug is easier to trigger in Ubuntu Trusty (kernel 3.13.0, libdrm-
nouveau2 2.4.50, xserver-xorg-video-nouveau 1.0.10, mesa 10.0.1),
occurring immediately on heavy graphics load and within a few minutes
even in ordinary use.
The
It's worse in Trusty, occurring immediately on heavy graphics load and
within a few minutes even in ordinary use.
The attached is the output of apport-bug xserver-xorg-video-nouveau
--save (apport-collect isn't installed by default) after rebooting, and
contains more instances of the warning than
Fixed in upstream 2.99 (packages available at
https://launchpad.net/~saiarcot895/+archive/flightgear-edge , but please
note that this is a development version and hence likely to contain
other bugs).
** Tags added: patch-accepted-upstream
--
You received this bug notification because you are a
This bug was fixed some time ago; sorry for the lack of response here.
Another bug makes --native-ctrls not work with JSBsim aircraft
(including the default c172p) in 2.10 and 2.12; this is fixed in 2.99
(packages available from https://launchpad.net/~saiarcot895/+archive
/flightgear-edge , but
Fixed since 13.04.
** Changed in: openscenegraph (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/1068238
Title:
pkg-config reports wrong path
To
Also exists in 3.2 and development head, reported upstream:
http://lists.openscenegraph.org/pipermail/osg-users-
openscenegraph.org/2013-December/065758.html
** Tags added: upstream
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
: (unassigned) = Rebecca Palmer (rebecca-palmer)
--
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 activate is there is recent joystick input
To manage notifications
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.
**
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.
**
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
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
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
Created attachment 89421
kernel log 2
--
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:
[NVS 4200M] X freeze, unhandled status 0x0080
To manage notifications about this bug go to:
Created attachment 89422
Xorg log 2
--
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:
[NVS 4200M] X freeze, unhandled status 0x0080
To manage notifications about this bug go to:
This bug seemed to become harder to trigger when I installed git-as-of-
Oct-26, then easier again when I installed git-as-of-Nov-14, but given
that this change seemed to persist after returning to 3.11 (suggesting a
left-behind configuration change) and the general randomness of the bug,
this
Switching to the 9.2 branch of mesa makes the git userspace start, but
it still has the original bug. In the attached logs:
Nov 18 16:29 and Xorg log: git kernel, git userspace (libdrm head,
xf86-video-nouveau head, mesa 9.2 branch head)
Nov 18 16:37: Ubuntu kernel, git userspace
--
You
This works for an upgrade of flightgear at the command line (log
attached), but in the case of a previously failed upgrade the user needs
to run sudo apt-get -f install as instructed, and I haven't tested
whether the graphical update manager displays this message (E: Unmet
dependencies. Try
** Bug watch added: freedesktop.org Bugzilla #71659
https://bugs.freedesktop.org/show_bug.cgi?id=71659
** Also affects: nouveau via
https://bugs.freedesktop.org/show_bug.cgi?id=71659
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a
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
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 suspend
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.
This is Debian bug http://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=722513, which is fixed in 2.10.0-3 (in Trusty).
In the meantime, it can be worked around by manually removing fgfs-
scenery-base before installing 2.10.
** Bug watch added: Debian Bug tracker #722513
Closing the bug as I prefer not to risk bricking my system to fix
something that has an easy workaround (and rumour suggests the FreeDOS
method no longer works with recent Dell BIOS updates:
http://askubuntu.com/questions/100945/how-do-i-update-the-bios-of-a
-dell-laptop/237742#237742).
**
Both 3.8 and 3.11 work with reboot=p
(https://wiki.ubuntu.com/BIOSandUbuntu#Reboot_Methods); 3.8 doesn't work
with any other reboot=, which suggests the regression is caused by a
change of default.
** Description changed:
Since upgrading to 13.10, attempting to restart (with either shutdown
apport information
** Attachment added: CurrentDmesg.txt
https://bugs.launchpad.net/bugs/1243557/+attachment/3892901/+files/CurrentDmesg.txt
** Description changed:
With the Nouveau driver selected, my system freezes within a few minutes
of boot if on battery, but only on heavy graphics
apport information
** Attachment added: BootLog.txt
https://bugs.launchpad.net/bugs/1243557/+attachment/3892900/+files/BootLog.txt
--
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:
apport information
** Attachment added: BootLog.txt
https://bugs.launchpad.net/bugs/1243557/+attachment/3892903/+files/BootLog.txt
--
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:
apport information
** Tags added: apport-collected
** Description changed:
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
apport information
** Attachment added: LightdmDisplayLog.txt
https://bugs.launchpad.net/bugs/1243557/+attachment/3892914/+files/LightdmDisplayLog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: HookError_source_xserver_xorg_video_nouveau.txt
https://bugs.launchpad.net/bugs/1243557/+attachment/3892913/+files/HookError_source_xserver_xorg_video_nouveau.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
apport information
** Attachment added: Dependencies.txt
https://bugs.launchpad.net/bugs/1243557/+attachment/3892905/+files/Dependencies.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1243557
apport information
** Attachment added: BootDmesg.txt
https://bugs.launchpad.net/bugs/1243557/+attachment/3892902/+files/BootDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1243557
apport information
** Attachment added: Xrandr.txt
https://bugs.launchpad.net/bugs/1243557/+attachment/3892929/+files/Xrandr.txt
--
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:
apport information
** Attachment added: LightdmGreeterLog.txt
https://bugs.launchpad.net/bugs/1243557/+attachment/3892915/+files/LightdmGreeterLog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: xdpyinfo.txt
https://bugs.launchpad.net/bugs/1243557/+attachment/3892930/+files/xdpyinfo.txt
--
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:
apport information
** Attachment added: UdevLog.txt
https://bugs.launchpad.net/bugs/1243557/+attachment/3892926/+files/UdevLog.txt
--
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:
apport information
** Attachment added: XorgLog.txt
https://bugs.launchpad.net/bugs/1243557/+attachment/3892927/+files/XorgLog.txt
--
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:
apport information
** Attachment added: xserver.outputs.txt
https://bugs.launchpad.net/bugs/1243557/+attachment/3892932/+files/xserver.outputs.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: xserver.devices.txt
https://bugs.launchpad.net/bugs/1243557/+attachment/3892931/+files/xserver.devices.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: CurrentDmesg.txt
https://bugs.launchpad.net/bugs/1243557/+attachment/3892904/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1243557
apport information
** Attachment added: MonitorsUser.xml.txt
https://bugs.launchpad.net/bugs/1243557/+attachment/3892920/+files/MonitorsUser.xml.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: ProcModules.txt
https://bugs.launchpad.net/bugs/1243557/+attachment/3892924/+files/ProcModules.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1243557
apport information
** Attachment added: LightdmGreeterLogOld.txt
https://bugs.launchpad.net/bugs/1243557/+attachment/3892916/+files/LightdmGreeterLogOld.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: XorgLogOld.txt
https://bugs.launchpad.net/bugs/1243557/+attachment/3892928/+files/XorgLogOld.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1243557
apport information
** Attachment added: ProcCpuinfo.txt
https://bugs.launchpad.net/bugs/1243557/+attachment/3892921/+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/1243557
apport information
** Attachment added: ProcInterrupts.txt
https://bugs.launchpad.net/bugs/1243557/+attachment/3892923/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: UdevDb.txt
https://bugs.launchpad.net/bugs/1243557/+attachment/3892925/+files/UdevDb.txt
--
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:
apport information
** Attachment added: DpkgLog.txt
https://bugs.launchpad.net/bugs/1243557/+attachment/3892912/+files/DpkgLog.txt
--
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:
apport information
** Attachment added: ProcEnviron.txt
https://bugs.launchpad.net/bugs/1243557/+attachment/3892922/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1243557
apport information
** Attachment added: Lspci.txt
https://bugs.launchpad.net/bugs/1243557/+attachment/3892918/+files/Lspci.txt
--
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:
[NVS
apport information
** Attachment added: LightdmLog.txt
https://bugs.launchpad.net/bugs/1243557/+attachment/3892917/+files/LightdmLog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1243557
apport information
** Attachment added: Lsusb.txt
https://bugs.launchpad.net/bugs/1243557/+attachment/3892919/+files/Lsusb.txt
--
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:
[NVS
** Attachment added: Xorg log; this one ran unusually long before crashing
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/1243557/+attachment/3892946/+files/nouveau_longrun_Xorg.log
--
You received this bug notification because you are a member of Ubuntu
Bugs,
** Description changed:
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:
** Attachment added: another Xorg log
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/1243557/+attachment/3892947/+files/Xorg.0.log.old
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This bug seems to have become less frequent since my upstream kernel
test: reliably triggering it now requires being on battery and (rather
than or) heavy graphics load. As no relevant packages are listed in the
apt log as upgraded since then, I suspect this test left a configuration
change
** Attachment added: FirmWare Test Suite results
https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1244312/+attachment/3892999/+files/fwts_results.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Haven't seen this since, closing.
** Changed in: nvidia-graphics-drivers (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/1126669
Title:
[regression] GF119
Public bug reported:
After cancelling a System program problem detected alert, it reappears
the next time the system is started, though /var/crash lists no new
crashes. Emptying /var/crash stops this happening.
Apart from being annoying, this gives the false impression that new
crashes are
I'm not comfortable with downloading a kernel from an insecure site (why
isn't kernel-ppa a real PPA, where it would have https and signatures?),
so I tested the upstream git head instead
(https://wiki.ubuntu.com/KernelTeam/GitKernelBuild); it also had this
bug.
** Changed in: linux (Ubuntu)
With the latest upstream kernel (but not changing the userspace parts of
the driver), this bug still exists but takes longer to occur.
** Attachment added: kern.log
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/1243557/+attachment/3892250/+files/kern.log
--
You
Kernel 3.8.0-32 (the next newest on my boot menu, probably the Raring
kernel) does not have this bug.
--
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:
[regression 13.10] Can't reboot
101 - 200 of 425 matches
Mail list logo
