[Ubuntu-x-swat] [Bug 1952619] Re: Xwayland crashed with SIGABRT in __libc_start_call_main()
*** This bug is a duplicate of bug 1751508 *** https://bugs.launchpad.net/bugs/1751508 It's hard to see why the retracing service marked this as a duplicate of 1751508. I'm fairly certain it is not. -- 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/1952619 Title: Xwayland crashed with SIGABRT in __libc_start_call_main() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xwayland/+bug/1952619/+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 1920067] Re: Xorg with EVDI can't start with Mesa 21.0
For those of you who landed here looking for how to use DisplayLink in Hirsute, I wrote up a workaround here: https://blog.kamens.us/2021/03/19 /update-on-using-displaylink-with-ubuntu-21-04-hirsute-hippo/ -- 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/1920067 Title: Xorg with EVDI can't start with Mesa 21.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1920067/+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 1920067] Re: Xorg with EVDI can't start with Mesa 21.0
I performed the splash -> nosplash test described above; it made no difference. -- 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/1920067 Title: Xorg with EVDI can't start with Mesa 21.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1920067/+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 1920067] Re: Somehow today's Hirsute updates have broken evdi with Xorg even when I boot with the 5.10 kernel
** 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/1920067 Title: Somehow today's Hirsute updates have broken evdi with Xorg even when I boot with the 5.10 kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1920067/+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 1920067] Re: Somehow today's Hirsute updates have broken evdi with Xorg even when I boot with the 5.10 kernel
I debugged this further and discovered that one of the following updates caused evdi with kernel 5.10 to start failing as described above: 2021-03-18 21:55:45 upgrade libegl-mesa0:amd64 20.3.4-1 21.0.0-1 2021-03-18 21:55:45 upgrade libgbm1:amd64 20.3.4-1 21.0.0-1 2021-03-18 21:55:45 upgrade libgl1-mesa-dri:i386 20.3.4-1 21.0.0-1 2021-03-18 21:55:46 upgrade libgl1-mesa-dri:amd64 20.3.4-1 21.0.0-1 2021-03-18 21:55:47 upgrade libglx-mesa0:i386 20.3.4-1 21.0.0-1 2021-03-18 21:55:48 upgrade libglx-mesa0:amd64 20.3.4-1 21.0.0-1 2021-03-18 21:55:48 upgrade libglapi-mesa:amd64 20.3.4-1 21.0.0-1 2021-03-18 21:55:48 upgrade libglapi-mesa:i386 20.3.4-1 21.0.0-1 When I downgraded all of the listed debs to the old version indicated (20.3.4-1) and rebooted, evdi with kernel 5.10 started working again. So I guess this is a mesa bug? -- 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/1920067 Title: Somehow today's Hirsute updates have broken evdi with Xorg even when I boot with the 5.10 kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1920067/+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 1920067] [NEW] Somehow today's Hirsute updates have broken evdi with Xorg even when I boot with the 5.10 kernel
Public bug reported: As I indicated in a bug report I filed earlier today, https://bugs.launchpad.net/ubuntu/+source/evdi/+bug/1920059, evdi-dkms can no longer compile the evdi kernel module with the 5.11 kernel. So, to work around this, I need to keep using the 5.10 kernel instead. But I can't, because when I boot with the 5.10 kernel this is what shows up in /var/log/Xorg.0.log when gdm3 tries to start up the login screen (note: I have an NVIDIA graphics card, which is why (I believe) Wayland isn't being used here): [ 857.957] (EE) modeset(G0): drmSetMaster failed: Device or resource busy [ 857.957] (EE) Fatal server error: [ 857.957] (EE) AddScreen/ScreenInit failed for gpu driver 0 -1 [ 857.957] (EE) [ 857.957] (EE) Please consult the The X.Org Foundation support at http://wiki.x.org for help. [ 857.957] (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information. [ 857.957] (EE) [ 858.144] (EE) Server terminated with error (1). Closing log file. This is probably not what you will see in the Xorg.0.log (if any) attached automatically to this bug because I've completely wiped the evdi kernel module from my system since that was the only way I could get a display manager up so I could use ubuntu-bug to submit this bug. Here's what I updated today: 2021-03-18 15:03:26 upgrade sysvinit-utils:amd64 2.96-5ubuntu1 2.96-6ubuntu1 2021-03-18 15:03:27 upgrade cron:amd64 3.0pl1-136ubuntu1 3.0pl1-136ubuntu2 2021-03-18 15:03:28 upgrade gpg-wks-client:amd64 2.2.20-1ubuntu2 2.2.20-1ubuntu3 2021-03-18 15:03:28 upgrade dirmngr:amd64 2.2.20-1ubuntu2 2.2.20-1ubuntu3 2021-03-18 15:03:29 upgrade gpg-wks-server:amd64 2.2.20-1ubuntu2 2.2.20-1ubuntu3 2021-03-18 15:03:29 upgrade gnupg-utils:amd64 2.2.20-1ubuntu2 2.2.20-1ubuntu3 2021-03-18 15:03:29 upgrade gpg-agent:amd64 2.2.20-1ubuntu2 2.2.20-1ubuntu3 2021-03-18 15:03:30 upgrade gpg:amd64 2.2.20-1ubuntu2 2.2.20-1ubuntu3 2021-03-18 15:03:30 upgrade gpgconf:amd64 2.2.20-1ubuntu2 2.2.20-1ubuntu3 2021-03-18 15:03:30 upgrade gnupg-l10n:all 2.2.20-1ubuntu2 2.2.20-1ubuntu3 2021-03-18 15:03:31 upgrade gnupg:all 2.2.20-1ubuntu2 2.2.20-1ubuntu3 2021-03-18 15:03:31 upgrade gpgsm:amd64 2.2.20-1ubuntu2 2.2.20-1ubuntu3 2021-03-18 15:03:31 upgrade gpgv:amd64 2.2.20-1ubuntu2 2.2.20-1ubuntu3 2021-03-18 15:03:32 upgrade libjs-sphinxdoc:all 3.5.1-2 3.5.2-1 2021-03-18 15:03:33 upgrade libnfsidmap2:amd64 0.25-5.1ubuntu2 0.25-6 2021-03-18 15:03:33 install linux-modules-5.11.0-11-generic:amd64 5.11.0-11.12 2021-03-18 15:03:35 install linux-image-5.11.0-11-generic:amd64 5.11.0-11.12 2021-03-18 15:03:36 install linux-modules-extra-5.11.0-11-generic:amd64 5.11.0-11.12 2021-03-18 15:03:40 upgrade linux-generic:amd64 5.10.0.14.16 5.11.0.11.12 2021-03-18 15:03:40 upgrade linux-image-generic:amd64 5.10.0.14.16 5.11.0.11.12 2021-03-18 15:03:41 install linux-headers-5.11.0-11:all 5.11.0-11.12 2021-03-18 15:03:44 install linux-headers-5.11.0-11-generic:amd64 5.11.0-11.12 2021-03-18 15:03:47 upgrade linux-headers-generic:amd64 5.10.0.14.16 5.11.0.11.12 2021-03-18 15:03:47 upgrade linux-libc-dev:amd64 5.10.0-14.15 5.11.0-11.12 2021-03-18 15:03:48 upgrade slack-desktop:amd64 4.13.0 4.14.0 2021-03-18 15:03:52 upgrade xwayland:amd64 2:1.20.10-3ubuntu3 2:21.0.99.902-0ubuntu1 2021-03-18 15:56:42 upgrade at:amd64 3.1.23-1.1ubuntu2 3.1.23-1.1ubuntu3 At first glance I don't understand how any of these could be causing this behavior. Potentially relevant: I had to recompile and reinstall the evdi kernel module while booted into 5.10 because when I install the 5.11 kernel dkms removed the module from 5.10 and then failed to rebuild it because the 5.11 build failed (or something I don't really understand why dkms does what it does *sigh*). I don't see how that should matter because the recompiled version of the module should have been identical, but *shrug*. As noted above, when I remove the evdi kernel modules from /lib/modules and reboot with 5.10 the problem goes away, so this does appear to be an evdi issue. In short: despite the fact that it's not clear how upgrading any of the modules listed above would cause evdi that used to work to suddenly stop working, that appears to be the case. Any advice would be appreciated because now I can't use the displays connected to my DisplayLink hub with either 5.10 or 5.11 kernels, despite the fact that they worked with the 5.10 kernel before today. Please let me know if there's any other info you need here. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xserver-xorg 1:7.7+22ubuntu1 ProcVersionSignature: Ubuntu 5.10.0-14.15-generic 5.10.11 Uname: Linux 5.10.0-14-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.141 Mon Dec 28 16:21:32 UTC 2020
[Ubuntu-x-swat] [Bug 1849484] Re: [X1 Carbon 7, i915, HDMI] Ultra-wide monitor recognized properly when plugged in only intermittently [Xorg only]
[72227.300557] [drm:drm_dp_dual_mode_detect [drm_kms_helper]] *ERROR* Unexpected DP dual mode adaptor ID 50 [72228.173908] [drm:drm_dp_dual_mode_detect [drm_kms_helper]] *ERROR* Unexpected DP dual mode adaptor ID 50 [72229.956316] [drm:drm_dp_dual_mode_detect [drm_kms_helper]] *ERROR* Unexpected DP dual mode adaptor ID 50 [72233.510378] [drm:drm_dp_dual_mode_detect [drm_kms_helper]] *ERROR* Unexpected DP dual mode adaptor ID 50 [72236.205870] [drm:drm_dp_dual_mode_detect [drm_kms_helper]] *ERROR* Unexpected DP dual mode adaptor ID 50 [72237.999470] [drm:drm_dp_dual_mode_detect [drm_kms_helper]] *ERROR* Unexpected DP dual mode adaptor ID 50 [72239.786382] [drm:drm_dp_dual_mode_detect [drm_kms_helper]] *ERROR* Unexpected DP dual mode adaptor ID 50 [72242.549836] [drm:drm_dp_dual_mode_detect [drm_kms_helper]] *ERROR* Unexpected DP dual mode adaptor ID 50 [72243.442375] [drm:drm_dp_dual_mode_detect [drm_kms_helper]] *ERROR* Unexpected DP dual mode adaptor ID 54 [72244.361826] [drm:drm_dp_dual_mode_detect [drm_kms_helper]] *ERROR* Unexpected DP dual mode adaptor ID 50 [72250.961559] [drm:drm_dp_dual_mode_detect [drm_kms_helper]] *ERROR* Unexpected DP dual mode adaptor ID 50 [72254.547660] [drm:drm_dp_dual_mode_detect [drm_kms_helper]] *ERROR* Unexpected DP dual mode adaptor ID 50 [72269.690250] [drm:drm_dp_dual_mode_detect [drm_kms_helper]] *ERROR* Unexpected DP dual mode adaptor ID 50 [72273.607350] [drm] EDID has major version 93, instead of 1 [72279.495513] [drm:drm_dp_dual_mode_detect [drm_kms_helper]] *ERROR* Unexpected DP dual mode adaptor ID 50 [72290.492743] [drm:drm_dp_dual_mode_detect [drm_kms_helper]] *ERROR* Unexpected DP dual mode adaptor ID 54 [72293.153731] [drm:drm_dp_dual_mode_detect [drm_kms_helper]] *ERROR* Unexpected DP dual mode adaptor ID 54 [72294.043151] [drm:drm_dp_dual_mode_detect [drm_kms_helper]] *ERROR* Unexpected DP dual mode adaptor ID 54 [72295.855213] [drm:drm_dp_dual_mode_detect [drm_kms_helper]] *ERROR* Unexpected DP dual mode adaptor ID 50 [72297.632687] [drm:drm_dp_dual_mode_detect [drm_kms_helper]] *ERROR* Unexpected DP dual mode adaptor ID 54 [72300.590655] [drm:drm_dp_dual_mode_detect [drm_kms_helper]] *ERROR* Unexpected DP dual mode adaptor ID 54 [72301.836996] i2c i2c-3: sendbytes: error -110 [72315.236846] [drm] EDID has major version 93, instead of 1 [72318.454559] [drm:drm_dp_dual_mode_detect [drm_kms_helper]] *ERROR* Unexpected DP dual mode adaptor ID 50 [72318.778580] [drm] EDID has major version 93, instead of 1 [72321.074870] [drm:drm_dp_dual_mode_detect [drm_kms_helper]] *ERROR* Unexpected DP dual mode adaptor ID 50 [72322.836269] [drm:drm_dp_dual_mode_detect [drm_kms_helper]] *ERROR* Unexpected DP dual mode adaptor ID 50 [72324.607377] [drm:drm_dp_dual_mode_detect [drm_kms_helper]] *ERROR* Unexpected DP dual mode adaptor ID 54 [72325.489757] [drm:drm_dp_dual_mode_detect [drm_kms_helper]] *ERROR* Unexpected DP dual mode adaptor ID 50 [72330.776866] [drm:drm_dp_dual_mode_detect [drm_kms_helper]] *ERROR* Unexpected DP dual mode adaptor ID 50 [72332.734125] mce: CPU7: Core temperature above threshold, cpu clock throttled (total events = 575) [72332.734125] mce: CPU3: Core temperature above threshold, cpu clock throttled (total events = 575) [72332.734127] mce: CPU1: Package temperature above threshold, cpu clock throttled (total events = 871) [72332.734127] mce: CPU5: Package temperature above threshold, cpu clock throttled (total events = 871) [72332.734128] mce: CPU6: Package temperature above threshold, cpu clock throttled (total events = 871) [72332.734129] mce: CPU0: Package temperature above threshold, cpu clock throttled (total events = 871) [72332.734130] mce: CPU4: Package temperature above threshold, cpu clock throttled (total events = 871) [72332.734131] mce: CPU2: Package temperature above threshold, cpu clock throttled (total events = 871) [72332.734132] mce: CPU3: Package temperature above threshold, cpu clock throttled (total events = 871) [72332.734133] mce: CPU7: Package temperature above threshold, cpu clock throttled (total events = 871) [72332.766080] mce: CPU3: Core temperature/speed normal [72332.766080] mce: CPU7: Core temperature/speed normal [72332.766081] mce: CPU1: Package temperature/speed normal [72332.766082] mce: CPU5: Package temperature/speed normal [72332.766083] mce: CPU2: Package temperature/speed normal [72332.766083] mce: CPU6: Package temperature/speed normal [72332.766084] mce: CPU4: Package temperature/speed normal [72332.766085] mce: CPU0: Package temperature/speed normal [72332.766086] mce: CPU7: Package temperature/speed normal [72332.766087] mce: CPU3: Package temperature/speed normal [72334.303794] [drm:drm_dp_dual_mode_detect [drm_kms_helper]] *ERROR* Unexpected DP dual mode adaptor ID 50 [72335.184591] [drm:drm_dp_dual_mode_detect [drm_kms_helper]] *ERROR* Unexpected DP dual mode adaptor ID 50 [72336.941529] [drm:drm_dp_dual_mode_detect [drm_kms_helper]] *ERROR* Unexpected DP
[Ubuntu-x-swat] [Bug 1849484] Re: [X1 Carbon 7, i915, HDMI] Ultra-wide monitor recognized properly when plugged in only intermittently [Xorg only]
"If you see changes like that after boot then please attach output from 'dmesg' showing the period of time when the change occurred." I'm sorry, I'm not sure what you're asking me to watch for here. Can you clarify? -- 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/1849484 Title: [X1 Carbon 7, i915, HDMI] Ultra-wide monitor recognized properly when plugged in only intermittently [Xorg only] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1849484/+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 1849484] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1849484/+attachment/5300910/+files/PulseList.txt -- 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/1849484 Title: [X1 Carbon 7, i915, HDMI] Ultra-wide monitor recognized properly when plugged in only intermittently [Xorg only] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1849484/+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 1849484] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1849484/+attachment/5300911/+files/RfKill.txt -- 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/1849484 Title: [X1 Carbon 7, i915, HDMI] Ultra-wide monitor recognized properly when plugged in only intermittently [Xorg only] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1849484/+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 1849484] Re: [X1 Carbon 7, i915, HDMI] Ultra-wide monitor recognized properly when plugged in only intermittently [Xorg only]
FYI: While apport-collect was running, my screens went blank briefly and then when they came back my monitor configuration was wrong: the ultra- wide monitor was at a lower resolution than it's supposed to be and the two monitors' relative positions were not configured correctly. Unplugging the ultra-wide and plugging it back in fixed this situation. This is similar to the behavior I see which prompted me to file this bug in the first place. It would seem that something that apport-collect did triggers the issue or a similar one. So does launching the TeamViewer client, by the way. -- 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/1849484 Title: [X1 Carbon 7, i915, HDMI] Ultra-wide monitor recognized properly when plugged in only intermittently [Xorg only] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1849484/+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 1849484] XorgLogOld.txt
apport information ** Attachment added: "XorgLogOld.txt" https://bugs.launchpad.net/bugs/1849484/+attachment/5300916/+files/XorgLogOld.txt -- 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/1849484 Title: [X1 Carbon 7, i915, HDMI] Ultra-wide monitor recognized properly when plugged in only intermittently [Xorg only] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1849484/+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 1849484] Xrandr.txt
apport information ** Attachment added: "Xrandr.txt" https://bugs.launchpad.net/bugs/1849484/+attachment/5300917/+files/Xrandr.txt -- 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/1849484 Title: [X1 Carbon 7, i915, HDMI] Ultra-wide monitor recognized properly when plugged in only intermittently [Xorg only] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1849484/+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 1849484] xdpyinfo.txt
apport information ** Attachment added: "xdpyinfo.txt" https://bugs.launchpad.net/bugs/1849484/+attachment/5300918/+files/xdpyinfo.txt ** Changed in: linux (Ubuntu) Status: Incomplete => New ** Changed in: linux (Ubuntu) Status: New => Confirmed -- 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/1849484 Title: [X1 Carbon 7, i915, HDMI] Ultra-wide monitor recognized properly when plugged in only intermittently [Xorg only] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1849484/+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 1849484] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1849484/+attachment/5300901/+files/IwConfig.txt -- 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/1849484 Title: [X1 Carbon 7, i915, HDMI] Ultra-wide monitor recognized properly when plugged in only intermittently [Xorg only] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1849484/+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 1849484] XorgLog.txt
apport information ** Attachment added: "XorgLog.txt" https://bugs.launchpad.net/bugs/1849484/+attachment/5300915/+files/XorgLog.txt -- 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/1849484 Title: [X1 Carbon 7, i915, HDMI] Ultra-wide monitor recognized properly when plugged in only intermittently [Xorg only] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1849484/+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 1849484] DpkgLog.txt
apport information ** Attachment added: "DpkgLog.txt" https://bugs.launchpad.net/bugs/1849484/+attachment/5300900/+files/DpkgLog.txt -- 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/1849484 Title: [X1 Carbon 7, i915, HDMI] Ultra-wide monitor recognized properly when plugged in only intermittently [Xorg only] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1849484/+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 1849484] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1849484/+attachment/5300914/+files/WifiSyslog.txt -- 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/1849484 Title: [X1 Carbon 7, i915, HDMI] Ultra-wide monitor recognized properly when plugged in only intermittently [Xorg only] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1849484/+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 1849484] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1849484/+attachment/5300912/+files/UdevDb.txt -- 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/1849484 Title: [X1 Carbon 7, i915, HDMI] Ultra-wide monitor recognized properly when plugged in only intermittently [Xorg only] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1849484/+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 1849484] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1849484/+attachment/5300909/+files/ProcModules.txt -- 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/1849484 Title: [X1 Carbon 7, i915, HDMI] Ultra-wide monitor recognized properly when plugged in only intermittently [Xorg only] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1849484/+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 1849484] UnitySupportTest.txt
apport information ** Attachment added: "UnitySupportTest.txt" https://bugs.launchpad.net/bugs/1849484/+attachment/5300913/+files/UnitySupportTest.txt -- 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/1849484 Title: [X1 Carbon 7, i915, HDMI] Ultra-wide monitor recognized properly when plugged in only intermittently [Xorg only] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1849484/+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 1849484] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1849484/+attachment/5300908/+files/ProcInterrupts.txt -- 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/1849484 Title: [X1 Carbon 7, i915, HDMI] Ultra-wide monitor recognized properly when plugged in only intermittently [Xorg only] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1849484/+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 1849484] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1849484/+attachment/5300903/+files/Lsusb.txt -- 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/1849484 Title: [X1 Carbon 7, i915, HDMI] Ultra-wide monitor recognized properly when plugged in only intermittently [Xorg only] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1849484/+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 1849484] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1849484/+attachment/5300905/+files/ProcCpuinfo.txt -- 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/1849484 Title: [X1 Carbon 7, i915, HDMI] Ultra-wide monitor recognized properly when plugged in only intermittently [Xorg only] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1849484/+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 1849484] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1849484/+attachment/5300906/+files/ProcCpuinfoMinimal.txt -- 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/1849484 Title: [X1 Carbon 7, i915, HDMI] Ultra-wide monitor recognized properly when plugged in only intermittently [Xorg only] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1849484/+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 1849484] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1849484/+attachment/5300907/+files/ProcEnviron.txt -- 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/1849484 Title: [X1 Carbon 7, i915, HDMI] Ultra-wide monitor recognized properly when plugged in only intermittently [Xorg only] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1849484/+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 1849484] MonitorsUser.xml.txt
apport information ** Attachment added: "MonitorsUser.xml.txt" https://bugs.launchpad.net/bugs/1849484/+attachment/5300904/+files/MonitorsUser.xml.txt -- 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/1849484 Title: [X1 Carbon 7, i915, HDMI] Ultra-wide monitor recognized properly when plugged in only intermittently [Xorg only] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1849484/+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 1849484] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1849484/+attachment/5300902/+files/Lspci.txt -- 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/1849484 Title: [X1 Carbon 7, i915, HDMI] Ultra-wide monitor recognized properly when plugged in only intermittently [Xorg only] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1849484/+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 1849484] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1849484/+attachment/5300898/+files/CRDA.txt -- 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/1849484 Title: [X1 Carbon 7, i915, HDMI] Ultra-wide monitor recognized properly when plugged in only intermittently [Xorg only] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1849484/+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 1849484] Re: [X1 Carbon 7, i915, HDMI] Ultra-wide monitor recognized properly when plugged in only intermittently [Xorg only]
apport information ** Tags added: apport-collected ubuntu ** Description changed: I have an LG ultra-wide (2560x1080) monitor. Sometimes when I plug it into my laptop, whose screen was working fine before I plugged it in, both screens go black but nothing else happens. I can still see the mouse cursor and move it between the two monitors (sometimes in the correct location configuration I've configured, sometimes not), but nothing is rendered on the screens. Sometimes when I plug the monitor in, it comes on, but the resolution is wrong. Sometimes it is actually recognized and configured correctly. Frequently I have to unplug the monitor and plug it back in three times or more before it is recognized correctly. I wish it just worked right the first time. :-/ ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.34.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Oct 23 08:34:07 2019 DisplayManager: gdm3 InstallationDate: Installed on 2019-09-12 (40 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) RelatedPackageVersions: mutter-common 3.34.1-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to eoan on 2019-09-20 (32 days ago) + --- + ProblemType: Bug + .tmp.unity_support_test.0: + + ApportVersion: 2.20.11-0ubuntu8 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC1: jik3196 F pulseaudio + /dev/snd/pcmC1D0p: jik3196 F...m pulseaudio + /dev/snd/controlC0: jik3196 F pulseaudio + BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' + CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' + CompositorRunning: None + CurrentDesktop: ubuntu:GNOME + DistUpgraded: 2019-09-20 10:09:14,777 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' + DistroCodename: eoan + DistroRelease: Ubuntu 19.10 + DistroVariant: ubuntu + ExtraDebuggingInterest: Yes + GraphicsCard: + Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (rev 02) (prog-if 00 [VGA controller]) +Subsystem: Lenovo UHD Graphics 620 (Whiskey Lake) [17aa:2292] + InstallationDate: Installed on 2019-09-12 (45 days ago) + InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) + MachineType: LENOVO 20QD001VUS + NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair + Package: xorg-server (not installed) + ProcFB: 0 i915drmfb + ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-19-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 + ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 + RelatedPackageVersions: + linux-restricted-modules-5.3.0-19-generic N/A + linux-backports-modules-5.3.0-19-generic N/A + linux-firmware1.183.1 + Tags: eoan ubuntu + Uname: Linux 5.3.0-19-generic x86_64 + UpgradeStatus: Upgraded to eoan on 2019-09-20 (38 days ago) + UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers wireshark + _MarkForUpload: True + dmi.bios.date: 07/04/2019 + dmi.bios.vendor: LENOVO + dmi.bios.version: N2HET30W (1.13 ) + dmi.board.asset.tag: Not Available + dmi.board.name: 20QD001VUS + dmi.board.vendor: LENOVO + dmi.board.version: SDK0J40697 WIN + dmi.chassis.asset.tag: No Asset Information + dmi.chassis.type: 10 + dmi.chassis.vendor: LENOVO + dmi.chassis.version: None + dmi.modalias: dmi:bvnLENOVO:bvrN2HET30W(1.13):bd07/04/2019:svnLENOVO:pn20QD001VUS:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20QD001VUS:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: + dmi.product.family: ThinkPad X1 Carbon 7th + dmi.product.name: 20QD001VUS + dmi.product.sku: LENOVO_MT_20QD_BU_Think_FM_ThinkPad X1 Carbon 7th + dmi.product.version: ThinkPad X1 Carbon 7th + dmi.sys.vendor: LENOVO + modified.conffile..etc.apport.crashdb.conf: [modified] + mtime.conffile..etc.apport.crashdb.conf: 2019-10-23T16:51:18.143596 + version.compiz: compiz 1:0.9.14.0+19.10.20190918-0ubuntu1 + version.libdrm2: libdrm2 2.4.99-1ubuntu1 + version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1 + version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1 + version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 + version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A + version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1 + version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 + version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1849484/+attachment/5300897/+files/AlsaInfo.txt -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to
[Ubuntu-x-swat] [Bug 1849484] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1849484/+attachment/5300899/+files/CurrentDmesg.txt -- 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/1849484 Title: [X1 Carbon 7, i915, HDMI] Ultra-wide monitor recognized properly when plugged in only intermittently [Xorg only] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1849484/+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 1849484] Re: [X1 Carbon 7, i915, HDMI] Ultra-wide monitor recognized properly when plugged in only intermittently [Xorg only]
I tried a different cable. It didn't help. Also, I can trigger my monitors freaking out as described above merely by launching the Synology Drive Client when the ultra-wide monitor is connected. Also, the issue seems to be triggered even if the applet isn't visible in my top bar, i.e., even if the only Synology Drive processes that are running are the background processes. Synology Drive does kernel stuff -- I believe it uses inotify to monitor directories for changes -- so I'm suspecting that there's something misbehaving in the kernel and something that Synology Drive does is banging up against it. -- 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/1849484 Title: [X1 Carbon 7, i915, HDMI] Ultra-wide monitor recognized properly when plugged in only intermittently [Xorg only] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1849484/+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 1849484] Re: [X1 Carbon 7, i915, HDMI] Ultra-wide monitor recognized properly when plugged in only intermittently [Xorg only]
It's not clear to me how this can be a cable or monitor issue when it only happens in Xorg and it happens much more frequently when one particular app is running (see comment #4). Having said that, I will try to find a spare HDMI cable and test. I am not using an adapter, I'm plugging an HDMI cable directly into an HDMI port both on the monitor and on the laptop. -- 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/1849484 Title: [X1 Carbon 7, i915, HDMI] Ultra-wide monitor recognized properly when plugged in only intermittently [Xorg only] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1849484/+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 1733032] Re: touchpad disable while typing, disable tap-to-click don't work in 17.10
OK, so... Both disabling tap-to-click and enabling disable-touchpad-while-typing work properly, in both "Ubuntu" and "Ubuntu on Xorg", when I remove the xserver-xorg-input-synaptics package. I suppose that means this bug is invalid, BUT... 1) It still seems like a bug to me that installing xserver-xorg-input- synaptics breaks stuff. Shouldn't both the settings app and gnome-tweak- tool be able to tell when that X server driver is being used and behave appropriately? 2) I don't believe I ever installed xserver-xorg-input-synaptics by hand, so I assume it was a holdover from before I upgraded to 17.10. So is it a bug we should be paying attention to -- or documenting in the release notes, or SOMETHING -- that upgrading from before 17.10 to 17.10 or later is going to break anyone who has the xserver-xorg-input- synaptics package installed before the upgrade? -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to libinput in Ubuntu. https://bugs.launchpad.net/bugs/1733032 Title: touchpad disable while typing, disable tap-to-click don't work in 17.10 To manage notifications about this bug go to: https://bugs.launchpad.net/libinput/+bug/1733032/+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 1733032] Re: touchpad disable while typing, disable tap-to-click don't work in 17.10
Logging into Ubuntu (i.e., not "Ubuntu on Xorg"), the "Disable While Typing" Touchpad setting in gnome-tweak-tool now appears to work. Furthermore, tapping to click does _not_ work, i.e., the behavior I want is present by default as far as I can tell. In fact, I can't figure out any way to cause tapping the touchpad to generate a click. So either the behavior has changed in an update since I reported this bug, or I was using Xorg but thought I was using Wayland. Logging into Ubuntu on Xorg, without anything special in any of my X server config files, the "Disable While Typing" setting in gnome-tweak- tool doesn't do anything, and tap to click is enabled and there's no way I can find to disable it. So that appears to be a bug in GNOME, not a bug in libinput. There should be a way to disable tap to click, and the "Disable While Typing" setting should be obeyed. If it's not, then I believe that means GNOME isn't populating that setting through to the X server the way it needs to be, which doesn't sound like a libinput bug. Logging into Ubuntu on Xorg, these lines added to the "libinput touchpad catchall" section of /usr/share/X11/xorg.conf.d/40-libinput.conf appear to have no effect, even though Xorg.0.log confirms that section is being applied: Option "Tapping" "false" Option "DisableWhileTyping" "true" Option "PalmDetection" "true" Perhaps this is a libinput bug, or perhaps the synaptics sections that are being applied to the device after the libinput sections are overriding the libinput settings? Again logging into Ubuntu on Xorg, if I add this to my X config then tap to click is gone and it seems like there is _some_ protection against brushing against the trackpad, although there still isn't full disable by typing: Section "InputClass" Identifier "disable touchpad tap to click, enable palm detection" Driver "synaptics" MatchIsTouchpad "on" MatchDevicePath "/dev/input/event*" Option "MaxTapTime" "0" Option "PalmDetect" "on" EndSection So, the potential issues that _I_ see here are that the Disable While Typing setting does not work in "Ubuntu on Xorg", and that the libinput options I'm configuring into my X server don't appear to take effect. Should I indeed open a libinput bug about that, or re-open the bug I opened and closed but clarify in the re-opened bug that it only applies to Xorg, not to Wayland? -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to libinput in Ubuntu. https://bugs.launchpad.net/bugs/1733032 Title: touchpad disable while typing, disable tap-to-click don't work in 17.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1733032/+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 1733032] Re: touchpad disable while typing, disable tap-to-click don't work in 17.10
Actually, I think opening a libinput bug is premature, for reasons I will explain below. I'm going to close that other bug until I can quantify better what is going on. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to libinput in Ubuntu. https://bugs.launchpad.net/bugs/1733032 Title: touchpad disable while typing, disable tap-to-click don't work in 17.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1733032/+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 1733032] Re: touchpad disable while typing, disable tap-to-click don't work in 17.10
Filed https://bugs.freedesktop.org/show_bug.cgi?id=104956. ** Bug watch added: freedesktop.org Bugzilla #104956 https://bugs.freedesktop.org/show_bug.cgi?id=104956 -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to libinput in Ubuntu. https://bugs.launchpad.net/bugs/1733032 Title: touchpad disable while typing, disable tap-to-click don't work in 17.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1733032/+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 1744510] [NEW] RF mouse (with USB dongle) doesn't work after reboot until I unplug it and plug it back in
Public bug reported: My wireless mouse doesn't work after I reboot until I unplug its USB dongle and plug it back in. I don't see anything in Xorg.0.log which obviously explains this problem. It looks like the mouse is added to the X server configuration on startup without any problems, at least unless I'm misreading the log, and then the second time it's added, when I unplug it and plug it back in, it looks like the same thing happens in the log, but then the mouse works. This was a problem in 17.04 as well, i.e., it isn't new in 17.10. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: xserver-xorg-core 2:1.19.5-0ubuntu2 ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13 Uname: Linux 4.13.0-25-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 384.111 Tue Dec 19 23:51:45 PST 2017 GCC version: gcc version 7.2.0 (Ubuntu 7.2.0-8ubuntu3) .tmp.unity_support_test.0: ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Jan 20 18:31:15 2018 DistUpgraded: 2018-01-20 12:11:24,767 ERROR Cache can not be locked (E:Could not get lock /var/lib/dpkg/lock - open (11: Resource temporarily unavailable), E:Unable to lock the administration directory (/var/lib/dpkg/), is another process using it?) DistroCodename: artful DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GM204 [GeForce GTX 970] [10de:13c2] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Device [196e:1131] InstallationDate: Installed on 2016-01-16 (735 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: Acer Predator G6-710 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-25-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: xorg-server UpgradeStatus: Upgraded to artful on 2018-01-20 (0 days ago) dmi.bios.date: 05/18/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: R01-A4 dmi.board.name: Predator G6-710 dmi.board.vendor: Acer dmi.chassis.type: 3 dmi.chassis.vendor: Acer dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrR01-A4:bd05/18/2016:svnAcer:pnPredatorG6-710:pvr:rvnAcer:rnPredatorG6-710:rvr:cvnAcer:ct3:cvr: dmi.product.family: Acer Desktop dmi.product.name: Predator G6-710 dmi.sys.vendor: Acer version.compiz: compiz 1:0.9.13.1+17.10.20170901-0ubuntu1 version.libdrm2: libdrm2 2.4.83-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu1~17.10.2 version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~17.10.2 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20170309-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Sat Jan 20 17:16:47 2018 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.19.5-0ubuntu2 ** Affects: xorg-server (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful ubuntu -- 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/1744510 Title: RF mouse (with USB dongle) doesn't work after reboot until I unplug it and plug it back in To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1744510/+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 1727742] [NEW] "peek" hangs Wayland display server
Public bug reported: I have "peek" installed from its PPA repository as described at https://github.com/phw/peek#ubuntu . When I attempt to record a GIF with peek under Wayland, it counts down and then my display hangs. I can't even switch VTs, so the only thing I can do at this point is power-cycle my laptop. I know it's just the display hanging, not everything, because the music I'm listening to continues to play. This occurs whether or not I set GDK_BACKEND to x11 before launching peek. Peek works fine when I use it under Xorg instead of Xwayland. See also https://github.com/phw/peek/issues/202 , the bug I filed with the peek developers about this, but regardless of whether peek is doing something wrong, it shouldn't be able to cause the display server to hang. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: xwayland 2:1.19.5-0ubuntu2 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Oct 26 10:09:23 2017 DistUpgraded: 2017-10-20 10:34:09,954 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: artful DistroVariant: ubuntu DkmsStatus: virtualbox, 5.1.30, 4.10.0-37-generic, x86_64: installed virtualbox, 5.1.30, 4.13.0-16-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Crystal Well Integrated Graphics Controller [8086:0d26] (rev 08) (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer Crystal Well Integrated Graphics Controller [1558:7410] InstallationDate: Installed on 2017-05-19 (159 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: System76, Inc. Galago UltraPro ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: xorg-server UpgradeStatus: Upgraded to artful on 2017-10-20 (5 days ago) dmi.bios.date: 12/12/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: Tag 12345 dmi.board.name: W740SU dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd12/12/2013:svnSystem76,Inc.:pnGalagoUltraPro:pvrgalu1:rvnNotebook:rnW740SU:rvrNotApplicable:cvnNotebook:ct9:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: Galago UltraPro dmi.product.version: galu1 dmi.sys.vendor: System76, Inc. version.compiz: compiz 1:0.9.13.1+17.10.20170901-0ubuntu1 version.libdrm2: libdrm2 2.4.83-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20170309-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 ** Affects: xorg-server (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful ubuntu wayland-session -- 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/1727742 Title: "peek" hangs Wayland display server To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1727742/+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 1536165] Re: X server hangs on start when DisplayPort is connected
>I'm not sure what you are going on about, but you found an offense where none was given. "You're not allowed to be offended unless I say you're allowed to be offended." >Despite this, since you aren't interested in pursuing this further, there is nothing further to do with this report. Your commitment to the quality of the software you maintain is admirable. -- 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/1536165 Title: X server hangs on start when DisplayPort is connected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1536165/+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 1536165] Re: X server hangs on start when DisplayPort is connected
Good grief. I took the time to submit the bug. I took the time to upgrade my BIOS and report to you that it's still broken after doing so. I have a solution to my problem -- using the nvidia driver instead of nouveau -- so the marginal value to me in continuing to invest time and effort in this is minimal. I think I've done my duty here. Do something more about this or not; that's your call. I'm out. -- 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/1536165 Title: X server hangs on start when DisplayPort is connected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1536165/+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 1536165] Re: X server hangs on start when DisplayPort is connected
By the way, perhaps I would be more likely to be willing to help more if you hadn't made a snotty comment about bug-reporting etiquette when you asked me to update my BIOS. A comment which, oddly, appears to have disappeared. I find it quite disconcerting that people are apparently able to make passive-aggressive rude comments to bug reporters and then delete them without a trace. -- 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/1536165 Title: X server hangs on start when DisplayPort is connected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1536165/+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 1536165] Re: X server hangs on start when DisplayPort is connected
>1) Please provide the output of the following terminal command (not perform an >apport-collect): >sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date $ sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date [sudo] password for jik: R01-A4 05/18/2016 $ ** Changed in: xorg (Ubuntu) Status: Expired => 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/1536165 Title: X server hangs on start when DisplayPort is connected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1536165/+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 1536165] Re: X server hangs on start when DisplayPort is connected
>If you update to this following https://help.ubuntu.com/community/BIOSUpdate does it change anything? No. -- 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/1536165 Title: X server hangs on start when DisplayPort is connected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1536165/+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 1576842] [NEW] None of the recovery options from boot-time low-graphics mode work
Public bug reported: In Ubuntu 16.04 x86_64, I accidentally installed the nvidia driver on a machine that actually has an intel graphics controller. This caused two different failure modes in the time I was trying to figure out what was wrong: sometimes the X server was unable to start at all, and other times it loaded both nvidia and intel drivers, successfully deduced that nvidia shouldn't have been loaded and unloaded it, and successfully displayed the lightdm login screen, but then wouldn't let me log in because the X server had failed to configure opengl properly, probably because installing the nvidia driver caused the X server to be configured to use the wrong mesa library. This bug report is about the first failure mode mentioned above, i.e., the X server was unable to start at all on boot. Instead, I was presented with a dialog that said "The system is running in low-graphics mode" and offered me several choices for what to do about it. I believe that this dialog was displayed by xdiagnose (version 3.8.4), which is why I'm filing this report for that package. If I'm wrong, please redirect the bug report as appropriate. The point of this bug report is that none of the recovery options presented by the dialogs worked. In particular: * Selecting "Try running with default graphics mode" didn't work: the screen flashed several times and then settled on a black screen showing nothing but the results of the boot-time fsck of the root filesystem. At that point, I couldn't switch VTs or anything else; the system was simply hosed and power-cycling was the only option. * Selecting "Reconfigure graphics" (either "Use default (generic) configuration" or "Use your backed-up configuration) just flashed and returned me to the same screen asking me again which configuration to use. * Selecting "Troubleshoot the error" and then "Edit configuration file" didn't work; I was not presented with an editor window, but rather I was simply returned to the same prompt. * "Exit to console login" didn't work; it had the same fsck-screen failure mode described above for "Try running with default graphics mode". I also tried booting in recovery mode and selecting failsafe graphics mode from the recovery menu. This didn't work either. See the attached screenshot for what I got when I tried that. In particular, note the "cp: cannot stat '/etc/X11/xorg.conf': No such file or directory" and "/usr/share/xdiagnose/failsafeXinit: line 117: return: zenity: numeric argument required" error messages. ** Affects: xdiagnose (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xdiagnose in Ubuntu. https://bugs.launchpad.net/bugs/1576842 Title: None of the recovery options from boot-time low-graphics mode work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xdiagnose/+bug/1576842/+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 1576842] Re: None of the recovery options from boot-time low-graphics mode work
** Attachment added: "screen shot of trying to run failsafe X server from recovery boot" https://bugs.launchpad.net/ubuntu/+source/xdiagnose/+bug/1576842/+attachment/4651682/+files/screenshot.jpg -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xdiagnose in Ubuntu. https://bugs.launchpad.net/bugs/1576842 Title: None of the recovery options from boot-time low-graphics mode work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xdiagnose/+bug/1576842/+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 1536165] [NEW] X server hangs on start when DisplayPort is connected
Public bug reported: I just bought a new Acer Predator AG6-710, which supposedly comes with a NVIDIA GeForce GTX 980 graphics controller. It has four output plugs -- DVI, two mini DisplayPort, and HDMI. When I have only one monitor plugged in, on the DVI port using DVI-A, i.e., through a DVI-A -> VGA adapter and then a VGA cable, Ubuntu boots up just fine. However, when I have two monitors plugged in, the first as described above and the second through one of the DisplayPorts via a mini DisplayPort to DVI-I adapter and a DVI-A cable, the X server hangs on boot, and I end up with two blank screens and monitors claiming no signal is being sent. I've attached the Xorg log file when this happens. It happens every single time I boot, i.e., it is reliable. Any additional debugging information I can provide or debugging steps I can take, please ask, I will gladly help. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: xserver-xorg 1:7.7+7ubuntu4 ProcVersionSignature: Ubuntu 4.2.0-25.30-generic 4.2.6 Uname: Linux 4.2.0-25-generic x86_64 .tmp.unity.support.test.1: ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Wed Jan 20 07:13:46 2016 DistUpgraded: Fresh install DistroCodename: wily DistroVariant: ubuntu DkmsStatus: virtualbox, 5.0.10, 4.2.0-23-generic, x86_64: installed virtualbox, 5.0.10, 4.2.0-25-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GM204 [GeForce GTX 970] [10de:13c2] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Device [196e:1131] InstallationDate: Installed on 2016-01-16 (4 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: Acer Predator G6-710 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-25-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 Renderer: Software SourcePackage: xorg UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/21/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: R01-A1 dmi.board.name: Predator G6-710 dmi.board.vendor: Acer dmi.chassis.type: 3 dmi.chassis.vendor: Acer dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrR01-A1:bd09/21/2015:svnAcer:pnPredatorG6-710:pvr:rvnAcer:rnPredatorG6-710:rvr:cvnAcer:ct3:cvr: dmi.product.name: Predator G6-710 dmi.sys.vendor: Acer version.compiz: compiz 1:0.9.12.2+15.10.20151015-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.64-1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.2-1ubuntu4 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.2-1ubuntu4 version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu9.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0+git20150819-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20150808-0ubuntu4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu3 xserver.bootTime: Wed Jan 20 06:50:52 2016 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.17.2-1ubuntu9.1 xserver.video_driver: modeset ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 ubuntu wily ** Attachment added: "Log file when X server fails to come up" https://bugs.launchpad.net/bugs/1536165/+attachment/4553304/+files/Xorg.0.log.old -- 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/1536165 Title: X server hangs on start when DisplayPort is connected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1536165/+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 1536165] Re: X server hangs on start when DisplayPort is connected
Problem goes away if I install nvidia-352. -- 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/1536165 Title: X server hangs on start when DisplayPort is connected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1536165/+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 1518411] Re: "Maximum number of clients reached", new in Ubuntu 15.10
This has something to do with the fact that I have a script running in the background that changes my background image every couple minutes. When I disable that script, the problem goes away. -- 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/1518411 Title: "Maximum number of clients reached", new in Ubuntu 15.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1518411/+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
