[Ubuntu-x-swat] [Bug 1794033]

2019-03-15 Thread Oss-linuxpf
I saw this problem three times from yesterday. All of them occurred during file sync over LAN with rsync. I think this problem might be related to load by disk i/o or network i/o. But unfortunately I have not re-compiled kernel with CONFIG_DRM_I915_DEBUG_GEM yet. I will try to it next week. -- Y

[Ubuntu-x-swat] [Bug 1811731] Re: compuer freeze

2019-03-15 Thread Launchpad Bug Tracker
[Expired for xorg-server (Ubuntu) because there has been no activity for 60 days.] ** Changed in: xorg-server (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launc

[Ubuntu-x-swat] [Bug 1820368] [NEW] x

2019-03-15 Thread Müller
Public bug reported: xx ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18 Uname: Linux 4.15.0-45-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CompizPlugins: No

Re: [Ubuntu-x-swat] [Bug 1803681] Re: osmesa doesn't suport core contexts but could

2019-03-15 Thread Greg
Fully patched 64-bit Ubuntu 18.04LTS Intel I7 AMD Radeon HD 7950 open-source drivers. Is this fixed in 18.10 or 19.04? And did you try the test program? And looking at https://packages.ubuntu.com/bionic/libs/libosmesa6, I don't see the dependency on llvm. -- Greg On Thu, Mar 14, 2019, 01:50

[Ubuntu-x-swat] [Bug 1742711] Re: MIR: vulkan-loader

2019-03-15 Thread Timo Aaltonen
** Description changed: [Availability] Has been in universe since March '16 [Rationale] - mesa-vulkan-drivers depends on libvulkan1, and once m-v-d is added to ubuntu-desktop Depends libvulkan1 will want to migrate. + mesa-vulkan-drivers depends on libvulkan1, and once m-v-d is added to

[Ubuntu-x-swat] [Bug 1742711] Re: MIR: vulkan-loader

2019-03-15 Thread Mathieu Trudel-Lapierre
Looks generally good to me, but this is a very large and complex project. I've tried to review the code as much as I could, but I would feel better if there were more eyes on it. Assigning to ~ubuntu-security ... I'm not requesting a full security code review, but leaving it to the Security Team to

[Ubuntu-x-swat] [Bug 1813701] Re: [amdgpu] Flickering graphics corruption (but none observed in kernels 4.18.10-4.18.12)

2019-03-15 Thread Caleb Brinkley
This also affects me on a fresh Arch Linux install with the RX 580 8GB GPU. I have found a temporary workaround to this issue until it is finally solved. I used Budgie Settings to enable the execution of this command each time it enters the environment: xrandr --output HDMI-A-0 --mode 1920x1080 -r

[Ubuntu-x-swat] [Bug 1820323] [NEW] xorg crash

2019-03-15 Thread Jill Manfield
Public bug reported: This is on Precision 3620, Precision 5820, Precision 7820 - systems with AMD bundled for OEM fail to properly boot after update/upgrade. I believe this is related to this issue: https://www.amd.com/en/support/kb/faq/amdgpupro-ubuntu-advisory Since our image contains the amd

[Ubuntu-x-swat] [Bug 1815759] Re: Does not recognize connected HDMI monitor

2019-03-15 Thread Timo Aaltonen
The actual driver is in the kernel, which in your case is ancient If 5.0 doesn't work, file a bug upstream and hope for the best ** Package changed: xserver-xorg-video-nouveau (Ubuntu) => linux (Ubuntu) ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug not

[Ubuntu-x-swat] [Bug 1820303] [NEW] Ubuntu 18.04 LTS

2019-03-15 Thread Christopher Wilson
Public bug reported: Failure to display prior desktop login GUI (Cinnamon). ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18 Uname: Linux 4.15.0-46-generic i686 .tmp.unity_support_test.0: ApportVersion: 2.20.9

[Ubuntu-x-swat] [Bug 1815236] Re: totem assert failure: totem: src/intel/genxml/gen9_pack.h:72: __gen_uint: La declaración `v <= max' no se cumple.

2019-03-15 Thread Launchpad Bug Tracker
This bug was fixed in the package mesa - 19.0.0-1ubuntu1 --- mesa (19.0.0-1ubuntu1) disco; urgency=medium * Merge from Debian. (LP: #1818516) * revert-set-full-thread-affinity.diff: Fix qemu crash. (LP: #1815889) -- Timo Aaltonen Thu, 14 Mar 2019 18:48:18 +0200 ** Changed in:

[Ubuntu-x-swat] [Bug 1815889] Re: qemu-system-x86_64 crashed with signal 31 in __pthread_setaffinity_new()

2019-03-15 Thread Launchpad Bug Tracker
This bug was fixed in the package mesa - 19.0.0-1ubuntu1 --- mesa (19.0.0-1ubuntu1) disco; urgency=medium * Merge from Debian. (LP: #1818516) * revert-set-full-thread-affinity.diff: Fix qemu crash. (LP: #1815889) -- Timo Aaltonen Thu, 14 Mar 2019 18:48:18 +0200 ** Changed in:

[Ubuntu-x-swat] [Bug 1818516] Re: FFe: Mesa 19.0.x for disco

2019-03-15 Thread Launchpad Bug Tracker
This bug was fixed in the package mesa - 19.0.0-1ubuntu1 --- mesa (19.0.0-1ubuntu1) disco; urgency=medium * Merge from Debian. (LP: #1818516) * revert-set-full-thread-affinity.diff: Fix qemu crash. (LP: #1815889) -- Timo Aaltonen Thu, 14 Mar 2019 18:48:18 +0200 ** Changed in: