[Ubuntu-x-swat] [Bug 1722897] Re: Unexpected behavior with Wayland desktop
This is urgent issue because ubuntu will GA on Oct/19/17. Is it possible to be get fixed in GA ? thanks very much! -- 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/1722897 Title: Unexpected behavior with Wayland desktop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1722897/+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 1722998] [NEW] VMware memory allocation process ... HUGE RESOURCE HIT ?
Public bug reported: Hi, I am writing this with concerns on the way RAM(memory) is handled by the same software(VMware Workstation) across different versions of the Ubuntu OS. I am however unsure if the concern i am reporting here is actually a Bug ... or ... a feature that has been withdrawn on purpose ... or ... a feature that's got overlooked from kernel to kernel updates. How did i stumble upon this issue ? My primary daily driver OS is Ubuntu 14.04 (ker. 3.13), i use VMware workstation on this host to run Windows 7 to run my work software which does not have a linux version. While my VM guest*Windows 7) has been allocated 8GB of RAM the RAM usage on my Host shows no more than 3-4GB. I while back i had installed Ubuntu 16.04 on an adjacent partition and tried running a copy of the exact same VM guest and to my shock saw that right from boot the entire 8GB of RAM gets blocked on the host system. What was earlier 3-4 GB of RAM consumption in Ubuntu 14.04 now shot up to a whopping 10-11GB in Ubuntu 16.04. A HUGE resource hit. Now i am test driving Deepin OS i find the same resource hit on this OS too just like the one experienced on Ubuntu 16.04 ... 10-12 GB of RAM is affected the moment i boot up my vm machine. I am using an exact same copy from Ubuntu 14.04 to run even here. What additional test's have i done to probe this issue ? I have tested this HUGE RESOURCE HIT on the following versions ... I used the exact same version of VMware Workstation on my test OS's as well as the latest version of VMware workstation, following are the findings. software version tested on ... VMware Workstation 12.1.0 VMware Workstation 14 OS versions tested on ... Ubuntu 14.04 (Ker. 3.13) Ubuntu 15.04 (Ker. 3.19) Ubuntu 15.10 (Ker. 4.2) tests on the above OS's show that the memory is efficiently handled and the overall memory consumption(both Host and Guest VM included)is roughly around 4 GB even though the VM is configured with 8GB of RAM UbuntuGnome 16.04 (Ker. 4.4) Deepin 15.4.1 (Ker. 4.9) UbuntuGnome 17.04 (Ker. 4.10) However my tests on these OS resulted in a HUGE RESOURCE HIT ... the overall memory consumption(both Host and Guest VM included) here has been a WHOPPING 10-12GB. What proof do you have of this inconsistency ? I am attaching a screenshot with the memory consumed marked side by side. I have Deepin OS 15.4.1(Ker. 4.9) and Ubuntu 14.04(Ker. 3.13) on my system ... one demonstrating the resource hog i am reporting ... and ... the other demonstrating the efficient use of system resources. So if you require any logs or commands to be run out of both this environments to further probe this resource leakage please let me know the direct commands and i'll provide the respective outputs to help you identify the issue. PS : I am not a geek but rather consider myself as a power user, hence direct commands to collect additional info out of the 2 environments would help. thanks for looking. ** Affects: xserver-xorg-video-vmware (Ubuntu) Importance: Undecided Status: New ** Attachment added: "Memory Resource Hit.png" https://bugs.launchpad.net/bugs/1722998/+attachment/4968265/+files/Memory%20Resource%20Hit.png -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-vmware in Ubuntu. https://bugs.launchpad.net/bugs/1722998 Title: VMware memory allocation process ... HUGE RESOURCE HIT ? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-vmware/+bug/1722998/+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 1722940] Re: 17.10 boots to black screen with cursor
*** This bug is a duplicate of bug 1722988 *** https://bugs.launchpad.net/bugs/1722988 Be warned of #3 - reboot brings terminal login :*( Ok so after steps from #3, this seems to have fixed it: sudo dpkg-reconfigure gdm3 select gdm3, push enter Reboot -- 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/1722940 Title: 17.10 boots to black screen with cursor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1722940/+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 1722940] Re: 17.10 boots to black screen with cursor
*** This bug is a duplicate of bug 1722988 *** https://bugs.launchpad.net/bugs/1722988 ** This bug has been marked a duplicate of bug 1722988 Crash, black screen with lightdm -- 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/1722940 Title: 17.10 boots to black screen with cursor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1722940/+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 1722940] Re: 17.10 boots to black screen with cursor
Workaround (works for me) to get login screen back, switch from lightdm to gdm: sudo systemctl disable lightdm sudo systemctl stop lightdm sudo systemctl enable gdm #Seems to fail sudo systemctl start gdm h/t @judd for the tip on https://forum.antergos.com/topic/3000/unable-to-log-in-black-screen-with-cursor-where-lightdm-used-to-be/10 -- 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/1722940 Title: 17.10 boots to black screen with cursor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1722940/+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 1722987] [NEW] screen brightness control is backwards
Public bug reported: Increase brightness key on my keyboard (func-f3) makes the screen more dim. Decrease brightness key on my keyboard (func-f2) makes the screen more bright. The gnome-shell on-screen display of brightness is backwards also. I see on google search results that this was a problem with older kernels. I guess the problem is back / possible regression. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: xorg 1:7.7+19ubuntu2 ProcVersionSignature: Ubuntu 4.13.0-15.16-generic 4.13.4 Uname: Linux 4.13.0-15-generic x86_64 ApportVersion: 2.20.7-0ubuntu2 Architecture: amd64 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Oct 11 20:52:44 2017 DistUpgraded: Fresh install DistroCodename: artful DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display [8086:0f31] (rev 0e) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Atom Processor Z36xxx/Z37xxx Series Graphics & Display [103c:2209] InstallationDate: Installed on 2017-10-08 (3 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 005: ID 0cf3:3121 Atheros Communications, Inc. Bus 001 Device 003: ID 1a40:0101 Terminus Technology Inc. Hub Bus 001 Device 002: ID 05c8:036e Cheng Uei Precision Industry Co., Ltd (Foxlink) Webcam Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Hewlett-Packard HP Pavilion 11 x360 PC ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-15-generic.efi.signed root=UUID=3db6d4f1-3d95-4b8c-93d1-ab9465947670 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/11/2014 dmi.bios.vendor: Insyde dmi.bios.version: F.15 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 2209 dmi.board.vendor: Hewlett-Packard dmi.board.version: 57.37 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.15:bd11/11/2014:svnHewlett-Packard:pnHPPavilion11x360PC:pvr096F100800405F00010420180:rvnHewlett-Packard:rn2209:rvr57.37:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV X=MIN dmi.product.name: HP Pavilion 11 x360 PC dmi.product.version: 096F100800405F00010420180 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz N/A 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.3-1ubuntu7 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 (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 in Ubuntu. https://bugs.launchpad.net/bugs/1722987 Title: screen brightness control is backwards To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1722987/+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 1722940] Re: 17.10 boots to black screen with cursor
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: xorg (Ubuntu) Status: New => Confirmed -- 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/1722940 Title: 17.10 boots to black screen with cursor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1722940/+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 1722974] Re: Wayland xorg not scalling screens properly
** Description changed: When I try scale the screen on my xps 15 9560 core i7 screen 4k the image start to flap and sometimes the screen stay all black. - I tried use the nvidia driver but still doesn work and when I try scale - the apply using the settings option the button disapear. + I tried use the nvidia driver but still doesn't work and when I try + scale using the settings option, the button "apply" disapear. + + Additional monitor used: Dell U2715Hc with 2K resolution. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: xorg 1:7.7+19ubuntu2 ProcVersionSignature: Ubuntu 4.13.0-15.16-generic 4.13.4 Uname: Linux 4.13.0-15-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.90 Tue Sep 19 19:17:35 PDT 2017 - GCC version: gcc version 7.2.0 (Ubuntu 7.2.0-8ubuntu2) + NVRM version: NVIDIA UNIX x86_64 Kernel Module 384.90 Tue Sep 19 19:17:35 PDT 2017 + GCC version: gcc version 7.2.0 (Ubuntu 7.2.0-8ubuntu2) ApportVersion: 2.20.7-0ubuntu2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Oct 12 12:50:54 2017 DistUpgraded: Fresh install DistroCodename: artful DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: - Intel Corporation Device [8086:591b] (rev 04) (prog-if 00 [VGA controller]) -Subsystem: Dell Device [1028:07be] -Subsystem: Dell GP107M [GeForce GTX 1050 Mobile] [1028:07be] + Intel Corporation Device [8086:591b] (rev 04) (prog-if 00 [VGA controller]) + Subsystem: Dell Device [1028:07be] + Subsystem: Dell GP107M [GeForce GTX 1050 Mobile] [1028:07be] InstallationDate: Installed on 2017-10-10 (1 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) MachineType: Dell Inc. XPS 15 9560 ProcEnviron: - LANGUAGE=en_AU:en - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=en_AU.UTF-8 - SHELL=/bin/bash + LANGUAGE=en_AU:en + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_AU.UTF-8 + SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-15-generic root=UUID=cdd76ef8-2ee7-4962-b264-6671cf81976b ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/30/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.0 dmi.board.name: 05FFDN dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.5.0:bd08/30/2017:svnDellInc.:pnXPS159560:pvr:rvnDellInc.:rn05FFDN:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9560 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A 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.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu7 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 -- 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/1722974 Title: Wayland xorg not scalling screens properly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1722974/+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 1722897] Re: Unexpected behavior with Wayland desktop
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: xorg (Ubuntu) Status: New => Confirmed -- 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/1722897 Title: Unexpected behavior with Wayland desktop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1722897/+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 1722974] [NEW] Wayland xorg not scalling screens properly
Public bug reported: When I try scale the screen on my xps 15 9560 core i7 screen 4k the image start to flap and sometimes the screen stay all black. I tried use the nvidia driver but still doesn work and when I try scale the apply using the settings option the button disapear. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: xorg 1:7.7+19ubuntu2 ProcVersionSignature: Ubuntu 4.13.0-15.16-generic 4.13.4 Uname: Linux 4.13.0-15-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.90 Tue Sep 19 19:17:35 PDT 2017 GCC version: gcc version 7.2.0 (Ubuntu 7.2.0-8ubuntu2) ApportVersion: 2.20.7-0ubuntu2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Oct 12 12:50:54 2017 DistUpgraded: Fresh install DistroCodename: artful DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:591b] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:07be] Subsystem: Dell GP107M [GeForce GTX 1050 Mobile] [1028:07be] InstallationDate: Installed on 2017-10-10 (1 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) MachineType: Dell Inc. XPS 15 9560 ProcEnviron: LANGUAGE=en_AU:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-15-generic root=UUID=cdd76ef8-2ee7-4962-b264-6671cf81976b ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/30/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.0 dmi.board.name: 05FFDN dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.5.0:bd08/30/2017:svnDellInc.:pnXPS159560:pvr:rvnDellInc.:rn05FFDN:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9560 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A 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.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu7 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 (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 in Ubuntu. https://bugs.launchpad.net/bugs/1722974 Title: Wayland xorg not scalling screens properly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1722974/+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 1722940] [NEW] 17.10 boots to black screen with cursor
Public bug reported: After the following update Start-Date: 2017-10-11 21:02:12 Commandline: aptdaemon role='role-commit-packages' sender=':1.136' Install: fonts-gubbi:amd64 (1.3-3, automatic), fonts-indic:amd64 (2:1.2, automatic), fonts-beng-extra:amd64 (1.0-6, automatic), fonts-deva:amd64 (2:1.2, automatic), fonts-samyak-deva:amd64 (1.2.2-4, automatic), fonts-telu-extra:amd64 (2.0-4, automatic), fonts-smc:amd64 (6.0-1, automatic), fonts-gargi:amd64 (2.0-4, automatic), fonts-deva-extra:amd64 (3.0-4, automatic), fonts-kalapi:amd64 (1.0-2, automatic), linux-image-extra-4.13.0-15-generic:amd64 (4.13.0-15.16, automatic), fonts-navilu:amd64 (1.2-2, automatic), linux-tools-4.13.0-15-generic:amd64 (4.13.0-15.16, automatic), fonts-orya:amd64 (2:1.2, automatic), linux-headers-4.13.0-15-generic:amd64 (4.13.0-15.16, automatic), fonts-pagul:amd64 (1.0-7, automatic), fonts-knda:amd64 (2:1.2, automatic), fonts-sahadeva:amd64 (1.0-4, automatic), fonts-lohit-deva:amd64 (2.95.4-2, automatic), fonts-taml:amd64 (2:1.3, automatic), fonts-samyak-taml:amd64 (1.2.2-4, automatic), fonts-telu:amd64 (2:1.2, automatic), fonts-lohit-orya:amd64 (2.91.2-1, automatic), linux-headers-4.13.0-15:amd64 (4.13.0-15.16, automatic), fonts-lohit-knda:amd64 (2.5.4-1, automatic), fonts-gujr:amd64 (2:1.2, automatic), fonts-samyak-gujr:amd64 (1.2.2-4, automatic), linux-tools-4.13.0-15:amd64 (4.13.0-15.16, automatic), fonts-nakula:amd64 (1.0-3, automatic), fonts-lohit-beng-bengali:amd64 (2.91.5-1, automatic), fonts-orya-extra:amd64 (2.0-5, automatic), fonts-mlym:amd64 (2:1.2, automatic), fonts-lohit-taml:amd64 (2.91.3-1, automatic), fonts-beng:amd64 (2:1.2, automatic), fonts-samyak-mlym:amd64 (1.2.2-4, automatic), fonts-lohit-telu:amd64 (2.5.5-1, automatic), fonts-gujr-extra:amd64 (1.0-6, automatic), linux-image-4.13.0-15-generic:amd64 (4.13.0-15.16, automatic), fonts-lohit-beng-assamese:amd64 (2.91.5-1, automatic), fonts-lohit-gujr:amd64 (2.92.4-2, automatic), linux-signed-image-4.13.0-15-generic:amd64 (4.13.0-15.16, automatic), fonts-sarai:amd64 (1.0-2, automatic), fonts-lohit-mlym:amd64 (2.92.2-1, automatic), fonts-lohit-taml-classical:amd64 (2. 5.4-1, automatic) Upgrade: libgraphicsmagick-q16-3:amd64 (1.3.26-12, 1.3.26-13), libunity-settings-daemon1:amd64 (15.04.1+17.04.20170619-0ubuntu3, 15.04.1+17.10.20171003-0ubuntu1), libmpx0:amd64 (5.4.1-13ubuntu1, 5.5.0-1ubuntu1), empathy-common:amd64 (3.25.90-0ubuntu1, 3.25.90+really3.12.14-0ubuntu1), libgcj17:amd64 (6.4.0-7ubuntu1, 6.4.0-8ubuntu1), gnome-control-center-data:amd64 (1:3.26.1-0ubuntu1, 1:3.26.1-0ubuntu3), libgcc-5-dev:amd64 (5.4.1-13ubuntu1, 5.5.0-1ubuntu1), poppler-utils:amd64 (0.57.0-2ubuntu2, 0.57.0-2ubuntu4), postfix:amd64 (3.2.2-1, 3.2.3-1), libseccomp2:amd64 (2.3.1-2.1ubuntu2, 2.3.1-2.1ubuntu3), gnome-settings-daemon-schemas:amd64 (3.26.1-0ubuntu1, 3.26.1-0ubuntu3), unity-schemas:amd64 (7.5.0+17.10.20170925.1-0ubuntu1, 7.5.0+17.10.20171010-0ubuntu1), update-manager-core:amd64 (1:17.10.10, 1:17.10.11), libsemanage1:amd64 (2.7-1, 2.7-2), linux-headers-generic:amd64 (4.13.0.12.13, 4.13.0.15.16), gnome-session-common:amd64 (3.26.0-0ubuntu2, 3.26.1-0ubuntu3), unity-session:amd64 (3.26. 0-0ubuntu2, 3.26.1-0ubuntu3), gir1.2-mutter-1:amd64 (3.26.1-1, 3.26.1-2), gnome-control-center:amd64 (1:3.26.1-0ubuntu1, 1:3.26.1-0ubuntu3), linux-libc-dev:amd64 (4.13.0-12.13, 4.13.0-15.16), gnome-software-plugin-snap:amd64 (3.26.0-0ubuntu3, 3.26.1-0ubuntu1), va-driver-all:amd64 (1.8.3-1, 1.8.3-2), linux-image-generic:amd64 (4.13.0.12.13, 4.13.0.15.16), cpp-5:amd64 (5.4.1-13ubuntu1, 5.5.0-1ubuntu1), cpp-6:amd64 (6.4.0-7ubuntu1, 6.4.0-8ubuntu1), gsettings-ubuntu-schemas:amd64 (0.0.7+17.04.20161109-0ubuntu1, 0.0.7+17.10.20170922-0ubuntu1), update-manager:amd64 (1:17.10.10, 1:17.10.11), postfix-sqlite:amd64 (3.2.2-1, 3.2.3-1), libpoppler-qt4-4:amd64 (0.57.0-2ubuntu2, 0.57.0-2ubuntu4), linux-signed-image-generic:amd64 (4.13.0.12.13, 4.13.0.15.16), gnome-software:amd64 (3.26.0-0ubuntu3, 3.26.1-0ubuntu1), libmutter-1-0:amd64 (3.26.1-1, 3.26.1-2), ubuntu-standard:amd64 (1.402, 1.403), gir1.2-accountsservice-1.0:amd64 (0.6.42-0ubuntu2, 0.6.42-0ubuntu3), nodejs:amd64 (6.11.2~dfsg-3ubuntu1, 6.11.4~dfsg-1ubuntu1), ubuntu-session:amd64 (3.26.0-0ubuntu2, 3.26.1-0ubuntu3), gnome-orca:amd64 (3.26.0-1ubuntu1, 3.26.0-1ubuntu2), ubuntu-desktop:amd64 (1.402, 1.403), gnome-settings-daemon:amd64 (3.26.1-0ubuntu1, 3.26.1-0ubuntu3), libgfortran-5-dev:amd64 (5.4.1-13ubuntu1, 5.5.0-1ubuntu1), unity:amd64 (7.5.0+17.10.20170925.1-0ubuntu1, 7.5.0+17.10.20171010-0ubuntu1), libasan2:amd64 (5.4.1-13ubuntu1, 5.5.0-1ubuntu1), libasan3:amd64 (6.4.0-7ubuntu1, 6.4.0-8ubuntu1), gdm3:amd64 (3.26.0-1ubuntu1, 3.26.1-3ubuntu2), libwmf0.2-7:amd64 (0.2.8.4-10.6ubuntu1, 0.2.8.4-10.6ubuntu2), xkb-data:amd64 (2.19-1ubuntu1, 2.19-1.1ubuntu1), libxmlgraphics-commons-java:amd64 (2.1-2, 2.2-1), gcc-6-base:amd64 (6.4.0-7ubuntu1, 6.4.0-8ubuntu1), linux-signed-generic:amd64 (4.13.0.12.1
[Ubuntu-x-swat] [Bug 1722897] Re: Unexpected behavior with Wayland desktop
** Tags added: kernel-da-key -- 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/1722897 Title: Unexpected behavior with Wayland desktop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1722897/+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 1722897] [NEW] Unexpected behavior with Wayland desktop
Public bug reported: I'm fixing an issue with drm/vmwgfx on 17.10 Wayland desktop, and I'd like to chat with someone about how Ubuntu Wayland works. Specifically, when a VM is configured to have 4MB of GPU memory, we have trouble setting modes above 1024x768@32bpp even though there's technically enough GPU memory to handle the framebuffer. This does not happen with Ubuntu 17.10 Xorg desktop. >From what I can see there are two things: 1. Ubuntu Wayland seems to be allocated 2-3 framebuffer sized surfaces. Is it doing triple-buffering? 2. For certain modes, e.g. 1360x768 and 800x600, the pitch coming into .create_fb is greater than mode->width * bytes-per-pixel. For instance, for 800x600@32bpp, the requested pitch is 3328 instead of 3200. These two behaviors is different from what we assumed for low memory configurations, and so is causing some issues. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: xorg 1:7.7+19ubuntu2 Uname: Linux 4.13.0-syeh-v4.13 x86_64 ApportVersion: 2.20.7-0ubuntu2 Architecture: amd64 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Oct 11 12:50:08 2017 DistUpgraded: Fresh install DistroCodename: artful DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller]) Subsystem: VMware SVGA II Adapter [15ad:0405] InstallationDate: Installed on 2017-10-03 (8 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 004: ID 0e0f:0008 VMware, Inc. Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: VMware, Inc. VMware Virtual Platform 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.13.0-username-v4.13 root=UUID=e5e24738-af43-4671-9595-cccd3f4c77b8 ro find_preseed=/preseed.cfg auto noprompt priority=critical locale=en_US quiet modprobe.blacklist=vmwgfx kgdboc=ttyS1,115200 Renderer: Software SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/19/2017 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd05/19/2017:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. version.compiz: compiz N/A 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.3-1ubuntu7 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 xserver.bootTime: Wed Oct 11 12:38:36 2017 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputVMware VMware Virtual USB Mouse MOUSE, id 7 inputVirtualPS/2 VMware VMMouse MOUSE, id 8 inputVirtualPS/2 VMware VMMouse MOUSE, id 9 inputAT Translated Set 2 keyboard KEYBOARD, id 10 xserver.errors: open /dev/dri/card0: No such file or directory open /dev/fb0: No such file or directory vmware(0): Failed to open drm. AIGLX: reverting to software rendering xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.19.3-1ubuntu7 ** Affects: xorg (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 in Ubuntu. https://bugs.launchpad.net/bugs/1722897 Title: Unexpected behavior with Wayland desktop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1722897/+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 1720133] Re: USB 3.0 displays are black on Ubuntu after x.org update to 1.18.3 or newer
16.10 is EOL already, so it won't be possible to fix there. I've nominated it for the other releases though that got 1.18.3. ** Also affects: xorg-server (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: xorg-server (Ubuntu Artful) Importance: High Assignee: Timo Aaltonen (tjaalton) Status: Triaged ** Also affects: xorg-server (Ubuntu Zesty) 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/1720133 Title: USB 3.0 displays are black on Ubuntu after x.org update to 1.18.3 or newer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1720133/+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 1722835] [NEW] I was working and everything freeze.
Public bug reported: Running Netbeans, Firefox, Audacious, Filemanager... ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.10.0-37.41~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-37-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Wed Oct 11 11:28:40 2017 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation GF116 [GeForce GTX 550 Ti] [10de:1244] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GF116 [GeForce GTX 550 Ti] [1043:83be] InstallationDate: Installed on 2017-10-10 (0 days ago) InstallationMedia: Ubuntu-GNOME 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) MachineType: Gigabyte Technology Co., Ltd. B85M-DS3H ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-37-generic.efi.signed root=UUID=ab28a80a-2036-46f7-af84-696df85b60bf ro quiet splash SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/09/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F3 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B85M-DS3H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF3:bd04/09/2014:svnGigabyteTechnologyCo.,Ltd.:pnB85M-DS3H:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnB85M-DS3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: B85M-DS3H dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.2 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 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/1722835 Title: I was working and everything freeze. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1722835/+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 1721245] Re: Flicker when using dual head on resume
*** This bug is a duplicate of bug 1554613 *** https://bugs.launchpad.net/bugs/1554613 ** This bug has been marked a duplicate of bug 1554613 Screen flickers on XPS 13 9350/9550 (Intel Skylake/Broadwell GPU) -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-intel-hwe-16.04 in Ubuntu. https://bugs.launchpad.net/bugs/1721245 Title: Flicker when using dual head on resume To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel-hwe-16.04/+bug/1721245/+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 1722824] Re: Xorg crashed with SIGABRT
*** This bug is a duplicate of bug 1557346 *** https://bugs.launchpad.net/bugs/1557346 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1557346, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1722824/+attachment/4967674/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1722824/+attachment/4967677/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1722824/+attachment/4967689/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1722824/+attachment/4967691/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1722824/+attachment/4967692/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1722824/+attachment/4967693/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1722824/+attachment/4967694/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1557346 Xorg crashed with SIGABRT in OsAbort() ** Tags removed: need-amd64-retrace -- 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/1722824 Title: Xorg crashed with SIGABRT To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1722824/+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 1557346] Re: Xorg crashed with SIGABRT in OsAbort()
** Tags added: artful -- 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/1557346 Title: Xorg crashed with SIGABRT in OsAbort() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1557346/+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 1722824] [NEW] Xorg crashed with SIGABRT
*** This bug is a duplicate of bug 1557346 *** https://bugs.launchpad.net/bugs/1557346 Public bug reported: Happened after an upgrade. First the desktop became unresponsive (Emacs window stopped accepting input even while appearing to have focus according to cursor shape, Alt-Tab did nothing, nor did clicking on any desktop icons). Console switching still worked. SIGTERM failed to impress panel and desktop, so turned to SIGKILL. No change on the desktop (still a working mouse cursor but no reaction to keys or clicks) when console-switching back. Finally, switching back stopped working also, displaying just a blinking text cursor on a blank screen, then this abort. ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: xserver-xorg-core 2:1.19.3-1ubuntu7 ProcVersionSignature: Ubuntu 4.13.0-12.13-lowlatency 4.13.3 Uname: Linux 4.13.0-12-lowlatency x86_64 ApportVersion: 2.20.7-0ubuntu2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Wed Oct 11 16:14:49 2017 DistUpgraded: Fresh install DistroCodename: artful DistroVariant: ubuntu ExecutablePath: /usr/lib/xorg/Xorg GraphicsCard: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (primary) [8086:2a02] (rev 0c) (prog-if 00 [VGA controller]) Subsystem: Lenovo ThinkPad T61/R61 [17aa:20b5] Subsystem: Lenovo ThinkPad T61/R61 [17aa:20b5] InstallationDate: Installed on 2011-10-14 (2189 days ago) InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111011) MachineType: LENOVO 7661LN8 PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcCmdline: /usr/lib/xorg/Xorg -core :0 -seat seat0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch ProcEnviron: PATH=(custom, no user) ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-12-lowlatency root=UUID=a5b30f2d-d555-4bea-9b89-e322f13656be ro quiet splash threadirqs resume=UUID=29869a91-5410-4e9b-9bd9-2aea1ecb1637 Signal: 6 SourcePackage: xorg-server StacktraceTop: () () () xf86VTEnter () WakeupHandler () Title: Xorg crashed with SIGABRT UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 03/18/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 7LETC9WW (2.29 ) dmi.board.name: 7661LN8 dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: 000L004051 dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr7LETC9WW(2.29):bd03/18/2011:svnLENOVO:pn7661LN8:pvrThinkPadT61:rvnLENOVO:rn7661LN8:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T61 dmi.product.name: 7661LN8 dmi.product.version: ThinkPad T61 dmi.sys.vendor: LENOVO version.compiz: compiz N/A 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.3-1ubuntu7 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-crash artful ubuntu ** Information type changed from Private to Public -- 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/1722824 Title: Xorg crashed with SIGABRT To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1722824/+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 1707929] Re: [FFe] Revert blacklisting of Indic layouts
Btw, it's easy to 'unhide' the Indic layouts in 17.04. Just open a terminal window and run: gsettings set org.gnome.desktop.input-sources show-all-sources true -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xkeyboard-config in Ubuntu. https://bugs.launchpad.net/bugs/1707929 Title: [FFe] Revert blacklisting of Indic layouts To manage notifications about this bug go to: https://bugs.launchpad.net/xkeyboard-config/+bug/1707929/+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 1707929] Re: [FFe] Revert blacklisting of Indic layouts
@Nathan: We don't backport changes to this package unless some really important bug is spotted. The reason is that many users make custom keyboard configuration by editing xkb-data files, and a package update in a stable release would wipe out such changes. So no, sorry. (17.04 will only live 3 more months anyway.) -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xkeyboard-config in Ubuntu. https://bugs.launchpad.net/bugs/1707929 Title: [FFe] Revert blacklisting of Indic layouts To manage notifications about this bug go to: https://bugs.launchpad.net/xkeyboard-config/+bug/1707929/+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 1707929] Re: [FFe] Revert blacklisting of Indic layouts
Happy to see this fixed; thank you. What are the chances it could be backported to 17.04? It seems straightforward enough; it certainly interferes with my ability to work on Indic support in my projects and, by extension, other people's ability to test -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xkeyboard-config in Ubuntu. https://bugs.launchpad.net/bugs/1707929 Title: [FFe] Revert blacklisting of Indic layouts To manage notifications about this bug go to: https://bugs.launchpad.net/xkeyboard-config/+bug/1707929/+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 1721245] Re: Flicker when using dual head on resume
I believe this is a bug in the PSR (Panel Self Refresh) module/code. Marking as a duplicate of: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1554613 -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-intel-hwe-16.04 in Ubuntu. https://bugs.launchpad.net/bugs/1721245 Title: Flicker when using dual head on resume To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel-hwe-16.04/+bug/1721245/+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 1717928] Re: gnome crashes when using qemu display
The issue described there looks like the one fixed in https://launchpad.net/ubuntu/+source/xorg-server/2:1.19.3-1ubuntu6 ** Package changed: gnome-shell (Ubuntu) => xorg-server (Ubuntu) ** Changed in: xorg-server (Ubuntu) Importance: Undecided => High ** Changed in: xorg-server (Ubuntu) Status: Incomplete => Fix Released -- 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/1717928 Title: gnome crashes when using qemu display To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1717928/+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 1717928] [NEW] gnome crashes when using qemu display
You have been subscribed to a public bug: Using the qemu vga display under gnome is reliably causing gnome to crash on my laptop. I've seen this when using libvirt and also when invoking qemu from the command line. I've tried several display options for qemu: -vga qxl -vga virtio -display gtk All result in the crash. No crash report is appearing in /var/crash after this happens, but I checked dmesg the last time and found this: [15078.446564] gnome-shell[10327]: segfault at 8 ip 7f4c53c794af sp 7ffd7eb03e90 error 4 in libmutter-cogl-1.so[7f4c53c14000+a5000] The crash usually doesn't happen right away. Sometimes it happens a few seconds after the display is opened, other times it's happened when I've moved to another window and then select the qemu display using Alt-Tab. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1 Uname: Linux 4.13.0-11-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Sep 18 08:11:44 2017 DisplayManager: gdm3 EcryptfsInUse: Yes InstallationDate: Installed on 2017-03-30 (172 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170329) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell UpgradeStatus: Upgraded to artful on 2017-04-27 (143 days ago) ** Affects: xorg-server (Ubuntu) Importance: High Status: Fix Released ** Tags: amd64 apport-bug artful wayland-session -- gnome crashes when using qemu display https://bugs.launchpad.net/bugs/1717928 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server 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 1722708] Re: Crash when setting laptop display resolution
Not quite; with X the screens flicker a couple of times, somehow change resolution temporarily, but then come back with the original settings. With the X case (don't remember checking the wayland one), when I start the resolution modification, I see things like this when starting gnome- control-center from the console: (gnome-control-center:15810): display-cc-panel-WARNING **: Config not applicable: GDBus.Error:org.freedesktop.DBus.Error.InvalidArgs: Logical monitor scales must be identical ...and the Apply button does not show up. When I change the external monitor to 100% scaling, the Apply button appears and is enabled, then clicking on it gives this stuff on console while the flickering etc occurs: (gnome-control-center:15810): display-cc-panel-WARNING **: Config not applicable: GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message recipient disconnected from message bus without replying (gnome-control-center:15810): display-cc-panel-WARNING **: Config not applicable: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Name "org.gnome.Mutter.DisplayConfig" does not exist ...and then, after that, finally this on the console: (gnome-control-center:15810): display-cc-panel-WARNING **: Config not applicable: GDBus.Error:org.freedesktop.DBus.Error.AccessDenied: The requested configuration is based on stale information -- 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/1722708 Title: Crash when setting laptop display resolution To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1722708/+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 1705124] Re: Snap apps have blurry icons in Wayland session
I confirmed this. Installed and ran Atom from the snap package, and indeed the icon appearing on the dock is noticeably blurry compared to others. Same for VLC. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to wayland in Ubuntu. https://bugs.launchpad.net/bugs/1705124 Title: Snap apps have blurry icons in Wayland session To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1705124/+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 1705124] Re: Snap apps have blurry icons in Wayland session
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: wayland (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to wayland in Ubuntu. https://bugs.launchpad.net/bugs/1705124 Title: Snap apps have blurry icons in Wayland session To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1705124/+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 1705124] Re: Snap apps have blurry icons in Wayland session
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: snapd (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to wayland in Ubuntu. https://bugs.launchpad.net/bugs/1705124 Title: Snap apps have blurry icons in Wayland session To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1705124/+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 1059947] Re: xvfb-run munges stdout and stderr together
the source package is xorg-server changing this would break a ton of autopkgtests that use xvfb-run which now get errors like: testsuiteFAIL stderr: QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-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/1059947 Title: xvfb-run munges stdout and stderr together To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1059947/+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 1722727] Re: Xorg crashed with SIGABRT in OsAbort()
*** This bug is a duplicate of bug 1546541 *** https://bugs.launchpad.net/bugs/1546541 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1546541, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1722727/+attachment/4967335/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1722727/+attachment/4967338/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1722727/+attachment/4967348/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1722727/+attachment/4967350/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1722727/+attachment/4967351/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1722727/+attachment/4967352/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1722727/+attachment/4967353/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1546541 ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- 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/1722727 Title: Xorg crashed with SIGABRT in OsAbort() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1722727/+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 1722708] Re: Crash when setting laptop display resolution
The default session uses wayland. You can select X from the login screen, does it fail the same way? -- 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/1722708 Title: Crash when setting laptop display resolution To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1722708/+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 1722419] Re: 17.10 xrandr doesn't seem to function
** Changed in: xrandr (Ubuntu) Status: New => Invalid ** No longer affects: ubuntu -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xrandr in Ubuntu. https://bugs.launchpad.net/bugs/1722419 Title: 17.10 xrandr doesn't seem to function To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xrandr/+bug/1722419/+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
