Hi all,
The latest kernel tree
(https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git) has
the complete solution to fix this bug. So we can expect kernel v5.11 to
fix this issue without any additional work. Before the release of v5.11,
you are suggested to use #189 to save your
Hi @Helmut Stult (helmut-stult)
On Wed, Dec 16, 2020 at 6:32 PM Helmut Stult <1887...@bugs.launchpad.net>
wrote:
> The problem is your last patch
>
>
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/pinctrl
>
Hi Logan,
On Sun, Dec 6, 2020 at 12:05 PM Logan <1887...@bugs.launchpad.net> wrote:
> The output Coiby requested
> [root@lappy-the-laptop ~]# journalctl -k | grep -i amd_
> Dec 05 15:55:13 lappy-the-laptop kernel: amd_uncore: AMD NB counters detected
> Dec 05 15:55:13 lappy-the-laptop kernel:
Hi Mike,
On Sun, Dec 06, 2020 at 09:12:23PM -, Mike Boruta wrote:
>Hello Coiby,
>
>I built and installed the module as per the instructions in the branch
>you linked me to and `journalctl -k|grep amd_gpio` showed nothing. No
>new printouts in the kernel log. So I recompiled the module again
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: xserver-xorg-input-libinput (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-input-libinput in Ubuntu.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: xserver-xorg-video-intel (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-intel in Ubuntu.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: xorg (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1908728
Title:
This is not an issue with 12.04.
I have experienced this consistently in 16.04, 18.04 and 20.04
I have nvidia, so the common theme seems to be nvidia (however, may not even be
that).
I have tried in vain to find a fix for the last 4 years and have now
learned to live with it (save frequently,
In /var/crash there is only one relevant crash file and I tried ubuntu-bug
YOURFILE.crash but nothing happens, the command just hangs forever.
I've tried "https://errors.ubuntu.com/user/ID where ID is the content of file
/var/lib/whoopsie/whoopsie-id" but it just says "Sorry, you are not a
Public bug reported:
Usually after the screen lock has been engaged for some time this error
occurs. X will freeze and eventually crash.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
Uname: Linux
** Changed in: mesa (Ubuntu Groovy)
Status: New => In Progress
** Changed in: mesa (Ubuntu Focal)
Status: New => In Progress
--
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/1908699
@Helmut Stult (helmut-stult) I got it working both on Manjaro and Gentoo
with kernel 5.10.1 downloaded from kernel.org with #189. On Gentoo I had
to use Manjaro's running .config obtained with make localmodconfig while
in chroot from manjaro.
--
You received this bug notification because you are
The page is empty "no errors reported from this system"
But whoopsie-id:
b744c83b79ee4cccf7a0b4df8befd415349bf7a3c7812ca07ae97fffe4e2e1f6c3e6948c17804619bd89042abaa65cba74d7a2f997c74edb893fd356abf6abe7
https://errors.ubuntu.com/oops/c77eb797-4110-11eb-8995-fa163e6cac46
--
You received this bug
I found the ID in /var/crash/_usr_lib_xorg_Xorg.0.uploaded
ID: c77eb797-4110-11eb-8995-fa163e6cac46
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1908535
Title:
Xorg crash after clean
Public bug reported:
[Impact]
This is the last point-release of the 20.2.x-series, we should put it in
groovy so latest bugfixes would get there, and for focal because that
would minimize the risk of regressions when going from 20.0.x to 20.2.x.
[Test case]
Install the updates, test desktop
15 matches
Mail list logo
