[Ubuntu-x-swat] [Bug 2085340] Re: Plenty of amdgpu backtraces post resume
I enabled that debug option thingy. I'll try to have a go at a mainline kernel build at some point. Now the problem is I can't reproduce this so far. gnome-shell/xwayland randomly exits at some point without any explanation (you can see it just starts broken pipe at 12:31:54, no crash before, I need to find the cause for that and report another bug :(), and then it *might* trigger a suspend when switching to the gdm session. But like not every logout (forced or manual) triggers that. I think the hard part is that it suspends while it's VT switching to gdm. -- 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/2085340 Title: Plenty of amdgpu backtraces post resume To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2085340/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 2085340] Re: Plenty of amdgpu backtraces post resume
Attaching the Journal, the initial crash can be seen at 12:31:54, lots going on there, but nothing root-causing this. ** Attachment added: "Journal.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2085340/+attachment/5830742/+files/Journal.txt -- 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/2085340 Title: Plenty of amdgpu backtraces post resume To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2085340/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 2085340] [NEW] Plenty of amdgpu backtraces post resume
Public bug reported: This is a very weird case: The GNOME session crashed 3 times today, the last time, it went to gdm, but then gdm did not recognize it was docked and suspended. I think the kernel needed two attempts to resume, it got suspended again after the first one; and it produced a whole bunch of back traces in dmesg. [ 3300.659129] WARNING: CPU: 1 PID: 65823 at drivers/gpu/drm/amd/amdgpu/../display/dc/gpio/gpio_service.c:315 dal_gpio_service_open+0x1b6/0x270 [amdgpu] [ 3410.146130] WARNING: CPU: 4 PID: 73742 at drivers/gpu/drm/amd/amdgpu/../display/dc/dce/dmub_psr.c:221 dmub_psr_enable+0x102/0x110 [amdgpu] ProblemType: Bug DistroRelease: Ubuntu 24.10 Package: linux-image-6.11.0-9-generic 6.11.0-9.9 ProcVersionSignature: Ubuntu 6.11.0-9.9-generic 6.11.0 Uname: Linux 6.11.0-9-generic x86_64 ApportVersion: 2.30.0-0ubuntu4 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: GNOME Date: Tue Oct 22 12:45:20 2024 InstallationDate: Installed on 2022-11-26 (696 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20221126) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: LENOVO 21CF004PGE ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.11.0-9-generic root=/dev/mapper/ubuntu-root ro rootflags=subvol=@next quiet splash crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M zswap.enabled=1 zswap.compressor=zstd zswap.max_pool_percent=20 zswap.zpool=zsmalloc vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-6.11.0-9-generic N/A linux-backports-modules-6.11.0-9-generic N/A linux-firmware20240913.gita34e7a5f-0ubuntu2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/29/2024 dmi.bios.release: 1.53 dmi.bios.vendor: LENOVO dmi.bios.version: R23ET77W (1.53 ) dmi.board.asset.tag: Not Available dmi.board.name: 21CF004PGE dmi.board.vendor: LENOVO dmi.board.version: SDK0T76538 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.32 dmi.modalias: dmi:bvnLENOVO:bvrR23ET77W(1.53):bd05/29/2024:br1.53:efr1.32:svnLENOVO:pn21CF004PGE:pvrThinkPadT14Gen3:rvnLENOVO:rn21CF004PGE:rvrSDK0T76538WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21CF_BU_Think_FM_ThinkPadT14Gen3: dmi.product.family: ThinkPad T14 Gen 3 dmi.product.name: 21CF004PGE dmi.product.sku: LENOVO_MT_21CF_BU_Think_FM_ThinkPad T14 Gen 3 dmi.product.version: ThinkPad T14 Gen 3 dmi.sys.vendor: LENOVO ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Affects: mesa (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug oracular third-party-packages wayland-session ** Also affects: mesa (Ubuntu) Importance: Undecided Status: New ** Description changed: This is a very weird case: The GNOME session crashed 3 times today, the last time, it went to gdm, but then gdm did not recognize it was docked and suspended. I think the kernel needed two attempts to resume, it got suspended again after the first one; and it produced a whole bunch of back traces in dmesg. + + + [ 3300.659129] WARNING: CPU: 1 PID: 65823 at drivers/gpu/drm/amd/amdgpu/../display/dc/gpio/gpio_service.c:315 dal_gpio_service_open+0x1b6/0x270 [amdgpu] + [ 3410.146130] WARNING: CPU: 4 PID: 73742 at drivers/gpu/drm/amd/amdgpu/../display/dc/dce/dmub_psr.c:221 dmub_psr_enable+0x102/0x110 [amdgpu] ProblemType: Bug DistroRelease: Ubuntu 24.10 Package: linux-image-6.11.0-9-generic 6.11.0-9.9 ProcVersionSignature: Ubuntu 6.11.0-9.9-generic 6.11.0 Uname: Linux 6.11.0-9-generic x86_64 ApportVersion: 2.30.0-0ubuntu4 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: GNOME Date: Tue Oct 22 12:45:20 2024 InstallationDate: Installed on 2022-11-26 (696 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20221126) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: LENOVO 21CF004PGE ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.11.0-9-generic root=/dev/mapper/ubuntu-root ro rootflags=subvol=@next quiet splash crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M zswap.enabled=1 zswap.compressor=zstd zswap.max_pool_percent=20 zswap.zpool=zsmalloc vt.handoff=7 RelatedPackageVersions: - linux-restricted-modules-6.11.0-9-generic N/A - linux-backports-modules-6.11.0-9-generic N/A - linux-firmware20240913.gita34e7a5f-0ubuntu2 + linux-restricted-modules-6.11.0-9-generic N/A + linux-backports-modules-6.11.0-9-generic N/A + linux-firmware20240913.gita34e7a5f-0ubuntu2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/29/2024 dmi.bios.release: 1.53 dmi.bios.vendor: LENOVO dmi.bios.version: R23ET77W (1.
[Ubuntu-x-swat] [Bug 2083538] Re: amdgpu: [mmhub] page fault (src_id:0 ring:8 vmid:6 pasid:32781 / Fence fallback timer expired on ring sdma0
Happy to sponsor. We need to fill out the SRU template, and need to add some test plan there as per: https://canonical-sru-docs.readthedocs-hosted.com/en/latest/howto/standard/ https://canonical-sru-docs.readthedocs-hosted.com/en/latest/reference/bug-template/#reference-sru-bug-template -- 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/2083538 Title: amdgpu: [mmhub] page fault (src_id:0 ring:8 vmid:6 pasid:32781 / Fence fallback timer expired on ring sdma0 To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/2083538/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 2083538] Re: amdgpu: [mmhub] page fault (src_id:0 ring:8 vmid:6 pasid:32781 / Fence fallback timer expired on ring sdma0
One thing I wonder, the crash is one thing; but the inability of the kernel/firmware to recover from that is another. As in, new mesa fixing that particular crash is ok, but optimally you'd also be able to recover from the crash with the old mesa; but the GPU restarts are failing and the driver apparently deadlocks or something (quite a bunch of mutex backtraces). -- 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/2083538 Title: amdgpu: [mmhub] page fault (src_id:0 ring:8 vmid:6 pasid:32781 / Fence fallback timer expired on ring sdma0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/2083538/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 2083538] Re: amdgpu: [mmhub] page fault (src_id:0 ring:8 vmid:6 pasid:32781 / Fence fallback timer expired on ring sdma0
** Also affects: firefox (Ubuntu) Importance: Undecided Status: New -- 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/2083538 Title: amdgpu: [mmhub] page fault (src_id:0 ring:8 vmid:6 pasid:32781 / Fence fallback timer expired on ring sdma0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/2083538/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 2083568] Re: full system freezes and needs to be hard rebooted
** Package changed: ubuntu-release-upgrader (Ubuntu) => mesa (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/2083568 Title: full system freezes and needs to be hard rebooted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2083568/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 2083538] Re: amdgpu: [mmhub] page fault (src_id:0 ring:8 vmid:6 pasid:32781 / Fence fallback timer expired on ring sdma0
To the best of my knowledge the issue started happening when the kernel was upgraded. That being said, the Firefox process that seemingly causes stalls is a snap so it is using its own mesa and not the host one, and I can't speak to the snap's mesa version. -- 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/2083538 Title: amdgpu: [mmhub] page fault (src_id:0 ring:8 vmid:6 pasid:32781 / Fence fallback timer expired on ring sdma0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2083538/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 2079819] [NEW] xwayland repeats keypresses, ignores modifier
Public bug reported: I switch into Mattermost with Windows+3 key combination, this causes an endless stream of 3 to be written into the mattermost field until I press another key (similarly for any other number key, I did not try non-numbers) If we look at the keyboard input device with https://github.com/DIGImend/evdev-dump we can see that the key is not stuck, all the input events are correct: /dev/input/event4 1725622057.447632 EV_MSC MSC_SCAN 0x00DB /dev/input/event4 1725622057.447632 EV_KEY KEY_LEFTMETA 0x0002 ^ press windows key /dev/input/event4 1725622057.447632 EV_SYN SYN_REPORT 0x /dev/input/event4 1725622057.477343 EV_MSC MSC_SCAN 0x0004 /dev/input/event4 1725622057.477343 EV_KEY KEY_3 0x0001 ^ press key 3 /dev/input/event4 1725622057.477343 EV_SYN SYN_REPORT 0x /dev/input/event4 1725622057.627896 EV_MSC MSC_SCAN 0x0004 /dev/input/event4 1725622057.627896 EV_KEY KEY_3 0x ^ release key 3 /dev/input/event4 1725622057.627896 EV_SYN SYN_REPORT 0x /dev/input/event4 1725622057.997495 EV_MSC MSC_SCAN 0x00DB /dev/input/event4 1725622057.997495 EV_KEY KEY_LEFTMETA 0x ^ release windows key (now it starts endlessly dumping 3 into mattermost) /dev/input/event4 1725622057.997495 EV_SYN SYN_REPORT 0x /dev/input/event4 1725622059.869769 EV_MSC MSC_SCAN 0x00DB /dev/input/event4 1725622059.869769 EV_KEY KEY_LEFTMETA 0x0001 ^ press windows key again /dev/input/event4 1725622059.869769 EV_SYN SYN_REPORT 0x /dev/input/event4 1725622059.919605 EV_MSC MSC_SCAN 0x0009 /dev/input/event4 1725622059.919605 EV_KEY KEY_8 0x0001 ^ press 8 to switch to the terminal window This only affects Xwayland, native Wayland clients behave correctly. ProblemType: Bug DistroRelease: Ubuntu 24.10 Package: xwayland 2:24.1.2-1 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.30.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: GNOME Date: Fri Sep 6 13:26:18 2024 InstallationDate: Installed on 2022-11-26 (650 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20221126) SourcePackage: xwayland UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: xwayland (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug oracular wayland-session ** Description changed: I switch into Mattermost with Windows+3 key combination, this causes an endless stream of 3 to be written into the mattermost field until I - press another key. + press another key (similarly for any other number key, I did not try + non-numbers) If we look at the keyboard input device with https://github.com/DIGImend/evdev-dump we can see that the key is not stuck, all the input events are correct: /dev/input/event4 1725622057.447632 EV_MSC MSC_SCAN 0x00DB /dev/input/event4 1725622057.447632 EV_KEY KEY_LEFTMETA 0x0002 ^ press windows key /dev/input/event4 1725622057.447632 EV_SYN SYN_REPORT 0x /dev/input/event4 1725622057.477343 EV_MSC MSC_SCAN 0x0004 /dev/input/event4 1725622057.477343 EV_KEY KEY_3 0x0001 ^ press key 3 /dev/input/event4 1725622057.477343 EV_SYN SYN_REPORT 0x /dev/input/event4 1725622057.627896 EV_MSC MSC_SCAN 0x0004 /dev/input/event4 1725622057.627896 EV_KEY KEY_3 0x ^ release key 3 /dev/input/event4 1725622057.627896 EV_SYN SYN_REPORT 0x /dev/input/event4 1725622057.997495 EV_MSC MSC_SCAN 0x00DB /dev/input/event4 1725622057.997495 EV_KEY KEY_LEFTMETA 0x ^ release windows key (now it starts endlessly dumping 3 into mattermost) /dev/input/event4 1725622057.997495 EV_SYN SYN_REPORT 0x /dev/input/event4 1725622059.869769 EV_MSC MSC_SCAN 0x00DB /dev/input/event4 1725622059.869769 EV_KEY KEY_LEFTMETA 0x0001 ^ press windows key again /dev/input/event4 1725622059.869769 EV_SYN SYN_REPORT 0x /dev/input/event4 1725622059.919605 EV_MSC MSC_SCAN 0x0009 /dev/input/event4 1725622059.919605 EV_KEY KEY_8 0x0001 ^ press 8 to switch to the terminal window - This only affects Xwayland, native Wayland clients behave correctly. ProblemType: Bug DistroRelease: Ubuntu 24.10 Package: xwayland 2:24.1.2-1 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.30.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: GNOME Date: Fri Sep 6 13:26:18 2024 InstallationDate: Installed on 2022-11-26 (650 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20221126) SourcePackage: xwayland UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xwayland in Ubuntu.
[Ubuntu-x-swat] [Bug 2045899] Re: More amdgpu crashes: pagefaults, ring timeouts and parser bugs
Waiting for 6.5.13 to actually build but on 6.6.0-14 from proposed now which is based on 6.6.3 which probably has all the fancy patches too -- 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/2045899 Title: More amdgpu crashes: pagefaults, ring timeouts and parser bugs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045899/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 2045899] Re: More amdgpu crashes: pagefaults, ring timeouts and parser bugs
These ones I don't remember seeing before: [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125! -- 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/2045899 Title: More amdgpu crashes: pagefaults, ring timeouts and parser bugs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045899/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 2045899] Re: More amdgpu crashes: pagefaults, ring timeouts and parser bugs
I saw similar messages in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2032386 but that only caused hangs and not block the entire desktop (and Firefox is good now so I don't know) -- 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/2045899 Title: More amdgpu crashes: pagefaults, ring timeouts and parser bugs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045899/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 2045899] Re: More amdgpu crashes: pagefaults, ring timeouts and parser bugs
** Attachment added: "OlderDmesg.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045899/+attachment/5727266/+files/OlderDmesg.txt ** Also affects: mesa (Ubuntu) Importance: Undecided Status: New -- 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/2045899 Title: More amdgpu crashes: pagefaults, ring timeouts and parser bugs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045899/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1875015] Re: Displaylink is extremely slow in Xorg sessions
Unsubscribing ubuntu-sponsors as the bug has been inactive for months now and it's not clear what, if anything, still needs sponsoring. Please add a comment and resubscribe if sponsorship is still required. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-nouveau in Ubuntu. https://bugs.launchpad.net/bugs/1875015 Title: Displaylink is extremely slow in Xorg sessions To manage notifications about this bug go to: https://bugs.launchpad.net/nouveau/+bug/1875015/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1929854] Re: Vital and critical configuration files get overridden by system updates without warning
Please don't modify that in /etc/grub.d, set GRUB_RECORDFAIL_TIMEOUT=5 in the /etc/default/grub file (or in an /etc/default/grub.d snippet). /etc/grub.d file changes are last resort, that file changes and incorporating those changes with your own ones will be annoying. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to libx11 in Ubuntu. https://bugs.launchpad.net/bugs/1929854 Title: Vital and critical configuration files get overridden by system updates without warning To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1929854/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1845801] Re: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login.
The proposed debdiff is wrong, it reverts a patch in the patch series by adding a new patch. I think we can probably remove the vt-handoff.patch from the patch series for groovy without much checking, but any SRU will need to consult with flavours to check if they need the handoff. -- 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/1845801 Title: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1845801/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1861756] Re: upgrade from 18.04 to 20.04 issues due to colord / libsane issue
There were two issues: (1) mesa in focal has lower version than in releases, newer one stuck in proposed (2) ubuntu-release-upgrader did not check that the solution it picked at the end (after re-marking meta packages for upgrades) was actually valid. It assumed that if mark_upgrade() failed, the operation was a no- change, when it actually led to broken packages. (2) is fixed, (1) should be fixed soon. ** Also affects: mesa (Ubuntu) Importance: Undecided Status: New ** Changed in: mesa (Ubuntu) Status: New => Fix Committed -- 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/1861756 Title: upgrade from 18.04 to 20.04 issues due to colord / libsane issue To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1861756/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1756459] Re: VP9 hardware decoding broken in 17.10, displaying corrupted images in frames while playing videos
Fixed with the 2.1 upload as well. ** Changed in: intel-vaapi-driver (Ubuntu) Status: New => Fix Committed ** Also affects: intel-vaapi-driver (Ubuntu Bionic) Importance: Undecided Status: Fix Committed ** Also affects: intel-vaapi-driver (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: intel-vaapi-driver (Ubuntu Artful) 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/1756459 Title: VP9 hardware decoding broken in 17.10, displaying corrupted images in frames while playing videos To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-vaapi-driver/+bug/1756459/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1756380] Re: vaapi VP9 hardware decoding not working anymore in bionic
** Changed in: intel-vaapi-driver (Ubuntu) Status: Confirmed => Fix Committed -- 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/1756380 Title: vaapi VP9 hardware decoding not working anymore in bionic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-vaapi-driver/+bug/1756380/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
