[Touch-packages] [Bug 1804885] [NEW] Desktop freeze running VirtualBox, Intel graphics
Public bug reported: When I start a VirtualBox virtual machine (reproducible with the Ubuntu 18.04/VirtualBox 5.2.22 packages from virtualbox.org) with VMSVGA emulation and 3D pass-through enabled, my system hangs. Sometimes I can recover if I get to a VT fast enough to kill the process. Also, the OOM killer sometimes triggers and kills the process or gnome-shell, but the OOM killer entries in dmesg look like neither of the two are using excessive memory compared to available system RAM. When I switch to the Ubuntu drm-tip kernel packages from the kernel PPA the problem goes away. Debugging shows that the hang occurs during the first glXMakeCurrent call made by the application. It did not occur using the standard Ubuntu kernel but running the application under apitrace. I can provide the trace if that helps. Short extract from glxinfo running the 4.20 drm-tip kernel: Extended renderer info (GLX_MESA_query_renderer): Vendor: Intel Open Source Technology Center (0x8086) Device: Mesa DRI Intel(R) HD Graphics 620 (Kaby Lake GT2) (0x5916) Version: 18.2.2 Accelerated: yes Video memory: 3072MB Unified memory: yes Preferred profile: core (0x1) Max core profile version: 4.5 Max compat profile version: 3.0 Max GLES1 profile version: 1.1 Max GLES[23] profile version: 3.2 ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: xorg 1:7.7+19ubuntu8 Uname: Linux 4.20.0-994-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 BootLog: Error: [Errno 13] Отказано в доступе: '/var/log/boot.log' CasperVersion: 1.399 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Nov 23 21:13:00 2018 DistUpgraded: 2018-10-08 10:28:22,218 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: cosmic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GpuHangFrequency: Several times a day GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Lenovo HD Graphics 620 [17aa:2245] InstallationDate: Installed on 2018-06-12 (164 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: LENOVO 20HES0E73E ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.20.0-994-generic root=/dev/mapper/ubuntu--vg-root ro scsi_mod.use_blk_mq=1 quiet splash crashkernel=384M-:128M SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to cosmic on 2018-10-08 (46 days ago) dmi.bios.date: 09/13/2018 dmi.bios.vendor: LENOVO dmi.bios.version: N1QET78W (1.53 ) dmi.board.asset.tag: Not Available dmi.board.name: 20HES0E73E dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1QET78W(1.53):bd09/13/2018:svnLENOVO:pn20HES0E73E:pvrThinkPadT470:rvnLENOVO:rn20HES0E73E:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T470 dmi.product.name: 20HES0E73E dmi.product.sku: LENOVO_MT_20HE_BU_Think_FM_ThinkPad T470 dmi.product.version: ThinkPad T470 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.3-0~ubuntu18.10.1~ppa1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug cosmic freeze third-party-packages ubuntu wayland-session -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1804885 Title: Desktop freeze running VirtualBox, Intel graphics Status in xorg package in Ubuntu: New Bug description: When I start a VirtualBox virtual machine (reproducible with the Ubuntu 18.04/VirtualBox 5.2.22 packages from virtualbox.org) with VMSVGA emulation and 3D pass-through enabled, my system hangs. Sometimes I can recover if I get to a VT fast enough to kill the process. Also, the OOM killer sometimes triggers and kills the process or gnome-shell, but the OOM killer entries in dmesg look like neither of the two are using excessive memory compared to available system RAM. When I switch to the Ubuntu drm-tip kernel packages from the kernel PPA the problem goes away. Debugging shows that the hang
[Touch-packages] [Bug 1805151] [NEW] Desktop freeze running VirtualBox, Intel graphics
Public bug reported: This is identical to bug 1804885, but as requested I am filing this while running the standard Ubuntu kernel. I will copy and paste my summary below. Updates since I created that bug: * This occurs with the mainline PPA 4.18.12-041812-generic kernel. * The glxinfo section I include below is identical with 4.18.0-11-generic (presumably no surprise). * I would appreciate a bit of hand-holding for bisecting this. Does the kernel team have ready-built kernel packages for bisecting? Or guidance about the fastest way of doing it (i.e. not rebuilding things which do not need to be rebuilt for successive rounds)? === Original report follows === When I start a VirtualBox virtual machine (reproducible with the Ubuntu 18.04/VirtualBox 5.2.22 packages from virtualbox.org) with VMSVGA emulation and 3D pass-through enabled, my system hangs. Sometimes I can recover if I get to a VT fast enough to kill the process. Also, the OOM killer sometimes triggers and kills the process or gnome-shell, but the OOM killer entries in dmesg look like neither of the two are using excessive memory compared to available system RAM. When I switch to the Ubuntu drm-tip kernel packages from the kernel PPA the problem goes away. Debugging shows that the hang occurs during the first glXMakeCurrent call made by the application. It did not occur using the standard Ubuntu kernel but running the application under apitrace. I can provide the trace if that helps. Short extract from glxinfo running the 4.20 drm-tip kernel: Extended renderer info (GLX_MESA_query_renderer): Vendor: Intel Open Source Technology Center (0x8086) Device: Mesa DRI Intel(R) HD Graphics 620 (Kaby Lake GT2) (0x5916) Version: 18.2.2 Accelerated: yes Video memory: 3072MB Unified memory: yes Preferred profile: core (0x1) Max core profile version: 4.5 Max compat profile version: 3.0 Max GLES1 profile version: 1.1 Max GLES[23] profile version: 3.2 ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: xorg 1:7.7+19ubuntu8 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 BootLog: Error: [Errno 13] Отказано в доступе: '/var/log/boot.log' CasperVersion: 1.399 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Nov 26 15:01:53 2018 DistUpgraded: 2018-10-08 10:28:22,218 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: cosmic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GpuHangFrequency: Several times a day GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Lenovo HD Graphics 620 [17aa:2245] InstallationDate: Installed on 2018-06-12 (166 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: LENOVO 20HES0E73E ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-11-generic root=/dev/mapper/ubuntu--vg-root ro scsi_mod.use_blk_mq=1 quiet splash crashkernel=384M-:128M SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to cosmic on 2018-10-08 (49 days ago) dmi.bios.date: 09/13/2018 dmi.bios.vendor: LENOVO dmi.bios.version: N1QET78W (1.53 ) dmi.board.asset.tag: Not Available dmi.board.name: 20HES0E73E dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1QET78W(1.53):bd09/13/2018:svnLENOVO:pn20HES0E73E:pvrThinkPadT470:rvnLENOVO:rn20HES0E73E:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T470 dmi.product.name: 20HES0E73E dmi.product.sku: LENOVO_MT_20HE_BU_Think_FM_ThinkPad T470 dmi.product.version: ThinkPad T470 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.3-0~ubuntu18.10.1~ppa1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug cosmic freeze third-party-packages ubuntu wayland-session -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1805151 Title: Desktop freeze ru
[Touch-packages] [Bug 1805151] Re: Desktop freeze running VirtualBox, Intel graphics
Update: 4.19.4-041904-generic is affected, 4.20.0-042000rc1-generic is not. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1805151 Title: Desktop freeze running VirtualBox, Intel graphics Status in xorg package in Ubuntu: New Bug description: This is identical to bug 1804885, but as requested I am filing this while running the standard Ubuntu kernel. I will copy and paste my summary below. Updates since I created that bug: * This occurs with the mainline PPA 4.18.12-041812-generic kernel. * The glxinfo section I include below is identical with 4.18.0-11-generic (presumably no surprise). * I would appreciate a bit of hand-holding for bisecting this. Does the kernel team have ready-built kernel packages for bisecting? Or guidance about the fastest way of doing it (i.e. not rebuilding things which do not need to be rebuilt for successive rounds)? === Original report follows === When I start a VirtualBox virtual machine (reproducible with the Ubuntu 18.04/VirtualBox 5.2.22 packages from virtualbox.org) with VMSVGA emulation and 3D pass-through enabled, my system hangs. Sometimes I can recover if I get to a VT fast enough to kill the process. Also, the OOM killer sometimes triggers and kills the process or gnome-shell, but the OOM killer entries in dmesg look like neither of the two are using excessive memory compared to available system RAM. When I switch to the Ubuntu drm-tip kernel packages from the kernel PPA the problem goes away. Debugging shows that the hang occurs during the first glXMakeCurrent call made by the application. It did not occur using the standard Ubuntu kernel but running the application under apitrace. I can provide the trace if that helps. Short extract from glxinfo running the 4.20 drm-tip kernel: Extended renderer info (GLX_MESA_query_renderer): Vendor: Intel Open Source Technology Center (0x8086) Device: Mesa DRI Intel(R) HD Graphics 620 (Kaby Lake GT2) (0x5916) Version: 18.2.2 Accelerated: yes Video memory: 3072MB Unified memory: yes Preferred profile: core (0x1) Max core profile version: 4.5 Max compat profile version: 3.0 Max GLES1 profile version: 1.1 Max GLES[23] profile version: 3.2 ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: xorg 1:7.7+19ubuntu8 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 BootLog: Error: [Errno 13] Отказано в доступе: '/var/log/boot.log' CasperVersion: 1.399 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Nov 26 15:01:53 2018 DistUpgraded: 2018-10-08 10:28:22,218 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: cosmic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GpuHangFrequency: Several times a day GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Lenovo HD Graphics 620 [17aa:2245] InstallationDate: Installed on 2018-06-12 (166 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: LENOVO 20HES0E73E ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-11-generic root=/dev/mapper/ubuntu--vg-root ro scsi_mod.use_blk_mq=1 quiet splash crashkernel=384M-:128M SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to cosmic on 2018-10-08 (49 days ago) dmi.bios.date: 09/13/2018 dmi.bios.vendor: LENOVO dmi.bios.version: N1QET78W (1.53 ) dmi.board.asset.tag: Not Available dmi.board.name: 20HES0E73E dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1QET78W(1.53):bd09/13/2018:svnLENOVO:pn20HES0E73E:pvrThinkPadT470:rvnLENOVO:rn20HES0E73E:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T470 dmi.product.name: 20HES0E73E dmi.product.sku: LENOVO_MT_20HE_BU_Think_FM_ThinkPad T470 dmi.product.version: ThinkPad T470 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.3-0~ubuntu18.10.1~ppa1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1 version.xs
[Touch-packages] [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 Touch seeded packages, which is subscribed to qtchooser in Ubuntu. https://bugs.launchpad.net/bugs/1781861 Title: qtchooser should select right version when only one is installed Status in qtchooser package in Ubuntu: New Bug description: 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) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtchooser/+bug/1781861/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [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 Touch seeded packages, which is subscribed to kbd in Ubuntu. https://bugs.launchpad.net/bugs/1443853 Title: Ubuntu boot in Oracle VirtualBox ends up with a corrupted display Status in Virtualbox: Invalid Status in console-setup package in Ubuntu: Triaged Status in kbd package in Ubuntu: Triaged Status in virtualbox package in Ubuntu: Triaged Bug description: (Content copied from "Ubuntu 14.10 ISO live boot ends up with a corrupted display" #13615 VirtualBox bug ticket, by piotrjurkiewicz) Booting up live session of Ubuntu MATE 14.10 and Ubuntu Gnome 14.10 from ISO ends up with a corrupted screen. See the screenshot: https://launchpadlibrarian.net/186864347/ubu.png Switching back and forth to the tty7 (ctrl+alt+F1 and then alt+F7) fixes the display. I think that this might be a problem with resolution setting: ``` 00:00:31.226379 Display::handleDisplayResize(): uScreenId = 0, pvVRAM= w=1152 h=400 bpp=0 cbLine=0x0, flags=0x1 00:00:31.226399 UIFrameBuffer::RequestResize: Screen=0, Format=0, BitsPerPixel=0, BytesPerLine=0, Size=1152x400, Sending to async-handler.. 00:00:31.226457 UIFrameBufferQImage::resizeEvent: Format=0, BitsPerPixel=0, BytesPerLine=0, Size=1152x400 00:00:31.226467 UIFrameBufferQImage::resizeEvent: Resizing to FALLBACK buffer due to format is invalid.. ``` After switching back and forth to the tty7 (what fixes the display) the log says: ``` 00:00:31.226379 Display::handleDisplayResize(): uScreenId = 0, pvVRAM= w=1152 h=400 bpp=0 cbLine=0x0, flags=0x1 00:00:31.226399 UIFrameBuffer::RequestResize: Screen=0, Format=0, BitsPerPixel=0, BytesPerLine=0, Size=1152x400, Sending to async-handler.. 00:00:31.226457 UIFrameBufferQImage::resizeEvent: Format=0, BitsPerPixel=0, BytesPerLine=0, Size=1152x400 00:00:31.226467 UIFrameBufferQImage::resizeEvent: Resizing to FALLBACK buffer due to format is invalid.. 00:01:37.584616 Display::handleDisplayResize(): uScreenId = 0, pvVRAM= w=720 h=400 bpp=0 cbLine=0x0, flags=0x1 00:01:37.584634 UIFrameBuffer::RequestResize: Screen=0, Format=0, BitsPerPixel=0, BytesPerLine=0, Size=720x400, Sending to async-handler.. 00:01:37.584680 UIFrameBufferQImage::resizeEvent: Format=0, BitsPerPixel=0, BytesPerLine=0, Size=720x400 00:01:37.584692 UIFrameBufferQImage::resizeEvent: Resizing to FALLBACK buffer due to format is invalid.. 00:01:39.055475 Display::handleDisplayResize(): uScreenId = 0, pvVRAM=0a7f w=1024 h=768 bpp=32 cbLine=0x1000, flags=0x1 00:01:39.055495 UIFrameBuffer::RequestResize: Screen=0, Format=843204434, BitsPerPixel=32, BytesPerLine=4096, Size=1024x768, Sending to async-handler.. 00:01:39.09 UIFrameBufferQImage::resizeEvent: Format=843204434, BitsPerPixel=32, BytesPerLine=4096, Size=1024x768 00:01:39.055568 UIFrameBufferQImage::resizeEvent: Resizing to directly use VGA device content.. ``` I have tested 4.3.18 and also the testbuild 4.3.19 r96825, it happens on both of them. You can download the ISO images of these two systems here: https://ubuntu-mate.r.worldssl.net/download/ubuntu-mate-14.10 -desktop-amd64.iso http://cdimage.ubuntu.com/ubuntu-gnome/releases/14.10/release/ubuntu- gnome-14.10-desktop-amd64.iso To manage notifications about this bug go to: https://bugs.launchpad.net/virtualbox/+bug/1443853/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [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 Touch seeded packages, which is subscribed to kbd in Ubuntu. https://bugs.launchpad.net/bugs/1443853 Title: Ubuntu boot in Oracle VirtualBox ends up with a corrupted display Status in Virtualbox: Invalid Status in console-setup package in Ubuntu: Invalid Status in kbd package in Ubuntu: Invalid Status in virtualbox package in Ubuntu: Fix Released Bug description: (Content copied from "Ubuntu 14.10 ISO live boot ends up with a corrupted display" #13615 VirtualBox bug ticket, by piotrjurkiewicz) Booting up live session of Ubuntu MATE 14.10 and Ubuntu Gnome 14.10 from ISO ends up with a corrupted screen. See the screenshot: https://launchpadlibrarian.net/186864347/ubu.png Switching back and forth to the tty7 (ctrl+alt+F1 and then alt+F7) fixes the display. I think that this might be a problem with resolution setting: ``` 00:00:31.226379 Display::handleDisplayResize(): uScreenId = 0, pvVRAM= w=1152 h=400 bpp=0 cbLine=0x0, flags=0x1 00:00:31.226399 UIFrameBuffer::RequestResize: Screen=0, Format=0, BitsPerPixel=0, BytesPerLine=0, Size=1152x400, Sending to async-handler.. 00:00:31.226457 UIFrameBufferQImage::resizeEvent: Format=0, BitsPerPixel=0, BytesPerLine=0, Size=1152x400 00:00:31.226467 UIFrameBufferQImage::resizeEvent: Resizing to FALLBACK buffer due to format is invalid.. ``` After switching back and forth to the tty7 (what fixes the display) the log says: ``` 00:00:31.226379 Display::handleDisplayResize(): uScreenId = 0, pvVRAM= w=1152 h=400 bpp=0 cbLine=0x0, flags=0x1 00:00:31.226399 UIFrameBuffer::RequestResize: Screen=0, Format=0, BitsPerPixel=0, BytesPerLine=0, Size=1152x400, Sending to async-handler.. 00:00:31.226457 UIFrameBufferQImage::resizeEvent: Format=0, BitsPerPixel=0, BytesPerLine=0, Size=1152x400 00:00:31.226467 UIFrameBufferQImage::resizeEvent: Resizing to FALLBACK buffer due to format is invalid.. 00:01:37.584616 Display::handleDisplayResize(): uScreenId = 0, pvVRAM= w=720 h=400 bpp=0 cbLine=0x0, flags=0x1 00:01:37.584634 UIFrameBuffer::RequestResize: Screen=0, Format=0, BitsPerPixel=0, BytesPerLine=0, Size=720x400, Sending to async-handler.. 00:01:37.584680 UIFrameBufferQImage::resizeEvent: Format=0, BitsPerPixel=0, BytesPerLine=0, Size=720x400 00:01:37.584692 UIFrameBufferQImage::resizeEvent: Resizing to FALLBACK buffer due to format is invalid.. 00:01:39.055475 Display::handleDisplayResize(): uScreenId = 0, pvVRAM=0a7f w=1024 h=768 bpp=32 cbLine=0x1000, flags=0x1 00:01:39.055495 UIFrameBuffer::RequestResize: Screen=0, Format=843204434, BitsPerPixel=32, BytesPerLine=4096, Size=1024x768, Sending to async-handler.. 00:01:39.09 UIFrameBufferQImage::resizeEvent: Format=843204434, BitsPerPixel=32, BytesPerLine=4096, Size=1024x768 00:01:39.055568 UIFrameBufferQImage::resizeEvent: Resizing to directly use VGA device content.. ``` I have tested 4.3.18 and also the testbuild 4.3.19 r96825, it happens on both of them. You can download the ISO images of these two systems here: https://ubuntu-mate.r.worldssl.net/download/ubuntu-mate-14.10 -desktop-amd64.iso http://cdimage.ubuntu.com/ubuntu-gnome/releases/14.10/release/ubuntu- gnome-14.10-desktop-amd64.iso To manage notifications about this bug go to: https://bugs.launchpad.net/virtualbox/+bug/1443853/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [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 Touch seeded packages, which is subscribed to kbd in Ubuntu. https://bugs.launchpad.net/bugs/1443853 Title: Ubuntu boot in Oracle VirtualBox ends up with a corrupted display Status in Virtualbox: Invalid Status in console-setup package in Ubuntu: Invalid Status in kbd package in Ubuntu: Invalid Status in virtualbox package in Ubuntu: Fix Released Bug description: (Content copied from "Ubuntu 14.10 ISO live boot ends up with a corrupted display" #13615 VirtualBox bug ticket, by piotrjurkiewicz) Booting up live session of Ubuntu MATE 14.10 and Ubuntu Gnome 14.10 from ISO ends up with a corrupted screen. See the screenshot: https://launchpadlibrarian.net/186864347/ubu.png Switching back and forth to the tty7 (ctrl+alt+F1 and then alt+F7) fixes the display. I think that this might be a problem with resolution setting: ``` 00:00:31.226379 Display::handleDisplayResize(): uScreenId = 0, pvVRAM= w=1152 h=400 bpp=0 cbLine=0x0, flags=0x1 00:00:31.226399 UIFrameBuffer::RequestResize: Screen=0, Format=0, BitsPerPixel=0, BytesPerLine=0, Size=1152x400, Sending to async-handler.. 00:00:31.226457 UIFrameBufferQImage::resizeEvent: Format=0, BitsPerPixel=0, BytesPerLine=0, Size=1152x400 00:00:31.226467 UIFrameBufferQImage::resizeEvent: Resizing to FALLBACK buffer due to format is invalid.. ``` After switching back and forth to the tty7 (what fixes the display) the log says: ``` 00:00:31.226379 Display::handleDisplayResize(): uScreenId = 0, pvVRAM= w=1152 h=400 bpp=0 cbLine=0x0, flags=0x1 00:00:31.226399 UIFrameBuffer::RequestResize: Screen=0, Format=0, BitsPerPixel=0, BytesPerLine=0, Size=1152x400, Sending to async-handler.. 00:00:31.226457 UIFrameBufferQImage::resizeEvent: Format=0, BitsPerPixel=0, BytesPerLine=0, Size=1152x400 00:00:31.226467 UIFrameBufferQImage::resizeEvent: Resizing to FALLBACK buffer due to format is invalid.. 00:01:37.584616 Display::handleDisplayResize(): uScreenId = 0, pvVRAM= w=720 h=400 bpp=0 cbLine=0x0, flags=0x1 00:01:37.584634 UIFrameBuffer::RequestResize: Screen=0, Format=0, BitsPerPixel=0, BytesPerLine=0, Size=720x400, Sending to async-handler.. 00:01:37.584680 UIFrameBufferQImage::resizeEvent: Format=0, BitsPerPixel=0, BytesPerLine=0, Size=720x400 00:01:37.584692 UIFrameBufferQImage::resizeEvent: Resizing to FALLBACK buffer due to format is invalid.. 00:01:39.055475 Display::handleDisplayResize(): uScreenId = 0, pvVRAM=0a7f w=1024 h=768 bpp=32 cbLine=0x1000, flags=0x1 00:01:39.055495 UIFrameBuffer::RequestResize: Screen=0, Format=843204434, BitsPerPixel=32, BytesPerLine=4096, Size=1024x768, Sending to async-handler.. 00:01:39.09 UIFrameBufferQImage::resizeEvent: Format=843204434, BitsPerPixel=32, BytesPerLine=4096, Size=1024x768 00:01:39.055568 UIFrameBufferQImage::resizeEvent: Resizing to directly use VGA device content.. ``` I have tested 4.3.18 and also the testbuild 4.3.19 r96825, it happens on both of them. You can download the ISO images of these two systems here: https://ubuntu-mate.r.worldssl.net/download/ubuntu-mate-14.10 -desktop-amd64.iso http://cdimage.ubuntu.com/ubuntu-gnome/releases/14.10/release/ubuntu- gnome-14.10-desktop-amd64.iso To manage notifications about this bug go to: https://bugs.launchpad.net/virtualbox/+bug/1443853/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [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 Touch seeded packages, which is subscribed to kbd in Ubuntu. https://bugs.launchpad.net/bugs/1443853 Title: Ubuntu boot in Oracle VirtualBox ends up with a corrupted display Status in Virtualbox: Invalid Status in console-setup package in Ubuntu: Invalid Status in kbd package in Ubuntu: Invalid Status in virtualbox package in Ubuntu: Fix Released Bug description: (Content copied from "Ubuntu 14.10 ISO live boot ends up with a corrupted display" #13615 VirtualBox bug ticket, by piotrjurkiewicz) Booting up live session of Ubuntu MATE 14.10 and Ubuntu Gnome 14.10 from ISO ends up with a corrupted screen. See the screenshot: https://launchpadlibrarian.net/186864347/ubu.png Switching back and forth to the tty7 (ctrl+alt+F1 and then alt+F7) fixes the display. I think that this might be a problem with resolution setting: ``` 00:00:31.226379 Display::handleDisplayResize(): uScreenId = 0, pvVRAM= w=1152 h=400 bpp=0 cbLine=0x0, flags=0x1 00:00:31.226399 UIFrameBuffer::RequestResize: Screen=0, Format=0, BitsPerPixel=0, BytesPerLine=0, Size=1152x400, Sending to async-handler.. 00:00:31.226457 UIFrameBufferQImage::resizeEvent: Format=0, BitsPerPixel=0, BytesPerLine=0, Size=1152x400 00:00:31.226467 UIFrameBufferQImage::resizeEvent: Resizing to FALLBACK buffer due to format is invalid.. ``` After switching back and forth to the tty7 (what fixes the display) the log says: ``` 00:00:31.226379 Display::handleDisplayResize(): uScreenId = 0, pvVRAM= w=1152 h=400 bpp=0 cbLine=0x0, flags=0x1 00:00:31.226399 UIFrameBuffer::RequestResize: Screen=0, Format=0, BitsPerPixel=0, BytesPerLine=0, Size=1152x400, Sending to async-handler.. 00:00:31.226457 UIFrameBufferQImage::resizeEvent: Format=0, BitsPerPixel=0, BytesPerLine=0, Size=1152x400 00:00:31.226467 UIFrameBufferQImage::resizeEvent: Resizing to FALLBACK buffer due to format is invalid.. 00:01:37.584616 Display::handleDisplayResize(): uScreenId = 0, pvVRAM= w=720 h=400 bpp=0 cbLine=0x0, flags=0x1 00:01:37.584634 UIFrameBuffer::RequestResize: Screen=0, Format=0, BitsPerPixel=0, BytesPerLine=0, Size=720x400, Sending to async-handler.. 00:01:37.584680 UIFrameBufferQImage::resizeEvent: Format=0, BitsPerPixel=0, BytesPerLine=0, Size=720x400 00:01:37.584692 UIFrameBufferQImage::resizeEvent: Resizing to FALLBACK buffer due to format is invalid.. 00:01:39.055475 Display::handleDisplayResize(): uScreenId = 0, pvVRAM=0a7f w=1024 h=768 bpp=32 cbLine=0x1000, flags=0x1 00:01:39.055495 UIFrameBuffer::RequestResize: Screen=0, Format=843204434, BitsPerPixel=32, BytesPerLine=4096, Size=1024x768, Sending to async-handler.. 00:01:39.09 UIFrameBufferQImage::resizeEvent: Format=843204434, BitsPerPixel=32, BytesPerLine=4096, Size=1024x768 00:01:39.055568 UIFrameBufferQImage::resizeEvent: Resizing to directly use VGA device content.. ``` I have tested 4.3.18 and also the testbuild 4.3.19 r96825, it happens on both of them. You can download the ISO images of these two systems here: https://ubuntu-mate.r.worldssl.net/download/ubuntu-mate-14.10 -desktop-amd64.iso http://cdimage.ubuntu.com/ubuntu-gnome/releases/14.10/release/ubuntu- gnome-14.10-desktop-amd64.iso To manage notifications about this bug go to: https://bugs.launchpad.net/virtualbox/+bug/1443853/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [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 Touch seeded packages, which is subscribed to resolvconf in Ubuntu. https://bugs.launchpad.net/bugs/1722722 Title: Search domains not deleted from resolv.conf Status in resolvconf package in Ubuntu: New Bug description: 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) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1722722/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1723075] [NEW] System freeze after docking and display configuration change
Public bug reported: I have been having regular system freezes after switching from using my laptop stand-alone to waking it up on a docking station with an external monitor. I have seen this using two identical docking station plus monitor combinations. I am still trying to find a pattern. I often find the laptop going to sleep again immediately after being woken up. When it freezes, the screen saver is visible on the internal display and the external monitor is (I think) enabled but blank. I saw this with 4.13.0-13-generic, and have not yet had the chance to test it with 4.13.0-15-generic. I have also not had the chance yet to try to ssh in. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: xorg 1:7.7+19ubuntu2 ProcVersionSignature: Ubuntu 4.13.0-15.16-generic 4.13.4 Uname: Linux 4.13.0-15-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.7-0ubuntu2 Architecture: amd64 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Oct 12 11:52:51 2017 DistUpgraded: 2017-10-05 07:40:01,856 ERROR got an error from dpkg for pkg: 'linux-image-extra-4.13.0-12-generic': 'subprocess installed post-installation script returned error exit status 1' DistroCodename: artful DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: Several times a week GpuHangReproducibility: Occurs more often under certain circumstances GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell 2nd Generation Core Processor Family Integrated Graphics Controller [1028:0493] InstallationDate: Installed on 2016-05-31 (498 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: Dell Inc. Latitude E6420 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-15-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to artful on 2017-10-05 (7 days ago) dmi.bios.date: 11/14/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A21 dmi.board.name: 0K0DNP dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA21:bd11/14/2013:svnDellInc.:pnLatitudeE6420:pvr01:rvnDellInc.:rn0K0DNP:rvrA02:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6420 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.13.1+17.10.20170901-0ubuntu1 version.libdrm2: libdrm2 2.4.83-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20170309-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful freeze ubuntu wayland-session -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1723075 Title: System freeze after docking and display configuration change Status in xorg package in Ubuntu: New Bug description: I have been having regular system freezes after switching from using my laptop stand-alone to waking it up on a docking station with an external monitor. I have seen this using two identical docking station plus monitor combinations. I am still trying to find a pattern. I often find the laptop going to sleep again immediately after being woken up. When it freezes, the screen saver is visible on the internal display and the external monitor is (I think) enabled but blank. I saw this with 4.13.0-13-generic, and have not yet had the chance to test it with 4.13.0-15-generic. I have also not had the chance yet to try to ssh in. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: xorg 1:7.7+19ubuntu2 ProcVersionSignature: Ubuntu 4.13.0-15.16-generic 4.13.4 Uname: Linux 4.13.0-15-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.7-0ubuntu2 Architecture: amd64 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Oct 12 11:52:51 2017 DistUpgraded: 2017-10-05 07:40:01,856 ERROR got an error from dpkg for pkg: 'linux-image-extra-4.13.0-12-generic': 'subprocess installed post-installation script returned error exit status 1' DistroCodename: artful DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: Several times a week GpuHangReproducibility: Occurs more often under certain circumstances GpuHangStarted: Immediately after installing this versi
[Touch-packages] [Bug 1723075] Re: System freeze after docking and display configuration change
Just got this again with 4.13.0-15-generic after suspending and resuming the laptop. No docking station or screen reconfiguration. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1723075 Title: System freeze after docking and display configuration change Status in xorg package in Ubuntu: New Bug description: I have been having regular system freezes after switching from using my laptop stand-alone to waking it up on a docking station with an external monitor. I have seen this using two identical docking station plus monitor combinations. I am still trying to find a pattern. I often find the laptop going to sleep again immediately after being woken up. When it freezes, the screen saver is visible on the internal display and the external monitor is (I think) enabled but blank. I saw this with 4.13.0-13-generic, and have not yet had the chance to test it with 4.13.0-15-generic. I have also not had the chance yet to try to ssh in. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: xorg 1:7.7+19ubuntu2 ProcVersionSignature: Ubuntu 4.13.0-15.16-generic 4.13.4 Uname: Linux 4.13.0-15-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.7-0ubuntu2 Architecture: amd64 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Oct 12 11:52:51 2017 DistUpgraded: 2017-10-05 07:40:01,856 ERROR got an error from dpkg for pkg: 'linux-image-extra-4.13.0-12-generic': 'subprocess installed post-installation script returned error exit status 1' DistroCodename: artful DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: Several times a week GpuHangReproducibility: Occurs more often under certain circumstances GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell 2nd Generation Core Processor Family Integrated Graphics Controller [1028:0493] InstallationDate: Installed on 2016-05-31 (498 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: Dell Inc. Latitude E6420 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-15-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to artful on 2017-10-05 (7 days ago) dmi.bios.date: 11/14/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A21 dmi.board.name: 0K0DNP dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA21:bd11/14/2013:svnDellInc.:pnLatitudeE6420:pvr01:rvnDellInc.:rn0K0DNP:rvrA02:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6420 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.13.1+17.10.20170901-0ubuntu1 version.libdrm2: libdrm2 2.4.83-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20170309-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1723075/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1723075] Re: System freeze after docking and display configuration change
*** This bug is a duplicate of bug 1724259 *** https://bugs.launchpad.net/bugs/1724259 Reported this again using apport as bug 1724259. ** This bug has been marked a duplicate of bug 1724259 System freeze after docking and display configuration change -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1723075 Title: System freeze after docking and display configuration change Status in xorg package in Ubuntu: New Bug description: I have been having regular system freezes after switching from using my laptop stand-alone to waking it up on a docking station with an external monitor. I have seen this using two identical docking station plus monitor combinations. I am still trying to find a pattern. I often find the laptop going to sleep again immediately after being woken up. When it freezes, the screen saver is visible on the internal display and the external monitor is (I think) enabled but blank. I saw this with 4.13.0-13-generic, and have not yet had the chance to test it with 4.13.0-15-generic. I have also not had the chance yet to try to ssh in. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: xorg 1:7.7+19ubuntu2 ProcVersionSignature: Ubuntu 4.13.0-15.16-generic 4.13.4 Uname: Linux 4.13.0-15-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.7-0ubuntu2 Architecture: amd64 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Oct 12 11:52:51 2017 DistUpgraded: 2017-10-05 07:40:01,856 ERROR got an error from dpkg for pkg: 'linux-image-extra-4.13.0-12-generic': 'subprocess installed post-installation script returned error exit status 1' DistroCodename: artful DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: Several times a week GpuHangReproducibility: Occurs more often under certain circumstances GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell 2nd Generation Core Processor Family Integrated Graphics Controller [1028:0493] InstallationDate: Installed on 2016-05-31 (498 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: Dell Inc. Latitude E6420 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-15-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to artful on 2017-10-05 (7 days ago) dmi.bios.date: 11/14/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A21 dmi.board.name: 0K0DNP dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA21:bd11/14/2013:svnDellInc.:pnLatitudeE6420:pvr01:rvnDellInc.:rn0K0DNP:rvrA02:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6420 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.13.1+17.10.20170901-0ubuntu1 version.libdrm2: libdrm2 2.4.83-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20170309-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1723075/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [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 Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1726020 Title: apport will not process report in /var/crash Status in systemd package in Ubuntu: New Bug description: 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. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1726020/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [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 Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1726020 Title: apport will not process report in /var/crash Status in systemd package in Ubuntu: New Bug description: 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. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1726020/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [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 Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1427600 Title: apport-unpack: ValueError: ['UserGroups'] has no binary content Status in apport package in Ubuntu: Triaged Status in apport source package in Xenial: Triaged Bug description: When running apport-unpack to get at a core dump laney@raleigh> sudo apport-unpack _usr_lib_x86_64-linux-gnu_urfkill_urfkilld.0.crash ~/temp/zozoz [sudo] password for laney: Traceback (most recent call last): File "/usr/bin/apport-unpack", line 73, in pr.extract_keys(f, bin_keys, dir) File "/usr/lib/python3/dist-packages/problem_report.py", line 253, in extract_keys [item for item, element in b64_block.items() if element is False]) ValueError: ['UserGroups'] has no binary content laney@raleigh> apport-cli --version 2.16.2 It's not terrible, because most files are unpacked (those which sort before UserGroups, I guess). ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: apport 2.16.2-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0 Uname: Linux 3.19.0-7-generic x86_64 ApportLog: ApportVersion: 2.16.2-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Tue Mar 3 10:09:26 2015 InstallationDate: Installed on 2012-10-07 (876 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Beta amd64 (20121007) PackageArchitecture: all SourcePackage: apport UpgradeStatus: Upgraded to vivid on 2013-05-07 (665 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1427600/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [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 Touch seeded packages, which is subscribed to kbd in Ubuntu. https://bugs.launchpad.net/bugs/1443853 Title: Ubuntu 14.10 ISO live boot in Oracle VirtualBox ends up with a corrupted display Status in Virtualbox: Invalid Status in console-setup package in Ubuntu: Incomplete Status in kbd package in Ubuntu: Incomplete Status in virtualbox package in Ubuntu: Incomplete Bug description: (Content copied from "Ubuntu 14.10 ISO live boot ends up with a corrupted display" #13615 VirtualBox bug ticket, by piotrjurkiewicz) Booting up live session of Ubuntu MATE 14.10 and Ubuntu Gnome 14.10 from ISO ends up with a corrupted screen. See the screenshot: https://launchpadlibrarian.net/186864347/ubu.png Switching back and forth to the tty7 (ctrl+alt+F1 and then alt+F7) fixes the display. I think that this might be a problem with resolution setting: ``` 00:00:31.226379 Display::handleDisplayResize(): uScreenId = 0, pvVRAM= w=1152 h=400 bpp=0 cbLine=0x0, flags=0x1 00:00:31.226399 UIFrameBuffer::RequestResize: Screen=0, Format=0, BitsPerPixel=0, BytesPerLine=0, Size=1152x400, Sending to async-handler.. 00:00:31.226457 UIFrameBufferQImage::resizeEvent: Format=0, BitsPerPixel=0, BytesPerLine=0, Size=1152x400 00:00:31.226467 UIFrameBufferQImage::resizeEvent: Resizing to FALLBACK buffer due to format is invalid.. ``` After switching back and forth to the tty7 (what fixes the display) the log says: ``` 00:00:31.226379 Display::handleDisplayResize(): uScreenId = 0, pvVRAM= w=1152 h=400 bpp=0 cbLine=0x0, flags=0x1 00:00:31.226399 UIFrameBuffer::RequestResize: Screen=0, Format=0, BitsPerPixel=0, BytesPerLine=0, Size=1152x400, Sending to async-handler.. 00:00:31.226457 UIFrameBufferQImage::resizeEvent: Format=0, BitsPerPixel=0, BytesPerLine=0, Size=1152x400 00:00:31.226467 UIFrameBufferQImage::resizeEvent: Resizing to FALLBACK buffer due to format is invalid.. 00:01:37.584616 Display::handleDisplayResize(): uScreenId = 0, pvVRAM= w=720 h=400 bpp=0 cbLine=0x0, flags=0x1 00:01:37.584634 UIFrameBuffer::RequestResize: Screen=0, Format=0, BitsPerPixel=0, BytesPerLine=0, Size=720x400, Sending to async-handler.. 00:01:37.584680 UIFrameBufferQImage::resizeEvent: Format=0, BitsPerPixel=0, BytesPerLine=0, Size=720x400 00:01:37.584692 UIFrameBufferQImage::resizeEvent: Resizing to FALLBACK buffer due to format is invalid.. 00:01:39.055475 Display::handleDisplayResize(): uScreenId = 0, pvVRAM=0a7f w=1024 h=768 bpp=32 cbLine=0x1000, flags=0x1 00:01:39.055495 UIFrameBuffer::RequestResize: Screen=0, Format=843204434, BitsPerPixel=32, BytesPerLine=4096, Size=1024x768, Sending to async-handler.. 00:01:39.09 UIFrameBufferQImage::resizeEvent: Format=843204434, BitsPerPixel=32, BytesPerLine=4096, Size=1024x768 00:01:39.055568 UIFrameBufferQImage::resizeEvent: Resizing to directly use VGA device content.. ``` I have tested 4.3.18 and also the testbuild 4.3.19 r96825, it happens on both of them. You can download the ISO images of these two systems here: https://ubuntu-mate.r.worldssl.net/download/ubuntu-mate-14.10 -desktop-amd64.iso http://cdimage.ubuntu.com/ubuntu-gnome/releases/14.10/release/ubuntu- gnome-14.10-desktop-amd64.iso To manage notifications about this bug go to: https://bugs.launchpad.net/virtualbox/+bug/1443853/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [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 Touch seeded packages, which is subscribed to libdrm in Ubuntu. https://bugs.launchpad.net/bugs/1671377 Title: Crash in VirtualBox with libdrm/intel, fixed in git Status in libdrm package in Ubuntu: New Bug description: 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
[Touch-packages] [Bug 1499133] Re: unity-panel-service crashed with SIGSEGV in gtk_menu_tracker_remove_items()
Might this be related to bug 1499747<1>? <1> https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1499747 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1499133 Title: unity-panel-service crashed with SIGSEGV in gtk_menu_tracker_remove_items() Status in Unity: Incomplete Status in unity package in Ubuntu: Incomplete Bug description: Crash in panel using Eclipse (not sure if Eclipse trigger this bug) ProblemType: Crash DistroRelease: Ubuntu 15.10 Package: unity-services 7.3.2+15.10.20150921-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-22.29-generic 3.16.4 Uname: Linux 3.16.0-22-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.18.1-0ubuntu1 Architecture: amd64 BootLog: CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Thu Sep 24 03:39:33 2015 DistUpgraded: Fresh install DistroCodename: wily DistroVariant: ubuntu DkmsStatus: virtualbox, 5.0.4: added ExecutablePath: /usr/lib/unity/unity-panel-service GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Madison [Mobility Radeon HD 5650/5750 / 6530M/6550M] [1002:68c1] (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Mobility Radeon HD 5650 [1025:042f] InstallationDate: Installed on 2014-05-08 (503 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: Acer Aspire 5943G ProcCmdline: /usr/lib/unity/unity-panel-service ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-22-generic root=UUID=e9be64c9-5b7e-438a-ac82-6b89bf946a86 ro quiet splash vt.handoff=7 SegvAnalysis: Segfault happened at: 0x7f24b28143ec:mov(%rdi),%rbx PC (0x7f24b28143ec) ok source "(%rdi)" (0x) not located in a known VMA region (needed readable region)! destination "%rbx" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: unity StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6 ffi_call () from /usr/lib/x86_64-linux-gnu/libffi.so.6 g_cclosure_marshal_generic () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: unity-panel-service crashed with SIGSEGV in ffi_call_unix64() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo dmi.bios.date: 10/21/2010 dmi.bios.vendor: Acer dmi.bios.version: V1.15 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Aspire 5943G dmi.board.vendor: Acer dmi.board.version: V1.15 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.15 dmi.modalias: dmi:bvnAcer:bvrV1.15:bd10/21/2010:svnAcer:pnAspire5943G:pvrV1.15:rvnAcer:rnAspire5943G:rvrV1.15:cvnAcer:ct10:cvrV1.15: dmi.product.name: Aspire 5943G dmi.product.version: V1.15 dmi.sys.vendor: Acer version.compiz: compiz 1:0.9.12.2+15.10.20150908-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.64-1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.0-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.0-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0+git20150819-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20150808-0ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu3 xserver.bootTime: Thu Sep 24 02:58:04 2015 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.17.2-1ubuntu7 xserver.video_driver: radeon To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1499133/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1499747] Re: gedit crashed with SIGABRT in g_assertion_message()
Seems to be fixed here too. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1499747 Title: gedit crashed with SIGABRT in g_assertion_message() Status in gedit package in Ubuntu: Invalid Status in glib2.0 package in Ubuntu: Fix Released Status in unity-gtk-module package in Ubuntu: Invalid Bug description: Gedit crashed just after opening a (small) text file from nautilus with "Open with". ProblemType: Crash DistroRelease: Ubuntu 15.10 Package: gedit 3.10.4-0ubuntu13 ProcVersionSignature: Ubuntu 4.2.0-11.13-lowlatency 4.2.1 Uname: Linux 4.2.0-11-lowlatency x86_64 ApportVersion: 2.18.1-0ubuntu1 Architecture: amd64 CrashCounter: 1 CurrentDesktop: Unity Date: Fri Sep 25 16:05:28 2015 ExecutablePath: /usr/bin/gedit InstallationDate: Installed on 2014-12-13 (285 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) ProcCmdline: gedit /home/username/Bureau/Export_cabmnt_329340483152739798.csv Signal: 6 SourcePackage: gedit StacktraceTop: g_assertion_message () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6 ffi_call () from /usr/lib/x86_64-linux-gnu/libffi.so.6 Title: gedit crashed with SIGABRT in g_assertion_message() UpgradeStatus: Upgraded to wily on 2015-09-21 (4 days ago) UserGroups: adm audio cdrom dialout dip libvirtd lpadmin lxd plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1499747/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1499747] Re: gedit crashed with SIGABRT in g_assertion_message()
I can also reproduce this as described in comment 14, and get it whenever I start Pidgin and log in to my Jabber account: $ pidgin ** GLib-GIO:ERROR:/build/glib2.0-pRoDo9/glib2.0-2.46.0/./gio/gmenuexporter.c:256:g_menu_exporter_menu_items_changed: assertion failed: (position + removed <= g_sequence_get_length (menu->item_links)) Aborted (core dumped) $ gedit ** GLib-GIO:ERROR:/build/glib2.0-pRoDo9/glib2.0-2.46.0/./gio/gmenuexporter.c:256:g_menu_exporter_menu_items_changed: assertion failed: (position + removed <= g_sequence_get_length (menu->item_links)) Aborted (core dumped) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1499747 Title: gedit crashed with SIGABRT in g_assertion_message() Status in gedit package in Ubuntu: Invalid Status in glib2.0 package in Ubuntu: Invalid Status in unity-gtk-module package in Ubuntu: Triaged Bug description: Gedit crashed just after opening a (small) text file from nautilus with "Open with". ProblemType: Crash DistroRelease: Ubuntu 15.10 Package: gedit 3.10.4-0ubuntu13 ProcVersionSignature: Ubuntu 4.2.0-11.13-lowlatency 4.2.1 Uname: Linux 4.2.0-11-lowlatency x86_64 ApportVersion: 2.18.1-0ubuntu1 Architecture: amd64 CrashCounter: 1 CurrentDesktop: Unity Date: Fri Sep 25 16:05:28 2015 ExecutablePath: /usr/bin/gedit InstallationDate: Installed on 2014-12-13 (285 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) ProcCmdline: gedit /home/username/Bureau/Export_cabmnt_329340483152739798.csv Signal: 6 SourcePackage: gedit StacktraceTop: g_assertion_message () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6 ffi_call () from /usr/lib/x86_64-linux-gnu/libffi.so.6 Title: gedit crashed with SIGABRT in g_assertion_message() UpgradeStatus: Upgraded to wily on 2015-09-21 (4 days ago) UserGroups: adm audio cdrom dialout dip libvirtd lpadmin lxd plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1499747/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1443853] Re: Ubuntu 14.10 ISO live boot in Oracle VirtualBox ends up with a corrupted display
Please see comment 1[1] and 14[2] on that ticket. We believe that this is a problem in setfont, not in VirtualBox (or Ubuntu for that matter). [1] https://www.virtualbox.org/ticket/13615#comment:1 [2] https://www.virtualbox.org/ticket/13615#comment:14 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to console-setup in Ubuntu. https://bugs.launchpad.net/bugs/1443853 Title: Ubuntu 14.10 ISO live boot in Oracle VirtualBox ends up with a corrupted display Status in Virtualbox: New Status in console-setup package in Ubuntu: New Status in virtualbox package in Ubuntu: New Bug description: (Content copied from "Ubuntu 14.10 ISO live boot ends up with a corrupted display" #13615 VirtualBox bug ticket, by piotrjurkiewicz) Booting up live session of Ubuntu MATE 14.10 and Ubuntu Gnome 14.10 from ISO ends up with a corrupted screen. See the screenshot: https://launchpadlibrarian.net/186864347/ubu.png Switching back and forth to the tty7 (ctrl+alt+F1 and then alt+F7) fixes the display. I think that this might be a problem with resolution setting: ``` 00:00:31.226379 Display::handleDisplayResize(): uScreenId = 0, pvVRAM= w=1152 h=400 bpp=0 cbLine=0x0, flags=0x1 00:00:31.226399 UIFrameBuffer::RequestResize: Screen=0, Format=0, BitsPerPixel=0, BytesPerLine=0, Size=1152x400, Sending to async-handler.. 00:00:31.226457 UIFrameBufferQImage::resizeEvent: Format=0, BitsPerPixel=0, BytesPerLine=0, Size=1152x400 00:00:31.226467 UIFrameBufferQImage::resizeEvent: Resizing to FALLBACK buffer due to format is invalid.. ``` After switching back and forth to the tty7 (what fixes the display) the log says: ``` 00:00:31.226379 Display::handleDisplayResize(): uScreenId = 0, pvVRAM= w=1152 h=400 bpp=0 cbLine=0x0, flags=0x1 00:00:31.226399 UIFrameBuffer::RequestResize: Screen=0, Format=0, BitsPerPixel=0, BytesPerLine=0, Size=1152x400, Sending to async-handler.. 00:00:31.226457 UIFrameBufferQImage::resizeEvent: Format=0, BitsPerPixel=0, BytesPerLine=0, Size=1152x400 00:00:31.226467 UIFrameBufferQImage::resizeEvent: Resizing to FALLBACK buffer due to format is invalid.. 00:01:37.584616 Display::handleDisplayResize(): uScreenId = 0, pvVRAM= w=720 h=400 bpp=0 cbLine=0x0, flags=0x1 00:01:37.584634 UIFrameBuffer::RequestResize: Screen=0, Format=0, BitsPerPixel=0, BytesPerLine=0, Size=720x400, Sending to async-handler.. 00:01:37.584680 UIFrameBufferQImage::resizeEvent: Format=0, BitsPerPixel=0, BytesPerLine=0, Size=720x400 00:01:37.584692 UIFrameBufferQImage::resizeEvent: Resizing to FALLBACK buffer due to format is invalid.. 00:01:39.055475 Display::handleDisplayResize(): uScreenId = 0, pvVRAM=0a7f w=1024 h=768 bpp=32 cbLine=0x1000, flags=0x1 00:01:39.055495 UIFrameBuffer::RequestResize: Screen=0, Format=843204434, BitsPerPixel=32, BytesPerLine=4096, Size=1024x768, Sending to async-handler.. 00:01:39.09 UIFrameBufferQImage::resizeEvent: Format=843204434, BitsPerPixel=32, BytesPerLine=4096, Size=1024x768 00:01:39.055568 UIFrameBufferQImage::resizeEvent: Resizing to directly use VGA device content.. ``` I have tested 4.3.18 and also the testbuild 4.3.19 r96825, it happens on both of them. You can download the ISO images of these two systems here: https://ubuntu-mate.r.worldssl.net/download/ubuntu-mate-14.10 -desktop-amd64.iso http://cdimage.ubuntu.com/ubuntu-gnome/releases/14.10/release/ubuntu- gnome-14.10-desktop-amd64.iso To manage notifications about this bug go to: https://bugs.launchpad.net/virtualbox/+bug/1443853/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1456789] Re: restarting services hangs on systemd-tty-ask-password-agent
Ran into something similar just now. A bit of internet searching suggested<1><2> that it was due to systemd's internal state getting out of sync, and indeed running "systemctl daemon-reload" made it go away. <1> https://github.com/NixOS/nixpkgs/issues/2584 <2> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=774153 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1456789 Title: restarting services hangs on systemd-tty-ask-password-agent Status in systemd package in Ubuntu: Confirmed Status in systemd package in Debian: Incomplete Bug description: I have a script run as root from cron that tweaks smb.conf and restarts smbd and winbind. Problem is, starting today after working perfectly up till yesterday, this script now hangs on Ubuntu 15.04. When run from cron, the process tree looks like this: service smbd restart \_ systemctl restart smbd.service \_ /bin/systemd-tty-ask-password-agent --watch \_ /usr/bin/pkttyagent --notify-fd 5 --fallback Run from a shell via sudo, same thing except the process tree (obviously) includes the sudo command. It times out after 5 minutes, causing the script to fail. If I manually kill the processes, it fails faster. The simplest possible scripts that reproduce this, run as root or through cron or via sudo, are: #!/bin/sh service smbd restart #!/bin/sh systemctl restart smbd.service Using 'service', this works perfectly on Ubuntu 14.04 and 14.10, and until this morning worked perfectly on 15.04 as well. 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu Ubuntu 15.04 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center systemd 219-7ubuntu5 samba 2:4.1.13+dfsg-4ubuntu3 3) What you expected to happen Services to restart 4) What happened instead Services didn't restart, 'systemctl' hung To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1456789/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1456789] Re: restarting services hangs on systemd-tty-ask-password-agent
Sorry, "systemctl daemon-reexec". -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1456789 Title: restarting services hangs on systemd-tty-ask-password-agent Status in systemd package in Ubuntu: Confirmed Status in systemd package in Debian: Incomplete Bug description: I have a script run as root from cron that tweaks smb.conf and restarts smbd and winbind. Problem is, starting today after working perfectly up till yesterday, this script now hangs on Ubuntu 15.04. When run from cron, the process tree looks like this: service smbd restart \_ systemctl restart smbd.service \_ /bin/systemd-tty-ask-password-agent --watch \_ /usr/bin/pkttyagent --notify-fd 5 --fallback Run from a shell via sudo, same thing except the process tree (obviously) includes the sudo command. It times out after 5 minutes, causing the script to fail. If I manually kill the processes, it fails faster. The simplest possible scripts that reproduce this, run as root or through cron or via sudo, are: #!/bin/sh service smbd restart #!/bin/sh systemctl restart smbd.service Using 'service', this works perfectly on Ubuntu 14.04 and 14.10, and until this morning worked perfectly on 15.04 as well. 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu Ubuntu 15.04 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center systemd 219-7ubuntu5 samba 2:4.1.13+dfsg-4ubuntu3 3) What you expected to happen Services to restart 4) What happened instead Services didn't restart, 'systemctl' hung To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1456789/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1604009] Re: Empty menus in global app-menu in VirtualBox second window
Just did a quick test after upgrading to 16.10. I (still) see double menus (both local and global) in a single window machine. Should I remove appmenu-qt* and try again? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libdbusmenu-qt in Ubuntu. https://bugs.launchpad.net/bugs/1604009 Title: Empty menus in global app-menu in VirtualBox second window Status in libdbusmenu-qt package in Ubuntu: New Bug description: Reporting this following this IRC discussion: https://irclogs.ubuntu.com/2016/07/15/%23ubuntu-devel.html#t14:00 The basic summary: when I run a two-screen/two-window virtual machine with VirtualBox under Ubuntu 16.04 with Unity and the global app-menu, the menus are empty when the second screen window has the input focus. During start-up I get a number (55) of these messages on the console: Qt WARNING: void DBusMenuExporterPrivate::fillLayoutItem(DBusMenuLayoutItem*, QMenu*, int, int, const QStringList&): No id for action and a number (7) of these: Qt WARNING: uint DBusMenuExporterDBus::GetLayout(int, int, const QStringList&, DBusMenuLayoutItem&): Condition failed: menu Then another 55 of the first and two of the second. Looking at the interesting parts of the VirtualBox source code, I see that the menu items for the first window (menu displayed correctly) and the second (not displayed) share the same QAction objects. A very quick guess is that this might be triggering the condition in DBusMenuExporterPrivate::addMenu(). ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: libdbusmenu-qt5 0.9.3+16.04.20160218-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10 Uname: Linux 4.4.0-24-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: Unity Date: Mon Jul 18 15:44:00 2016 Dependencies: gcc-5-base 5.4.0-6ubuntu1~16.04.1 gcc-6-base 6.0.1-0ubuntu1 libc6 2.23-0ubuntu3 libgcc1 1:6.0.1-0ubuntu1 libstdc++6 5.4.0-6ubuntu1~16.04.1 InstallationDate: Installed on 2016-05-31 (48 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: libdbusmenu-qt UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdbusmenu-qt/+bug/1604009/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1604009] Re: Empty menus in global app-menu in VirtualBox second window
Removed appmenu-qt5 and checked that I am on 5.6.1+dfsg-3ubuntu3~3, but still no joy. I would not rule out user error though (and I have not yet rebooted since upgrading from 16.04, so there might be something stale in memory). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libdbusmenu-qt in Ubuntu. https://bugs.launchpad.net/bugs/1604009 Title: Empty menus in global app-menu in VirtualBox second window Status in libdbusmenu-qt package in Ubuntu: New Bug description: Reporting this following this IRC discussion: https://irclogs.ubuntu.com/2016/07/15/%23ubuntu-devel.html#t14:00 The basic summary: when I run a two-screen/two-window virtual machine with VirtualBox under Ubuntu 16.04 with Unity and the global app-menu, the menus are empty when the second screen window has the input focus. During start-up I get a number (55) of these messages on the console: Qt WARNING: void DBusMenuExporterPrivate::fillLayoutItem(DBusMenuLayoutItem*, QMenu*, int, int, const QStringList&): No id for action and a number (7) of these: Qt WARNING: uint DBusMenuExporterDBus::GetLayout(int, int, const QStringList&, DBusMenuLayoutItem&): Condition failed: menu Then another 55 of the first and two of the second. Looking at the interesting parts of the VirtualBox source code, I see that the menu items for the first window (menu displayed correctly) and the second (not displayed) share the same QAction objects. A very quick guess is that this might be triggering the condition in DBusMenuExporterPrivate::addMenu(). ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: libdbusmenu-qt5 0.9.3+16.04.20160218-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10 Uname: Linux 4.4.0-24-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: Unity Date: Mon Jul 18 15:44:00 2016 Dependencies: gcc-5-base 5.4.0-6ubuntu1~16.04.1 gcc-6-base 6.0.1-0ubuntu1 libc6 2.23-0ubuntu3 libgcc1 1:6.0.1-0ubuntu1 libstdc++6 5.4.0-6ubuntu1~16.04.1 InstallationDate: Installed on 2016-05-31 (48 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: libdbusmenu-qt UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdbusmenu-qt/+bug/1604009/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1604009] Re: Empty menus in global app-menu in VirtualBox second window
I can confirm though that the global menu now works for the second window. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libdbusmenu-qt in Ubuntu. https://bugs.launchpad.net/bugs/1604009 Title: Empty menus in global app-menu in VirtualBox second window Status in libdbusmenu-qt package in Ubuntu: New Bug description: Reporting this following this IRC discussion: https://irclogs.ubuntu.com/2016/07/15/%23ubuntu-devel.html#t14:00 The basic summary: when I run a two-screen/two-window virtual machine with VirtualBox under Ubuntu 16.04 with Unity and the global app-menu, the menus are empty when the second screen window has the input focus. During start-up I get a number (55) of these messages on the console: Qt WARNING: void DBusMenuExporterPrivate::fillLayoutItem(DBusMenuLayoutItem*, QMenu*, int, int, const QStringList&): No id for action and a number (7) of these: Qt WARNING: uint DBusMenuExporterDBus::GetLayout(int, int, const QStringList&, DBusMenuLayoutItem&): Condition failed: menu Then another 55 of the first and two of the second. Looking at the interesting parts of the VirtualBox source code, I see that the menu items for the first window (menu displayed correctly) and the second (not displayed) share the same QAction objects. A very quick guess is that this might be triggering the condition in DBusMenuExporterPrivate::addMenu(). ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: libdbusmenu-qt5 0.9.3+16.04.20160218-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10 Uname: Linux 4.4.0-24-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: Unity Date: Mon Jul 18 15:44:00 2016 Dependencies: gcc-5-base 5.4.0-6ubuntu1~16.04.1 gcc-6-base 6.0.1-0ubuntu1 libc6 2.23-0ubuntu3 libgcc1 1:6.0.1-0ubuntu1 libstdc++6 5.4.0-6ubuntu1~16.04.1 InstallationDate: Installed on 2016-05-31 (48 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: libdbusmenu-qt UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdbusmenu-qt/+bug/1604009/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [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 Touch seeded packages, which is subscribed to libdbusmenu-qt in Ubuntu. https://bugs.launchpad.net/bugs/1604009 Title: Empty menus in global app-menu in VirtualBox second window Status in libdbusmenu-qt package in Ubuntu: New Bug description: Reporting this following this IRC discussion: https://irclogs.ubuntu.com/2016/07/15/%23ubuntu-devel.html#t14:00 The basic summary: when I run a two-screen/two-window virtual machine with VirtualBox under Ubuntu 16.04 with Unity and the global app-menu, the menus are empty when the second screen window has the input focus. During start-up I get a number (55) of these messages on the console: Qt WARNING: void DBusMenuExporterPrivate::fillLayoutItem(DBusMenuLayoutItem*, QMenu*, int, int, const QStringList&): No id for action and a number (7) of these: Qt WARNING: uint DBusMenuExporterDBus::GetLayout(int, int, const QStringList&, DBusMenuLayoutItem&): Condition failed: menu Then another 55 of the first and two of the second. Looking at the interesting parts of the VirtualBox source code, I see that the menu items for the first window (menu displayed correctly) and the second (not displayed) share the same QAction objects. A very quick guess is that this might be triggering the condition in DBusMenuExporterPrivate::addMenu(). ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: libdbusmenu-qt5 0.9.3+16.04.20160218-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10 Uname: Linux 4.4.0-24-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: Unity Date: Mon Jul 18 15:44:00 2016 Dependencies: gcc-5-base 5.4.0-6ubuntu1~16.04.1 gcc-6-base 6.0.1-0ubuntu1 libc6 2.23-0ubuntu3 libgcc1 1:6.0.1-0ubuntu1 libstdc++6 5.4.0-6ubuntu1~16.04.1 InstallationDate: Installed on 2016-05-31 (48 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: libdbusmenu-qt UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdbusmenu-qt/+bug/1604009/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [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 Touch seeded packages, which is subscribed to libdbusmenu-qt in Ubuntu. https://bugs.launchpad.net/bugs/1604009 Title: Empty menus in global app-menu in VirtualBox second window Status in libdbusmenu-qt package in Ubuntu: New Bug description: Reporting this following this IRC discussion: https://irclogs.ubuntu.com/2016/07/15/%23ubuntu-devel.html#t14:00 The basic summary: when I run a two-screen/two-window virtual machine with VirtualBox under Ubuntu 16.04 with Unity and the global app-menu, the menus are empty when the second screen window has the input focus. During start-up I get a number (55) of these messages on the console: Qt WARNING: void DBusMenuExporterPrivate::fillLayoutItem(DBusMenuLayoutItem*, QMenu*, int, int, const QStringList&): No id for action and a number (7) of these: Qt WARNING: uint DBusMenuExporterDBus::GetLayout(int, int, const QStringList&, DBusMenuLayoutItem&): Condition failed: menu Then another 55 of the first and two of the second. Looking at the interesting parts of the VirtualBox source code, I see that the menu items for the first window (menu displayed correctly) and the second (not displayed) share the same QAction objects. A very quick guess is that this might be triggering the condition in DBusMenuExporterPrivate::addMenu(). ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: libdbusmenu-qt5 0.9.3+16.04.20160218-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10 Uname: Linux 4.4.0-24-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: Unity Date: Mon Jul 18 15:44:00 2016 Dependencies: gcc-5-base 5.4.0-6ubuntu1~16.04.1 gcc-6-base 6.0.1-0ubuntu1 libc6 2.23-0ubuntu3 libgcc1 1:6.0.1-0ubuntu1 libstdc++6 5.4.0-6ubuntu1~16.04.1 InstallationDate: Installed on 2016-05-31 (48 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: libdbusmenu-qt UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdbusmenu-qt/+bug/1604009/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [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 Touch seeded packages, which is subscribed to libdbusmenu-qt in Ubuntu. https://bugs.launchpad.net/bugs/1604009 Title: Empty menus in global app-menu in VirtualBox second window Status in libdbusmenu-qt package in Ubuntu: New Bug description: Reporting this following this IRC discussion: https://irclogs.ubuntu.com/2016/07/15/%23ubuntu-devel.html#t14:00 The basic summary: when I run a two-screen/two-window virtual machine with VirtualBox under Ubuntu 16.04 with Unity and the global app-menu, the menus are empty when the second screen window has the input focus. During start-up I get a number (55) of these messages on the console: Qt WARNING: void DBusMenuExporterPrivate::fillLayoutItem(DBusMenuLayoutItem*, QMenu*, int, int, const QStringList&): No id for action and a number (7) of these: Qt WARNING: uint DBusMenuExporterDBus::GetLayout(int, int, const QStringList&, DBusMenuLayoutItem&): Condition failed: menu Then another 55 of the first and two of the second. Looking at the interesting parts of the VirtualBox source code, I see that the menu items for the first window (menu displayed correctly) and the second (not displayed) share the same QAction objects. A very quick guess is that this might be triggering the condition in DBusMenuExporterPrivate::addMenu(). ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: libdbusmenu-qt5 0.9.3+16.04.20160218-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10 Uname: Linux 4.4.0-24-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: Unity Date: Mon Jul 18 15:44:00 2016 Dependencies: gcc-5-base 5.4.0-6ubuntu1~16.04.1 gcc-6-base 6.0.1-0ubuntu1 libc6 2.23-0ubuntu3 libgcc1 1:6.0.1-0ubuntu1 libstdc++6 5.4.0-6ubuntu1~16.04.1 InstallationDate: Installed on 2016-05-31 (48 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: libdbusmenu-qt UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdbusmenu-qt/+bug/1604009/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [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 Touch seeded packages, which is subscribed to libdbusmenu-qt in Ubuntu. https://bugs.launchpad.net/bugs/1604009 Title: Empty menus in global app-menu in VirtualBox second window Status in libdbusmenu-qt package in Ubuntu: New Bug description: Reporting this following this IRC discussion: https://irclogs.ubuntu.com/2016/07/15/%23ubuntu-devel.html#t14:00 The basic summary: when I run a two-screen/two-window virtual machine with VirtualBox under Ubuntu 16.04 with Unity and the global app-menu, the menus are empty when the second screen window has the input focus. During start-up I get a number (55) of these messages on the console: Qt WARNING: void DBusMenuExporterPrivate::fillLayoutItem(DBusMenuLayoutItem*, QMenu*, int, int, const QStringList&): No id for action and a number (7) of these: Qt WARNING: uint DBusMenuExporterDBus::GetLayout(int, int, const QStringList&, DBusMenuLayoutItem&): Condition failed: menu Then another 55 of the first and two of the second. Looking at the interesting parts of the VirtualBox source code, I see that the menu items for the first window (menu displayed correctly) and the second (not displayed) share the same QAction objects. A very quick guess is that this might be triggering the condition in DBusMenuExporterPrivate::addMenu(). ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: libdbusmenu-qt5 0.9.3+16.04.20160218-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10 Uname: Linux 4.4.0-24-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: Unity Date: Mon Jul 18 15:44:00 2016 Dependencies: gcc-5-base 5.4.0-6ubuntu1~16.04.1 gcc-6-base 6.0.1-0ubuntu1 libc6 2.23-0ubuntu3 libgcc1 1:6.0.1-0ubuntu1 libstdc++6 5.4.0-6ubuntu1~16.04.1 InstallationDate: Installed on 2016-05-31 (48 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: libdbusmenu-qt UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdbusmenu-qt/+bug/1604009/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1599775] Re: "low-graphics mode" in VirtualBox guest, but X server running
** Attachment added: "The log file from yesterday." https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1599775/+attachment/4696780/+files/lightdm.log.1 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1599775 Title: "low-graphics mode" in VirtualBox guest, but X server running Status in lightdm package in Ubuntu: New Bug description: I sometimes get the "low-graphics mode" message when starting an Ubuntu 16.04 virtual machine inside of VirtualBox (current development code trunk, somewhere past version 5.1 beta 3 and a debug build). When I switch to VT-7 I find the X server running without any visible issues (I am the upstream developer of the guest graphics drivers, so I have a reasonable but not infallible understanding of the X server). The virtual machine has Guest Additions installed, same vintage and also a debug build. Two screens are enabled as is 3D acceleration. The host system is also Ubuntu 16.04. I am still trying to work out what triggers the message, but in my last attempts a cold boot failed to produce it, while a clean reboot did, but only when the host system was not under load (under load as in building VirtualBox). Searching the lightdm log files led me to the message "CRITICAL **: session_get_login1_session_id: assertion 'session != NULL' failed", which in turn led me to this similar-looking Debian bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=814760 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: lightdm 1.18.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13 Uname: Linux 4.4.0-28-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Thu Jul 7 10:49:27 2016 InstallationDate: Installed on 2016-06-08 (28 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1599775/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1599775] [NEW] "low-graphics mode" in VirtualBox guest, but X server running
Public bug reported: I sometimes get the "low-graphics mode" message when starting an Ubuntu 16.04 virtual machine inside of VirtualBox (current development code trunk, somewhere past version 5.1 beta 3 and a debug build). When I switch to VT-7 I find the X server running without any visible issues (I am the upstream developer of the guest graphics drivers, so I have a reasonable but not infallible understanding of the X server). The virtual machine has Guest Additions installed, same vintage and also a debug build. Two screens are enabled as is 3D acceleration. The host system is also Ubuntu 16.04. I am still trying to work out what triggers the message, but in my last attempts a cold boot failed to produce it, while a clean reboot did, but only when the host system was not under load (under load as in building VirtualBox). Searching the lightdm log files led me to the message "CRITICAL **: session_get_login1_session_id: assertion 'session != NULL' failed", which in turn led me to this similar-looking Debian bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=814760 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: lightdm 1.18.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13 Uname: Linux 4.4.0-28-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Thu Jul 7 10:49:27 2016 InstallationDate: Installed on 2016-06-08 (28 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: lightdm (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1599775 Title: "low-graphics mode" in VirtualBox guest, but X server running Status in lightdm package in Ubuntu: New Bug description: I sometimes get the "low-graphics mode" message when starting an Ubuntu 16.04 virtual machine inside of VirtualBox (current development code trunk, somewhere past version 5.1 beta 3 and a debug build). When I switch to VT-7 I find the X server running without any visible issues (I am the upstream developer of the guest graphics drivers, so I have a reasonable but not infallible understanding of the X server). The virtual machine has Guest Additions installed, same vintage and also a debug build. Two screens are enabled as is 3D acceleration. The host system is also Ubuntu 16.04. I am still trying to work out what triggers the message, but in my last attempts a cold boot failed to produce it, while a clean reboot did, but only when the host system was not under load (under load as in building VirtualBox). Searching the lightdm log files led me to the message "CRITICAL **: session_get_login1_session_id: assertion 'session != NULL' failed", which in turn led me to this similar-looking Debian bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=814760 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: lightdm 1.18.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13 Uname: Linux 4.4.0-28-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Thu Jul 7 10:49:27 2016 InstallationDate: Installed on 2016-06-08 (28 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1599775/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1599775] Re: "low-graphics mode" in VirtualBox guest, but X server running
Just checked, I do not have that message in the current log file, attached the file from yesterday containing the message. I asked about this on #ubuntu-devel, here are the relevant logs: (17:09:06) michael-vb: Afternoon. Not sure if this is the right place to ask, but someone will probably know what is. (17:09:06) michael-vb: I have the following problem with my VirtualBox Ubuntu 16.04 guest with development Guest Additions installed: when I start the guest I get the message "The system is running in low-graphics mode" (on VT 2) even though the X server is running fine (on VT 7). (17:09:06) michael-vb: I would very much like to know exactly what logic triggers that message so I can work out why I am triggering it and change whatever is responsible (I am the developer of the VirtualBox guest driver and Additions installer). (18:04:34) michael-vb: Interesting - I just booted the guest system twice with a loaded host (rebuilding VirtualBox) and did not get the "low-graphics mode" message. (18:27:01) michael-vb: CRITICAL: session_get_login1_session_id: assertion 'session != NULL' failed in the lightdm log file. (18:31:13) michael-vb: https://bugs.debian.org/cgi- bin/bugreport.cgi?bug=814760 (09:57:21) sladen: michael-vb: http://askubuntu.com/questions/141606/how-to-fix-the-system-is-running-in-low-graphics-mode-error (09:57:35) michael-vb: Found that already. (09:57:50) michael-vb: I am wanting to understand this as a developer, not as a user. (09:59:07) michael-vb: sladen: it was following from that askubuntu question that I found the system log entry. (09:59:34) michael-vb: The session clearly gets started just after lightdm checks whether it is running. (10:01:04) michael-vb: As I said, this does not happen under high load. I suppose the question is, who would understand this stuff well enough to tell me how I can avoid triggering it. (10:01:15) michael-vb: Or what causes the session to start too late, or lightdm too early. (10:03:00) michael-vb: I assume that some dependency is not specified well enough somewhere. (10:03:31) sladen: michael-vb: apt-get source lightdm && grep -r "Error message" is probably the most effective way of identifing the logic causing the error (if it is coming from lightdm) (10:03:31) michael-vb: But it is annoying, because if it hits users they will blame us first, not you! (10:04:15) sladen: michael-vb: I'm not too familiar with the inner workings of lightdm; the developer was Robert Ancell in the DX team (10:04:57) sladen: michael-vb: if it's happening so of the time (seemingly randomly), then there's probably a race condition (10:06:33) michael-vb: I'm sort of suspecting that it is related to the change to systemd which upset some expectation in lightdm. (10:08:13) sladen: willcooke: if you're around later, could you get in contact with michael-vb (upstream developer of VirtualBox guest driver), about debugging and resolving the "The system is running in low-graphics mode" message. https://irclogs.ubuntu.com/2016/07/07/%23ubuntu-devel.html#t07:52 onwards (10:08:50) michael-vb: willcooke: and michael dot thayer at oracle if I am not on IRC at that time. (10:08:56) michael-vb: sladen, willcooke: thanks. (10:10:59) willcooke: Trevinho, is this something you can help with? ^ (10:11:09) willcooke: It looks like it's a problem with X rather than Unity though (10:11:13) willcooke: "problem" (10:11:22) willcooke: maybe tjaalton knows what triggers it? ^ (10:13:46) talatb [~talatb@137.158.22.10] entered the room. (10:14:23) tjaalton: I don't, if lightdm is randomly not starting on debian (which doesn't have "failsafe-x") (10:15:20) tjaalton: sounds like a lightdm bug to me (10:16:59) willcooke: oki (10:17:04) willcooke: thanks tjaalton (10:30:07) willcooke: michael-vb, Hmm, I can't see anything obvious here. Please log a bug in Ubuntu against lightdm if there isn't already one, and we take take a look. (10:30:54) michael-vb: willcooke: to me it sounds like an init dependency problem. (10:31:18) sladen: michael-vb: can we get as much of the (known good) information into a Launchpad bug report (10:31:34) michael-vb: If I understood all this GNOME-systemd-login stuff better... (10:31:41) michael-vb: sladen: sounds reasonable. (10:31:44) sladen: michael-vb: and then get that linked to/from the debbugs and Askubuntu pages (10:33:25) michael-vb: Oh how nice, for reasons unknown I can no longer trigger it. (10:33:34) willcooke: \o/ (10:33:47) willcooke: fixed! (10:34:00) willcooke: certainly smells like a race then (10:34:23) michael-vb: I think that is clear enough from the Debian bug. (10:34:47) michael-vb: I think that someone from the systemd camp would be best placed to solve it. (10:36:07) michael-vb: But before I open a bug report I will at least try to track down the error in the lightdm sources. (10:39:45) sladen: yes, it would be good to point in the bug report exactly where the origin of the assert is coming from, but if it can't
[Touch-packages] [Bug 1599775] Re: "low-graphics mode" in VirtualBox guest, but X server running
Actually, perhaps I misunderstand the lightdm log rotation and the .1 logfile does contain the relevant log. I assume the lightdm developers will know. My uneducated guess is that there is some sort of race here between lightdm and logind which needs better dependency specification. And I just checked that I do not always see this on a clean reboot either. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1599775 Title: "low-graphics mode" in VirtualBox guest, but X server running Status in lightdm package in Ubuntu: New Bug description: I sometimes get the "low-graphics mode" message when starting an Ubuntu 16.04 virtual machine inside of VirtualBox (current development code trunk, somewhere past version 5.1 beta 3 and a debug build). When I switch to VT-7 I find the X server running without any visible issues (I am the upstream developer of the guest graphics drivers, so I have a reasonable but not infallible understanding of the X server). The virtual machine has Guest Additions installed, same vintage and also a debug build. Two screens are enabled as is 3D acceleration. The host system is also Ubuntu 16.04. I am still trying to work out what triggers the message, but in my last attempts a cold boot failed to produce it, while a clean reboot did, but only when the host system was not under load (under load as in building VirtualBox). Searching the lightdm log files led me to the message "CRITICAL **: session_get_login1_session_id: assertion 'session != NULL' failed", which in turn led me to this similar-looking Debian bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=814760 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: lightdm 1.18.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13 Uname: Linux 4.4.0-28-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Thu Jul 7 10:49:27 2016 InstallationDate: Installed on 2016-06-08 (28 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1599775/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1599775] Re: "low-graphics mode" in VirtualBox guest, but X server running
I was able to reproduce this with the lightdm deb file from that package installed. I did not install the other deb files built from the package. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1599775 Title: "low-graphics mode" in VirtualBox guest, but X server running Status in lightdm package in Ubuntu: New Bug description: I sometimes get the "low-graphics mode" message when starting an Ubuntu 16.04 virtual machine inside of VirtualBox (current development code trunk, somewhere past version 5.1 beta 3 and a debug build). When I switch to VT-7 I find the X server running without any visible issues (I am the upstream developer of the guest graphics drivers, so I have a reasonable but not infallible understanding of the X server). The virtual machine has Guest Additions installed, same vintage and also a debug build. Two screens are enabled as is 3D acceleration. The host system is also Ubuntu 16.04. I am still trying to work out what triggers the message, but in my last attempts a cold boot failed to produce it, while a clean reboot did, but only when the host system was not under load (under load as in building VirtualBox). Searching the lightdm log files led me to the message "CRITICAL **: session_get_login1_session_id: assertion 'session != NULL' failed", which in turn led me to this similar-looking Debian bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=814760 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: lightdm 1.18.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13 Uname: Linux 4.4.0-28-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Thu Jul 7 10:49:27 2016 InstallationDate: Installed on 2016-06-08 (28 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) IRC discussion at: https://irclogs.ubuntu.com/2016/07/07/%23ubuntu-devel.html#t07:52 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1599775/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1599775] Re: "low-graphics mode" in VirtualBox guest, but X server running
My apologies, I missed that one, so this is probably my bug! I will fix that and then get back to you. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1599775 Title: "low-graphics mode" in VirtualBox guest, but X server running Status in lightdm package in Ubuntu: New Bug description: I sometimes get the "low-graphics mode" message when starting an Ubuntu 16.04 virtual machine inside of VirtualBox (current development code trunk, somewhere past version 5.1 beta 3 and a debug build). When I switch to VT-7 I find the X server running without any visible issues (I am the upstream developer of the guest graphics drivers, so I have a reasonable but not infallible understanding of the X server). The virtual machine has Guest Additions installed, same vintage and also a debug build. Two screens are enabled as is 3D acceleration. The host system is also Ubuntu 16.04. I am still trying to work out what triggers the message, but in my last attempts a cold boot failed to produce it, while a clean reboot did, but only when the host system was not under load (under load as in building VirtualBox). Searching the lightdm log files led me to the message "CRITICAL **: session_get_login1_session_id: assertion 'session != NULL' failed", which in turn led me to this similar-looking Debian bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=814760 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: lightdm 1.18.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13 Uname: Linux 4.4.0-28-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Thu Jul 7 10:49:27 2016 InstallationDate: Installed on 2016-06-08 (28 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) IRC discussion at: https://irclogs.ubuntu.com/2016/07/07/%23ubuntu-devel.html#t07:52 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1599775/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1640112] [NEW] Irregular USB network tethering failures
Public bug reported: Reporting this against network manager for want of better information. Sorry for the imprecise report - I will be glad to observe and update. Since upgrading to 16.10 I have had problems with my USB "ethernet" network connection provided by a tethered Android 2.3 device. Initial connection works well, but after a while Ubuntu looses connection, indicated by the nm-applet icon switching to "wifi connecting". Ubuntu seems unable to obtain an IP address. Neither rebooting the laptop nor restarting the phone help, but after a while the problem goes away on its own. In the meantime I am able to tether using the phone's wireless hotspot functionality. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: network-manager 1.2.4-0ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0 Uname: Linux 4.8.0-26-generic x86_64 ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Tue Nov 8 11:00:59 2016 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2016-05-31 (160 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH eno1ethernet connected /org/freedesktop/NetworkManager/Devices/2 Wired connection 2 a48d1ead-bcd2-37cb-8731-1d687642ff2c /org/freedesktop/NetworkManager/ActiveConnection/7 wlp2s0 wifi connected /org/freedesktop/NetworkManager/Devices/1 clear 4c47ad41-0865-488f-bcf6-2cc10a2d5a87 /org/freedesktop/NetworkManager/ActiveConnection/6 lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/3 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.2.4connected started full enabled enabled enabled enabled enabled ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug yakkety -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1640112 Title: Irregular USB network tethering failures Status in network-manager package in Ubuntu: New Bug description: Reporting this against network manager for want of better information. Sorry for the imprecise report - I will be glad to observe and update. Since upgrading to 16.10 I have had problems with my USB "ethernet" network connection provided by a tethered Android 2.3 device. Initial connection works well, but after a while Ubuntu looses connection, indicated by the nm-applet icon switching to "wifi connecting". Ubuntu seems unable to obtain an IP address. Neither rebooting the laptop nor restarting the phone help, but after a while the problem goes away on its own. In the meantime I am able to tether using the phone's wireless hotspot functionality. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: network-manager 1.2.4-0ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0 Uname: Linux 4.8.0-26-generic x86_64 ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Tue Nov 8 11:00:59 2016 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2016-05-31 (160 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH eno1ethernet connected /org/freedesktop/NetworkManager/Devices/2 Wired connection 2 a48d1ead-bcd2-37cb-8731-1d687642ff2c /org/freedesktop/NetworkManager/ActiveConnection/7 wlp2s0 wifi connected /org/freedesktop/NetworkManager/Devices/1 clear 4c47ad41-0865-488f-bcf6-2cc10a2d5a87 /org/freedesktop/NetworkManager/ActiveConnection/6 lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/3 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI
Re: [Touch-packages] [Bug 1443853] Re: Ubuntu 14.10 ISO live boot in Oracle VirtualBox ends up with a corrupted display
Hello, Short answer (mobile mail). On the whole a bug with a workaround is usually (understandably) less important to people than one without. I am slightly surprised that Canonical have not looked at this since I have provided a fix which may well be acceptable as is, but of course I do not presume to try to tell them what their priorities should be. Regards, Michael On 30. August 2016 02:58:14 GMT+03:00, "S. McCandlish" wrote: >Re: "I note that the person asking the question seemingly never >bothered >to create an Ubuntu bug, so it can't have been that important to them." >That's not actually a safe assumption at all. Many people are on the >clock and are not paid to file bug reports for the rest of the world. >As >soon they find a work-around that deals with the problem temporarily >and >locally, they move on. This problem has been reported world-wide in >multiple circumstances, and is still happening with 16.04. It just >happened to me right now (with the Xubunutu 16.04.1 ISO in a VirtualBox >VM). The Right-Ctrl F1 and Right-Ctrl F7 (or "Host" F1, "Host" F7, if >you've redefined the "Host" key) trick worked for me in this case, so >I'm done with it and getting back to work. It is possible I (or >someone >in my situation) might remember to try to replicate and debug this >problem further for everyone, on a VM at home, on our own time. But >Canonical cannot depend on this happening. It's a "bad administrator >experience" issue that should be dealt with like any other serious bug. > >-- >You received this bug notification because you are subscribed to the >bug >report. >https://bugs.launchpad.net/bugs/1443853 > >Title: > Ubuntu 14.10 ISO live boot in Oracle VirtualBox ends up with a > corrupted display > >Status in Virtualbox: > Invalid >Status in console-setup package in Ubuntu: > Confirmed >Status in kbd package in Ubuntu: > Confirmed >Status in virtualbox package in Ubuntu: > Incomplete > >Bug description: > (Content copied from "Ubuntu 14.10 ISO live boot ends up with a > corrupted display" #13615 VirtualBox bug ticket, by piotrjurkiewicz) > >Booting up live session of Ubuntu MATE 14.10 and Ubuntu Gnome 14.10 >from ISO ends up with a corrupted screen. See the screenshot: > https://launchpadlibrarian.net/186864347/ubu.png > > Switching back and forth to the tty7 (ctrl+alt+F1 and then alt+F7) > fixes the display. > > I think that this might be a problem with resolution setting: > > ``` >00:00:31.226379 Display::handleDisplayResize(): uScreenId = 0, >pvVRAM= w=1152 h=400 bpp=0 cbLine=0x0, flags=0x1 >00:00:31.226399 UIFrameBuffer::RequestResize: Screen=0, Format=0, >BitsPerPixel=0, BytesPerLine=0, Size=1152x400, Sending to >async-handler.. >00:00:31.226457 UIFrameBufferQImage::resizeEvent: Format=0, >BitsPerPixel=0, BytesPerLine=0, Size=1152x400 >00:00:31.226467 UIFrameBufferQImage::resizeEvent: Resizing to FALLBACK >buffer due to format is invalid.. > ``` > > After switching back and forth to the tty7 (what fixes the display) > the log says: > > ``` >00:00:31.226379 Display::handleDisplayResize(): uScreenId = 0, >pvVRAM= w=1152 h=400 bpp=0 cbLine=0x0, flags=0x1 >00:00:31.226399 UIFrameBuffer::RequestResize: Screen=0, Format=0, >BitsPerPixel=0, BytesPerLine=0, Size=1152x400, Sending to >async-handler.. >00:00:31.226457 UIFrameBufferQImage::resizeEvent: Format=0, >BitsPerPixel=0, BytesPerLine=0, Size=1152x400 >00:00:31.226467 UIFrameBufferQImage::resizeEvent: Resizing to FALLBACK >buffer due to format is invalid.. >00:01:37.584616 Display::handleDisplayResize(): uScreenId = 0, >pvVRAM= w=720 h=400 bpp=0 cbLine=0x0, flags=0x1 >00:01:37.584634 UIFrameBuffer::RequestResize: Screen=0, Format=0, >BitsPerPixel=0, BytesPerLine=0, Size=720x400, Sending to >async-handler.. >00:01:37.584680 UIFrameBufferQImage::resizeEvent: Format=0, >BitsPerPixel=0, BytesPerLine=0, Size=720x400 >00:01:37.584692 UIFrameBufferQImage::resizeEvent: Resizing to FALLBACK >buffer due to format is invalid.. >00:01:39.055475 Display::handleDisplayResize(): uScreenId = 0, >pvVRAM=0a7f w=1024 h=768 bpp=32 cbLine=0x1000, flags=0x1 >00:01:39.055495 UIFrameBuffer::RequestResize: Screen=0, >Format=843204434, BitsPerPixel=32, BytesPerLine=4096, Size=1024x768, >Sending to async-handler.. >00:01:39.09 UIFrameBufferQImage::resizeEvent: Format=843204434, >BitsPerPixel=32, BytesPerLine=4096, Size=1024x768 >00:01:39.055568 UIFrameBufferQImage::resizeEvent: Resizing to directly >use VGA device content.. > ``` > > I have tested 4.3.18 and also the testbuild 4.3.19 r96825, it happens > on both of them. > > You can download the ISO images of these two systems here: > > https://ubuntu-mate.r.worldssl.net/download/ubuntu-mate-14.10 > -desktop-amd64.iso > > http://cdimage.ubuntu.com/ubuntu-gnome/releases/14.10/release/ubuntu- > gnome-14.10-desktop-amd64.iso > >To manage notifications about this bug go to: >https://bugs.launchpad.net/virtualbox/+bug/1443853/+sub
[Touch-packages] [Bug 1599775] Re: "low-graphics mode" in VirtualBox guest, but X server running
Sorry, that doesn't do it yet. (Shame I didn't manage to fix this for 5.0.0.) However I realised that Mesa has exactly the same problem, so I have taken a look at their code to see what they do. Also looks like a bit of a hack, but since nothing relevant can afford not to work with Mesa it should be a safe one. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1599775 Title: "low-graphics mode" in VirtualBox guest, but X server running Status in lightdm package in Ubuntu: New Bug description: I sometimes get the "low-graphics mode" message when starting an Ubuntu 16.04 virtual machine inside of VirtualBox (current development code trunk, somewhere past version 5.1 beta 3 and a debug build). When I switch to VT-7 I find the X server running without any visible issues (I am the upstream developer of the guest graphics drivers, so I have a reasonable but not infallible understanding of the X server). The virtual machine has Guest Additions installed, same vintage and also a debug build. Two screens are enabled as is 3D acceleration. The host system is also Ubuntu 16.04. I am still trying to work out what triggers the message, but in my last attempts a cold boot failed to produce it, while a clean reboot did, but only when the host system was not under load (under load as in building VirtualBox). Searching the lightdm log files led me to the message "CRITICAL **: session_get_login1_session_id: assertion 'session != NULL' failed", which in turn led me to this similar-looking Debian bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=814760 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: lightdm 1.18.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13 Uname: Linux 4.4.0-28-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Thu Jul 7 10:49:27 2016 InstallationDate: Installed on 2016-06-08 (28 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) IRC discussion at: https://irclogs.ubuntu.com/2016/07/07/%23ubuntu-devel.html#t07:52 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1599775/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1436405] Re: Duplicate menu (both unity and in-app) for Qt5 apps
VirtualBox is affected by this. When I comment out calls to menuBar()->setVisible() in the VirtualBox source the duplicate menu bar goes away. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libdbusmenu-qt in Ubuntu. https://bugs.launchpad.net/bugs/1436405 Title: Duplicate menu (both unity and in-app) for Qt5 apps Status in One Hundred Papercuts: Confirmed Status in appmenu-qt5 package in Ubuntu: Confirmed Status in libdbusmenu-qt package in Ubuntu: Confirmed Bug description: At least konsole and khelpcenter suffers from this bug: Start the app inside the default Unity environment (not under KDE). Notice that the app's menubar appears twice. Once in the upper row of the whole desktop, as expected and as it is for every Gnome app. And also inside the application's window, wasting precious screen real estate. In Utopic, at least for konsole, I'm quite sure that the menu wasn't duplicated inside the app, it only appeared on the desktop's top Unity bar. (I'm not sure I guessed the component right; please reassign as appropriate.) ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: libdbusmenu-qt5 0.9.3+14.10.20140619-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-10.10-generic 3.19.2 Uname: Linux 3.19.0-10-generic x86_64 ApportVersion: 2.16.2-0ubuntu4 Architecture: amd64 CurrentDesktop: Unity Date: Wed Mar 25 16:33:14 2015 InstallationDate: Installed on 2012-05-30 (1028 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) SourcePackage: libdbusmenu-qt UpgradeStatus: Upgraded to vivid on 2015-03-17 (7 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1436405/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1599775] Re: "low-graphics mode" in VirtualBox guest, but X server running
I hope this upstream change set will do the trick: https://www.virtualbox.org/changeset/62242 Re comment 11, I looked at Mesa to see how they were distinguishing client and server GL and applied that to my code (see comments in change set). To summarise the issue: the tricks that we were playing to prevent the X server from loading our GL libraries, which unlike Mesa are designed to be client only, were not working here, and the X server process was failing when our libraries tried to call a function (RTR3InitDll) in another library which gets loaded by clients but which the X server was not (not sure why). I refined the tricks by studying how Mesa handles detecting being loaded by the server (technically being loaded for use with GBM rather than with X11) and in addition got rid of the immediate dependency which was failing. Was that at all helpful? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1599775 Title: "low-graphics mode" in VirtualBox guest, but X server running Status in lightdm package in Ubuntu: New Bug description: I sometimes get the "low-graphics mode" message when starting an Ubuntu 16.04 virtual machine inside of VirtualBox (current development code trunk, somewhere past version 5.1 beta 3 and a debug build). When I switch to VT-7 I find the X server running without any visible issues (I am the upstream developer of the guest graphics drivers, so I have a reasonable but not infallible understanding of the X server). The virtual machine has Guest Additions installed, same vintage and also a debug build. Two screens are enabled as is 3D acceleration. The host system is also Ubuntu 16.04. I am still trying to work out what triggers the message, but in my last attempts a cold boot failed to produce it, while a clean reboot did, but only when the host system was not under load (under load as in building VirtualBox). Searching the lightdm log files led me to the message "CRITICAL **: session_get_login1_session_id: assertion 'session != NULL' failed", which in turn led me to this similar-looking Debian bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=814760 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: lightdm 1.18.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13 Uname: Linux 4.4.0-28-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Thu Jul 7 10:49:27 2016 InstallationDate: Installed on 2016-06-08 (28 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) IRC discussion at: https://irclogs.ubuntu.com/2016/07/07/%23ubuntu-devel.html#t07:52 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1599775/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1604009] [NEW] Empty menus in global app-menu in VirtualBox second window
Public bug reported: Reporting this following this IRC discussion: https://irclogs.ubuntu.com/2016/07/15/%23ubuntu-devel.html#t14:00 The basic summary: when I run a two-screen/two-window virtual machine with VirtualBox under Ubuntu 16.04 with Unity and the global app-menu, the menus are empty when the second screen window has the input focus. During start-up I get a number (55) of these messages on the console: Qt WARNING: void DBusMenuExporterPrivate::fillLayoutItem(DBusMenuLayoutItem*, QMenu*, int, int, const QStringList&): No id for action and a number (7) of these: Qt WARNING: uint DBusMenuExporterDBus::GetLayout(int, int, const QStringList&, DBusMenuLayoutItem&): Condition failed: menu Then another 55 of the first and two of the second. Looking at the interesting parts of the VirtualBox source code, I see that the menu items for the first window (menu displayed correctly) and the second (not displayed) share the same QAction objects. A very quick guess is that this might be triggering the condition in DBusMenuExporterPrivate::addMenu(). ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: libdbusmenu-qt5 0.9.3+16.04.20160218-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10 Uname: Linux 4.4.0-24-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: Unity Date: Mon Jul 18 15:44:00 2016 Dependencies: gcc-5-base 5.4.0-6ubuntu1~16.04.1 gcc-6-base 6.0.1-0ubuntu1 libc6 2.23-0ubuntu3 libgcc1 1:6.0.1-0ubuntu1 libstdc++6 5.4.0-6ubuntu1~16.04.1 InstallationDate: Installed on 2016-05-31 (48 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: libdbusmenu-qt UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: libdbusmenu-qt (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libdbusmenu-qt in Ubuntu. https://bugs.launchpad.net/bugs/1604009 Title: Empty menus in global app-menu in VirtualBox second window Status in libdbusmenu-qt package in Ubuntu: New Bug description: Reporting this following this IRC discussion: https://irclogs.ubuntu.com/2016/07/15/%23ubuntu-devel.html#t14:00 The basic summary: when I run a two-screen/two-window virtual machine with VirtualBox under Ubuntu 16.04 with Unity and the global app-menu, the menus are empty when the second screen window has the input focus. During start-up I get a number (55) of these messages on the console: Qt WARNING: void DBusMenuExporterPrivate::fillLayoutItem(DBusMenuLayoutItem*, QMenu*, int, int, const QStringList&): No id for action and a number (7) of these: Qt WARNING: uint DBusMenuExporterDBus::GetLayout(int, int, const QStringList&, DBusMenuLayoutItem&): Condition failed: menu Then another 55 of the first and two of the second. Looking at the interesting parts of the VirtualBox source code, I see that the menu items for the first window (menu displayed correctly) and the second (not displayed) share the same QAction objects. A very quick guess is that this might be triggering the condition in DBusMenuExporterPrivate::addMenu(). ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: libdbusmenu-qt5 0.9.3+16.04.20160218-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10 Uname: Linux 4.4.0-24-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: Unity Date: Mon Jul 18 15:44:00 2016 Dependencies: gcc-5-base 5.4.0-6ubuntu1~16.04.1 gcc-6-base 6.0.1-0ubuntu1 libc6 2.23-0ubuntu3 libgcc1 1:6.0.1-0ubuntu1 libstdc++6 5.4.0-6ubuntu1~16.04.1 InstallationDate: Installed on 2016-05-31 (48 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: libdbusmenu-qt UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdbusmenu-qt/+bug/1604009/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1604009] Re: Empty menus in global app-menu in VirtualBox second window
By the way the commit which fixed that KDE bug is: http://bazaar.launchpad.net/~dbusmenu-team/libdbusmenu- qt/trunk/revision/189 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libdbusmenu-qt in Ubuntu. https://bugs.launchpad.net/bugs/1604009 Title: Empty menus in global app-menu in VirtualBox second window Status in libdbusmenu-qt package in Ubuntu: New Bug description: Reporting this following this IRC discussion: https://irclogs.ubuntu.com/2016/07/15/%23ubuntu-devel.html#t14:00 The basic summary: when I run a two-screen/two-window virtual machine with VirtualBox under Ubuntu 16.04 with Unity and the global app-menu, the menus are empty when the second screen window has the input focus. During start-up I get a number (55) of these messages on the console: Qt WARNING: void DBusMenuExporterPrivate::fillLayoutItem(DBusMenuLayoutItem*, QMenu*, int, int, const QStringList&): No id for action and a number (7) of these: Qt WARNING: uint DBusMenuExporterDBus::GetLayout(int, int, const QStringList&, DBusMenuLayoutItem&): Condition failed: menu Then another 55 of the first and two of the second. Looking at the interesting parts of the VirtualBox source code, I see that the menu items for the first window (menu displayed correctly) and the second (not displayed) share the same QAction objects. A very quick guess is that this might be triggering the condition in DBusMenuExporterPrivate::addMenu(). ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: libdbusmenu-qt5 0.9.3+16.04.20160218-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10 Uname: Linux 4.4.0-24-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: Unity Date: Mon Jul 18 15:44:00 2016 Dependencies: gcc-5-base 5.4.0-6ubuntu1~16.04.1 gcc-6-base 6.0.1-0ubuntu1 libc6 2.23-0ubuntu3 libgcc1 1:6.0.1-0ubuntu1 libstdc++6 5.4.0-6ubuntu1~16.04.1 InstallationDate: Installed on 2016-05-31 (48 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: libdbusmenu-qt UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdbusmenu-qt/+bug/1604009/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1604009] Re: Empty menus in global app-menu in VirtualBox second window
I got in touch with Aurélien, who wrote the original libdbusmenu-qt code, in case he has any ideas. This is a bit tricky for me, as I can only justify spending a limited time on it (my main area is graphics driver work), and while I could probably fix something up that would work for me, I don't understand the code well enough to be confident that I am not causing regressions - in particular I do not even have a test case for the original issue (the test in the commit just checks the fix, not the problem). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libdbusmenu-qt in Ubuntu. https://bugs.launchpad.net/bugs/1604009 Title: Empty menus in global app-menu in VirtualBox second window Status in libdbusmenu-qt package in Ubuntu: New Bug description: Reporting this following this IRC discussion: https://irclogs.ubuntu.com/2016/07/15/%23ubuntu-devel.html#t14:00 The basic summary: when I run a two-screen/two-window virtual machine with VirtualBox under Ubuntu 16.04 with Unity and the global app-menu, the menus are empty when the second screen window has the input focus. During start-up I get a number (55) of these messages on the console: Qt WARNING: void DBusMenuExporterPrivate::fillLayoutItem(DBusMenuLayoutItem*, QMenu*, int, int, const QStringList&): No id for action and a number (7) of these: Qt WARNING: uint DBusMenuExporterDBus::GetLayout(int, int, const QStringList&, DBusMenuLayoutItem&): Condition failed: menu Then another 55 of the first and two of the second. Looking at the interesting parts of the VirtualBox source code, I see that the menu items for the first window (menu displayed correctly) and the second (not displayed) share the same QAction objects. A very quick guess is that this might be triggering the condition in DBusMenuExporterPrivate::addMenu(). ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: libdbusmenu-qt5 0.9.3+16.04.20160218-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10 Uname: Linux 4.4.0-24-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: Unity Date: Mon Jul 18 15:44:00 2016 Dependencies: gcc-5-base 5.4.0-6ubuntu1~16.04.1 gcc-6-base 6.0.1-0ubuntu1 libc6 2.23-0ubuntu3 libgcc1 1:6.0.1-0ubuntu1 libstdc++6 5.4.0-6ubuntu1~16.04.1 InstallationDate: Installed on 2016-05-31 (48 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: libdbusmenu-qt UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdbusmenu-qt/+bug/1604009/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1443853] Re: Ubuntu 14.10 ISO live boot in Oracle VirtualBox ends up with a corrupted display
I think that in this day and age EGA console fonts are meaningless for 99% of the user base or more. I also think that if you remove the functionality the remaining 1% will complain very loudly. However, I suspect that many of those will have set up custom fonts to be loaded. So my suggested fix is to comment out everything in /etc/default /console-setup. Then the code will just not execute for users who have not set up custom fonts. Someone who actually understands the details of this should check whether this makes sense before implementing it. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to kbd in Ubuntu. https://bugs.launchpad.net/bugs/1443853 Title: Ubuntu 14.10 ISO live boot in Oracle VirtualBox ends up with a corrupted display Status in Virtualbox: Invalid Status in console-setup package in Ubuntu: Confirmed Status in kbd package in Ubuntu: Confirmed Status in virtualbox package in Ubuntu: Incomplete Bug description: (Content copied from "Ubuntu 14.10 ISO live boot ends up with a corrupted display" #13615 VirtualBox bug ticket, by piotrjurkiewicz) Booting up live session of Ubuntu MATE 14.10 and Ubuntu Gnome 14.10 from ISO ends up with a corrupted screen. See the screenshot: https://launchpadlibrarian.net/186864347/ubu.png Switching back and forth to the tty7 (ctrl+alt+F1 and then alt+F7) fixes the display. I think that this might be a problem with resolution setting: ``` 00:00:31.226379 Display::handleDisplayResize(): uScreenId = 0, pvVRAM= w=1152 h=400 bpp=0 cbLine=0x0, flags=0x1 00:00:31.226399 UIFrameBuffer::RequestResize: Screen=0, Format=0, BitsPerPixel=0, BytesPerLine=0, Size=1152x400, Sending to async-handler.. 00:00:31.226457 UIFrameBufferQImage::resizeEvent: Format=0, BitsPerPixel=0, BytesPerLine=0, Size=1152x400 00:00:31.226467 UIFrameBufferQImage::resizeEvent: Resizing to FALLBACK buffer due to format is invalid.. ``` After switching back and forth to the tty7 (what fixes the display) the log says: ``` 00:00:31.226379 Display::handleDisplayResize(): uScreenId = 0, pvVRAM= w=1152 h=400 bpp=0 cbLine=0x0, flags=0x1 00:00:31.226399 UIFrameBuffer::RequestResize: Screen=0, Format=0, BitsPerPixel=0, BytesPerLine=0, Size=1152x400, Sending to async-handler.. 00:00:31.226457 UIFrameBufferQImage::resizeEvent: Format=0, BitsPerPixel=0, BytesPerLine=0, Size=1152x400 00:00:31.226467 UIFrameBufferQImage::resizeEvent: Resizing to FALLBACK buffer due to format is invalid.. 00:01:37.584616 Display::handleDisplayResize(): uScreenId = 0, pvVRAM= w=720 h=400 bpp=0 cbLine=0x0, flags=0x1 00:01:37.584634 UIFrameBuffer::RequestResize: Screen=0, Format=0, BitsPerPixel=0, BytesPerLine=0, Size=720x400, Sending to async-handler.. 00:01:37.584680 UIFrameBufferQImage::resizeEvent: Format=0, BitsPerPixel=0, BytesPerLine=0, Size=720x400 00:01:37.584692 UIFrameBufferQImage::resizeEvent: Resizing to FALLBACK buffer due to format is invalid.. 00:01:39.055475 Display::handleDisplayResize(): uScreenId = 0, pvVRAM=0a7f w=1024 h=768 bpp=32 cbLine=0x1000, flags=0x1 00:01:39.055495 UIFrameBuffer::RequestResize: Screen=0, Format=843204434, BitsPerPixel=32, BytesPerLine=4096, Size=1024x768, Sending to async-handler.. 00:01:39.09 UIFrameBufferQImage::resizeEvent: Format=843204434, BitsPerPixel=32, BytesPerLine=4096, Size=1024x768 00:01:39.055568 UIFrameBufferQImage::resizeEvent: Resizing to directly use VGA device content.. ``` I have tested 4.3.18 and also the testbuild 4.3.19 r96825, it happens on both of them. You can download the ISO images of these two systems here: https://ubuntu-mate.r.worldssl.net/download/ubuntu-mate-14.10 -desktop-amd64.iso http://cdimage.ubuntu.com/ubuntu-gnome/releases/14.10/release/ubuntu- gnome-14.10-desktop-amd64.iso To manage notifications about this bug go to: https://bugs.launchpad.net/virtualbox/+bug/1443853/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1443853] Re: Ubuntu 14.10 ISO live boot in Oracle VirtualBox ends up with a corrupted display
If you do actually find someone at Ubuntu who knows about this, perhaps you can ask them to comment on this thread: https://www.virtualbox.org/pipermail/vbox-dev/2016-July/013926.html I note that the person asking the question seemingly never bothered to create an Ubuntu bug, so it can't have been that important to them. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to kbd in Ubuntu. https://bugs.launchpad.net/bugs/1443853 Title: Ubuntu 14.10 ISO live boot in Oracle VirtualBox ends up with a corrupted display Status in Virtualbox: Invalid Status in console-setup package in Ubuntu: Confirmed Status in kbd package in Ubuntu: Confirmed Status in virtualbox package in Ubuntu: Incomplete Bug description: (Content copied from "Ubuntu 14.10 ISO live boot ends up with a corrupted display" #13615 VirtualBox bug ticket, by piotrjurkiewicz) Booting up live session of Ubuntu MATE 14.10 and Ubuntu Gnome 14.10 from ISO ends up with a corrupted screen. See the screenshot: https://launchpadlibrarian.net/186864347/ubu.png Switching back and forth to the tty7 (ctrl+alt+F1 and then alt+F7) fixes the display. I think that this might be a problem with resolution setting: ``` 00:00:31.226379 Display::handleDisplayResize(): uScreenId = 0, pvVRAM= w=1152 h=400 bpp=0 cbLine=0x0, flags=0x1 00:00:31.226399 UIFrameBuffer::RequestResize: Screen=0, Format=0, BitsPerPixel=0, BytesPerLine=0, Size=1152x400, Sending to async-handler.. 00:00:31.226457 UIFrameBufferQImage::resizeEvent: Format=0, BitsPerPixel=0, BytesPerLine=0, Size=1152x400 00:00:31.226467 UIFrameBufferQImage::resizeEvent: Resizing to FALLBACK buffer due to format is invalid.. ``` After switching back and forth to the tty7 (what fixes the display) the log says: ``` 00:00:31.226379 Display::handleDisplayResize(): uScreenId = 0, pvVRAM= w=1152 h=400 bpp=0 cbLine=0x0, flags=0x1 00:00:31.226399 UIFrameBuffer::RequestResize: Screen=0, Format=0, BitsPerPixel=0, BytesPerLine=0, Size=1152x400, Sending to async-handler.. 00:00:31.226457 UIFrameBufferQImage::resizeEvent: Format=0, BitsPerPixel=0, BytesPerLine=0, Size=1152x400 00:00:31.226467 UIFrameBufferQImage::resizeEvent: Resizing to FALLBACK buffer due to format is invalid.. 00:01:37.584616 Display::handleDisplayResize(): uScreenId = 0, pvVRAM= w=720 h=400 bpp=0 cbLine=0x0, flags=0x1 00:01:37.584634 UIFrameBuffer::RequestResize: Screen=0, Format=0, BitsPerPixel=0, BytesPerLine=0, Size=720x400, Sending to async-handler.. 00:01:37.584680 UIFrameBufferQImage::resizeEvent: Format=0, BitsPerPixel=0, BytesPerLine=0, Size=720x400 00:01:37.584692 UIFrameBufferQImage::resizeEvent: Resizing to FALLBACK buffer due to format is invalid.. 00:01:39.055475 Display::handleDisplayResize(): uScreenId = 0, pvVRAM=0a7f w=1024 h=768 bpp=32 cbLine=0x1000, flags=0x1 00:01:39.055495 UIFrameBuffer::RequestResize: Screen=0, Format=843204434, BitsPerPixel=32, BytesPerLine=4096, Size=1024x768, Sending to async-handler.. 00:01:39.09 UIFrameBufferQImage::resizeEvent: Format=843204434, BitsPerPixel=32, BytesPerLine=4096, Size=1024x768 00:01:39.055568 UIFrameBufferQImage::resizeEvent: Resizing to directly use VGA device content.. ``` I have tested 4.3.18 and also the testbuild 4.3.19 r96825, it happens on both of them. You can download the ISO images of these two systems here: https://ubuntu-mate.r.worldssl.net/download/ubuntu-mate-14.10 -desktop-amd64.iso http://cdimage.ubuntu.com/ubuntu-gnome/releases/14.10/release/ubuntu- gnome-14.10-desktop-amd64.iso To manage notifications about this bug go to: https://bugs.launchpad.net/virtualbox/+bug/1443853/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
