[Touch-packages] [Bug 1771102] Re: 17.10->18.04 LTS hangs, CPU stalls in apt-pkg cache
Brian, I'm sorry but I had to upgrade to 18.04 LTS by reinstalling the whole system. No idea why apt-clone would hang like that but it seems to definitely be a bug. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-apt in Ubuntu. https://bugs.launchpad.net/bugs/1771102 Title: 17.10->18.04 LTS hangs, CPU stalls in apt-pkg cache Status in python-apt package in Ubuntu: New Status in ubuntu-release-upgrader package in Ubuntu: New Bug description: When I do as root: do-release-upgrade The bionic tarball is downloaded and the python based "bionic" process is forked. On the screen I see the first "Reading cache..." message and then the process spikes the CPU to 100% where it stays there forever (I waited 15-20 minutes and there was no change in CPU state). Here is the dist-upgrade log file: 2018-05-14 07:17:19,308 INFO uname information: 'Linux kitt 4.13.0-41-generic #46-Ubuntu SMP Wed May 2 13:38:30 UTC 2018 x86_64' 2018-05-14 07:17:19,594 INFO apt version: '1.5.1' 2018-05-14 07:17:19,594 INFO python version: '3.6.3 (default, Oct 3 2017, 21:45:48) [GCC 7.2.0]' 2018-05-14 07:17:19,596 INFO release-upgrader version '18.04.17' started 2018-05-14 07:17:19,600 INFO locale: 'en_US' 'UTF-8' 2018-05-14 07:17:19,605 INFO screen could not be run 2018-05-14 07:17:19,744 DEBUG Using 'DistUpgradeViewText' view 2018-05-14 07:17:19,788 DEBUG enable dpkg --force-overwrite 2018-05-14 07:17:19,817 DEBUG creating statefile: '/var/log/dist-upgrade/apt-clone_system_state.tar.gz' strace output of the "bionic" process: $ sudo strace -f -p 6469 strace: Process 6469 attached with 3 threads [pid 6546] restart_syscall(<... resuming interrupted poll ...> [pid 6547] restart_syscall(<... resuming interrupted poll ...>strace: [ Process PID=6469 runs in x32 mode. ] top output: PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND 6469 root 20 0 270048 33108 15728 R 99.7 0.1 0:38.85 bionic 6555 pisymbol 20 0 46736 4376 3344 R 0.7 0.0 0:00.04 top Looking at this further, it seems that the installer sets the the "rootdir=/" when it initiates the python-apt's Cache class. This hangs. I can reproduce this by simply changing it's test code to pass rootdir="/" and it hangs. It sorta smells like a deadlock issue though deep in the C++ module (apt_pkg) that backs the python one (GetLock?). But I'm not 100% sure. This behavior is seen on my 32-core Threadripper machine (AMD64). This is 17.10 latest with: $ dpkg -l python-apt libapt-pkg5.0 Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-==---= ii libapt-pkg5.0:amd641.5.1 amd64package management runtime library ii python-apt 1.4.0~beta3build2 amd64Python interface to libapt-pkg To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/1771102/+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 1771102] Re: 17.10->18.04 LTS hangs, CPU stalls in apt-pkg cache
Does anyone know of anything I can do to move forward? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-apt in Ubuntu. https://bugs.launchpad.net/bugs/1771102 Title: 17.10->18.04 LTS hangs, CPU stalls in apt-pkg cache Status in python-apt package in Ubuntu: New Bug description: When I do as root: do-release-upgrade The bionic tarball is downloaded and the python based "bionic" process is forked. On the screen I see the first "Reading cache..." message and then the process spikes the CPU to 100% where it stays there forever (I waited 15-20 minutes and there was no change in CPU state). Here is the dist-upgrade log file: 2018-05-14 07:17:19,308 INFO uname information: 'Linux kitt 4.13.0-41-generic #46-Ubuntu SMP Wed May 2 13:38:30 UTC 2018 x86_64' 2018-05-14 07:17:19,594 INFO apt version: '1.5.1' 2018-05-14 07:17:19,594 INFO python version: '3.6.3 (default, Oct 3 2017, 21:45:48) [GCC 7.2.0]' 2018-05-14 07:17:19,596 INFO release-upgrader version '18.04.17' started 2018-05-14 07:17:19,600 INFO locale: 'en_US' 'UTF-8' 2018-05-14 07:17:19,605 INFO screen could not be run 2018-05-14 07:17:19,744 DEBUG Using 'DistUpgradeViewText' view 2018-05-14 07:17:19,788 DEBUG enable dpkg --force-overwrite 2018-05-14 07:17:19,817 DEBUG creating statefile: '/var/log/dist-upgrade/apt-clone_system_state.tar.gz' strace output of the "bionic" process: $ sudo strace -f -p 6469 strace: Process 6469 attached with 3 threads [pid 6546] restart_syscall(<... resuming interrupted poll ...> [pid 6547] restart_syscall(<... resuming interrupted poll ...>strace: [ Process PID=6469 runs in x32 mode. ] top output: PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND 6469 root 20 0 270048 33108 15728 R 99.7 0.1 0:38.85 bionic 6555 pisymbol 20 0 46736 4376 3344 R 0.7 0.0 0:00.04 top Looking at this further, it seems that the installer sets the the "rootdir=/" when it initiates the python-apt's Cache class. This hangs. I can reproduce this by simply changing it's test code to pass rootdir="/" and it hangs. It sorta smells like a deadlock issue though deep in the C++ module (apt_pkg) that backs the python one (GetLock?). But I'm not 100% sure. This behavior is seen on my 32-core Threadripper machine (AMD64). This is 17.10 latest with: $ dpkg -l python-apt libapt-pkg5.0 Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-==---= ii libapt-pkg5.0:amd641.5.1 amd64package management runtime library ii python-apt 1.4.0~beta3build2 amd64Python interface to libapt-pkg To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/1771102/+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 1771102] [NEW] 17.10->18.04 LTS hangs, CPU stalls in apt-pkg cache
Public bug reported: When I do as root: do-release-upgrade The bionic tarball is downloaded and the python based "bionic" process is forked. On the screen I see the first "Reading cache..." message and then the process spikes the CPU to 100% where it stays there forever (I waited 15-20 minutes and there was no change in CPU state). Here is the dist-upgrade log file: 2018-05-14 07:17:19,308 INFO uname information: 'Linux kitt 4.13.0-41-generic #46-Ubuntu SMP Wed May 2 13:38:30 UTC 2018 x86_64' 2018-05-14 07:17:19,594 INFO apt version: '1.5.1' 2018-05-14 07:17:19,594 INFO python version: '3.6.3 (default, Oct 3 2017, 21:45:48) [GCC 7.2.0]' 2018-05-14 07:17:19,596 INFO release-upgrader version '18.04.17' started 2018-05-14 07:17:19,600 INFO locale: 'en_US' 'UTF-8' 2018-05-14 07:17:19,605 INFO screen could not be run 2018-05-14 07:17:19,744 DEBUG Using 'DistUpgradeViewText' view 2018-05-14 07:17:19,788 DEBUG enable dpkg --force-overwrite 2018-05-14 07:17:19,817 DEBUG creating statefile: '/var/log/dist-upgrade/apt-clone_system_state.tar.gz' strace output of the "bionic" process: $ sudo strace -f -p 6469 strace: Process 6469 attached with 3 threads [pid 6546] restart_syscall(<... resuming interrupted poll ...> [pid 6547] restart_syscall(<... resuming interrupted poll ...>strace: [ Process PID=6469 runs in x32 mode. ] top output: PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND 6469 root 20 0 270048 33108 15728 R 99.7 0.1 0:38.85 bionic 6555 pisymbol 20 0 46736 4376 3344 R 0.7 0.0 0:00.04 top Looking at this further, it seems that the installer sets the the "rootdir=/" when it initiates the python-apt's Cache class. This hangs. I can reproduce this by simply changing it's test code to pass rootdir="/" and it hangs. It sorta smells like a deadlock issue though deep in the C++ module (apt_pkg) that backs the python one (GetLock?). But I'm not 100% sure. This behavior is seen on my 32-core Threadripper machine (AMD64). This is 17.10 latest with: $ dpkg -l python-apt libapt-pkg5.0 Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-==---= ii libapt-pkg5.0:amd641.5.1 amd64package management runtime library ii python-apt 1.4.0~beta3build2 amd64Python interface to libapt-pkg ** Affects: python-apt (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-apt in Ubuntu. https://bugs.launchpad.net/bugs/1771102 Title: 17.10->18.04 LTS hangs, CPU stalls in apt-pkg cache Status in python-apt package in Ubuntu: New Bug description: When I do as root: do-release-upgrade The bionic tarball is downloaded and the python based "bionic" process is forked. On the screen I see the first "Reading cache..." message and then the process spikes the CPU to 100% where it stays there forever (I waited 15-20 minutes and there was no change in CPU state). Here is the dist-upgrade log file: 2018-05-14 07:17:19,308 INFO uname information: 'Linux kitt 4.13.0-41-generic #46-Ubuntu SMP Wed May 2 13:38:30 UTC 2018 x86_64' 2018-05-14 07:17:19,594 INFO apt version: '1.5.1' 2018-05-14 07:17:19,594 INFO python version: '3.6.3 (default, Oct 3 2017, 21:45:48) [GCC 7.2.0]' 2018-05-14 07:17:19,596 INFO release-upgrader version '18.04.17' started 2018-05-14 07:17:19,600 INFO locale: 'en_US' 'UTF-8' 2018-05-14 07:17:19,605 INFO screen could not be run 2018-05-14 07:17:19,744 DEBUG Using 'DistUpgradeViewText' view 2018-05-14 07:17:19,788 DEBUG enable dpkg --force-overwrite 2018-05-14 07:17:19,817 DEBUG creating statefile: '/var/log/dist-upgrade/apt-clone_system_state.tar.gz' strace output of the "bionic" process: $ sudo strace -f -p 6469 strace: Process 6469 attached with 3 threads [pid 6546] restart_syscall(<... resuming interrupted poll ...> [pid 6547] restart_syscall(<... resuming interrupted poll ...>strace: [ Process PID=6469 runs in x32 mode. ] top output: PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND 6469 root 20 0 270048 33108 15728 R 99.7 0.1 0:38.85 bionic 6555 pisymbol 20 0 46736 4376 3344 R 0.7 0.0 0:00.04 top Looking at this further, it seems that the installer sets the the "rootdir=/" when it initiates the
[Touch-packages] [Bug 1560899] Re: sqlite triggers syscall error if run as root in snappy default confinement (fchown not allowed)
subscribing ubuntu release. would like to see this considered for final
release still as sqlite is an often used components in snaps and with
this patch you can pull in the binary from the archive through the
convenient snapcraft stage-packages ...
patch should be safe as it basically just avoids a null op that in case
of snappy then gets the process killed for no reason (e.g. chown from 0
to 0 -> seccomp kicks in).
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to sqlite3 in Ubuntu.
https://bugs.launchpad.net/bugs/1560899
Title:
sqlite triggers syscall error if run as root in snappy default
confinement (fchown not allowed)
Status in sqlite3 package in Ubuntu:
New
Bug description:
Code currently tries to change user to uid if geteuid is root; this
call triggers fchown syscall exception in snappy.
Good news is that in snappy this call is a null op in theory as both
geteuid as well as uid are 0, so changing wouldnt do anything.
Fix is to not try to chown if geteuid is equal to uid (e.g. if it
would be a null op anyway). "Safe" patch should be:
Index: sqlite3-3.11.0/src/os_unix.c
===
--- sqlite3-3.11.0.orig/src/os_unix.c
+++ sqlite3-3.11.0/src/os_unix.c
@@ -497,7 +497,7 @@ static struct unix_syscall {
*/
static int robustFchown(int fd, uid_t uid, gid_t gid){
#if defined(HAVE_FCHOWN)
- return osGeteuid() ? 0 : osFchown(fd,uid,gid);
+ return osGeteuid() || osGeteuid() == uid ? 0 : osFchown(fd,uid,gid);
#else
return 0;
#endif
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sqlite3/+bug/1560899/+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 1560899] Re: sqlite triggers syscall error if run as root in snappy default confinement (fchown not allowed)
** Patch added: "quilt dropin patch against latest xenial"
https://bugs.launchpad.net/ubuntu/+source/sqlite3/+bug/1560899/+attachment/4608367/+files/10-avoid-null-op-fchown-when-when-root.patch
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to sqlite3 in Ubuntu.
https://bugs.launchpad.net/bugs/1560899
Title:
sqlite triggers syscall error if run as root in snappy default
confinement (fchown not allowed)
Status in sqlite3 package in Ubuntu:
New
Bug description:
Code currently tries to change user to uid if geteuid is root; this
call triggers fchown syscall exception in snappy.
Good news is that in snappy this call is a null op in theory as both
geteuid as well as uid are 0, so changing wouldnt do anything.
Fix is to not try to chown if geteuid is equal to uid (e.g. if it
would be a null op anyway). "Safe" patch should be:
Index: sqlite3-3.11.0/src/os_unix.c
===
--- sqlite3-3.11.0.orig/src/os_unix.c
+++ sqlite3-3.11.0/src/os_unix.c
@@ -497,7 +497,7 @@ static struct unix_syscall {
*/
static int robustFchown(int fd, uid_t uid, gid_t gid){
#if defined(HAVE_FCHOWN)
- return osGeteuid() ? 0 : osFchown(fd,uid,gid);
+ return osGeteuid() || osGeteuid() == uid ? 0 : osFchown(fd,uid,gid);
#else
return 0;
#endif
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sqlite3/+bug/1560899/+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 1560899] [NEW] sqlite triggers syscall error if run as root in snappy default confinement (fchown not allowed)
Public bug reported:
Code currently tries to change user to uid if geteuid is root; this call
triggers fchown syscall exception in snappy.
Good news is that in snappy this call is a null op in theory as both
geteuid as well as uid are 0, so changing wouldnt do anything.
Fix is to not try to chown if geteuid is equal to uid (e.g. if it would
be a null op anyway). "Safe" patch should be:
Index: sqlite3-3.11.0/src/os_unix.c
===
--- sqlite3-3.11.0.orig/src/os_unix.c
+++ sqlite3-3.11.0/src/os_unix.c
@@ -497,7 +497,7 @@ static struct unix_syscall {
*/
static int robustFchown(int fd, uid_t uid, gid_t gid){
#if defined(HAVE_FCHOWN)
- return osGeteuid() ? 0 : osFchown(fd,uid,gid);
+ return osGeteuid() || osGeteuid() == uid ? 0 : osFchown(fd,uid,gid);
#else
return 0;
#endif
** Affects: sqlite3 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to sqlite3 in Ubuntu.
https://bugs.launchpad.net/bugs/1560899
Title:
sqlite triggers syscall error if run as root in snappy default
confinement (fchown not allowed)
Status in sqlite3 package in Ubuntu:
New
Bug description:
Code currently tries to change user to uid if geteuid is root; this
call triggers fchown syscall exception in snappy.
Good news is that in snappy this call is a null op in theory as both
geteuid as well as uid are 0, so changing wouldnt do anything.
Fix is to not try to chown if geteuid is equal to uid (e.g. if it
would be a null op anyway). "Safe" patch should be:
Index: sqlite3-3.11.0/src/os_unix.c
===
--- sqlite3-3.11.0.orig/src/os_unix.c
+++ sqlite3-3.11.0/src/os_unix.c
@@ -497,7 +497,7 @@ static struct unix_syscall {
*/
static int robustFchown(int fd, uid_t uid, gid_t gid){
#if defined(HAVE_FCHOWN)
- return osGeteuid() ? 0 : osFchown(fd,uid,gid);
+ return osGeteuid() || osGeteuid() == uid ? 0 : osFchown(fd,uid,gid);
#else
return 0;
#endif
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sqlite3/+bug/1560899/+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 1495688] Re: system-image-cli tool fails on dangling symlink
** Changed in: snappy
Status: Fix Committed => Fix Released
--
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/1495688
Title:
system-image-cli tool fails on dangling symlink
Status in Snappy:
Fix Released
Status in Ubuntu system image:
Triaged
Status in livecd-rootfs package in Ubuntu:
Fix Committed
Status in system-image package in Ubuntu:
New
Bug description:
(amd64)ubuntu@localhost:~$ system-image-cli -i
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/systemimage/helpers.py", line 253, in
last_update_date
timestamp = datetime.fromtimestamp(os.stat(LAST_UPDATE_FILE).st_mtime)
FileNotFoundError: [Errno 2] No such file or directory:
'/userdata/.last_update'
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/bin/system-image-cli", line 9, in
load_entry_point('system-image==3.0.1', 'console_scripts',
'system-image-cli')()
File "/usr/lib/python3/dist-packages/systemimage/main.py", line 289, in main
last_update=last_update_date(),
File "/usr/lib/python3/dist-packages/systemimage/helpers.py", line 258, in
last_update_date
for path in config.ini_files)
File "/usr/lib/python3/dist-packages/systemimage/helpers.py", line 258, in
for path in config.ini_files)
File "/usr/lib/python3.4/pathlib.py", line 1048, in stat
return self._accessor.stat(self)
File "/usr/lib/python3.4/pathlib.py", line 326, in wrapped
return strfunc(str(pathobj), *args)
FileNotFoundError: [Errno 2] No such file or directory:
'/etc/system-image/config.d/00_default.ini'
To manage notifications about this bug go to:
https://bugs.launchpad.net/snappy/+bug/1495688/+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 1387231] Re: [clock] alarm still rings once it's been deleted
I cannot reproduce this after deleting; however, i saw this all time when disabling the alarm in clock app for last week. Not sure if its related or a different bug. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-datetime in Ubuntu. https://bugs.launchpad.net/bugs/1387231 Title: [clock] alarm still rings once it's been deleted Status in Clock application for Ubuntu devices: Incomplete Status in “indicator-datetime” package in Ubuntu: New Bug description: (r135) Steps to reproduce: 1. Create a single type alarm to ring in the next 5 minutes. 2. Wait for the alarm to ring. 3. After dismissing the alarm, delete it from the clock app. Actual behaviour: Once the alarm's been deleted, it still rings! Expected behaviour: Once you delete the alarm, this shouldn't ring anymore. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-clock-app/+bug/1387231/+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 1382039] Re: [TOPBLOCKER] Apps scope empty on boot
Hello, Hello, seems this is stuck'ish again? Who needs doing what here to get us to a good app scope back asap? Thanks! - Alexander -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-scope-click in Ubuntu. https://bugs.launchpad.net/bugs/1382039 Title: [TOPBLOCKER] Apps scope empty on boot Status in “qtmir” package in Ubuntu: Triaged Status in “unity-scope-click” package in Ubuntu: Invalid Status in “unity-scopes-api” package in Ubuntu: Invalid Status in “unity-scopes-shell” package in Ubuntu: Invalid Status in “unity8” package in Ubuntu: Invalid Bug description: Several people reported today that the apps scope came up empty on boot. A pull-to-refresh makes results come in again. Note: it seems the problem is more likely to happen if you wait for at least 1 minute after reboot, and then unlock your device. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtmir/+bug/1382039/+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 1348557] Re: Make scrolling speed resolution independent
general comment: please try to submit bugs for product team landing request with many incomplete tasks etc. in future. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1348557 Title: Make scrolling speed resolution independent Status in QT Ubuntu: Invalid Status in Ubuntu UI Toolkit: Confirmed Status in “qtbase-opensource-src” package in Ubuntu: Incomplete Status in “qtdeclarative-opensource-src” package in Ubuntu: Incomplete Status in “unity8” package in Ubuntu: Fix Released Bug description: Following https://bugreports.qt-project.org/browse/QTBUG-35608 the default speed of scrollable components (components inheriting from flickable basically) is not resolution independent. The result is that scrolling speed on our high dpi touch screens is slow. We could workaround this in the SDK until the bug is fixed upstream (I bet it won't happen in time for our releases), by simply adding components named as Flickable, Listview, Gridview etc etc in the Ubuntu.Components, where each of them sets the speed to be resolution independent following our GU guidelines To manage notifications about this bug go to: https://bugs.launchpad.net/qtubuntu/+bug/1348557/+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 1358343] Re: TOPBLOCKER too easy to answer a call by accident
** Summary changed: - [notifications] too easy to answer a call by accident + TOPBLOCKER too easy to answer a call by accident ** Summary changed: - TOPBLOCKER too easy to answer a call by accident + [TOPBLOCKER] too easy to answer a call by accident -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-notifications in Ubuntu. https://bugs.launchpad.net/bugs/1358343 Title: [TOPBLOCKER] too easy to answer a call by accident Status in Telephony Service: Confirmed Status in Ubuntu UX bugs: Fix Committed Status in “dialer-app” package in Ubuntu: Confirmed Status in “telephony-service” package in Ubuntu: New Status in “unity-notifications” package in Ubuntu: In Progress Status in “unity8” package in Ubuntu: In Progress Bug description: If you put the phone in your pocket with locked screen and you receive a call is too easy to answer or reject that by mistake. Or pressing the screen while trying to get the phone or the call can be answered without you noticed by your pocket. To manage notifications about this bug go to: https://bugs.launchpad.net/telephony-service/+bug/1358343/+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 1378043] Re: [TOPBLOCKER] Phone is getting locked during a call
** Summary changed: - Phone is getting locked during a call + [TOPBLOCKER] Phone is getting locked during a call -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to powerd in Ubuntu. https://bugs.launchpad.net/bugs/1378043 Title: [TOPBLOCKER] Phone is getting locked during a call Status in Dialer app for Ubuntu Touch: Invalid Status in “powerd” package in Ubuntu: In Progress Bug description: The phone is getting lock during a call. How to reproduce 1 - Open dialer app 2 - Type a number 3 - Click to call 4 - Cover the proximity sensor 5 - Uncover the proximity sensor Expected The phone shows the active call information Current results === The phone get locked and you need to type your password to unlock it OBS: If you wait the call complete for about 3~ secs everything works nice. To manage notifications about this bug go to: https://bugs.launchpad.net/dialer-app/+bug/1378043/+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 1382039] Re: [TOPBLOCKER] Apps scope empty on boot
** Summary changed: - Apps scope empty on boot + [TOPBLOCKER] Apps scope empty on boot -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-scope-click in Ubuntu. https://bugs.launchpad.net/bugs/1382039 Title: [TOPBLOCKER] Apps scope empty on boot Status in “unity-scope-click” package in Ubuntu: New Status in “unity-scopes-api” package in Ubuntu: New Status in “unity-scopes-shell” package in Ubuntu: Confirmed Status in “unity8” package in Ubuntu: Triaged Bug description: Several people reported today that the apps scope came up empty on boot. A pull-to-refresh makes results come in again. Note: it seems the problem is more likely to happen if you wait for at least 1 minute after reboot, and then unlock your device. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-scope-click/+bug/1382039/+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 1374419] Re: [TOPBLOCKER] Threading issue with the MenuModel Updates
** Summary changed: - Threading issue with the MenuModel Updates + [TOPBLOCKER] Threading issue with the MenuModel Updates -- 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/1374419 Title: [TOPBLOCKER] Threading issue with the MenuModel Updates Status in “indicator-network” package in Ubuntu: In Progress Status in “ubuntu-system-settings” package in Ubuntu: Invalid Bug description: This and other corruptions in the i-network menus is caused by a race condition in the i-network-service GMainLoop synchronization. === Some access points in indicator-network show twice, when they should be merged into a single entry given that security and SSID are the same. See attached screenshot. For example, Instant Staff should only show once, not greyed out. There are not multiple APs with different security settings to justify two different entries. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1374419/+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 1382595] Re: [TOPBLOCKER] /usr/lib/arm-linux-gnueabihf/indicator-network/indicator-network-service:indicator-network-service: pthread_mutex_lock.c:80: __pthread_mutex_lock: Asser
** Summary changed: - /usr/lib/arm-linux-gnueabihf/indicator-network/indicator-network-service:indicator-network-service: pthread_mutex_lock.c:80: __pthread_mutex_lock: Assertion `mutex-__data.__owner == 0' failed. + [TOPBLOCKER] /usr/lib/arm-linux-gnueabihf/indicator-network/indicator-network-service:indicator-network-service: pthread_mutex_lock.c:80: __pthread_mutex_lock: Assertion `mutex-__data.__owner == 0' failed. -- 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/1382595 Title: [TOPBLOCKER] /usr/lib/arm-linux-gnueabihf/indicator-network/indicator- network-service:indicator-network-service: pthread_mutex_lock.c:80: __pthread_mutex_lock: Assertion `mutex-__data.__owner == 0' failed. Status in “indicator-network” package in Ubuntu: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding indicator-network. This problem was most recently seen with version 0.5.1+14.10.20141015-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/ecc14b5d54f3e0a0f1720cad0c623f81c8a16988 contains more details. steps to reproduce: (need to trigger race condition) 1. pull down network indicator 2. toggle flight mode on and off quickly a few times 3. click sim card 1 and 2 4. toggle flight mode 5. swipe up close indicators 6. repeat steps 1-5 until crash occurs expected results: no crash happens actual results: Bluetooth indicator blinks (appear and disappear) in indicator bar at top of screen, and network indicator crashes. additional info: eventually the bluetooth indicator appears stable in the indicators at the top of the screen. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1382595/+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 1383724] Re: In the welcome wizard enable location but not here services and in here maps app you get no location
we have other bugs track that normal GPS doesn't work. once those are fixed this won't be that critical. -- 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/1383724 Title: In the welcome wizard enable location but not here services and in here maps app you get no location Status in “location-service” package in Ubuntu: New Bug description: STEPS: 1. Flash a fresh image 2. Complete the welcome wizard enable location but leave the here tos unchecked 3. Complete the edges demo 4. Open here webapp EXPECTED: I expect to get a location of some sort as location is enabled ACTUAL: No location is given at all. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/location-service/+bug/1383724/+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 1383357] Re: enabling flight mode shows airplane + 2g icon
tvoss asked to have this also tracked on network-manager... ** Also affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags added: ota-1 -- 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/1383357 Title: enabling flight mode shows airplane + 2g icon Status in “indicator-network” package in Ubuntu: Confirmed Status in “network-manager” package in Ubuntu: New Bug description: I see this when I toggle the indicator in the indicator-network.logs void core::dbus::PropertyT::handle_changed(const core::dbus::types::Variant) [with PropertyType = org::freedesktop::URfkill::Interface::Killswitch::Property::State]: org.freedesktop.DBus.Error.UnknownMethod: Method Get with signature ss on interface org.freedesktop.DBus.Properties doesn't exist There is nothing crashing according to /var/crash Modem seems to be offline: phablet@ubuntu-phablet:~$ /usr/share/ofono/scripts/list-modems [ /ril_1 ] Features = Manufacturer = Fake Manufacturer Lockdown = 0 Powered = 1 Online = 0 Interfaces = org.ofono.CallVolume org.ofono.VoiceCallManager org.ofono.NetworkTime Serial = 354142060406982 Type = hardware Emergency = 0 Revision = MOLY.WR8.W1315.MD.WG.MP.V37.P5, 2014/05/15 11:49 Model = Fake Modem Model [ org.ofono.CallVolume ] SpeakerVolume = 0 Muted = 0 MicrophoneVolume = 0 [ org.ofono.VoiceCallManager ] EmergencyNumbers = 08 000 999 110 112 911 118 119 [ org.ofono.NetworkTime ] [ /ril_0 ] Features = Manufacturer = Fake Manufacturer Lockdown = 0 Powered = 1 Online = 0 Interfaces = org.ofono.CallVolume org.ofono.VoiceCallManager org.ofono.NetworkTime Serial = 354142060126986 Type = hardware Emergency = 0 Revision = MOLY.WR8.W1315.MD.WG.MP.V37.P5, 2014/05/15 11:49 Model = Fake Modem Model [ org.ofono.CallVolume ] SpeakerVolume = 0 Muted = 0 MicrophoneVolume = 0 [ org.ofono.VoiceCallManager ] EmergencyNumbers = 112 911 [ org.ofono.NetworkTime ] phablet@ubuntu-phablet:~$ /usr/share/urfkill/scripts/flight-mode flight-mode is: 1 phablet@ubuntu-phablet:~$ /usr/share/urfkill/scripts/enumerate /org/freedesktop/URfkill/devices/0 Printing props for unspecialized device: /org/freedesktop/URfkill/devices/0 Printing props for Kernel device: /org/freedesktop/URfkill/devices/0 type: 2 hard: 0 index: 0 urftype: org.freedesktop.URfkill.Device.Kernel name: hci0 platform: 0 soft: 1 /org/freedesktop/URfkill/devices/200 Printing props for unspecialized device: /org/freedesktop/URfkill/devices/200 Printing props for Hybris device: /org/freedesktop/URfkill/devices/200 type: 1 index: 200 urftype: org.freedesktop.URfkill.Device.Hybris name: hybris_wifi platform: 0 soft: 1 /org/freedesktop/URfkill/devices/100 Printing props for unspecialized device: /org/freedesktop/URfkill/devices/100 Printing props for Ofono device: /org/freedesktop/URfkill/devices/100 type: 5 index: 100 urftype: org.freedesktop.URfkill.Device.Ofono name: Fake Manufacturer Fake Modem Model platform: 0 soft: 1 /org/freedesktop/URfkill/devices/101 Printing props for unspecialized device: /org/freedesktop/URfkill/devices/101 Printing props for Ofono device: /org/freedesktop/URfkill/devices/101 type: 5 index: 101 urftype: org.freedesktop.URfkill.Device.Ofono name: Fake Manufacturer Fake Modem Model platform: 0 soft: 1 phablet@ubuntu-phablet:~$ system-image-cli -i current build number: 117 device name: krillin channel: ubuntu-touch/ubuntu-rtm/14.09-proposed last update: 2014-10-19 08:18:48 version version: 117 version ubuntu: 20141019 version device: 20141015-32e0f27 version custom: 1413412663 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1383357/+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 1383357] Re: enabling flight mode shows airplane + 2g icon
used ota-1 tag assuming that its just UI problem. If thats not case, please drop that tag again. -- 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/1383357 Title: enabling flight mode shows airplane + 2g icon Status in “indicator-network” package in Ubuntu: Confirmed Status in “network-manager” package in Ubuntu: New Bug description: I see this when I toggle the indicator in the indicator-network.logs void core::dbus::PropertyT::handle_changed(const core::dbus::types::Variant) [with PropertyType = org::freedesktop::URfkill::Interface::Killswitch::Property::State]: org.freedesktop.DBus.Error.UnknownMethod: Method Get with signature ss on interface org.freedesktop.DBus.Properties doesn't exist There is nothing crashing according to /var/crash Modem seems to be offline: phablet@ubuntu-phablet:~$ /usr/share/ofono/scripts/list-modems [ /ril_1 ] Features = Manufacturer = Fake Manufacturer Lockdown = 0 Powered = 1 Online = 0 Interfaces = org.ofono.CallVolume org.ofono.VoiceCallManager org.ofono.NetworkTime Serial = 354142060406982 Type = hardware Emergency = 0 Revision = MOLY.WR8.W1315.MD.WG.MP.V37.P5, 2014/05/15 11:49 Model = Fake Modem Model [ org.ofono.CallVolume ] SpeakerVolume = 0 Muted = 0 MicrophoneVolume = 0 [ org.ofono.VoiceCallManager ] EmergencyNumbers = 08 000 999 110 112 911 118 119 [ org.ofono.NetworkTime ] [ /ril_0 ] Features = Manufacturer = Fake Manufacturer Lockdown = 0 Powered = 1 Online = 0 Interfaces = org.ofono.CallVolume org.ofono.VoiceCallManager org.ofono.NetworkTime Serial = 354142060126986 Type = hardware Emergency = 0 Revision = MOLY.WR8.W1315.MD.WG.MP.V37.P5, 2014/05/15 11:49 Model = Fake Modem Model [ org.ofono.CallVolume ] SpeakerVolume = 0 Muted = 0 MicrophoneVolume = 0 [ org.ofono.VoiceCallManager ] EmergencyNumbers = 112 911 [ org.ofono.NetworkTime ] phablet@ubuntu-phablet:~$ /usr/share/urfkill/scripts/flight-mode flight-mode is: 1 phablet@ubuntu-phablet:~$ /usr/share/urfkill/scripts/enumerate /org/freedesktop/URfkill/devices/0 Printing props for unspecialized device: /org/freedesktop/URfkill/devices/0 Printing props for Kernel device: /org/freedesktop/URfkill/devices/0 type: 2 hard: 0 index: 0 urftype: org.freedesktop.URfkill.Device.Kernel name: hci0 platform: 0 soft: 1 /org/freedesktop/URfkill/devices/200 Printing props for unspecialized device: /org/freedesktop/URfkill/devices/200 Printing props for Hybris device: /org/freedesktop/URfkill/devices/200 type: 1 index: 200 urftype: org.freedesktop.URfkill.Device.Hybris name: hybris_wifi platform: 0 soft: 1 /org/freedesktop/URfkill/devices/100 Printing props for unspecialized device: /org/freedesktop/URfkill/devices/100 Printing props for Ofono device: /org/freedesktop/URfkill/devices/100 type: 5 index: 100 urftype: org.freedesktop.URfkill.Device.Ofono name: Fake Manufacturer Fake Modem Model platform: 0 soft: 1 /org/freedesktop/URfkill/devices/101 Printing props for unspecialized device: /org/freedesktop/URfkill/devices/101 Printing props for Ofono device: /org/freedesktop/URfkill/devices/101 type: 5 index: 101 urftype: org.freedesktop.URfkill.Device.Ofono name: Fake Manufacturer Fake Modem Model platform: 0 soft: 1 phablet@ubuntu-phablet:~$ system-image-cli -i current build number: 117 device name: krillin channel: ubuntu-touch/ubuntu-rtm/14.09-proposed last update: 2014-10-19 08:18:48 version version: 117 version ubuntu: 20141019 version device: 20141015-32e0f27 version custom: 1413412663 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1383357/+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 1381658] Re: Top Crasher: /usr/share/apport/recoverable_problem:AttributeError:add_proc_info:main:add_proc_info:/usr/share/apport/recoverable_problem@75:main
I assume this has impact on our ability to retrieve crash reports on RTM? If so, I am sure this is critical for product. Can someone confirm that this is the case? -- 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/1381658 Title: Top Crasher: /usr/share/apport/recoverable_problem:AttributeError:add_proc_info:main:add_proc_info:/usr/share/apport/recoverable_problem@75:main Status in “apport” package in Ubuntu: Fix Released Status in “apport” package in Ubuntu RTM: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding apport. This problem was most recently seen with version 2.14.7-0ubuntu5, the problem page at https://errors.ubuntu.com/problem/d7b8b576c9b773cd5d822e833534e98fba85e30d contains more details. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1381658/+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 1380120] Re: Manage Scopes - All Is Unusable
I still see the issue; will not clean the cache in case you need someone to validate that it auto recovers after landing the fix. Let me know (ping on IRC) if I shall test something. -- 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/1380120 Title: Manage Scopes - All Is Unusable Status in “unity8” package in Ubuntu: Invalid Status in “qtdeclarative-opensource-src” package in Ubuntu RTM: Confirmed Bug description: This only happens when upgraded with deltas: $ ubuntu-device-flash --channel=ubuntu-touch/ubuntu-rtm/14.09-proposed --revision=96 and OTA to r100 Steps: 1. Got to manage scopes 2. Click all Observed: The UI is unusable as in attached picture To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1380120/+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 1380120] Re: Manage Scopes - Is Unusable
i see the same issue. ** Changed in: unity8 (Ubuntu) Status: New = Confirmed ** Changed in: unity8 (Ubuntu) Importance: Undecided = Critical ** Tags added: rtm14 ** Description changed: - This is in krillin r99. + This is in krillin r99 rtm-proposed Steps: 1. Got to manage scopes 2. Click all Observed: The UI is unusable as in attached picture -- 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/1380120 Title: Manage Scopes - All Is Unusable Status in “unity8” package in Ubuntu: Confirmed Bug description: This is in krillin r99 rtm-proposed Steps: 1. Got to manage scopes 2. Click all Observed: The UI is unusable as in attached picture To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1380120/+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 1379296] Re: unity8-dash should be excluded from app lifecycle management
** Tags added: rtm14 -- 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/1379296 Title: unity8-dash should be excluded from app lifecycle management Status in “qtmir” package in Ubuntu: In Progress Status in “unity8” package in Ubuntu: Opinion Bug description: STEPS: 1. Install the BBC NEWS app from the store 2. Go back to the apps scope 3. Open the bbc app browse about a bit 4. Click on a video link 5. let it play for a while 6. Cycle back to the scopes Scopes then restarts having a lot of apps open my unity8-dash gets contantly killed along the apps if a certain OOM threshold is reached ... this appears like a system crash of the UI (even though it is desired killing) from a user perspective ... checking the oom_score_adj values of all running apps i see that the dash has the same high value as all other open foreground apps: ... 117960oxide-renderer 117963oxide-renderer 117988oxide-renderer 300 6170oxide-renderer 802 12514 unity8-dash 802 6088webbrowser-app 802 6873webapp-containe 802 7425webapp-containe 802 7910webapp-containe (the full log can be found at http://paste.ubuntu.com/8526308/ ) given that the dash is one part of our core UI it should be excluded from app lifecycle management (keeping the same oom_score of 10 as unity8 does) so that only actual apps get killed on high memory pressure. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtmir/+bug/1379296/+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 1375896] Re: location not working reliably in browser or webapps
** Tags added: rtm14 -- 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/1375896 Title: location not working reliably in browser or webapps Status in Web Browser App: Invalid Status in “location-service” package in Ubuntu: New Bug description: krillin build 72 - I have not wiped my phone in quite a while but instead have been doing OTA updates - I manually re-ran the setup wizard to ensure the HERE location stuff was enabled, which it is - reboot the phone I launch Google Maps webapp and it tells me Your location could not be determined. I try this repeatedly over the course of many minutes with the same results. I do the same with HERE maps webapp and I get the same message. I run OSMtouch app and it is able to locate me. I do get a popup saying No GPS available. Position is approximate but the location on the map is roughly accurate. To manage notifications about this bug go to: https://bugs.launchpad.net/webbrowser-app/+bug/1375896/+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 1379025] Re: phone didnt see updates from r89 to r91 until r93 became available
** Attachment added: ubuntu-download-manager.ERROR https://bugs.launchpad.net/ubuntu/+source/ubuntu-download-manager/+bug/1379025/+attachment/4228922/+files/ubuntu-download-manager.ERROR -- 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/1379025 Title: phone didnt see updates from r89 to r91 until r93 became available Status in “ubuntu-download-manager” package in Ubuntu: New Bug description: situation as best as i can capture: 1. updated in morning to r89 2. had internet outage for half a day 3. afterwards r91 was published 4. system settings didnt offer to upgrade system 5. while debugging r93 became available and system settings started downloading etc. checking with barry and sergio it seems udm had some kind of troubles getting back to system image when asked to check for updates. what makes no sense is that it recovered when new image r93 was there; so imo this feels there must be a component hand over somewhere that doesnt retry if its step fails half way through; but guess there are more ways to cause this behaviour. Would be great to at least have a sensible story so we can understand if our user base will be at risk not getting important updates. system image client.log: http://paste.ubuntu.com/8522507/ will attach ubuntu-download-manager logs as tarball too... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-download-manager/+bug/1379025/+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 1379025] Re: phone didnt see updates from r89 to r91 until r93 became available
** Attachment added: ubuntu-download-manager.WARNING https://bugs.launchpad.net/ubuntu/+source/ubuntu-download-manager/+bug/1379025/+attachment/4228924/+files/ubuntu-download-manager.WARNING -- 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/1379025 Title: phone didnt see updates from r89 to r91 until r93 became available Status in “ubuntu-download-manager” package in Ubuntu: New Bug description: situation as best as i can capture: 1. updated in morning to r89 2. had internet outage for half a day 3. afterwards r91 was published 4. system settings didnt offer to upgrade system 5. while debugging r93 became available and system settings started downloading etc. checking with barry and sergio it seems udm had some kind of troubles getting back to system image when asked to check for updates. what makes no sense is that it recovered when new image r93 was there; so imo this feels there must be a component hand over somewhere that doesnt retry if its step fails half way through; but guess there are more ways to cause this behaviour. Would be great to at least have a sensible story so we can understand if our user base will be at risk not getting important updates. system image client.log: http://paste.ubuntu.com/8522507/ will attach ubuntu-download-manager logs as tarball too... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-download-manager/+bug/1379025/+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 1379025] [NEW] phone didnt see updates from r89 to r91 until r93 became available
Public bug reported: situation as best as i can capture: 1. updated in morning to r89 2. had internet outage for half a day 3. afterwards r91 was published 4. system settings didnt offer to upgrade system 5. while debugging r93 became available and system settings started downloading etc. checking with barry and sergio it seems udm had some kind of troubles getting back to system image when asked to check for updates. what makes no sense is that it recovered when new image r93 was there; so imo this feels there must be a component hand over somewhere that doesnt retry if its step fails half way through; but guess there are more ways to cause this behaviour. Would be great to at least have a sensible story so we can understand if our user base will be at risk not getting important updates. system image client.log: http://paste.ubuntu.com/8522507/ will attach ubuntu-download-manager logs as tarball too... ** Affects: ubuntu-download-manager (Ubuntu) Importance: Undecided Assignee: Sergio Schvezov (sergiusens) Status: New -- 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/1379025 Title: phone didnt see updates from r89 to r91 until r93 became available Status in “ubuntu-download-manager” package in Ubuntu: New Bug description: situation as best as i can capture: 1. updated in morning to r89 2. had internet outage for half a day 3. afterwards r91 was published 4. system settings didnt offer to upgrade system 5. while debugging r93 became available and system settings started downloading etc. checking with barry and sergio it seems udm had some kind of troubles getting back to system image when asked to check for updates. what makes no sense is that it recovered when new image r93 was there; so imo this feels there must be a component hand over somewhere that doesnt retry if its step fails half way through; but guess there are more ways to cause this behaviour. Would be great to at least have a sensible story so we can understand if our user base will be at risk not getting important updates. system image client.log: http://paste.ubuntu.com/8522507/ will attach ubuntu-download-manager logs as tarball too... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-download-manager/+bug/1379025/+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 1379025] Re: phone didnt see updates from r89 to r91 until r93 became available
dont know what to do here, feels super risky; assigning to sergio who said he will try something with mocking, but feel free to unassign if you dont have an idea. Please dont close this bug as invalid etc. until we have a story or until we haven't seen something similar for ages. if you need anything, just ask me on IRC as my bugmail process is not very good ... ** Changed in: ubuntu-download-manager (Ubuntu) Assignee: (unassigned) = Sergio Schvezov (sergiusens) -- 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/1379025 Title: phone didnt see updates from r89 to r91 until r93 became available Status in “ubuntu-download-manager” package in Ubuntu: New Bug description: situation as best as i can capture: 1. updated in morning to r89 2. had internet outage for half a day 3. afterwards r91 was published 4. system settings didnt offer to upgrade system 5. while debugging r93 became available and system settings started downloading etc. checking with barry and sergio it seems udm had some kind of troubles getting back to system image when asked to check for updates. what makes no sense is that it recovered when new image r93 was there; so imo this feels there must be a component hand over somewhere that doesnt retry if its step fails half way through; but guess there are more ways to cause this behaviour. Would be great to at least have a sensible story so we can understand if our user base will be at risk not getting important updates. system image client.log: http://paste.ubuntu.com/8522507/ will attach ubuntu-download-manager logs as tarball too... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-download-manager/+bug/1379025/+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 1379025] Re: phone didnt see updates from r89 to r91 until r93 became available
** Attachment added: ubuntu-download-manager.INFO https://bugs.launchpad.net/ubuntu/+source/ubuntu-download-manager/+bug/1379025/+attachment/4228923/+files/ubuntu-download-manager.INFO -- 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/1379025 Title: phone didnt see updates from r89 to r91 until r93 became available Status in “ubuntu-download-manager” package in Ubuntu: New Bug description: situation as best as i can capture: 1. updated in morning to r89 2. had internet outage for half a day 3. afterwards r91 was published 4. system settings didnt offer to upgrade system 5. while debugging r93 became available and system settings started downloading etc. checking with barry and sergio it seems udm had some kind of troubles getting back to system image when asked to check for updates. what makes no sense is that it recovered when new image r93 was there; so imo this feels there must be a component hand over somewhere that doesnt retry if its step fails half way through; but guess there are more ways to cause this behaviour. Would be great to at least have a sensible story so we can understand if our user base will be at risk not getting important updates. system image client.log: http://paste.ubuntu.com/8522507/ will attach ubuntu-download-manager logs as tarball too... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-download-manager/+bug/1379025/+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 1374397] Re: Camera app takes 1 minute to load
bumped camera-app task to critical on request by joe/victorp. ** Changed in: camera-app Importance: High = Critical -- 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/1374397 Title: Camera app takes 1 minute to load Status in Camera App: In Progress Bug description: current build number: 2 device name: krillin channel: ubuntu-touch/ubuntu-rtm/14.09 last update: 2014-09-24 20:28:13 version version: 2 version ubuntu: 20140924 version device: 20140919-1b3e670 version custom: 1411084873 After a moment with the phone, the camera-app takes up to one minute to load. Immediately after a reboot it just takes a few seconds. When it happens the spinner is spinning for a few seconds, then everything hangs (UI stops responding, launcher, panel and switcher doesn't work) and after one minute or so the camera eventually starts and shell is back to normal operations. When it starts happening once, only a reboot makes the camera behave properly again. To manage notifications about this bug go to: https://bugs.launchpad.net/camera-app/+bug/1374397/+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 1371454] Re: unity8.indicators.tests.test_indicators.IndicatorExistsTestCase.test_indicator_exists hangs on mako #245 #246
if there was a new media-hub landing, then guess that might be a good
candidate to try backing out locally and see if that helps.
--
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/1371454
Title:
unity8.indicators.tests.test_indicators.IndicatorExistsTestCase.test_indicator_exists
hangs on mako #245 #246
Status in Media Hub:
New
Status in “unity8” package in Ubuntu:
Opinion
Bug description:
Steps to reproduce - take
* flash ubuntu-touch/devel-proposed reviosion 245 or later to mako
* configure pin, developer mode, writable-image, network, ..
* sudo apt-get install unity8-autopilot
* sudo powerd-cli display on bright
* autopilot run -v unity8-autopilot unity8
tests seem to run fine up to this point:
07:15:01.082 DEBUG __init__:305 - Unity started, waiting for it to be ready.
07:15:01.088 DEBUG dbus:433 - Selecting objects of type QQuickView with
attributes: {}
07:15:01.185 DEBUG dbus:433 - Selecting objects of any type with attributes:
{'objectName': 'greeterContentLoader'}
07:15:02.658 DEBUG __init__:307 - Unity loaded and ready.
07:15:02.659 DEBUG dbus:433 - Selecting objects of type QQuickView with
attributes: {}
07:15:02.730 DEBUG dbus:433 - Selecting objects of type Greeter with
attributes: {}
07:15:04.068 INFO process_helpers:95 - Greeter unlocked, continuing.
07:15:04.069 DEBUG dbus:433 - Selecting objects of type QQuickView with
attributes: {}
07:15:04.166 DEBUG dbus:433 - Selecting objects of type
DefaultIndicatorWidget with attributes: {'objectName': 'indicator-power-widget'}
07:15:05.095 INFO __init__:330 - Stopping unity
07:15:06.262 INFO __init__:246 - Resetting upstart env QT_LOAD_TESTABILITY to
None
07:15:06.432 INFO testresult:46 - OK:
unity8.indicators.tests.test_indicators.IndicatorExistsTestCase.test_indicator_exists(Power,Native
Device)
07:15:06.436 INFO globals:58 -
07:15:06.436 INFO globals:59 - Starting test
unity8.indicators.tests.test_indicators.IndicatorExistsTestCase.test_indicator_exists
(Sound,Native Device)
07:15:06.438 WARNING testcase:116 - No tracing available - install the
python-autopilot-trace package!
07:15:06.443 WARNING testcase:157 - Process manager backend unavailable,
application snapshot support disabled.
07:15:06.452 WARNING utilities:265 - WARNING: in file
/usr/lib/python2.7/dist-packages/unity8/shell/tests/__init__.py, line 164 in
setUp
This function is deprecated. Please use 'the Touch class to instantiate a
device object' instead.
07:15:06.727 INFO __init__:268 - Lib path is
'/usr/lib/arm-linux-gnueabihf/unity8', binary path is '/usr/bin/unity8'
07:15:06.729 INFO __init__:346 - Setting up LightDM mock type 'single'
07:15:06.837 INFO __init__:355 - New library path:
/usr/lib/arm-linux-gnueabihf/unity8/qml/mocks/libusermetrics:/usr/lib/arm-linux-gnueabihf/unity8/qml/mocks/LightDM/single
07:15:06.884 INFO __init__:108 - New QML2 import path:
/usr/lib/arm-linux-gnueabihf/unity8/qml/mocks
07:15:06.951 INFO __init__:317 - Starting unity
07:15:07.047 INFO process_helpers:151 - Starting job unity8 with arguments
('BINARY=/usr/bin/unity8', 'ARGS=',
'XDG_DATA_DIRS=/usr/share/unity8/mocks/data:/usr/share/ubuntu-touch:/usr/local/share:/usr/share',
'LD_LIBRARY_PATH=/usr/lib/arm-linux-gnueabihf/unity8/qml/mocks/libusermetrics:/usr/lib/arm-linux-gnueabihf/unity8/qml/mocks/LightDM/single',
'QML2_IMPORT_PATH=/usr/lib/arm-linux-gnueabihf/unity8/qml/mocks',
'QT_LOAD_TESTABILITY=1').
07:15:07.679 INFO process_helpers:159 - unity8 start/running, process 7450
07:15:33.540 ERROR proxies:410 - Introspect error on
:1.391:/com/canonical/Autopilot/Introspection: dbus.exceptions.DBusException:
org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes
include: the remote application did not send a reply, the message bus security
policy blocked the reply, the reply timeout expired, or the network connection
was broken.
07:15:33.547 DEBUG proxies:413 - Executing introspect queue due to error
07:16:25.189 ERROR proxies:410 - Introspect error on
:1.413:/com/canonical/Autopilot/Introspection: dbus.exceptions.DBusException:
org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes
include: the remote application did not send a reply, the message bus security
policy blocked the reply, the reply timeout expired, or the network connection
was broken.
07:16:25.195 DEBUG proxies:413 - Executing introspect queue due to error
07:17:15.309 ERROR proxies:410 - Introspect error on
:1.391:/com/canonical/Autopilot/Introspection: dbus.exceptions.DBusException:
org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes
include: the remote application did not send a reply, the message bus security
policy blocked the reply, the reply timeout
[Touch-packages] [Bug 1371454] Re: unity8.indicators.tests.test_indicators.IndicatorExistsTestCase.test_indicator_exists hangs on mako #245 #246
can you nail down a regression window by image and maybe even package?
This would help finding the cause I guess...
--
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/1371454
Title:
unity8.indicators.tests.test_indicators.IndicatorExistsTestCase.test_indicator_exists
hangs on mako #245 #246
Status in Media Hub:
New
Status in “unity8” package in Ubuntu:
Opinion
Bug description:
Steps to reproduce - take
* flash ubuntu-touch/devel-proposed reviosion 245 or later to mako
* configure pin, developer mode, writable-image, network, ..
* sudo apt-get install unity8-autopilot
* sudo powerd-cli display on bright
* autopilot run -v unity8-autopilot unity8
tests seem to run fine up to this point:
07:15:01.082 DEBUG __init__:305 - Unity started, waiting for it to be ready.
07:15:01.088 DEBUG dbus:433 - Selecting objects of type QQuickView with
attributes: {}
07:15:01.185 DEBUG dbus:433 - Selecting objects of any type with attributes:
{'objectName': 'greeterContentLoader'}
07:15:02.658 DEBUG __init__:307 - Unity loaded and ready.
07:15:02.659 DEBUG dbus:433 - Selecting objects of type QQuickView with
attributes: {}
07:15:02.730 DEBUG dbus:433 - Selecting objects of type Greeter with
attributes: {}
07:15:04.068 INFO process_helpers:95 - Greeter unlocked, continuing.
07:15:04.069 DEBUG dbus:433 - Selecting objects of type QQuickView with
attributes: {}
07:15:04.166 DEBUG dbus:433 - Selecting objects of type
DefaultIndicatorWidget with attributes: {'objectName': 'indicator-power-widget'}
07:15:05.095 INFO __init__:330 - Stopping unity
07:15:06.262 INFO __init__:246 - Resetting upstart env QT_LOAD_TESTABILITY to
None
07:15:06.432 INFO testresult:46 - OK:
unity8.indicators.tests.test_indicators.IndicatorExistsTestCase.test_indicator_exists(Power,Native
Device)
07:15:06.436 INFO globals:58 -
07:15:06.436 INFO globals:59 - Starting test
unity8.indicators.tests.test_indicators.IndicatorExistsTestCase.test_indicator_exists
(Sound,Native Device)
07:15:06.438 WARNING testcase:116 - No tracing available - install the
python-autopilot-trace package!
07:15:06.443 WARNING testcase:157 - Process manager backend unavailable,
application snapshot support disabled.
07:15:06.452 WARNING utilities:265 - WARNING: in file
/usr/lib/python2.7/dist-packages/unity8/shell/tests/__init__.py, line 164 in
setUp
This function is deprecated. Please use 'the Touch class to instantiate a
device object' instead.
07:15:06.727 INFO __init__:268 - Lib path is
'/usr/lib/arm-linux-gnueabihf/unity8', binary path is '/usr/bin/unity8'
07:15:06.729 INFO __init__:346 - Setting up LightDM mock type 'single'
07:15:06.837 INFO __init__:355 - New library path:
/usr/lib/arm-linux-gnueabihf/unity8/qml/mocks/libusermetrics:/usr/lib/arm-linux-gnueabihf/unity8/qml/mocks/LightDM/single
07:15:06.884 INFO __init__:108 - New QML2 import path:
/usr/lib/arm-linux-gnueabihf/unity8/qml/mocks
07:15:06.951 INFO __init__:317 - Starting unity
07:15:07.047 INFO process_helpers:151 - Starting job unity8 with arguments
('BINARY=/usr/bin/unity8', 'ARGS=',
'XDG_DATA_DIRS=/usr/share/unity8/mocks/data:/usr/share/ubuntu-touch:/usr/local/share:/usr/share',
'LD_LIBRARY_PATH=/usr/lib/arm-linux-gnueabihf/unity8/qml/mocks/libusermetrics:/usr/lib/arm-linux-gnueabihf/unity8/qml/mocks/LightDM/single',
'QML2_IMPORT_PATH=/usr/lib/arm-linux-gnueabihf/unity8/qml/mocks',
'QT_LOAD_TESTABILITY=1').
07:15:07.679 INFO process_helpers:159 - unity8 start/running, process 7450
07:15:33.540 ERROR proxies:410 - Introspect error on
:1.391:/com/canonical/Autopilot/Introspection: dbus.exceptions.DBusException:
org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes
include: the remote application did not send a reply, the message bus security
policy blocked the reply, the reply timeout expired, or the network connection
was broken.
07:15:33.547 DEBUG proxies:413 - Executing introspect queue due to error
07:16:25.189 ERROR proxies:410 - Introspect error on
:1.413:/com/canonical/Autopilot/Introspection: dbus.exceptions.DBusException:
org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes
include: the remote application did not send a reply, the message bus security
policy blocked the reply, the reply timeout expired, or the network connection
was broken.
07:16:25.195 DEBUG proxies:413 - Executing introspect queue due to error
07:17:15.309 ERROR proxies:410 - Introspect error on
:1.391:/com/canonical/Autopilot/Introspection: dbus.exceptions.DBusException:
org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes
include: the remote application did not send a reply, the message bus security
policy blocked the reply, the reply timeout expired, or the
[Touch-packages] [Bug 1370106] Re: telepathy-ofono crashed with SIGSEGV in ~QString()
Hey, can we submit these to the error tracker too? or is there an error tracker OOPS? Would be interesting to see how frequent this crash signature is seen by our dogfooders. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to telepathy-ofono in Ubuntu. https://bugs.launchpad.net/bugs/1370106 Title: telepathy-ofono crashed with SIGSEGV in ~QString() Status in “telepathy-ofono” package in Ubuntu: New Bug description: I don't have definitive steps. I was trying to switch between two calls multiple times, and also a multiple times tried to merge them as well (though my network does not support call merging). ProblemType: Crash DistroRelease: Ubuntu 14.10 Package: telepathy-ofono 0.2+14.10.20140910-0ubuntu1 Uname: Linux 3.4.0-5-mako armv7l ApportVersion: 2.14.7-0ubuntu2 Architecture: armhf CurrentDesktop: Unity Date: Tue Sep 16 20:09:25 2014 ExecutablePath: /usr/lib/telepathy/telepathy-ofono InstallationDate: Installed on 2014-09-16 (0 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20140916-020205) ProcCmdline: /usr/lib/telepathy/telepathy-ofono Signal: 11 SourcePackage: telepathy-ofono StacktraceTop: oFonoCallChannel::onDtmfComplete(bool) () QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/arm-linux-gnueabihf/libQt5Core.so.5 OfonoVoiceCallManager::sendTonesComplete(bool) () from /usr/lib/arm-linux-gnueabihf/libofono-qt.so.1 ?? () from /usr/lib/arm-linux-gnueabihf/libofono-qt.so.1 OfonoVoiceCallManager::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib/arm-linux-gnueabihf/libofono-qt.so.1 Title: telepathy-ofono crashed with SIGSEGV in oFonoCallChannel::onDtmfComplete() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip plugdev sudo tty video To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/telepathy-ofono/+bug/1370106/+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 1295623] Re: Sometimes input breaks and only edges are responsive
would be good to get the fix landed in rtm today or tomorrow so we can use a promoted image to hand to customer QA team this week.. -- 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/1295623 Title: Sometimes input breaks and only edges are responsive Status in The Unity 8 shell: In Progress Status in “unity8” package in Ubuntu: In Progress Bug description: I had the music app (paused) open over night on my mako, waking up the device I found the application page showing me the one open app. The shell page itself is completely unresponsive, all side edge swipes seem to work fine though. I can switch to the music app when swiping from the right, bring up the launcher from the left and use the indicators from the top. When I am in the music app I can bring up the HUD from the bottom (trying to close the app, since the closing via the unresponsive shell does not work) but the HUD is completely unresponsive. Trying to close the HUD again via swiping down I see the indicators expand behind it and I am able to get input into the expanded indicators behind the HUD, but not the HUD itself. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity8 7.84+14.04.20140319.1-0ubuntu1 Uname: Linux 3.4.0-5-mako armv7l ApportVersion: 2.13.3-0ubuntu1 Architecture: armhf Date: Fri Mar 21 11:57:53 2014 InstallationDate: Installed on 2014-03-20 (1 days ago) InstallationMedia: Ubuntu Trusty Tahr (development branch) - armhf (20140320) ProcEnviron: TERM=linux PATH=(custom, no user) SourcePackage: unity8 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/unity8/+bug/1295623/+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 1366314] [NEW] security issue? auto suggest seems to copy credentials into clipboard
Public bug reported: on todays image (krillin rtm-proposed r21) with ONLY auto suggest language option on I get: 13:57 asac 1. kill terminal 13:57 asac 2. open terminal and enter pin 13:57 asac 3. click in terminal pastes my pin :) obviously not good for security. Think might be bad. Seems its not getting to dictionary at least: 13:58 asac 4. /me uses backspace to delete 13:58 asac 5. type ls 13:58 asac 6. type first digit of pin - does not suggest my pin This doesn't happen if I turn auto suggestion off. Not sure if the paste is what doesn't happen or the clipboarding doesn't happen. Surely important to check out and know for sure. We should check other credential prompts too: pin lock screen, sim pin etc. Haven't tried, but I assume UITK password fields and browser dont have that, but might be worth checking. Thanks! ** Affects: ubuntu-keyboard (Ubuntu) Importance: Critical Status: New ** Tags: rtm14 ** Description changed: - on todays image (krillin rtm-proposed r21) + on todays image (krillin rtm-proposed r21) with ONLY auto suggest + language option on I get: - 13:57 asac 1. kill terminal + 13:57 asac 1. kill terminal 13:57 asac 2. open terminal and enter pin 13:57 asac 3. click in terminal pastes my pin :) obviously not good for security. Think might be bad. Seems its not getting to dictionary at least: 13:58 asac 4. /me uses backspace to delete 13:58 asac 5. type ls 13:58 asac 6. type first digit of pin - does not suggest my pin - we should check other credential prompts too: pin lock screen, sim pin + This doesn't happen if I turn auto suggestion off. Not sure if the paste + is what doesn't happen or the clipboarding doesn't happen. Surely + important to check out and know for sure. + + We should check other credential prompts too: pin lock screen, sim pin etc. Haven't tried, but I assume UITK password fields and browser dont have that, but might be worth checking. Thanks! ** Changed in: ubuntu-keyboard (Ubuntu) Importance: Undecided = Critical ** Tags added: rtm14 ** Summary changed: - auto suggest seems to copy credentials into clipboard + security issue? auto suggest seems to copy credentials into clipboard -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-keyboard in Ubuntu. https://bugs.launchpad.net/bugs/1366314 Title: security issue? auto suggest seems to copy credentials into clipboard Status in “ubuntu-keyboard” package in Ubuntu: New Bug description: on todays image (krillin rtm-proposed r21) with ONLY auto suggest language option on I get: 13:57 asac 1. kill terminal 13:57 asac 2. open terminal and enter pin 13:57 asac 3. click in terminal pastes my pin :) obviously not good for security. Think might be bad. Seems its not getting to dictionary at least: 13:58 asac 4. /me uses backspace to delete 13:58 asac 5. type ls 13:58 asac 6. type first digit of pin - does not suggest my pin This doesn't happen if I turn auto suggestion off. Not sure if the paste is what doesn't happen or the clipboarding doesn't happen. Surely important to check out and know for sure. We should check other credential prompts too: pin lock screen, sim pin etc. Haven't tried, but I assume UITK password fields and browser dont have that, but might be worth checking. Thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-keyboard/+bug/1366314/+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 1365095] Re: Greeter not asking for pin code in image 11 (krillin)
** Tags added: rtm14 -- 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/1365095 Title: Greeter not asking for pin code in image 11 (krillin) Status in “lightdm” package in Ubuntu: New Status in “unity8” package in Ubuntu: Confirmed Status in “unity8” package in Ubuntu RTM: New Status in “unity8” source package in 14.09: New Bug description: Flashed with: adb reboot bootloader; ubuntu-device-flash --channel =ubuntu-touch/utopic-proposed --bootstrap phablet@ubuntu-phablet:~$ system-image-cli -i current build number: 11 device name: krillin channel: ubuntu-touch/utopic-proposed last update: 2014-09-03 17:25:13 version version: 11 version ubuntu: 20140903.1 version device: 20140902-42bae3c Wizard worked fine, and I selected pin code, adding my passwd with 4 digits, but Unity8 is not requesting my pin once it's up (not even after reboot). The welcome wizard is also showing up at every boot. Nothing special in the wizard, accepted everything and skipped the network setup. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1365095/+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 1365095] Re: Greeter not asking for pin code in image 11 (krillin)
** Changed in: unity8 (Ubuntu) Importance: Undecided = High -- 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/1365095 Title: Greeter not asking for pin code in image 11 (krillin) Status in “lightdm” package in Ubuntu: New Status in “unity8” package in Ubuntu: Confirmed Status in “unity8” package in Ubuntu RTM: New Status in “unity8” source package in 14.09: New Bug description: Flashed with: adb reboot bootloader; ubuntu-device-flash --channel =ubuntu-touch/utopic-proposed --bootstrap phablet@ubuntu-phablet:~$ system-image-cli -i current build number: 11 device name: krillin channel: ubuntu-touch/utopic-proposed last update: 2014-09-03 17:25:13 version version: 11 version ubuntu: 20140903.1 version device: 20140902-42bae3c Wizard worked fine, and I selected pin code, adding my passwd with 4 digits, but Unity8 is not requesting my pin once it's up (not even after reboot). The welcome wizard is also showing up at every boot. Nothing special in the wizard, accepted everything and skipped the network setup. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1365095/+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 1361181] Re: dragging files in nautilus onto an SD card does not work
tenatively putting it on critical to target it for next week milestone image... if there is prio conflict, please let me know. ** Changed in: mtp (Ubuntu) Importance: High = Critical -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mtp in Ubuntu. https://bugs.launchpad.net/bugs/1361181 Title: dragging files in nautilus onto an SD card does not work Status in “mtp” package in Ubuntu: Confirmed Bug description: Steps: 1. Have an sd card into the phone 2. Plug the phone into your ubuntu desktop (I am on Utopic) 3. Note that the sd card is not visible under the krillin folder in nautilus 4. Drag some video files over Result: There was an error copying the file into mtp://[usb:002,010]/BEB5-7A9F. libmtp error: Could not send object info. Expected: The files are copied over This is on krillin r207 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mtp/+bug/1361181/+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 1360593] Re: unity8 freezes randomly
reproduced hang. followed gdb instructions; this didn't produce a gdb.txt; here what i got on console: adb shell root@ubuntu-phablet:/# gdb program `pidof unity8` GNU gdb (Ubuntu 7.8-0ubuntu1) 7.8 Copyright (C) 2014 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type show copying and show warranty for details. This GDB was configured as arm-linux-gnueabihf. Type show configuration for configuration details. For bug reporting instructions, please see: http://www.gnu.org/software/gdb/bugs/. Find the GDB manual and other documentation resources online at: http://www.gnu.org/software/gdb/documentation/. For help, type help. Type apropos word to search for commands related to word... program: No such file or directory. Attaching to process 6503 Reading symbols from /usr/bin/unity8...(no debugging symbols found)...done. Reading symbols from /usr/lib/arm-linux-gnueabihf/libQt5Gui.so.5...(no debugging symbols found)...done. Loaded symbols for /usr/lib/arm-linux-gnueabihf/libQt5Gui.so.5 Reading symbols from /usr/lib/arm-linux-gnueabihf/libQt5Qml.so.5...(no debugging symbols found)...done. Loaded symbols for /usr/lib/arm-linux-gnueabihf/libQt5Qml.so.5 Reading symbols from /usr/lib/arm-linux-gnueabihf/libQt5Quick.so.5...(no debugging symbols found)...done. Loaded symbols for /usr/lib/arm-linux-gnueabihf/libQt5Quick.so.5 Reading symbols from /usr/lib/arm-linux-gnueabihf/libQt5Network.so.5...(no debugging symbols found)...done. Loaded symbols for /usr/lib/arm-linux-gnueabihf/libQt5Network.so.5 Reading symbols from /usr/lib/arm-linux-gnueabihf/libQt5Core.so.5...(no debugging symbols found)...done. Loaded symbols for /usr/lib/arm-linux-gnueabihf/libQt5Core.so.5 Reading symbols from /usr/lib/arm-linux-gnueabihf/libstdc++.so.6...(no debugging symbols found)...done. Loaded symbols for /usr/lib/arm-linux-gnueabihf/libstdc++.so.6 Reading symbols from /lib/arm-linux-gnueabihf/libgcc_s.so.1...(no debugging symbols found)...done. Loaded symbols for /lib/arm-linux-gnueabihf/libgcc_s.so.1 Reading symbols from /lib/arm-linux-gnueabihf/libc.so.6...(no debugging symbols found)...done. Loaded symbols for /lib/arm-linux-gnueabihf/libc.so.6 Reading symbols from /lib/ld-linux-armhf.so.3...(no debugging symbols found)...done. Loaded symbols for /lib/ld-linux-armhf.so.3 Reading symbols from /lib/arm-linux-gnueabihf/libpng12.so.0...(no debugging symbols found)...done. Loaded symbols for /lib/arm-linux-gnueabihf/libpng12.so.0 Reading symbols from /usr/lib/arm-linux-gnueabihf/libharfbuzz.so.0...(no debugging symbols found)...done. Loaded symbols for /usr/lib/arm-linux-gnueabihf/libharfbuzz.so.0 Reading symbols from /lib/arm-linux-gnueabihf/libz.so.1...(no debugging symbols found)...done. Loaded symbols for /lib/arm-linux-gnueabihf/libz.so.1 Reading symbols from /usr/lib/arm-linux-gnueabihf/libhybris-egl/libGLESv2.so.2...(no debugging symbols found)...done. Loaded symbols for /usr/lib/arm-linux-gnueabihf/libhybris-egl/libGLESv2.so.2 Reading symbols from /lib/arm-linux-gnueabihf/libm.so.6...(no debugging symbols found)...done. Loaded symbols for /lib/arm-linux-gnueabihf/libm.so.6 Reading symbols from /lib/arm-linux-gnueabihf/libpthread.so.0...(no debugging symbols found)...done. [New LWP 8000] [New LWP 6840] [New LWP 6839] [New LWP 6838] [New LWP 6828] [New LWP 6770] [New LWP 6763] [New LWP 6669] [New LWP 6617] [New LWP 6566] [New LWP 6562] [New LWP 6561] [New LWP 6544] [New LWP 6543] [New LWP 6542] [New LWP 6541] [New LWP 6540] [New LWP 6539] [New LWP 6538] [New LWP 6537] [New LWP 6536] [New LWP 6535] [New LWP 6531] [Thread debugging using libthread_db enabled] Using host libthread_db library /lib/arm-linux-gnueabihf/libthread_db.so.1. Loaded symbols for /lib/arm-linux-gnueabihf/libpthread.so.0 Reading symbols from /usr/lib/arm-linux-gnueabihf/libicui18n.so.52...(no debugging symbols found)...done. Loaded symbols for /usr/lib/arm-linux-gnueabihf/libicui18n.so.52 Reading symbols from /usr/lib/arm-linux-gnueabihf/libicuuc.so.52...(no debugging symbols found)...done. Loaded symbols for /usr/lib/arm-linux-gnueabihf/libicuuc.so.52 Reading symbols from /lib/arm-linux-gnueabihf/libdl.so.2...(no debugging symbols found)...done. Loaded symbols for /lib/arm-linux-gnueabihf/libdl.so.2 Reading symbols from /lib/arm-linux-gnueabihf/libglib-2.0.so.0...(no debugging symbols found)...done. Loaded symbols for /lib/arm-linux-gnueabihf/libglib-2.0.so.0 Reading symbols from /lib/arm-linux-gnueabihf/librt.so.1...(no debugging symbols found)...done. Loaded symbols for /lib/arm-linux-gnueabihf/librt.so.1 Reading symbols from /usr/lib/arm-linux-gnueabihf/libfreetype.so.6...(no debugging symbols found)...done. Loaded symbols for /usr/lib/arm-linux-gnueabihf/libfreetype.so.6 Reading symbols from /usr/lib/arm-linux-gnueabihf/libgraphite2.so.3...(no debugging symbols
[Touch-packages] [Bug 1360593] Re: unity8 freezes randomly
ok, had to cd to /tmp so its writable... attached the gdb.txt file; seems its the same then what i posted inline before. ** Attachment added: gdb.txt https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1360593/+attachment/4187215/+files/gdb.txt -- 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/1360593 Title: unity8 freezes randomly Status in “unity8” package in Ubuntu: New Bug description: krillin #205 [Sorry for the poor description] On krillin UI freeze randomly. For example on the screenshot it occurred while dragging the greeter to unlock the phone. I was playing music, woke up the phone with the power button to turn the display on and did a right edge swipe to remove the greeter. This has been reported by several people in the past days, but I didn't find a pattern to reproduce this bug reliably. There is no crash in /var/crash and no apport activity. If I press the power button to turn the screen off/on again, the greeter is completely displayed (ie. doesn't cover half of the screen like the screenshot) but the UI is not responsive to gestures or input events. A long press on the power button shows the shutdown dialog but none of the button can be pressed. top doesn't show any specific process going crazy ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: unity8 8.00+14.10.20140822-0ubuntu1 Uname: Linux 3.4.67 armv7l ApportVersion: 2.14.6-0ubuntu2 Architecture: armhf Date: Sat Aug 23 14:18:00 2014 InstallationDate: Installed on 2014-08-23 (0 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20140823-020205) SourcePackage: unity8 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1360593/+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 1360582] Re: Can't manually install clicks Signature verification error since #205
I tested on our rtm image r6; seems I can still install apps from store, which means we could backout the click change that introduced the signature checking. ** Also affects: click (Ubuntu) Importance: Undecided Status: New -- 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/1360582 Title: Can't manually install clicks Signature verification error since #205 Status in “click” package in Ubuntu: New Status in “phablet-tools” package in Ubuntu: Confirmed Bug description: See mailing list thread at https://lists.launchpad.net/ubuntu- phone/msg09607.html Since image #205 I can't install click packages using click-buddy pkcon install-local. Changed click-buddy to use adb $ADBOPTS shell click install --user=$DEVICE_USER --allow-unauthenticated /tmp/$click which worked for me, but dunno if that's the right thing to do. alan@deep-thought:~/phablet/code/coreapps⟫ adb push com.ubuntu.music_1.3.597_all.click /tmp 2560 KB/s (401406 bytes in 0.153s) alan@deep-thought:~/phablet/code/coreapps⟫ phablet-shell start: Job is already running: ssh /home/alan/.ssh/known_hosts updated. Original contents retained as /home/alan/.ssh/known_hosts.old 9 KB/s (399 bytes in 0.040s) Warning: Permanently added '[localhost]:' (RSA) to the list of known hosts. Welcome to Ubuntu Utopic Unicorn (development branch) (GNU/Linux 3.4.0-5-mako armv7l) * Documentation: https://help.ubuntu.com/ Last login: Fri Aug 22 23:53:19 2014 from localhost.localdomain phablet@ubuntu-phablet:~$ pkcon install-local /tmp/com.ubuntu.music_1.3.597_all.click Installing files [=] Finished [=] Installing files [=] Waiting for authentication[=] Starting [=] Finished [=] Fatal error: /tmp/com.ubuntu.music_1.3.597_all.click failed to install. Cannot install /tmp/com.ubuntu.music_1.3.597_all.click: Signature verification error: debsig: Origin Signature check failed. This deb might not be signed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/click/+bug/1360582/+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 1360582] Re: Can't manually install clicks Signature verification error since #205
will SDK work without further changes with the patch by mvo or do we need to coordinate some landing? -- 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/1360582 Title: Can't manually install clicks Signature verification error since #205 Status in “click” package in Ubuntu: Confirmed Status in “phablet-tools” package in Ubuntu: Confirmed Bug description: See mailing list thread at https://lists.launchpad.net/ubuntu- phone/msg09607.html Since image #205 I can't install click packages using click-buddy pkcon install-local. Changed click-buddy to use adb $ADBOPTS shell click install --user=$DEVICE_USER --allow-unauthenticated /tmp/$click which worked for me, but dunno if that's the right thing to do. alan@deep-thought:~/phablet/code/coreapps⟫ adb push com.ubuntu.music_1.3.597_all.click /tmp 2560 KB/s (401406 bytes in 0.153s) alan@deep-thought:~/phablet/code/coreapps⟫ phablet-shell start: Job is already running: ssh /home/alan/.ssh/known_hosts updated. Original contents retained as /home/alan/.ssh/known_hosts.old 9 KB/s (399 bytes in 0.040s) Warning: Permanently added '[localhost]:' (RSA) to the list of known hosts. Welcome to Ubuntu Utopic Unicorn (development branch) (GNU/Linux 3.4.0-5-mako armv7l) * Documentation: https://help.ubuntu.com/ Last login: Fri Aug 22 23:53:19 2014 from localhost.localdomain phablet@ubuntu-phablet:~$ pkcon install-local /tmp/com.ubuntu.music_1.3.597_all.click Installing files [=] Finished [=] Installing files [=] Waiting for authentication[=] Starting [=] Finished [=] Fatal error: /tmp/com.ubuntu.music_1.3.597_all.click failed to install. Cannot install /tmp/com.ubuntu.music_1.3.597_all.click: Signature verification error: debsig: Origin Signature check failed. This deb might not be signed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/click/+bug/1360582/+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 1360569] Re: /usr/bin/mtp-server:6:__gnu_cxx::__verbose_terminate_handler:__cxxabiv1::__terminate:std::terminate:__cxxabiv1::__cxa_throw:core::dbus::Bus::send_with_reply_and_bloc
top crasher on armhf on errors.ubuntu.com; assigning cypher for now... ** Changed in: mtp (Ubuntu) Importance: Undecided = High ** Tags added: rtm14 ** Changed in: mtp (Ubuntu) Assignee: (unassigned) = Mathieu Trudel-Lapierre (mathieu-tl) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mtp in Ubuntu. https://bugs.launchpad.net/bugs/1360569 Title: /usr/bin/mtp- server:6:__gnu_cxx::__verbose_terminate_handler:__cxxabiv1::__terminate:std::terminate:__cxxabiv1::__cxa_throw:core::dbus::Bus::send_with_reply_and_block_for_at_most Status in “mtp” package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding mtp. This problem was most recently seen with version 0.0.4+14.10.20140821-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/0f0165a8d2d5c03c309e06a5ad25aa2db26daf76 contains more details. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mtp/+bug/1360569/+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 1360569] Re: /usr/bin/mtp-server:6:__gnu_cxx::__verbose_terminate_handler:__cxxabiv1::__terminate:std::terminate:__cxxabiv1::__cxa_throw:core::dbus::Bus::send_with_reply_and_bloc
** Changed in: mtp (Ubuntu) Importance: High = Critical ** Summary changed: - /usr/bin/mtp-server:6:__gnu_cxx::__verbose_terminate_handler:__cxxabiv1::__terminate:std::terminate:__cxxabiv1::__cxa_throw:core::dbus::Bus::send_with_reply_and_block_for_at_most + TOPCRASHER: /usr/bin/mtp-server:6:__gnu_cxx::__verbose_terminate_handler:__cxxabiv1::__terminate:std::terminate:__cxxabiv1::__cxa_throw:core::dbus::Bus::send_with_reply_and_block_for_at_most -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mtp in Ubuntu. https://bugs.launchpad.net/bugs/1360569 Title: TOPCRASHER: /usr/bin/mtp- server:6:__gnu_cxx::__verbose_terminate_handler:__cxxabiv1::__terminate:std::terminate:__cxxabiv1::__cxa_throw:core::dbus::Bus::send_with_reply_and_block_for_at_most Status in “mtp” package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding mtp. This problem was most recently seen with version 0.0.4+14.10.20140821-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/0f0165a8d2d5c03c309e06a5ad25aa2db26daf76 contains more details. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mtp/+bug/1360569/+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 1358384] Re: MP4s won't play without a reboot of the phone
could be related or same as bug 1358712 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mediascanner in Ubuntu. https://bugs.launchpad.net/bugs/1358384 Title: MP4s won't play without a reboot of the phone Status in “mediascanner” package in Ubuntu: New Bug description: this is krillin r197 Steps: 1. Have an mp4 file 2. Plug your phone into your computer 3. In nautilus, drill down into the Videos folder 4. Copy the video over 5. Go to the video scope, note that the video is not there 6. go to file manager, click on the file, note that the video does not play 7. Reboot the phone Observed: The video is now in the scope and plays Expected: The video works without rebooting the phone To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mediascanner/+bug/1358384/+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 1358384] Re: MP4s won't play without a reboot of the phone
for me mediascanner also falls over on krillin r199; it works for same video on N4. ./.cache/upstart/mediascanner-2.0.log shows: Extracting metadata from /home/phablet/Videos/big_buck_bunny_480p_H264_AAC_25fps_1800K.MP4. Error when indexing: Unable to discover file /home/phablet/Videos/big_buck_bunny_480p_H264_AAC_25fps_1800K.MP4 Videos i tried: + http://samplemedia.linaro.org/H264/big_buck_bunny_480p_H264_AAC_25fps_1800K_short.MP4 + http://samplemedia.linaro.org/H264/big_buck_bunny_720p_H264_AAC_25fps_3400K_short.MP4 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mediascanner in Ubuntu. https://bugs.launchpad.net/bugs/1358384 Title: MP4s won't play without a reboot of the phone Status in “mediascanner” package in Ubuntu: New Bug description: this is krillin r197 Steps: 1. Have an mp4 file 2. Plug your phone into your computer 3. In nautilus, drill down into the Videos folder 4. Copy the video over 5. Go to the video scope, note that the video is not there 6. go to file manager, click on the file, note that the video does not play 7. Reboot the phone Observed: The video is now in the scope and plays Expected: The video works without rebooting the phone To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mediascanner/+bug/1358384/+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 1329289] Re: Messaging indicator sometimes fails to send a reply
this bug annoyed me regularly enough for last few month and today i lost again big text i typed because of that; bumping to high, mark avengers, surely something we try to nail for RTM. ** Tags added: avengers ** Changed in: indicator-messages (Ubuntu) Importance: Undecided = High ** Changed in: indicator-messages (Ubuntu) Assignee: (unassigned) = Thomas Strehl (strehl-t) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-messages in Ubuntu. https://bugs.launchpad.net/bugs/1329289 Title: Messaging indicator sometimes fails to send a reply Status in “indicator-messages” package in Ubuntu: Confirmed Bug description: STEPS: 1. Open the messaging app 2. Send a message to your own phone 3. Close the messaging app 4. Hit the power button 5. Drag down the indicator 6. Reply to the message 7 Repeat steps 5-6 until the indicator nolonger send the meassage and instead saves it. See attached screenshot note the greyed send button WORKAROUND: Remove all messages from the indicator and use the messaging app once to reply, you will then be good till your indicator locks up again. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: indicator-messages 13.10.1+14.10.20140611-0ubuntu1 Uname: Linux 3.4.0-5-mako armv7l ApportVersion: 2.14.3-0ubuntu1 Architecture: armhf Date: Thu Jun 12 12:01:29 2014 InstallationDate: Installed on 2014-06-12 (0 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20140612) SourcePackage: indicator-messages UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-messages/+bug/1329289/+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 1329289] Re: Messaging indicator sometimes fails to send a reply
assigning to thostr to raise awareness for now. ** Changed in: indicator-messages (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-messages in Ubuntu. https://bugs.launchpad.net/bugs/1329289 Title: Messaging indicator sometimes fails to send a reply Status in “indicator-messages” package in Ubuntu: Confirmed Bug description: STEPS: 1. Open the messaging app 2. Send a message to your own phone 3. Close the messaging app 4. Hit the power button 5. Drag down the indicator 6. Reply to the message 7 Repeat steps 5-6 until the indicator nolonger send the meassage and instead saves it. See attached screenshot note the greyed send button WORKAROUND: Remove all messages from the indicator and use the messaging app once to reply, you will then be good till your indicator locks up again. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: indicator-messages 13.10.1+14.10.20140611-0ubuntu1 Uname: Linux 3.4.0-5-mako armv7l ApportVersion: 2.14.3-0ubuntu1 Architecture: armhf Date: Thu Jun 12 12:01:29 2014 InstallationDate: Installed on 2014-06-12 (0 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20140612) SourcePackage: indicator-messages UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-messages/+bug/1329289/+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
