Public bug reported:
PulseAudio Preferences (paprefs) appears to be searching for modules in
the wrong location.
Specifically, the "install" button appears when modules relevant modules
cannot be found by paprefs.
paprefs is searching for modules in the location: /usr/lib/pulse-13.99/modules/
I can confirm that I am still having this issue on 3.34 as well
(Manjaro).
This is shocking to me that anyone using Gnome to develop doesn't
encounter this bug at minimum of 5x per day. Or are Gnome developers
using MacOS and MBPs to develop like those in the lol "Linux"
Foundation.
+Scott
For those that run linux and want to update their Firefox icon so it
automatically launches with GTK_THEME="Adwaita:light" firefox %u instead
(band-aid work around that shouldn't need to be).
$ cp /usr/share/applications/firefox.desktop ~/.local/share/applications
$ gedit
I am having this issue with Firefox 66.0.3 using Ubuntu 19.04 (Gnome
3.32 using Adwaita dark).
This release seems to ignore:
widget.content.allow-gtk-dark-theme in about:config is set to default / false
widget.chrome.allow-gtk-dark-theme in about:config is also default /false
I came back to
I believe I made a mistake in the steps taken above.
I believe I rebooted my computer once after the `journalctl --vacuum-
time=1s`
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
# journalctl rotate
# journalctl --vacuum-time=1s
journalctl -b-1 --no-pager > prevboot.txt
** Attachment added: "prevboot.txt"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1828649/+attachment/5264569/+files/prevboot.txt
--
You received this bug notification because you
Public bug reported:
When I switch to wayland the gnome desktop locks up before I see my desktop.
It doesn't lock up when I have my laptop closed and only one display connected.
When I connect up the second display, it locks up every time.
I tried deleting my monitors.xml file.. that doesn't
The solution until this is solved is to use something other than gnome
shell as far as I know. Mint Cinnamon and Elementary are both popular
alternatives.
On Sun, Feb 10, 2019, 1:29 PM Adrian <1181...@bugs.launchpad.net wrote:
> I am facing the same issue in Ubuntu 18.10. The super key randomly
Don't get too excited..
https://gitlab.gnome.org/GNOME/nautilus/issues/703
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gvfs in Ubuntu.
https://bugs.launchpad.net/bugs/1706097
Title:
gvfsd-mtp crashed with SIGSEGV
Status in gvfs:
** Attachment added: "the horizontal band"
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1799061/+attachment/5203629/+files/20181020_172736.jpg
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
** Attachment added: "the bright box"
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1799061/+attachment/5203630/+files/20181020_172739.jpg
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
Also note that the screen jitters at the GDM login screen.
My video card does not exhibit have any of these issues when I boot into
Windows 10.
Sometimes logging in doesn't fix the jittering so I reboot into Windows
10.
--
You received this bug notification because you are a member of Desktop
Public bug reported:
Video does not appear to be getting set correctly for GDM but seems
"corrected" after I login.
I have attached some screenshots.
ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: xorg 1:7.7+19ubuntu8
ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
Uname: Linux
Copy and Paste is not working for me on a freshly installed copy of 18.04.1
using Wayland.
Is this regression from 3 years ago still not resolved?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to file-roller in Ubuntu.
** 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
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
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:
This also affects 18.04 (updated to July 5, 2018)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager-applet in Ubuntu.
https://bugs.launchpad.net/bugs/1724921
Title:
VLANs get incorrectly listed under Bluetooth
Status in
Public bug reported:
When I use a Wayland session I am unable to use either Portrait mode.
I have the same problem at work using my Intel Integrated Video on my
Lenovo X230 laptop.
Given that both AMD and Intel are broken, it looks to be a regression of
some sort.
ProblemType: Bug
('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
Also note that this problem also affects Bionic 18.04 users with
4.15.0-12-generic
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1710754
Title:
[System Product Name, VIA VT2020,
** Attachment added: "Fresh boot -- after re-plug -- woking sound from rear
green jack"
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1710754/+attachment/5082539/+files/alsa-info-after.txt
--
You received this bug notification because you are a member of Desktop
Packages, which
** Attachment added: "Fresh boot -- no sound from rear green jack"
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1710754/+attachment/5082538/+files/alsa-info-before.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
I believe I have corrected this by changing my refresh rate from 59.99
Hz to 59.86 Hz.
Is this a requirement for 2560x1600 resolution on DL-DVI? Should this
perhaps be communicated upstream to someone who knows better?
--
You received this bug notification because you are a member of Desktop
I just installed the 18.04 daily and formatted a fresh partition (no
prior home directory or any existing data used) and this is still an
issue in 4.15.0-12-generic.
Can I run a command to manually turn on this jack at startup or force it
to recheck that input to see if something is plugged in?
Public bug reported:
This is likely a wayland issue. I can't bear the tearing if I don't use
wayland.
I get screen flickering (approximately every 5 seconds) and some windows
seem to bring up some mis-colored moving artifacts that clear when the
window is closed.
ProblemType: Bug
The other bug was closed. Here is the correct one.
https://bugzilla.gnome.org/show_bug.cgi?id=789626
** Bug watch added: GNOME Bug Tracker #789626
https://bugzilla.gnome.org/show_bug.cgi?id=789626
--
You received this bug notification because you are a member of Desktop
Packages, which is
https://gitlab.gnome.org/GNOME/nautilus/issues/91
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gvfs in Ubuntu.
https://bugs.launchpad.net/bugs/1723815
Title:
Unable to show files on MTP connection
Status in gvfs package in Ubuntu:
I tried to file a bug report here:
https://gitlab.gnome.org/GNOME/Infrastructure/issues/50
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager-applet in Ubuntu.
https://bugs.launchpad.net/bugs/1725532
Title:
wired network
This was fixed for a while by an update that came in, but now this
problem has come back.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1710754
Title:
[System Product Name, VIA
It could be related to this bug:
See Comment #62 https://bugzilla.gnome.org/show_bug.cgi?id=745079#c62
** Bug watch added: GNOME Bug Tracker #745079
https://bugzilla.gnome.org/show_bug.cgi?id=745079
--
You received this bug notification because you are a member of Desktop
Packages, which
Also, The Active Jobs window does not seem to ever update / refresh
itself.
I accidentally printed the same document two times. My printer wasn't
plugged in so I just went to the Active Jobs window and clicked the [X]
button to delete the "Pending" entry. It did nothing. I plugged in my
Oh! I should also note that I am running Ubuntu 17.10.
Printer is a Samsung C460.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1093129
Title:
system settings ->
Public bug reported:
My onboard Intel network adapter has [X] Connect automatically but when
I start my Gnome session, I always have to tell it to Connect which it
does without error.
You can't see it in the Gnome dialog windows but this connection is set
to also connect to a VPN. I setup this
I have attached a photo of my screen showing this behavior.
Notice how the icon is shown with correct orientation but the mouse
cursor has landscape orientation.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
Oops, I attached the wrong picture. This one is correct.
** Attachment added: "20171019_140503.jpg"
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1724977/+attachment/4976890/+files/20171019_140503.jpg
--
You received this bug notification because you are a member of Desktop
Packages,
I have attached a copy of a monitor.xml file I can use that will yield
this behavior.
** Attachment added: "monitors.xml"
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1724977/+attachment/4976873/+files/monitors.xml-order_and_rotation_correct
--
You received this bug notification
Public bug reported:
On Windows I use all three displays without issue, but I can only seem
to activate any 2 of my 3 displays in Ubuntu. The moment I activate the
3rd, the system freezes.
It may also be worth noting that due to this I have been disabling my
built-in laptop display and leaving
Public bug reported:
When my 2nd Asus (Ancor) display is in portrait mode and is set to be to
the left of my centered landscape display in extended mode, moving the
mouse to roughly the left 20% of my landscape display will show a mouse
cursor on my landcape display AND portrait display at the
Public bug reported:
Settings - Display - Primary Displayoffers me a choice of 3 displays.
Clicking on any of the non checked displays does nothing.
NOTE: My other 2 displays are currently disabled and likely shouldn't be
showing up in this list.
ProblemType: Bug
DistroRelease: Ubuntu 17.10
Public bug reported:
I am unable to drag the displays in the Display Arrangement section. I
have a dual monitor setup and they are in the reverse order.
ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: xorg 1:7.7+19ubuntu3
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname:
Public bug reported:
Gnome removed the ability to add/remove VLANs. When people ask /
complain about how this is to be accomplished, they are usually referred
to nm-connection-editor.
Can a Gnome developer please add an "Advanced Configuration" button that
launches nm-connection-editor?
Public bug reported:
I expected them to show up under Wired because the VLANs' associated
adapter is wired.
ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: network-manager-gnome 1.8.4-1ubuntu1
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
Public bug reported:
Sometimes when I open Settings - Network I see my VLANs, sometimes I
don't. I don't think changes made in nm-connection-editor are being
properly recognized by Gnome.
I use nm-connection-editor to add and configure VLANs.
ProblemType: Bug
DistroRelease: Ubuntu 17.10
Public bug reported:
This bug should actually be linked to ubuntu software, not gnome
software.
Search for "libre"
1. yacas
2. wormhole
.
.
.
I can't even find "libre" in the package name, nor the description of
the first few pages of results.
Way down on the list is "libreoffice" but even
Public bug reported:
Shotwell would not let my scroll down any further to select some photoss
on the bottom row.
ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: shotwell 0.26.3-1ubuntu1
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
Public bug reported:
Opening "Samsung_Android\Card\DCIM\Camera" folder with many images gets
stuck at "Loading..." and never shows anything. I have waited 10
minutes. There is no error and not a single icon shows.
ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: nautilus 1:3.26.0-0ubuntu1
Public bug reported:
Increase brightness key on my keyboard (func-f3) makes the screen more dim.
Decrease brightness key on my keyboard (func-f2) makes the screen more bright.
The gnome-shell on-screen display of brightness is backwards also.
I see on google search results that this was a
These seems to be related to what is in monitors.xml.
When I deleted that file the flickering was gone but my monitors were out of
order and alignment.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
Some updates must have come in, in the last few days that fixed this.
Close the bug.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1721160
Title:
[System Product Name, VIA
Public bug reported:
"Scan All Pages From Feeder" action scans the first page and feeds the
rest without scanning them.
ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: simple-scan 3.26.1-0ubuntu1
ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
Uname: Linux 4.13.0-12-generic x86_64
** Attachment added: "Screenshot from 2017-10-04 19-45-09.png"
https://bugs.launchpad.net/ubuntu/+source/network-manager-openvpn/+bug/1721430/+attachment/4962439/+files/Screenshot%20from%202017-10-04%2019-45-09.png
** Description changed:
- When I create a new connection using `sudo nmcli`
Public bug reported:
When I create a new connection using nmcli the entry is missing in
Network settings but exists in the popup. Also the name used to create
the connection is not displayed. (see screenshots attached)
The commands used to create the connection are basically:
** Attachment added: "Screenshot from 2017-10-03 17-18-29.png"
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1721160/+attachment/4961790/+files/Screenshot%20from%202017-10-03%2017-18-29.png
--
You received this bug notification because you are a member of Desktop
Packages, which
Public bug reported:
If I unplug the green plug to my speakers after my computer finishes
booting and then immediately plug it back in again, sound works
correctly.
Prior to the unplug / replug trick the Line-out is missing from Sound settings.
After the unplug / replug trick the Line-out is
** Attachment added: "Screenshot from 2017-10-03 17-18-43.png"
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1721160/+attachment/4961791/+files/Screenshot%20from%202017-10-03%2017-18-43.png
--
You received this bug notification because you are a member of Desktop
Packages, which
Public bug reported:
Using both my nvidia and radeon cards my 2560x1600 display flickers.
The screen is fine in Windows. This only seems to happen when I run the
open source driver.
Additionally, if I drop that screen to a lower 16:10 resolution like
1920x1200 it goes black.
ProblemType: Bug
Public bug reported:
When I start my computer I have no sound. If I unplug my line out and
plug it in again sound works fine. In Windows 10 this unplug and replug
is not required (the jack is fine).
Running:
$ amixer -c0 contents
so I can compare the non working state with the working state,
Public bug reported:
I get no sound on most boots. In Sound settings the default Output device is
HDMI / DisplayPort -
Built-in Audio and there is no option to select anything else. If I unplug my
line out and plug it in again it shows up in the list, automatically sets
itself as default
I just changed my video card to a Radeon RX 560 using the open source
driver and the same problem exists.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-session in Ubuntu.
https://bugs.launchpad.net/bugs/1709159
Title:
Mouse
I am getting similar behaviour on 17.10. If I unplug my line out and
plug it in again it works fine. In Windows 10 this unplug and replug is
not required (the jack is fine).
Running:
$ amixer -c0 contents
so I can compare the non working state with the working state, the following
Public bug reported:
I am running a Wayland session with Nouveau drivers on an NVIDIA GeForce GTS
450.
I have a dual monitor setup with my primary on the right.
My primary display is slightly higher than my secondary on the left as
configured in Displays.
When I play a video full screen on the
** Changed in: gnome-session (Ubuntu)
Assignee: ega (egagoodoodle) => (unassigned)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-session in Ubuntu.
https://bugs.launchpad.net/bugs/1582496
Title:
GLib-GObject-CRITICAL
I no longer have the affected hardware.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-video-nouveau in Ubuntu.
https://bugs.launchpad.net/bugs/1333417
Title:
[regression] [Dell Latitude E6520] [NVS 4200M] Hangs on
Public bug reported:
I'm installing 15.04 on a 2013 Macbook Pro, 13 retina.
It looks like each 'screen' in the process is displayed in a pane or
window, that you can drag around to relocate. One of the panes is
titled Install )as superuser) Preparing to Install Ubuntu' and the
checkmarks for
After reading this again, I don't think I'm accurately describing the
pane
I'm not referring to each screen during the install, but more.. the
frame or screen that the install screen is being drawn onto. the
window you can drag around with the mouse. maybe a better name would
be.. modal?
--
This is after I drag the screen to the upper left. Notice how the
underlying pane that the installation step is redrawn onto.. extends
past the bottom of the screen you normally see displayed? I suspect
the UEFI warning is being drawn below that, so if you don't drag it
up.. the UEFI screen
** Attachment added: 1
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1437482/+attachment/4358230/+files/IMG_20150327_155934.jpg
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
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
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
I just installed Inkscape on Mavericks on an iMac for the first time.
The Inkscape window opens and it is easy to expand the page to full
screen, but the apparent work page is a very small rectangle within a
much larger work space. Is one supposed to work within the tiny window
or ignore it, in
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
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
(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 appeared but
** Also affects: mesa (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1079011
Title:
stellarium assert failure: nv10_state_fb.c:50:
That message means invalid/unsupported buffer format (
http://sources.debian.net/src/mesa/10.3.2-1/src/mesa/drivers/dri/nouveau/nv10_state_fb.c
), and as it appears to refer to an internal nouveau buffer rather than
a passed-in texture, I suspect this is actually a mesa/nouveau bug.
As I do not
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
I am on Ubuntu 14.04
I have the same problem with a Samsung Galaxy S3 Mini on Android 4.1
but on a Galaxy Nexus with Android 4.3 I do not see the problem and can access
files directly.
Both phones are setup with MTP enabled in USB settings.
--
You received this bug notification because you are
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 Desktop
Packages, which is subscribed to
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
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
** 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 Desktop
Packages, which is subscribed to xserver-xorg-video-nouveau in Ubuntu.
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
Created attachment 96611
Xorg log 3.14rc-Mar-26
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-video-nouveau in Ubuntu.
https://bugs.launchpad.net/bugs/1243557
Title:
10de:1056 [Dell Latitude E6520] [NVS 4200M] X freeze,
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
Created attachment 96610
kernel log 3.14rc-Mar-26
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-video-nouveau in Ubuntu.
https://bugs.launchpad.net/bugs/1243557
Title:
10de:1056 [Dell Latitude E6520] [NVS 4200M] X
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 [
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 Desktop
Packages, which is subscribed to xserver-xorg-video-nouveau in Ubuntu.
https://bugs.launchpad.net/bugs/1243557
Title:
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 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
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
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
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
1 - 100 of 164 matches
Mail list logo
