[maemo-developers] [maemo-developers] Reboot Cycle

From: Johannes Eickhold jeickhold at gmx.de
Date: Tue Aug 29 23:58:48 EEST 2006
Am Freitag, den 28.07.2006, 00:06 -0400 schrieb Peter Kahle: 
> Well, it was inevitable, I got myself into a reboot cycle. Using the 
> no-lifeguard-reset flag seems to bring the system back to a very stable 
> state, though, so I'm wondering if there's a list of programs that 
> should be running that the lifeguard will watch for so I can debug what 
> exactly is failing?
> If not, if someone with a fairly pristine system could send me a list of 
> what's running on their box, that would be great too.

I have the same problem: used upt-get upgrade while having a
"http://repository.maemo.org/ mistral" line in my /etc/sources.list and
entered reboot cycle. :-( - After that I found the "Apt-got my way into
a reboot loop??" thread in this list and used the no-lifeguard-reset
flag. Then I was able to complete the interrupted upgrade with "dpkg
--configure -a". Now it seems that gstreamer elements can't be loaded
anymore (segmentation fault, when I try to start e.g. sofsip_cli on the
command line). Also the video and audioplayer can't play files anymore.

Has anybody found a solution to this problem that avoids reflashing?
Reflashing would cause me a lot of work :-/.

I think it would be a good idea not to say "You can freely alternate
between AI 2006 and apt-get, say. Changes done to the system via apt-get
or dpkg are picked up by the AI 2006 without confusing it, and vice
versa." like [1] does, if it can cause so much trouble. As quite some
packages in the ApplicationCatalog state that they depend on some
packages in "http://repository.maemo.org/ mistral" it is not uncommon to
have it in the sources.list.

I admit I typed "y" too fast when apt-get asked me to proceed and I
didn't read the update lines carefully enough.



More information about the maemo-developers mailing list