Working fine here on skylake-y.
** Tags removed: verification-needed
** Tags added: verification-done
--
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/1506107
Title:
Bad
** Package changed: unity-control-center (Ubuntu) => xserver-xorg-video-
intel (Ubuntu)
--
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/1530171
Title:
[Regression] Thinkpad
You have been subscribed to a public bug:
On Thinkpad L540 with intel graphics:
External monitors are not recognized in display settings when plugged
into any dock port.
They *are* recognized after a reboot (not after logout).
After plugging out and the in again they are not recognized.
A
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: xorg-server (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
Public bug reported:
mobile intel 945GM chipset family
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: xorg 1:7.6+12ubuntu2
ProcVersionSignature: Ubuntu 3.13.0-74.118~precise1-generic 3.13.11-ckt30
Uname: Linux 3.13.0-74-generic i686
.tmp.unity.support.test.0:
ApportVersion:
*** This bug is a duplicate of bug 1522727 ***
https://bugs.launchpad.net/bugs/1522727
** Attachment added: "xorg-log"
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1528011/+attachment/4544428/+files/xorg-log
--
You received this bug notification because you
The native gallium vdpau and vaapi drivers accelerate video decode
directly using UVD. Shaders are only used for codecs that were not
directly supported by older UVD hardware. There is no need to use any
sort of vdpau <-> vaapi translation layers; just use the native backend
for whichever API
See bug #1441631 . It is required whenever you do HW decoding with
"nouveau" driver (no matter the top level API i.e. vdpau, VA-APi, OMX
...)
(Any other solutions will necessarily uses the proprietary NVIDIA
driver)
--
You received this bug notification because you are a member of Ubuntu-X,
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug. I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross
For the full /boot see a guide like http://askubuntu.com/questions/89710
/how-do-i-free-up-more-space-in-boot for some advice. It'll require a
bit of manual work but isn't terrible..
Thanks
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg
I think this is not related to the Intel graphics driver (I'm having the
same problem with a nvidia video card).
Workarounds that worked for me:
1. Turn off antialiasing (fonts will be extremely ugly)
OR
2. Add this to eclipse.ini:
--launcher.GTK_version
2
So it looks like a GTK3 problems.
--
[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.
Public bug reported:
I tried reporting this to Totem[1], but they assured me this is an issue
with X.
I've tried playing both mkv and avi files in Totem in a almost totally
newly installed Ubuntu Gnome 15.10 64 bit, updated to Gnome 3.18 with
the Gnome Staging PPA.
Every time I play the files
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug. I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross
*** This bug is a duplicate of bug 1493888 ***
https://bugs.launchpad.net/bugs/1493888
** This bug is no longer a duplicate of bug 1512307
fglrx and fglrx-updates install crashes system: no screen access possible
** This bug has been marked a duplicate of bug 1493888
FGLRX incompatible
*** This bug is a duplicate of bug 1493888 ***
https://bugs.launchpad.net/bugs/1493888
Done.
"
Then:
- If this bug is gone, please mark it as a duplicate of bug #1493888.
- If not, set this report status back to "confirmed".
"
--
You received this bug notification because you are a member
*** This bug is a duplicate of bug 1493888 ***
https://bugs.launchpad.net/bugs/1493888
So, it worked on both A-10 and E-450.
This issue seems to be solved.
Thanks for the work!
** This bug has been marked a duplicate of bug 1493888
FGLRX incompatible with gcc 5
--
You received this bug
*** Bug 93595 has been marked as a duplicate of this bug. ***
--
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/1041790
Title:
[snb] GPU lockup IPEHR: 0x0b160001 IPEHR:
Don't have the full dkms log any more, but this is from apt.
Setting up nvidia-304 (304.131-0ubuntu2) ...^M
update-alternatives: using /usr/lib/nvidia-304/ld.so.conf to provide
/etc/ld.so.conf.d/x86_64-linux-gnu_GL.conf (x86_64-linux-gnu_gl_conf) in auto
mode^M
update-alternatives: using
Public bug reported:
I just installed "nvidia-current", which was probably an error (I'm now using
-352) but nevertheless it couldn't be loaded into my 4.3 kernel, on xenial.
Jan 05 12:10:54 raleigh.local kernel: mtrr: no MTRR for f100,e0 found
Jan 05 12:10:55 raleigh.local kernel:
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug. I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug. I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross
22 matches
Mail list logo
