Bug 10415 – "My location" in chat status hangs and doesn't get updated

Bug 10415 - "My location" in chat status hangs and doesn't get updated


Summary:	"My location" in chat status hangs and doesn't get updated

Status:	RESOLVED DUPLICATE of bug 9963

Product:	Chat & Call & SMS
Component:	General
Version:	5.0:(10.2010.19-1)
Platform:	All Maemo

Importance:	Unspecified normal with 1 vote (vote)
Target Milestone:	---
Assigned To:	rtcomm@maemo.org
QA Contact:	communication-bugs

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree

Reported:	2010-05-30 02:10 UTC by fileshifter
Modified:	2010-06-04 19:49 UTC (History)
CC List:	1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note

You need to log in before you can comment on or make changes to this bug.

Description fileshifter (reporter) 2010-05-30 02:10:28 UTC

SOFTWARE VERSION:
10.2010.29-1

EXACT STEPS LEADING TO PROBLEM: 
1. Tap status area -> Availability
2. Pick My location (I always do district level)
3. travel around for a couple of days

EXPECTED OUTCOME:
The location updates whenever you move

ACTUAL OUTCOME:
At random - sometimes after just a few hours, sometimes after more then a week
- the location won't update anymore. GPS still works fine, i.e. in Maps or maep
or anywhere, really. Tracking works perfectly. But the status area location
does not get updated! This doesn't change, if I switch to street level or any
other level, or to "don't show" and back. Only thing that fixes this is a
reboot.

REPRODUCIBILITY:
10/10 if you wait long enough

OTHER COMMENTS:
If you don't fix the bug, please at least tell me how to restart the
chat/telepathy thing or whatever updates the location for the chat so that it
can start over without having to reboot. Thanks.

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.3)
Gecko/20100402 Firefox/3.5

Comment 1 Andre Klapper maemo.org

2010-05-31 11:43:01 UTC

Settings welcome (e.g. "Enable network positioning" enabled?).

Comment 2 fileshifter (reporter) 2010-05-31 12:00:13 UTC

Yes, network positioning (supl.nokia.com) is enabled, as is GPS. It also
doesn't matter if I'm on GSM or WLAN, the location displayed just doesn't
change, no matter what I try.

Btw, when I enable "Show location" once it's frozen, the GPS antenna symbol
does not blink even once. It's there, the location is wrong, and nothing else
shows any reaction (except the syslog below). This doesn't change the fact that
the GPS works fine in Maps or maep. As soon as I open maep, the GPS antenna
symbol starts blinking (because it needs a more accurate reading). Yet changing
the precision of "Show location" doesn't do anything. And even as maep gets
very accurate readings, the location doesn't change.

Here's the output in syslog when I enable the status (It still shows the 3 days
old, wrong location, when I enable it. Again, disabling/enabling doesn't do
anything, neither does changing precision):

May 31 10:50:35 Nokia-N900 location-daemon[3864]: GLIB DEBUG default - :1.56
now having 1 connections
May 31 10:50:35 Nokia-N900 location-daemon[3864]: GLIB DEBUG default - Starting
a new LAS session with method = 0x2, interval = 0x4b0, reason = 0
May 31 10:50:35 Nokia-N900 location-daemon[3864]: GLIB DEBUG default - Speeding
up first ACWP session using default interval
May 31 10:50:35 Nokia-N900 location-daemon[3864]: GLIB DEBUG default - Tracking
ongoing, status: 1, npe_id: 15
May 31 10:50:35 Nokia-N900 location-daemon[3864]: GLIB DEBUG default -
Modifying LAS session method = 0x2, interval = 0x4b0, old_meth = 0x2, old_ival
= 0x0, reason = 2
May 31 10:50:35 Nokia-N900 location-daemon[3864]: GLIB DEBUG default - Tracking
succesfully stopped, status: 5
May 31 10:50:35 Nokia-N900 location-daemon[3864]: GLIB DEBUG default - Starting
a new LAS session with method = 0x2, interval = 0x4b0, reason = 2
May 31 10:50:35 Nokia-N900 location-daemon[3864]: GLIB DEBUG default - Tracking
ongoing, status: 1, npe_id: 16


And this when I again disable tracking:

May 31 10:55:00 Nokia-N900 location-daemon[3864]: GLIB DEBUG default - :1.56
now having 0 connections
May 31 10:55:00 Nokia-N900 location-daemon[3864]: GLIB DEBUG default - Stopping
LAS session, reason: 1
May 31 10:55:00 Nokia-N900 location-daemon[3864]: GLIB DEBUG default - Tracking
succesfully stopped, status: 5

Not really revealing anything...

Comment 3 fileshifter (reporter) 2010-05-31 12:04:27 UTC

When I launch maep, this is the output in syslog:

May 31 10:59:16 Nokia-N900 fmtxd[3997]: GLIB WARNING ** default - No marshaller
for signature of signal 'Condition'
May 31 10:59:18 Nokia-N900 maep[3998]: GLIB DEBUG liblocation - Loading initial
values from com.nokia.Location::las
May 31 10:59:18 Nokia-N900 location-daemon[3994]: GLIB DEBUG default - :1.557
now having 1 connections
May 31 10:59:18 Nokia-N900 maep[3998]: GLIB DEBUG liblocation - Object path:
/com/nokia/location/las
May 31 10:59:18 Nokia-N900 location-daemon[3994]: GLIB DEBUG default - :1.557
now having 0 connections
May 31 10:59:19 Nokia-N900 location-daemon[3994]: GLIB DEBUG default - :1.555
now having 1 connections
May 31 10:59:19 Nokia-N900 location-daemon[3994]: GLIB DEBUG default -
Modifying LAS session method = 0xa, interval = 0x0, old_meth = 0x2, old_ival =
0x4b0, reason = 0
May 31 10:59:19 Nokia-N900 location-daemon[3994]: GLIB DEBUG default - Tracking
ongoing, status: 1, npe_id: 18
May 31 10:59:19 Nokia-N900 maep[3998]: GLIB WARNING ** default - Menu: item
Graph does not exist
May 31 10:59:19 Nokia-N900 maep[3998]: GLIB WARNING ** default - Menu: item
Graph does not exist
May 31 10:59:20 Nokia-N900 location-daemon[3994]: GLIB DEBUG default - GPS
STATE: search
May 31 10:59:32 Nokia-N900 location-daemon[3994]: GLIB DEBUG default - GPS
STATE: fix
May 31 11:00:35 Nokia-N900 fmtxd[4001]: GLIB WARNING ** default - No marshaller
for signature of signal 'Condition'

Comment 4 Andre Klapper maemo.org

2010-06-04 14:04:46 UTC

I think that this is a duplicate of bug 9963... do you agree?

Comment 5 fileshifter (reporter) 2010-06-04 19:49:13 UTC

Yep, seems like it. I can't say it has something to do with losing the
connection (and GPS should somewhat work without any connection as well, or at
least try to get a lock), but surely when traveling a loss of connection can
occur. Probably the same bug, yes.

*** This bug has been marked as a duplicate of bug 9963 ***