[Touch-packages] [Bug 1408106] Re: attach_disconnected not sufficient for overlayfs
@lamont does this need to have a MAAS task? Are we going to address it
somehow in MAAS?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/1408106
Title:
attach_disconnected not sufficient for overlayfs
Status in AppArmor:
In Progress
Status in MAAS:
New
Status in apparmor package in Ubuntu:
Confirmed
Status in linux package in Ubuntu:
Triaged
Bug description:
With the following use of overlayfs, we get a disconnected path:
$ cat ./profile
#include
profile foo {
#include
capability sys_admin,
capability sys_chroot,
mount,
pivot_root,
}
$ cat ./overlay.c
#include
#include
#include
#include
#include
#include
#include
int main(int argc, char* argv[]) {
int i = 0;
int len = 0;
int ret = 0;
char* options;
if (geteuid())
unshare(CLONE_NEWUSER);
unshare(CLONE_NEWNS);
for (i = 1; i < argc; i++) {
if (i == 1) {
len = strlen(argv[i]) + strlen("upperdir=,lowerdir=/") + 2;
options = alloca(len);
ret = snprintf(options, len, "upperdir=%s,lowerdir=/", argv[i]);
}
else {
len = strlen(argv[i]) + strlen("upperdir=,lowerdir=/mnt") + 2;
options = alloca(len);
ret = snprintf(options, len, "upperdir=%s,lowerdir=/mnt",
argv[i]);
}
mount("overlayfs", "/mnt", "overlayfs", MS_MGC_VAL, options);
}
chdir("/mnt");
pivot_root(".", ".");
chroot(".");
chdir("/");
execl("/bin/bash", "/bin/bash", NULL);
}
$ sudo apparmor_parser -r ./profile && aa-exec -p foo -- ./a.out /tmp
[255]
...
Dec 12 14:31:38 localhost kernel: [57278.040216] audit: type=1400
audit(1418387498.613:712): apparmor="DENIED" operation="exec" info="Failed name
lookup - disconnected path" error=-13 profile="foo" name="/bin/bash" pid=18255
comm="a.out" requested_mask="x" denied_mask="x" fsuid=1000 ouid=0
With the above, the expectation was for the denial to be /mnt/bin/bash. There
are three ways forward:
1. the correct solution is to patch overlayfs to properly track the loopback,
but this will take a while, may ultimately be unachievable. UPDATE: upstream is
currently working on this and Ubuntu will engage with them
2. we could rely on the fact that overlayfs creates a private unshared
submount, and provide a way to not mediate the path when that is present, and
tagged. This would take a bit of time, and might be the preferred method over 1
longer term
3. we could extend attach_disconnected so that we can define the attach root.
Eg, we can use profile foo (attach_disconnected=/mnt) {} such that '/bin/bash'
maps to '/mnt/bin/bash'. UPDATE: THIS IS NOT VIABLE
To manage notifications about this bug go to:
https://bugs.launchpad.net/apparmor/+bug/1408106/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1523501] Re: r1712 broke our AP tests on desktop and device
** Branch linked: lp:~canonical-platform-qa/ubuntu-ui- toolkit/fix_keyboard_bug1523501 -- 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/1523501 Title: r1712 broke our AP tests on desktop and device Status in ubuntu-ui-toolkit package in Ubuntu: New Bug description: File "/home/tim/dev/ubuntu-ui-toolkit/m/fix-header-ap-landing/tests/autopilot/ubuntuuitoolkit/_custom_proxy_objects/_flickable.py", line 41, in _get_visible_container_bottom if keyboard._keyboard.is_available(): AttributeError: 'Keyboard' object has no attribute '_keyboard' See, for example http://pastebin.ubuntu.com/13788069/ I suspect r1712 of our staging broke it, because that revision added the failing lines to _flickable.py. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1523501/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1520164] [NEW] overlay buttons globalRect has wrong y co-ordinate (represents center of the object, rather than the top)
Public bug reported: The globalRect property of an object is supposed to represent the top left hand corner of it, along with the width and height. Taking advantage of that fact, Autopilot calculates the middle as x, y = x+w/2, y+h/2 This calculation seems to have been thrown off by the overlay buttons in the camera-app. In this case the globalRect represents the center of the object. We determined this by enabling the touch vizualisation in Unity8: $ apt-get install qtdbus-qt5 $ qdbus --system com.canonical.Unity.Screen / com.canonical.Unity.Screen.setTouchVisualizationEnabled true When clicking using click_object this clicks in the center, just below the button. If we use the globalRect co-ordinates directly (without adding width and height) it clicks in the exact center of the button. Note that camera-app seems to be the only application affected by this issue at the moment. Another note - the x, y, width and height properties (outside of globalRect) seem to be correct. $ system-image-cli -i current build number: 187 device name: krillin channel: ubuntu-touch/rc-proposed/bq-aquaris.en last update: 2015-11-24 09:51:16 version version: 187 version ubuntu: 20151124 version device: 20151028-869191d version custom: 2015--36-46-vivid ** Affects: camera-app Importance: Undecided Status: New ** Affects: ubuntu-ui-toolkit (Ubuntu) Importance: Undecided Status: New ** Also 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/1520164 Title: overlay buttons globalRect has wrong y co-ordinate (represents center of the object, rather than the top) Status in camera-app: New Status in ubuntu-ui-toolkit package in Ubuntu: New Bug description: The globalRect property of an object is supposed to represent the top left hand corner of it, along with the width and height. Taking advantage of that fact, Autopilot calculates the middle as x, y = x+w/2, y+h/2 This calculation seems to have been thrown off by the overlay buttons in the camera-app. In this case the globalRect represents the center of the object. We determined this by enabling the touch vizualisation in Unity8: $ apt-get install qtdbus-qt5 $ qdbus --system com.canonical.Unity.Screen / com.canonical.Unity.Screen.setTouchVisualizationEnabled true When clicking using click_object this clicks in the center, just below the button. If we use the globalRect co-ordinates directly (without adding width and height) it clicks in the exact center of the button. Note that camera-app seems to be the only application affected by this issue at the moment. Another note - the x, y, width and height properties (outside of globalRect) seem to be correct. $ system-image-cli -i current build number: 187 device name: krillin channel: ubuntu-touch/rc-proposed/bq-aquaris.en last update: 2015-11-24 09:51:16 version version: 187 version ubuntu: 20151124 version device: 20151028-869191d version custom: 2015--36-46-vivid To manage notifications about this bug go to: https://bugs.launchpad.net/camera-app/+bug/1520164/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1520164] Re: overlay buttons globalRect has wrong y co-ordinate (represents center of the object, rather than the top)
Well it will be once this is fixed: https://bugs.launchpad.net/camera- app/+bug/1520171 -- 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/1520164 Title: overlay buttons globalRect has wrong y co-ordinate (represents center of the object, rather than the top) Status in camera-app: New Status in Canonical System Image: Confirmed Status in ubuntu-ui-toolkit package in Ubuntu: New Bug description: The globalRect property of an object is supposed to represent the top left hand corner of it, along with the width and height. Taking advantage of that fact, Autopilot calculates the middle as x, y = x+w/2, y+h/2 This calculation seems to have been thrown off by the overlay buttons in the camera-app. In this case the globalRect represents the center of the object. We determined this by enabling the touch vizualisation in Unity8: $ apt-get install qtdbus-qt5 $ qdbus --system com.canonical.Unity.Screen / com.canonical.Unity.Screen.setTouchVisualizationEnabled true When clicking using click_object this clicks in the center, just below the button. If we use the globalRect co-ordinates directly (without adding width and height) it clicks in the exact center of the button. Note that camera-app seems to be the only application affected by this issue at the moment. Another note - the x, y, width and height properties (outside of globalRect) seem to be correct. $ system-image-cli -i current build number: 187 device name: krillin channel: ubuntu-touch/rc-proposed/bq-aquaris.en last update: 2015-11-24 09:51:16 version version: 187 version ubuntu: 20151124 version device: 20151028-869191d version custom: 2015--36-46-vivid To manage notifications about this bug go to: https://bugs.launchpad.net/camera-app/+bug/1520164/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1513044] [NEW] autopilot tests failing, unable to find 'Label'
Public bug reported:
Running the messaging-app autopilot tests, we get 20 out of 27 tests
failing. The majority of them due to not being able to find 'Label'
objects. This appears to be because Label has changed to UCLabel in a
recent version of messaging-app. Below is a typical traceback from one
of the failures:
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/messaging_app/tests/test_messaging.py",
line 290, in test_delete_message_swipe_right
self.main_view.send_message([phone_num], message)
File "/usr/lib/python3/dist-packages/autopilot/logging.py", line 46, in inner
return f(instance, *args, **kwargs)
File "/usr/lib/python3/dist-packages/messaging_app/emulators.py", line 392,
in send_message
thread_bubble = self.get_message(message)
File "/usr/lib/python3/dist-packages/messaging_app/emulators.py", line 68, in
get_message
'{}'.format(text))
messaging_app.emulators.EmulatorException: Could not find message with the text
delete me okay
phablet@ubuntu-phablet:~$ system-image-cli -i
current build number: 164
device name: krillin
channel: ubuntu-touch/rc-proposed/bq-aquaris.en
last update: 2015-11-04 10:36:00
version version: 164
version ubuntu: 20151104
version device: 20150821-736d127
version custom: 20150925-901-35-40-vivid
Attached is a subunit file with all the results from the run - it can be
best viewed with the 'trv' application:
https://launchpad.net/~thomir/+archive/ubuntu/trv
** Affects: messaging-app (Ubuntu)
Importance: Undecided
Status: New
** Attachment added: "messaging.subunit"
https://bugs.launchpad.net/bugs/1513044/+attachment/4512708/+files/messaging.subunit
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to messaging-app in Ubuntu.
https://bugs.launchpad.net/bugs/1513044
Title:
autopilot tests failing, unable to find 'Label'
Status in messaging-app package in Ubuntu:
New
Bug description:
Running the messaging-app autopilot tests, we get 20 out of 27 tests
failing. The majority of them due to not being able to find 'Label'
objects. This appears to be because Label has changed to UCLabel in a
recent version of messaging-app. Below is a typical traceback from one
of the failures:
Traceback (most recent call last):
File
"/usr/lib/python3/dist-packages/messaging_app/tests/test_messaging.py", line
290, in test_delete_message_swipe_right
self.main_view.send_message([phone_num], message)
File "/usr/lib/python3/dist-packages/autopilot/logging.py", line 46, in
inner
return f(instance, *args, **kwargs)
File "/usr/lib/python3/dist-packages/messaging_app/emulators.py", line 392,
in send_message
thread_bubble = self.get_message(message)
File "/usr/lib/python3/dist-packages/messaging_app/emulators.py", line 68,
in get_message
'{}'.format(text))
messaging_app.emulators.EmulatorException: Could not find message with the
text delete me okay
phablet@ubuntu-phablet:~$ system-image-cli -i
current build number: 164
device name: krillin
channel: ubuntu-touch/rc-proposed/bq-aquaris.en
last update: 2015-11-04 10:36:00
version version: 164
version ubuntu: 20151104
version device: 20150821-736d127
version custom: 20150925-901-35-40-vivid
Attached is a subunit file with all the results from the run - it can
be best viewed with the 'trv' application:
https://launchpad.net/~thomir/+archive/ubuntu/trv
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/messaging-app/+bug/1513044/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1507491] Re: Some behaviors in 'Find in page' mode do not meet the requirements
@Evan, this is a partial duplicate of https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1511736 (for the first behaviour), please update this bug to only mention the second issue, and please don't file one bug for multiple distinct issues (even though they are related to the same test case, you should instead link both bugs to that test case) -- 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/1507491 Title: Some behaviors in 'Find in page' mode do not meet the requirements Status in webbrowser-app package in Ubuntu: New Bug description: $ adb shell system-image-cli -i current build number: 152 device name: krillin channel: ubuntu-touch/rc-proposed/bq-aquaris.en last update: 2015-10-16 04:40:26 version version: 152 version ubuntu: 20151016 version device: 20150821-736d127 version custom: 20150925-901-35-40-vivid Steps to reproduce: 1. Launch web browser 2. Enable "Find in page" mode from top-right corner menu Action 1: Typing one or more matched letters in search box, the Next/Previous chevrons is not disabled when at the top/bottom of the list, please refer to attachment 1 Expected: Next/Previous chevrons will be disabled if at the top/bottom of the list Action 2: Typing some unmatched letters in search box, the hint text at the right is not highlighted in red, pls refer to attachment 2 Expected: If there are no matches, the hint text at the right is highlighted in red To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1507491/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1511736] [NEW] Find in page search wraps around, but spec says it should not
Public bug reported: The Find in Page specification for the browser says: "Next/Previous chevrons will be disabled if at the top/bottom of the list" However they are not and the search wraps around if they are pressed at that point https://docs.google.com/presentation/d/1Qrd4Flfs3EH-fI79IfrYgLdAx2nce- L7ve8NKLCX324/edit#slide=id.g3ddd7bb9c_031 > system-image-cli -i current build number: 161 device name: krillin channel: ubuntu-touch/rc-proposed/bq-aquaris.en last update: 2015-10-30 08:59:33 version version: 161 version ubuntu: 20151030 version device: 20150821-736d127 version custom: 20150925-901-35-40-vivid ** Affects: webbrowser-app (Ubuntu) Importance: Undecided Status: New ** Summary changed: - Find in page search wraps around, but spec says it should not be + Find in page search wraps around, but spec says it should not -- 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/1511736 Title: Find in page search wraps around, but spec says it should not Status in webbrowser-app package in Ubuntu: New Bug description: The Find in Page specification for the browser says: "Next/Previous chevrons will be disabled if at the top/bottom of the list" However they are not and the search wraps around if they are pressed at that point https://docs.google.com/presentation/d/1Qrd4Flfs3EH-fI79IfrYgLdAx2nce- L7ve8NKLCX324/edit#slide=id.g3ddd7bb9c_031 > system-image-cli -i current build number: 161 device name: krillin channel: ubuntu-touch/rc-proposed/bq-aquaris.en last update: 2015-10-30 08:59:33 version version: 161 version ubuntu: 20151030 version device: 20150821-736d127 version custom: 20150925-901-35-40-vivid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1511736/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1508130] [NEW] 'find in page' fails to focus address bar every second time
Public bug reported: Steps to reproduce: 1. Open the Web Browser 2. Open the Drawer widget on the top right corner 3. Select Find In Page 4. Confirm the address bar is focused (in find in page mode) and the keyboard appears 5. Press Back to return to normal browsing view 6. Open the Drawer widget again 7. Select Find In Page again Expected result: The address bar (in find in page mode) is focused and the keyboard appears Actual result: Find in page mode is active but the address bar is not focused and the keyboard does not appear current build number: 152 device name: krillin channel: ubuntu-touch/rc-proposed/bq-aquaris.en last update: 2015-10-18 22:11:48 version version: 152 version ubuntu: 20151016 version device: 20150821-736d127 version custom: 20150925-901-35-40-vivid ** Affects: webbrowser-app (Ubuntu) Importance: High Assignee: Ugo Riboni (uriboni) Status: Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu. https://bugs.launchpad.net/bugs/1508130 Title: 'find in page' fails to focus address bar every second time Status in webbrowser-app package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Open the Web Browser 2. Open the Drawer widget on the top right corner 3. Select Find In Page 4. Confirm the address bar is focused (in find in page mode) and the keyboard appears 5. Press Back to return to normal browsing view 6. Open the Drawer widget again 7. Select Find In Page again Expected result: The address bar (in find in page mode) is focused and the keyboard appears Actual result: Find in page mode is active but the address bar is not focused and the keyboard does not appear current build number: 152 device name: krillin channel: ubuntu-touch/rc-proposed/bq-aquaris.en last update: 2015-10-18 22:11:48 version version: 152 version ubuntu: 20151016 version device: 20150821-736d127 version custom: 20150925-901-35-40-vivid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1508130/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1491484] [NEW] Anker keyboard doesn't send key events to krillin
Public bug reported: I have an Anker BT keyboard which seems to work fine on the Nexus 4 with Android, but when I use it with Krillin and Ubuntu it doesn't seem to receive keypresses. In fact I have used a hack boot.img to get it to even connect. The exact model is : http://www.amazon.co.uk/Compact- Wireless-Bluetooth-Keyboard- Rechargeable/dp/B00PIMRCFG/ref=sr_1_2?ie=UTF8=1441209196=8-2=anker+bluetooth+keyboard phablet@ubuntu-phablet:~$ system-image-cli -i current build number: 114 device name: krillin channel: ubuntu-touch/rc-proposed/bq-aquaris.en last update: 2015-09-02 08:01:15 version version: 114 version ubuntu: 20150902 version device: 20150821-736d127 version custom: 20150821-887-33-32-vivid ** Affects: bluez (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1491484 Title: Anker keyboard doesn't send key events to krillin Status in bluez package in Ubuntu: New Bug description: I have an Anker BT keyboard which seems to work fine on the Nexus 4 with Android, but when I use it with Krillin and Ubuntu it doesn't seem to receive keypresses. In fact I have used a hack boot.img to get it to even connect. The exact model is : http://www.amazon.co.uk /Compact-Wireless-Bluetooth-Keyboard- Rechargeable/dp/B00PIMRCFG/ref=sr_1_2?ie=UTF8=1441209196=8-2=anker+bluetooth+keyboard phablet@ubuntu-phablet:~$ system-image-cli -i current build number: 114 device name: krillin channel: ubuntu-touch/rc-proposed/bq-aquaris.en last update: 2015-09-02 08:01:15 version version: 114 version ubuntu: 20150902 version device: 20150821-736d127 version custom: 20150821-887-33-32-vivid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1491484/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1479734] [NEW] After restarting unity8, clicking 'Purchase' button doesn't launch online-accounts-ui dialog
Public bug reported: Prerequisites: The user has not logged in to their Ubuntu One account Steps to reproduce: 1. Stop unity8 '/sbin/initctl/stop unity8' 2. Start unity8 '/sbin/initctl/start unity8' 3. Swipe to the apps scope 4. Scroll down and tap on the Ubuntu Store icon 5. Search for the app 'Riddling' 6. Tap on the purchase button Expected result: online-accounts-ui dialog opens Actual result: Button flashes 'In progress' and the dialog never opens Going back from the preview screen and returning and tapping on the purchase button again will cause the accounts dialog to appear ** Affects: unity-scope-click (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-scope-click in Ubuntu. https://bugs.launchpad.net/bugs/1479734 Title: After restarting unity8, clicking 'Purchase' button doesn't launch online-accounts-ui dialog Status in unity-scope-click package in Ubuntu: New Bug description: Prerequisites: The user has not logged in to their Ubuntu One account Steps to reproduce: 1. Stop unity8 '/sbin/initctl/stop unity8' 2. Start unity8 '/sbin/initctl/start unity8' 3. Swipe to the apps scope 4. Scroll down and tap on the Ubuntu Store icon 5. Search for the app 'Riddling' 6. Tap on the purchase button Expected result: online-accounts-ui dialog opens Actual result: Button flashes 'In progress' and the dialog never opens Going back from the preview screen and returning and tapping on the purchase button again will cause the accounts dialog to appear To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-scope-click/+bug/1479734/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1464414] [NEW] Contact number not filled if full name is entered but number is not selected from drop-down
Public bug reported: Prerequisites: A contact is in the address book with a name and number (e.g. 'Test Tester', '0011223344' 1. Open the messaging application 2. Swipe up to create a new message 3. Enter the full name of the contact (i.e. 'Test Tester') in the To: field 4. Tap on the 'Write a message...' field 5. Enter your message text 6. Tap on Send Expected result: Message is sent successfully (assuming sufficient credit and a valid number). Opening the message info shows the number of the contact Actual result: The message fails to send and opening the message info shows the To: field as blank current build number: 410 device name: krillin channel: ubuntu-touch/rc-proposed/bq-aquaris.en-proposed last update: 2015-06-11 10:06:15 version version: 410 version ubuntu: 20150611 version device: 20150529-8e13c5f version custom: 20150528-722-29-15-vivid ** Affects: messaging-app (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to messaging-app in Ubuntu. https://bugs.launchpad.net/bugs/1464414 Title: Contact number not filled if full name is entered but number is not selected from drop-down Status in messaging-app package in Ubuntu: New Bug description: Prerequisites: A contact is in the address book with a name and number (e.g. 'Test Tester', '0011223344' 1. Open the messaging application 2. Swipe up to create a new message 3. Enter the full name of the contact (i.e. 'Test Tester') in the To: field 4. Tap on the 'Write a message...' field 5. Enter your message text 6. Tap on Send Expected result: Message is sent successfully (assuming sufficient credit and a valid number). Opening the message info shows the number of the contact Actual result: The message fails to send and opening the message info shows the To: field as blank current build number: 410 device name: krillin channel: ubuntu-touch/rc-proposed/bq-aquaris.en-proposed last update: 2015-06-11 10:06:15 version version: 410 version ubuntu: 20150611 version device: 20150529-8e13c5f version custom: 20150528-722-29-15-vivid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/messaging-app/+bug/1464414/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1450730] Re: enter_search_query sometimes fails to open the search box
** Changed in: unity-scope-click (Ubuntu)
Status: New = In Progress
** Changed in: unity-scope-click (Ubuntu)
Assignee: (unassigned) = Brendan Donegan (brendan-donegan)
--
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/1450730
Title:
enter_search_query sometimes fails to open the search box
Status in unity-scope-click package in Ubuntu:
In Progress
Bug description:
It appears that sometimes the enter_search_query AP helper is failing
to click the Search button in the Dash. This means we end up with the
following traceback:
Traceback (most recent call last):
File
/tmp/adt-run.CIYj4V/build.vwJ/real-tree/ubuntu_sanity_tests/tests/test_app_store.py,
line 101, in test_install_free_app
store_scope.enter_search_query('OSMTouch')
File
/tmp/adt-run.CIYj4V/deps/usr/lib/python3/dist-packages/autopilot/logging.py,
line 46, in inner
return f(instance, *args, **kwargs)
File
/tmp/adt-run.CIYj4V/deps/usr/lib/python3/dist-packages/unityclickscope/init.py,
line 95, in enter_search_query
headerContainer.contentY.wait_for(0)
File
/tmp/adt-run.CIYj4V/deps/usr/lib/python3/dist-packages/autopilot/introspection/types.py,
line 180, in wait_for
failure_msg))
AssertionError: After 10.0 seconds test on QQuickFlickable.contentY failed: 0
!= dbus.Double(91.0, variant_level=1)
Checking the helper it looks like it is doing select_single, not
wait_select_single leaving it open to timing issues.
current build number: 201
device name: krillin
channel: ubuntu-touch/devel-proposed
alias: ubuntu-touch/vivid-proposed
last update: 2015-04-30 22:23:07
version version: 201
version ubuntu: 20150430
version device: 20150326-f0c5ba5
version custom: 20150430
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-scope-click/+bug/1450730/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1450730] [NEW] enter_search_query sometimes fails to open the search box
Public bug reported:
It appears that sometimes the enter_search_query AP helper is failing to
click the Search button in the Dash. This means we end up with the
following traceback:
Traceback (most recent call last):
File
/tmp/adt-run.CIYj4V/build.vwJ/real-tree/ubuntu_sanity_tests/tests/test_app_store.py,
line 101, in test_install_free_app
store_scope.enter_search_query('OSMTouch')
File
/tmp/adt-run.CIYj4V/deps/usr/lib/python3/dist-packages/autopilot/logging.py,
line 46, in inner
return f(instance, *args, **kwargs)
File
/tmp/adt-run.CIYj4V/deps/usr/lib/python3/dist-packages/unityclickscope/init.py,
line 95, in enter_search_query
headerContainer.contentY.wait_for(0)
File
/tmp/adt-run.CIYj4V/deps/usr/lib/python3/dist-packages/autopilot/introspection/types.py,
line 180, in wait_for
failure_msg))
AssertionError: After 10.0 seconds test on QQuickFlickable.contentY failed: 0
!= dbus.Double(91.0, variant_level=1)
Checking the helper it looks like it is doing select_single, not
wait_select_single leaving it open to timing issues.
current build number: 201
device name: krillin
channel: ubuntu-touch/devel-proposed
alias: ubuntu-touch/vivid-proposed
last update: 2015-04-30 22:23:07
version version: 201
version ubuntu: 20150430
version device: 20150326-f0c5ba5
version custom: 20150430
** Affects: unity-scope-click (Ubuntu)
Importance: Undecided
Assignee: Brendan Donegan (brendan-donegan)
Status: In Progress
--
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/1450730
Title:
enter_search_query sometimes fails to open the search box
Status in unity-scope-click package in Ubuntu:
In Progress
Bug description:
It appears that sometimes the enter_search_query AP helper is failing
to click the Search button in the Dash. This means we end up with the
following traceback:
Traceback (most recent call last):
File
/tmp/adt-run.CIYj4V/build.vwJ/real-tree/ubuntu_sanity_tests/tests/test_app_store.py,
line 101, in test_install_free_app
store_scope.enter_search_query('OSMTouch')
File
/tmp/adt-run.CIYj4V/deps/usr/lib/python3/dist-packages/autopilot/logging.py,
line 46, in inner
return f(instance, *args, **kwargs)
File
/tmp/adt-run.CIYj4V/deps/usr/lib/python3/dist-packages/unityclickscope/init.py,
line 95, in enter_search_query
headerContainer.contentY.wait_for(0)
File
/tmp/adt-run.CIYj4V/deps/usr/lib/python3/dist-packages/autopilot/introspection/types.py,
line 180, in wait_for
failure_msg))
AssertionError: After 10.0 seconds test on QQuickFlickable.contentY failed: 0
!= dbus.Double(91.0, variant_level=1)
Checking the helper it looks like it is doing select_single, not
wait_select_single leaving it open to timing issues.
current build number: 201
device name: krillin
channel: ubuntu-touch/devel-proposed
alias: ubuntu-touch/vivid-proposed
last update: 2015-04-30 22:23:07
version version: 201
version ubuntu: 20150430
version device: 20150326-f0c5ba5
version custom: 20150430
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-scope-click/+bug/1450730/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1413316] Re: Dialler shows 'No network' even though SIM is present (vivid)
I wouldn't call a phone not being able to make phone calls anything less than Critical! ** Changed in: telepathy-ofono (Ubuntu) Importance: High = Critical -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to telepathy-ofono in Ubuntu. https://bugs.launchpad.net/bugs/1413316 Title: Dialler shows 'No network' even though SIM is present (vivid) Status in the base for Ubuntu mobile products: Confirmed Status in telepathy-ofono package in Ubuntu: Confirmed Bug description: I have a SIM inserted in the first SIM slot, but dialler is showing a 'No network' message and messaging says 'No SIM card selected' when trying to send. The output of /usr/share/ofono/scripts/list-modems seems okay so I'm assuming this is a telepathy-ofono issue. https://pastebin.canonical.com/123899/ ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: telepathy-ofono 0.2+15.04.20141216-0ubuntu1 Uname: Linux 3.4.67 armv7l ApportVersion: 2.15.1-0ubuntu2 Architecture: armhf Date: Wed Jan 21 17:22:33 2015 InstallationDate: Installed on 2015-01-21 (0 days ago) InstallationMedia: Ubuntu Vivid Vervet (development branch) - armhf (20150121-020205) SourcePackage: telepathy-ofono UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1413316/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1414591] Re: Location service toggle in wizard is off by default - used to be on
@Charles - is this during the wizard? It seems to be running after the system is fully booted -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to location-service in Ubuntu. https://bugs.launchpad.net/bugs/1414591 Title: Location service toggle in wizard is off by default - used to be on Status in Indicator Location: New Status in location-service package in Ubuntu: In Progress Bug description: When running the wizard, previously the first check box for selecting whether to enable the location service was on. Now it is off by default which is unexpected. Contents of /var/lib/ubuntu-location-service/config.ini are: http://paste.ubuntu.com/9879658/ ProblemType: Bug DistroRelease: Ubuntu RTM 14.09 Package: ubuntu-location-service-bin 2.1+15.04.20150125~rtm-0ubuntu1 Uname: Linux 3.4.67 armv7l ApportVersion: 2.14.7-0ubuntu8 Architecture: armhf Date: Mon Jan 26 10:06:16 2015 InstallationDate: Installed on 2015-01-26 (0 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20150126-030204) SourcePackage: location-service UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.init.ubuntu.location.service.conf: 2015-01-21T12:40:24 To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-location/+bug/1414591/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1414591] [NEW] Location service toggle in wizard is off by default - used to be on
Public bug reported: When running the wizard, previously the first check box for selecting whether to enable the location service was on. Now it is off by default which is unexpected. Contents of /var/lib/ubuntu-location-service/config.ini are: http://paste.ubuntu.com/9879658/ ProblemType: Bug DistroRelease: Ubuntu RTM 14.09 Package: ubuntu-location-service-bin 2.1+15.04.20150125~rtm-0ubuntu1 Uname: Linux 3.4.67 armv7l ApportVersion: 2.14.7-0ubuntu8 Architecture: armhf Date: Mon Jan 26 10:06:16 2015 InstallationDate: Installed on 2015-01-26 (0 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20150126-030204) SourcePackage: location-service UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.init.ubuntu.location.service.conf: 2015-01-21T12:40:24 ** Affects: location-service (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug armhf utopic ** Description changed: When running the wizard, previously the first check box for selecting whether to enable the location service was on. Now it is off by default which is unexpected. + + Contents of /var/lib/ubuntu-location-service/config.ini are: + http://paste.ubuntu.com/9879658/ ProblemType: Bug DistroRelease: Ubuntu RTM 14.09 Package: ubuntu-location-service-bin 2.1+15.04.20150125~rtm-0ubuntu1 Uname: Linux 3.4.67 armv7l ApportVersion: 2.14.7-0ubuntu8 Architecture: armhf Date: Mon Jan 26 10:06:16 2015 InstallationDate: Installed on 2015-01-26 (0 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20150126-030204) SourcePackage: location-service UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.init.ubuntu.location.service.conf: 2015-01-21T12:40:24 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to location-service in Ubuntu. https://bugs.launchpad.net/bugs/1414591 Title: Location service toggle in wizard is off by default - used to be on Status in location-service package in Ubuntu: New Bug description: When running the wizard, previously the first check box for selecting whether to enable the location service was on. Now it is off by default which is unexpected. Contents of /var/lib/ubuntu-location-service/config.ini are: http://paste.ubuntu.com/9879658/ ProblemType: Bug DistroRelease: Ubuntu RTM 14.09 Package: ubuntu-location-service-bin 2.1+15.04.20150125~rtm-0ubuntu1 Uname: Linux 3.4.67 armv7l ApportVersion: 2.14.7-0ubuntu8 Architecture: armhf Date: Mon Jan 26 10:06:16 2015 InstallationDate: Installed on 2015-01-26 (0 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20150126-030204) SourcePackage: location-service UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.init.ubuntu.location.service.conf: 2015-01-21T12:40:24 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/location-service/+bug/1414591/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1414610] [NEW] Location indicator switches are off and won't switch on if HERE TCs were not accepted in the wizard
Public bug reported: Steps to reproduce: 1. Boot the device and run the wizard 2. On the Location screen select the first checkbox 'Allow apps to use your mobile and Wi-Fi networks to determine your location' 3. Tap Continue and finish the wizard 4. Skip the edges demo and open the location indicator Expected result: Switches are on but HERE TCs are not shown Actual result: Switches are off and toggling them on doesn't work (they switch off after a few seconds), and HERE TCs are not shown ProblemType: Bug DistroRelease: Ubuntu RTM 14.09 Package: indicator-location 13.10.0+14.10.20141007-0ubuntu1 Uname: Linux 3.4.67 armv7l ApportVersion: 2.14.7-0ubuntu8 Architecture: armhf Date: Mon Jan 26 11:28:18 2015 InstallationDate: Installed on 2015-01-26 (0 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20150126-030204) SourcePackage: indicator-location UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: indicator-location (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug armhf utopic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-location in Ubuntu. https://bugs.launchpad.net/bugs/1414610 Title: Location indicator switches are off and won't switch on if HERE TCs were not accepted in the wizard Status in indicator-location package in Ubuntu: New Bug description: Steps to reproduce: 1. Boot the device and run the wizard 2. On the Location screen select the first checkbox 'Allow apps to use your mobile and Wi-Fi networks to determine your location' 3. Tap Continue and finish the wizard 4. Skip the edges demo and open the location indicator Expected result: Switches are on but HERE TCs are not shown Actual result: Switches are off and toggling them on doesn't work (they switch off after a few seconds), and HERE TCs are not shown ProblemType: Bug DistroRelease: Ubuntu RTM 14.09 Package: indicator-location 13.10.0+14.10.20141007-0ubuntu1 Uname: Linux 3.4.67 armv7l ApportVersion: 2.14.7-0ubuntu8 Architecture: armhf Date: Mon Jan 26 11:28:18 2015 InstallationDate: Installed on 2015-01-26 (0 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20150126-030204) SourcePackage: indicator-location UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-location/+bug/1414610/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1414029] Re: HERE asks to download the Android app on first launch
** Attachment added: Android app prompt https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1414029/+attachment/4304402/+files/here-android-app.png -- 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/1414029 Title: HERE asks to download the Android app on first launch Status in webbrowser-app package in Ubuntu: Confirmed Bug description: Prerequisites: HERE webapp has never been launched before Steps to reproduce: 1. Launch HERE 2. Accept location prompt 3. Dismiss prompts until you see the one asking to install the Android app Expected result: This prompt should never be shown since we're on Ubuntu Actual result: It is shown and could confuse users apart from being irrelevant ProblemType: Bug DistroRelease: Ubuntu RTM 14.09 Package: webapp-container 0.23+15.04.20141218~rtm-0ubuntu1 [origin: unknown] Uname: Linux 3.4.67 armv7l ApportVersion: 2.14.7-0ubuntu8 Architecture: armhf Date: Fri Jan 23 14:44:40 2015 InstallationDate: Installed on 2015-01-23 (0 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20150123-030204) SourcePackage: webbrowser-app UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1414029/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1414029] [NEW] HERE asks to download the Android app on first launch
Public bug reported: Prerequisites: HERE webapp has never been launched before Steps to reproduce: 1. Launch HERE 2. Accept location prompt 3. Dismiss prompts until you see the one asking to install the Android app Expected result: This prompt should never be shown since we're on Ubuntu Actual result: It is shown and could confuse users apart from being irrelevant ProblemType: Bug DistroRelease: Ubuntu RTM 14.09 Package: webapp-container 0.23+15.04.20141218~rtm-0ubuntu1 [origin: unknown] Uname: Linux 3.4.67 armv7l ApportVersion: 2.14.7-0ubuntu8 Architecture: armhf Date: Fri Jan 23 14:44:40 2015 InstallationDate: Installed on 2015-01-23 (0 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20150123-030204) SourcePackage: webbrowser-app UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: webbrowser-app (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug armhf third-party-packages utopic -- 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/1414029 Title: HERE asks to download the Android app on first launch Status in webbrowser-app package in Ubuntu: New Bug description: Prerequisites: HERE webapp has never been launched before Steps to reproduce: 1. Launch HERE 2. Accept location prompt 3. Dismiss prompts until you see the one asking to install the Android app Expected result: This prompt should never be shown since we're on Ubuntu Actual result: It is shown and could confuse users apart from being irrelevant ProblemType: Bug DistroRelease: Ubuntu RTM 14.09 Package: webapp-container 0.23+15.04.20141218~rtm-0ubuntu1 [origin: unknown] Uname: Linux 3.4.67 armv7l ApportVersion: 2.14.7-0ubuntu8 Architecture: armhf Date: Fri Jan 23 14:44:40 2015 InstallationDate: Installed on 2015-01-23 (0 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20150123-030204) SourcePackage: webbrowser-app UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1414029/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1413682] [NEW] Translucent black square shown behind 'You have no contacts' dialog
Public bug reported: Ensure that Contacts has never been opened before running this test Steps to reproduce: 1. Open Contacts 2. Wait for the 'You have no contacts' dialog to appear Expected result: Dialog is displayed over the Contacts app without visual glitches Actual result: Behind the dialog is a translucent black square as shown in the attached screenshot ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: address-book-app 0.2+15.04.20150120-0ubuntu1 Uname: Linux 3.4.67 armv7l ApportVersion: 2.15.1-0ubuntu2 Architecture: armhf Date: Thu Jan 22 17:46:13 2015 InstallationDate: Installed on 2015-01-22 (0 days ago) InstallationMedia: Ubuntu Vivid Vervet (development branch) - armhf (20150122-020204) SourcePackage: address-book-app UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: address-book-app (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug armhf vivid ** Attachment added: no contacts dialog black square https://bugs.launchpad.net/bugs/1413682/+attachment/4303717/+files/no_contacts.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to address-book-app in Ubuntu. https://bugs.launchpad.net/bugs/1413682 Title: Translucent black square shown behind 'You have no contacts' dialog Status in address-book-app package in Ubuntu: New Bug description: Ensure that Contacts has never been opened before running this test Steps to reproduce: 1. Open Contacts 2. Wait for the 'You have no contacts' dialog to appear Expected result: Dialog is displayed over the Contacts app without visual glitches Actual result: Behind the dialog is a translucent black square as shown in the attached screenshot ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: address-book-app 0.2+15.04.20150120-0ubuntu1 Uname: Linux 3.4.67 armv7l ApportVersion: 2.15.1-0ubuntu2 Architecture: armhf Date: Thu Jan 22 17:46:13 2015 InstallationDate: Installed on 2015-01-22 (0 days ago) InstallationMedia: Ubuntu Vivid Vervet (development branch) - armhf (20150122-020204) SourcePackage: address-book-app UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/address-book-app/+bug/1413682/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1413284] [NEW] Terms 'Social' and 'IM' used interchangeably in address book
Public bug reported: Steps to reproduce: 1. Open Contacts 2. Create a new contact by swiping from the bottom edge 3. Tap on Add Field 4. Observe that there is an option called Social, tap on it 5. A field is added titled 'IM' with the text 'Enter a social alias' and the type 'Skype' 6. Enter something here and a First and Last name for the contact 7. From the contact list tap on the new contact and tap on the view contact button 8. Observe that there is a field with the name 'Social' 9. Tap on the 'Edit' icon in the top-right corner 10. Observe that there is a field with the name 'IM' Expected result: In steps 4,5,8 and 10 the term used should be the same Actual result: The term is different in 4 and 8 vs 5 and 10 ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: address-book-app 0.2+15.04.20150120-0ubuntu1 Uname: Linux 3.4.67 armv7l ApportVersion: 2.15.1-0ubuntu2 Architecture: armhf Date: Wed Jan 21 15:45:36 2015 InstallationDate: Installed on 2015-01-21 (0 days ago) InstallationMedia: Ubuntu Vivid Vervet (development branch) - armhf (20150121-020205) SourcePackage: address-book-app UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: address-book-app (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug armhf vivid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to address-book-app in Ubuntu. https://bugs.launchpad.net/bugs/1413284 Title: Terms 'Social' and 'IM' used interchangeably in address book Status in address-book-app package in Ubuntu: New Bug description: Steps to reproduce: 1. Open Contacts 2. Create a new contact by swiping from the bottom edge 3. Tap on Add Field 4. Observe that there is an option called Social, tap on it 5. A field is added titled 'IM' with the text 'Enter a social alias' and the type 'Skype' 6. Enter something here and a First and Last name for the contact 7. From the contact list tap on the new contact and tap on the view contact button 8. Observe that there is a field with the name 'Social' 9. Tap on the 'Edit' icon in the top-right corner 10. Observe that there is a field with the name 'IM' Expected result: In steps 4,5,8 and 10 the term used should be the same Actual result: The term is different in 4 and 8 vs 5 and 10 ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: address-book-app 0.2+15.04.20150120-0ubuntu1 Uname: Linux 3.4.67 armv7l ApportVersion: 2.15.1-0ubuntu2 Architecture: armhf Date: Wed Jan 21 15:45:36 2015 InstallationDate: Installed on 2015-01-21 (0 days ago) InstallationMedia: Ubuntu Vivid Vervet (development branch) - armhf (20150121-020205) SourcePackage: address-book-app UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/address-book-app/+bug/1413284/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1413316] [NEW] Dialler shows 'No network' even though SIM is present
Public bug reported: I have a SIM inserted in the first SIM slot, but dialler is showing a 'No network' message and messaging says 'No SIM card selected' when trying to send. The output of /usr/share/ofono/scripts/list-modems seems okay so I'm assuming this is a telepathy-ofono issue. https://pastebin.canonical.com/123899/ ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: telepathy-ofono 0.2+15.04.20141216-0ubuntu1 Uname: Linux 3.4.67 armv7l ApportVersion: 2.15.1-0ubuntu2 Architecture: armhf Date: Wed Jan 21 17:22:33 2015 InstallationDate: Installed on 2015-01-21 (0 days ago) InstallationMedia: Ubuntu Vivid Vervet (development branch) - armhf (20150121-020205) SourcePackage: telepathy-ofono UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: telepathy-ofono (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug armhf vivid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to telepathy-ofono in Ubuntu. https://bugs.launchpad.net/bugs/1413316 Title: Dialler shows 'No network' even though SIM is present Status in telepathy-ofono package in Ubuntu: New Bug description: I have a SIM inserted in the first SIM slot, but dialler is showing a 'No network' message and messaging says 'No SIM card selected' when trying to send. The output of /usr/share/ofono/scripts/list-modems seems okay so I'm assuming this is a telepathy-ofono issue. https://pastebin.canonical.com/123899/ ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: telepathy-ofono 0.2+15.04.20141216-0ubuntu1 Uname: Linux 3.4.67 armv7l ApportVersion: 2.15.1-0ubuntu2 Architecture: armhf Date: Wed Jan 21 17:22:33 2015 InstallationDate: Installed on 2015-01-21 (0 days ago) InstallationMedia: Ubuntu Vivid Vervet (development branch) - armhf (20150121-020205) SourcePackage: telepathy-ofono UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/telepathy-ofono/+bug/1413316/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1412524] [NEW] Keyboard doesn't open in 2-step verification dialog after opening notification bar
Public bug reported: Steps to reproduce: 1. Open System Settings 2. Open Accounts 3. Tap on Google 4. Enter correct email and password for an account with 2-step verification enabled and tap 'Sign-in' 5. Tap on 'Enter code' field to focus 6. After receiving the 2-step verification message, pull down the indicator until the keyboard is closed, then push it back up 7. Tap on the 'Enter code' field again Expected result: Keyboard appears to enter the code Actual result: The keyboard doesn't appear. After pushing the notification bar back up we can notice a flicker of the keyboard attempting to reveal itself at the bottom of the screen ProblemType: Bug DistroRelease: Ubuntu RTM 14.09 Package: ubuntu-system-settings-online-accounts 0.5+15.04.20150105~rtm-0ubuntu1 Uname: Linux 3.4.67 armv7l ApportVersion: 2.14.7-0ubuntu8 Architecture: armhf Date: Mon Jan 19 17:21:27 2015 InstallationDate: Installed on 2015-01-19 (0 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20150119-030204) SourcePackage: ubuntu-system-settings-online-accounts UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubuntu-system-settings-online-accounts (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug armhf utopic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-system-settings- online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1412524 Title: Keyboard doesn't open in 2-step verification dialog after opening notification bar Status in ubuntu-system-settings-online-accounts package in Ubuntu: New Bug description: Steps to reproduce: 1. Open System Settings 2. Open Accounts 3. Tap on Google 4. Enter correct email and password for an account with 2-step verification enabled and tap 'Sign-in' 5. Tap on 'Enter code' field to focus 6. After receiving the 2-step verification message, pull down the indicator until the keyboard is closed, then push it back up 7. Tap on the 'Enter code' field again Expected result: Keyboard appears to enter the code Actual result: The keyboard doesn't appear. After pushing the notification bar back up we can notice a flicker of the keyboard attempting to reveal itself at the bottom of the screen ProblemType: Bug DistroRelease: Ubuntu RTM 14.09 Package: ubuntu-system-settings-online-accounts 0.5+15.04.20150105~rtm-0ubuntu1 Uname: Linux 3.4.67 armv7l ApportVersion: 2.14.7-0ubuntu8 Architecture: armhf Date: Mon Jan 19 17:21:27 2015 InstallationDate: Installed on 2015-01-19 (0 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20150119-030204) SourcePackage: ubuntu-system-settings-online-accounts UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-system-settings-online-accounts/+bug/1412524/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1411782] Re: Camera app crashes if unfocused while loading
** Attachment added: camera-app crash https://bugs.launchpad.net/ubuntu/+source/camera-app/+bug/1411782/+attachment/4300139/+files/_opt_click.ubuntu.com_com.ubuntu.camera_3.0.0.461_camera-app.32011.crash -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to camera-app in Ubuntu. https://bugs.launchpad.net/bugs/1411782 Title: Camera app crashes if unfocused while loading Status in camera-app package in Ubuntu: New Bug description: Steps to reproduced: 1. Open camera app 2. While it is loading unfocus the window Expected result: It continues to load in the background (or suspends gracefully) Actual result: A crash file is generated (attached) and a zombie window is present in the task switcher for a short period of time, which eventually disappears. Trying to launch the app before that will fail. current build number: 200 device name: krillin channel: ubuntu-touch/ubuntu-rtm/14.09-proposed last update: 2015-01-16 11:51:53 version version: 200 version ubuntu: 20150116 version device: 20150113-2a2e4c5 version custom: 20150112-494-23-173 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/camera-app/+bug/1411782/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1411782] [NEW] Camera app crashes if unfocused while loading
Public bug reported: Steps to reproduced: 1. Open camera app 2. While it is loading unfocus the window Expected result: It continues to load in the background (or suspends gracefully) Actual result: A crash file is generated (attached) and a zombie window is present in the task switcher for a short period of time, which eventually disappears. Trying to launch the app before that will fail. current build number: 200 device name: krillin channel: ubuntu-touch/ubuntu-rtm/14.09-proposed last update: 2015-01-16 11:51:53 version version: 200 version ubuntu: 20150116 version device: 20150113-2a2e4c5 version custom: 20150112-494-23-173 ** Affects: camera-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 camera-app in Ubuntu. https://bugs.launchpad.net/bugs/1411782 Title: Camera app crashes if unfocused while loading Status in camera-app package in Ubuntu: New Bug description: Steps to reproduced: 1. Open camera app 2. While it is loading unfocus the window Expected result: It continues to load in the background (or suspends gracefully) Actual result: A crash file is generated (attached) and a zombie window is present in the task switcher for a short period of time, which eventually disappears. Trying to launch the app before that will fail. current build number: 200 device name: krillin channel: ubuntu-touch/ubuntu-rtm/14.09-proposed last update: 2015-01-16 11:51:53 version version: 200 version ubuntu: 20150116 version device: 20150113-2a2e4c5 version custom: 20150112-494-23-173 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/camera-app/+bug/1411782/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1390136] Re: need a transition state for indicators reflecting laggy backends
The fix for https://bugs.launchpad.net/ubuntu/+source/indicator- network/+bug/1393488 improves the visual behaviour but the recommendation is that this still gets redesigned to provide a more robust solution -- 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/1390136 Title: need a transition state for indicators reflecting laggy backends Status in the base for Ubuntu mobile products: Confirmed Status in Ubuntu UX bugs: Fix Committed Status in indicator-network package in Ubuntu: Confirmed Status in ubuntu-system-settings package in Ubuntu: Confirmed Status in unity8 package in Ubuntu: Triaged Status in indicator-network source package in Utopic: Confirmed Status in ubuntu-system-settings source package in Utopic: Confirmed Status in indicator-network source package in Vivid: Confirmed Status in ubuntu-system-settings source package in Vivid: Confirmed Status in unity8 source package in Vivid: Triaged Status in indicator-network package in Ubuntu RTM: New Status in ubuntu-system-settings package in Ubuntu RTM: New Status in unity8 package in Ubuntu RTM: New Bug description: spawned from efforts in bug 1336715 because the user's input toggle for airplane mode is both a reflection of user intent the state of the backendand the backend is unfortunately variable lengthy to change (anywhere from 1 to ~10+ seconds sometimes) we need to have an intermediate/transition statee.g. toggle to airplane mode onthen animate somehow that there's a transition happening, until it either fails/succeeds comment from dizzypaty Between the user’s action of toggling the airplane switcher on and/or off and the backend updating the state, the indicator icon displayed on the statusbar should be the following: network-idle.svg (https://drive.google.com/drive/#folders/0BzbnWoHmYF3aZTA4WHNPYW1jeUE/0BzbnWoHmYF3aS2pVejVicktrdm8/0BzbnWoHmYF3ablBITVByRnpzdEk). Desired resolution Summary: the interface should immediately respond to user input confirming the action, even if the backend takes up to 20 seconds to actually change state. Having the UI and backend out of sync for up to 30 seconds is not a problem, as long as it always goes back into sync after this delay. 1.When the user changes the flight mode toggle switch it should instantly change state. 2.The backend should then be informed of the state change. 3.Up to 30 seconds later the backend completes the state change Note: The cellular connection indicator should always display the backend state, not the current flight mode toggle switch state Variation - user switches the flight mode toggle on and off rapidly. Once a flight mode state change request has been sent to the backend but before a conformation that the state change is complete is received, all further user interactions should be buffered on the client. When the client receives conformation of the state change from the backend it should check to see if the state is in sync with its buffer. If it is in sync nothing happens and the buffer is cleared. If it is not in sync another state change signal is sent to the backend and the buffer is cleared. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1390136/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1401563] [NEW] Playing a video from the photo roll exhibits odd behaviour if a video is currently loaded in the media player
Public bug reported: Prerequisites: There must be two videos loaded on the phone, at least one which must have been taken with the phones camera and stored in the photo roll Steps to reproduce: 1. Navigate to the Videos scope 2. Tap on a video 3. Tap on the Play button 4. Let the video play for some time and then open the camera application 5. Swipe left to get to the photo roll and swipe to any video in the photo roll 6. Tap on the play button Expected result: The video from the photo roll plays properly in the media player Actual result: The video is corrupted in some way - usually the video that was already loaded is shown as a still but with the sound of the video from the photo roll. Sometimes the correct video will be played but in the wrong aspect ratio. current build number: 176 device name: krillin channel: ubuntu-touch/ubuntu-rtm/14.09-proposed last update: 2014-12-11 14:44:52 version version: 176 version ubuntu: 20141211 version device: 20141209-cae2b5f version custom: 20141119-442-21-160 ** Affects: camera-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 camera-app in Ubuntu. https://bugs.launchpad.net/bugs/1401563 Title: Playing a video from the photo roll exhibits odd behaviour if a video is currently loaded in the media player Status in camera-app package in Ubuntu: New Bug description: Prerequisites: There must be two videos loaded on the phone, at least one which must have been taken with the phones camera and stored in the photo roll Steps to reproduce: 1. Navigate to the Videos scope 2. Tap on a video 3. Tap on the Play button 4. Let the video play for some time and then open the camera application 5. Swipe left to get to the photo roll and swipe to any video in the photo roll 6. Tap on the play button Expected result: The video from the photo roll plays properly in the media player Actual result: The video is corrupted in some way - usually the video that was already loaded is shown as a still but with the sound of the video from the photo roll. Sometimes the correct video will be played but in the wrong aspect ratio. current build number: 176 device name: krillin channel: ubuntu-touch/ubuntu-rtm/14.09-proposed last update: 2014-12-11 14:44:52 version version: 176 version ubuntu: 20141211 version device: 20141209-cae2b5f version custom: 20141119-442-21-160 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/camera-app/+bug/1401563/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1391522] Re: tel:/// URLs dispatched when phone is locked are not respected
The duplicate bug has clear reproduction steps -- 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/1391522 Title: tel:/// URLs dispatched when phone is locked are not respected Status in Dialer app for Ubuntu Touch: New Status in “dialer-app” package in Ubuntu: Confirmed Bug description: Steps to reproduce: * have a passcode-locked phone * run: $ gdbus call -e -d com.canonical.URLDispatcher -o /com/canonical/URLDispatcher -m com.canonical.URLDispatcher.DispatchURL 'tel:///1234' '' * type the passcode Expected: * dialer opens with 1234 typed in the number box Current: * dialer opens blank or with 1234 that resets to blank a split second later ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: dialer-app 0.1+15.04.20141106-0ubuntu1 Uname: Linux 3.4.67 armv7l ApportVersion: 2.14.7-0ubuntu10 Architecture: armhf Date: Tue Nov 11 14:29:21 2014 InstallationDate: Installed on 2014-11-11 (0 days ago) InstallationMedia: Ubuntu Vivid Vervet (development branch) - armhf (2014-020204) SourcePackage: dialer-app UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/dialer-app/+bug/1391522/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1392347] [NEW] Pause button changes to Play after low-battery notification when a video is playing
Public bug reported: Steps to reproduce: 1. Open a video in mediaplayer-app 2. Enable the mock battery: gdbus call --session --dest com.canonical.indicator.power \ --object-path /com/canonical/indicator/power/Testing \ --method org.freedesktop.DBus.Properties.Set \ com.canonical.indicator.power.Testing \ MockBatteryEnabled \ true 3. Trigger the low battery notification: gdbus call --session --dest com.canonical.indicator.power \ --object-path /com/canonical/indicator/power/Testing \ --method org.freedesktop.DBus.Properties.Set \ com.canonical.indicator.power.Testing \ MockBatteryLevel \ uint32 10 4. Dismiss the Low battery notification Expected result: Video resumes playing and Pause button is available in bottom left corner Actual result: Video resumes playing but Pause button has changed to Play, which is clearly wrong since the video is playing ProblemType: Bug DistroRelease: Ubuntu RTM 14.09 Package: mediaplayer-app 0.20.5+14.10.20141015-0ubuntu1 Uname: Linux 3.4.67 armv7l ApportVersion: 2.14.7-0ubuntu8 Architecture: armhf Date: Thu Nov 13 15:01:43 2014 InstallationDate: Installed on 2014-11-12 (0 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20141112-181954) SourcePackage: mediaplayer-app UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: mediaplayer-app (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug armhf qa-promotion utopic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mediaplayer-app in Ubuntu. https://bugs.launchpad.net/bugs/1392347 Title: Pause button changes to Play after low-battery notification when a video is playing Status in “mediaplayer-app” package in Ubuntu: New Bug description: Steps to reproduce: 1. Open a video in mediaplayer-app 2. Enable the mock battery: gdbus call --session --dest com.canonical.indicator.power \ --object-path /com/canonical/indicator/power/Testing \ --method org.freedesktop.DBus.Properties.Set \ com.canonical.indicator.power.Testing \ MockBatteryEnabled \ true 3. Trigger the low battery notification: gdbus call --session --dest com.canonical.indicator.power \ --object-path /com/canonical/indicator/power/Testing \ --method org.freedesktop.DBus.Properties.Set \ com.canonical.indicator.power.Testing \ MockBatteryLevel \ uint32 10 4. Dismiss the Low battery notification Expected result: Video resumes playing and Pause button is available in bottom left corner Actual result: Video resumes playing but Pause button has changed to Play, which is clearly wrong since the video is playing ProblemType: Bug DistroRelease: Ubuntu RTM 14.09 Package: mediaplayer-app 0.20.5+14.10.20141015-0ubuntu1 Uname: Linux 3.4.67 armv7l ApportVersion: 2.14.7-0ubuntu8 Architecture: armhf Date: Thu Nov 13 15:01:43 2014 InstallationDate: Installed on 2014-11-12 (0 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20141112-181954) SourcePackage: mediaplayer-app UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mediaplayer-app/+bug/1392347/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1388976] Re: [Time Date] After switching from Manual time setting back to Automatic, the clock does not update until rebooted
*** This bug is a duplicate of bug 1392292 *** https://bugs.launchpad.net/bugs/1392292 ** This bug has been marked a duplicate of bug 1392292 Clock doesn't update when switching time from manual to automatic -- 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/1388976 Title: [Time Date] After switching from Manual time setting back to Automatic, the clock does not update until rebooted Status in “indicator-datetime” package in Ubuntu: New Bug description: Steps to reproduce: 1. Open System Settings 2. Open the Time Date panel 3. Set 'Set the time and date:' to 'Manually' 4. Tap on the date and time label and set the date and time to something in the future (a few months ahead) 5. Go back and wait for the time indicator to update 6. Set 'Set the time and date:' to Automatically 7. Go back and wait for the time indicator to update again Expected result: The indicator reverts back to the previous time Actual result: The indicator never updates the time until the device is rebooted ProblemType: Bug DistroRelease: Ubuntu RTM 14.09 Package: indicator-datetime 13.10.0+14.10.20141009-0ubuntu1 Uname: Linux 3.4.67 armv7l ApportVersion: 2.14.7-0ubuntu8 Architecture: armhf Date: Fri Dec 5 21:21:42 2014 InstallationDate: Installed on 2014-10-31 (35 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20141031-175022) SourcePackage: indicator-datetime UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1388976/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1392405] [NEW] MTP device cannot be mounted after some time
Public bug reported: It's hard to get exact steps for this, but basically the behaviour I'm seeing is that if I leave the device disconnected, after a while (10-15 minutes, when I go to plug it back in, it is not mounted. Then no matter how many times I unplug and plug the device it will never be mounted. When I reboot it works again - for another 10-15 minutes then it breaks again in the same way. ProblemType: Bug DistroRelease: Ubuntu RTM 14.09 Package: libmtpserver1 0.0.4+15.04.20141104~rtm-0ubuntu1 Uname: Linux 3.4.67 armv7l ApportVersion: 2.14.7-0ubuntu8 Architecture: armhf Date: Thu Nov 13 16:52:46 2014 InstallationDate: Installed on 2014-11-12 (0 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20141112-181954) SourcePackage: mtp UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: mtp (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug armhf qa-promotion utopic ** Attachment added: mtp-server.log https://bugs.launchpad.net/bugs/1392405/+attachment/4260040/+files/mtp-server.log ** Tags added: qa-promotion -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mtp in Ubuntu. https://bugs.launchpad.net/bugs/1392405 Title: MTP device cannot be mounted after some time Status in “mtp” package in Ubuntu: New Bug description: It's hard to get exact steps for this, but basically the behaviour I'm seeing is that if I leave the device disconnected, after a while (10-15 minutes, when I go to plug it back in, it is not mounted. Then no matter how many times I unplug and plug the device it will never be mounted. When I reboot it works again - for another 10-15 minutes then it breaks again in the same way. ProblemType: Bug DistroRelease: Ubuntu RTM 14.09 Package: libmtpserver1 0.0.4+15.04.20141104~rtm-0ubuntu1 Uname: Linux 3.4.67 armv7l ApportVersion: 2.14.7-0ubuntu8 Architecture: armhf Date: Thu Nov 13 16:52:46 2014 InstallationDate: Installed on 2014-11-12 (0 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20141112-181954) SourcePackage: mtp UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mtp/+bug/1392405/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1392405] Re: MTP device cannot be mounted after some time
** Description changed: It's hard to get exact steps for this, but basically the behaviour I'm seeing is that if I leave the device disconnected, after a while (10-15 minutes, when I go to plug it back in, it is not mounted. Then no matter how many times I unplug and plug the device it will never be mounted. When I reboot it works again - for another 10-15 minutes then it breaks again in the same way. STEPS: 1. Connect the phone via mtp ensure you can see content on both phone and sd card 2. Unplug the phone 3. Leave the phone to one side till the screen blanks 4. Now time it for 15 minutes 5. Plug the phone back in. 6. Now try and connect to the device via mtp You now get an error message from nautilus that you can't connect to - mtp. - + mtp, and 'ls $XDG_RUNTIME_DIR/gvfs' on the host contains nothing when it + should contain the MTP device. Also on the phone 'status mtp-server' + shows stopped/waiting. Restarting mtp-server and replugging, or + rebooting the device revives things. ProblemType: Bug DistroRelease: Ubuntu RTM 14.09 Package: libmtpserver1 0.0.4+15.04.20141104~rtm-0ubuntu1 Uname: Linux 3.4.67 armv7l ApportVersion: 2.14.7-0ubuntu8 Architecture: armhf Date: Thu Nov 13 16:52:46 2014 InstallationDate: Installed on 2014-11-12 (0 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20141112-181954) SourcePackage: mtp UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mtp in Ubuntu. https://bugs.launchpad.net/bugs/1392405 Title: MTP device cannot be mounted after some time Status in “mtp” package in Ubuntu: Confirmed Bug description: It's hard to get exact steps for this, but basically the behaviour I'm seeing is that if I leave the device disconnected, after a while (10-15 minutes, when I go to plug it back in, it is not mounted. Then no matter how many times I unplug and plug the device it will never be mounted. When I reboot it works again - for another 10-15 minutes then it breaks again in the same way. STEPS: 1. Connect the phone via mtp ensure you can see content on both phone and sd card 2. Unplug the phone 3. Leave the phone to one side till the screen blanks 4. Now time it for 15 minutes 5. Plug the phone back in. 6. Now try and connect to the device via mtp You now get an error message from nautilus that you can't connect to mtp, and 'ls $XDG_RUNTIME_DIR/gvfs' on the host contains nothing when it should contain the MTP device. Also on the phone 'status mtp- server' shows stopped/waiting. Restarting mtp-server and replugging, or rebooting the device revives things. ProblemType: Bug DistroRelease: Ubuntu RTM 14.09 Package: libmtpserver1 0.0.4+15.04.20141104~rtm-0ubuntu1 Uname: Linux 3.4.67 armv7l ApportVersion: 2.14.7-0ubuntu8 Architecture: armhf Date: Thu Nov 13 16:52:46 2014 InstallationDate: Installed on 2014-11-12 (0 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20141112-181954) SourcePackage: mtp UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mtp/+bug/1392405/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1391909] [NEW] Caller number not loaded in Dialler when Call Back or phone icon is clicked in missed call notification and the device is locked
Public bug reported: Steps to reproduce: 1. Place a call to the device and hang up on the other end (to generate a missed call notification) 2. Ensure the greeter is locked 3. Swipe down on the notifications indicator (message icon) 4. Tap on the missed call 5. Tap on Calll Back 6. Unlock the screen Expected result: Dialler application opens with the number loaded ready to call Actual result: Dialler application opens but the number is not loaded N.B. At step 4 we can tap on the phone icon in the missed call notification to get the same effect, it appears to be functionally equivalent to the Call Back button ProblemType: Bug DistroRelease: Ubuntu RTM 14.09 Package: indicator-messages 13.10.1+14.10.20141007-0ubuntu1 Uname: Linux 3.4.67 armv7l ApportVersion: 2.14.7-0ubuntu8 Architecture: armhf Date: Wed Nov 12 14:50:42 2014 InstallationDate: Installed on 2014-11-12 (0 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20141112-030205) SourcePackage: indicator-messages UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: indicator-messages (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug armhf qa-manual-testing utopic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-messages in Ubuntu. https://bugs.launchpad.net/bugs/1391909 Title: Caller number not loaded in Dialler when Call Back or phone icon is clicked in missed call notification and the device is locked Status in “indicator-messages” package in Ubuntu: New Bug description: Steps to reproduce: 1. Place a call to the device and hang up on the other end (to generate a missed call notification) 2. Ensure the greeter is locked 3. Swipe down on the notifications indicator (message icon) 4. Tap on the missed call 5. Tap on Calll Back 6. Unlock the screen Expected result: Dialler application opens with the number loaded ready to call Actual result: Dialler application opens but the number is not loaded N.B. At step 4 we can tap on the phone icon in the missed call notification to get the same effect, it appears to be functionally equivalent to the Call Back button ProblemType: Bug DistroRelease: Ubuntu RTM 14.09 Package: indicator-messages 13.10.1+14.10.20141007-0ubuntu1 Uname: Linux 3.4.67 armv7l ApportVersion: 2.14.7-0ubuntu8 Architecture: armhf Date: Wed Nov 12 14:50:42 2014 InstallationDate: Installed on 2014-11-12 (0 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20141112-030205) SourcePackage: indicator-messages UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-messages/+bug/1391909/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1391909] Re: Caller number not loaded in Dialler when Call Back or phone icon is clicked in missed call notification and the device is locked
** Description changed: Steps to reproduce: 1. Place a call to the device and hang up on the other end (to generate a missed call notification) 2. Ensure the greeter is locked 3. Swipe down on the notifications indicator (message icon) 4. Tap on the missed call - 5. Tap on Calll Back + 5. Tap on Call Back 6. Unlock the screen Expected result: Dialler application opens with the number loaded ready to call Actual result: - Dialler application opens but the number is not loaded N.B. At step 4 we can tap on the phone icon in the missed call notification to get the same effect, it appears to be functionally equivalent to the Call Back button ProblemType: Bug DistroRelease: Ubuntu RTM 14.09 Package: indicator-messages 13.10.1+14.10.20141007-0ubuntu1 Uname: Linux 3.4.67 armv7l ApportVersion: 2.14.7-0ubuntu8 Architecture: armhf Date: Wed Nov 12 14:50:42 2014 InstallationDate: Installed on 2014-11-12 (0 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20141112-030205) SourcePackage: indicator-messages UpgradeStatus: No upgrade log present (probably fresh install) ** Also affects: dialer-app (Ubuntu) Importance: Undecided Status: New ** Summary changed: - Caller number not loaded in Dialler when Call Back or phone icon is clicked in missed call notification and the device is locked + Caller number not loaded in Dialer when Call Back or phone icon is clicked in missed call notification and the device is locked ** Summary changed: - Caller number not loaded in Dialer when Call Back or phone icon is clicked in missed call notification and the device is locked + Caller number not loaded in dialler when Call Back or phone icon is clicked in missed call notification and the device is locked -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-messages in Ubuntu. https://bugs.launchpad.net/bugs/1391909 Title: Caller number not loaded in dialler when Call Back or phone icon is clicked in missed call notification and the device is locked Status in “dialer-app” package in Ubuntu: New Status in “indicator-messages” package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Place a call to the device and hang up on the other end (to generate a missed call notification) 2. Ensure the greeter is locked 3. Swipe down on the notifications indicator (message icon) 4. Tap on the missed call 5. Tap on Call Back 6. Unlock the screen Expected result: Dialler application opens with the number loaded ready to call Actual result: Dialler application opens but the number is not loaded N.B. At step 4 we can tap on the phone icon in the missed call notification to get the same effect, it appears to be functionally equivalent to the Call Back button ProblemType: Bug DistroRelease: Ubuntu RTM 14.09 Package: indicator-messages 13.10.1+14.10.20141007-0ubuntu1 Uname: Linux 3.4.67 armv7l ApportVersion: 2.14.7-0ubuntu8 Architecture: armhf Date: Wed Nov 12 14:50:42 2014 InstallationDate: Installed on 2014-11-12 (0 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20141112-030205) SourcePackage: indicator-messages UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dialer-app/+bug/1391909/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1391954] [NEW] indicator-sound not running on first boot
Public bug reported: Steps to reproduce: 1. Boot the device after a fresh flash with --wipe or --bootstrap 2. Complete the wizard steps 3. Check the indicators for the presence of the sound indicator Expected result: Sound indicator is present and running Actual result: Indicator is not present. There is a placeholder for it on the menu as shown in http://people.canonical.com/~brendan-donegan/indicator- sound.png Running 'status indicator-sound' shows it is stopped ProblemType: Bug DistroRelease: Ubuntu RTM 14.09 Package: indicator-sound 12.10.2+14.10.20141021~rtm-0ubuntu1 Uname: Linux 3.4.67 armv7l ApportVersion: 2.14.7-0ubuntu8 Architecture: armhf Date: Wed Nov 12 16:26:28 2014 InstallationDate: Installed on 2014-11-12 (0 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20141112-135345) SourcePackage: indicator-sound UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: indicator-sound (Ubuntu) Importance: Critical Status: New ** Tags: apport-bug armhf qa-sanity utopic ** Changed in: indicator-sound (Ubuntu) Importance: Undecided = Critical -- 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/1391954 Title: indicator-sound not running on first boot Status in “indicator-sound” package in Ubuntu: New Bug description: Steps to reproduce: 1. Boot the device after a fresh flash with --wipe or --bootstrap 2. Complete the wizard steps 3. Check the indicators for the presence of the sound indicator Expected result: Sound indicator is present and running Actual result: Indicator is not present. There is a placeholder for it on the menu as shown in http://people.canonical.com/~brendan-donegan/indicator- sound.png Running 'status indicator-sound' shows it is stopped ProblemType: Bug DistroRelease: Ubuntu RTM 14.09 Package: indicator-sound 12.10.2+14.10.20141021~rtm-0ubuntu1 Uname: Linux 3.4.67 armv7l ApportVersion: 2.14.7-0ubuntu8 Architecture: armhf Date: Wed Nov 12 16:26:28 2014 InstallationDate: Installed on 2014-11-12 (0 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20141112-135345) SourcePackage: indicator-sound UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-sound/+bug/1391954/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1391493] [NEW] Location tagging doesn't work for videos
Public bug reported: Steps to reproduce: 1. Open the Camera application 2. Switch to Video mode 3. Swipe up to reveal the sub-controls 4. Tap on Location 5. Tap On 6. Wait for several minutes to allow a fix to be retrieved 7. Record a short video Expected result: When viewing EXIF data for the video, location information is present Actual result: When viewing EXIF data, location information is not present ** Affects: camera-app (Ubuntu) Importance: Undecided Status: New ** Tags: qa-daily-testing -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to camera-app in Ubuntu. https://bugs.launchpad.net/bugs/1391493 Title: Location tagging doesn't work for videos Status in “camera-app” package in Ubuntu: New Bug description: Steps to reproduce: 1. Open the Camera application 2. Switch to Video mode 3. Swipe up to reveal the sub-controls 4. Tap on Location 5. Tap On 6. Wait for several minutes to allow a fix to be retrieved 7. Record a short video Expected result: When viewing EXIF data for the video, location information is present Actual result: When viewing EXIF data, location information is not present To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/camera-app/+bug/1391493/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1390510] [NEW] Camera app crashes
Public bug reported: There have been a lot of reports of camera-app crashes, most notably they are happening consistently on the CI dashboard. Attached is one of the crash files, but others can be added if needed. This appears to have been happening for quite a while. There are no clear reproduction steps. http://people.canonical.com/~brendan- donegan/_usr_share_click_preinstalled_com.ubuntu.camera_3.0.0 .412_camera-app.32011.crash ** Affects: camera-app (Ubuntu) Importance: Undecided Status: New ** Tags: qa-daily-testing -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to camera-app in Ubuntu. https://bugs.launchpad.net/bugs/1390510 Title: Camera app crashes Status in “camera-app” package in Ubuntu: New Bug description: There have been a lot of reports of camera-app crashes, most notably they are happening consistently on the CI dashboard. Attached is one of the crash files, but others can be added if needed. This appears to have been happening for quite a while. There are no clear reproduction steps. http://people.canonical.com/~brendan- donegan/_usr_share_click_preinstalled_com.ubuntu.camera_3.0.0 .412_camera-app.32011.crash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/camera-app/+bug/1390510/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1389510] Re: SD card and contents listed several times
I can't reproduce this here - are you sure your version of gmtp isn't buggy? I'm on Utopic and running 1.3.7-1 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mtp in Ubuntu. https://bugs.launchpad.net/bugs/1389510 Title: SD card and contents listed several times Status in “mtp” package in Ubuntu: New Bug description: When connecting to a krillin running rtm image 142, I see the SD card device listed several times. If I connect to that device and list its contents, each file and directory is listed several times too. The exact number is consistent during a session, but varies per boot. If I then add a new file, disconnect, and reconnect, that file is listed just once while everything else is listed several times. The mtp client I'm using to test this is gmtp. Results may appear different with Nautilus, because I think it ignores duplicates. Screenshots demonstrating what I see are attached. This issue isn't new, but it seems to happen every time now instead of just once in a while. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mtp/+bug/1389510/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1267821] Re: Need to enable copy/paste
** No longer affects: indicator-display (Ubuntu 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/1267821 Title: Need to enable copy/paste Status in Calculator application for Ubuntu devices: Triaged Status in “ubuntu-ui-toolkit” package in Ubuntu: Fix Released Bug description: On both phone and desktop, it needs to be easy to copy and paste numbers (input and results) to/from the calculator app. Standard keyboard shortcuts (CTRL+C, CTRL+V) should be used on desktop. Long press with pop-over should be used on the phone. More informatio is available at: https://wiki.ubuntu.com/Touch/CoreApps/Calculator/Design To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-calculator-app/+bug/1267821/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1389516] Re: new camera videos not shown in scope until after reboot
*** This bug is a duplicate of bug 1385302 *** https://bugs.launchpad.net/bugs/1385302 ** This bug has been marked a duplicate of bug 1385302 Recorded videos don't show up in Videos scope -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-scope-mediascanner in Ubuntu. https://bugs.launchpad.net/bugs/1389516 Title: new camera videos not shown in scope until after reboot Status in “unity-scope-mediascanner” package in Ubuntu: Confirmed Bug description: After recording some videos with the camera app, they don't show up in the Videos scope until after a reboot. Performing a search or using pull-to-refresh does not cause them to show up, but rebooting does. Not sure if this is caused by the scope itself or if it's an underlying issue with mediascanner. This was seen in krillin rtm image 142. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-scope-mediascanner/+bug/1389516/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1388876] [NEW] Pinch to zoom not supported when taking video
Public bug reported: Steps to reproduce: 1. Open the camera application 2. Press the Video button to switch to video mode 3. Place two fingers on the screen and move them apart to attempt to zoom Expected result: The picture zooms in and a slider appears indicating the zoom level Actual result: The slider appears but the picture does not zoom in and there is no marker on the slider to indicate the zoom level ** Affects: camera-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 camera-app in Ubuntu. https://bugs.launchpad.net/bugs/1388876 Title: Pinch to zoom not supported when taking video Status in “camera-app” package in Ubuntu: New Bug description: Steps to reproduce: 1. Open the camera application 2. Press the Video button to switch to video mode 3. Place two fingers on the screen and move them apart to attempt to zoom Expected result: The picture zooms in and a slider appears indicating the zoom level Actual result: The slider appears but the picture does not zoom in and there is no marker on the slider to indicate the zoom level To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/camera-app/+bug/1388876/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1373985] Re: foreground app doesn't get activated after we leave the lock screen
Definitely solves at least https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1385462 and https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1377817 for me. I would suggest this fix is good -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to maliit-framework in Ubuntu. https://bugs.launchpad.net/bugs/1373985 Title: foreground app doesn't get activated after we leave the lock screen Status in “maliit-framework” package in Ubuntu: In Progress Status in “unity8” package in Ubuntu: Invalid Bug description: Steps to reproduce the issue: 1 - have unity8-dash on the foreground 2 - lock the phone (reboot or have the display off and then turn it back on) 3 - type you password [you're brought to unity8-dash] 4 - tap on the looking glass icon in the top right [search bar text entry shows up with Search apps written on it] Expected outcome: A blinking cursor caret is displayed on the app search text entry and the VKB comes up. Actual outcome: Nothing happens. Causing unity-8 dash to be refocused, such as bringing the indicators panel down and then back up solves it. Comments: Happens with any application that happens to be in the foreground, unity8-dash being just one test case that is easy to reproduce. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maliit-framework/+bug/1373985/+subscriptions -- Mailing list: https://launchpad.net/~touch-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
When you say it's 'crashy' how many crashes did you actually get - just the one? The description doesn't make that clear. -- 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 1387959] Re: unity8 crash in image krillin rtm 139
In 3 hours testing this morning I got one crash: http://people.canonical.com/~brendan-donegan/_usr_bin_unity8.32011.crash -- 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 1387949] Re: power cycling BT device caused phone to reboot
Is this headset new? You might have hit an interop issue - if there was no crash it was probably a kernel panic or something like that. I've tried disconnecting and reconnecting a number of time with my headset and there are no issues. ** Changed in: indicator-bluetooth (Ubuntu) Status: New = Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-bluetooth in Ubuntu. https://bugs.launchpad.net/bugs/1387949 Title: power cycling BT device caused phone to reboot Status in “indicator-bluetooth” package in Ubuntu: Incomplete Bug description: While sanity testing krillin rtm image 139, I paired a bluetooth headset. I made a call with it, hung up, then turned the headset off. I noticed this caused the BT indicator icon to invert, which is a nice way to indicate whether something is connected. So, I turned the device back on, waited for the icon to invert, turned the device off, waited, and instead of inverting the icon... the phone rebooted. Not sure what exactly failed here, like which component, but it's definitely not good when a paired headset can cause the phone to spontaneously reboot. I don't see any relevant .crash files, and all I see in syslog from that time is this: Oct 30 23:42:27 ubuntu-phablet NetworkManager[1429]: warn Activation (/ril_1) failed for connection '/310410695117999/context1' Oct 30 23:42:27 ubuntu-phablet NetworkManager[1429]: info (/ril_1): device state change: failed - disconnected (reason 'none') [120 30 0] Oct 30 23:42:27 ubuntu-phablet NetworkManager[1429]: info (/ril_1): deactivating device (reason 'none') [0] Oct 30 23:43:01 ubuntu-phablet kernel: [ 747.229681][Ker_PM][request_suspend_state]wakeup (3-0) at 747214006509 (2014-10-31 05:43:01.704759580 UTC) Oct 30 23:43:02 ubuntu-phablet kernel: [ 747.779813]mtk-tpd: TPD wake up Oct 30 23:43:02 ubuntu-phablet kernel: [ 747.816572]mtk-tpd: TPD wake up done Oct 30 23:43:02 ubuntu-phablet kernel: [ 747.816593]MAGNETIC mag_context_obj ok---hwm_obj-early_suspend=0 Oct 30 23:43:09 ubuntu-phablet dbus[769]: [system] Activating service name='org.freedesktop.systemd1' (using servicehelper) Oct 30 23:43:09 ubuntu-phablet dbus[769]: [system] Successfully activated service 'org.freedesktop.systemd1' Oct 30 23:43:09 ubuntu-phablet rsyslogd: [origin software=rsyslogd swVersion=7.4.4 x-pid=771 x-info=http://www.rsyslog.com;] exiting on signal 15. Oct 30 23:43:42 ubuntu-phablet rsyslogd: [origin software=rsyslogd swVersion=7.4.4 x-pid=785 x-info=http://www.rsyslog.com;] start Oct 30 23:43:42 ubuntu-phablet rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ] Oct 30 23:43:42 ubuntu-phablet rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ] Oct 30 23:43:42 ubuntu-phablet rsyslogd: rsyslogd's groupid changed to 103 Oct 30 23:43:42 ubuntu-phablet rsyslogd: rsyslogd's userid changed to 100 Oct 30 23:43:42 ubuntu-phablet kernel: [0.00]Booting Linux on physical CPU 0 Oct 30 23:43:42 ubuntu-phablet kernel: [0.00]Initializing cgroup subsys cpu Oct 30 23:43:42 ubuntu-phablet kernel: [0.00]Linux version 3.4.67 (root@android-barajas_1414177384) (gcc version 4.7 (GCC) ) #1 SMP PREEMPT Tue Oct 28 11:57:42 UTC 2014 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-bluetooth/+bug/1387949/+subscriptions -- Mailing list: https://launchpad.net/~touch-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] Re: [webapp-container] apps are not handled by lifecycle management properly
** Tags added: exploratory -- 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 Oxide Webview: New Status in Web Browser App: New 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/oxide/+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 1387949] Re: power cycling BT device caused phone to reboot
** Package changed: indicator-bluetooth (Ubuntu) = bluez (Ubuntu) ** Summary changed: - power cycling BT device caused phone to reboot + power cycling Emerson EM229 headset caused phone to reboot -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1387949 Title: power cycling Emerson EM229 headset caused phone to reboot Status in “bluez” package in Ubuntu: New Bug description: While sanity testing krillin rtm image 139, I paired a bluetooth headset. I made a call with it, hung up, then turned the headset off. I noticed this caused the BT indicator icon to invert, which is a nice way to indicate whether something is connected. So, I turned the device back on, waited for the icon to invert, turned the device off, waited, and instead of inverting the icon... the phone rebooted. Not sure what exactly failed here, like which component, but it's definitely not good when a paired headset can cause the phone to spontaneously reboot. I don't see any relevant .crash files, and all I see in syslog from that time is this: Oct 30 23:42:27 ubuntu-phablet NetworkManager[1429]: warn Activation (/ril_1) failed for connection '/310410695117999/context1' Oct 30 23:42:27 ubuntu-phablet NetworkManager[1429]: info (/ril_1): device state change: failed - disconnected (reason 'none') [120 30 0] Oct 30 23:42:27 ubuntu-phablet NetworkManager[1429]: info (/ril_1): deactivating device (reason 'none') [0] Oct 30 23:43:01 ubuntu-phablet kernel: [ 747.229681][Ker_PM][request_suspend_state]wakeup (3-0) at 747214006509 (2014-10-31 05:43:01.704759580 UTC) Oct 30 23:43:02 ubuntu-phablet kernel: [ 747.779813]mtk-tpd: TPD wake up Oct 30 23:43:02 ubuntu-phablet kernel: [ 747.816572]mtk-tpd: TPD wake up done Oct 30 23:43:02 ubuntu-phablet kernel: [ 747.816593]MAGNETIC mag_context_obj ok---hwm_obj-early_suspend=0 Oct 30 23:43:09 ubuntu-phablet dbus[769]: [system] Activating service name='org.freedesktop.systemd1' (using servicehelper) Oct 30 23:43:09 ubuntu-phablet dbus[769]: [system] Successfully activated service 'org.freedesktop.systemd1' Oct 30 23:43:09 ubuntu-phablet rsyslogd: [origin software=rsyslogd swVersion=7.4.4 x-pid=771 x-info=http://www.rsyslog.com;] exiting on signal 15. Oct 30 23:43:42 ubuntu-phablet rsyslogd: [origin software=rsyslogd swVersion=7.4.4 x-pid=785 x-info=http://www.rsyslog.com;] start Oct 30 23:43:42 ubuntu-phablet rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ] Oct 30 23:43:42 ubuntu-phablet rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ] Oct 30 23:43:42 ubuntu-phablet rsyslogd: rsyslogd's groupid changed to 103 Oct 30 23:43:42 ubuntu-phablet rsyslogd: rsyslogd's userid changed to 100 Oct 30 23:43:42 ubuntu-phablet kernel: [0.00]Booting Linux on physical CPU 0 Oct 30 23:43:42 ubuntu-phablet kernel: [0.00]Initializing cgroup subsys cpu Oct 30 23:43:42 ubuntu-phablet kernel: [0.00]Linux version 3.4.67 (root@android-barajas_1414177384) (gcc version 4.7 (GCC) ) #1 SMP PREEMPT Tue Oct 28 11:57:42 UTC 2014 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1387949/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1373985] Re: foreground app doesn't get activated after we leave the lock screen
This may be making some of our smoke tests fail too -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to maliit-framework in Ubuntu. https://bugs.launchpad.net/bugs/1373985 Title: foreground app doesn't get activated after we leave the lock screen Status in “maliit-framework” package in Ubuntu: In Progress Status in “unity8” package in Ubuntu: Invalid Bug description: Steps to reproduce the issue: 1 - have unity8-dash on the foreground 2 - lock the phone (reboot or have the display off and then turn it back on) 3 - type you password [you're brought to unity8-dash] 4 - tap on the looking glass icon in the top right [search bar text entry shows up with Search apps written on it] Expected outcome: A blinking cursor caret is displayed on the app search text entry and the VKB comes up. Actual outcome: Nothing happens. Causing unity-8 dash to be refocused, such as bringing the indicators panel down and then back up solves it. Comments: Happens with any application that happens to be in the foreground, unity8-dash being just one test case that is easy to reproduce. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maliit-framework/+bug/1373985/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1386803] Re: [TOPBLOCKER] unity8 crashing a lot since image #126
I've just been testing silo 13 - it makes the crashes go away but after enabling flight mode I can't disable it. The fix might need a bit of tweaking. -- 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/1386803 Title: [TOPBLOCKER] unity8 crashing a lot since image #126 Status in “dbus-cpp” package in Ubuntu: In Progress Status in “unity8” package in Ubuntu: Opinion Bug description: Since RTM image #126 was released on friday, most users have been reporting frequent unity8 crashes. Some scenarios where this commonly happen appear to be: - Unlocking SIM cards for the first time - Tapping on snap notifications when receiving an SMS A lot of crashes are also observed during automated image testing. ProblemType: Bug DistroRelease: Ubuntu RTM 14.09 Package: unity8 8.00+14.10.20141017-0ubuntu1 [origin: unknown] Uname: Linux 3.4.67 armv7l ApportVersion: 2.14.7-0ubuntu8 Architecture: armhf Date: Tue Oct 28 17:20:40 2014 InstallationDate: Installed on 2014-10-28 (0 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20141028-030205) SourcePackage: unity8 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbus-cpp/+bug/1386803/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1385462] [NEW] apps are not told they have focus when unlocking the greeter
Public bug reported: Steps to reproduce: 1. Open the camera app 2. Press the power button to lock the device 3. Press the power button to unlock the device 4. Swipe right to unlock the greeter and enter the PIN/password if appropriate Expected result: The viewfinder shows the input from the camera Actual result: The viewfinder shows a black surface Alternate steps to reproduce: 1. Open the messaging app 2. Swipe up to open the message composition view 2. Press the power button to lock the device 3. Press the power button to unlock the device 4. Swipe right to unlock the greeter and enter the PIN/password if appropriate 5. Tap on the Write a message field Expected result: The field gets focus and the keyboard opens Actual result: The field doesn't get focus and the keyboard doesn't open ProblemType: Bug DistroRelease: Ubuntu RTM 14.09 Package: unity8 8.00+14.10.20141017-0ubuntu1 [origin: unknown] Uname: Linux 3.4.67 armv7l ApportVersion: 2.14.7-0ubuntu8 Architecture: armhf Date: Fri Oct 24 19:16:45 2014 InstallationDate: Installed on 2014-10-24 (0 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20141024-030204) SourcePackage: unity8 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: qtmir (Ubuntu) Importance: Undecided Status: New ** Affects: unity8 (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug armhf exploratory qa-daily-testing third-party-packages utopic ** Summary changed: - apps told they have focus when unlocking the greeter + apps are not told they have focus when unlocking the greeter ** 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/1385462 Title: apps are not told they have focus when unlocking the greeter Status in “qtmir” package in Ubuntu: New Status in “unity8” package in Ubuntu: New Bug description: Steps to reproduce: 1. Open the camera app 2. Press the power button to lock the device 3. Press the power button to unlock the device 4. Swipe right to unlock the greeter and enter the PIN/password if appropriate Expected result: The viewfinder shows the input from the camera Actual result: The viewfinder shows a black surface Alternate steps to reproduce: 1. Open the messaging app 2. Swipe up to open the message composition view 2. Press the power button to lock the device 3. Press the power button to unlock the device 4. Swipe right to unlock the greeter and enter the PIN/password if appropriate 5. Tap on the Write a message field Expected result: The field gets focus and the keyboard opens Actual result: The field doesn't get focus and the keyboard doesn't open ProblemType: Bug DistroRelease: Ubuntu RTM 14.09 Package: unity8 8.00+14.10.20141017-0ubuntu1 [origin: unknown] Uname: Linux 3.4.67 armv7l ApportVersion: 2.14.7-0ubuntu8 Architecture: armhf Date: Fri Oct 24 19:16:45 2014 InstallationDate: Installed on 2014-10-24 (0 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20141024-030204) SourcePackage: unity8 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtmir/+bug/1385462/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1373985] Re: unity8-dash doesn't seem to get activated after we leave the lock screen
FTR this happens with camera-app (see https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1385462) which as far as I know never tries to do anything with maliit so to my untrained eye it looks like a more general issue. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to maliit-framework in Ubuntu. https://bugs.launchpad.net/bugs/1373985 Title: unity8-dash doesn't seem to get activated after we leave the lock screen Status in “maliit-framework” package in Ubuntu: In Progress Status in “unity8” package in Ubuntu: Invalid Bug description: Steps to reproduce the issue: 1 - lock the phone (reboot or have the display off and then turn it back on) 2 - type you password [you're brought to unity8-dash] 3 - tap on the looking glass icon in the top right [search bar text entry shows up with Search apps written on it] Expected outcome: A blinking cursor caret is displayed on the app search text entry and the VKB comes up. Actual outcome: Nothing happens. Causing unity-8 dash to be refocused, such as bringing the indicators panel down and then back up solves it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maliit-framework/+bug/1373985/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1381930] [NEW] 7digital previews do not play in the scope
Public bug reported: Steps to reproduce: 1. Navigate to the music scope 2. In the section 'New albums from 7digital' click on any album 3. Press the play button on one of the track previews Expected result: The preview plays Actual result: No preview plays ProblemType: Bug DistroRelease: Ubuntu RTM 14.09 Package: unity-scope-mediascanner2 0.2+14.10.20141009-0ubuntu1 Uname: Linux 3.4.67 armv7l ApportVersion: 2.14.7-0ubuntu5 Architecture: armhf Date: Thu Oct 16 08:11:12 2014 InstallationDate: Installed on 2014-10-16 (0 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20141016-010328) SourcePackage: unity-scope-mediascanner UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: unity-scope-mediascanner (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug armhf utopic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-scope-mediascanner in Ubuntu. https://bugs.launchpad.net/bugs/1381930 Title: 7digital previews do not play in the scope Status in “unity-scope-mediascanner” package in Ubuntu: New Bug description: Steps to reproduce: 1. Navigate to the music scope 2. In the section 'New albums from 7digital' click on any album 3. Press the play button on one of the track previews Expected result: The preview plays Actual result: No preview plays ProblemType: Bug DistroRelease: Ubuntu RTM 14.09 Package: unity-scope-mediascanner2 0.2+14.10.20141009-0ubuntu1 Uname: Linux 3.4.67 armv7l ApportVersion: 2.14.7-0ubuntu5 Architecture: armhf Date: Thu Oct 16 08:11:12 2014 InstallationDate: Installed on 2014-10-16 (0 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20141016-010328) SourcePackage: unity-scope-mediascanner UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-scope-mediascanner/+bug/1381930/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1382027] [NEW] Tracks without embedded art do not download the art
Public bug reported: Steps to reproduce: 1. Download http://people.canonical.com/~j-lallement/supertramp_1979_paris_cd1_School.mp3 2. Plug the device in and transfer the file above over MTP to the internal storage 3. Open the Music scope and locate the track (by searching or browsing) 4. Confirm that eventually the album art for the track is downloaded Expected result: After a period of time the album art is downloaded and appears as the cover art Actual result: The album art is never downloaded ProblemType: Bug DistroRelease: Ubuntu RTM 14.09 Package: unity-scope-mediascanner2 0.2+14.10.20141009-0ubuntu1 Uname: Linux 3.4.67 armv7l ApportVersion: 2.14.7-0ubuntu5 Architecture: armhf Date: Thu Oct 16 12:09:07 2014 InstallationDate: Installed on 2014-10-16 (0 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20141016-010328) SourcePackage: unity-scope-mediascanner UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: unity-scope-mediascanner (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug armhf utopic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-scope-mediascanner in Ubuntu. https://bugs.launchpad.net/bugs/1382027 Title: Tracks without embedded art do not download the art Status in “unity-scope-mediascanner” package in Ubuntu: New Bug description: Steps to reproduce: 1. Download http://people.canonical.com/~j-lallement/supertramp_1979_paris_cd1_School.mp3 2. Plug the device in and transfer the file above over MTP to the internal storage 3. Open the Music scope and locate the track (by searching or browsing) 4. Confirm that eventually the album art for the track is downloaded Expected result: After a period of time the album art is downloaded and appears as the cover art Actual result: The album art is never downloaded ProblemType: Bug DistroRelease: Ubuntu RTM 14.09 Package: unity-scope-mediascanner2 0.2+14.10.20141009-0ubuntu1 Uname: Linux 3.4.67 armv7l ApportVersion: 2.14.7-0ubuntu5 Architecture: armhf Date: Thu Oct 16 12:09:07 2014 InstallationDate: Installed on 2014-10-16 (0 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20141016-010328) SourcePackage: unity-scope-mediascanner UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-scope-mediascanner/+bug/1382027/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1382049] [NEW] Web apps that use OA just close if there is no existing account and no connection
Public bug reported: Prerequisites: There must be NO account created for the web app in question (steps assume Facebook). Connectivity should have been disabled (flight mode on and make sure wifi is disabled too) Steps to reproduce: 1. Open the Facebook web app from the click scope 2. Wait a few seconds Expected result: There is some obvious feedback as to what happened (need a connection to create an account but don't have one) Actual result: The application just closes ProblemType: Bug DistroRelease: Ubuntu RTM 14.09 Package: webapp-container 0.23+14.10.20141008-0ubuntu1 Uname: Linux 3.4.67 armv7l ApportVersion: 2.14.7-0ubuntu5 Architecture: armhf Date: Thu Oct 16 12:55:46 2014 InstallationDate: Installed on 2014-10-16 (0 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20141016-010328) SourcePackage: webbrowser-app UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubuntu-ux Importance: Undecided Status: New ** Affects: webapps-core Importance: Undecided Status: Opinion ** Tags: apport-bug armhf utopic ** Package changed: webbrowser-app (Ubuntu) = webapps-core -- 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/1382049 Title: Web apps that use OA just close if there is no existing account and no connection Status in Ubuntu UX bugs: New Status in The Webapps-core project: Opinion Bug description: Prerequisites: There must be NO account created for the web app in question (steps assume Facebook). Connectivity should have been disabled (flight mode on and make sure wifi is disabled too) Steps to reproduce: 1. Open the Facebook web app from the click scope 2. Wait a few seconds Expected result: There is some obvious feedback as to what happened (need a connection to create an account but don't have one) Actual result: The application just closes ProblemType: Bug DistroRelease: Ubuntu RTM 14.09 Package: webapp-container 0.23+14.10.20141008-0ubuntu1 Uname: Linux 3.4.67 armv7l ApportVersion: 2.14.7-0ubuntu5 Architecture: armhf Date: Thu Oct 16 12:55:46 2014 InstallationDate: Installed on 2014-10-16 (0 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20141016-010328) SourcePackage: webbrowser-app UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1382049/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1381930] Re: 7digital previews do not play in the scope
** Tags added: rtm14 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-scope-mediascanner in Ubuntu. https://bugs.launchpad.net/bugs/1381930 Title: 7digital previews do not play in the scope Status in “unity-scope-mediascanner” package in Ubuntu: New Bug description: Steps to reproduce: 1. Navigate to the music scope 2. In the section 'New albums from 7digital' click on any album 3. Press the play button on one of the track previews Expected result: The preview plays Actual result: No preview plays ProblemType: Bug DistroRelease: Ubuntu RTM 14.09 Package: unity-scope-mediascanner2 0.2+14.10.20141009-0ubuntu1 Uname: Linux 3.4.67 armv7l ApportVersion: 2.14.7-0ubuntu5 Architecture: armhf Date: Thu Oct 16 08:11:12 2014 InstallationDate: Installed on 2014-10-16 (0 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20141016-010328) SourcePackage: unity-scope-mediascanner UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-scope-mediascanner/+bug/1381930/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1378811] [NEW] If a SIM slot with no signal is selected as the default SIM then replying via the indicator fails silently
Public bug reported: Prerquisites: The 'For messages use' option in System Settings Cellular panel should be set to a slot that contains a SIM card with no signal Steps to reproduce: 1. Send a message to the SUT (with the messaging-app closed) 2. Wait for the snap notification to disappear 3. Open the messaging indicator and press anywhere on the message (except on the message icon which will open the messaging app) 4. Enter your reply in the text field that appears (keeping in mind that there may be a bug that stops the Send button from being enabled if the keyboard is in the middle of autocorrecting a word) 5.) Hit the send button when it is enabled Expected result: I'm either informed that sending failed because the SIM had no signal, or better, offered the option to rectify this by choosing a SIM for that action. Actual result: The message disappears from the menu, the same as if it was successfully sent, but it was not successfully sent (as it was not received on the other end). Note that if the 'For messages use' option is set to nothing, or 'Ask me each time' then the user will be prompted to choose a SIM ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: indicator-messages 13.10.1+14.10.20140925-0ubuntu1 [origin: unknown] Uname: Linux 3.4.67 armv7l ApportVersion: 2.14.7-0ubuntu3 Architecture: armhf Date: Wed Oct 8 12:49:00 2014 InstallationDate: Installed on 2014-10-08 (0 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20141008-030204) SourcePackage: indicator-messages UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: indicator-messages (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug armhf exploratory qa-daily-testing rtm14 third-party-packages utopic ** Tags added: exploratory qa-daily-testing -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-messages in Ubuntu. https://bugs.launchpad.net/bugs/1378811 Title: If a SIM slot with no signal is selected as the default SIM then replying via the indicator fails silently Status in “indicator-messages” package in Ubuntu: New Bug description: Prerquisites: The 'For messages use' option in System Settings Cellular panel should be set to a slot that contains a SIM card with no signal Steps to reproduce: 1. Send a message to the SUT (with the messaging-app closed) 2. Wait for the snap notification to disappear 3. Open the messaging indicator and press anywhere on the message (except on the message icon which will open the messaging app) 4. Enter your reply in the text field that appears (keeping in mind that there may be a bug that stops the Send button from being enabled if the keyboard is in the middle of autocorrecting a word) 5.) Hit the send button when it is enabled Expected result: I'm either informed that sending failed because the SIM had no signal, or better, offered the option to rectify this by choosing a SIM for that action. Actual result: The message disappears from the menu, the same as if it was successfully sent, but it was not successfully sent (as it was not received on the other end). Note that if the 'For messages use' option is set to nothing, or 'Ask me each time' then the user will be prompted to choose a SIM ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: indicator-messages 13.10.1+14.10.20140925-0ubuntu1 [origin: unknown] Uname: Linux 3.4.67 armv7l ApportVersion: 2.14.7-0ubuntu3 Architecture: armhf Date: Wed Oct 8 12:49:00 2014 InstallationDate: Installed on 2014-10-08 (0 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20141008-030204) SourcePackage: indicator-messages UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-messages/+bug/1378811/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1378938] [NEW] App switcher can be put in a bad state by grabbing the app before it comes into focus
Public bug reported: It seems it is possible to put the app switcher in an odd 'in-between' state through the right combination of taps. To reproduce this, open a few apps and: 1. Swipe from the right to open the app switcher 2. Tap on an app to focus it and immediately tap on it again and hold down - before it comes into focus - don't take your finger off yet 3. Now swiping up or down will dismiss the app 4. After that the switcher will be open but all of the previews will appear closer to the screen. Tapping the screen won't do anything. Interaction can only be restored by swiping from the right again. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: unity8 8.00+14.10.20141006-0ubuntu1 [origin: Ubuntu RTM] Uname: Linux 3.4.67 armv7l ApportVersion: 2.14.7-0ubuntu3 Architecture: armhf Date: Wed Oct 8 16:03:25 2014 InstallationDate: Installed on 2014-10-08 (0 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20141008-090632) SourcePackage: unity8 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: unity8 (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug armhf third-party-packages utopic -- 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/1378938 Title: App switcher can be put in a bad state by grabbing the app before it comes into focus Status in “unity8” package in Ubuntu: New Bug description: It seems it is possible to put the app switcher in an odd 'in-between' state through the right combination of taps. To reproduce this, open a few apps and: 1. Swipe from the right to open the app switcher 2. Tap on an app to focus it and immediately tap on it again and hold down - before it comes into focus - don't take your finger off yet 3. Now swiping up or down will dismiss the app 4. After that the switcher will be open but all of the previews will appear closer to the screen. Tapping the screen won't do anything. Interaction can only be restored by swiping from the right again. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: unity8 8.00+14.10.20141006-0ubuntu1 [origin: Ubuntu RTM] Uname: Linux 3.4.67 armv7l ApportVersion: 2.14.7-0ubuntu3 Architecture: armhf Date: Wed Oct 8 16:03:25 2014 InstallationDate: Installed on 2014-10-08 (0 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20141008-090632) 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/1378938/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1370376] Re: Can't receive MMS despite ability to send on Tele2
** Tags added: operators -- 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/1370376 Title: Can't receive MMS despite ability to send on Tele2 Status in “network-manager” package in Ubuntu: New Status in “nuntium” package in Ubuntu: Incomplete Bug description: I can send MMS (and they actually come through to the recipient), but I can't receive MMS. I am not sure if this is an APN settings issue, but I would have thought it either worked both ways or not at all. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1370376/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1370376] Re: Can't receive MMS despite ability to send on Tele2
** Tags removed: operators -- 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/1370376 Title: Can't receive MMS despite ability to send on Tele2 Status in “network-manager” package in Ubuntu: New Status in “nuntium” package in Ubuntu: Confirmed Bug description: I can send MMS (and they actually come through to the recipient), but I can't receive MMS. I am not sure if this is an APN settings issue, but I would have thought it either worked both ways or not at all. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1370376/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1377806] [NEW] 'Music Audio' category is slightly odd - should be 'Music Video'?
Public bug reported: One of the categories in the click scope is 'Music Audio', which while not strictly wrong, does sound a bit odd, like saying 'Alcohol Beer'. This should probably be Music Video or Audio Video (since I see it includes Media Player which is for Video) ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: unity-scope-click 0.1.1+14.10.20141002-0ubuntu1 [origin: LP-PPA-ci-train-ppa-service-landing-026] Uname: Linux 3.4.67 armv7l ApportVersion: 2.14.7-0ubuntu1 Architecture: armhf Date: Mon Oct 6 06:10:20 2014 InstallationDate: Installed on 2014-10-06 (0 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20141006-030205) SourcePackage: unity-scope-click UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: unity-scope-click (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug armhf third-party-packages utopic -- 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/1377806 Title: 'Music Audio' category is slightly odd - should be 'Music Video'? Status in “unity-scope-click” package in Ubuntu: New Bug description: One of the categories in the click scope is 'Music Audio', which while not strictly wrong, does sound a bit odd, like saying 'Alcohol Beer'. This should probably be Music Video or Audio Video (since I see it includes Media Player which is for Video) ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: unity-scope-click 0.1.1+14.10.20141002-0ubuntu1 [origin: LP-PPA-ci-train-ppa-service-landing-026] Uname: Linux 3.4.67 armv7l ApportVersion: 2.14.7-0ubuntu1 Architecture: armhf Date: Mon Oct 6 06:10:20 2014 InstallationDate: Installed on 2014-10-06 (0 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20141006-030205) SourcePackage: unity-scope-click UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-scope-click/+bug/1377806/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1377809] [NEW] Wizard sometimes crashes after entering wireless passphrase
Public bug reported: With recent images I'm finding that every so often when I run the wizard, after entering the wireless passphrase, unity8 freezes, hangs and then crashes before the keyboard can fully close. First the keyboard gets stuck near the bottom of the screen, then for a minute or so the screen is unresponsive and then unity8 restarts. This is not easy to reproduce - you'd have to keep running the wizard repeatedly and eventually you might catch it. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: unity8 8.00+14.10.20140930.2-0ubuntu1 [origin: Ubuntu RTM] Uname: Linux 3.4.67 armv7l ApportVersion: 2.14.7-0ubuntu1 Architecture: armhf Date: Mon Oct 6 06:24:59 2014 InstallationDate: Installed on 2014-10-06 (0 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20141006-030205) SourcePackage: unity8 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubuntu-system-settings (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug armhf third-party-packages utopic -- 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/1377809 Title: Wizard sometimes crashes after entering wireless passphrase Status in “ubuntu-system-settings” package in Ubuntu: New Bug description: With recent images I'm finding that every so often when I run the wizard, after entering the wireless passphrase, unity8 freezes, hangs and then crashes before the keyboard can fully close. First the keyboard gets stuck near the bottom of the screen, then for a minute or so the screen is unresponsive and then unity8 restarts. This is not easy to reproduce - you'd have to keep running the wizard repeatedly and eventually you might catch it. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: unity8 8.00+14.10.20140930.2-0ubuntu1 [origin: Ubuntu RTM] Uname: Linux 3.4.67 armv7l ApportVersion: 2.14.7-0ubuntu1 Architecture: armhf Date: Mon Oct 6 06:24:59 2014 InstallationDate: Installed on 2014-10-06 (0 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20141006-030205) SourcePackage: unity8 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-system-settings/+bug/1377809/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1377817] [NEW] Search box isn't always focused when clicking on search
Public bug reported: Normally when we click on the search button in the dash, the search field appears, is focused and the keyboard pops up. With a certain amount of use, I am now finding that sometimes it won't appear. The exact circumstances are still unclear, but with 10-15 minutes usage it should eventually happen. I'll keep looking for some firm reproduction steps. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: unity8 8.00+14.10.20140930.2-0ubuntu1 [origin: Ubuntu RTM] Uname: Linux 3.4.67 armv7l ApportVersion: 2.14.7-0ubuntu1 Architecture: armhf Date: Mon Oct 6 07:22:52 2014 InstallationDate: Installed on 2014-10-06 (0 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20141006-030205) SourcePackage: unity8 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: unity8 (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug armhf third-party-packages utopic -- 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/1377817 Title: Search box isn't always focused when clicking on search Status in “unity8” package in Ubuntu: New Bug description: Normally when we click on the search button in the dash, the search field appears, is focused and the keyboard pops up. With a certain amount of use, I am now finding that sometimes it won't appear. The exact circumstances are still unclear, but with 10-15 minutes usage it should eventually happen. I'll keep looking for some firm reproduction steps. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: unity8 8.00+14.10.20140930.2-0ubuntu1 [origin: Ubuntu RTM] Uname: Linux 3.4.67 armv7l ApportVersion: 2.14.7-0ubuntu1 Architecture: armhf Date: Mon Oct 6 07:22:52 2014 InstallationDate: Installed on 2014-10-06 (0 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20141006-030205) 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/1377817/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 1373462] Re: [background] Preview/Background is black for some images
This is starting to get a little tedious - can't the fix be done at a lower level so that each application doesn't have to make sure it's 'doing it right'? On Fri, Oct 3, 2014 at 1:11 PM, Victor Tuson Palau 1373...@bugs.launchpad.net wrote: this impacts telegram image preview, the fix was done for thumbnails in chats, but seems local images (ones sent by you) on the preview ** Also affects: libqtelegram Importance: Undecided Status: New ** Changed in: libqtelegram Importance: Undecided = Critical -- You received this bug notification because you are subscribed to a duplicate bug report (1373855). https://bugs.launchpad.net/bugs/1373462 Title: [background] Preview/Background is black for some images To manage notifications about this bug go to: https://bugs.launchpad.net/libqtelegram/+bug/1373462/+subscriptions -- 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/1373462 Title: [background] Preview/Background is black for some images Status in Libqtelegram - a qt library to access telegram.: Fix Committed Status in Messaging App: New Status in “messaging-app” package in Ubuntu: Confirmed Status in “ubuntu-system-settings” package in Ubuntu: Fix Released Status in “unity8” package in Ubuntu: Fix Released Status in “messaging-app” package in Ubuntu RTM: New Bug description: With some images the preview and the background is black but the image is fine in the gallery app. For example picture attached looks correct, but preview and background are black. TEST CASE: 1. Upload the attached picture to the phone with mtp 2. Go to system-settings / background 3. Tap 'Add an image' 4. Select this image - Verify that the preview is correct 5. Validate your choice, 6. Press the power button twice to show the greeter - Verify that the background is correct ACTUAL RESULT Background and preview are black. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: ubuntu-system-settings 0.3+14.10.20140913-0ubuntu1 [origin: Ubuntu RTM] Uname: Linux 3.4.67 armv7l ApportVersion: 2.14.7-0ubuntu1 Architecture: armhf Date: Wed Sep 24 16:34:18 2014 InstallationDate: Installed on 2014-09-16 (8 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20140916-030205) SourcePackage: ubuntu-system-settings UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/libqtelegram/+bug/1373462/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1371032] Re: Cannot send MMS from Yoigo
Having understood a bit more the nature of this bug, I'd still like to
be critical.
** Changed in: network-manager (Ubuntu)
Importance: High = Critical
** Changed in: nuntium (Ubuntu)
Importance: High = Critical
** Changed in: ofono (Ubuntu)
Importance: High = Critical
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to messaging-app in Ubuntu.
https://bugs.launchpad.net/bugs/1371032
Title:
Cannot send MMS from Yoigo
Status in “messaging-app” package in Ubuntu:
New
Status in “network-manager” package in Ubuntu:
Incomplete
Status in “nuntium” package in Ubuntu:
In Progress
Status in “ofono” package in Ubuntu:
Invalid
Status in “nuntium” package in Ubuntu RTM:
New
Bug description:
phablet@ubuntu-phablet:~$ /usr/share/ofono/scripts/list-contexts
[ /ril_1 ]
[ /ril_0 ]
[ /ril_0/context1 ]
AccessPointName = internet
Name = Yoigo Internet
Password =
Protocol = ip
IPv6.Settings = { }
Type = internet
Active = 1
Username =
Settings = { DomainNameServers=217.168.13.34,46.6.113.2,
Address=10.192.132.31 Method=static Netmask=255.255.255.0 Gateway=10.192.132.31
Interface=ccmni0 }
[ /ril_0/context2 ]
AccessPointName = mms
MessageCenter = http://mmss/
Name = Yoigo MMS
Password =
Protocol = ip
MessageProxy = 193.209.134.141:80
IPv6.Settings = { }
Type = mms
Active = 0
Username =
Settings = { }
phablet@ubuntu-phablet:~$ /usr/share/ofono/scripts/activate-context /ril_0 2
Error activating /ril_0/context2: org.ofono.Error.NotAttached: GPRS is not
attached
phablet@ubuntu-phablet:~$ /usr/share/ofono/scripts/activate-context
/ril_0 1
Additional info:
- I didn't see any error in the messaging app.
- Couldn't send nor receive MMS.
- 3G connection is activated, but usually after a reboot. After a while, it
looses it.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/messaging-app/+bug/1371032/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1374419] Re: Some APs show twice, should be merged
I also see APs twice with the following test case: Prerequisite: Make sure you are already connected to a network 1. Open the network indicator 2. Select another network to connect to 3. Cancel the snap decision 4. Check the AP list, the previously selected AP will be shown twice and selected each time. I feel this is a different bug than the one mentioned here but Antii says otherwise, so for now I'm just adding this comment. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-network in Ubuntu. https://bugs.launchpad.net/bugs/1374419 Title: Some APs show twice, should be merged Status in “indicator-network” package in Ubuntu: Incomplete Status in “ubuntu-system-settings” package in Ubuntu: Invalid Bug description: Some access points in indicator-network show twice, when they should be merged into a single entry given that security and SSID are the same. See attached screenshot. For example, Instant Staff should only show once, not greyed out. There are not multiple APs with different security settings to justify two different entries. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1374419/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1376315] [NEW] Unable to add image in Yelp webapp, but can on m.yelp.com in the browser
Public bug reported: Steps to reproduce: 1. Open the 'Yelp' application 2. From the home screen click on a review (under Hot New Businesses Nearby) 3. Click on the 'Add Photo' button on the businesses page Expected result: Content hub opens and offers e.g. Camera and Gallery as sources Actual result: Content hub opens with message 'Sorry there aren't currently any apps installed that can provide this type of content' Repeating the same test case by replacing step 1 with 'Open the browser and navigate to m.yelp.com' gives the Expected result ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: webbrowser-app 0.23+14.10.20140926-0ubuntu1 [origin: unknown] Uname: Linux 3.4.67 armv7l ApportVersion: 2.14.7-0ubuntu1 Architecture: armhf Date: Wed Oct 1 15:17:45 2014 InstallationDate: Installed on 2014-10-01 (0 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20141001-030204) SourcePackage: webbrowser-app UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: webbrowser-app (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug armhf third-party-packages utopic -- 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/1376315 Title: Unable to add image in Yelp webapp, but can on m.yelp.com in the browser Status in “webbrowser-app” package in Ubuntu: New Bug description: Steps to reproduce: 1. Open the 'Yelp' application 2. From the home screen click on a review (under Hot New Businesses Nearby) 3. Click on the 'Add Photo' button on the businesses page Expected result: Content hub opens and offers e.g. Camera and Gallery as sources Actual result: Content hub opens with message 'Sorry there aren't currently any apps installed that can provide this type of content' Repeating the same test case by replacing step 1 with 'Open the browser and navigate to m.yelp.com' gives the Expected result ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: webbrowser-app 0.23+14.10.20140926-0ubuntu1 [origin: unknown] Uname: Linux 3.4.67 armv7l ApportVersion: 2.14.7-0ubuntu1 Architecture: armhf Date: Wed Oct 1 15:17:45 2014 InstallationDate: Installed on 2014-10-01 (0 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20141001-030204) SourcePackage: webbrowser-app UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1376315/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1334807] Re: gallery-app crashes when trying to delete multiple photos
Not reproducible on the latest RTM image (#75). There is another bug with the tabulation of the number of images (it counts the event as an image), but this bug I can't reproduce. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gallery-app in Ubuntu. https://bugs.launchpad.net/bugs/1334807 Title: gallery-app crashes when trying to delete multiple photos Status in Gallery App: In Progress Status in “gallery-app” package in Ubuntu: In Progress Bug description: Mako #162 OOPS: https://errors.ubuntu.com/oops/00ec1658-1892-11e4-9140-fa163e5bb1a2 On the main Events page when I try to delete multiple images from different days the app crashes. TEST CASE: 1. Open the camera and take several photos (half a dozen) 2. Open the gallery 3. Long press the shape with the date of the day to select all the photos that have just been taken. 2. Tap 'Delete' in the toolbar ACTUAL RESULT the app crashes. see the attached .crash file. EXPECTED RESULT It doesn't crash ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: gallery-app (not installed) Uname: Linux 3.4.0-5-mako armv7l ApportVersion: 2.14.3-0ubuntu2 Architecture: armhf Date: Thu Jun 26 23:50:19 2014 InstallationDate: Installed on 2014-06-26 (0 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20140626-020204) SourcePackage: gallery-app UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gallery-app/+bug/1334807/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1373462] Re: [background] Preview/Background is black for some images
Also needs to be fixed in messaging-app - previews in MMS messages show a black square as well ** Also affects: messaging-app (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1373462 Title: [background] Preview/Background is black for some images Status in Messaging App: New Status in “messaging-app” package in Ubuntu: Confirmed Status in “ubuntu-system-settings” package in Ubuntu: Fix Released Status in “unity8” package in Ubuntu: Fix Released Bug description: With some images the preview and the background is black but the image is fine in the gallery app. For example picture attached looks correct, but preview and background are black. TEST CASE: 1. Upload the attached picture to the phone with mtp 2. Go to system-settings / background 3. Tap 'Add an image' 4. Select this image - Verify that the preview is correct 5. Validate your choice, 6. Press the power button twice to show the greeter - Verify that the background is correct ACTUAL RESULT Background and preview are black. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: ubuntu-system-settings 0.3+14.10.20140913-0ubuntu1 [origin: Ubuntu RTM] Uname: Linux 3.4.67 armv7l ApportVersion: 2.14.7-0ubuntu1 Architecture: armhf Date: Wed Sep 24 16:34:18 2014 InstallationDate: Installed on 2014-09-16 (8 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20140916-030205) SourcePackage: ubuntu-system-settings UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/messaging-app/+bug/1373462/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1376500] Re: [regression] thumbnails and image previews displayed wrong
The black square in messaging-app is actually this bug: https://bugs.launchpad.net/ubuntu/+source/messaging-app/+bug/1373462 This regression came well after the resolution increase so that isn't the only reason (although it may be part of it). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to thumbnailer in Ubuntu. https://bugs.launchpad.net/bugs/1376500 Title: [regression] thumbnails and image previews displayed wrong Status in Camera App: New Status in Gallery App: New Status in Ubuntu UI Toolkit: New Status in “thumbnailer” package in Ubuntu: Confirmed Bug description: build 76 rtm-proposed on krillin Take a picture with camera-app swipe to the right to display it it looks squashed and like it's being displayed at the wrong aspect ration open the gallery-app and view the photo and it looks equally bad share the photo to messaging-app, and the preview of the photo is black copy the photo to your desktop and open there and the photo looks fine these are all new regressions, not sure what layer it's in bug guessing a low layer as gallery, camera and messaging-app have not changed in this regard To manage notifications about this bug go to: https://bugs.launchpad.net/camera-app/+bug/1376500/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1376500] Re: [regression] thumbnails and image previews displayed wrong
This started happening in image #75 which saw a thumbnailer landing - I installed #74 and upgraded only the thumbnailer binary packages and indeed it can be reproduced that way. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to thumbnailer in Ubuntu. https://bugs.launchpad.net/bugs/1376500 Title: [regression] thumbnails and image previews displayed wrong Status in Camera App: Invalid Status in Gallery App: Invalid Status in Ubuntu UI Toolkit: Invalid Status in “thumbnailer” package in Ubuntu: Confirmed Bug description: build 76 rtm-proposed on krillin Take a picture with camera-app swipe to the right to display it it looks squashed and like it's being displayed at the wrong aspect ration open the gallery-app and view the photo and it looks equally bad share the photo to messaging-app, and the preview of the photo is black copy the photo to your desktop and open there and the photo looks fine these are all new regressions, not sure what layer it's in bug guessing a low layer as gallery, camera and messaging-app have not changed in this regard To manage notifications about this bug go to: https://bugs.launchpad.net/camera-app/+bug/1376500/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1371032] Re: Cannot send MMS from Yoigo
Victor provided the log so setting this to confirmed. If you have all
the information you need then set it to Triaged
** Changed in: ofono (Ubuntu)
Status: Incomplete = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1371032
Title:
Cannot send MMS from Yoigo
Status in “network-manager” package in Ubuntu:
New
Status in “ofono” package in Ubuntu:
Confirmed
Bug description:
phablet@ubuntu-phablet:~$ /usr/share/ofono/scripts/list-contexts
[ /ril_1 ]
[ /ril_0 ]
[ /ril_0/context1 ]
AccessPointName = internet
Name = Yoigo Internet
Password =
Protocol = ip
IPv6.Settings = { }
Type = internet
Active = 1
Username =
Settings = { DomainNameServers=217.168.13.34,46.6.113.2,
Address=10.192.132.31 Method=static Netmask=255.255.255.0 Gateway=10.192.132.31
Interface=ccmni0 }
[ /ril_0/context2 ]
AccessPointName = mms
MessageCenter = http://mmss/
Name = Yoigo MMS
Password =
Protocol = ip
MessageProxy = 193.209.134.141:80
IPv6.Settings = { }
Type = mms
Active = 0
Username =
Settings = { }
phablet@ubuntu-phablet:~$ /usr/share/ofono/scripts/activate-context /ril_0 2
Error activating /ril_0/context2: org.ofono.Error.NotAttached: GPRS is not
attached
phablet@ubuntu-phablet:~$ /usr/share/ofono/scripts/activate-context
/ril_0 1
Additional info:
- I didn't see any error in the messaging app.
- Couldn't send nor receive MMS.
- 3G connection is activated, but usually after a reboot. After a while, it
looses it.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1371032/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1367417] Re: app crashes after address-book-service restarts
** Project changed: address-book-app = address-book-app (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to address-book-app in Ubuntu. https://bugs.launchpad.net/bugs/1367417 Title: app crashes after address-book-service restarts Status in “address-book-app” package in Ubuntu: In Progress Status in “qtpim-opensource-src” package in Ubuntu: New Bug description: build 25 on krillin Steps to reproduce: - open messaging-app - open a thread from a contact - click the contacts button to open the contacts app - press the back button (to return to messaging-app) - switch back to contacts app, scrolling works fine - switch back to messaging-app - now run restart address-book-service and wait until it starts - switch back to address-book-app and start scrolling in list view and app crashes You will get a crash file in /var/crash/_usr_bin_address-book-app.crash You can upack the core file by doing: apport-unpack path-to-crash-file somedir cd somedir gdb /usr/bin/address-book-app CoreDump [Thread debugging using libthread_db enabled] Using host libthread_db library /lib/arm-linux-gnueabihf/libthread_db.so.1. Core was generated by `/usr/bin/address-book-app addressbook:///contact?callback=messaging-app.desktop'. Program terminated with signal SIGSEGV, Segmentation fault. #0 0xaaada450 in QtContacts::QContactId::operator=(QtContacts::QContactId const) () from /usr/lib/arm-linux-gnueabihf/libQt5Contacts.so.5 (gdb) bt #0 0xaaada450 in QtContacts::QContactId::operator=(QtContacts::QContactId const) () from /usr/lib/arm-linux-gnueabihf/libQt5Contacts.so.5 #1 0xaab85a58 in ?? () from /usr/lib/arm-linux-gnueabihf/qt5/qml/QtContacts/libdeclarative_contacts.so Backtrace stopped: previous frame identical to this frame (corrupt stack?) (gdb) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/address-book-app/+bug/1367417/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1373855] Re: Photos taken with Krillin camera show as black in preview and when set as wallpaper
This failure first occured in image #58 with the following changelog: http://people.canonical.com/~ogra/touch-image-stats/rtm/58.changes cameraplugin-aal looks suspect -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to content-hub in Ubuntu. https://bugs.launchpad.net/bugs/1373855 Title: Photos taken with Krillin camera show as black in preview and when set as wallpaper Status in “content-hub” package in Ubuntu: New Bug description: Prerequisite: You should already have taken a photo with the Krillins camera 1. Open the System Settings application 2. Open the Background panel 3. From the 'Custom' section select 'Add an Image' 4. Choose the image that you took with the phones camera from the gallery 5. Confirm that the image appears in preview correctly and press 'Set' 6. Confirm that the image is selected in the Background panel 7. Press the power button twice, to return the phone to the lock screen 8. Confirm that the image is shown as the background on the lock screen Steps 5 and 8 fail since the image is black This is very similar behaviour to : https://launchpad.net/bugs/1373462, but might not be a duplicate since when that bug was reported, Krillin camera images did work. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: ubuntu-system-settings 0.3+14.10.20140924-0ubuntu1 [origin: Ubuntu RTM] Uname: Linux 3.4.67 armv7l ApportVersion: 2.14.7-0ubuntu1 Architecture: armhf Date: Thu Sep 25 09:48:54 2014 InstallationDate: Installed on 2014-09-25 (0 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20140925-030205) SourcePackage: ubuntu-system-settings UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/content-hub/+bug/1373855/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1374015] [NEW] Accepting a call with the dialer app open while a message notification is present leaves us unable to hang up the call
Public bug reported: Steps to reproduce: 1. Open the dialer application on the SUT 2. From another device, send an SMS message to the SUT 3. Soon after, place a call to the SUT, such that you receive the call snap decision after the message snap decision 4. Accept the call snap decision Expected result: The call snap decision closes and we are brought to the active call screen in the dialer-app Actual result: The snap decision closes and we remain on the dial pad screen - the notification bar is green indicating an active call and we can talk through the line, however once we click the notification bar we are brought to a corrupt version of the active call screen - there is no time shown and pressing the hang up button does nothing ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: dialer-app 0.1+14.10.20140924-0ubuntu1 [origin: unknown] Uname: Linux 3.4.67 armv7l ApportVersion: 2.14.7-0ubuntu1 Architecture: armhf Date: Thu Sep 25 15:35:44 2014 InstallationDate: Installed on 2014-09-25 (0 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20140925-100336) SourcePackage: dialer-app UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: dialer-app (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug armhf third-party-packages utopic -- 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/1374015 Title: Accepting a call with the dialer app open while a message notification is present leaves us unable to hang up the call Status in “dialer-app” package in Ubuntu: New Bug description: Steps to reproduce: 1. Open the dialer application on the SUT 2. From another device, send an SMS message to the SUT 3. Soon after, place a call to the SUT, such that you receive the call snap decision after the message snap decision 4. Accept the call snap decision Expected result: The call snap decision closes and we are brought to the active call screen in the dialer-app Actual result: The snap decision closes and we remain on the dial pad screen - the notification bar is green indicating an active call and we can talk through the line, however once we click the notification bar we are brought to a corrupt version of the active call screen - there is no time shown and pressing the hang up button does nothing ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: dialer-app 0.1+14.10.20140924-0ubuntu1 [origin: unknown] Uname: Linux 3.4.67 armv7l ApportVersion: 2.14.7-0ubuntu1 Architecture: armhf Date: Thu Sep 25 15:35:44 2014 InstallationDate: Installed on 2014-09-25 (0 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20140925-100336) SourcePackage: dialer-app UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dialer-app/+bug/1374015/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1374015] Re: Accepting a call with the dialer app open while a message notification is present leaves us unable to hang up the call
*** This bug is a duplicate of bug 1370240 *** https://bugs.launchpad.net/bugs/1370240 ** This bug has been marked a duplicate of bug 1370240 Clicking a snap decision button makes the foreground application inactive -- 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/1374015 Title: Accepting a call with the dialer app open while a message notification is present leaves us unable to hang up the call Status in “dialer-app” package in Ubuntu: New Bug description: Steps to reproduce: 1. Open the dialer application on the SUT 2. From another device, send an SMS message to the SUT 3. Soon after, place a call to the SUT, such that you receive the call snap decision after the message snap decision 4. Accept the call snap decision Expected result: The call snap decision closes and we are brought to the active call screen in the dialer-app Actual result: The snap decision closes and we remain on the dial pad screen - the notification bar is green indicating an active call and we can talk through the line, however once we click the notification bar we are brought to a corrupt version of the active call screen - there is no time shown and pressing the hang up button does nothing ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: dialer-app 0.1+14.10.20140924-0ubuntu1 [origin: unknown] Uname: Linux 3.4.67 armv7l ApportVersion: 2.14.7-0ubuntu1 Architecture: armhf Date: Thu Sep 25 15:35:44 2014 InstallationDate: Installed on 2014-09-25 (0 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20140925-100336) SourcePackage: dialer-app UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dialer-app/+bug/1374015/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1373431] [NEW] Opening indicators while entering a URL resets the URL bar
Public bug reported: Steps to reproduce: 1. Click on the URL bar 2. Enter some text 'http://www.goog' for example 3. Open any indicator all the way 4. Close the indicator again 5. Check the contents of the URL bar Expected result URL bar contains 'http://www.goog' Actual result URL bar contains the url of the page we were just on (e.g. start.ubuntu.com) ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: webbrowser-app 0.23+14.10.20140922-0ubuntu1 [origin: LP-PPA-ci-train-ppa-service-landing-003] Uname: Linux 3.4.67 armv7l ApportVersion: 2.14.7-0ubuntu1 Architecture: armhf Date: Wed Sep 24 13:34:07 2014 InstallationDate: Installed on 2014-09-24 (0 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20140924-030204) SourcePackage: webbrowser-app UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: webbrowser-app (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug armhf exploratory qa-daily-testing third-party-packages utopic ** Tags added: exploratory qa-daily-testing -- 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/1373431 Title: Opening indicators while entering a URL resets the URL bar Status in “webbrowser-app” package in Ubuntu: New Bug description: Steps to reproduce: 1. Click on the URL bar 2. Enter some text 'http://www.goog' for example 3. Open any indicator all the way 4. Close the indicator again 5. Check the contents of the URL bar Expected result URL bar contains 'http://www.goog' Actual result URL bar contains the url of the page we were just on (e.g. start.ubuntu.com) ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: webbrowser-app 0.23+14.10.20140922-0ubuntu1 [origin: LP-PPA-ci-train-ppa-service-landing-003] Uname: Linux 3.4.67 armv7l ApportVersion: 2.14.7-0ubuntu1 Architecture: armhf Date: Wed Sep 24 13:34:07 2014 InstallationDate: Installed on 2014-09-24 (0 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20140924-030204) SourcePackage: webbrowser-app UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1373431/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1373431] Re: Opening indicators while entering a URL resets the URL bar
oSoMoN brendand, not a bug, it’s the intended behaviour: unfocusing the address bar resets the URL to the previous validated one. brendand oSoMoN, sure - but pulling the indicator down shouldn't unfocus it. maybe it's more of a unity8 bug then oSoMoN brendand, maybe, indeed oSoMoN brendand, it doesn’t sound utterly wrong that the current app looses focus when pulling down an indicator though john-mcaleely rsalveti, https://code-review.barajas-git.canonical.com/#/c/724/ brendand greyback_, mzanetti - any opinion on that ^ greyback_ brendand: IMO if you're interacting with an indicator, the app should be unfocused. E.g. a game should pause in that situation, as you're not interacting with it brendand greyback_, yeah but it seems to have some unintended consequences ricmm greyback_: brendand so there used to exist (maybe still?) design for these kind of overlays covering parts of an app ricmm that were more greyscale than the black and white focused/unfocused greyback_ brendand: it is up to the application to decide how to behave brendand greyback_, and the user isn't really aware that they are incidentally unfocusing the applications greyback_ brendand: better to tell the app what's happening, than not ricmm probably another thing that fell through the cracks of inifinite revs cwayne will it just recompile the caches? greyback_ ricmm: probably, but nothing I've been informed about recently ricmm I mean I remember tvoss had a set of definitions for unfocused states ricmm and ways to deliver the location of overlays to the app and so forth ricmm maybe in 2016 greyback_ I vaguely heard about that idea :) brendand oSoMoN, the user wouldn't expect that if they swipe down the indicator to check something then the url they are typing is gone brendand oSoMoN, whereas they might expect that if they click out of the url bar explicitly then it does oSoMoN brendand, right, unfortunately the same thing happens in both cases: the address bar looses focus brendand oSoMoN, technically both you and greyback_ are correct, it just seems really wrong. and it's certainly not what other mobile browsers do brendand oSoMoN, so i don't think it's invalid, although i can understand if you don't want to fix it immediately brendand oSoMoN, actually in android pulling down the menu doesn't unfocus anything oSoMoN brendand, ok, feel free to reset the status of the bug report then, and please paste our conversation here in the bug report for reference ** Changed in: webbrowser-app (Ubuntu) Status: Invalid = 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/1373431 Title: Opening indicators while entering a URL resets the URL bar Status in “webbrowser-app” package in Ubuntu: New Bug description: Steps to reproduce: 1. Click on the URL bar 2. Enter some text 'http://www.goog' for example 3. Open any indicator all the way 4. Close the indicator again 5. Check the contents of the URL bar Expected result URL bar contains 'http://www.goog' Actual result URL bar contains the url of the page we were just on (e.g. start.ubuntu.com) ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: webbrowser-app 0.23+14.10.20140922-0ubuntu1 [origin: LP-PPA-ci-train-ppa-service-landing-003] Uname: Linux 3.4.67 armv7l ApportVersion: 2.14.7-0ubuntu1 Architecture: armhf Date: Wed Sep 24 13:34:07 2014 InstallationDate: Installed on 2014-09-24 (0 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20140924-030204) SourcePackage: webbrowser-app UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1373431/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1370127] Re: unity8 UI freeze for some time - external translations process/gettext a clue
** Description changed: Brendan Donegan found that unity8 froze Was only able to get a partial backtrace: http://pastebin.com/REPjL5Pq which points to the external translation process (the gettext binary) for libusermetrics acting weird (quoting Pete Woods) The unity8.log http://paste.ubuntu.com/8358720/ contains this: - QProcess: Destroyed while process (gettext) is still running. + QProcess: Destroyed while process (gettext) is still running. which furthers Pete's hypothesis + + This happened when trying to open the camera-app via content-hub when + creating a new MMS. Specifically it froze whilst camera-app was opening. -- 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/1370127 Title: unity8 UI freeze for some time - external translations process/gettext a clue Status in “libusermetrics” package in Ubuntu: New Status in “unity8” package in Ubuntu: New Bug description: Brendan Donegan found that unity8 froze Was only able to get a partial backtrace: http://pastebin.com/REPjL5Pq which points to the external translation process (the gettext binary) for libusermetrics acting weird (quoting Pete Woods) The unity8.log http://paste.ubuntu.com/8358720/ contains this: QProcess: Destroyed while process (gettext) is still running. which furthers Pete's hypothesis This happened when trying to open the camera-app via content-hub when creating a new MMS. Specifically it froze whilst camera-app was opening. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libusermetrics/+bug/1370127/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1368295] [NEW] latest UI toolkit causes visual glitch in Recent tab of dialer-app
Public bug reported: Prerequisites: You should have a received or missed call in the call log. Steps to reproduce: 1. Open the dialer app 2. Slide the Recent tab fully up, opening that page Expected result: The page appears normally Actual result: There is a clear visual glitch as in the attached screenshot. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: qtdeclarative5-ubuntu-ui-toolkit-plugin 1.1.1239+14.10.20140908-0ubuntu1 Uname: Linux 3.4.0-5-mako armv7l ApportVersion: 2.14.7-0ubuntu2 Architecture: armhf Date: Thu Sep 11 15:19:12 2014 InstallationDate: Installed on 2014-09-11 (0 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20140911-120509) SourcePackage: ubuntu-ui-toolkit UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubuntu-ui-toolkit (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: apport-bug armhf qa-daily-testing rtm14 utopic ** Attachment added: recent calls page glitched https://bugs.launchpad.net/bugs/1368295/+attachment/4201553/+files/recent.png -- 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/1368295 Title: latest UI toolkit causes visual glitch in Recent tab of dialer-app Status in “ubuntu-ui-toolkit” package in Ubuntu: Confirmed Bug description: Prerequisites: You should have a received or missed call in the call log. Steps to reproduce: 1. Open the dialer app 2. Slide the Recent tab fully up, opening that page Expected result: The page appears normally Actual result: There is a clear visual glitch as in the attached screenshot. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: qtdeclarative5-ubuntu-ui-toolkit-plugin 1.1.1239+14.10.20140908-0ubuntu1 Uname: Linux 3.4.0-5-mako armv7l ApportVersion: 2.14.7-0ubuntu2 Architecture: armhf Date: Thu Sep 11 15:19:12 2014 InstallationDate: Installed on 2014-09-11 (0 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20140911-120509) SourcePackage: ubuntu-ui-toolkit UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1368295/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1367334] Re: Local music previews non-functional
** Tags added: rtm14 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-scope-mediascanner in Ubuntu. https://bugs.launchpad.net/bugs/1367334 Title: Local music previews non-functional Status in “unity-scope-mediascanner” package in Ubuntu: Confirmed Bug description: Put some music on the device, and try and preview it using the local music scope. The play buttons do not work. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-scope-mediascanner/+bug/1367334/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1365967] [NEW] Locking/unlocking the device while a login page is open makes the page disappear and leaves u-s-s-o-a in an unusable state
Public bug reported: 1.) Select any account from the Add Account screen 2.) When you get the login page, lock the screen 3.) Unlock the screen and check if the login page is still there The actual result is that it has disappeared and the add account screen is unusable. ** Affects: ubuntu-system-settings-online-accounts (Ubuntu) Importance: Undecided Status: New ** Tags: exploratory qa-daily-testing rtm14 testcase -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-system-settings- online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1365967 Title: Locking/unlocking the device while a login page is open makes the page disappear and leaves u-s-s-o-a in an unusable state Status in “ubuntu-system-settings-online-accounts” package in Ubuntu: New Bug description: 1.) Select any account from the Add Account screen 2.) When you get the login page, lock the screen 3.) Unlock the screen and check if the login page is still there The actual result is that it has disappeared and the add account screen is unusable. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-system-settings-online-accounts/+bug/1365967/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1365967] Re: Locking/unlocking the device while a login page is open makes the page disappear and leaves u-s-s-o-a in an unusable state
*** This bug is a duplicate of bug 1365972 *** https://bugs.launchpad.net/bugs/1365972 ** This bug has been marked a duplicate of bug 1365972 Locking/unlocking the device while a login page is open makes the page disappear and leaves u-s-s-o-a in an unusable state -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-system-settings- online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1365967 Title: Locking/unlocking the device while a login page is open makes the page disappear and leaves u-s-s-o-a in an unusable state Status in “ubuntu-system-settings-online-accounts” package in Ubuntu: New Bug description: 1.) Select any account from the Add Account screen 2.) When you get the login page, lock the screen 3.) Unlock the screen and check if the login page is still there The actual result is that it has disappeared and the add account screen is unusable. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-system-settings-online-accounts/+bug/1365967/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1365972] [NEW] Locking/unlocking the device while a login page is open makes the page disappear and leaves u-s-s-o-a in an unusable state
Public bug reported: 1.) Select any account from the Add Account screen 2.) When you get the login page, lock the screen 3.) Unlock the screen and check if the login page is still there The actual result is that it has disappeared and the add account screen is unusable. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: ubuntu-system-settings-online-accounts 0.4+14.10.20140827-0ubuntu1 [origin: Ubuntu RTM] Uname: Linux 3.4.67 armv7l ApportVersion: 2.14.7-0ubuntu1 Architecture: armhf Date: Fri Sep 5 11:59:50 2014 InstallationDate: Installed on 2014-09-05 (0 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20140905-030204) SourcePackage: ubuntu-system-settings-online-accounts UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubuntu-system-settings-online-accounts (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug armhf exploratory qa-daily-testing rtm14 testcase third-party-packages utopic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-system-settings- online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1365972 Title: Locking/unlocking the device while a login page is open makes the page disappear and leaves u-s-s-o-a in an unusable state Status in “ubuntu-system-settings-online-accounts” package in Ubuntu: New Bug description: 1.) Select any account from the Add Account screen 2.) When you get the login page, lock the screen 3.) Unlock the screen and check if the login page is still there The actual result is that it has disappeared and the add account screen is unusable. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: ubuntu-system-settings-online-accounts 0.4+14.10.20140827-0ubuntu1 [origin: Ubuntu RTM] Uname: Linux 3.4.67 armv7l ApportVersion: 2.14.7-0ubuntu1 Architecture: armhf Date: Fri Sep 5 11:59:50 2014 InstallationDate: Installed on 2014-09-05 (0 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20140905-030204) SourcePackage: ubuntu-system-settings-online-accounts UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-system-settings-online-accounts/+bug/1365972/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1288332] Re: Orientation lock not available (rotation/portrait lock)
The orientation lock option is there in system-settings now but doesn't work. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gsettings-ubuntu-touch- schemas in Ubuntu. https://bugs.launchpad.net/bugs/1288332 Title: Orientation lock not available (rotation/portrait lock) Status in Platform API: In Progress Status in Qt integration with the Mir display server: In Progress Status in QT Ubuntu: In Progress Status in “gsettings-ubuntu-touch-schemas” package in Ubuntu: Fix Released Status in “ubuntu-system-settings” package in Ubuntu: Fix Released Status in “ubuntu-ui-toolkit” package in Ubuntu: Opinion Status in “unity8” package in Ubuntu: Opinion Bug description: Ubuntu Trusty r188 1. Open System Settings. 2. Try to turn on Orientation Lock. What happens: There's no such setting. https://wiki.ubuntu.com/SystemSettings#phone-quick-access: The quick access area is a group of list items at the top of the overview screen. It should always contain 'Orientation Lock'... To manage notifications about this bug go to: https://bugs.launchpad.net/platform-api/+bug/1288332/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1362671] [NEW] after flashing with --wipe the keyboard does not appear (rebooting fixes it)
Public bug reported: On RTM image #2 we're finding that after flashing with --wipe, any time the keyboard should be opened, it isn't - a simple example is to compose a message in the Messaging application. Rebooting the device makes this problem go away. ** Affects: ubuntu-keyboard (Ubuntu) Importance: Undecided Status: New ** Tags: qa-daily-testing rtm14 ** Tags added: qa-daily-testing rtm14 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-keyboard in Ubuntu. https://bugs.launchpad.net/bugs/1362671 Title: after flashing with --wipe the keyboard does not appear (rebooting fixes it) Status in “ubuntu-keyboard” package in Ubuntu: New Bug description: On RTM image #2 we're finding that after flashing with --wipe, any time the keyboard should be opened, it isn't - a simple example is to compose a message in the Messaging application. Rebooting the device makes this problem go away. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-keyboard/+bug/1362671/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1218294] Re: [dialer-app] During a live call, volume adjustment doesn't work in earpiece
This was fixed last week in image 203 ** Changed in: pulseaudio (Ubuntu) Status: Confirmed = Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1218294 Title: [dialer-app] During a live call, volume adjustment doesn't work in earpiece Status in Ubuntu UX bugs: Fix Committed Status in “pulseaudio” package in Ubuntu: Fix Released Bug description: Current situation: Can't adjust the voice volume during a live call, making it difficult to hear the receiver Desired: Can adjust volume during a live call (Eg using the volume buttons on the device) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1218294/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1362133] [NEW] Rebooting after disabling wifi leaves wifi in wrong state (enabled but doesn't show networks)
Public bug reported: Steps to reproduce: 1.) Open the network indicator 2.) Toggle the Wi-Fi switch to 'Off' 3.) Reboot the device 4.) Open the network indicator Expected result: Wi-Fi is either disabled and shows no networks, or is enabled and shows networks Actual result: Wi-Fi is enabled and shows no networks. Toggling it on and off returns it to normal. ** Affects: indicator-network (Ubuntu) Importance: Undecided Status: New ** Tags: exploratory qa-daily-testing rtm14 testcase ** Attachment added: enabled no network https://bugs.launchpad.net/bugs/1362133/+attachment/4188226/+files/enabled_no_networks.png -- 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/1362133 Title: Rebooting after disabling wifi leaves wifi in wrong state (enabled but doesn't show networks) Status in “indicator-network” package in Ubuntu: New Bug description: Steps to reproduce: 1.) Open the network indicator 2.) Toggle the Wi-Fi switch to 'Off' 3.) Reboot the device 4.) Open the network indicator Expected result: Wi-Fi is either disabled and shows no networks, or is enabled and shows networks Actual result: Wi-Fi is enabled and shows no networks. Toggling it on and off returns it to normal. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1362133/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1353935] [NEW] click packages fail with mysterious error when disk is full
Public bug reported: Sometimes I get the following error when trying to manually install a click package. Package works fine in other systems pkcon install-local com.canonical.scopes.etsy_1.0.10_armhf.click mhf.click Installing files [=] Finished [=] Installing files [=] Waiting for authentication [=] Starting [=] Finished [=] Fatal error: /home/phablet/clicks/com.canonical.scopes.etsy_1.0.10_armhf.click failed to install. Traceback (most recent call last): File /usr/bin/click, line 86, in module sys.exit(main()) File /usr/bin/click, line 82, in main return mod.run(args) File /usr/lib/python3/dist-packages/click/commands/install.py, line 57, in run package_path, user=options.user, all_users=options.all_users) File /usr/lib/python3/dist-packages/click/install.py, line 384, in install path, user=user, all_users=all_users) File /usr/lib/python3/dist-packages/click/install.py, line 344, in _unpack env=env, **kwargs) File /usr/lib/python3.4/subprocess.py, line 556, in check_call retcode = call(*popenargs, **kwargs) File /usr/lib/python3.4/subprocess.py, line 537, in call with Popen(*popenargs, **kwargs) as p: File /usr/lib/python3.4/subprocess.py, line 858, in __init__ restore_signals, start_new_session) File /usr/lib/python3.4/subprocess.py, line 1457, in _execute_child raise child_exception_type(err_msg) subprocess.SubprocessError: Exception occurred in preexec_fn. This appears to be because the disk is full. As well as making this error cleaner and clearer, some general testing should be done around what happens when we try to install click apps when the disk is full. ** Affects: click (Ubuntu) Importance: Undecided Status: Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to click in Ubuntu. https://bugs.launchpad.net/bugs/1353935 Title: click packages fail with mysterious error when disk is full Status in “click” package in Ubuntu: Confirmed Bug description: Sometimes I get the following error when trying to manually install a click package. Package works fine in other systems pkcon install-local com.canonical.scopes.etsy_1.0.10_armhf.click mhf.click Installing files [=] Finished [=] Installing files [=] Waiting for authentication [=] Starting [=] Finished [=] Fatal error: /home/phablet/clicks/com.canonical.scopes.etsy_1.0.10_armhf.click failed to install. Traceback (most recent call last): File /usr/bin/click, line 86, in module sys.exit(main()) File /usr/bin/click, line 82, in main return mod.run(args) File /usr/lib/python3/dist-packages/click/commands/install.py, line 57, in run package_path, user=options.user, all_users=options.all_users) File /usr/lib/python3/dist-packages/click/install.py, line 384, in install path, user=user, all_users=all_users) File /usr/lib/python3/dist-packages/click/install.py, line 344, in _unpack env=env, **kwargs) File /usr/lib/python3.4/subprocess.py, line 556, in check_call retcode = call(*popenargs, **kwargs) File /usr/lib/python3.4/subprocess.py, line 537, in call with Popen(*popenargs, **kwargs) as p: File /usr/lib/python3.4/subprocess.py, line 858, in __init__ restore_signals, start_new_session) File /usr/lib/python3.4/subprocess.py, line 1457, in _execute_child raise child_exception_type(err_msg) subprocess.SubprocessError: Exception occurred in preexec_fn. This appears to be because the disk is full. As well as making this error cleaner and clearer, some general testing should be done around what happens when we try to install click apps when the disk is full. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/click/+bug/1353935/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1353513] [NEW] Facebook account page shows a blank entry in 'Access to this account'
Public bug reported: After creating an account for Facebook and going to that accounts details page, we see a list of 3 checkboxes under 'Access to this account'. Two are 'Contacts' and 'Notifications'. The other is blank. ** Affects: ubuntu-system-settings-online-accounts (Ubuntu) Importance: Undecided Status: New ** Tags: qa-daily-testing rtm14 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-system-settings- online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1353513 Title: Facebook account page shows a blank entry in 'Access to this account' Status in “ubuntu-system-settings-online-accounts” package in Ubuntu: New Bug description: After creating an account for Facebook and going to that accounts details page, we see a list of 3 checkboxes under 'Access to this account'. Two are 'Contacts' and 'Notifications'. The other is blank. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-system-settings-online-accounts/+bug/1353513/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1353513] Re: Facebook account page shows a blank entry in 'Access to this account'
** Attachment added: Screenshot https://bugs.launchpad.net/ubuntu/+source/ubuntu-system-settings-online-accounts/+bug/1353513/+attachment/4171152/+files/facebook_account.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-system-settings- online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1353513 Title: Facebook account page shows a blank entry in 'Access to this account' Status in “ubuntu-system-settings-online-accounts” package in Ubuntu: New Bug description: After creating an account for Facebook and going to that accounts details page, we see a list of 3 checkboxes under 'Access to this account'. Two are 'Contacts' and 'Notifications'. The other is blank. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-system-settings-online-accounts/+bug/1353513/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1307430] Re: Grooveshark audio stops when not focused
*** This bug is a duplicate of bug 1249586 *** https://bugs.launchpad.net/bugs/1249586 ** This bug has been marked a duplicate of bug 1249586 music stops when app goes to background -- 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/1307430 Title: Grooveshark audio stops when not focused Status in Unity WebApps QML component: Confirmed Status in “webbrowser-app” package in Ubuntu: Confirmed Bug description: Song plays fine when locked or when browser is focussed, song stops on welcome or scope screen. https://www.youtube.com/watch?v=5CMbIFlDuRM shows this Go to grooveshark scope choose a song click play in grooveshark Browser opens - click play Listen to song. Lock phone: Song carries on Unlock phone: Song stops if welcome screen is displayed Swipe away unlock screen: Song stops if on app scope ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: webbrowser-app 0.23+14.04.20140411.1-0ubuntu1 Uname: Linux 3.4.0-5-mako armv7l ApportVersion: 2.14.1-0ubuntu2 Architecture: armhf Date: Mon Apr 14 11:52:48 2014 InstallationDate: Installed on 2014-04-14 (0 days ago) InstallationMedia: Ubuntu 14.04 LTS - armhf (20140414) SourcePackage: webbrowser-app UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/unity-webapps-qml/+bug/1307430/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1323844] Re: Ubuntu One account screen obscured by OSK
This no longer seems to be the case -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-keyboard in Ubuntu. https://bugs.launchpad.net/bugs/1323844 Title: Ubuntu One account screen obscured by OSK Status in Ubuntu Keyboard: Confirmed Status in Online Accounts setup for Ubuntu Touch: New Status in “ubuntu-keyboard” package in Ubuntu: Confirmed Bug description: per bug https://bugs.launchpad.net/ubuntu-keyboard/+bug/1321676 - go to system-settings-accounts and choose Ubuntu One - note that Cancel and Continue buttons are not visible once the OSK is displayed Use the anchorToKeyboard property as described here to fix it: http://nik90.com/ubuntu-touch-keyboard-tricks/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-keyboard/+bug/1323844/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1352939] [NEW] [UX performance] First time Ubuntu One login journey can be improved
Public bug reported: When we view an app after first boot and we are not logged into Ubuntu One, we click on the Install button and will be prompted to Go to accounts to set up our Ubuntu One account. Clicking this button first launches system settings, then launches online-accounts. This means that for this one action we need to start two applications and wait for them to load in sequence. This is messy and suboptimal in terms of user experience. ** Affects: unity-scope-click (Ubuntu) Importance: Undecided Status: New ** Tags: qa-daily-testing rtm14 ** Tags added: qa-daily-testing rtm14 -- 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/1352939 Title: [UX performance] First time Ubuntu One login journey can be improved Status in “unity-scope-click” package in Ubuntu: New Bug description: When we view an app after first boot and we are not logged into Ubuntu One, we click on the Install button and will be prompted to Go to accounts to set up our Ubuntu One account. Clicking this button first launches system settings, then launches online-accounts. This means that for this one action we need to start two applications and wait for them to load in sequence. This is messy and suboptimal in terms of user experience. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-scope-click/+bug/1352939/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1352744] Re: List of WiFi access point is empty
** Attachment added: indicator-network crash file https://bugs.launchpad.net/ubuntu/+source/ofono/+bug/1352744/+attachment/4170480/+files/_usr_lib_arm-linux-gnueabihf_indicator-network_indicator-network-service.32011.crash -- 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/1352744 Title: List of WiFi access point is empty Status in “indicator-network” package in Ubuntu: In Progress Status in “ofono” package in Ubuntu: Confirmed Bug description: Last known good image: #169 On mako build #17O the list of wifi access point in system-settings is empty and there is no network-indicator. Although already configured network is working correctly. Problem on errors.u.c https://errors.ubuntu.com/bucket/?id=/usr/lib/arm-linux-gnueabihf/indicator-network/indicator-network-service%3A11%3Achanged%3AModemManager%3A%3APrivate%3A%3Aofono_appeared%3AModemManager%3A%3APrivate%3A%3APrivate%3AModemManager%3A%3AModemManager%3Aconstruct ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: ofono 1.12.bzr6872+14.10.20140804-0ubuntu1 Uname: Linux 3.4.0-5-mako armv7l ApportVersion: 2.14.5-0ubuntu3 Architecture: armhf Date: Tue Aug 5 09:23:38 2014 InstallationDate: Installed on 2014-08-05 (0 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20140805-020204) SourcePackage: ofono UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1352744/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
