** Changed in: chromium-browser (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to intel-vaapi-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1698287
Title:
VA-API fails to initialize in a Gnome
** Also affects: chromium-browser (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to intel-vaapi-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1698287
Title:
VA-API fails to initialize in
Daniel, you are saying comment #20 states that Mir's thread-per-monitor
rendering manifests the problem? (I don't have any nouveau based kit to
test on.)
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in Ubuntu.
Doug, and all:
https://bugs.launchpad.net/ubuntu/+source/mpv/+bug/1708102/comments/3
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to intel-vaapi-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1698287
Title:
VA-API fails to initialize in a
Well, yes. The problem description before that covers the fact that
Mir's multi-threaded compositor manifests the problem (assuming you have
multiple monitors). And comment #20 states that avoiding multiple
threads (a single headed or cloned config) avoids the instability.
--
You received this
I don't think the problem description is clear that both the Mir and
Unity8 compositors are affected. (It can be read as applying to the
stack including Unity8.) Thanks for clarifying.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in
Actually, the snapshotting/screencasting thread could also trigger it.
If that's still a thing...?
--
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/1553328
Title:
Mir/Unity8/USC crashes/freezes
Update:
* totem is fixed by the gst-plugins-bad fix released today.
* mpv is fixed by the patch proposed in bug 1708102.
* chromium needs to either be ported to native Wayland, or for libva to be
enhanced with DRI3 support. There are no workarounds for Chromium other than to
avoid Wayland and
** Changed in: hundredpapercuts
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to khronos-opencl-headers in Ubuntu.
https://bugs.launchpad.net/bugs/1619706
Title:
outdated opencl header cl2.hpp
To
** Changed in: nvidia-graphics-drivers-304 (Ubuntu)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers-304 in Ubuntu.
https://bugs.launchpad.net/bugs/1709317
Title:
Sorry Thomas, it was not my intention at all I'm new in xterm pkgs.
Thanks for point us this link.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xterm in Ubuntu.
https://bugs.launchpad.net/bugs/1629587
Title:
ESC ] 6;12;? ESC \ freezes
** 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/1709488
Title:
impossível fazer upgrade
To manage notifications about this bug go to:
Public bug reported:
Computer freezes without apparent cause.
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.10.0-30.34~16.04.1-generic 4.10.17
Uname: Linux 4.10.0-30-generic x86_64
.tmp.unity_support_test.0:
ApportVersion:
Public bug reported:
Cannot be changed
ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: xorg 1:7.7+16ubuntu3
ProcVersionSignature: Ubuntu 4.10.0-30.34-generic 4.10.17
Uname: Linux 4.10.0-30-generic i686
.tmp.unity_support_test.0:
ApportVersion: 2.20.4-0ubuntu4.5
Architecture: i386
** Attachment added: "E4E255DA9DA98CF3.jpg"
https://bugs.launchpad.net/bugs/127280/+attachment/4929681/+files/E4E255DA9DA98CF3.jpg
** Attachment added: "E4E255DA9DA98CF31.jpg"
https://bugs.launchpad.net/bugs/127280/+attachment/4929682/+files/E4E255DA9DA98CF31.jpg
** Attachment added:
Public bug reported:
When upgrading from ubuntu 17.04 to 17.10 (obviously new window manager)
... there is no longer the ability to configure the HiDPI scaling within
the window manager. This may be an intentional regression or simply
something that got passed by. But I find this configuration
** Tags added: upgrade-software-version
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to wayland in Ubuntu.
https://bugs.launchpad.net/bugs/1709628
Title:
New release wayland 1.14.0
To manage notifications about this bug go to:
The workaround here is to manually execute
```gsettings set org.gnome.desktop.interface scaling-factor 2```
and then restart the system to be into a scaled (2x) mode.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
Ubuntu's wayland package is synced from Debian. Therefore, you can file
a Debian bug if you want to see this updated sooner.
Is there any change in particular you were expecting in the new version?
** Changed in: wayland (Ubuntu)
Importance: Undecided => Wishlist
--
You received this bug
Update appreciated -- waiting for notification is not the same as an
ETA. We're hard-down for one of our environments waiting for a fix
here.
Thanks,
John
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libxfont in Ubuntu.
@John Arnold
There is a really simple workaround till this is fixed.
This worked for me and let me compile xorgxrdp. Not sure what your use
case is but...
step 1
*$ sudo touch /usr/include/X11/fonts/fontutil.h*
This file is owned by *root:root*, with mode *0o644*.
Then edit that file and put
@John Arnold
There is a really simple workaround till this is fixed.
This worked for me and let me compile xorgxrdp. Not sure what your use
case is but...
step 1
$ sudo touch /usr/include/X11/fonts/fontutil.h
This file is owned by root:root, with mode 0o644.
Then edit that file and put
Brian, thanks for the steps.
I tried adding the fontutil.h, but i still get ABI conflicts when using:
johnar@nettools1-co1:~$ sudo dpkg -l | grep -e libxfont -e xserver-xorg-dev
ii libxfont-dev 1:2.0.1-3~ubuntu16.04.1
amd64X11 font
Public bug reported:
Hello,
New Release:
https://lists.freedesktop.org/archives/wayland-devel/2017-August/034748.html
Regards,
--
Cristian
** Affects: wayland (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu-X,
24 matches
Mail list logo
