Hmm it seems this bug refuses to expire.
Can't be reproduced any more and only happens using a rendering approach
we have never used.
** No longer affects: mesa
** Changed in: mir
Status: Incomplete => New
** Changed in: mir
Status: New => Incomplete
** Changed in: mir
[Expired for xorg (Ubuntu) because there has been no activity for 60
days.]
** Changed in: xorg (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
The tricky thing is that it is not a system crash, the computer keeps
running fine. Just the screen goes blank and it is pretty much
impossible to do anything after that. I hope that there is some kind of
error message produced when it happens, now if i could only find it.
--
You received this
James Funk, in order to debug your issue please provide a log
uncompressed/untarred following
https://wiki.ubuntu.com/DebuggingSystemCrash .
** Tags added: zesty
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-amdgpu in
No luck with the daily live-cd, some of the kernel messages fly by and
when it tries to change graphics modes for the first time, black screen.
With 16.04 it would sometimes get to the desktop and then would go to
black screen.
I also found this bug report describing the same exact problem:
Sorry I mis read the report.
I am getting the login loop with nvidea 304 not 340
--
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/1637652
Title:
stucked in a login loop
To manage notifications
I am also getting the login loop with nvidia-304.134
--
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/1637652
Title:
stucked in a login loop
To manage notifications about this bug go to:
I had several installations on the same computer now (for other reasons) and
ALWAYS the correct resolution was found (without changing anything with the
cables). To my view it cannot be the cable.
Why is the resolution then never changed back to UHD even after restart/power
on/off ?
Additional
Xenial added as a target, we will be providing unrenamed backports from
now on.
** Description changed:
[Impact]
Mesa 12.0.5 is now available as a point release in the stable branch. Mesa
has MRE for these.
The release contains multiple fixes amongst which:
The nouveau vdpau driver
** Description changed:
[Impact]
We need a few packages backported to xenial for lts-hwe X stack.
[Test case]
libdrm, mesa: run a desktop session, see that things still work
[Regression potential]
libdrm:
slim to none, changes from 2.4.67..2.4.70:
- amdgpu: spelling
** Also affects: mesa (Ubuntu Xenial)
Importance: Undecided
Status: New
--
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/1641017
Title:
Mesa 12.0.5 - multiple important fixes, stable
This change was made by a bot.
** Changed in: linux (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-input-synaptics in Ubuntu.
https://bugs.launchpad.net/bugs/1641451
Title:
ALPS Touchpad
dropped libclc, yakkety shipped with the same version
** Changed in: libclc (Ubuntu Xenial)
Status: Incomplete => Won't Fix
** Also affects: mesa (Ubuntu)
Importance: Undecided
Status: New
** Changed in: mesa (Ubuntu)
Status: New => Invalid
** Description changed:
13 matches
Mail list logo
