After several weekends of testing, I believe I can report with high
confidence that the kernel update to 4.17-rc2 fixes the second of the
two problems; specifically, we no longer see kernel crashes after using
Alt-SysRq-k to recover from frozen/hanging blank screens.
However, the
*** This bug is a security vulnerability ***
Public security bug reported:
Hello, folks,
Today when I returned to my computer (which I locked with Super+L) and
attempted to unlock it, it displayed my passphrase in cleartext in the
'Password' box. I noticed as soon as I got the first character
*** This bug is a duplicate of bug 1758651 ***
https://bugs.launchpad.net/bugs/1758651
Thank you for taking the time to report this crash and helping to make
this software better. This particular crash has already been reported
and is a duplicate of bug #1758651, so is being marked as such.
*** This bug is a duplicate of bug 1758651 ***
https://bugs.launchpad.net/bugs/1758651
Public bug reported:
I did not really notice a crash, but I think I had to press Escape twice
to get the form where I can enter my password to unlock the screen. It
might be totally unrelated though.
** Changed in: libinput
Status: Unknown => Won't Fix
** Changed in: libinput
Importance: Unknown => Medium
--
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/1772083
Title:
eGalax
I would have done that already, but have not verified if the problem
really is in mesa-va-drivers.
It's hard to tell when mpv doesn't work either (for different reasons).
So we haven't yet excluded the possibility that the bug is in
gstreamer1.0-vaapi.
--
You received this bug notification
*** This bug is a duplicate of bug 1727356 ***
https://bugs.launchpad.net/bugs/1727356
Thank you for taking the time to review this.
Everything worked fine until I upgraded from 17.10 to 18.
I will try this fix and if it doesn't work I will attempt to reinstal
17.10 and not upgrade
It looks like this bug has been previously reported on the libinput
database as bug 102632 and they marked it WONTFIX. This touchscreen
worked fine with Ubuntu 16.04 (which used evdev), so I am trying to
figure out how that worked.
--
You received this bug notification because you are a member
*** This bug is a duplicate of bug 1727356 ***
https://bugs.launchpad.net/bugs/1727356
** This bug has been marked a duplicate of bug 1727356
Wayland sessions (including the login screen itself) don't start up on older
Intel GPUs.
--
You received this bug notification because you are a
** Tags removed: need-duplicate-check
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libdrm in Ubuntu.
https://bugs.launchpad.net/bugs/1772643
Title:
package libdrm-intel1 2.4.83-1~16.04.1 failed to install/upgrade:
trying to overwrite
Public bug reported:
I cannot update becuase of some problem with tird party programs, howeve
I deleted all of them an it is still occurring. It also appears a new
user called LibvirtQuemu.
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: libdrm-intel1 2.4.83-1~16.04.1
Public bug reported:
Hi,
I asked a question here
https://answers.launchpad.net/ubuntu/+source/xinput/+question/668859 but
no one seems to answer... So I try here
I can't make multitouch work with my yoga 720 convertible. At least not
as expected. The touchscreen work, some gestures work but
Public bug reported:
[Impact]
*** hwe-16.04 refresh for 16.04.4 ***
A minor update, only xserver sync, some driver updates plus a newer
Mesa.
Mesa needs llvm-toolchain-6.0 and libclc, libdrm, updates.
[Test case]
upgrade from/to stock & old hwe stack, test desktop usage
[Regression
Thanks for the answer!
When and why it was dropped, while drivers still have GLES1 calls inside
binary? Mesa's libGL.so still does have them.
Proprietary drivers also don't drop GLES1 support, GLES1 functionality
persists in latest NVidia driver.
--
You received this bug notification because
I had working proprietary drivers for my GTX 1080 Ti and then I upgraded
from 17.10 to 18.04. Everything worked well, gdm login screen appears,
but AFTER entering username and password and hitting ENTER, I only get a
black screen.
For me #123 solved the problem, thanks for the detailed
you should file it upstream at
https://bugs.freedesktop.org/enter_bug.cgi?product=Mesa
drivers/gallium/radeonsi
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1767312
Title:
[radeon] Totem
I'm not using oibaf.
I used to use it, but uninstalled it with ppa-purge, but this problem is
present regardless of oibaf is installed.
** Changed in: mesa (Ubuntu)
Status: Invalid => New
** Changed in: xorg-server (Ubuntu)
Status: Invalid => New
--
You received this bug
Public bug reported:
[Impact]
Ubuntu 18.04 shipped with mesa 18.0.0~rc5, and deserves to get the last point
release of the series.
[Test Case]
Check on intel/radeon hw that things still work fine.
** Affects: mesa (Ubuntu)
Importance: Undecided
Status: Invalid
** Affects: mesa
was a qt bug
** Changed in: mesa (Ubuntu Bionic)
Status: New => Invalid
** Changed in: mesa (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1749472
GLESv1 support was dropped quite some time ago.
** Changed in: mesa (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1749766
Title:
No libGLESv1_CM.so
you are using the oibaf ppa
** Changed in: xorg-server (Ubuntu)
Status: New => Invalid
** Changed in: mesa (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in Ubuntu.
Public bug reported:
xserver-xorg-video-all has not depended on these drivers for quite some
time now, meaning that installation images didn't have them either nor
installed them on the system. Now would be the time to drop them from
the archive well before next LTS and in preparation for xserver
22 matches
Mail list logo
