[Touch-packages] [Bug 1367304] Re: adbd crashes if adb root is used
** Changed in: android-tools (Ubuntu) Status: New = Confirmed ** Changed in: android-tools (Ubuntu) Importance: Undecided = Medium ** Changed in: android-tools (Ubuntu) Assignee: (unassigned) = Oliver Grawert (ogra) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to android-tools in Ubuntu. https://bugs.launchpad.net/bugs/1367304 Title: adbd crashes if adb root is used Status in “android-tools” package in Ubuntu: Confirmed Bug description: adbd crashes when adb root is used, instead it should be a noop, this came up because the Ubuntu SDK is using adb root in one of the device detection scripts (Line 27): http://pastebin.ubuntu.com/8300137/ ogra_ zbenjamin, on android adbd starts as the shell user and with adb root you can switch to a full root user mode ogra_ we dont allow that at all zbenjamin ogra_: sergiusens: ah ok zbenjamin thanks ogra_ zbenjamin, so a bug against android-tools would help ... adbd should not crash ... it should just be a no-op sergiusens zbenjamin: you probably can get rid of the adb_root function comletely ogra_ zbenjamin, feel free to assign me directly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/android-tools/+bug/1367304/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1327139] Re: mirscreencast broke (moved socket) in #71
iirc the move was a security team requirement, i assume the default socket should actually be moved to $XDG_RUNTIME_DIR and yes, then the lightdm startup should drop teh arg. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1327139 Title: mirscreencast broke (moved socket) in #71 Status in Light Display Manager: New Status in Mir: Invalid Status in “mir” package in Ubuntu: Invalid Status in “phablet-tools” package in Ubuntu: Fix Released Bug description: Since the mir_socket moved from /tmp to /var/run, mirscreencast broke. $ adb shell mirscreencast -n 1 Failed to connect to server. Error was :connect: No such file or directory This works:- $ adb shell mirscreencast -m /var/run/mir_socket -n 1 ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: mir-utils 0.1.9+14.10.20140430.1-0ubuntu1 Uname: Linux 3.4.0-5-mako armv7l ApportVersion: 2.14.3-0ubuntu1 Architecture: armhf Date: Fri Jun 6 10:47:19 2014 InstallationDate: Installed on 2014-06-06 (0 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20140606.1) SourcePackage: mir UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1327139/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1368084] Re: phablet-shell: 72: [: /bin/bash:: unexpected operator, tries to read /root/.bash_profile
fixed in the latest android-tools-adbd ** Changed in: phablet-tools (Ubuntu) Status: New = Invalid ** Changed in: android-tools (Ubuntu) Status: New = Fix Released ** Changed in: android-tools (Ubuntu) Importance: Undecided = High ** Changed in: android-tools (Ubuntu) Assignee: (unassigned) = Oliver Grawert (ogra) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to android-tools in Ubuntu. https://bugs.launchpad.net/bugs/1368084 Title: phablet-shell: 72: [: /bin/bash:: unexpected operator, tries to read /root/.bash_profile Status in “android-tools” package in Ubuntu: Fix Released Status in “phablet-tools” package in Ubuntu: Invalid Bug description: Recent phablet-shell (r307) gives a lot of error messages: $ ~/ubuntu/phablet-tools/phablet-shell /home/martin/ubuntu/phablet-tools/phablet-shell: 72: [: /bin/bash:: unexpected operator /bin/bash: /root/.bash_profile: Permission denied /home/martin/.ssh/known_hosts updated. Original contents retained as /home/martin/.ssh/known_hosts.old 9 KB/s (395 bytes in 0.040s) /bin/bash: /root/.bash_profile: Permission denied /bin/bash: /root/.bash_profile: Permission denied /bin/bash: /root/.bash_profile: Permission denied The syntax error comes from ADBUID=$(adb shell id -u|tr -d '\n') if [ $ADBUID -eq 0 ]; then as the shell command includes all these errors about /root/.bash_profile: $ adb shell 'id -u' /bin/bash: /root/.bash_profile: Permission denied 32011 Supposedly the recent changes to adbd forgot to set a proper $HOME or something similar? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/android-tools/+bug/1368084/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1371048] Re: phone believed to enforce undocumented password policy
there is no hard coding it checks if the username and password are identical ... in teh beginning of working on developer mode this helped to force people to update their password and make sure dev-mode was properly enabled (we used to set the password to match teh username in former installs) indeed this code needs to go ... password secuity needs to be managed while the password is being set anyway ** Changed in: android-tools (Ubuntu) Status: New = Confirmed ** Changed in: android-tools (Ubuntu) Importance: Undecided = High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to android-tools in Ubuntu. https://bugs.launchpad.net/bugs/1371048 Title: phone believed to enforce undocumented password policy Status in “android-tools” package in Ubuntu: Confirmed Bug description: Per conversation on IRC with ogra. The phone will reject passwords which match the username. Fine and dandy, but isn't password security the responsibilty of other entities and code. Rejecting just this insecure password, hard-coded, seems a bit odd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/android-tools/+bug/1371048/+subscriptions -- Mailing list: https://launchpad.net/~touch-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
we see a similar error in utopic smoke tests since a while, these do not
show up in rtm image tests at all. paul nailed down the first image
where it started to show up in smoke testing to
http://people.canonical.com/~ogra/touch-image-stats/233.changes ...
the adbd and system-settings packages on that list are also in rtm which
makes them very unlikely to be the cause.
this leaves pcap, gettext and gstreamer ... i wonder if downgrading one
of them to their former version might help.
--
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
[Touch-packages] [Bug 1371454] Re: unity8.indicators.tests.test_indicators.IndicatorExistsTestCase.test_indicator_exists hangs on mako #245 #246
did anyone try to downgrade to the former gstreamer1.0-plugins-base
version yet ?
--
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 network connection
was broken.
[Touch-packages] [Bug 1363129] Re: No more syslog update after the 21st of August
*** This bug is a duplicate of bug 1332538 *** https://bugs.launchpad.net/bugs/1332538 ** This bug has been marked a duplicate of bug 1332538 No UID checks on rootfs updates -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsyslog in Ubuntu. https://bugs.launchpad.net/bugs/1363129 Title: No more syslog update after the 21st of August Status in “rsyslog” package in Ubuntu: Confirmed Bug description: Since the 21st of August, my phone doesn't have any other syslog update. I noticed the files had started being owned by 'usermetrics'. Some details: $ ls /var/log/syslog -rw-r- 1 root adm 9076723 Aug 21 11:56 /var/log/syslog $ ls /var drwxrwxr-x 12 root usermetrics 4096 Aug 29 07:49 log $ df /var/log Filesystem 1K-blocksUsed Available Use% Mounted on /dev/mmcblk0p23 5942324 2263384 3376708 41% /var/log To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1363129/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1350881] [NEW] Left edge drag area should be below the OSK
Public bug reported: with recent changes of unity8 in image 160 and above typing letters that live in the most left column of the keyboard got pretty hard since they are not fully sensitive anymore. ** Affects: ubuntu-ux Importance: Undecided Status: New ** Affects: unity8 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1350881 Title: Left edge drag area should be below the OSK Status in Ubuntu UX bugs: New Status in “unity8” package in Ubuntu: New Bug description: with recent changes of unity8 in image 160 and above typing letters that live in the most left column of the keyboard got pretty hard since they are not fully sensitive anymore. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1350881/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1270248] Re: /var/log fills up disk space on phone
lxc-android-config (0.185) utopic; urgency=medium * ship /etc/cron.hourly/logrotate to make sure on very noisy systems the syslog file doesn't excessively grow before we can rotate it. ... lxc-android-config (0.182) utopic; urgency=medium * divert rsyslog logrotate config and ship /etc/logrotate.d/touch-syslog as a replacement, this makes sure the file will be flushed by logrotate once it hits 10M in size. ** Changed in: logrotate (Ubuntu) Status: Confirmed = Invalid ** Also affects: lxc-android-config (Ubuntu) Importance: Undecided Status: New ** Changed in: lxc-android-config (Ubuntu) Importance: Undecided = Critical ** Changed in: lxc-android-config (Ubuntu) Assignee: (unassigned) = Oliver Grawert (ogra) ** Changed in: lxc-android-config (Ubuntu) Status: New = Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to logrotate in Ubuntu. https://bugs.launchpad.net/bugs/1270248 Title: /var/log fills up disk space on phone Status in “android” package in Ubuntu: New Status in “linux-flo” package in Ubuntu: Confirmed Status in “linux-mako” package in Ubuntu: Fix Released Status in “logrotate” package in Ubuntu: Invalid Status in “lxc-android-config” package in Ubuntu: Fix Released Bug description: The effect of this is that certain important things stop working. For example, text messages are no longer displayed in the messaging app. root@ubuntu-phablet:/# du -hcs /var/log/* 0 /var/log/alternatives.log 12K /var/log/alternatives.log.1 4.0K /var/log/apport.log 8.0K /var/log/apport.log.1 4.0K /var/log/apport.log.2.gz 4.0K /var/log/apport.log.3.gz 4.0K /var/log/apport.log.4.gz 4.0K /var/log/apport.log.5.gz 8.0K /var/log/apport.log.6.gz 4.0K /var/log/apport.log.7.gz 16K /var/log/apt 128K /var/log/auth.log 212K /var/log/auth.log.1 8.0K /var/log/auth.log.2.gz 8.0K /var/log/auth.log.3.gz 8.0K /var/log/auth.log.4.gz 56K /var/log/bootstrap.log 0 /var/log/btmp 0 /var/log/btmp.1 56K /var/log/dmesg 44K /var/log/dmesg.0 16K /var/log/dmesg.3.gz 16K /var/log/dmesg.4.gz 0 /var/log/dpkg.log 640K /var/log/dpkg.log.1 752K /var/log/faillog 4.0K /var/log/fontconfig.log 12K /var/log/fsck 4.0K /var/log/installer 265M /var/log/kern.log 311M /var/log/kern.log.1 27M /var/log/kern.log.2.gz 34M /var/log/kern.log.3.gz 19M /var/log/kern.log.4.gz 9.0M /var/log/lastlog 12K /var/log/lightdm 16K /var/log/lxc 0 /var/log/mail.err 0 /var/log/mail.log 4.0K /var/log/news 272K /var/log/pm-powersave.log 200K /var/log/pm-powersave.log.1 4.0K /var/log/pm-powersave.log.2.gz 101M /var/log/syslog 52M /var/log/syslog.1 1.4M /var/log/syslog.1.gz 4.5M /var/log/syslog.2.gz 5.9M /var/log/syslog.3.gz 764K /var/log/syslog.4.gz 3.3M /var/log/syslog.5.gz 6.4M /var/log/syslog.6.gz 2.6M /var/log/syslog.7.gz 156K /var/log/system-image 340K /var/log/udev 0 /var/log/ufw.log 4.0K /var/log/unattended-upgrades 724K /var/log/upstart 120K /var/log/wtmp 100K /var/log/wtmp.1 844M total root@ubuntu-phablet:/# ls -l total 72 drwxrwxrwt 7 root root 140 Jan 16 16:41 android drwxr-xr-x 2 root root4096 Jan 7 13:39 bin drwxr-xr-x 2 root root4096 Oct 18 10:07 boot lrwxrwxrwx 1 root root 14 Oct 26 17:22 cache - /android/cache lrwxrwxrwx 1 root root 13 Oct 26 17:22 data - /android/data drwxr-xr-x 17 root root6180 Jan 16 16:48 dev drwxr-xr-x 98 root root4096 Jan 9 14:53 etc lrwxrwxrwx 1 root root 16 Oct 26 17:22 factory - /android/factory lrwxrwxrwx 1 root root 17 Oct 26 17:22 firmware - /android/firmware drwxr-xr-x 3 root root4096 Oct 26 17:18 home drwxr-xr-x 18 root root4096 Jan 9 14:52 lib drwxr-xr-x 2 root root 16384 Oct 26 17:18 lost+found drwxr-xr-x 2 root root4096 Oct 24 12:47 media drwxr-xr-x 2 root root4096 Oct 18 10:07 mnt drwxr-xr-x 3 root root4096 Oct 26 17:18 opt lrwxrwxrwx 1 root root 16 Oct 26 17:22 persist - /android/persist dr-xr-xr-x 236 root root 0 Dec 31 1969 proc drwx-- 2 root root4096 Oct 26 17:18 root drwxr-xr-x 18 root root 600 Jan 16 16:41 run drwxr-xr-x 2 root root4096 Jan 9 14:52 sbin drwxr-xr-x 2 root root4096 Oct 24 12:47 srv dr-xr-xr-x 12 root root 0 Jan 16 16:41 sys lrwxrwxrwx 1 root root 15 Oct 26 17:22 system - /android/system drwxrwxrwt 6 root root 320 Jan 17 12:18 tmp drwxrwx--x 7 system system 4096 Nov 4 08:20 userdata drwxr-xr-x 10 root root4096 Oct 26 17:22 usr drwxr-xr-x 13 root root4096 Oct 26 17:22 var lrwxrwxrwx 1 root root 22 Oct 26 17:22 vendor - /android/system/vendor To manage
[Touch-packages] [Bug 1328646] Re: Clock out of sync on resume from suspend
i must say that you are very lucky only getting teh clock being off by a few minutes ... *every* morning when i go to the landing meeting which starts at 10:30 for me the notification for that particular meeting goes off at 10:40 or 10:45 ... when the screen turns on with the notification both, the lock screen and indicator still show a time around 10:20 .. this is reproducable every morning for me ... -- 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/1328646 Title: Clock out of sync on resume from suspend Status in The Date and Time Indicator: New Status in The Unity 8 shell: Triaged Status in “indicator-datetime” package in Ubuntu: Confirmed Bug description: When the device is resumed by pressing the power button and the device is not connected over USB the clock is out of sync You need another system to compare the time to verify this bug report, and make sure both clocks are in sync. TEST CASE 1. Unplug the device from its USB cable 2. Press the power button to switch to suspend mode or wait until it goes to suspend 3. Wait 2 or more minutes 4. Press the power button again to resume the device 5. Compare the time on the greeter and indicator with the time on the other system EXPECTED RESULT Clocks are in sync ACTUAL RESULT Time on the device is behind by several minutes. The use case are people who use their device as a watch. You usually resume it, check the time, suspend it. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: unity8 7.88+14.10.20140606-0ubuntu1 Uname: Linux 3.4.0-5-mako armv7l ApportVersion: 2.14.3-0ubuntu1 Architecture: armhf Date: Tue Jun 10 19:11:42 2014 InstallationDate: Installed on 2014-06-10 (0 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20140610) SourcePackage: unity8 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-datetime/+bug/1328646/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1350881] Re: Left edge drag area should be below the OSK
** Changed in: unity8 (Ubuntu) Status: New = Confirmed -- 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/1350881 Title: Left edge drag area should be below the OSK Status in Ubuntu UX bugs: New Status in “unity8” package in Ubuntu: Confirmed Bug description: with recent changes of unity8 in image 160 and above typing letters that live in the most left column of the keyboard got pretty hard since they are not fully sensitive anymore. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1350881/+subscriptions -- Mailing list: https://launchpad.net/~touch-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
a session upstart job that flushes the cache after upgrades should be shipped (with lxc-android-config or ubuntu-touch-session) i.e call it /usr/share/upstart/sessions/clear-qml-caches.conf with the following content (untested, but should work): # This allows to flush all app caches when # a new image version arrives start on :sys:boot-hooks WHEN=new-version pre-start script # clear all QML app caches on image upgrade CACHEDIR=$HOME/.cache/QML [ -e $CACHEDIR ] rm -rf $CACHEDIR/* end script -- 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: Incomplete Status in “qtdeclarative-opensource-src” package in Ubuntu RTM: New 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 1380946] Re: Remove account-plugin-evernote from phone image
** Also affects: ubuntu-touch-meta (Ubuntu RTM) Importance: Undecided Status: New ** Changed in: ubuntu-touch-meta (Ubuntu RTM) Status: New = Fix Committed ** Changed in: ubuntu-touch-meta (Ubuntu) Status: In Progress = Fix Committed ** Changed in: ubuntu-touch-meta (Ubuntu RTM) Importance: Undecided = Critical ** Changed in: ubuntu-touch-meta (Ubuntu RTM) Assignee: (unassigned) = Oliver Grawert (ogra) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-touch-meta in Ubuntu. https://bugs.launchpad.net/bugs/1380946 Title: Remove account-plugin-evernote from phone image Status in “ubuntu-touch-meta” package in Ubuntu: Fix Committed Status in “ubuntu-touch-meta” package in Ubuntu RTM: Fix Committed Bug description: We want to ship an evernote accounts plugin in the reminders-app click package. As such we no longer need the account-plugin-evernote in the image. Note: the main reason for the move is that we want to ship the Evernote API key in the Reminders app click package instead of a .deb package. This way we're not tied to system updates if the key needs to be updated or revoked. In addition to that, we can get Jenkins to manage the API keys and keep them private instead of making them public. This needs to be coordinated with an upload of the new Reminders app that includes the account in the click package: https://bugs.launchpad.net/reminders-app/+bug/1367235 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-touch-meta/+bug/1380946/+subscriptions -- Mailing list: https://launchpad.net/~touch-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
if the dash would not be in lifecycle management at all and you would have gotten your system in such a state, the kernel would just have randomly killed bits of your session instead of the dash. it is wanted that in such cases the dash gets killed before i.e. ofono gets killed so that your session still stays functional. imho the behavior is just fine, in case the sysem functions normal it should be the last of your UI apps that gets killed. in case where not even that would free up enough memory you have a whole lot of bigger probs ... the bug here lies within the apps that consume all your ram where they should not. -- 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: Fix Released Status in “unity8” package in Ubuntu: Invalid Status in “qtmir” package in Ubuntu RTM: New 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 1382278] Re: Image #94 on mako / #88 on flo fails to start - mir crash
qtmir was changed in image #93 (which translates to rtm krillin image 111) image #94 maps to krillin rtm 112 for which the change set is at http://people.canonical.com/~ogra/touch-image-stats/rtm/112.changes ... note that the libhybris change in there required a change on the android side, i assume this bit was forgotten for mako. ** Also affects: libhybris (Ubuntu) Importance: Undecided Status: New ** Package changed: libhybris (Ubuntu) = libhybris (Ubuntu RTM) -- 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/1382278 Title: Image #94 on mako / #88 on flo fails to start - mir crash Status in “qtmir” package in Ubuntu: Confirmed Status in “unity8” package in Ubuntu: Confirmed Status in “libhybris” package in Ubuntu RTM: New Bug description: Update from #93 to #94 and I get the constant ubuntu spinning logo. adb shell to device and find unity8, maliit and unity8-dash dying, this is in their logs. Reverting to #93 'fixes' it, and going forward to #94 breaks it again. FATAL: UbuntuClientIntegration: connection to Mir server failed. Check that a Mir server is running, and the correct socket is being used and is accessible. The shell may have rejected the incoming connection, so check its log file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtmir/+bug/1382278/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1382559] [NEW] adbd does not check the screen state before allowing a connection
Public bug reported: according to https://wiki.ubuntu.com/SecurityAndPrivacySettings/ProtectingUserData adbd should only allow a connection attempt to succeed when teh screen is unlocked. adbd currently does not do this and needs to be fixed. ** Affects: android-tools (Ubuntu) Importance: Critical Assignee: Oliver Grawert (ogra) Status: Confirmed ** Tags: ota-1 rtm14 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to android-tools in Ubuntu. https://bugs.launchpad.net/bugs/1382559 Title: adbd does not check the screen state before allowing a connection Status in “android-tools” package in Ubuntu: Confirmed Bug description: according to https://wiki.ubuntu.com/SecurityAndPrivacySettings/ProtectingUserData adbd should only allow a connection attempt to succeed when teh screen is unlocked. adbd currently does not do this and needs to be fixed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/android-tools/+bug/1382559/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1382559] Re: adbd does not check the screen state before allowing a connection
additionaly there needs to be support for an override file the installer can put in place so that this feature does not break our automated testing. ** Changed in: android-tools (Ubuntu) Status: New = Confirmed ** Changed in: android-tools (Ubuntu) Importance: Undecided = Critical ** Tags added: ota-1 rtm14 ** Changed in: android-tools (Ubuntu) Assignee: (unassigned) = Oliver Grawert (ogra) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to android-tools in Ubuntu. https://bugs.launchpad.net/bugs/1382559 Title: adbd does not check the screen state before allowing a connection Status in “android-tools” package in Ubuntu: Confirmed Bug description: according to https://wiki.ubuntu.com/SecurityAndPrivacySettings/ProtectingUserData adbd should only allow a connection attempt to succeed when teh screen is unlocked. adbd currently does not do this and needs to be fixed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/android-tools/+bug/1382559/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1383479] Re: Remove autopilot from touch images
** Changed in: ubuntu-touch-meta (Ubuntu) Assignee: (unassigned) = Oliver Grawert (ogra) ** Changed in: ubuntu-touch-meta (Ubuntu) Importance: Undecided = Critical ** Changed in: ubuntu-touch-meta (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-touch-meta in Ubuntu. https://bugs.launchpad.net/bugs/1383479 Title: Remove autopilot from touch images Status in “ubuntu-touch-meta” package in Ubuntu: Confirmed Bug description: Autopilot should be removed from the image. We intend to ship a consumer image, testing and debugging packages such as autopilot should not be needed. The ramfications affect app developers and CI who depend and assume autopilot exists on the image. To fix this, CI will migrate to adt- run. In the interim, autopilot will be added as a dependency so the current CI setup continues to run properly. phablet-test-run will also migrate to a wrapper for adt-run so users who have not already switched will have a seamless experience. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-touch-meta/+bug/1383479/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1383494] [NEW] prefixing existing phone numbers with a country code only adds 0 in the front and immediately appends + at the end of the number
Public bug reported: when i try to use an international code instead of the zero in i.e. 0561 ... in the number field of the dialer app, pressing and holding the 0 on the numberpad produces something 00561 + which makes it impossible to actually add the country prefix to replace the first 0 in the number. ** Affects: dialer-app (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dialer-app in Ubuntu. https://bugs.launchpad.net/bugs/1383494 Title: prefixing existing phone numbers with a country code only adds 0 in the front and immediately appends + at the end of the number Status in “dialer-app” package in Ubuntu: New Bug description: when i try to use an international code instead of the zero in i.e. 0561 ... in the number field of the dialer app, pressing and holding the 0 on the numberpad produces something 00561 + which makes it impossible to actually add the country prefix to replace the first 0 in the number. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dialer-app/+bug/1383494/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1383479] Re: Remove autopilot from touch images
there is an apparmor file that needs to move from autopilot-touch into dbus-property-service, added the according bugtasks ** Also affects: dbus-property-service (Ubuntu) Importance: Undecided Status: New ** Changed in: dbus-property-service (Ubuntu) Status: New = Confirmed ** Changed in: dbus-property-service (Ubuntu) Importance: Undecided = Critical ** Changed in: dbus-property-service (Ubuntu) Assignee: (unassigned) = Oliver Grawert (ogra) ** Also affects: dbus-property-service (Ubuntu RTM) Importance: Undecided Status: New ** Changed in: dbus-property-service (Ubuntu RTM) Status: New = Confirmed ** Changed in: dbus-property-service (Ubuntu RTM) Importance: Undecided = Critical ** Changed in: dbus-property-service (Ubuntu RTM) Assignee: (unassigned) = Oliver Grawert (ogra) ** Also affects: ubuntu-touch-meta (Ubuntu RTM) Importance: Undecided Status: New ** Changed in: ubuntu-touch-meta (Ubuntu RTM) Status: New = Confirmed ** Changed in: ubuntu-touch-meta (Ubuntu RTM) Importance: Undecided = Critical ** Changed in: ubuntu-touch-meta (Ubuntu RTM) Assignee: (unassigned) = Oliver Grawert (ogra) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-touch-meta in Ubuntu. https://bugs.launchpad.net/bugs/1383479 Title: Remove autopilot from touch images Status in “dbus-property-service” package in Ubuntu: Confirmed Status in “ubuntu-touch-meta” package in Ubuntu: Confirmed Status in “dbus-property-service” package in Ubuntu RTM: Confirmed Status in “ubuntu-touch-meta” package in Ubuntu RTM: Confirmed Bug description: Autopilot should be removed from the image. We intend to ship a consumer image, testing and debugging packages such as autopilot should not be needed. The ramfications affect app developers and CI who depend and assume autopilot exists on the image. To fix this, CI will migrate to adt- run. In the interim, autopilot will be added as a dependency so the current CI setup continues to run properly. phablet-test-run will also migrate to a wrapper for adt-run so users who have not already switched will have a seamless experience. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbus-property-service/+bug/1383479/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1383479] Re: Remove autopilot from touch images
** Also affects: autopilot (Ubuntu) Importance: Undecided Status: New ** Also affects: autopilot (Ubuntu RTM) Importance: Undecided Status: New ** Changed in: autopilot (Ubuntu) Importance: Undecided = Critical ** Changed in: autopilot (Ubuntu RTM) Importance: Undecided = Critical ** Changed in: autopilot (Ubuntu) Assignee: (unassigned) = Christopher Lee (veebers) ** Changed in: autopilot (Ubuntu) Status: New = Confirmed ** Changed in: autopilot (Ubuntu RTM) Status: New = Incomplete ** Changed in: autopilot (Ubuntu RTM) Status: Incomplete = Confirmed ** Changed in: autopilot (Ubuntu RTM) Assignee: (unassigned) = Christopher Lee (veebers) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to autopilot in Ubuntu. https://bugs.launchpad.net/bugs/1383479 Title: Remove autopilot from touch images Status in “autopilot” package in Ubuntu: Confirmed Status in “dbus-property-service” package in Ubuntu: Confirmed Status in “ubuntu-touch-meta” package in Ubuntu: Confirmed Status in “autopilot” package in Ubuntu RTM: Confirmed Status in “dbus-property-service” package in Ubuntu RTM: Confirmed Status in “ubuntu-touch-meta” package in Ubuntu RTM: Confirmed Bug description: Autopilot should be removed from the image. We intend to ship a consumer image, testing and debugging packages such as autopilot should not be needed. The ramfications affect app developers and CI who depend and assume autopilot exists on the image. To fix this, CI will migrate to adt- run. In the interim, autopilot will be added as a dependency so the current CI setup continues to run properly. phablet-test-run will also migrate to a wrapper for adt-run so users who have not already switched will have a seamless experience. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/autopilot/+bug/1383479/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1384841] [NEW] Need to sync tzdata into RTM before final image goes out
Public bug reported: tzdata in Utopic got some serious fixes for a few timezones and DST switching behavior ... if this is not synced into RTM before the final image goes out there will be broken clock and DST switching behavior for the users, which will be very visible. ** Affects: tzdata (Ubuntu) Importance: Undecided Status: Won't Fix ** Affects: tzdata (Ubuntu RTM) Importance: Critical Assignee: Oliver Grawert (ogra) Status: Triaged ** Tags: rtm14 ** Also affects: tzdata (Ubuntu RTM) Importance: Undecided Status: New ** Changed in: tzdata (Ubuntu) Status: New = Won't Fix ** Changed in: tzdata (Ubuntu RTM) Status: New = Triaged ** Changed in: tzdata (Ubuntu RTM) Importance: Undecided = Critical ** Changed in: tzdata (Ubuntu RTM) Assignee: (unassigned) = Oliver Grawert (ogra) ** Tags added: rtm14 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu. https://bugs.launchpad.net/bugs/1384841 Title: Need to sync tzdata into RTM before final image goes out Status in “tzdata” package in Ubuntu: Won't Fix Status in “tzdata” package in Ubuntu RTM: Triaged Bug description: tzdata in Utopic got some serious fixes for a few timezones and DST switching behavior ... if this is not synced into RTM before the final image goes out there will be broken clock and DST switching behavior for the users, which will be very visible. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1384841/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1383479] Re: Remove autopilot from touch images
** Changed in: autopilot (Ubuntu) Status: Confirmed = Fix Released ** Changed in: autopilot (Ubuntu RTM) Status: Confirmed = Fix Released ** Changed in: dbus-property-service (Ubuntu) Status: Confirmed = Fix Released ** Changed in: dbus-property-service (Ubuntu RTM) Status: Confirmed = Fix Released ** Changed in: ubuntu-touch-meta (Ubuntu) Status: Confirmed = Fix Released ** Changed in: ubuntu-touch-meta (Ubuntu RTM) Status: Confirmed = Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to autopilot in Ubuntu. https://bugs.launchpad.net/bugs/1383479 Title: Remove autopilot from touch images Status in “autopilot” package in Ubuntu: Fix Released Status in “dbus-property-service” package in Ubuntu: Fix Released Status in “ubuntu-touch-meta” package in Ubuntu: Fix Released Status in “autopilot” package in Ubuntu RTM: Fix Released Status in “dbus-property-service” package in Ubuntu RTM: Fix Released Status in “ubuntu-touch-meta” package in Ubuntu RTM: Fix Released Bug description: Autopilot should be removed from the image. We intend to ship a consumer image, testing and debugging packages such as autopilot should not be needed. The ramfications affect app developers and CI who depend and assume autopilot exists on the image. To fix this, CI will migrate to adt- run. In the interim, autopilot will be added as a dependency so the current CI setup continues to run properly. phablet-test-run will also migrate to a wrapper for adt-run so users who have not already switched will have a seamless experience. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/autopilot/+bug/1383479/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1385332] [NEW] after notification in pocket turns the screen on device gets locked with too many wrong unlock attempts, wait for 3 min
Public bug reported: having my phone in my pocket i just got some notifications for events which turned on the screen ... obviously while walking with the device in pocket and the screen being on, the movement punched in PIN numbers to the lock screen which made it hit the threshold for too many wrong unlock attempts ** Affects: unity8 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1385332 Title: after notification in pocket turns the screen on device gets locked with too many wrong unlock attempts, wait for 3 min Status in “unity8” package in Ubuntu: New Bug description: having my phone in my pocket i just got some notifications for events which turned on the screen ... obviously while walking with the device in pocket and the screen being on, the movement punched in PIN numbers to the lock screen which made it hit the threshold for too many wrong unlock attempts To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1385332/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1385332] Re: after notification in pocket turns the screen on device gets locked with too many wrong unlock attempts, wait for 3 min
i think the solution here is that notifications should not turn on the screen in your pocket by checking the proximity sensor. ** Tags added: rtm14 ** 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 unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1385332 Title: after notification in pocket turns the screen on device gets locked with too many wrong unlock attempts, wait for 3 min Status in “unity8” package in Ubuntu: New Bug description: having my phone in my pocket i just got some notifications for events which turned on the screen ... obviously while walking with the device in pocket and the screen being on, the movement punched in PIN numbers to the lock screen which made it hit the threshold for too many wrong unlock attempts To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1385332/+subscriptions -- Mailing list: https://launchpad.net/~touch-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
I just had my phone hard locked on the PIN unlock screen due to this issue (screen turned on by an event notification and the ulocking was disabled due to too many wrong unlock attempts ) ... here swipe will not help at all and proximity would be the only solution IMHO -- 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 1358343] Re: [TOPBLOCKER] too easy to answer a call by accident
this was reported as bug 1385332 -- 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 1385473] [NEW] Unlock dialogs (SIM PIN as well as Unlock screen) both do not use custom selected wallpaper
Public bug reported: All unlock dialogs currently do not use a custom wallpaper but show the violet default wallpaper even if the user selected a custom one ... ** Affects: unity8 (Ubuntu) Importance: High Assignee: Michael Zanetti (mzanetti) Status: Confirmed ** Affects: unity8 (Ubuntu RTM) Importance: High Assignee: Michael Zanetti (mzanetti) Status: Confirmed ** Tags: rtm14 ** Changed in: unity8 (Ubuntu) Assignee: (unassigned) = Michael Zanetti (mzanetti) ** Changed in: unity8 (Ubuntu) Importance: Undecided = High ** Changed in: unity8 (Ubuntu) Status: New = Confirmed ** Tags added: rtm14 ** Also affects: unity8 (Ubuntu RTM) Importance: Undecided Status: New ** Changed in: unity8 (Ubuntu RTM) Importance: Undecided = High ** Changed in: unity8 (Ubuntu RTM) Status: New = Confirmed ** Changed in: unity8 (Ubuntu RTM) Assignee: (unassigned) = Michael Zanetti (mzanetti) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1385473 Title: Unlock dialogs (SIM PIN as well as Unlock screen) both do not use custom selected wallpaper Status in “unity8” package in Ubuntu: Confirmed Status in “unity8” package in Ubuntu RTM: Confirmed Bug description: All unlock dialogs currently do not use a custom wallpaper but show the violet default wallpaper even if the user selected a custom one ... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1385473/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1382857] Re: No way to swipe away sound notification
We should at least consider to not show it at all on fullscreen video playback (not to mention it uses the currently hardcoded shell rotation so it comes up in portrait mode while playing video in landscape). pop- over volume notification that you cant swipe away is one of the most annoying things ever invented on mobile OSes, i wonder if we cant do better than the others here :) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-sound in Ubuntu. https://bugs.launchpad.net/bugs/1382857 Title: No way to swipe away sound notification Status in “indicator-sound” package in Ubuntu: Confirmed Bug description: Using RTM 5 on Mako, there is no way to swipe away the new sound notification overlay. While it doesn't last very long, this is annoying. Touching it, or swiping it away, would be a preferable way to dismiss this. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-sound/+bug/1382857/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1387635] Re: unable to install autopilot-touch on vivid, conflicts with dbus-property-service
*** This bug is a duplicate of bug 1385475 *** https://bugs.launchpad.net/bugs/1385475 ** This bug has been marked a duplicate of bug 1385475 error processing archive /var/cache/apt/archives/dbus-property-service_0.7_all.deb (--unpack): trying to overwrite '/usr/share/autopilot-touch/apparmor/click.rules', which is also in package autopilot-touch 1.5.0+14.10.20140812-0ubuntu1 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to autopilot in Ubuntu. https://bugs.launchpad.net/bugs/1387635 Title: unable to install autopilot-touch on vivid, conflicts with dbus- property-service Status in “autopilot” package in Ubuntu: New Status in “dbus-property-service” package in Ubuntu: New Bug description: On flo, vivid image #1: $ sudo apt-get install autopilot-touch Reading package lists... Done Building dependency tree Reading state information... Done The following NEW packages will be installed: autopilot-touch 0 upgraded, 1 newly installed, 0 to remove and 5 not upgraded. 1 not fully installed or removed. Need to get 0 B/1 984 B of archives. After this operation, 50,2 kB of additional disk space will be used. (Reading database ... 41492 files and directories currently installed.) Preparing to unpack .../autopilot-touch_1.5.0+14.10.20140812-0ubuntu1_all.deb ... Unpacking autopilot-touch (1.5.0+14.10.20140812-0ubuntu1) ... dpkg: error processing archive /var/cache/apt/archives/autopilot-touch_1.5.0+14.10.20140812-0ubuntu1_all.deb (--unpack): trying to overwrite '/usr/share/autopilot-touch/apparmor/click.rules', which is also in package dbus-property-service 0.7 Errors were encountered while processing: /var/cache/apt/archives/autopilot-touch_1.5.0+14.10.20140812-0ubuntu1_all.deb E: Sub-process /usr/bin/dpkg returned an error code (1) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/autopilot/+bug/1387635/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1387810] Re: device_changed callback does unnecessary work
in image smoke testing for touch we have a test called systemsettle it checks the idle state of the system before and after a test run by iterating over the top values (it doesnt actually use top but reads directly from /proc) ten times ... if the average idle value for these ten runs is not above 97.5% the test is considered a failure. on the krillin device the systemsettle test constantly fails (while it passes on mako). looking through the logs we found that upowerd, indicator-power, powerd and specifically dbus-daemon seem to always be the top consumers causing the failure of the test. for now we decided to give the test a little more wiggle room by lowering the threshold by 1% but i think it is very valuable to get the described behavior of this bug fixed in the RTM touch image which IMHO will likely make the dbus noise be lower overall. Thus this bug should be on the critical fixes list (the so called olli's list) for RTM. ** Also affects: powerd (Ubuntu RTM) Importance: Undecided Status: New ** Changed in: powerd (Ubuntu RTM) Status: New = Confirmed ** Changed in: powerd (Ubuntu RTM) Importance: Undecided = High -- 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/1387810 Title: device_changed callback does unnecessary work Status in “powerd” package in Ubuntu: New Status in “powerd” package in Ubuntu RTM: Confirmed Bug description: up_device_changed_cb iterates over all devices every time it's called. It is passed the device so this is unnecessary work and will result in a lot of dbus traffic. You should just look at the device which you've been told has changed. With https://code.launchpad.net/~pitti/powerd/upower0.99/+merge/240141 we're getting upower 0.99 support. One of the new additions to the 1.0 API you get with this version is proper notify signals for properties on UpClient and UpDevice. powerd should be refactored to only listen to property changes in the properties it is interested in. This will result in more efficient code and a process that is only woken up when it needs to be, and it will be nicer as it will then be properly event driven. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: powerd (not installed) ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4 Uname: Linux 3.16.0-23-generic x86_64 ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Thu Oct 30 17:05:13 2014 InstallationDate: Installed on 2012-10-07 (752 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Beta amd64 (20121007) SourcePackage: powerd UpgradeStatus: Upgraded to utopic on 2013-05-07 (541 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/powerd/+bug/1387810/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1374553] Re: In image rtm 69 infographics stopped functioning
** Changed in: libusermetrics (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libusermetrics in Ubuntu. https://bugs.launchpad.net/bugs/1374553 Title: In image rtm 69 infographics stopped functioning Status in “libusermetrics” package in Ubuntu: Confirmed Bug description: STEPS: 1. Fresh flash (bootstrap or wipe) image 69 on krillin 2. Make a call for a minute 3. Send yourself an sms 4. Play a game of sudoku 5. play a song 6. hit the power button 7. hit the power button again 8. Tap on the infographics EXPECTED: I expect the infographics to cycle through the the various metrics ACTUAL: You are just shown no data notice. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libusermetrics/+bug/1374553/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1374553] Re: In image rtm 69 infographics stopped functioning
the issue here is that the /var/lib/usermetrics directory does not exist anymore. with the switch to using a hardcoded /etc/passwd|group|shadow on the image in livecd-rootfs we have the users existing in the password db ... usermetricsservice uses the following postinst script: ... if ! getent passwd usermetrics /dev/null; then adduser --system --ingroup usermetrics --home /var/lib/usermetrics usermetrics usermod -c User Metrics usermetrics usermod -d /var/lib/usermetrics usermetrics usermod -g usermetrics usermetrics usermod -s /bin/falseusermetrics fi ... here the adduser line creates the /var/lib/usermetrics directory, but since the user exists already in the database the if will never be executed ... i assume this needs to be fixed in livecd-rootfs since this is teh place where we broke it :) ** Also affects: livecd-rootfs (Ubuntu) Importance: Undecided Status: New ** Changed in: livecd-rootfs (Ubuntu) Importance: Undecided = Critical -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libusermetrics in Ubuntu. https://bugs.launchpad.net/bugs/1374553 Title: In image rtm 69 infographics stopped functioning Status in “libusermetrics” package in Ubuntu: Confirmed Status in “livecd-rootfs” package in Ubuntu: New Bug description: STEPS: 1. Fresh flash (bootstrap or wipe) image 69 on krillin 2. Make a call for a minute 3. Send yourself an sms 4. Play a game of sudoku 5. play a song 6. hit the power button 7. hit the power button again 8. Tap on the infographics EXPECTED: I expect the infographics to cycle through the the various metrics ACTUAL: You are just shown no data notice. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libusermetrics/+bug/1374553/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1374553] Re: In image rtm 69 infographics stopped functioning
the following makes the infographics work again: phablet@ubuntu-phablet:~$ sudo mount -o remount,rw / phablet@ubuntu-phablet:~$ sudo mkdir -p /var/lib/usermetrics phablet@ubuntu-phablet:~$ sudo chown -R usermetrics:usermetrics /var/lib/usermetrics phablet@ubuntu-phablet:~$ sudo chmod 0750 /var/lib/usermetrics phablet@ubuntu-phablet:~$ sudo mount -o remount,ro / phablet@ubuntu-phablet:~$ sudo reboot -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libusermetrics in Ubuntu. https://bugs.launchpad.net/bugs/1374553 Title: In image rtm 69 infographics stopped functioning Status in “libusermetrics” package in Ubuntu: Confirmed Status in “livecd-rootfs” package in Ubuntu: New Bug description: STEPS: 1. Fresh flash (bootstrap or wipe) image 69 on krillin 2. Make a call for a minute 3. Send yourself an sms 4. Play a game of sudoku 5. play a song 6. hit the power button 7. hit the power button again 8. Tap on the infographics EXPECTED: I expect the infographics to cycle through the the various metrics ACTUAL: You are just shown no data notice. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libusermetrics/+bug/1374553/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1374553] Re: In image rtm 69 infographics stopped functioning
** Changed in: libusermetrics (Ubuntu) Status: Confirmed = Invalid ** Changed in: livecd-rootfs (Ubuntu) Status: New = Confirmed ** Also affects: livecd-rootfs (Ubuntu RTM) Importance: Undecided Status: New ** Changed in: livecd-rootfs (Ubuntu RTM) Status: New = Confirmed ** Changed in: livecd-rootfs (Ubuntu RTM) Importance: Undecided = Critical -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libusermetrics in Ubuntu. https://bugs.launchpad.net/bugs/1374553 Title: In image rtm 69 infographics stopped functioning Status in “libusermetrics” package in Ubuntu: Invalid Status in “livecd-rootfs” package in Ubuntu: Confirmed Status in “livecd-rootfs” package in Ubuntu RTM: Confirmed Bug description: STEPS: 1. Fresh flash (bootstrap or wipe) image 69 on krillin 2. Make a call for a minute 3. Send yourself an sms 4. Play a game of sudoku 5. play a song 6. hit the power button 7. hit the power button again 8. Tap on the infographics EXPECTED: I expect the infographics to cycle through the the various metrics ACTUAL: You are just shown no data notice. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libusermetrics/+bug/1374553/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1374553] Re: In image rtm 69 infographics stopped functioning
** Changed in: livecd-rootfs (Ubuntu) Assignee: (unassigned) = Stéphane Graber (stgraber) ** Changed in: livecd-rootfs (Ubuntu RTM) Assignee: (unassigned) = Oliver Grawert (ogra) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libusermetrics in Ubuntu. https://bugs.launchpad.net/bugs/1374553 Title: In image rtm 69 infographics stopped functioning Status in “libusermetrics” package in Ubuntu: Invalid Status in “livecd-rootfs” package in Ubuntu: Confirmed Status in “livecd-rootfs” package in Ubuntu RTM: Confirmed Bug description: STEPS: 1. Fresh flash (bootstrap or wipe) image 69 on krillin 2. Make a call for a minute 3. Send yourself an sms 4. Play a game of sudoku 5. play a song 6. hit the power button 7. hit the power button again 8. Tap on the infographics EXPECTED: I expect the infographics to cycle through the the various metrics ACTUAL: You are just shown no data notice. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libusermetrics/+bug/1374553/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1374650] Re: cannot make dbus connections inside a shell started via adb shell
** Changed in: ubuntu-touch-session (Ubuntu) Assignee: (unassigned) = Oliver Grawert (ogra) ** Changed in: ubuntu-touch-session (Ubuntu) Importance: Undecided = High ** Changed in: ubuntu-touch-session (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-touch-session in Ubuntu. https://bugs.launchpad.net/bugs/1374650 Title: cannot make dbus connections inside a shell started via adb shell Status in “ubuntu-touch-session” package in Ubuntu: Confirmed Bug description: For example launching media-player inside such a shell: /usr/bin/mediaplayer-app file:///home/phablet/Videos/BigBuckBunny_320x180.mp4 --fullscreen --desktop_file_hint=/usr/share/applications/mediaplayer-app.desktop Results in: http://pastebin.ubuntu.com/8436397/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-touch-session/+bug/1374650/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1374650] Re: cannot make dbus connections inside a shell started via adb shell
seemingly a bug in adbd, it does not process the shell invoked by adb shell as login shell (and thus does not parse /etc/profile) ** Also affects: android-tools (Ubuntu) Importance: Undecided Status: New ** Changed in: android-tools (Ubuntu) Importance: Undecided = Critical ** Changed in: android-tools (Ubuntu) Assignee: (unassigned) = Oliver Grawert (ogra) ** Changed in: android-tools (Ubuntu) Status: New = Confirmed ** Changed in: ubuntu-touch-session (Ubuntu) Status: Confirmed = Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-touch-session in Ubuntu. https://bugs.launchpad.net/bugs/1374650 Title: cannot make dbus connections inside a shell started via adb shell Status in “android-tools” package in Ubuntu: Confirmed Status in “ubuntu-touch-session” package in Ubuntu: Invalid Bug description: For example launching media-player inside such a shell: /usr/bin/mediaplayer-app file:///home/phablet/Videos/BigBuckBunny_320x180.mp4 --fullscreen --desktop_file_hint=/usr/share/applications/mediaplayer-app.desktop Results in: http://pastebin.ubuntu.com/8436397/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/android-tools/+bug/1374650/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1374650] Re: cannot make dbus connections inside a shell started via adb shell
** Also affects: android-tools (Ubuntu RTM) Importance: Undecided Status: New ** Changed in: android-tools (Ubuntu RTM) Importance: Undecided = Critical ** Changed in: android-tools (Ubuntu RTM) Status: New = In Progress ** Changed in: android-tools (Ubuntu RTM) Assignee: (unassigned) = Oliver Grawert (ogra) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-touch-session in Ubuntu. https://bugs.launchpad.net/bugs/1374650 Title: cannot make dbus connections inside a shell started via adb shell Status in “android-tools” package in Ubuntu: Fix Released Status in “ubuntu-touch-session” package in Ubuntu: Invalid Status in “android-tools” package in Ubuntu RTM: In Progress Bug description: For example launching media-player inside such a shell: /usr/bin/mediaplayer-app file:///home/phablet/Videos/BigBuckBunny_320x180.mp4 --fullscreen --desktop_file_hint=/usr/share/applications/mediaplayer-app.desktop Results in: http://pastebin.ubuntu.com/8436397/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/android-tools/+bug/1374650/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1371048] Re: phone believed to enforce undocumented password policy
** Also affects: android-tools (Ubuntu RTM) Importance: Undecided Status: New ** Changed in: android-tools (Ubuntu RTM) Status: New = In Progress ** Changed in: android-tools (Ubuntu RTM) Importance: Undecided = High ** Changed in: android-tools (Ubuntu RTM) Assignee: (unassigned) = Oliver Grawert (ogra) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to android-tools in Ubuntu. https://bugs.launchpad.net/bugs/1371048 Title: phone believed to enforce undocumented password policy Status in “android-tools” package in Ubuntu: Fix Released Status in “android-tools” package in Ubuntu RTM: In Progress Bug description: Per conversation on IRC with ogra. The phone will reject passwords which match the username. Fine and dandy, but isn't password security the responsibilty of other entities and code. Rejecting just this insecure password, hard-coded, seems a bit odd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/android-tools/+bug/1371048/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 258110] Re: Camera application cannot record video
** Changed in: cmpc Status: In Progress = Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gstreamer0.10 in Ubuntu. https://bugs.launchpad.net/bugs/258110 Title: Camera application cannot record video Status in Cheese Camera Application: Expired Status in Application and image devlopment around the Classmate PC: Won't Fix Status in “cheese” package in Ubuntu: Fix Released Status in “gstreamer0.10” package in Ubuntu: Fix Released Status in “cheese” source package in Hardy: Fix Released Status in “gstreamer0.10” source package in Hardy: Fix Released Status in “cheese” source package in Intrepid: Fix Released Status in “gstreamer0.10” source package in Intrepid: Fix Released Bug description: Run cheese, select video and start recording.Try clicking stop recording but there's no response. To manage notifications about this bug go to: https://bugs.launchpad.net/cheese/+bug/258110/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1371627] Re: Remove unused fonts
** Changed in: ubuntu-touch-meta (Ubuntu) Status: New = Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-touch-meta in Ubuntu. https://bugs.launchpad.net/bugs/1371627 Title: Remove unused fonts Status in “ubuntu-touch-meta” package in Ubuntu: Fix Released Bug description: fonts-freefont-ttf fonts-dejavu-extra do not seem to be requried and will save 17 MB To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-touch-meta/+bug/1371627/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1323711] Re: music scope and music-app only play songs owned by user 'phablet'
with the switch to phablet for all adb access, adb push will now use this UID for adb push as well ... which makes me belive this bug can be closed ** Changed in: android-tools (Ubuntu) Status: Confirmed = Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to android-tools in Ubuntu. https://bugs.launchpad.net/bugs/1323711 Title: music scope and music-app only play songs owned by user 'phablet' Status in “android-tools” package in Ubuntu: Fix Released Status in “media-hub” package in Ubuntu: New Bug description: Songs not owned by user 'phablet' are not played in Music App and Music scope preview mode, even if the file is readable by this user. TEST CASE: 1. Copy a song (mp3 or ogg) to a device to /home/phablet/Music $ adb push file /home/phablet/Music/ 2. Verify that the file is not owned by phablet but that phablet read access (mode 0666) $ adb shell ls -l /home/phablet/Music/ -rw-rw-rw- 1 root root 25304292 May 26 17:18 test_file 3. Play this song in music scope or music app 4. Verify that the song plays 5. Change ownership of the file to user 'phablet' $ adb shell chown phablet /home/phablet/Music/file EXPECTED RESULT Music app or scope play the song ACTUAL RESULT Music app or scope doesn't play the song and there is no error message. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: media-hub 0.0.2+14.10.20140521-0ubuntu1 Uname: Linux 3.4.0-5-mako armv7l ApportVersion: 2.14.2-0ubuntu4 Architecture: armhf Date: Tue May 27 16:53:47 2014 InstallationDate: Installed on 2014-05-27 (0 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20140527) SourcePackage: media-hub UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/android-tools/+bug/1323711/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1377427] [NEW] white 1 pixel line on left edge of the screen since RTM image 81
Public bug reported: with image 81 my krillin shows a white 1px line on the left edge of the screen, specifically visible when switching apps or sliding the launcher in. ** Affects: unity8 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1377427 Title: white 1 pixel line on left edge of the screen since RTM image 81 Status in “unity8” package in Ubuntu: New Bug description: with image 81 my krillin shows a white 1px line on the left edge of the screen, specifically visible when switching apps or sliding the launcher in. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1377427/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1377427] Re: white 1 pixel line on left edge of the screen since RTM image 81
** Summary changed: - white 1 pxel line on left edge of the screen since RTM image 81 + white 1 pixel line on left edge of the screen since RTM image 81 -- 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/1377427 Title: white 1 pixel line on left edge of the screen since RTM image 81 Status in “unity8” package in Ubuntu: New Bug description: with image 81 my krillin shows a white 1px line on the left edge of the screen, specifically visible when switching apps or sliding the launcher in. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1377427/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1377648] [NEW] dekko cant display content anymore (with apparmor denials for /run/shm/WK2SharedMemory.*)
Public bug reported: since a while dekko does not display any mail content for me anymore ... checking syslog i see a lot of: Oct 5 16:41:33 ubuntu-phablet kernel: [ 6327.720986] (0)[16417:dekko]type=1400 audit(1412520093.649:761): apparmor=DENIED operation=mknod profile=com.ubuntu.developer.dpniel.dekko_dekko_0.2.9 name=/run/shm/WK2SharedMemory.3491348362 pid=16417 comm=dekko requested_mask=c denied_mask=c fsuid=32011 ouid=32011 ** Affects: dekko Importance: Undecided Status: New ** Affects: apparmor-easyprof-ubuntu (Ubuntu) Importance: Undecided Status: New ** Also affects: dekko Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor-easyprof-ubuntu in Ubuntu. https://bugs.launchpad.net/bugs/1377648 Title: dekko cant display content anymore (with apparmor denials for /run/shm/WK2SharedMemory.*) Status in dekko: New Status in “apparmor-easyprof-ubuntu” package in Ubuntu: New Bug description: since a while dekko does not display any mail content for me anymore ... checking syslog i see a lot of: Oct 5 16:41:33 ubuntu-phablet kernel: [ 6327.720986] (0)[16417:dekko]type=1400 audit(1412520093.649:761): apparmor=DENIED operation=mknod profile=com.ubuntu.developer.dpniel.dekko_dekko_0.2.9 name=/run/shm/WK2SharedMemory.3491348362 pid=16417 comm=dekko requested_mask=c denied_mask=c fsuid=32011 ouid=32011 To manage notifications about this bug go to: https://bugs.launchpad.net/dekko/+bug/1377648/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1377427] Re: white 1 pixel line on left edge of the screen since RTM image 81
yes, it seems to have vanished during the day after a few lock/unlock cycles. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1377427 Title: white 1 pixel line on left edge of the screen since RTM image 81 Status in Mir: Incomplete Status in “mir” package in Ubuntu: Incomplete Status in “unity8” package in Ubuntu: New Bug description: with image 81 my krillin shows a white 1px line on the left edge of the screen, specifically visible when switching apps or sliding the launcher in. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1377427/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1377869] Re: Set a positive value to oom_score_adj for session processes
** Also affects: lxc-android-config (Ubuntu RTM) Importance: Undecided Status: New ** Changed in: lxc-android-config (Ubuntu RTM) Importance: Undecided = Critical ** Changed in: lxc-android-config (Ubuntu RTM) Assignee: (unassigned) = Oliver Grawert (ogra) ** Changed in: lxc-android-config (Ubuntu) Status: New = Confirmed ** Changed in: lxc-android-config (Ubuntu RTM) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc-android-config in Ubuntu. https://bugs.launchpad.net/bugs/1377869 Title: Set a positive value to oom_score_adj for session processes Status in “lxc-android-config” package in Ubuntu: Confirmed Status in “lxc-android-config” package in Ubuntu RTM: Confirmed Bug description: Reference: bug 1376165 In /etc/init/lightdm.override the oom score adjustment is set to -10. But system processes have an adjustment of 0 which means system processes will be preferred to session process in out of memory conditions. The score for session processes should be much higher. I tried the following test case: - Take a picture with camera - Copy it 100 times to simulate several shots with the camera. - Then go to the Photo scope - tap on My Pictures With the current setting oom killer selects system dbus or powerd which requires a hard reboot of the device. I tried 300 (this is an example to have a significant difference with current setting) and OOM killer selects unity8-dash (which used 44% of the memory) and the system recovered without a reboot. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: lxc-android-config 0.207 [origin: Ubuntu RTM] Uname: Linux 3.4.67 armv7l ApportVersion: 2.14.7-0ubuntu1 Architecture: armhf Date: Mon Oct 6 11:41:24 2014 InstallationDate: Installed on 2014-09-29 (7 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20140929-030205) PackageArchitecture: all SourcePackage: lxc-android-config UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.init.device.hacks.conf: [modified] mtime.conffile..etc.init.device.hacks.conf: 2014-09-25T15:57:00 upstart.alsa-restore.override: manual upstart.alsa-store.override: manual upstart.boot-hooks: Error: [Errno 21] Is a directory: '/etc/init/boot-hooks' upstart.cups.override: # cups - CUPS Printing spooler and server # socket activation overrides for touch start on socket PROTO=inet PORT=631 ADDR=127.0.0.1 exec /usr/sbin/cupsd -f -x 30 upstart.lxc-net.override: manual upstart.plymouth-upstart-bridge.override: manual upstart.setvtrgb.override: manual upstart.ssh.override: manual exec /usr/sbin/sshd -D -o PasswordAuthentication=no upstart.tty1.override: manual upstart.tty2.override: manual upstart.tty3.override: manual upstart.tty4.override: manual upstart.tty5.override: manual upstart.tty6.override: manual upstart.ureadahead-other.override: manual upstart.ureadahead.override: manual To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc-android-config/+bug/1377869/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1377869] Re: Set a positive value to oom_score_adj for session processes
sigh, indeed the file is in ubuntu-touch-session ... not in lxc-android- config, adjusting bug taslks accordingly ** Also affects: ubuntu-touch-session (Ubuntu) Importance: Undecided Status: New ** Also affects: ubuntu-touch-session (Ubuntu RTM) Importance: Undecided Status: New ** Changed in: ubuntu-touch-session (Ubuntu) Status: New = Confirmed ** Changed in: ubuntu-touch-session (Ubuntu) Importance: Undecided = Critical ** Changed in: ubuntu-touch-session (Ubuntu RTM) Status: New = Confirmed ** Changed in: ubuntu-touch-session (Ubuntu RTM) Importance: Undecided = Critical ** Changed in: ubuntu-touch-session (Ubuntu) Assignee: (unassigned) = Oliver Grawert (ogra) ** Changed in: ubuntu-touch-session (Ubuntu RTM) Assignee: (unassigned) = Oliver Grawert (ogra) ** Changed in: lxc-android-config (Ubuntu) Status: Confirmed = Invalid ** Changed in: lxc-android-config (Ubuntu RTM) Status: Confirmed = Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc-android-config in Ubuntu. https://bugs.launchpad.net/bugs/1377869 Title: Set a positive value to oom_score_adj for session processes Status in “lxc-android-config” package in Ubuntu: Invalid Status in “ubuntu-touch-session” package in Ubuntu: Confirmed Status in “lxc-android-config” package in Ubuntu RTM: Invalid Status in “ubuntu-touch-session” package in Ubuntu RTM: Confirmed Bug description: Reference: bug 1376165 In /etc/init/lightdm.override the oom score adjustment is set to -10. But system processes have an adjustment of 0 which means system processes will be preferred to session process in out of memory conditions. The score for session processes should be much higher. I tried the following test case: - Take a picture with camera - Copy it 100 times to simulate several shots with the camera. - Then go to the Photo scope - tap on My Pictures With the current setting oom killer selects system dbus or powerd which requires a hard reboot of the device. I tried 300 (this is an example to have a significant difference with current setting) and OOM killer selects unity8-dash (which used 44% of the memory) and the system recovered without a reboot. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: lxc-android-config 0.207 [origin: Ubuntu RTM] Uname: Linux 3.4.67 armv7l ApportVersion: 2.14.7-0ubuntu1 Architecture: armhf Date: Mon Oct 6 11:41:24 2014 InstallationDate: Installed on 2014-09-29 (7 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20140929-030205) PackageArchitecture: all SourcePackage: lxc-android-config UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.init.device.hacks.conf: [modified] mtime.conffile..etc.init.device.hacks.conf: 2014-09-25T15:57:00 upstart.alsa-restore.override: manual upstart.alsa-store.override: manual upstart.boot-hooks: Error: [Errno 21] Is a directory: '/etc/init/boot-hooks' upstart.cups.override: # cups - CUPS Printing spooler and server # socket activation overrides for touch start on socket PROTO=inet PORT=631 ADDR=127.0.0.1 exec /usr/sbin/cupsd -f -x 30 upstart.lxc-net.override: manual upstart.plymouth-upstart-bridge.override: manual upstart.setvtrgb.override: manual upstart.ssh.override: manual exec /usr/sbin/sshd -D -o PasswordAuthentication=no upstart.tty1.override: manual upstart.tty2.override: manual upstart.tty3.override: manual upstart.tty4.override: manual upstart.tty5.override: manual upstart.tty6.override: manual upstart.ureadahead-other.override: manual upstart.ureadahead.override: manual To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc-android-config/+bug/1377869/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1377869] Re: Set a positive value to oom_score_adj for session processes
** Branch linked: lp:~ogra/ubuntu-touch-session/fix-oom-score-1377869 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc-android-config in Ubuntu. https://bugs.launchpad.net/bugs/1377869 Title: Set a positive value to oom_score_adj for session processes Status in “lxc-android-config” package in Ubuntu: Invalid Status in “ubuntu-touch-session” package in Ubuntu: Confirmed Status in “lxc-android-config” package in Ubuntu RTM: Invalid Status in “ubuntu-touch-session” package in Ubuntu RTM: Confirmed Bug description: Reference: bug 1376165 In /etc/init/lightdm.override the oom score adjustment is set to -10. But system processes have an adjustment of 0 which means system processes will be preferred to session process in out of memory conditions. The score for session processes should be much higher. I tried the following test case: - Take a picture with camera - Copy it 100 times to simulate several shots with the camera. - Then go to the Photo scope - tap on My Pictures With the current setting oom killer selects system dbus or powerd which requires a hard reboot of the device. I tried 300 (this is an example to have a significant difference with current setting) and OOM killer selects unity8-dash (which used 44% of the memory) and the system recovered without a reboot. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: lxc-android-config 0.207 [origin: Ubuntu RTM] Uname: Linux 3.4.67 armv7l ApportVersion: 2.14.7-0ubuntu1 Architecture: armhf Date: Mon Oct 6 11:41:24 2014 InstallationDate: Installed on 2014-09-29 (7 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20140929-030205) PackageArchitecture: all SourcePackage: lxc-android-config UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.init.device.hacks.conf: [modified] mtime.conffile..etc.init.device.hacks.conf: 2014-09-25T15:57:00 upstart.alsa-restore.override: manual upstart.alsa-store.override: manual upstart.boot-hooks: Error: [Errno 21] Is a directory: '/etc/init/boot-hooks' upstart.cups.override: # cups - CUPS Printing spooler and server # socket activation overrides for touch start on socket PROTO=inet PORT=631 ADDR=127.0.0.1 exec /usr/sbin/cupsd -f -x 30 upstart.lxc-net.override: manual upstart.plymouth-upstart-bridge.override: manual upstart.setvtrgb.override: manual upstart.ssh.override: manual exec /usr/sbin/sshd -D -o PasswordAuthentication=no upstart.tty1.override: manual upstart.tty2.override: manual upstart.tty3.override: manual upstart.tty4.override: manual upstart.tty5.override: manual upstart.tty6.override: manual upstart.ureadahead-other.override: manual upstart.ureadahead.override: manual To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc-android-config/+bug/1377869/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1377427] Re: white 1 pixel line on left edge of the screen since RTM image 81
i am pretty sure we have another bug like this from months ago, i have filed a new one because i havent seen it in months (and i cant reproduce it at all now) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1377427 Title: white 1 pixel line on left edge of the screen since RTM image 81 Status in Mir: Incomplete Status in “mir” package in Ubuntu: Incomplete Status in “unity8” package in Ubuntu: New Bug description: with image 81 my krillin shows a white 1px line on the left edge of the screen, specifically visible when switching apps or sliding the launcher in. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1377427/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1377869] Re: Set a positive value to oom_score_adj for session processes
http://paste.ubuntu.com/8505997/ for reference -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc-android-config in Ubuntu. https://bugs.launchpad.net/bugs/1377869 Title: Set a positive value to oom_score_adj for session processes Status in “lxc-android-config” package in Ubuntu: Invalid Status in “ubuntu-touch-session” package in Ubuntu: Confirmed Status in “lxc-android-config” package in Ubuntu RTM: Invalid Status in “ubuntu-touch-session” package in Ubuntu RTM: Confirmed Bug description: Reference: bug 1376165 In /etc/init/lightdm.override the oom score adjustment is set to -10. But system processes have an adjustment of 0 which means system processes will be preferred to session process in out of memory conditions. The score for session processes should be much higher. I tried the following test case: - Take a picture with camera - Copy it 100 times to simulate several shots with the camera. - Then go to the Photo scope - tap on My Pictures With the current setting oom killer selects system dbus or powerd which requires a hard reboot of the device. I tried 300 (this is an example to have a significant difference with current setting) and OOM killer selects unity8-dash (which used 44% of the memory) and the system recovered without a reboot. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: lxc-android-config 0.207 [origin: Ubuntu RTM] Uname: Linux 3.4.67 armv7l ApportVersion: 2.14.7-0ubuntu1 Architecture: armhf Date: Mon Oct 6 11:41:24 2014 InstallationDate: Installed on 2014-09-29 (7 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20140929-030205) PackageArchitecture: all SourcePackage: lxc-android-config UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.init.device.hacks.conf: [modified] mtime.conffile..etc.init.device.hacks.conf: 2014-09-25T15:57:00 upstart.alsa-restore.override: manual upstart.alsa-store.override: manual upstart.boot-hooks: Error: [Errno 21] Is a directory: '/etc/init/boot-hooks' upstart.cups.override: # cups - CUPS Printing spooler and server # socket activation overrides for touch start on socket PROTO=inet PORT=631 ADDR=127.0.0.1 exec /usr/sbin/cupsd -f -x 30 upstart.lxc-net.override: manual upstart.plymouth-upstart-bridge.override: manual upstart.setvtrgb.override: manual upstart.ssh.override: manual exec /usr/sbin/sshd -D -o PasswordAuthentication=no upstart.tty1.override: manual upstart.tty2.override: manual upstart.tty3.override: manual upstart.tty4.override: manual upstart.tty5.override: manual upstart.tty6.override: manual upstart.ureadahead-other.override: manual upstart.ureadahead.override: manual To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc-android-config/+bug/1377869/+subscriptions -- Mailing list: https://launchpad.net/~touch-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] [NEW] unity8-dash should be excluded from app lifecycle management
Public bug reported: 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: ... 11 7960oxide-renderer 11 7963oxide-renderer 11 7988oxide-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. ** Affects: qtmir (Ubuntu) Importance: Undecided Status: New ** Affects: unity8 (Ubuntu) Importance: High Status: Triaged ** Also affects: qtmir (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1379296 Title: unity8-dash should be excluded from app lifecycle management Status in “qtmir” package in Ubuntu: New Status in “unity8” package in Ubuntu: Triaged Bug description: 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 1388089] [NEW] [webapp-container] apps are not handled by lifecycle management properly
Public bug reported: in image 137, if you open a gazillion of apps and have webapps among them, the webapp screenshots never turn blurry when the OOM score is reached on high memory pressure ... once you switch to such a webapp, the whole content window turns white (sometimes the app header stays around, sometimes the whole app window is white). seemingly the renderer is lifecycle managed and gets properly OOM killed on high memory pressure , but the frontend of the webapp does not. ** Affects: qtmir (Ubuntu) Importance: Undecided Status: New ** Affects: webbrowser-app (Ubuntu) Importance: Undecided Status: New ** Affects: qtmir (Ubuntu RTM) Importance: Undecided Status: New ** Affects: webbrowser-app (Ubuntu RTM) Importance: Undecided Status: New ** Description changed: in image 137, if you open a gazillion of apps and have webapps among - them, the webapp screenshot never turn blurry when the OOM score is + them, the webapp screenshots never turn blurry when the OOM score is reached on high memory pressure ... once you switch to such a webapp, - the whole content window turns white. + the whole content window turns white (sometimes the app header stays + around, sometimes the whole app window is white). seemingly the renderer is lifecycle managed and gets properly OOM killed on high memory pressure , but the frontend of the webapp does not. ** Also affects: qtmir (Ubuntu) Importance: Undecided Status: New ** Also affects: qtmir (Ubuntu RTM) Importance: Undecided Status: New ** Also affects: webbrowser-app (Ubuntu RTM) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu. https://bugs.launchpad.net/bugs/1388089 Title: [webapp-container] apps are not handled by lifecycle management properly Status in “qtmir” package in Ubuntu: New Status in “webbrowser-app” package in Ubuntu: New Status in “qtmir” package in Ubuntu RTM: New Status in “webbrowser-app” package in Ubuntu RTM: New Bug description: in image 137, if you open a gazillion of apps and have webapps among them, the webapp screenshots never turn blurry when the OOM score is reached on high memory pressure ... once you switch to such a webapp, the whole content window turns white (sometimes the app header stays around, sometimes the whole app window is white). seemingly the renderer is lifecycle managed and gets properly OOM killed on high memory pressure , but the frontend of the webapp does not. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtmir/+bug/1388089/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1388235] Re: Icon turns red at 30%
** Changed in: ubuntu-ux Status: New = Confirmed ** Changed in: indicator-power (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-power in Ubuntu. https://bugs.launchpad.net/bugs/1388235 Title: Battery icon turns red at 30% Status in Ubuntu UX bugs: Confirmed Status in “indicator-power” package in Ubuntu: Confirmed Bug description: This seems a bit pessimistic since the phone still has a great deal of capacity and time left, perhaps 15 or 20% is a better threshold To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1388235/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1387959] Re: unity8 crash in image krillin rtm 139
for me it happened out of the blue without any incoming calls yesterday ... (with a few webapps and dekko open) -- 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/1387959 Title: unity8 crash in image krillin rtm 139 Status in “unity8” package in Ubuntu: New Bug description: Earlier today, a few QA folks tested image krillin rtm 138 plus silo 13, and found that it fixed the unity8 crash from bug 1382595. Silo 13 plus silo 10 landed in image 139. Now, in image 139, unity8 is crashy again. Olli mentioned getting two crashes within a few minutes, and I got a unity8 crash while trying to accept an incoming call. I'm not sure if it's the same crash as before, or if it's a new one. Attached is the crash dump I got just after hitting 'accept' for an incoming call. I tried to pre-process it in apport-cli, but it failed with Sorry, the program unity8 closed unexpectedly // Your computer does not have enough free memory to automatically analyze the problem and send a report to the developers. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1387959/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1388569] [NEW] popup dialog content shifted to the left in image 140
Public bug reported: on krilling image 140 all content of popup dialogs is shifted to the left instead of being properly centerd (i think this has started far before 140 though, but can not nail it to one specific image) this is easily reproducable by bringing up the shutdown/reboot dialog ** Affects: ubuntu-ui-toolkit (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1388569 Title: popup dialog content shifted to the left in image 140 Status in “ubuntu-ui-toolkit” package in Ubuntu: New Bug description: on krilling image 140 all content of popup dialogs is shifted to the left instead of being properly centerd (i think this has started far before 140 though, but can not nail it to one specific image) this is easily reproducable by bringing up the shutdown/reboot dialog To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1388569/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1388359] Re: User metrics can no longer be changed by double tap
same here -- 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/1388359 Title: User metrics can no longer be changed by double tap Status in “unity8” package in Ubuntu: Confirmed Bug description: Krillin #139 proposed On the welcome screen I only see No text messages sent today. In previous images double tapping the welcome screen would cycle through music played, phone calls made/received etc. I don't seem to be able to get it to move on. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1388359/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1388359] Re: User metrics can no longer be changed by double tap
http://paste.ubuntu.com/8802213/ is what gets printed into ~/.cache/upstart/unity8.log if i double-tap on the usermetrics UI in the greeter -- 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/1388359 Title: User metrics can no longer be changed by double tap Status in “unity8” package in Ubuntu: In Progress Bug description: Krillin #139 proposed On the welcome screen I only see No text messages sent today. In previous images double tapping the welcome screen would cycle through music played, phone calls made/received etc. I don't seem to be able to get it to move on. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1388359/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1389718] Re: krillin 142 frozen on welcome screen when unlocking
i see this since the 130's from time to time but have not reported it yet due to insufficient data ** Changed in: unity8 (Ubuntu) Status: New = Confirmed -- 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/1389718 Title: krillin 142 frozen on welcome screen when unlocking Status in “unity8” package in Ubuntu: Confirmed Bug description: On a couple of occasions now my krillin has frozen at the partly drawn welcome screen when I press the power button to wake it. The display doesn't update and touching the screen does nothing. Pressing the power button again blanks the screen and wakes again on next press, but the phone is no longer usable. No crash files are made. ProblemType: Bug DistroRelease: Ubuntu RTM 14.09 Package: unity8 8.01+15.04.20141030~rtm-0ubuntu1 Uname: Linux 3.4.67 armv7l ApportVersion: 2.14.7-0ubuntu8 Architecture: armhf Date: Wed Nov 5 13:49:54 2014 InstallationDate: Installed on 2014-11-04 (1 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20141104-030206) 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/1389718/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1382559] Re: adbd does not check the screen state before allowing a connection
** Also affects: android-tools (Ubuntu RTM) Importance: Undecided Status: New ** Changed in: android-tools (Ubuntu RTM) Status: New = Confirmed ** Changed in: android-tools (Ubuntu RTM) Importance: Undecided = Critical ** Changed in: android-tools (Ubuntu RTM) Assignee: (unassigned) = Oliver Grawert (ogra) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to android-tools in Ubuntu. https://bugs.launchpad.net/bugs/1382559 Title: adbd does not check the screen state before allowing a connection Status in “android-tools” package in Ubuntu: Confirmed Status in “android-tools” package in Ubuntu RTM: Confirmed Bug description: according to https://wiki.ubuntu.com/SecurityAndPrivacySettings/ProtectingUserData adbd should only allow a connection attempt to succeed when teh screen is unlocked. adbd currently does not do this and needs to be fixed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/android-tools/+bug/1382559/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1387214] Re: [TOPBLOCKER] file corruption on touch images in rw portions of the filesystem
your dconf issues are caused by illegal use of dconf by an app (apps should not be able to use dconf according to the security policy as i understand it, to avoid exactly this), please file a fresh bug for this. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools-ubuntu- touch in Ubuntu. https://bugs.launchpad.net/bugs/1387214 Title: [TOPBLOCKER] file corruption on touch images in rw portions of the filesystem Status in “android” package in Ubuntu: Triaged Status in “initramfs-tools-ubuntu-touch” package in Ubuntu: Triaged Bug description: Symptoms are that cache files in /var/cache/apparmor and profiles in /var/lib/apparmor/profiles are sometimes corrupted after a reboot. We've already fixed several bugs in the apparmor and click-apparmor and made both more robust in the face of corruption and we've reduced the impact when there is a corrupted profile, but we've still not found the cause of the corruption. This corruption can still affect real-world devices: if a profile in /var/lib/apparmor/profiles is corrupted and the cache file is out of date, then the profile won't compile and that app/scope won't start. Workaround: remove the affected profile and then run 'sudo aa- clickhook'. This obviously is not viable on an end-user device. The investigation is ongoing and this may not be a problem with the kernel at all, so this bug may be retargeted to another project. The security team and the kernel team have discussed this a lot and Colin King is currently looking at this. This bug is just so it can be tracked. Here is an excerpt from my latest email to Colin: I believe I have conclusively ruled out apparmor_parser and aa- clickhook by creating a new 'home/bug/test-with-true.sh'. Here is the test output: http://paste.ubuntu.com/8648109/ Specifically, home/bug/test-with-true.sh changes the interesting parts of the algorithm to: 1. wait for unity8 to start (this ensures the apparmor upstart job is finished) 2. restore apparmor_parser and aa-clickhook, if needed 3. if /home/bug/profiles... exists, perform a diff -Naur /home/bug/profiles... /var/lib/apparmor/profiles and fail if differences (note, apparmor_parser and aa-clickhook were /bin/true during boot so they could not have changed /var/lib/apparmor/profiles) 4. verify the profiles, exit with error if they do not 5. alternately upgrade/downgrade the packages 6. verify the profiles, exit with error if they do not 7. copy the known good profiles in the previous step to /home/bug/profiles... 8. have apparmor_parser and aa-clickhook point to /bin/true 9. reboot 10. go to step 1 In the paste you'll notice that in step 6 the profiles were successfully created by the installation of the packages, then verified, then copied aside, then apparmor_parser and aa-clickhook diverted, then rebooted, only to have the profiles in /var/lib/apparmor/profiles be different than what was copied aside. It would be nice to verify on your device as well (I reproduced several times here) and verify the reproducer algorithm. I think this suggests this is a kernel issue and not userspace. IMPORTANT: you will want to update the reproducer and refollow all of these steps (ie, I updated the scripts, the debs, the sudoers file, etc): $ wget http://people.canonical.com/~jamie/cking/aa-corruption.tar.gz $ tar -zxvf ./aa-corruption.tar.gz ... $ adb push ./aa-corruption.tar.gz /tmp $ adb shell phablet@ubuntu-phablet:~$ cd /tmp phablet@ubuntu-phablet:~$ tar -zxvf ./aa-corruption.tar.gz phablet@ubuntu-phablet:~$ sudo mount -o remount,rw / phablet@ubuntu-phablet:~$ sudo cp ./aa-corruption/etc/sudoers.d/phablet /etc/sudoers.d/ phablet@ubuntu-phablet:~$ sudo mount -o remount,ro / phablet@ubuntu-phablet:~$ sudo cp -a ./aa-corruption/home/bug /home phablet@ubuntu-phablet:~$ exit $ cd ./aa-corruption $ ./test-from-host.sh ... The old script is still in place. Simply adjust ./test-from-host.sh to have: testscript=/home/bug/test.sh #testscript=/home/bug/test-with-true.sh The kernel team has verified the above reproducer and symptoms. Related bugs: * bug 1371771 * bug 1371765 * bug 1377338 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/android/+bug/1387214/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1391149] [NEW] greeter not reacting to swipes
Public bug reported: i had this a few times over the weekend with images 150-153, suddenly the greeter does not react to right/left swipes on the wallpaper to reveal the PIN unlock dialog ... swiping in the launcher from the left makes the greeter go away and reveals the PIN unlock dialog then. ** Affects: unity8 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1391149 Title: greeter not reacting to swipes Status in “unity8” package in Ubuntu: New Bug description: i had this a few times over the weekend with images 150-153, suddenly the greeter does not react to right/left swipes on the wallpaper to reveal the PIN unlock dialog ... swiping in the launcher from the left makes the greeter go away and reveals the PIN unlock dialog then. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1391149/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1391149] Re: greeter not reacting to swipes
i am wondering if that is the same as bug #1391076 , just in a less intrusive manifestation -- 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/1391149 Title: greeter not reacting to swipes Status in “unity8” package in Ubuntu: New Bug description: i had this a few times over the weekend with images 150-153, suddenly the greeter does not react to right/left swipes on the wallpaper to reveal the PIN unlock dialog ... swiping in the launcher from the left makes the greeter go away and reveals the PIN unlock dialog then. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1391149/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1387214] Re: [TOPBLOCKER] file corruption on touch images in rw portions of the filesystem
adding an android-tools task, since adb reboot forces a hard reset without unmounting the filesystems ... adding something along: ogra_ root@ubuntu-phablet:~# echo u /proc/sysrq-trigger ogra_ root@ubuntu-phablet:~# touch /userdata/foo ogra_ touch: cannot touch ‘/userdata/foo’: Read-only file system to core/adbd/services.c in the reboot_service function (instead of the vdc call) should help here ** Also affects: android-tools (Ubuntu) Importance: Undecided Status: New ** Also affects: android-tools (Ubuntu RTM) Importance: Undecided Status: New ** Changed in: android-tools (Ubuntu) Status: New = In Progress ** Changed in: android-tools (Ubuntu RTM) Status: New = In Progress ** Changed in: android-tools (Ubuntu) Importance: Undecided = Critical ** Changed in: android-tools (Ubuntu RTM) Importance: Undecided = Critical ** Changed in: android-tools (Ubuntu) Assignee: (unassigned) = Oliver Grawert (ogra) ** Changed in: android-tools (Ubuntu RTM) Assignee: (unassigned) = Oliver Grawert (ogra) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools-ubuntu- touch in Ubuntu. https://bugs.launchpad.net/bugs/1387214 Title: [TOPBLOCKER] file corruption on touch images in rw portions of the filesystem Status in “android” package in Ubuntu: In Progress Status in “android-tools” package in Ubuntu: In Progress Status in “initramfs-tools-ubuntu-touch” package in Ubuntu: Fix Released Status in “android” package in Ubuntu RTM: New Status in “android-tools” package in Ubuntu RTM: In Progress Status in “initramfs-tools-ubuntu-touch” package in Ubuntu RTM: New Bug description: Symptoms are that cache files in /var/cache/apparmor and profiles in /var/lib/apparmor/profiles are sometimes corrupted after a reboot. We've already fixed several bugs in the apparmor and click-apparmor and made both more robust in the face of corruption and we've reduced the impact when there is a corrupted profile, but we've still not found the cause of the corruption. This corruption can still affect real-world devices: if a profile in /var/lib/apparmor/profiles is corrupted and the cache file is out of date, then the profile won't compile and that app/scope won't start. Workaround: remove the affected profile and then run 'sudo aa- clickhook'. This obviously is not viable on an end-user device. The investigation is ongoing and this may not be a problem with the kernel at all, so this bug may be retargeted to another project. The security team and the kernel team have discussed this a lot and Colin King is currently looking at this. This bug is just so it can be tracked. Here is an excerpt from my latest email to Colin: I believe I have conclusively ruled out apparmor_parser and aa- clickhook by creating a new 'home/bug/test-with-true.sh'. Here is the test output: http://paste.ubuntu.com/8648109/ Specifically, home/bug/test-with-true.sh changes the interesting parts of the algorithm to: 1. wait for unity8 to start (this ensures the apparmor upstart job is finished) 2. restore apparmor_parser and aa-clickhook, if needed 3. if /home/bug/profiles... exists, perform a diff -Naur /home/bug/profiles... /var/lib/apparmor/profiles and fail if differences (note, apparmor_parser and aa-clickhook were /bin/true during boot so they could not have changed /var/lib/apparmor/profiles) 4. verify the profiles, exit with error if they do not 5. alternately upgrade/downgrade the packages 6. verify the profiles, exit with error if they do not 7. copy the known good profiles in the previous step to /home/bug/profiles... 8. have apparmor_parser and aa-clickhook point to /bin/true 9. reboot 10. go to step 1 In the paste you'll notice that in step 6 the profiles were successfully created by the installation of the packages, then verified, then copied aside, then apparmor_parser and aa-clickhook diverted, then rebooted, only to have the profiles in /var/lib/apparmor/profiles be different than what was copied aside. It would be nice to verify on your device as well (I reproduced several times here) and verify the reproducer algorithm. I think this suggests this is a kernel issue and not userspace. IMPORTANT: you will want to update the reproducer and refollow all of these steps (ie, I updated the scripts, the debs, the sudoers file, etc): $ wget http://people.canonical.com/~jamie/cking/aa-corruption.tar.gz $ tar -zxvf ./aa-corruption.tar.gz ... $ adb push ./aa-corruption.tar.gz /tmp $ adb shell phablet@ubuntu-phablet:~$ cd /tmp phablet@ubuntu-phablet:~$ tar -zxvf ./aa-corruption.tar.gz phablet@ubuntu-phablet:~$ sudo mount -o remount,rw / phablet@ubuntu-phablet:~$ sudo cp ./aa-corruption/etc/sudoers.d/phablet /etc/sudoers.d/ phablet@ubuntu-phablet:~$ sudo mount -o remount,ro / phablet
[Touch-packages] [Bug 1393410] Re: [TOPBLOCKER] Apps with prices are not shown by default
** Tags added: lt-blocker lt-category-visible lt-prio-high -- 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/1393410 Title: [TOPBLOCKER] Apps with prices are not shown by default Status in “unity-scope-click” package in Ubuntu: In Progress Status in “unity-scope-click” package in Ubuntu RTM: In Progress Bug description: The current default in the scope is to not show apps with prices, and they are only shown after running a special script. This was done like that so the payments feature could be tested in a more controlled environment. Now it needs to be enabled so the default is to show apps with prices to everybody. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-scope-click/+bug/1393410/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1393515] [NEW] browser allows browsing the phone filesystem
Public bug reported: using a URL like: file:/// gets you to the root of the phone filesystem ... i assume this is not actually desired since we even block the filemanager app to go higher up then $HOME without requiring a password. ** Affects: webbrowser-app (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu. https://bugs.launchpad.net/bugs/1393515 Title: browser allows browsing the phone filesystem Status in “webbrowser-app” package in Ubuntu: New Bug description: using a URL like: file:/// gets you to the root of the phone filesystem ... i assume this is not actually desired since we even block the filemanager app to go higher up then $HOME without requiring a password. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1393515/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1387214] Re: [TOPBLOCKER] file corruption on touch images in rw portions of the filesystem
after researching the adbd part for two days it seems that adbd already tries to call echo u /proc/sysrq-trigger when adb reboot is issued but at this point we already dropped privs to the phablet user ... /proc/sysrq-trigger is owned by root:system and writable for both, the only solution i see (beyond making /proc/sysrq-trigger owned by phablet or its group which would rip a giant security hole) is to make adbd start with setguid system and have it drop this group membership right before any adb shell call (so that the logged in phablet user is not member of system by default) i'm trying to implement this but am constantly running into smaller issues. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools-ubuntu- touch in Ubuntu. https://bugs.launchpad.net/bugs/1387214 Title: [TOPBLOCKER] file corruption on touch images in rw portions of the filesystem Status in “android” package in Ubuntu: Fix Released Status in “android-tools” package in Ubuntu: In Progress Status in “initramfs-tools-ubuntu-touch” package in Ubuntu: Fix Released Status in “linux-mako” package in Ubuntu: New Status in “android” package in Ubuntu RTM: In Progress Status in “android-tools” package in Ubuntu RTM: In Progress Status in “initramfs-tools-ubuntu-touch” package in Ubuntu RTM: In Progress Status in “linux-mako” package in Ubuntu RTM: New Bug description: Symptoms are that cache files in /var/cache/apparmor and profiles in /var/lib/apparmor/profiles are sometimes corrupted after a reboot. We've already fixed several bugs in the apparmor and click-apparmor and made both more robust in the face of corruption and we've reduced the impact when there is a corrupted profile, but we've still not found the cause of the corruption. This corruption can still affect real-world devices: if a profile in /var/lib/apparmor/profiles is corrupted and the cache file is out of date, then the profile won't compile and that app/scope won't start. Workaround: remove the affected profile and then run 'sudo aa- clickhook'. This obviously is not viable on an end-user device. The investigation is ongoing and this may not be a problem with the kernel at all, so this bug may be retargeted to another project. The security team and the kernel team have discussed this a lot and Colin King is currently looking at this. This bug is just so it can be tracked. Here is an excerpt from my latest email to Colin: I believe I have conclusively ruled out apparmor_parser and aa- clickhook by creating a new 'home/bug/test-with-true.sh'. Here is the test output: http://paste.ubuntu.com/8648109/ Specifically, home/bug/test-with-true.sh changes the interesting parts of the algorithm to: 1. wait for unity8 to start (this ensures the apparmor upstart job is finished) 2. restore apparmor_parser and aa-clickhook, if needed 3. if /home/bug/profiles... exists, perform a diff -Naur /home/bug/profiles... /var/lib/apparmor/profiles and fail if differences (note, apparmor_parser and aa-clickhook were /bin/true during boot so they could not have changed /var/lib/apparmor/profiles) 4. verify the profiles, exit with error if they do not 5. alternately upgrade/downgrade the packages 6. verify the profiles, exit with error if they do not 7. copy the known good profiles in the previous step to /home/bug/profiles... 8. have apparmor_parser and aa-clickhook point to /bin/true 9. reboot 10. go to step 1 In the paste you'll notice that in step 6 the profiles were successfully created by the installation of the packages, then verified, then copied aside, then apparmor_parser and aa-clickhook diverted, then rebooted, only to have the profiles in /var/lib/apparmor/profiles be different than what was copied aside. It would be nice to verify on your device as well (I reproduced several times here) and verify the reproducer algorithm. I think this suggests this is a kernel issue and not userspace. IMPORTANT: you will want to update the reproducer and refollow all of these steps (ie, I updated the scripts, the debs, the sudoers file, etc): $ wget http://people.canonical.com/~jamie/cking/aa-corruption.tar.gz $ tar -zxvf ./aa-corruption.tar.gz ... $ adb push ./aa-corruption.tar.gz /tmp $ adb shell phablet@ubuntu-phablet:~$ cd /tmp phablet@ubuntu-phablet:~$ tar -zxvf ./aa-corruption.tar.gz phablet@ubuntu-phablet:~$ sudo mount -o remount,rw / phablet@ubuntu-phablet:~$ sudo cp ./aa-corruption/etc/sudoers.d/phablet /etc/sudoers.d/ phablet@ubuntu-phablet:~$ sudo mount -o remount,ro / phablet@ubuntu-phablet:~$ sudo cp -a ./aa-corruption/home/bug /home phablet@ubuntu-phablet:~$ exit $ cd ./aa-corruption $ ./test-from-host.sh ... The old script is still in place. Simply adjust ./test-from-host.sh to have: testscript=/home/bug/test.sh
[Touch-packages] [Bug 1357321] Re: QNetworkAccessManager doesn't support roaming on Ubuntu
it is tagged ota-1, so it will land, just not in one of the next two promoted images, which just delays it by two weeks -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1357321 Title: QNetworkAccessManager doesn't support roaming on Ubuntu Status in Platform API: Invalid Status in The Savilerow project: New Status in “network-manager” package in Ubuntu: Invalid Status in “ofono” package in Ubuntu: Invalid Status in “qtbase-opensource-src” package in Ubuntu: In Progress Status in “qtbase-opensource-src” package in Ubuntu RTM: New Bug description: scope images load fine in wifi, but not on hsdpa even when there is good connectivity and browsing works well. Results are return, but images do not load. To manage notifications about this bug go to: https://bugs.launchpad.net/platform-api/+bug/1357321/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1394155] Re: Deadlock / crash of the dash possible through Today scope
** Changed in: unity-scopes-shell (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-scopes-shell in Ubuntu. https://bugs.launchpad.net/bugs/1394155 Title: Deadlock / crash of the dash possible through Today scope Status in “unity-scopes-shell” package in Ubuntu: Confirmed Bug description: On krillin: 1) Go to the Today scope 2) Scroll to the bottom 3) Tap Tell me more... 4) Scroll to the bottom again 5) Tap Finished Hard lock / sometimes crash. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-scopes-shell/+bug/1394155/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1391560] Re: [themes] [design] Develop a strategy to keep fonts readable wherever we allow the user setting his own background image
in case someone needs an example http://people.canonical.com/~ogra /greeter-wallpaper.png (the screenshot is even more readable than the real thing, the date below the time is completely unreadable on the display with such a noisy wallpaper) -- 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/1391560 Title: [themes] [design] Develop a strategy to keep fonts readable wherever we allow the user setting his own background image Status in Ubuntu UX bugs: New Status in “unity8” package in Ubuntu: Incomplete Bug description: As discussed with Olga, we need to develop a strategy on keeping the fonts readable when we allow the user to change the background. This is currently the case on the Greeter and the Lockscreens. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1391560/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1394380] Re: QML cache not regenerated correctly on image update
below upstart job for lxc-android-config (untested yet) that should be shipped as /etc/init/boot-hooks/wipe-qml-cache.conf: # This allows wiping of the complete QML app cache on OTA upgrades start on boot-hooks WHEN=new-version pre-start script rm -rf /home/*/.cache/QML/Apps/* end script ** Also affects: lxc-android-config (Ubuntu) Importance: Undecided Status: New ** Also affects: lxc-android-config (Ubuntu RTM) Importance: Undecided Status: New ** Changed in: lxc-android-config (Ubuntu) Importance: Undecided = Critical ** Changed in: lxc-android-config (Ubuntu RTM) Importance: Undecided = Critical ** Changed in: lxc-android-config (Ubuntu) Assignee: (unassigned) = Oliver Grawert (ogra) ** Changed in: lxc-android-config (Ubuntu RTM) Assignee: (unassigned) = Oliver Grawert (ogra) ** Changed in: lxc-android-config (Ubuntu) Status: New = Confirmed ** Changed in: lxc-android-config (Ubuntu RTM) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc-android-config in Ubuntu. https://bugs.launchpad.net/bugs/1394380 Title: QML cache not regenerated correctly on image update Status in “android” package in Ubuntu: Invalid Status in “lxc-android-config” package in Ubuntu: Confirmed Status in “lxc-android-config” package in Ubuntu RTM: Confirmed Bug description: image rtm-proposed 166 Multiple problems here, due to the fact that oxide was updated (a new release) and webrowser-app was updated 1) webbrowser-app cache was not updated on the image upgrade in .cache/QML/Apps/webbrowser-app and desktop versions of web pages are displayed until the cache is destroyed or regenerated. Try cnn.com or nytimes.com 2) no webbapps cache is regenerated, so launching of the webapps displays wrong pages (.cache/QML/Apps/*webapps*) due to stale cache. You can try Google Maps for an example. Deleting the cache makes them work again properly. Expected Results: - after image upgrade, either all of the apps should be regenerated smartly, or we should blow away all of the caches to prevent an issue when a library (like oxide) is upgraded and causes an invalid cache. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/android/+bug/1394380/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1394380] Re: QML cache not regenerated correctly on image update
teh above should be sufficient as a quick fix to wipe the cache on every OTA ** Changed in: android (Ubuntu) Status: New = Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc-android-config in Ubuntu. https://bugs.launchpad.net/bugs/1394380 Title: QML cache not regenerated correctly on image update Status in “android” package in Ubuntu: Invalid Status in “lxc-android-config” package in Ubuntu: Confirmed Status in “lxc-android-config” package in Ubuntu RTM: Confirmed Bug description: image rtm-proposed 166 Multiple problems here, due to the fact that oxide was updated (a new release) and webrowser-app was updated 1) webbrowser-app cache was not updated on the image upgrade in .cache/QML/Apps/webbrowser-app and desktop versions of web pages are displayed until the cache is destroyed or regenerated. Try cnn.com or nytimes.com 2) no webbapps cache is regenerated, so launching of the webapps displays wrong pages (.cache/QML/Apps/*webapps*) due to stale cache. You can try Google Maps for an example. Deleting the cache makes them work again properly. Expected Results: - after image upgrade, either all of the apps should be regenerated smartly, or we should blow away all of the caches to prevent an issue when a library (like oxide) is upgraded and causes an invalid cache. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/android/+bug/1394380/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1394380] Re: QML cache not regenerated correctly on image update
that might be, but what if we change the format of teh cache content, what if we get another category of apps that behave the same... i belive invalidating the cache after system upgrades is a good thing to prevent us from any such possibilities -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc-android-config in Ubuntu. https://bugs.launchpad.net/bugs/1394380 Title: QML cache not regenerated correctly on image update Status in “android” package in Ubuntu: Invalid Status in “lxc-android-config” package in Ubuntu: Confirmed Status in “lxc-android-config” package in Ubuntu RTM: Confirmed Bug description: image rtm-proposed 166 Multiple problems here, due to the fact that oxide was updated (a new release) and webrowser-app was updated 1) webbrowser-app cache was not updated on the image upgrade in .cache/QML/Apps/webbrowser-app and desktop versions of web pages are displayed until the cache is destroyed or regenerated. Try cnn.com or nytimes.com 2) no webbapps cache is regenerated, so launching of the webapps displays wrong pages (.cache/QML/Apps/*webapps*) due to stale cache. You can try Google Maps for an example. Deleting the cache makes them work again properly. Expected Results: - after image upgrade, either all of the apps should be regenerated smartly, or we should blow away all of the caches to prevent an issue when a library (like oxide) is upgraded and causes an invalid cache. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/android/+bug/1394380/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1394380] Re: [TOPBLOCKER] QML cache not regenerated correctly on image update
added top blocker status since it is considered to go in before the golden milestone ** Summary changed: - QML cache not regenerated correctly on image update + [TOPBLOCKER] QML cache not regenerated correctly on image update -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc-android-config in Ubuntu. https://bugs.launchpad.net/bugs/1394380 Title: [TOPBLOCKER] QML cache not regenerated correctly on image update Status in “android” package in Ubuntu: Invalid Status in “lxc-android-config” package in Ubuntu: Confirmed Status in “lxc-android-config” package in Ubuntu RTM: Confirmed Bug description: image rtm-proposed 166 Multiple problems here, due to the fact that oxide was updated (a new release) and webrowser-app was updated 1) webbrowser-app cache was not updated on the image upgrade in .cache/QML/Apps/webbrowser-app and desktop versions of web pages are displayed until the cache is destroyed or regenerated. Try cnn.com or nytimes.com 2) no webbapps cache is regenerated, so launching of the webapps displays wrong pages (.cache/QML/Apps/*webapps*) due to stale cache. You can try Google Maps for an example. Deleting the cache makes them work again properly. Expected Results: - after image upgrade, either all of the apps should be regenerated smartly, or we should blow away all of the caches to prevent an issue when a library (like oxide) is upgraded and causes an invalid cache. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/android/+bug/1394380/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1323711] Re: music scope and music-app only play songs owned by user 'phablet'
this will be fixed when we default to running adbd as phablet user once the final developer mode changes land. ** Also affects: android-tools (Ubuntu) Importance: Undecided Status: New ** Changed in: android-tools (Ubuntu) Assignee: (unassigned) = Oliver Grawert (ogra) ** Changed in: media-hub (Ubuntu) Importance: Undecided = Wishlist ** Changed in: media-hub (Ubuntu) Assignee: Oliver Grawert (ogra) = (unassigned) ** Changed in: android-tools (Ubuntu) Importance: Undecided = High ** Changed in: android-tools (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to android-tools in Ubuntu. https://bugs.launchpad.net/bugs/1323711 Title: music scope and music-app only play songs owned by user 'phablet' Status in “android-tools” package in Ubuntu: Confirmed Status in “media-hub” package in Ubuntu: New Bug description: Songs not owned by user 'phablet' are not played in Music App and Music scope preview mode, even if the file is readable by this user. TEST CASE: 1. Copy a song (mp3 or ogg) to a device to /home/phablet/Music $ adb push file /home/phablet/Music/ 2. Verify that the file is not owned by phablet but that phablet read access (mode 0666) $ adb shell ls -l /home/phablet/Music/ -rw-rw-rw- 1 root root 25304292 May 26 17:18 test_file 3. Play this song in music scope or music app 4. Verify that the song plays 5. Change ownership of the file to user 'phablet' $ adb shell chown phablet /home/phablet/Music/file EXPECTED RESULT Music app or scope play the song ACTUAL RESULT Music app or scope doesn't play the song and there is no error message. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: media-hub 0.0.2+14.10.20140521-0ubuntu1 Uname: Linux 3.4.0-5-mako armv7l ApportVersion: 2.14.2-0ubuntu4 Architecture: armhf Date: Tue May 27 16:53:47 2014 InstallationDate: Installed on 2014-05-27 (0 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20140527) SourcePackage: media-hub UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/android-tools/+bug/1323711/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1360162] [NEW] system-image should not allow upgrading when power is to low
Public bug reported: currently you can even upgrade your phone if the power level is extremely low ... with the potential the the phone crashes during unpacking in recovery ad you end up with a corrupt image. system-image needs to check the battery level before allowing to reboot and install the image. if the level is below a safe threshold it should ask the user to apply power before allowing to reboot and install. ** Affects: system-image (Ubuntu) Importance: Undecided Status: New -- 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/1360162 Title: system-image should not allow upgrading when power is to low Status in “system-image” package in Ubuntu: New Bug description: currently you can even upgrade your phone if the power level is extremely low ... with the potential the the phone crashes during unpacking in recovery ad you end up with a corrupt image. system-image needs to check the battery level before allowing to reboot and install the image. if the level is below a safe threshold it should ask the user to apply power before allowing to reboot and install. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/system-image/+bug/1360162/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1296431] Re: Phone doesn't alert user of critical power situations
i just filed bug 1360162 which is a far cousin of this one -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-power in Ubuntu. https://bugs.launchpad.net/bugs/1296431 Title: Phone doesn't alert user of critical power situations Status in “indicator-power” package in Ubuntu: In Progress Bug description: The phone doesn't currently alert the user when the battery is critical. This leads to power loss at times and the user doesn't know it's about to happen or had happened. e.g. during a call, or while listening to music. Also if the phone is sat on the desk unplugged from power connection. https://wiki.ubuntu.com/Power#Warnings: When the device’s battery/batteries are discharging and reach — or begin discharging and already have — 1 hour or less remaining (PC) or 20% or less remaining (phone/tablet), a notification bubble should appear ... When the device’s battery/batteries are discharging and reach — or begin discharging and already have — 30 minutes or less remaining (PC) or 10% or less remaining (phone/tablet), an alert should appear... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-power/+bug/1296431/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1307687] Re: swiping upwards in the updater dialog while it downloads an image makes the UI vanish
no, long gone ... ** Changed in: ubuntu-system-settings (Ubuntu) Status: Incomplete = Invalid ** Changed in: ubuntu-download-manager (Ubuntu) Status: Confirmed = Invalid -- 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/1307687 Title: swiping upwards in the updater dialog while it downloads an image makes the UI vanish Status in “ubuntu-download-manager” package in Ubuntu: Invalid Status in “ubuntu-system-settings” package in Ubuntu: Invalid Bug description: I noticed a few times already that while the download manager downloads an OTA image and you swipe upwards in the empty space underneath the progress bar (to keep the screen on), at some point the UI completely vanishes, leaving only the page header around. The upgrade seems to still continue and at some point i get the reboot dialog. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-download-manager/+bug/1307687/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1363129] Re: No more syslog update after the 21st of August
i think rsyslogd can only write if teh file/dir is owned by teh syslog user, it seems like the GID for syslog changed under you -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsyslog in Ubuntu. https://bugs.launchpad.net/bugs/1363129 Title: No more syslog update after the 21st of August Status in “rsyslog” package in Ubuntu: Confirmed Bug description: Since the 21st of August, my phone doesn't have any other syslog update. I noticed the files had started being owned by 'usermetrics'. Some details: $ ls /var/log/syslog -rw-r- 1 root adm 9076723 Aug 21 11:56 /var/log/syslog $ ls /var drwxrwxr-x 12 root usermetrics 4096 Aug 29 07:49 log $ df /var/log Filesystem 1K-blocksUsed Available Use% Mounted on /dev/mmcblk0p23 5942324 2263384 3376708 41% /var/log To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1363129/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1363129] Re: No more syslog update after the 21st of August
can you check if there is anything more in the files in /var/lib/extrausers than the phablet user/group ? (or even attach the files) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsyslog in Ubuntu. https://bugs.launchpad.net/bugs/1363129 Title: No more syslog update after the 21st of August Status in “rsyslog” package in Ubuntu: Confirmed Bug description: Since the 21st of August, my phone doesn't have any other syslog update. I noticed the files had started being owned by 'usermetrics'. Some details: $ ls /var/log/syslog -rw-r- 1 root adm 9076723 Aug 21 11:56 /var/log/syslog $ ls /var drwxrwxr-x 12 root usermetrics 4096 Aug 29 07:49 log $ df /var/log Filesystem 1K-blocksUsed Available Use% Mounted on /dev/mmcblk0p23 5942324 2263384 3376708 41% /var/log To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1363129/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1364412] Re: unity8 freezes after pocket touches
*** This bug is a duplicate of bug 1358257 *** https://bugs.launchpad.net/bugs/1358257 ** This bug has been marked a duplicate of private bug 1358257 -- 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/1364412 Title: unity8 freezes after pocket touches Status in “unity8” package in Ubuntu: New Bug description: I have a mako running the rtm branch and I use a PIN. If I lock the phone and put it in my pocket, sometimes I can hear my phone pocket dialing. If I take it out of my pocket, I can see the emergency dialer is open. Sometimes I can interact with the dialer and make it go away. Other times, the phone is locked up and doesn't respond to touch events. When it is unresponsive, if I long press the power button, I get the dialog to restart or cancel but most of the time it doesn't respond to events. When in this state, the only recourse is to reboot the phone. I think a number of problem are here: 1. I know that before we could set a PIN, I would sometimes see touch events pass through the 'swipe to unlock' screen. This could be a contributing factor 2. swipe isn't taking into account pocket detection. The swipe happens too easily and then there is the pin/passphrase dialog with the 'Emergency Call' link to open the dialer available to be touched 3. at some point enough happens that the phone is no longer responsive to any input (other than the power button) Within the course of one hour over the weekend, I had to restart my phone 4 times. I am going to add the rtm14 tag and mark as Critical because if this is not fixed, it will be a cause of returns. (FYI, f I leave the phone outside of my pocket on the desk, I don't see lockups very often). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1364412/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1364872] Re: The gdbserver is not available on the device image
** Also affects: ubuntu-touch-meta (Ubuntu) Importance: Undecided Status: New ** Changed in: ubuntu-meta (Ubuntu) Status: New = Invalid ** Changed in: ubuntu-touch-meta (Ubuntu) Importance: Undecided = Medium ** Changed in: ubuntu-touch-meta (Ubuntu) Assignee: (unassigned) = Oliver Grawert (ogra) ** Changed in: ubuntu-touch-meta (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-touch-meta in Ubuntu. https://bugs.launchpad.net/bugs/1364872 Title: The gdbserver is not available on the device image Status in “ubuntu-touch-meta” package in Ubuntu: Confirmed Bug description: To enable debugging of applications with C++ code the target device must have gdbserver package installed. Right now for that the app developers need to turn the device writable and manually install the gdbserver package. It would be much more convinient and secure to keep the device readonly and have the gdbserver pre-installed on the device. The disk space should not be a concern as all installed files from the package use up 215KB (binary - 190KB + doc - 20KB + manpage - 5KB) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-touch-meta/+bug/1364872/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1365911] Re: MTP not working on boot if passcode not set
but i need to verify first that ubuntu-device-flash actually sets teh proper default when --developer-mode is used as option ** Changed in: lxc-android-config (Ubuntu) Status: Confirmed = In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc-android-config in Ubuntu. https://bugs.launchpad.net/bugs/1365911 Title: MTP not working on boot if passcode not set Status in “dbus-property-service” package in Ubuntu: Invalid Status in “lxc-android-config” package in Ubuntu: In Progress Bug description: mako devel-proposed#223 MTP doesn't work for me on boot if I don't have a passcode set up. This seems to be related to the new developer mode landings. Devmode is still forced on on boot so that we don't lock ourselves out, but MTP should be unaffected. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: dbus-property-service 0.5 Uname: Linux 3.4.0-5-mako armv7l ApportVersion: 2.14.7-0ubuntu2 Architecture: armhf Date: Fri Sep 5 10:37:51 2014 InstallationDate: Installed on 2014-09-05 (0 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20140905-020205) PackageArchitecture: all SourcePackage: dbus-property-service UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbus-property-service/+bug/1365911/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1365911] Re: MTP not working on boot if passcode not set
ok, this seems to be the case ... uploaded to the archive -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc-android-config in Ubuntu. https://bugs.launchpad.net/bugs/1365911 Title: MTP not working on boot if passcode not set Status in “dbus-property-service” package in Ubuntu: Invalid Status in “lxc-android-config” package in Ubuntu: In Progress Bug description: mako devel-proposed#223 MTP doesn't work for me on boot if I don't have a passcode set up. This seems to be related to the new developer mode landings. Devmode is still forced on on boot so that we don't lock ourselves out, but MTP should be unaffected. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: dbus-property-service 0.5 Uname: Linux 3.4.0-5-mako armv7l ApportVersion: 2.14.7-0ubuntu2 Architecture: armhf Date: Fri Sep 5 10:37:51 2014 InstallationDate: Installed on 2014-09-05 (0 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20140905-020205) PackageArchitecture: all SourcePackage: dbus-property-service UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbus-property-service/+bug/1365911/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1316978] Re: ubuntu-touch-session needs to be able to start even if the homedir is filled to 100%
** Tags added: rtm -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dbus in Ubuntu. https://bugs.launchpad.net/bugs/1316978 Title: ubuntu-touch-session needs to be able to start even if the homedir is filled to 100% Status in Ubuntu CI Services: New Status in “android” package in Ubuntu: Invalid Status in “dbus” package in Ubuntu: Confirmed Status in “hud” package in Ubuntu: Confirmed Status in “ubuntu-touch-session” package in Ubuntu: Confirmed Bug description: When the ~/phablet tree has media files added to it by the user, it is possible for the storage space to be filled, and consequently for the device not to boot. From the OEM project bug: After further investigation this problem was caused by the following: 1) Files were pushed to ~phablet/ 2) The files filled the home partition completely 3) Upon a restart of the phone the upstart session job /usr/share/upstart/sessions/dbus.conf is attempted 4) Because the partition is full, the final line of the pre-start stanza fails as $HOME/.cache/upstart/dbus-session cannot be created 5) As there is no running dbus session instance unity8 fails to start Clearing space on the home partition allows unity8 to start again. Posted here, since following discussion in #ubuntu-touch it has the same underlying cause as bug #1270248, also reported on this package. Raised as a separate bug, because this was caused by user action, rather than simply the system failing to do log housekeeping. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ci-services-itself/+bug/1316978/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1334312] Re: platform-api shouldn't try to use vibrator if not available
i think this bug should be higher prio ... it makes application logs grow quite a bit ... -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to usensord in Ubuntu. https://bugs.launchpad.net/bugs/1334312 Title: platform-api shouldn't try to use vibrator if not available Status in “platform-api” package in Ubuntu: Confirmed Status in “usensord” package in Ubuntu: Confirmed Bug description: Currently on flo I get the following message every time someone calls the vibrate function: com.canonical.usensord.Error: open /sys/class/timed_output/vibrator/enable: no such file or directory That's basically because there's no vibrator hardware/driver available for flo. Platform-api should be smart enough to not use it if not available. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/platform-api/+bug/1334312/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1317860] Re: [system] the phone should switch itself off before completely draining battery
android does warn when it goes below 15% ... i wonder if we should not do teh same here ... -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-power in Ubuntu. https://bugs.launchpad.net/bugs/1317860 Title: [system] the phone should switch itself off before completely draining battery Status in The Power Indicator: Confirmed Status in Ubuntu UX bugs: Fix Committed Status in “indicator-power” package in Ubuntu: Confirmed Bug description: the phone should switch itself off at around ~5% remaining battery. This is to preserve a little battery for use cases such as: * turn it back on once or twice for urgent short phone calls * prevent the battery from going into a state where it can't be charged any more * have enough power to turn itself on again and trigger an alarm Desired resolution The following actions should take place as the phone/tablet runs out of battery: at 10% - Notification battery under 10% at 5% - Notification saying battery level is critical, will shutdown soon. at 1-2% - Shell fades out, animation fades in (same as startup animation), phone initiates full shutdown. The notification should be a clickable notification with the tap action mapped to dismiss. To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-power/+bug/1317860/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1394919] [NEW] constant crash in trying to collect info for recoverable error
Public bug reported: since a few days my phone started producing a /var/crash/_usr_share_apport_recoverable_problem.32011.crash i see the timestamp updated multiple times and the matching PID from the traceback seems to be cgmanager https://errors.ubuntu.com/oops/c25e8678-70f2-11e4-976f-fa163e4aaad4 https://errors.ubuntu.com/oops/94398858-70a0-11e4-906f-fa163e339c81 https://errors.ubuntu.com/oops/235b2dd0-7118-11e4-837c-fa163e5bb1a2 are the respective whoopsie uploads. ** Affects: apport (Ubuntu) Importance: Undecided Status: New ** Affects: cgmanager (Ubuntu) Importance: Undecided Status: New ** Affects: apport (Ubuntu RTM) Importance: Undecided Status: New ** Affects: cgmanager (Ubuntu RTM) Importance: Undecided Status: New ** Also affects: cgmanager (Ubuntu) Importance: Undecided Status: New ** Also affects: apport (Ubuntu RTM) Importance: Undecided Status: New ** Also affects: cgmanager (Ubuntu RTM) Importance: Undecided Status: New -- 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/1394919 Title: constant crash in trying to collect info for recoverable error Status in “apport” package in Ubuntu: New Status in “cgmanager” package in Ubuntu: New Status in “apport” package in Ubuntu RTM: New Status in “cgmanager” package in Ubuntu RTM: New Bug description: since a few days my phone started producing a /var/crash/_usr_share_apport_recoverable_problem.32011.crash i see the timestamp updated multiple times and the matching PID from the traceback seems to be cgmanager https://errors.ubuntu.com/oops/c25e8678-70f2-11e4-976f-fa163e4aaad4 https://errors.ubuntu.com/oops/94398858-70a0-11e4-906f-fa163e339c81 https://errors.ubuntu.com/oops/235b2dd0-7118-11e4-837c-fa163e5bb1a2 are the respective whoopsie uploads. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1394919/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1394919] Re: constant crash in trying to collect info for recoverable error
the timestamps seem to go along with a session crash i see -- 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/1394919 Title: constant crash in trying to collect info for recoverable error Status in “apport” package in Ubuntu: New Status in “cgmanager” package in Ubuntu: New Status in “apport” package in Ubuntu RTM: New Status in “cgmanager” package in Ubuntu RTM: New Bug description: since a few days my phone started producing a /var/crash/_usr_share_apport_recoverable_problem.32011.crash i see the timestamp updated multiple times and the matching PID from the traceback seems to be cgmanager https://errors.ubuntu.com/oops/c25e8678-70f2-11e4-976f-fa163e4aaad4 https://errors.ubuntu.com/oops/94398858-70a0-11e4-906f-fa163e339c81 https://errors.ubuntu.com/oops/235b2dd0-7118-11e4-837c-fa163e5bb1a2 are the respective whoopsie uploads. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1394919/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1394919] Re: constant crash in trying to collect info for recoverable error
no, we havent, the timestamps of teh crash files just match the time of session crashes i had -- 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/1394919 Title: constant crash in trying to collect info for recoverable error Status in “apport” package in Ubuntu: New Status in “cgmanager” package in Ubuntu: New Status in “apport” package in Ubuntu RTM: New Status in “cgmanager” package in Ubuntu RTM: New Bug description: since a few days my phone started producing a /var/crash/_usr_share_apport_recoverable_problem.32011.crash i see the timestamp updated multiple times and the matching PID from the traceback seems to be cgmanager https://errors.ubuntu.com/oops/c25e8678-70f2-11e4-976f-fa163e4aaad4 https://errors.ubuntu.com/oops/94398858-70a0-11e4-906f-fa163e339c81 https://errors.ubuntu.com/oops/235b2dd0-7118-11e4-837c-fa163e5bb1a2 are the respective whoopsie uploads. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1394919/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1395088] [NEW] APs with same SSID and support for the same encryption should be merged into one on the network list
Public bug reported: as you can see in the iwlist scan output below i have two APs in my house, one supporting WPA2 only, the other supporting WPA (enabled for some weird old wifi HW) and WPA2 ... while nm-applet merges these two into one entry in the network list on various ubuntu desktop devices here, the phone shows one entry per AP. this behavior should be brought in sync (preferably by making indicator-network also only show one entry in this case) wlan0 Scan completed : Cell 01 - Address: 00:23:69:B9:C2:E0 ESSID:grawert.net Frequency:2.412 GHz (Channel 1) Mode:Managed Signal level=-76 dBm Encryption key:on Bit Rates:54 Mb/s Extra:Rates (Mb/s): 1 2 5.5 11 6 9 12 18 24 36 48 54 IE: Unknown: DD770050F204104A0001101044000102103B00010310470010002369B9C2DE002369B9C2DE02313535102100104C696E6B73797320627920436973636F102300085752543136304E4C1024000876312E30302E30311042000231351054000800060050F2040001101100085752543136304E4C100800020084 IE: IEEE 802.11i/WPA2 Version 1 Group Cipher : CCMP Pairwise Ciphers (1) : CCMP Authentication Suites (1) : PSK Cell 02 - Address: C0:3F:0E:CA:36:26 ESSID:grawert.net Frequency:2.437 GHz (Channel 6) Mode:Managed Signal level=-46 dBm Encryption key:on Bit Rates:54 Mb/s Extra:Rates (Mb/s): 1 2 5.5 11 6 9 12 18 24 36 48 54 IE: WPA Version 1 Group Cipher : TKIP Pairwise Ciphers (2) : CCMP TKIP Authentication Suites (1) : PSK IE: Unknown: DD0E0050F204104A0001101044000102 IE: IEEE 802.11i/WPA2 Version 1 Group Cipher : TKIP Pairwise Ciphers (2) : CCMP TKIP Authentication Suites (1) : PSK ** Affects: indicator-network (Ubuntu) Importance: Undecided Status: New ** Summary changed: - APs with same SSID and support for teh same encryption should be merged into one on the network list + APs with same SSID and support for the same encryption should be merged into one on the network list -- 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/1395088 Title: APs with same SSID and support for the same encryption should be merged into one on the network list Status in “indicator-network” package in Ubuntu: New Bug description: as you can see in the iwlist scan output below i have two APs in my house, one supporting WPA2 only, the other supporting WPA (enabled for some weird old wifi HW) and WPA2 ... while nm-applet merges these two into one entry in the network list on various ubuntu desktop devices here, the phone shows one entry per AP. this behavior should be brought in sync (preferably by making indicator-network also only show one entry in this case) wlan0 Scan completed : Cell 01 - Address: 00:23:69:B9:C2:E0 ESSID:grawert.net Frequency:2.412 GHz (Channel 1) Mode:Managed Signal level=-76 dBm Encryption key:on Bit Rates:54 Mb/s Extra:Rates (Mb/s): 1 2 5.5 11 6 9 12 18 24 36 48 54 IE: Unknown: DD770050F204104A0001101044000102103B00010310470010002369B9C2DE002369B9C2DE02313535102100104C696E6B73797320627920436973636F102300085752543136304E4C1024000876312E30302E30311042000231351054000800060050F2040001101100085752543136304E4C100800020084 IE: IEEE 802.11i/WPA2 Version 1 Group Cipher : CCMP Pairwise Ciphers (1) : CCMP Authentication Suites (1) : PSK Cell 02 - Address: C0:3F:0E:CA:36:26 ESSID:grawert.net Frequency:2.437 GHz (Channel 6) Mode:Managed Signal level=-46 dBm Encryption key:on Bit Rates:54 Mb/s Extra:Rates (Mb/s): 1 2 5.5 11 6 9 12 18 24 36 48 54 IE: WPA Version 1 Group Cipher : TKIP Pairwise Ciphers (2) : CCMP TKIP Authentication Suites (1) : PSK IE: Unknown: DD0E0050F204104A0001101044000102 IE: IEEE 802.11i/WPA2 Version 1 Group Cipher : TKIP Pairwise
[Touch-packages] [Bug 1394919] Re: constant crash in trying to collect info for recoverable error
cgmanager log when the issue happens: http://paste.ubuntu.com/9156976/ syslog when the issue happens: http://paste.ubuntu.com/9157026/ -- 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/1394919 Title: constant crash in trying to collect info for recoverable error Status in “apport” package in Ubuntu: New Status in “cgmanager” package in Ubuntu: New Status in “ubuntu-app-launch” package in Ubuntu: New Status in “apport” package in Ubuntu RTM: New Status in “cgmanager” package in Ubuntu RTM: New Bug description: Errors Bucket - https://errors.ubuntu.com/problem/9a1df90760a88c9b4e5e7e3b4ef450f6b5669c7c since a few days my phone started producing a /var/crash/_usr_share_apport_recoverable_problem.32011.crash i see the timestamp updated multiple times and the matching PID from the traceback seems to be cgmanager https://errors.ubuntu.com/oops/c25e8678-70f2-11e4-976f-fa163e4aaad4 https://errors.ubuntu.com/oops/94398858-70a0-11e4-906f-fa163e339c81 https://errors.ubuntu.com/oops/235b2dd0-7118-11e4-837c-fa163e5bb1a2 are the respective whoopsie uploads. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1394919/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1394919] Re: constant crash in trying to collect info for recoverable error
after this happened, the session recovers on its own but no apps can be started anymore.. -- 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/1394919 Title: constant crash in trying to collect info for recoverable error Status in “apport” package in Ubuntu: New Status in “cgmanager” package in Ubuntu: New Status in “ubuntu-app-launch” package in Ubuntu: New Status in “apport” package in Ubuntu RTM: New Status in “cgmanager” package in Ubuntu RTM: New Bug description: Errors Bucket - https://errors.ubuntu.com/problem/9a1df90760a88c9b4e5e7e3b4ef450f6b5669c7c since a few days my phone started producing a /var/crash/_usr_share_apport_recoverable_problem.32011.crash i see the timestamp updated multiple times and the matching PID from the traceback seems to be cgmanager https://errors.ubuntu.com/oops/c25e8678-70f2-11e4-976f-fa163e4aaad4 https://errors.ubuntu.com/oops/94398858-70a0-11e4-906f-fa163e339c81 https://errors.ubuntu.com/oops/235b2dd0-7118-11e4-837c-fa163e5bb1a2 are the respective whoopsie uploads. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1394919/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1394919] Re: constant crash in trying to collect info for recoverable error
i had it several times today that: a) apps do not start anymore b) suspended apps do not recover anymore c) only a system reboot helps to get out of this state i collected a bunch of logs at http://paste.ubuntu.com/9197719/ while the system is in this state obviously cgmanager hangs and does not react anymore to any interaction here ... -- 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/1394919 Title: constant crash in trying to collect info for recoverable error Status in “apport” package in Ubuntu: New Status in “cgmanager” package in Ubuntu: New Status in “ubuntu-app-launch” package in Ubuntu: Fix Released Status in “apport” package in Ubuntu RTM: New Status in “cgmanager” package in Ubuntu RTM: Confirmed Bug description: Errors Bucket - https://errors.ubuntu.com/problem/9a1df90760a88c9b4e5e7e3b4ef450f6b5669c7c since a few days my phone started producing a /var/crash/_usr_share_apport_recoverable_problem.32011.crash i see the timestamp updated multiple times and the matching PID from the traceback seems to be cgmanager https://errors.ubuntu.com/oops/c25e8678-70f2-11e4-976f-fa163e4aaad4 https://errors.ubuntu.com/oops/94398858-70a0-11e4-906f-fa163e339c81 https://errors.ubuntu.com/oops/235b2dd0-7118-11e4-837c-fa163e5bb1a2 are the respective whoopsie uploads. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1394919/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1394919] Re: constant crash in trying to collect info for recoverable error
i also just noticed that my dbus log is full of: ** (zeitgeist-fts:2999): WARNING **: Unable to get info on application://ubuntu-app-launch.desktop (process:2082): GLib-GObject-WARNING **: /build/buildd/glib2.0-2.41.5/./gobject/gsignal.c:3101: signal id '33' is invalid for instance '0x1829ad8' (process:2082): GLib-GObject-WARNING **: /build/buildd/glib2.0-2.41.5/./gobject/gsignal.c:3101: signal id '33' is invalid for instance '0x1829ad8' ** Summary changed: - constant crash in trying to collect info for recoverable error + constant crash in trying to collect info for recoverable error of cgmanager -- 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/1394919 Title: constant crash in trying to collect info for recoverable error of cgmanager Status in “apport” package in Ubuntu: New Status in “cgmanager” package in Ubuntu: New Status in “ubuntu-app-launch” package in Ubuntu: Fix Released Status in “apport” package in Ubuntu RTM: New Status in “cgmanager” package in Ubuntu RTM: Confirmed Bug description: Errors Bucket - https://errors.ubuntu.com/problem/9a1df90760a88c9b4e5e7e3b4ef450f6b5669c7c since a few days my phone started producing a /var/crash/_usr_share_apport_recoverable_problem.32011.crash i see the timestamp updated multiple times and the matching PID from the traceback seems to be cgmanager https://errors.ubuntu.com/oops/c25e8678-70f2-11e4-976f-fa163e4aaad4 https://errors.ubuntu.com/oops/94398858-70a0-11e4-906f-fa163e339c81 https://errors.ubuntu.com/oops/235b2dd0-7118-11e4-837c-fa163e5bb1a2 are the respective whoopsie uploads. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1394919/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1394919] Re: constant crash in trying to collect info for recoverable error of cgmanager
i am pretty sure this is simply the same as bug 1377332 the core issue with cgmanager from this bug was never fixed (it is in critical, incomplete and unassigned state) only workarounds have been put in place to hide the symptoms in ubuntu-app-launch. the actual crash/breakage was never fixed. according to commant #38 in the above bug i enabled the debug mode for cgmanager now. i belive everyone who could repro this bug should try to do the same to collect as much info as we can. -- 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/1394919 Title: constant crash in trying to collect info for recoverable error of cgmanager Status in “apport” package in Ubuntu: Confirmed Status in “cgmanager” package in Ubuntu: Confirmed Status in “ubuntu-app-launch” package in Ubuntu: Fix Released Status in “apport” package in Ubuntu RTM: New Status in “cgmanager” package in Ubuntu RTM: Confirmed Bug description: Errors Bucket - https://errors.ubuntu.com/problem/9a1df90760a88c9b4e5e7e3b4ef450f6b5669c7c since a few days my phone started producing a /var/crash/_usr_share_apport_recoverable_problem.32011.crash i see the timestamp updated multiple times and the matching PID from the traceback seems to be cgmanager https://errors.ubuntu.com/oops/c25e8678-70f2-11e4-976f-fa163e4aaad4 https://errors.ubuntu.com/oops/94398858-70a0-11e4-906f-fa163e339c81 https://errors.ubuntu.com/oops/235b2dd0-7118-11e4-837c-fa163e5bb1a2 are the respective whoopsie uploads. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1394919/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1387806] Re: toolkit dialogs have wonky padding
can we please have RTM tasks for both ? else we will miss when it lands in RTM -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1387806 Title: toolkit dialogs have wonky padding Status in “ubuntu-system-settings” package in Ubuntu: Confirmed Status in “ubuntu-ui-toolkit” package in Ubuntu: In Progress Bug description: Ubuntu 14.10 r135 1. Go to System Settings Wi-Fi. 2. If Wi-Fi is off, turn it on. 3. Scroll to the bottom of the list and choose Connect to hidden network. What you see: A dialog where the left padding (x1) is less than the right padding (x2), and the top padding (y1) is less than the bottom padding (y2). What you should see: A dialog where the left and right padding are equal (x1 = x2), and the top and bottom padding are equal (y1 = y2). I don't know whether this is a System Settings bug, a toolkit bug, or a combination. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-system-settings/+bug/1387806/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1303666] Re: unity8 randomly crashes
i have definitely not seen that in weeks ... why did you assign this bug to me, would you expect a patch ? :) ** Changed in: unity8 (Ubuntu) Assignee: Oliver Grawert (ogra) = (unassigned) ** Changed in: unity8 (Ubuntu) Status: Incomplete = Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1303666 Title: unity8 randomly crashes Status in “unity8” package in Ubuntu: Invalid Bug description: during the weekend i had my UI restart plenty of times when trying out porting my web-apps to the new webapp container ... today i found a .crash file in /var/crash ... i also noticed that the application scope is often completely empty (you have to expand/collapse the empty category to get any content back) and webapps die all the time (might be related or not). ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity8 7.85+14.04.20140403.1-0ubuntu1 Uname: Linux 3.4.0-5-mako armv7l ApportVersion: 2.14.1-0ubuntu1 Architecture: armhf Date: Mon Apr 7 10:59:07 2014 InstallationDate: Installed on 2014-04-06 (1 days ago) InstallationMedia: Ubuntu Trusty Tahr (development branch) - armhf (20140406) 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/1303666/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1377332] Re: [TOPBLOCKER] UI randomly freezes
serge: not really ... we need armhf binaries on the phone (which would be fine thanks to your debdiff we could build that in a silo, but ...) the RTM distro is on 0.30 (and i think stuck there since we can not easily upgrade to latest lxc if i understood stephane correctly) ... https://launchpad.net/ubuntu-rtm/+source/cgmanager -- 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/1377332 Title: [TOPBLOCKER] UI randomly freezes Status in “cgmanager” package in Ubuntu: Confirmed Status in “ubuntu-app-launch” package in Ubuntu: Fix Released Status in “unity8” package in Ubuntu: Opinion Status in “ubuntu-app-launch” package in Ubuntu RTM: Fix Released Status in “unity8” package in Ubuntu RTM: Opinion Bug description: Summary UI randomly freezes steps: 1. unlock greeter 2. open app 3. pull down random indicator 4. close indicator 5. open app 6. swipe to view all open apps 7. open launcher 8. close some open apps 9. repeat until ui freezes device info: [service] base: system-image.ubuntu.com http_port: 80 https_port: 443 channel: ubuntu-touch/ubuntu-rtm/14.09-proposed device: krillin build_number: 79 version_detail: ubuntu=20141002,device=20141002-d5938d7,custom=1412208099,version=79 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cgmanager/+bug/1377332/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
