[Expired for xorg-server (Ubuntu) because there has been no activity for
60 days.]
** Changed in: xorg-server (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
*** This bug is a duplicate of bug 1683383 ***
https://bugs.launchpad.net/bugs/1683383
! SOLUTION !
For myself I created temporary hack allowing to switch Keyboard layouts
(en<->ru) by Ctrl+Shift on key release. My method does not interfere
with other shortcuts. I use it myself on daily
Fixed by bug #1740894, confirmed in Cosmic and Disco
** Changed in: xkeyboard-config (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xkeyboard-config in Ubuntu.
Fixed by changed in bug #1740894
** Changed in: xkeyboard-config (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xkeyboard-config in Ubuntu.
https://bugs.launchpad.net/bugs/1800727
Title:
I can confirm that xkb-data 2.23.1-1ubuntu1.18.10.1 fixes this issue for
me on cosmic
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xkeyboard-config in Ubuntu.
https://bugs.launchpad.net/bugs/1740894
Title:
KEY_RFKILL is not passed to
Hello Timo, or anyone else affected,
Accepted libx11 into bionic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/libx11/2:1.6.4-3ubuntu0.2 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
Hello Timo, or anyone else affected,
Accepted mesa into bionic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/mesa/18.2.8-0ubuntu0~18.04.2 in a
few hours, and then in the -proposed repository.
Please help us by testing this new package. See
Hello Timo, or anyone else affected,
Accepted mesa into bionic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/mesa/18.2.8-0ubuntu0~18.04.2 in a
few hours, and then in the -proposed repository.
Please help us by testing this new package. See
Hello Alkis, or anyone else affected,
Accepted mesa into bionic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/mesa/18.2.8-0ubuntu0~18.04.2 in a
few hours, and then in the -proposed repository.
Please help us by testing this new package. See
** Changed in: mesa
Status: Confirmed => Fix Released
--
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/1815172
Title:
Black screen on skylake after 18.0 => 18.2 update
To manage
< I tried with 4.20.7 and it appears to work fine! Thanks!
You are welcome :)
So closing?
--
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/1815172
Title:
Black screen on skylake after 18.0 =>
Most likely mesa were broken with commit:
commit a363bb2cd0e2a141f2c60be005009703bffcbe4e
Author: Kenneth Graunke
Date: Tue Apr 10 01:18:25 2018 -0700
i965: Allocate VMA in userspace for full-PPGTT systems.
In the kernel (especially 32-bit) it requires such commits (all of them are
4.15 is EOL upstream, but Canonical does pull patches from stable to the
distro kernel in 18.04, I'm not sure why these never got in.. probably
didn't apply cleanly.
anyway, I'll make sure they get applied eventually, but for now will
disable softpin from mesa so that 32bit 18.04.2 image will
I don't know the software stacks involved:
If I understood it correctly,
mesa 18.3.3 doesn't work with older kernels while 18.0 did work,
and so I'll do a bisection to see which kernel commit fixes the issue,
and then distro kernel maintainers may cherrypick it for older kernels.
If there's no
FWIW, I am not able to reproduce this issue on Arch Linux with Mesa
18.3.3 and kernel 4.18.16.
--
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/1815172
Title:
Black screen on skylake after 18.0
Most likely mesa were broken with commit:
commit a363bb2cd0e2a141f2c60be005009703bffcbe4e
Author: Kenneth Graunke
Date: Tue Apr 10 01:18:25 2018 -0700
i965: Allocate VMA in userspace for full-PPGTT systems.
In the kernel (especially 32-bit) it requires such commits (all of them are
I tried a small kernel bisection using the ubuntu kernel binaries,
4.19.2-041902=fails,
4.19.3-041903=works
--
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/1815172
Title:
Black screen on skylake
Hello, Alkis.
Could you, please, try to use a kernel not less than v4.19.3?
And could you provide outputs of
/usr/bin/glxinfo -B
file /usr/bin/glxinfo
uname -a
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in Ubuntu.
Hello Sergii,
I tried with 4.20.7 and it appears to work fine! Thanks!
Output of the commands:
# uname -a
Linux srv-6gym-chalk 4.20.7-042007-generic #201902061234 SMP Wed Feb 6 17:49:39
UTC 2019 i686 i686 i686 GNU/Linux
# file /usr/bin/glxinfo
/usr/bin/glxinfo: ELF 32-bit LSB shared object,
one theory is that this is related to legacy bios boot
--
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/1815172
Title:
Black screen on skylake after 18.0 => 18.2 update
To manage notifications
I just tried with 4.18.0-14-generic, the same issue happens there as
well.
And, another school reported the issue on HD Graphics 630:
root@pc02:~# lspci -nn -k | grep -A 2 VGA 00:02.0 VGA compatible
controller [0300]: Intel Corporation HD Graphics 630 [8086:5912] (rev
04) Subsystem:
21 matches
Mail list logo
