[Touch-packages] [Bug 1630085] Re: Ubuntu 16.10 beta breaks Asus Laptop touchpad behavior
nothing changed on the xorg side ** Package changed: xorg (Ubuntu) => linux (Ubuntu) -- 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/1630085 Title: Ubuntu 16.10 beta breaks Asus Laptop touchpad behavior Status in linux package in Ubuntu: Incomplete Bug description: In 16.04 LTS, the touchpad behaved perfectly, and as soon as I stepped up to 16.10 beta the touchpad became unusable. When holding a single finger on the touchpad, without moving my finger, the cursor jumps around like crazy, and even performs clicks. When placing a second finger on the touchpad, without moving either, it gets even worse. See desktop recording clip as reference of the behavior (attached as out.ogv). The laptop is an Asus ZenBook UX31E. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: xorg 1:7.7+13ubuntu4 ProcVersionSignature: Ubuntu 4.8.0-17.19-generic 4.8.0-rc7 Uname: Linux 4.8.0-17-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 BootLog: /dev/sda1: clean, 415810/7815168 files, 10983001/31258368 blocks 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: Mon Oct 3 21:04:16 2016 DistUpgraded: Fresh install DistroCodename: yakkety DistroVariant: ubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. 2nd Generation Core Processor Family Integrated Graphics Controller [1043:1427] InstallationDate: Installed on 2016-03-17 (200 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160316) MachineType: ASUSTeK Computer Inc. UX31E ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-17-generic root=UUID=77be5fdd-c844-4d59-af29-cc718cf6b41a ro intel_state=disable pcie_aspm=force drm.vblankoffdelay=1 i915.semaphores=1 "acpi_osi=Windows 2009" "acpi_os_name=Windows 2009" quiet splash intel_state=disable pcie_aspm=force drm.vblankoffdelay=1 i915.semaphores=1 "acpi_osi=Windows 2009" "acpi_os_name=Windows 2009" SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/26/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX31E.210 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX31E dmi.board.vendor: ASUSTeK Computer Inc. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK Computer Inc. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX31E.210:bd12/26/2011:svnASUSTeKComputerInc.:pnUX31E:pvr1.0:rvnASUSTeKComputerInc.:rnUX31E:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0: dmi.product.name: UX31E dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK Computer Inc. version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu2 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.70-1 version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.3-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.3-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6 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.7.1-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.12-2 xserver.bootTime: Mon Oct 3 16:12:15 2016 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-1ubuntu6 xserver.video_driver: modeset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1630085/+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 1630877] [NEW] 1:4.2.6.p3+dfsg-1ubuntu3.11 - OPENSSL_1.0.0 not defined in file libcrypto.so.1.0.0
Public bug reported: Getting error after upgrade in 12.04 LTS (3.2.0-23-virtual) - ntpq: relocation error: ntpq: symbol CRYPTO_memcmp, version OPENSSL_1.0.0 not defined in file libcrypto.so.1.0.0 with link time reference ntpd not starting after the upgrade. ** Affects: ntp (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ntp in Ubuntu. https://bugs.launchpad.net/bugs/1630877 Title: 1:4.2.6.p3+dfsg-1ubuntu3.11 - OPENSSL_1.0.0 not defined in file libcrypto.so.1.0.0 Status in ntp package in Ubuntu: New Bug description: Getting error after upgrade in 12.04 LTS (3.2.0-23-virtual) - ntpq: relocation error: ntpq: symbol CRYPTO_memcmp, version OPENSSL_1.0.0 not defined in file libcrypto.so.1.0.0 with link time reference ntpd not starting after the upgrade. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1630877/+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 1630873] Re: i am unable to install the latest intel drivers on my DELL LATITUDE E6410
if you mean intel drivers from 01.org, we don't support them if you mean distribution updates, then check your package mirror and change it if necessary ** Changed in: xorg (Ubuntu) Status: New => Invalid -- 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/1630873 Title: i am unable to install the latest intel drivers on my DELL LATITUDE E6410 Status in xorg package in Ubuntu: Invalid Bug description: i get gpg error ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19 Uname: Linux 4.4.0-38-generic x86_64 NonfreeKernelModules: wl .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 BootLog: [[0;32m OK [0m] Started LSB: Speech Dispatcher. [[0;32m OK [0m] Started LSB: Set the CPU Frequency Scaling governor to "ondemand". [[0;32m OK [0m] Started Raise network interfaces. [[0;32m OK [0m] Reached target Network. 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 Oct 6 09:31:06 2016 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.248+bdcom, 4.4.0-21-generic, x86_64: installed bcmwl, 6.30.223.248+bdcom, 4.4.0-38-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Dell Latitude E6410 [1028:040a] InstallationDate: Installed on 2016-09-29 (6 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: Dell Inc. Latitude E6410 PlymouthDebug: Error: [Errno 13] Permission denied: '/var/log/plymouth-debug.log' ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-38-generic root=UUID=2a1688ea-72b3-4932-8ca3-0ffb4c0d5825 ro drm.debug=0xe plymouth:debug splash quiet SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/23/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A10 dmi.board.name: 0667CC dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA10:bd08/23/2011:svnDellInc.:pnLatitudeE6410:pvr0001:rvnDellInc.:rn0667CC:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6410 dmi.product.version: 0001 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Thu Oct 6 07:38:06 2016 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 21828 vendor AUO xserver.version: 2:1.18.3-1ubuntu2.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1630873/+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 1630309] Re: plasma panel auto hide - panel disappears and does not come back
not xorg ** Package changed: xorg (Ubuntu) => plasma-desktop (Ubuntu) -- 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/1630309 Title: plasma panel auto hide - panel disappears and does not come back Status in plasma-desktop package in Ubuntu: New Bug description: I have to open plasmashellrc and set planelVisibility to 0 to make it return. Simple reboot doesn't solve the problem. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19 Uname: Linux 4.4.0-38-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: KDE Date: Tue Oct 4 13:33:15 2016 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: kubuntu ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell 3rd Gen Core processor Graphics Controller [1028:0591] InstallationDate: Installed on 2016-07-27 (68 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Dell Inc. Inspiron 3421 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-38-generic.efi.signed root=UUID=11cb0acd-e2d1-4040-8e64-08167dfa22cf ro quiet splash SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/07/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A12 dmi.board.vendor: Dell Inc. dmi.board.version: A12 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA12:bd05/07/2014:svnDellInc.:pnInspiron3421:pvrNotSpecified:rvnDellInc.:rn:rvrA12:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Inspiron 3421 dmi.product.version: Not Specified dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Tue Oct 4 08:52:12 2016 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id5238 vendor CMN xserver.version: 2:1.18.3-1ubuntu2.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plasma-desktop/+bug/1630309/+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 1630291] Re: last update tension
that's compiz/unity not starting up properly ** Package changed: xorg (Ubuntu) => compiz (Ubuntu) -- 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/1630291 Title: last update tension Status in compiz package in Ubuntu: New Bug description: after last update, no more desktop : no button no sidebar nothing just the background pict and info coming like wifi connection... i tried the recovery mode but still. thanks for your help, work.. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.1 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 Date: Tue Oct 4 19:39:41 2016 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu DpkgLog: ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Sky Lake Integrated Graphics [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Skylake Integrated Graphics [1043:246a] Subsystem: ASUSTeK Computer Inc. GM108M [GeForce 940M] [1043:246a] InstallationDate: Installed on 2016-05-08 (149 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: ASUSTeK COMPUTER INC. X556UB ProcEnviron: LANGUAGE=fr_FR PATH=(custom, no user) LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic.efi.signed root=UUID=d89eb2d2-2577-4fc1-a25e-748f361946c0 ro quiet splash SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/09/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X556UB.402 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X556UB dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX556UB.402:bd03/09/2016:svnASUSTeKCOMPUTERINC.:pnX556UB:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX556UB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: X556UB dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Tue Oct 4 18:02:09 2016 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 14573 vendor AUO xserver.version: 2:1.18.3-1ubuntu2.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/1630291/+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 1630884] [NEW] Xorg freeze; mouse moves, but no mouse click or keyboard response
Public bug reported: I've encountered this issue on several fresh installations of Ubuntu 16.04.1 on different machines. Typically, the machine becomes unresponsive to the keyboard presses or to mouse clicks; however, it does respond to mouse movement. I am unable to open a text console to manipulate processes, and I am forced to hard restart the machine. During the most recent instance, I noticed that the mouse cursor would change in response to its location on the screen while The issue most often occurs about 3-5 minutes after Chromium has been opened, but it has also occurred without Chromium being installed. Moreover, it as occurred while using Xfce and GNOME 3 and while using open source and proprietary video drivers. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19 Uname: Linux 4.4.0-38-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: GNOME Date: Thu Oct 6 00:04:47 2016 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: Several times a day GpuHangReproducibility: Occurs more often under certain circumstances GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: NVIDIA Corporation GF119M [NVS 4200M] [10de:1056] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell GF119M [NVS 4200M] [1028:0493] InstallationDate: Installed on 2016-10-06 (0 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Dell Inc. Latitude E6420 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-38-generic root=UUID=3c7f4e14-5817-44b1-adbb-1666f8c29348 ro SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/04/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: A23 dmi.board.asset.tag: TSI3251 dmi.board.name: 032T9K dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.asset.tag: TSI3251 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA23:bd01/04/2016:svnDellInc.:pnLatitudeE6420:pvr01:rvnDellInc.:rn032T9K:rvrA02:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6420 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug freeze ubuntu xenial -- 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/1630884 Title: Xorg freeze; mouse moves, but no mouse click or keyboard response Status in xorg package in Ubuntu: New Bug description: I've encountered this issue on several fresh installations of Ubuntu 16.04.1 on different machines. Typically, the machine becomes unresponsive to the keyboard presses or to mouse clicks; however, it does respond to mouse movement. I am unable to open a text console to manipulate processes, and I am forced to hard restart the machine. During the most recent instance, I noticed that the mouse cursor would change in response to its location on the screen while The issue most often occurs about 3-5 minutes after Chromium has been opened, but it has also occurred without Chromium being installed. Moreover, it as occurred while using Xfce and GNOME 3 and while using open source and proprietary video drivers. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19 Uname: Linux 4.4.0-38-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: GNOME Date: Thu Oct 6 00:04:47 2016 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: Several times a day GpuHangReproducibility: Occurs more often under certain circumstances GpuHangStarted: Immediately after installing this version of Ubuntu G
[Touch-packages] [Bug 1598584] Re: wifi slows to a crawl when bluetooth is enabled
I have also heard other experts say this. And that the problem might be more pronounced in mediatek devices. That would suggest that solving this might not be possible from within UT. But in that case we would need some one to confirm that using BT and wifi together on -for example- the M10 running android has the same issue. If not, this should be fixable. And at the risk of stating the obvious, I would add that in the context of convergence, having this working properly is pretty essential because users connecting mice/keyboards is almost a given. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-network in Ubuntu. https://bugs.launchpad.net/bugs/1598584 Title: wifi slows to a crawl when bluetooth is enabled Status in arale: New Status in Canonical System Image: Confirmed Status in frieza: Confirmed Status in indicator-network package in Ubuntu: Invalid Bug description: I am having serious wifi performance issues on my Aquaris M10 (running rc-proposed r133). When measuring the wifi speed, I get download speeds of less than 1/20 compared to my Pro 5 at the same distance from the wifi router. This seems to be consistent through reboots. I had similar wifi performance also before recently upgrading to rc- proposed, which I thought would have fixed the issue. I am in the same place testing 3 different ubuntu devices and these are the readings of the wifi download speed: Laptop: 4 MB/s Pro 5: 3.5 MB/s Aquaris M10: 0.16 MB/s However, upload speed is about the same on all three devices. Turning bluetooth off gets Aquaris M10 wifi speed back to sort of normal, 2.5-3.4 MB/s. Bluetooth on, again 0.1-0.2 MB/s. Seems the two wireless technologies interfere with each other on the M10, while the Pro 5 doesn't have that problem. To manage notifications about this bug go to: https://bugs.launchpad.net/arale/+bug/1598584/+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 1495475] Re: DatePicker hard to use/read when in Dialogs and SuruDark theme
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: ubuntu-ui-toolkit (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1495475 Title: DatePicker hard to use/read when in Dialogs and SuruDark theme Status in ubuntu-ui-toolkit package in Ubuntu: Confirmed Bug description: As the summary says, see attached example qml To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1495475/+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 1338138] Re: [sdk] Time Picker component does not respect user locale
** Changed in: ubuntu-ui-toolkit (Ubuntu)
Assignee: Zsombor Egri (zsombi) => Christian Dywan (kalikiana)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in
Ubuntu.
https://bugs.launchpad.net/bugs/1338138
Title:
[sdk] Time Picker component does not respect user locale
Status in Ubuntu UX:
Fix Committed
Status in ubuntu-ui-toolkit package in Ubuntu:
Confirmed
Bug description:
In the new clock app we are using the Date Picker component to allow
the user to choose a time. Hence the mode used was "Hours|Minutes".
However the Date Picker seems to always display the time in 24 hour
instead of using the user's locale. So whereever 12-hour time format
is required, the time picker ignores that.
The code below shows the usage in the clock app.
DatePicker {
id: _timePicker
anchors {
left: parent.left
right: parent.right
margins: units.gu(-2)
}
clip: true
mode: "Hours|Minutes"
}
-- Design solution --
https://docs.google.com/a/canonical.com/document/d/1nFm8xiYhKXXuEO_IvMXoD0lASbYzYXva1BWMVanU3iw/edit#heading=h.tuxva2dtgvpk
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-ux/+bug/1338138/+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 1526250] Re: Pressing Escape should close an open PickerPanel
** Changed in: ubuntu-ui-toolkit (Ubuntu) Assignee: (unassigned) => Christian Dywan (kalikiana) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1526250 Title: Pressing Escape should close an open PickerPanel Status in ubuntu-ui-toolkit package in Ubuntu: Confirmed Bug description: If a DatePicker opens a PickerPanel, Escape should close it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1526250/+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 1298306] Re: Do not hardcode ordering of day number and day name in DatePicker
** Changed in: ubuntu-ui-toolkit (Ubuntu) Assignee: Zsombor Egri (zsombi) => Christian Dywan (kalikiana) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1298306 Title: Do not hardcode ordering of day number and day name in DatePicker Status in ubuntu-ui-toolkit package in Ubuntu: Confirmed Bug description: In my locale, when I'm seeing the day name and day number in a sentence, I expect to have them in "day_name day_number" format. However in the DatePicker, they seem to be the other way around. I.e. "dissabte 26" (expected, correct) vs "26 dissabte" (actual, incorrect). This comes from hardcoding the ordering in DayModel.qml [1]. Instead, - the day_name, day_number ordering should be taken from the user's locale or, - alternatively, if that ordering is not available, the string should be made translatable so that translators can reorder it according to their locale by translating the SDK zsombi mentioned there is a bug in MonthModel.qml too, but I couldn't quite find it. See the attached image showing the wrong order for the day picker. [1] http://bazaar.launchpad.net/~ubuntu-sdk-team/ubuntu-ui- toolkit/trunk/view/head:/modules/Ubuntu/Components/Pickers/DayModel.qml To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1298306/+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 1630872] Re: Clear text (x) does not clear the first suggested but not committed word
** Attachment added: "video20161005_175452486.mp4" https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1630872/+attachment/4755744/+files/video20161005_175452486.mp4 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1630872 Title: Clear text (x) does not clear the first suggested but not committed word Status in ubuntu-ui-toolkit package in Ubuntu: Confirmed Bug description: When the "Word suggestions" option in the "Language & Text" settings then the (x) clear button does not clear the first not committed word from the text input. It seems that the suggested word is not yet in the text innut but only in the input method and the clear button does not clear the input method. After the first word is committed, the second suggestion is cleared if you clear the content. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1630872/+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 1502145] Re: Apps can keep screen lit permanently
Bob, could you please attach /var/log/repowerd.log and /var/log/syslog to this bug. It could help us debug this issue. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-system-compositor in Ubuntu. https://bugs.launchpad.net/bugs/1502145 Title: Apps can keep screen lit permanently Status in Canonical System Image: Confirmed Status in Oxide: Fix Released Status in Oxide 1.10 series: Fix Released Status in qtmir package in Ubuntu: Confirmed Status in unity-system-compositor package in Ubuntu: Confirmed Status in unity8 package in Ubuntu: Confirmed Bug description: rc-proposed, r140, krillin There are times when it seems the display blanking policy stops working and the display stays on until I press the power button. Steps to reproduce: * install and start Siete * put it in background Expected outcome: * the display is switched off after a predetermined amount of time Actual outcome: * the display stays on forever == Now that apps can request the screen to stay on, they can do so regardless of whether they're focused/visible or not. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1502145/+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 1573524] Re: side stage first-use hint about 3-finger swipe does not stop (Frieza)
The screenshot i posted above doesn't really explain a lot. I expired that and did a small vid in which both scenario's are shown. 1. switch an app from sidestage to mainstage -> empty sidestage remains. It should imo dissapear. 2. kill a sidestaged app --> empty sidestage reappears after returning from app carrousel. It should imo dissapear. http://77.174.228.163/owncloud/public.php?service=files&t=36df8c5fafff6846a824bfc5c0142585 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1573524 Title: side stage first-use hint about 3-finger swipe does not stop (Frieza) Status in unity8 package in Ubuntu: Confirmed Bug description: OS: Ubuntu touch 15.04 OTA-10.1 Stable channel Device: BQ Aquaris M10 - (Frieza) As the bug title says: The 3-finger swipe hint to move apps between front- and side-stage, should only be shown once. However on the M10 Aquaris tablet, it is shown every time. It gets a bit annoying. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1573524/+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 1624738] Re: Firefox search and location boxes have black borders when unselected
The bg of the Firefox entry is styled by this selector, which feel like this might possibly be a Firefox bug: https://github.com/flexiondotorg/ubuntu-mate- themes/blob/master/usr/share/themes/Ambiant-MATE/gtk-3.0/gtk- widgets.css#L824 ** Also affects: ubuntu-themes (Ubuntu) Importance: Undecided Status: New ** Tags added: yakkety ** Description changed: - The Firefox tool tips bug it's fix but now there it's another problem. Its the same one from Libreoffice #1624571 - So it's the same a GTK3 implementation or a theming problem? - - OS: Ubuntu 16.10 daily - Interface : Mate 1.15.1 + As seen in the attached screen shot the borders around Firefox location + and search entry boxes are black when unselected but they should be + grey. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1624738 Title: Firefox search and location boxes have black borders when unselected Status in ubuntu-mate-artwork package in Ubuntu: Triaged Status in ubuntu-themes package in Ubuntu: New Bug description: As seen in the attached screen shot the borders around Firefox location and search entry boxes are black when unselected but they should be grey. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-mate-artwork/+bug/1624738/+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 1622423] Re: My activity child link disappears after logged in fitbit account
** Branch linked: lp:~aacid/unity8/dashSectionDelegateUpdateFix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1622423 Title: My activity child link disappears after logged in fitbit account Status in Canonical System Image: New Status in Today Scope: Confirmed Status in unity-scopes-shell package in Ubuntu: New Status in unity8 package in Ubuntu: In Progress Bug description: $ system-image-cli -i current build number: 15 device name: turbo channel: ubuntu-touch/rc/meizu-pd.en last update: 2016-09-05 03:19:44 version version: 15 version ubuntu: 20160903 version tag: OTA-13-rc version device: 20160824-d33b825 version custom: 20160831-992-8-12 The child arrow link of My Activity session disappears once logged in fitbit account in Today scope, so unable to open My Activity child scope from Today scope Steps to reproduce: 1. Open Today scope and navigate to My Activity session, 2. Existing a child link, tap it will open My Activity scope 2. Tap 'Add your fitbit account' and login with Google account 3. Once logged in, back to Today scope and refresh, check if the child link still exist. Actual results: Once logged in fitbit account, some items of fitbit displayed in session, but the child scope link has gone, unable to open My Activity scope from Today scope If open My Activity scope from manage page by swiping up, blank scope page shown To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1622423/+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 1624571] Re: White lines visible around toolbars in LibreOffice when using GTK3 and a dark theme
For reference, here is the commit from the Arc theme that fixes/works around this issue: * https://github.com/horst3180/arc- theme/commit/5b15bdc4425b6b3b8e374f76541f020419663edd ** Also affects: ubuntu-mate-artwork (Ubuntu) Importance: Undecided Status: New ** Changed in: ubuntu-mate-artwork (Ubuntu) Status: New => Triaged ** Also affects: ubuntu-themes (Ubuntu) Importance: Undecided Status: New ** Changed in: ubuntu-themes (Ubuntu) Status: New => Triaged -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1624571 Title: White lines visible around toolbars in LibreOffice when using GTK3 and a dark theme Status in ubuntu-mate: Triaged Status in libreoffice package in Ubuntu: Triaged Status in ubuntu-mate-artwork package in Ubuntu: Triaged Status in ubuntu-themes package in Ubuntu: Triaged Bug description: There are some portions where the theme is not consistent like on the right side "x" and so on. In the pictures you will see a comparation side by side with UBUNTU Mate 16.04 with Mate 1.14 gtk2 ppa The top bar from the picture it's from 16.10 and the next bar it's from 16.04 OS: Ubuntu 16.10 daily Interface : Mate 1.15.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1624571/+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 1630551] Re: indicator-network-secret-agent crashed with SIGSEGV in do_lookup_x()
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: indicator-network (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-network in Ubuntu. https://bugs.launchpad.net/bugs/1630551 Title: indicator-network-secret-agent crashed with SIGSEGV in do_lookup_x() Status in indicator-network package in Ubuntu: Confirmed Bug description: Crash on startup ProblemType: Crash DistroRelease: Ubuntu 16.10 Package: indicator-network 0.8.0+16.10.20160930.5-0ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-17.19-generic 4.8.0-rc7 Uname: Linux 4.8.0-17-generic i686 ApportVersion: 2.20.3-0ubuntu7 Architecture: i386 Date: Wed Oct 5 12:38:48 2016 ExecutablePath: /usr/lib/i386-linux-gnu/indicator-network/indicator-network-secret-agent ProcCmdline: /usr/lib/i386-linux-gnu/indicator-network/indicator-network-secret-agent ProcEnviron: PATH=(custom, no user) LANGUAGE=en_GB:en XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/false SegvAnalysis: Segfault happened at: 0xb779beba : mov0x4(%eax),%ebx PC (0xb779beba) ok source "0x4(%eax)" (0x0074) not located in a known VMA region (needed readable region)! destination "%ebx" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: indicator-network Stacktrace: #0 do_lookup_x (undef_name=0x0, new_hash=1, old_hash=0xbfaa21eb, ref=0x0, result=0x4cd, scope=0x70, i=3807944636, version=0xb779c529 , flags=5, skip=0x1, type_class=-1226319944, undef_map=0xd62) at dl-lookup.c:361 n = list = #1 0x in ?? () No symbol table info available. StacktraceTop: do_lookup_x (undef_name=0x0, new_hash=1, old_hash=0xbfaa21eb, ref=0x0, result=0x4cd, scope=0x70, i=3807944636, version=0xb779c529 , flags=5, skip=0x1, type_class=-1226319944, undef_map=0xd62) at dl-lookup.c:361 ?? () Title: indicator-network-secret-agent crashed with SIGSEGV in do_lookup_x() UpgradeStatus: Upgraded to yakkety on 2016-09-26 (8 days ago) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1630551/+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 1478319] Re: Wifi doesn't reconnect to AP if it uses the same SSID than another AP
I'll ask CE QA team to support the verification again. ** Changed in: canonical-devices-system-image Status: Won't Fix => Incomplete -- 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/1478319 Title: Wifi doesn't reconnect to AP if it uses the same SSID than another AP Status in Canonical System Image: Incomplete Status in network-manager package in Ubuntu: Expired Bug description: current build number: 68 device name: arale channel: ubuntu-touch/rc-proposed/meizu.en last update: 2015-07-24 08:00:20 version version: 68 version ubuntu: 20150724 version device: 20150709-8965e37 version custom: 20150716-819-8-42 My ISP (Free in France) provides a hotspot service so that customers can use the connection of any other customer using a generic open Wifi connection (for reference http://www.free.fr/assistance/2303.html - in French) The SSID is called 'FreeWifi' on all the boxes but obviously APs are all different since it's customers' DSL routers. When I connect to one of this access point, suspend the phone and resume it in another location where the SSID is available but from a different AP, the phone doesn't connect to this AP and the list of networks in the network-indicator doesn't refresh and still show the list of network from the previous location. I have to forget the network called 'FreeWifi' and reconnect in order to refresh the list and make it work. It's 100% reproducible. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1478319/+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 1630872] Re: Clear text (x) does not clear the first suggested but not committed word
- No AP tests fail. - Word suggestions are off by default, but don't affect the test results. - The most recent change related to the clear button is confirmed to not affect this bug: http://bazaar.launchpad.net/~ubuntu-sdk-team/ubuntu-ui-toolkit/staging/revision/2115 - Apparently with AP we don't test the button visibility directly. - We don't force the right IM settings to reproduce it either. ** Changed in: ubuntu-ui-toolkit (Ubuntu) Status: Confirmed => Triaged -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1630872 Title: Clear text (x) does not clear the first suggested but not committed word Status in ubuntu-ui-toolkit package in Ubuntu: Triaged Bug description: When the "Word suggestions" option in the "Language & Text" settings then the (x) clear button does not clear the first not committed word from the text input. It seems that the suggested word is not yet in the text innut but only in the input method and the clear button does not clear the input method. After the first word is committed, the second suggestion is cleared if you clear the content. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1630872/+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 1581626] Re: Switching to USB sound device stops USB mouse clicks from registering
Solution from post #10 worked for me. -- 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/1581626 Title: Switching to USB sound device stops USB mouse clicks from registering Status in xorg package in Ubuntu: Incomplete Bug description: When I switch the primary sound device to a USB headset connected to my laptop, mouse click events no longer work except in the Sound Settings window. This does not seem to occur when the device is connected, only when it is made the default audio device. Once this occurs, the mouse events do not work until the device is disconnected. Clicks inside the Sound Settings window are registered (including buttons and other tabs inside the System Settings window, but not the titlebar or close/minimize/maximize buttons.) Focus can be given to other windows via alt-tab and keyboard input continues to function, but mouse events do not register on windows focused in this way. This is *deeply* weird, BTW. Hardware: Jabra EVOLVE 80 headset lsusb reports: Bus 002 Device 022: ID 0b0e:0305 GN Netcom Steps to reproduce: 1. Connect the device to a USB port. 2. Open Sound Settings window. 3. Select the Jabra USB device as the primary sound device. 4. Observe that mouse clicks no longer register outside of the System Settings window. dmesg shows the following during this process: [130169.130542] usb 2-2.1.1: new full-speed USB device number 22 using xhci_hcd [130169.223026] usb 2-2.1.1: New USB device found, idVendor=0b0e, idProduct=0305 [130169.223031] usb 2-2.1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [130169.223034] usb 2-2.1.1: Product: Jabra EVOLVE LINK MS [130169.223036] usb 2-2.1.1: Manufacturer: GN Netcom A/S [130169.223038] usb 2-2.1.1: SerialNumber: 51E7669007 [130169.225586] usb 2-2.1.1: 1:1: cannot get freq at ep 0x83 [130169.227472] usb 2-2.1.1: 2:1: cannot get freq at ep 0x4 [130169.248162] input: GN Netcom A/S Jabra EVOLVE LINK MS as /devices/pci:00/:00:14.0/usb2/2-2/2-2.1/2-2.1.1/2-2.1.1:1.3/0003:0B0E:0305.0013/input/input34 [130169.302858] hid-generic 0003:0B0E:0305.0013: input,hiddev0,hidraw5: USB HID v1.00 Device [GN Netcom A/S Jabra EVOLVE LINK MS] on usb-:00:14.0-2.1.1/input3 [130169.351940] usb 2-2.1.1: 1:1: cannot get freq at ep 0x83 [130169.352187] usb 2-2.1.1: 1:1: cannot get freq at ep 0x83 [130169.358162] usb 2-2.1.1: 2:1: cannot get freq at ep 0x4 [130169.358439] usb 2-2.1.1: 2:1: cannot get freq at ep 0x4 [130169.361073] usb 2-2.1.1: 1:1: cannot get freq at ep 0x83 [130169.361323] usb 2-2.1.1: 1:1: cannot get freq at ep 0x83 [130169.373535] usb 2-2.1.1: 2:1: cannot get freq at ep 0x4 [130169.373904] usb 2-2.1.1: 2:1: cannot get freq at ep 0x4 [130169.380322] usb 2-2.1.1: 1:1: cannot get freq at ep 0x83 [130169.380645] usb 2-2.1.1: 1:1: cannot get freq at ep 0x83 [130177.637403] usb 2-2.1.1: USB disconnect, device number 22 This appears to possibly be related to bug #1371853. I'm happy to provide more information, try custom kernels, etc. as needed. Thanks! ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 NonfreeKernelModules: wl .tmp.unity_support_test.0: ApportVersion: 2.20.1-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 Date: Fri May 13 13:00:25 2016 DistUpgraded: 2016-04-25 16:22:59,827 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process "./xorg_fix_proprietary.py" (No such file or directory) (8)) DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.248+bdcom, 4.2.0-35-generic, x86_64: installed bcmwl, 6.30.223.248+bdcom, 4.4.0-21-generic, x86_64: installed i915-4.3.3-4.2.0, 2, 4.2.0-35-generic, x86_64: installed virtualbox, 5.0.18, 4.2.0-35-generic, x86_64: installed virtualbox, 5.0.18, 4.4.0-21-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Broadwell-U Integrated Graphics [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell Broadwell-U Integrated Graphics [1028:0665] InstallationDate: Installed on 2015-10-03 (222 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: Dell Inc. XPS 13 9343 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic root=UUID=21920f07-2445-42e9-82fe-5d6b209d8688 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to xenial on 2016-04-25 (17 days ago)
[Touch-packages] [Bug 1630908] [NEW] Scopes - Unable to remove
Public bug reported: Large number of Scopes on Touch can not be removed (BQ 4.5) in the store or even via the Terminal. 7digital 8Coupons Amazon eBay Holidays Open Library Reddit Wikipedia Yahoo! Finance Probably more. (Posted this as a question but got no answer, just realised ill get a close enough answer by posting it as a bug. Apologies if i am being annoying, just driven by curiosity) ** Affects: unity8 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1630908 Title: Scopes - Unable to remove Status in unity8 package in Ubuntu: New Bug description: Large number of Scopes on Touch can not be removed (BQ 4.5) in the store or even via the Terminal. 7digital 8Coupons Amazon eBay Holidays Open Library Reddit Wikipedia Yahoo! Finance Probably more. (Posted this as a question but got no answer, just realised ill get a close enough answer by posting it as a bug. Apologies if i am being annoying, just driven by curiosity) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1630908/+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 1630906] [NEW] QML segfault on arm64 due to builder kernel change
Public bug reported: Builders were changed from wily to xenial (4.4) kernel for arm64, and likely due to this the following kind of errors started happening: https://launchpadlibrarian.net/288487533/buildlog_ubuntu-yakkety-arm64 .ubuntu-push-qml_0.1+15.10.20150826.1-0ubuntu2_BUILDING.txt.gz They happen when executing QML code. I've ruled out that reverting to previous qtbase and qtdeclarative versions don't affect this, so it's not coming from a Qt change. I've also verified there's no problem eg on our Bq tablet running the same tests on xenial+overlay. There are currently no found changes at least in Qt upstream to backport arm64 related fixes. Cause is unknown. But the same problem is there on vivid, xenial and yakkety builds: https://launchpadlibrarian.net/288516465/buildlog_ubuntu-yakkety-arm64.online-accounts-api_0.1+16.10.20161006.1-0ubuntu1_BUILDING.txt.gz https://launchpadlibrarian.net/288515705/buildlog_ubuntu-xenial-arm64.online-accounts-api_0.1+16.04.20161006.1-0ubuntu1_BUILDING.txt.gz https://launchpadlibrarian.net/288515510/buildlog_ubuntu-vivid-arm64.online-accounts-api_0.1+15.04.20161006.1-0ubuntu1_BUILDING.txt.gz This means it does not matter if it's Qt 5.4 or 5.6, GCC 4.9, 5 or 6, or glibc 2.21, 2.23 or 2.24. More logs from affected packages: https://launchpadlibrarian.net/288493058/buildlog_ubuntu-yakkety-arm64.qtdeclarative-opensource-src_5.6.1-7ubuntu3~1_BUILDING.txt.gz https://launchpadlibrarian.net/288347391/buildlog_ubuntu-xenial-arm64.webbrowser-app_0.23+16.04.20161005.1-0ubuntu1_BUILDING.txt.gz https://launchpadlibrarian.net/288385063/buildlog_ubuntu-vivid-arm64.qmenumodel_0.2.10+15.04.20161005.1-0ubuntu1_BUILDING.txt.gz ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Affects: online-accounts-api (Ubuntu) Importance: Undecided Status: New ** Affects: qmenumodel (Ubuntu) Importance: Undecided Status: New ** Affects: qtdeclarative-opensource-src (Ubuntu) Importance: Undecided Status: New ** Affects: ubuntu-push-qml (Ubuntu) Importance: Undecided Status: New ** Affects: unity8 (Ubuntu) Importance: Undecided Status: New ** Affects: webbrowser-app (Ubuntu) Importance: Undecided Status: New ** Also affects: ubuntu-push-qml (Ubuntu) Importance: Undecided Status: New ** Also affects: online-accounts-api (Ubuntu) Importance: Undecided Status: New ** Summary changed: - QML segfault on arm64 due to builder change + QML segfault on arm64 due to builder kernel change ** Also affects: qtdeclarative-opensource-src (Ubuntu) Importance: Undecided Status: New ** Description changed: Builders were changed from wily to xenial (4.4) kernel for arm64, and likely due to this the following kind of errors started happening: https://launchpadlibrarian.net/288487533/buildlog_ubuntu-yakkety-arm64 .ubuntu-push-qml_0.1+15.10.20150826.1-0ubuntu2_BUILDING.txt.gz + They happen when executing QML code. + I've ruled out that reverting to previous qtbase and qtdeclarative versions don't affect this, so it's not coming from a Qt change. I've also verified there's no problem eg on our Bq tablet running the same - tests. There are currently no found changes at least in Qt upstream to - backport arm64 related fixes. + tests on xenial+overlay. There are currently no found changes at least + in Qt upstream to backport arm64 related fixes. Cause is unknown. But the same problem is there on vivid, xenial and yakkety builds: https://launchpadlibrarian.net/288516465/buildlog_ubuntu-yakkety-arm64.online-accounts-api_0.1+16.10.20161006.1-0ubuntu1_BUILDING.txt.gz https://launchpadlibrarian.net/288515705/buildlog_ubuntu-xenial-arm64.online-accounts-api_0.1+16.04.20161006.1-0ubuntu1_BUILDING.txt.gz https://launchpadlibrarian.net/288515510/buildlog_ubuntu-vivid-arm64.online-accounts-api_0.1+15.04.20161006.1-0ubuntu1_BUILDING.txt.gz This means it does not matter if it's Qt 5.4 or 5.6, GCC 4.9, 5 or 6, or glibc 2.21, 2.23 or 2.24. + + More logs from affected packages: + https://launchpadlibrarian.net/288493058/buildlog_ubuntu-yakkety-arm64.qtdeclarative-opensource-src_5.6.1-7ubuntu3~1_BUILDING.txt.gz ** Also affects: webbrowser-app (Ubuntu) Importance: Undecided Status: New ** Description changed: Builders were changed from wily to xenial (4.4) kernel for arm64, and likely due to this the following kind of errors started happening: https://launchpadlibrarian.net/288487533/buildlog_ubuntu-yakkety-arm64 .ubuntu-push-qml_0.1+15.10.20150826.1-0ubuntu2_BUILDING.txt.gz They happen when executing QML code. I've ruled out that reverting to previous qtbase and qtdeclarative versions don't affect this, so it's not coming from a Qt change. I've also verified there's no problem eg on our Bq tablet running the same tests on xenial+overlay. There are currently no found changes at least in Qt
[Touch-packages] [Bug 1630906] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. >From a terminal window please run: apport-collect 1630906 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtdeclarative-opensource- src in Ubuntu. https://bugs.launchpad.net/bugs/1630906 Title: QML segfault on arm64 due to builder kernel change Status in linux package in Ubuntu: Incomplete Status in online-accounts-api package in Ubuntu: New Status in qmenumodel package in Ubuntu: New Status in qtdeclarative-opensource-src package in Ubuntu: New Status in ubuntu-push-qml package in Ubuntu: New Status in unity8 package in Ubuntu: New Status in webbrowser-app package in Ubuntu: New Bug description: Builders were changed from wily to xenial (4.4) kernel for arm64, and likely due to this the following kind of errors started happening: https://launchpadlibrarian.net/288487533/buildlog_ubuntu-yakkety-arm64 .ubuntu-push-qml_0.1+15.10.20150826.1-0ubuntu2_BUILDING.txt.gz They happen when executing QML code. I've ruled out that reverting to previous qtbase and qtdeclarative versions don't affect this, so it's not coming from a Qt change. I've also verified there's no problem eg on our Bq tablet running the same tests on xenial+overlay. There are currently no found changes at least in Qt upstream to backport arm64 related fixes. Cause is unknown. But the same problem is there on vivid, xenial and yakkety builds: https://launchpadlibrarian.net/288516465/buildlog_ubuntu-yakkety-arm64.online-accounts-api_0.1+16.10.20161006.1-0ubuntu1_BUILDING.txt.gz https://launchpadlibrarian.net/288515705/buildlog_ubuntu-xenial-arm64.online-accounts-api_0.1+16.04.20161006.1-0ubuntu1_BUILDING.txt.gz https://launchpadlibrarian.net/288515510/buildlog_ubuntu-vivid-arm64.online-accounts-api_0.1+15.04.20161006.1-0ubuntu1_BUILDING.txt.gz This means it does not matter if it's Qt 5.4 or 5.6, GCC 4.9, 5 or 6, or glibc 2.21, 2.23 or 2.24. More logs from affected packages: https://launchpadlibrarian.net/288493058/buildlog_ubuntu-yakkety-arm64.qtdeclarative-opensource-src_5.6.1-7ubuntu3~1_BUILDING.txt.gz https://launchpadlibrarian.net/288347391/buildlog_ubuntu-xenial-arm64.webbrowser-app_0.23+16.04.20161005.1-0ubuntu1_BUILDING.txt.gz https://launchpadlibrarian.net/288385063/buildlog_ubuntu-vivid-arm64.qmenumodel_0.2.10+15.04.20161005.1-0ubuntu1_BUILDING.txt.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1630906/+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 1630919] Re: sudo crashed with SIGABRT in kill()
*** This bug is a duplicate of bug 1565332 *** https://bugs.launchpad.net/bugs/1565332 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1565332, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1630919/+attachment/4755758/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1630919/+attachment/4755760/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1630919/+attachment/4755763/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1630919/+attachment/4755764/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1630919/+attachment/4755765/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1630919/+attachment/4755766/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1630919/+attachment/4755768/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1565332 sudo crashed with SIGABRT in kill() ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sudo in Ubuntu. https://bugs.launchpad.net/bugs/1630919 Title: sudo crashed with SIGABRT in kill() Status in sudo package in Ubuntu: New Bug description: After login, I get a crash report from the system about sudo. ProblemType: Crash DistroRelease: Ubuntu 16.04 Package: sudo 1.8.16-0ubuntu1.2 ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19 Uname: Linux 4.4.0-38-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: Unity Date: Mon Oct 3 17:20:23 2016 ExecutablePath: /usr/bin/sudo InstallationDate: Installed on 2016-09-20 (16 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) ProcCmdline: sudo ./svoss-ctrl 10.0.2.57 --port 2101 --activate 512 Signal: 6 SourcePackage: sudo StacktraceTop: kill () at ../sysdeps/unix/syscall-template.S:84 ?? () __libc_start_main (main=0x564d8a6aba20, argc=7, argv=0x7ffc914e5bc8, init=, fini=, rtld_fini=, stack_end=0x7ffc914e5bb8) at ../csu/libc-start.c:291 ?? () Title: sudo crashed with SIGABRT in kill() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: VisudoCheck: /etc/sudoers: analisi effettuata correttamente /etc/sudoers.d/README: analisi effettuata correttamente To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/1630919/+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 1624571] Re: White lines visible around toolbars in LibreOffice when using GTK3 and a dark theme
** Changed in: ubuntu-mate-artwork (Ubuntu) Importance: Undecided => Medium ** Changed in: ubuntu-themes (Ubuntu) Importance: Undecided => Low ** Changed in: ubuntu-mate-artwork (Ubuntu) Status: Triaged => Fix Committed ** Changed in: ubuntu-mate-artwork (Ubuntu) Assignee: (unassigned) => Martin Wimpress (flexiondotorg) ** Changed in: ubuntu-themes (Ubuntu) Assignee: (unassigned) => Martin Wimpress (flexiondotorg) ** Changed in: ubuntu-themes (Ubuntu) Status: Triaged => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1624571 Title: White lines visible around toolbars in LibreOffice when using GTK3 and a dark theme Status in ubuntu-mate: Triaged Status in libreoffice package in Ubuntu: Triaged Status in ubuntu-mate-artwork package in Ubuntu: Fix Committed Status in ubuntu-themes package in Ubuntu: In Progress Bug description: There are some portions where the theme is not consistent like on the right side "x" and so on. In the pictures you will see a comparation side by side with UBUNTU Mate 16.04 with Mate 1.14 gtk2 ppa The top bar from the picture it's from 16.10 and the next bar it's from 16.04 OS: Ubuntu 16.10 daily Interface : Mate 1.15.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1624571/+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 1630931] [NEW] Wayland turkish language bug
Public bug reported: I can not write any of these letters "ı,I,i,İ" in GNOME Wayland Session. ** Affects: wayland (Ubuntu) Importance: Undecided Status: New ** Affects: fedora Importance: Unknown Status: Unknown ** Bug watch added: Red Hat Bugzilla #1229763 https://bugzilla.redhat.com/show_bug.cgi?id=1229763 ** Also affects: fedora via https://bugzilla.redhat.com/show_bug.cgi?id=1229763 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wayland in Ubuntu. https://bugs.launchpad.net/bugs/1630931 Title: Wayland turkish language bug Status in wayland package in Ubuntu: New Status in Fedora: Unknown Bug description: I can not write any of these letters "ı,I,i,İ" in GNOME Wayland Session. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wayland/+bug/1630931/+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 1603835] Re: Sometimes url and description of the url do not match in the address bar
** Changed in: webbrowser-app (Ubuntu) Assignee: Olivier Tilloy (osomon) => Andrew Hayzen (ahayzen) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu. https://bugs.launchpad.net/bugs/1603835 Title: Sometimes url and description of the url do not match in the address bar Status in webbrowser-app package in Ubuntu: Confirmed Bug description: In the webbrowser, when entering an address url of a website in the address bar, a list of similar webpages is provided below by auto-completion. The list is composed of url with a description of the address. But sometimes (and quite randomly it seems) the url address and the description do not match at all. Guess: It seems to happen with websites that I had removed from the history. Actually, a website that has been suppressed from the history should not appear in the url list no? Mx4 Ota 11 stable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1603835/+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 1630941] [NEW] Crash at shutdown in ~QNetworkConfiguration
Public bug reported: After the recent landing for bug 1618590 the Ubuntu Download Manager tests frequently crash at shutdown with the following stack trace: Thread 1 "test_mms_downlo" received signal SIGSEGV, Segmentation fault. 0x77201b23 in QNetworkConfiguration::~QNetworkConfiguration() () from /usr/lib/x86_64-linux-gnu/libQt5Network.so.5 (gdb) bt #0 0x77201b23 in QNetworkConfiguration::~QNetworkConfiguration() () from /usr/lib/x86_64-linux-gnu/libQt5Network.so.5 #1 0x76f31169 in QMetaType::destroy(int, void*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x76f46bf9 in QMetaCallEvent::~QMetaCallEvent() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #3 0x76f46c79 in QMetaCallEvent::~QMetaCallEvent() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x76f1c9a8 in QCoreApplicationPrivate::cleanupThreadData() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x76f1ca8a in QCoreApplicationPrivate::~QCoreApplicationPrivate() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x76f1cba9 in QCoreApplicationPrivate::~QCoreApplicationPrivate() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x76f510dc in QObject::~QObject() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x76f1ed12 in QCoreApplication::~QCoreApplication() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x00449bbc in main (argc=1, argv=) at /home/mike/src/udm/fix-1628635/tests/downloads/daemon/test_mms_download.cpp:97 This commit seems especially relevant: https://codereview.qt- project.org/#/c/172173/ Neither this test, nor UDM itself make any explicit use of QPluginLoader, so this is unlikely to be a case of UDM incorrectly unloading a plugin itself. To reproduce simply run UDM's test_mms_download test a number of times (crashes only occur intermittently). When tested with a silo without the three patches added for bug 1618590 this crash no-longer occurs. A similar crash appears to be happening in webbrowser-app as well: https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1630765 Possibly another similar crash in ~QNetworkSession: https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1630510 ** Affects: qtbase-opensource-src (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1630941 Title: Crash at shutdown in ~QNetworkConfiguration Status in qtbase-opensource-src package in Ubuntu: New Bug description: After the recent landing for bug 1618590 the Ubuntu Download Manager tests frequently crash at shutdown with the following stack trace: Thread 1 "test_mms_downlo" received signal SIGSEGV, Segmentation fault. 0x77201b23 in QNetworkConfiguration::~QNetworkConfiguration() () from /usr/lib/x86_64-linux-gnu/libQt5Network.so.5 (gdb) bt #0 0x77201b23 in QNetworkConfiguration::~QNetworkConfiguration() () from /usr/lib/x86_64-linux-gnu/libQt5Network.so.5 #1 0x76f31169 in QMetaType::destroy(int, void*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x76f46bf9 in QMetaCallEvent::~QMetaCallEvent() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #3 0x76f46c79 in QMetaCallEvent::~QMetaCallEvent() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x76f1c9a8 in QCoreApplicationPrivate::cleanupThreadData() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x76f1ca8a in QCoreApplicationPrivate::~QCoreApplicationPrivate() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x76f1cba9 in QCoreApplicationPrivate::~QCoreApplicationPrivate() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x76f510dc in QObject::~QObject() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x76f1ed12 in QCoreApplication::~QCoreApplication() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x00449bbc in main (argc=1, argv=) at /home/mike/src/udm/fix-1628635/tests/downloads/daemon/test_mms_download.cpp:97 This commit seems especially relevant: https://codereview.qt- project.org/#/c/172173/ Neither this test, nor UDM itself make any explicit use of QPluginLoader, so this is unlikely to be a case of UDM incorrectly unloading a plugin itself. To reproduce simply run UDM's test_mms_download test a number of times (crashes only occur intermittently). When tested with a silo without the three patches added for bug 1618590 this crash no-longer occurs. A similar crash appears to be happening in webbrowser-app as well: https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1630765 Possibly another similar crash in ~QNetworkSession: https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1630510 To manage notifications about this
[Touch-packages] [Bug 1630946] [NEW] ubuntu-server depends on open-iscsi and runs iscsid
Public bug reported: ubuntu-server has a hard dependency on open-iscsi, which means there is a daemon running (iscsid), and the package cannot be removed. All unnecessary daemons are a cause of concern when auditing a system. Propose moving this to "Recommends" instead, which currently has: Recommends: lxd, snapd ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: ubuntu-server 1.361 ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19 Uname: Linux 4.4.0-38-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 Date: Thu Oct 6 10:43:04 2016 Ec2AMI: ami-c06b1eb3 Ec2AMIManifest: (unknown) Ec2AvailabilityZone: eu-west-1a Ec2InstanceType: t2.medium Ec2Kernel: unavailable Ec2Ramdisk: unavailable ProcEnviron: TERM=xterm-256color SHELL=/bin/bash PATH=(custom, user) LANG=en_US.UTF-8 XDG_RUNTIME_DIR= SourcePackage: ubuntu-meta UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubuntu-meta (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug ec2-images xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1630946 Title: ubuntu-server depends on open-iscsi and runs iscsid Status in ubuntu-meta package in Ubuntu: New Bug description: ubuntu-server has a hard dependency on open-iscsi, which means there is a daemon running (iscsid), and the package cannot be removed. All unnecessary daemons are a cause of concern when auditing a system. Propose moving this to "Recommends" instead, which currently has: Recommends: lxd, snapd ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: ubuntu-server 1.361 ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19 Uname: Linux 4.4.0-38-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 Date: Thu Oct 6 10:43:04 2016 Ec2AMI: ami-c06b1eb3 Ec2AMIManifest: (unknown) Ec2AvailabilityZone: eu-west-1a Ec2InstanceType: t2.medium Ec2Kernel: unavailable Ec2Ramdisk: unavailable ProcEnviron: TERM=xterm-256color SHELL=/bin/bash PATH=(custom, user) LANG=en_US.UTF-8 XDG_RUNTIME_DIR= SourcePackage: ubuntu-meta UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1630946/+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 1630951] [NEW] systemd 219-7ubuntu6 ADT test failure with linux 3.19.0-70.78
Public bug reported: Testing failed on: armhf: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-vivid/vivid/armhf/s/systemd/20161003_153931@/log.gz ** Affects: systemd (Ubuntu) Importance: Undecided Status: New -- 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/1630951 Title: systemd 219-7ubuntu6 ADT test failure with linux 3.19.0-70.78 Status in systemd package in Ubuntu: New Bug description: Testing failed on: armhf: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-vivid/vivid/armhf/s/systemd/20161003_153931@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1630951/+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 1624342] Re: tst_textarea.11.qml unit test fails
** Changed in: ubuntu-ui-toolkit (Ubuntu) Assignee: (unassigned) => Christian Dywan (kalikiana) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1624342 Title: tst_textarea.11.qml unit test fails Status in ubuntu-ui-toolkit package in Ubuntu: Confirmed Bug description: Fails with Qt 5.6. FAIL! : components::TextAreaAPI::test_0_color() TextArea.color is same as TextEdit.canUndo Actual (): #5d5d5d Expected (): #00 Loc: [/tmp/buildd/ubuntu-ui-toolkit-1.3.2085+16.10.20160831.4/tests/unit/visual/tst_textarea.11.qml(141)] See https://jenkins.ubuntu.com/ubuntu-sdk/job/ubuntu-ui-toolkit-ci- amd64-devel/1201/consoleFull To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1624342/+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 1624340] Re: tst_textfield.11.qml unit test failures
** Changed in: ubuntu-ui-toolkit (Ubuntu) Assignee: (unassigned) => Christian Dywan (kalikiana) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1624340 Title: tst_textfield.11.qml unit test failures Status in ubuntu-ui-toolkit package in Ubuntu: Confirmed Bug description: Fails with Qt 5.6. FAIL! : components::TextFieldAPI::test_0_cursorRectangle() cursorRectangle 0 by default Actual (): QRectF(0, 4, 1, 16) Expected (): QRectF(0, 0, 0, 0) Loc: [/tmp/buildd/ubuntu-ui-toolkit-1.3.2085+16.10.20160831.4/tests/unit/visual/tst_textfield.11.qml(168)] See https://jenkins.ubuntu.com/ubuntu-sdk/job/ubuntu-ui-toolkit-ci- amd64-devel/1201/consoleFull. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1624340/+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 1470599] Re: Stuck mountall inside container
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: lxc (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1470599 Title: Stuck mountall inside container Status in lxc package in Ubuntu: Confirmed Bug description: trusty lxc 1.1.2-0ubuntu3~cloud0 kernel Linux ambipom 3.13.0-55-generic #94-Ubuntu SMP Thu Jun 18 00:27:10 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux All processes running on the container: 34700 ?Ss 0:00 [lxc monitor] /var/lib/lxc juju-machine-3-lxc-1 34729 ?Ss 0:00 \_ /sbin/init 34789 ?S 0:00 \_ @sbin/plymouthd --mode=boot --attach-to-session 34797 ?Ss 0:00 \_ plymouth-upstart-bridge 34803 ?S 0:00 \_ mountall --daemon 35368 ?S 0:00 \_ upstart-socket-bridge --daemon 36248 ?Ss 0:00 \_ dhclient -1 -v -pf /run/dhclient.eth0.pid -lf /var/lib/dhcp/dhclient.eth0.leases eth0 Several other containers on the same host started up just fine. If mountall is killed and restarted from the command line with verbose and debug flags, this is the output: root@juju-machine-3-lxc-1:~# mountall -v --debug Connected to Plymouth parse_filesystems: reading filesystems parse_filesystems: sysfs (nodev) parse_filesystems: rootfs (nodev) parse_filesystems: ramfs (nodev) parse_filesystems: bdev (nodev) parse_filesystems: proc (nodev) parse_filesystems: cgroup (nodev) parse_filesystems: cpuset (nodev) parse_filesystems: tmpfs (nodev) parse_filesystems: devtmpfs (nodev) parse_filesystems: debugfs (nodev) parse_filesystems: securityfs (nodev) parse_filesystems: sockfs (nodev) parse_filesystems: pipefs (nodev) parse_filesystems: anon_inodefs (nodev) parse_filesystems: devpts (nodev) parse_filesystems: ext3 parse_filesystems: ext2 parse_filesystems: ext4 parse_filesystems: hugetlbfs (nodev) parse_filesystems: vfat parse_filesystems: ecryptfs (nodev) parse_filesystems: fuseblk parse_filesystems: fuse (nodev) parse_filesystems: fusectl (nodev) parse_filesystems: pstore (nodev) parse_filesystems: efivarfs (nodev) parse_filesystems: mqueue (nodev) parse_filesystems: xfs parse_fstab: updating from /lib/init/fstab update_mount: /: / /dev/root rootfs defaults check update_mount: /proc: /proc none proc nodev,noexec,nosuid update_mount: /proc/sys/fs/binfmt_misc: /proc/sys/fs/binfmt_misc none binfmt_misc nodev,noexec,nosuid,optional update_mount: /sys: /sys none sysfs nodev,noexec,nosuid update_mount: /sys/fs/cgroup: /sys/fs/cgroup none tmpfs optional,uid=0,gid=0,mode=0755,size=1024 update_mount: /sys/fs/fuse/connections: /sys/fs/fuse/connections none fusectl optional update_mount: /sys/kernel/debug: /sys/kernel/debug none debugfs optional update_mount: /sys/kernel/security: /sys/kernel/security none securityfs optional update_mount: /sys/firmware/efi/efivars: /sys/firmware/efi/efivars none efivarfs optional update_mount: /spu: /spu none spufs gid=spu,optional update_mount: /dev: /dev none devtmpfs,tmpfs mode=0755 update_mount: /dev/pts: /dev/pts none devpts noexec,nosuid,gid=tty,mode=0620 update_mount: /tmp: /tmp none none defaults update_mount: /run: /run none tmpfs noexec,nosuid,size=10%,mode=0755 update_mount: /run/lock: /run/lock none tmpfs nodev,noexec,nosuid,size=5242880 update_mount: /run/shm: /run/shm none tmpfs nosuid,nodev update_mount: /run/user: /run/user none tmpfs nodev,noexec,nosuid,size=104857600,mode=0755 update_mount: /sys/fs/pstore: /sys/fs/pstore none pstore optional parse_fstab: updating from /etc/fstab update_mount: /: / LABEL=cloudimg-rootfs ext4 defaults parse_mountinfo_file: updating mounts update_mount: /: / /dev/disk/by-uuid/7d38a3ed-8f5b-49d4-8087-b1573a17bb98 ext4 defaults update_mount: /dev: /dev none tmpfs mode=0755 update_mount: /proc: /proc proc proc nodev,noexec,nosuid update_mount: /proc/sys/net: /proc/sys/net proc proc rw,nosuid,nodev,noexec,relatime,rw update_mount: /proc/sys: /proc/sys proc proc ro,nosuid,nodev,noexec,relatime,rw update_mount: /proc/sysrq-trigger: /proc/sysrq-trigger proc proc ro,nosuid,nodev,noexec,relatime,rw update_mount: /sys: /sys sysfs sysfs nodev,noexec,nosuid update_mount: /sys: /sys sysfs sysfs nodev,noexec,nosuid update_mount: /sys/devices/virtual/net: /sys/devices/virtual/net sysfs sysfs rw,relatime,rw update_mount: /sys/devices/virtual/net: /sys/devices/virtual/net sysfs sysfs rw,relatime,rw update_mount: /sys/fs/fuse/connections: /sys/fs/fuse/connections none fusectl optional update_mount: /sys/kernel/debug: /sys/kernel/debug none debugfs optional update_mount: /sys/kernel/security: /sys/kernel/security none securityfs optional update_mount: /sys/fs/pstore: /sys/fs/pstor
[Touch-packages] [Bug 1630951] Re: systemd 219-7ubuntu6 ADT test failure with linux 3.19.0-70.78
As discussed on IRC, let's ignore this. The test is by and large fine, there's just something wrong with either configuring lightdm, or apparmor profiles or what not. It works in later releases, we don't do vivid SRUs any more, and there's nothing actually broken in the package, so britney hinting it is :-) ** Also affects: systemd (Ubuntu Vivid) Importance: Undecided Status: New ** Changed in: systemd (Ubuntu) Status: New => Fix Released ** Changed in: systemd (Ubuntu Vivid) Status: New => Won't Fix -- 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/1630951 Title: systemd 219-7ubuntu6 ADT test failure with linux 3.19.0-70.78 Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Vivid: Won't Fix Bug description: Testing failed on: armhf: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-vivid/vivid/armhf/s/systemd/20161003_153931@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1630951/+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 1630877] Re: 1:4.2.6.p3+dfsg-1ubuntu3.11 - OPENSSL_1.0.0 not defined in file libcrypto.so.1.0.0
That's odd. Do you have a custom openssl installed? Could you please paste the output of the following commands: $ ldd /usr/bin/ntpq $ apt-cache policy openssl Thanks! ** Changed in: ntp (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ntp in Ubuntu. https://bugs.launchpad.net/bugs/1630877 Title: 1:4.2.6.p3+dfsg-1ubuntu3.11 - OPENSSL_1.0.0 not defined in file libcrypto.so.1.0.0 Status in ntp package in Ubuntu: Incomplete Bug description: Getting error after upgrade in 12.04 LTS (3.2.0-23-virtual) - ntpq: relocation error: ntpq: symbol CRYPTO_memcmp, version OPENSSL_1.0.0 not defined in file libcrypto.so.1.0.0 with link time reference ntpd not starting after the upgrade. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1630877/+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 1628855] Re: UITK Gallery: first click on left panel list items activates the focus frame
** Branch linked: lp:~zsombi/ubuntu-ui-toolkit/listItemFocusRegression -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1628855 Title: UITK Gallery: first click on left panel list items activates the focus frame Status in ubuntu-ui-toolkit package in Ubuntu: Confirmed Bug description: ubuntu-ui-toolkit/staging r2133 Environment: Yakkety Beta libqt5core5a: Installed: 5.6.1+dfsg-3ubuntu5~xenialoverlay1~1 How to reproduce: - build uitk source - run the gallery (./gallery.sh) - Click on a list item in the left panel Expected outcome: the list item is selected, no focus frame is shown Actual outcome: The list item is selected and the focus frame is shown around it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1628855/+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 1625372] Re: NTP security issues on Precise and Trusty
http://www.ubuntu.com/usn/usn-3096-1/ ** Changed in: ntp (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ntp in Ubuntu. https://bugs.launchpad.net/bugs/1625372 Title: NTP security issues on Precise and Trusty Status in ntp package in Ubuntu: Fix Released Bug description: Based on the changelog, precise and trusty have not received patches for the following CVE issues: CVE-2016-1547 CVE-2016-1548 CVE-2016-1550 CVE-2016-2516 CVE-2016-2518 When will these be fixed on Precise and Trusty? They have been fixed on Debian 7 and 8. Thanks, Bryan To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1625372/+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 1630877] Re: 1:4.2.6.p3+dfsg-1ubuntu3.11 - OPENSSL_1.0.0 not defined in file libcrypto.so.1.0.0
Also: $ apt-cache policy libssl1.0.0 Thanks -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ntp in Ubuntu. https://bugs.launchpad.net/bugs/1630877 Title: 1:4.2.6.p3+dfsg-1ubuntu3.11 - OPENSSL_1.0.0 not defined in file libcrypto.so.1.0.0 Status in ntp package in Ubuntu: Incomplete Bug description: Getting error after upgrade in 12.04 LTS (3.2.0-23-virtual) - ntpq: relocation error: ntpq: symbol CRYPTO_memcmp, version OPENSSL_1.0.0 not defined in file libcrypto.so.1.0.0 with link time reference ntpd not starting after the upgrade. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1630877/+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 1624343] Re: Qt5.6: UbuntuListView unit test fails with TypeError
** Changed in: ubuntu-ui-toolkit (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1624343 Title: Qt5.6: UbuntuListView unit test fails with TypeError Status in ubuntu-ui-toolkit package in Ubuntu: Fix Committed Bug description: Failing unit tests with Qt 5.6: * Start testing of components * Config: Using QtTest library 5.6.1, Qt 5.6.1 (x86_64-little_endian-lp64 shared (dynamic) release build; by GCC 5.4.0 20160609) PASS : components::UbuntuListView::initTestCase() PASS : components::UbuntuListView::test_collapseByClickingOutside() PASS : components::UbuntuListView::test_collapseOnClick() PASS : components::UbuntuListView::test_destroyAndRecreateExpanded() PASS : components::UbuntuListView::test_dimOthers() PASS : components::UbuntuListView::test_expandedItem() FAIL! : components::UbuntuListView::test_noScrollingNeeded() Uncaught exception: Type error Loc: [/tmp/buildd/ubuntu-ui-toolkit-1.3.2085+16.10.20160831.4/tests/unit/visual/tst_ubuntulistview.10.qml(116)] FAIL! : components::UbuntuListView::test_scrollIntoView() Uncaught exception: Type error Loc: [/tmp/buildd/ubuntu-ui-toolkit-1.3.2085+16.10.20160831.4/tests/unit/visual/tst_ubuntulistview.10.qml(142)] FAIL! : components::UbuntuListView::test_scrollToTop() Uncaught exception: Type error Loc: [/tmp/buildd/ubuntu-ui-toolkit-1.3.2085+16.10.20160831.4/tests/unit/visual/tst_ubuntulistview.10.qml(129)] PASS : components::UbuntuListView::cleanupTestCase() Totals: 7 passed, 3 failed, 0 skipped, 0 blacklisted * Finished testing of components * See https://jenkins.ubuntu.com/ubuntu-sdk/job/ubuntu-ui-toolkit-ci- amd64-devel/1201/consoleFull To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1624343/+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 1603835] Re: Sometimes url and description of the url do not match in the address bar
When the user requests a page this starts a request in the webview, then once this has completed a loadEvent is fired [0]. This load event adds a history entry with url and current title (the url) [1] and stores the url in an internal cache [2]. The normally when a page has finished rendering the title changes [3], which updates the history entry with the new title and blocks any future updates. However if you start a request to another page while loading a slow page and the title has not changed. Then the onTitleChanged [3] code is triggered before the loadEvent [0] as the title is updated to the new request url. But because of the cached url [2] it updates the wrong history entry. I've found a reproducible way of doing this on my machine. Navigate to [4]. Click on one of the entries, such as Firewatch [5]. Now as the page is loading quickly navigate to google.com. If you were fast enough, when you type "Firewatch" into the address bar you get a title of "google.com" and a url of "store.playstation.com/..." So to resolve this issue when a new page is requested, the cache needs to be unset or the code in onTitleChanged needs to be blocked. 0 - http://bazaar.launchpad.net/~phablet-team/webbrowser-app/trunk/view/head:/src/app/webbrowser/Browser.qml#L1237 1 - http://bazaar.launchpad.net/~phablet-team/webbrowser-app/trunk/view/head:/src/app/webbrowser/Browser.qml#L1252 2 - http://bazaar.launchpad.net/~phablet-team/webbrowser-app/trunk/view/head:/src/app/webbrowser/Browser.qml#L1231 3 - http://bazaar.launchpad.net/~phablet-team/webbrowser-app/trunk/view/head:/src/app/webbrowser/Browser.qml#L1255 4 - http://www.thesixthaxis.com/2016/10/05/the-october-savings-sale-for-the-ps-store-is-now-live/ 5 - https://store.playstation.com/#!/cid=EP0144-CUSA04118_00-FIREWATCH000?smcid=psblog:en:October savings start today on PlayStation Store, inc. Uncharted 4, Just Cause 3, moreFirewatch ** Changed in: webbrowser-app (Ubuntu) Status: Confirmed => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu. https://bugs.launchpad.net/bugs/1603835 Title: Sometimes url and description of the url do not match in the address bar Status in webbrowser-app package in Ubuntu: In Progress Bug description: In the webbrowser, when entering an address url of a website in the address bar, a list of similar webpages is provided below by auto-completion. The list is composed of url with a description of the address. But sometimes (and quite randomly it seems) the url address and the description do not match at all. Guess: It seems to happen with websites that I had removed from the history. Actually, a website that has been suppressed from the history should not appear in the url list no? Mx4 Ota 11 stable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1603835/+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 1581626] Re: Switching to USB sound device stops USB mouse clicks from registering
Michael Rauch, it will help immensely if you filed a new report with Ubuntu by ensuring you have the package xdiagnose installed, and that you click the Yes button for attaching additional debugging information running the following from a terminal: ubuntu-bug xorg Also, please feel free to subscribe me to it. For more on why this is helpful, please see https://wiki.ubuntu.com/ReportingBugs. -- 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/1581626 Title: Switching to USB sound device stops USB mouse clicks from registering Status in xorg package in Ubuntu: Incomplete Bug description: When I switch the primary sound device to a USB headset connected to my laptop, mouse click events no longer work except in the Sound Settings window. This does not seem to occur when the device is connected, only when it is made the default audio device. Once this occurs, the mouse events do not work until the device is disconnected. Clicks inside the Sound Settings window are registered (including buttons and other tabs inside the System Settings window, but not the titlebar or close/minimize/maximize buttons.) Focus can be given to other windows via alt-tab and keyboard input continues to function, but mouse events do not register on windows focused in this way. This is *deeply* weird, BTW. Hardware: Jabra EVOLVE 80 headset lsusb reports: Bus 002 Device 022: ID 0b0e:0305 GN Netcom Steps to reproduce: 1. Connect the device to a USB port. 2. Open Sound Settings window. 3. Select the Jabra USB device as the primary sound device. 4. Observe that mouse clicks no longer register outside of the System Settings window. dmesg shows the following during this process: [130169.130542] usb 2-2.1.1: new full-speed USB device number 22 using xhci_hcd [130169.223026] usb 2-2.1.1: New USB device found, idVendor=0b0e, idProduct=0305 [130169.223031] usb 2-2.1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [130169.223034] usb 2-2.1.1: Product: Jabra EVOLVE LINK MS [130169.223036] usb 2-2.1.1: Manufacturer: GN Netcom A/S [130169.223038] usb 2-2.1.1: SerialNumber: 51E7669007 [130169.225586] usb 2-2.1.1: 1:1: cannot get freq at ep 0x83 [130169.227472] usb 2-2.1.1: 2:1: cannot get freq at ep 0x4 [130169.248162] input: GN Netcom A/S Jabra EVOLVE LINK MS as /devices/pci:00/:00:14.0/usb2/2-2/2-2.1/2-2.1.1/2-2.1.1:1.3/0003:0B0E:0305.0013/input/input34 [130169.302858] hid-generic 0003:0B0E:0305.0013: input,hiddev0,hidraw5: USB HID v1.00 Device [GN Netcom A/S Jabra EVOLVE LINK MS] on usb-:00:14.0-2.1.1/input3 [130169.351940] usb 2-2.1.1: 1:1: cannot get freq at ep 0x83 [130169.352187] usb 2-2.1.1: 1:1: cannot get freq at ep 0x83 [130169.358162] usb 2-2.1.1: 2:1: cannot get freq at ep 0x4 [130169.358439] usb 2-2.1.1: 2:1: cannot get freq at ep 0x4 [130169.361073] usb 2-2.1.1: 1:1: cannot get freq at ep 0x83 [130169.361323] usb 2-2.1.1: 1:1: cannot get freq at ep 0x83 [130169.373535] usb 2-2.1.1: 2:1: cannot get freq at ep 0x4 [130169.373904] usb 2-2.1.1: 2:1: cannot get freq at ep 0x4 [130169.380322] usb 2-2.1.1: 1:1: cannot get freq at ep 0x83 [130169.380645] usb 2-2.1.1: 1:1: cannot get freq at ep 0x83 [130177.637403] usb 2-2.1.1: USB disconnect, device number 22 This appears to possibly be related to bug #1371853. I'm happy to provide more information, try custom kernels, etc. as needed. Thanks! ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 NonfreeKernelModules: wl .tmp.unity_support_test.0: ApportVersion: 2.20.1-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 Date: Fri May 13 13:00:25 2016 DistUpgraded: 2016-04-25 16:22:59,827 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process "./xorg_fix_proprietary.py" (No such file or directory) (8)) DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.248+bdcom, 4.2.0-35-generic, x86_64: installed bcmwl, 6.30.223.248+bdcom, 4.4.0-21-generic, x86_64: installed i915-4.3.3-4.2.0, 2, 4.2.0-35-generic, x86_64: installed virtualbox, 5.0.18, 4.2.0-35-generic, x86_64: installed virtualbox, 5.0.18, 4.4.0-21-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Broadwell-U Integrated Graphics [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell Broadwell-U Integrated Graphics [1028:0665] InstallationDate: Installed on 201
[Touch-packages] [Bug 1630966] [NEW] SMS notified only when screen is ON
Public bug reported: Since OTA 13, when screen is OFF, incoming SMS are not received until the screen is switched ON: no SMS tone is played, LED is not blinking. As soon as I switch my screen ON, the tone will be played and the LED will start blinking, as if it had just arrived. However, please note that after a long time with screen OFF, the notification is effective. Seen on: BQ Aquaris E4.5 Ubuntu 15.04 OTA 13 ** Affects: messaging-app (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to messaging-app in Ubuntu. https://bugs.launchpad.net/bugs/1630966 Title: SMS notified only when screen is ON Status in messaging-app package in Ubuntu: New Bug description: Since OTA 13, when screen is OFF, incoming SMS are not received until the screen is switched ON: no SMS tone is played, LED is not blinking. As soon as I switch my screen ON, the tone will be played and the LED will start blinking, as if it had just arrived. However, please note that after a long time with screen OFF, the notification is effective. Seen on: BQ Aquaris E4.5 Ubuntu 15.04 OTA 13 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/messaging-app/+bug/1630966/+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 1630969] Re: package android-tools-adbd 5.1.1r36+git20160322-0ubuntu4 failed to install/upgrade: subprocess new pre-removal script returned error exit status 5
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to android-tools in Ubuntu. https://bugs.launchpad.net/bugs/1630969 Title: package android-tools-adbd 5.1.1r36+git20160322-0ubuntu4 failed to install/upgrade: subprocess new pre-removal script returned error exit status 5 Status in android-tools package in Ubuntu: New Bug description: that package is not upgadable, that is all i can say, sorry) ProblemType: Package DistroRelease: Ubuntu 16.10 Package: android-tools-adbd 5.1.1r36+git20160322-0ubuntu4 ProcVersionSignature: Ubuntu 4.8.0-19.21-generic 4.8.0-rc8 Uname: Linux 4.8.0-19-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 Date: Thu Oct 6 04:03:47 2016 ErrorMessage: subprocess new pre-removal script returned error exit status 5 InstallationDate: Installed on 2016-09-23 (13 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160726) RelatedPackageVersions: dpkg 1.18.10ubuntu1 apt 1.3.1 SourcePackage: android-tools Title: package android-tools-adbd 5.1.1r36+git20160322-0ubuntu4 failed to install/upgrade: subprocess new pre-removal script returned error exit status 5 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/android-tools/+bug/1630969/+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 1630969] [NEW] package android-tools-adbd 5.1.1r36+git20160322-0ubuntu4 failed to install/upgrade: subprocess new pre-removal script returned error exit status 5
Public bug reported: that package is not upgadable, that is all i can say, sorry) ProblemType: Package DistroRelease: Ubuntu 16.10 Package: android-tools-adbd 5.1.1r36+git20160322-0ubuntu4 ProcVersionSignature: Ubuntu 4.8.0-19.21-generic 4.8.0-rc8 Uname: Linux 4.8.0-19-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 Date: Thu Oct 6 04:03:47 2016 ErrorMessage: subprocess new pre-removal script returned error exit status 5 InstallationDate: Installed on 2016-09-23 (13 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160726) RelatedPackageVersions: dpkg 1.18.10ubuntu1 apt 1.3.1 SourcePackage: android-tools Title: package android-tools-adbd 5.1.1r36+git20160322-0ubuntu4 failed to install/upgrade: subprocess new pre-removal script returned error exit status 5 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: android-tools (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package yakkety -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to android-tools in Ubuntu. https://bugs.launchpad.net/bugs/1630969 Title: package android-tools-adbd 5.1.1r36+git20160322-0ubuntu4 failed to install/upgrade: subprocess new pre-removal script returned error exit status 5 Status in android-tools package in Ubuntu: New Bug description: that package is not upgadable, that is all i can say, sorry) ProblemType: Package DistroRelease: Ubuntu 16.10 Package: android-tools-adbd 5.1.1r36+git20160322-0ubuntu4 ProcVersionSignature: Ubuntu 4.8.0-19.21-generic 4.8.0-rc8 Uname: Linux 4.8.0-19-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 Date: Thu Oct 6 04:03:47 2016 ErrorMessage: subprocess new pre-removal script returned error exit status 5 InstallationDate: Installed on 2016-09-23 (13 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160726) RelatedPackageVersions: dpkg 1.18.10ubuntu1 apt 1.3.1 SourcePackage: android-tools Title: package android-tools-adbd 5.1.1r36+git20160322-0ubuntu4 failed to install/upgrade: subprocess new pre-removal script returned error exit status 5 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/android-tools/+bug/1630969/+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 1630702] Re: CVE-2016-8332 allows an out-of-bound heap write to occur resulting in heap corruption and arbitrary code execution
Thanks for taking the time to report this bug and helping to make Ubuntu better. Since the package referred to in this bug is in universe or multiverse, it is community maintained. If you are able, I suggest coordinating with upstream and posting a debdiff for this issue. When a debdiff is available, members of the security team will review it and publish the package. See the following link for more information: https://wiki.ubuntu.com/SecurityTeam/UpdateProcedures ** Changed in: openjpeg (Ubuntu) Status: New => Incomplete ** Changed in: openjpeg2 (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openjpeg in Ubuntu. https://bugs.launchpad.net/bugs/1630702 Title: CVE-2016-8332 allows an out-of-bound heap write to occur resulting in heap corruption and arbitrary code execution Status in openjpeg package in Ubuntu: Incomplete Status in openjpeg2 package in Ubuntu: Incomplete Bug description: A security vulnerability was recently disclosed in openjpeg and assigned the CVE number of CVE-2016-8332. The vulnerability is described here (http://www.zdnet.com/article /openjpeg-zero-day-flaw-leads-to-remote-code-execution/): " Cisco Talos researchers have uncovered a severe zero-day flaw in the OpenJPEG JPEG 2000 codec which could lead to remote code execution on compromised systems. On Friday, researchers from Cisco revealed the existence of the zero- day flaw in the JPEG 2000 image file format parser implemented in OpenJPEG library. The out-of-bounds vulnerability, assigned as CVE-2016-8332, could allow an out-of-bound heap write to occur resulting in heap corruption and arbitrary code execution. OpenJPEG is an open-source JPEG 2000 codec. Written in C, the software was created to promote JPEG 2000, an image compression standard which is in popular use and is often used for tasks including embedding images within PDF documents through software including Poppler, MuPDF and Pdfium. The bug, assigned a CVSS score of 7.5, was caused by errors in parsing mcc records in the jpeg2000 file, resulting in "an erroneous read and write of adjacent heap area memory." If manipulated, these errors can lead to heap metadata process memory corruption. In a security advisory, the team said the security vulnerability can be exploited by attackers if victims open specifically crafted, malicious JPEG 2000 images. For example, if this content was within a phishing email or hosted on legitimate services such as Google Drive or Dropbox, once downloaded to their system, the path is created for attackers to execute code remotely. The vulnerability was discovered by Aleksander Nikolic from the Cisco Talos security team in OpenJpeg openjp2 version 2.1.1. Cisco Talos disclosed the vulnerability to affected vendors on 26 July, granting them time to prepare patches to fix the problem before public release. " I am filing this report as a fix for the issue doesn't seem to have yet been backported in and given the importance of the issue and the ease in exploiting it, it would be good if this is done soon. This is the fix on GitHub: https://github.com/uclouvain/openjpeg/pull/820/files To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openjpeg/+bug/1630702/+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 1630440] Re: package udev 229-4ubuntu10 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find. ** Information type changed from Private Security to Public -- 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/1630440 Title: package udev 229-4ubuntu10 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in systemd package in Ubuntu: New Bug description: . ProblemType: Package DistroRelease: Ubuntu 16.04 Package: udev 229-4ubuntu10 ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19 Uname: Linux 4.4.0-38-generic i686 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: i386 CustomUdevRuleFiles: 98_smfpautoconf_samsung.rules 99_smfpautoconf_samsung.rules Date: Tue Oct 4 23:56:20 2016 DpkgHistoryLog: Start-Date: 2016-10-04 23:55:59 Commandline: aptdaemon role='role-commit-packages' sender=':1.45' Upgrade: libsystemd0:i386 (229-4ubuntu8, 229-4ubuntu10), udev:i386 (229-4ubuntu8, 229-4ubuntu10), libudev1:i386 (229-4ubuntu8, 229-4ubuntu10), systemd-sysv:i386 (229-4ubuntu8, 229-4ubuntu10), libpam-systemd:i386 (229-4ubuntu8, 229-4ubuntu10), systemd:i386 (229-4ubuntu8, 229-4ubuntu10) ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2016-09-18 (16 days ago) InstallationMedia: Lubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1) MachineType: HP-Pavilion 061 ER875AA-ABM SR1703LS ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-38-generic root=UUID=d0d75028-45b7-431e-a350-6e80a6864bfe ro quiet splash vt.handoff=7 RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.12~ubuntu16.04.1 SourcePackage: systemd Title: package udev 229-4ubuntu10 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/18/2007 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3.24 dmi.board.name: Asterope dmi.board.vendor: ECS dmi.board.version: 1.0 dmi.chassis.type: 3 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3.24:bd01/18/2007:svnHP-Pavilion061:pnER875AA-ABMSR1703LS:pvr0001411LX101ASTER10:rvnECS:rnAsterope:rvr1.0:cvnHewlett-Packard:ct3:cvr: dmi.product.name: ER875AA-ABM SR1703LS dmi.product.version: 0001411LX101ASTER10 dmi.sys.vendor: HP-Pavilion 061 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1630440/+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 1630440] Re: package udev 229-4ubuntu10 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
** Tags removed: need-duplicate-check -- 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/1630440 Title: package udev 229-4ubuntu10 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in systemd package in Ubuntu: New Bug description: . ProblemType: Package DistroRelease: Ubuntu 16.04 Package: udev 229-4ubuntu10 ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19 Uname: Linux 4.4.0-38-generic i686 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: i386 CustomUdevRuleFiles: 98_smfpautoconf_samsung.rules 99_smfpautoconf_samsung.rules Date: Tue Oct 4 23:56:20 2016 DpkgHistoryLog: Start-Date: 2016-10-04 23:55:59 Commandline: aptdaemon role='role-commit-packages' sender=':1.45' Upgrade: libsystemd0:i386 (229-4ubuntu8, 229-4ubuntu10), udev:i386 (229-4ubuntu8, 229-4ubuntu10), libudev1:i386 (229-4ubuntu8, 229-4ubuntu10), systemd-sysv:i386 (229-4ubuntu8, 229-4ubuntu10), libpam-systemd:i386 (229-4ubuntu8, 229-4ubuntu10), systemd:i386 (229-4ubuntu8, 229-4ubuntu10) ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2016-09-18 (16 days ago) InstallationMedia: Lubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1) MachineType: HP-Pavilion 061 ER875AA-ABM SR1703LS ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-38-generic root=UUID=d0d75028-45b7-431e-a350-6e80a6864bfe ro quiet splash vt.handoff=7 RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.12~ubuntu16.04.1 SourcePackage: systemd Title: package udev 229-4ubuntu10 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/18/2007 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3.24 dmi.board.name: Asterope dmi.board.vendor: ECS dmi.board.version: 1.0 dmi.chassis.type: 3 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3.24:bd01/18/2007:svnHP-Pavilion061:pnER875AA-ABMSR1703LS:pvr0001411LX101ASTER10:rvnECS:rnAsterope:rvr1.0:cvnHewlett-Packard:ct3:cvr: dmi.product.name: ER875AA-ABM SR1703LS dmi.product.version: 0001411LX101ASTER10 dmi.sys.vendor: HP-Pavilion 061 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1630440/+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 1629746] Re: package account-plugin-google 0.12+16.04.20160126-0ubuntu1 failed to install/upgrade: el paquete account-plugin-google no está listo para configurarse no se puede c
Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find. ** Information type changed from Private Security to Public -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to account-plugins in Ubuntu. https://bugs.launchpad.net/bugs/1629746 Title: package account-plugin-google 0.12+16.04.20160126-0ubuntu1 failed to install/upgrade: el paquete account-plugin-google no está listo para configurarse no se puede configurar (estado actual `half-installed') Status in account-plugins package in Ubuntu: New Bug description: Se encontraron errores al procesar: account-plugin-google E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Package DistroRelease: Ubuntu 16.04 Package: account-plugin-google 0.12+16.04.20160126-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19 Uname: Linux 4.4.0-38-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 AptOrdering: kde-l10n-engb: Remove kde-l10n-es: Remove account-plugin-google: Configure NULL: ConfigurePending Architecture: amd64 Date: Sun Oct 2 21:39:30 2016 ErrorMessage: el paquete account-plugin-google no está listo para configurarse no se puede configurar (estado actual `half-installed') InstallationDate: Installed on 2016-10-01 (1 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.14 SourcePackage: account-plugins Title: package account-plugin-google 0.12+16.04.20160126-0ubuntu1 failed to install/upgrade: el paquete account-plugin-google no está listo para configurarse no se puede configurar (estado actual `half-installed') UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/account-plugins/+bug/1629746/+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 1624571] Re: White lines visible around toolbars in LibreOffice when using GTK3 and a dark theme
The following merge proposal has been submitted for ubuntu-themes: * https://code.launchpad.net/~flexiondotorg/ubuntu- themes/lp1624571/+merge/307819 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1624571 Title: White lines visible around toolbars in LibreOffice when using GTK3 and a dark theme Status in ubuntu-mate: Triaged Status in libreoffice package in Ubuntu: Triaged Status in ubuntu-mate-artwork package in Ubuntu: Fix Committed Status in ubuntu-themes package in Ubuntu: In Progress Bug description: There are some portions where the theme is not consistent like on the right side "x" and so on. In the pictures you will see a comparation side by side with UBUNTU Mate 16.04 with Mate 1.14 gtk2 ppa The top bar from the picture it's from 16.10 and the next bar it's from 16.04 OS: Ubuntu 16.10 daily Interface : Mate 1.15.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1624571/+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 1628855] Re: UITK Gallery: first click on left panel list items activates the focus frame
** Changed in: ubuntu-ui-toolkit (Ubuntu) Status: Confirmed => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1628855 Title: UITK Gallery: first click on left panel list items activates the focus frame Status in ubuntu-ui-toolkit package in Ubuntu: In Progress Bug description: ubuntu-ui-toolkit/staging r2133 Environment: Yakkety Beta libqt5core5a: Installed: 5.6.1+dfsg-3ubuntu5~xenialoverlay1~1 How to reproduce: - build uitk source - run the gallery (./gallery.sh) - Click on a list item in the left panel Expected outcome: the list item is selected, no focus frame is shown Actual outcome: The list item is selected and the focus frame is shown around it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1628855/+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 1630974] [NEW] on boot
Public bug reported: i (re)boot ubuntu, apport came up ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: cups 2.1.3-4 ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19 Uname: Linux 4.4.0-38-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CupsErrorLog: E [05/Oct/2016:19:25:13 +0200] [cups-deviced] PID 2623 (gutenprint52+usb) stopped with status 1! CurrentDesktop: XFCE Date: Thu Oct 6 14:07:49 2016 InstallationDate: Installed on 2016-08-21 (45 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Lpstat: device for Brother_HL-5340D_series: usb://Brother/HL-5340D%20series?serial=C2J484409 MachineType: Hewlett-Packard HP Compaq dc5800 Microtower Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/Brother_HL-5340D_series.ppd'] failed with exit code 2: grep: /etc/cups/ppd/Brother_HL-5340D_series.ppd: Permission denied ProcEnviron: LANGUAGE=de_DE PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-38-generic root=UUID=636bf0b1-0f8e-4eda-9a0e-caeac815dcfd ro quiet splash vt.handoff=7 SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/31/2008 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 786F2 v01.04 dmi.board.asset.tag: CZC8163PK6 dmi.board.name: 2820h dmi.board.vendor: Hewlett-Packard dmi.chassis.asset.tag: CZC8163PK6 dmi.chassis.type: 6 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr786F2v01.04:bd01/31/2008:svnHewlett-Packard:pnHPCompaqdc5800Microtower:pvr:rvnHewlett-Packard:rn2820h:rvr:cvnHewlett-Packard:ct6:cvr: dmi.product.name: HP Compaq dc5800 Microtower dmi.sys.vendor: Hewlett-Packard ** Affects: cups (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 cups in Ubuntu. https://bugs.launchpad.net/bugs/1630974 Title: on boot Status in cups package in Ubuntu: New Bug description: i (re)boot ubuntu, apport came up ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: cups 2.1.3-4 ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19 Uname: Linux 4.4.0-38-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CupsErrorLog: E [05/Oct/2016:19:25:13 +0200] [cups-deviced] PID 2623 (gutenprint52+usb) stopped with status 1! CurrentDesktop: XFCE Date: Thu Oct 6 14:07:49 2016 InstallationDate: Installed on 2016-08-21 (45 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Lpstat: device for Brother_HL-5340D_series: usb://Brother/HL-5340D%20series?serial=C2J484409 MachineType: Hewlett-Packard HP Compaq dc5800 Microtower Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/Brother_HL-5340D_series.ppd'] failed with exit code 2: grep: /etc/cups/ppd/Brother_HL-5340D_series.ppd: Permission denied ProcEnviron: LANGUAGE=de_DE PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-38-generic root=UUID=636bf0b1-0f8e-4eda-9a0e-caeac815dcfd ro quiet splash vt.handoff=7 SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/31/2008 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 786F2 v01.04 dmi.board.asset.tag: CZC8163PK6 dmi.board.name: 2820h dmi.board.vendor: Hewlett-Packard dmi.chassis.asset.tag: CZC8163PK6 dmi.chassis.type: 6 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr786F2v01.04:bd01/31/2008:svnHewlett-Packard:pnHPCompaqdc5800Microtower:pvr:rvnHewlett-Packard:rn2820h:rvr:cvnHewlett-Packard:ct6:cvr: dmi.product.name: HP Compaq dc5800 Microtower dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1630974/+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 1603835] Re: Sometimes url and description of the url do not match in the address bar
** Branch linked: lp:~ahayzen/webbrowser-app/fix-1603835-incorrect- history-title -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu. https://bugs.launchpad.net/bugs/1603835 Title: Sometimes url and description of the url do not match in the address bar Status in webbrowser-app package in Ubuntu: In Progress Bug description: In the webbrowser, when entering an address url of a website in the address bar, a list of similar webpages is provided below by auto-completion. The list is composed of url with a description of the address. But sometimes (and quite randomly it seems) the url address and the description do not match at all. Guess: It seems to happen with websites that I had removed from the history. Actually, a website that has been suppressed from the history should not appear in the url list no? Mx4 Ota 11 stable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1603835/+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 1620323] Re: Address Bar Spoofing in Default Browser of Ubuntu LTS.
This isn't really a security issue, it is how URLs work. The value specified before the "@" is considered to be the username. See RFC 3986. (https://www.ietf.org/rfc/rfc3986.txt) That being said, while Chrome simply allows the username, firefox does display a warning to the user. ** Changed in: webbrowser-app (Ubuntu) Status: New => Confirmed ** Information type changed from Private Security to Public -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu. https://bugs.launchpad.net/bugs/1620323 Title: Address Bar Spoofing in Default Browser of Ubuntu LTS. Status in webbrowser-app package in Ubuntu: Confirmed Bug description: Hello , The default browser of the Ubuntu LTS is vulnerable to Address Bar Spoofing. Steps : Ubuntu browser allows attacker to spoof the web-browser by just using '@' symbol. Example : https://google@bing.com , this will redirect a user or a victim to bing.com rather than google.com. An attacker can take an advantage of it and may redirect it to any malicious website. Example : https://facebook@attacker.com , similarly this will also redirect to attacker.com rather than facebook.com. There are various scenario to exploit , one of it using BeeF using [hook.js] which is browser based exploitation and as such many more. Example: https://example.com@attacker.com/hook.js Well where as hook.js is a component of BeeF, which allows attacker to leads to browser based exploitation As far i recommend and request there should be a pop-up for this as a mitigation that some one is trying to tamper the URL. Kindly have a look on the attached Video POC , to clear the above scenario. I would be happy to hear from the team. Thank you To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1620323/+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 1443203] Re: GUFW blocks all incoming VNC connections even if rules allow
** Information type changed from Private Security to Public -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ufw in Ubuntu. https://bugs.launchpad.net/bugs/1443203 Title: GUFW blocks all incoming VNC connections even if rules allow Status in ufw package in Ubuntu: New Bug description: I am having a problem with GUFW. I have it set to block incoming connections from everything. I then set rules to allow incoming connections from a VNC client on my local network to a VMWare Player VNC setup but no matter what I do with those rules, I cannot connect to the VNC server on my machine unless I change the setting for my profile to Allow for everything. Making and applying rules has no effect if the "Incoming" setting at the top of the application is set to Deny or Reject. The only other option is to turn off the firewall entirely for a moment for the VNC client to connect, and then turn it back on again once a connection is established. Allowing all incoming connections for even a few moments just to use VNC on one port is a security risk. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ufw/+bug/1443203/+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 1388743] Re: iOS 8.1 - Could not start com.apple.mobile.installation_proxy!
libusbmuxd was updated: http://www.ubuntu.com/usn/usn-3026-2/ ** Changed in: libusbmuxd (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libimobiledevice in Ubuntu. https://bugs.launchpad.net/bugs/1388743 Title: iOS 8.1 - Could not start com.apple.mobile.installation_proxy! Status in libimobiledevice package in Ubuntu: Fix Released Status in libusbmuxd package in Ubuntu: Fix Released Status in libimobiledevice source package in Xenial: Fix Released Bug description: * Impact When running ideviceinstaller -l, I get the following error: Could not start com.apple.mobile.installation_proxy! * Test case connect an iOS >8 device and try to use ideviceinstaller * Regression potential It's fixing code that was not working before, should create any new issue Pairing works and I can mount the phone using iFuse. iPhone 4S, iOS 8.1 libimobiledevice is probably outdated. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: ideviceinstaller 1.0.1-0.2build1 ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4 Uname: Linux 3.16.0-24-generic x86_64 ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CurrentDesktop: KDE Date: Mon Nov 3 09:33:21 2014 InstallationDate: Installed on 2014-11-02 (0 days ago) InstallationMedia: Kubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) SourcePackage: ideviceinstaller UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libimobiledevice/+bug/1388743/+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 1581066] Re: [desktop] Display doesn't dim or turn off on inactivity
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: repowerd (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to powerd in Ubuntu. https://bugs.launchpad.net/bugs/1581066 Title: [desktop] Display doesn't dim or turn off on inactivity Status in powerd package in Ubuntu: Confirmed Status in repowerd package in Ubuntu: Confirmed Status in unity8 package in Ubuntu: Incomplete Bug description: When leaving my laptop idle, the screen stays at a constant brightness forever. I have System Settings configured to "Lock when idle" after 2 minutes, but that doesn't happen. Adjusting the screen brightness manually doesn't do anything. Expectation: Screen dims after a short period of time, and turns off (and locks) after the configured 2 minutes of inactivity. Actual: Screen stays on and at the same brightness indefinitely. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/powerd/+bug/1581066/+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 1630906] Re: QML segfault on arm64 due to builder kernel change
This happens in launchpad builders. I don't think it is possible for us to log in and run apport-collect. Also there are many logs linked in the bug description. Putting back to Confirmed. ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtdeclarative-opensource- src in Ubuntu. https://bugs.launchpad.net/bugs/1630906 Title: QML segfault on arm64 due to builder kernel change Status in linux package in Ubuntu: Confirmed Status in online-accounts-api package in Ubuntu: New Status in qmenumodel package in Ubuntu: New Status in qtdeclarative-opensource-src package in Ubuntu: New Status in ubuntu-push-qml package in Ubuntu: New Status in unity8 package in Ubuntu: New Status in webbrowser-app package in Ubuntu: New Bug description: Builders were changed from wily to xenial (4.4) kernel for arm64, and likely due to this the following kind of errors started happening: https://launchpadlibrarian.net/288487533/buildlog_ubuntu-yakkety-arm64 .ubuntu-push-qml_0.1+15.10.20150826.1-0ubuntu2_BUILDING.txt.gz They happen when executing QML code. I've ruled out that reverting to previous qtbase and qtdeclarative versions don't affect this, so it's not coming from a Qt change. I've also verified there's no problem eg on our Bq tablet running the same tests on xenial+overlay. There are currently no found changes at least in Qt upstream to backport arm64 related fixes. Cause is unknown. But the same problem is there on vivid, xenial and yakkety builds: https://launchpadlibrarian.net/288516465/buildlog_ubuntu-yakkety-arm64.online-accounts-api_0.1+16.10.20161006.1-0ubuntu1_BUILDING.txt.gz https://launchpadlibrarian.net/288515705/buildlog_ubuntu-xenial-arm64.online-accounts-api_0.1+16.04.20161006.1-0ubuntu1_BUILDING.txt.gz https://launchpadlibrarian.net/288515510/buildlog_ubuntu-vivid-arm64.online-accounts-api_0.1+15.04.20161006.1-0ubuntu1_BUILDING.txt.gz This means it does not matter if it's Qt 5.4 or 5.6, GCC 4.9, 5 or 6, or glibc 2.21, 2.23 or 2.24. More logs from affected packages: https://launchpadlibrarian.net/288493058/buildlog_ubuntu-yakkety-arm64.qtdeclarative-opensource-src_5.6.1-7ubuntu3~1_BUILDING.txt.gz https://launchpadlibrarian.net/288347391/buildlog_ubuntu-xenial-arm64.webbrowser-app_0.23+16.04.20161005.1-0ubuntu1_BUILDING.txt.gz https://launchpadlibrarian.net/288385063/buildlog_ubuntu-vivid-arm64.qmenumodel_0.2.10+15.04.20161005.1-0ubuntu1_BUILDING.txt.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1630906/+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 1630724] Re: Application remains on unity launcher after uninstallation
This has been introduced by the recent switch from using .dekstop files to using u-a-l to get information about items. The old code would remove an app if the .desktop file goes away. I suspect u-a-l keeps information about the app around for while which makes the code think it is still installed. ** Changed in: unity8 (Ubuntu) Assignee: (unassigned) => Michael Terry (mterry) ** Changed in: qtmir (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1630724 Title: Application remains on unity launcher after uninstallation Status in Canonical System Image: New Status in qtmir package in Ubuntu: Invalid Status in unity8 package in Ubuntu: New Bug description: I'm not sure if this is reproducible but this is what I did: 1. Enter Ubuntu One account details through system settings -> online accounts. 2. Open the app store from the main app scope. 3. Install Popey's Youtube app and then "open" it from the app store page. 4. Play around in Youtube app for a bit. 5. Go to the main app scope and long press the Youtube icon to open the store page. 6. Uninstall the app. 7. Search the store for another Youtube app and install it. (This time I installed the top rated one.) 8. Again, open it by pressing "open" on the store page. 9. Swipe the left edge to open the app switcher. At this point I have two Youtube icons on the switcher. One corresponds to the first youtube app, now uninstalled. If I press it, I see a low resolution screenshot of that app. I can't interact with it though, and if I tap the screen it flickers between the screenshot and another app. Next I plugged in a keyboard and mouse, activating desktop mode. The ghost youtube app now brings up a black window with "youtube" in the middle in white text. The close button on the window has no effect. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1630724/+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 1630877] Re: 1:4.2.6.p3+dfsg-1ubuntu3.11 - OPENSSL_1.0.0 not defined in file libcrypto.so.1.0.0
Running into the same issue on 12.04: $ ldd /usr/bin/ntpq linux-vdso.so.1 => (0x7fff76bc9000) libopts.so.25 => /usr/lib/libopts.so.25 (0x7fabe42dd000) libedit.so.2 => /usr/lib/x86_64-linux-gnu/libedit.so.2 (0x7fabe40b6000) libcrypto.so.1.0.0 => /lib/x86_64-linux-gnu/libcrypto.so.1.0.0 (0x7fabe3cdb000) librt.so.1 => /lib/x86_64-linux-gnu/librt.so.1 (0x7fabe3ad3000) libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7fabe3715000) libbsd.so.0 => /lib/x86_64-linux-gnu/libbsd.so.0 (0x7fabe3508000) libtinfo.so.5 => /lib/x86_64-linux-gnu/libtinfo.so.5 (0x7fabe32e1000) libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x7fabe30dd000) libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x7fabe2ebf000) /lib64/ld-linux-x86-64.so.2 (0x7fabe473c000) $ apt-cache policy openssl openssl: Installed: 1.0.1f-1ubuntu2.8 Candidate: 1.0.1f-1ubuntu2.8 Version table: *** 1.0.1f-1ubuntu2.8 0 100 /var/lib/dpkg/status 1.0.1-4ubuntu5.38 0 500 http://security.ubuntu.com/ubuntu/ precise-security/main amd64 Packages $ apt-cache policy libssl1.0.0 libssl1.0.0: Installed: 1.0.1f-1ubuntu2.8 Candidate: 1.0.1f-1ubuntu2.8 Version table: *** 1.0.1f-1ubuntu2.8 0 100 /var/lib/dpkg/status 1.0.1-4ubuntu5.38 0 500 http://security.ubuntu.com/ubuntu/ precise-security/main amd64 Packages -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ntp in Ubuntu. https://bugs.launchpad.net/bugs/1630877 Title: 1:4.2.6.p3+dfsg-1ubuntu3.11 - OPENSSL_1.0.0 not defined in file libcrypto.so.1.0.0 Status in ntp package in Ubuntu: Incomplete Bug description: Getting error after upgrade in 12.04 LTS (3.2.0-23-virtual) - ntpq: relocation error: ntpq: symbol CRYPTO_memcmp, version OPENSSL_1.0.0 not defined in file libcrypto.so.1.0.0 with link time reference ntpd not starting after the upgrade. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1630877/+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
Re: [Touch-packages] [Bug 1630834] Re: tracker-extract crashed with SIGABRT in raise()
*** This bug is a duplicate of bug 1543354 *** https://bugs.launchpad.net/bugs/1543354 When I attempted to see this Bug Report(1543354), I got an error message: Lost something? This page does not exist, or you may not have permission to see it. If you have been to this page before, it is possible it has been removed. Check that you are logged in with the correct account, or that you entered the address correctly, or search for it: On Oct 5, 2016 22:35, "Apport retracing service" <1630...@bugs.launchpad.net> wrote: > *** This bug is a duplicate of bug 1543354 *** > https://bugs.launchpad.net/bugs/1543354 > > Thank you for taking the time to report this crash and helping to make > this software better. This particular crash has already been reported > and is a duplicate of bug #1543354, so is being marked as such. Please > look at the other bug report to see if there is any missing information > that you can provide, or to see if there is a workaround for the bug. > Additionally, any further discussion regarding the bug should occur in > the other report. Please continue to report any other bugs you may > find. > > ** Attachment removed: "CoreDump.gz" >https://bugs.launchpad.net/bugs/1630834/+attachment/ > 479/+files/CoreDump.gz > > ** Attachment removed: "Disassembly.txt" >https://bugs.launchpad.net/bugs/1630834/+attachment/ > 4755561/+files/Disassembly.txt > > ** Attachment removed: "ProcMaps.txt" >https://bugs.launchpad.net/bugs/1630834/+attachment/ > 4755563/+files/ProcMaps.txt > > ** Attachment removed: "ProcStatus.txt" >https://bugs.launchpad.net/bugs/1630834/+attachment/ > 4755564/+files/ProcStatus.txt > > ** Attachment removed: "Registers.txt" >https://bugs.launchpad.net/bugs/1630834/+attachment/ > 4755565/+files/Registers.txt > > ** Attachment removed: "Stacktrace.txt" >https://bugs.launchpad.net/bugs/1630834/+attachment/ > 4755566/+files/Stacktrace.txt > > ** Attachment removed: "ThreadStacktrace.txt" >https://bugs.launchpad.net/bugs/1630834/+attachment/4755567/+files/ > ThreadStacktrace.txt > > ** This bug has been marked a duplicate of private bug 1543354 > > ** Information type changed from Private to Public > > ** Tags removed: need-amd64-retrace > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1630834 > > Title: > tracker-extract crashed with SIGABRT in raise() > > Status in tracker package in Ubuntu: > New > > Bug description: > Every time that I sign into Ubuntu 16.10 Gnome I get this Tracker > crashed error. > > matthew@stacy-desktop:~$ lsb_release -rd > Description:Ubuntu Yakkety Yak (development branch) > Release:16.10 > matthew@stacy-desktop:~$ uname -r > 4.8.0-19-generic > matthew@stacy-desktop:~$ uname -a > Linux stacy-desktop 4.8.0-19-generic #21-Ubuntu SMP Thu Sep 29 19:39:23 > UTC 2016 x86_64 x86_64 x86_64 GNU/Linux > matthew@stacy-desktop:~$ > > matthew@stacy-desktop:~$ apt-cache policy tracker > tracker: > Installed: 1.10.0-1ubuntu1 > Candidate: 1.10.0-1ubuntu1 > Version table: >*** 1.10.0-1ubuntu1 500 > 500 http://archive.ubuntu.com/ubuntu yakkety/universe amd64 > Packages > 100 /var/lib/dpkg/status > matthew@stacy-desktop:~$ > > ProblemType: Crash > DistroRelease: Ubuntu 16.10 > Package: tracker-extract 1.10.0-1ubuntu1 > ProcVersionSignature: Ubuntu 4.8.0-19.21-generic 4.8.0-rc8 > Uname: Linux 4.8.0-19-generic x86_64 > NonfreeKernelModules: zfs zunicode zcommon znvpair zavl nvidia_uvm > nvidia_drm nvidia_modeset nvidia > ApportVersion: 2.20.3-0ubuntu7 > Architecture: amd64 > CrashCounter: 1 > CurrentDesktop: KDE > Date: Wed Oct 5 14:35:26 2016 > ExecutablePath: /usr/lib/tracker/tracker-extract > InstallationDate: Installed on 2014-06-01 (857 days ago) > InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 > (20140417) > ProcCmdline: /usr/lib/tracker/tracker-extract > ProcEnviron: >PATH=(custom, user) >XDG_RUNTIME_DIR= >LANG=en_US.UTF-8 >SHELL=/bin/bash > Signal: 6 > SourcePackage: tracker > StacktraceTop: >raise () from /lib/x86_64-linux-gnu/libc.so.6 >abort () from /lib/x86_64-linux-gnu/libc.so.6 >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/libgstaudio-1.0.so.0 > Title: tracker-extract crashed with SIGABRT in raise() > UpgradeStatus: Upgraded to yakkety on 2016-09-30 (5 days ago) > UserGroups: adm cdrom dip kismet libvirt libvirtd lpadmin mythtv netdev > plugdev sambashare sudo > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/tracker/+bug/ > 1630834/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tracker in Ubuntu. https
[Touch-packages] [Bug 1502145] Re: Apps can keep screen lit permanently
The original report for the browser was closed some time ago so I suggest we need a new bug. Per comment #27 this may be a new behavior with the new repowered in ota13. (I added lp:1630986) Per comment #25 I think this is actually functioning as intended, if an app sets display on and is an active app we honor it. What is missing IMO is any indication that this is the state of the display. Also would be nice to add display on to the app permissions controlled via settings.(lp:1630989) ** No longer affects: qtmir (Ubuntu) ** No longer affects: unity-system-compositor (Ubuntu) ** Changed in: canonical-devices-system-image Status: Confirmed => Fix Released ** No longer affects: unity8 (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-system-compositor in Ubuntu. https://bugs.launchpad.net/bugs/1502145 Title: Apps can keep screen lit permanently Status in Canonical System Image: Fix Released Status in Oxide: Fix Released Status in Oxide 1.10 series: Fix Released Bug description: rc-proposed, r140, krillin There are times when it seems the display blanking policy stops working and the display stays on until I press the power button. Steps to reproduce: * install and start Siete * put it in background Expected outcome: * the display is switched off after a predetermined amount of time Actual outcome: * the display stays on forever == Now that apps can request the screen to stay on, they can do so regardless of whether they're focused/visible or not. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1502145/+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 1630877] Re: 1:4.2.6.p3+dfsg-1ubuntu3.11 - OPENSSL_1.0.0 not defined in file libcrypto.so.1.0.0
It looks like you're using an openssl package that wasn't built for Ubuntu 12.04 LTS. You'll need to rebuild ntp for your custom openssl version, or use the openssl package that comes from Ubuntu 12.04 LTS. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ntp in Ubuntu. https://bugs.launchpad.net/bugs/1630877 Title: 1:4.2.6.p3+dfsg-1ubuntu3.11 - OPENSSL_1.0.0 not defined in file libcrypto.so.1.0.0 Status in ntp package in Ubuntu: Incomplete Bug description: Getting error after upgrade in 12.04 LTS (3.2.0-23-virtual) - ntpq: relocation error: ntpq: symbol CRYPTO_memcmp, version OPENSSL_1.0.0 not defined in file libcrypto.so.1.0.0 with link time reference ntpd not starting after the upgrade. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1630877/+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 1470599] Re: Stuck mountall inside container
Closing as 1.1.2 has long been out of support and we've not heard of anything like that on more recent Ubuntu. ** Changed in: lxc (Ubuntu) Status: Confirmed => Invalid ** Changed in: lxc (Ubuntu) Status: Invalid => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1470599 Title: Stuck mountall inside container Status in lxc package in Ubuntu: Won't Fix Bug description: trusty lxc 1.1.2-0ubuntu3~cloud0 kernel Linux ambipom 3.13.0-55-generic #94-Ubuntu SMP Thu Jun 18 00:27:10 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux All processes running on the container: 34700 ?Ss 0:00 [lxc monitor] /var/lib/lxc juju-machine-3-lxc-1 34729 ?Ss 0:00 \_ /sbin/init 34789 ?S 0:00 \_ @sbin/plymouthd --mode=boot --attach-to-session 34797 ?Ss 0:00 \_ plymouth-upstart-bridge 34803 ?S 0:00 \_ mountall --daemon 35368 ?S 0:00 \_ upstart-socket-bridge --daemon 36248 ?Ss 0:00 \_ dhclient -1 -v -pf /run/dhclient.eth0.pid -lf /var/lib/dhcp/dhclient.eth0.leases eth0 Several other containers on the same host started up just fine. If mountall is killed and restarted from the command line with verbose and debug flags, this is the output: root@juju-machine-3-lxc-1:~# mountall -v --debug Connected to Plymouth parse_filesystems: reading filesystems parse_filesystems: sysfs (nodev) parse_filesystems: rootfs (nodev) parse_filesystems: ramfs (nodev) parse_filesystems: bdev (nodev) parse_filesystems: proc (nodev) parse_filesystems: cgroup (nodev) parse_filesystems: cpuset (nodev) parse_filesystems: tmpfs (nodev) parse_filesystems: devtmpfs (nodev) parse_filesystems: debugfs (nodev) parse_filesystems: securityfs (nodev) parse_filesystems: sockfs (nodev) parse_filesystems: pipefs (nodev) parse_filesystems: anon_inodefs (nodev) parse_filesystems: devpts (nodev) parse_filesystems: ext3 parse_filesystems: ext2 parse_filesystems: ext4 parse_filesystems: hugetlbfs (nodev) parse_filesystems: vfat parse_filesystems: ecryptfs (nodev) parse_filesystems: fuseblk parse_filesystems: fuse (nodev) parse_filesystems: fusectl (nodev) parse_filesystems: pstore (nodev) parse_filesystems: efivarfs (nodev) parse_filesystems: mqueue (nodev) parse_filesystems: xfs parse_fstab: updating from /lib/init/fstab update_mount: /: / /dev/root rootfs defaults check update_mount: /proc: /proc none proc nodev,noexec,nosuid update_mount: /proc/sys/fs/binfmt_misc: /proc/sys/fs/binfmt_misc none binfmt_misc nodev,noexec,nosuid,optional update_mount: /sys: /sys none sysfs nodev,noexec,nosuid update_mount: /sys/fs/cgroup: /sys/fs/cgroup none tmpfs optional,uid=0,gid=0,mode=0755,size=1024 update_mount: /sys/fs/fuse/connections: /sys/fs/fuse/connections none fusectl optional update_mount: /sys/kernel/debug: /sys/kernel/debug none debugfs optional update_mount: /sys/kernel/security: /sys/kernel/security none securityfs optional update_mount: /sys/firmware/efi/efivars: /sys/firmware/efi/efivars none efivarfs optional update_mount: /spu: /spu none spufs gid=spu,optional update_mount: /dev: /dev none devtmpfs,tmpfs mode=0755 update_mount: /dev/pts: /dev/pts none devpts noexec,nosuid,gid=tty,mode=0620 update_mount: /tmp: /tmp none none defaults update_mount: /run: /run none tmpfs noexec,nosuid,size=10%,mode=0755 update_mount: /run/lock: /run/lock none tmpfs nodev,noexec,nosuid,size=5242880 update_mount: /run/shm: /run/shm none tmpfs nosuid,nodev update_mount: /run/user: /run/user none tmpfs nodev,noexec,nosuid,size=104857600,mode=0755 update_mount: /sys/fs/pstore: /sys/fs/pstore none pstore optional parse_fstab: updating from /etc/fstab update_mount: /: / LABEL=cloudimg-rootfs ext4 defaults parse_mountinfo_file: updating mounts update_mount: /: / /dev/disk/by-uuid/7d38a3ed-8f5b-49d4-8087-b1573a17bb98 ext4 defaults update_mount: /dev: /dev none tmpfs mode=0755 update_mount: /proc: /proc proc proc nodev,noexec,nosuid update_mount: /proc/sys/net: /proc/sys/net proc proc rw,nosuid,nodev,noexec,relatime,rw update_mount: /proc/sys: /proc/sys proc proc ro,nosuid,nodev,noexec,relatime,rw update_mount: /proc/sysrq-trigger: /proc/sysrq-trigger proc proc ro,nosuid,nodev,noexec,relatime,rw update_mount: /sys: /sys sysfs sysfs nodev,noexec,nosuid update_mount: /sys: /sys sysfs sysfs nodev,noexec,nosuid update_mount: /sys/devices/virtual/net: /sys/devices/virtual/net sysfs sysfs rw,relatime,rw update_mount: /sys/devices/virtual/net: /sys/devices/virtual/net sysfs sysfs rw,relatime,rw update_mount: /sys/fs/fuse/connections: /sys/fs/fuse/connections none fusectl optional update_mount: /sys/kernel/debug: /sys/kernel/debug none debugfs optional update_mount: /sys
[Touch-packages] [Bug 1631003] [NEW] OSK is slow to appear the first time
Public bug reported: If you boot a phone and go to log in at the passcode entry, you may have to wait a few seconds for the OSK to appear. This is partially because (A) the OSK takes a while to start and (B) we only start maliit-server *after* unity8 starts. Can we fix either A or B? B seems to be because the OSK assumes u8 and its Mir server already exists, but could we fix the OSK to wait for u8 to appear? Or just make maliit/OSK faster? ** Affects: ubuntu-keyboard (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-keyboard in Ubuntu. https://bugs.launchpad.net/bugs/1631003 Title: OSK is slow to appear the first time Status in ubuntu-keyboard package in Ubuntu: New Bug description: If you boot a phone and go to log in at the passcode entry, you may have to wait a few seconds for the OSK to appear. This is partially because (A) the OSK takes a while to start and (B) we only start maliit-server *after* unity8 starts. Can we fix either A or B? B seems to be because the OSK assumes u8 and its Mir server already exists, but could we fix the OSK to wait for u8 to appear? Or just make maliit/OSK faster? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-keyboard/+bug/1631003/+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 1631010] [NEW] please add a cmdline option to chose between ipv4, ipv6, or dual-stack network boot
Public bug reported: Right now, I can boot with "ip=hostname:BOOTIF" in the kernel commandline, and (after bug 1621507), I get whatever it came up with for ipv4 and ipv6. If for nothing more than testing on a dual-stack environment, it would be nice to be able to force that to try both (current behavior, and an excellent default), only try IPv4, or only IPv6. NOT something that needs to be fixed before yakkety, but would be nice to eventually get back to xenial. ** Affects: initramfs-tools (Ubuntu) Importance: Wishlist Status: New ** Changed in: initramfs-tools (Ubuntu) Importance: Undecided => Wishlist -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1631010 Title: please add a cmdline option to chose between ipv4, ipv6, or dual-stack network boot Status in initramfs-tools package in Ubuntu: New Bug description: Right now, I can boot with "ip=hostname:BOOTIF" in the kernel commandline, and (after bug 1621507), I get whatever it came up with for ipv4 and ipv6. If for nothing more than testing on a dual-stack environment, it would be nice to be able to force that to try both (current behavior, and an excellent default), only try IPv4, or only IPv6. NOT something that needs to be fixed before yakkety, but would be nice to eventually get back to xenial. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1631010/+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 1630906] Re: QML segfault on arm64 due to builder kernel change
I got a temporary access (now revoked) to an arm64 box where I could reproduce the segfault by running qmlplugindump. Here's the backtrace: QV4::Object::defineReadonlyProperty (this=this@entry=0x0, name=0x450bf8, value=...) at jsruntime/qv4object.cpp:184 184 jsruntime/qv4object.cpp: No such file or directory. (gdb) bt #0 QV4::Object::defineReadonlyProperty (this=this@entry=0x0, name=0x450bf8, value=...) at jsruntime/qv4object.cpp:184 #1 0xb7a9f774 in QV4::ObjectPrototype::init (this=0x0, v4=v4@entry=0x4508f0, ctor=0x0) at jsruntime/qv4objectproto.cpp:84 #2 0xb7a5a20c in QV4::ExecutionEngine::ExecutionEngine (this=0x4508f0, factory=) at jsruntime/qv4engine.cpp:367 #3 0xb7b86d94 in QV8Engine::QV8Engine (this=0x4502a0, qq=) at qml/v8/qv8engine.cpp:144 #4 0xb7a25de8 in QJSEngine::QJSEngine (this=0xf298, dd=..., parent=) at jsapi/qjsengine.cpp:201 #5 0xb7af738c in QQmlEngine::QQmlEngine (this=0xf298, parent=0x0) at qml/qqmlengine.cpp:927 #6 0x004067b8 in main (argc=0, argv=) at main.cpp:1041 Where the code in question is http://code.qt.io/cgit/qt/qtdeclarative.git/tree/src/qml/jsruntime/qv4object.cpp?h=5.6.1#n184 I hope that helps somehow. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtdeclarative-opensource- src in Ubuntu. https://bugs.launchpad.net/bugs/1630906 Title: QML segfault on arm64 due to builder kernel change Status in linux package in Ubuntu: Confirmed Status in online-accounts-api package in Ubuntu: New Status in qmenumodel package in Ubuntu: New Status in qtdeclarative-opensource-src package in Ubuntu: New Status in ubuntu-push-qml package in Ubuntu: New Status in unity8 package in Ubuntu: New Status in webbrowser-app package in Ubuntu: New Bug description: Builders were changed from wily to xenial (4.4) kernel for arm64, and likely due to this the following kind of errors started happening: https://launchpadlibrarian.net/288487533/buildlog_ubuntu-yakkety-arm64 .ubuntu-push-qml_0.1+15.10.20150826.1-0ubuntu2_BUILDING.txt.gz They happen when executing QML code. I've ruled out that reverting to previous qtbase and qtdeclarative versions don't affect this, so it's not coming from a Qt change. I've also verified there's no problem eg on our Bq tablet running the same tests on xenial+overlay. There are currently no found changes at least in Qt upstream to backport arm64 related fixes. Cause is unknown. But the same problem is there on vivid, xenial and yakkety builds: https://launchpadlibrarian.net/288516465/buildlog_ubuntu-yakkety-arm64.online-accounts-api_0.1+16.10.20161006.1-0ubuntu1_BUILDING.txt.gz https://launchpadlibrarian.net/288515705/buildlog_ubuntu-xenial-arm64.online-accounts-api_0.1+16.04.20161006.1-0ubuntu1_BUILDING.txt.gz https://launchpadlibrarian.net/288515510/buildlog_ubuntu-vivid-arm64.online-accounts-api_0.1+15.04.20161006.1-0ubuntu1_BUILDING.txt.gz This means it does not matter if it's Qt 5.4 or 5.6, GCC 4.9, 5 or 6, or glibc 2.21, 2.23 or 2.24. More logs from affected packages: https://launchpadlibrarian.net/288493058/buildlog_ubuntu-yakkety-arm64.qtdeclarative-opensource-src_5.6.1-7ubuntu3~1_BUILDING.txt.gz https://launchpadlibrarian.net/288347391/buildlog_ubuntu-xenial-arm64.webbrowser-app_0.23+16.04.20161005.1-0ubuntu1_BUILDING.txt.gz https://launchpadlibrarian.net/288385063/buildlog_ubuntu-vivid-arm64.qmenumodel_0.2.10+15.04.20161005.1-0ubuntu1_BUILDING.txt.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1630906/+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 1630906] Re: QML segfault on arm64 due to builder kernel change
For completeness, also the other copy-pastes I made: Thread 1 "qmlplugindump" received signal SIGSEGV, Segmentation fault. QV4::Object::defineReadonlyProperty (this=this@entry=0x0, name=0x450bf8, value=...) at jsruntime/qv4object.cpp:184 184 jsruntime/qv4object.cpp: No such file or directory. (gdb) info frame Stack level 0, frame at 0xee00: pc = 0xb7a4 in QV4::Object::defineReadonlyProperty (jsruntime/qv4object.cpp:184); saved pc = 0xb7a9f774 called by frame at 0xee90 source language c++. Arglist at 0xedb0, args: this=this@entry=0x0, name=0x450bf8, value=... Locals at 0xedb0, Previous frame's sp is 0xee00 Saved registers: x19 at 0xedc0, x20 at 0xedc8, x21 at 0xedd0, x29 at 0xedb0, x30 at 0xedb8 (gdb) up #1 0xb7a9f774 in QV4::ObjectPrototype::init (this=0x0, v4=v4@entry=0x4508f0, ctor=0x0) at jsruntime/qv4objectproto.cpp:84 84 jsruntime/qv4objectproto.cpp: No such file or directory. (gdb) info frame Stack level 1, frame at 0xee90: pc = 0xb7a9f774 in QV4::ObjectPrototype::init (jsruntime/qv4objectproto.cpp:84); saved pc = 0xb7a5a20c called by frame at 0xefe0, caller of frame at 0xee00 source language c++. Arglist at 0xee00, args: this=0x0, v4=v4@entry=0x4508f0, ctor=0x0 Locals at 0xee00, Previous frame's sp is 0xee90 Saved registers: x19 at 0xee10, x20 at 0xee18, x21 at 0xee20, x22 at 0xee28, x23 at 0xee30, x24 at 0xee38, x25 at 0xee40, x26 at 0xee48, x27 at 0xee50, x28 at 0xee58, x29 at 0xee00, x30 at 0xee08 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtdeclarative-opensource- src in Ubuntu. https://bugs.launchpad.net/bugs/1630906 Title: QML segfault on arm64 due to builder kernel change Status in linux package in Ubuntu: Confirmed Status in online-accounts-api package in Ubuntu: New Status in qmenumodel package in Ubuntu: New Status in qtdeclarative-opensource-src package in Ubuntu: New Status in ubuntu-push-qml package in Ubuntu: New Status in unity8 package in Ubuntu: New Status in webbrowser-app package in Ubuntu: New Bug description: Builders were changed from wily to xenial (4.4) kernel for arm64, and likely due to this the following kind of errors started happening: https://launchpadlibrarian.net/288487533/buildlog_ubuntu-yakkety-arm64 .ubuntu-push-qml_0.1+15.10.20150826.1-0ubuntu2_BUILDING.txt.gz They happen when executing QML code. I've ruled out that reverting to previous qtbase and qtdeclarative versions don't affect this, so it's not coming from a Qt change. I've also verified there's no problem eg on our Bq tablet running the same tests on xenial+overlay. There are currently no found changes at least in Qt upstream to backport arm64 related fixes. Cause is unknown. But the same problem is there on vivid, xenial and yakkety builds: https://launchpadlibrarian.net/288516465/buildlog_ubuntu-yakkety-arm64.online-accounts-api_0.1+16.10.20161006.1-0ubuntu1_BUILDING.txt.gz https://launchpadlibrarian.net/288515705/buildlog_ubuntu-xenial-arm64.online-accounts-api_0.1+16.04.20161006.1-0ubuntu1_BUILDING.txt.gz https://launchpadlibrarian.net/288515510/buildlog_ubuntu-vivid-arm64.online-accounts-api_0.1+15.04.20161006.1-0ubuntu1_BUILDING.txt.gz This means it does not matter if it's Qt 5.4 or 5.6, GCC 4.9, 5 or 6, or glibc 2.21, 2.23 or 2.24. More logs from affected packages: https://launchpadlibrarian.net/288493058/buildlog_ubuntu-yakkety-arm64.qtdeclarative-opensource-src_5.6.1-7ubuntu3~1_BUILDING.txt.gz https://launchpadlibrarian.net/288347391/buildlog_ubuntu-xenial-arm64.webbrowser-app_0.23+16.04.20161005.1-0ubuntu1_BUILDING.txt.gz https://launchpadlibrarian.net/288385063/buildlog_ubuntu-vivid-arm64.qmenumodel_0.2.10+15.04.20161005.1-0ubuntu1_BUILDING.txt.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1630906/+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 1630906] Re: QML segfault on arm64 due to builder kernel change
Correction to the code url: http://code.qt.io/cgit/qt/qtdeclarative.git/tree/src/qml/jsruntime/qv4object.cpp?h=5.6.2#n184 (5.6.1 branch doesn't exist over there, but code seems unchanged) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtdeclarative-opensource- src in Ubuntu. https://bugs.launchpad.net/bugs/1630906 Title: QML segfault on arm64 due to builder kernel change Status in linux package in Ubuntu: Confirmed Status in online-accounts-api package in Ubuntu: New Status in qmenumodel package in Ubuntu: New Status in qtdeclarative-opensource-src package in Ubuntu: New Status in ubuntu-push-qml package in Ubuntu: New Status in unity8 package in Ubuntu: New Status in webbrowser-app package in Ubuntu: New Bug description: Builders were changed from wily to xenial (4.4) kernel for arm64, and likely due to this the following kind of errors started happening: https://launchpadlibrarian.net/288487533/buildlog_ubuntu-yakkety-arm64 .ubuntu-push-qml_0.1+15.10.20150826.1-0ubuntu2_BUILDING.txt.gz They happen when executing QML code. I've ruled out that reverting to previous qtbase and qtdeclarative versions don't affect this, so it's not coming from a Qt change. I've also verified there's no problem eg on our Bq tablet running the same tests on xenial+overlay. There are currently no found changes at least in Qt upstream to backport arm64 related fixes. Cause is unknown. But the same problem is there on vivid, xenial and yakkety builds: https://launchpadlibrarian.net/288516465/buildlog_ubuntu-yakkety-arm64.online-accounts-api_0.1+16.10.20161006.1-0ubuntu1_BUILDING.txt.gz https://launchpadlibrarian.net/288515705/buildlog_ubuntu-xenial-arm64.online-accounts-api_0.1+16.04.20161006.1-0ubuntu1_BUILDING.txt.gz https://launchpadlibrarian.net/288515510/buildlog_ubuntu-vivid-arm64.online-accounts-api_0.1+15.04.20161006.1-0ubuntu1_BUILDING.txt.gz This means it does not matter if it's Qt 5.4 or 5.6, GCC 4.9, 5 or 6, or glibc 2.21, 2.23 or 2.24. More logs from affected packages: https://launchpadlibrarian.net/288493058/buildlog_ubuntu-yakkety-arm64.qtdeclarative-opensource-src_5.6.1-7ubuntu3~1_BUILDING.txt.gz https://launchpadlibrarian.net/288347391/buildlog_ubuntu-xenial-arm64.webbrowser-app_0.23+16.04.20161005.1-0ubuntu1_BUILDING.txt.gz https://launchpadlibrarian.net/288385063/buildlog_ubuntu-vivid-arm64.qmenumodel_0.2.10+15.04.20161005.1-0ubuntu1_BUILDING.txt.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1630906/+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 1550740] Re: networkmanager segfault on startup
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: network-manager (Ubuntu) Status: New => Confirmed -- 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/1550740 Title: networkmanager segfault on startup Status in network-manager package in Ubuntu: Confirmed Bug description: NetworkManager[677]: segfault at 168 ip 004c39cd sp 7ffe4ff2c1c0 error 4 in NetworkManager[40+1bf000] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1550740/+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 1550740] Re: networkmanager segfault on startup
also happens to me randomly. any ideas? NetworkManager[837]: segfault at 4e8 ip 0046c7d0 sp 7ffec3967e20 error 4 in NetworkManager[40+2b9000] -- 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/1550740 Title: networkmanager segfault on startup Status in network-manager package in Ubuntu: Confirmed Bug description: NetworkManager[677]: segfault at 168 ip 004c39cd sp 7ffe4ff2c1c0 error 4 in NetworkManager[40+1bf000] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1550740/+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 1558018] Re: Scrolling of icons in Toolbar
** Branch linked: lp:~tpeeters/ubuntu-ui-toolkit/toolbarScroll -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1558018 Title: Scrolling of icons in Toolbar Status in Ubuntu UX: In Progress Status in ubuntu-ui-toolkit package in Ubuntu: In Progress Bug description: Currently, when the icons do not all fit in the toolbar, an overflow button is shown that shows an overflow popover/panel when clicked. This needs to be replaced by icon scrolling instead. See https://docs.google.com/document/d/1F-zD6CF8YFfA- nAtpdRniCqwUNJhSDJVFrRO76A1M-Q/edit UX solution: https://docs.google.com/document/edit?hgd=1&id=1F-zD6CF8YFfA-nAtpdRniCqwUNJhSDJVFrRO76A1M-Q#heading=h.w16v0yn510iy is this not what you need? https://docs.google.com/document/edit?hgd=1&id=1F-zD6CF8YFfA- nAtpdRniCqwUNJhSDJVFrRO76A1M-Q#heading=h.duaef4xy7sqv To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1558018/+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 1629009] Re: Does not work inside a snap due to hardcoded paths
** Branch linked: lp:~mterry/unity-scopes-shell/snap-root
** Changed in: unity-scopes-shell (Ubuntu)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu.
https://bugs.launchpad.net/bugs/1629009
Title:
Does not work inside a snap due to hardcoded paths
Status in address-book-app package in Ubuntu:
Fix Committed
Status in dialer-app package in Ubuntu:
New
Status in messaging-app package in Ubuntu:
New
Status in ubuntu-system-settings package in Ubuntu:
In Progress
Status in ubuntu-terminal-app package in Ubuntu:
New
Status in unity-scopes-api package in Ubuntu:
In Progress
Status in unity-scopes-shell package in Ubuntu:
In Progress
Status in unity8 package in Ubuntu:
In Progress
Status in webbrowser-app package in Ubuntu:
In Progress
Bug description:
Some apps can't find their main qml file. Error messages like:
"file:///build/messaging-app-gcXPE6/messaging-
app-0.1+16.04.20160831/src/qml/messaging-app.qml: File not found"
(in my case, the file was in /snap/unity8-session/x24/usr/share
/messaging-app/messaging-app.qml)
Seems due to code like the following in config.h.in. Probably needs
to consider the value of $SNAP or just be a little more forgiving.
inline bool isRunningInstalled() {
static bool installed = (QCoreApplication::applicationDirPath() ==
QDir(("@CMAKE_INSTALL_PREFIX@/@CMAKE_INSTALL_BINDIR@")).canonicalPath());
return installed;
}
inline QString messagingAppDirectory() {
if (isRunningInstalled()) {
return QString("@CMAKE_INSTALL_PREFIX@/@MESSAGING_APP_DIR@/");
} else {
return QString("@CMAKE_SOURCE_DIR@/src/qml/");
}
}
inline QString ubuntuPhonePluginPath() {
if (isRunningInstalled()) {
return QString::null;
} else {
return QString("@CMAKE_SOURCE_DIR@/");
}
}
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/address-book-app/+bug/1629009/+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 1630906] Re: QML segfault on arm64 due to builder kernel change
Albert pointed to https://codereview.qt-project.org/#/c/169892 -> https://bileto.ubuntu.com/#/ticket/2055 (xenial and yakkety currently building) I need to stop for today but if someone has time please check if 5.4 backport is possible. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtdeclarative-opensource- src in Ubuntu. https://bugs.launchpad.net/bugs/1630906 Title: QML segfault on arm64 due to builder kernel change Status in linux package in Ubuntu: Confirmed Status in online-accounts-api package in Ubuntu: New Status in qmenumodel package in Ubuntu: New Status in qtdeclarative-opensource-src package in Ubuntu: New Status in ubuntu-push-qml package in Ubuntu: New Status in unity8 package in Ubuntu: New Status in webbrowser-app package in Ubuntu: New Bug description: Builders were changed from wily to xenial (4.4) kernel for arm64, and likely due to this the following kind of errors started happening: https://launchpadlibrarian.net/288487533/buildlog_ubuntu-yakkety-arm64 .ubuntu-push-qml_0.1+15.10.20150826.1-0ubuntu2_BUILDING.txt.gz They happen when executing QML code. I've ruled out that reverting to previous qtbase and qtdeclarative versions don't affect this, so it's not coming from a Qt change. I've also verified there's no problem eg on our Bq tablet running the same tests on xenial+overlay. There are currently no found changes at least in Qt upstream to backport arm64 related fixes. Cause is unknown. But the same problem is there on vivid, xenial and yakkety builds: https://launchpadlibrarian.net/288516465/buildlog_ubuntu-yakkety-arm64.online-accounts-api_0.1+16.10.20161006.1-0ubuntu1_BUILDING.txt.gz https://launchpadlibrarian.net/288515705/buildlog_ubuntu-xenial-arm64.online-accounts-api_0.1+16.04.20161006.1-0ubuntu1_BUILDING.txt.gz https://launchpadlibrarian.net/288515510/buildlog_ubuntu-vivid-arm64.online-accounts-api_0.1+15.04.20161006.1-0ubuntu1_BUILDING.txt.gz This means it does not matter if it's Qt 5.4 or 5.6, GCC 4.9, 5 or 6, or glibc 2.21, 2.23 or 2.24. More logs from affected packages: https://launchpadlibrarian.net/288493058/buildlog_ubuntu-yakkety-arm64.qtdeclarative-opensource-src_5.6.1-7ubuntu3~1_BUILDING.txt.gz https://launchpadlibrarian.net/288347391/buildlog_ubuntu-xenial-arm64.webbrowser-app_0.23+16.04.20161005.1-0ubuntu1_BUILDING.txt.gz https://launchpadlibrarian.net/288385063/buildlog_ubuntu-vivid-arm64.qmenumodel_0.2.10+15.04.20161005.1-0ubuntu1_BUILDING.txt.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1630906/+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 1630724] Re: Application remains on unity launcher after uninstallation
** Changed in: unity8 (Ubuntu) Assignee: Michael Terry (mterry) => Michael Zanetti (mzanetti) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1630724 Title: Application remains on unity launcher after uninstallation Status in Canonical System Image: New Status in qtmir package in Ubuntu: Invalid Status in unity8 package in Ubuntu: New Bug description: I'm not sure if this is reproducible but this is what I did: 1. Enter Ubuntu One account details through system settings -> online accounts. 2. Open the app store from the main app scope. 3. Install Popey's Youtube app and then "open" it from the app store page. 4. Play around in Youtube app for a bit. 5. Go to the main app scope and long press the Youtube icon to open the store page. 6. Uninstall the app. 7. Search the store for another Youtube app and install it. (This time I installed the top rated one.) 8. Again, open it by pressing "open" on the store page. 9. Swipe the left edge to open the app switcher. At this point I have two Youtube icons on the switcher. One corresponds to the first youtube app, now uninstalled. If I press it, I see a low resolution screenshot of that app. I can't interact with it though, and if I tap the screen it flickers between the screenshot and another app. Next I plugged in a keyboard and mouse, activating desktop mode. The ghost youtube app now brings up a black window with "youtube" in the middle in white text. The close button on the window has no effect. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1630724/+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 1629009] Re: Does not work inside a snap due to hardcoded paths
** Changed in: ubuntu-system-settings (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu.
https://bugs.launchpad.net/bugs/1629009
Title:
Does not work inside a snap due to hardcoded paths
Status in address-book-app package in Ubuntu:
Fix Committed
Status in dialer-app package in Ubuntu:
New
Status in messaging-app package in Ubuntu:
New
Status in ubuntu-system-settings package in Ubuntu:
Fix Committed
Status in ubuntu-terminal-app package in Ubuntu:
New
Status in unity-scopes-api package in Ubuntu:
In Progress
Status in unity-scopes-shell package in Ubuntu:
In Progress
Status in unity8 package in Ubuntu:
In Progress
Status in webbrowser-app package in Ubuntu:
In Progress
Bug description:
Some apps can't find their main qml file. Error messages like:
"file:///build/messaging-app-gcXPE6/messaging-
app-0.1+16.04.20160831/src/qml/messaging-app.qml: File not found"
(in my case, the file was in /snap/unity8-session/x24/usr/share
/messaging-app/messaging-app.qml)
Seems due to code like the following in config.h.in. Probably needs
to consider the value of $SNAP or just be a little more forgiving.
inline bool isRunningInstalled() {
static bool installed = (QCoreApplication::applicationDirPath() ==
QDir(("@CMAKE_INSTALL_PREFIX@/@CMAKE_INSTALL_BINDIR@")).canonicalPath());
return installed;
}
inline QString messagingAppDirectory() {
if (isRunningInstalled()) {
return QString("@CMAKE_INSTALL_PREFIX@/@MESSAGING_APP_DIR@/");
} else {
return QString("@CMAKE_SOURCE_DIR@/src/qml/");
}
}
inline QString ubuntuPhonePluginPath() {
if (isRunningInstalled()) {
return QString::null;
} else {
return QString("@CMAKE_SOURCE_DIR@/");
}
}
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/address-book-app/+bug/1629009/+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 1552100] Re: Create .snap packages of core apps
** Changed in: ubuntu-filemanager-app Status: Triaged => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu. https://bugs.launchpad.net/bugs/1552100 Title: Create .snap packages of core apps Status in Canonical System Image: Opinion Status in Ubuntu Music App: Triaged Status in Ubuntu Notes app: Triaged Status in Telegram app: Triaged Status in Ubuntu Calculator App: New Status in Ubuntu Calendar App: In Progress Status in Ubuntu Clock App: Triaged Status in Ubuntu Document Viewer App: Triaged Status in Ubuntu File Manager App: In Progress Status in Ubuntu Shorts App: New Status in Ubuntu Terminal App: In Progress Status in Ubuntu Weather App: Triaged Status in webbrowser-app package in Ubuntu: Invalid Bug description: Move all packages and the system to .snap (snappy) To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1552100/+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 1629009] Re: Does not work inside a snap due to hardcoded paths
** Branch linked: lp:~renatofilho/ubuntu-filemanager-app/no-hardcoded-
icons
** Also affects: ubuntu-filemanager-app
Importance: Undecided
Status: New
** Changed in: ubuntu-filemanager-app
Status: New => In Progress
** Changed in: ubuntu-filemanager-app
Assignee: (unassigned) => Renato Araujo Oliveira Filho (renatofilho)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu.
https://bugs.launchpad.net/bugs/1629009
Title:
Does not work inside a snap due to hardcoded paths
Status in Ubuntu File Manager App:
In Progress
Status in address-book-app package in Ubuntu:
Fix Committed
Status in dialer-app package in Ubuntu:
New
Status in messaging-app package in Ubuntu:
New
Status in ubuntu-system-settings package in Ubuntu:
Fix Committed
Status in ubuntu-terminal-app package in Ubuntu:
New
Status in unity-scopes-api package in Ubuntu:
In Progress
Status in unity-scopes-shell package in Ubuntu:
In Progress
Status in unity8 package in Ubuntu:
In Progress
Status in webbrowser-app package in Ubuntu:
In Progress
Bug description:
Some apps can't find their main qml file. Error messages like:
"file:///build/messaging-app-gcXPE6/messaging-
app-0.1+16.04.20160831/src/qml/messaging-app.qml: File not found"
(in my case, the file was in /snap/unity8-session/x24/usr/share
/messaging-app/messaging-app.qml)
Seems due to code like the following in config.h.in. Probably needs
to consider the value of $SNAP or just be a little more forgiving.
inline bool isRunningInstalled() {
static bool installed = (QCoreApplication::applicationDirPath() ==
QDir(("@CMAKE_INSTALL_PREFIX@/@CMAKE_INSTALL_BINDIR@")).canonicalPath());
return installed;
}
inline QString messagingAppDirectory() {
if (isRunningInstalled()) {
return QString("@CMAKE_INSTALL_PREFIX@/@MESSAGING_APP_DIR@/");
} else {
return QString("@CMAKE_SOURCE_DIR@/src/qml/");
}
}
inline QString ubuntuPhonePluginPath() {
if (isRunningInstalled()) {
return QString::null;
} else {
return QString("@CMAKE_SOURCE_DIR@/");
}
}
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-filemanager-app/+bug/1629009/+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 1621507] Re: initramfs-tools configure_networking() fails to dhcp ipv6 addresses
This was resolved by switching away from klibc's ipconfig ** Changed in: klibc (Ubuntu Xenial) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu. https://bugs.launchpad.net/bugs/1621507 Title: initramfs-tools configure_networking() fails to dhcp ipv6 addresses Status in MAAS: Fix Released Status in initramfs-tools package in Ubuntu: Fix Released Status in isc-dhcp package in Ubuntu: Fix Released Status in klibc package in Ubuntu: Won't Fix Status in open-iscsi package in Ubuntu: Fix Released Status in initramfs-tools source package in Xenial: Fix Released Status in isc-dhcp source package in Xenial: Fix Released Status in klibc source package in Xenial: Won't Fix Status in open-iscsi source package in Xenial: Fix Released Status in klibc package in Debian: New Bug description: initramfs' configure_networking function uses ipconfig to configure the network. ipconfig does not support dhcpv6. See: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=627164 Related bugs: * bug 1229458: grub2 needed changes * bug 1621615: network not configured when ipv6 netbooted into cloud-init [Impact] It is not possible to netboot Ubuntu with a network-based root filesystem in an ipv6-only environment. Anyone wanting to netboot in an ipv6-only environment is affected. These uploads address this by replacing the one-off klibc dhcp client (IPv4-only) with the defacto standard isc-dhcp-client, and thereby provide both ipv6 and ipv4 DHCP configuration. [Test Case] See Bug 1229458. Configure radvd, dhcpd, and tftpd for your ipv6-only netbooting world. Pass the boot process an ipv6 address to talk to, and see it fail to configure the network. [Regression Potential] 1) This increases the uncompressed initramfs size by approximately 500KB, since isc-dhcp-client is added, but klibc is still needed for some other things, and is therefore present. On systems with a very small /boot partition, this could result in failure to upgrade the initramfs. 2) In at least some cases, DHCP network configuration shifts from klibc's ipconfig to isc-dhcp-client's dhclient. This should be of minimal risk, as isc-dhcp-client is in very very widespread use. In the event of a regression, network boot would fail, but the prior kernel should still be bootable. To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1621507/+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 1621507] Re: initramfs-tools configure_networking() fails to dhcp ipv6 addresses
** Changed in: maas Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu. https://bugs.launchpad.net/bugs/1621507 Title: initramfs-tools configure_networking() fails to dhcp ipv6 addresses Status in MAAS: Fix Released Status in initramfs-tools package in Ubuntu: Fix Released Status in isc-dhcp package in Ubuntu: Fix Released Status in klibc package in Ubuntu: Won't Fix Status in open-iscsi package in Ubuntu: Fix Released Status in initramfs-tools source package in Xenial: Fix Released Status in isc-dhcp source package in Xenial: Fix Released Status in klibc source package in Xenial: Won't Fix Status in open-iscsi source package in Xenial: Fix Released Status in klibc package in Debian: New Bug description: initramfs' configure_networking function uses ipconfig to configure the network. ipconfig does not support dhcpv6. See: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=627164 Related bugs: * bug 1229458: grub2 needed changes * bug 1621615: network not configured when ipv6 netbooted into cloud-init [Impact] It is not possible to netboot Ubuntu with a network-based root filesystem in an ipv6-only environment. Anyone wanting to netboot in an ipv6-only environment is affected. These uploads address this by replacing the one-off klibc dhcp client (IPv4-only) with the defacto standard isc-dhcp-client, and thereby provide both ipv6 and ipv4 DHCP configuration. [Test Case] See Bug 1229458. Configure radvd, dhcpd, and tftpd for your ipv6-only netbooting world. Pass the boot process an ipv6 address to talk to, and see it fail to configure the network. [Regression Potential] 1) This increases the uncompressed initramfs size by approximately 500KB, since isc-dhcp-client is added, but klibc is still needed for some other things, and is therefore present. On systems with a very small /boot partition, this could result in failure to upgrade the initramfs. 2) In at least some cases, DHCP network configuration shifts from klibc's ipconfig to isc-dhcp-client's dhclient. This should be of minimal risk, as isc-dhcp-client is in very very widespread use. In the event of a regression, network boot would fail, but the prior kernel should still be bootable. To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1621507/+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 1621507] Re: initramfs-tools configure_networking() fails to dhcp ipv6 addresses
This was resolved by switching away from klibc's ipconfig ** Changed in: klibc (Ubuntu) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu. https://bugs.launchpad.net/bugs/1621507 Title: initramfs-tools configure_networking() fails to dhcp ipv6 addresses Status in MAAS: Fix Released Status in initramfs-tools package in Ubuntu: Fix Released Status in isc-dhcp package in Ubuntu: Fix Released Status in klibc package in Ubuntu: Won't Fix Status in open-iscsi package in Ubuntu: Fix Released Status in initramfs-tools source package in Xenial: Fix Released Status in isc-dhcp source package in Xenial: Fix Released Status in klibc source package in Xenial: Won't Fix Status in open-iscsi source package in Xenial: Fix Released Status in klibc package in Debian: New Bug description: initramfs' configure_networking function uses ipconfig to configure the network. ipconfig does not support dhcpv6. See: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=627164 Related bugs: * bug 1229458: grub2 needed changes * bug 1621615: network not configured when ipv6 netbooted into cloud-init [Impact] It is not possible to netboot Ubuntu with a network-based root filesystem in an ipv6-only environment. Anyone wanting to netboot in an ipv6-only environment is affected. These uploads address this by replacing the one-off klibc dhcp client (IPv4-only) with the defacto standard isc-dhcp-client, and thereby provide both ipv6 and ipv4 DHCP configuration. [Test Case] See Bug 1229458. Configure radvd, dhcpd, and tftpd for your ipv6-only netbooting world. Pass the boot process an ipv6 address to talk to, and see it fail to configure the network. [Regression Potential] 1) This increases the uncompressed initramfs size by approximately 500KB, since isc-dhcp-client is added, but klibc is still needed for some other things, and is therefore present. On systems with a very small /boot partition, this could result in failure to upgrade the initramfs. 2) In at least some cases, DHCP network configuration shifts from klibc's ipconfig to isc-dhcp-client's dhclient. This should be of minimal risk, as isc-dhcp-client is in very very widespread use. In the event of a regression, network boot would fail, but the prior kernel should still be bootable. To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1621507/+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 1615021] Re: Unable to network boot Ubuntu 16.04 installer normally on Briggs
Just a note that the udev rules change from comment 6 seems to be necessary to reliably get an image booted under QEMU to bring up a getty on the serial console. What seems to happen without it is that udevd spends all its time running copies of 'readlink', and it doesn't get around to telling systemd about the presence of ttyAMA0 until after systemd's 1m30 timeout has expired and it gives up, reporting "Timed out waiting for device dev-ttyAMA0.device". (This happens most of the time on an emulated QEMU CPU and at least occasionally on one running with single-vcpu KVM, probably dependent on speed of the host hardware.) -- 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/1615021 Title: Unable to network boot Ubuntu 16.04 installer normally on Briggs Status in busybox package in Ubuntu: Fix Released Status in debian-installer package in Ubuntu: Invalid Status in systemd package in Ubuntu: Fix Released Status in busybox source package in Xenial: Won't Fix Status in debian-installer source package in Xenial: Invalid Status in systemd source package in Xenial: Fix Released Status in busybox source package in Yakkety: Fix Released Status in debian-installer source package in Yakkety: Invalid Status in systemd source package in Yakkety: Fix Released Bug description: == Comment: #7 - Guilherme Guaglianoni Piccoli - 2016-08-19 10:08:07 == The normal procedure to perform a Netboot installation of Ubuntu 16.04 is to download the latest vmlinux and initrd.gz files available, and kexec them with no parameters (at least in ppc64el). We're experiencing a strange issue in which the installer freezes before menus are showed. The system hangs in the point specified below, right after the i40e driver initialization: [ 11.052832] i40e 0002:01:00.0 enP2p1s0f0: renamed from eth0 [ 11.073976] i40e 0002:01:00.1 enP2p1s0f1: renamed from eth1 [ 11.117799] i40e 0002:01:00.2 enP2p1s0f2: renamed from eth2 [ 11.225745] i40e 0002:01:00.3 enP2p1s0f3: renamed from eth3 ***HANG*** The most difficult part in this issue is that it seems to be a timing issue/race condition, and many debug trials end up by avoiding the issue reproduction (heisenbug). We were successful though in getting logs by booting the kernel with the command-line "BOOT_DEBUG=2" and by changing the initrd in order to enable systemd debug; only the files "init" and "start-udev" were changed in initrd, both attached here. We've attached here a saved screen session that shows the entire boot process until it gets flooded with lots of messages like: "starting '/bin/readlink /etc/udev/rules.d/80-net-setup-link.rules' '/bin/readlink /etc/udev/rules.d/80-net-setup-link.rules'(err) 'failed to execute '/bin/readlink' '/bin/readlink /etc/ udev/rules.d/80-net-setup-link.rules': No such file or directory' seq 3244 queued, 'add' 'pci_bus' starting '/bin/readlink /etc/udev/rules.d/80-net-setup-link.rules' passed 408 byte device to netlink monitor 0x1003cfe8020seq 3236 running'/bin/readlink /etc/udev/rules.d/80-net-setup-l ink.rules'(err) 'failed to execute '/bin/readlink' '/bin/readlink /etc/udev/rules.d/80-net-setup-link.rules': No such file or directory' '/bin/readlink /etc/udev/rules.d/80-net-setup-link.rules'(err) 'failed to execute '/bin/readlink' '/bin/readlink /etc/ udev/rules.d/80-net-setup-link.rules': No such file or directory' Process '/bin/readlink /etc/udev/rules.d/80-net-setup-link.rules' failed with exit code 2. PROGRAM '/bin/readlink /etc/udev/rules.d/80-net-setup-link.rules' /lib/udev/rules.d/73-usb-net-by-mac.rules:6 passed device to netlink monitor 0x1003d01f730 " Then it keeps hanged in this stage. We re-tested it by changing the file 73-usb-net-by-mac.rules in initrd, replacing " /etc/udev/rules.d/80-net-setup-link.rules" to "/lib/udev/rules.d/80 -net-setup-link.rules", since the former does not exist whereas the latter does. Same issue were observed! Notice that if we boot the installer with command-line "net.ifnames=0" or "net.ifnames=1", the problem does not reproduces anymore. We want to ask Canonical's help in investigating this issue. Thanks, Guilherme SRU INFORMATION for systemd === Test case: * Check what happens for uevents on devices which are not USB network interfaces: udevadm test /sys/devices/virtual/mem/null udevadm test /sys/class/net/lo With the current version these will run PROGRAM '/bin/readlink /etc/udev/rules.d/80-net-setup-link.rules' /lib/udev/rules.d/73-usb-net-by-mac.rules:6 which is pointless. With the proposed version these should be gone. * Ensure that the rule still works as intended by connecting an USB network device that has a permanent MAC address (e. g. Android tethering uses a temporary MAC): You should ge
[Touch-packages] [Bug 1630877] Re: 1:4.2.6.p3+dfsg-1ubuntu3.11 - OPENSSL_1.0.0 not defined in file libcrypto.so.1.0.0
~$ ldd /usr/bin/ntpq linux-vdso.so.1 => (0x7fff4d9ff000) libopts.so.25 => /usr/lib/libopts.so.25 (0x7f753cb2b000) libedit.so.2 => /usr/lib/x86_64-linux-gnu/libedit.so.2 (0x7f753c904000) libcrypto.so.1.0.0 => /lib/x86_64-linux-gnu/libcrypto.so.1.0.0 (0x7f753c53b000) librt.so.1 => /lib/x86_64-linux-gnu/librt.so.1 (0x7f753c333000) libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7f753bf76000) libbsd.so.0 => /lib/x86_64-linux-gnu/libbsd.so.0 (0x7f753bd69000) libtinfo.so.5 => /lib/x86_64-linux-gnu/libtinfo.so.5 (0x7f753bb42000) libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x7f753b93e000) libz.so.1 => /lib/x86_64-linux-gnu/libz.so.1 (0x7f753b726000) libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x7f753b509000) /lib64/ld-linux-x86-64.so.2 (0x7f753cf8e000) ~$ apt-cache policy openssl openssl: Installed: 1.0.1-4ubuntu5.38 Candidate: 1.0.1-4ubuntu5.38 Version table: *** 1.0.1-4ubuntu5.38 0 500 http://archive.ubuntu.com/ubuntu/ precise-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu/ precise-security/main amd64 Packages 100 /var/lib/dpkg/status 1.0.1-4ubuntu3 0 500 http://archive.ubuntu.com/ubuntu/ precise/main amd64 Packages $ apt-cache policy libssl1.0.0 libssl1.0.0: Installed: 1.0.1-4ubuntu5 Candidate: 1.0.1-4ubuntu5.38 Version table: 1.0.1-4ubuntu5.38 0 500 http://archive.ubuntu.com/ubuntu/ precise-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu/ precise-security/main amd64 Packages *** 1.0.1-4ubuntu5 0 100 /var/lib/dpkg/status 1.0.1-4ubuntu3 0 500 http://archive.ubuntu.com/ubuntu/ precise/main amd64 Packages This is happening in all machines having kernel 3.2.0-23-virtual. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ntp in Ubuntu. https://bugs.launchpad.net/bugs/1630877 Title: 1:4.2.6.p3+dfsg-1ubuntu3.11 - OPENSSL_1.0.0 not defined in file libcrypto.so.1.0.0 Status in ntp package in Ubuntu: Incomplete Bug description: Getting error after upgrade in 12.04 LTS (3.2.0-23-virtual) - ntpq: relocation error: ntpq: symbol CRYPTO_memcmp, version OPENSSL_1.0.0 not defined in file libcrypto.so.1.0.0 with link time reference ntpd not starting after the upgrade. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1630877/+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 1630877] Re: 1:4.2.6.p3+dfsg-1ubuntu3.11 - OPENSSL_1.0.0 not defined in file libcrypto.so.1.0.0
all the machines are having openssl installed from ubuntu repository. dpkg -l | grep openssl ii openssl 1.0.1-4ubuntu5.38 Secure Socket Layer (SSL) binary and related cryptographic tools -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ntp in Ubuntu. https://bugs.launchpad.net/bugs/1630877 Title: 1:4.2.6.p3+dfsg-1ubuntu3.11 - OPENSSL_1.0.0 not defined in file libcrypto.so.1.0.0 Status in ntp package in Ubuntu: Incomplete Bug description: Getting error after upgrade in 12.04 LTS (3.2.0-23-virtual) - ntpq: relocation error: ntpq: symbol CRYPTO_memcmp, version OPENSSL_1.0.0 not defined in file libcrypto.so.1.0.0 with link time reference ntpd not starting after the upgrade. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1630877/+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 1629009] Re: Does not work inside a snap due to hardcoded paths
** Also affects: unity-scope-scopes (Ubuntu)
Importance: Undecided
Status: New
** Branch linked: lp:~mterry/unity-scope-scopes/snap-root
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to messaging-app in Ubuntu.
https://bugs.launchpad.net/bugs/1629009
Title:
Does not work inside a snap due to hardcoded paths
Status in Ubuntu File Manager App:
In Progress
Status in address-book-app package in Ubuntu:
Fix Committed
Status in dialer-app package in Ubuntu:
New
Status in messaging-app package in Ubuntu:
New
Status in ubuntu-system-settings package in Ubuntu:
Fix Committed
Status in ubuntu-terminal-app package in Ubuntu:
New
Status in unity-scope-scopes package in Ubuntu:
New
Status in unity-scopes-api package in Ubuntu:
In Progress
Status in unity-scopes-shell package in Ubuntu:
In Progress
Status in unity8 package in Ubuntu:
In Progress
Status in webbrowser-app package in Ubuntu:
In Progress
Bug description:
Some apps can't find their main qml file. Error messages like:
"file:///build/messaging-app-gcXPE6/messaging-
app-0.1+16.04.20160831/src/qml/messaging-app.qml: File not found"
(in my case, the file was in /snap/unity8-session/x24/usr/share
/messaging-app/messaging-app.qml)
Seems due to code like the following in config.h.in. Probably needs
to consider the value of $SNAP or just be a little more forgiving.
inline bool isRunningInstalled() {
static bool installed = (QCoreApplication::applicationDirPath() ==
QDir(("@CMAKE_INSTALL_PREFIX@/@CMAKE_INSTALL_BINDIR@")).canonicalPath());
return installed;
}
inline QString messagingAppDirectory() {
if (isRunningInstalled()) {
return QString("@CMAKE_INSTALL_PREFIX@/@MESSAGING_APP_DIR@/");
} else {
return QString("@CMAKE_SOURCE_DIR@/src/qml/");
}
}
inline QString ubuntuPhonePluginPath() {
if (isRunningInstalled()) {
return QString::null;
} else {
return QString("@CMAKE_SOURCE_DIR@/");
}
}
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-filemanager-app/+bug/1629009/+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 1586013] Re: UITK Date picker broken on xenial
** Branch linked: lp:~ubuntu-sdk-team/ubuntu-ui- toolkit/rewriteDatePickerInternal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1586013 Title: UITK Date picker broken on xenial Status in Canonical System Image: Confirmed Status in ubuntu-ui-toolkit package in Ubuntu: In Progress Bug description: Seems somewhat broken on both Qt 5.5 (left) and even more so on Qt 5.6 (right). More information on Qt 5.6 at https://wiki.ubuntu.com/Touch/QtTesting tests/xvfb.sh tests/unit/runtest.sh _build/tests/unit/visual/visual tests/unit/visual/tst_datepicker.bug1567840.SEGFAULT.13.qml [...] FAIL! : components::DatePicker13API::test_1_changeMinimumBeforeDate() Uncaught exception: Cannot call method hasOwnProperty of null Loc:[./_build/qml/Ubuntu/Test/UbuntuTestCase13.qml(86)] To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1586013/+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 1631043] [NEW] Internal microphone does not work due to phase inversion
Public bug reported: PulseAudio detects internal microphone but cannot receive any sound from it. WORK-AROUND: Issue command: $ pactl set-source-volume 1 0% 100% or "Install the pavucontrol application, start it and go to the "Input Devices" tab. Unlock the channels (there is a keylock icon), then mute the right channel while keeping the left channel at the volume you want. If the internal mic is now working correctly, you have an inverted internal mic, so that your right channel cancels out the left one." source: https://bugs.launchpad.net/ubuntu/+source/alsa- driver/+bug/1002978 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: pulseaudio 1:8.0-0ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19 Uname: Linux 4.4.0-38-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: chris 1737 F pulseaudio chris 10382 F alsamixer Date: Thu Oct 6 10:47:52 2016 InstallationDate: Installed on 2016-10-05 (1 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/15/2016 dmi.bios.vendor: LENOVO dmi.bios.version: D5CN46WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: VIUU4 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40700 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 300-17ISK dmi.modalias: dmi:bvnLENOVO:bvrD5CN46WW:bd03/15/2016:svnLENOVO:pn80QH:pvrLenovoideapad300-17ISK:rvnLENOVO:rnVIUU4:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrLenovoideapad300-17ISK: dmi.product.name: 80QH dmi.product.version: Lenovo ideapad 300-17ISK dmi.sys.vendor: LENOVO ** Affects: pulseaudio (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 pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1631043 Title: Internal microphone does not work due to phase inversion Status in pulseaudio package in Ubuntu: New Bug description: PulseAudio detects internal microphone but cannot receive any sound from it. WORK-AROUND: Issue command: $ pactl set-source-volume 1 0% 100% or "Install the pavucontrol application, start it and go to the "Input Devices" tab. Unlock the channels (there is a keylock icon), then mute the right channel while keeping the left channel at the volume you want. If the internal mic is now working correctly, you have an inverted internal mic, so that your right channel cancels out the left one." source: https://bugs.launchpad.net/ubuntu/+source/alsa- driver/+bug/1002978 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: pulseaudio 1:8.0-0ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19 Uname: Linux 4.4.0-38-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: chris 1737 F pulseaudio chris 10382 F alsamixer Date: Thu Oct 6 10:47:52 2016 InstallationDate: Installed on 2016-10-05 (1 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/15/2016 dmi.bios.vendor: LENOVO dmi.bios.version: D5CN46WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: VIUU4 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40700 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 300-17ISK dmi.modalias: dmi:bvnLENOVO:bvrD5CN46WW:bd03/15/2016:svnLENOVO:pn80QH:pvrLenovoideapad300-17ISK:rvnLENOVO:rnVIUU4:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrLenovoideapad300-17ISK: dmi.product.name: 80QH dmi.product.version: Lenovo ideapad 300-17ISK dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1631043/+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 1626454] Re: can't connect with owncloud calendars
When does the fix will land to Rc-proposed ? Currently the 06/10/16, i still cannot use pwd like OYMGY-LVNGX-BFXDJ-RXRUI to connect to owncloud calendar, from syncevolution no prob. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to account-plugins in Ubuntu. https://bugs.launchpad.net/bugs/1626454 Title: can't connect with owncloud calendars Status in Canonical System Image: Fix Committed Status in Ubuntu Calendar App: New Status in account-plugins package in Ubuntu: In Progress Bug description: Running my own ownCloud (v9.1.1). Tried to connect Aquarius 4.5 with Calendar App The httpS certificate is official, up to date and not self-signed I use 7 calendars in my ownCloud-calendar-app. (yes, username and password is correct) This I tried: https://mydomain/owncloud/(suggested minimal path on the phone) Error message: Invalid username or password https://mydomain/owncloud/remote.php/ Error message: Invalid host URL https://mydomain/owncloud/remote.php/dav/ --> (This is the primary caldav address suggested by ownCloud calendar-app) Error message: Invalid host URL https://mydomain/owncloud/remote.php/dav/calendars/ Error message: Invalid host URL https://mydomain/owncloud/remote.php/dav/calendars/MYUSERNAME/ Error message: Invalid host URL https://mydomain/owncloud/remote.php/dav/calendars/MYUSERNAME/MYCALENDARNAME/ Error message: Invalid host URL --> This direct path to one of my calendars I use for example to connect my different calendars with Thunderbird lightning (its working) I tried all with and without ending "/" To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1626454/+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 1630877] Re: 1:4.2.6.p3+dfsg-1ubuntu3.11 - OPENSSL_1.0.0 not defined in file libcrypto.so.1.0.0
@nayan: your libssl1.0.0 package hasn't been updated in a long time, is too old, and contains numerous security vulnerabilities. You need to update it to the version that matches your openssl package (1.0.1-4ubuntu5.38) by installing all security updates: $ sudo apt-get update $ sudo apt-get dist-upgrade -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ntp in Ubuntu. https://bugs.launchpad.net/bugs/1630877 Title: 1:4.2.6.p3+dfsg-1ubuntu3.11 - OPENSSL_1.0.0 not defined in file libcrypto.so.1.0.0 Status in ntp package in Ubuntu: Incomplete Bug description: Getting error after upgrade in 12.04 LTS (3.2.0-23-virtual) - ntpq: relocation error: ntpq: symbol CRYPTO_memcmp, version OPENSSL_1.0.0 not defined in file libcrypto.so.1.0.0 with link time reference ntpd not starting after the upgrade. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1630877/+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 1625877] Re: VLC screen always on top
Christopher, I'm experiencing the same issue using ubuntu 16.04 and a toshiba Tegra and i would like to keep this version as it is an LTS. If i understand well the bug is fixed using 16.10 but when can we expect a fix for 16.04 or do you have an idea on what could i do to workaround this bug. I have been installing the last intel driver but this is the same. :( -- 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/1625877 Title: VLC screen always on top Status in xorg package in Ubuntu: Invalid Bug description: After new installed VLC on 16.04 The video screen always on top only while playing with VLC the interface disappeared while minimum VLC (video playing) video screen remains only but the situation is fixed after canceled the option "Accelerated video output(Overlay)" in Preference > Video > Display Reference: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1537053 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16 Uname: Linux 4.4.0-36-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Wed Sep 21 09:23:57 2016 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Sky Lake Integrated Graphics [8086:1912] (rev 06) (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer Skylake Integrated Graphics [1558:6588] InstallationDate: Installed on 2016-09-01 (19 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04f2:b5b0 Chicony Electronics Co., Ltd Bus 001 Device 004: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 045e:07fd Microsoft Corp. Nano Transceiver 1.1 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: COPELION INTERNATIONAL CO., LTD. SY Series ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-36-generic.efi.signed root=UUID=5e244808-04fe-428e-993a-b6260daede38 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/09/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5.11 dmi.board.asset.tag: Tag 12345 dmi.board.name: SY Series dmi.board.vendor: COPELION INTERNATIONAL CO., LTD. dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5.11:bd07/09/2016:svnCOPELIONINTERNATIONALCO.,LTD.:pnSYSeries:pvrNotApplicable:rvnCOPELIONINTERNATIONALCO.,LTD.:rnSYSeries:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A: dmi.product.name: SY Series dmi.product.version: Not Applicable dmi.sys.vendor: COPELION INTERNATIONAL CO., LTD. version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Tue Sep 20 22:21:24 2016 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id1191 vendor LGD xserver.version: 2:1.18.3-1ubuntu2.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1625877/+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 1002978] Re: [meta-bug] Inverted Internal microphone (phase inversion)
Lenovo ideapad 300-17ISK https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1631043 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1002978 Title: [meta-bug] Inverted Internal microphone (phase inversion) Status in alsa-driver package in Ubuntu: Confirmed Bug description: This is a metabug for all machines that are having phase inverted internal microphones. If your internal mic is either completely silent (no signal), or you can possibly pick a very small sound, with much background noise, even though you have set gain to maximum, there is something you could try. Install the pavucontrol application, start it and go to the "Input Devices" tab. Unlock the channels (there is a keylock icon), then mute the right channel while keeping the left channel at the volume you want. If the internal mic is now working correctly, you have an inverted internal mic, so that your right channel cancels out the left one. (If you're not running PulseAudio, you can try doing the same through AlsaMixer instead (see https://wiki.ubuntu.com/Audio/Alsamixer ), try changing "Capture" level or "Internal Mic" or "Internal Mic Boost" using the Q,E,Z,C keys.) If so, please file a separate bug against the alsa-driver for your issue, make sure hardware info gets attached to it (either alsa-info as per https://wiki.ubuntu.com/Audio/AlsaInfo or the standard ones that follows when you do "ubuntu-bug alsa-driver" ), then write a comment in this bug, with your machine name and a pointer to the other bug. As time permits, I'll try to work on fixing them for the next Ubuntu release. Thanks! -- David Henningsson To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1002978/+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 1626651] Re: brightness keys are handled slower in Yakkety than Xenial
Okay, an interesting hint is that this problem seems to be fixed if
u-s-d is started under the Upstart user session instead of the systemd
user session.
If anyone wants to try this, just comment out these three lines in
/etc/X11/Xsession.d/00upstart:
if [ "${1#*.target}" != "$1" ]; then
export
XDG_CONFIG_DIRS="/usr/share/upstart/systemd-session:$XDG_CONFIG_DIRS"
fi
I'm attaching the result of me starting u-s-d under Upstart, running
`sudo forkstat -D 4`, and then pressing the brightness up key.
(I'll attach the same from under systemd next comment.)
>From talking to Martin Pitt on IRC, sounds like switching u-s-d back to
being started by Upstart might not be viable, but hopefully this at
least helps narrow the search.
** Attachment added: "with-upstart.txt"
https://bugs.launchpad.net/ubuntu/+source/unity-settings-daemon/+bug/1626651/+attachment/4756098/+files/with-upstart.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to policykit-1 in Ubuntu.
https://bugs.launchpad.net/bugs/1626651
Title:
brightness keys are handled slower in Yakkety than Xenial
Status in policykit-1 package in Ubuntu:
Triaged
Status in unity-settings-daemon package in Ubuntu:
Triaged
Bug description:
I've noticed on Lenovo X220 and X230 laptops that pressing brightness
keys on Yakkety seems less responsive and slower than Xenial. I ran
forkstat on Xenial and just observed udev being forked off:
Xenial:
$ sudo forkstat
Time Event PID Info Duration Process
17:37:35 fork273 parent /lib/systemd/systemd-udevd
17:37:35 fork 1977 child /lib/systemd/systemd-udevd
17:37:35 exit 1977 00.008 /lib/systemd/systemd-udevd
Whereas on Yakkety, there is far more activity:
Time Event PID Info Duration Process
16:35:34 fork 2626 parent update-notifier
16:35:34 fork 2645 child update-notifier
16:35:34 exec 2645 /usr/bin/python3
/usr/share/apport/apport-checkreports
16:35:34 exit 26452560.221 /usr/bin/python3
/usr/share/apport/apport-checkreports
16:35:34 fork 2626 parent update-notifier
16:35:34 fork 2646 child update-notifier
16:35:34 exec 2646 /usr/bin/python3
/usr/share/apport/apport-checkreports --system
16:35:34 exit 26462560.188 /usr/bin/python3
/usr/share/apport/apport-checkreports --system
16:35:36 fork 1576 parent
/usr/lib/unity-settings-daemon/unity-settings-daemon
16:35:36 fork 2647 child
/usr/lib/unity-settings-daemon/unity-settings-daemon
16:35:36 exec 2647
/usr/lib/unity-settings-daemon/usd-backlight-helper --get-max-brightness
16:35:36 exit 2647 00.008
/usr/lib/unity-settings-daemon/usd-backlight-helper --get-max-brightness
16:35:36 fork 1576 parent
/usr/lib/unity-settings-daemon/unity-settings-daemon
16:35:36 fork 2648 child
/usr/lib/unity-settings-daemon/unity-settings-daemon
16:35:36 exec 2648
/usr/lib/unity-settings-daemon/usd-backlight-helper --get-brightness
16:35:36 exit 2648 00.006
/usr/lib/unity-settings-daemon/usd-backlight-helper --get-brightness
16:35:36 fork 1576 parent
/usr/lib/unity-settings-daemon/unity-settings-daemon
16:35:36 fork 2649 child
/usr/lib/unity-settings-daemon/unity-settings-daemon
16:35:36 exec 2649
/usr/lib/unity-settings-daemon/usd-backlight-helper --get-brightness
16:35:36 exit 2649 00.007
/usr/lib/unity-settings-daemon/usd-backlight-helper --get-brightness
16:35:36 fork 1576 parent
/usr/lib/unity-settings-daemon/unity-settings-daemon
16:35:36 fork 2650 child
/usr/lib/unity-settings-daemon/unity-settings-daemon
16:35:36 exec 2650
/usr/lib/unity-settings-daemon/usd-backlight-helper --get-max-brightness
16:35:36 exit 2650 00.006
/usr/lib/unity-settings-daemon/usd-backlight-helper --get-max-brightness
16:35:36 fork 1576 parent
/usr/lib/unity-settings-daemon/unity-settings-daemon
16:35:36 fork 2651 child
/usr/lib/unity-settings-daemon/unity-settings-daemon
16:35:36 exec 2651 pkexec
/usr/lib/unity-settings-daemon/usd-backlight-helper --set-brightness 2250
16:35:36 clone 2651 parent pkexec
/usr/lib/unity-settings-daemon/usd-backlight-helper --set-brightness 2250
16:35:36 clone 2652 thread pkexec
/usr/lib/unity-settings-daemon/usd-backlight-helper --set-brightness 2250
16:35:36 clone 2651 parent pkexec
/usr/lib/unity-settings-daemon/usd-backlight-helper --set-brightness 2250
16:35:36 clone 2653 thread pkexec
/usr/lib/unity-settings-daemon/usd-backlight-helper --set-brightness 2250
16:35:36 fork 1 parent /sbin/init splash
16:35:36 fork 2654 chil
[Touch-packages] [Bug 1626651] Re: brightness keys are handled slower in Yakkety than Xenial
`sudo forkstat -D 4` when u-s-d is started under systemd and I press the brightness up hotkey. ** Attachment added: "with-systemd.txt" https://bugs.launchpad.net/ubuntu/+source/unity-settings-daemon/+bug/1626651/+attachment/4756099/+files/with-systemd.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to policykit-1 in Ubuntu. https://bugs.launchpad.net/bugs/1626651 Title: brightness keys are handled slower in Yakkety than Xenial Status in policykit-1 package in Ubuntu: Triaged Status in unity-settings-daemon package in Ubuntu: Triaged Bug description: I've noticed on Lenovo X220 and X230 laptops that pressing brightness keys on Yakkety seems less responsive and slower than Xenial. I ran forkstat on Xenial and just observed udev being forked off: Xenial: $ sudo forkstat Time Event PID Info Duration Process 17:37:35 fork273 parent /lib/systemd/systemd-udevd 17:37:35 fork 1977 child /lib/systemd/systemd-udevd 17:37:35 exit 1977 00.008 /lib/systemd/systemd-udevd Whereas on Yakkety, there is far more activity: Time Event PID Info Duration Process 16:35:34 fork 2626 parent update-notifier 16:35:34 fork 2645 child update-notifier 16:35:34 exec 2645 /usr/bin/python3 /usr/share/apport/apport-checkreports 16:35:34 exit 26452560.221 /usr/bin/python3 /usr/share/apport/apport-checkreports 16:35:34 fork 2626 parent update-notifier 16:35:34 fork 2646 child update-notifier 16:35:34 exec 2646 /usr/bin/python3 /usr/share/apport/apport-checkreports --system 16:35:34 exit 26462560.188 /usr/bin/python3 /usr/share/apport/apport-checkreports --system 16:35:36 fork 1576 parent /usr/lib/unity-settings-daemon/unity-settings-daemon 16:35:36 fork 2647 child /usr/lib/unity-settings-daemon/unity-settings-daemon 16:35:36 exec 2647 /usr/lib/unity-settings-daemon/usd-backlight-helper --get-max-brightness 16:35:36 exit 2647 00.008 /usr/lib/unity-settings-daemon/usd-backlight-helper --get-max-brightness 16:35:36 fork 1576 parent /usr/lib/unity-settings-daemon/unity-settings-daemon 16:35:36 fork 2648 child /usr/lib/unity-settings-daemon/unity-settings-daemon 16:35:36 exec 2648 /usr/lib/unity-settings-daemon/usd-backlight-helper --get-brightness 16:35:36 exit 2648 00.006 /usr/lib/unity-settings-daemon/usd-backlight-helper --get-brightness 16:35:36 fork 1576 parent /usr/lib/unity-settings-daemon/unity-settings-daemon 16:35:36 fork 2649 child /usr/lib/unity-settings-daemon/unity-settings-daemon 16:35:36 exec 2649 /usr/lib/unity-settings-daemon/usd-backlight-helper --get-brightness 16:35:36 exit 2649 00.007 /usr/lib/unity-settings-daemon/usd-backlight-helper --get-brightness 16:35:36 fork 1576 parent /usr/lib/unity-settings-daemon/unity-settings-daemon 16:35:36 fork 2650 child /usr/lib/unity-settings-daemon/unity-settings-daemon 16:35:36 exec 2650 /usr/lib/unity-settings-daemon/usd-backlight-helper --get-max-brightness 16:35:36 exit 2650 00.006 /usr/lib/unity-settings-daemon/usd-backlight-helper --get-max-brightness 16:35:36 fork 1576 parent /usr/lib/unity-settings-daemon/unity-settings-daemon 16:35:36 fork 2651 child /usr/lib/unity-settings-daemon/unity-settings-daemon 16:35:36 exec 2651 pkexec /usr/lib/unity-settings-daemon/usd-backlight-helper --set-brightness 2250 16:35:36 clone 2651 parent pkexec /usr/lib/unity-settings-daemon/usd-backlight-helper --set-brightness 2250 16:35:36 clone 2652 thread pkexec /usr/lib/unity-settings-daemon/usd-backlight-helper --set-brightness 2250 16:35:36 clone 2651 parent pkexec /usr/lib/unity-settings-daemon/usd-backlight-helper --set-brightness 2250 16:35:36 clone 2653 thread pkexec /usr/lib/unity-settings-daemon/usd-backlight-helper --set-brightness 2250 16:35:36 fork 1 parent /sbin/init splash 16:35:36 fork 2654 child /sbin/init splash Time Event PID Info Duration Process 16:35:36 fork233 parent /lib/systemd/systemd-udevd 16:35:36 fork 2655 child /lib/systemd/systemd-udevd 16:35:36 fork233 parent /lib/systemd/systemd-udevd 16:35:36 fork 2656 child /lib/systemd/systemd-udevd 16:35:36 fork233 parent /lib/systemd/systemd-udevd 16:35:36 fork 2657 child /lib/systemd/systemd-udevd 16:35:36 fork233 parent /lib/systemd/systemd-udevd 16:35:36 fork 2658 child /lib/systemd/systemd-udevd 16:35:36 fork233 parent /lib/systemd
[Touch-packages] [Bug 1548019] Re: Bypassing certificate checks
** Changed in: ubuntu-download-manager (Ubuntu) Status: New => Confirmed ** Changed in: webbrowser-app (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu. https://bugs.launchpad.net/bugs/1548019 Title: Bypassing certificate checks Status in ubuntu-download-manager package in Ubuntu: Confirmed Status in webbrowser-app package in Ubuntu: Confirmed Bug description: I'm hosting a webserver. Right now I have not registred my SSL-Certificate, so I have to confirm with "proceed anyway"; Then I can access the homepage without problems. But if I try do download something from this homepage, the download shows in download manager, but it does not start. Copying the downloadlink via rightClick and selecting copy Link, then opening the Terminal and typing "wget www.link.de/file --no-check-certificate" works pretty fine. I think, the browser delegates downloads to UDM, the Ubuntu Download Manager. I guess UDM doesn’t allow bypassing certificate checks. If nessesary I can provide a temporary download link for testing the issues. Tested on UbuntuPhone OTA9 (Nexus 4) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-download-manager/+bug/1548019/+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 1631069] [NEW] Irregular display in my Machine.
Public bug reported: Tried to solve the problem by installing nvidia driver. Still i get only Two Resolutions 1024x780 and 800x600. Get me a solution to get higher resolutions. My Monitor is acer P166HQL, LCD. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 4.4.0-38.57~14.04.1-generic 4.4.19 Uname: Linux 4.4.0-38-generic i686 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.21 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Thu Oct 6 22:02:28 2016 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:844d] InstallationDate: Installed on 2016-09-24 (11 days ago) InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release i386 (20160217.1) Lsusb: Bus 002 Device 003: ID 0458:003a KYE Systems Corp. (Mouse Systems) NetScroll+ Mini Traveler / Genius NetScroll 120 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: System manufacturer System Product Name ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-38-generic root=UUID=82804ed2-6725-48ab-9819-5455d7b5666c ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/11/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0501 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8H61-M LX3 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0501:bd01/11/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8H61-MLX3:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz 1:0.9.11.3+14.04.20160425-0ubuntu1 version.libdrm2: libdrm2 2.4.67-1ubuntu0.14.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri N/A version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Thu Oct 6 19:28:24 2016 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.18.3-1ubuntu2.2~trusty3 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 trusty ubuntu -- 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/1631069 Title: Irregular display in my Machine. Status in xorg package in Ubuntu: New Bug description: Tried to solve the problem by installing nvidia driver. Still i get only Two Resolutions 1024x780 and 800x600. Get me a solution to get higher resolutions. My Monitor is acer P166HQL, LCD. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 4.4.0-38.57~14.04.1-generic 4.4.19 Uname: Linux 4.4.0-38-generic i686 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.21 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Thu Oct 6 22:02:28 2016 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:844d] InstallationDate: Installed on 2016-09-24 (11 days ago) InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release i386 (20160217.1) Lsusb: Bus 002 Device 003: ID 0458:003a KYE Systems Corp. (Mouse Systems) NetScroll+ Mini Traveler / Genius NetScroll 120 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:00
[Touch-packages] [Bug 1630877] Re: 1:4.2.6.p3+dfsg-1ubuntu3.11 - OPENSSL_1.0.0 not defined in file libcrypto.so.1.0.0
Thanks Mark , upgrade of libssl1.0.0 fixed the issue of ntp. dpkg -l | grep libssl1 ii libssl1.0.0 1.0.1-4ubuntu5.38 SSL shared libraries dpkg -l | grep openssl ii openssl 1.0.1-4ubuntu5.38 Secure Socket Layer (SSL) binary and related cryptographic tools dpkg -l | grep ntp ii ntp 1:4.2.6.p3+dfsg-1ubuntu3.11 Network Time Protocol daemon and utility programs -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ntp in Ubuntu. https://bugs.launchpad.net/bugs/1630877 Title: 1:4.2.6.p3+dfsg-1ubuntu3.11 - OPENSSL_1.0.0 not defined in file libcrypto.so.1.0.0 Status in ntp package in Ubuntu: Incomplete Bug description: Getting error after upgrade in 12.04 LTS (3.2.0-23-virtual) - ntpq: relocation error: ntpq: symbol CRYPTO_memcmp, version OPENSSL_1.0.0 not defined in file libcrypto.so.1.0.0 with link time reference ntpd not starting after the upgrade. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1630877/+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 1630472] Re: unity-system-compositor crashed with SIGABRT in mir::fatal_error_abort()
*** This bug is a duplicate of bug 1584894 *** https://bugs.launchpad.net/bugs/1584894 Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: unity-system-compositor (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-system-compositor in Ubuntu. https://bugs.launchpad.net/bugs/1630472 Title: unity-system-compositor crashed with SIGABRT in mir::fatal_error_abort() Status in unity-system-compositor package in Ubuntu: Confirmed Bug description: Just after reboot when running unity8 on qemu ProblemType: Crash DistroRelease: Ubuntu 16.10 Package: unity-system-compositor 0.7.1+16.10.20160909.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-17.19-generic 4.8.0-rc7 Uname: Linux 4.8.0-17-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 Date: Wed Oct 5 09:01:48 2016 ExecutablePath: /usr/sbin/unity-system-compositor GraphicsCard: Device [1234:] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Red Hat, Inc Device [1af4:1100] InstallationDate: Installed on 2016-10-03 (1 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) ProcCmdline: /usr/sbin/unity-system-compositor --disable-inactivity-policy=true --on-fatal-error-abort --file /run/mir_socket --from-dm-fd 12 --to-dm-fd 21 --vt 8 ProcEnviron: Signal: 6 SourcePackage: unity-system-compositor StacktraceTop: mir::fatal_error_abort(char const*, ...) () from /usr/lib/x86_64-linux-gnu/libmircommon.so.6 ?? () from /usr/lib/x86_64-linux-gnu/mir/server-platform/graphics-mesa-kms.so.10 ?? () from /usr/lib/x86_64-linux-gnu/libmirserver.so.41 ?? () from /usr/lib/x86_64-linux-gnu/libmirserver.so.41 ?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 Title: unity-system-compositor crashed with SIGABRT in mir::fatal_error_abort() UpgradeStatus: Upgraded to yakkety on 2016-10-04 (0 days ago) UserGroups: version.libdrm: libdrm2 2.4.70-1 version.lightdm: lightdm 1.19.5-0ubuntu1 version.mesa: libegl1-mesa-dev N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-system-compositor/+bug/1630472/+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 1630877] Re: 1:4.2.6.p3+dfsg-1ubuntu3.11 - OPENSSL_1.0.0 not defined in file libcrypto.so.1.0.0
Great, I'm closing this bug. Thanks! ** Changed in: ntp (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ntp in Ubuntu. https://bugs.launchpad.net/bugs/1630877 Title: 1:4.2.6.p3+dfsg-1ubuntu3.11 - OPENSSL_1.0.0 not defined in file libcrypto.so.1.0.0 Status in ntp package in Ubuntu: Invalid Bug description: Getting error after upgrade in 12.04 LTS (3.2.0-23-virtual) - ntpq: relocation error: ntpq: symbol CRYPTO_memcmp, version OPENSSL_1.0.0 not defined in file libcrypto.so.1.0.0 with link time reference ntpd not starting after the upgrade. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1630877/+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 1626651] Re: brightness keys are handled slower in Yakkety than Xenial
I'm back to testing u-s-d started under systemd, and I found some serious wackiness observing `sudo journalctl -f` when I use the brigtness up/down hotkeys. The attached "wacky-journalctl.txt" file has the output of `sudo journalctl -f` during which I used the brightness hotkeys *twice*, and you'll see a slew interesting things happening *each* time I press a hot key. For example, this is a small excerpt of what I'm seeing for every hotkey press: Oct 06 10:44:50 jason-Gazelle-Professional systemd[1]: Created slice User Slice of root. Oct 06 10:44:50 jason-Gazelle-Professional systemd[1]: Starting User Manager for UID 0... Oct 06 10:44:50 jason-Gazelle-Professional systemd[1]: Started Session 1 of user root. Oct 06 10:44:50 jason-Gazelle-Professional systemd[4805]: pam_unix(systemd-user:session): session opened for user root by (uid=0) Oct 06 10:44:50 jason-Gazelle-Professional systemd[4805]: Reached target Paths. Oct 06 10:44:50 jason-Gazelle-Professional systemd[4805]: Starting D-Bus User Message Bus Socket. Oct 06 10:44:50 jason-Gazelle-Professional systemd[4805]: Reached target Timers. Oct 06 10:44:50 jason-Gazelle-Professional systemd[4805]: Listening on D-Bus User Message Bus Socket. Oct 06 10:44:50 jason-Gazelle-Professional systemd[4805]: Reached target Sockets. Oct 06 10:44:50 jason-Gazelle-Professional systemd[4805]: Reached target Basic System. Oct 06 10:44:50 jason-Gazelle-Professional systemd[4805]: Starting Run Click user-level hooks... Oct 06 10:44:50 jason-Gazelle-Professional systemd[4805]: Started D-Bus User Message Bus. Oct 06 10:44:50 jason-Gazelle-Professional dbus-daemon[4839]: Activating via systemd: service name='org.gtk.vfs.Daemon' unit='gvfs-daemon.service' ** Attachment added: "wacky-journalctl.txt" https://bugs.launchpad.net/ubuntu/+source/unity-settings-daemon/+bug/1626651/+attachment/4756139/+files/wacky-journalctl.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to policykit-1 in Ubuntu. https://bugs.launchpad.net/bugs/1626651 Title: brightness keys are handled slower in Yakkety than Xenial Status in policykit-1 package in Ubuntu: Triaged Status in unity-settings-daemon package in Ubuntu: Triaged Bug description: I've noticed on Lenovo X220 and X230 laptops that pressing brightness keys on Yakkety seems less responsive and slower than Xenial. I ran forkstat on Xenial and just observed udev being forked off: Xenial: $ sudo forkstat Time Event PID Info Duration Process 17:37:35 fork273 parent /lib/systemd/systemd-udevd 17:37:35 fork 1977 child /lib/systemd/systemd-udevd 17:37:35 exit 1977 00.008 /lib/systemd/systemd-udevd Whereas on Yakkety, there is far more activity: Time Event PID Info Duration Process 16:35:34 fork 2626 parent update-notifier 16:35:34 fork 2645 child update-notifier 16:35:34 exec 2645 /usr/bin/python3 /usr/share/apport/apport-checkreports 16:35:34 exit 26452560.221 /usr/bin/python3 /usr/share/apport/apport-checkreports 16:35:34 fork 2626 parent update-notifier 16:35:34 fork 2646 child update-notifier 16:35:34 exec 2646 /usr/bin/python3 /usr/share/apport/apport-checkreports --system 16:35:34 exit 26462560.188 /usr/bin/python3 /usr/share/apport/apport-checkreports --system 16:35:36 fork 1576 parent /usr/lib/unity-settings-daemon/unity-settings-daemon 16:35:36 fork 2647 child /usr/lib/unity-settings-daemon/unity-settings-daemon 16:35:36 exec 2647 /usr/lib/unity-settings-daemon/usd-backlight-helper --get-max-brightness 16:35:36 exit 2647 00.008 /usr/lib/unity-settings-daemon/usd-backlight-helper --get-max-brightness 16:35:36 fork 1576 parent /usr/lib/unity-settings-daemon/unity-settings-daemon 16:35:36 fork 2648 child /usr/lib/unity-settings-daemon/unity-settings-daemon 16:35:36 exec 2648 /usr/lib/unity-settings-daemon/usd-backlight-helper --get-brightness 16:35:36 exit 2648 00.006 /usr/lib/unity-settings-daemon/usd-backlight-helper --get-brightness 16:35:36 fork 1576 parent /usr/lib/unity-settings-daemon/unity-settings-daemon 16:35:36 fork 2649 child /usr/lib/unity-settings-daemon/unity-settings-daemon 16:35:36 exec 2649 /usr/lib/unity-settings-daemon/usd-backlight-helper --get-brightness 16:35:36 exit 2649 00.007 /usr/lib/unity-settings-daemon/usd-backlight-helper --get-brightness 16:35:36 fork 1576 parent /usr/lib/unity-settings-daemon/unity-settings-daemon 16:35:36 fork 2650 child /usr/lib/unity-settings-daemon/unity-settings-daemon 16:35:36 exec 2650 /usr/lib/unity-settings-daemon/usd-backlight-helper --get-max-brightness 16:
[Touch-packages] [Bug 1126108] Re: Indicator disappears entirely when disabling / turning off bluetooth
This bug is marked as fixed, so if you still have this problem please say you
are affected at:
https://bugs.launchpad.net/ubuntu/+source/indicator-bluetooth/+bug/1595695
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to indicator-bluetooth in
Ubuntu.
https://bugs.launchpad.net/bugs/1126108
Title:
Indicator disappears entirely when disabling / turning off bluetooth
Status in indicator-bluetooth package in Ubuntu:
Fix Released
Bug description:
Bug 1116289 made the BT indicator disappear when there is no hardware.
However, with that version I now also have it disappear when my
existing BT hardware is merely disabled. I. e. I disable BT from the
indicator, then it disappears, leaving me no obvious method to turn it
back on again. I can re-enabble it in control-center, and then the
indicator comes back.
I think when it sees no actual BT hardware it ought to check rfkill
whether there is disabled BT hardware:
$ grep -r . /sys/class/rfkill/rfkill0/{type,state,soft,persistent}
/sys/class/rfkill/rfkill0/type:bluetooth
/sys/class/rfkill/rfkill0/state:1
/sys/class/rfkill/rfkill0/soft:0
/sys/class/rfkill/rfkill0/persistent:1
After disabling BT from the indicator, "soft" changes to 1:
$ grep -r . /sys/class/rfkill/rfkill0/{type,state,soft,persistent}
/sys/class/rfkill/rfkill0/type:bluetooth
/sys/class/rfkill/rfkill0/state:0
/sys/class/rfkill/rfkill0/soft:1
/sys/class/rfkill/rfkill0/persistent:1
ProblemType: Bug
DistroRelease: Ubuntu 13.04
Package: indicator-bluetooth 0.0.6-0ubuntu1
ProcVersionSignature: Ubuntu 3.8.0-6.13-generic 3.8.0-rc7
Uname: Linux 3.8.0-6-generic x86_64
ApportVersion: 2.8-0ubuntu4
Architecture: amd64
Date: Fri Feb 15 12:08:26 2013
EcryptfsInUse: Yes
InstallationDate: Installed on 2013-02-08 (7 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130207.1)
MarkForUpload: True
ProcEnviron:
TERM=xterm
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=de_DE.UTF-8
SHELL=/bin/bash
SourcePackage: indicator-bluetooth
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-bluetooth/+bug/1126108/+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
