[Desktop-packages] [Bug 1630336] Re: NM doesn't scan for wifi networks after suspend
** Summary changed: - NM doesn't scan for wifi networks after hibernation + NM doesn't scan for wifi networks after suspend -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-applet in Ubuntu. https://bugs.launchpad.net/bugs/1630336 Title: NM doesn't scan for wifi networks after suspend Status in network-manager-applet package in Ubuntu: Confirmed Bug description: Sometimes, after waking up the laptop from hibernation, nm-applet won't scan for networks. In these cases, the list of available Wifis can be just outdated or directly empty. Switching Wireless on/off and Network on/off doesn't trigger a scan. Usually running sudo iwlist scan on a terminal makes the wifi networks available immediately in nm-applet I'm using 16.04 (ubt had the same problem on 15.10) network-manager-gnome: Installed: 1.2.0-0ubuntu0.16.04.4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1630336/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1630336] Re: NM doesn't scan for wifi networks after hibernation
OOps, yes. I meant suspend, indeed. I will try with that method to see if that works for me, but as per #2 i can have a hard time trying to fix it -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-applet in Ubuntu. https://bugs.launchpad.net/bugs/1630336 Title: NM doesn't scan for wifi networks after hibernation Status in network-manager-applet package in Ubuntu: Confirmed Bug description: Sometimes, after waking up the laptop from hibernation, nm-applet won't scan for networks. In these cases, the list of available Wifis can be just outdated or directly empty. Switching Wireless on/off and Network on/off doesn't trigger a scan. Usually running sudo iwlist scan on a terminal makes the wifi networks available immediately in nm-applet I'm using 16.04 (ubt had the same problem on 15.10) network-manager-gnome: Installed: 1.2.0-0ubuntu0.16.04.4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1630336/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1630336] Re: NM doesn't scan for wifi networks after hibernation
Today I saw it again and scanning on the terminal didn't work. Tried with "nmcli d wifi list" which showed the networks available on the terminal, but not on the applet. In the end, I added the new network by hand, which worked and got me connected, but it was annoying. I then turned on a hotspot my computer knew, and it got connected right away - could it be that it's not *displaying* the networks, but it does scan them? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-applet in Ubuntu. https://bugs.launchpad.net/bugs/1630336 Title: NM doesn't scan for wifi networks after hibernation Status in network-manager-applet package in Ubuntu: Confirmed Bug description: Sometimes, after waking up the laptop from hibernation, nm-applet won't scan for networks. In these cases, the list of available Wifis can be just outdated or directly empty. Switching Wireless on/off and Network on/off doesn't trigger a scan. Usually running sudo iwlist scan on a terminal makes the wifi networks available immediately in nm-applet I'm using 16.04 (ubt had the same problem on 15.10) network-manager-gnome: Installed: 1.2.0-0ubuntu0.16.04.4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1630336/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1630336] [NEW] NM doesn't scan for wifi networks after hibernation
Public bug reported: Sometimes, after waking up the laptop from hibernation, nm-applet won't scan for networks. In these cases, the list of available Wifis can be just outdated or directly empty. Switching Wireless on/off and Network on/off doesn't trigger a scan. Usually running sudo iwlist scan on a terminal makes the wifi networks available immediately in nm-applet I'm using 16.04 (ubt had the same problem on 15.10) network-manager-gnome: Installed: 1.2.0-0ubuntu0.16.04.4 ** Affects: network-manager-applet (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-applet in Ubuntu. https://bugs.launchpad.net/bugs/1630336 Title: NM doesn't scan for wifi networks after hibernation Status in network-manager-applet package in Ubuntu: New Bug description: Sometimes, after waking up the laptop from hibernation, nm-applet won't scan for networks. In these cases, the list of available Wifis can be just outdated or directly empty. Switching Wireless on/off and Network on/off doesn't trigger a scan. Usually running sudo iwlist scan on a terminal makes the wifi networks available immediately in nm-applet I'm using 16.04 (ubt had the same problem on 15.10) network-manager-gnome: Installed: 1.2.0-0ubuntu0.16.04.4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1630336/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1616943] Re: Can't auth against U1 in g-s
Thanks for the update, Robert -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1616943 Title: Can't auth against U1 in g-s Status in gnome-software package in Ubuntu: In Progress Status in gnome-software source package in Xenial: Triaged Status in gnome-software source package in Yakkety: In Progress Bug description: [Impact] Authentication using Ubuntu One credentials to install/remove snaps always fails. This is due to a behaviour change in snapd (no longer accepts login requests from non-root users). Existing credentials continue to work. [Test Case] 1. Delete any existing credentials by deleting passwords marked "com.ubuntu.UbuntuOne.GnomeSoftware" using Seahorse. 2. Start GNOME Software 3. Search for a snap (e.g. "moon-buggy") 4. Install Snap 5. Enter Ubuntu One credentials when prompted Expected result: Observed result: Dialog says "Incorrect email or password". Expected result: Authentication completes and the snap is installed. [Regression Potential] The solution is to use a new D-Bus service (snapd-login-service) and new library (snapd-glib) to get the Macaroon from snapd. This has some risk of introducing new bugs. The change is minimised (other snapd code paths unchanged) and the alternative is login to be impossible. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1616943/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1478319] Re: Wifi doesn't reconnect to AP if it uses the same SSID than another AP
@jean-baptiste do you still see this? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1478319 Title: Wifi doesn't reconnect to AP if it uses the same SSID than another AP Status in Canonical System Image: Incomplete Status in network-manager package in Ubuntu: Expired Bug description: current build number: 68 device name: arale channel: ubuntu-touch/rc-proposed/meizu.en last update: 2015-07-24 08:00:20 version version: 68 version ubuntu: 20150724 version device: 20150709-8965e37 version custom: 20150716-819-8-42 My ISP (Free in France) provides a hotspot service so that customers can use the connection of any other customer using a generic open Wifi connection (for reference http://www.free.fr/assistance/2303.html - in French) The SSID is called 'FreeWifi' on all the boxes but obviously APs are all different since it's customers' DSL routers. When I connect to one of this access point, suspend the phone and resume it in another location where the SSID is available but from a different AP, the phone doesn't connect to this AP and the list of networks in the network-indicator doesn't refresh and still show the list of network from the previous location. I have to forget the network called 'FreeWifi' and reconnect in order to refresh the list and make it work. It's 100% reproducible. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1478319/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1378814] Re: greeter does not properly update infographic after unlock
** Also affects: band-aids-uphone Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-greeter in Ubuntu. https://bugs.launchpad.net/bugs/1378814 Title: greeter does not properly update infographic after unlock Status in Band-aids for Ubuntu Phone: New Status in Canonical System Image: Confirmed Status in unity-greeter package in Ubuntu: Confirmed Bug description: This bug has been here since forever, but really needs to get cleaned up for rtm. Steps to reproduce: - send 2 text messages - lock your phone - unlock your phone - confirm infographic says "2 text messages sent today" - lock your phone for the night and go to sleep - unlock your phone the next day Expected results: - infographic should be cleared, or show relevant information for today Actual results: - infographic still says "2 text messages sent today" When the phone is unlocked the greeter should update the infographic text To manage notifications about this bug go to: https://bugs.launchpad.net/band-aids-uphone/+bug/1378814/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1364647] Re: Can't hear clock alarm when headphones are plugged in but not in your ears
** Description changed: When a bluetooth or wired headset the phone embedded speakerphone should ring anyway as you probably won't wear an headset while sleeping, while you prefer keeping your headset connected all the times. -- SOLUTION -- Alarms should *always* be played to the speaker phones, as well as in the wired/wireless headset. - (The equivalent for the ringtone is bug 1364647.) + (The equivalent for the ringtone is bug 1583981.) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1364647 Title: Can't hear clock alarm when headphones are plugged in but not in your ears Status in Band-aids for Ubuntu Phone: New Status in Canonical System Image: Confirmed Status in Ubuntu Clock App: Invalid Status in Ubuntu UX: Triaged Status in indicator-datetime package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: When a bluetooth or wired headset the phone embedded speakerphone should ring anyway as you probably won't wear an headset while sleeping, while you prefer keeping your headset connected all the times. -- SOLUTION -- Alarms should *always* be played to the speaker phones, as well as in the wired/wireless headset. (The equivalent for the ringtone is bug 1583981.) To manage notifications about this bug go to: https://bugs.launchpad.net/band-aids-uphone/+bug/1364647/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1364647] Re: Can't hear clock alarm when headphones are plugged in but not in your ears
As for ringtone, I'd rather suggest some time of only headphones, and if after some time the alarm is not dismissed, both on headphones and speakers (as it may indeed happen that you use alarms for other than waking up and it could be embarrassing/annoying to have it played on the speakers right away) ** Also affects: band-aids-uphone Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1364647 Title: Can't hear clock alarm when headphones are plugged in but not in your ears Status in Band-aids for Ubuntu Phone: New Status in Canonical System Image: Confirmed Status in Ubuntu Clock App: Invalid Status in Ubuntu UX: Triaged Status in indicator-datetime package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: When a bluetooth or wired headset the phone embedded speakerphone should ring anyway as you probably won't wear an headset while sleeping, while you prefer keeping your headset connected all the times. -- SOLUTION -- Alarms should *always* be played to the speaker phones, as well as in the wired/wireless headset. (The equivalent for the ringtone is bug 1364647.) To manage notifications about this bug go to: https://bugs.launchpad.net/band-aids-uphone/+bug/1364647/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1407928] Re: [phone] Does not auto-switch to available, known WiFi
I'm on rc-proposed with arale, and last Sunday this happened: - I'm on my cellular network - In the morning I go to a place that offers free wifi. I connect to it. - I leave this place, change city, go back home (with its own known wifi network) at night - I sleep over the night - The morning after (Monday morning) I want to check a video; before that I want to make sure I'm on wifi. I pulled down the wifi indicator and I see I'm still "connected" to the wifi of the place where I had breakfast the day before - My home's wifi is in the list (!) so I just choose it and it connects. I'm not sure if the phone was indeed connected to my ap but displaying something else, or if it wasn't connected at all. The other times I've seen something like this usually the indicator updates (either connecting or showing the right connection, who knows) pretty quickly *after* I pull down. Is it possible to get any logs that could better show what's going on for real? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1407928 Title: [phone] Does not auto-switch to available, known WiFi Status in Canonical System Image: Confirmed Status in indicator-network package in Ubuntu: Invalid Status in network-manager package in Ubuntu: Confirmed Bug description: This might not be the place for this bug, please reassign as appropriate. I was only able to reproduce this on mako/rtm, krillin/vivid seems to behave better (but I do remember the same issue there). Steps: * connect to a password-protected WiFi network * go out of range * make sure a GSM connection is established * go back in the WiFi range Expected: * phone connects to the known WiFi automatically Current: * phone does not connect to WiFi Please find attached network-test-session logs from when I toggled WiFi and Plane mode to get some data on the issue. ProblemType: Bug DistroRelease: Ubuntu RTM 14.09 Package: indicator-network 0.5.1+15.04.20141215~rtm-0ubuntu1 Uname: Linux 3.4.0-5-mako armv7l ApportVersion: 2.14.7-0ubuntu8 Architecture: armhf Date: Tue Jan 6 12:01:55 2015 InstallationDate: Installed on 2014-12-18 (18 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20141218-163635) SourcePackage: indicator-network UpgradeStatus: No upgrade log present (probably fresh install) indicator-network.log: Attempted to unregister path (path[0] = org path[1] = freedesktop) which isn't registered Attempted to unregister path (path[0] = org path[1] = freedesktop) which isn't registered upstart.indicator-network.log: Attempted to unregister path (path[0] = org path[1] = freedesktop) which isn't registered Attempted to unregister path (path[0] = org path[1] = freedesktop) which isn't registered To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1407928/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1407928] Re: [phone] Does not auto-switch to available, known WiFi
@awe, I tried this again: arriving at home without cellular data, but with wifi enabled. I gave it 10/15 minutes of time to try to reconnect on its own. Then I woke up the phone, the indicator said wifi was offline. I checked on the browser and I couldn't browse (said I was offline). I pulled down the network indicator and only then the phone started connecting on the known home wifi network. After this I could browse. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1407928 Title: [phone] Does not auto-switch to available, known WiFi Status in Canonical System Image: Confirmed Status in indicator-network package in Ubuntu: Invalid Status in network-manager package in Ubuntu: Confirmed Bug description: This might not be the place for this bug, please reassign as appropriate. I was only able to reproduce this on mako/rtm, krillin/vivid seems to behave better (but I do remember the same issue there). Steps: * connect to a password-protected WiFi network * go out of range * make sure a GSM connection is established * go back in the WiFi range Expected: * phone connects to the known WiFi automatically Current: * phone does not connect to WiFi Please find attached network-test-session logs from when I toggled WiFi and Plane mode to get some data on the issue. ProblemType: Bug DistroRelease: Ubuntu RTM 14.09 Package: indicator-network 0.5.1+15.04.20141215~rtm-0ubuntu1 Uname: Linux 3.4.0-5-mako armv7l ApportVersion: 2.14.7-0ubuntu8 Architecture: armhf Date: Tue Jan 6 12:01:55 2015 InstallationDate: Installed on 2014-12-18 (18 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20141218-163635) SourcePackage: indicator-network UpgradeStatus: No upgrade log present (probably fresh install) indicator-network.log: Attempted to unregister path (path[0] = org path[1] = freedesktop) which isn't registered Attempted to unregister path (path[0] = org path[1] = freedesktop) which isn't registered upstart.indicator-network.log: Attempted to unregister path (path[0] = org path[1] = freedesktop) which isn't registered Attempted to unregister path (path[0] = org path[1] = freedesktop) which isn't registered To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1407928/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1507769] Re: App store does not display images
I reproduce this on OTA 9.1 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1507769 Title: App store does not display images Status in Canonical System Image: Fix Committed Status in indicator-network package in Ubuntu: Invalid Status in network-manager package in Ubuntu: Invalid Status in qtbase-opensource-src package in Ubuntu: Fix Released Status in thumbnailer package in Ubuntu: Invalid Status in unity8 package in Ubuntu: Confirmed Status in qtbase-opensource-src package in Ubuntu RTM: Fix Released Bug description: On both mako and arale using latest rc-proposed No images are loaded in the app store view I noticed free showed less than 100MB available on the mako Closing a few apps and refreshing loaded the images, as did a reboot on the arale. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1507769/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1476476] Re: battery indicator only sort of reflects actual battery charge
Among strange updates backwards in the graphic, the other day I witnessed this with Arale: - Phone plugged for 7+ hours, says battery 100% - Unplugged phone, battery % starts to decrease. First value is oddly enough 98% - Plugged it again (plugged to wall, btw, not computer) - Battery starts to drain really quickly: within minutes (literally, less than two minutes) battery says 1% - Phone turns off *for real* - I turned it on again, while still plugged. Battery says 100% I've also seen it plugged for several hours, but when disconnected show strange values such as 44%, 20%, etc. Have some screenshots of the battery graphics, if useful. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to upower in Ubuntu. https://bugs.launchpad.net/bugs/1476476 Title: battery indicator only sort of reflects actual battery charge Status in Canonical System Image: New Status in upower package in Ubuntu: New Bug description: On Ubuntu Touch devices, the battery indicator and graph behave in strange ways which do not accurately represent the state of the phone's battery or power supply. This may be several bugs, but more than one of those can probably be fixed in a single straightforward way. Attached is a graph showing, at the top, what the battery indicator and graph show. Below, the blue line shows the kernel's voltage value from /sys/class/power_supply/battery/voltage_now , and the green line shows the actual voltage going in to the phone from a power supply. To help make sense of the graph, here are the events which happened during the measurement period: - I tested bug 1476468, but this part of the graph is cut off to the left. - I turned the power supply up to 4.2X V and turned the phone back on. It was not plugged in to USB. - At about 0.1 hours I turned the power supply down to 3.1V and waited. - At about 0.35 hours the phone turned itself off; I guess I set the input power too low. - At about 0.45 hours I noticed, turned the power up to 4.3V, and turned the phone back on. After it booted, I turned the power down to 3.3V and waited again. - Time passed; I was working on other things. - At ~2.7 hours, I turned up the power supply to 4.3 V. - At ~2.8 hours, I plugged in USB. - At ~3.8 hours, the battery indicator noticed, jumped to 85%, and retroactively changed the graph from a horizontal line to a diagonal rising line. One issue is that the user-visible graph lags way behind the power supply. It took about 35 to 60 minutes to notice that the power had dropped to a very low level, then plummeted all at once. Before this, it merely declined a few percent. The kernel's reading also lags a bit, but it looks like it may simply have a lowpass filter or something on it. Regardless, the kernel's raw value is much closer to reality. A second issue is that the user-visible graph and percent do not go up when the battery voltage increases. It refuses to increase the estimated charge, ever, unless USB is plugged in. However, li-ion batteries normally recover some voltage after a high-amperage drain stops. So, if you watch videos for half an hour and stop, the charge actually recovers and the battery indicator should reflect this. Letting the percent go up while it's not plugged in is not an error, it's just how the battery works. A third (and fourth) issue is that it took about an hour for the indicator to show an increased charge even after the USB cable was plugged in. ... and then despite jumping suddenly from 1% to 85% it *retroactively* changed the graph to make it look like the level had been increasing the whole time. I notice that the kernel sees voltage increases immediately, but decreases take a while to settle. Not ideal, but probably not bad either. What I propose as a solution: Instead of using the current code to estimate a charge percent, we should perhaps translate the kernel's voltage value into a percent directly. At least while unplugged. While plugged in, I'm not sure if the kernel has an accurate value anywhere. Using the kernel data directly would give a more accurate representation of the battery state, and is not prone to the bizarre behaviors reported on the mailing lists (or the corner cases I've observed in testing on a modified phone). As for translating the kernel voltage into a percent, it simply needs to go through a curve correction function. It should look approximately like one of these, depending on the exact battery type: http://www.lygte-info.dk/pic/Batteries2011/All18650/Capacity-0.2A.png To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1476476/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More
[Desktop-packages] [Bug 1378814] Re: greeter does not properly update infographic after unlock
This still happens after ota4 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-greeter in Ubuntu. https://bugs.launchpad.net/bugs/1378814 Title: greeter does not properly update infographic after unlock Status in the base for Ubuntu mobile products: Confirmed Status in unity-greeter package in Ubuntu: Confirmed Bug description: This bug has been here since forever, but really needs to get cleaned up for rtm. Steps to reproduce: - send 2 text messages - lock your phone - unlock your phone - confirm infographic says 2 text messages sent today - lock your phone for the night and go to sleep - unlock your phone the next day Expected results: - infographic should be cleared, or show relevant information for today Actual results: - infographic still says 2 text messages sent today When the phone is unlocked the greeter should update the infographic text To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1378814/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
