One difference between artful and bionic is that bionic has libglvnd0
installed (and libegl1 depends on it, so I can't really remove it).
Artful doesn't have it installed. I read in one bug report (for Arch or
Fedora? I can't find it now) with similar symptoms (ie no wayland
session) that libglvnd
Yes definitely try blacklisting nouveau.
The GTX 1050 is relatively new. In my experience the GTX 1060 (slightly
older) only started working recently and the GTX 960 still doesn't work
with nouveau at last check.
Although when I say "working" I mean the machine boots without hanging
and doesn't f
I tried purging nvidia and bumblebee and reinstalling all the libs that
I could find related to GL, eGL, and mesa, but gdm3 still starts using
llvmpipe and the VMWare driver.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
And I only saw your feedback after I put my last comment in... :O
The lspci -k command run from artful shows this:
01:00.0 3D controller: NVIDIA Corporation GP107M [GeForce GTX 1050 Mobile] (rev
ff)
Kernel modules: nvidiafb, nouveau, nvidia_387_drm, nvidia_387
I've got all those blackli
P.P.S If you don't care for the Nvidia GPU and just want something that
works reliably, you might be able to disable the discrete GPU properly
in your BIOS. Just use integrated graphics. Then Linux will never see it
at all and there shouldn't be as much confusion.
** Summary changed:
- wayland se
Also, you might find 'lspci -k' reports nouveau is being loaded too. In
that case the fallback to software rendering (AKA LLVMpipe, AKA VMware)
is an expected problem for some newer Nvidia chipsets that nouveau can't
handle adequately.
P.S. Note that Gnome does not advertise hybrid graphics as sup
What made me suspect you used the nvidia installer was the terminology:
"manually reinstalled bumblebee and nvidia-387". My mistake, and moving
on...
Next, note that the "VMware driver" in use is actually LLVMpipe. This is
the Mesa software renderer that all systems can use, apparently written
by
You have been subscribed to a public bug:
I upgraded to 18.04 and I no longer get an option to run a wayland
session (17.10 offered both the default ubuntu wayland session and xorg
on this laptop).
gnome-shell runs under the llvmpipe driver. (Unity used to run when I
first upgraded, but now gnome
** Changed in: libinput (Debian)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libinput in Ubuntu.
https://bugs.launchpad.net/bugs/1715479
Title:
Touchpad won't stay disabled after resuming from suspe
For reference, I've found some other reports with the same basic issue -
Wayland crash with an error like this:
Oct 27 08:28:38 danielpc-arch org.gnome.Shell.desktop[7418]: (EE)
Oct 27 08:28:38 danielpc-arch org.gnome.Shell.desktop[7418]: Fatal server
error:
Oct 27 08:28:38 danielpc-a
This bug was fixed in the package libinput - 1.9.4-1
---
libinput (1.9.4-1) unstable; urgency=medium
* New upstream release.
* Add fix-lp1696929.patch to fix unresponsive/laggy touchpad behaviour
caused by inappropriate use of software hysteresis (LP: #1696929).
Thanks, Da
** Tags added: patch
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers-304 in Ubuntu.
https://bugs.launchpad.net/bugs/1737750
Title:
nvidia-graphics-drivers-304 304.137-0ubuntu2 ADT test failure with
linux 4.15.0-1.2
T
Confirm Kostas and Alessandro. Here is the output of `journalctl -e
/usr/bin/gnome-shell`
** Attachment added: "error.wayland"
https://bugs.launchpad.net/gnome-shell/+bug/1726224/+attachment/5022664/+files/error.wayland
--
You received this bug notification because you are a member of Ubuntu
Public bug reported:
My machine (XPS 13 9360) won't go into suspend properly after upgrading
from linux-image-4.13.0-17-generic to linux-image-4.13.0-19-generic.
This affects both suspend through lid close and "systemctl suspend".
Screen goes off, power led remains lit. Then after some time the s
Note that I've compile tested the attached fix but don't have hardware
to do run-time testing.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers-304 in Ubuntu.
https://bugs.launchpad.net/bugs/1737750
Title:
nvidia-graphic
** Changed in: nvidia-graphics-drivers-304 (Ubuntu)
Importance: Undecided => Medium
** Changed in: nvidia-graphics-drivers-304 (Ubuntu)
Status: New => In Progress
** Changed in: nvidia-graphics-drivers-304 (Ubuntu)
Assignee: (unassigned) => Seth Forshee (sforshee)
** Patch added:
After a clean reinstall, the boot is successful, though all program is
gone after clean install. If ubuntu has a repair function like windows
does, it'd be easier. Though it's fine for me now.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserv
17 matches
Mail list logo