View Single Post
Posts: 209 | Thanked: 8 times | Joined on Nov 2005 @ Fishers, Indiana
#23
Originally Posted by penguinbait View Post
Thats really odd guys, just now this is what I did?

I loaded brand spanking new flash 10-7
untarred KDE from root
Booted and I thought it had crash, not sure if it actually did? I used the power button and turned off the n800.
I booted back up, installed becomeroot, osso-xterm, openssh-installer
logged in via ssh
What user did you log in as (user or root?)
Originally Posted by penguinbait View Post
ran stopmaemo
did you do anything besides typing 'stopmaemo' (i.e. sudo)?

(snip)
Originally Posted by penguinbait View Post
What exactly happens when you start kde from the menu, does the screen turn black? does the splash screen display, does the desktop load with icons. Are you rebooting it or does it crash? How long are you waiting after you click the KDE icon?
I normally run stopmaemo as user 'user' with no arguments. The screen goes white then black, then I see KDE starting up. In another ssh session I can see that matchbox is still running. It never quits and so once KDE starts up to the point where I get the blue desktop/icons I get the message about kicker crashing. Matchbox is still running and if I run '/etc/af-services stop' as root I can manually start kwin and kicker and things will work. Running stopmaemo via the KDE icon from the Extras menu does exactly the same thing.
I've finally come up with a sort of solution-- I added the line below to stopmaemo after the matchbox.sh stop:
sudo /etc/init.d/af-services stop

Originally Posted by penguinbait View Post
Larry when you run stopmaemo, as user "user" are you saying after matchbox stop runs, "ps | grep matchbox" shows it running? There is a small lag between when matchbox stops and kwin starts. the splash screen is displayed before kwin starts.
Yes, that's exactly what's happening. I can wait forever but matchbox never dies.

Larry