[Touch-packages] [Bug 1723372] [NEW] nmcli pollutes terse output with unrequested information
Public bug reported: For example on my system with a wifi device named wlp2s0, run the following command which should just print out the three requested fields: $ nmcli -t -f SSID,CHAN,FREQ d wifi list ifname wlp2s0 wlp2s0 Canonical:1:2412 MHz Canonical:6:2437 MHz Canonical:11:2462 MHz Canonical:40:5200 MHz Canonical:36:5180 MHz ... The first line of output is the interface name and should not be included. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: network-manager 1.4.4-1ubuntu3.2 ProcVersionSignature: Ubuntu 4.10.0-32.36-generic 4.10.17 Uname: Linux 4.10.0-32-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.4-0ubuntu4.5 Architecture: amd64 CurrentDesktop: Unity:Unity7 Date: Fri Oct 13 10:17:13 2017 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2017-04-18 (177 days ago) InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412) IpRoute: default via 10.20.64.1 dev enxa0cec802a800 proto static metric 100 10.20.64.0/21 dev enxa0cec802a800 proto kernel scope link src 10.20.66.44 metric 100 10.111.44.0/24 dev lxdbr0 proto kernel scope link src 10.111.44.1 169.254.0.0/16 dev enxa0cec802a800 scope link metric 1000 NetworkManager.conf: [main] plugins=ifupdown,keyfile [ifupdown] managed=false NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH lxdbr0 bridgeconnected /org/freedesktop/NetworkManager/Devices/3 lxdbr0 6e757793-2287-4147-8426-7585435bbe4e /org/freedesktop/NetworkManager/ActiveConnection/1 enxa0cec802a800 ethernet connected /org/freedesktop/NetworkManager/Devices/5 Wired connection 1 d7f88012-4a23-3692-bbf2-64f2c5854f29 /org/freedesktop/NetworkManager/ActiveConnection/9 wlp2s0 wifi disconnected /org/freedesktop/NetworkManager/Devices/1 -- -- -- lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/0 -- -- -- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.4.4connected started full enabled enabled enabled enabled enabled ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug zesty -- 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/1723372 Title: nmcli pollutes terse output with unrequested information Status in network-manager package in Ubuntu: New Bug description: For example on my system with a wifi device named wlp2s0, run the following command which should just print out the three requested fields: $ nmcli -t -f SSID,CHAN,FREQ d wifi list ifname wlp2s0 wlp2s0 Canonical:1:2412 MHz Canonical:6:2437 MHz Canonical:11:2462 MHz Canonical:40:5200 MHz Canonical:36:5180 MHz ... The first line of output is the interface name and should not be included. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: network-manager 1.4.4-1ubuntu3.2 ProcVersionSignature: Ubuntu 4.10.0-32.36-generic 4.10.17 Uname: Linux 4.10.0-32-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.4-0ubuntu4.5 Architecture: amd64 CurrentDesktop: Unity:Unity7 Date: Fri Oct 13 10:17:13 2017 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2017-04-18 (177 days ago) InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412) IpRoute: default via 10.20.64.1 dev enxa0cec802a800 proto static metric 100 10.20.64.0/21 dev enxa0cec802a800 proto kernel scope link src 10.20.66.44 metric 100 10.111.44.0/24 dev lxdbr0 proto kernel scope link src 10.111.44.1 169.254.0.0/16 dev enxa0cec802a800 scope link metric 1000 NetworkManager.conf: [main] plugins=ifupdown,keyfile [ifupdown] managed=false NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH lxdbr0 bridge
[Touch-packages] [Bug 1439710] Re: Indicator failed to show cellular icon
** Changed in: indicator-network (Ubuntu) Assignee: Jonathan Cave (jocave) => (unassigned) -- 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/1439710 Title: Indicator failed to show cellular icon Status in Canonical System Image: Fix Released Status in indicator-network package in Ubuntu: Incomplete Bug description: Version: ubuntu-touch/vivid-proposed arale r148 Inserted a SIM and rebooted after flash of the above. After boot network indicator showed a wifi connection, but no cellular connection. On the menu the cellular showed "Offline". Examing ofono list-modems showed ril_0 as online. Issued a "restart network-indicator" and the state then showed the cellular connection correctly. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1439710/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1459198] [NEW] unity8 crash - krillin, bluetooth settings screen, sms notification
Public bug reported: current build number: 15 device name: krillin channel: ubuntu-touch/rc-proposed/bq-aquaris.en last update: 2015-05-27 10:13:41 version version: 15 version ubuntu: 20150526 version device: 20150511-3912934 version custom: 20150507-685-29-11-vivid Phone had been sat on Bluetooth settings screen for a while, think crash occurred around the same time as SMSs received. Display locked and eventual unity8 restart - crash file created. ** Affects: unity8 (Ubuntu) Importance: Undecided Status: New ** Attachment added: _usr_bin_unity8.32011.crash https://bugs.launchpad.net/bugs/1459198/+attachment/4405363/+files/_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/1459198 Title: unity8 crash - krillin, bluetooth settings screen, sms notification Status in unity8 package in Ubuntu: New Bug description: current build number: 15 device name: krillin channel: ubuntu-touch/rc-proposed/bq-aquaris.en last update: 2015-05-27 10:13:41 version version: 15 version ubuntu: 20150526 version device: 20150511-3912934 version custom: 20150507-685-29-11-vivid Phone had been sat on Bluetooth settings screen for a while, think crash occurred around the same time as SMSs received. Display locked and eventual unity8 restart - crash file created. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1459198/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1459198] Re: unity8 crash - krillin, bluetooth settings screen, sms notification
** Attachment added: unity8.log https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1459198/+attachment/4405364/+files/unity8.log -- 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/1459198 Title: unity8 crash - krillin, bluetooth settings screen, sms notification Status in unity8 package in Ubuntu: New Bug description: current build number: 15 device name: krillin channel: ubuntu-touch/rc-proposed/bq-aquaris.en last update: 2015-05-27 10:13:41 version version: 15 version ubuntu: 20150526 version device: 20150511-3912934 version custom: 20150507-685-29-11-vivid Phone had been sat on Bluetooth settings screen for a while, think crash occurred around the same time as SMSs received. Display locked and eventual unity8 restart - crash file created. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1459198/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1450427] [NEW] Message history not showing contact names just numbers
Public bug reported: Version: ubuntu-touch/devel-proposed/krillin.en r97 vegetahd Steps to reproduce: * freshly flashed device * set up some contacts on the phone (mine were sync'ed from google) * open messaging * new message * type in name in address - pulled from address book * send a SMS * go to Messages page Expected result: - previous message listed under contact name Actual result: - listed using mobile number ** Affects: messaging-app (Ubuntu) Importance: Undecided Status: New ** Also affects: messaging-app Importance: Undecided Status: New ** No longer affects: messaging-app -- 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/1450427 Title: Message history not showing contact names just numbers Status in messaging-app package in Ubuntu: New Bug description: Version: ubuntu-touch/devel-proposed/krillin.en r97 vegetahd Steps to reproduce: * freshly flashed device * set up some contacts on the phone (mine were sync'ed from google) * open messaging * new message * type in name in address - pulled from address book * send a SMS * go to Messages page Expected result: - previous message listed under contact name Actual result: - listed using mobile number To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/messaging-app/+bug/1450427/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1450427] Re: Message history not showing contact names just numbers
** 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 messaging-app in Ubuntu. https://bugs.launchpad.net/bugs/1450427 Title: Message history not showing contact names just numbers Status in the base for Ubuntu mobile products: New Status in messaging-app package in Ubuntu: New Bug description: Version: ubuntu-touch/devel-proposed/krillin.en r97 vegetahd Steps to reproduce: * freshly flashed device * set up some contacts on the phone (mine were sync'ed from google) * open messaging * new message * type in name in address - pulled from address book * send a SMS * go to Messages page Expected result: - previous message listed under contact name Actual result: - listed using mobile number To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1450427/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1449925] Re: SIM PIN unlock dialog mis-titled opening from indicator
Version: ubuntu-touch/devel-proposed/krillin.en r67 vegetahd Less easy to trigger on vivid as you do not have unlock the SIM again after flight mode if the SIM is still in location. Can still repro by moving a locked SIM from one slot to another whilst in flight mode though. -- 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/1449925 Title: SIM PIN unlock dialog mis-titled opening from indicator Status in the base for Ubuntu mobile products: New Status in indicator-network package in Ubuntu: New Bug description: Version: ubuntu-touch/stable/bq-aquaris.en r21 krillin Steps to reproduce: * 2 SIMs in the device both PIN locked * both SIMs connected to network * indicator-network - enable Flight Mode * wait till disconnected * indicator-network - disable Flight Mode * wait for indicator updated Actual results: - hit SIM 1 unlock button, dialog titled Enter SIM 2 PIN note that dialog does acutally refer to SIM1 and will unlock it, hitting the Cancel X and then second attempt to unlock results in correct title - hit SIM 2 unlock button, dialog titled Enter SIM 1 PIN same behaviour as SIM1 Expected result: - always show the correct title on the unlock dialog To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1449925/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1450427] Re: Message history not showing contact names just numbers
After a reboot the titles were correctly using names rather than numbers. -- 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/1450427 Title: Message history not showing contact names just numbers Status in the base for Ubuntu mobile products: New Status in messaging-app package in Ubuntu: New Bug description: Version: ubuntu-touch/devel-proposed/krillin.en r97 vegetahd Steps to reproduce: * freshly flashed device * set up some contacts on the phone (mine were sync'ed from google) * open messaging * new message * type in name in address - pulled from address book * send a SMS * go to Messages page Expected result: - previous message listed under contact name Actual result: - listed using mobile number To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1450427/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1450427] Re: Message history not showing contact names just numbers
** Description changed: - Version: ubuntu-touch/devel-proposed/krillin.en r97 vegetahd + Version: ubuntu-touch/devel-proposed/krillin.en r67 vegetahd Steps to reproduce: - * freshly flashed device - * set up some contacts on the phone (mine were sync'ed from google) - * open messaging - * new message - * type in name in address - pulled from address book - * send a SMS - * go to Messages page + * freshly flashed device + * set up some contacts on the phone (mine were sync'ed from google) + * open messaging + * new message + * type in name in address - pulled from address book + * send a SMS + * go to Messages page Expected result: - - previous message listed under contact name + - previous message listed under contact name Actual result: - - listed using mobile number + - listed using mobile number -- 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/1450427 Title: Message history not showing contact names just numbers Status in the base for Ubuntu mobile products: New Status in messaging-app package in Ubuntu: New Bug description: Version: ubuntu-touch/devel-proposed/krillin.en r67 vegetahd Steps to reproduce: * freshly flashed device * set up some contacts on the phone (mine were sync'ed from google) * open messaging * new message * type in name in address - pulled from address book * send a SMS * go to Messages page Expected result: - previous message listed under contact name Actual result: - listed using mobile number To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1450427/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1449925] [NEW] SIM PIN unlock dialog mis-titled opening from indicator
Public bug reported: Version: ubuntu-touch/stable/bq-aquaris.en r21 krillin Steps to reproduce: * 2 SIMs in the device both PIN locked * both SIMs connected to network * indicator-network - enable Flight Mode * wait till disconnected * indicator-network - disable Flight Mode * wait for indicator updated Actual results: - hit SIM 1 unlock button, dialog titled Enter SIM 2 PIN note that dialog does acutally refer to SIM1 and will unlock it, hitting the Cancel X and then second attempt to unlock results in correct title - hit SIM 2 unlock button, dialog titled Enter SIM 1 PIN same behaviour as SIM1 Expected result: - always show the correct title on the unlock dialog ** Affects: canonical-devices-system-image Importance: Undecided Status: New ** Affects: indicator-network (Ubuntu) Importance: Undecided Status: New ** Also affects: indicator-network (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-network in Ubuntu. https://bugs.launchpad.net/bugs/1449925 Title: SIM PIN unlock dialog mis-titled opening from indicator Status in the base for Ubuntu mobile products: New Status in indicator-network package in Ubuntu: New Bug description: Version: ubuntu-touch/stable/bq-aquaris.en r21 krillin Steps to reproduce: * 2 SIMs in the device both PIN locked * both SIMs connected to network * indicator-network - enable Flight Mode * wait till disconnected * indicator-network - disable Flight Mode * wait for indicator updated Actual results: - hit SIM 1 unlock button, dialog titled Enter SIM 2 PIN note that dialog does acutally refer to SIM1 and will unlock it, hitting the Cancel X and then second attempt to unlock results in correct title - hit SIM 2 unlock button, dialog titled Enter SIM 1 PIN same behaviour as SIM1 Expected result: - always show the correct title on the unlock dialog To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1449925/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1449503] [NEW] unity8-dash header items too small on krillin vivid
Public bug reported: Version: ubuntu-touch/devel-proposed/krillin.en r66 krillin Items on the header bar (Title text, search icon, configuration icon, favourites icon) are too small on krillin vivid release. Noticeably smaller than on RTM Comparison screenshot attached. ** Affects: unity8 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1449503 Title: unity8-dash header items too small on krillin vivid Status in unity8 package in Ubuntu: New Bug description: Version: ubuntu-touch/devel-proposed/krillin.en r66 krillin Items on the header bar (Title text, search icon, configuration icon, favourites icon) are too small on krillin vivid release. Noticeably smaller than on RTM Comparison screenshot attached. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1449503/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1449503] Re: unity8-dash header items too small on krillin vivid
** Attachment added: dash-comparison.png https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1449503/+attachment/4386533/+files/dash-comparison.png -- 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/1449503 Title: unity8-dash header items too small on krillin vivid Status in unity8 package in Ubuntu: New Bug description: Version: ubuntu-touch/devel-proposed/krillin.en r66 krillin Items on the header bar (Title text, search icon, configuration icon, favourites icon) are too small on krillin vivid release. Noticeably smaller than on RTM Comparison screenshot attached. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1449503/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1448100] Re: Indicator appearing to lose status of Wi-Fi connection
** Attachment added: syslog https://bugs.launchpad.net/ubuntu-rtm/+source/indicator-network/+bug/1448100/+attachment/4382927/+files/syslog ** Also affects: indicator-network (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-network in Ubuntu. https://bugs.launchpad.net/bugs/1448100 Title: Indicator appearing to lose status of Wi-Fi connection Status in indicator-network package in Ubuntu: New Status in indicator-network package in Ubuntu RTM: New Bug description: Version: ubuntu-touch/stable/bq-aquaris.en r21 vegeta Don't have a scenario to reproduce this at the moment - but observed on few occasions. Symptoms: * Have been connected to Wi-Fi network for a while (Canonical-2.4GHz-g) * Connection appears to drop * Indicator icon shows me no information about data connectivity (see screenshot) * Indicator menu shows presence on a unsecured network of same name - this doesn't exist * ifconfig indicates wifi still connected * can browse internet To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1448100/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1445080] Re: Cellular data not activated after exiting flight mode
Version: ubuntu-touch/devel-proposed/krillin.en r59 krillin Slightly different scenario with similar symptoms: * Tesco Mobile SIM in slot 1 (O2 MVNO) * On booting the phone registers on network and cellular data is enabled * Can browse internet etc * After some time it appears the network drops (bars empty) * It reconnects quickly but the data connection does not come back up -- 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/1445080 Title: Cellular data not activated after exiting flight mode Status in the base for Ubuntu mobile products: New Status in network-manager package in Ubuntu: Confirmed Bug description: Cellular data is not activated in ~50% of the cases in arale after setting then unsetting flight mode. I obtained the attached log this way: 1. Disabled wifi (to have less noise) and removed syslog (to make smaller the attached one) 2. Reboot 3. See cellular data is on: route is right, I have network access 4. Set flight mode 5. Unset flight mode 6. Data is not restored even after waiting for a few minutes. ccmni0 interface is down. list-modems shows that the modem is data-attached list-contexts output shows that no IP context has been activated Doing usr/share/ofono/scripts/activate-context 1 sudo ip route add default dev ccmni0 ping 8.8.8.8 works and I receive the ping responses. $ system-image-cli -i current build number: 12 device name: arale channel: ubuntu-touch/tangxi-vivid-proposed last update: 2015-04-16 08:06:39 version version: 12 version ubuntu: 20150416.0 version device: a17b9320788e7215ddf123544a3a2b5a4fa61f0d5add83f393866e8c7a9155b0 version custom: 20150416.0 + NetworkManager 0.9.10.0-4ubuntu15~mtrudel1 (silo 29 atm) To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1445080/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1445080] Re: Cellular data not activated after exiting flight mode
list-contexts when data is working ** Attachment added: list-contexts-post-boot.txt https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1445080/+attachment/4381215/+files/list-contexts-post-boot.txt -- 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/1445080 Title: Cellular data not activated after exiting flight mode Status in the base for Ubuntu mobile products: New Status in network-manager package in Ubuntu: Confirmed Bug description: Cellular data is not activated in ~50% of the cases in arale after setting then unsetting flight mode. I obtained the attached log this way: 1. Disabled wifi (to have less noise) and removed syslog (to make smaller the attached one) 2. Reboot 3. See cellular data is on: route is right, I have network access 4. Set flight mode 5. Unset flight mode 6. Data is not restored even after waiting for a few minutes. ccmni0 interface is down. list-modems shows that the modem is data-attached list-contexts output shows that no IP context has been activated Doing usr/share/ofono/scripts/activate-context 1 sudo ip route add default dev ccmni0 ping 8.8.8.8 works and I receive the ping responses. $ system-image-cli -i current build number: 12 device name: arale channel: ubuntu-touch/tangxi-vivid-proposed last update: 2015-04-16 08:06:39 version version: 12 version ubuntu: 20150416.0 version device: a17b9320788e7215ddf123544a3a2b5a4fa61f0d5add83f393866e8c7a9155b0 version custom: 20150416.0 + NetworkManager 0.9.10.0-4ubuntu15~mtrudel1 (silo 29 atm) To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1445080/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1445080] Re: Cellular data not activated after exiting flight mode
** Attachment added: syslog https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1445080/+attachment/4381230/+files/syslog -- 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/1445080 Title: Cellular data not activated after exiting flight mode Status in the base for Ubuntu mobile products: New Status in network-manager package in Ubuntu: Confirmed Bug description: Cellular data is not activated in ~50% of the cases in arale after setting then unsetting flight mode. I obtained the attached log this way: 1. Disabled wifi (to have less noise) and removed syslog (to make smaller the attached one) 2. Reboot 3. See cellular data is on: route is right, I have network access 4. Set flight mode 5. Unset flight mode 6. Data is not restored even after waiting for a few minutes. ccmni0 interface is down. list-modems shows that the modem is data-attached list-contexts output shows that no IP context has been activated Doing usr/share/ofono/scripts/activate-context 1 sudo ip route add default dev ccmni0 ping 8.8.8.8 works and I receive the ping responses. $ system-image-cli -i current build number: 12 device name: arale channel: ubuntu-touch/tangxi-vivid-proposed last update: 2015-04-16 08:06:39 version version: 12 version ubuntu: 20150416.0 version device: a17b9320788e7215ddf123544a3a2b5a4fa61f0d5add83f393866e8c7a9155b0 version custom: 20150416.0 + NetworkManager 0.9.10.0-4ubuntu15~mtrudel1 (silo 29 atm) To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1445080/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1446595] Re: Rapid brightness adjustment causes unity8 crash
Should be it... ** Attachment added: _usr_bin_unity8.32011.crash https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1446595/+attachment/4380597/+files/_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/1446595 Title: Rapid brightness adjustment causes unity8 crash Status in mir package in Ubuntu: New Status in unity8 package in Ubuntu: Incomplete Bug description: Version: ubuntu-touch/devel-proposed/krillin.en r59 krillin Steps to reproduce: * System Settings Battery Brightness * Rapidly adjust the brightness level Expected result: - brightness adjusted correctly Acutal result: - brightness gets stuck at max brightness and a unity crash follows To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mir/+bug/1446595/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1446595] [NEW] Rapid brightness adjustment causes unity8 crash
Public bug reported: Version: ubuntu-touch/devel-proposed/krillin.en r59 krillin Steps to reproduce: * System Settings Battery Brightness * Rapidly adjust the brightness level Expected result: - brightness adjusted correctly Acutal result: - brightness gets stuck at max brightness and a unity crash follows ** Affects: unity8 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1446595 Title: Rapid brightness adjustment causes unity8 crash Status in unity8 package in Ubuntu: New Bug description: Version: ubuntu-touch/devel-proposed/krillin.en r59 krillin Steps to reproduce: * System Settings Battery Brightness * Rapidly adjust the brightness level Expected result: - brightness adjusted correctly Acutal result: - brightness gets stuck at max brightness and a unity crash follows To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1446595/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1446627] [NEW] The settings available in the indicator should match those in system-settings
Public bug reported: OS Version: ubuntu-touch/devel-proposed/krillin.en r59 krillin There are 3 states that the location services can be in within System Settings Security Privacy Location access: * Using GPS only * Using GPS anonymised Wi-Fi and mobile network info * Not at all It would not be obvious to a user how these states match the four possible combined states of the two toggle switches on the indicator. The indicator should be modified to match the above 3 states. ** Affects: indicator-location (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-location in Ubuntu. https://bugs.launchpad.net/bugs/1446627 Title: The settings available in the indicator should match those in system- settings Status in indicator-location package in Ubuntu: New Bug description: OS Version: ubuntu-touch/devel-proposed/krillin.en r59 krillin There are 3 states that the location services can be in within System Settings Security Privacy Location access: * Using GPS only * Using GPS anonymised Wi-Fi and mobile network info * Not at all It would not be obvious to a user how these states match the four possible combined states of the two toggle switches on the indicator. The indicator should be modified to match the above 3 states. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-location/+bug/1446627/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1445580] Re: Impossible to end a call after switching to airplane mode
/usr/share/ofono/scripts/list-calls shows nothing active. -- 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/1445580 Title: Impossible to end a call after switching to airplane mode Status in the base for Ubuntu mobile products: Confirmed Status in dialer-app package in Ubuntu: New Bug description: As I described here https://lists.launchpad.net/ubuntu-phone/msg12177.html I accidentally switched the phone to the airplane mode while having an active incoming call. As a result it is impossible to end a call - the red button does not end the call. The bug is easy to reproduce: 1. Make a call to your Ubuntu phone and answer it. 2. Switch on 'airplane mode' 3. As a result you get unusable phone. Of course switching gsm off while having an active call is not a typical use of the phone, but still the phone should react to this situation differently. Another thing is that I somehow switched gsm off while holding my phone to my ear (which may suggest some issue with the top panel) - but I don't know how to reproduce this, hence currently I treat this as an very unfortunate accident. Workaround for ending the call: make another incoming call to your phone. BQ (r21) To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1445580/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1439710] [NEW] Indicator failed to show cellular icon
Public bug reported: Version: ubuntu-touch/vivid-proposed arale r148 Inserted a SIM and rebooted after flash of the above. After boot network indicator showed a wifi connection, but no cellular connection. On the menu the cellular showed Offline. Examing ofono list-modems showed ril_0 as online. Issued a restart network-indicator and the state then showed the cellular connection correctly. ** Affects: canonical-devices-system-image Importance: Undecided Status: New ** Affects: indicator-network (Ubuntu) Importance: Undecided Status: New ** Attachment added: indicator-network.log https://bugs.launchpad.net/bugs/1439710/+attachment/4364278/+files/indicator-network.log ** Also affects: indicator-network (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-network in Ubuntu. https://bugs.launchpad.net/bugs/1439710 Title: Indicator failed to show cellular icon Status in the base for Ubuntu mobile products: New Status in indicator-network package in Ubuntu: New Bug description: Version: ubuntu-touch/vivid-proposed arale r148 Inserted a SIM and rebooted after flash of the above. After boot network indicator showed a wifi connection, but no cellular connection. On the menu the cellular showed Offline. Examing ofono list-modems showed ril_0 as online. Issued a restart network-indicator and the state then showed the cellular connection correctly. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1439710/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1435776] Re: NM does not activate a valid ofono context
Syslog using the same setup as per my previous comment ** Attachment added: syslog https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1435776/+attachment/4361149/+files/syslog -- 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/1435776 Title: NM does not activate a valid ofono context Status in network-manager package in Ubuntu: New Bug description: Device: Krillin Software: Vivid r157 NM does not activate a valid ofono context which is present in the gprs file (context_1 in this case) I was able to activate the context manually using ./activate-context /ril_0 1 You can find syslog, list-modems and list-contexts attached To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1435776/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1435776] Re: NM does not activate a valid ofono context
** Attachment added: list-contexts.txt https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1435776/+attachment/4358012/+files/list-contexts.txt -- 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/1435776 Title: NM does not activate a valid ofono context Status in network-manager package in Ubuntu: New Bug description: Device: Krillin Software: Vivid r157 NM does not activate a valid ofono context which is present in the gprs file (context_1 in this case) I was able to activate the context manually using ./activate-context /ril_0 1 You can find syslog, list-modems and list-contexts attached To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1435776/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1435776] Re: NM does not activate a valid ofono context
ubuntu-touch/devel-proposed/krillin.en r29 krillin Also happening to me on the above with a giffgaff SIM -- 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/1435776 Title: NM does not activate a valid ofono context Status in network-manager package in Ubuntu: New Bug description: Device: Krillin Software: Vivid r157 NM does not activate a valid ofono context which is present in the gprs file (context_1 in this case) I was able to activate the context manually using ./activate-context /ril_0 1 You can find syslog, list-modems and list-contexts attached To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1435776/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1426467] Re: Indicator can fail to display panel icon
ubuntu-touch/vivid-proposed arale r148 Inserted a SIM and rebooted after flash of the above. After boot network indicator showed a wifi connection, but no cellular connection. On the menu the cellular showed Offline. Examing ofono list-modems showed ril_0 as online. Issued a restart network-indicator and the state then showed the cellular connection correctly. ** Attachment added: indicator-network.log https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1426467/+attachment/4355397/+files/indicator-network.log -- 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/1426467 Title: Indicator can fail to display panel icon Status in the base for Ubuntu mobile products: Confirmed Status in indicator-network package in Ubuntu: Confirmed Bug description: current build number: 122 device name: krillin channel: ubuntu-touch/devel-proposed It's possible for the device to boot in such a manner that the network-indicator doesn't display an icon on the top panel ( see attached screenshot ). This bug was discovered while testing an ofono vivid silo. The associated ofono merge request is: https://code.launchpad.net/~phablet- team/ofono/ww10-update/+merge/250665 The version of ofono in the silo (ubuntu-013) is: 1.12.bzr6888+15.04.20150224-0ubuntu1 This version of ofono fixes a couple of bugs, the most important being a regression on krillin where the 2nd SIM isn't always recognized on boot. My testing was performed using two SIMs, with the 2nd SIM being PIN- locked. In the case of the missing icon, no PIN unlock screen was displayed after booting. I checked using 'ps' and an indicator-network process is running, however when I checked /home/phablet/.cache/upstart, there only indicator-network log files I see are the saved .gz files. There's no unzipped/current indicator-network.log. The .gz log file with the most recent timestamp shows a single log message: phablet@ubuntu-phablet:~/.cache/upstart$ less indicator-network.log.1.gz void core::dbus::PropertyT::handle_changed(const core::dbus::types::Variant) [with PropertyType = org::freedesktop::URfkill::Interface::Killswitch::Property::State]: org.freedesktop.DBus.Error.UnknownMethod: Method Get with signature ss on interface org.freedesktop.DBus.Properties doesn't exist I checked and urfkilld is running on the system. I also verified that there were no crash files present on the system. I also checked and there was nothing relevant in syslog. This bug is hard to reproduce as well. I've hit it 4 or 5 times out of a total of maybe 45-50 reboots. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1426467/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1415029] Re: Not yet available but configured providers should be added as soon as they become available
Version: ubuntu-touch/stable/bq-aquaris.en r18 krillin Just tried to switch to HERE supported location after having initially been set to GPS only. A reboot was required before the HERE app was able to find my location. -- 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/1415029 Title: Not yet available but configured providers should be added as soon as they become available Status in the base for Ubuntu mobile products: Fix Released Status in location-service package in Ubuntu: In Progress Status in ubuntu-location-provider-here package in Ubuntu: In Progress Status in ubuntu-location-provider-here package in Ubuntu RTM: Fix Released Bug description: Right now, the location service tries to instantiate configured providers at startup. In specific corner cases, some of the configured sensors might not be available and the service should be able to be notified when those providers become available. In particular, this affects the wizard running on first boot, and subsequent login to the user session. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1415029/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1380736] Re: Unlocking sim while dash is not loaded leads to a system lockup
Reproduced here (r104). I have found that eventually unity8 is restarted (the system goes back the spinner and session restarts), when back up the SIM is unlocked. -- 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/1380736 Title: Unlocking sim while dash is not loaded leads to a system lockup Status in Network Menu: Invalid Status in “unity8” package in Ubuntu: New Bug description: STEPS: 1. Install a new image (Apparently it works with just re-running the wizard) 2. While the dash is empty drag down the network indicator 3. Click on the first unlock sim button 4. Type in the unlock code and hit the tick 5. System locks up EXPECTED: I expect the lock you unlock the sim and change back to the indicator ACTUAL: The system hard locks nothing works. In the end you are forced to hard shutdown the phone by pressing and holding the power button till the phone powers down. Booting the Phone back up after this and everthing works as expected. Also waiting on the dash to fully load and fill with apps and then unlocking works. To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-network/+bug/1380736/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
