[Bug 1829029] Re: Feature request: allow use of update-secureboot-policy for non-DKMS modules
By the way, I know that we could get this by just using DKMS for our modules (and we could still do that if we absolutely had to), but we prefer not to. The reason for this is that not all distributions that we target support DKMS, so we still need to provide our home-grown DKMS replacement. We used to support DKMS as well, but because DKMS occasionally went wrong on users's systems, often enough to be cause us additional support work, we decided to drop it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1829029 Title: Feature request: allow use of update-secureboot-policy for non-DKMS modules To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shim-signed/+bug/1829029/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1829029] Re: Feature request: allow use of update-secureboot-policy for non-DKMS modules
** Patch added: "First suggested patch" https://bugs.launchpad.net/ubuntu/+source/shim-signed/+bug/1829029/+attachment/5263673/+files/update-secureboot-policy.diff ** Description changed: - Already discussed by e-mail/IRC with Matthieu. We (the VirtualBox team) + Already discussed by e-mail/IRC with Mathieu. We (the VirtualBox team) would like to call update-secureboot-policy to enroll a signing key when we install our host kernel modules on Ubuntu/Debian systems. However, currently the tool exits if no DKMS modules are found. This patch would add a "--force" parameter which would let us call the tool interactively as part of our installation scripts even if DKMS was not installed. Not sure how or if we should handle the new DKMS list in non-interactive mode. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: shim-signed 1.39+15+1533136590.3beb971-0ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 .proc.sys.kernel.moksbstate_disabled: Error: [Errno 2] Нет такого файла или каталога: '/proc/sys/kernel/moksbstate_disabled' ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CasperVersion: 1.405 CurrentDesktop: ubuntu:GNOME Date: Tue May 14 16:56:38 2019 EFITables: - Mai 13 11:05:20 michael-ThinkPad-T470 kernel: efi: EFI v2.50 by Lenovo - Mai 13 11:05:20 michael-ThinkPad-T470 kernel: efi: SMBIOS=0x9a6d8000 SMBIOS 3.0=0x9a6d5000 ACPI=0x9b5fe000 ACPI 2.0=0x9b5fe014 ESRT=0x9a5a2000 MEMATTR=0x9532e298 TPMEventLog=0x8e96d018 - Mai 13 11:05:20 michael-ThinkPad-T470 kernel: secureboot: Secure boot enabled - Mai 13 11:05:20 michael-ThinkPad-T470 kernel: esrt: Reserving ESRT space from 0x9a5a2000 to 0x9a5a2088. - Mai 13 11:05:21 michael-ThinkPad-T470 kernel: Bluetooth: hci0: Secure boot is enabled + Mai 13 11:05:20 michael-ThinkPad-T470 kernel: efi: EFI v2.50 by Lenovo + Mai 13 11:05:20 michael-ThinkPad-T470 kernel: efi: SMBIOS=0x9a6d8000 SMBIOS 3.0=0x9a6d5000 ACPI=0x9b5fe000 ACPI 2.0=0x9b5fe014 ESRT=0x9a5a2000 MEMATTR=0x9532e298 TPMEventLog=0x8e96d018 + Mai 13 11:05:20 michael-ThinkPad-T470 kernel: secureboot: Secure boot enabled + Mai 13 11:05:20 michael-ThinkPad-T470 kernel: esrt: Reserving ESRT space from 0x9a5a2000 to 0x9a5a2088. + Mai 13 11:05:21 michael-ThinkPad-T470 kernel: Bluetooth: hci0: Secure boot is enabled InstallationDate: Installed on 2018-06-12 (335 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SecureBoot: 6 0 0 0 1 SourcePackage: shim-signed UpgradeStatus: Upgraded to disco on 2019-03-26 (49 days ago) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1829029 Title: Feature request: allow use of update-secureboot-policy for non-DKMS modules To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shim-signed/+bug/1829029/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1829029] [NEW] Feature request: allow use of update-secureboot-policy for non-DKMS modules
Public bug reported: Already discussed by e-mail/IRC with Mathieu. We (the VirtualBox team) would like to call update-secureboot-policy to enroll a signing key when we install our host kernel modules on Ubuntu/Debian systems. However, currently the tool exits if no DKMS modules are found. This patch would add a "--force" parameter which would let us call the tool interactively as part of our installation scripts even if DKMS was not installed. Not sure how or if we should handle the new DKMS list in non-interactive mode. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: shim-signed 1.39+15+1533136590.3beb971-0ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 .proc.sys.kernel.moksbstate_disabled: Error: [Errno 2] Нет такого файла или каталога: '/proc/sys/kernel/moksbstate_disabled' ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CasperVersion: 1.405 CurrentDesktop: ubuntu:GNOME Date: Tue May 14 16:56:38 2019 EFITables: Mai 13 11:05:20 michael-ThinkPad-T470 kernel: efi: EFI v2.50 by Lenovo Mai 13 11:05:20 michael-ThinkPad-T470 kernel: efi: SMBIOS=0x9a6d8000 SMBIOS 3.0=0x9a6d5000 ACPI=0x9b5fe000 ACPI 2.0=0x9b5fe014 ESRT=0x9a5a2000 MEMATTR=0x9532e298 TPMEventLog=0x8e96d018 Mai 13 11:05:20 michael-ThinkPad-T470 kernel: secureboot: Secure boot enabled Mai 13 11:05:20 michael-ThinkPad-T470 kernel: esrt: Reserving ESRT space from 0x9a5a2000 to 0x9a5a2088. Mai 13 11:05:21 michael-ThinkPad-T470 kernel: Bluetooth: hci0: Secure boot is enabled InstallationDate: Installed on 2018-06-12 (335 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SecureBoot: 6 0 0 0 1 SourcePackage: shim-signed UpgradeStatus: Upgraded to disco on 2019-03-26 (49 days ago) ** Affects: shim-signed (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco wayland-session -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1829029 Title: Feature request: allow use of update-secureboot-policy for non-DKMS modules To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shim-signed/+bug/1829029/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1803319 Title: GNOME Shell task bar menus not updated with external monitor primary and laptop screen fractionally scaled To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1803319/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1803319 Title: GNOME Shell task bar menus not updated with external monitor primary and laptop screen fractionally scaled To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1803319/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1803319 Title: GNOME Shell task bar menus not updated with external monitor primary and laptop screen fractionally scaled To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1803319/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1805151] Re: Desktop freeze running VirtualBox, Intel graphics
I started bisecting, but a colleague happened to find a work-around which fixed the problem, so I stopped. You might update your bisection page to mention that one should do bindeb-pkg builds, not deb-pkg. I used the Ubuntu mainline git repository - is that any different from Linus's repository? And is there any way to avoid a full rebuild each time, which happens (more or less) even when I do not clean in-between? Interested in the answers, but since I will not be pursuing this further you can probably close it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1805151 Title: Desktop freeze running VirtualBox, Intel graphics To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1805151/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1805151] Re: Desktop freeze running VirtualBox, Intel graphics
Does anyone know of anything similar or possibly interesting kernel commits to look at before I spend too long bisecting? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1805151 Title: Desktop freeze running VirtualBox, Intel graphics To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1805151/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1805151 Title: Desktop freeze running VirtualBox, Intel graphics To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1805151/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1805151 Title: Desktop freeze running VirtualBox, Intel
[Bug 1804885] Re: Desktop freeze running VirtualBox, Intel graphics
Created bug 1805151. Thanks for your time. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1804885 Title: Desktop freeze running VirtualBox, Intel graphics To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1804885/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1804885 Title: Desktop freeze running VirtualBox, Intel graphics To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1804885/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1803319 Title: GNOME Shell task bar menus not updated with external monitor primary and laptop screen fractionally scaled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1803319/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1790851] Re: GPG_AGENT_INFO not being set in user session
Note: works as expected in 18.10. As no one else seems to be interested I will close this. ** Changed in: gnupg2 (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1790851 Title: GPG_AGENT_INFO not being set in user session To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnupg2/+bug/1790851/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1723045 Title: GNOME Terminal does not get into GNOME Shell's frequently used list To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1723045/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1792000 Title: VirtualBox icon does not show un dock until screen locks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1792000/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1792000 Title: VirtualBox icon does not show un dock until screen locks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1792000/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1790851] [NEW] GPG_AGENT_INFO not being set in user session
Public bug reported: For some time now I have noticed that Subversion fails to use the gpg agent to store passwords in memory for the current session. Someone on the Subversion mailing list[1] suggested that it might be because the GPG_AGENT_INFO variable is not being set in the environment, and pointed me to /etc/X11/Xsession.d/90gpg-agent. I can confirm that when I source that file the problem goes away. Might this be due to my using a Wayland, not an X11 session? I see that there is a similar file for systemd, but it does not seem to be doing the trick. [1] https://svn.haxx.se/users/archive-2016-10/0058.shtml ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gpg-agent 2.2.4-1ubuntu1.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: Wed Sep 5 12:54:39 2018 InstallationDate: Installed on 2018-06-12 (84 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: gnupg2 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnupg2 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic wayland-session -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1790851 Title: GPG_AGENT_INFO not being set in user session To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnupg2/+bug/1790851/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1781861] [NEW] qtchooser should select right version when only one is installed
Public bug reported: I have trouble imagining I am the first person to report this, but I did not (quickly) find a duplicate. When only one version of Qt is installed, can qtchooser select it automatically? E.g. when I start linguist and only have Qt5 installed, could it start Qt5 Linguist? ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: qtchooser 64-ga1b6736-5 ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18 Uname: Linux 4.15.0-24-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Jul 16 08:50:05 2018 Dependencies: gcc-8-base 8-20180414-1ubuntu2 libc6 2.27-3ubuntu1 libgcc1 1:8-20180414-1ubuntu2 libstdc++6 8-20180414-1ubuntu2 InstallationDate: Installed on 2018-06-12 (33 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: qtchooser UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: qtchooser (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic wayland-session -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1781861 Title: qtchooser should select right version when only one is installed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtchooser/+bug/1781861/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1773088] Re: svn does not use GNOME password store by default
This has mysteriously started working again. I can't see any relevant package updates, so I can only assume that it was some local problem. ** Changed in: subversion (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1773088 Title: svn does not use GNOME password store by default To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/subversion/+bug/1773088/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1773088] [NEW] svn does not use GNOME password store by default
Public bug reported: I did a fresh installation of Ubuntu 18.04 and put Subversion on it. I expected Subversion to use the GNOME keyring by default (i.e. without further interaction from me) for storing passwords, but it asks me instead whether I want to store passwords as plain text. Is this expected? ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: subversion 1.9.7-4ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu May 24 07:57:31 2018 InstallationDate: Installed on 2018-05-15 (8 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: subversion UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: subversion (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic wayland-session -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1773088 Title: svn does not use GNOME password store by default To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/subversion/+bug/1773088/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1754601] Re: openconnect has trouble maintaining a VPN connection
The information I added today is rather relativised by the fact that today I am unable to reproduce the problem with the Ubuntu 4.15 kernels either. I will update this when (if?) it happens again. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1754601 Title: openconnect has trouble maintaining a VPN connection To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1754601/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1754601] JournalErrors.txt
apport information ** Attachment added: "JournalErrors.txt" https://bugs.launchpad.net/bugs/1754601/+attachment/5088051/+files/JournalErrors.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1754601 Title: openconnect has trouble maintaining a VPN connection To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1754601/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1754601] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1754601/+attachment/5088060/+files/UdevDb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1754601 Title: openconnect has trouble maintaining a VPN connection To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1754601/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1754601] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1754601/+attachment/5088047/+files/CRDA.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1754601 Title: openconnect has trouble maintaining a VPN connection To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1754601/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1754601] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1754601/+attachment/5088059/+files/RfKill.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1754601 Title: openconnect has trouble maintaining a VPN connection To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1754601/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1754601] Dependencies.txt
apport information ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1754601/+attachment/5088049/+files/Dependencies.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1754601 Title: openconnect has trouble maintaining a VPN connection To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1754601/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1754601] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1754601/+attachment/5088050/+files/IwConfig.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1754601 Title: openconnect has trouble maintaining a VPN connection To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1754601/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1754601] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1754601/+attachment/5088053/+files/Lsusb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1754601 Title: openconnect has trouble maintaining a VPN connection To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1754601/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1754601] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1754601/+attachment/5088057/+files/ProcModules.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1754601 Title: openconnect has trouble maintaining a VPN connection To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1754601/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1754601] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1754601/+attachment/5088054/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1754601 Title: openconnect has trouble maintaining a VPN connection To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1754601/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1754601] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1754601/+attachment/5088061/+files/WifiSyslog.txt ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1754601 Title: openconnect has trouble maintaining a VPN connection To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1754601/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1754601] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1754601/+attachment/5088048/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1754601 Title: openconnect has trouble maintaining a VPN connection To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1754601/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1754601] Re: openconnect has trouble maintaining a VPN connection
apport information ** Tags added: apport-collected ** Description changed: Some time after upgrading to Bionic, I have found that openconnect has some trouble keeping a VPN connection open to our company VPN. Since openconnect in Bionic seems to be based on the same upstream release as in Artful I assume that the problem is more likely to be in the kernel, and the timing of when it started could fit the kernel upgrade from 4.13 to 4.15.. I regularly see this in the output: SSL read error: Error in the pull function.; reconnecting. SSL negotiation with SSL connection failure: The operation timed out sleep 10s, remaining timeout 300s SSL negotiation with SSL connection failure: The operation timed out sleep 20s, remaining timeout 290 ... Interestingly I just now saw it recover from that problem for the first time I am aware of. I know that it would make sense to test it with the old kernel, and I will try that some time (I don't reboot that often, and am not always on VPN). In the mean time, I am creating this report in the hope that it will ring some bell with someone. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: openconnect 7.08-3 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Mar 9 10:25:56 2018 InstallationDate: Installed on 2017-10-24 (135 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) SourcePackage: openconnect UpgradeStatus: Upgraded to bionic on 2018-02-06 (30 days ago) + --- + ApportVersion: 2.20.8-0ubuntu10 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC0: michael1608 F pulseaudio + /dev/snd/controlC1: michael1608 F pulseaudio + CurrentDesktop: ubuntu:GNOME + DistroRelease: Ubuntu 18.04 + HibernationDevice: RESUME=UUID=701963f8-cca7-4480-b062-4d2d5006f10d + InstallationDate: Installed on 2017-10-24 (149 days ago) + InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) + MachineType: Dell Inc. Latitude E7440 + Package: openconnect 7.08-3 + PackageArchitecture: amd64 + ProcFB: 0 inteldrmfb + ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-12-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash + ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 + RelatedPackageVersions: + linux-restricted-modules-4.15.0-12-generic N/A + linux-backports-modules-4.15.0-12-generic N/A + linux-firmware 1.173 + Tags: wayland-session bionic wayland-session + Uname: Linux 4.15.0-12-generic x86_64 + UpgradeStatus: Upgraded to bionic on 2018-02-06 (44 days ago) + UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers + _MarkForUpload: True + dmi.bios.date: 02/02/2015 + dmi.bios.vendor: Dell Inc. + dmi.bios.version: A14 + dmi.board.name: 0WK2DM + dmi.board.vendor: Dell Inc. + dmi.chassis.type: 9 + dmi.chassis.vendor: Dell Inc. + dmi.modalias: dmi:bvnDellInc.:bvrA14:bd02/02/2015:svnDellInc.:pnLatitudeE7440:pvr01:rvnDellInc.:rn0WK2DM:rvr:cvnDellInc.:ct9:cvr: + dmi.product.name: Latitude E7440 + dmi.product.version: 01 + dmi.sys.vendor: Dell Inc. ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1754601/+attachment/5088046/+files/AlsaInfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1754601 Title: openconnect has trouble maintaining a VPN connection To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1754601/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1754601] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1754601/+attachment/5088056/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1754601 Title: openconnect has trouble maintaining a VPN connection To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1754601/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1754601] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1754601/+attachment/5088052/+files/Lspci.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1754601 Title: openconnect has trouble maintaining a VPN connection To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1754601/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1754601] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1754601/+attachment/5088058/+files/PulseList.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1754601 Title: openconnect has trouble maintaining a VPN connection To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1754601/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1754601] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1754601/+attachment/5088055/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1754601 Title: openconnect has trouble maintaining a VPN connection To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1754601/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1754601] Re: openconnect has trouble maintaining a VPN connection
No problems seen so far with 4.15.7-041507-generic either, after 25 minutes connected to the VPN. Sounds like it might be a problem in the Ubuntu changes to 4.15 after all. ** Also affects: linux-meta (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1754601 Title: openconnect has trouble maintaining a VPN connection To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1754601/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1754601] Re: openconnect has trouble maintaining a VPN connection
The Cisco tool has trouble with both kernels. openconnect has so far not had problems with 4.16rc6 from the mainline PPA. So it is only Bionic's 4.15 so far. Not tested with mainline PPA 4.15, but I can if that makes sense. I am guessing it is a heisenbug, but I might be wrong. I posted to the openconnect mailing list[1], but no answer yet. [1] http://lists.infradead.org/pipermail/openconnect- devel/2018-March/004795.html -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1754601 Title: openconnect has trouble maintaining a VPN connection To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openconnect/+bug/1754601/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1754601] Re: openconnect has trouble maintaining a VPN connection
I tried it for a bit with the old Artful kernel without issues. As soon as I booted back into the Bionic 4.15 I was unable to connect to the VPN again. It might be worth mentioning that the Cisco VPN tool also failed to connect. I did not try that one with 4.13. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1754601 Title: openconnect has trouble maintaining a VPN connection To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openconnect/+bug/1754601/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1754601] [NEW] openconnect has trouble maintaining a VPN connection
Public bug reported: Some time after upgrading to Bionic, I have found that openconnect has some trouble keeping a VPN connection open to our company VPN. Since openconnect in Bionic seems to be based on the same upstream release as in Artful I assume that the problem is more likely to be in the kernel, and the timing of when it started could fit the kernel upgrade from 4.13 to 4.15.. I regularly see this in the output: SSL read error: Error in the pull function.; reconnecting. SSL negotiation with SSL connection failure: The operation timed out sleep 10s, remaining timeout 300s SSL negotiation with SSL connection failure: The operation timed out sleep 20s, remaining timeout 290 ... Interestingly I just now saw it recover from that problem for the first time I am aware of. I know that it would make sense to test it with the old kernel, and I will try that some time (I don't reboot that often, and am not always on VPN). In the mean time, I am creating this report in the hope that it will ring some bell with someone. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: openconnect 7.08-3 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Mar 9 10:25:56 2018 InstallationDate: Installed on 2017-10-24 (135 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) SourcePackage: openconnect UpgradeStatus: Upgraded to bionic on 2018-02-06 (30 days ago) ** Affects: openconnect (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic third-party-packages wayland-session -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1754601 Title: openconnect has trouble maintaining a VPN connection To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openconnect/+bug/1754601/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1722725 Title: GNOME Shell disabling wrong screen when docking laptop To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1722725/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1722725 Title: GNOME Shell disabling wrong screen when docking laptop To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1722725/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1722725 Title: GNOME Shell disabling wrong screen when docking laptop To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1722725/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1722725 Title: GNOME Shell disabling wrong screen when docking laptop To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1722725/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1724259 Title: gnome-shell frozen and using 100% CPU after docking and display configuration change To manage notifications about this bug go to: https://bugs.launchpad.net/libinput/+bug/1724259/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1736116] Re: Host with kernel 4.13 freezes when starting a VM with VirtualBox
For those people having host freezes, please try to reproduce them using packages from virtualbox.org and open a bug report there if appropriate. It would be appreciated if you link to any appropriate Launchpad bugs, but still provide all information on the virtualbox.org bug, including a log file from the last virtual machine you started. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1736116 Title: Host with kernel 4.13 freezes when starting a VM with VirtualBox To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/1736116/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1443853] Re: Ubuntu boot in Oracle VirtualBox ends up with a corrupted display
Ah, it is the old problem with lightdm not waiting for the udev notification that the driver is loaded. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1443853 Title: Ubuntu boot in Oracle VirtualBox ends up with a corrupted display To manage notifications about this bug go to: https://bugs.launchpad.net/virtualbox/+bug/1443853/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1443853] Re: Ubuntu boot in Oracle VirtualBox ends up with a corrupted display
Actually Lubuntu probably doesn't support Wayland at all. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1443853 Title: Ubuntu boot in Oracle VirtualBox ends up with a corrupted display To manage notifications about this bug go to: https://bugs.launchpad.net/virtualbox/+bug/1443853/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1443853] Re: Ubuntu boot in Oracle VirtualBox ends up with a corrupted display
I would just point out that the problem with Lubuntu live which was reported and which I reproduced would force a fall-back from Wayland to X.Org. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1443853 Title: Ubuntu boot in Oracle VirtualBox ends up with a corrupted display To manage notifications about this bug go to: https://bugs.launchpad.net/virtualbox/+bug/1443853/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1443853] Re: Ubuntu boot in Oracle VirtualBox ends up with a corrupted display
This issue should be fixed in versions of Ubuntu which provide the VirtualBox graphics driver. However the person who re-opened the bug discovered another issue: at least the Lubuntu live ISO seems to load the VirtualBox driver rather late in the boot process, which can result in X.Org loading with the VESA driver (because it does not find the VirtualBox one) at the same time as the VirtualBox driver, and both trying to access the graphics device at the same time. Not sure if this deserves a new bug. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1443853 Title: Ubuntu boot in Oracle VirtualBox ends up with a corrupted display To manage notifications about this bug go to: https://bugs.launchpad.net/virtualbox/+bug/1443853/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1724259 Title: gnome-shell frozen and using 100% CPU after docking and display configuration change To manage notifications about this bug go to: https://bugs.launchpad.net/libinput/+bug/1724259/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to 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"] To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1505409/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to 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"] To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1505409/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1724259 Title: gnome-shell frozen and using 100% CPU after docking and display configuration change To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1724259/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1724259 Title: gnome-shell frozen and using 100% CPU after docking and display configuration change To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1724259/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1724259 Title: gnome-shell frozen and using 100% CPU after docking and display configuration change To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1724259/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1724259 Title: gnome-shell frozen and using 100% CPU after docking and display configuration change To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1724259/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1724259 Title: gnome-shell frozen and using 100% CPU after docking and display configuration change To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1724259/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1724259 Title: gnome-shell frozen and using 100% CPU after docking and display configuration change To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1724259/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1724259 Title: gnome-shell frozen and using 100% CPU after docking and display configuration change To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1724259/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1724259 Title: gnome-shell frozen and using 100% CPU after docking and display configuration change To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1724259/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1724259 Title: gnome-shell frozen and using 100% CPU after docking and display configuration change To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1724259/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1724259 Title: gnome-shell frozen and using 100% CPU after docking and display configuration change To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1724259/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1724259 Title: gnome-shell frozen and using 100% CPU after docking and display configuration change To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1724259/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1722725 Title: GNOME Shell disabling wrong screen when docking laptop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1722725/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1427600] Re: apport-unpack: ValueError: ['UserGroups'] has no binary content
To my way of thinking, an exception is for something the programmer did not foresee. Since this is now a known failure mode of Apport, I would expect - in an ideal world in which there was enough time to work on all known bugs - a clean exit with a clear error message. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1427600 Title: apport-unpack: ValueError: ['UserGroups'] has no binary content To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1427600/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1726020] [NEW] apport will not process report in /var/crash
Public bug reported: I have an 11K crash report in /var/crash, which Apport refuses to process due to a lack of "free memory to automatically analyze the problem and send a report to the developers". So I am attaching it here in case it is of interest. At least the question of why Apport has so much trouble of it might be interesting. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: udev 234-2ubuntu12 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 CustomUdevRuleFiles: 60-vboxdrv.rules Date: Sun Oct 22 16:11:44 2017 InstallationDate: Installed on 2016-05-31 (509 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: Dell Inc. Latitude E6420 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: systemd UpgradeStatus: Upgraded to artful on 2017-10-05 (17 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. ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful wayland-session -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1726020 Title: apport will not process report in /var/crash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1726020/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1726020] Re: apport will not process report in /var/crash
** Attachment added: "_lib_systemd_systemd-udevd.0.crash" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1726020/+attachment/4985136/+files/_lib_systemd_systemd-udevd.0.crash -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1726020 Title: apport will not process report in /var/crash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1726020/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1724810] Re: 17.10/wayland causing flashes in virtualbox
Are you talking about the guest screen or the host screen flashing? And are you sure that X11 is running after installing those packages? In a terminal in the guest run "ps -Af | grep X" and see if Xwayland is in the list. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1724810 Title: 17.10/wayland causing flashes in virtualbox To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/1724810/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to 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) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1724886/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1724259 Title: System freeze after docking and display configuration change To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1724259/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1723075 Title: System freeze after docking and display configuration change To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1723075/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1724259 Title: System freeze after docking and display configuration change To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1724259/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1723075 Title: System freeze after docking and display configuration change To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1723075/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1723075 Title: System freeze after docking and display configuration change To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1723075/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1723045 Title: GNOME Terminal does not get into GNOME Shell's frequently used list To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1723045/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1722725 Title: GNOME Shell disabling wrong screen when docking laptop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1722725/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1722722] [NEW] Search domains not deleted from resolv.conf
Public bug reported: I hope that this is the right place for this. What I am seeing is that every time I switch networks with my laptop entries get added to the resolv.conf search list but never deleted. For whatever reason, once I have left our company network I am unable to access resources which are internal in the network but also availably externally (e.g. the main company home page) until I have removed the search entries manually. If more information or testing would be useful please let me know what. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: resolvconf 1.79ubuntu8 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 08:50:33 2017 InstallationDate: Installed on 2016-05-31 (497 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) PackageArchitecture: all SourcePackage: resolvconf UpgradeStatus: Upgraded to artful on 2017-10-05 (6 days ago) ** Affects: resolvconf (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful wayland-session -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1722722 Title: Search domains not deleted from resolv.conf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1722722/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1721718] Re: Segmentation fault in meta_monitor_mode_get_resolution
Update: I see that there are files in /var/crash, but they are all from October 5. I will try deleting the GNOME Shell one and see if a new one is created if another crash happens. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1721718 Title: Segmentation fault in meta_monitor_mode_get_resolution To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1721718/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1721718] Re: Segmentation fault in meta_monitor_mode_get_resolution
I saw something similar again today. Hard to say how similar. For some reason Apport does not seem to be doing the automatic reporting, though it looked like it was set up at a quick glance. I will try catching it myself. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1721718 Title: Segmentation fault in meta_monitor_mode_get_resolution To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1721718/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1721718] Re: Segmentation fault in meta_monitor_mode_get_resolution
I overcame my laziness and restarted everything. I was just able to reconfigure monitors without a crash, so assume this is fixed. I can always re-open if really necessary. Thanks. ** Changed in: mutter (Ubuntu) Status: Incomplete => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1721718 Title: Segmentation fault in meta_monitor_mode_get_resolution To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1721718/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1721718] Re: Segmentation fault in meta_monitor_mode_get_resolution
Gianfranco suggested off-Launchpad that I test the most recent version of libmutter (3.26.1), as it looks from the source as though this issue is fixed there. I will report back in a few days (I generally suspend and resume without restarting my session, so it will be a while until I start using the new library). Until then and unless I see otherwise let's assume that 3.26.1 fixes this. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1721718 Title: Segmentation fault in meta_monitor_mode_get_resolution To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1721718/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1721718] Re: Segmentation fault in meta_monitor_mode_get_resolution
Quick fix below. For reasons of time I have done no testing beyond that GNOME Shell no longer crashes with the patch below. I have not tested the effect on scaling settings. ** Patch added: "mutter.patch" https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1721718/+attachment/4963800/+files/mutter.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1721718 Title: Segmentation fault in meta_monitor_mode_get_resolution To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1721718/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1721718] Re: Segmentation fault in meta_monitor_mode_get_resolution
Second try with debug symbols for glib2.0 and libmutter. Thread 1 "gnome-shell" received signal SIGSEGV, Segmentation fault. meta_monitor_mode_get_resolution (monitor_mode=monitor_mode@entry=0x0, width=width@entry=0x7fff256d5ad8, height=height@entry=0x7fff256d5adc) at backends/meta-monitor.c:1582 1582backends/meta-monitor.c: Нет такого файла или каталога. (gdb) bt #0 0x7f3df4941f50 in meta_monitor_mode_get_resolution (monitor_mode=monitor_mode@entry=0x0, width=width@entry=0x7fff256d5ad8, height=height@entry=0x7fff256d5adc) at backends/meta-monitor.c:1582 #1 0x7f3df4941fd2 in calculate_scale (monitor_mode=0x0, monitor=0x55c462ebd040 [MetaMonitorNormal]) at backends/meta-monitor.c:1377 #2 0x7f3df4941fd2 in meta_monitor_calculate_mode_scale (monitor=monitor@entry=0x55c462ebd040 [MetaMonitorNormal], monitor_mode=0x0) at backends/meta-monitor.c:1439 #3 0x7f3df493e437 in meta_finish_monitors_config_migration (monitor_manager=monitor_manager@entry=0x55c462af81b0 [MetaMonitorManagerKms], config=config@entry=0x7f3dd0019750 [MetaMonitorsConfig], error=error@entry=0x7fff256d5b60) at backends/meta-monitor-config-migration.c:1177 #4 0x7f3df493b8fe in meta_monitor_config_manager_get_stored (config_manager=0x7f3dd0005f20 [MetaMonitorConfigManager]) at backends/meta-monitor-config-manager.c:385 #5 0x7f3df4943732 in meta_monitor_manager_ensure_configured (manager=0x55c462af81b0 [MetaMonitorManagerKms]) at backends/meta-monitor-manager.c:487 #9 0x7f3df6733f4f in (instance=instance@entry=0x7f3dd000cb70, signal_id=, detail=) at ../../../../gobject/gsignal.c:3447 #6 0x7f3df6717f9d in g_closure_invoke (closure=0x55c462ecde10, return_value=0x0, n_param_values=2, param_values=0x7fff256d5dc0, invocation_hint=0x7fff256d5d40) at ../../../../gobject/gclosure.c:804 ---Type to continue, or q to quit--- #7 0x7f3df672ad5e in signal_emit_unlocked_R (node=node@entry=0x55c462ae0060, detail=detail@entry=302, instance=instance@entry=0x7f3dd000cb70, emission_return=emission_return@entry=0x0, instance_and_params=instance_and_params@entry=0x7fff256d5dc0) at ../../../../gobject/gsignal.c:3635 #8 0x7f3df6733535 in g_signal_emit_valist (instance=0x7f3dd000cb70, signal_id=, detail=302, var_args=var_args@entry=0x7fff256d5f90) at ../../../../gobject/gsignal.c:3391 #10 0x7f3df671c464 in g_object_dispatch_properties_changed (object=0x7f3dd000cb70 [UpClient], n_pspecs=, pspecs=) at ../../../../gobject/gobject.c:1064 #11 0x7f3df671e8b9 in g_object_notify_by_spec_internal (pspec=0x55c462b1c830 [GParamBoolean], object=0x7f3dd000cb70 [UpClient]) at ../../../../gobject/gobject.c:1157 #12 0x7f3df671e8b9 in g_object_notify (object=0x7f3dd000cb70 [UpClient], property_name=0x55c462ad20ff "lid-is-closed") at ../../../../gobject/gobject.c:1205 #16 0x7f3df6733f4f in (instance=instance@entry=0x55c462ae9580, signal_id=, detail=) at ../../../../gobject/gsignal.c:3447 #13 0x7f3df6717f9d in g_closure_invoke (closure=0x55c462ecdbd0, return_value=0x0, n_param_values=2, param_values=0x7fff256d62a0, invocation_hint=0x7fff256d6220) at ../../../../gobject/gclosure.c:804 ---Type to continue, or q to quit--- #14 0x7f3df672ad5e in signal_emit_unlocked_R (node=node@entry=0x55c462ae0060, detail=detail@entry=302, instance=instance@entry=0x55c462ae9580, emission_return=emission_return@entry=0x0, instance_and_params=instance_and_params@entry=0x7fff256d62a0) at ../../../../gobject/gsignal.c:3635 #15 0x7f3df6733535 in g_signal_emit_valist (instance=0x55c462ae9580, signal_id=, detail=302, var_args=var_args@entry=0x7fff256d6470) at ../../../../gobject/gsignal.c:3391 #17 0x7f3df671c464 in g_object_dispatch_properties_changed (object=0x55c462ae9580 [UpExportedDaemonProxy], n_pspecs=, pspecs=) at ../../../../gobject/gobject.c:1064 #18 0x7f3df671e8b9 in g_object_notify_by_spec_internal (pspec=0x55c462b0fc40 [GParamOverride], object=0x55c462ae9580 [UpExportedDaemonProxy]) at ../../../../gobject/gobject.c:1157 #19 0x7f3df671e8b9 in g_object_notify (object=0x55c462ae9580 [UpExportedDaemonProxy], property_name=0x7f3deb10b5cd "lid-is-closed") at ../../../../gobject/gobject.c:1205 #20 0x7f3deb100bbc in () at /usr/lib/x86_64-linux-gnu/libupower-glib.so.3 #21 0x7f3df03a1e18 in ffi_call_unix64 () at /usr/lib/x86_64-linux-gnu/libffi.so.6 #22 0x7f3df03a187a in ffi_call () at /usr/lib/x86_64-linux-gnu/libffi.so.6 #27 0x7f3df6733f4f in (instance=instance@entry=0x55c462ae9580, signal_id=, detail=detail@entry=0) at ../../../../gobject/gsignal.c:3447 ---Type to continue, or q to quit--- #23 0x7f3df6718799 in g_cclosure_marshal_generic (closure=0x55c462ae73a0, return_gvalue=0x0, n_param_values=, param_values=, invocation_hint=, marshal_data=) at ../../../../gobject/gclosure.c:1490 #24 0x7f3df6717f9d in g_closure_invoke (closure=0x55c462ae73a0,
[Bug 1721718] [NEW] Segmentation fault in meta_monitor_mode_get_resolution
Public bug reported: When I change the monitor configuration on my newly updated Artful system I get a desktop crash. A quick reproduction with gdb attached to gnome-shell gave the following back-trace, unfortunately with symbols for gnome-shell but not for libmutter (I am still a bit of a new-comer to gnome-shell). Thread 1 "gnome-shell" received signal SIGSEGV, Segmentation fault. 0x7f2b2d75bf50 in meta_monitor_mode_get_resolution () from /usr/lib/x86_64-linux-gnu/libmutter-1.so.0 (gdb) bt #0 0x7f2b2d75bf50 in meta_monitor_mode_get_resolution () at /usr/lib/x86_64-linux-gnu/libmutter-1.so.0 #1 0x7f2b2d75bfd2 in meta_monitor_calculate_mode_scale () at /usr/lib/x86_64-linux-gnu/libmutter-1.so.0 #2 0x7f2b2d758437 in meta_finish_monitors_config_migration () at /usr/lib/x86_64-linux-gnu/libmutter-1.so.0 #3 0x7f2b2d7558fe in meta_monitor_config_manager_get_stored () at /usr/lib/x86_64-linux-gnu/libmutter-1.so.0 #4 0x7f2b2d75d732 in meta_monitor_manager_ensure_configured () at /usr/lib/x86_64-linux-gnu/libmutter-1.so.0 #5 0x7f2b2f531f9d in g_closure_invoke () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 #6 0x7f2b2f544d5e in () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 #7 0x7f2b2f54d535 in g_signal_emit_valist () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 #8 0x7f2b2f54df4f in g_signal_emit () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 #9 0x7f2b2f536464 in () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 #10 0x7f2b2f5388b9 in g_object_notify () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 #11 0x7f2b2f531f9d in g_closure_invoke () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 #12 0x7f2b2f544d5e in () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 ---Type to continue, or q to quit--- #13 0x7f2b2f54d535 in g_signal_emit_valist () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 #14 0x7f2b2f54df4f in g_signal_emit () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 #15 0x7f2b2f536464 in () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 #16 0x7f2b2f5388b9 in g_object_notify () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 #17 0x7f2b23f1abbc in () at /usr/lib/x86_64-linux-gnu/libupower-glib.so.3 #18 0x7f2b291bbe18 in ffi_call_unix64 () at /usr/lib/x86_64-linux-gnu/libffi.so.6 #19 0x7f2b291bb87a in ffi_call () at /usr/lib/x86_64-linux-gnu/libffi.so.6 #20 0x7f2b2f532799 in g_cclosure_marshal_generic () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 #21 0x7f2b2f531f9d in g_closure_invoke () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 #22 0x7f2b2f5447d8 in () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 #23 0x7f2b2f54d535 in g_signal_emit_valist () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 #24 0x7f2b2f54df4f in g_signal_emit () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 #25 0x7f2b2f83f311 in () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 #26 0x7f2b2f82e804 in () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 #27 0x7f2b2f258de5 in g_main_context_dispatch () ---Type to continue, or q to quit--- at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #28 0x7f2b2f2591b0 in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #29 0x7f2b2f2594c2 in g_main_loop_run () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #30 0x7f2b2d79201c in meta_run () at /usr/lib/x86_64-linux-gnu/libmutter-1.so.0 #31 0x56266c5ff307 in main (argc=, argv=) at ../src/main.c:462 ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: libmutter-1-0 3.26.0+20170925~ea214fb-1ubuntu1 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: Fri Oct 6 10:03:09 2017 InstallationDate: Installed on 2016-05-31 (492 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: mutter UpgradeStatus: Upgraded to artful on 2017-10-05 (1 days ago) ** Affects: mutter (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful wayland-session -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1721718 Title: Segmentation fault in meta_monitor_mode_get_resolution To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1721718/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1674838] Re: kernel BUG at /build/linux-7LGLH_/linux-4.10.0/include/linux/swapops.h:129
I was also experiencing this issue with the official 4.10.0-21-generic kernel; I ran the ~lp1674838 kernel for several days, and have been running the -22-generic test kernel for a couple without problems. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1674838 Title: kernel BUG at /build/linux- 7LGLH_/linux-4.10.0/include/linux/swapops.h:129 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1674838/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 536832] Re: Setting compose key as 'right CTRL' traps cursor in VirtualBox
If upstream means VirtualBox upstream, I wonder whether this is still an issue with VirtualBox 5.1. We re-did the capturing code for that version when we switched to Qt 5. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/536832 Title: Setting compose key as 'right CTRL' traps cursor in VirtualBox To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-lts-xenial/+bug/536832/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1671377] [NEW] Crash in VirtualBox with libdrm/intel, fixed in git
Public bug reported: When starting a VirtualBox virtual machine using VMSVGA emulation on Ubuntu 17.04 I get a crash. I tracked this down to the Intel code in libdrm and Chris Wilson committed the fix to git as 19c4cfc5. I verified that the crash occurs with libdrm build from git before but not after that commit. Could you please apply this to the Ubuntu package? ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: libdrm-intel1 2.4.75-1 ProcVersionSignature: Ubuntu 4.10.0-8.10-generic 4.10.0-rc8 Uname: Linux 4.10.0-8-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.4-0ubuntu2 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:Unity7 Date: Thu Mar 9 09:07:59 2017 DistUpgraded: Fresh install DistroCodename: zesty DistroVariant: 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 (281 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) Lsusb: Bus 002 Device 003: ID 0a5c:5801 Broadcom Corp. BCM5880 Secure Applications Processor with fingerprint swipe sensor Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Latitude E6420 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-8-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: libdrm UpgradeStatus: No upgrade log present (probably fresh install) 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.04.20170109-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.75-1 version.libgl1-mesa-dri: libgl1-mesa-dri 13.0.4-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 13.0.4-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu9 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.8.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160706-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.13-1 ** Affects: libdrm (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 has-fix regression reproducible ubuntu zesty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1671377 Title: Crash in VirtualBox with libdrm/intel, fixed in git To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1671377/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1443853] Re: Ubuntu 14.10 ISO live boot in Oracle VirtualBox ends up with a corrupted display
Gianfranco, now I am interested - could you point me to the change you mean? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1443853 Title: Ubuntu 14.10 ISO live boot in Oracle VirtualBox ends up with a corrupted display To manage notifications about this bug go to: https://bugs.launchpad.net/virtualbox/+bug/1443853/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1640112 Title: Irregular USB network tethering failures To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1640112/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1634737] Re: ohci-pci: frame counter not updating; disabled
The problem is not caused by any changes in the Linux OHCI or USB code (and obviously the VirtualBox USB emulation did not change either). It's almost certainly triggered by the timer wheel rework which went into the 4.8 kernel. There is a watchdog routine in the OHCI driver which is meant to be run every 250 milliseconds and check whether the frame counter is updating (which happens at most every millisecond). In Linux 4.8, the watchdog routine can be run again after 4 milliseconds or possibly even less. If it sees the same frame counter value twice, it declares the HC dead and unloads the driver. That is the problem. The "irq 22: nobody cared" and subsequent "Disabling IRQ #22" errors are caused by a bug in VirtualBox which is only triggered by unloading the OHCI driver. The "frame counter not updating" error is the real issue and highly likely to be an unintentional change in Linux 4.8 behavior. As far as the OHCI driver is concerned, it's OK to run the watchdog routine later than requested, but it must not be run too soon. And yes, https://bugs.launchpad.net/ubuntu/+bug/1635012 is almost certainly the same problem occurring on physical hardware. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1634737 Title: ohci-pci: frame counter not updating; disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1634737/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1633409] Re: dpkg hang while installing mainline kernel packages
Oh sorry, I see that I ran ubuntu-bug on the (Yakkety) host system, so the information in the bug is obviously incorrect. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1633409 Title: dpkg hang while installing mainline kernel packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/1633409/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1633409] Re: dpkg hang while installing mainline kernel packages
This is a Xenial virtual system. Can I do the test on that? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1633409 Title: dpkg hang while installing mainline kernel packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/1633409/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1633409] [NEW] dpkg hang while installing mainline kernel packages
Public bug reported: Before I start: this issue does not inconvenience me very much. I am mainly submitting it because it provides a good test case to investigate dpkg hangs, which it seems do occur from time to time. If it is not of interest please feel free to close again, or to let the bug expire. When I install the mainline daily kernel i386 headers and builds built on October 11 and on October 13 in an almost completely fresh 32-bit Ubuntu 16.04 virtual machine in VirtualBox, installation is painfully slow - currently, after nearly two hours, it is on the second package of three. I do the installation by manually downloading the headers-all, the headers-generic and the image-generic packages (for completeness I download on the host, and I scp them from the guest) and executing "sudo dpkg -i" in a gnome-terminal on the guest. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: dpkg 1.18.10ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-17.19-generic 4.8.0-rc7 Uname: Linux 4.8.0-17-generic x86_64 ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity:Unity7 Date: Fri Oct 14 11:47:46 2016 InstallationDate: Installed on 2016-05-31 (135 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: dpkg UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: dpkg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug yakkety -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1633409 Title: dpkg hang while installing mainline kernel packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/1633409/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1604009] Re: Empty menus in global app-menu in VirtualBox second window
Sorry for the noise. After fixing my change the local menus are gone. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1604009 Title: Empty menus in global app-menu in VirtualBox second window To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdbusmenu-qt/+bug/1604009/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1604009] Re: Empty menus in global app-menu in VirtualBox second window
User error indeed - I did #if 0 instead of #if 1. Rebuilding now, but because of my lack of experience with debuild I am stuck in a full build again. By the way, lots of test cases fail after the change. I disabled them in debian/rules locally. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1604009 Title: Empty menus in global app-menu in VirtualBox second window To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdbusmenu-qt/+bug/1604009/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1604009] Re: Empty menus in global app-menu in VirtualBox second window
I rebuilt Qt5 with that change but do not see any difference. Might be user error of course. I downloaded with apt-get source, made the change, rebuilt with debuild binary and (for simplicity) installed all resulting .deb files with dpkg -i. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1604009 Title: Empty menus in global app-menu in VirtualBox second window To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdbusmenu-qt/+bug/1604009/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1604009] Re: Empty menus in global app-menu in VirtualBox second window
Not sure if you want to include the double menu issue here or if you prefer to treat the bug as fixed. As a reminder, the double menu issue seemed to happen with appmenu-qt because it simply hid the local menus but did not intercept hide and show requests from the application. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1604009 Title: Empty menus in global app-menu in VirtualBox second window To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdbusmenu-qt/+bug/1604009/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
