Active Topics

 


Reply
Thread Tools
Posts: 12 | Thanked: 3 times | Joined on Oct 2008
#11
Originally Posted by Andre Klapper View Post
Hi, there's enough free disk space, I assume?
> 95 MB. I've been watching the disk space with an applet (or desklet or how it is called) - it's visible on the screenshot above.

How about the CPU usage? Running "top" in a Terminal window should tell you if there's processes using a lot of CPU and/or memory...
I am running an applet that shows the CPU and memory usage and no, CPU was idling most of the time.

You have installed the latest updates, I assume? (running version 4.2008.36-5)
Yes, I do (mentioned in the first post). I actually feel like it could be caused by the 36-5 upgrade so right now (after fourth reflash) I am using 30-2 and waiting when/if it occurs again. Pity that latest maemo-mapper seems like depends on the 36-5 as it wants to upgrade some 33 MB applications..
 
Posts: 12 | Thanked: 3 times | Joined on Oct 2008
#12
Originally Posted by mikkov View Post
My guess is that reason is found somewhere from /home/user/.osso directory
Yes, I thought that too. I was thinking about making a full disk backup before it happens and then compare all files after the problem appears.

I tried using "tar cvf - / | ssh myhost "tar cf - ." but it died early when it started copying the /dev nodes. How do you copy the whole "/"? Maybe Midnight Commander would do it? Or the full GNU tar? I also tried rsync but that died (was killed) too, probably not enough memory or something.
 
Posts: 12 | Thanked: 3 times | Joined on Oct 2008
#13
Originally Posted by qwerty12 View Post
Some people installed bash...

http://www.internettablettalk.com/fo...ad.php?t=14915
So I am not alone. I am so glad to hear that. Maybe that Nokia engineers would like to look into this issue as reflashing a fully set up device is a major pain.

Anyway, when it happened to me second time (on Saturday afternoon) I was using a totally clean device. I had no external application installed (well apart from openssh) and was just browsing using the internal web browser when it happened.. So I doubt that installing bash would help :-(
 
Benson's Avatar
Posts: 4,930 | Thanked: 2,272 times | Joined on Oct 2007
#14
Well, you can try installing bash; if it does help, it helps , and if it doesn't, no harm done. It seems like the best hope found so far.


(Although as it's been noted in that thread, it's very puzzling why bash should fix it, and what triggers the manifestation in the first place...)
 
Posts: 961 | Thanked: 565 times | Joined on Jul 2007 @ Tyneside, North East England
#15
I was experiencing this very issue when playing with the Mythtv port back in spring.

It was always when I exited myth. I don't use modest at all, and it's 2 revisions of diablo back, so it's been around for a while
I had bash installed, and it was still doing it. I tried a few things, and read a few threads but found nothing that pinpointed it, or fixed it other than a reflash, and even with a full complete backup, that took a couple fo hours to reinstall everything and get it all back to just how..

Be really interested in a fix which does not need a reflash, especially if it's fairly straightforward.
 
Posts: 12 | Thanked: 3 times | Joined on Oct 2008
#16
It happened when you exit myth? That is quite interesting considering that for me the problem appeared first time when I UNinstalled "mythetomer" on Friday night. I even thought that perhaps the mythetomer uninstalled also some dependent libraries that draw the widgets and stuff (nonsense, I know).

When it happened second and third time, after complete reflash and without anything myth* related I became clueless and posted here.

Though I have probably found out what was behind the sudden charge level drop from full to 14% during one reboot. It seems that the charge level indicator stops updating itself so it keeps showing FULL eventhough it is almost empty (thanks to battery-status I can see the real battery state).

Another coincidental thing on that black Friday was that I turned the device off and then couldn't turn it back on on Saturday morning. It just didn't want to start booting. Oh man. I read about it a bit recently and realized that the "fix" for this issue is simply to never turn it off (the other fix using the fridge is something I don't want to accept :-).

Unfortunately the subject of this thread (disappeared UI widgets) can happen even when you don't turn the device off...
 
Reply


 
Forum Jump


All times are GMT. The time now is 21:57.