Reply
Thread Tools
Posts: 604 | Thanked: 108 times | Joined on Feb 2010 @ Phoenix, WA
#1
hi everyone3,

this seems a bit weird. my load applet icon is always maxed out white bars, or even red. it goes back and forth... so i did 'top' and that one process up top is almost always about 75-80 percent.

http://www.flickr.com/photos/29629961@N03/4775801455/

i noticed this today... help plz
 
Posts: 755 | Thanked: 406 times | Joined on Feb 2008 @ UK
#2
Kill hildon-input-method or reboot. Does it start behaving?
 
Posts: 83 | Thanked: 130 times | Joined on Dec 2009
#3
err.. Linux noob here. how exactly did u pull up the info on Terminal?
 
ossipena's Avatar
Posts: 3,159 | Thanked: 2,023 times | Joined on Feb 2008 @ Finland
#4
Originally Posted by rnb89 View Post
err.. Linux noob here. how exactly did u pull up the info on Terminal?

Originally Posted by SAABoy View Post
... so i did 'top' and that one process up top is almost always about 75-80 percent....
write the bolded text to terminal and press enter
__________________
Want to know something?
K.I.S.S. approach:
wiki category:beginners. Browse it through and you'll be much wiser!
If the link doesn't help, just use
Google Custom Search
 

The Following User Says Thank You to ossipena For This Useful Post:
Posts: 71 | Thanked: 33 times | Joined on Dec 2009 @ Munich, Germany
#5
I did also notice this the last couple of weeks (after upgrade to PR 1.2). I first thought it's been because my son recorded a video which brought up a status message like "Memory full". But even after deleting all videos and pictures load maxes out a lot.

I did get some improvement though by using the power saving hack (vdd_1, vdd_2)
 
Posts: 604 | Thanked: 108 times | Joined on Feb 2010 @ Phoenix, WA
#6
Originally Posted by codeMonkey View Post
Kill hildon-input-method or reboot. Does it start behaving?
How do I kill a process?

I've rebooted a few times and it doesnt change anything. In fact its still doing it now. I dont have any windows open or anything going on (to the best of my knowledge) and its sitting at 90-100% ;(
 
Posts: 4,556 | Thanked: 1,624 times | Joined on Dec 2007
#7
In Xterm (the terminal) type in kill (or killall) hildon-input-method.

I recommend installing HTOP (from the extras repo). After using that app it will show you all running processes and you can kill from there.
__________________
Originally Posted by ysss View Post
They're maemo and MeeGo...

"Meamo!" sounds like what Zorro would say to catherine zeta jones... after she slaps him for looking at her dirtily...
 

The Following User Says Thank You to Laughing Man For This Useful Post:
Posts: 604 | Thanked: 108 times | Joined on Feb 2010 @ Phoenix, WA
#8
Originally Posted by Laughing Man View Post
In Xterm (the terminal) type in kill (or killall) hildon-input-method.

I recommend installing HTOP (from the extras repo). After using that app it will show you all running processes and you can kill from there.
Thank you.

I typed 'kill hildon-input-method' and hit enter.
I got this back: "sh: bad pid 'hildon-input-method'
 
cddiede's Avatar
Posts: 1,034 | Thanked: 784 times | Joined on Dec 2007 @ Annapolis, MD
#9
Originally Posted by SAABoy View Post
Thank you.

I typed 'kill hildon-input-method' and hit enter.
I got this back: "sh: bad pid 'hildon-input-method'
The kill command expects you to specific processes for termination by Process ID Number (PID). This is the left most column of the top command output. In your posted screenshot, that would be 1211.

Beware that some processes don't die easily and if the kill command doesn't work (the process still shows as running in your "top" display), then try using the "-9" argument, which tells the system to kill with extreme prejudice. Like so:

kill -9 <PID number>

Alternately, you can use the pkill (process kill) command to kill processes by their name, such as:

pkill hildon-input-method

Note that none of this tells us WHY your hildon-input-method has run amok...

Last edited by cddiede; 2010-07-09 at 19:00.
 
Posts: 604 | Thanked: 108 times | Joined on Feb 2010 @ Phoenix, WA
#10
Originally Posted by cddiede View Post
The kill command expects you to specific processes for termination by Process ID Number (PID). This is the left most column of the top command output. In your posted screenshot, that would be 1211.

Beware that some processes don't die easily and if the kill command doesn't work (the process still shows as running in your "top" display), then try using the "-9" argument, which tells the system to kill with extreme prejudice. Like so:

kill -9 <PID number>

Alternately, you can use the pkill (process kill) command to kill processes by their name, such as:

pkill hildon-input-method

Note that none of this tells us WHY your hildon-input-method has run amok...
WOOOOHOOOOOOOO!!! pkill hildon-input-method didnt do anything. kill (PID number) didnt do anything. kill -9 (PID number) worked! xterm crashed and a yellow message said 'internal error, xterm app closing' you know... and now its all better
 
Reply


 
Forum Jump


All times are GMT. The time now is 03:52.