After apply the patch it is working perfectly for wily and trusty.
Thanks.
** Tags removed: verification-done-trusty verification-needed-wily
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-ope
** Information type changed from Private Security to Public
--
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/1560322
Title:
I don't know why it is happening to me...!
To manage notifications abou
** Information type changed from Private Security to Public
--
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/1560168
Title:
Ubuntu-bug xorg
To manage notifications about this bug go to:
https://b
> I'm trying to add tag:verification-done-wily.
Well, this is a pretty useless page: "PerformingSRUVerification",
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification. The section
"Tagging the report" is especially useless.
--
You received this bug notification because you are a member of Ub
I'm trying to add tag:verification-done-wily.
The updated driver at http://launchpad.net/ubuntu/+source/xserver-xorg-
video-openchrome/1:0.3.3-1ubuntu1.1 was tested under Wily/15.10 it
tested OK. The driver was installed from wily-proposed.
The test rig for Wily/15.10 was a Qotom T26
(http://www.
Here's a related bug report that focuses purely on getting the updated
OpenChrome driver into Updates:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-
openchrome/+bug/1561275.
Once the 1561275 is closed, this should be closed, too.
--
You received this bug notification because you
The patch appears to be available in Ubuntu in the -proposed repository.
I tested the proposed patch from Debian upstream under Ubuntu, and the
machine tested OK.
The machine also tested OK with the manual patch as outlined by Kevin
Brace at http://lists.freedesktop.org/archives/openchrome-
users/
My bad... The proposed update is available; it was not called '0.3.4'.
The patch appears to be available in Ubuntu in the -proposed repository.
I tested the proposed patch from Debian upstream under Ubuntu, and the
machine tested OK.
The machine also tested OK with the manual patch as outlined by
Public bug reported:
I'm working on an i686 machine with a VIA C7-D processor and VIA PM400
graphics chipset. The machine runs Wily (15.10). The machine is
available at http://www.amazon.com/dp/B01AXR2KBQ.
Xserver crashes at boot because the downlevel driver does not handle the
PM400 chipset very
@francis-regan: I'm still getting issues with Chromium on 16.04, but I
don't see the same (fifo_underrun) error. So it's likely that it was
solved.
What I see now (only just checked the logs) are messages like:
Mar 23 08:27:11 hpmor kernel: [20182.144009] [drm] stuck on render ring
Mar 23 08:27:1
To the SRU team:
Due to lack of hardware to test it under Wily we can either ignore it (since it
EOLs in 3 moths anyway) or take under consideration the minimal impact and the
fact that it is available in Trusty and Xenial and release it.
It's your call, thank you.
--
You received this bug noti
same bug effect as this
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics/+bug/1096046?comments=all
--
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/1560981
Title:
Touchpad n
I'm closing this for now until I know more.
1.18.2 did not help with this, but instead I tried a daily build live
session and there the rendering was fine. So it looks like something
went wrong in the upgrade from trusty.
** Changed in: xserver-xorg-video-ati (Ubuntu)
Status: New => Invali
1.18.2 from the x-staging ppa works, thanks Timo!
** Changed in: linux (Ubuntu)
Status: Confirmed => Invalid
** Changed in: xorg-server (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-ser
Public bug reported:
the Laptop was restarted in between the upgrade, the update was manually
continued again after restarting
ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: xorg 1:7.7+7ubuntu4
ProcVersionSignature: Ubuntu 3.19.0-56.62~14.04.1-generic 3.19.8-ckt15
Uname: Linux 3.19.0-56-ge
facing the same issue after upgrade from 14.04 to 15.10
--
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/1096046
Title:
Touchpad not working after last apt-get upgrade
To
Public bug reported:
The following Shortcut-Keys does not work any more in ubuntu.
Description from "man xorg"
Ctrl+Alt+Keypad-Plus
Change video mode to next one specified in the configuration
file. This can be disabled with the DontZoom xorg.conf(5) file option.
Public bug reported:
Soon after new installation of ubuntu, comming from windows 10.
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: xorg 1:7.7+1ubuntu8.1
ProcVersionSignature: Ubuntu 3.13.0-83.127-generic 3.13.11-ckt35
Uname: Linux 3.13.0-83-generic i686
.tmp.unity.support.test.0:
Apport
Yes, I've upgraded the system to version 15.10 and installed all the
updates. glmark2 "ideas" benchmark now works but FooBillard++ still
triggers the lockup almost immediately. What really changed is that now
a reboot from another virtual console is no more needed. After the
lockup, the GPU restart
Michael Nelson: has 16.04 solved this issue?
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-intel in Ubuntu.
https://bugs.launchpad.net/bugs/1451632
Title:
drm:intel_cpu_fifo_underrun_irq_handler [i915] - complete lockups
20 matches
Mail list logo
