Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

engine.cpp and queue.cpp errors while exporting #4

Open
Eskotus opened this issue Aug 28, 2012 · 3 comments
Open

engine.cpp and queue.cpp errors while exporting #4

Eskotus opened this issue Aug 28, 2012 · 3 comments

Comments

@Eskotus
Copy link

Eskotus commented Aug 28, 2012

When trying to export my SMS I get first lot's of errors like this

libqtcontacts-tracker: engine.cpp:1591: Not cleaning up obsolete resources for nao:hasTag property since the property's range is too generic(rdfs:Resource).

While these errors came the file was growing and filling up with proper SMS data but after a while I start to get following errors:

libqtcontacts-tracker: queue.cpp:104: The taskqueue's background thread stalled

When this error came the output file wasn't growing anymore so I'm guessing the application stopped exporting messages.

@wwwjfy
Copy link
Owner

wwwjfy commented Aug 28, 2012

This seems a service error caused by libqtcontacts-tracker.
I'm sorry I cannot do anything about it. What I suggest is closing all application, or even rebooting the device to avoid anything to interrupt this. I'm not an expert on Meego, so I cannot know the details.

A reply from the forum suggests that rerun may solve the problem magically.

@camwebb
Copy link

camwebb commented Dec 11, 2012

Great tool. Thx @wwwjfy.

I also had this issue, but found the hang happened at random times, some sooner, some later, so running the app several times increased the chance of getting a full SMS backup. The app seems to be reading the SMSs in the order that the associated people were added to the db, hence in a partial backup you'll get SMSs to/from your old friends, but not your new ones!

@keithzg
Copy link

keithzg commented Jun 9, 2016

I may be the last person on earth that was still using an N9 ;) so I've gone about trying to use this today (my N9 is actually still working fine, but I can't really justify carrying it around anymore), and I've run into this error. Going to try and avoid rebooting it, if only because it's at over 200 days of uptime and after I fully retire it I plan on mostly just trying to see how much uptime I can get in the end, heh.

So far it's gotten far further once I closed all my (long, long open) message windows.

Many thanks though, @wwwjfy, for this tool :) I rather miss the N900/N9 dev community, even though I barely took direct part myself.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants