[Ubuntu-x-swat] [Bug 1873895] Re: Regression: block staircase display with side-by-side monitors of different pixel widths

2021-02-07 Thread Bill (franksmcb)
Some follow-up with users from the Ubuntu MATE Community forums show that this is occurring on Focal and Groovy; with 5.4, 5.8, and 5.10 kernels. Following is a list of hardware and graphics information from affected users: System: Host: huppyryzen Kernel: 5.4.0-54-generic x86_64 bits: 64 D

[Ubuntu-x-swat] [Bug 1875944] Re: Lenovo Ideapad 130-15AST 20.04 distorted and unusable

2020-05-08 Thread Bill (franksmcb)
*** This bug is a duplicate of bug 1873895 *** https://bugs.launchpad.net/bugs/1873895 ** This bug has been marked a duplicate of bug 1873895 Regression: block staircase display with side-by-side monitors of different pixel widths -- You received this bug notification because you are a m

[Ubuntu-x-swat] [Bug 1745345] Re: Xorg assert failure: Xorg: /usr/include/xorg/privates.h:122: dixGetPrivateAddr: Assertion `key->initialized' failed.

2020-03-14 Thread Bill (franksmcb)
Ubuntu MATE 20.04 2020315 QEMU: crash VirtualBox VBoxVGA crash VirtualBox VMSVGA: no crash In this case VirtualBox 6.1.4 (version shipping in 20.04) -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.n

[Ubuntu-x-swat] [Bug 1745345] Re: Xorg assert failure: Xorg: /usr/include/xorg/privates.h:122: dixGetPrivateAddr: Assertion `key->initialized' failed.

2020-03-05 Thread Bill (franksmcb)
This continues to be an issue with Virt-Manager/QEMU with the 20200306 ISO of Ubuntu MATE and the 20200305 ISO of Ubuntu Budgie. With VirtualBox 6.1.4 the following results occur: 1. Using VMSVGA there is no crash 2. Using VBoxSVGA the crash occurs. -- You received this bug notification because

[Ubuntu-x-swat] [Bug 1745345] Re: Xorg assert failure: Xorg: /usr/include/xorg/privates.h:122: dixGetPrivateAddr: Assertion `key->initialized' failed.

2020-02-16 Thread Bill (franksmcb)
This does occur with 20200216 ISO with Ubuntu MATE using Virt- manager/QEMU, however this issue does not occur using VirtualBox. -- 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/1745345 Title

[Ubuntu-x-swat] [Bug 1851162] Re: nvidia-drivers-390 fail to build with kernel 5.3

2020-01-31 Thread Bill (franksmcb)
@Alberto 390.116 There is more info on a duplicate bug but for brevity this is a T430 using NVIDIA GF108M [NVS 5400M] -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1851162

[Ubuntu-x-swat] [Bug 1851162] Re: nvidia-drivers-390 fail to build with kernel 5.3

2020-01-30 Thread Bill (franksmcb)
These are not working on 5.3.0-28 -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1851162 Title: nvidia-drivers-390 fail to build with kernel 5.3 To manage notifications a

[Ubuntu-x-swat] [Bug 1861191] Re: System hangs on graphical boot after kernel and nVidia upgrade

2020-01-28 Thread Bill (franksmcb)
nVidia driver 340.107 is available, however switching to that in Software & Updates has resulted in some issues. After Apply Changes, I am kicked to the Nouveau driver. And I get an ErrorBrokenCount > 0 Trying to resolve with sudo apt --fix-broken install as recommended by apt gives me: The fol

[Ubuntu-x-swat] [Bug 1861191] [NEW] System hangs on graphical boot after kernel and nVidia upgrade

2020-01-28 Thread Bill (franksmcb)
Public bug reported: System is Ubuntu MATE 18.04.3 T430 with nVidia On 27 Jan 2019 nvidia drivers were updated to 390.116 via apt upgrades with no issues. On 28 Jan 2919 kernel was updated to 5.3.0-28.30-18 via apt upgrades with no issues. System was rebooted today. Expected outcome: System re