[Ubuntu-x-swat] [Bug 1865870] Re: [nvidia] xorg via gdm-x-session fails to start with "Cannot run in framebuffer mode. Please specify busIDs for all framebuffer devices"
I saw this on an ubuntu 20.04 alpha system when I did 'ubuntu-drivers install' to get drivers for my gtx 1080. Reinstalling ubuntu 20.04 final made the problem vanish (whew). -- 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/1865870 Title: [nvidia] xorg via gdm-x-session fails to start with "Cannot run in framebuffer mode. Please specify busIDs for all framebuffer devices" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-440/+bug/1865870/+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 1814607] [NEW] ubuntu 18.04.2 daily is janky with chromium on fishgl.com?
Public bug reported: I've been testing as follows: - install chromium (or chrome, or chrome beta) - open http://fishgl.com - crank up number of fish to 325 (or as high as it'll go and sustain 60 fps) - after fish are happily swimming, watch them swim for 60 seconds, and count number of times the screen freezes This was fine (i.e. zero hangs) on 18.04.1 + https://ubuntuforums.org/showthread.php?t=2400400 but not fine on 18.04.2 (i.e. always hangs briefly within 60 seconds) The last four times I ran this, I got 4, 2, 8, 3 hangs in 60 seconds. Each hang usually lasted for less than a second. Some lasted for a second and a half (maybe that was two hangs back to back). Running xclock -update 1 seems to show that the hang extends to other apps, i.e. when the fish hang, xclock also seems to hang. Running firefox in parallel, or a second chromium window, seems to avoid the hang. tail -f /var/log/syslog didn't show any new output during hangs. (There are a lot of gnome-shell stack dumps in /var/log/syslog, fwiw.) I'll try to test on a non-Hades system. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.18.0-14.15~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-14-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Feb 4 16:50:27 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Device [1002:694e] (rev c0) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation Device [8086:2073] InstallationDate: Installed on 2019-02-04 (0 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Beta amd64 (20190204) MachineType: Intel Corporation NUC8i7HNK ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-14-generic root=UUID=861436ab-4967-41b5-99bc-64b8726682a5 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/01/2018 dmi.bios.vendor: Intel Corp. dmi.bios.version: HNKBLi70.86A.0049.2018.0801.1601 dmi.board.name: NUC8i7HNB dmi.board.vendor: Intel Corporation dmi.board.version: J68197-502 dmi.chassis.type: 3 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnIntelCorp.:bvrHNKBLi70.86A.0049.2018.0801.1601:bd08/01/2018:svnIntelCorporation:pnNUC8i7HNK:pvrJ71486-502:rvnIntelCorporation:rnNUC8i7HNB:rvrJ68197-502:cvnIntelCorporation:ct3:cvr2.0: dmi.product.family: Intel NUC dmi.product.name: NUC8i7HNK dmi.product.version: J71486-502 dmi.sys.vendor: Intel Corporation version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1~18.04.1 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic performance 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/1814607 Title: ubuntu 18.04.2 daily is janky with chromium on fishgl.com? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1814607/+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 1814606] [NEW] ubuntu 18.04.2 daily is janky with chromium on fishgl.com?
Public bug reported: I've been testing Ubuntu 18.04.1 with Hades Canyon using the recipe https://mzwiki.oblong.com/wiki/Hades_Canyon My smoke test is: - install chromium (or chrome, or chrome beta) - open http://fishgl.com - crank up number of fish to 325 (or as high as it'll go and sustain 60 fps) - after fish are happily swimming, watch them swim for 60 seconds, and count number of times the screen freezes This was fine (i.e. zero hangs) on 18.04.1 + https://mzwiki.oblong.com/wiki/Hades_Canyon but not fine on 18.04.2 (i.e. always hangs briefly within 60 seconds) The last four times I ran this, I got 4, 2, 8, 3 hangs in 60 seconds. Each hang usually lasted for less than a second. Some lasted for a second and a half (maybe that was two hangs back to back). Running xclock -update 1 seems to show that the hang extends to other apps, i.e. when the fish hang, xclock also seems to hang. Running firefox in parallel, or a second chromium window, seems to avoid the hang. tail -f /var/log/syslog didn't show any new output during hangs. (There are a lot of gnome-shell stack dumps in /var/log/syslog, fwiw.) I'll try to test on a non-Hades system. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.18.0-14.15~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-14-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Feb 4 16:15:59 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Device [1002:694e] (rev c0) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation Device [8086:2073] InstallationDate: Installed on 2019-02-04 (0 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Beta amd64 (20190204) MachineType: Intel Corporation NUC8i7HNK ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-14-generic root=UUID=861436ab-4967-41b5-99bc-64b8726682a5 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/01/2018 dmi.bios.vendor: Intel Corp. dmi.bios.version: HNKBLi70.86A.0049.2018.0801.1601 dmi.board.name: NUC8i7HNB dmi.board.vendor: Intel Corporation dmi.board.version: J68197-502 dmi.chassis.type: 3 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnIntelCorp.:bvrHNKBLi70.86A.0049.2018.0801.1601:bd08/01/2018:svnIntelCorporation:pnNUC8i7HNK:pvrJ71486-502:rvnIntelCorporation:rnNUC8i7HNB:rvrJ68197-502:cvnIntelCorporation:ct3:cvr2.0: dmi.product.family: Intel NUC dmi.product.name: NUC8i7HNK dmi.product.version: J71486-502 dmi.sys.vendor: Intel Corporation version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1~18.04.1 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic performance 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/1814606 Title: ubuntu 18.04.2 daily is janky with chromium on fishgl.com? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1814606/+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 1714178] Re: Triple 4K monitor display failed (modesetting driver limited to 8192x8192)
I should have mentioned, my Hades has 32GB of RAM. With 8GB or less of RAM, the problem might persist (if I understand the mailing list posts). -- 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/1714178 Title: Triple 4K monitor display failed (modesetting driver limited to 8192x8192) To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1714178/+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 1714178] Re: Triple 4K monitor display failed (modesetting driver limited to 8192x8192)
This just changed for me... but the hardware may matter, as I'm on Hades Canyon, using the amd gpu, not HD graphics. A few days ago I updated to the then-latest 4.19-rc2 (and wrote https://ubuntuforums.org/showthread.php?t=2400400 documenting exactly what I did). Using plain old X (no desktop) on my Hades Canyon, I now see a 16384 x 16384 limit: $ xrandr Screen 0: minimum 320 x 200, current 11520 x 2160, maximum 16384 x 16384 Three screens horizontally work. https://www.mail-archive.com/amd-gfx@lists.freedesktop.org/msg24954.html looks related. I have not yet tested on HD graphics with the new kernel. -- 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/1714178 Title: Triple 4K monitor display failed (modesetting driver limited to 8192x8192) To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1714178/+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 1770742] Re: Cannot find -lGL
This just hit me as well, on a kosher 18.04 system. I recently upgraded to a newer nvidia card, so that must have mangled it somehow. Looks like three of its symlinks got nuked: ls: cannot access '/usr/lib/x86_64-linux-gnu/libEGL.so': No such file or directory ls: cannot access '/usr/lib/x86_64-linux-gnu/libGL.so': No such file or directory ls: cannot access '/usr/lib/x86_64-linux-gnu/libGLESv2.so': No such file or directory lrwxrwxrwx 1 root root 22 Jun 5 07:16 /usr/lib/x86_64-linux-gnu/libGLdispatch.so -> libGLdispatch.so.0.0.0 ... -rw-r--r-- 1 root root 4697 Jan 25 2018 /usr/share/doc/libglvnd-dev/copyright Doing sudo apt install --reinstall libglvnd-dev resolved the problem here. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to libglvnd in Ubuntu. https://bugs.launchpad.net/bugs/1770742 Title: Cannot find -lGL To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libglvnd/+bug/1770742/+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 1776260] Re: Can't use three monitors properly; "xrandr: screen cannot be larger than 8192x8192"
Thanks... sounds like it's a hardware limitation, and the fix involves noticing when the limit's being violated, and doing extra work in that case. I wonder what the framerate impact of that extra work will be. -- 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/1776260 Title: Can't use three monitors properly; "xrandr: screen cannot be larger than 8192x8192" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1776260/+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 1776260] Re: Can't use three monitors properly; "xrandr: screen cannot be larger than 8192x8192"
Thanks, I'll try weston-launch when I get a chance, and I'll try it on ubuntu 18.04 with intel graphics. In the meantime, I checked the maximum size a few systems report, and it does seem to be a property of the graphics hardware and/or driver. See also http://webglstats.com/webgl2/parameter/MAX_TEXTURE_SIZE === + uname -a Linux rbb-ubu1604-6 4.4.0-128-generic #154-Ubuntu SMP Fri May 25 14:15:18 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux + grep maximum + xrandr Screen 0: minimum 8 x 8, current 3840 x 6480, maximum 32767 x 32767 + lspci + grep VGA 03:00.0 VGA compatible controller: NVIDIA Corporation Device 1c03 (rev a1) + glxinfo + grep string server glx vendor string: NVIDIA Corporation server glx version string: 1.4 client glx vendor string: NVIDIA Corporation client glx version string: 1.4 OpenGL vendor string: NVIDIA Corporation OpenGL renderer string: GeForce GTX 1060 6GB/PCIe/SSE2 OpenGL core profile version string: 4.5.0 NVIDIA 390.67 OpenGL core profile shading language version string: 4.50 NVIDIA OpenGL version string: 4.6.0 NVIDIA 390.67 OpenGL shading language version string: 4.60 NVIDIA OpenGL ES profile version string: OpenGL ES 3.2 NVIDIA 390.67 OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.20 === + uname -a Linux rbb-ubu1804-5 4.17.0-999-generic #201806080237 SMP Fri Jun 8 06:41:11 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux + xrandr + grep maximum Screen 0: minimum 320 x 200, current 7680 x 2160, maximum 16384 x 16384 + lspci + grep VGA 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Vega [Radeon RX Vega M] (rev c0) + glxinfo + grep string server glx vendor string: SGI server glx version string: 1.4 client glx vendor string: Mesa Project and SGI client glx version string: 1.4 OpenGL vendor string: X.Org OpenGL renderer string: AMD VEGAM (DRM 3.26.0, 4.17.0-999-generic, LLVM 6.0.0) OpenGL core profile version string: 4.5 (Core Profile) Mesa 18.2.0-devel OpenGL core profile shading language version string: 4.50 OpenGL version string: 3.1 Mesa 18.2.0-devel OpenGL shading language version string: 1.40 OpenGL ES profile version string: OpenGL ES 3.1 Mesa 18.2.0-devel OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.10 === + uname -a Linux rbb-ubu1804-6 4.15.0-23-generic #25-Ubuntu SMP Wed May 23 18:02:16 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux + xrandr + grep maximum Screen 0: minimum 320 x 200, current 3840 x 6480, maximum 8192 x 8192 + lspci + grep VGA 00:02.0 VGA compatible controller: Intel Corporation Iris Pro Graphics 580 (rev 09) + glxinfo + grep string server glx vendor string: SGI server glx version string: 1.4 client glx vendor string: Mesa Project and SGI client glx version string: 1.4 OpenGL vendor string: Intel Open Source Technology Center OpenGL renderer string: Mesa DRI Intel(R) Iris Pro Graphics 580 (Skylake GT4e) OpenGL core profile version string: 4.5 (Core Profile) Mesa 18.0.0-rc5 OpenGL core profile shading language version string: 4.50 OpenGL version string: 3.0 Mesa 18.0.0-rc5 OpenGL shading language version string: 1.30 OpenGL ES profile version string: OpenGL ES 3.2 Mesa 18.0.0-rc5 OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.20 -- 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/1776260 Title: Can't use three monitors properly; "xrandr: screen cannot be larger than 8192x8192" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1776260/+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 1776260] Re: Can't use three monitors properly; "xrandr: screen cannot be larger than 8192x8192"
Sorry, that Intel URL should have been https://www.intel.com/content/www/us/en/support/articles/05571/mini- pcs.html -- 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/1776260 Title: Can't use three monitors properly; "xrandr: screen cannot be larger than 8192x8192" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1776260/+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 1776260] [NEW] Can't use three monitors properly; "xrandr: screen cannot be larger than 8192x8192"
Public bug reported: https://www.intel.com/content/www/us.../mini-pcs.html claims that the Skull Canyon ( NUC6i7KYK ) can handle three 4k displays, so I'm experimenting with a Skull Canyon running a fresh minimal Ubuntu 18.04. It works great when plugged into one 4k monitor (via any of the three ports: hdmi, mini-dp, or type c; all three show up in xrandr as DisplayPort). It even seems to work ok when I plug in two. Doesn't matter which two. When I plug in all three, and boot to normal graphical.target mode with the usual gdm greeter, one of the three screens does show gdm, and allows me to log in. But I can't seem to get all three screens active at the same time. Falling back to old school tools, I did 'sudo systemctl set-default multi-user.target' and rebooted. Logging in, creating a trivial .xinitrc, and doing 'startx' started the X server, and all three screens show the same output. So far so good. But trying to arrange them like this: $ xrandr --auto --output DP-2 --right-of DP-1 --output DP-3 --right-of DP-2 fails with xrandr: screen cannot be larger than 8192x8192 (desired size 11520x2160) Using --above instead of --right-of works, but that's not how the monitors are arranged. I tried creating /usr/share/X11/xorg.conf.d/85-screen.conf containing Section "Screen" Identifier "Default Screen" DefaultDepth24 SubSection "Display" Virtual 11520 6480 EndSubSection EndSection and applied it by killing X and doing startx again, but that gave very strange results: the mouse showed up on two screens, but .xinit didn't seem to have taken effect, and the content on the screen was the same as before startx. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xserver-xorg-core 2:1.19.6-1ubuntu4 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Mon Jun 11 09:49:40 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Iris Pro Graphics 580 [8086:193b] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation Iris Pro Graphics 580 [8086:2064] InstallationDate: Installed on 2018-06-08 (2 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-22-generic root=UUID=80ac733c-b098-4643-84a4-fe81874f2101 ro rootflags=subvol=@ quiet splash vt.handoff=1 SourcePackage: xorg-server UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/03/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: KYSKLi70.86A.0037.2016.0603.1032 dmi.board.name: NUC6i7KYB dmi.board.vendor: Intel Corporation dmi.board.version: H90766-404 dmi.chassis.type: 3 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrKYSKLi70.86A.0037.2016.0603.1032:bd06/03/2016:svn:pn:pvr:rvnIntelCorporation:rnNUC6i7KYB:rvrH90766-404:cvnIntelCorporation:ct3:cvr1.0: version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 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 bionic 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/1776260 Title: Can't use three monitors properly; "xrandr: screen cannot be larger than 8192x8192" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1776260/+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 1655709] Re: Spurious crash report dialog on every login
Still in ubuntu 17.10 with nvidia card. -- 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/1655709 Title: Spurious crash report dialog on every login To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1655709/+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 1655709] [NEW] Spurious crash report dialog on every login
Public bug reported: For the last few years, on nearly all my computers, ubuntu has rewarded my logging in with a crash dialog. Nothing's actually wrong; xorg probably trips over its shoelaces every time it shuts down, but so late in the process that it doesn't matter. Today I went through the crash upload procedure, but no web browser window opened, so either I did something wrong, or the bug is marked 'ignore uploads' somehow... hence this manual report. This bug has to have been reported before, but has probably been marked WONTFIX or something because it is benign. But it does matter, and it's not benign, because I, my wife, and my son get those darn crash dialogs. It doesn't seem to matter what graphics card or driver is in use. Want the crash file left behind after the last upload? ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xserver-xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-43.63-generic 4.4.21 Uname: Linux 4.4.0-43-generic x86_64 NonfreeKernelModules: nvidia_uvm 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 340.96 Sun Nov 8 22:33:28 PST 2015 GCC version: gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.2) .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.1 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 11 08:56:26 2017 DistUpgraded: 2016-04-26 16:26:11,919 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: xenial DistroVariant: ubuntu DpkgLog: ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GT215M [GeForce GTS 360M] [10de:0cb1] (rev a2) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GT215M [GeForce GTS 360M] [1043:203c] InstallationDate: Installed on 2014-07-18 (908 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) Lsusb: Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 04f2:b071 Chicony Electronics Co., Ltd 2.0M UVC Webcam / CNF7129 Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK Computer Inc. G60JX ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.4.0-43-generic root=UUID=28258489-6453-456a-9ecc-c41a02ad0631 ro rootflags=subvol=@ nomodeset quiet splash SourcePackage: xorg UpgradeStatus: Upgraded to xenial on 2016-04-26 (259 days ago) dmi.bios.date: 08/16/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 208 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: G60JX dmi.board.vendor: PEGATRON CORPORATION dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: PEGATRON Computer Inc. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr208:bd08/16/2010:svnASUSTeKComputerInc.:pnG60JX:pvr1.0:rvnPEGATRONCORPORATION:rnG60JX:rvr1.0:cvnPEGATRONComputerInc.:ct10:cvr1.0: dmi.product.name: G60JX dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK Computer Inc. version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Wed Jan 11 08:41:53 2017 xserver.configfile: default xserver.errors: open /dev/fb0: No such file or directory xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.18.3-1ubuntu2.3 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 third-party-packages ubuntu xenial -- 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/1655709 Title: Spurious crash report dialog on every login To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1655709/+subscriptions
[Ubuntu-x-swat] [Bug 1639640] Re: haswell i915 black screen regression with DVI; VGA ok?
Not sure which package this should be against; since it might be DRM, maybe it should be against the linux kernel? -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-intel in Ubuntu. https://bugs.launchpad.net/bugs/1639640 Title: haswell i915 black screen regression with DVI; VGA ok? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1639640/+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 1639640] Re: black screen at boot until pressing power-off button?
I booted with drm.debug=14 and looked at the output of dmesg. It had lines like [0.717202] [drm:i915_dump_device_info] i915 device info: gen=7, pciid=0x0412 rev=0x06 flags=need_gfx_hws,is_haswell,has_fbc,has_hotplug,has_llc,has_ddi,has_fpga_dbg, ... [0.938640] [drm:drm_helper_probe_single_connector_modes_merge_bits] [CONNECTOR:36:VGA-1] disconnected [0.938641] [drm:drm_helper_probe_single_connector_modes_merge_bits] [CONNECTOR:39:HDMI-A-1] [0.938642] [drm:intel_hdmi_detect] [CONNECTOR:39:HDMI-A-1] which made me realize: the drm driver cares a lot about which video connector you plug into. On a whim, I replaced the DVI video cable with a VGA one... and the problem went away! So, that's a better workaround for me: just use a vga cable. ** Summary changed: - black screen at boot until pressing power-off button? + haswell i915 black screen regression with DVI; VGA ok? -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-intel in Ubuntu. https://bugs.launchpad.net/bugs/1639640 Title: haswell i915 black screen regression with DVI; VGA ok? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1639640/+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 1639640] Re: black screen at boot until pressing power-off button?
Seems to have gotten worse with the next batch of updates (linux-image-4.4.0-47-generic:amd64); now it won't show a screen at all, even when booting to multiuser, after the kernel sets the graphics mode. Works fine if I give nomodeset, but then I can't use accelerated graphics. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-intel in Ubuntu. https://bugs.launchpad.net/bugs/1639640 Title: black screen at boot until pressing power-off button? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1639640/+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 1639640] [NEW] black screen at boot until pressing power-off button?
Public bug reported: After a recent update (early Nov 2016), my 16.04 system (an HP Pavillion 500-321, i.e. a generic i5-4570 system with integrated graphics) started showing a black screen on boot (after the grub menu finished). A fresh 16.10 live USB image also has the same problem on this system (but not on an nvidia system), as does a fresh 16.10 install. A fresh 16.04 install does NOT have the problem; the problem can be reproduced on this system by doing a fresh 16.04 install followed by letting it update automatically to the latest 16.04 packages. After some experimentation, I discovered that after booting up into the black screen, I could (usually?) rescue the session by pressing the computer's power button. This brought the screen to life, showing Ubuntu's "reboot or power down?" dialog. Cancelling that left you with a working system. I also discovered that if I booted first to text mode with sudo systemctl set-default multi-user.target and then after logging in via text mode, switch to graphics with startx or with sudo systemctl start graphical.target the screen also was fine. So, um, er, is it a race condition? Is graphical.target missing a wants? And what recent update could be introducing this problem? ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.1 ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21 Uname: Linux 4.4.0-45-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.1 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: Sun Nov 6 14:00:22 2016 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [103c:2af7] InstallationDate: Installed on 2016-11-06 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: Hewlett-Packard 500-321 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-45-generic root=UUID=a3be56db-508b-49ea-9d57-7f8270d98e4e ro SourcePackage: xserver-xorg-video-intel UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/27/2014 dmi.bios.vendor: AMI dmi.bios.version: 80.18 dmi.board.name: 2AF7 dmi.board.vendor: Hewlett-Packard dmi.board.version: 1.04 dmi.chassis.asset.tag: MXX4320BPH dmi.chassis.type: 3 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnAMI:bvr80.18:bd06/27/2014:svnHewlett-Packard:pn500-321:pvr1.00:rvnHewlett-Packard:rn2AF7:rvr1.04:cvnHewlett-Packard:ct3:cvr: dmi.product.name: 500-321 dmi.product.version: 1.00 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Sun Nov 6 13:52:03 2016 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id9170 vendor ACI xserver.version: 2:1.18.3-1ubuntu2 ** Affects: xserver-xorg-video-intel (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 ubuntu xenial -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-intel in Ubuntu. https://bugs.launchpad.net/bugs/1639640 Title: black screen at boot until pressing power-off button? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1639640/+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 1521806] [NEW] undefined reference to glProgramUniform3fv when building opengl app
Public bug reported: A library which is being developed against the nvidia libGL.so fails to link against mesa's libGL.so. The linker complains: foo: undefined reference to `glProgramUniform1fv' foo: undefined reference to `glProgramUniform1i' foo: undefined reference to `glProgramUniform2fv' foo: undefined reference to `glProgramUniform3fv' foo: undefined reference to `glProgramUniform4fv' foo: undefined reference to `glProgramUniformMatrix3fv' foo: undefined reference to `glProgramUniformMatrix4fv' foo: undefined reference to `glXCreateContextAttribsARB' Is this expected behavior, punishing the developer for not using an extension loader, or something? Or should mesa export everything nvidia exports? Sounds like it's expected behavior, given http://sourceforge.net/p/mesa3d/mailman/message/26157363/ but I thought I'd file it in case some other OpenGL noob runs into it. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: libgl1-mesa-dev 10.1.3-0ubuntu0.4 ProcVersionSignature: Ubuntu 3.13.0-55.92-generic 3.13.11-ckt20 Uname: Linux 3.13.0-55-generic x86_64 NonfreeKernelModules: veth aufs xt_CHECKSUM iptable_mangle ipt_MASQUERADE iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack xt_tcpudp bridge stp llc iptable_filter ip_tables x_tables rfcomm bnep bluetooth coretemp crct10dif_pclmul crc32_pclmul ghash_clmulni_intel vmw_balloon aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd serio_raw vmwgfx ppdev ttm parport_pc lp parport drm shpchp mac_hid vmw_vmci i2c_piix4 psmouse vmw_pvscsi vmxnet3 mptspi e1000 floppy mptscsih mptbase pata_acpi ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 Date: Tue Dec 1 15:29:17 2015 ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: mesa UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: mesa (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- 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/1521806 Title: undefined reference to glProgramUniform3fv when building opengl app To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1521806/+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 1487748] Re: Touchpad not recognized in Aspire E15 e5-573g-59c3
Workaround: at boot, press F2 to get into BIOS, then set trackpad to Basic instead of Advanced. This even lets you scroll with a two-fingered gesture, and changes the output of cat /proc/bus/input/devices to: I: Bus=0011 Vendor=0002 Product=0007 Version=01b1 N: Name=SynPS/2 Synaptics TouchPad P: Phys=isa0060/serio1/input0 S: Sysfs=/devices/platform/i8042/serio1/input/input6 U: Uniq= H: Handlers=mouse1 event8 B: PROP=5 B: EV=b B: KEY=e520 61 0 0 0 0 B: ABS=66080001103 -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-input-synaptics in Ubuntu. https://bugs.launchpad.net/bugs/1487748 Title: Touchpad not recognized in Aspire E15 e5-573g-59c3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics/+bug/1487748/+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 1487748] [NEW] Touchpad not recognized in Aspire E15 e5-573g-59c3
Public bug reported: Live booting Ubuntu 15.04 via USB key worked, but touchpad and wifi didn't work, had to plug in a mouse and ethernet. This report is about the touchpad. cat /proc/bus/input/devices says I: Bus=0018 Vendor=06cb Product=2970 Version=0100 N: Name=SYN1B81:01 06CB:2970 UNKNOWN P: Phys= S: Sysfs=/devices/pci:00/INT3432:00/i2c-8/i2c-SYN1B81:01/0018:06CB:2970.0001/input/input14 U: Uniq= H: Handlers=mouse0 event13 B: PROP=5 B: EV=b B: KEY=6420 1 0 0 0 0 B: ABS=2608003 ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: xserver-xorg-input-synaptics 1.8.1-1ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3 Uname: Linux 3.19.0-15-generic x86_64 ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CasperVersion: 1.360 CurrentDesktop: Unity Date: Sat Aug 22 18:23:44 2015 DistUpgraded: Fresh install DistroCodename: vivid DistroVariant: ubuntu LiveMediaBuild: Ubuntu 15.04 Vivid Vervet - Release amd64 (20150422) MachineType: Acer Aspire E5-573G ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi file=/cdrom/preseed/username.seed boot=casper quiet splash --- SourcePackage: xserver-xorg-input-synaptics UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/17/2015 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.07 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: ZORO_BH dmi.board.vendor: Acer dmi.board.version: Type2 - A01 Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.07:bd03/17/2015:svnAcer:pnAspireE5-573G:pvrV3.72:rvnAcer:rnZORO_BH:rvrType2-A01BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.name: Aspire E5-573G dmi.product.version: V3.72 dmi.sys.vendor: Acer version.compiz: compiz 1:0.9.12.1+15.04.20150410.1-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.60-2 version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.2-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0-1ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917-1~exp1ubuntu2build1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2build1 xserver.bootTime: Sat Aug 22 09:32:26 2015 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 16620 vendor AUO xserver.version: 2:1.17.1-0ubuntu3 ** Affects: xserver-xorg-input-synaptics (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug ubuntu vivid -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-input-synaptics in Ubuntu. https://bugs.launchpad.net/bugs/1487748 Title: Touchpad not recognized in Aspire E15 e5-573g-59c3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics/+bug/1487748/+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 1314367] Re: Flickering with Ubuntu 14.04 and nvidia card reappeared
fwiw: I hit this using the latest from Nvidia's download site, and also using the xorg-edgers ppa ( 346.47-0ubuntu1-xedgers14.04.1 ). The flipping in the terminal seems to be at the same speed as the cursor blink. I only noticed it in gnome terminal. xterm does not exhibit the problem. My system's a Dell T7500 with a Geforce gtx 570 running somewhat up to date ubuntu 14.04.1 CCSMWorkaroundsForce synchronization between X and GLX seemed to help a bit initially, but the problem is still present enough to make gnome terminal nearly unusable. nvidia-settings -a GPUPowerMizerMode=1 seems to help more. With that, I haven't seen the flipping in my 30 seconds of extensive testing. Like Tom, I don't think I can install a new OS on this system, but I guess I might have time to boot the live cd sometime. -- 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/1314367 Title: Flickering with Ubuntu 14.04 and nvidia card reappeared To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1314367/+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 538691] Re: no versioned library symlinks provided for libGL in /usr/lib
google earth may not have had correct dependencies. -- 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/538691 Title: no versioned library symlinks provided for libGL in /usr/lib To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/538691/+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 1072403] Re: [GeForce 8600M GT] Unity and GnomeShell hang or crash with nouveau kernel error messages fail ttm_validate, validate vram_list and validate: -12
The default install of Ubuntu 13.10 seems to have this problem for me on an old Dell Optiplex 740 with built-in GeForce 6150 LE. Dec 23 22:34:01 ath64 kernel: [ 5663.040020] nouveau E[Xorg[25847]] reloc wait_idle failed: -16 Dec 23 22:34:01 ath64 kernel: [ 5663.040028] nouveau E[Xorg[25847]] reloc apply: -16 Dec 23 22:34:02 ath64 whoopsie[945]: online Dec 23 22:34:46 ath64 kernel: [ 5708.120570] nouveau E[Xorg[25847]] fail ttm_validate Dec 23 22:34:46 ath64 kernel: [ 5708.120581] nouveau E[Xorg[25847]] validate vram_list Dec 23 22:34:46 ath64 kernel: [ 5708.120584] nouveau E[Xorg[25847]] validate: -16 Dec 23 22:35:32 ath64 kernel: [ 5753.249571] nouveau E[ PGRAPH][:00:05.0] ERROR nsource: ILLEGAL_MTHD nstatus: BAD_ARGUMENT PROTECTION_FAULT Dec 23 22:35:32 ath64 kernel: [ 5753.249581] nouveau E[ PGRAPH][:00:05.0] ch 1 [0x00048000 Xorg[25847]] subc 0 class 0x0039 mthd 0x0480 data 0x015f1000 Dec 23 22:35:32 ath64 kernel: [ 5753.249599] nouveau E[ PGRAPH][:00:05.0] ERROR nsource: ILLEGAL_MTHD nstatus: BAD_ARGUMENT PROTECTION_FAULT Dec 23 22:35:32 ath64 kernel: [ 5753.249605] nouveau E[ PGRAPH][:00:05.0] ch 1 [0x00048000 Xorg[25847]] subc 0 class 0x0039 mthd 0x0484 data 0x015f1000 ... Dec 23 22:36:09 ath64 kernel: [ 5791.241800] nouveau W[ PFIFO][:00:05.0] unknown intr 0x0001, ch 1 Dec 23 22:36:09 ath64 kernel: [ 5791.241806] nouveau W[ PFIFO][:00:05.0] unknown intr 0x0001, ch 1 Dec 23 22:36:09 ath64 kernel: [ 5791.241811] nouveau E[ PFIFO][:00:05.0] still angry after 101 spins, halt ... Dec 24 07:36:05 ath64 kernel: [ 1101.587875] nouveau E[Xorg[1039]] fail ttm_validate Dec 24 07:36:05 ath64 kernel: [ 1101.587883] nouveau E[Xorg[1039]] validate vram_list Dec 24 07:36:05 ath64 kernel: [ 1101.587885] nouveau E[Xorg[1039]] validate: -12 Dec 24 07:36:05 ath64 kernel: [ 1101.588144] nouveau E[Xorg[1039]] fail ttm_validate Dec 24 07:36:05 ath64 kernel: [ 1101.588146] nouveau E[Xorg[1039]] validate vram_list Dec 24 07:36:05 ath64 kernel: [ 1101.588148] nouveau E[Xorg[1039]] validate: -12 Dec 24 07:36:20 ath64 kernel: [ 1116.588016] nouveau E[Xorg[1039]] reloc wait_idle failed: -16 Dec 24 07:36:20 ath64 kernel: [ 1116.588023] nouveau E[Xorg[1039]] reloc apply: -16 Dec 24 07:36:20 ath64 kernel: [ 1116.592006] [sched_delayed] sched: RT throttling activated Dec 24 07:36:50 ath64 kernel: [ 1146.588016] nouveau E[Xorg[1039]] reloc wait_idle failed: -16 Dec 24 07:36:50 ath64 kernel: [ 1146.588023] nouveau E[Xorg[1039]] reloc apply: -16 Dec 24 07:39:11 ath64 gnome-session[1726]: Gdk-WARNING: gnome-session: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.#012 The system seemed unstable. Leaving it on overnight, the display was dead (although ctl-alt-f1 was able to take me to the console); after rebooting, it failed to configure and build wine (!). Installing the proprietary Nvidia seems to help; building wine now succeeds, and there are no warnings in syslog. So, at least on this old nvidia hardware, xserver-xorg-video-nouveau 1:1.0.9-2ubuntu1 does not seem production-ready for even light use. I'm ok with the proprietary driver, but it would be nice to run untainted someday. ** Attachment added: syslog.txt https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/1072403/+attachment/3935177/+files/syslog.txt -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-nouveau in Ubuntu. https://bugs.launchpad.net/bugs/1072403 Title: [GeForce 8600M GT] Unity and GnomeShell hang or crash with nouveau kernel error messages fail ttm_validate, validate vram_list and validate: -12 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/1072403/+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 1033533] Re: Xorg crashed with SIGABRT: exaMemcpyBox with src=0x0 on nouveau with SW rendering
This is 100% reproducible here. All I have to do is run 'make check' in wine, tell gdb to attach to X and ignore SIGPIPE, and in a few minutes, gdb says e.g. Program received signal SIGSEGV, Segmentation fault. 0x7f74ae864bd5 in ?? () from /lib/x86_64-linux-gnu/libc.so.6 (gdb) bt #0 0x7f74ae864bd5 in ?? () from /lib/x86_64-linux-gnu/libc.so.6 #1 0x7f74ac53985e in memcpy (__len=2700, __src=0x0, __dest=0x7f74b2ba40d0) at /usr/include/x86_64-linux-gnu/bits/string3.h:51 #2 exaMemcpyBox (pbox=pbox@entry=0x7fffd5a2fbc0, src=0x0, src_pitch=2752, dst=0x7f74b2ba40d0 h\377\255\256t\177, dst_pitch=2700, pPixmap=0x7f74b2b80e50) at ../../exa/exa_migration_classic.c:59 ... This is on a stock install of 13.04 daily from April 21 or so. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-nouveau in Ubuntu. https://bugs.launchpad.net/bugs/1033533 Title: Xorg crashed with SIGABRT: exaMemcpyBox with src=0x0 on nouveau with SW rendering To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/1033533/+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 792278] Re: Often xorg freezes with EQ overflowing
My laptop just had this same hang. syslog says: Jan 4 18:27:36 i5lap kernel: [ 9525.635064] NVRM: Xid (:01:00): 13, 0004 8597 1b0c 1000f010 0040 Xorg.0.log says [ 9544.565] (WW) NVIDIA(0): WAIT (2, 6, 0x8000, 0x09f0, 0x3570) [ 9551.272] [mi] EQ overflowing. The server is probably stuck in an infinite loop. [ 9551.272] Backtrace: [ 9551.326] 0: /usr/bin/X (xorg_backtrace+0x37) [0x80a66f7] [ 9551.326] 1: /usr/bin/X (mieqEnqueue+0x1d1) [0x80a06b1] [ 9551.326] 2: /usr/bin/X (xf86PostMotionEventM+0xb0) [0x80c7e60] [ 9551.326] 3: /usr/lib/xorg/modules/input/evdev_drv.so (0x221000+0x35ed) [0x2245ed] [ 9551.327] 4: /usr/lib/xorg/modules/input/evdev_drv.so (0x221000+0x531d) [0x22631d] [ 9551.327] 5: /usr/lib/xorg/modules/input/evdev_drv.so (0x221000+0x5b85) [0x226b85] [ 9551.327] 6: /usr/bin/X (0x8048000+0x6cb81) [0x80b4b81] [ 9551.327] 7: /usr/bin/X (0x8048000+0x12d2a2) [0x81752a2] [ 9551.327] 8: (vdso) (__kernel_sigreturn+0x0) [0x4f1400] [ 9551.327] 9: /usr/lib/i386-linux-gnu/xorg/extra-modules/nvidia_drv.so (0x12d8000+0x5b8d2) [0x13338d2] It locked X hard. I can still log in over the network. I'll try using apport, but for the moment, here are some basic info: Linux i5lap 3.0.0-14-generic #23-Ubuntu SMP Mon Nov 21 20:34:47 UTC 2011 i686 i686 i386 GNU/Linux Ubuntu 11.10 \n \l nvidia-current 280.13-0ubuntu6 -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers in Ubuntu. https://bugs.launchpad.net/bugs/792278 Title: Often xorg freezes with EQ overflowing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/792278/+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 792278] Re: Often xorg freezes with EQ overflowing
Sigh. apport-cli -u 792278 failed after Authorize application to access Launchpad on your behalf with Launchpad requires a REFERER header to perform this action. Guess I'll reboot. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers in Ubuntu. https://bugs.launchpad.net/bugs/792278 Title: Often xorg freezes with EQ overflowing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/792278/+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 792598] Re: XWarpPointer sends wrong raw mouse input event - jumping mouse when XInput2 in use
I think it's fixed in 11.10, judging by the initial test case. (I haven't tried Wine, but my guess is that would be happy, too.) -- 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/792598 Title: XWarpPointer sends wrong raw mouse input event - jumping mouse when XInput2 in use To manage notifications about this bug go to: https://bugs.launchpad.net/wine/+bug/792598/+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 792598] Re: XWarpPointer sends wrong raw mouse input event - jumping mouse when XInput2 in use
Yes, I know, I would have to go back to an old version of wine to test with that. (I suppose that's what Bryce wanted, so I probably will soon.) But the original freedesktop.org bug report had a nice non-wine testcase that now passes. -- 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/792598 Title: XWarpPointer sends wrong raw mouse input event - jumping mouse when XInput2 in use To manage notifications about this bug go to: https://bugs.launchpad.net/wine/+bug/792598/+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 882483] Re: Xorg freeze
-- 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/882483 Title: Xorg freeze To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/882483/+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 882483] [NEW] Xorg freeze
Public bug reported: Happened after nine runs of the wine test suite. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: xorg 1:7.6+7ubuntu7 ProcVersionSignature: Ubuntu 3.0.0-13.21-generic-pae 3.0.6 Uname: Linux 3.0.0-13-generic-pae i686 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86 Kernel Module 280.13 Wed Jul 27 16:55:43 PDT 2011 GCC version: gcc version 4.6.1 (Ubuntu/Linaro 4.6.1-9ubuntu3) .tmp.unity.support.test.0: ApportVersion: 1.23-0ubuntu3 Architecture: i386 CompizPlugins: [core,bailer,detection,composite,opengl,compiztoolbox,decor,grid,vpswitch,resize,regex,mousepoll,imgpng,place,session,move,snap,animation,gnomecompat,wall,unitymtgrabhandles,fade,workarounds,expo,ezoom,scale,unityshell] CompositorRunning: compiz Date: Thu Oct 27 02:47:53 2011 DistUpgraded: Fresh install DistroCodename: oneiric DistroVariant: ubuntu ExtraDebuggingInterest: Yes, whatever it takes to get this fixed in Ubuntu GpuHangFrequency: This is the first time GpuHangReproducibility: I don't know GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: nVidia Corporation GT216 [GeForce GT 220] [10de:0a20] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Device [196e:0699] InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release i386 (20111012) JockeyStatus: xorg:nvidia_current - NVIDIA accelerated graphics driver (Proprietary, Disabled, Not in use) xorg:nvidia_current_updates - NVIDIA accelerated graphics driver (post-release updates) (Proprietary, Enabled, In use) MachineType: System manufacturer P5K PRO ProcEnviron: PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0.0-13-generic-pae root=UUID=9e03df19-4b8c-4f29-a528-0d7c9d2abf3c ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) XorgConf: Section Device Identifier Default Device Option NoLogoTrue EndSection dmi.bios.date: 04/18/2008 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1002 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5K PRO dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1002:bd04/18/2008:svnSystemmanufacturer:pnP5KPRO:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5KPRO:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: P5K PRO dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz 1:0.9.6+bzr20110929-0ubuntu5 version.libdrm2: libdrm2 2.4.26-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 7.11-0ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 7.11-0ubuntu3 version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A version.xserver-xorg: xserver-xorg 1:7.6+7ubuntu7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.6.0-1ubuntu13 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.14.99~git20110811.g93fc084-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.15.901-1ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:0.0.16+git20110411+8378443-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug compiz-0.9 freeze i386 oneiric running-unity 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/882483 Title: Xorg freeze To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/882483/+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 567696] Re: [mi] EQ overflowing. The server is probably stuck in an infinite loop
FWIW, I saw nearly exactly the same backtrace in a Natty system (using kernel 2.6.38-11-generic-pae) just now: [214132.465] [mi] EQ overflowing. The server is probably stuck in an infinite loop. [214132.465] Backtrace: [214132.465] 0: /usr/bin/X (xorg_backtrace+0x3b) [0x80eab2b] [214132.465] 1: /usr/bin/X (mieqEnqueue+0x1ab) [0x80e9d0b] [214132.465] 2: /usr/bin/X (xf86PostMotionEventM+0xbf) [0x80c4b6f] [214132.481] 3: /usr/lib/xorg/modules/input/evdev_drv.so (0xb4d15000+0x368f) [0xb4d1868f] [214132.481] 4: /usr/lib/xorg/modules/input/evdev_drv.so (0xb4d15000+0x54e9) [0xb4d1a4e9] [214132.481] 5: /usr/lib/xorg/modules/input/evdev_drv.so (0xb4d15000+0x5d4d) [0xb4d1ad4d] [214132.481] 6: /usr/bin/X (0x8048000+0x6b41f) [0x80b341f] [214132.481] 7: /usr/bin/X (0x8048000+0x12ddb6) [0x8175db6] [214132.481] 8: (vdso) (__kernel_sigreturn+0x0) [0xb777e400] (Not sure what triggered it. I'd been using vncviewer, appletviewer, chrome, and cygwin sed.exe in wine.) -- 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/567696 Title: [mi] EQ overflowing. The server is probably stuck in an infinite loop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/567696/+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 792598]
Only once enough people have the new X, which will happen in about 1-2 years (if we feel adventurous) or never (if we feel conservative). -- 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/792598 Title: XWarpPointer sends wrong raw mouse input event To manage notifications about this bug go to: https://bugs.launchpad.net/wine/+bug/792598/+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 792598] Re: XWarpPointer sends wrong raw mouse input event
Wine has not fixed this bug; they've worked around it with great effort. Fixing X is still worth doing, so other apps don't have to do what Wine did. -- 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/792598 Title: XWarpPointer sends wrong raw mouse input event To manage notifications about this bug go to: https://bugs.launchpad.net/wine/+bug/792598/+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 792598]
In today's git (wine-1.3.22-255-g4c0c0d3) I still get nasty jumping in the Quake 3 Arena demo menu. -- 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/792598 Title: XWarpPointer sends wrong raw mouse input event To manage notifications about this bug go to: https://bugs.launchpad.net/wine/+bug/792598/+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 792598] Re: XWarpPointer sends wrong raw mouse input event
We'll probably have more wine bugs to link to this one. I don't think it's time to close this yet. -- 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/792598 Title: XWarpPointer sends wrong raw mouse input event To manage notifications about this bug go to: https://bugs.launchpad.net/wine/+bug/792598/+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 792598] [NEW] XWarpPointer sends wrong raw mouse input event
Public bug reported: From https://bugs.freedesktop.org/show_bug.cgi?id=30068 XWarpPointer should generate Motion but not RawMotion (it's RAW, right?). And it definitely generates wrong RawMotion, because it contains valuators' values equal to absolute screen coordinates of mouse move target (and that is definitely wrong, since all other mouse events are relative). So, my point is that XWarpPointer shouldn't generate RawMotion events at all. He also includes a small testcase. Happens in Ubuntu 10.10 and 11.04 (or any Ubuntu with XInput2 support). Affects apps that use xinput2, e.g. wine as of roughly wine-1.3.20 or later. Drives users nuts... the main menu of Bioshock Demo and many other games is nearly completely useless because of the jumping mouse when xinput2 is used; see http://bugs.winehq.org/show_bug.cgi?id=27380 The lead Wine developer, Alexandre Julliard, has been waiting for this bug to be fixed for some time now. He's trying to work around it, without much luck so far. ** Affects: xorg-server (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/792598 Title: XWarpPointer sends wrong raw mouse input event ___ 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 626321]
World of Goo (demo) also doesn't restore its resolution when it quits. -- 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/626321 Title: X.org server should keep track of and restore its initial (desktop) resolution and refresh rate ___ 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 546525] Re: Xorg crash with SIGPIPE after successful login
This is now happening for me on *every* run of 3dmark2000. -- Xorg crash with SIGPIPE after successful login https://bugs.launchpad.net/bugs/546525 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers 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 546525] Re: Xorg crash with SIGPIPE after successful login
Got a SIGPIPE again, this time while wineboot was running (just as 3dmark2000 was starting): Program received signal SIGPIPE, Broken pipe. 0xb7769430 in __kernel_vsyscall () (gdb) bt #0 0xb7769430 in __kernel_vsyscall () #1 0xb754ea61 in writev () from /lib/tls/i686/cmov/libc.so.6 #2 0x080ad40e in ?? () #3 0x080acb5f in ?? () #4 0x080a84d6 in ?? () #5 0x080a8f3f in FlushAllOutput () #6 0x0807230d in ?? () #7 0x08066d7a in _start () but this time I tried handle SIGPIPE pass cont and X didn't crash. So perhaps not all SIGPIPEs are crashy. -- Xorg crash with SIGPIPE after successful login https://bugs.launchpad.net/bugs/546525 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers 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 546525] Re: Xorg crash with SIGPIPE after successful login
I think this affects me - in my case, the SIGPIPE comes when I run 3dmark2000 or 3dmark06 in wine. It only happens once in a while, but it's happened three times today. Program received signal SIGPIPE, Broken pipe. 0xb7769430 in __kernel_vsyscall () (gdb) bt #0 0xb7769430 in __kernel_vsyscall () #1 0xb754ea61 in writev () from /lib/tls/i686/cmov/libc.so.6 #2 0x080ad40e in ?? () #3 0x080acb5f in ?? () #4 0x080a84d6 in ?? () #5 0x080a8f3f in FlushAllOutput () #6 0x080a8f71 in FlushIfCriticalOutputPending () #7 0x080723a5 in ?? () #8 0x08066d7a in _start () I've previously posted about this at http://www.nvnews.net/vbulletin/showthread.php?p=2245689 and http://www.mail-archive.com/ubunt...@lists.ubuntu.com/msg00424.html before I tried gdb; the stack trace from xorg.log looks different. When I did 'cont' after the SIGPIPE, 3dmark2000 happily continues, but I think without gdb there, the server aborts. -- Xorg crash with SIGPIPE after successful login https://bugs.launchpad.net/bugs/546525 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers 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 546525] Re: Xorg crash with SIGPIPE after successful login
Oh, sorry, I should add that I've seen Xorg crash on 3d benchmarks on wine on Ubuntu 10.04 32 bit with the 195.36.15 drivers that come with Ubuntu and nvidia GT 220 and GT 240 cards, as well as on latest gentoo with gtx 295 cards. -- Xorg crash with SIGPIPE after successful login https://bugs.launchpad.net/bugs/546525 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers 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 519576] Re: Race condition in libXext
I'm hitting this with Karmic + wine + steam a lot on my new i7. Happily, I can move to Lucid beta, but there are a lot of Karmic users out there who can't... -- Race condition in libXext https://bugs.launchpad.net/bugs/519576 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to libxext 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
