[Touch-packages] [Bug 1552410] Re: Cannot pair mako with 2014 Subaru Forester
Sorry it took so long to get to this, but I was finally able to test on my phone with OTA-8. The pairing worked as expected. -- 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/1552410 Title: Cannot pair mako with 2014 Subaru Forester Status in Canonical System Image: Confirmed Status in bluez package in Ubuntu: Confirmed Bug description: Since the bluez5 transition my mako has not been able to pair with the radio in my 2014 Subaru Forester. When the radio is put into pairing mode the phone sees the CAR_M_MEDIA device, but when I click "connect" the radio immediately shows "failed" and no PIN prompt is shown on the phone. Additionally, the entry in system-settings for the car stereo is left in a limbo state with the "forget" button inactive. The only way to remove the entry is to use bluetoothctl from the command line. Here's what the phone is currently running: current build number: 252 device name: mako channel: ubuntu-touch/rc-proposed/bq-aquaris.en last update: 2016-03-02 00:31:33 version version: 252 version ubuntu: 20160302 version device: 20160112 version custom: 20160201-5-vivid To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1552410/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1552410] Re: Cannot pair mako with 2014 Subaru Forester
** Attachment added: "hcidump of a pairing attempt" https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1552410/+attachment/4643207/+files/hcidump-hr.log -- 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/1552410 Title: Cannot pair mako with 2014 Subaru Forester Status in Canonical System Image: Confirmed Status in bluez package in Ubuntu: Confirmed Bug description: Since the bluez5 transition my mako has not been able to pair with the radio in my 2014 Subaru Forester. When the radio is put into pairing mode the phone sees the CAR_M_MEDIA device, but when I click "connect" the radio immediately shows "failed" and no PIN prompt is shown on the phone. Additionally, the entry in system-settings for the car stereo is left in a limbo state with the "forget" button inactive. The only way to remove the entry is to use bluetoothctl from the command line. Here's what the phone is currently running: current build number: 252 device name: mako channel: ubuntu-touch/rc-proposed/bq-aquaris.en last update: 2016-03-02 00:31:33 version version: 252 version ubuntu: 20160302 version device: 20160112 version custom: 20160201-5-vivid To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1552410/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1552410] Re: Cannot pair mako with 2014 Subaru Forester
Here's the syslog snippet from when I tried pairing using bluetoothctl ** Attachment added: "syslog part containing pairing attempt using bluetoothctl" https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1552410/+attachment/4641441/+files/syslog-snippet-bluetoothctl -- 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/1552410 Title: Cannot pair mako with 2014 Subaru Forester Status in Canonical System Image: Confirmed Status in bluez package in Ubuntu: Confirmed Bug description: Since the bluez5 transition my mako has not been able to pair with the radio in my 2014 Subaru Forester. When the radio is put into pairing mode the phone sees the CAR_M_MEDIA device, but when I click "connect" the radio immediately shows "failed" and no PIN prompt is shown on the phone. Additionally, the entry in system-settings for the car stereo is left in a limbo state with the "forget" button inactive. The only way to remove the entry is to use bluetoothctl from the command line. Here's what the phone is currently running: current build number: 252 device name: mako channel: ubuntu-touch/rc-proposed/bq-aquaris.en last update: 2016-03-02 00:31:33 version version: 252 version ubuntu: 20160302 version device: 20160112 version custom: 20160201-5-vivid To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1552410/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1552410] Re: Cannot pair mako with 2014 Subaru Forester
** Attachment added: "ubuntu-system-settings log" https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1552410/+attachment/4640868/+files/application-legacy-ubuntu-system-settings-.log -- 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/1552410 Title: Cannot pair mako with 2014 Subaru Forester Status in Canonical System Image: Confirmed Status in bluez package in Ubuntu: New Bug description: Since the bluez5 transition my mako has not been able to pair with the radio in my 2014 Subaru Forester. When the radio is put into pairing mode the phone sees the CAR_M_MEDIA device, but when I click "connect" the radio immediately shows "failed" and no PIN prompt is shown on the phone. Additionally, the entry in system-settings for the car stereo is left in a limbo state with the "forget" button inactive. The only way to remove the entry is to use bluetoothctl from the command line. Here's what the phone is currently running: current build number: 252 device name: mako channel: ubuntu-touch/rc-proposed/bq-aquaris.en last update: 2016-03-02 00:31:33 version version: 252 version ubuntu: 20160302 version device: 20160112 version custom: 20160201-5-vivid To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1552410/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1552410] Re: Cannot pair mako with 2014 Subaru Forester
Still didn't work for me. ** Attachment added: "syslog part containing pairing attempt" https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1552410/+attachment/4640867/+files/syslog-snippet -- 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/1552410 Title: Cannot pair mako with 2014 Subaru Forester Status in Canonical System Image: Confirmed Status in bluez package in Ubuntu: New Bug description: Since the bluez5 transition my mako has not been able to pair with the radio in my 2014 Subaru Forester. When the radio is put into pairing mode the phone sees the CAR_M_MEDIA device, but when I click "connect" the radio immediately shows "failed" and no PIN prompt is shown on the phone. Additionally, the entry in system-settings for the car stereo is left in a limbo state with the "forget" button inactive. The only way to remove the entry is to use bluetoothctl from the command line. Here's what the phone is currently running: current build number: 252 device name: mako channel: ubuntu-touch/rc-proposed/bq-aquaris.en last update: 2016-03-02 00:31:33 version version: 252 version ubuntu: 20160302 version device: 20160112 version custom: 20160201-5-vivid To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1552410/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1560094] Re: Starting bluez service is denied
** Branch linked: lp:~ssweeny/bluez/snappy-interface -- 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/1560094 Title: Starting bluez service is denied Status in bluez package in Ubuntu: In Progress Bug description: If snappy core is updated in the background (on Raspberry Pi 2), and then bluez installed, starting the service is failing. Denials: [ 45.955490] audit: type=1400 audit(1458574955.667:11): apparmor="DENIED" operation="mknod" profile="bluez5_bluez_5.37-2-armhf" name="/etc/dbus-1/system.d/bluez5_bluez_5.37-2-armhf.conf" pid=834 comm="c0 [ 46.197608] audit: type=1326 audit(1458574955.907:12): auid=4294967295 uid=0 gid=0 ses=4294967295 pid=831 comm="obexd" exe="/snaps/bluez5/5.37-2-armhf/usr/lib/bluetooth/obexd" sig=31 arch=4028 sysc0 [ 46.275680] audit: type=1400 audit(1458574955.987:13): apparmor="DENIED" operation="create" profile="bluez5_bluez_5.37-2-armhf" pid=829 comm="bluetoothd" family="bluetooth" sock_type="raw" protocol=1 [ 46.276483] audit: type=1326 audit(1458574955.987:14): auid=4294967295 uid=0 gid=0 ses=4294967295 pid=829 comm="bluetoothd" exe="/snaps/bluez5/5.37-2-armhf/usr/lib/bluetooth/bluetoothd" sig=31 arch=4000 [ 46.412021] audit: type=1326 audit(1458574956.123:15): auid=4294967295 uid=0 gid=0 ses=4294967295 pid=839 comm="obexd" exe="/snaps/bluez5/5.37-2-armhf/usr/lib/bluetooth/obexd" sig=31 arch=4028 sysc0 [ 46.504308] audit: type=1400 audit(1458574956.215:16): apparmor="DENIED" operation="mknod" profile="bluez5_bluez_5.37-2-armhf" name="/etc/dbus-1/system.d/bluez5_bluez_5.37-2-armhf.conf" pid=842 comm="c0 [ 46.520137] audit: type=1400 audit(1458574956.231:17): apparmor="DENIED" operation="create" profile="bluez5_bluez_5.37-2-armhf" pid=841 comm="bluetoothd" family="bluetooth" sock_type="raw" protocol=1 [ 46.520800] audit: type=1326 audit(1458574956.231:18): auid=4294967295 uid=0 gid=0 ses=4294967295 pid=841 comm="bluetoothd" exe="/snaps/bluez5/5.37-2-armhf/usr/lib/bluetooth/bluetoothd" sig=31 arch=4000 [ 46.625293] audit: type=1326 audit(1458574956.335:19): auid=4294967295 uid=0 gid=0 ses=4294967295 pid=844 comm="obexd" exe="/snaps/bluez5/5.37-2-armhf/usr/lib/bluetooth/obexd" sig=31 arch=4028 sysc0 [ 46.721080] audit: type=1400 audit(1458574956.431:20): apparmor="DENIED" operation="mknod" profile="bluez5_bluez_5.37-2-armhf" name="/etc/dbus-1/system.d/bluez5_bluez_5.37-2-armhf.conf" pid=847 comm="c2 If trying to start bluetootctl: [ 582.205066] audit: type=1400 audit(1458575491.915:31): apparmor="DENIED" operation="connect" profile="bluez5_bluetoothctl_5.37-2-armhf" name="/run/dbus/system_bus_socket" pid=993 comm="bluetoothctl" re0 [bluetooth]# ubuntu@localhost:~$ snappy list NameDate Version Developer bluez5 2016-02-04 5.37-2-armhf canonical canonical-pi2 2016-02-02 3.0 canonical canonical-pi2-linux 2016-02-03 4.3.0-1006-3 canonical ubuntu-core 2016-03-08 16.04.0-15.armhf canonical ubuntu@localhost:~$ ubuntu@localhost:~$ snappy info release: core/rolling architecture: armhf frameworks: bluez5.canonical apps: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1560094/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1552410] Re: Cannot pair mako with 2014 Subaru Forester
I tried to pair today using bluetoothctl but all I got back was Failed to pair: org.bluez.Error.AuthenticationRejected and the same "failed" message on the radio display. -- 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/1552410 Title: Cannot pair mako with 2014 Subaru Forester Status in Canonical System Image: Confirmed Status in bluez package in Ubuntu: New Bug description: Since the bluez5 transition my mako has not been able to pair with the radio in my 2014 Subaru Forester. When the radio is put into pairing mode the phone sees the CAR_M_MEDIA device, but when I click "connect" the radio immediately shows "failed" and no PIN prompt is shown on the phone. Additionally, the entry in system-settings for the car stereo is left in a limbo state with the "forget" button inactive. The only way to remove the entry is to use bluetoothctl from the command line. Here's what the phone is currently running: current build number: 252 device name: mako channel: ubuntu-touch/rc-proposed/bq-aquaris.en last update: 2016-03-02 00:31:33 version version: 252 version ubuntu: 20160302 version device: 20160112 version custom: 20160201-5-vivid To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1552410/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1558840] Re: Update downloads hang when connection changes
IIRC the Today scope doesn't make any network calls itself, but farms the queries out to the child scopes. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1558840 Title: Update downloads hang when connection changes Status in Canonical System Image: In Progress Status in qtbase-opensource-src package in Ubuntu: In Progress Bug description: Downloads that use QNetworkRequest will seemingly hang when the connection changes from mobile data to wifi and vice versa. It would be nice if they would resume when the connection switch is completed. This requires changes in the bearer backend to enable forced session roaming, as well as some changes in QNAM. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1558840/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1552410] Re: Cannot pair mako with 2014 Subaru Forester
Unfortunately the latest rc-proposed image does not fix the problem. -- 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/1552410 Title: Cannot pair mako with 2014 Subaru Forester Status in Canonical System Image: Confirmed Status in bluez package in Ubuntu: New Bug description: Since the bluez5 transition my mako has not been able to pair with the radio in my 2014 Subaru Forester. When the radio is put into pairing mode the phone sees the CAR_M_MEDIA device, but when I click "connect" the radio immediately shows "failed" and no PIN prompt is shown on the phone. Additionally, the entry in system-settings for the car stereo is left in a limbo state with the "forget" button inactive. The only way to remove the entry is to use bluetoothctl from the command line. Here's what the phone is currently running: current build number: 252 device name: mako channel: ubuntu-touch/rc-proposed/bq-aquaris.en last update: 2016-03-02 00:31:33 version version: 252 version ubuntu: 20160302 version device: 20160112 version custom: 20160201-5-vivid To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1552410/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1552410] Re: Cannot pair mako with 2014 Subaru Forester
It is intentional, as the bq-aquaris channel includes things like the HERE AGPS service. My BT keyboard, mouse, and headset all work so it's something to do with the HFP changes that came with bluez5 I have to assume, since before the switch I could pair with the car just fine. -- 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/1552410 Title: Cannot pair mako with 2014 Subaru Forester Status in Canonical System Image: New Status in bluez package in Ubuntu: New Bug description: Since the bluez5 transition my mako has not been able to pair with the radio in my 2014 Subaru Forester. When the radio is put into pairing mode the phone sees the CAR_M_MEDIA device, but when I click "connect" the radio immediately shows "failed" and no PIN prompt is shown on the phone. Additionally, the entry in system-settings for the car stereo is left in a limbo state with the "forget" button inactive. The only way to remove the entry is to use bluetoothctl from the command line. Here's what the phone is currently running: current build number: 252 device name: mako channel: ubuntu-touch/rc-proposed/bq-aquaris.en last update: 2016-03-02 00:31:33 version version: 252 version ubuntu: 20160302 version device: 20160112 version custom: 20160201-5-vivid To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1552410/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1552410] Re: Cannot pair mako with 2014 Subaru Forester
** Attachment added: "system-settings log showing some potentially interesting errors" https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1552410/+attachment/4586975/+files/application-legacy-ubuntu-system-settings-.log ** Also affects: canonical-devices-system-image Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1552410 Title: Cannot pair mako with 2014 Subaru Forester Status in Canonical System Image: New Status in bluez package in Ubuntu: New Bug description: Since the bluez5 transition my mako has not been able to pair with the radio in my 2014 Subaru Forester. When the radio is put into pairing mode the phone sees the CAR_M_MEDIA device, but when I click "connect" the radio immediately shows "failed" and no PIN prompt is shown on the phone. Additionally, the entry in system-settings for the car stereo is left in a limbo state with the "forget" button inactive. The only way to remove the entry is to use bluetoothctl from the command line. Here's what the phone is currently running: current build number: 252 device name: mako channel: ubuntu-touch/rc-proposed/bq-aquaris.en last update: 2016-03-02 00:31:33 version version: 252 version ubuntu: 20160302 version device: 20160112 version custom: 20160201-5-vivid To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1552410/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1552410] [NEW] Cannot pair mako with 2014 Subaru Forester
Public bug reported: Since the bluez5 transition my mako has not been able to pair with the radio in my 2014 Subaru Forester. When the radio is put into pairing mode the phone sees the CAR_M_MEDIA device, but when I click "connect" the radio immediately shows "failed" and no PIN prompt is shown on the phone. Additionally, the entry in system-settings for the car stereo is left in a limbo state with the "forget" button inactive. The only way to remove the entry is to use bluetoothctl from the command line. Here's what the phone is currently running: current build number: 252 device name: mako channel: ubuntu-touch/rc-proposed/bq-aquaris.en last update: 2016-03-02 00:31:33 version version: 252 version ubuntu: 20160302 version device: 20160112 version custom: 20160201-5-vivid ** Affects: canonical-devices-system-image Importance: Undecided Status: New ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Attachment added: "syslog" https://bugs.launchpad.net/bugs/1552410/+attachment/4586974/+files/syslog -- 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/1552410 Title: Cannot pair mako with 2014 Subaru Forester Status in Canonical System Image: New Status in bluez package in Ubuntu: New Bug description: Since the bluez5 transition my mako has not been able to pair with the radio in my 2014 Subaru Forester. When the radio is put into pairing mode the phone sees the CAR_M_MEDIA device, but when I click "connect" the radio immediately shows "failed" and no PIN prompt is shown on the phone. Additionally, the entry in system-settings for the car stereo is left in a limbo state with the "forget" button inactive. The only way to remove the entry is to use bluetoothctl from the command line. Here's what the phone is currently running: current build number: 252 device name: mako channel: ubuntu-touch/rc-proposed/bq-aquaris.en last update: 2016-03-02 00:31:33 version version: 252 version ubuntu: 20160302 version device: 20160112 version custom: 20160201-5-vivid To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1552410/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1137630] Re: Emojis are not shown in ubuntu applications (and phone)
In Settings -> Language & Text -> Keyboard Layouts make sure that Emoji is enabled, then use the globe icon on the keyboard to switch to that layout when typing a message. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1137630 Title: Emojis are not shown in ubuntu applications (and phone) Status in ttf-ancient-fonts package in Ubuntu: Fix Released Status in ubuntu-meta package in Ubuntu: Fix Released Status in ubuntu-touch-meta package in Ubuntu: Confirmed Bug description: Hi, As Ubuntu is being ported to tablets and phones, where communication is an important aspect of their fonctionality, I would like to ask whether it would be possible to add the glyphs of the emojis and other symbols, which have been defined in Unicode 6.0 and 6.1 to the Ubuntu font. If I am correct, the emoticons/emojis are code in Unicode from U+1F600 bis U+1F64F. However, other symbols like broken heart and others might also be interesting, for example: U+1F493 - U+1F493, U+1F4A1 - U+1F4A6, U+2639 - U+2642,... For those interested, these glyphs are currently included in the fonts-vlgothic package in the Ubuntu repositories. Cheers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ttf-ancient-fonts/+bug/1137630/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1462664] Re: [Ubuntu Phone] With WIFI = ON the GPS stops
** Changed in: location-service (Ubuntu) Assignee: Manuel de la Peña (mandel) => Scott Sweeny (ssweeny) -- 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/1462664 Title: [Ubuntu Phone] With WIFI = ON the GPS stops Status in Canonical System Image: Confirmed Status in Oxide: New Status in ubuntu-system-settings: New Status in location-service package in Ubuntu: Confirmed Bug description: Hi! Steps: 1. Enable WIFI = ON on phone. 2. Run one of these apps: GPS Navigation, HERE maps, Sensor Status. 3. Drive. 4. When you'll be into a WIFI area as a town or city, I'm thinking the WIFI will try to search WIFIs and then the GPS will stop, the GPS apps will not receive more new positions from the GPS. Extra info1: If you had GPS Navigation & Sensor running, both of them will not receive new GPS positions from the device. If you restart for example GPS Navigation, GPS Navigation will receive new positions, but Sensor Status not, until you restart it too. Extra info2: When the GPS stops the icon in the status disappears, but it you kill and relaunch the app, the icon will appear again. Thanks in advance! To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1462664/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1474739] Re: Move from ota4 image to ota5 image doesn't update the override file for the favourite apps
** Changed in: ubuntu-touch-customization-hooks (Ubuntu) Status: Triaged = In Progress ** Changed in: ubuntu-touch-customization-hooks (Ubuntu) Assignee: (unassigned) = Scott Sweeny (ssweeny) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-touch- customization-hooks in Ubuntu. https://bugs.launchpad.net/bugs/1474739 Title: Move from ota4 image to ota5 image doesn't update the override file for the favourite apps Status in Canonical System Image: Invalid Status in ubuntu-touch-customization-hooks package in Ubuntu: In Progress Bug description: STEPS: 1. install on arale image 2 from rc (equivalent to ota4) 2. Upgrade to image 4 (ota5 candidate) 3. Check the apps scope EXPECTED: I should see 8 apps in the favourite section ACTUAL: I still see 6 and the override file hasn't been updated VERSIONS: current build number: 4 device name: arale channel: ubuntu-touch/rc/meizu.en last update: 2015-07-14 14:49:50 version version: 4 version ubuntu: 20150713 version device: 20150709-8965e37 version custom: 20150709-814-6-40 MODIFICATIONS: Upgraded from image 2 to image 4 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1474739/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1401717] Re: Scope test fixture throws exception when scope uses cache_directory()
Given that this is part of the test framework and not functionality run on the phone itself is there any chance of this fix being backported to utopic? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-scopes-api in Ubuntu. https://bugs.launchpad.net/bugs/1401717 Title: Scope test fixture throws exception when scope uses cache_directory() Status in unity-scopes-api package in Ubuntu: Fix Committed Bug description: When using TypedScopeFixture to test a scope that makes use of cache_directory any tests will always fail with the following message (regardless of where the cache_directory call is in the scope code): C++ exception with description unity::LogicException: ScopeBase::cache_directory() cannot be called from constructor thrown in the test body. A similar problem with scope_directory() was solved by adding a set_scope_directory() method to the fixture. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-scopes-api/+bug/1401717/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1401717] [NEW] Scope test fixture throws exception when scope uses cache_directory()
Public bug reported: When using TypedScopeFixture to test a scope that makes use of cache_directory any tests will always fail with the following message (regardless of where the cache_directory call is in the scope code): C++ exception with description unity::LogicException: ScopeBase::cache_directory() cannot be called from constructor thrown in the test body. A similar problem with scope_directory() was solved by adding a set_scope_directory() method to the fixture. ** Affects: unity-scopes-api (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-scopes-api in Ubuntu. https://bugs.launchpad.net/bugs/1401717 Title: Scope test fixture throws exception when scope uses cache_directory() Status in unity-scopes-api package in Ubuntu: New Bug description: When using TypedScopeFixture to test a scope that makes use of cache_directory any tests will always fail with the following message (regardless of where the cache_directory call is in the scope code): C++ exception with description unity::LogicException: ScopeBase::cache_directory() cannot be called from constructor thrown in the test body. A similar problem with scope_directory() was solved by adding a set_scope_directory() method to the fixture. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-scopes-api/+bug/1401717/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1350969] Re: Can't dismiss bottom-edge menu
This appears to be fixed with the latest app update. ** Changed in: camera-app (Ubuntu) Status: New = Fix Released -- 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/1350969 Title: Can't dismiss bottom-edge menu Status in “camera-app” package in Ubuntu: Fix Released Bug description: Using a mako on image 162 (though this has happened in the last few images as well) in the camera app if you swipe up the bottom-edge menu (location, flash, HDR options) there's no obvious way to dismiss said menu and go back to a functioning camera. You can swipe to the existing pictures or leave the app (which doesn't save any settings changes for next time) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/camera-app/+bug/1350969/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1350969] [NEW] Can't dismiss bottom-edge menu
Public bug reported: Using a mako on image 162 (though this has happened in the last few images as well) in the camera app if you swipe up the bottom-edge menu (location, flash, HDR options) there's no obvious way to dismiss said menu and go back to a functioning camera. You can swipe to the existing pictures or leave the app (which doesn't save any settings changes for next time) ** 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/1350969 Title: Can't dismiss bottom-edge menu Status in “camera-app” package in Ubuntu: New Bug description: Using a mako on image 162 (though this has happened in the last few images as well) in the camera app if you swipe up the bottom-edge menu (location, flash, HDR options) there's no obvious way to dismiss said menu and go back to a functioning camera. You can swipe to the existing pictures or leave the app (which doesn't save any settings changes for next time) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/camera-app/+bug/1350969/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
