This is interesting. I've been having to override the auth type after
the wizard for years, since it always gives me passphrase even if I
select pin and enter a 4-digit code. Didn't realize there was a new
issue with the same symptoms.
--
You received this bug notification because you are a mem
This behavior isn't always a bad thing. It might be good to make it a
configurable option, since people sometimes want to see in-progress
events and sometimes don't. The widget I use on other devices has an
option to remove events on end rather than on start, show or hide all-
day events, highlig
Thanks for adding this. It's not a huge deal, but it would be nice if
it updated a little more often during the last hour or so before an
event starts.
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to indicator-datetime in Ubuntu.
Matching sub
The headset I'm using is what they directed me to at Walmart when I
asked for an inexpensive bluetooth headset, the Emerson EM229. It has
to be a pretty popular device in the states in order to be carried at
Walmart, especially at under $20.
--
You received this bug notification because you are
Sometimes I have to turn the headset off and on twice, but I've never
seen it take more than two tries.
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to indicator-bluetooth in Ubuntu.
https://bugs.launchpad.net/bugs/1387949
Title:
power cycl
This is a headset.
BTW, this issue is easily reproducible. All I have to do is turn the
headset on, wait for the icon to go white, wait another couple seconds,
then turn the headset off. Within a few seconds the phone will
completely lock up, and a few more seconds later it reboots.
** Changed
Public bug reported:
While sanity testing krillin rtm image 139, I paired a bluetooth
headset. I made a call with it, hung up, then turned the headset off.
I noticed this caused the BT indicator icon to invert, which is a nice
way to indicate whether something is connected. So, I turned the devi
** Description changed:
+ Consider this invalid for now... unable to reproduce the issue on a
+ fresh-flashed phone, and by default it actually does ask the user to
+ pick a SIM even when replying from an indicator on a locked phone.
+
+ -
+
In krillin rtm image 112, I noticed that there
** Summary changed:
- reply to SMS fails silently if no default SIM is set
+ reply to SMS (via indicator) fails silently if no default SIM is set
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to indicator-messages in Ubuntu.
Matching subscript
Public bug reported:
In krillin rtm image 112, I noticed that there is a silent failure if
the user tries to respond to a SMS message via indicator if no default
SIM has been set for SMS.
After choosing a SIM in the messaging app, replies via indicator work
fine... but until then, replies are si
FWIW, fixed in rtm krillin image 112.
** Changed in: indicator-sound (Ubuntu)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to indicator-sound in Ubuntu.
Matching subscriptions: dx-packages
https://bu
Wow. So, when I tried again 13 minutes later, the clock was already 5
minutes behind. Apparently the speed isn't consistent.
It figured out the correct time again about 30 seconds later, but it
seems the onboard clock might be way off without help from the network
(cell or wifi).
--
You receiv
Or maybe it's not the onboard clock, but just the display widget. If I
open the actual clock app, I can see two different times -- one in the
indicator, one in the app. So apparently the welcome time widget and
indicator widget just get out of sync with the system clock.
--
You received this bu
Note, given the behavior I saw, it's also possible that it was only
behind by about 40 seconds, and the second screen update wasn't related
to NTP or data from cell towers. The first (immediate) update could
have been the usual split second before the screen redraws on resume.
In any case, that's
Confirmed on Utopic 161.
I unplugged the mako from USB, turned its screen off, and let it sit for
10 minutes next to a computer with a known-good clock. When I turned it
back on, its clock updated within one second from T-2m to T-1m -- that
is, it was just over a minute behind, after being idle f
** Tags added: qa-daily-testing rtm14
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to indicator-datetime in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1340329
Title:
Phone should turn on screen and unlock it
Still jittery and a bit laggy in Utopic 161.
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to indicator-sound in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1306499
Title:
Sound indicator is laggy
Status in S
In Utopic 140, it still lags a bit (up to a few seconds, if I drag it
rapidly back and forth), but it's mostly not too bad. It just feels
jittery, instead of being massively behind what the user told it to do.
By jittery, I mean that sliding it smoothly from one end to the other
tends to result in
As of image utopic 60, this is much much better. The lag is a second or
less instead of being up to a full minute.
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to indicator-sound in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.lau
Just confirming this works for me now, on image utopic 18.
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to indicator-datetime in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1283236
Title:
Alarms are triggered
** Tags added: r276
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to indicator-datetime in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1283236
Title:
Alarms are triggered in UTC tz despite saving in local tz
FWIW, this also apparently makes it impossible to set an alarm for today
if the current time is between midnight and the number of hours past UTC
your time zone is.
So, I'm in UTC-6. It's 2am. I can't set an alarm to go off in 15
minutes (or any time before 6am), because it automatically sets th
** Tags added: r263
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to indicator-datetime in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1283236
Title:
Alarms are triggered in UTC tz despite saving in local tz
23 matches
Mail list logo