package up for testing at ppa:tjaalton/test
** Changed in: mesa (Ubuntu Yakkety)
Assignee: (unassigned) => Timo Aaltonen (tjaalton)
--
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
This is actually a kernel bug where the PWM isn't saved. It affects the
specific display type in this machine. It's been fixed upstream
already, and was brought into Ubuntu 16.04 (See SRU
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1625932).
The Precision 5510 however ships with Ubuntu
*** This bug is a duplicate of bug 1646537 ***
https://bugs.launchpad.net/bugs/1646537
** This bug has been marked a duplicate of bug 1646537
Backlight sometimes fails to resume from suspend & screen brightness
sometimes will not dim below 100%
--
You received this bug notification
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/1646537
Title:
Well… Switching to another window manager doesn't solve the “any 3D/GLX
app would crash” issue…
In my case I would have preferred to use the nouveau driver from the
beginning, except that for ancient cards like the 6150SE it makes the
whole system freeze after only a few minutes…
Finally, I was
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Unfortunately, we cannot work on this bug because your
description didn't include enough information. You may find it helpful
to read "How to report bugs effectively"
** Attachment added: "warzone2100.gdmp-YvHauJ"
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1646937/+attachment/4786706/+files/warzone2100.gdmp-YvHauJ
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
Public bug reported:
Running `optirun warzone2100` I get
> optirun warzone2100
info|08:03:22: [realmain:1145] Using
/home/richter/.warzone2100-3.1/logs/WZlog-1202_200322.txt debug file
libpng warning: iCCP: known incorrect sRGB profile
Cannot connect to server socket err =
Same problem, 16.10, Kodi 17.0-beta6
--
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/1636573
Title:
xinit flooding syslog
To manage notifications about this bug go to:
Same here: Ubuntu 16.10, latest kodi
--
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/1636573
Title:
xinit flooding syslog
To manage notifications about this bug go to:
Public bug reported:
its even ok if some who can fix the bugs share the screen
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-51.72-generic 4.4.30
Uname: Linux 4.4.0-51-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture:
To all those who could hardly await a fix: Since it is closed source
driver, this issue has to be resolved upstream. So far, Nvidia has not
provided an update, although (according to Aaron Plattner) they are
working on it [1]. Just downgrading isn't always preferable, either.
Last update was
As stated by jokrebel in comment #4, a possible temporary workaround
could be to use Gnome (Metacity) desktop session.
1) Press Ctrl + Alt + F1 and login with username and password
2) sudo apt install gnome-session-flashback
3) sudo service lightdm restart
4) Select Gnome (metacity) session and
It also affects to my computer. (Ubuntu 16.04. Then I updated to 16.10
and still the same bug, so now I'm using the open drivers).
I don't understand why this critical bug which makes your computer
useless is not solved yet.
You should realize that maybe thousands of computers can't log in
For me the problem disappeared since I upgraded to the mainline kernel
4.8.9-040809-generic (my random pick) from here
http://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D
as suggested by PeterPall above. Ubuntu runs like a charm, I only had to
update my VirtulBox to the 5.1 series.
--
You
zesty is still in limbo, gtk tests fail because of glibc or whatever,
mesa is not to blame
** Description changed:
- Mesa 12.0.4 is now available as a point release in the stable branch.
+ [Impact]
+ Mesa 12.0.4 is now available as a point release in the stable branch. Mesa
has MRE for these.
try 16.10
** Also affects: mesa (Ubuntu)
Importance: Undecided
Status: New
** Changed in: mesa (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in Ubuntu.
*** This bug is a duplicate of bug 1610591 ***
https://bugs.launchpad.net/bugs/1610591
doesn't need a new bug for it
--
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/1646140
Title:
Radeon
I have the same problem on a DELL XPS-13. Only started recently after an
update to 16.04 but I'm not sure which kernel was the cause. Doesn't
seem to happen every time but is very annoying when it does.
uname -r: 4.4.0-47-generic
lspci -nn:
00:00.0 Host bridge [0600]: Intel Corporation
Also affects VM (qemu/kvm) lp:1646532
--
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/1639745
Title:
Mir GL clients never appear at all on VirtualBox
To manage notifications about this bug go
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Unfortunately, we cannot work on this bug because your
description didn't include enough information. You may find it helpful
to read "How to report bugs effectively"
21 matches
Mail list logo
