[Ubuntu-x-swat] [Bug 1915565] Re: screen fades for about 10 seconds then returns to normal
[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.launchpad.net/bugs/1915565 Title: screen fades for about 10 seconds then returns to normal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1915565/+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 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05
The solution has been found and should have been rather obvious in the first place... Just try a different distribution. I decided to try out Linux Mint 20.1 and have been testing it for the past ~6 hours, completely stock (except for all updates installed), no kernel modifications or GRUB options and it works every time on bootup with the touchpad. I am rather surprised that such a relatively old kernel (5.4) works with this new-ish laptop. Perhaps this was why I was so falsely focused on having newer kernels available in a distribution in the first place. I even tried 40 consecutive reboots whilst messing with the touchpad as the machine was booting and it still worked every time. Let it be known that the fix for the Lenovo IdeaPad 3 14ADA05 is to simply install Linux Mint. I have to imagine that other Ubuntu-based installs also work with this particular laptop, especially since it says "Fix Released" under Ubuntu and Ubuntu-related distributions. As far as Manjaro goes, also let it be known that something was introduced after Kernel 5.9.16-1 which breaks the ability for the touchpad to reliably work with this laptop. My best educated guess is that something is loaded too early or too late during bootup which gets jumbled up at random. No idea what that could possibly be, but I hope that Manjaro devs might take note. I know that at least @Helmut Stult might still be looking in this thread. I consider this fixed for my laptop :) -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-input-libinput in Ubuntu. https://bugs.launchpad.net/bugs/1887190 Title: MSFT Touchpad not working on Lenovo Legion-5 15ARH05 To manage notifications about this bug go to: https://bugs.launchpad.net/pop-os/+bug/1887190/+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 1924667] [NEW] Once in a while, xorg crashes after a restart.
Public bug reported: [ 1681.827] (II) FBDEV: driver for framebuffer: fbdev [ 1681.827] (II) VESA: driver for VESA chipsets: vesa [ 1681.828] (**) modeset(0): claimed PCI slot 0@0:2:0 [ 1681.828] (II) modeset(0): using default device [ 1681.828] (WW) Falling back to old probe method for fbdev [ 1681.828] (II) Loading sub module "fbdevhw" [ 1681.828] (II) LoadModule: "fbdevhw" [ 1681.828] (II) Loading /usr/lib/xorg/modules/libfbdevhw.so [ 1681.828] (II) Module fbdevhw: vendor="X.Org Foundation" [ 1681.828]compiled for 1.20.8, module version = 0.0.2 [ 1681.828]ABI class: X.Org Video Driver, version 24.1 [ 1681.828] (II) modeset(0): Creating default Display subsection in Screen section "Default Screen Section" for depth/fbbpp 24/32 [ 1681.828] (==) modeset(0): Depth 24, (==) framebuffer bpp 32 [ 1681.828] (EE) [ 1681.828] (EE) Backtrace: [ 1681.829] (EE) 0: /usr/lib/xorg/Xorg (OsLookupColor+0x13c) [0x563983d6277c] [ 1681.829] (EE) 1: /lib/x86_64-linux-gnu/libpthread.so.0 (funlockfile+0x60) [0x7f7d9807041f] [ 1681.829] (EE) 2: /usr/lib/xorg/Xorg (xf86PlatformMatchDriver+0x5b0) [0x563983c5c400] [ 1681.829] (EE) 3: /usr/lib/xorg/Xorg (xf86CollectOptions+0x77) [0x563983c3f227] [ 1681.829] (EE) unw_get_proc_name failed: no unwind info found [-10] [ 1681.829] (EE) 4: /usr/lib/xorg/modules/drivers/modesetting_drv.so (?+0x0) [0x7f7d97845bd0] [ 1681.829] (EE) 5: /usr/lib/xorg/Xorg (InitOutput+0xb94) [0x563983c42be4] [ 1681.829] (EE) 6: /usr/lib/xorg/Xorg (InitFonts+0x1d4) [0x563983c04e34] [ 1681.829] (EE) 7: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf3) [0x7f7d97e8e0b3] [ 1681.829] (EE) 8: /usr/lib/xorg/Xorg (_start+0x2e) [0x563983beea7e] [ 1681.829] (EE) [ 1681.829] (EE) Segmentation fault at address 0x124 [ 1681.829] (EE) Fatal server error: [ 1681.829] (EE) Caught signal 11 (Segmentation fault). Server aborting [ 1681.829] (EE) [ 1681.829] (EE) I am using Ubuntu 20.04. When I reboot my laptop, the screen will probably go grey. After checking the log, I find the error message above. ** Affects: xorg (Ubuntu) Importance: Undecided Status: New -- 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/1924667 Title: Once in a while, xorg crashes after a restart. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1924667/+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 1923153] Re: [radeon] Display output laggy from iGPU when operating on desktop with attaching AMD R7 430 graphic (dGPU)
** Also affects: xserver-xorg-driver-ati via https://gitlab.freedesktop.org/xorg/driver/xf86-video-ati/-/issues/194 Importance: Unknown Status: Unknown -- 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/1923153 Title: [radeon] Display output laggy from iGPU when operating on desktop with attaching AMD R7 430 graphic (dGPU) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1923153/+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 1896171] Re: Wayland GL apps appear corrupt on Raspberry Pi 4B (v3d driver)
This bug was fixed in the package mutter - 3.38.4-1ubuntu2 --- mutter (3.38.4-1ubuntu2) hirsute; urgency=medium [ Daniel van Vugt ] * Revert "debian/patches: Properly handle configuration events on windows" to fix a regression making some windows to move on resize (LP: #1922034). * Add 61-mutter.rules-Enable-KMS-modifiers-for-Raspberry-P.patch. To enable KMS modifiers on Raspberry Pi, which means to enable the first fix in wayland-dma-buf-Add-support-for-DRM_FORMAT_ABGR2101010.patch (LP: #1896171) [ Marco Trevisan (Treviño) ] * debian/patches: Backport workspace fixes from upstream gnome-3-38 branch * debian/patches: Use Xwayland pkg-config if available * debian/patches: Use -listenfd to invoke XWayland if available (LP: #1922539) -- Marco Trevisan (Treviño) Thu, 15 Apr 2021 06:28:51 +0200 ** Changed in: mutter (Ubuntu) Status: Fix Committed => Fix Released -- 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/1896171 Title: Wayland GL apps appear corrupt on Raspberry Pi 4B (v3d driver) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1896171/+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 1924583] Re: ASPEED AST driver seems unstable in 20.04.2 LTS
** Package changed: ubuntu => xorg (Ubuntu) -- 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/1924583 Title: ASPEED AST driver seems unstable in 20.04.2 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1924583/+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 1924583] [NEW] ASPEED AST driver seems unstable in 20.04.2 LTS
You have been subscribed to a public bug: I have had the screen go blank several times. Each time that this occurred, I was selecting the "Settings" item from the upper right corner arrow. Perhaps there are a lot of low level accesses that occur when this menu item is selected that somehow locks up the ASPEED AST driver or some other part of the display? When this problem occurs, the only way I have been able to recover is to power cycle the system. The info collected for this bug report was taken after rebooting the system. I originally had a problem that the initial login screen did not display (blank screen) but I came across the following that provided a solution of disable Wayland: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1872091 I am not able to reproduce the problem at will. I can usually access the "Settings" without a problem. However, each time the screen has gone blank it was right after clicking on the "Settings" menu item. I have six identical machines (Supermicro SYS-5019C-FL) and this problem has occurred on several of them. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-49.55~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-49-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Apr 15 08:16:08 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: ASPEED Technology, Inc. ASPEED Graphics Family [1a03:2000] (rev 41) (prog-if 00 [VGA controller]) Subsystem: Super Micro Computer Inc ASPEED Graphics Family [15d9:1b0e] InstallationDate: Installed on 2021-04-13 (1 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: Supermicro Super Server ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-49-generic root=UUID=9242ef3a-0904-41c6-8ee2-4c224bb71e1a ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/05/2020 dmi.bios.release: 5.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: X11SCL-IF dmi.board.vendor: Supermicro dmi.board.version: 1.01 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 17 dmi.chassis.vendor: Supermicro dmi.chassis.version: 0123456789 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.5:bd10/05/2020:br5.13:svnSupermicro:pnSuperServer:pvr0123456789:rvnSupermicro:rnX11SCL-IF:rvr1.01:cvnSupermicro:ct17:cvr0123456789: dmi.product.family: To be filled by O.E.M. dmi.product.name: Super Server dmi.product.sku: To be filled by O.E.M. dmi.product.version: 0123456789 dmi.sys.vendor: Supermicro version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubuntu -- ASPEED AST driver seems unstable in 20.04.2 LTS https://bugs.launchpad.net/bugs/1924583 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in Ubuntu. ___ 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 1918985] Re: Xorg crashed with SIGABRT (caught SIGSEGV) in libinput_device_config_send_events_get_modes(device=NULL) from LibinputApplyConfig() from LibinputSetProperty() from XIC
thanks. Timo, could you SRU this one please? ** Also affects: xserver-xorg-input-libinput (Ubuntu Hirsute) Importance: High Status: Triaged ** Changed in: xserver-xorg-input-libinput (Ubuntu Hirsute) Assignee: (unassigned) => Timo Aaltonen (tjaalton) ** Tags removed: rls-hh-incoming -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-input-libinput in Ubuntu. https://bugs.launchpad.net/bugs/1918985 Title: Xorg crashed with SIGABRT (caught SIGSEGV) in libinput_device_config_send_events_get_modes(device=NULL) from LibinputApplyConfig() from LibinputSetProperty() from XIChangeDeviceProperty() To manage notifications about this bug go to: https://bugs.launchpad.net/xserver-xorg-input-libinput/+bug/1918985/+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 1923153] Re: [radeon] Display output laggy from iGPU when operating on desktop with attaching AMD R7 430 graphic (dGPU)
Hi Daniel, Thank you for sharing. We are not allow to provide a customization as workaround before we know the fix plan. I reported an upstream issue: https://gitlab.freedesktop.org/xorg/driver/xf86-video-ati/-/issues/194 -- 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/1923153 Title: [radeon] Display output laggy from iGPU when operating on desktop with attaching AMD R7 430 graphic (dGPU) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1923153/+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 1923153] Re: [radeon] Display output laggy from iGPU when operating on desktop with attaching AMD R7 430 graphic (dGPU)
Hi Daniel, Thank you for sharing. OEM team is not allow the provide a customization as workaround before we don't know the plan to fix. I reported an issue as https://gitlab.freedesktop.org/xorg/driver/xf86-video-ati/-/issues/194 ** Bug watch added: gitlab.freedesktop.org/xorg/driver/xf86-video-ati/-/issues #194 https://gitlab.freedesktop.org/xorg/driver/xf86-video-ati/-/issues/194 -- 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/1923153 Title: [radeon] Display output laggy from iGPU when operating on desktop with attaching AMD R7 430 graphic (dGPU) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1923153/+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 1924289] [NEW] migrate to llvm 12
Public bug reported: llvm 12.0 is finally out, migrate the Intel OpenCL stack to it to match Mesa et al. ** Affects: intel-opencl-clang (Ubuntu) Importance: Undecided Status: New ** Affects: spirv-llvm-translator (Ubuntu) Importance: Undecided Status: New ** Also affects: intel-opencl-clang (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to intel-opencl-clang in Ubuntu. https://bugs.launchpad.net/bugs/1924289 Title: migrate to llvm 12 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-opencl-clang/+bug/1924289/+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 1921991] Re: [SRU] Support isdv4-aes stylus group and multiple AES stylus definitions
@seb128, Thanks a lot! -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to libwacom in Ubuntu. https://bugs.launchpad.net/bugs/1921991 Title: [SRU] Support isdv4-aes stylus group and multiple AES stylus definitions To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1921991/+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 1923153] Re: [radeon] Display output laggy from iGPU when operating on desktop with attaching AMD R7 430 graphic (dGPU)
Anyway, for this bug my thinking is that if a different config satisfies the OEM then that can be considered as a semipermanent workaround. Other than that, it looks like the bug needs to be reported upstream to https://gitlab.freedesktop.org/xorg/driver/xf86-video-ati -- 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/1923153 Title: [radeon] Display output laggy from iGPU when operating on desktop with attaching AMD R7 430 graphic (dGPU) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1923153/+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 1923153] Re: [radeon] Display output laggy from iGPU when operating on desktop with attaching AMD R7 430 graphic (dGPU)
Good point. Running 'man amdgpu' I can immediately see one such good reason: Option "TearFree" "boolean" -- 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/1923153 Title: [radeon] Display output laggy from iGPU when operating on desktop with attaching AMD R7 430 graphic (dGPU) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1923153/+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 1923153] Re: [radeon] Display output laggy from iGPU when operating on desktop with attaching AMD R7 430 graphic (dGPU)
because the native drivers have features that modesetting_drv does not have, and how AMD expects them to be used -- 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/1923153 Title: [radeon] Display output laggy from iGPU when operating on desktop with attaching AMD R7 430 graphic (dGPU) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1923153/+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 1921991] Re: [SRU] Support isdv4-aes stylus group and multiple AES stylus definitions
Uploaded to focal -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to libwacom in Ubuntu. https://bugs.launchpad.net/bugs/1921991 Title: [SRU] Support isdv4-aes stylus group and multiple AES stylus definitions To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1921991/+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 1919093] Re: [ThinkPad P1 Gen 3 w/ Intel + Nvidia Quadro T2000] Desktop does not load after login - purple screen with mouse
I've seen a couple of people report issues with manual NVIDIA driver installations recently but so long as you installed the NVIDIA driver through the 'Additional Drivers' app then it is expected to work. I think I ran out of ideas for this bug a month ago but it does seem to be assigned to the wrong project so I shall change that. ** Package changed: xorg-server (Ubuntu) => nvidia-graphics-drivers-460 (Ubuntu) ** Also affects: linux-hwe-5.8 (Ubuntu) Importance: Undecided Status: New -- 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/1919093 Title: [ThinkPad P1 Gen 3 w/ Intel + Nvidia Quadro T2000] Desktop does not load after login - purple screen with mouse To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.8/+bug/1919093/+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 1919093] Re: [ThinkPad P1 Gen 3 w/ Intel + Nvidia Quadro T2000] Desktop does not load after login - purple screen with mouse
Can I do anything to help troubleshoot this issue further? The issue has persisted through the last kernel updates, I am now on kernel version 5.8.0-49. Wayland works for the most part, but some apps won't start, and screen sharing works only partially. -- 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/1919093 Title: [ThinkPad P1 Gen 3 w/ Intel + Nvidia Quadro T2000] Desktop does not load after login - purple screen with mouse To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1919093/+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
