Openambit crashing when attempting to sync. NB: The runs/Moves had already been downloaded from the Ambit during a previous sync i.e. they were listed in the pane on the left hand side.
The output in the terminal is included below.
xxxx@xxxx:~$ sudo openambit
[sudo] password for xxxx:
"QLocalSocket::connectToServer: Connection refused"
roadkill@roadkill-1000:~$ sudo openambit
"sni-qt/7268" WARN 21:51:37.299 void StatusNotifierItemFactory::connectToSnw() Invalid interface to SNW_SERVICE
QObject: Cannot create children for a parent that is in a different thread.
(Parent is QNetworkAccessManager(0x9e05e10), parent's thread is QThread(0x9f0f3f0), current thread is QThread(0x9d51948)
QObject: Cannot create children for a parent that is in a different thread.
(Parent is QNetworkAccessManager(0x9e05e10), parent's thread is QThread(0x9f0f3f0), current thread is QThread(0xbfe89e14)
"Unexpected ''.
Line 89, column 39"
Hi Robin
Can you attach the specific log XML file (in ~/.openambit/) causing the crash. We are facing 2 problems here, 1 the application has generated a messed up XML and 2, it crashes when trying to use it...
/Emil
By the way, it seems that OpenAmbit always crashes if there are existing log files in the folder. If I delete the existing files then it seems to work.
I have reproduced the crash using the attached file (which is a few seconds long).
The console output in this instance was:
roadkill@roadkill-1000:~/.openambit$ openambit
QObject: Cannot create children for a parent that is in a different thread.
(Parent is QNetworkAccessManager(0x8e38d48), parent's thread is QThread(0x8e142f8), current thread is QThread(0x8b37948)
QObject: Cannot create children for a parent that is in a different thread.
(Parent is QNetworkAccessManager(0x8e38d48), parent's thread is QThread(0x8e142f8), current thread is QThread(0x8b37948)
Failed to upload log, movescount.com replied with " ""Move already exists (UserDeviceID: 166409, StartTime_LT: 2\/9\/2014 11:10:12 AM, move.Duration.TotalSeconds: 2.5)"" "
"Unexpected ''.
Line 89, column 39"
Segmentation fault (core dumped)
Do you have any logs which happens to have an activity name longer than 15 letters? For example "crosscountry ski"?
I think "Interval session" is longest i.e. 15 chars.
On 1 Mar 2014 10:46, "Emil Ljungdahl" svenstorp@users.sf.net wrote:
Related
Tickets:
#27By the way, is it possible to modify watch settings via OpenAmbit? For example, can I edit the name of an activity type (such as change "Interval session" to "Intervals") on the website and then upload that to the watch?
Moved to github