[Touch-packages] [Bug 1539548] Re: Ubuntu 16.04: not possible to install qemu-system-common
Thanks for reporting this bug. mountkernfs should not be a problem, here is its description: # Short-Description: Mount kernel virtual file systems. # Description: Mount initial set of virtual filesystems the kernel #provides and that are required by everything. I'll mark this as affecting initscripts, which provides mountkernfs, because I don't know what to look for to determine why mountkernfs would not be provided. ** Also affects: sysvinit (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sysvinit in Ubuntu. https://bugs.launchpad.net/bugs/1539548 Title: Ubuntu 16.04: not possible to install qemu-system-common Status in qemu package in Ubuntu: New Status in sysvinit package in Ubuntu: New Bug description: Attempt to install qemu-system-common fails: # apt-get install qemu-system-common ... Setting up qemu-system-common (1:2.5+dfsg-1ubuntu3) ... insserv: Service mountkernfs has to be enabled to start service qemu-system-x86 insserv: exiting now! update-rc.d: error: insserv rejected the script header dpkg: error processing package qemu-system-common (--configure): subprocess installed post-installation script returned error exit status 1 W/A: remove mountkernfs from 'Required-Start' in /etc/init.d/qemu-kvm Additional details: $ lsb_release -rd Description: Ubuntu Xenial Xerus (development branch) Release: 16.04 $ apt-cache policy qemu-system-common qemu-system-common: Installed: 1:2.5+dfsg-1ubuntu3 Candidate: 1:2.5+dfsg-1ubuntu3 Version table: *** 1:2.5+dfsg-1ubuntu3 500 500 http://ru.archive.ubuntu.com/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: qemu-system-common 1:2.5+dfsg-1ubuntu3 ProcVersionSignature: Ubuntu 4.3.0-7.18-generic 4.3.3 Uname: Linux 4.3.0-7-generic x86_64 ApportVersion: 2.19.4-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Fri Jan 29 17:25:01 2016 InstallationDate: Installed on 2016-01-29 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160127) KvmCmdLine: COMMAND STAT EUID RUID PID PPID %CPU COMMAND kvm-irqfd-clean S< 0 0 17260 2 0.0 [kvm-irqfd-clean] MachineType: LENOVO 20BX002KRT ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.3.0-7-generic root=UUID=b8ac91de-9dc8-4e51-a7e6-18069c42cd7a ro quiet splash SourcePackage: qemu UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/08/2015 dmi.bios.vendor: LENOVO dmi.bios.version: JBET51WW (1.16 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BX002KRT dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrJBET51WW(1.16):bd07/08/2015:svnLENOVO:pn20BX002KRT:pvrThinkPadT450s:rvnLENOVO:rn20BX002KRT:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone: dmi.product.name: 20BX002KRT dmi.product.version: ThinkPad T450s dmi.sys.vendor: LENOVO mtime.conffile..etc.init.d.qemu.kvm: 2016-01-29T17:15:30.052385 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1539548/+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 1543735] Re: package tzdata-java 2015g-0ubuntu0.14.04 failed to install/upgrade: package tzdata-java is already installed and configured
*** This bug is a duplicate of bug 1407757 *** https://bugs.launchpad.net/bugs/1407757 ** This bug has been marked a duplicate of bug 1407757 multi-arch packages cannot be installed due to dpkg wrongly detecting them as already installed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu. https://bugs.launchpad.net/bugs/1543735 Title: package tzdata-java 2015g-0ubuntu0.14.04 failed to install/upgrade: package tzdata-java is already installed and configured Status in tzdata package in Ubuntu: New Bug description: error encounterd wen installing java ProblemType: Package DistroRelease: Ubuntu 14.04 Package: tzdata-java 2015g-0ubuntu0.14.04 ProcVersionSignature: Ubuntu 3.19.0-49.55~14.04.1-lowlatency 3.19.8-ckt12 Uname: Linux 3.19.0-49-lowlatency i686 NonfreeKernelModules: wl ApportVersion: 2.14.1-0ubuntu3.19 AptdaemonVersion: 1.1.1-1ubuntu5.2 Architecture: i386 Date: Tue Feb 9 18:45:23 2016 DuplicateSignature: package:tzdata-java:2015g-0ubuntu0.14.04:package tzdata-java is already installed and configured ErrorMessage: package tzdata-java is already installed and configured InstallationDate: Installed on 2016-02-07 (2 days ago) InstallationMedia: Ubuntu-Studio 14.04.3 LTS "Trusty Tahr" - Beta i386 (20150805) PackageArchitecture: all RelatedPackageVersions: dpkg 1.17.5ubuntu5.5 apt 1.0.1ubuntu2.11 SourcePackage: tzdata Title: package tzdata-java 2015g-0ubuntu0.14.04 failed to install/upgrade: package tzdata-java is already installed and configured UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1543735/+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 1527053] Re: Tab names unreadable in GTK3 in Ubuntu
** Changed in: ubuntu-themes (Ubuntu) Status: New => Invalid -- 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/1527053 Title: Tab names unreadable in GTK3 in Ubuntu Status in LibreOffice: Confirmed Status in ubuntu-themes package in Ubuntu: Invalid Bug description: Steps to reproduce: 1. On Ubuntu 15.4 or 15.10, install or build libreoffice 5.1 2. Open a tabbed dialog box such Format->Paragraph Note the text is white on light gray, which is very hard to read. In Fedora or Debian, when you select a "dark" theme, the tabs are rendered as white text on a black background. In Ubuntu other UI elements such as the toolbar and context menus are rendered the same as Debian's dark theme(white text on black). To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1527053/+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 1545161] Re: package libunity-scopes1.0:amd64 1.0.3+16.04.20160209-0ubuntu1 failed to install/upgrade: package libunity-scopes1.0:amd64 is already installed and configured
*** This bug is a duplicate of bug 1407757 *** https://bugs.launchpad.net/bugs/1407757 ** This bug is no longer a duplicate of bug 1545156 package libunity-scopes1.0:amd64 1.0.3+16.04.20160209-0ubuntu1 failed to install/upgrade: package libunity-scopes1.0:amd64 is already installed and configured ** This bug has been marked a duplicate of bug 1407757 multi-arch packages cannot be installed due to dpkg wrongly detecting them as already installed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-scopes-api in Ubuntu. https://bugs.launchpad.net/bugs/1545161 Title: package libunity-scopes1.0:amd64 1.0.3+16.04.20160209-0ubuntu1 failed to install/upgrade: package libunity-scopes1.0:amd64 is already installed and configured Status in unity-scopes-api package in Ubuntu: New Bug description: On startup ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libunity-scopes1.0:amd64 1.0.3+16.04.20160209-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-5.20-generic 4.4.1 Uname: Linux 4.4.0-5-generic x86_64 ApportVersion: 2.19.4-0ubuntu2 AptdaemonVersion: 1.1.1+bzr982-0ubuntu14 Architecture: amd64 Date: Fri Feb 12 13:59:44 2016 ErrorMessage: package libunity-scopes1.0:amd64 is already installed and configured InstallationDate: Installed on 2016-02-05 (6 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160205) RelatedPackageVersions: dpkg 1.18.4ubuntu1 apt 1.1.10 SourcePackage: unity-scopes-api Title: package libunity-scopes1.0:amd64 1.0.3+16.04.20160209-0ubuntu1 failed to install/upgrade: package libunity-scopes1.0:amd64 is already installed and configured UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-scopes-api/+bug/1545161/+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 1545157] Re: package libunity-scopes1.0 1.0.3+16.04.20160209-0ubuntu1 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1
*** This bug is a duplicate of bug 1407757 *** https://bugs.launchpad.net/bugs/1407757 ** This bug is no longer a duplicate of bug 1545156 package libunity-scopes1.0:amd64 1.0.3+16.04.20160209-0ubuntu1 failed to install/upgrade: package libunity-scopes1.0:amd64 is already installed and configured ** This bug has been marked a duplicate of bug 1407757 multi-arch packages cannot be installed due to dpkg wrongly detecting them as already installed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-scopes-api in Ubuntu. https://bugs.launchpad.net/bugs/1545157 Title: package libunity-scopes1.0 1.0.3+16.04.20160209-0ubuntu1 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1 Status in unity-scopes-api package in Ubuntu: New Bug description: On start-up ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libunity-scopes1.0 1.0.3+16.04.20160209-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-5.20-generic 4.4.1 Uname: Linux 4.4.0-5-generic x86_64 ApportVersion: 2.19.4-0ubuntu2 Architecture: amd64 Date: Fri Feb 12 13:58:36 2016 ErrorMessage: subprocess new pre-removal script returned error exit status 1 InstallationDate: Installed on 2016-02-05 (6 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160205) RelatedPackageVersions: dpkg 1.18.4ubuntu1 apt 1.1.10 SourcePackage: unity-scopes-api Title: package libunity-scopes1.0 1.0.3+16.04.20160209-0ubuntu1 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-scopes-api/+bug/1545157/+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 1399734] Re: Current tab is not highlighted
Isn't this a duplicate of https://bugs.launchpad.net/ubuntu/+source /ubuntu-themes/+bug/1399734? -- 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/1399734 Title: Current tab is not highlighted Status in ubuntu-themes package in Ubuntu: Confirmed Bug description: With the Ambiance or Radiance theme, in windows using a GtkNotebook the current tab is not highlighted to distinguish it from hidden tabs. In some apps you can just about see a faint line under the inactive tabs, but some apps, such as roxterm, don't use the border option, so it's impossible to tell which tab is selected. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: light-themes 14.04+14.10.20141015-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7 Uname: Linux 3.16.0-25-generic x86_64 ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Fri Dec 5 17:27:41 2014 InstallationDate: Installed on 2014-06-13 (174 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) PackageArchitecture: all SourcePackage: ubuntu-themes UpgradeStatus: Upgraded to utopic on 2014-10-24 (42 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1399734/+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 1525719] Re: PCI/internal sound card not detected inside Hyper-V
[Expired for alsa-driver (Ubuntu) because there has been no activity for 60 days.] ** Changed in: alsa-driver (Ubuntu) Status: Incomplete => Expired -- 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/1525719 Title: PCI/internal sound card not detected inside Hyper-V Status in alsa-driver package in Ubuntu: Expired Bug description: aplay -l reports aplay: device_list:268: no soundcards found... ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-25.26~14.04.1-generic 3.19.8-ckt2 Uname: Linux 3.19.0-25-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: Unity Date: Sun Dec 13 14:23:38 2015 InstallationDate: Installed on 2015-12-13 (0 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/26/2012 dmi.bios.vendor: Microsoft Corporation dmi.bios.version: Hyper-V UEFI Release v1.0 dmi.board.asset.tag: None dmi.board.name: Virtual Machine dmi.board.vendor: Microsoft Corporation dmi.board.version: Hyper-V UEFI Release v1.0 dmi.chassis.asset.tag: 2658-6322-8002-9577-5138-8780-03 dmi.chassis.type: 3 dmi.chassis.vendor: Microsoft Corporation dmi.chassis.version: Hyper-V UEFI Release v1.0 dmi.modalias: dmi:bvnMicrosoftCorporation:bvrHyper-VUEFIReleasev1.0:bd11/26/2012:svnMicrosoftCorporation:pnVirtualMachine:pvrHyper-VUEFIReleasev1.0:rvnMicrosoftCorporation:rnVirtualMachine:rvrHyper-VUEFIReleasev1.0:cvnMicrosoftCorporation:ct3:cvrHyper-VUEFIReleasev1.0: dmi.product.name: Virtual Machine dmi.product.version: Hyper-V UEFI Release v1.0 dmi.sys.vendor: Microsoft Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1525719/+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 1523158] Re: Add printer
[Expired for cups (Ubuntu) because there has been no activity for 60 days.] ** Changed in: cups (Ubuntu) Status: Incomplete => Expired -- 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/1523158 Title: Add printer Status in cups package in Ubuntu: Expired Bug description: I tried to download epson 420 driver on my UBUNTU 15.10. It is connecting using Wi-Fi . The set up works perfectly until I am asked to Authenticate then it hangs up. I can do it using the CUPS website. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1523158/+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 1538471] Re: scope-runner-dbus.py assert failure: *** Error in `/usr/bin/python3': free(): invalid next size (fast): 0x0000000001ca17b0 ***
Forgot to add the error such top of this page: ProblemType: Crash DistroRelease: Ubuntu 16.04 Package: unity-scopes-runner 7.1.4+15.10.20151002-0ubuntu2 ProcVersionSignature: Ubuntu 4.3.0-7.18-generic 4.3.3 Uname: Linux 4.3.0-7-generic x86_64 ApportVersion: 2.19.4-0ubuntu1 Architecture: amd64 AssertionMessage: *** Error in `/usr/bin/python3': free(): invalid next size (fast): 0x01ca17b0 *** CrashCounter: 1 CurrentDesktop: Unity Date: Wed Jan 27 10:41:54 2016 Dependencies: ExecutablePath: /usr/share/unity-scopes/scope-runner-dbus.py InstallationDate: Installed on 2015-04-30 (271 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) InterpreterPath: /usr/bin/python3.5 PackageArchitecture: all ProcCmdline: /usr/bin/python3 /usr/share/unity-scopes/scope-runner-dbus.py -s info/calculator.scope Signal: 6 SourcePackage: libunity StacktraceTop: __libc_message (do_abort=do_abort@entry=1, fmt=fmt@entry=0x7fd789926128 "*** Error in `%s': %s: 0x%s ***\n") at ../sysdeps/posix/libc_fatal.c:175 malloc_printerr (ptr=, str=0x7fd7899261a0 "free(): invalid next size (fast)", action=1) at malloc.c:4965 _int_free (av=, p=, have_lock=0) at malloc.c:3834 __GI___libc_free (mem=) at malloc.c:2950 ?? () from /usr/lib/python3/dist-packages/gi/_gi.cpython-35m-x86_64-linux-gnu.so SystemImageInfo: Error: command ['system-image-cli', '-i'] failed with exit code 2: Title: scope-runner-dbus.py assert failure: *** Error in `/usr/bin/python3': free(): invalid next size (fast): 0x01ca17b0 *** UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip libvirtd lpadmin plugdev sambashare sudo -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libunity in Ubuntu. https://bugs.launchpad.net/bugs/1538471 Title: scope-runner-dbus.py assert failure: *** Error in `/usr/bin/python3': free(): invalid next size (fast): 0x01ca17b0 *** Status in libunity package in Ubuntu: Confirmed Bug description: No idea what happened. ProblemType: Crash DistroRelease: Ubuntu 16.04 Package: unity-scopes-runner 7.1.4+15.10.20151002-0ubuntu2 ProcVersionSignature: Ubuntu 4.3.0-7.18-generic 4.3.3 Uname: Linux 4.3.0-7-generic x86_64 ApportVersion: 2.19.4-0ubuntu1 Architecture: amd64 AssertionMessage: *** Error in `/usr/bin/python3': free(): invalid next size (fast): 0x01ca17b0 *** CrashCounter: 1 CurrentDesktop: Unity Date: Wed Jan 27 10:41:54 2016 Dependencies: ExecutablePath: /usr/share/unity-scopes/scope-runner-dbus.py InstallationDate: Installed on 2015-04-30 (271 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) InterpreterPath: /usr/bin/python3.5 PackageArchitecture: all ProcCmdline: /usr/bin/python3 /usr/share/unity-scopes/scope-runner-dbus.py -s info/calculator.scope Signal: 6 SourcePackage: libunity StacktraceTop: __libc_message (do_abort=do_abort@entry=1, fmt=fmt@entry=0x7fd789926128 "*** Error in `%s': %s: 0x%s ***\n") at ../sysdeps/posix/libc_fatal.c:175 malloc_printerr (ptr=, str=0x7fd7899261a0 "free(): invalid next size (fast)", action=1) at malloc.c:4965 _int_free (av=, p=, have_lock=0) at malloc.c:3834 __GI___libc_free (mem=) at malloc.c:2950 ?? () from /usr/lib/python3/dist-packages/gi/_gi.cpython-35m-x86_64-linux-gnu.so SystemImageInfo: Error: command ['system-image-cli', '-i'] failed with exit code 2: Title: scope-runner-dbus.py assert failure: *** Error in `/usr/bin/python3': free(): invalid next size (fast): 0x01ca17b0 *** UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip libvirtd lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libunity/+bug/1538471/+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 1538471] Re: scope-runner-dbus.py assert failure: *** Error in `/usr/bin/python3': free(): invalid next size (fast): 0x0000000001ca17b0 ***
Idem top page but in a fresh installed ubu 16.04 LTS. Happened after the upgrade of "ofono" and "telepathy-ring" on Feb 12 2016. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libunity in Ubuntu. https://bugs.launchpad.net/bugs/1538471 Title: scope-runner-dbus.py assert failure: *** Error in `/usr/bin/python3': free(): invalid next size (fast): 0x01ca17b0 *** Status in libunity package in Ubuntu: Confirmed Bug description: No idea what happened. ProblemType: Crash DistroRelease: Ubuntu 16.04 Package: unity-scopes-runner 7.1.4+15.10.20151002-0ubuntu2 ProcVersionSignature: Ubuntu 4.3.0-7.18-generic 4.3.3 Uname: Linux 4.3.0-7-generic x86_64 ApportVersion: 2.19.4-0ubuntu1 Architecture: amd64 AssertionMessage: *** Error in `/usr/bin/python3': free(): invalid next size (fast): 0x01ca17b0 *** CrashCounter: 1 CurrentDesktop: Unity Date: Wed Jan 27 10:41:54 2016 Dependencies: ExecutablePath: /usr/share/unity-scopes/scope-runner-dbus.py InstallationDate: Installed on 2015-04-30 (271 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) InterpreterPath: /usr/bin/python3.5 PackageArchitecture: all ProcCmdline: /usr/bin/python3 /usr/share/unity-scopes/scope-runner-dbus.py -s info/calculator.scope Signal: 6 SourcePackage: libunity StacktraceTop: __libc_message (do_abort=do_abort@entry=1, fmt=fmt@entry=0x7fd789926128 "*** Error in `%s': %s: 0x%s ***\n") at ../sysdeps/posix/libc_fatal.c:175 malloc_printerr (ptr=, str=0x7fd7899261a0 "free(): invalid next size (fast)", action=1) at malloc.c:4965 _int_free (av=, p=, have_lock=0) at malloc.c:3834 __GI___libc_free (mem=) at malloc.c:2950 ?? () from /usr/lib/python3/dist-packages/gi/_gi.cpython-35m-x86_64-linux-gnu.so SystemImageInfo: Error: command ['system-image-cli', '-i'] failed with exit code 2: Title: scope-runner-dbus.py assert failure: *** Error in `/usr/bin/python3': free(): invalid next size (fast): 0x01ca17b0 *** UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip libvirtd lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libunity/+bug/1538471/+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 1471459] Re: First run of nano creates a directory in $HOME, if run as sudo will be root owned
This bug was fixed in the package nano - 2.5.2-1 --- nano (2.5.2-1) unstable; urgency=medium * New upstream release. - Ignores $HOME when effective user is root, to avoid creating root-owned files when for example invoking under sudo (LP: #1471459). * Sync debian/nanorc with upstream nanorc.sample. * Use https for the download URL and Vcs-Browser. -- Jordi Mallach Fri, 12 Feb 2016 14:29:11 +0100 ** Changed in: nano (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to nano in Ubuntu. https://bugs.launchpad.net/bugs/1471459 Title: First run of nano creates a directory in $HOME, if run as sudo will be root owned Status in One Hundred Papercuts: Confirmed Status in nano package in Ubuntu: Fix Released Bug description: If nano is started for the first with sudo then a root owned directory named .nano is created in the user's $HOME directory. If 1st. started as a user then the user owns .nano & ownership will not be altered by subsequent use of sudo nano. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: nano 2.4.1-1 ProcVersionSignature: Ubuntu 3.19.0-22.22-generic 3.19.8-ckt1 Uname: Linux 3.19.0-22-generic x86_64 ApportVersion: 2.17.3-0ubuntu4 Architecture: amd64 Date: Sat Jul 4 20:06:16 2015 InstallationDate: Installed on 2015-02-25 (128 days ago) InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20150224) SourcePackage: nano UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1471459/+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 1543344] Re: scroll wheel too fast
It appears that the internal USC default for scroll speed is 1.0 (on a scale of 0.0 to 1.0). But the default that unity8 will start using once [1] lands is 0.5. So I *think* this will be solved by that (already approved) branch. But unfortunately, it's a little hard to test that right this second, because it has a complicated dependency chain. But once I do, I will mark this bug accordingly. [1] https://code.launchpad.net/~mterry/unity8/new-input- proxies/+merge/285364 -- 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/1543344 Title: scroll wheel too fast Status in Canonical Pocket Desktop: New Status in unity8 package in Ubuntu: New Bug description: just need to tune the scroll imho use window mode, trackpad mode, select dash 2 finger scroll - too fast to be useful To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-pocket-desktop/+bug/1543344/+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 1545190] Re: package patch 2.7.1-4ubuntu2.3 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to patch in Ubuntu. https://bugs.launchpad.net/bugs/1545190 Title: package patch 2.7.1-4ubuntu2.3 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in patch package in Ubuntu: New Bug description: all avvio segnale errore nel sisema. non riconosce la tastiera nei tasti speciali ProblemType: Package DistroRelease: Ubuntu 14.04 Package: patch 2.7.1-4ubuntu2.3 ProcVersionSignature: Ubuntu 3.13.0-77.121-generic 3.13.11-ckt32 Uname: Linux 3.13.0-77-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 Date: Fri Feb 12 17:26:19 2016 Dependencies: gcc-4.9-base 4.9.3-0ubuntu4 libc6 2.19-0ubuntu6.6 libgcc1 1:4.9.3-0ubuntu4 multiarch-support 2.19-0ubuntu6.6 DuplicateSignature: package:patch:2.7.1-4ubuntu2.3:package is in a very bad inconsistent state; you should reinstall it before attempting configuration ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2014-09-22 (508 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) RelatedPackageVersions: dpkg 1.17.5ubuntu5.5 apt 1.0.1ubuntu2.11 SourcePackage: patch Title: package patch 2.7.1-4ubuntu2.3 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/patch/+bug/1545190/+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 1545190] [NEW] package patch 2.7.1-4ubuntu2.3 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration
Public bug reported: all avvio segnale errore nel sisema. non riconosce la tastiera nei tasti speciali ProblemType: Package DistroRelease: Ubuntu 14.04 Package: patch 2.7.1-4ubuntu2.3 ProcVersionSignature: Ubuntu 3.13.0-77.121-generic 3.13.11-ckt32 Uname: Linux 3.13.0-77-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 Date: Fri Feb 12 17:26:19 2016 Dependencies: gcc-4.9-base 4.9.3-0ubuntu4 libc6 2.19-0ubuntu6.6 libgcc1 1:4.9.3-0ubuntu4 multiarch-support 2.19-0ubuntu6.6 DuplicateSignature: package:patch:2.7.1-4ubuntu2.3:package is in a very bad inconsistent state; you should reinstall it before attempting configuration ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2014-09-22 (508 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) RelatedPackageVersions: dpkg 1.17.5ubuntu5.5 apt 1.0.1ubuntu2.11 SourcePackage: patch Title: package patch 2.7.1-4ubuntu2.3 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: patch (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package trusty -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to patch in Ubuntu. https://bugs.launchpad.net/bugs/1545190 Title: package patch 2.7.1-4ubuntu2.3 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in patch package in Ubuntu: New Bug description: all avvio segnale errore nel sisema. non riconosce la tastiera nei tasti speciali ProblemType: Package DistroRelease: Ubuntu 14.04 Package: patch 2.7.1-4ubuntu2.3 ProcVersionSignature: Ubuntu 3.13.0-77.121-generic 3.13.11-ckt32 Uname: Linux 3.13.0-77-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 Date: Fri Feb 12 17:26:19 2016 Dependencies: gcc-4.9-base 4.9.3-0ubuntu4 libc6 2.19-0ubuntu6.6 libgcc1 1:4.9.3-0ubuntu4 multiarch-support 2.19-0ubuntu6.6 DuplicateSignature: package:patch:2.7.1-4ubuntu2.3:package is in a very bad inconsistent state; you should reinstall it before attempting configuration ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2014-09-22 (508 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) RelatedPackageVersions: dpkg 1.17.5ubuntu5.5 apt 1.0.1ubuntu2.11 SourcePackage: patch Title: package patch 2.7.1-4ubuntu2.3 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/patch/+bug/1545190/+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 1545174] Re: can no longer use hands free calling after upgrade to OTA9
** Description changed: I'm on arale, OTA9. With OTA8.5 I could pair, listen to music and make calls with no problem. After upgrading (and without unpairing/re-pairing after upgrading), I can connect to the car, and I can listen to music but if I try to make a call while connected to bluetooth, the car will after a few moments say "the call has been transferred to the phone", - but when I pick up the phone to continue the call, the call appears to - be made (ie, the dialer indicates the call is ongoing) but there is no - sound. I have not tried unpairing and re-pairing. In other words, I can - no longer use hands free calling after upgrading to OTA9. + but when I pick up the phone to continue the call, the call is made (ie, + the dialer indicates the call is ongoing and the person I called sees an + incoming call from me) but there is no sound and the other end cannot + hear me. + + I have not tried unpairing and re-pairing. In other words, I can no + longer use hands free calling after upgrading to OTA9. I'm not sure if this is related, but after OTA9 I can connect to the car and both the phone and the car say they're connected, but then after a second or two it disconnects and then after a while 10-30 seconds, the reconnect and they stay connected. Before, once connected they would stay connected. I'm not sure this is related to bug #1539158 or not, but I was afraid to unpair due to other MX4 users in that bug. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1545174 Title: can no longer use hands free calling after upgrade to OTA9 Status in Canonical System Image: New Status in bluez package in Ubuntu: New Bug description: I'm on arale, OTA9. With OTA8.5 I could pair, listen to music and make calls with no problem. After upgrading (and without unpairing/re- pairing after upgrading), I can connect to the car, and I can listen to music but if I try to make a call while connected to bluetooth, the car will after a few moments say "the call has been transferred to the phone", but when I pick up the phone to continue the call, the call is made (ie, the dialer indicates the call is ongoing and the person I called sees an incoming call from me) but there is no sound and the other end cannot hear me. I have not tried unpairing and re-pairing. In other words, I can no longer use hands free calling after upgrading to OTA9. I'm not sure if this is related, but after OTA9 I can connect to the car and both the phone and the car say they're connected, but then after a second or two it disconnects and then after a while 10-30 seconds, the reconnect and they stay connected. Before, once connected they would stay connected. I'm not sure this is related to bug #1539158 or not, but I was afraid to unpair due to other MX4 users in that bug. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1545174/+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 1545118] Re: can't easily grab scrollbar with mouse if dual column
This was discussed already this week, the UX team will provide a solution to the conflict. The column resizing area was large to allow easy resizing using touch, but since we now could have draggable scrollbars there (on touch as well), the situation has become delicate. Adding ubuntu-ux ** Also affects: ubuntu-ui-toolkit Importance: Undecided Status: New ** No longer affects: ubuntu-ui-toolkit ** Also affects: ubuntu-ux Importance: Undecided Status: New ** Changed in: ubuntu-ux Importance: Undecided => High ** Changed in: ubuntu-ux Importance: High => Medium -- 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/1545118 Title: can't easily grab scrollbar with mouse if dual column Status in Canonical System Image: New Status in Ubuntu UX: New Status in ubuntu-ui-toolkit package in Ubuntu: New Bug description: If you have an app that uses AdaptivePageLayout and supports 2 columns, if there is a scrollbar in the first column, it's very difficult to grab it with your mouse because when you get close to it, you get the horizontal arrows showing to allow resizing of the panels in the multi-column layout. You can try this with messaging-app in silo 30 (soon to land) To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1545118/+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 1341611] Re: [apt-get] The option -f, --fix-broken does not work in LM17 x64
Hello Tomás F. L. I don't know why they changed it. I think you can do the same by two commands: apt-get --fix-broken install apt-get autoclean As for your fixed synopsis, I meant that -f works with also commands upgrade, dist-upgrade and autoremove, as they may install/remove packages, too. But otherwise your synopsis looks good for the -f option. By the way, option -s does works only with commands upgrade, dist-upgrade, install, remove, purge, check, clean, autoclean and autoremove. The manual is not perfect as for autoremove: Bug #1052864 The respective Debian bug was reported on 2009 and is still not fixed. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1341611 Title: [apt-get] The option -f, --fix-broken does not work in LM17 x64 Status in apt package in Ubuntu: New Bug description: Linux Mint 17 Quiana 64 bits (ISO v2) Like root: apt-get -f autoclean E: No se conoce la opción de línea de órdenes «f» [de -f]. apt-get --fix-broken autoclean E: No se entiende la opción de línea de órdenes --fix-broken I verified it in a portable and in a virtual machine, always with the same error: E: There is not known the option of line of orders "f" [of -f]. E: There is not understood the option of line of orders - fix-broken The above mentioned option appears in the apt-get man: -f, --fix-broken Fix; attempt to correct a system with broken dependencies in place. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1341611/+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 1545174] [NEW] can no longer use hands free calling after upgrade to OTA9
Public bug reported: I'm on arale, OTA9. With OTA8.5 I could pair, listen to music and make calls with no problem. After upgrading (and without unpairing/re-pairing after upgrading), I can connect to the car, and I can listen to music but if I try to make a call while connected to bluetooth, the car will after a few moments say "the call has been transferred to the phone", but when I pick up the phone to continue the call, the call appears to be made (ie, the dialer indicates the call is ongoing) but there is no sound. I have not tried unpairing and re-pairing. In other words, I can no longer use hands free calling after upgrading to OTA9. I'm not sure if this is related, but after OTA9 I can connect to the car and both the phone and the car say they're connected, but then after a second or two it disconnects and then after a while 10-30 seconds, the reconnect and they stay connected. Before, once connected they would stay connected. I'm not sure this is related to bug #1539158 or not, but I was afraid to unpair due to other MX4 users in that bug. ** Affects: canonical-devices-system-image Importance: Undecided Status: New ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Tags: bluetooth ** Description changed: I'm on arale, OTA9. With OTA8.5 I could pair, listen to music and make calls with no problem. After upgrading (and without unpairing/re-pairing after upgrading), I can connect to the car, and I can listen to music but if I try to make a call while connected to bluetooth the car after a few moments says "the call has been transferred to the phone", but when I pick up the phone to conduct the call, the call appears to be made but there is no sound. I have not tried unpairing and re-pairing. In other words, I can no longer use hands free calling after upgrading to OTA9. I'm not sure if this is related, but after OTA9 I can connect to the car and both the phone and the car say they're connected, but then after a second or two it disconnects and then after a while 10-30 seconds, the reconnect and they stay connected. Before, once connected they would stay connected. + + I'm not sure this is related to bug #1539158 or not, but I was afraid to + unpair due to other MX4 users in that bug. ** Also affects: canonical-devices-system-image Importance: Undecided Status: New ** Description changed: I'm on arale, OTA9. With OTA8.5 I could pair, listen to music and make calls with no problem. After upgrading (and without unpairing/re-pairing after upgrading), I can connect to the car, and I can listen to music - but if I try to make a call while connected to bluetooth the car after a - few moments says "the call has been transferred to the phone", but when - I pick up the phone to conduct the call, the call appears to be made but - there is no sound. I have not tried unpairing and re-pairing. In other - words, I can no longer use hands free calling after upgrading to OTA9. + but if I try to make a call while connected to bluetooth, the car will + after a few moments say "the call has been transferred to the phone", + but when I pick up the phone to continue the call, the call appears to + be made (ie, the dialer indicates the call is ongoing) but there is no + sound. I have not tried unpairing and re-pairing. In other words, I can + no longer use hands free calling after upgrading to OTA9. I'm not sure if this is related, but after OTA9 I can connect to the car and both the phone and the car say they're connected, but then after a second or two it disconnects and then after a while 10-30 seconds, the reconnect and they stay connected. Before, once connected they would stay connected. I'm not sure this is related to bug #1539158 or not, but I was afraid to unpair due to other MX4 users in that bug. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1545174 Title: can no longer use hands free calling after upgrade to OTA9 Status in Canonical System Image: New Status in bluez package in Ubuntu: New Bug description: I'm on arale, OTA9. With OTA8.5 I could pair, listen to music and make calls with no problem. After upgrading (and without unpairing/re- pairing after upgrading), I can connect to the car, and I can listen to music but if I try to make a call while connected to bluetooth, the car will after a few moments say "the call has been transferred to the phone", but when I pick up the phone to continue the call, the call appears to be made (ie, the dialer indicates the call is ongoing) but there is no sound. I have not tried unpairing and re-pairing. In other words, I can no longer use hands free calling after upgrading to OTA9. I'm not sure if this is related, but after OTA9 I can connect to the car and both the phone and the car say they're connect
[Touch-packages] [Bug 1508081] Re: Fails to receive OTA updates
I'm going to call the signal DownloadStarted. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to system-image in Ubuntu. https://bugs.launchpad.net/bugs/1508081 Title: Fails to receive OTA updates Status in Canonical System Image: In Progress Status in Ubuntu system image: In Progress Status in system-image package in Ubuntu: Confirmed Status in ubuntu-download-manager package in Ubuntu: In Progress Status in ubuntu-system-settings package in Ubuntu: In Progress Bug description: Ubuntu Touch 15.04 (r23) [mako] Issue: Phone appears to fail to receive OTA updates. Previously, I jumped from (r15) to (r23) due to missing OTA updates. Currently, I see (r24) appears to be released on 2015 Oct 16. Expected behavior: System Settings > System > Updates (or System Settings > About this phone > Check for updates) reveals new image that I can release and download. Actual behavior: Checking for updates... > Software is up to date See the comment regarding similar issues for large app installs. It seems if anything interrupts the transfer or if the connection is somewhat slow the download performance degenerates then times out. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1508081/+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 1542098] Re: remove vertical separator in Bluetooth panel
** Changed in: canonical-devices-system-image Status: New => Won't Fix -- 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/1542098 Title: remove vertical separator in Bluetooth panel Status in Canonical System Image: Won't Fix Status in ubuntu-ui-toolkit package in Ubuntu: In Progress Bug description: from design: should not be a vertical separator to left of chevron in list items. Examples: * System Settings “Bluetooth” page * System Settings “Wi-Fi” page To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1542098/+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 1545021] Re: location settings refer to cellular data when no modem is present
** Changed in: ubuntu-system-settings (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to location-service in Ubuntu. https://bugs.launchpad.net/bugs/1545021 Title: location settings refer to cellular data when no modem is present Status in The Avila project: Confirmed Status in Canonical System Image: New Status in location-service package in Ubuntu: New Status in ubuntu-system-settings package in Ubuntu: In Progress Bug description: In system settings & the welcome wizard, the phrase "Using GPS, anonymised wifi and cellular network info'" is used to describe the way HERE gathers data. On non-cellular devices with HERE 'and cellular network info' should be ommitted. To manage notifications about this bug go to: https://bugs.launchpad.net/avila/+bug/1545021/+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 1528625] Re: messaging-app should run confined
This bug was fixed in the package messaging-app - 0.1+16.04.20160205-0ubuntu1 --- messaging-app (0.1+16.04.20160205-0ubuntu1) xenial; urgency=medium [ Arthur Mello ] * Add a thumbnail to MMS previewer after video has ended to reduce visual issues * Add audio attachments text to ThreadDelegate * Add initial QML test for voice recording * Add initial voice recording support. Most of the code was originally written by Arthur Renato Mello. * Add video attachment delegates * During audio playback bar pause instead of stop * Implement swipe-to-cancel for audio recording, and change the UI to be compliant with the designs. [ Gustavo Pichorim Boiko ] * Add audio attachments text to ThreadDelegate * Add delivery status indication on bubbles. * Add fallback accountId to the history filter. * Add initial QML test for voice recording * Add initial voice recording support. Most of the code was originally written by Arthur Renato Mello. * Disable tests that are currently failing. * Display dialog to warn users that the maximum file size was reached. * Do not reload the history filters when just the active accounts have changed. * Enable document attachments. * Fix the swipe to cancel audio recording. * Implement swipe-to-cancel for audio recording, and change the UI to be compliant with the designs. * Load audio and sticker components asynchronously. * Make it possible to share contacts and extra content types (disabled for now). * Move the bottom part of Messages view to a separate QML file for better code readability. * Prototype implementation for stickers support. * Refactor MMSAudio delegate * Show an overlay icon and a background image depending on the protocol used. * Update the bubble to match the designs. [ Tiago Salem Herrmann ] * Add apparmor profile and enable app confinement. (LP: #1528625) * Add delivery status indication on bubbles. * Add fallback accountId to the history filter. * Add video attachment delegates * Display dialog to warn users that the maximum file size was reached. * Load audio and sticker components asynchronously. * Refactor MMSAudio delegate [ Ugo Riboni ] * Prototype implementation for stickers support. -- Gustavo Pichorim Boiko Fri, 05 Feb 2016 01:10:31 + ** Changed in: messaging-app (Ubuntu) Status: Confirmed => Fix Released -- 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/1528625 Title: messaging-app should run confined Status in Canonical System Image: In Progress Status in messaging-app package in Ubuntu: Fix Released Bug description: We're introducing the ability to record audio clips from the messaging-app which will record voice using the microphone. This requires trust-store integration for the prompts and we've been told making the app confined will allow us to get this for free. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1528625/+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 1545157] Re: package libunity-scopes1.0 1.0.3+16.04.20160209-0ubuntu1 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1
*** This bug is a duplicate of bug 1545156 *** https://bugs.launchpad.net/bugs/1545156 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 #1545156, 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. ** Tags removed: need-duplicate-check ** This bug has been marked a duplicate of bug 1545156 package libunity-scopes1.0:amd64 1.0.3+16.04.20160209-0ubuntu1 failed to install/upgrade: package libunity-scopes1.0:amd64 is already installed and configured -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-scopes-api in Ubuntu. https://bugs.launchpad.net/bugs/1545157 Title: package libunity-scopes1.0 1.0.3+16.04.20160209-0ubuntu1 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1 Status in unity-scopes-api package in Ubuntu: New Bug description: On start-up ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libunity-scopes1.0 1.0.3+16.04.20160209-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-5.20-generic 4.4.1 Uname: Linux 4.4.0-5-generic x86_64 ApportVersion: 2.19.4-0ubuntu2 Architecture: amd64 Date: Fri Feb 12 13:58:36 2016 ErrorMessage: subprocess new pre-removal script returned error exit status 1 InstallationDate: Installed on 2016-02-05 (6 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160205) RelatedPackageVersions: dpkg 1.18.4ubuntu1 apt 1.1.10 SourcePackage: unity-scopes-api Title: package libunity-scopes1.0 1.0.3+16.04.20160209-0ubuntu1 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-scopes-api/+bug/1545157/+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 1545161] Re: package libunity-scopes1.0:amd64 1.0.3+16.04.20160209-0ubuntu1 failed to install/upgrade: package libunity-scopes1.0:amd64 is already installed and configured
*** This bug is a duplicate of bug 1545156 *** https://bugs.launchpad.net/bugs/1545156 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 #1545156, 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. ** Tags removed: need-duplicate-check ** This bug has been marked a duplicate of bug 1545156 package libunity-scopes1.0:amd64 1.0.3+16.04.20160209-0ubuntu1 failed to install/upgrade: package libunity-scopes1.0:amd64 is already installed and configured -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-scopes-api in Ubuntu. https://bugs.launchpad.net/bugs/1545161 Title: package libunity-scopes1.0:amd64 1.0.3+16.04.20160209-0ubuntu1 failed to install/upgrade: package libunity-scopes1.0:amd64 is already installed and configured Status in unity-scopes-api package in Ubuntu: New Bug description: On startup ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libunity-scopes1.0:amd64 1.0.3+16.04.20160209-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-5.20-generic 4.4.1 Uname: Linux 4.4.0-5-generic x86_64 ApportVersion: 2.19.4-0ubuntu2 AptdaemonVersion: 1.1.1+bzr982-0ubuntu14 Architecture: amd64 Date: Fri Feb 12 13:59:44 2016 ErrorMessage: package libunity-scopes1.0:amd64 is already installed and configured InstallationDate: Installed on 2016-02-05 (6 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160205) RelatedPackageVersions: dpkg 1.18.4ubuntu1 apt 1.1.10 SourcePackage: unity-scopes-api Title: package libunity-scopes1.0:amd64 1.0.3+16.04.20160209-0ubuntu1 failed to install/upgrade: package libunity-scopes1.0:amd64 is already installed and configured UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-scopes-api/+bug/1545161/+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 1545159] Re: package click 0.4.43+16.04.20160203-0ubuntu1 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 1
*** This bug is a duplicate of bug 1544776 *** https://bugs.launchpad.net/bugs/1544776 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 #1544776, 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. ** Tags removed: need-duplicate-check ** This bug has been marked a duplicate of bug 1544776 package click 0.4.42+16.04.20151229-0ubuntu1 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 1 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to click in Ubuntu. https://bugs.launchpad.net/bugs/1545159 Title: package click 0.4.43+16.04.20160203-0ubuntu1 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 1 Status in click package in Ubuntu: New Bug description: On startup ProblemType: Package DistroRelease: Ubuntu 16.04 Package: click 0.4.43+16.04.20160203-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-5.20-generic 4.4.1 Uname: Linux 4.4.0-5-generic x86_64 ApportVersion: 2.19.4-0ubuntu2 Architecture: amd64 Date: Fri Feb 12 13:57:28 2016 ErrorMessage: subprocess installed pre-removal script returned error exit status 1 InstallationDate: Installed on 2016-02-05 (6 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160205) RelatedPackageVersions: dpkg 1.18.4ubuntu1 apt 1.1.10 SourcePackage: click Title: package click 0.4.43+16.04.20160203-0ubuntu1 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/click/+bug/1545159/+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 1545161] [NEW] package libunity-scopes1.0:amd64 1.0.3+16.04.20160209-0ubuntu1 failed to install/upgrade: package libunity-scopes1.0:amd64 is already installed and configured
*** This bug is a duplicate of bug 1545156 *** https://bugs.launchpad.net/bugs/1545156 Public bug reported: On startup ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libunity-scopes1.0:amd64 1.0.3+16.04.20160209-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-5.20-generic 4.4.1 Uname: Linux 4.4.0-5-generic x86_64 ApportVersion: 2.19.4-0ubuntu2 AptdaemonVersion: 1.1.1+bzr982-0ubuntu14 Architecture: amd64 Date: Fri Feb 12 13:59:44 2016 ErrorMessage: package libunity-scopes1.0:amd64 is already installed and configured InstallationDate: Installed on 2016-02-05 (6 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160205) RelatedPackageVersions: dpkg 1.18.4ubuntu1 apt 1.1.10 SourcePackage: unity-scopes-api Title: package libunity-scopes1.0:amd64 1.0.3+16.04.20160209-0ubuntu1 failed to install/upgrade: package libunity-scopes1.0:amd64 is already installed and configured UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: unity-scopes-api (Ubuntu) Importance: Undecided Status: New ** Tags: already-installed amd64 apport-package package-from-proposed xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-scopes-api in Ubuntu. https://bugs.launchpad.net/bugs/1545161 Title: package libunity-scopes1.0:amd64 1.0.3+16.04.20160209-0ubuntu1 failed to install/upgrade: package libunity-scopes1.0:amd64 is already installed and configured Status in unity-scopes-api package in Ubuntu: New Bug description: On startup ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libunity-scopes1.0:amd64 1.0.3+16.04.20160209-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-5.20-generic 4.4.1 Uname: Linux 4.4.0-5-generic x86_64 ApportVersion: 2.19.4-0ubuntu2 AptdaemonVersion: 1.1.1+bzr982-0ubuntu14 Architecture: amd64 Date: Fri Feb 12 13:59:44 2016 ErrorMessage: package libunity-scopes1.0:amd64 is already installed and configured InstallationDate: Installed on 2016-02-05 (6 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160205) RelatedPackageVersions: dpkg 1.18.4ubuntu1 apt 1.1.10 SourcePackage: unity-scopes-api Title: package libunity-scopes1.0:amd64 1.0.3+16.04.20160209-0ubuntu1 failed to install/upgrade: package libunity-scopes1.0:amd64 is already installed and configured UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-scopes-api/+bug/1545161/+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 1545159] [NEW] package click 0.4.43+16.04.20160203-0ubuntu1 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 1
*** This bug is a duplicate of bug 1544776 *** https://bugs.launchpad.net/bugs/1544776 Public bug reported: On startup ProblemType: Package DistroRelease: Ubuntu 16.04 Package: click 0.4.43+16.04.20160203-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-5.20-generic 4.4.1 Uname: Linux 4.4.0-5-generic x86_64 ApportVersion: 2.19.4-0ubuntu2 Architecture: amd64 Date: Fri Feb 12 13:57:28 2016 ErrorMessage: subprocess installed pre-removal script returned error exit status 1 InstallationDate: Installed on 2016-02-05 (6 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160205) RelatedPackageVersions: dpkg 1.18.4ubuntu1 apt 1.1.10 SourcePackage: click Title: package click 0.4.43+16.04.20160203-0ubuntu1 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: click (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package package-from-proposed xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to click in Ubuntu. https://bugs.launchpad.net/bugs/1545159 Title: package click 0.4.43+16.04.20160203-0ubuntu1 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 1 Status in click package in Ubuntu: New Bug description: On startup ProblemType: Package DistroRelease: Ubuntu 16.04 Package: click 0.4.43+16.04.20160203-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-5.20-generic 4.4.1 Uname: Linux 4.4.0-5-generic x86_64 ApportVersion: 2.19.4-0ubuntu2 Architecture: amd64 Date: Fri Feb 12 13:57:28 2016 ErrorMessage: subprocess installed pre-removal script returned error exit status 1 InstallationDate: Installed on 2016-02-05 (6 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160205) RelatedPackageVersions: dpkg 1.18.4ubuntu1 apt 1.1.10 SourcePackage: click Title: package click 0.4.43+16.04.20160203-0ubuntu1 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/click/+bug/1545159/+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 1545157] [NEW] package libunity-scopes1.0 1.0.3+16.04.20160209-0ubuntu1 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1
Public bug reported: On start-up ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libunity-scopes1.0 1.0.3+16.04.20160209-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-5.20-generic 4.4.1 Uname: Linux 4.4.0-5-generic x86_64 ApportVersion: 2.19.4-0ubuntu2 Architecture: amd64 Date: Fri Feb 12 13:58:36 2016 ErrorMessage: subprocess new pre-removal script returned error exit status 1 InstallationDate: Installed on 2016-02-05 (6 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160205) RelatedPackageVersions: dpkg 1.18.4ubuntu1 apt 1.1.10 SourcePackage: unity-scopes-api Title: package libunity-scopes1.0 1.0.3+16.04.20160209-0ubuntu1 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: unity-scopes-api (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package need-duplicate-check package-from-proposed xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-scopes-api in Ubuntu. https://bugs.launchpad.net/bugs/1545157 Title: package libunity-scopes1.0 1.0.3+16.04.20160209-0ubuntu1 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1 Status in unity-scopes-api package in Ubuntu: New Bug description: On start-up ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libunity-scopes1.0 1.0.3+16.04.20160209-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-5.20-generic 4.4.1 Uname: Linux 4.4.0-5-generic x86_64 ApportVersion: 2.19.4-0ubuntu2 Architecture: amd64 Date: Fri Feb 12 13:58:36 2016 ErrorMessage: subprocess new pre-removal script returned error exit status 1 InstallationDate: Installed on 2016-02-05 (6 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160205) RelatedPackageVersions: dpkg 1.18.4ubuntu1 apt 1.1.10 SourcePackage: unity-scopes-api Title: package libunity-scopes1.0 1.0.3+16.04.20160209-0ubuntu1 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-scopes-api/+bug/1545157/+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 1539446] Re: Today scope hangs-on after OTA9 update
** Also affects: canonical-devices-system-image 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/1539446 Title: Today scope hangs-on after OTA9 update Status in Canonical System Image: New Status in Today Scope: New Status in unity8 package in Ubuntu: New Bug description: really often from Yesterday night (OTA9 updated at 11 p.m.) the Today scope freeze the screen and no other actiion is possibile to achieve. the system restart itself after 20-30 seconds . it happens especially recalling the Today scope by sweeping from Rhs to Lhs to view the full open scopes on the screeen. when you touch the Today scope to acces it (or, as well, if you touch the Ubuntu logo icon in the Unity view) the scope open full screen and the device freeze. no more possibility to acces vertical "courtains" menu (notifications, blutooth, netwoorks a.s.o.) neither any of the other icons. If you send a call to the device SIM number, you can ear (frpm the sender device speaker) the usual network ringigng tone, but nothing happens on the Ubuntu phone . After the self reboot, the lost call is correctly notified on the notification menu. device BQ E5 - Ubuntu 15.04 OTA9 (28/01/2016) - UA001808 available for testing and further info supply Regards and thanks To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1539446/+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 1530807] Re: Bluetooth cannot be activated on several devices
My bq 4.5 does not seem to have this problem in normal usage, so here's how I managed to reproduce it: 1) disable autostart of the bluetooth daemon: $ echo "manual" | sudo tee /etc/init/bluetooth.override 2) reboot your phone 3) wait until everything is loaded, then run: $ sudo start bluetooth After that, the on/off switch in indicator and system settings don't seem to match each other, just like described above in the bug. Also, the bluetooth connection seems to be independent of changes to the switches, since it keeps being discoverable for other devices even any or both of those switches are off. -- 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/1530807 Title: Bluetooth cannot be activated on several devices Status in The Avila project: In Progress Status in Canonical System Image: Confirmed Status in Canonical Pocket Desktop: Confirmed Status in indicator-bluetooth package in Ubuntu: In Progress Status in ubuntu-system-settings package in Ubuntu: Confirmed Bug description: Using RC proposed 04/01/2016 bluetooth cannot be enabled. Tested on a nexus 7. Expected behavior: Bluetooth slider is moved to on Bluetooth activates Available devices appear in the list Experienced behavior: Bluetooth slider is moved to on Activity spinners appear Bluetooth slider moves to off. To manage notifications about this bug go to: https://bugs.launchpad.net/avila/+bug/1530807/+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 1539446] Re: Today scope hangs-on after OTA9 update
Hi Danilo, thanks for the persistence and the logs and etc! So, several times this failure has occurred when tapping on a Unity icon: * comment 18: "- swipe left to right. To access unity A tap on telegram icon to open it." * initial description: "as well, if you touch the Ubuntu logo icon in the Unity view" I am thinking this means it is not related to the today scope. I will email some Unity engineers and bring this to their attention. NOTE: there is a telegram crash file (among others). Thanks! -- 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/1539446 Title: Today scope hangs-on after OTA9 update Status in Today Scope: New Status in unity8 package in Ubuntu: New Bug description: really often from Yesterday night (OTA9 updated at 11 p.m.) the Today scope freeze the screen and no other actiion is possibile to achieve. the system restart itself after 20-30 seconds . it happens especially recalling the Today scope by sweeping from Rhs to Lhs to view the full open scopes on the screeen. when you touch the Today scope to acces it (or, as well, if you touch the Ubuntu logo icon in the Unity view) the scope open full screen and the device freeze. no more possibility to acces vertical "courtains" menu (notifications, blutooth, netwoorks a.s.o.) neither any of the other icons. If you send a call to the device SIM number, you can ear (frpm the sender device speaker) the usual network ringigng tone, but nothing happens on the Ubuntu phone . After the self reboot, the lost call is correctly notified on the notification menu. device BQ E5 - Ubuntu 15.04 OTA9 (28/01/2016) - UA001808 available for testing and further info supply Regards and thanks To manage notifications about this bug go to: https://bugs.launchpad.net/today-scope/+bug/1539446/+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 1502094] Re: libgee-0.8-dev should be used, libgee-dev will be removed from the archive
** Tags added: patch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libfriends in Ubuntu. https://bugs.launchpad.net/bugs/1502094 Title: libgee-0.8-dev should be used, libgee-dev will be removed from the archive Status in indicator-keyboard package in Ubuntu: Fix Released Status in indicator-sound package in Ubuntu: In Progress Status in indicator-sound-gtk2 package in Ubuntu: Fix Released Status in libfriends package in Ubuntu: Fix Released Status in libgee package in Ubuntu: New Status in unity-china-music-scope package in Ubuntu: Fix Released Status in unity-china-video-scope package in Ubuntu: Fix Released Status in unity-lens-applications package in Ubuntu: In Progress Status in unity-lens-files package in Ubuntu: Fix Released Status in unity-lens-friends package in Ubuntu: Fix Released Status in unity-lens-music package in Ubuntu: Fix Released Status in unity-lens-video package in Ubuntu: In Progress Status in unity-scope-home package in Ubuntu: In Progress Status in indicator-keyboard source package in Xenial: Fix Released Status in indicator-sound source package in Xenial: In Progress Status in indicator-sound-gtk2 source package in Xenial: Fix Released Status in libfriends source package in Xenial: Fix Released Status in libgee source package in Xenial: New Status in unity-china-music-scope source package in Xenial: Fix Released Status in unity-china-video-scope source package in Xenial: Fix Released Status in unity-lens-applications source package in Xenial: In Progress Status in unity-lens-files source package in Xenial: Fix Released Status in unity-lens-friends source package in Xenial: Fix Released Status in unity-lens-music source package in Xenial: Fix Released Status in unity-lens-video source package in Xenial: In Progress Status in unity-scope-home source package in Xenial: In Progress Bug description: The libgee source is obsolete, replaced by the libgee-0.8 source. Packages should change their build dependency to libgee-0.8-dev instead. The libgee source was already removed in Debian; it will be removed in Ubuntu as well. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-keyboard/+bug/1502094/+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 1539446] Re: Today scope hangs-on after OTA9 update
** Attachment added: "scope-registry.log" https://bugs.launchpad.net/bugs/1539446/+attachment/4570344/+files/scope-registry.log ** Attachment added: "scope-registry.log.1.gz" https://bugs.launchpad.net/bugs/1539446/+attachment/4570345/+files/scope-registry.log.1.gz ** Attachment added: "scope-registry.log.2.gz" https://bugs.launchpad.net/bugs/1539446/+attachment/4570346/+files/scope-registry.log.2.gz ** Attachment added: "scope-registry.log.3.gz" https://bugs.launchpad.net/bugs/1539446/+attachment/4570347/+files/scope-registry.log.3.gz ** Attachment added: "scope-registry.log.4.gz" https://bugs.launchpad.net/bugs/1539446/+attachment/4570348/+files/scope-registry.log.4.gz ** Attachment added: "scope-registry.log.5.gz" https://bugs.launchpad.net/bugs/1539446/+attachment/4570349/+files/scope-registry.log.5.gz ** Attachment added: "scope-registry.log.6.gz" https://bugs.launchpad.net/bugs/1539446/+attachment/4570350/+files/scope-registry.log.6.gz ** Attachment added: "scope-registry.log.7.gz" https://bugs.launchpad.net/bugs/1539446/+attachment/4570351/+files/scope-registry.log.7.gz -- 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/1539446 Title: Today scope hangs-on after OTA9 update Status in Today Scope: New Status in unity8 package in Ubuntu: New Bug description: really often from Yesterday night (OTA9 updated at 11 p.m.) the Today scope freeze the screen and no other actiion is possibile to achieve. the system restart itself after 20-30 seconds . it happens especially recalling the Today scope by sweeping from Rhs to Lhs to view the full open scopes on the screeen. when you touch the Today scope to acces it (or, as well, if you touch the Ubuntu logo icon in the Unity view) the scope open full screen and the device freeze. no more possibility to acces vertical "courtains" menu (notifications, blutooth, netwoorks a.s.o.) neither any of the other icons. If you send a call to the device SIM number, you can ear (frpm the sender device speaker) the usual network ringigng tone, but nothing happens on the Ubuntu phone . After the self reboot, the lost call is correctly notified on the notification menu. device BQ E5 - Ubuntu 15.04 OTA9 (28/01/2016) - UA001808 available for testing and further info supply Regards and thanks To manage notifications about this bug go to: https://bugs.launchpad.net/today-scope/+bug/1539446/+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 1539446] Today scope hangs-on after OTA9 update
Hi, This is the scenario: A message coming from telegram. Notification already deleted without access phone ( courtain menu). - accessed phone (4 figures code). - today scope on screen - swipe left to right. To access unity A tap on telegram icon to open it. Today scope disappear and white screen waiting for unknown event ( no rounding Ubuntu logo, neither some other vital sign.) - after around 20 secs, system reboots from the raw (Ubuntu in letters and rounding dots). Don't know if it could be related to the topic, but this is the only "strange and unusual" event of the last days, after all other scopes removal. Thanks abdicate regards. D On Wednesday, 10 February 2016 15:12:44 CET, Kyle Nitzsche wrote: > HI Danilo, > > Thanks for your responses! > > Can you please get the following file right after the "freeze" > and attach it to this bug: > /home/phablet/.cache/upstart/scope-registry.log > > Cheers > -- Sent using Dekko from my Ubuntu phone device -- 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/1539446 Title: Today scope hangs-on after OTA9 update Status in Today Scope: New Status in unity8 package in Ubuntu: New Bug description: really often from Yesterday night (OTA9 updated at 11 p.m.) the Today scope freeze the screen and no other actiion is possibile to achieve. the system restart itself after 20-30 seconds . it happens especially recalling the Today scope by sweeping from Rhs to Lhs to view the full open scopes on the screeen. when you touch the Today scope to acces it (or, as well, if you touch the Ubuntu logo icon in the Unity view) the scope open full screen and the device freeze. no more possibility to acces vertical "courtains" menu (notifications, blutooth, netwoorks a.s.o.) neither any of the other icons. If you send a call to the device SIM number, you can ear (frpm the sender device speaker) the usual network ringigng tone, but nothing happens on the Ubuntu phone . After the self reboot, the lost call is correctly notified on the notification menu. device BQ E5 - Ubuntu 15.04 OTA9 (28/01/2016) - UA001808 available for testing and further info supply Regards and thanks To manage notifications about this bug go to: https://bugs.launchpad.net/today-scope/+bug/1539446/+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 1545123] Re: camera viewfinder is black when attaching video from messaging-app
Note, I can reproduce this on mako and arale, but works fine on krillin -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to camera-app in Ubuntu. https://bugs.launchpad.net/bugs/1545123 Title: camera viewfinder is black when attaching video from messaging-app Status in Canonical System Image: New Status in camera-app package in Ubuntu: New Bug description: testing silo 52 (messaging-app) on latest rc-proposed Steps to repro: - open messaging-app - create message - press + button and select video - choose camera app Expected results: camera app is launched with viewfinder active Actual results: camera app is launched with black viewfinder. Note: switching to front camera or swiping app away and back will make the viewfinder appear correctly. Also, you can still record the video even though the viewfinder is black. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1545123/+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 1530807] Re: Bluetooth cannot be activated on several devices
** Changed in: avila Status: Confirmed => In Progress -- 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/1530807 Title: Bluetooth cannot be activated on several devices Status in The Avila project: In Progress Status in Canonical System Image: Confirmed Status in Canonical Pocket Desktop: Confirmed Status in indicator-bluetooth package in Ubuntu: In Progress Status in ubuntu-system-settings package in Ubuntu: Confirmed Bug description: Using RC proposed 04/01/2016 bluetooth cannot be enabled. Tested on a nexus 7. Expected behavior: Bluetooth slider is moved to on Bluetooth activates Available devices appear in the list Experienced behavior: Bluetooth slider is moved to on Activity spinners appear Bluetooth slider moves to off. To manage notifications about this bug go to: https://bugs.launchpad.net/avila/+bug/1530807/+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 1530807] Re: Bluetooth cannot be activated on several devices
I think there is an indicator-datetime issue herer wrt the on/off toggle in the indicator, but there is also a separate issue with the Discoverable / Not Discoverable status being shown in system-settings. indicator-bluetooth doesn't advertise that state; system-settings is getting that from talking to bluez. ** Also affects: ubuntu-system-settings (Ubuntu) Importance: Undecided Status: New ** Changed in: ubuntu-system-settings (Ubuntu) Status: New => Confirmed ** Changed in: ubuntu-system-settings (Ubuntu) Importance: Undecided => Critical -- 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/1530807 Title: Bluetooth cannot be activated on several devices Status in The Avila project: In Progress Status in Canonical System Image: Confirmed Status in Canonical Pocket Desktop: Confirmed Status in indicator-bluetooth package in Ubuntu: In Progress Status in ubuntu-system-settings package in Ubuntu: Confirmed Bug description: Using RC proposed 04/01/2016 bluetooth cannot be enabled. Tested on a nexus 7. Expected behavior: Bluetooth slider is moved to on Bluetooth activates Available devices appear in the list Experienced behavior: Bluetooth slider is moved to on Activity spinners appear Bluetooth slider moves to off. To manage notifications about this bug go to: https://bugs.launchpad.net/avila/+bug/1530807/+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 1528955] Re: Camera app can be uninstalled permanently.
I think the right place to report this bug is Software Center Agent https://launchpad.net/software-center-agent -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to camera-app in Ubuntu. https://bugs.launchpad.net/bugs/1528955 Title: Camera app can be uninstalled permanently. Status in camera-app: New Status in camera-app package in Ubuntu: Confirmed Bug description: When I do long-tapping on the camera app icon, the app store is opened, showing the camera app's descrition. Then it is possible to click on "Uninstall" to unistall the camera app. After that the camera app is uninstalled and no photos can be taken, so far so good. But then it is not possible to reinstall the camera app, because the app can't be found in app store by searching for "camera". This happened on Nexus 4 in stable channel. This did NOT happen on Nexus 4 in rc-proposed channel. This happened on Aquaris E4.5. Further information here: To manage notifications about this bug go to: https://bugs.launchpad.net/camera-app/+bug/1528955/+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 1530807] Re: Bluetooth cannot be activated on several devices
** Changed in: indicator-bluetooth (Ubuntu) Status: Confirmed => In Progress -- 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/1530807 Title: Bluetooth cannot be activated on several devices Status in The Avila project: Confirmed Status in Canonical System Image: Confirmed Status in Canonical Pocket Desktop: Confirmed Status in indicator-bluetooth package in Ubuntu: In Progress Bug description: Using RC proposed 04/01/2016 bluetooth cannot be enabled. Tested on a nexus 7. Expected behavior: Bluetooth slider is moved to on Bluetooth activates Available devices appear in the list Experienced behavior: Bluetooth slider is moved to on Activity spinners appear Bluetooth slider moves to off. To manage notifications about this bug go to: https://bugs.launchpad.net/avila/+bug/1530807/+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 1532358] Re: flaky autopkgtests cause migration issues
** Changed in: unity-scope-click (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 unity-scopes-shell in Ubuntu. https://bugs.launchpad.net/bugs/1532358 Title: flaky autopkgtests cause migration issues Status in Canonical System Image: Fix Committed Status in unity-scope-click package in Ubuntu: Fix Committed Status in unity-scopes-shell package in Ubuntu: Triaged Bug description: A few times recently when unity8 got into xenial-proposed for migration, unity-scope-click's autopkgtest failed on the first run, having passed on the next: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/amd64/u/unity-scope-click/20160105_174239@/log.gz https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/armhf/u/unity-scope-click/20160108_185317@/log.gz https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial-ci-train-ppa-service-landing-030/xenial/armhf/u/unity-scope-click/20160111_213558@/log.gz This delays migration until someone notices the failure and asks for a re-run, which usually passes. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: unity-scope-click 0.1.1+16.04.20151216.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.3.0-5.16-generic 4.3.3 Uname: Linux 4.3.0-5-generic x86_64 ApportVersion: 2.19.3-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Sat Jan 9 00:29:21 2016 SourcePackage: unity-scope-click UpgradeStatus: Upgraded to xenial on 2015-10-28 (72 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1532358/+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 1544615] Re: Can not install, uninstall and install again an app (wihtout rebooting)
** No longer affects: unity-scope-click (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-download-manager in Ubuntu. https://bugs.launchpad.net/bugs/1544615 Title: Can not install, uninstall and install again an app (wihtout rebooting) Status in ubuntu-download-manager package in Ubuntu: New Bug description: Today's rc-proposed How to reproduce: * Have a phone where Dekko is not installed (i guess any other would work, but i'm using Dekko) * reboot the phone * Go to the apps scope * Press on the Ubuntu store icon at the bottom * Press on the Dekko icon * Press the install button * Wait for it to install * Press the uninstall button * Press the confirm button * You're back to the dekko preview with the progress at 0% so you can't install it anymore unless you reboot This seems related or a regression of https://bugs.launchpad.net/ubuntu/+source/unity-scope- click/+bug/1531118 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-download-manager/+bug/1544615/+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 1545123] [NEW] camera viewfinder is black when attaching video from messaging-app
Public bug reported: testing silo 52 (messaging-app) on latest rc-proposed Steps to repro: - open messaging-app - create message - press + button and select video - choose camera app Expected results: camera app is launched with viewfinder active Actual results: camera app is launched with black viewfinder. Note: switching to front camera or swiping app away and back will make the viewfinder appear correctly. Also, you can still record the video even though the viewfinder is black. ** Affects: canonical-devices-system-image Importance: High Assignee: Bill Filler (bfiller) Status: New ** Affects: camera-app (Ubuntu) Importance: High Assignee: Florian Boucault (fboucault) Status: New ** Also affects: camera-app (Ubuntu) Importance: Undecided Status: New ** Changed in: canonical-devices-system-image Milestone: None => ww08-2016 ** Changed in: canonical-devices-system-image Assignee: (unassigned) => Bill Filler (bfiller) ** Changed in: canonical-devices-system-image Importance: Undecided => High ** Changed in: camera-app (Ubuntu) Assignee: (unassigned) => Florian Boucault (fboucault) ** Changed in: camera-app (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to camera-app in Ubuntu. https://bugs.launchpad.net/bugs/1545123 Title: camera viewfinder is black when attaching video from messaging-app Status in Canonical System Image: New Status in camera-app package in Ubuntu: New Bug description: testing silo 52 (messaging-app) on latest rc-proposed Steps to repro: - open messaging-app - create message - press + button and select video - choose camera app Expected results: camera app is launched with viewfinder active Actual results: camera app is launched with black viewfinder. Note: switching to front camera or swiping app away and back will make the viewfinder appear correctly. Also, you can still record the video even though the viewfinder is black. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1545123/+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 1544925] Re: location-service and system-settings have opposite needs from ofono on a non-cellular device
This MP: https://code.launchpad.net/~morphis/avila- private/+git/device_malatamobile_bq_aquaris_m10_FHD/+merge/285903 Made ofono better configured on avila, so this is no longer critical ** Changed in: avila Importance: Critical => High ** Changed in: avila Milestone: ww04-2016 => ww06-2016 ** Changed in: canonical-devices-system-image Importance: Critical => High ** Changed in: canonical-devices-system-image Milestone: ww04-2016 => ww08-2016 ** Changed in: canonical-devices-system-image Assignee: (unassigned) => Bill Filler (bfiller) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to location-service in Ubuntu. https://bugs.launchpad.net/bugs/1544925 Title: location-service and system-settings have opposite needs from ofono on a non-cellular device Status in The Avila project: Confirmed Status in Canonical System Image: Confirmed Status in location-service package in Ubuntu: New Status in ubuntu-system-settings package in Ubuntu: New Bug description: In a set of recent changes to support devices which have no modem, but do have GPS & HERE servcies enabled: - System Settings now tries not to display 'cellular' options - Location service has a hard dependency on ofono starting (bug #1544712) The correct behaviour is for location services to function, and system settings to not display 'cellular' options. In the medium term, ofono will be disabled on devices like this: bug #1544210 To manage notifications about this bug go to: https://bugs.launchpad.net/avila/+bug/1544925/+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 1545078] Re: unity-lens-video fails to build from source (using deprecated vala)
** Changed in: unity-lens-video (Ubuntu) Milestone: None => ubuntu-16.04 ** Changed in: unity-lens-video (Ubuntu) Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) ** Changed in: unity-lens-video (Ubuntu) Status: Confirmed => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-lens-video in Ubuntu. https://bugs.launchpad.net/bugs/1545078 Title: unity-lens-video fails to build from source (using deprecated vala) Status in unity-lens-video package in Ubuntu: In Progress Bug description: Making all in src make[3]: Entering directory '/home/packages/tmp/x/unity-lens-video-0.3.15+13.10.20130920/src' /usr/bin/valac -C --pkg dee-1.0 --pkg unity --pkg unity-extras --pkg gio-2.0 --pkg gio-unix-2.0 --pkg glib-2.0 --pkg gee-0.8 --pkg zeitgeist-1.0 --vapidir . --vapidir ../vapi --target-glib=2.26 blacklist-tracker.vala daemon.vala main.vala locate.vala scope.vala config.vala thumbnailer.vala utils.vala video-file.vala blacklist-tracker.vala:70.37-70.68: warning: unhandled error `GLib.Error' Variant all_templates = yield blacklist_proxy.get_templates (); blacklist-tracker.vala:51.7-51.30: warning: implicit .begin is deprecated blacklist-tracker.vala:57.11-57.26: warning: implicit .begin is deprecated scope.vala:156.29-156.57: error: Argument 1: Cannot convert from `GLib.CompareFunc?' to `GLib.CompareDataFunc?' result_list.sort ((GLib.CompareFunc?)sort_alpha); ^ scope.vala:200.27-200.34: warning: GLib.PtrArray has been deprecated since vala-0.26. Use GenericArray scope.vala:127.15-127.21: warning: implicit .begin is deprecated scope.vala:76.9-76.23: warning: implicit .begin is deprecated scope.vala:293.9-293.35: warning: implicit .begin is deprecated daemon.vala:31.9-31.23: warning: unhandled error `GLib.Error' scope.export (); ^^^ Compilation failed: 1 error(s), 8 warning(s) Makefile:1063: recipe for target 'unity_video_lens_daemon.vala.stamp' failed make[3]: *** [unity_video_lens_daemon.vala.stamp] Error 1 make[3]: Leaving directory '/home/packages/tmp/x/unity-lens-video-0.3.15+13.10.20130920/src' Makefile:451: recipe for target 'all-recursive' failed make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory '/home/packages/tmp/x/unity-lens-video-0.3.15+13.10.20130920' Makefile:382: recipe for target 'all' failed make[1]: *** [all] Error 2 make[1]: Leaving directory '/home/packages/tmp/x/unity-lens-video-0.3.15+13.10.20130920' dh_auto_build: make -j1 returned exit code 2 debian/rules:5: recipe for target 'build' failed make: *** [build] Error 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-lens-video/+bug/1545078/+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 1545078] Re: unity-lens-video fails to build from source (using deprecated vala)
** Branch linked: lp:~3v1n0/unity-lens-video/use-gee-0.8 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-lens-video in Ubuntu. https://bugs.launchpad.net/bugs/1545078 Title: unity-lens-video fails to build from source (using deprecated vala) Status in unity-lens-video package in Ubuntu: In Progress Bug description: Making all in src make[3]: Entering directory '/home/packages/tmp/x/unity-lens-video-0.3.15+13.10.20130920/src' /usr/bin/valac -C --pkg dee-1.0 --pkg unity --pkg unity-extras --pkg gio-2.0 --pkg gio-unix-2.0 --pkg glib-2.0 --pkg gee-0.8 --pkg zeitgeist-1.0 --vapidir . --vapidir ../vapi --target-glib=2.26 blacklist-tracker.vala daemon.vala main.vala locate.vala scope.vala config.vala thumbnailer.vala utils.vala video-file.vala blacklist-tracker.vala:70.37-70.68: warning: unhandled error `GLib.Error' Variant all_templates = yield blacklist_proxy.get_templates (); blacklist-tracker.vala:51.7-51.30: warning: implicit .begin is deprecated blacklist-tracker.vala:57.11-57.26: warning: implicit .begin is deprecated scope.vala:156.29-156.57: error: Argument 1: Cannot convert from `GLib.CompareFunc?' to `GLib.CompareDataFunc?' result_list.sort ((GLib.CompareFunc?)sort_alpha); ^ scope.vala:200.27-200.34: warning: GLib.PtrArray has been deprecated since vala-0.26. Use GenericArray scope.vala:127.15-127.21: warning: implicit .begin is deprecated scope.vala:76.9-76.23: warning: implicit .begin is deprecated scope.vala:293.9-293.35: warning: implicit .begin is deprecated daemon.vala:31.9-31.23: warning: unhandled error `GLib.Error' scope.export (); ^^^ Compilation failed: 1 error(s), 8 warning(s) Makefile:1063: recipe for target 'unity_video_lens_daemon.vala.stamp' failed make[3]: *** [unity_video_lens_daemon.vala.stamp] Error 1 make[3]: Leaving directory '/home/packages/tmp/x/unity-lens-video-0.3.15+13.10.20130920/src' Makefile:451: recipe for target 'all-recursive' failed make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory '/home/packages/tmp/x/unity-lens-video-0.3.15+13.10.20130920' Makefile:382: recipe for target 'all' failed make[1]: *** [all] Error 2 make[1]: Leaving directory '/home/packages/tmp/x/unity-lens-video-0.3.15+13.10.20130920' dh_auto_build: make -j1 returned exit code 2 debian/rules:5: recipe for target 'build' failed make: *** [build] Error 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-lens-video/+bug/1545078/+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 1545118] [NEW] can't easily grab scrollbar with mouse if dual column
Public bug reported: If you have an app that uses AdaptivePageLayout and supports 2 columns, if there is a scrollbar in the first column, it's very difficult to grab it with your mouse because when you get close to it, you get the horizontal arrows showing to allow resizing of the panels in the multi- column layout. You can try this with messaging-app in silo 30 (soon to land) ** Affects: canonical-devices-system-image Importance: Medium Assignee: Zoltan Balogh (bzoltan) Status: New ** Affects: ubuntu-ui-toolkit (Ubuntu) Importance: Medium Assignee: Zoltan Balogh (bzoltan) Status: New ** Changed in: ubuntu-ui-toolkit (Ubuntu) Assignee: (unassigned) => Zoltan Balogh (bzoltan) ** Also affects: canonical-devices-system-image Importance: Undecided Status: New ** Changed in: canonical-devices-system-image Assignee: (unassigned) => Zoltan Balogh (bzoltan) ** Changed in: canonical-devices-system-image Milestone: None => ww08-2016 ** Changed in: canonical-devices-system-image Importance: Undecided => Medium ** Changed in: ubuntu-ui-toolkit (Ubuntu) Importance: Undecided => Medium -- 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/1545118 Title: can't easily grab scrollbar with mouse if dual column Status in Canonical System Image: New Status in ubuntu-ui-toolkit package in Ubuntu: New Bug description: If you have an app that uses AdaptivePageLayout and supports 2 columns, if there is a scrollbar in the first column, it's very difficult to grab it with your mouse because when you get close to it, you get the horizontal arrows showing to allow resizing of the panels in the multi-column layout. You can try this with messaging-app in silo 30 (soon to land) To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1545118/+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 1502094] Re: libgee-0.8-dev should be used, libgee-dev will be removed from the archive
** Changed in: unity-lens-video (Ubuntu Xenial) Status: Confirmed => In Progress ** Changed in: unity-lens-video (Ubuntu Xenial) Assignee: (unassigned) => Matthias Klose (doko) ** Changed in: indicator-sound (Ubuntu Xenial) Status: Confirmed => In Progress ** Changed in: indicator-sound (Ubuntu Xenial) Assignee: Xavi Garcia (xavi-garcia-mena) => Matthias Klose (doko) ** Changed in: unity-lens-applications (Ubuntu Xenial) Status: Confirmed => In Progress ** Changed in: unity-lens-applications (Ubuntu Xenial) Assignee: (unassigned) => Matthias Klose (doko) ** Changed in: unity-scope-home (Ubuntu Xenial) Status: Confirmed => In Progress ** Changed in: unity-scope-home (Ubuntu Xenial) Assignee: (unassigned) => Matthias Klose (doko) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libfriends in Ubuntu. https://bugs.launchpad.net/bugs/1502094 Title: libgee-0.8-dev should be used, libgee-dev will be removed from the archive Status in indicator-keyboard package in Ubuntu: Fix Released Status in indicator-sound package in Ubuntu: In Progress Status in indicator-sound-gtk2 package in Ubuntu: Fix Released Status in libfriends package in Ubuntu: Fix Released Status in libgee package in Ubuntu: New Status in unity-china-music-scope package in Ubuntu: Fix Released Status in unity-china-video-scope package in Ubuntu: Fix Released Status in unity-lens-applications package in Ubuntu: In Progress Status in unity-lens-files package in Ubuntu: Fix Released Status in unity-lens-friends package in Ubuntu: Fix Released Status in unity-lens-music package in Ubuntu: Fix Released Status in unity-lens-video package in Ubuntu: In Progress Status in unity-scope-home package in Ubuntu: In Progress Status in indicator-keyboard source package in Xenial: Fix Released Status in indicator-sound source package in Xenial: In Progress Status in indicator-sound-gtk2 source package in Xenial: Fix Released Status in libfriends source package in Xenial: Fix Released Status in libgee source package in Xenial: New Status in unity-china-music-scope source package in Xenial: Fix Released Status in unity-china-video-scope source package in Xenial: Fix Released Status in unity-lens-applications source package in Xenial: In Progress Status in unity-lens-files source package in Xenial: Fix Released Status in unity-lens-friends source package in Xenial: Fix Released Status in unity-lens-music source package in Xenial: Fix Released Status in unity-lens-video source package in Xenial: In Progress Status in unity-scope-home source package in Xenial: In Progress Bug description: The libgee source is obsolete, replaced by the libgee-0.8 source. Packages should change their build dependency to libgee-0.8-dev instead. The libgee source was already removed in Debian; it will be removed in Ubuntu as well. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-keyboard/+bug/1502094/+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 1545108] [NEW] crontab ignores the day of month, and executes based only on the time and the weekday.
Public bug reported: here is my crontab: 45 5 * * 1-5 pkill -f flash 48 6 * * 1-5 musicalarm 50 9 * * 1-5 mpc random off 30 7 5 2 5 echo -e "I'm not coming in today.\n\nHave a good one!" | mail -s "No pikupordropov needed" em...@example.com Obviously I have changed the email a bit, but it gives you an idea. The email got sent today, even though it is clearly not the 5th of February. Something similar happened a couple days ago (another command that was scheduled for that day, but earlier in the month). ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: cron 3.0pl1-124ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-77.121-generic 3.13.11-ckt32 Uname: Linux 3.13.0-77-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 Date: Fri Feb 12 10:33:41 2016 InstallationDate: Installed on 2014-02-04 (738 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) SourcePackage: cron UpgradeStatus: Upgraded to trusty on 2014-07-20 (571 days ago) ** Affects: cron (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cron in Ubuntu. https://bugs.launchpad.net/bugs/1545108 Title: crontab ignores the day of month, and executes based only on the time and the weekday. Status in cron package in Ubuntu: New Bug description: here is my crontab: 45 5 * * 1-5 pkill -f flash 48 6 * * 1-5 musicalarm 50 9 * * 1-5 mpc random off 30 7 5 2 5 echo -e "I'm not coming in today.\n\nHave a good one!" | mail -s "No pikupordropov needed" em...@example.com Obviously I have changed the email a bit, but it gives you an idea. The email got sent today, even though it is clearly not the 5th of February. Something similar happened a couple days ago (another command that was scheduled for that day, but earlier in the month). ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: cron 3.0pl1-124ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-77.121-generic 3.13.11-ckt32 Uname: Linux 3.13.0-77-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 Date: Fri Feb 12 10:33:41 2016 InstallationDate: Installed on 2014-02-04 (738 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) SourcePackage: cron UpgradeStatus: Upgraded to trusty on 2014-07-20 (571 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cron/+bug/1545108/+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 1544976] Re: [Wishlist] Owner info on lock screen
** Description changed: It would be great if the user is allowed to enter details (owner info) - which will be shown in the circle on the lock screen (like the way one - can do in android) + which will be shown in (or above/below) the circle on the lock screen + (like the way one can do in android) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libusermetrics in Ubuntu. https://bugs.launchpad.net/bugs/1544976 Title: [Wishlist] Owner info on lock screen Status in libusermetrics package in Ubuntu: New Bug description: It would be great if the user is allowed to enter details (owner info) which will be shown in (or above/below) the circle on the lock screen (like the way one can do in android) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libusermetrics/+bug/1544976/+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 1502094] Re: libgee-0.8-dev should be used, libgee-dev will be removed from the archive
This bug was fixed in the package indicator-sound-gtk2 - 12.10.0.1-0ubuntu5 --- indicator-sound-gtk2 (12.10.0.1-0ubuntu5) xenial; urgency=medium * Build using libgee-0.8-dev instead of libgee-dev. LP: #1502094. -- Matthias Klose Fri, 12 Feb 2016 18:00:07 +0100 ** Branch linked: lp:~3v1n0/indicator-sound/use-gee-0.8 ** Branch linked: lp:~3v1n0/unity-lens-applications/use-gee-0.8 ** Branch linked: lp:~3v1n0/unity-lens-video/use-gee-0.8 ** Branch linked: lp:~3v1n0/unity-scope-home/use-gee-0.8 ** Changed in: indicator-sound-gtk2 (Ubuntu Xenial) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libfriends in Ubuntu. https://bugs.launchpad.net/bugs/1502094 Title: libgee-0.8-dev should be used, libgee-dev will be removed from the archive Status in indicator-keyboard package in Ubuntu: Fix Released Status in indicator-sound package in Ubuntu: Confirmed Status in indicator-sound-gtk2 package in Ubuntu: Fix Released Status in libfriends package in Ubuntu: Fix Released Status in libgee package in Ubuntu: New Status in unity-china-music-scope package in Ubuntu: Fix Released Status in unity-china-video-scope package in Ubuntu: Fix Released Status in unity-lens-applications package in Ubuntu: Confirmed Status in unity-lens-files package in Ubuntu: Fix Released Status in unity-lens-friends package in Ubuntu: Fix Released Status in unity-lens-music package in Ubuntu: Fix Released Status in unity-lens-video package in Ubuntu: Confirmed Status in unity-scope-home package in Ubuntu: Confirmed Status in indicator-keyboard source package in Xenial: Fix Released Status in indicator-sound source package in Xenial: Confirmed Status in indicator-sound-gtk2 source package in Xenial: Fix Released Status in libfriends source package in Xenial: Fix Released Status in libgee source package in Xenial: New Status in unity-china-music-scope source package in Xenial: Fix Released Status in unity-china-video-scope source package in Xenial: Fix Released Status in unity-lens-applications source package in Xenial: Confirmed Status in unity-lens-files source package in Xenial: Fix Released Status in unity-lens-friends source package in Xenial: Fix Released Status in unity-lens-music source package in Xenial: Fix Released Status in unity-lens-video source package in Xenial: Confirmed Status in unity-scope-home source package in Xenial: Confirmed Bug description: The libgee source is obsolete, replaced by the libgee-0.8 source. Packages should change their build dependency to libgee-0.8-dev instead. The libgee source was already removed in Debian; it will be removed in Ubuntu as well. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-keyboard/+bug/1502094/+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 1341611] Re: [apt-get] The option -f, --fix-broken does not work in LM17 x64
Hello Jarno Suni.
If the operation is as you say, that [-f | --fix-broken] only work with
install, remove or purge, the manual should be as follows.
[-f] removed from common options [-sqdymubV] and moved to like this:
apt-get [-sqdymubV] [-o= config_string ] [-c= config_file ]
[-t= target_release] [-a= default_architecture] {update |
upgrade | dselect-upgrade | dist-upgrade |
{ [ { -f | --fix-broken } ] install pkg [ { =pkg_version_number
| /target_release } ] ...
| remove pkg... | purge pkg... | }
source pkg [ { =pkg_version_number | /target_release } ] ... |
build-dep pkg... | check | clean | autoclean | autoremove |
{-v | --version} | {-h | --help}}
With this [-f] only affects to install, remove and purge, no? And check,
clean, autoclean, etc isn't affect. It's an example.
Correct?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1341611
Title:
[apt-get] The option -f, --fix-broken does not work in LM17 x64
Status in apt package in Ubuntu:
New
Bug description:
Linux Mint 17 Quiana 64 bits (ISO v2)
Like root:
apt-get -f autoclean
E: No se conoce la opción de línea de órdenes «f» [de -f].
apt-get --fix-broken autoclean
E: No se entiende la opción de línea de órdenes --fix-broken
I verified it in a portable and in a virtual machine, always with the same
error:
E: There is not known the option of line of orders "f" [of -f].
E: There is not understood the option of line of orders - fix-broken
The above mentioned option appears in the apt-get man:
-f, --fix-broken
Fix; attempt to correct a system with broken dependencies in place.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1341611/+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 923876] Re: FR: Limit and clean-up kernel images and headers automatically
For another thing, original bug reporter Sam_ seems to be after the ability of GUI package managers to handle removing old kernels. Current fix does not seem to fix the issue with e.g. update-manager. There is another bug report about it: Bug #1389620 Also unattended-upgrades are involved: Bug #1054927 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/923876 Title: FR: Limit and clean-up kernel images and headers automatically Status in apt package in Ubuntu: Fix Released Status in aptitude package in Ubuntu: Fix Released Status in apt source package in Precise: Fix Released Status in aptitude source package in Precise: Confirmed Status in apt source package in Quantal: Fix Released Status in aptitude source package in Quantal: Won't Fix Bug description: Question #186146 is one among multiple where user unintentionally collects multiple kernel images in particular with LTS. There is no hint from relevant package management application GUIs which advise to clean up those images. With future LTS support of five years the issue presumable will extend. Expected. After installation of a newer kernel image ask the user if previous kernel images should be removed. Checkbox: yes - no If yes, offer a list of installed kernel images, don't list the one booted. Advise to keep at least the last functional one. Also remove -headers. Perhaps an additional consideration for the blueprint. https://blueprints.launchpad.net/ubuntu/+spec/foundations-p-lts-upgrades There is a new Quantal blueprint regarding the subject. https://blueprints.launchpad.net/ubuntu/+spec/desktop-q-clean-old-kernels To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/923876/+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 1543790] Re: OOBE not designed well for the tablet screen size
** Changed in: unity8 (Ubuntu) Status: New => In Progress ** Changed in: unity8 (Ubuntu) Assignee: (unassigned) => Lukáš Tinkl (lukas-kde) -- 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/1543790 Title: OOBE not designed well for the tablet screen size Status in Canonical System Image: Confirmed Status in Ubuntu UX: New Status in unity8 package in Ubuntu: In Progress Bug description: The UI is quite odd on a wide landscape mode tablet Language selector should not be the entire width of the tablet in landscape Lock security selection shows a check mark on far right hand side of the screen and is very hard to detect Need to select the box on far right hand side for the Access point The Wifi screen never updated to show the AP was connected, and so it never changed from Skip to Continue After completing the wizard the lock screen is shown but the passcode is not required, tapping opens it To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1543790/+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 1528955] Re: Camera app can be uninstalled permanently.
If it can help, the deb file of the camera apps for ubuntu touch for manual reinstall ** Attachment added: "camera app ubuntu touch 3.0.0 .deb" https://bugs.launchpad.net/camera-app/+bug/1528955/+attachment/4570217/+files/camera-app_3.0.0+15.04.20160114-0ubuntu1_armhf.deb -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to camera-app in Ubuntu. https://bugs.launchpad.net/bugs/1528955 Title: Camera app can be uninstalled permanently. Status in camera-app: New Status in camera-app package in Ubuntu: Confirmed Bug description: When I do long-tapping on the camera app icon, the app store is opened, showing the camera app's descrition. Then it is possible to click on "Uninstall" to unistall the camera app. After that the camera app is uninstalled and no photos can be taken, so far so good. But then it is not possible to reinstall the camera app, because the app can't be found in app store by searching for "camera". This happened on Nexus 4 in stable channel. This did NOT happen on Nexus 4 in rc-proposed channel. This happened on Aquaris E4.5. Further information here: To manage notifications about this bug go to: https://bugs.launchpad.net/camera-app/+bug/1528955/+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 1528955] Re: Camera app can be uninstalled permanently.
Hello anupam, I don't have yout issue, very strange. I'm not ubuntu touch os specialist, but maybe your camera binary was not deleted when you accidentaly uninstall it, only the shortcut on main screen ? When you have reinstalled the system encountered the old version and put it also in the main scope ? Do you have reinstalled this app after ota9 update or before ? for me it was in OTA 8,5. Maybe look with apt-cache search camera-app if you have the both app with different version number ? If yes you can choose to uninstall the one you don't want, with one linux command like this "apt-get uninstall camera-appX" Possibly another solution using apps like "tweakgeek" or "ubuntu touch tweak tool". Very bad solution, you look for the location of the apps with "find / -name "camera"" in the terminal, look for the main app folder, look for the oldest version and delete it and refresh main scope or reboot, maybe the unliked app diseapear, but at your own risk :-( I've put the .deb camera app if it can help anyone to manually reinstall. Anupam, if I was In your situation, I keep the two version in case of :-) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to camera-app in Ubuntu. https://bugs.launchpad.net/bugs/1528955 Title: Camera app can be uninstalled permanently. Status in camera-app: New Status in camera-app package in Ubuntu: Confirmed Bug description: When I do long-tapping on the camera app icon, the app store is opened, showing the camera app's descrition. Then it is possible to click on "Uninstall" to unistall the camera app. After that the camera app is uninstalled and no photos can be taken, so far so good. But then it is not possible to reinstall the camera app, because the app can't be found in app store by searching for "camera". This happened on Nexus 4 in stable channel. This did NOT happen on Nexus 4 in rc-proposed channel. This happened on Aquaris E4.5. Further information here: To manage notifications about this bug go to: https://bugs.launchpad.net/camera-app/+bug/1528955/+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 1544776] Re: package click 0.4.42+16.04.20151229-0ubuntu1 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 1
I confirm that python3-click-package did installed without issues in a one of the upgrades I did today. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to click in Ubuntu. https://bugs.launchpad.net/bugs/1544776 Title: package click 0.4.42+16.04.20151229-0ubuntu1 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 1 Status in click package in Ubuntu: Fix Released Bug description: happend while upgrading from xenial-proposed ProblemType: Package DistroRelease: Ubuntu 16.04 Package: click 0.4.42+16.04.20151229-0ubuntu1 Uname: Linux 4.4.1-040401-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.19.4-0ubuntu2 Architecture: amd64 Date: Thu Feb 11 23:28:44 2016 ErrorMessage: subprocess installed pre-removal script returned error exit status 1 InstallationDate: Installed on 2016-01-26 (16 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) RelatedPackageVersions: dpkg 1.18.4ubuntu1 apt 1.1.10 SourcePackage: click Title: package click 0.4.42+16.04.20151229-0ubuntu1 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/click/+bug/1544776/+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 923876] Re: FR: Limit and clean-up kernel images and headers automatically
As for apt, does the fix offered to this bug mean that you can upgrade by sudo apt-get dist-upgrade and have no fear of /boot getting full? Anyway, I suppose this method of upgrading will work now for the issue in Trusty and later: sudo apt-get dist-upgrade --auto-remove --purge sudo apt-get autoremove may also remove other packages besides old kernels and related packages, but maybe that is not bad thing. If I install a kernel manually by `apt-get install`, it will be marked as "manual", and will not be removed by `apt-get autoremove`, unless I run `apt-mark auto` for it first. Isn't is bad to skip removing any manually installed kernels? Would it be better to skip only kernels marked as "hold"? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/923876 Title: FR: Limit and clean-up kernel images and headers automatically Status in apt package in Ubuntu: Fix Released Status in aptitude package in Ubuntu: Fix Released Status in apt source package in Precise: Fix Released Status in aptitude source package in Precise: Confirmed Status in apt source package in Quantal: Fix Released Status in aptitude source package in Quantal: Won't Fix Bug description: Question #186146 is one among multiple where user unintentionally collects multiple kernel images in particular with LTS. There is no hint from relevant package management application GUIs which advise to clean up those images. With future LTS support of five years the issue presumable will extend. Expected. After installation of a newer kernel image ask the user if previous kernel images should be removed. Checkbox: yes - no If yes, offer a list of installed kernel images, don't list the one booted. Advise to keep at least the last functional one. Also remove -headers. Perhaps an additional consideration for the blueprint. https://blueprints.launchpad.net/ubuntu/+spec/foundations-p-lts-upgrades There is a new Quantal blueprint regarding the subject. https://blueprints.launchpad.net/ubuntu/+spec/desktop-q-clean-old-kernels To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/923876/+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 1545091] [NEW] package systemd 225-1ubuntu9 failed to install/upgrade: Unterprozess installiertes post-installation-Skript gab den Fehlerwert 1 zurück
Public bug reported: post-installation-Skript gab den Fehlerwert 1 zurück ProblemType: Package DistroRelease: Ubuntu 15.10 Package: systemd 225-1ubuntu9 ProcVersionSignature: Ubuntu 3.19.0-49.55-generic 3.19.8-ckt12 Uname: Linux 3.19.0-49-generic i686 ApportVersion: 2.17.2-0ubuntu1.8 Architecture: i386 Date: Fri Feb 12 18:07:53 2016 DuplicateSignature: package:systemd:225-1ubuntu9:Unterprozess installiertes post-installation-Skript gab den Fehlerwert 1 zurück ErrorMessage: Unterprozess installiertes post-installation-Skript gab den Fehlerwert 1 zurück InstallationDate: Installed on 2014-11-18 (451 days ago) InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Release i386 (20141022.1) MachineType: ASUSTeK Computer INC. 1005PX ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-49-generic root=UUID=6b7d7a62-87dd-493d-bf57-ee2b18a548cb ro quiet splash vt.handoff=7 RelatedPackageVersions: dpkg 1.17.25ubuntu1.1 apt 1.0.9.7ubuntu4.2 SourcePackage: systemd Title: package systemd 225-1ubuntu9 failed to install/upgrade: Unterprozess installiertes post-installation-Skript gab den Fehlerwert 1 zurück UpgradeStatus: Upgraded to wily on 2016-02-12 (0 days ago) dmi.bios.date: 08/12/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0904 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: 1001PX dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: x.xx dmi.chassis.asset.tag: 0x dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK Computer INC. dmi.chassis.version: x.x dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0904:bd08/12/2010:svnASUSTeKComputerINC.:pn1005PX:pvrx.x:rvnASUSTeKComputerINC.:rn1001PX:rvrx.xx:cvnASUSTeKComputerINC.:ct10:cvrx.x: dmi.product.name: 1005PX dmi.product.version: x.x dmi.sys.vendor: ASUSTeK Computer INC. ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package i386 third-party-packages wily -- 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/1545091 Title: package systemd 225-1ubuntu9 failed to install/upgrade: Unterprozess installiertes post-installation-Skript gab den Fehlerwert 1 zurück Status in systemd package in Ubuntu: New Bug description: post-installation-Skript gab den Fehlerwert 1 zurück ProblemType: Package DistroRelease: Ubuntu 15.10 Package: systemd 225-1ubuntu9 ProcVersionSignature: Ubuntu 3.19.0-49.55-generic 3.19.8-ckt12 Uname: Linux 3.19.0-49-generic i686 ApportVersion: 2.17.2-0ubuntu1.8 Architecture: i386 Date: Fri Feb 12 18:07:53 2016 DuplicateSignature: package:systemd:225-1ubuntu9:Unterprozess installiertes post-installation-Skript gab den Fehlerwert 1 zurück ErrorMessage: Unterprozess installiertes post-installation-Skript gab den Fehlerwert 1 zurück InstallationDate: Installed on 2014-11-18 (451 days ago) InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Release i386 (20141022.1) MachineType: ASUSTeK Computer INC. 1005PX ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-49-generic root=UUID=6b7d7a62-87dd-493d-bf57-ee2b18a548cb ro quiet splash vt.handoff=7 RelatedPackageVersions: dpkg 1.17.25ubuntu1.1 apt 1.0.9.7ubuntu4.2 SourcePackage: systemd Title: package systemd 225-1ubuntu9 failed to install/upgrade: Unterprozess installiertes post-installation-Skript gab den Fehlerwert 1 zurück UpgradeStatus: Upgraded to wily on 2016-02-12 (0 days ago) dmi.bios.date: 08/12/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0904 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: 1001PX dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: x.xx dmi.chassis.asset.tag: 0x dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK Computer INC. dmi.chassis.version: x.x dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0904:bd08/12/2010:svnASUSTeKComputerINC.:pn1005PX:pvrx.x:rvnASUSTeKComputerINC.:rn1001PX:rvrx.xx:cvnASUSTeKComputerINC.:ct10:cvrx.x: dmi.product.name: 1005PX dmi.product.version: x.x dmi.sys.vendor: ASUSTeK Computer INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1545091/+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 1544776] Re: package click 0.4.42+16.04.20151229-0ubuntu1 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 1
This bug was fixed in the package click - 0.4.43+16.04.20160203-0ubuntu2 --- click (0.4.43+16.04.20160203-0ubuntu2) xenial; urgency=medium * Fix python3-click-package -> python3-click Replaces version (LP: #1544776). -- Colin Watson Fri, 12 Feb 2016 11:10:43 + ** Changed in: click (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to click in Ubuntu. https://bugs.launchpad.net/bugs/1544776 Title: package click 0.4.42+16.04.20151229-0ubuntu1 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 1 Status in click package in Ubuntu: Fix Released Bug description: happend while upgrading from xenial-proposed ProblemType: Package DistroRelease: Ubuntu 16.04 Package: click 0.4.42+16.04.20151229-0ubuntu1 Uname: Linux 4.4.1-040401-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.19.4-0ubuntu2 Architecture: amd64 Date: Thu Feb 11 23:28:44 2016 ErrorMessage: subprocess installed pre-removal script returned error exit status 1 InstallationDate: Installed on 2016-01-26 (16 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) RelatedPackageVersions: dpkg 1.18.4ubuntu1 apt 1.1.10 SourcePackage: click Title: package click 0.4.42+16.04.20151229-0ubuntu1 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/click/+bug/1544776/+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 1545091] Re: package systemd 225-1ubuntu9 failed to install/upgrade: Unterprozess installiertes post-installation-Skript gab den Fehlerwert 1 zurück
** 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/1545091 Title: package systemd 225-1ubuntu9 failed to install/upgrade: Unterprozess installiertes post-installation-Skript gab den Fehlerwert 1 zurück Status in systemd package in Ubuntu: New Bug description: post-installation-Skript gab den Fehlerwert 1 zurück ProblemType: Package DistroRelease: Ubuntu 15.10 Package: systemd 225-1ubuntu9 ProcVersionSignature: Ubuntu 3.19.0-49.55-generic 3.19.8-ckt12 Uname: Linux 3.19.0-49-generic i686 ApportVersion: 2.17.2-0ubuntu1.8 Architecture: i386 Date: Fri Feb 12 18:07:53 2016 DuplicateSignature: package:systemd:225-1ubuntu9:Unterprozess installiertes post-installation-Skript gab den Fehlerwert 1 zurück ErrorMessage: Unterprozess installiertes post-installation-Skript gab den Fehlerwert 1 zurück InstallationDate: Installed on 2014-11-18 (451 days ago) InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Release i386 (20141022.1) MachineType: ASUSTeK Computer INC. 1005PX ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-49-generic root=UUID=6b7d7a62-87dd-493d-bf57-ee2b18a548cb ro quiet splash vt.handoff=7 RelatedPackageVersions: dpkg 1.17.25ubuntu1.1 apt 1.0.9.7ubuntu4.2 SourcePackage: systemd Title: package systemd 225-1ubuntu9 failed to install/upgrade: Unterprozess installiertes post-installation-Skript gab den Fehlerwert 1 zurück UpgradeStatus: Upgraded to wily on 2016-02-12 (0 days ago) dmi.bios.date: 08/12/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0904 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: 1001PX dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: x.xx dmi.chassis.asset.tag: 0x dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK Computer INC. dmi.chassis.version: x.x dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0904:bd08/12/2010:svnASUSTeKComputerINC.:pn1005PX:pvrx.x:rvnASUSTeKComputerINC.:rn1001PX:rvrx.xx:cvnASUSTeKComputerINC.:ct10:cvrx.x: dmi.product.name: 1005PX dmi.product.version: x.x dmi.sys.vendor: ASUSTeK Computer INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1545091/+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 1525474] Re: Indic characters are not visible
for missing fonts issue, the best option is to include ttf-indic-fonts package -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-touch-meta in Ubuntu. https://bugs.launchpad.net/bugs/1525474 Title: Indic characters are not visible Status in ubuntu-touch-meta package in Ubuntu: Confirmed Bug description: Ubuntu Touch is not displaying characters of many Indic scripts including Bengali (except Devnagari). Any app or webpage containing characters from these scripts are shown blank. A quick examination of /usr/share/fonts showed that the required fonts were missing. After I added fonts myself, rendering was okay. I am proposing the addition of the following packages. ttf-bengali-fonts ttf-gujarati-fonts ttf-kannada-fonts These packages would allow the rendering of the most popular indic fonts in use. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-touch-meta/+bug/1525474/+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 1502094] Re: libgee-0.8-dev should be used, libgee-dev will be removed from the archive
** Tags added: u7-trello-import ** Also affects: libgee (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: indicator-sound (Ubuntu Xenial) Importance: High Assignee: Xavi Garcia (xavi-garcia-mena) Status: Confirmed ** Also affects: unity-lens-applications (Ubuntu Xenial) Importance: High Status: Confirmed ** Also affects: unity-lens-files (Ubuntu Xenial) Importance: High Status: Fix Released ** Also affects: unity-lens-music (Ubuntu Xenial) Importance: Undecided Status: Fix Released ** Also affects: unity-lens-video (Ubuntu Xenial) Importance: High Status: Confirmed ** Also affects: indicator-sound-gtk2 (Ubuntu Xenial) Importance: High Status: Confirmed ** Also affects: libfriends (Ubuntu Xenial) Importance: Undecided Status: Fix Released ** Also affects: unity-lens-friends (Ubuntu Xenial) Importance: Undecided Status: Fix Released ** Also affects: unity-china-music-scope (Ubuntu Xenial) Importance: Undecided Status: Fix Released ** Also affects: unity-scope-home (Ubuntu Xenial) Importance: High Status: Confirmed ** Also affects: indicator-keyboard (Ubuntu Xenial) Importance: Low Status: Fix Released ** Also affects: unity-china-video-scope (Ubuntu Xenial) Importance: Undecided Status: Fix Released ** Tags removed: u7-trello-import ** Tags added: rls-x-incoming -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libfriends in Ubuntu. https://bugs.launchpad.net/bugs/1502094 Title: libgee-0.8-dev should be used, libgee-dev will be removed from the archive Status in indicator-keyboard package in Ubuntu: Fix Released Status in indicator-sound package in Ubuntu: Confirmed Status in indicator-sound-gtk2 package in Ubuntu: Confirmed Status in libfriends package in Ubuntu: Fix Released Status in libgee package in Ubuntu: New Status in unity-china-music-scope package in Ubuntu: Fix Released Status in unity-china-video-scope package in Ubuntu: Fix Released Status in unity-lens-applications package in Ubuntu: Confirmed Status in unity-lens-files package in Ubuntu: Fix Released Status in unity-lens-friends package in Ubuntu: Fix Released Status in unity-lens-music package in Ubuntu: Fix Released Status in unity-lens-video package in Ubuntu: Confirmed Status in unity-scope-home package in Ubuntu: Confirmed Status in indicator-keyboard source package in Xenial: Fix Released Status in indicator-sound source package in Xenial: Confirmed Status in indicator-sound-gtk2 source package in Xenial: Confirmed Status in libfriends source package in Xenial: Fix Released Status in libgee source package in Xenial: New Status in unity-china-music-scope source package in Xenial: Fix Released Status in unity-china-video-scope source package in Xenial: Fix Released Status in unity-lens-applications source package in Xenial: Confirmed Status in unity-lens-files source package in Xenial: Fix Released Status in unity-lens-friends source package in Xenial: Fix Released Status in unity-lens-music source package in Xenial: Fix Released Status in unity-lens-video source package in Xenial: Confirmed Status in unity-scope-home source package in Xenial: Confirmed Bug description: The libgee source is obsolete, replaced by the libgee-0.8 source. Packages should change their build dependency to libgee-0.8-dev instead. The libgee source was already removed in Debian; it will be removed in Ubuntu as well. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-keyboard/+bug/1502094/+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 1511072] Re: Language selector scrolling performance is poor in welcome wizard
** Changed in: unity8 (Ubuntu) Status: Triaged => In Progress -- 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/1511072 Title: Language selector scrolling performance is poor in welcome wizard Status in unity8 package in Ubuntu: In Progress Bug description: Device: krillin Image version: 159 Channel: ubuntu-touch/rc-proposed/bq-aquaris.en Scrolling in the language selector is slow. In the image reported above, the list doesn't even scroll automatically if you swipe. It just moves two or three items down and stops. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1511072/+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 1502094] Re: libgee-0.8-dev should be used, libgee-dev will be removed from the archive
** Patch added: "indicator-sound.diff" https://bugs.launchpad.net/ubuntu/+source/indicator-sound/+bug/1502094/+attachment/4570156/+files/indicator-sound.diff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-scope-home in Ubuntu. https://bugs.launchpad.net/bugs/1502094 Title: libgee-0.8-dev should be used, libgee-dev will be removed from the archive Status in indicator-keyboard package in Ubuntu: Fix Released Status in indicator-sound package in Ubuntu: Confirmed Status in indicator-sound-gtk2 package in Ubuntu: Confirmed Status in libfriends package in Ubuntu: Fix Released Status in libgee package in Ubuntu: New Status in unity-china-music-scope package in Ubuntu: Fix Released Status in unity-china-video-scope package in Ubuntu: Fix Released Status in unity-lens-applications package in Ubuntu: Confirmed Status in unity-lens-files package in Ubuntu: Fix Released Status in unity-lens-friends package in Ubuntu: Fix Released Status in unity-lens-music package in Ubuntu: Fix Released Status in unity-lens-video package in Ubuntu: Confirmed Status in unity-scope-home package in Ubuntu: Confirmed Bug description: The libgee source is obsolete, replaced by the libgee-0.8 source. Packages should change their build dependency to libgee-0.8-dev instead. The libgee source was already removed in Debian; it will be removed in Ubuntu as well. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-keyboard/+bug/1502094/+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 1502094] Re: libgee-0.8-dev should be used, libgee-dev will be removed from the archive
** Patch added: "unity-lens-video.diff" https://bugs.launchpad.net/ubuntu/+source/indicator-sound/+bug/1502094/+attachment/4570154/+files/unity-lens-video.diff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-scope-home in Ubuntu. https://bugs.launchpad.net/bugs/1502094 Title: libgee-0.8-dev should be used, libgee-dev will be removed from the archive Status in indicator-keyboard package in Ubuntu: Fix Released Status in indicator-sound package in Ubuntu: Confirmed Status in indicator-sound-gtk2 package in Ubuntu: Confirmed Status in libfriends package in Ubuntu: Fix Released Status in libgee package in Ubuntu: New Status in unity-china-music-scope package in Ubuntu: Fix Released Status in unity-china-video-scope package in Ubuntu: Fix Released Status in unity-lens-applications package in Ubuntu: Confirmed Status in unity-lens-files package in Ubuntu: Fix Released Status in unity-lens-friends package in Ubuntu: Fix Released Status in unity-lens-music package in Ubuntu: Fix Released Status in unity-lens-video package in Ubuntu: Confirmed Status in unity-scope-home package in Ubuntu: Confirmed Bug description: The libgee source is obsolete, replaced by the libgee-0.8 source. Packages should change their build dependency to libgee-0.8-dev instead. The libgee source was already removed in Debian; it will be removed in Ubuntu as well. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-keyboard/+bug/1502094/+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 1502094] Re: libgee-0.8-dev should be used, libgee-dev will be removed from the archive
** Patch added: "unity-scope-home.diff" https://bugs.launchpad.net/ubuntu/+source/indicator-sound/+bug/1502094/+attachment/4570155/+files/unity-scope-home.diff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-scope-home in Ubuntu. https://bugs.launchpad.net/bugs/1502094 Title: libgee-0.8-dev should be used, libgee-dev will be removed from the archive Status in indicator-keyboard package in Ubuntu: Fix Released Status in indicator-sound package in Ubuntu: Confirmed Status in indicator-sound-gtk2 package in Ubuntu: Confirmed Status in libfriends package in Ubuntu: Fix Released Status in libgee package in Ubuntu: New Status in unity-china-music-scope package in Ubuntu: Fix Released Status in unity-china-video-scope package in Ubuntu: Fix Released Status in unity-lens-applications package in Ubuntu: Confirmed Status in unity-lens-files package in Ubuntu: Fix Released Status in unity-lens-friends package in Ubuntu: Fix Released Status in unity-lens-music package in Ubuntu: Fix Released Status in unity-lens-video package in Ubuntu: Confirmed Status in unity-scope-home package in Ubuntu: Confirmed Bug description: The libgee source is obsolete, replaced by the libgee-0.8 source. Packages should change their build dependency to libgee-0.8-dev instead. The libgee source was already removed in Debian; it will be removed in Ubuntu as well. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-keyboard/+bug/1502094/+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 1347788] Re: find crashed when current working directory is not readable and -exec or -execdir used
Dave Chiluk (chiluk) wrote on 2016-01-07: #11
> Findutils just released a new blessed stable version 4.6.0
[...]
> What are the chances of getting this included into xenial?
Xenial is now at > 4.6. (4.6.0+git+20160126-2 )
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to findutils in Ubuntu.
https://bugs.launchpad.net/bugs/1347788
Title:
find crashed when current working directory is not readable and -exec
or -execdir used
Status in findutils package in Ubuntu:
Confirmed
Status in findutils source package in Xenial:
Confirmed
Bug description:
bug is similar to https://savannah.gnu.org/bugs/?15384 but for current
directory (when it not readable or not executable)
steps to reproduce
DIR=`mktemp -d`
cd $DIR
mkdir -p 1/1 2
cd 2
find $DIR/1 -type d -exec echo {} \;
find $DIR/1 -type d -execdir echo {} \;
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: findutils 4.4.2-7
Uname: Linux 3.15.4-031504-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.2
Architecture: amd64
CurrentDesktop: GNOME
Date: Wed Jul 23 20:17:19 2014
Dependencies:
gcc-4.9-base 4.9-20140406-0ubuntu1
libc6 2.19-0ubuntu6
libgcc1 1:4.9-20140406-0ubuntu1
multiarch-support 2.19-0ubuntu6
InstallationDate: Installed on 2014-04-24 (89 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
SourcePackage: findutils
UpgradeStatus: No upgrade log present (probably fresh install)
---
ApportVersion: 2.14.1-0ubuntu3.2
Architecture: amd64
CurrentDesktop: GNOME
Dependencies:
gcc-4.9-base 4.9-20140406-0ubuntu1
libc6 2.19-0ubuntu6
libgcc1 1:4.9-20140406-0ubuntu1
multiarch-support 2.19-0ubuntu6
DistroRelease: Ubuntu 14.04
InstallationDate: Installed on 2014-04-24 (89 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
Package: findutils 4.4.2-7
PackageArchitecture: amd64
Tags: trusty
Uname: Linux 3.15.4-031504-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/findutils/+bug/1347788/+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 1502094] Re: libgee-0.8-dev should be used, libgee-dev will be removed from the archive
** Patch added: "unity-lens-applications.diff" https://bugs.launchpad.net/ubuntu/+source/indicator-sound/+bug/1502094/+attachment/4570153/+files/unity-lens-applications.diff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-scope-home in Ubuntu. https://bugs.launchpad.net/bugs/1502094 Title: libgee-0.8-dev should be used, libgee-dev will be removed from the archive Status in indicator-keyboard package in Ubuntu: Fix Released Status in indicator-sound package in Ubuntu: Confirmed Status in indicator-sound-gtk2 package in Ubuntu: Confirmed Status in libfriends package in Ubuntu: Fix Released Status in libgee package in Ubuntu: New Status in unity-china-music-scope package in Ubuntu: Fix Released Status in unity-china-video-scope package in Ubuntu: Fix Released Status in unity-lens-applications package in Ubuntu: Confirmed Status in unity-lens-files package in Ubuntu: Fix Released Status in unity-lens-friends package in Ubuntu: Fix Released Status in unity-lens-music package in Ubuntu: Fix Released Status in unity-lens-video package in Ubuntu: Confirmed Status in unity-scope-home package in Ubuntu: Confirmed Bug description: The libgee source is obsolete, replaced by the libgee-0.8 source. Packages should change their build dependency to libgee-0.8-dev instead. The libgee source was already removed in Debian; it will be removed in Ubuntu as well. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-keyboard/+bug/1502094/+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 1341611] Re: [apt-get] The option -f, --fix-broken does not work in LM17 x64
Hello Jarno Suni. I use the program Bleachbit for cleaning the system of unnecessary files. When that program detected a fault, this indicated me that i would use that command to fix the fault. In LM13 works without problems but in LM17 fails and/or is the wrong command or the manual. The operation of the command has changed with the change of version, LM13 to LM17, but the manual is the same and therefore something must be wrong, don't you think so? This was a year ago and now I no longer use Linux Mint, i changed to Manjaro OpenRC because I don't like systemD. Thanks. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1341611 Title: [apt-get] The option -f, --fix-broken does not work in LM17 x64 Status in apt package in Ubuntu: New Bug description: Linux Mint 17 Quiana 64 bits (ISO v2) Like root: apt-get -f autoclean E: No se conoce la opción de línea de órdenes «f» [de -f]. apt-get --fix-broken autoclean E: No se entiende la opción de línea de órdenes --fix-broken I verified it in a portable and in a virtual machine, always with the same error: E: There is not known the option of line of orders "f" [of -f]. E: There is not understood the option of line of orders - fix-broken The above mentioned option appears in the apt-get man: -f, --fix-broken Fix; attempt to correct a system with broken dependencies in place. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1341611/+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 1543351] Re: osk with puritine apps
** Also affects: unity8 (Ubuntu) Importance: Undecided Status: New ** Also affects: ubuntu-ux Importance: Undecided Status: New ** Description changed: we currently can't interact with puritine apps relying on the OSK - wondering if we could add this ability + + to add this feature in where text-box selection on an xapp results in + triggering the osk, in unity8 would be a very large/complicated effort. + However, with a manual capability to trigger the OSK this could be + achieved. + + For design team + one idea was to add a show/hide button for the OSK. + realizing this may be undesirable to add another indicator item - a follow-on idea might be to add an alpha button in the corner of the xmir-root window (the window that holds any xapp at the moment) + this way the button presence would only be limited to the Xapp interaction. -- 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/1543351 Title: osk with puritine apps Status in Canonical Pocket Desktop: New Status in Ubuntu UX: New Status in unity8 package in Ubuntu: New Status in xorg-server package in Ubuntu: Confirmed Bug description: we currently can't interact with puritine apps relying on the OSK to add this feature in where text-box selection on an xapp results in triggering the osk, in unity8 would be a very large/complicated effort. However, with a manual capability to trigger the OSK this could be achieved. For design team one idea was to add a show/hide button for the OSK. realizing this may be undesirable to add another indicator item - a follow-on idea might be to add an alpha button in the corner of the xmir-root window (the window that holds any xapp at the moment) this way the button presence would only be limited to the Xapp interaction. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-pocket-desktop/+bug/1543351/+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 1545078] [NEW] unity-lens-video fails to build from source (using deprecated vala)
Public bug reported: Making all in src make[3]: Entering directory '/home/packages/tmp/x/unity-lens-video-0.3.15+13.10.20130920/src' /usr/bin/valac -C --pkg dee-1.0 --pkg unity --pkg unity-extras --pkg gio-2.0 --pkg gio-unix-2.0 --pkg glib-2.0 --pkg gee-0.8 --pkg zeitgeist-1.0 --vapidir . --vapidir ../vapi --target-glib=2.26 blacklist-tracker.vala daemon.vala main.vala locate.vala scope.vala config.vala thumbnailer.vala utils.vala video-file.vala blacklist-tracker.vala:70.37-70.68: warning: unhandled error `GLib.Error' Variant all_templates = yield blacklist_proxy.get_templates (); blacklist-tracker.vala:51.7-51.30: warning: implicit .begin is deprecated blacklist-tracker.vala:57.11-57.26: warning: implicit .begin is deprecated scope.vala:156.29-156.57: error: Argument 1: Cannot convert from `GLib.CompareFunc?' to `GLib.CompareDataFunc?' result_list.sort ((GLib.CompareFunc?)sort_alpha); ^ scope.vala:200.27-200.34: warning: GLib.PtrArray has been deprecated since vala-0.26. Use GenericArray scope.vala:127.15-127.21: warning: implicit .begin is deprecated scope.vala:76.9-76.23: warning: implicit .begin is deprecated scope.vala:293.9-293.35: warning: implicit .begin is deprecated daemon.vala:31.9-31.23: warning: unhandled error `GLib.Error' scope.export (); ^^^ Compilation failed: 1 error(s), 8 warning(s) Makefile:1063: recipe for target 'unity_video_lens_daemon.vala.stamp' failed make[3]: *** [unity_video_lens_daemon.vala.stamp] Error 1 make[3]: Leaving directory '/home/packages/tmp/x/unity-lens-video-0.3.15+13.10.20130920/src' Makefile:451: recipe for target 'all-recursive' failed make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory '/home/packages/tmp/x/unity-lens-video-0.3.15+13.10.20130920' Makefile:382: recipe for target 'all' failed make[1]: *** [all] Error 2 make[1]: Leaving directory '/home/packages/tmp/x/unity-lens-video-0.3.15+13.10.20130920' dh_auto_build: make -j1 returned exit code 2 debian/rules:5: recipe for target 'build' failed make: *** [build] Error 2 ** Affects: unity-lens-video (Ubuntu) Importance: Critical Status: Confirmed ** Tags: ftbfs -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-lens-video in Ubuntu. https://bugs.launchpad.net/bugs/1545078 Title: unity-lens-video fails to build from source (using deprecated vala) Status in unity-lens-video package in Ubuntu: Confirmed Bug description: Making all in src make[3]: Entering directory '/home/packages/tmp/x/unity-lens-video-0.3.15+13.10.20130920/src' /usr/bin/valac -C --pkg dee-1.0 --pkg unity --pkg unity-extras --pkg gio-2.0 --pkg gio-unix-2.0 --pkg glib-2.0 --pkg gee-0.8 --pkg zeitgeist-1.0 --vapidir . --vapidir ../vapi --target-glib=2.26 blacklist-tracker.vala daemon.vala main.vala locate.vala scope.vala config.vala thumbnailer.vala utils.vala video-file.vala blacklist-tracker.vala:70.37-70.68: warning: unhandled error `GLib.Error' Variant all_templates = yield blacklist_proxy.get_templates (); blacklist-tracker.vala:51.7-51.30: warning: implicit .begin is deprecated blacklist-tracker.vala:57.11-57.26: warning: implicit .begin is deprecated scope.vala:156.29-156.57: error: Argument 1: Cannot convert from `GLib.CompareFunc?' to `GLib.CompareDataFunc?' result_list.sort ((GLib.CompareFunc?)sort_alpha); ^ scope.vala:200.27-200.34: warning: GLib.PtrArray has been deprecated since vala-0.26. Use GenericArray scope.vala:127.15-127.21: warning: implicit .begin is deprecated scope.vala:76.9-76.23: warning: implicit .begin is deprecated scope.vala:293.9-293.35: warning: implicit .begin is deprecated daemon.vala:31.9-31.23: warning: unhandled error `GLib.Error' scope.export (); ^^^ Compilation failed: 1 error(s), 8 warning(s) Makefile:1063: recipe for target 'unity_video_lens_daemon.vala.stamp' failed make[3]: *** [unity_video_lens_daemon.vala.stamp] Error 1 make[3]: Leaving directory '/home/packages/tmp/x/unity-lens-video-0.3.15+13.10.20130920/src' Makefile:451: recipe for target 'all-recursive' failed make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory '/home/packages/tmp/x/unity-lens-video-0.3.15+13.10.20130920' Makefile:382: recipe for target 'all' failed make[1]: *** [all] Error 2 make[1]: Leaving directory '/home/packages/tmp/x/unity-lens-video-0.3.15+13.10.20130920' dh_auto_build: make -j1 returned exit code 2 debian/rules:5: recipe for target 'build' failed make: *** [build] Error 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-lens-video/+bug/154
[Touch-packages] [Bug 1466479] Re: "Searching for available drivers..." gives no indication of progress
I just discovered that the code already includes a progress bar:
self.label_driver_detail = Gtk.Label(label=_("Searching for available "
"drivers..."), **props)
self.box_driver_detail.add(self.label_driver_detail)
self.progress_bar = Gtk.ProgressBar()
self.box_driver_action.pack_end(self.progress_bar, False, False, 0)
self.progress_bar.set_visible(False)
Unfortunately there doesn’t seem to be any code that makes that progress
bar visible.
Anyway, specification updated.
** Changed in: software-properties (Ubuntu)
Status: In Progress => Triaged
** Changed in: software-properties (Ubuntu)
Assignee: Matthew Paul Thomas (mpt) => (unassigned)
** Description changed:
software-properties 0.92.37.3, Ubuntu 14.04
1. Open System Settings > "Software & Updates".
2. Choose "Additional Drivers".
3. Wait 30 seconds.
What you see:
2. The text "Searching for available drivers..." centered in the box, but no
other hint of progress.
3. A list of drivers.
What you should see:
2. A progress bar, if the driver search has determinate progress; otherwise a
spinner.
+
+ : “The
+ ‘Additional Drivers’ tab should begin with a listbox containing a
+ progress bar and the text ‘Searching for available drivers…’ until the
+ search is complete.”
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to software-properties in
Ubuntu.
https://bugs.launchpad.net/bugs/1466479
Title:
"Searching for available drivers..." gives no indication of progress
Status in software-properties package in Ubuntu:
Triaged
Bug description:
software-properties 0.92.37.3, Ubuntu 14.04
1. Open System Settings > "Software & Updates".
2. Choose "Additional Drivers".
3. Wait 30 seconds.
What you see:
2. The text "Searching for available drivers..." centered in the box, but no
other hint of progress.
3. A list of drivers.
What you should see:
2. A progress bar, if the driver search has determinate progress; otherwise a
spinner.
: “The
‘Additional Drivers’ tab should begin with a listbox containing a
progress bar and the text ‘Searching for available drivers…’ until the
search is complete.”
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1466479/+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 1540119] Re: [camera] improve preview and time to take next picture
** Changed in: camera-app (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 camera-app in Ubuntu. https://bugs.launchpad.net/bugs/1540119 Title: [camera] improve preview and time to take next picture Status in Canonical System Image: In Progress Status in Ubuntu UX: In Progress Status in camera-app package in Ubuntu: Fix Committed Bug description: improve the time it takes to snap pictures. investigate the cost of screen capture, animation, blocking on i/o, doing the minimal amount of things before re-enabling the shutter button. Most likely this will involve a change to the UX design to improve performance. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1540119/+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 1442050] Re: (colord:832): Cd-WARNING **: failed to get session [pid 690]: Unknown error -2
And now they came back again after todays udpates -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to colord in Ubuntu. https://bugs.launchpad.net/bugs/1442050 Title: (colord:832): Cd-WARNING **: failed to get session [pid 690]: Unknown error -2 Status in colord package in Ubuntu: Confirmed Bug description: Get that error logged into journalctl (colord:832): Cd-WARNING **: failed to get session [pid 690]: Unknown error -2 ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: systemd 219-6ubuntu3 ProcVersionSignature: Ubuntu 3.19.0-12.12-generic 3.19.3 Uname: Linux 3.19.0-12-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.17-0ubuntu1 Architecture: i386 CurrentDesktop: GNOME Date: Thu Apr 9 11:57:02 2015 Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 002: ID 046d:c50e Logitech, Inc. Cordless Mouse Receiver Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: ASUSTEK COMPUTER INC P5W DH Deluxe ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-12-generic root=UUID=7b1f4a51-558f-468f-85e0-f815d2f791e1 ro SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/22/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3002 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5W DH Deluxe dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3002:bd07/22/2010:svnASUSTEKCOMPUTERINC:pnP5WDHDeluxe:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5WDHDeluxe:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: P5W DH Deluxe dmi.product.version: System Version dmi.sys.vendor: ASUSTEK COMPUTER INC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/colord/+bug/1442050/+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 1428591] Re: Dash crashes when trying to authenticate soundcloud scope with google, empty auth page
I confirm that the update has not fixed the bug on my BQ e5. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to signon-ui in Ubuntu. https://bugs.launchpad.net/bugs/1428591 Title: Dash crashes when trying to authenticate soundcloud scope with google, empty auth page Status in Canonical System Image: Confirmed Status in Unity SoundCloud Scope: New Status in signon-ui package in Ubuntu: Confirmed Status in unity-scopes-shell package in Ubuntu: Confirmed Bug description: 1. Go to Soundcloud scope 2. Hit Log-in to SoundCloud button 3. Choose 'Sign in with Google' on the SoundCloud auth page 4. Fill in google account credentials, confirm soundcloud permissions Result: a blank page with 'Cancel' button, no way to navigate back, hitting it crashes the dash (I couldn't get a usable backtrace). NB, this works fine when authenticating using a genuine Soundcloud account. It seems like authenticating via Google is causing the problem. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1428591/+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 1544612] Re: Missing fix for 1299975 claimed to be in pm-utils (1.4.1-13ubuntu0.1)
** Tags added: regression-release ** Changed in: pm-utils (Ubuntu) Assignee: (unassigned) => Martin Pitt (pitti) ** Tags removed: trusty ** Tags added: rls-x-incomingtrusty ** Tags removed: rls-x-incomingtrusty ** Tags added: rls-x-incoming trusty -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pm-utils in Ubuntu. https://bugs.launchpad.net/bugs/1544612 Title: Missing fix for 1299975 claimed to be in pm-utils (1.4.1-13ubuntu0.1) Status in pm-utils package in Ubuntu: New Bug description: The patch debian/patches/17-fix-wireless-hook.patch for bug 1299975 is supposed to be applied in pm-utils (1.4.1-13ubuntu0.1) but is not installed in that version from trusty-updates. The file /usr/lib/pm-utils/power.d/wireless dated 2014-07-15 16:15 (attached) supposedly installed by the updated package still contains line 23 [ "$(cat /sys/class/net/$1/device/enabled)" = "1" ] || return 1 which should be [ "$(cat /sys/class/net/$1/device/enable)" = "1" ] || return 1 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: pm-utils 1.4.1-13ubuntu0.1 [modified: usr/lib/pm-utils/pm-functions] ProcVersionSignature: Ubuntu 3.13.0-78.122-generic 3.13.11-ckt33 Uname: Linux 3.13.0-78-generic i686 ApportVersion: 2.14.1-0ubuntu3.19 Architecture: i386 CurrentDesktop: LXDE Date: Thu Feb 11 15:10:05 2016 InstallationDate: Installed on 2014-07-15 (576 days ago) InstallationMedia: Lubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140416.2) PackageArchitecture: all SourcePackage: pm-utils UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pm-utils/+bug/1544612/+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 1502094] Re: libgee-0.8-dev should be used, libgee-dev will be removed from the archive
this really has to be fixed. having both versions is probably not what we want ** Changed in: unity-lens-video (Ubuntu) Importance: Undecided => High ** Changed in: unity-lens-video (Ubuntu) Status: New => Confirmed ** Changed in: unity-lens-video (Ubuntu) Milestone: None => ubuntu-16.02 ** Changed in: unity-scope-home (Ubuntu) Importance: Undecided => High ** Changed in: unity-scope-home (Ubuntu) Status: New => Confirmed ** Changed in: unity-scope-home (Ubuntu) Milestone: None => ubuntu-16.02 ** Changed in: unity-lens-applications (Ubuntu) Importance: Undecided => High ** Changed in: unity-lens-applications (Ubuntu) Status: New => Confirmed ** Changed in: indicator-sound-gtk2 (Ubuntu) Importance: Undecided => High ** Changed in: indicator-sound-gtk2 (Ubuntu) Status: New => Confirmed ** Changed in: indicator-sound-gtk2 (Ubuntu) Milestone: None => ubuntu-16.02 ** Changed in: indicator-sound (Ubuntu) Importance: Undecided => High ** Changed in: indicator-sound (Ubuntu) Status: New => Confirmed ** Changed in: indicator-sound (Ubuntu) Milestone: None => ubuntu-16.02 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-scope-home in Ubuntu. https://bugs.launchpad.net/bugs/1502094 Title: libgee-0.8-dev should be used, libgee-dev will be removed from the archive Status in indicator-keyboard package in Ubuntu: Fix Released Status in indicator-sound package in Ubuntu: Confirmed Status in indicator-sound-gtk2 package in Ubuntu: Confirmed Status in libfriends package in Ubuntu: Fix Released Status in libgee package in Ubuntu: New Status in unity-china-music-scope package in Ubuntu: Fix Released Status in unity-china-video-scope package in Ubuntu: Fix Released Status in unity-lens-applications package in Ubuntu: Confirmed Status in unity-lens-files package in Ubuntu: Fix Released Status in unity-lens-friends package in Ubuntu: Fix Released Status in unity-lens-music package in Ubuntu: Fix Released Status in unity-lens-video package in Ubuntu: Confirmed Status in unity-scope-home package in Ubuntu: Confirmed Bug description: The libgee source is obsolete, replaced by the libgee-0.8 source. Packages should change their build dependency to libgee-0.8-dev instead. The libgee source was already removed in Debian; it will be removed in Ubuntu as well. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-keyboard/+bug/1502094/+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 1211110] Re: network manager openvpn dns push data not updating system DNS addresses
Thank you Zephyr for the tip. That does help me automate the login somewhat. As for the fix Sam mentioned, I've been applying every update available for 15.10 and while I thought it was fixed after initial testing, I have found that the DNS is still leaking after subsequent tests. I admit though I have not yet installed 16.04 to verify the fix. Fingers crossed that it really is finally fixed! -- 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/120 Title: network manager openvpn dns push data not updating system DNS addresses Status in network-manager package in Ubuntu: Confirmed Status in openvpn package in Ubuntu: Confirmed Bug description: When IPv4 Method is set to Automatic VPN, DNS address recieved from OpenVPN server do not update resolv.conf. This can be achieved when using a standard openvpn config file by adding the lines: script-security 2 up /etc/openvpn/update-resolv-conf down /etc/openvpn/update-resolv-conf In Network-manager there seems to be no option to run connection specific scripts and the DNS data from the server is ignored. Ubuntu 13.04 Network-manager 0.9.8.0-0ubuntu6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/120/+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 798414] Re: update-initramfs should produce a more helpful error when there isn't enough free space
df -h | grep -E '(10|9)[0-9]%\s+/boot' && sudo apt-get autoremove -- 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/798414 Title: update-initramfs should produce a more helpful error when there isn't enough free space Status in initramfs-tools: New Status in initramfs-tools package in Ubuntu: Confirmed Bug description: Binary package hint: initramfs-tools When generating a new initramfs there is no check for available free space, subsequently its possible for update-initramfs to fail due to a lack of free space. This is resulting in package installation failures for initramfs-tools. For example: Setting up initramfs-tools (0.98.8ubuntu3) ... update-initramfs: deferring update (trigger activated) Processing triggers for initramfs-tools ... update-initramfs: Generating /boot/initrd.img-2.6.38-8-generic gzip: stdout: No space left on device E: mkinitramfs failure cpio 141 gzip 1 update-initramfs: failed for /boot/initrd.img-2.6.38-8-generic dpkg: error processing initramfs-tools (--configure): subprocess installed post-installation script returned error exit status 1 WORKAROUND: Remove unused kernels using computer janitor (not in repositories for 14.04 or later) or manually free space on your partition containing the /boot file system. To manage notifications about this bug go to: https://bugs.launchpad.net/initramfs-tools/+bug/798414/+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 1513813] Re: unity8 windowed mode should cascade
** Also affects: canonical-devices-system-image Importance: Undecided Status: New ** Changed in: canonical-devices-system-image Milestone: None => ww08-2016 ** Changed in: canonical-devices-system-image Assignee: (unassigned) => Michał Sawicz (saviq) ** Changed in: canonical-devices-system-image Importance: Undecided => High ** Changed in: canonical-devices-system-image Status: New => In Progress ** Changed in: canonical-pocket-desktop Status: New => In Progress -- 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/1513813 Title: unity8 windowed mode should cascade Status in Canonical System Image: In Progress Status in Canonical Pocket Desktop: In Progress Status in unity8 package in Ubuntu: In Progress Bug description: when launching transitioning to windowed mode or launching applications in windowed mode, each window by default is the same size and locates to the same default location. would be nicer to cascade To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1513813/+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 1530807] Re: Bluetooth cannot be activated on several devices
** Changed in: avila Milestone: ww06-2016 => ww04-2016 -- 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/1530807 Title: Bluetooth cannot be activated on several devices Status in The Avila project: Confirmed Status in Canonical System Image: Confirmed Status in Canonical Pocket Desktop: Confirmed Status in indicator-bluetooth package in Ubuntu: Confirmed Bug description: Using RC proposed 04/01/2016 bluetooth cannot be enabled. Tested on a nexus 7. Expected behavior: Bluetooth slider is moved to on Bluetooth activates Available devices appear in the list Experienced behavior: Bluetooth slider is moved to on Activity spinners appear Bluetooth slider moves to off. To manage notifications about this bug go to: https://bugs.launchpad.net/avila/+bug/1530807/+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 1542002] Re: browser chrashes a lot in Pocket Desktop
** Changed in: webbrowser-app (Ubuntu) Importance: Undecided => Critical ** Also affects: canonical-devices-system-image Importance: Undecided Status: New ** Changed in: canonical-devices-system-image Importance: Undecided => Critical -- 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/1542002 Title: browser chrashes a lot in Pocket Desktop Status in Canonical System Image: New Status in Canonical Pocket Desktop: New Status in webbrowser-app package in Ubuntu: Incomplete Bug description: the default browser constantly seems to crash when set up as pocket desktop. For example when viewing this page: http://www.digitaltrends.com/mobile/bq-aquaris-m10-ubuntu-edition-tablet-news Also when using google docs, and even launch pad. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1542002/+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 1445064] Re: Re-implement container crash forwarding
** Branch linked: lp:apport -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1445064 Title: Re-implement container crash forwarding Status in apport package in Ubuntu: Fix Committed Bug description: The container crash forwarding feature must be re-implemented to use a safe design. The current thought is: - Introduce a systemd unit and upstart job to have a socket activated apport crash handler - When a crash comes from a container, have apport connect to the socket in the crashed process' root, write the arguments it received to the socket. - The crash handler in the container will then run and close the socket when it doesn't need the crashed process anymore. - The host crash handler then exits. This means that we only rely on an accessible root directory for the crashed process and the crash handler will be spawned by init inside that container. This makes it safe for privileged and unprivileged containers. As an extra security measure, rate limiting should be added so that we can only have 10 in-flight crashes and that any crash taking more than 30s to be handled get cancelled (preventing host DoS). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1445064/+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 1445064] Re: Re-implement container crash forwarding
** Changed in: apport (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 apport in Ubuntu. https://bugs.launchpad.net/bugs/1445064 Title: Re-implement container crash forwarding Status in apport package in Ubuntu: Fix Committed Bug description: The container crash forwarding feature must be re-implemented to use a safe design. The current thought is: - Introduce a systemd unit and upstart job to have a socket activated apport crash handler - When a crash comes from a container, have apport connect to the socket in the crashed process' root, write the arguments it received to the socket. - The crash handler in the container will then run and close the socket when it doesn't need the crashed process anymore. - The host crash handler then exits. This means that we only rely on an accessible root directory for the crashed process and the crash handler will be spawned by init inside that container. This makes it safe for privileged and unprivileged containers. As an extra security measure, rate limiting should be added so that we can only have 10 in-flight crashes and that any crash taking more than 30s to be handled get cancelled (preventing host DoS). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1445064/+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 1544010] Re: Splash screen and trust prompt for camera displayed in portrait
Yes, Nexus 7 has this behaviour. -- 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/1544010 Title: Splash screen and trust prompt for camera displayed in portrait Status in Canonical System Image: Triaged Status in unity8 package in Ubuntu: Triaged Bug description: STEPS: 1. Flash the latest rc-proposed to a tablet 2. Open the camera app EXPECTED: I expect the app loading icon to be in the right orientation to the device ACTUAL: The icon is rotated 90° to the left To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1544010/+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 990887] Re: LightDM does not suspend when lid is closed
I experience the same problem. When someone closes my laptop lid, when no-one is logged in, the laptop keeps running and gets seriously hot like a toaster oven. It is bound to fry one day. Please increase the priority of this issue. I'm running: Distributor ID: Ubuntu Description:Ubuntu 12.04.5 LTS Release:12.04 Codename: precise -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/990887 Title: LightDM does not suspend when lid is closed Status in lightdm package in Ubuntu: Confirmed Bug description: Until ubuntu 11.10, when I closed the lid in lightdm the computer suspended. In Ubuntu 12.04, this behavior stopped to work while at the login screen (lightdm). When logged in on Unity or Gnome, closing the lid suspends normally as expected. I think that this is a bug, since all configurations panels, and configurations files I found out, was saying that when closing the lid, the computer will suspend. I've changed from lightdm to gdm using dpkg-reconfigure gdm and with gdm when closing the lid the computer suspend normally as expected. But I really prefer lightdm, and I would like to make this work as worked in lightdm on Ubuntu 11.10. thanks! ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: lightdm 1.2.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-24.37-generic 3.2.14 Uname: Linux 3.2.0-24-generic i686 NonfreeKernelModules: wl nvidia ApportVersion: 2.0.1-0ubuntu7 Architecture: i386 Date: Sun Apr 29 00:32:37 2012 InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5) ProcEnviron: LANGUAGE=pt_BR:en TERM=xterm PATH=(custom, no user) LANG=pt_BR.UTF-8 SHELL=/bin/bash SourcePackage: lightdm UpgradeStatus: Upgraded to precise on 2012-04-28 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/990887/+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 1541631] Re: MX4 today scope inconsistent date and alignment with OTA-9
*** This bug is a duplicate of bug 1540490 *** https://bugs.launchpad.net/bugs/1540490 Hi Kyle, Thanks for your reply and suggestion to use Today scope cached data when there is no wifi or 3G (even with refresh) . I think the same idea should be applied to other scopes as they have the same issue (blank screen with refresh). Note, I have been using my MX4 as my normal phone and used it on a recent trip to Germany. Moving between phone providers (roaming) , flying (flight mode) , time zones etc is bring up these sorts of issues. Having the ability to read cashed data would also be good during a plane flight, train journey etc. Thanks for your support, Regards Dave On Wed, 2016-02-03 at 23:48 +, Kyle Nitzsche wrote: > cached data instead -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-scopes-shell in Ubuntu. https://bugs.launchpad.net/bugs/1541631 Title: MX4 today scope inconsistent date and alignment with OTA-9 Status in Today Scope: New Status in unity-scopes-shell package in Ubuntu: New Status in unity8 package in Ubuntu: New Bug description: Hi I am using an MX4 with OTA-9 update. After updating to OTA-9 the Today scope sometimes cuts the day date icon in half and the scope is out of alignment with gaps between some sections. Please see screen capture attached. This is random and changes when you refresh the scope, but does not clear the problem. If I then use settings to remove the (untick Day info) , then add it again the problem is resolved. As a general comment, the Today scope is still very, plus other issues such as , slow to update, random results, fixed position for items selected so you cant put your high priority items such as news near the top. No option to add background picture (as every other OS does and all main stream users will expect this) As this is the main information scope for the phone I would have thought it should be given a lot of attention improving the performance etc (refresh is still painfully slow even on a fast internet connection). When you loose wifi and have no 3G the Today scope can be almost blank when switching the phone out of sleep or turning it on. I wonder if you could at least save all the previous data from the last wifi connection and show that as I don’t think your typical Android or apple user will accept a blank main screen. The today scope should also have custom backgrounds, these could then be used for all scopes if selected. Anyway sorry for going on and thanks for fixing the camera pinch to zoom (fine now on the MX4). I know its a thankless task and us users don’t help, I wish I could but I more of a hardware man. Just to say your all doing a great job and anything you can do to improve the Today scope is much appreciated, Regards Dave H To manage notifications about this bug go to: https://bugs.launchpad.net/today-scope/+bug/1541631/+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 1384243] Re: photos edited in gallery do not display edited in "My Photos" scope
fixed with com.canonical.scopes.photos-local_1.27_armhf.click in clicks branch. Penk, can you please arrange for QA? ** Changed in: savilerow Status: Confirmed => Fix Committed ** Changed in: savilerow Assignee: (unassigned) => Penk Chen (penk) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-scopes-shell in Ubuntu. https://bugs.launchpad.net/bugs/1384243 Title: photos edited in gallery do not display edited in "My Photos" scope Status in The Savilerow project: Fix Committed Status in Thumbnailer: Invalid Status in unity-scopes-api package in Ubuntu: Invalid Status in unity-scopes-shell package in Ubuntu: Invalid Bug description: I opened a photo from My Photos scope Preview > Open in the gallery. Rotate it. When I return to the scope, fully refreshed, the photo does not display rotated. Wait for scope to exit and then refresh it: still not rotated. Restart unity8-dash: now it displays rotated. I would expect dash toolkit to honor the edited state of a photo and display it rotated as appropriate. Note: Gallery app uses a URI that starts with image://thumbnailer/absPathToPhoto to display photos with correct rotation. However, scopes require the URI starts with photo://. Without that, the Open button on the preview does not open the photo in gallery. To manage notifications about this bug go to: https://bugs.launchpad.net/savilerow/+bug/1384243/+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 1544010] Re: Splash screen and trust prompt for camera displayed in portrait
By "tablet" you mean a Nexus 7? That info is relevant. -- 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/1544010 Title: Splash screen and trust prompt for camera displayed in portrait Status in Canonical System Image: Triaged Status in unity8 package in Ubuntu: Triaged Bug description: STEPS: 1. Flash the latest rc-proposed to a tablet 2. Open the camera app EXPECTED: I expect the app loading icon to be in the right orientation to the device ACTUAL: The icon is rotated 90° to the left To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1544010/+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 1530807] Re: Bluetooth cannot be activated on several devices
** Changed in: canonical-devices-system-image Milestone: ww08-2016 => ww04-2016 -- 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/1530807 Title: Bluetooth cannot be activated on several devices Status in The Avila project: Confirmed Status in Canonical System Image: Confirmed Status in Canonical Pocket Desktop: Confirmed Status in indicator-bluetooth package in Ubuntu: Confirmed Bug description: Using RC proposed 04/01/2016 bluetooth cannot be enabled. Tested on a nexus 7. Expected behavior: Bluetooth slider is moved to on Bluetooth activates Available devices appear in the list Experienced behavior: Bluetooth slider is moved to on Activity spinners appear Bluetooth slider moves to off. To manage notifications about this bug go to: https://bugs.launchpad.net/avila/+bug/1530807/+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 1517597] Re: [regression] mouse pointer support on emulator is broken
Mir report 0x0 is the actually something to be fixed in mir to get that bug resolved. ** Changed in: mir Status: Opinion => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1517597 Title: [regression] mouse pointer support on emulator is broken Status in Client Developer Experience: New Status in Canonical System Image: Confirmed Status in Mir: Confirmed Status in Mir 0.18 series: Opinion Status in android package in Ubuntu: Confirmed Status in mir package in Ubuntu: Invalid Bug description: STEPS: 1. Flash with sudo ubuntu-emulator create --channel ubuntu-touch/rc/ubuntu rc-test 2. Wait for it to build 3. Run with ubuntu-emulator run rc-test 4. Starts up but the mouse never moves meaning you can't leave the first page of the welcome wizard EXPECTED: I expect the emulator cursor to follow the mouse cursor and be able to click on things ACTUAL: Emulator cursors stay in the top left preventing movement. As noted below F6 toggles the input mode. The pointer movement is quite slow and jerky. You also can no longer initiate an edge swipe even in trackball mode. This is a major regression from how the emulator used to perform. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-developer-experience/+bug/1517597/+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 1544747] Re: Strange device names for USB NICs
Thanks for that explanation Pitti! THat makes sense now that I've read the thread. I wouldn't suggest making changes here for the sake of convenience, I also admit that I am a special corner case in this matter. Would it be a safe assumption that if I can decipher how to write a udev rule for network devices, I should be able to rename them myself? I think, knowing what you described above, that would be fine since this is intended behaviour. It just caught me off guard as this is the first time running anything but Trusty on this hardware and the only time I generally run an interim release is in VMs or Cloud instances which almost always only have one network device anyway. -- 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/1544747 Title: Strange device names for USB NICs Status in systemd package in Ubuntu: Incomplete Bug description: Fresh install of Xenial on an intel NUC with 1 onboard GigE and one USB GigE NIC. I was setting up networking for MAAS and discovered that the device names were ridiculous: bladernr@critical-maas:/etc/udev$ ifconfig |grep HWaddr eno1 Link encap:Ethernet HWaddr ec:a8:6b:fb:9f:66 enx8cae4cff4099 Link encap:Ethernet HWaddr 8c:ae:4c:ff:40:99 In the previous Trusty install on this NUC with the same USB dongle, they were named eth0 and em1. The predictable standard device names. Looking at udevadm: P: /devices/pci:00/:00:19.0/net/eno1 E: DEVPATH=/devices/pci:00/:00:19.0/net/eno1 E: ID_BUS=pci E: ID_MM_CANDIDATE=1 E: ID_MODEL_FROM_DATABASE=82579LM Gigabit Network Connection E: ID_MODEL_ID=0x1502 E: ID_NET_DRIVER=e1000e E: ID_NET_LABEL_ONBOARD=en L1U1 E: ID_NET_LINK_FILE=/lib/systemd/network/99-default.link E: ID_NET_NAME_MAC=enxeca86bfb9f66 E: ID_NET_NAME_ONBOARD=eno1 E: ID_NET_NAME_PATH=enp0s25 E: ID_OUI_FROM_DATABASE=ELITEGROUP COMPUTER SYSTEMS CO., LTD. E: ID_PATH=pci-:00:19.0 E: ID_PATH_TAG=pci-_00_19_0 E: ID_PCI_CLASS_FROM_DATABASE=Network controller E: ID_PCI_SUBCLASS_FROM_DATABASE=Ethernet controller E: ID_VENDOR_FROM_DATABASE=Intel Corporation E: ID_VENDOR_ID=0x8086 E: IFINDEX=2 E: INTERFACE=eno1 E: SUBSYSTEM=net E: SYSTEMD_ALIAS=/sys/subsystem/net/devices/eno1 E: TAGS=:systemd: E: USEC_INITIALIZED=5400250 P: /devices/pci:00/:00:1d.0/usb2/2-1/2-1.5/2-1.5:1.0/net/enx8cae4cff4099 E: DEVPATH=/devices/pci:00/:00:1d.0/usb2/2-1/2-1.5/2-1.5:1.0/net/enx8cae4cff4099 E: ID_BUS=usb E: ID_MM_CANDIDATE=1 E: ID_MODEL=AX88178 E: ID_MODEL_ENC=AX88178\x20 E: ID_MODEL_FROM_DATABASE=AX88178 E: ID_MODEL_ID=1780 E: ID_NET_DRIVER=asix E: ID_NET_LINK_FILE=/lib/systemd/network/90-mac-for-usb.link E: ID_NET_NAME=enx8cae4cff4099 E: ID_NET_NAME_MAC=enx8cae4cff4099 E: ID_NET_NAME_PATH=enp0s29u1u5 E: ID_OUI_FROM_DATABASE=Plugable Technologies E: ID_PATH=pci-:00:1d.0-usb-0:1.5:1.0 E: ID_PATH_TAG=pci-_00_1d_0-usb-0_1_5_1_0 E: ID_REVISION=0001 E: ID_SERIAL=ASIX_Elec._Corp._AX88178_02 E: ID_SERIAL_SHORT=02 E: ID_TYPE=generic E: ID_USB_CLASS_FROM_DATABASE=Vendor Specific Class E: ID_USB_DRIVER=asix E: ID_USB_INTERFACES=:00: E: ID_USB_INTERFACE_NUM=00 E: ID_USB_SUBCLASS_FROM_DATABASE=Vendor Specific Subclass E: ID_VENDOR=ASIX_Elec._Corp. E: ID_VENDOR_ENC=ASIX\x20Elec.\x20Corp. E: ID_VENDOR_FROM_DATABASE=ASIX Electronics Corp. E: ID_VENDOR_ID=0b95 E: IFINDEX=3 E: INTERFACE=enx8cae4cff4099 E: SUBSYSTEM=net E: SYSTEMD_ALIAS=/sys/subsystem/net/devices/enx8cae4cff4099 /sys/subsystem/net/devices/enx8cae4cff4099 E: TAGS=:systemd: E: USEC_INITIALIZED=8700146 And finally, looking in /etc/udev: bladernr@critical-maas:/etc/udev$ sudo ls -ra /etc/udev/* /etc/udev/udev.conf /etc/udev/rules.d: .. . /etc/udev/hwdb.d: .. . There are NO rules at all in udev for persistent names. Not even some samples and defaults. Looking at a completely different Xenial system with a single GigE NIC: bladernr@galactica:~$ ifconfig enp2s0Link encap:Ethernet HWaddr 40:8d:5c:51:5b:0d P: /devices/pci:00/:00:1b.2/:02:00.0/net/enp2s0 E: DEVPATH=/devices/pci:00/:00:1b.2/:02:00.0/net/enp2s0 E: ID_BUS=pci E: ID_MM_CANDIDATE=1 E: ID_MODEL_FROM_DATABASE=Killer E220x Gigabit Ethernet Controller E: ID_MODEL_ID=0xe091 E: ID_NET_DRIVER=alx E: ID_NET_LINK_FILE=/lib/systemd/network/99-default.link E: ID_NET_NAME_MAC=enx408d5c515b0d E: ID_NET_NAME_PATH=enp2s0 E: ID_OUI_FROM_DATABASE=GIGA-BYTE TECHNOLOGY CO.,LTD. E: ID_PATH=pci-:02:00.0 E: ID_PATH_TAG=pci-_02_00_0 E: ID_PCI_CLASS_FROM_DATABASE=Network controller E: ID_PCI_SUBCLASS_FROM_DATABASE=Ethernet controller E: ID_VENDOR_FROM_DATABASE=Qualcomm Atheros E: ID_VENDOR_ID=0x1969 E: IFINDEX=2 E: INTERFACE=enp2s0 E: SUBSYSTEM=net E: SYSTEMD_ALIAS=/sy
[Touch-packages] [Bug 1528955] Re: Camera app can be uninstalled permanently.
@Jacques MEULI (jacques-k) glad the solution worked for you too! But I have a small issue after reinstalling the camera-app using apt-get, I have two functioning camera apps in app menu now; one in the second row as usual, amongst the "featured" apps (along with phone, messaging, browser, clock etc.) and the other is listed alphabetically among all the other apps. The one in the "featured" apps is the updated one while the other is stuck on an older version (no shutter mute option, HDR can be enabled in video mode etc.). Long pressing this other camera icon takes me to a page with only an open button and two word info (see screenshot). Do you have the same issue? ** Attachment added: "screenshot20160212_205226044.png" https://bugs.launchpad.net/ubuntu/+source/camera-app/+bug/1528955/+attachment/4570117/+files/screenshot20160212_205226044.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to camera-app in Ubuntu. https://bugs.launchpad.net/bugs/1528955 Title: Camera app can be uninstalled permanently. Status in camera-app: New Status in camera-app package in Ubuntu: Confirmed Bug description: When I do long-tapping on the camera app icon, the app store is opened, showing the camera app's descrition. Then it is possible to click on "Uninstall" to unistall the camera app. After that the camera app is uninstalled and no photos can be taken, so far so good. But then it is not possible to reinstall the camera app, because the app can't be found in app store by searching for "camera". This happened on Nexus 4 in stable channel. This did NOT happen on Nexus 4 in rc-proposed channel. This happened on Aquaris E4.5. Further information here: To manage notifications about this bug go to: https://bugs.launchpad.net/camera-app/+bug/1528955/+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 1545021] Re: location settings refer to cellular data when no modem is present
** Branch linked: lp:~ken-vandine/ubuntu-system-settings/lp1545021 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to location-service in Ubuntu. https://bugs.launchpad.net/bugs/1545021 Title: location settings refer to cellular data when no modem is present Status in The Avila project: Confirmed Status in Canonical System Image: New Status in location-service package in Ubuntu: New Status in ubuntu-system-settings package in Ubuntu: New Bug description: In system settings & the welcome wizard, the phrase "Using GPS, anonymised wifi and cellular network info'" is used to describe the way HERE gathers data. On non-cellular devices with HERE 'and cellular network info' should be ommitted. To manage notifications about this bug go to: https://bugs.launchpad.net/avila/+bug/1545021/+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 1545021] Re: location settings refer to cellular data when no modem is present
** Also affects: location-service (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to location-service in Ubuntu. https://bugs.launchpad.net/bugs/1545021 Title: location settings refer to cellular data when no modem is present Status in The Avila project: Confirmed Status in Canonical System Image: New Status in location-service package in Ubuntu: New Status in ubuntu-system-settings package in Ubuntu: New Bug description: In system settings & the welcome wizard, the phrase "Using GPS, anonymised wifi and cellular network info'" is used to describe the way HERE gathers data. On non-cellular devices with HERE 'and cellular network info' should be ommitted. To manage notifications about this bug go to: https://bugs.launchpad.net/avila/+bug/1545021/+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 1545021] Re: location settings refer to cellular data when no modem is present
** Changed in: canonical-devices-system-image Milestone: None => ww04-2016 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to location-service in Ubuntu. https://bugs.launchpad.net/bugs/1545021 Title: location settings refer to cellular data when no modem is present Status in The Avila project: Confirmed Status in Canonical System Image: New Status in location-service package in Ubuntu: New Status in ubuntu-system-settings package in Ubuntu: New Bug description: In system settings & the welcome wizard, the phrase "Using GPS, anonymised wifi and cellular network info'" is used to describe the way HERE gathers data. On non-cellular devices with HERE 'and cellular network info' should be ommitted. To manage notifications about this bug go to: https://bugs.launchpad.net/avila/+bug/1545021/+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 1499879] Re: Moonphase could not be read
Ilonka: OK I understand. That was probably a previous translation that has already been replaced on launchpad. -- 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/1499879 Title: Moonphase could not be read Status in Day Scope: Confirmed Status in Today Scope: New Status in Ubuntu UX: New Status in unity8 package in Ubuntu: New Bug description: Hello guys! I want to read information for the moon phase in TodayScope. Problem is that the displayed text is to long, so I can see first word but not the rest. I think it is really a good think with this information, thank you for this :-) I use a BQ Aquaris E4.5 with Ubuntu 15.04 r25 dashboard 1.9.2 I sent a screenshot To manage notifications about this bug go to: https://bugs.launchpad.net/day-scope/+bug/1499879/+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 1528955] Re: Camera app can be uninstalled permanently.
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: camera-app (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to camera-app in Ubuntu. https://bugs.launchpad.net/bugs/1528955 Title: Camera app can be uninstalled permanently. Status in camera-app: New Status in camera-app package in Ubuntu: Confirmed Bug description: When I do long-tapping on the camera app icon, the app store is opened, showing the camera app's descrition. Then it is possible to click on "Uninstall" to unistall the camera app. After that the camera app is uninstalled and no photos can be taken, so far so good. But then it is not possible to reinstall the camera app, because the app can't be found in app store by searching for "camera". This happened on Nexus 4 in stable channel. This did NOT happen on Nexus 4 in rc-proposed channel. This happened on Aquaris E4.5. Further information here: To manage notifications about this bug go to: https://bugs.launchpad.net/camera-app/+bug/1528955/+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 1545005] Re: system settings displays 'cellular' control panel item when no modems are present
The real bug is probably in ofono, see the output of list-modems from a device without a modem and ofono running: http://pastebin.ubuntu.com/15024416/ So I think the real bug is that ofono reports a /ril_0 without any interfaces or features Connectivity API could work around this by assuming the modem isn't real if those values are NULL, but I think it's really an ofono bug. ** Also affects: ofono (Ubuntu) Importance: Undecided Status: New -- 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/1545005 Title: system settings displays 'cellular' control panel item when no modems are present Status in Canonical System Image: New Status in connectivity-api package in Ubuntu: New Status in indicator-network package in Ubuntu: New Status in ofono package in Ubuntu: New Bug description: In bug #1541588 several items were removed from system settings for tablets which have no cellular modem. In a related bug #1544712 ofono must still be present on such devices, in order for location to work. It seems that when it was tested, the landing for bug #1541588 happened when ofono was not running. I conclude therefore that the decision to display/not display cellular is keyed merely on the presence of ofono, rather than, say the count of modems ofono reports. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1545005/+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 1499879] Moonphase could not be read
Hi Kyle, I can't tell you the complete sentence because I only know first word of the sentence "einwachsend" And this word I can't find in german translations. I think next week should be this moonphase which it depends. If this word will appear again, we' ll know that the shown sentence isn't be part of the moonphase strings and then we'll see what to do 😃 Until next week Greetings Ilonka Am Mittwoch, 10. Februar 2016 00:20:41 CET schrieb Kyle Nitzsche : > Hi Ilonaka, > > I don't see any complete *sentences* in your screen shot from comment > #1. > > But, as mentioned, all the translations for the Day scope (this part of > the Today scope) are done here: https://translations.launchpad.net/day- > scope/trunk/+pots/day/de/ > > If you don't see it there, please type the string here and I will try > and direct you to it. > -- Mit Dekko von meinem Ubuntu-Gerät gesendet -- 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/1499879 Title: Moonphase could not be read Status in Day Scope: Confirmed Status in Today Scope: New Status in Ubuntu UX: New Status in unity8 package in Ubuntu: New Bug description: Hello guys! I want to read information for the moon phase in TodayScope. Problem is that the displayed text is to long, so I can see first word but not the rest. I think it is really a good think with this information, thank you for this :-) I use a BQ Aquaris E4.5 with Ubuntu 15.04 r25 dashboard 1.9.2 I sent a screenshot To manage notifications about this bug go to: https://bugs.launchpad.net/day-scope/+bug/1499879/+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
