[Desktop-packages] [Bug 1803319] Re: GNOME Shell task bar menus not updated with external monitor primary and laptop screen fractionally scaled
Seemed to work when I tested it yesterday (I do not always have access to the test set-up). So assuming fixed. Thank you. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1803319 Title: GNOME Shell task bar menus not updated with external monitor primary and laptop screen fractionally scaled Status in GNOME Shell: Fix Released Status in gnome-shell package in Ubuntu: Invalid Status in mutter package in Ubuntu: Fix Released Status in gnome-shell source package in Cosmic: Invalid Status in mutter source package in Cosmic: Triaged Status in gnome-shell source package in Disco: Invalid Status in mutter source package in Disco: Fix Released Bug description: My set-up: a laptop with an internal screen open and scaled to 150% and an external monitor at 100% set to act as the primary screen. When I open the menus in the GNOME Shell task bar (calendar or settings/log-out/etc menu) they are displayed but not updated when I mouse over them or click on them. I can still use them by blind clicking. When I set both screens to 100% I did not see this. I am using the Wayland session. With the internal screen at 125% I saw this too, but after changing the relative position of the two it went away. I think this was a fluke, but I was unable to do the same after going back to 150%. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: gnome-shell 3.30.1-2ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 CasperVersion: 1.399 CurrentDesktop: ubuntu:GNOME Date: Wed Nov 14 11:23:54 2018 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.shell' b'favorite-apps' redacted by apport b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2018-06-12 (154 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: gnome-shell UpgradeStatus: Upgraded to cosmic on 2018-10-08 (37 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1803319/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1803319] Re: GNOME Shell task bar menus not updated with external monitor primary and laptop screen fractionally scaled
Sounds reasonable. Thanks for letting me know. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1803319 Title: GNOME Shell task bar menus not updated with external monitor primary and laptop screen fractionally scaled Status in GNOME Shell: Fix Released Status in gnome-shell package in Ubuntu: Triaged Status in mutter package in Ubuntu: Triaged Status in gnome-shell source package in Cosmic: Triaged Status in mutter source package in Cosmic: Triaged Status in gnome-shell source package in Disco: Triaged Status in mutter source package in Disco: Triaged Bug description: My set-up: a laptop with an internal screen open and scaled to 150% and an external monitor at 100% set to act as the primary screen. When I open the menus in the GNOME Shell task bar (calendar or settings/log-out/etc menu) they are displayed but not updated when I mouse over them or click on them. I can still use them by blind clicking. When I set both screens to 100% I did not see this. I am using the Wayland session. With the internal screen at 125% I saw this too, but after changing the relative position of the two it went away. I think this was a fluke, but I was unable to do the same after going back to 150%. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: gnome-shell 3.30.1-2ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 CasperVersion: 1.399 CurrentDesktop: ubuntu:GNOME Date: Wed Nov 14 11:23:54 2018 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.shell' b'favorite-apps' redacted by apport b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2018-06-12 (154 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: gnome-shell UpgradeStatus: Upgraded to cosmic on 2018-10-08 (37 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1803319/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1803319] Re: GNOME Shell task bar menus not updated with external monitor primary and laptop screen fractionally scaled
Please let me know when there Ubuntu packages I can test. I have upgraded to 19.04. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1803319 Title: GNOME Shell task bar menus not updated with external monitor primary and laptop screen fractionally scaled Status in GNOME Shell: Fix Released Status in gnome-shell package in Ubuntu: In Progress Status in mutter package in Ubuntu: In Progress Status in gnome-shell source package in Bionic: New Status in mutter source package in Bionic: New Status in gnome-shell source package in Cosmic: Triaged Status in mutter source package in Cosmic: Triaged Status in gnome-shell source package in Disco: In Progress Status in mutter source package in Disco: In Progress Bug description: My set-up: a laptop with an internal screen open and scaled to 150% and an external monitor at 100% set to act as the primary screen. When I open the menus in the GNOME Shell task bar (calendar or settings/log-out/etc menu) they are displayed but not updated when I mouse over them or click on them. I can still use them by blind clicking. When I set both screens to 100% I did not see this. I am using the Wayland session. With the internal screen at 125% I saw this too, but after changing the relative position of the two it went away. I think this was a fluke, but I was unable to do the same after going back to 150%. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: gnome-shell 3.30.1-2ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 CasperVersion: 1.399 CurrentDesktop: ubuntu:GNOME Date: Wed Nov 14 11:23:54 2018 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.shell' b'favorite-apps' redacted by apport b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2018-06-12 (154 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: gnome-shell UpgradeStatus: Upgraded to cosmic on 2018-10-08 (37 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1803319/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1805151] Re: Desktop freeze running VirtualBox, Intel graphics
Update: 4.19.4-041904-generic is affected, 4.20.0-042000rc1-generic is not. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1805151 Title: Desktop freeze running VirtualBox, Intel graphics Status in xorg package in Ubuntu: New Bug description: This is identical to bug 1804885, but as requested I am filing this while running the standard Ubuntu kernel. I will copy and paste my summary below. Updates since I created that bug: * This occurs with the mainline PPA 4.18.12-041812-generic kernel. * The glxinfo section I include below is identical with 4.18.0-11-generic (presumably no surprise). * I would appreciate a bit of hand-holding for bisecting this. Does the kernel team have ready-built kernel packages for bisecting? Or guidance about the fastest way of doing it (i.e. not rebuilding things which do not need to be rebuilt for successive rounds)? === Original report follows === When I start a VirtualBox virtual machine (reproducible with the Ubuntu 18.04/VirtualBox 5.2.22 packages from virtualbox.org) with VMSVGA emulation and 3D pass-through enabled, my system hangs. Sometimes I can recover if I get to a VT fast enough to kill the process. Also, the OOM killer sometimes triggers and kills the process or gnome-shell, but the OOM killer entries in dmesg look like neither of the two are using excessive memory compared to available system RAM. When I switch to the Ubuntu drm-tip kernel packages from the kernel PPA the problem goes away. Debugging shows that the hang occurs during the first glXMakeCurrent call made by the application. It did not occur using the standard Ubuntu kernel but running the application under apitrace. I can provide the trace if that helps. Short extract from glxinfo running the 4.20 drm-tip kernel: Extended renderer info (GLX_MESA_query_renderer): Vendor: Intel Open Source Technology Center (0x8086) Device: Mesa DRI Intel(R) HD Graphics 620 (Kaby Lake GT2) (0x5916) Version: 18.2.2 Accelerated: yes Video memory: 3072MB Unified memory: yes Preferred profile: core (0x1) Max core profile version: 4.5 Max compat profile version: 3.0 Max GLES1 profile version: 1.1 Max GLES[23] profile version: 3.2 ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: xorg 1:7.7+19ubuntu8 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 BootLog: Error: [Errno 13] Отказано в доступе: '/var/log/boot.log' CasperVersion: 1.399 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Nov 26 15:01:53 2018 DistUpgraded: 2018-10-08 10:28:22,218 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: cosmic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GpuHangFrequency: Several times a day GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Lenovo HD Graphics 620 [17aa:2245] InstallationDate: Installed on 2018-06-12 (166 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: LENOVO 20HES0E73E ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-11-generic root=/dev/mapper/ubuntu--vg-root ro scsi_mod.use_blk_mq=1 quiet splash crashkernel=384M-:128M SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to cosmic on 2018-10-08 (49 days ago) dmi.bios.date: 09/13/2018 dmi.bios.vendor: LENOVO dmi.bios.version: N1QET78W (1.53 ) dmi.board.asset.tag: Not Available dmi.board.name: 20HES0E73E dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1QET78W(1.53):bd09/13/2018:svnLENOVO:pn20HES0E73E:pvrThinkPadT470:rvnLENOVO:rn20HES0E73E:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T470 dmi.product.name: 20HES0E73E dmi.product.sku: LENOVO_MT_20HE_BU_Think_FM_ThinkPad T470 dmi.product.version: ThinkPad T470 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.3-0~ubuntu18.10.1~ppa1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1
[Desktop-packages] [Bug 1805151] [NEW] Desktop freeze running VirtualBox, Intel graphics
Public bug reported: This is identical to bug 1804885, but as requested I am filing this while running the standard Ubuntu kernel. I will copy and paste my summary below. Updates since I created that bug: * This occurs with the mainline PPA 4.18.12-041812-generic kernel. * The glxinfo section I include below is identical with 4.18.0-11-generic (presumably no surprise). * I would appreciate a bit of hand-holding for bisecting this. Does the kernel team have ready-built kernel packages for bisecting? Or guidance about the fastest way of doing it (i.e. not rebuilding things which do not need to be rebuilt for successive rounds)? === Original report follows === When I start a VirtualBox virtual machine (reproducible with the Ubuntu 18.04/VirtualBox 5.2.22 packages from virtualbox.org) with VMSVGA emulation and 3D pass-through enabled, my system hangs. Sometimes I can recover if I get to a VT fast enough to kill the process. Also, the OOM killer sometimes triggers and kills the process or gnome-shell, but the OOM killer entries in dmesg look like neither of the two are using excessive memory compared to available system RAM. When I switch to the Ubuntu drm-tip kernel packages from the kernel PPA the problem goes away. Debugging shows that the hang occurs during the first glXMakeCurrent call made by the application. It did not occur using the standard Ubuntu kernel but running the application under apitrace. I can provide the trace if that helps. Short extract from glxinfo running the 4.20 drm-tip kernel: Extended renderer info (GLX_MESA_query_renderer): Vendor: Intel Open Source Technology Center (0x8086) Device: Mesa DRI Intel(R) HD Graphics 620 (Kaby Lake GT2) (0x5916) Version: 18.2.2 Accelerated: yes Video memory: 3072MB Unified memory: yes Preferred profile: core (0x1) Max core profile version: 4.5 Max compat profile version: 3.0 Max GLES1 profile version: 1.1 Max GLES[23] profile version: 3.2 ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: xorg 1:7.7+19ubuntu8 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 BootLog: Error: [Errno 13] Отказано в доступе: '/var/log/boot.log' CasperVersion: 1.399 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Nov 26 15:01:53 2018 DistUpgraded: 2018-10-08 10:28:22,218 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: cosmic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GpuHangFrequency: Several times a day GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Lenovo HD Graphics 620 [17aa:2245] InstallationDate: Installed on 2018-06-12 (166 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: LENOVO 20HES0E73E ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-11-generic root=/dev/mapper/ubuntu--vg-root ro scsi_mod.use_blk_mq=1 quiet splash crashkernel=384M-:128M SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to cosmic on 2018-10-08 (49 days ago) dmi.bios.date: 09/13/2018 dmi.bios.vendor: LENOVO dmi.bios.version: N1QET78W (1.53 ) dmi.board.asset.tag: Not Available dmi.board.name: 20HES0E73E dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1QET78W(1.53):bd09/13/2018:svnLENOVO:pn20HES0E73E:pvrThinkPadT470:rvnLENOVO:rn20HES0E73E:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T470 dmi.product.name: 20HES0E73E dmi.product.sku: LENOVO_MT_20HE_BU_Think_FM_ThinkPad T470 dmi.product.version: ThinkPad T470 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.3-0~ubuntu18.10.1~ppa1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug cosmic freeze third-party-packages ubuntu wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1805151 Title: Desktop freeze running
[Desktop-packages] [Bug 1804885] [NEW] Desktop freeze running VirtualBox, Intel graphics
Public bug reported: When I start a VirtualBox virtual machine (reproducible with the Ubuntu 18.04/VirtualBox 5.2.22 packages from virtualbox.org) with VMSVGA emulation and 3D pass-through enabled, my system hangs. Sometimes I can recover if I get to a VT fast enough to kill the process. Also, the OOM killer sometimes triggers and kills the process or gnome-shell, but the OOM killer entries in dmesg look like neither of the two are using excessive memory compared to available system RAM. When I switch to the Ubuntu drm-tip kernel packages from the kernel PPA the problem goes away. Debugging shows that the hang occurs during the first glXMakeCurrent call made by the application. It did not occur using the standard Ubuntu kernel but running the application under apitrace. I can provide the trace if that helps. Short extract from glxinfo running the 4.20 drm-tip kernel: Extended renderer info (GLX_MESA_query_renderer): Vendor: Intel Open Source Technology Center (0x8086) Device: Mesa DRI Intel(R) HD Graphics 620 (Kaby Lake GT2) (0x5916) Version: 18.2.2 Accelerated: yes Video memory: 3072MB Unified memory: yes Preferred profile: core (0x1) Max core profile version: 4.5 Max compat profile version: 3.0 Max GLES1 profile version: 1.1 Max GLES[23] profile version: 3.2 ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: xorg 1:7.7+19ubuntu8 Uname: Linux 4.20.0-994-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 BootLog: Error: [Errno 13] Отказано в доступе: '/var/log/boot.log' CasperVersion: 1.399 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Nov 23 21:13:00 2018 DistUpgraded: 2018-10-08 10:28:22,218 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: cosmic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GpuHangFrequency: Several times a day GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Lenovo HD Graphics 620 [17aa:2245] InstallationDate: Installed on 2018-06-12 (164 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: LENOVO 20HES0E73E ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.20.0-994-generic root=/dev/mapper/ubuntu--vg-root ro scsi_mod.use_blk_mq=1 quiet splash crashkernel=384M-:128M SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to cosmic on 2018-10-08 (46 days ago) dmi.bios.date: 09/13/2018 dmi.bios.vendor: LENOVO dmi.bios.version: N1QET78W (1.53 ) dmi.board.asset.tag: Not Available dmi.board.name: 20HES0E73E dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1QET78W(1.53):bd09/13/2018:svnLENOVO:pn20HES0E73E:pvrThinkPadT470:rvnLENOVO:rn20HES0E73E:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T470 dmi.product.name: 20HES0E73E dmi.product.sku: LENOVO_MT_20HE_BU_Think_FM_ThinkPad T470 dmi.product.version: ThinkPad T470 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.3-0~ubuntu18.10.1~ppa1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug cosmic freeze third-party-packages ubuntu wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1804885 Title: Desktop freeze running VirtualBox, Intel graphics Status in xorg package in Ubuntu: New Bug description: When I start a VirtualBox virtual machine (reproducible with the Ubuntu 18.04/VirtualBox 5.2.22 packages from virtualbox.org) with VMSVGA emulation and 3D pass-through enabled, my system hangs. Sometimes I can recover if I get to a VT fast enough to kill the process. Also, the OOM killer sometimes triggers and kills the process or gnome-shell, but the OOM killer entries in dmesg look like neither of the two are using excessive memory compared to available system RAM. When I switch to the Ubuntu drm-tip kernel packages from the kernel PPA the problem goes away. Debugging shows that the hang occurs
[Desktop-packages] [Bug 1803319] [NEW] GNOME Shell task bar menus not updated with external monitor primary and laptop screen fractionally scaled
Public bug reported: My set-up: a laptop with an internal screen open and scaled to 150% and an external monitor at 100% set to act as the primary screen. When I open the menus in the GNOME Shell task bar (calendar or settings/log- out/etc menu) they are displayed but not updated when I mouse over them or click on them. I can still use them by blind clicking. When I set both screens to 100% I did not see this. I am using the Wayland session. With the internal screen at 125% I saw this too, but after changing the relative position of the two it went away. I think this was a fluke, but I was unable to do the same after going back to 150%. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: gnome-shell 3.30.1-2ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 CasperVersion: 1.399 CurrentDesktop: ubuntu:GNOME Date: Wed Nov 14 11:23:54 2018 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.shell' b'favorite-apps' redacted by apport b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2018-06-12 (154 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: gnome-shell UpgradeStatus: Upgraded to cosmic on 2018-10-08 (37 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug cosmic third-party-packages wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1803319 Title: GNOME Shell task bar menus not updated with external monitor primary and laptop screen fractionally scaled Status in gnome-shell package in Ubuntu: New Bug description: My set-up: a laptop with an internal screen open and scaled to 150% and an external monitor at 100% set to act as the primary screen. When I open the menus in the GNOME Shell task bar (calendar or settings/log-out/etc menu) they are displayed but not updated when I mouse over them or click on them. I can still use them by blind clicking. When I set both screens to 100% I did not see this. I am using the Wayland session. With the internal screen at 125% I saw this too, but after changing the relative position of the two it went away. I think this was a fluke, but I was unable to do the same after going back to 150%. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: gnome-shell 3.30.1-2ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 CasperVersion: 1.399 CurrentDesktop: ubuntu:GNOME Date: Wed Nov 14 11:23:54 2018 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.shell' b'favorite-apps' redacted by apport b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2018-06-12 (154 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: gnome-shell UpgradeStatus: Upgraded to cosmic on 2018-10-08 (37 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1803319/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1723045] Re: GNOME Terminal does not get into GNOME Shell's frequently used list
After rebooting into 18.10 this morning this seemed to work. I will assume it is fixed, close the bug and re-open it if necessary. ** Changed in: gnome-shell (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1723045 Title: GNOME Terminal does not get into GNOME Shell's frequently used list Status in gnome-shell package in Ubuntu: Fix Released Bug description: I use GNOME Terminal frequently. I tend (at least since I upgraded) to start it from GNOME Shell's dash, using the "all applications" category. For some reason it never makes it to the frequently used list. If it is of interest: $ grep terminal .local/share/gnome-shell/application_state I wonder whether the fact that my desktop is mainly Russian localised (the main folder names are in English) is related, but my guess is that it is not. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.1-0ubuntu2 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 CurrentDesktop: ubuntu:GNOME Date: Thu Oct 12 11:12:37 2017 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.shell' b'favorite-apps' b"['ubiquity.desktop', 'org.gnome.Nautilus.desktop', 'firefox.desktop', 'libreoffice-writer.desktop', 'libreoffice-calc.desktop', 'libreoffice-impress.desktop', 'org.gnome.Software.desktop', 'gnome-control-center.desktop']" b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2016-05-31 (498 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: gnome-shell UpgradeStatus: Upgraded to artful on 2017-10-05 (7 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1723045/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1792000] Re: VirtualBox icon does not show un dock until screen locks
No desktop files installed: everything running out of the build directory, and the only thing installed outside is the kernel modules and a udev rule. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1792000 Title: VirtualBox icon does not show un dock until screen locks Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: New Bug description: Quite simple: I start VirtualBox or a virtual machine straight from the build directory (without installing) and the icon in the dock is a red, crossed-out circle. After deliberately or due to a timeout locking the screen and unlocking it, the correct X11 property icon is shown. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell-extension-ubuntu-dock 0.9.1ubuntu18.04.1 ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 Uname: Linux 4.15.0-33-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CasperVersion: 1.394 CurrentDesktop: ubuntu:GNOME Date: Tue Sep 11 20:32:51 2018 InstallationDate: Installed on 2018-06-12 (91 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all SourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1792000/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1792000] [NEW] VirtualBox icon does not show un dock until screen locks
Public bug reported: Quite simple: I start VirtualBox or a virtual machine straight from the build directory (without installing) and the icon in the dock is a red, crossed-out circle. After deliberately or due to a timeout locking the screen and unlocking it, the correct X11 property icon is shown. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell-extension-ubuntu-dock 0.9.1ubuntu18.04.1 ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 Uname: Linux 4.15.0-33-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CasperVersion: 1.394 CurrentDesktop: ubuntu:GNOME Date: Tue Sep 11 20:32:51 2018 InstallationDate: Installed on 2018-06-12 (91 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all SourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell-extension-ubuntu-dock (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1792000 Title: VirtualBox icon does not show un dock until screen locks Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: New Bug description: Quite simple: I start VirtualBox or a virtual machine straight from the build directory (without installing) and the icon in the dock is a red, crossed-out circle. After deliberately or due to a timeout locking the screen and unlocking it, the correct X11 property icon is shown. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell-extension-ubuntu-dock 0.9.1ubuntu18.04.1 ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 Uname: Linux 4.15.0-33-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CasperVersion: 1.394 CurrentDesktop: ubuntu:GNOME Date: Tue Sep 11 20:32:51 2018 InstallationDate: Installed on 2018-06-12 (91 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all SourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1792000/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1722725] Re: GNOME Shell disabling wrong screen when docking laptop
Even though 3.28 is due out after the Bionic feature freeze? What about X.Org 1.20, which is due out a few days later? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1722725 Title: GNOME Shell disabling wrong screen when docking laptop Status in GNOME Shell: Fix Released Status in gnome-shell package in Ubuntu: Fix Committed Bug description: I often switch between working with a docking station, closed laptop and an external monitor, and an open laptop without docking station or monitor. I noticed since updating to 17.10 that GNOME Shell would not switch correctly from the setup where the laptop was being used open without a docking station to the other. When I opened the laptop in the docking station the external monitor would come on, and when I closed the laptop it went off again. I manually switched the primary screen to be the external one and that solved it for now, so I assume that GNOME Shell was disabling the external screen instead of the internal one (it is a bit hard to see, and I have not yet tried ssh- ing in). ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Uname: Linux 4.13.0-12-generic x86_64 ApportVersion: 2.20.7-0ubuntu2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Oct 11 09:06:34 2017 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.shell' b'favorite-apps' b"['ubiquity.desktop', 'org.gnome.Nautilus.desktop', 'firefox.desktop', 'libreoffice-writer.desktop', 'libreoffice-calc.desktop', 'libreoffice-impress.desktop', 'org.gnome.Software.desktop', 'gnome-control-center.desktop']" b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2016-05-31 (497 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: gnome-shell UpgradeStatus: Upgraded to artful on 2017-10-05 (6 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1722725/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1722725] Re: GNOME Shell disabling wrong screen when docking laptop
Do you expect 3.26.3 to end up in Bionic? If not, would it be possible to back-port the fix? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1722725 Title: GNOME Shell disabling wrong screen when docking laptop Status in GNOME Shell: Fix Released Status in gnome-shell package in Ubuntu: Fix Committed Bug description: I often switch between working with a docking station, closed laptop and an external monitor, and an open laptop without docking station or monitor. I noticed since updating to 17.10 that GNOME Shell would not switch correctly from the setup where the laptop was being used open without a docking station to the other. When I opened the laptop in the docking station the external monitor would come on, and when I closed the laptop it went off again. I manually switched the primary screen to be the external one and that solved it for now, so I assume that GNOME Shell was disabling the external screen instead of the internal one (it is a bit hard to see, and I have not yet tried ssh- ing in). ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Uname: Linux 4.13.0-12-generic x86_64 ApportVersion: 2.20.7-0ubuntu2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Oct 11 09:06:34 2017 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.shell' b'favorite-apps' b"['ubiquity.desktop', 'org.gnome.Nautilus.desktop', 'firefox.desktop', 'libreoffice-writer.desktop', 'libreoffice-calc.desktop', 'libreoffice-impress.desktop', 'org.gnome.Software.desktop', 'gnome-control-center.desktop']" b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2016-05-31 (497 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: gnome-shell UpgradeStatus: Upgraded to artful on 2017-10-05 (6 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1722725/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1722725] Re: GNOME Shell disabling wrong screen when docking laptop
The patches are attached to gnome-bugs #788915. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1722725 Title: GNOME Shell disabling wrong screen when docking laptop Status in GNOME Shell: Fix Released Status in gnome-shell package in Ubuntu: Fix Committed Bug description: I often switch between working with a docking station, closed laptop and an external monitor, and an open laptop without docking station or monitor. I noticed since updating to 17.10 that GNOME Shell would not switch correctly from the setup where the laptop was being used open without a docking station to the other. When I opened the laptop in the docking station the external monitor would come on, and when I closed the laptop it went off again. I manually switched the primary screen to be the external one and that solved it for now, so I assume that GNOME Shell was disabling the external screen instead of the internal one (it is a bit hard to see, and I have not yet tried ssh- ing in). ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Uname: Linux 4.13.0-12-generic x86_64 ApportVersion: 2.20.7-0ubuntu2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Oct 11 09:06:34 2017 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.shell' b'favorite-apps' b"['ubiquity.desktop', 'org.gnome.Nautilus.desktop', 'firefox.desktop', 'libreoffice-writer.desktop', 'libreoffice-calc.desktop', 'libreoffice-impress.desktop', 'org.gnome.Software.desktop', 'gnome-control-center.desktop']" b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2016-05-31 (497 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: gnome-shell UpgradeStatus: Upgraded to artful on 2017-10-05 (6 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1722725/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1722725] Re: GNOME Shell disabling wrong screen when docking laptop
Would it be possible to apply the upstream patches to the version in Bionic? I am happy to install the updated packages before they hit the repositories. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1722725 Title: GNOME Shell disabling wrong screen when docking laptop Status in GNOME Shell: Fix Released Status in gnome-shell package in Ubuntu: Fix Committed Bug description: I often switch between working with a docking station, closed laptop and an external monitor, and an open laptop without docking station or monitor. I noticed since updating to 17.10 that GNOME Shell would not switch correctly from the setup where the laptop was being used open without a docking station to the other. When I opened the laptop in the docking station the external monitor would come on, and when I closed the laptop it went off again. I manually switched the primary screen to be the external one and that solved it for now, so I assume that GNOME Shell was disabling the external screen instead of the internal one (it is a bit hard to see, and I have not yet tried ssh- ing in). ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Uname: Linux 4.13.0-12-generic x86_64 ApportVersion: 2.20.7-0ubuntu2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Oct 11 09:06:34 2017 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.shell' b'favorite-apps' b"['ubiquity.desktop', 'org.gnome.Nautilus.desktop', 'firefox.desktop', 'libreoffice-writer.desktop', 'libreoffice-calc.desktop', 'libreoffice-impress.desktop', 'org.gnome.Software.desktop', 'gnome-control-center.desktop']" b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2016-05-31 (497 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: gnome-shell UpgradeStatus: Upgraded to artful on 2017-10-05 (6 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1722725/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1724259] Re: gnome-shell frozen and using 100% CPU after docking and display configuration change
I am currently running version 1.8.4-0ubuntu0.17.10.1 of both packages and have not seen this problem for a while. I have rebooted several times since installing the packages. Off-topic, but since yesterday (can't remember it happening earlier) I have started seeing mouse button freezes after suspend and resume, affecting clients. Most windows can still be dragged, and the dock responds to mouse buttons, but e.g. the terminal, Firefox and Thunderbird respond to keyboard but not mouse. I can raise the windows using the dock. Would you happen to know of any matching open bug for that, or anything else? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1724259 Title: gnome-shell frozen and using 100% CPU after docking and display configuration change Status in libinput: Fix Released Status in gnome-shell package in Ubuntu: Incomplete Status in libinput package in Ubuntu: Fix Released Status in gnome-shell source package in Artful: New Status in libinput source package in Artful: Fix Committed Bug description: [Impact] I have been having regular system freezes after switching from using my laptop stand-alone to waking it up on a docking station with an external monitor. I have seen this using two identical docking station plus monitor combinations. I am still trying to find a pattern. I was able to ssh in and use apport to save this bug information. The gnome-shell process was hung at 100% CPU utilisation. libinput 1.8.4 fixes this [Test case] Wake up while the system is docked and attached to an external monitor. [Regression potential] The bugfix comes via a new microrelease update, so chance of regressions should be minimal. -- ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.1-0ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Oct 17 15:56:34 2017 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell GsettingsChanges: b'org.gnome.shell' b'command-history' b"['gnome-terminal']" b'org.gnome.shell' b'had-bluetooth-devices-setup' b'true' b'org.gnome.shell' b'favorite-apps' b"['ubiquity.desktop', 'org.gnome.Nautilus.desktop', 'firefox.desktop', 'libreoffice-writer.desktop', 'libreoffice-calc.desktop', 'libreoffice-impress.desktop', 'org.gnome.Software.desktop', 'gnome-control-center.desktop']" b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2016-05-31 (504 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: gnome-shell UpgradeStatus: Upgraded to artful on 2017-10-05 (12 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/libinput/+bug/1724259/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1724259] Re: gnome-shell frozen and using 100% CPU after docking and display configuration change
I must admit that I have not seen this freeze for a while (unless I just missed it among all the swap-to-death freezes I have had recently), but I installed the packages. I did not enable proposed, I just manually installed libinput-bin and libinput10, versions 1.8.4. I probably can't give any meaningful feedback until after my next reboot though. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1724259 Title: gnome-shell frozen and using 100% CPU after docking and display configuration change Status in libinput: Fix Released Status in gnome-shell package in Ubuntu: Incomplete Status in libinput package in Ubuntu: Fix Released Status in gnome-shell source package in Artful: New Status in libinput source package in Artful: Fix Committed Bug description: [Impact] I have been having regular system freezes after switching from using my laptop stand-alone to waking it up on a docking station with an external monitor. I have seen this using two identical docking station plus monitor combinations. I am still trying to find a pattern. I was able to ssh in and use apport to save this bug information. The gnome-shell process was hung at 100% CPU utilisation. libinput 1.8.4 fixes this [Test case] Wake up while the system is docked and attached to an external monitor. [Regression potential] The bugfix comes via a new microrelease update, so chance of regressions should be minimal. -- ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.1-0ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Oct 17 15:56:34 2017 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell GsettingsChanges: b'org.gnome.shell' b'command-history' b"['gnome-terminal']" b'org.gnome.shell' b'had-bluetooth-devices-setup' b'true' b'org.gnome.shell' b'favorite-apps' b"['ubiquity.desktop', 'org.gnome.Nautilus.desktop', 'firefox.desktop', 'libreoffice-writer.desktop', 'libreoffice-calc.desktop', 'libreoffice-impress.desktop', 'org.gnome.Software.desktop', 'gnome-control-center.desktop']" b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2016-05-31 (504 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: gnome-shell UpgradeStatus: Upgraded to artful on 2017-10-05 (12 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/libinput/+bug/1724259/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1505409] Re: gnome-shell crashed with SIGTRAP in x_io_error() from _XIOError() from _XEventsQueued() from XPending() from gdk_check_xpending() ["Connection to xwayland lost"]
At least in my case, I think that the sensible approach is to make wayland-server treat requests for deleted objects non-fatal, as suggested by Pekka Paalanan in the blog post linked to above. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1505409 Title: gnome-shell crashed with SIGTRAP in x_io_error() from _XIOError() from _XEventsQueued() from XPending() from gdk_check_xpending() ["Connection to xwayland lost"] Status in GNOME Shell: Confirmed Status in Ubuntu GNOME: Confirmed Status in gdm3 package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Status in gdm3 source package in Artful: Confirmed Status in gnome-shell source package in Artful: Confirmed Status in mutter source package in Artful: Confirmed Bug description: https://errors.ubuntu.com/problem/d0252e2b465152efea2511e72f1e31681e2b2742 --- Occurred during start-up, before I did anything special... 1 Ubuntu Wily Werewolf (development branch) 15.10 2 3.16.3-1ubuntu6 3&4 not applicable ProblemType: Crash DistroRelease: Ubuntu 15.10 Package: gnome-shell 3.16.3-1ubuntu6 ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3 Uname: Linux 4.2.0-16-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.19.1-0ubuntu2 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Oct 12 19:22:07 2015 DisplayManager: gdm ExecutablePath: /usr/bin/gnome-shell GsettingsChanges: InstallationDate: Installed on 2015-10-08 (4 days ago) InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha amd64 (20150924) ProcCmdline: gnome-shell --mode=gdm --wayland --display-server ProcEnviron: SHELL=/bin/false PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=nl_NL.UTF-8 Signal: 5 SourcePackage: gnome-shell StacktraceTop: ?? () from /usr/lib/libmutter.so.0 _XIOError () from /usr/lib/x86_64-linux-gnu/libX11.so.6 _XEventsQueued () from /usr/lib/x86_64-linux-gnu/libX11.so.6 XPending () from /usr/lib/x86_64-linux-gnu/libX11.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0 Title: gnome-shell crashed with signal 5 in _XIOError() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1505409/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1505409] Re: gnome-shell crashed with SIGTRAP in x_io_error() from _XIOError() from _XEventsQueued() from XPending() from gdk_check_xpending() ["Connection to xwayland lost"]
Just for the sake of adding a comment too... I am getting this in the following situation. I hope the description is correct. 1) I change the display set-up on my laptop slightly too fast, e.g. close the lid, re-open, re-close (I did that quite a bit recently trying to work out bug patterns). 2) GNOME Shell creates a wl_output object for the internal screen, reports it to Xwayland, then removes it again because the screen is disabled again. 3) Xwayland asks GNOME Shell for more information about the no-longer-existing wl_output object and GNOME Shell (in the Wayland library code) terminates the connection because it considers asking about a non-existing object to be a bug. 4) Xwayland dutifully terminates and GNOME Shell panics and terminates too. See: https://phabricator.freedesktop.org/T7722 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1505409 Title: gnome-shell crashed with SIGTRAP in x_io_error() from _XIOError() from _XEventsQueued() from XPending() from gdk_check_xpending() ["Connection to xwayland lost"] Status in GNOME Shell: Confirmed Status in Ubuntu GNOME: Confirmed Status in gdm3 package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Status in gdm3 source package in Artful: Confirmed Status in gnome-shell source package in Artful: Confirmed Status in mutter source package in Artful: Confirmed Bug description: https://errors.ubuntu.com/problem/d0252e2b465152efea2511e72f1e31681e2b2742 --- Occurred during start-up, before I did anything special... 1 Ubuntu Wily Werewolf (development branch) 15.10 2 3.16.3-1ubuntu6 3&4 not applicable ProblemType: Crash DistroRelease: Ubuntu 15.10 Package: gnome-shell 3.16.3-1ubuntu6 ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3 Uname: Linux 4.2.0-16-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.19.1-0ubuntu2 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Oct 12 19:22:07 2015 DisplayManager: gdm ExecutablePath: /usr/bin/gnome-shell GsettingsChanges: InstallationDate: Installed on 2015-10-08 (4 days ago) InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha amd64 (20150924) ProcCmdline: gnome-shell --mode=gdm --wayland --display-server ProcEnviron: SHELL=/bin/false PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=nl_NL.UTF-8 Signal: 5 SourcePackage: gnome-shell StacktraceTop: ?? () from /usr/lib/libmutter.so.0 _XIOError () from /usr/lib/x86_64-linux-gnu/libX11.so.6 _XEventsQueued () from /usr/lib/x86_64-linux-gnu/libX11.so.6 XPending () from /usr/lib/x86_64-linux-gnu/libX11.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0 Title: gnome-shell crashed with signal 5 in _XIOError() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1505409/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1724259] Re: gnome-shell frozen and using 100% CPU after docking and display configuration change
Or a third hypothesis: systemd-logind triggers a suspend on lid close if there is no external monitor plugged in. Perhaps it looks for a while too long like there is no monitor, so that systemd-logind suspends the system and the GNOME Shell wayland output object disappears, causing the xwayland error. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1724259 Title: gnome-shell frozen and using 100% CPU after docking and display configuration change Status in gnome-shell package in Ubuntu: Incomplete Bug description: I have been having regular system freezes after switching from using my laptop stand-alone to waking it up on a docking station with an external monitor. I have seen this using two identical docking station plus monitor combinations. I am still trying to find a pattern. I was able to ssh in and use apport to save this bug information. The gnome-shell process was hung at 100% CPU utilisation. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.1-0ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Oct 17 15:56:34 2017 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell GsettingsChanges: b'org.gnome.shell' b'command-history' b"['gnome-terminal']" b'org.gnome.shell' b'had-bluetooth-devices-setup' b'true' b'org.gnome.shell' b'favorite-apps' b"['ubiquity.desktop', 'org.gnome.Nautilus.desktop', 'firefox.desktop', 'libreoffice-writer.desktop', 'libreoffice-calc.desktop', 'libreoffice-impress.desktop', 'org.gnome.Software.desktop', 'gnome-control-center.desktop']" b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2016-05-31 (504 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: gnome-shell UpgradeStatus: Upgraded to artful on 2017-10-05 (12 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1724259/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1724259] Re: gnome-shell frozen and using 100% CPU after docking and display configuration change
Thinking of it I might be confusing cause and effect here: the unexpected suspend might be caused somehow by the xwayland and gnome- shell crash. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1724259 Title: gnome-shell frozen and using 100% CPU after docking and display configuration change Status in gnome-shell package in Ubuntu: Incomplete Bug description: I have been having regular system freezes after switching from using my laptop stand-alone to waking it up on a docking station with an external monitor. I have seen this using two identical docking station plus monitor combinations. I am still trying to find a pattern. I was able to ssh in and use apport to save this bug information. The gnome-shell process was hung at 100% CPU utilisation. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.1-0ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Oct 17 15:56:34 2017 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell GsettingsChanges: b'org.gnome.shell' b'command-history' b"['gnome-terminal']" b'org.gnome.shell' b'had-bluetooth-devices-setup' b'true' b'org.gnome.shell' b'favorite-apps' b"['ubiquity.desktop', 'org.gnome.Nautilus.desktop', 'firefox.desktop', 'libreoffice-writer.desktop', 'libreoffice-calc.desktop', 'libreoffice-impress.desktop', 'org.gnome.Software.desktop', 'gnome-control-center.desktop']" b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2016-05-31 (504 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: gnome-shell UpgradeStatus: Upgraded to artful on 2017-10-05 (12 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1724259/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1724259] Re: gnome-shell frozen and using 100% CPU after docking and display configuration change
Not succeeded in reproducing this again after rebuilding GNOME Shell with ASAN_OPTIONS=detect_leaks=0 CFLAGS="-fsanitize=address -fsanitize=return -fsanitize=bounds -fsanitize=object-size". I do now manage to trigger debian bug 823216 quite reliably now, with the difference that I can log on again immediately. It is usually the user GNOME Shell and XWayland which crash, but at least once the gdm ones crashed. [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=823216 I trigger this by opening a few applications (Firefox with a few windows seems to make it easier to reproduce) and repeatedly opening and closing the laptop lid. It seems that, as per systemd logind settings this should not trigger a suspend when docked, but occasionally it does. The xwayland termination happens just before this (as observed from an ssh session on my other laptop: I can see the results just before the session stops responding due to the suspension). ** Bug watch added: Debian Bug tracker #823216 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=823216 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1724259 Title: gnome-shell frozen and using 100% CPU after docking and display configuration change Status in gnome-shell package in Ubuntu: Incomplete Bug description: I have been having regular system freezes after switching from using my laptop stand-alone to waking it up on a docking station with an external monitor. I have seen this using two identical docking station plus monitor combinations. I am still trying to find a pattern. I was able to ssh in and use apport to save this bug information. The gnome-shell process was hung at 100% CPU utilisation. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.1-0ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Oct 17 15:56:34 2017 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell GsettingsChanges: b'org.gnome.shell' b'command-history' b"['gnome-terminal']" b'org.gnome.shell' b'had-bluetooth-devices-setup' b'true' b'org.gnome.shell' b'favorite-apps' b"['ubiquity.desktop', 'org.gnome.Nautilus.desktop', 'firefox.desktop', 'libreoffice-writer.desktop', 'libreoffice-calc.desktop', 'libreoffice-impress.desktop', 'org.gnome.Software.desktop', 'gnome-control-center.desktop']" b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2016-05-31 (504 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: gnome-shell UpgradeStatus: Upgraded to artful on 2017-10-05 (12 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1724259/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1724259] Re: gnome-shell frozen and using 100% CPU after docking and display configuration change
>From the other bug (this is getting a bit tiring): I was able to trigger the crash pretty easily with the old library still in use by opening and closing the lid a few times in quick succession and then trying to type an update to this bug. After restarting I was not immediately able to trigger it, but instead brought gnome-shell down with an assertion (g_malloc failed to allocate 1.8x10^19 bytes). Working down the stack a few frames it looked like it was trying to use an invalid structure, presumably in memory which had already been freed. Which at least raises the possibility that gnome-shell has some memory use bug which triggers on suspend and resume and that libinput was collateral damage. I am thinking of rebuilding gnome-shell with memory debugging enabled. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1724259 Title: gnome-shell frozen and using 100% CPU after docking and display configuration change Status in gnome-shell package in Ubuntu: Incomplete Bug description: I have been having regular system freezes after switching from using my laptop stand-alone to waking it up on a docking station with an external monitor. I have seen this using two identical docking station plus monitor combinations. I am still trying to find a pattern. I was able to ssh in and use apport to save this bug information. The gnome-shell process was hung at 100% CPU utilisation. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.1-0ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Oct 17 15:56:34 2017 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell GsettingsChanges: b'org.gnome.shell' b'command-history' b"['gnome-terminal']" b'org.gnome.shell' b'had-bluetooth-devices-setup' b'true' b'org.gnome.shell' b'favorite-apps' b"['ubiquity.desktop', 'org.gnome.Nautilus.desktop', 'firefox.desktop', 'libreoffice-writer.desktop', 'libreoffice-calc.desktop', 'libreoffice-impress.desktop', 'org.gnome.Software.desktop', 'gnome-control-center.desktop']" b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2016-05-31 (504 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: gnome-shell UpgradeStatus: Upgraded to artful on 2017-10-05 (12 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1724259/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1724259] Re: gnome-shell frozen and using 100% CPU after docking and display configuration change
I have rebuilt libinput10 with the patch in that freedesktop.org bug report and will see if that helps things before trying to submit anything to launchpad. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1724259 Title: gnome-shell frozen and using 100% CPU after docking and display configuration change Status in gnome-shell package in Ubuntu: Incomplete Bug description: I have been having regular system freezes after switching from using my laptop stand-alone to waking it up on a docking station with an external monitor. I have seen this using two identical docking station plus monitor combinations. I am still trying to find a pattern. I was able to ssh in and use apport to save this bug information. The gnome-shell process was hung at 100% CPU utilisation. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.1-0ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Oct 17 15:56:34 2017 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell GsettingsChanges: b'org.gnome.shell' b'command-history' b"['gnome-terminal']" b'org.gnome.shell' b'had-bluetooth-devices-setup' b'true' b'org.gnome.shell' b'favorite-apps' b"['ubiquity.desktop', 'org.gnome.Nautilus.desktop', 'firefox.desktop', 'libreoffice-writer.desktop', 'libreoffice-calc.desktop', 'libreoffice-impress.desktop', 'org.gnome.Software.desktop', 'gnome-control-center.desktop']" b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2016-05-31 (504 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: gnome-shell UpgradeStatus: Upgraded to artful on 2017-10-05 (12 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1724259/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1724259] Re: gnome-shell frozen and using 100% CPU after docking and display configuration change
I installed debug symbols for libinput and had a look at the core file, and it looks very much like this: https://bugs.freedesktop.org/show_bug.cgi?id=103298 I am missing the top frame in that stack trace, but I am guessing that is just chance based on when I took the trace. The description of how to trigger it looks like it could apply too. In any case, here is my trace: (gdb) bt #0 0x7f6b37a2ccc7 in post_device_event (device=device@entry=0x56373d197e80, time=time@entry=1377003141, type=type@entry= LIBINPUT_EVENT_KEYBOARD_KEY, event=0x56373e972770) at libinput.c:2312 #1 0x7f6b37a2df5f in keyboard_notify_key (device=device@entry=0x56373d197e80, time=time@entry=1377003141, key=, state=) at libinput.c:2412 #2 0x7f6b37a30ab7 in fallback_keyboard_notify_key (device=device@entry=0x56373d197e80, time=time@entry=1377003141, key=, state=, dispatch=) at evdev.c:173 #3 0x7f6b37a339b3 in fallback_process_key (e=0x7ffe3b444aa0, e=0x7ffe3b444aa0, time=1377003141, device=0x56373d197e80, dispatch=) at evdev.c:969 #4 0x7f6b37a339b3 in fallback_process (evdev_dispatch=, device=0x56373d197e80, event=0x7ffe3b444aa0, time=1377003141) at evdev.c:1301 #5 0x7f6b37a31159 in evdev_process_event (e=0x7ffe3b444aa0, device=0x56373d197e80) at evdev.c:2052 #6 0x7f6b37a31159 in evdev_device_dispatch_one (ev=0x7ffe3b444aa0, device=0x56373d197e80) at evdev.c:2060 #7 0x7f6b37a31159 in evdev_device_dispatch (data=0x56373d197e80) at evdev.c:2119 #8 0x7f6b37a2cdaf in libinput_dispatch (libinput=0x56373d123d60) at libinput.c:2196 #9 0x7f6b4113be9c in () ---Type to continue, or q to quit--- at /usr/lib/x86_64-linux-gnu/mutter/libmutter-clutter-1.so #10 0x7f6b424c2fb7 in g_main_context_dispatch () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #11 0x7f6b424c31f0 in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #12 0x7f6b424c3502 in g_main_loop_run () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #13 0x7f6b409f868c in meta_run () at /usr/lib/x86_64-linux-gnu/libmutter-1.so.0 #14 0x56373c9ec2e7 in () #15 0x7f6b4038a1c1 in __libc_start_main (main= 0x56373c9ebef0, argc=1, argv=0x7ffe3b444f78, init=, fini=, rtld_fini=, stack_end=0x7ffe3b444f68) at ../csu/libc-start.c:308 #16 0x56373c9ec3fa in () I will not fiddle around trying to properly upload the apport report just now, but I will keep it around locally. ** Bug watch added: freedesktop.org Bugzilla #103298 https://bugs.freedesktop.org/show_bug.cgi?id=103298 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1724259 Title: gnome-shell frozen and using 100% CPU after docking and display configuration change Status in gnome-shell package in Ubuntu: Incomplete Bug description: I have been having regular system freezes after switching from using my laptop stand-alone to waking it up on a docking station with an external monitor. I have seen this using two identical docking station plus monitor combinations. I am still trying to find a pattern. I was able to ssh in and use apport to save this bug information. The gnome-shell process was hung at 100% CPU utilisation. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.1-0ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Oct 17 15:56:34 2017 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell GsettingsChanges: b'org.gnome.shell' b'command-history' b"['gnome-terminal']" b'org.gnome.shell' b'had-bluetooth-devices-setup' b'true' b'org.gnome.shell' b'favorite-apps' b"['ubiquity.desktop', 'org.gnome.Nautilus.desktop', 'firefox.desktop', 'libreoffice-writer.desktop', 'libreoffice-calc.desktop', 'libreoffice-impress.desktop', 'org.gnome.Software.desktop', 'gnome-control-center.desktop']" b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2016-05-31 (504 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: gnome-shell UpgradeStatus: Upgraded to artful on 2017-10-05 (12 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1724259/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1724259] Re: gnome-shell frozen and using 100% CPU after docking and display configuration change
That won't fix the outdated packages (one of them was curl...) though, will it? And does disabled mean that Launchpad will refuse to accept the upload even if my system tries to send it? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1724259 Title: gnome-shell frozen and using 100% CPU after docking and display configuration change Status in gnome-shell package in Ubuntu: Incomplete Bug description: I have been having regular system freezes after switching from using my laptop stand-alone to waking it up on a docking station with an external monitor. I have seen this using two identical docking station plus monitor combinations. I am still trying to find a pattern. I was able to ssh in and use apport to save this bug information. The gnome-shell process was hung at 100% CPU utilisation. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.1-0ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Oct 17 15:56:34 2017 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell GsettingsChanges: b'org.gnome.shell' b'command-history' b"['gnome-terminal']" b'org.gnome.shell' b'had-bluetooth-devices-setup' b'true' b'org.gnome.shell' b'favorite-apps' b"['ubiquity.desktop', 'org.gnome.Nautilus.desktop', 'firefox.desktop', 'libreoffice-writer.desktop', 'libreoffice-calc.desktop', 'libreoffice-impress.desktop', 'org.gnome.Software.desktop', 'gnome-control-center.desktop']" b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2016-05-31 (504 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: gnome-shell UpgradeStatus: Upgraded to artful on 2017-10-05 (12 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1724259/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1724259] Re: gnome-shell frozen and using 100% CPU after docking and display configuration change
I checked and it was the main thread which was using CPU. Uploading a crash report (Apport would not submit it due to a couple of outdated packages). Note that this is on a different system with a fresh Ubuntu 17.10 install (not upgraded; but the report should tell you all that). ** Attachment added: "crash.zip" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1724259/+attachment/4996103/+files/crash.zip -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1724259 Title: gnome-shell frozen and using 100% CPU after docking and display configuration change Status in gnome-shell package in Ubuntu: Incomplete Bug description: I have been having regular system freezes after switching from using my laptop stand-alone to waking it up on a docking station with an external monitor. I have seen this using two identical docking station plus monitor combinations. I am still trying to find a pattern. I was able to ssh in and use apport to save this bug information. The gnome-shell process was hung at 100% CPU utilisation. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.1-0ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Oct 17 15:56:34 2017 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell GsettingsChanges: b'org.gnome.shell' b'command-history' b"['gnome-terminal']" b'org.gnome.shell' b'had-bluetooth-devices-setup' b'true' b'org.gnome.shell' b'favorite-apps' b"['ubiquity.desktop', 'org.gnome.Nautilus.desktop', 'firefox.desktop', 'libreoffice-writer.desktop', 'libreoffice-calc.desktop', 'libreoffice-impress.desktop', 'org.gnome.Software.desktop', 'gnome-control-center.desktop']" b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2016-05-31 (504 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: gnome-shell UpgradeStatus: Upgraded to artful on 2017-10-05 (12 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1724259/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1724259] Re: gnome-shell frozen and using 100% CPU after docking and display configuration change
Thank you. I assume then that my failure to get a crash report was due to the GNOME Shell process and not to the underlying mechanism. I will just check the GNOME Shell/Mutter/whatever source next time beforehand. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1724259 Title: gnome-shell frozen and using 100% CPU after docking and display configuration change Status in gnome-shell package in Ubuntu: Incomplete Bug description: I have been having regular system freezes after switching from using my laptop stand-alone to waking it up on a docking station with an external monitor. I have seen this using two identical docking station plus monitor combinations. I am still trying to find a pattern. I was able to ssh in and use apport to save this bug information. The gnome-shell process was hung at 100% CPU utilisation. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.1-0ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Oct 17 15:56:34 2017 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell GsettingsChanges: b'org.gnome.shell' b'command-history' b"['gnome-terminal']" b'org.gnome.shell' b'had-bluetooth-devices-setup' b'true' b'org.gnome.shell' b'favorite-apps' b"['ubiquity.desktop', 'org.gnome.Nautilus.desktop', 'firefox.desktop', 'libreoffice-writer.desktop', 'libreoffice-calc.desktop', 'libreoffice-impress.desktop', 'org.gnome.Software.desktop', 'gnome-control-center.desktop']" b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2016-05-31 (504 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: gnome-shell UpgradeStatus: Upgraded to artful on 2017-10-05 (12 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1724259/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1724259] Re: gnome-shell frozen and using 100% CPU after docking and display configuration change
I will do that next time I see this. A question: is there a signal I can send to the process (SEGV?) to trigger an Apport bug report in /var/crash? And would that make things easier for you? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1724259 Title: gnome-shell frozen and using 100% CPU after docking and display configuration change Status in gnome-shell package in Ubuntu: Incomplete Bug description: I have been having regular system freezes after switching from using my laptop stand-alone to waking it up on a docking station with an external monitor. I have seen this using two identical docking station plus monitor combinations. I am still trying to find a pattern. I was able to ssh in and use apport to save this bug information. The gnome-shell process was hung at 100% CPU utilisation. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.1-0ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Oct 17 15:56:34 2017 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell GsettingsChanges: b'org.gnome.shell' b'command-history' b"['gnome-terminal']" b'org.gnome.shell' b'had-bluetooth-devices-setup' b'true' b'org.gnome.shell' b'favorite-apps' b"['ubiquity.desktop', 'org.gnome.Nautilus.desktop', 'firefox.desktop', 'libreoffice-writer.desktop', 'libreoffice-calc.desktop', 'libreoffice-impress.desktop', 'org.gnome.Software.desktop', 'gnome-control-center.desktop']" b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2016-05-31 (504 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: gnome-shell UpgradeStatus: Upgraded to artful on 2017-10-05 (12 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1724259/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1724259] Re: gnome-shell frozen and using 100% CPU after docking and display configuration change
Here is a gdb stacktrace. I tried sending signal 3 to the process in the hope that it would trigger an apport bug report, but it did not. ** Attachment added: "gdb.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1724259/+attachment/4991557/+files/gdb.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1724259 Title: gnome-shell frozen and using 100% CPU after docking and display configuration change Status in gnome-shell package in Ubuntu: Incomplete Bug description: I have been having regular system freezes after switching from using my laptop stand-alone to waking it up on a docking station with an external monitor. I have seen this using two identical docking station plus monitor combinations. I am still trying to find a pattern. I was able to ssh in and use apport to save this bug information. The gnome-shell process was hung at 100% CPU utilisation. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.1-0ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Oct 17 15:56:34 2017 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell GsettingsChanges: b'org.gnome.shell' b'command-history' b"['gnome-terminal']" b'org.gnome.shell' b'had-bluetooth-devices-setup' b'true' b'org.gnome.shell' b'favorite-apps' b"['ubiquity.desktop', 'org.gnome.Nautilus.desktop', 'firefox.desktop', 'libreoffice-writer.desktop', 'libreoffice-calc.desktop', 'libreoffice-impress.desktop', 'org.gnome.Software.desktop', 'gnome-control-center.desktop']" b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2016-05-31 (504 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: gnome-shell UpgradeStatus: Upgraded to artful on 2017-10-05 (12 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1724259/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1722725] Re: GNOME Shell disabling wrong screen when docking laptop
I have definitely observed bug 1716160 as well, even after correcting the GNOME settings (though it happens less often then). However this does not match either of the two. I still do not have a good feeling for exactly when it happens, so if you do not mind I will just update the bug next time it triggers with an unstructured chronology of what happened before. It might be related to bug 1723025, but I can't say for sure. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1722725 Title: GNOME Shell disabling wrong screen when docking laptop Status in gnome-shell package in Ubuntu: Incomplete Bug description: I often switch between working with a docking station, closed laptop and an external monitor, and an open laptop without docking station or monitor. I noticed since updating to 17.10 that GNOME Shell would not switch correctly from the setup where the laptop was being used open without a docking station to the other. When I opened the laptop in the docking station the external monitor would come on, and when I closed the laptop it went off again. I manually switched the primary screen to be the external one and that solved it for now, so I assume that GNOME Shell was disabling the external screen instead of the internal one (it is a bit hard to see, and I have not yet tried ssh- ing in). ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Uname: Linux 4.13.0-12-generic x86_64 ApportVersion: 2.20.7-0ubuntu2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Oct 11 09:06:34 2017 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.shell' b'favorite-apps' b"['ubiquity.desktop', 'org.gnome.Nautilus.desktop', 'firefox.desktop', 'libreoffice-writer.desktop', 'libreoffice-calc.desktop', 'libreoffice-impress.desktop', 'org.gnome.Software.desktop', 'gnome-control-center.desktop']" b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2016-05-31 (497 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: gnome-shell UpgradeStatus: Upgraded to artful on 2017-10-05 (6 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1722725/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1724886] Re: gnome-shell assert failure: gnome-shell: libinput.c:2157: assertion failed: libinput_device_destroy: list_empty(>event_listeners)
** Summary changed: - gnome-shell assert failure: gnome-shell: libinput.c:2157: libinput_device_destroy: list_empty(>event_listeners) + gnome-shell assert failure: gnome-shell: libinput.c:2157: assertion failed: libinput_device_destroy: list_empty(>event_listeners) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1724886 Title: gnome-shell assert failure: gnome-shell: libinput.c:2157: assertion failed: libinput_device_destroy: list_empty(>event_listeners) Status in gnome-shell package in Ubuntu: New Bug description: Sequence of events before this occurred: I started a rebuild of VirtualBox without disabling the "dangerous parts" while running a virtual machine, which brought my machine to its knees with swapping. After I had managed to kill the build and the machine over ssh and turn off the swap, the desktop was no longer responsive. Switching to a VT and back brought it back at a low resolution. I opened the configuration panel, wanted to select the monitor settings and the desktop crashed. ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.1-0ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 AssertionMessage: gnome-shell: libinput.c:2157: libinput_device_destroy: Проверочное утверждение «list_empty(>event_listeners)» не выполнено. CurrentDesktop: ubuntu:GNOME Date: Thu Oct 19 17:07:03 2017 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell GsettingsChanges: b'org.gnome.shell' b'command-history' b"['gnome-terminal']" b'org.gnome.shell' b'had-bluetooth-devices-setup' b'true' b'org.gnome.shell' b'favorite-apps' b"['ubiquity.desktop', 'org.gnome.Nautilus.desktop', 'firefox.desktop', 'libreoffice-writer.desktop', 'libreoffice-calc.desktop', 'libreoffice-impress.desktop', 'org.gnome.Software.desktop', 'gnome-control-center.desktop']" b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2016-05-31 (506 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) ProcCmdline: /usr/bin/gnome-shell Signal: 6 SourcePackage: gnome-shell StacktraceTop: __assert_fail_base (fmt=, assertion=assertion@entry=0x7f6d70c7e6b0 "list_empty(>event_listeners)", file=file@entry=0x7f6d70c7e56d "libinput.c", line=line@entry=2157, function=function@entry=0x7f6d70c7ee30 "libinput_device_destroy") at assert.c:92 __GI___assert_fail (assertion=0x7f6d70c7e6b0 "list_empty(>event_listeners)", file=0x7f6d70c7e56d "libinput.c", line=2157, function=0x7f6d70c7ee30 "libinput_device_destroy") at assert.c:101 () at /usr/lib/x86_64-linux-gnu/libinput.so.10 libinput_device_unref () at /usr/lib/x86_64-linux-gnu/libinput.so.10 () at /usr/lib/x86_64-linux-gnu/mutter/libmutter-clutter-1.so Title: gnome-shell assert failure: gnome-shell: libinput.c:2157: libinput_device_destroy: Проверочное утверждение «list_empty(>event_listeners)» не выполнено. UpgradeStatus: Upgraded to artful on 2017-10-05 (14 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sbuild sudo vboxusers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1724886/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1724259] Re: System freeze after docking and display configuration change
Looking at the journald error log, the problem happened after Okt 17 15:27:08. I hoped that apport would take a stack trace of the gnome- shell process, but I will probably have to do that myself when I get the chance. Can you retrace a stack trace if the debug packages are not installed? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1724259 Title: System freeze after docking and display configuration change Status in gnome-shell package in Ubuntu: New Bug description: I have been having regular system freezes after switching from using my laptop stand-alone to waking it up on a docking station with an external monitor. I have seen this using two identical docking station plus monitor combinations. I am still trying to find a pattern. I was able to ssh in and use apport to save this bug information. The gnome-shell process was hung at 100% CPU utilisation. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.1-0ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Oct 17 15:56:34 2017 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell GsettingsChanges: b'org.gnome.shell' b'command-history' b"['gnome-terminal']" b'org.gnome.shell' b'had-bluetooth-devices-setup' b'true' b'org.gnome.shell' b'favorite-apps' b"['ubiquity.desktop', 'org.gnome.Nautilus.desktop', 'firefox.desktop', 'libreoffice-writer.desktop', 'libreoffice-calc.desktop', 'libreoffice-impress.desktop', 'org.gnome.Software.desktop', 'gnome-control-center.desktop']" b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2016-05-31 (504 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: gnome-shell UpgradeStatus: Upgraded to artful on 2017-10-05 (12 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1724259/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1723075] Re: System freeze after docking and display configuration change
*** This bug is a duplicate of bug 1724259 *** https://bugs.launchpad.net/bugs/1724259 Reported this again using apport as bug 1724259. ** This bug has been marked a duplicate of bug 1724259 System freeze after docking and display configuration change -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1723075 Title: System freeze after docking and display configuration change Status in xorg package in Ubuntu: New Bug description: I have been having regular system freezes after switching from using my laptop stand-alone to waking it up on a docking station with an external monitor. I have seen this using two identical docking station plus monitor combinations. I am still trying to find a pattern. I often find the laptop going to sleep again immediately after being woken up. When it freezes, the screen saver is visible on the internal display and the external monitor is (I think) enabled but blank. I saw this with 4.13.0-13-generic, and have not yet had the chance to test it with 4.13.0-15-generic. I have also not had the chance yet to try to ssh in. 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 .tmp.unity_support_test.0: ApportVersion: 2.20.7-0ubuntu2 Architecture: amd64 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Oct 12 11:52:51 2017 DistUpgraded: 2017-10-05 07:40:01,856 ERROR got an error from dpkg for pkg: 'linux-image-extra-4.13.0-12-generic': 'subprocess installed post-installation script returned error exit status 1' DistroCodename: artful DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: Several times a week GpuHangReproducibility: Occurs more often under certain circumstances GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell 2nd Generation Core Processor Family Integrated Graphics Controller [1028:0493] InstallationDate: Installed on 2016-05-31 (498 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: Dell Inc. Latitude E6420 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-15-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to artful on 2017-10-05 (7 days ago) dmi.bios.date: 11/14/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A21 dmi.board.name: 0K0DNP dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA21:bd11/14/2013:svnDellInc.:pnLatitudeE6420:pvr01:rvnDellInc.:rn0K0DNP:rvrA02:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6420 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.13.1+17.10.20170901-0ubuntu1 version.libdrm2: libdrm2 2.4.83-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20170309-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1723075/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1724259] [NEW] System freeze after docking and display configuration change
Public bug reported: I have been having regular system freezes after switching from using my laptop stand-alone to waking it up on a docking station with an external monitor. I have seen this using two identical docking station plus monitor combinations. I am still trying to find a pattern. I was able to ssh in and use apport to save this bug information. The gnome-shell process was hung at 100% CPU utilisation. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.1-0ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Oct 17 15:56:34 2017 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell GsettingsChanges: b'org.gnome.shell' b'command-history' b"['gnome-terminal']" b'org.gnome.shell' b'had-bluetooth-devices-setup' b'true' b'org.gnome.shell' b'favorite-apps' b"['ubiquity.desktop', 'org.gnome.Nautilus.desktop', 'firefox.desktop', 'libreoffice-writer.desktop', 'libreoffice-calc.desktop', 'libreoffice-impress.desktop', 'org.gnome.Software.desktop', 'gnome-control-center.desktop']" b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2016-05-31 (504 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: gnome-shell UpgradeStatus: Upgraded to artful on 2017-10-05 (12 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1724259 Title: System freeze after docking and display configuration change Status in gnome-shell package in Ubuntu: New Bug description: I have been having regular system freezes after switching from using my laptop stand-alone to waking it up on a docking station with an external monitor. I have seen this using two identical docking station plus monitor combinations. I am still trying to find a pattern. I was able to ssh in and use apport to save this bug information. The gnome-shell process was hung at 100% CPU utilisation. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.1-0ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Oct 17 15:56:34 2017 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell GsettingsChanges: b'org.gnome.shell' b'command-history' b"['gnome-terminal']" b'org.gnome.shell' b'had-bluetooth-devices-setup' b'true' b'org.gnome.shell' b'favorite-apps' b"['ubiquity.desktop', 'org.gnome.Nautilus.desktop', 'firefox.desktop', 'libreoffice-writer.desktop', 'libreoffice-calc.desktop', 'libreoffice-impress.desktop', 'org.gnome.Software.desktop', 'gnome-control-center.desktop']" b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2016-05-31 (504 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: gnome-shell UpgradeStatus: Upgraded to artful on 2017-10-05 (12 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1724259/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1723075] Re: System freeze after docking and display configuration change
Just got this again with 4.13.0-15-generic after suspending and resuming the laptop. No docking station or screen reconfiguration. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1723075 Title: System freeze after docking and display configuration change Status in xorg package in Ubuntu: New Bug description: I have been having regular system freezes after switching from using my laptop stand-alone to waking it up on a docking station with an external monitor. I have seen this using two identical docking station plus monitor combinations. I am still trying to find a pattern. I often find the laptop going to sleep again immediately after being woken up. When it freezes, the screen saver is visible on the internal display and the external monitor is (I think) enabled but blank. I saw this with 4.13.0-13-generic, and have not yet had the chance to test it with 4.13.0-15-generic. I have also not had the chance yet to try to ssh in. 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 .tmp.unity_support_test.0: ApportVersion: 2.20.7-0ubuntu2 Architecture: amd64 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Oct 12 11:52:51 2017 DistUpgraded: 2017-10-05 07:40:01,856 ERROR got an error from dpkg for pkg: 'linux-image-extra-4.13.0-12-generic': 'subprocess installed post-installation script returned error exit status 1' DistroCodename: artful DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: Several times a week GpuHangReproducibility: Occurs more often under certain circumstances GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell 2nd Generation Core Processor Family Integrated Graphics Controller [1028:0493] InstallationDate: Installed on 2016-05-31 (498 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: Dell Inc. Latitude E6420 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-15-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to artful on 2017-10-05 (7 days ago) dmi.bios.date: 11/14/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A21 dmi.board.name: 0K0DNP dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA21:bd11/14/2013:svnDellInc.:pnLatitudeE6420:pvr01:rvnDellInc.:rn0K0DNP:rvrA02:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6420 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.13.1+17.10.20170901-0ubuntu1 version.libdrm2: libdrm2 2.4.83-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20170309-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1723075/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1723075] [NEW] System freeze after docking and display configuration change
Public bug reported: I have been having regular system freezes after switching from using my laptop stand-alone to waking it up on a docking station with an external monitor. I have seen this using two identical docking station plus monitor combinations. I am still trying to find a pattern. I often find the laptop going to sleep again immediately after being woken up. When it freezes, the screen saver is visible on the internal display and the external monitor is (I think) enabled but blank. I saw this with 4.13.0-13-generic, and have not yet had the chance to test it with 4.13.0-15-generic. I have also not had the chance yet to try to ssh in. 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 .tmp.unity_support_test.0: ApportVersion: 2.20.7-0ubuntu2 Architecture: amd64 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Oct 12 11:52:51 2017 DistUpgraded: 2017-10-05 07:40:01,856 ERROR got an error from dpkg for pkg: 'linux-image-extra-4.13.0-12-generic': 'subprocess installed post-installation script returned error exit status 1' DistroCodename: artful DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: Several times a week GpuHangReproducibility: Occurs more often under certain circumstances GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell 2nd Generation Core Processor Family Integrated Graphics Controller [1028:0493] InstallationDate: Installed on 2016-05-31 (498 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: Dell Inc. Latitude E6420 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-15-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to artful on 2017-10-05 (7 days ago) dmi.bios.date: 11/14/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A21 dmi.board.name: 0K0DNP dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA21:bd11/14/2013:svnDellInc.:pnLatitudeE6420:pvr01:rvnDellInc.:rn0K0DNP:rvrA02:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6420 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.13.1+17.10.20170901-0ubuntu1 version.libdrm2: libdrm2 2.4.83-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20170309-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful freeze ubuntu wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1723075 Title: System freeze after docking and display configuration change Status in xorg package in Ubuntu: New Bug description: I have been having regular system freezes after switching from using my laptop stand-alone to waking it up on a docking station with an external monitor. I have seen this using two identical docking station plus monitor combinations. I am still trying to find a pattern. I often find the laptop going to sleep again immediately after being woken up. When it freezes, the screen saver is visible on the internal display and the external monitor is (I think) enabled but blank. I saw this with 4.13.0-13-generic, and have not yet had the chance to test it with 4.13.0-15-generic. I have also not had the chance yet to try to ssh in. 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 .tmp.unity_support_test.0: ApportVersion: 2.20.7-0ubuntu2 Architecture: amd64 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Oct 12 11:52:51 2017 DistUpgraded: 2017-10-05 07:40:01,856 ERROR got an error from dpkg for pkg: 'linux-image-extra-4.13.0-12-generic': 'subprocess installed post-installation script returned error exit status 1' DistroCodename: artful DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: Several times a week GpuHangReproducibility: Occurs more often under certain circumstances GpuHangStarted: Immediately after installing this version of
[Desktop-packages] [Bug 1723045] [NEW] GNOME Terminal does not get into GNOME Shell's frequently used list
Public bug reported: I use GNOME Terminal frequently. I tend (at least since I upgraded) to start it from GNOME Shell's dash, using the "all applications" category. For some reason it never makes it to the frequently used list. If it is of interest: $ grep terminal .local/share/gnome-shell/application_state I wonder whether the fact that my desktop is mainly Russian localised (the main folder names are in English) is related, but my guess is that it is not. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.1-0ubuntu2 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 CurrentDesktop: ubuntu:GNOME Date: Thu Oct 12 11:12:37 2017 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.shell' b'favorite-apps' b"['ubiquity.desktop', 'org.gnome.Nautilus.desktop', 'firefox.desktop', 'libreoffice-writer.desktop', 'libreoffice-calc.desktop', 'libreoffice-impress.desktop', 'org.gnome.Software.desktop', 'gnome-control-center.desktop']" b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2016-05-31 (498 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: gnome-shell UpgradeStatus: Upgraded to artful on 2017-10-05 (7 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1723045 Title: GNOME Terminal does not get into GNOME Shell's frequently used list Status in gnome-shell package in Ubuntu: New Bug description: I use GNOME Terminal frequently. I tend (at least since I upgraded) to start it from GNOME Shell's dash, using the "all applications" category. For some reason it never makes it to the frequently used list. If it is of interest: $ grep terminal .local/share/gnome-shell/application_state I wonder whether the fact that my desktop is mainly Russian localised (the main folder names are in English) is related, but my guess is that it is not. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.1-0ubuntu2 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 CurrentDesktop: ubuntu:GNOME Date: Thu Oct 12 11:12:37 2017 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.shell' b'favorite-apps' b"['ubiquity.desktop', 'org.gnome.Nautilus.desktop', 'firefox.desktop', 'libreoffice-writer.desktop', 'libreoffice-calc.desktop', 'libreoffice-impress.desktop', 'org.gnome.Software.desktop', 'gnome-control-center.desktop']" b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2016-05-31 (498 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: gnome-shell UpgradeStatus: Upgraded to artful on 2017-10-05 (7 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1723045/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1722725] [NEW] GNOME Shell disabling wrong screen when docking laptop
Public bug reported: I often switch between working with a docking station, closed laptop and an external monitor, and an open laptop without docking station or monitor. I noticed since updating to 17.10 that GNOME Shell would not switch correctly from the setup where the laptop was being used open without a docking station to the other. When I opened the laptop in the docking station the external monitor would come on, and when I closed the laptop it went off again. I manually switched the primary screen to be the external one and that solved it for now, so I assume that GNOME Shell was disabling the external screen instead of the internal one (it is a bit hard to see, and I have not yet tried ssh-ing in). ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Uname: Linux 4.13.0-12-generic x86_64 ApportVersion: 2.20.7-0ubuntu2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Oct 11 09:06:34 2017 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.shell' b'favorite-apps' b"['ubiquity.desktop', 'org.gnome.Nautilus.desktop', 'firefox.desktop', 'libreoffice-writer.desktop', 'libreoffice-calc.desktop', 'libreoffice-impress.desktop', 'org.gnome.Software.desktop', 'gnome-control-center.desktop']" b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2016-05-31 (497 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: gnome-shell UpgradeStatus: Upgraded to artful on 2017-10-05 (6 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1722725 Title: GNOME Shell disabling wrong screen when docking laptop Status in gnome-shell package in Ubuntu: New Bug description: I often switch between working with a docking station, closed laptop and an external monitor, and an open laptop without docking station or monitor. I noticed since updating to 17.10 that GNOME Shell would not switch correctly from the setup where the laptop was being used open without a docking station to the other. When I opened the laptop in the docking station the external monitor would come on, and when I closed the laptop it went off again. I manually switched the primary screen to be the external one and that solved it for now, so I assume that GNOME Shell was disabling the external screen instead of the internal one (it is a bit hard to see, and I have not yet tried ssh- ing in). ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Uname: Linux 4.13.0-12-generic x86_64 ApportVersion: 2.20.7-0ubuntu2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Oct 11 09:06:34 2017 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.shell' b'favorite-apps' b"['ubiquity.desktop', 'org.gnome.Nautilus.desktop', 'firefox.desktop', 'libreoffice-writer.desktop', 'libreoffice-calc.desktop', 'libreoffice-impress.desktop', 'org.gnome.Software.desktop', 'gnome-control-center.desktop']" b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2016-05-31 (497 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: gnome-shell UpgradeStatus: Upgraded to artful on 2017-10-05 (6 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1722725/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1640112] [NEW] Irregular USB network tethering failures
Public bug reported: Reporting this against network manager for want of better information. Sorry for the imprecise report - I will be glad to observe and update. Since upgrading to 16.10 I have had problems with my USB "ethernet" network connection provided by a tethered Android 2.3 device. Initial connection works well, but after a while Ubuntu looses connection, indicated by the nm-applet icon switching to "wifi connecting". Ubuntu seems unable to obtain an IP address. Neither rebooting the laptop nor restarting the phone help, but after a while the problem goes away on its own. In the meantime I am able to tether using the phone's wireless hotspot functionality. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: network-manager 1.2.4-0ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0 Uname: Linux 4.8.0-26-generic x86_64 ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Tue Nov 8 11:00:59 2016 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2016-05-31 (160 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH eno1ethernet connected /org/freedesktop/NetworkManager/Devices/2 Wired connection 2 a48d1ead-bcd2-37cb-8731-1d687642ff2c /org/freedesktop/NetworkManager/ActiveConnection/7 wlp2s0 wifi connected /org/freedesktop/NetworkManager/Devices/1 clear 4c47ad41-0865-488f-bcf6-2cc10a2d5a87 /org/freedesktop/NetworkManager/ActiveConnection/6 lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/3 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.2.4connected started full enabled enabled enabled enabled enabled ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug yakkety -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1640112 Title: Irregular USB network tethering failures Status in network-manager package in Ubuntu: New Bug description: Reporting this against network manager for want of better information. Sorry for the imprecise report - I will be glad to observe and update. Since upgrading to 16.10 I have had problems with my USB "ethernet" network connection provided by a tethered Android 2.3 device. Initial connection works well, but after a while Ubuntu looses connection, indicated by the nm-applet icon switching to "wifi connecting". Ubuntu seems unable to obtain an IP address. Neither rebooting the laptop nor restarting the phone help, but after a while the problem goes away on its own. In the meantime I am able to tether using the phone's wireless hotspot functionality. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: network-manager 1.2.4-0ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0 Uname: Linux 4.8.0-26-generic x86_64 ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Tue Nov 8 11:00:59 2016 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2016-05-31 (160 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH eno1ethernet connected /org/freedesktop/NetworkManager/Devices/2 Wired connection 2 a48d1ead-bcd2-37cb-8731-1d687642ff2c /org/freedesktop/NetworkManager/ActiveConnection/7 wlp2s0 wifi connected /org/freedesktop/NetworkManager/Devices/1 clear 4c47ad41-0865-488f-bcf6-2cc10a2d5a87 /org/freedesktop/NetworkManager/ActiveConnection/6 lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/3 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW
[Desktop-packages] [Bug 1599775] Re: "low-graphics mode" in VirtualBox guest, but X server running
I hope this upstream change set will do the trick: https://www.virtualbox.org/changeset/62242 Re comment 11, I looked at Mesa to see how they were distinguishing client and server GL and applied that to my code (see comments in change set). To summarise the issue: the tricks that we were playing to prevent the X server from loading our GL libraries, which unlike Mesa are designed to be client only, were not working here, and the X server process was failing when our libraries tried to call a function (RTR3InitDll) in another library which gets loaded by clients but which the X server was not (not sure why). I refined the tricks by studying how Mesa handles detecting being loaded by the server (technically being loaded for use with GBM rather than with X11) and in addition got rid of the immediate dependency which was failing. Was that at all helpful? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1599775 Title: "low-graphics mode" in VirtualBox guest, but X server running Status in lightdm package in Ubuntu: New Bug description: I sometimes get the "low-graphics mode" message when starting an Ubuntu 16.04 virtual machine inside of VirtualBox (current development code trunk, somewhere past version 5.1 beta 3 and a debug build). When I switch to VT-7 I find the X server running without any visible issues (I am the upstream developer of the guest graphics drivers, so I have a reasonable but not infallible understanding of the X server). The virtual machine has Guest Additions installed, same vintage and also a debug build. Two screens are enabled as is 3D acceleration. The host system is also Ubuntu 16.04. I am still trying to work out what triggers the message, but in my last attempts a cold boot failed to produce it, while a clean reboot did, but only when the host system was not under load (under load as in building VirtualBox). Searching the lightdm log files led me to the message "CRITICAL **: session_get_login1_session_id: assertion 'session != NULL' failed", which in turn led me to this similar-looking Debian bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=814760 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: lightdm 1.18.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13 Uname: Linux 4.4.0-28-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Thu Jul 7 10:49:27 2016 InstallationDate: Installed on 2016-06-08 (28 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) IRC discussion at: https://irclogs.ubuntu.com/2016/07/07/%23ubuntu-devel.html#t07:52 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1599775/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1599775] Re: "low-graphics mode" in VirtualBox guest, but X server running
Sorry, that doesn't do it yet. (Shame I didn't manage to fix this for 5.0.0.) However I realised that Mesa has exactly the same problem, so I have taken a look at their code to see what they do. Also looks like a bit of a hack, but since nothing relevant can afford not to work with Mesa it should be a safe one. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1599775 Title: "low-graphics mode" in VirtualBox guest, but X server running Status in lightdm package in Ubuntu: New Bug description: I sometimes get the "low-graphics mode" message when starting an Ubuntu 16.04 virtual machine inside of VirtualBox (current development code trunk, somewhere past version 5.1 beta 3 and a debug build). When I switch to VT-7 I find the X server running without any visible issues (I am the upstream developer of the guest graphics drivers, so I have a reasonable but not infallible understanding of the X server). The virtual machine has Guest Additions installed, same vintage and also a debug build. Two screens are enabled as is 3D acceleration. The host system is also Ubuntu 16.04. I am still trying to work out what triggers the message, but in my last attempts a cold boot failed to produce it, while a clean reboot did, but only when the host system was not under load (under load as in building VirtualBox). Searching the lightdm log files led me to the message "CRITICAL **: session_get_login1_session_id: assertion 'session != NULL' failed", which in turn led me to this similar-looking Debian bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=814760 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: lightdm 1.18.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13 Uname: Linux 4.4.0-28-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Thu Jul 7 10:49:27 2016 InstallationDate: Installed on 2016-06-08 (28 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) IRC discussion at: https://irclogs.ubuntu.com/2016/07/07/%23ubuntu-devel.html#t07:52 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1599775/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1599775] Re: "low-graphics mode" in VirtualBox guest, but X server running
My apologies, I missed that one, so this is probably my bug! I will fix that and then get back to you. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1599775 Title: "low-graphics mode" in VirtualBox guest, but X server running Status in lightdm package in Ubuntu: New Bug description: I sometimes get the "low-graphics mode" message when starting an Ubuntu 16.04 virtual machine inside of VirtualBox (current development code trunk, somewhere past version 5.1 beta 3 and a debug build). When I switch to VT-7 I find the X server running without any visible issues (I am the upstream developer of the guest graphics drivers, so I have a reasonable but not infallible understanding of the X server). The virtual machine has Guest Additions installed, same vintage and also a debug build. Two screens are enabled as is 3D acceleration. The host system is also Ubuntu 16.04. I am still trying to work out what triggers the message, but in my last attempts a cold boot failed to produce it, while a clean reboot did, but only when the host system was not under load (under load as in building VirtualBox). Searching the lightdm log files led me to the message "CRITICAL **: session_get_login1_session_id: assertion 'session != NULL' failed", which in turn led me to this similar-looking Debian bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=814760 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: lightdm 1.18.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13 Uname: Linux 4.4.0-28-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Thu Jul 7 10:49:27 2016 InstallationDate: Installed on 2016-06-08 (28 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) IRC discussion at: https://irclogs.ubuntu.com/2016/07/07/%23ubuntu-devel.html#t07:52 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1599775/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1599775] Re: "low-graphics mode" in VirtualBox guest, but X server running
I was able to reproduce this with the lightdm deb file from that package installed. I did not install the other deb files built from the package. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1599775 Title: "low-graphics mode" in VirtualBox guest, but X server running Status in lightdm package in Ubuntu: New Bug description: I sometimes get the "low-graphics mode" message when starting an Ubuntu 16.04 virtual machine inside of VirtualBox (current development code trunk, somewhere past version 5.1 beta 3 and a debug build). When I switch to VT-7 I find the X server running without any visible issues (I am the upstream developer of the guest graphics drivers, so I have a reasonable but not infallible understanding of the X server). The virtual machine has Guest Additions installed, same vintage and also a debug build. Two screens are enabled as is 3D acceleration. The host system is also Ubuntu 16.04. I am still trying to work out what triggers the message, but in my last attempts a cold boot failed to produce it, while a clean reboot did, but only when the host system was not under load (under load as in building VirtualBox). Searching the lightdm log files led me to the message "CRITICAL **: session_get_login1_session_id: assertion 'session != NULL' failed", which in turn led me to this similar-looking Debian bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=814760 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: lightdm 1.18.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13 Uname: Linux 4.4.0-28-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Thu Jul 7 10:49:27 2016 InstallationDate: Installed on 2016-06-08 (28 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) IRC discussion at: https://irclogs.ubuntu.com/2016/07/07/%23ubuntu-devel.html#t07:52 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1599775/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1599775] Re: "low-graphics mode" in VirtualBox guest, but X server running
Actually, perhaps I misunderstand the lightdm log rotation and the .1 logfile does contain the relevant log. I assume the lightdm developers will know. My uneducated guess is that there is some sort of race here between lightdm and logind which needs better dependency specification. And I just checked that I do not always see this on a clean reboot either. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1599775 Title: "low-graphics mode" in VirtualBox guest, but X server running Status in lightdm package in Ubuntu: New Bug description: I sometimes get the "low-graphics mode" message when starting an Ubuntu 16.04 virtual machine inside of VirtualBox (current development code trunk, somewhere past version 5.1 beta 3 and a debug build). When I switch to VT-7 I find the X server running without any visible issues (I am the upstream developer of the guest graphics drivers, so I have a reasonable but not infallible understanding of the X server). The virtual machine has Guest Additions installed, same vintage and also a debug build. Two screens are enabled as is 3D acceleration. The host system is also Ubuntu 16.04. I am still trying to work out what triggers the message, but in my last attempts a cold boot failed to produce it, while a clean reboot did, but only when the host system was not under load (under load as in building VirtualBox). Searching the lightdm log files led me to the message "CRITICAL **: session_get_login1_session_id: assertion 'session != NULL' failed", which in turn led me to this similar-looking Debian bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=814760 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: lightdm 1.18.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13 Uname: Linux 4.4.0-28-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Thu Jul 7 10:49:27 2016 InstallationDate: Installed on 2016-06-08 (28 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1599775/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1599775] Re: "low-graphics mode" in VirtualBox guest, but X server running
Just checked, I do not have that message in the current log file, attached the file from yesterday containing the message. I asked about this on #ubuntu-devel, here are the relevant logs: (17:09:06) michael-vb: Afternoon. Not sure if this is the right place to ask, but someone will probably know what is. (17:09:06) michael-vb: I have the following problem with my VirtualBox Ubuntu 16.04 guest with development Guest Additions installed: when I start the guest I get the message "The system is running in low-graphics mode" (on VT 2) even though the X server is running fine (on VT 7). (17:09:06) michael-vb: I would very much like to know exactly what logic triggers that message so I can work out why I am triggering it and change whatever is responsible (I am the developer of the VirtualBox guest driver and Additions installer). (18:04:34) michael-vb: Interesting - I just booted the guest system twice with a loaded host (rebuilding VirtualBox) and did not get the "low-graphics mode" message. (18:27:01) michael-vb: CRITICAL: session_get_login1_session_id: assertion 'session != NULL' failed in the lightdm log file. (18:31:13) michael-vb: https://bugs.debian.org/cgi- bin/bugreport.cgi?bug=814760 (09:57:21) sladen: michael-vb: http://askubuntu.com/questions/141606/how-to-fix-the-system-is-running-in-low-graphics-mode-error (09:57:35) michael-vb: Found that already. (09:57:50) michael-vb: I am wanting to understand this as a developer, not as a user. (09:59:07) michael-vb: sladen: it was following from that askubuntu question that I found the system log entry. (09:59:34) michael-vb: The session clearly gets started just after lightdm checks whether it is running. (10:01:04) michael-vb: As I said, this does not happen under high load. I suppose the question is, who would understand this stuff well enough to tell me how I can avoid triggering it. (10:01:15) michael-vb: Or what causes the session to start too late, or lightdm too early. (10:03:00) michael-vb: I assume that some dependency is not specified well enough somewhere. (10:03:31) sladen: michael-vb: apt-get source lightdm && grep -r "Error message" is probably the most effective way of identifing the logic causing the error (if it is coming from lightdm) (10:03:31) michael-vb: But it is annoying, because if it hits users they will blame us first, not you! (10:04:15) sladen: michael-vb: I'm not too familiar with the inner workings of lightdm; the developer was Robert Ancell in the DX team (10:04:57) sladen: michael-vb: if it's happening so of the time (seemingly randomly), then there's probably a race condition (10:06:33) michael-vb: I'm sort of suspecting that it is related to the change to systemd which upset some expectation in lightdm. (10:08:13) sladen: willcooke: if you're around later, could you get in contact with michael-vb (upstream developer of VirtualBox guest driver), about debugging and resolving the "The system is running in low-graphics mode" message. https://irclogs.ubuntu.com/2016/07/07/%23ubuntu-devel.html#t07:52 onwards (10:08:50) michael-vb: willcooke: and michael dot thayer at oracle if I am not on IRC at that time. (10:08:56) michael-vb: sladen, willcooke: thanks. (10:10:59) willcooke: Trevinho, is this something you can help with? ^ (10:11:09) willcooke: It looks like it's a problem with X rather than Unity though (10:11:13) willcooke: "problem" (10:11:22) willcooke: maybe tjaalton knows what triggers it? ^ (10:13:46) talatb [~talatb@137.158.22.10] entered the room. (10:14:23) tjaalton: I don't, if lightdm is randomly not starting on debian (which doesn't have "failsafe-x") (10:15:20) tjaalton: sounds like a lightdm bug to me (10:16:59) willcooke: oki (10:17:04) willcooke: thanks tjaalton (10:30:07) willcooke: michael-vb, Hmm, I can't see anything obvious here. Please log a bug in Ubuntu against lightdm if there isn't already one, and we take take a look. (10:30:54) michael-vb: willcooke: to me it sounds like an init dependency problem. (10:31:18) sladen: michael-vb: can we get as much of the (known good) information into a Launchpad bug report (10:31:34) michael-vb: If I understood all this GNOME-systemd-login stuff better... (10:31:41) michael-vb: sladen: sounds reasonable. (10:31:44) sladen: michael-vb: and then get that linked to/from the debbugs and Askubuntu pages (10:33:25) michael-vb: Oh how nice, for reasons unknown I can no longer trigger it. (10:33:34) willcooke: \o/ (10:33:47) willcooke: fixed! (10:34:00) willcooke: certainly smells like a race then (10:34:23) michael-vb: I think that is clear enough from the Debian bug. (10:34:47) michael-vb: I think that someone from the systemd camp would be best placed to solve it. (10:36:07) michael-vb: But before I open a bug report I will at least try to track down the error in the lightdm sources. (10:39:45) sladen: yes, it would be good to point in the bug report exactly where the origin of the assert is coming from, but if it
[Desktop-packages] [Bug 1599775] Re: "low-graphics mode" in VirtualBox guest, but X server running
** Attachment added: "The log file from yesterday." https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1599775/+attachment/4696780/+files/lightdm.log.1 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1599775 Title: "low-graphics mode" in VirtualBox guest, but X server running Status in lightdm package in Ubuntu: New Bug description: I sometimes get the "low-graphics mode" message when starting an Ubuntu 16.04 virtual machine inside of VirtualBox (current development code trunk, somewhere past version 5.1 beta 3 and a debug build). When I switch to VT-7 I find the X server running without any visible issues (I am the upstream developer of the guest graphics drivers, so I have a reasonable but not infallible understanding of the X server). The virtual machine has Guest Additions installed, same vintage and also a debug build. Two screens are enabled as is 3D acceleration. The host system is also Ubuntu 16.04. I am still trying to work out what triggers the message, but in my last attempts a cold boot failed to produce it, while a clean reboot did, but only when the host system was not under load (under load as in building VirtualBox). Searching the lightdm log files led me to the message "CRITICAL **: session_get_login1_session_id: assertion 'session != NULL' failed", which in turn led me to this similar-looking Debian bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=814760 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: lightdm 1.18.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13 Uname: Linux 4.4.0-28-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Thu Jul 7 10:49:27 2016 InstallationDate: Installed on 2016-06-08 (28 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1599775/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1599775] [NEW] "low-graphics mode" in VirtualBox guest, but X server running
Public bug reported: I sometimes get the "low-graphics mode" message when starting an Ubuntu 16.04 virtual machine inside of VirtualBox (current development code trunk, somewhere past version 5.1 beta 3 and a debug build). When I switch to VT-7 I find the X server running without any visible issues (I am the upstream developer of the guest graphics drivers, so I have a reasonable but not infallible understanding of the X server). The virtual machine has Guest Additions installed, same vintage and also a debug build. Two screens are enabled as is 3D acceleration. The host system is also Ubuntu 16.04. I am still trying to work out what triggers the message, but in my last attempts a cold boot failed to produce it, while a clean reboot did, but only when the host system was not under load (under load as in building VirtualBox). Searching the lightdm log files led me to the message "CRITICAL **: session_get_login1_session_id: assertion 'session != NULL' failed", which in turn led me to this similar-looking Debian bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=814760 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: lightdm 1.18.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13 Uname: Linux 4.4.0-28-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Thu Jul 7 10:49:27 2016 InstallationDate: Installed on 2016-06-08 (28 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: lightdm (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1599775 Title: "low-graphics mode" in VirtualBox guest, but X server running Status in lightdm package in Ubuntu: New Bug description: I sometimes get the "low-graphics mode" message when starting an Ubuntu 16.04 virtual machine inside of VirtualBox (current development code trunk, somewhere past version 5.1 beta 3 and a debug build). When I switch to VT-7 I find the X server running without any visible issues (I am the upstream developer of the guest graphics drivers, so I have a reasonable but not infallible understanding of the X server). The virtual machine has Guest Additions installed, same vintage and also a debug build. Two screens are enabled as is 3D acceleration. The host system is also Ubuntu 16.04. I am still trying to work out what triggers the message, but in my last attempts a cold boot failed to produce it, while a clean reboot did, but only when the host system was not under load (under load as in building VirtualBox). Searching the lightdm log files led me to the message "CRITICAL **: session_get_login1_session_id: assertion 'session != NULL' failed", which in turn led me to this similar-looking Debian bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=814760 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: lightdm 1.18.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13 Uname: Linux 4.4.0-28-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Thu Jul 7 10:49:27 2016 InstallationDate: Installed on 2016-06-08 (28 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1599775/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1466368] Re: Middle click paste from touchpad sometimes stops working
Looks like a case of Problem between Keyboard and Chair. I notice that middle clicks work when I release the button very quickly. It is hard to say now of course, I think that that was not necessary previously, which is what mislead me. I will leave it up to others whether to keep this open or close it. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1466368 Title: Middle click paste from touchpad sometimes stops working Status in gnome-terminal package in Ubuntu: New Bug description: Quite often (subjectively nearly always) when I am using my laptop - Dell Latitude E7440 - undocked with the internal touch pad, after a while middle click paste stops working in gnome-terminal. I can middle-click paste in e.g. Firefox, but neither from nor to gnome- terminal. I have not seen this while docked with an external mouse. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: gnome-terminal 3.14.2-0ubuntu3 Uname: Linux 4.0.0-04rc2-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 CurrentDesktop: Unity Date: Thu Jun 18 08:30:11 2015 InstallationDate: Installed on 2014-08-01 (321 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) SourcePackage: gnome-terminal UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1466368/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1499747] Re: gedit crashed with SIGABRT in g_assertion_message()
Seems to be fixed here too. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/1499747 Title: gedit crashed with SIGABRT in g_assertion_message() Status in gedit package in Ubuntu: Invalid Status in glib2.0 package in Ubuntu: Fix Released Status in unity-gtk-module package in Ubuntu: Invalid Bug description: Gedit crashed just after opening a (small) text file from nautilus with "Open with". ProblemType: Crash DistroRelease: Ubuntu 15.10 Package: gedit 3.10.4-0ubuntu13 ProcVersionSignature: Ubuntu 4.2.0-11.13-lowlatency 4.2.1 Uname: Linux 4.2.0-11-lowlatency x86_64 ApportVersion: 2.18.1-0ubuntu1 Architecture: amd64 CrashCounter: 1 CurrentDesktop: Unity Date: Fri Sep 25 16:05:28 2015 ExecutablePath: /usr/bin/gedit InstallationDate: Installed on 2014-12-13 (285 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) ProcCmdline: gedit /home/username/Bureau/Export_cabmnt_329340483152739798.csv Signal: 6 SourcePackage: gedit StacktraceTop: g_assertion_message () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6 ffi_call () from /usr/lib/x86_64-linux-gnu/libffi.so.6 Title: gedit crashed with SIGABRT in g_assertion_message() UpgradeStatus: Upgraded to wily on 2015-09-21 (4 days ago) UserGroups: adm audio cdrom dialout dip libvirtd lpadmin lxd plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1499747/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1499747] Re: gedit crashed with SIGABRT in g_assertion_message()
I can also reproduce this as described in comment 14, and get it whenever I start Pidgin and log in to my Jabber account: $ pidgin ** GLib-GIO:ERROR:/build/glib2.0-pRoDo9/glib2.0-2.46.0/./gio/gmenuexporter.c:256:g_menu_exporter_menu_items_changed: assertion failed: (position + removed <= g_sequence_get_length (menu->item_links)) Aborted (core dumped) $ gedit ** GLib-GIO:ERROR:/build/glib2.0-pRoDo9/glib2.0-2.46.0/./gio/gmenuexporter.c:256:g_menu_exporter_menu_items_changed: assertion failed: (position + removed <= g_sequence_get_length (menu->item_links)) Aborted (core dumped) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/1499747 Title: gedit crashed with SIGABRT in g_assertion_message() Status in gedit package in Ubuntu: Invalid Status in glib2.0 package in Ubuntu: Invalid Status in unity-gtk-module package in Ubuntu: Triaged Bug description: Gedit crashed just after opening a (small) text file from nautilus with "Open with". ProblemType: Crash DistroRelease: Ubuntu 15.10 Package: gedit 3.10.4-0ubuntu13 ProcVersionSignature: Ubuntu 4.2.0-11.13-lowlatency 4.2.1 Uname: Linux 4.2.0-11-lowlatency x86_64 ApportVersion: 2.18.1-0ubuntu1 Architecture: amd64 CrashCounter: 1 CurrentDesktop: Unity Date: Fri Sep 25 16:05:28 2015 ExecutablePath: /usr/bin/gedit InstallationDate: Installed on 2014-12-13 (285 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) ProcCmdline: gedit /home/username/Bureau/Export_cabmnt_329340483152739798.csv Signal: 6 SourcePackage: gedit StacktraceTop: g_assertion_message () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6 ffi_call () from /usr/lib/x86_64-linux-gnu/libffi.so.6 Title: gedit crashed with SIGABRT in g_assertion_message() UpgradeStatus: Upgraded to wily on 2015-09-21 (4 days ago) UserGroups: adm audio cdrom dialout dip libvirtd lpadmin lxd plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1499747/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1492170] Re: Screen flicker and resolution problems after hot-plug
Current status: with BIOS A15 and kernel 4.2.0-11-generic I was unable to get the external screen to connect at all in an X session (a VT worked more or less fine). Now using kernel 4.3.0-040300rc3-generic and so far no visible graphical problems at all. I will keep you updated. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu. https://bugs.launchpad.net/bugs/1492170 Title: Screen flicker and resolution problems after hot-plug Status in xserver-xorg-video-intel package in Ubuntu: Incomplete Bug description: After upgrading to Wily, when I change the configuration of screens attached (specifically: dock the laptop to a docking station with a vertically larger external screen or open the laptop to activate the internal screen while correctly running with said external screen) this causes various display issues, including flickering while the mouse cursor is moved and or one screen flickering the contents of the other; incorrect resolution; incorrect offset of displayed screen contents on screen. I saw similar (can't say whether or not identical) effects using the stock 4.1.0-3.3 generic kernel, and mainline generic kernels 4.0.0-04rc2.201503031836 (working before the first reboot after upgrading to Wily), 4.1.3-040103.201507220129 and 4.1.6-040106.201508170230. In addition (probably a separate issue), when booting 4.1.0-3.3 to external monitor only, the mouse cursor was not shown. After my last test I was able to bring things back to "normal" by killing the X server and logging in again. $ lsb_release -rd Description: Ubuntu Wily Werewolf (development branch) Release: 15.10 $ apt-cache policy xserver-xorg-video-intel xserver-xorg-video-intel: Installed: 2:2.99.917+git20150808-0ubuntu2 Candidate: 2:2.99.917+git20150808-0ubuntu2 Version table: *** 2:2.99.917+git20150808-0ubuntu2 0 500 http://de.archive.ubuntu.com/ubuntu/ wily/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: xserver-xorg-video-intel 2:2.99.917+git20150808-0ubuntu2 Uname: Linux 4.1.6-040106-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.18-0ubuntu9 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: Fri Sep 4 11:11:59 2015 DistUpgraded: 2015-09-03 15:02:03,761 DEBUG enabling apt cron job DistroCodename: wily DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 0b) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:05cb] InstallationDate: Installed on 2014-08-01 (399 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: Dell Inc. Latitude E7440 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.1.6-040106-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: xserver-xorg-video-intel UpgradeStatus: Upgraded to wily on 2015-09-03 (0 days ago) dmi.bios.date: 06/26/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A10 dmi.board.name: 0RYCC9 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA10:bd06/26/2014:svnDellInc.:pnLatitudeE7440:pvr01:rvnDellInc.:rn0RYCC9:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E7440 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.1+15.10.20150805-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.64-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.6.3-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.6.3-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu5 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0+git20150819-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20150808-0ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu3 xserver.bootTime: Fri Sep 4 11:10:45 2015 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id4413 vendor AUO xserver.version: 2:1.17.2-1ubuntu5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1492170/+subscriptions -- Mailing list:
[Desktop-packages] [Bug 1184699] Re: Canon LIDE 110 can only scan once, then I need to replug the usb cable
Martin, it might be good to wait for more feedback before closing this. I suspect that different people may be seeing different issues, and that some might still have problems. And in defence of upstream, a short sleep does seem reasonable to me when dealing with timing issues in black box external hardware. You never know what is going in inside of it, and it could well just be that the designers never anticipated that it would have to cope with communication at the speed USB 3 allows for. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to sane-backends in Ubuntu. https://bugs.launchpad.net/bugs/1184699 Title: Canon LIDE 110 can only scan once, then I need to replug the usb cable Status in Simple Scan: Invalid Status in sane-backends package in Ubuntu: Fix Committed Bug description: I have a Canon LIDE 110 scanner which works by default on ubuntu 13.04. The problem is after first scan, I can not scan for second time. I need to reconnect the USB cable to use the scanner again. # TEST 1 : without reconnecting the usb cable francois@pc:~$ scanimage -v > test1.jpg # success scanimage: scanning image of size 636x885 pixels at 8 bits/pixel scanimage: acquiring gray frame scanimage: min/max graylevel value = 0/255 scanimage: read 562860 bytes in total # I don't unplug plug the usb cable. francois@pc:~$ scanimage -v > test2.jpg # FAIL scanimage: no SANE devices found # TEST 2 : reconnect usb cable between scan attempts francois@pc:~$ scanimage -v > test1.jpg # success scanimage: scanning image of size 636x885 pixels at 8 bits/pixel scanimage: acquiring gray frame scanimage: min/max graylevel value = 0/255 scanimage: read 562860 bytes in total # I unplug and replug the usb cable. francois@pc:~$ scanimage -v > test2.jpg # SUCCESS scanimage: scanning image of size 636x885 pixels at 8 bits/pixel scanimage: acquiring gray frame scanimage: min/max graylevel value = 0/255 scanimage: read 562860 bytes in total francois@pc:~$ dmesg # extract [ 829.365158] usb 3-1: USB disconnect, device number 2 [ 834.935000] usb 3-1: new high-speed USB device number 4 using xhci_hcd [ 834.952515] usb 3-1: New USB device found, idVendor=04a9, idProduct=1909 [ 834.952519] usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 834.952522] usb 3-1: Product: CanoScan [ 834.952524] usb 3-1: Manufacturer: Canon [ 1623.738811] usb 3-1: USB disconnect, device number 4 [ 1623.739072] xhci_hcd :00:14.0: Slot 3 endpoint 6 not removed from BW list! [ 1625.528827] usb 3-1: new high-speed USB device number 5 using xhci_hcd [ 1625.546327] usb 3-1: New USB device found, idVendor=04a9, idProduct=1909 [ 1625.546331] usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 1625.546334] usb 3-1: Product: CanoScan [ 1625.546336] usb 3-1: Manufacturer: Canon francois@pc:~$ uname -a && cat /etc/issue Linux pc 3.8.0-22-generic #33-Ubuntu SMP Thu May 16 15:17:14 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux Ubuntu 13.04 \n \l The problem was reported here by someone else : http://askubuntu.com/questions/278473/canon-lide-110-should-reconnect- usb-for-each-scan Thanks François To manage notifications about this bug go to: https://bugs.launchpad.net/simple-scan/+bug/1184699/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1184699] Re: Canon LIDE 110 can only scan once, then I need to replug the usb cable
Is this alright? ** Patch added: "Fix timing issues on USB3 or fast recent hardware. Back-port from upstream." https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1184699/+attachment/4465857/+files/usb3_timing_fix.debdiff -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to sane-backends in Ubuntu. https://bugs.launchpad.net/bugs/1184699 Title: Canon LIDE 110 can only scan once, then I need to replug the usb cable Status in Simple Scan: New Status in sane-backends package in Ubuntu: Confirmed Bug description: I have a Canon LIDE 110 scanner which works by default on ubuntu 13.04. The problem is after first scan, I can not scan for second time. I need to reconnect the USB cable to use the scanner again. # TEST 1 : without reconnecting the usb cable francois@pc:~$ scanimage -v > test1.jpg # success scanimage: scanning image of size 636x885 pixels at 8 bits/pixel scanimage: acquiring gray frame scanimage: min/max graylevel value = 0/255 scanimage: read 562860 bytes in total # I don't unplug plug the usb cable. francois@pc:~$ scanimage -v > test2.jpg # FAIL scanimage: no SANE devices found # TEST 2 : reconnect usb cable between scan attempts francois@pc:~$ scanimage -v > test1.jpg # success scanimage: scanning image of size 636x885 pixels at 8 bits/pixel scanimage: acquiring gray frame scanimage: min/max graylevel value = 0/255 scanimage: read 562860 bytes in total # I unplug and replug the usb cable. francois@pc:~$ scanimage -v > test2.jpg # SUCCESS scanimage: scanning image of size 636x885 pixels at 8 bits/pixel scanimage: acquiring gray frame scanimage: min/max graylevel value = 0/255 scanimage: read 562860 bytes in total francois@pc:~$ dmesg # extract [ 829.365158] usb 3-1: USB disconnect, device number 2 [ 834.935000] usb 3-1: new high-speed USB device number 4 using xhci_hcd [ 834.952515] usb 3-1: New USB device found, idVendor=04a9, idProduct=1909 [ 834.952519] usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 834.952522] usb 3-1: Product: CanoScan [ 834.952524] usb 3-1: Manufacturer: Canon [ 1623.738811] usb 3-1: USB disconnect, device number 4 [ 1623.739072] xhci_hcd :00:14.0: Slot 3 endpoint 6 not removed from BW list! [ 1625.528827] usb 3-1: new high-speed USB device number 5 using xhci_hcd [ 1625.546327] usb 3-1: New USB device found, idVendor=04a9, idProduct=1909 [ 1625.546331] usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 1625.546334] usb 3-1: Product: CanoScan [ 1625.546336] usb 3-1: Manufacturer: Canon francois@pc:~$ uname -a && cat /etc/issue Linux pc 3.8.0-22-generic #33-Ubuntu SMP Thu May 16 15:17:14 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux Ubuntu 13.04 \n \l The problem was reported here by someone else : http://askubuntu.com/questions/278473/canon-lide-110-should-reconnect- usb-for-each-scan Thanks François To manage notifications about this bug go to: https://bugs.launchpad.net/simple-scan/+bug/1184699/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1492170] Re: Screen flicker and resolution problems after hot-plug
I am now no longer seeing the flicker and resolution issues much (and poking the hardware, e.g. by opening the Display control panel usually gets rid of it). I have a suspicion there might be hardware issues too. The mouse cursor issue is still present with kernel 4.2.0-7-generic, and still not present with the mainline kernel, tested with 4.2.0-040200-generic. However it is very hard to get a graphical log-in with either of the 4.2 kernels at all - it is shown briefly, then I have a black screen and can get a VT but usually not an X console. I am currently using 4.1.6-040106-generic again, which just now is working as well as Ubuntu 15.04 did. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu. https://bugs.launchpad.net/bugs/1492170 Title: Screen flicker and resolution problems after hot-plug Status in xserver-xorg-video-intel package in Ubuntu: New Bug description: After upgrading to Wily, when I change the configuration of screens attached (specifically: dock the laptop to a docking station with a vertically larger external screen or open the laptop to activate the internal screen while correctly running with said external screen) this causes various display issues, including flickering while the mouse cursor is moved and or one screen flickering the contents of the other; incorrect resolution; incorrect offset of displayed screen contents on screen. I saw similar (can't say whether or not identical) effects using the stock 4.1.0-3.3 generic kernel, and mainline generic kernels 4.0.0-04rc2.201503031836 (working before the first reboot after upgrading to Wily), 4.1.3-040103.201507220129 and 4.1.6-040106.201508170230. In addition (probably a separate issue), when booting 4.1.0-3.3 to external monitor only, the mouse cursor was not shown. After my last test I was able to bring things back to "normal" by killing the X server and logging in again. $ lsb_release -rd Description: Ubuntu Wily Werewolf (development branch) Release: 15.10 $ apt-cache policy xserver-xorg-video-intel xserver-xorg-video-intel: Installed: 2:2.99.917+git20150808-0ubuntu2 Candidate: 2:2.99.917+git20150808-0ubuntu2 Version table: *** 2:2.99.917+git20150808-0ubuntu2 0 500 http://de.archive.ubuntu.com/ubuntu/ wily/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: xserver-xorg-video-intel 2:2.99.917+git20150808-0ubuntu2 Uname: Linux 4.1.6-040106-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.18-0ubuntu9 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: Fri Sep 4 11:11:59 2015 DistUpgraded: 2015-09-03 15:02:03,761 DEBUG enabling apt cron job DistroCodename: wily DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 0b) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:05cb] InstallationDate: Installed on 2014-08-01 (399 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: Dell Inc. Latitude E7440 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.1.6-040106-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: xserver-xorg-video-intel UpgradeStatus: Upgraded to wily on 2015-09-03 (0 days ago) dmi.bios.date: 06/26/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A10 dmi.board.name: 0RYCC9 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA10:bd06/26/2014:svnDellInc.:pnLatitudeE7440:pvr01:rvnDellInc.:rn0RYCC9:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E7440 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.1+15.10.20150805-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.64-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.6.3-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.6.3-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu5 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0+git20150819-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20150808-0ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu3 xserver.bootTime: Fri Sep 4 11:10:45 2015 xserver.configfile: default xserver.errors: xserver.logfile:
[Desktop-packages] [Bug 1492170] [NEW] Screen flicker and resolution problems after hot-plug
Public bug reported: After upgrading to Wily, when I change the configuration of screens attached (specifically: dock the laptop to a docking station with a vertically larger external screen or open the laptop to activate the internal screen while correctly running with said external screen) this causes various display issues, including flickering while the mouse cursor is moved and or one screen flickering the contents of the other; incorrect resolution; incorrect offset of displayed screen contents on screen. I saw similar (can't say whether or not identical) effects using the stock 4.1.0-3.3 generic kernel, and mainline generic kernels 4.0.0-04rc2.201503031836 (working before the first reboot after upgrading to Wily), 4.1.3-040103.201507220129 and 4.1.6-040106.201508170230. In addition (probably a separate issue), when booting 4.1.0-3.3 to external monitor only, the mouse cursor was not shown. After my last test I was able to bring things back to "normal" by killing the X server and logging in again. $ lsb_release -rd Description:Ubuntu Wily Werewolf (development branch) Release:15.10 $ apt-cache policy xserver-xorg-video-intel xserver-xorg-video-intel: Installed: 2:2.99.917+git20150808-0ubuntu2 Candidate: 2:2.99.917+git20150808-0ubuntu2 Version table: *** 2:2.99.917+git20150808-0ubuntu2 0 500 http://de.archive.ubuntu.com/ubuntu/ wily/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: xserver-xorg-video-intel 2:2.99.917+git20150808-0ubuntu2 Uname: Linux 4.1.6-040106-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.18-0ubuntu9 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: Fri Sep 4 11:11:59 2015 DistUpgraded: 2015-09-03 15:02:03,761 DEBUG enabling apt cron job DistroCodename: wily DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 0b) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:05cb] InstallationDate: Installed on 2014-08-01 (399 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: Dell Inc. Latitude E7440 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.1.6-040106-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: xserver-xorg-video-intel UpgradeStatus: Upgraded to wily on 2015-09-03 (0 days ago) dmi.bios.date: 06/26/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A10 dmi.board.name: 0RYCC9 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA10:bd06/26/2014:svnDellInc.:pnLatitudeE7440:pvr01:rvnDellInc.:rn0RYCC9:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E7440 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.1+15.10.20150805-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.64-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.6.3-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.6.3-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu5 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0+git20150819-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20150808-0ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu3 xserver.bootTime: Fri Sep 4 11:10:45 2015 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id4413 vendor AUO xserver.version: 2:1.17.2-1ubuntu5 ** Affects: xserver-xorg-video-intel (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 ubuntu wily -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu. https://bugs.launchpad.net/bugs/1492170 Title: Screen flicker and resolution problems after hot-plug Status in xserver-xorg-video-intel package in Ubuntu: New Bug description: After upgrading to Wily, when I change the configuration of screens attached (specifically: dock the laptop to a docking station with a vertically larger external screen or open the laptop to activate the internal screen while correctly running with said external screen) this causes various display issues, including flickering while the mouse cursor is moved and or one screen flickering the contents of the other; incorrect resolution; incorrect offset of displayed
[Desktop-packages] [Bug 1466368] Re: Middle click paste from touchpad sometimes stops working
Update: I noticed that I was unable to select and paste URLs and parts of URLs from Firefox to Pidgin this morning. I naively assume that it is the same issue. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1466368 Title: Middle click paste from touchpad sometimes stops working Status in gnome-terminal package in Ubuntu: New Bug description: Quite often (subjectively nearly always) when I am using my laptop - Dell Latitude E7440 - undocked with the internal touch pad, after a while middle click paste stops working in gnome-terminal. I can middle-click paste in e.g. Firefox, but neither from nor to gnome- terminal. I have not seen this while docked with an external mouse. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: gnome-terminal 3.14.2-0ubuntu3 Uname: Linux 4.0.0-04rc2-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 CurrentDesktop: Unity Date: Thu Jun 18 08:30:11 2015 InstallationDate: Installed on 2014-08-01 (321 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) SourcePackage: gnome-terminal UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1466368/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1466368] [NEW] Middle click paste from touchpad sometimes stops working
Public bug reported: Quite often (subjectively nearly always) when I am using my laptop - Dell Latitude E7440 - undocked with the internal touch pad, after a while middle click paste stops working in gnome-terminal. I can middle- click paste in e.g. Firefox, but neither from nor to gnome-terminal. I have not seen this while docked with an external mouse. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: gnome-terminal 3.14.2-0ubuntu3 Uname: Linux 4.0.0-04rc2-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 CurrentDesktop: Unity Date: Thu Jun 18 08:30:11 2015 InstallationDate: Installed on 2014-08-01 (321 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) SourcePackage: gnome-terminal UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-terminal (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug third-party-packages vivid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1466368 Title: Middle click paste from touchpad sometimes stops working Status in gnome-terminal package in Ubuntu: New Bug description: Quite often (subjectively nearly always) when I am using my laptop - Dell Latitude E7440 - undocked with the internal touch pad, after a while middle click paste stops working in gnome-terminal. I can middle-click paste in e.g. Firefox, but neither from nor to gnome- terminal. I have not seen this while docked with an external mouse. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: gnome-terminal 3.14.2-0ubuntu3 Uname: Linux 4.0.0-04rc2-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 CurrentDesktop: Unity Date: Thu Jun 18 08:30:11 2015 InstallationDate: Installed on 2014-08-01 (321 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) SourcePackage: gnome-terminal UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1466368/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1353675] Re: _NET_WM_FULLSCREEN_MONITORS not handled correctly
Got a colleague to test 1:0.9.11.3+14.04.20150122-0ubuntu1 and confirm that the fix works. Once again, I am unpleasantly surprised at how much work you offload onto someone who points out an obvious typing mistake in a line of source code. ** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to compiz in Ubuntu. https://bugs.launchpad.net/bugs/1353675 Title: _NET_WM_FULLSCREEN_MONITORS not handled correctly Status in Compiz: Fix Released Status in Compiz 0.9.11 series: In Progress Status in compiz package in Ubuntu: Fix Released Status in compiz source package in Trusty: Fix Committed Bug description: PrivateWindow::setFullscreenMonitors() contains the following: CompRect fsRect (screen-outputDevs ()[monitors-left].x1 (), screen-outputDevs ()[monitors-top].y1 (), screen-outputDevs ()[monitors-right].x2 (), screen-outputDevs ()[monitors-bottom].y2 ()); However, the prototype is: CompRect::CompRect (int x, int y, int width, int height) This causes Compiz to miscalculate the dimensions of a full-screen window when the EWMH protocol _NET_WM_FULLSCREEN_MONITORS is used. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: compiz-core 1:0.9.11.2+14.04.20140714-0ubuntu1 Uname: Linux 3.15.8-031508-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.3 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 Aug 6 22:18:39 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 0b) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:05cb] InstallationDate: Installed on 2014-08-01 (5 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) MachineType: Dell Inc. Latitude E7440 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.15.8-031508-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 drm.debug=0xe SourcePackage: compiz UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/26/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A10 dmi.board.name: 0RYCC9 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA10:bd06/26/2014:svnDellInc.:pnLatitudeE7440:pvr01:rvnDellInc.:rn0RYCC9:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E7440 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.1 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Wed Aug 6 15:17:04 2014 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id4413 vendor AUO xserver.version: 2:1.15.1-0ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1353675/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1353675] Re: _NET_WM_FULLSCREEN_MONITORS not handled correctly
I no longer run a Trusty system myself - I run Utopic, which already contains the fix (which I can and have confirmed). I have however added a note onto the VirtualBox bug tickets, in which this was reported as a bug in VirtualBox, asking the users to test the fixed Ubuntu package. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to compiz in Ubuntu. https://bugs.launchpad.net/bugs/1353675 Title: _NET_WM_FULLSCREEN_MONITORS not handled correctly Status in Compiz: Fix Released Status in Compiz 0.9.11 series: In Progress Status in compiz package in Ubuntu: Fix Released Status in compiz source package in Trusty: Fix Committed Bug description: PrivateWindow::setFullscreenMonitors() contains the following: CompRect fsRect (screen-outputDevs ()[monitors-left].x1 (), screen-outputDevs ()[monitors-top].y1 (), screen-outputDevs ()[monitors-right].x2 (), screen-outputDevs ()[monitors-bottom].y2 ()); However, the prototype is: CompRect::CompRect (int x, int y, int width, int height) This causes Compiz to miscalculate the dimensions of a full-screen window when the EWMH protocol _NET_WM_FULLSCREEN_MONITORS is used. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: compiz-core 1:0.9.11.2+14.04.20140714-0ubuntu1 Uname: Linux 3.15.8-031508-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.3 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 Aug 6 22:18:39 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 0b) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:05cb] InstallationDate: Installed on 2014-08-01 (5 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) MachineType: Dell Inc. Latitude E7440 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.15.8-031508-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 drm.debug=0xe SourcePackage: compiz UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/26/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A10 dmi.board.name: 0RYCC9 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA10:bd06/26/2014:svnDellInc.:pnLatitudeE7440:pvr01:rvnDellInc.:rn0RYCC9:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E7440 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.1 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Wed Aug 6 15:17:04 2014 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id4413 vendor AUO xserver.version: 2:1.15.1-0ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1353675/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1353675] Re: _NET_WM_FULLSCREEN_MONITORS not handled correctly
[Impact] * VirtualBox and other multi-monitor full-screen applications using the freedesktop.org standard are not displayed in a usable way when running multi-monitor full-screen in Unity without this fix. * The bug makes the above set-up unusable. Low regression potential as this is an obvious fix for something which works correctly in other major window managers which were tested, so applications are unlikely to depend on the bug. * The proposed fix corrects an obviously incorrect use of an internal programming interface. [Test Case] * detailed instructions how to reproduce the bug * these should allow someone who is not familiar with the affected package to reproduce the bug and verify that the updated package fixes the problem. [Regression Potential] * I do not see a likelihood of regressions, as the fix makes Unity correctly implement a standard which other window managers already correctly implement. Please feel free to discuss. * I believe that any theoretical regressions would involve applications running in full-screen mode. [Other Info] * I think this process is very heavyweight for a simple bug fix which addresses what should be a very obvious programming mistake to any of your developers who cares to review it. This does not increase my interest in contributing to Ubuntu in future. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to compiz in Ubuntu. https://bugs.launchpad.net/bugs/1353675 Title: _NET_WM_FULLSCREEN_MONITORS not handled correctly Status in Compiz: Fix Released Status in Compiz 0.9.11 series: In Progress Status in compiz package in Ubuntu: Fix Released Status in compiz source package in Trusty: In Progress Bug description: PrivateWindow::setFullscreenMonitors() contains the following: CompRect fsRect (screen-outputDevs ()[monitors-left].x1 (), screen-outputDevs ()[monitors-top].y1 (), screen-outputDevs ()[monitors-right].x2 (), screen-outputDevs ()[monitors-bottom].y2 ()); However, the prototype is: CompRect::CompRect (int x, int y, int width, int height) This causes Compiz to miscalculate the dimensions of a full-screen window when the EWMH protocol _NET_WM_FULLSCREEN_MONITORS is used. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: compiz-core 1:0.9.11.2+14.04.20140714-0ubuntu1 Uname: Linux 3.15.8-031508-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.3 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 Aug 6 22:18:39 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 0b) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:05cb] InstallationDate: Installed on 2014-08-01 (5 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) MachineType: Dell Inc. Latitude E7440 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.15.8-031508-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 drm.debug=0xe SourcePackage: compiz UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/26/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A10 dmi.board.name: 0RYCC9 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA10:bd06/26/2014:svnDellInc.:pnLatitudeE7440:pvr01:rvnDellInc.:rn0RYCC9:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E7440 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.1 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Wed Aug 6 15:17:04 2014 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id4413 vendor AUO xserver.version: 2:1.15.1-0ubuntu2 To manage notifications
[Desktop-packages] [Bug 1353675] Re: _NET_WM_FULLSCREEN_MONITORS not handled correctly
You might want to try a recent test build of VirtualBox1. We are reworking full-screen mode to use the official freedesktop/EWMH APIs and having a hard time writing code which all the different window managers like. The specifications leave quite a bit open to interpretation... 1 https://www.virtualbox.org/wiki/Testbuilds -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to compiz in Ubuntu. https://bugs.launchpad.net/bugs/1353675 Title: _NET_WM_FULLSCREEN_MONITORS not handled correctly Status in Compiz: In Progress Status in “compiz” package in Ubuntu: Fix Released Bug description: PrivateWindow::setFullscreenMonitors() contains the following: CompRect fsRect (screen-outputDevs ()[monitors-left].x1 (), screen-outputDevs ()[monitors-top].y1 (), screen-outputDevs ()[monitors-right].x2 (), screen-outputDevs ()[monitors-bottom].y2 ()); However, the prototype is: CompRect::CompRect (int x, int y, int width, int height) This causes Compiz to miscalculate the dimensions of a full-screen window when the EWMH protocol _NET_WM_FULLSCREEN_MONITORS is used. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: compiz-core 1:0.9.11.2+14.04.20140714-0ubuntu1 Uname: Linux 3.15.8-031508-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.3 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 Aug 6 22:18:39 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 0b) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:05cb] InstallationDate: Installed on 2014-08-01 (5 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) MachineType: Dell Inc. Latitude E7440 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.15.8-031508-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 drm.debug=0xe SourcePackage: compiz UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/26/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A10 dmi.board.name: 0RYCC9 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA10:bd06/26/2014:svnDellInc.:pnLatitudeE7440:pvr01:rvnDellInc.:rn0RYCC9:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E7440 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.1 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Wed Aug 6 15:17:04 2014 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id4413 vendor AUO xserver.version: 2:1.15.1-0ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1353675/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1353675] Re: _NET_WM_FULLSCREEN_MONITORS not handled correctly
By the way, I am not (of course!) saying that it is a bug in VirtualBox. Realistically there are probably equal chances of it being a problem with VirtualBox, a problem with Unity or a misunderstanding between the two. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to compiz in Ubuntu. https://bugs.launchpad.net/bugs/1353675 Title: _NET_WM_FULLSCREEN_MONITORS not handled correctly Status in Compiz: In Progress Status in “compiz” package in Ubuntu: Fix Released Bug description: PrivateWindow::setFullscreenMonitors() contains the following: CompRect fsRect (screen-outputDevs ()[monitors-left].x1 (), screen-outputDevs ()[monitors-top].y1 (), screen-outputDevs ()[monitors-right].x2 (), screen-outputDevs ()[monitors-bottom].y2 ()); However, the prototype is: CompRect::CompRect (int x, int y, int width, int height) This causes Compiz to miscalculate the dimensions of a full-screen window when the EWMH protocol _NET_WM_FULLSCREEN_MONITORS is used. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: compiz-core 1:0.9.11.2+14.04.20140714-0ubuntu1 Uname: Linux 3.15.8-031508-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.3 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 Aug 6 22:18:39 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 0b) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:05cb] InstallationDate: Installed on 2014-08-01 (5 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) MachineType: Dell Inc. Latitude E7440 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.15.8-031508-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 drm.debug=0xe SourcePackage: compiz UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/26/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A10 dmi.board.name: 0RYCC9 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA10:bd06/26/2014:svnDellInc.:pnLatitudeE7440:pvr01:rvnDellInc.:rn0RYCC9:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E7440 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.1 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Wed Aug 6 15:17:04 2014 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id4413 vendor AUO xserver.version: 2:1.15.1-0ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1353675/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1353675] Re: _NET_WM_FULLSCREEN_MONITORS not handled correctly
Thank you. I wonder whether your flickering issue will stay fixed, as I can't think why a reboot would make a difference for VirtualBox (perhaps for Unity...) I suspect that the menu bar issue is because this is a generic Linux and not a specific Ubuntu build, but I suggest that that discussion move to our various communication channels1 if you wish to continue it so as not to disturb the Unity developers. 1 https://www.virtualbox.org/wiki/Community -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to compiz in Ubuntu. https://bugs.launchpad.net/bugs/1353675 Title: _NET_WM_FULLSCREEN_MONITORS not handled correctly Status in Compiz: Fix Committed Status in Compiz 0.9.11 series: Triaged Status in “compiz” package in Ubuntu: Fix Released Bug description: PrivateWindow::setFullscreenMonitors() contains the following: CompRect fsRect (screen-outputDevs ()[monitors-left].x1 (), screen-outputDevs ()[monitors-top].y1 (), screen-outputDevs ()[monitors-right].x2 (), screen-outputDevs ()[monitors-bottom].y2 ()); However, the prototype is: CompRect::CompRect (int x, int y, int width, int height) This causes Compiz to miscalculate the dimensions of a full-screen window when the EWMH protocol _NET_WM_FULLSCREEN_MONITORS is used. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: compiz-core 1:0.9.11.2+14.04.20140714-0ubuntu1 Uname: Linux 3.15.8-031508-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.3 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 Aug 6 22:18:39 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 0b) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:05cb] InstallationDate: Installed on 2014-08-01 (5 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) MachineType: Dell Inc. Latitude E7440 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.15.8-031508-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 drm.debug=0xe SourcePackage: compiz UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/26/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A10 dmi.board.name: 0RYCC9 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA10:bd06/26/2014:svnDellInc.:pnLatitudeE7440:pvr01:rvnDellInc.:rn0RYCC9:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E7440 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.1 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Wed Aug 6 15:17:04 2014 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id4413 vendor AUO xserver.version: 2:1.15.1-0ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1353675/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1353675] Re: _NET_WM_FULLSCREEN_MONITORS not handled correctly
Any estimate as to how long this will take to get into Ubuntu, and which versions it will get into? We have to know whether to provide a work- around in our software. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to compiz in Ubuntu. https://bugs.launchpad.net/bugs/1353675 Title: _NET_WM_FULLSCREEN_MONITORS not handled correctly Status in Compiz: In Progress Status in “compiz” package in Ubuntu: In Progress Bug description: PrivateWindow::setFullscreenMonitors() contains the following: CompRect fsRect (screen-outputDevs ()[monitors-left].x1 (), screen-outputDevs ()[monitors-top].y1 (), screen-outputDevs ()[monitors-right].x2 (), screen-outputDevs ()[monitors-bottom].y2 ()); However, the prototype is: CompRect::CompRect (int x, int y, int width, int height) This causes Compiz to miscalculate the dimensions of a full-screen window when the EWMH protocol _NET_WM_FULLSCREEN_MONITORS is used. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: compiz-core 1:0.9.11.2+14.04.20140714-0ubuntu1 Uname: Linux 3.15.8-031508-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.3 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 Aug 6 22:18:39 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 0b) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:05cb] InstallationDate: Installed on 2014-08-01 (5 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) MachineType: Dell Inc. Latitude E7440 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.15.8-031508-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 drm.debug=0xe SourcePackage: compiz UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/26/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A10 dmi.board.name: 0RYCC9 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA10:bd06/26/2014:svnDellInc.:pnLatitudeE7440:pvr01:rvnDellInc.:rn0RYCC9:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E7440 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.1 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Wed Aug 6 15:17:04 2014 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id4413 vendor AUO xserver.version: 2:1.15.1-0ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1353675/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1353675] Re: _NET_WM_FULLSCREEN_MONITORS not handled correctly
We are re-working multi-monitor full-screen support in VirtualBox, and the new code, which should be part of the next fails in Compiz because of this bug. Specifically the top left-hand corners of guest screens is offset from that of the host screen by an amount related to the position of the host screen in the virtual desktop area. I would be happy to provide a pre-release VirtualBox build you could use for testing, or alternatively to test any fix you produce. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to compiz in Ubuntu. https://bugs.launchpad.net/bugs/1353675 Title: _NET_WM_FULLSCREEN_MONITORS not handled correctly Status in “compiz” package in Ubuntu: New Bug description: PrivateWindow::setFullscreenMonitors() contains the following: CompRect fsRect (screen-outputDevs ()[monitors-left].x1 (), screen-outputDevs ()[monitors-top].y1 (), screen-outputDevs ()[monitors-right].x2 (), screen-outputDevs ()[monitors-bottom].y2 ()); However, the prototype is: CompRect::CompRect (int x, int y, int width, int height) This causes Compiz to miscalculate the dimensions of a full-screen window when the EWMH protocol _NET_WM_FULLSCREEN_MONITORS is used. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: compiz-core 1:0.9.11.2+14.04.20140714-0ubuntu1 Uname: Linux 3.15.8-031508-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.3 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 Aug 6 22:18:39 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 0b) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:05cb] InstallationDate: Installed on 2014-08-01 (5 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) MachineType: Dell Inc. Latitude E7440 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.15.8-031508-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 drm.debug=0xe SourcePackage: compiz UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/26/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A10 dmi.board.name: 0RYCC9 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA10:bd06/26/2014:svnDellInc.:pnLatitudeE7440:pvr01:rvnDellInc.:rn0RYCC9:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E7440 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.1 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Wed Aug 6 15:17:04 2014 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id4413 vendor AUO xserver.version: 2:1.15.1-0ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/1353675/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1353675] [NEW] _NET_WM_FULLSCREEN_MONITORS not handled correctly
Public bug reported: PrivateWindow::setFullscreenMonitors() contains the following: CompRect fsRect (screen-outputDevs ()[monitors-left].x1 (), screen-outputDevs ()[monitors-top].y1 (), screen-outputDevs ()[monitors-right].x2 (), screen-outputDevs ()[monitors-bottom].y2 ()); However, the prototype is: CompRect::CompRect (int x, int y, int width, int height) This causes Compiz to miscalculate the dimensions of a full-screen window when the EWMH protocol _NET_WM_FULLSCREEN_MONITORS is used. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: compiz-core 1:0.9.11.2+14.04.20140714-0ubuntu1 Uname: Linux 3.15.8-031508-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.3 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 Aug 6 22:18:39 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 0b) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:05cb] InstallationDate: Installed on 2014-08-01 (5 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) MachineType: Dell Inc. Latitude E7440 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.15.8-031508-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 drm.debug=0xe SourcePackage: compiz UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/26/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A10 dmi.board.name: 0RYCC9 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA10:bd06/26/2014:svnDellInc.:pnLatitudeE7440:pvr01:rvnDellInc.:rn0RYCC9:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E7440 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.1 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Wed Aug 6 15:17:04 2014 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id4413 vendor AUO xserver.version: 2:1.15.1-0ubuntu2 ** Affects: compiz (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 trusty ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to compiz in Ubuntu. https://bugs.launchpad.net/bugs/1353675 Title: _NET_WM_FULLSCREEN_MONITORS not handled correctly Status in “compiz” package in Ubuntu: New Bug description: PrivateWindow::setFullscreenMonitors() contains the following: CompRect fsRect (screen-outputDevs ()[monitors-left].x1 (), screen-outputDevs ()[monitors-top].y1 (), screen-outputDevs ()[monitors-right].x2 (), screen-outputDevs ()[monitors-bottom].y2 ()); However, the prototype is: CompRect::CompRect (int x, int y, int width, int height) This causes Compiz to miscalculate the dimensions of a full-screen window when the EWMH protocol _NET_WM_FULLSCREEN_MONITORS is used. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: compiz-core 1:0.9.11.2+14.04.20140714-0ubuntu1 Uname: Linux 3.15.8-031508-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.3 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 Aug 6 22:18:39 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 0b) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:05cb] InstallationDate: Installed on 2014-08-01 (5 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) MachineType: Dell
[Desktop-packages] [Bug 146862] Re: Should not allow to paste in the Leave Message box
I would like to draw attention to this issue again. The fix which was created is somewhat problematic, as it causes clipboard content to be lost when the screensaver password screen is shown. Relevant to me is that when that screen is shown in an Ubuntu guest in VirtualBox using clipboard sharing it causes the host clipboard contents to be lost. The original problem which the fix solved no longer exists, since the leave a message functionality in gnome-screensaver is long gone, but the upstream GNOME developers do not seem interested in reverting the fix, as gnome-screensaver is only used by Ubuntu at this point and is deprecated upstream. Would it be possible then for you to make that change in Ubuntu? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/146862 Title: Should not allow to paste in the Leave Message box Status in GNOME Screensaver: Fix Released Status in “gnome-screensaver” package in Ubuntu: Fix Released Bug description: Binary package hint: gnome-screensaver Pressing Ctrl+V while leaving a message pastes the contents of the clipboard. As the session is locked, should potentially anybody be able to see what's on your clipboard? To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-screensaver/+bug/146862/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1171856] [NEW] Pidgin main window no longer accessible from messaging menu or dock
Public bug reported: In Raring, when pidgin is running with an IRC chat window open and all others closed, I find no way to get to the main window (Buddy List) except re-launching the pidgin executable, e.g. via the Dash. Until a couple of weeks ago this could be done by clicking on the Pidgin Internet Messanger entry in the messaging menu. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: pidgin 1:2.10.7-0ubuntu4 ProcVersionSignature: Ubuntu 3.8.0-14.24-generic 3.8.4 Uname: Linux 3.8.0-14-generic x86_64 ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 Date: Tue Apr 23 15:21:49 2013 InstallationDate: Installed on 2012-11-27 (147 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5) MarkForUpload: True SourcePackage: pidgin UpgradeStatus: Upgraded to raring on 2013-03-27 (27 days ago) ** Affects: pidgin (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug raring -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pidgin in Ubuntu. https://bugs.launchpad.net/bugs/1171856 Title: Pidgin main window no longer accessible from messaging menu or dock Status in “pidgin” package in Ubuntu: New Bug description: In Raring, when pidgin is running with an IRC chat window open and all others closed, I find no way to get to the main window (Buddy List) except re-launching the pidgin executable, e.g. via the Dash. Until a couple of weeks ago this could be done by clicking on the Pidgin Internet Messanger entry in the messaging menu. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: pidgin 1:2.10.7-0ubuntu4 ProcVersionSignature: Ubuntu 3.8.0-14.24-generic 3.8.4 Uname: Linux 3.8.0-14-generic x86_64 ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 Date: Tue Apr 23 15:21:49 2013 InstallationDate: Installed on 2012-11-27 (147 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5) MarkForUpload: True SourcePackage: pidgin UpgradeStatus: Upgraded to raring on 2013-03-27 (27 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pidgin/+bug/1171856/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1107598] Re: Blank screen on resume from suspend
Thank you. Is there also a test build for Quantal? I will not upgrade before the beta cycle. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu. https://bugs.launchpad.net/bugs/1107598 Title: Blank screen on resume from suspend Status in “xserver-xorg-video-intel” package in Ubuntu: Fix Released Bug description: I was previously reporting this on bug 966744, which is however now marked as fixed and we are requested to open new reports. This is an issue which I get very sporadically on resuming my Dell Latitude E6410 whereby the keyboard is still active (I was able to switch to a virtual terminal and reboot, and now to file this bug report via a script which I have previously created) but the screen stays completely blank. Rebooting via the reboot command brings the system back to life. I do not recall seeing this issue when resuming on mains power, which for me usually means with a docking station and external monitor attached, but I have been having it very irregularly for over a year - possibly two - so I would not like to make a definite statement about that. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: xserver-xorg-video-intel 2:2.20.9-0ubuntu2 ProcVersionSignature: Ubuntu 3.5.0-22.34-generic 3.5.7.2 Uname: Linux 3.5.0-22-generic x86_64 ApportVersion: 2.6.1-0ubuntu9 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Mon Jan 28 08:18:06 2013 DistUpgraded: Fresh install DistroCodename: quantal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:040a] InstallationDate: Installed on 2012-11-27 (61 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5) MachineType: Dell Inc. Latitude E6410 MarkForUpload: True ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.5.0-22-generic root=/dev/mapper/ubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xserver-xorg-video-intel UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/09/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: A12 dmi.board.vendor: Dell Inc. dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA12:bd05/09/2012:svnDellInc.:pnLatitudeE6410:pvr0001:rvnDellInc.:rn:rvr:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6410 dmi.product.version: 0001 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.8.6-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.39-0ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.0-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.0-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.13.0-0ubuntu6.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.99.99~git20120913.8637f772-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.20.9-0ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.2-0ubuntu3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1107598/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1107598] [NEW] Blank screen on resume from suspend
Public bug reported: I was previously reporting this on bug 966744, which is however now marked as fixed and we are requested to open new reports. This is an issue which I get very sporadically on resuming my Dell Latitude E6410 whereby the keyboard is still active (I was able to switch to a virtual terminal and reboot, and now to file this bug report via a script which I have previously created) but the screen stays completely blank. Rebooting via the reboot command brings the system back to life. I do not recall seeing this issue when resuming on mains power, which for me usually means with a docking station and external monitor attached, but I have been having it very irregularly for over a year - possibly two - so I would not like to make a definite statement about that. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: xserver-xorg-video-intel 2:2.20.9-0ubuntu2 ProcVersionSignature: Ubuntu 3.5.0-22.34-generic 3.5.7.2 Uname: Linux 3.5.0-22-generic x86_64 ApportVersion: 2.6.1-0ubuntu9 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Mon Jan 28 08:18:06 2013 DistUpgraded: Fresh install DistroCodename: quantal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:040a] InstallationDate: Installed on 2012-11-27 (61 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5) MachineType: Dell Inc. Latitude E6410 MarkForUpload: True ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.5.0-22-generic root=/dev/mapper/ubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xserver-xorg-video-intel UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/09/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: A12 dmi.board.vendor: Dell Inc. dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA12:bd05/09/2012:svnDellInc.:pnLatitudeE6410:pvr0001:rvnDellInc.:rn:rvr:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6410 dmi.product.version: 0001 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.8.6-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.39-0ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.0-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.0-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.13.0-0ubuntu6.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.99.99~git20120913.8637f772-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.20.9-0ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.2-0ubuntu3 ** Affects: xserver-xorg-video-intel (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug quantal ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu. https://bugs.launchpad.net/bugs/1107598 Title: Blank screen on resume from suspend Status in “xserver-xorg-video-intel” package in Ubuntu: New Bug description: I was previously reporting this on bug 966744, which is however now marked as fixed and we are requested to open new reports. This is an issue which I get very sporadically on resuming my Dell Latitude E6410 whereby the keyboard is still active (I was able to switch to a virtual terminal and reboot, and now to file this bug report via a script which I have previously created) but the screen stays completely blank. Rebooting via the reboot command brings the system back to life. I do not recall seeing this issue when resuming on mains power, which for me usually means with a docking station and external monitor attached, but I have been having it very irregularly for over a year - possibly two - so I would not like to make a definite statement about that. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: xserver-xorg-video-intel 2:2.20.9-0ubuntu2 ProcVersionSignature: Ubuntu 3.5.0-22.34-generic 3.5.7.2 Uname: Linux 3.5.0-22-generic x86_64 ApportVersion: 2.6.1-0ubuntu9 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Mon Jan 28 08:18:06 2013 DistUpgraded: Fresh install DistroCodename: quantal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:040a] InstallationDate: Installed on 2012-11-27 (61 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5) MachineType: Dell Inc. Latitude E6410 MarkForUpload: True
[Desktop-packages] [Bug 304889] Re: Does not use system proxy settings
Nice little workaround for IRC, and hence for idle (at least it does the job at a pinch): http://wiki.tcl.tk/3125 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to empathy in Ubuntu. https://bugs.launchpad.net/bugs/304889 Title: Does not use system proxy settings Status in Chat app, and Telepathy user interface: Invalid Status in Jabber/XMPP connection manager: Confirmed Status in Telepathy Haze: Confirmed Status in A full-featured IRC connection manager for telepathy.: Confirmed Status in “empathy” package in Ubuntu: Invalid Status in “empathy” source package in Lucid: Invalid Status in “empathy” package in Unity Linux: Invalid Bug description: Binary package hint: empathy Empathy wont connect to any major service trough a proxy. I've tried Google Talk, Jabber, MSN and Yahoo. I set the proxy preferences in GNOME, it's a plain proxy for all protocols, without authentication. Pidgin works normally in the same setup. Ubuntu 8.10, Empathy 2.24.1 To manage notifications about this bug go to: https://bugs.launchpad.net/empathy/+bug/304889/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 9441] Re: the locate pointer option breaks other keybindings
Kirill: I am commenting as the member of the VirtualBox development team in charge of keyboard handling in Linux. My guess is that the locate pointer tool places a passive grab [1] on the control key. What this means if it is correct is that as of the point when the grab is placed no other application can see the control key being pressed or released unless the tool explicitly allows it (I presume it doesn't); however they can still (usually) see combinations including the control key, such as Ctrl-Scroll in Frederik's example above. Certainly VirtualBox relies on being able to spot individual keypresses and releases and doesn't try to monitor key combinations to work around this sort of thing: we take the point of view that if the user wants to take keys away from us for other purposes they should know what they are doing, and we don't want to add complexity to deal with it and risk creating bugs for other people. If there were a nice way of spotting passive grabs by other applications we might warn the user, but I don't know of any way other than trying to grab every key ourselves to see which ones we can't get. [1] http://tronche.com/gui/x/xlib/input/XGrabKey.html -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/9441 Title: the locate pointer option breaks other keybindings Status in GNOME Control Center: Confirmed Status in “gnome-settings-daemon” package in Ubuntu: Triaged Bug description: If 'Locate pointer' mouse feature is enabled (Computer-Desktop preferences-Mouse-Cursors-Locate Pointer), and you try to copy file by Ctrl+dragging, nautilus will stop responding when you release Ctrl or left mouse button to drop copy to destination folder. This effectively disables all desktop operations and panels until nautilus is killed from console. Exact sequence to reproduce: 0) Enable 'Locate pointer' mouse feature 1) press Ctrl 2) drag file to destinaton 3) release Ctrl or left mouse button You must FIRST press Ctrl, and THEN begin to drag file - if order is reverse operation will success. http://bugzilla.gnome.org/show_bug.cgi?id=125618: http://bugzilla.gnome.org/show_bug.cgi?id=125618 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/9441/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
