View Single Post
penguinbait's Avatar
Posts: 3,096 | Thanked: 1,525 times | Joined on Jan 2006 @ Michigan, USA
#25
Originally Posted by lbattraw View Post
What user did you log in as (user or root?)

did you do anything besides typing 'stopmaemo' (i.e. sudo)?

(snip)

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


Yes, that's exactly what's happening. I can wait forever but matchbox never dies.

Larry

Can you tell me whats installed, is this a plain jane. I have heard of people having problems if they are running a theme. I am only using the default theme, could this be an issue with you?


stopmaemo should be run as user, the variables in the stopmaemo script are necessary to get matchbox to stop. I only ran as user, no sudo is needed.

If you look in the stopmaemo you will see the line to stop matchbox, what happens if you run that manually.

You say you "SEE" matchbox is still running? Are you talking visibly, not ps? You can not see matchbox running, you can see maemo-desktop running?