[Ubuntu-x-swat] [Bug 2048438] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/2048438/+attachment/5739501/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xwayland in Ubuntu. https://bugs.launchpad.net/bugs/2048438 Title: Dual monitor extend (join) not working with Wayland with p14s ThinkPad laptop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xwayland/+bug/2048438/+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 2048438] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/2048438/+attachment/5739500/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xwayland in Ubuntu. https://bugs.launchpad.net/bugs/2048438 Title: Dual monitor extend (join) not working with Wayland with p14s ThinkPad laptop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xwayland/+bug/2048438/+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 2048438] Re: Dual monitor extend (join) not working with Wayland with p14s ThinkPad laptop
apport information ** Tags added: apport-collected mantic ** Description changed: I have a Lenovo ThinkPad P14s gen4 amd laptop, which has an integrated GPU. I installed Ubuntu 23.10, and it defaults to using Wayland and connected it to an external Dell Dell P2720D monitor via HDMI. The UI under Settings > Displays then "Mirror", the default setting works, and I see the display duplicated as expected, with the large external monitor having a low resolution limited to that of the laptop. But if I switch to "Join" does not allow to Apply with message: > Changes Cannot be Applied. This could be due to hardware limitations. Logging off and changing to X allows "Join" to work, so it is a Wayland issue. - Is there a way to make it work on Wayland? Mostly out of morbid - curiosity. + Is there a way to make it work on Wayland? Mostly out of morbid curiosity. + --- + ProblemType: Bug + ApportVersion: 2.27.0-0ubuntu5 + Architecture: amd64 + CasperMD5CheckResult: pass + CurrentDesktop: ubuntu:GNOME + DistroRelease: Ubuntu 23.10 + InstallationDate: Installed on 2023-11-25 (51 days ago) + InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1) + Package: xwayland 2:23.2.0-1ubuntu0.3 + PackageArchitecture: amd64 + ProcVersionSignature: Ubuntu 6.5.0-14.14-generic 6.5.3 + Tags: mantic + Uname: Linux 6.5.0-14-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dialout dip lpadmin ollama plugdev sudo users + _MarkForUpload: True ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/2048438/+attachment/5739499/+files/Dependencies.txt -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xwayland in Ubuntu. https://bugs.launchpad.net/bugs/2048438 Title: Dual monitor extend (join) not working with Wayland with p14s ThinkPad laptop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xwayland/+bug/2048438/+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 2048438] [NEW] Dual monitor extend (join) not working with Wayland with p14s ThinkPad laptop
Public bug reported: I have a Lenovo ThinkPad P14s gen4 amd laptop, which has an integrated GPU. I installed Ubuntu 23.10, and it defaults to using Wayland and connected it to an external Dell Dell P2720D monitor via HDMI. The UI under Settings > Displays then "Mirror", the default setting works, and I see the display duplicated as expected, with the large external monitor having a low resolution limited to that of the laptop. But if I switch to "Join" does not allow to Apply with message: > Changes Cannot be Applied. This could be due to hardware limitations. Logging off and changing to X allows "Join" to work, so it is a Wayland issue. Is there a way to make it work on Wayland? Mostly out of morbid curiosity. ** Affects: xwayland (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xwayland in Ubuntu. https://bugs.launchpad.net/bugs/2048438 Title: Dual monitor extend (join) not working with Wayland with p14s ThinkPad laptop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xwayland/+bug/2048438/+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 1931387] [NEW] Ubuntu UI screen image freezes randomly during usage after fresh 21.04 install, suspecting Wayland
Public bug reported: Also submitted at: https://askubuntu.com/questions/1344736/ubuntu-ui- freezes-randomly-after-fresh-21-04-install-suspecting-wayland Let me know if there's any way to collect more useful information if there is ever a future crash, or a better place to report. I was running 20.10 previously with NVIDIA drivers, Then four days ago, I did a clean 21.04 install without installing the NVIDIA drivers, and since then the UI has frozen three times on my. I am unable to determine exactly what action triggered the freeze. The third time, I was just looking at a webpage, I wasn't even touching my mouse at that exact moment, and then it just froze. I am then unable to see anything move on the screen, including after Ctrl + Alt + Fn, the last image just stays fixed. The third time was also a bit different. A few seconds after freezing, it actually went down to a black terminal screen as during boot messages and then I was redirected to the login screen, as if I had been logged out. I was able to login, my programs were closed, so I was effectively logged out. Then two Apport windows showed up, and one of them contained several references to Xwayland. Under `/var/crash/_usr_bin_Xwayland.1000.crash` I see one of them: - `ProcCmdline: /usr/bin/Xwayland :0 -rootless -noreset -accessx -core -auth /run/user/1000/.mutter-Xwaylandauth.48ZQ40 -listen 4 -listen 5 -displayfd 6 -initfd 7 - `StackTraceAddressSignature` contained mentions of Xwayland and nouveau_dri.so: ``` StacktraceAddressSignature: /usr/bin/Xwayland:6:/usr/lib/x86_64-linux-gnu/libc-2.33.so+864:/usr/bin/Xwayland+13cb40:/usr/bin/Xwayland+14866f:/usr/bin/Xwayland+13b1a7:/usr/lib/x86_64-linux-gnu/libc-2.33.so+864:/usr/lib/x86_64-linux-gnu/libc-2.33.so+749:/usr/lib/x86_64-linux-gnu/libc-2.33.so+123d6:/usr/lib/x86_64-linux-gnu/libdrm_nouveau.so.2.0.0+25d7:/usr/lib/x86_64-linux-gnu/libdrm_nouveau.so.2.0.0+2537:/usr/lib/x86_64-linux-gnu/libdrm_nouveau.so.2.0.0+265f:/usr/lib/x86_64-linux-gnu/libdrm_nouveau.so.2.0.0+2a77:/usr/lib/x86_64-linux-gnu/libdrm_nouveau.so.2.0.0+31aa:/usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so+93b943:/usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so+93bc61:/usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so+17cc01 ``` I also checked and I am using Wayland (the default since 21.04 apparently): https://askubuntu.com/questions/904940/how-can-i-tell-if-i -am-running-wayland/1344287#1344287 Hardware: - Lenovo ThinkPad P51 - NVIDIA Quadro M1200 4GB GDDR5 GPU Just after the crash, dmesg contained the following possibly interesting lines: ``` [ 9556.450894] nouveau :01:00.0: gr: TRAP ch 3 [00ff8cf000 Xwayland[3831]] [ 9556.450907] nouveau :01:00.0: gr: GPC0/TPC2/MP trap: global 0004 [MULTIPLE_WARP_ERRORS] warp 3c000d [OOR_REG] [ 9556.454264] nouveau :01:00.0: gr: TRAP ch 3 [00ff8cf000 Xwayland[3831]] [ 9556.454283] nouveau :01:00.0: gr: GPC0/TPC0/MP trap: global 0004 [MULTIPLE_WARP_ERRORS] warp 3e000d [OOR_REG] [ 9556.466339] nouveau :01:00.0: gr: TRAP ch 3 [00ff8cf000 Xwayland[3831]] [ 9556.466351] nouveau :01:00.0: gr: GPC0/TPC3/MP trap: global 0004 [MULTIPLE_WARP_ERRORS] warp 3e000d [OOR_REG] [ 9698.230726] nouveau :01:00.0: Xwayland[3831]: failed to idle channel 5 [Xwayland[3831]] [ 9713.230743] nouveau :01:00.0: Xwayland[3831]: failed to idle channel 5 [Xwayland[3831]] [ 9713.231918] nouveau :01:00.0: fifo: fault 00 [READ] at 00056000 engine 07 [HOST0] client 06 [HUB/HOST] reason 02 [PTE] on channel 5 [00ff0d9000 Xwayland[3831]] [ 9713.231930] nouveau :01:00.0: fifo: channel 5: killed [ 9713.231932] nouveau :01:00.0: fifo: runlist 0: scheduled for recovery [ 9713.231939] nouveau :01:00.0: fifo: engine 5: scheduled for recovery [ 9713.231943] nouveau :01:00.0: Xwayland[3831]: channel 5 killed! [ 9717.642691] nouveau :01:00.0: fifo: SCHED_ERROR 0a [CTXSW_TIMEOUT] [ 9717.642702] nouveau :01:00.0: fifo: runlist 0: scheduled for recovery [ 9717.642709] nouveau :01:00.0: fifo: channel 3: killed [ 9717.642714] nouveau :01:00.0: fifo: engine 0: scheduled for recovery [ 9717.643113] nouveau :01:00.0: Xwayland[3831]: channel 3 killed! [ 9719.351714] apport-gtk[119654]: segfault at 18 ip 7f337637d194 sp 7ffd95094dc0 error 4 in libgtk-3.so.0.2404.21[7f3376274000+385000] [ 9719.351721] Code: c4 08 5b 5d c3 90 f3 0f 1e fa 48 8b 7f 10 48 85 ff 74 0b e9 ce c6 ff ff 66 0f 1f 44 00 00 48 83 ec 08 48 89 d7 e8 0c 36 17 00 <48> 8b 40 18 48 8b 78 10 e8 ef 03 09 00 48 83 c4 08 48 89 c7 e9 a3 [ 9744.187533] rfkill: input handler enabled [ 9745.940823] rfkill: input handler disabled [ 9775.737572] rfkill: input handler enabled [ 9777.953055] rfkill: input handler disabled ``` Related: - https://askubuntu.com/questions/1334177/ubuntu-21-04-wayland-gimp- black-window GIMP works fine ** Affects: wayland (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of
[Ubuntu-x-swat] [Bug 551475] Re: amdcccle settings do not persist lucid
Reproduce on 14.04. Settings don't even persist if I just close and reopen amdcccle without reboot. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to fglrx-installer in Ubuntu. https://bugs.launchpad.net/bugs/551475 Title: amdcccle settings do not persist lucid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/551475/+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
