Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v5.0 kernel [0].
If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.
If the mainline kernel does not fix t
I guess it's still related to the kernel:
[3.674022] [drm] {1680x1050, 1840x1080@119000Khz}
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-amdgpu in Ubuntu.
https://bugs.launchpad.net/bugs/1819383
Title:
VEGA 64 config
It sounds like the XFCE window manager has crashed, but I'm not sure. It
might be a good idea to follow these steps:
https://wiki.ubuntu.com/Bugs/Responses#Missing_a_crash_report_or_having_a_.crash_attachment
** Summary changed:
- Problem with windows
+ No border around windows, no resizing butt
Hmm...`cp` in xterm is a pretty clear indicator that this issue is
random and not triggered by a specific workload.
Lionel suggested that it would be good to have a feedback from the
kernel about what didn't pass validation.
There is a kernel option to generate debug traces for that but you have
(In reply to Mark Janes from comment #20)
> Yoshinori: Mesa i965 team is seeking a way to reproduce this bug, so we can
> analyze and fix it.
>
> How often does this occur in your product? If it is reproducible, then
> perhaps we can use an apitrace to investigate the root cause.
While I operate
This bug was fixed in the package xorg - 1:7.7+19ubuntu10
---
xorg (1:7.7+19ubuntu10) disco; urgency=medium
* control: Add mesa-vulkan-drivers to xserver-xorg Recommends. (LP:
#1742714)
-- Timo Aaltonen Wed, 13 Mar 2019 13:54:57 +0200
** Changed in: xorg (Ubuntu)
Sta
Public bug reported:
I am running intel core2duo cpu and ubuntu 18.10 is running fine. I installed
GRML , copied Ubuntu 19.04 iso to the grml folder in boot directory and then
updated grub. Restarted the computer and on booting the ISO no login screen
appeared. However,after pressing alt + ctrl
I just tagged a 1.1.1 release for libglvnd with the AARCH64 and PPC64LE fixes:
https://github.com/NVIDIA/libglvnd/releases/tag/v1.1.1
If you're switching from 1.0.0, note that the dispatch table order
changed between v1.0.0 and v1.1.0, so you'll need matching builds of
libGLdispatch.so, libOpenGL.
tested the ppa version (19.0 rc7) on AMD Ryzen / Vega Mobile now, works
fine (desktop, glxgears, vkcube)
--
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/1818516
Title:
FFe: Mesa 19.0.x for disco
Exactly. I did the "verification-done-bionic" step for 18.2.2 in comment
#12 above; and unfortunately I don't have an affected school nearby,
where I could test 18.2.8 in cosmic, and installing cosmic in a remote
school would be hard.
Thanks a lot Timo!
--
You received this bug notification beca
Hi, do you install vanilla/stock Ubuntu Xenial, or the preloaded OEM
Xenial?
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers in Ubuntu.
https://bugs.launchpad.net/bugs/1818816
Title:
Ubuntu 16.04 LTS + "lspci: Cannot op
The upstream release tracker probably helps showing that there's only
one identified bug on the list, which is triggered by Intel's CI. AMD
has something similar but not as comprehensive AIUI.
I've tested this on an Intel gen9 (coffee lake) gpu so far, AMD
Ryzen/Vega Mobile is soon done
--
You r
bionic was already fixed earlier by 18.2.2-0ubuntu1~18.04.2 in time for
18.04.2 release
cosmic got the exact same oneliner in 18.2.8-0ubuntu0~blah, and then
that was backported to bionic which reopened this bug. Requiring Alkis
to test this on cosmic is too much IMO, as it would involve first to s
** Description changed:
[Impact]
There are some new Intel GPU pci-id's that need to be added to several places:
0x3E98
0x87C0
and to make future additions easier, add platform definitions for
Whiskey Lake and Amber Lake too.
[Test case]
- Check that the user session uses the
This was already fixed in bionic by 18.2.2-0ubuntu1~18.04.1, now the
same is included upstream in 18.2.8 which was upload to cosmic too as
well as to bionic via a new backport.
Again, I don't have the hardware (AML, WHL is broken atm), adding pci-
id's just allow the X driver to load the DRI drive
Public bug reported:
No border around windows, no resizing buttons (max, min, close). Windows
cannot be moved or resized. Alt+tab and Alt+F4 have no effect, but some
other keyboard shortcuts, e.g. ctrl+alt+T and ctrl+Q, seem to work ok.
Only closing a window changes focus; even clicking with mouse
If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-cosmic to verification-done-cosmic.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed
What testing did you perform?
** Tags removed: verification-done verification-done-cosmic
** Tags added: verification-needed verification-needed-cosmic
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bu
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 mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1742714
Title:
moving back to the metapackage
** Package changed: xorg-server (Ubuntu) => xorg (Ubuntu)
--
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/1742714
Title:
MIR: mesa-vulkan-drivers FFE: install by d
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.
https://bugs.launchpad.net/bugs/1763
This bug was fixed in the package intel-vaapi-driver - 2.3.0-0ubuntu2
---
intel-vaapi-driver (2.3.0-0ubuntu2) disco; urgency=medium
* Restore debian/patches, disable all but an upstream commit to fix
loading on wayland. (LP: #1813131)
-- Timo Aaltonen Wed, 13 Mar 2019 09:25:
22 matches
Mail list logo
