maemo.org - Talk - View Single Post - [Canola] Canola2-B8 Stopped working with error

	fattomm	2009-05-14 , 01:41
	Posts: 109 \| Thanked: 37 times \| Joined on Oct 2008 @ NYC, NY	#17

Originally Posted by salinmooch

Same issue here with beta 11. After the first time it happened I thought I had some bad sectors as i had some recent crashes. After fsck'ing same problem. Checking permissions in .canola did not reveal any issues. I fixed it by renaming the canola.db file
and allowing canola to create a new one (first startup hung, killing restarting canola made it happy after removing the db file). It worked again for about a week and then had the same error. Removing the db file fixes it for me but obviously you loose all our podcast settings, etc.

Love canola, hope this can be squashed soon.

Was there any fix to this? I started getting this today -- and "cleaned up" quite a lot of space (uselessly) and still haven't resolved the problem.....

I can the "canola -vvv" someone earlier had recommended. I past some "Multitask Model with filters, past the "no autostart plugins" messages, the last thing that looks ok is a "setting battery status ..." and "battery status is full", then it starts with a

Code:

1242265366.8972 DEBUG system:112:_update_battery() Setting battery status to (1, 1.000000).
1242265366.9083 DEBUG system:224:_do_disable() Asking system to keep the screen light on.
1242265366.9245 DBG_W controller:433:db_locked() received DB locked signal but already notifying user, ignoring it ...
1242265368.2218 DEBUG controller:132:get_controller_for_model() looking for controller for model with filter 'Model/Notify/Error/Fatal' ...

Which looks like a locked DB? (which? where?) The looks like it then devolves to the error message, and screen prompt as everyone is seeing ...

I can post the full log if it'd be helpful.

Last edited by fattomm; 2009-05-14 at 02:05. Reason: verbose logging messages added

Quote & Reply |