 |
 |
 |
|
 |
You are not logged in.
Actaully, if 'pidof' worked then you should be able to figure out what the parent process is with:
grep PPid /proc/`pidof X`/status
I get:
PPid: 4444
Then you can try checking what process that is, and kill it if it doesn't look important. :-)
Offline
Looks like Xorg is started by xinit. If you kill xinit, does that stop X from restarting? :-)
Offline
turns out i've been killing xorg- when i did the parent with your suggestion that killed xinit- I'm killing away and no matter what I kill AsusLauncher always comes back!
Offline
It may not be xinit at all... there looks like there's a shell script calling startx which calls xinit. Do you mind pasting the output of...?
ps -eo pid,ppid,user,args
Offline
Also interested in the contents of the /etc/inittab file :-)
Offline
Woo hoo. No kicker though. :-)
Offline
Yeah, if I try to run kicker it says "ERROR: Communication problem with kicker, it probably crashed"
Offline
yikes, I didn't understand a thing out of that whole exchange. goes to show how much I know about linux: nothing!
however the scans that ant came up with definitely look promising
Offline
Crazy idea... what happens if you choose "Run command" from that right-click menu and type...?
programs:/
Offline
Forget the other pictures:
http://www.flickr.com/photos/eeeuser/1797406837/
Looks like we got it!
Offline
The gui probably keeps restarting because it is an init script. Check if there is a file called /etc/init.d/kdm... if there is type "sudo /etc/init.d/kdm stop"... if that doesn't exist then see if /etc/init.d contains any files with the word 'asus' in it... that might be the init script for the asus launcher.
Good luck.
Offline
Nice! :-) How'd you get that?
Offline
My next question would be how does the KDE environment run compared to the Basic GUI? Is it just as snappy or does it cause extra overhead?
Offline
Here's the whole process to get KDE:
0) apt-get kicker
1) edit the xorg to remove the line: Option "DontVTSwitch" "true"
2) reboot, then ctrl alt F3, login
3) killall: fastinit, startx, xinit, xorg (at some point screen will go back to tty2- so press ctrl alt F3)
4) X &
5) go back to tty3 (ctrl alt F3) and ctrl+c
6) export DISPLAY=:0
7) kdesktop &
8) kicker &
9) kwin &
10) ctrl alt F2
Semi-hilarious part? Right above "logout administrator" you'll see "Easy Mode".
Offline
oinker wrote:
Nice! :-) How'd you get that?
yes please! that's exactly what i'm looking for. no need for me to even consider installing xp
Offline
Seems to be just as fast as AsusLauncher
Offline
But wasn't kicker crashing on startup?
Anything interesting under the Applications menu? :-)
Offline
yikes, how does one apt-get kicker?
Offline
robhimself wrote:
yikes, how does one apt-get kicker?
Usually you'd just type 'apt-get install kicker' from a console window.
Offline
ant wrote:
Forget the other pictures:
http://www.flickr.com/photos/eeeuser/1797406837/
Looks like we got it!
Excellent news!! That is awesome! That just made me increase my desire for the eee... I can't wait for this to get tweaked to perfection...
Offline
kicker was crashing but i think it's because i didn't do the whole export DISPLAY thing, or maybe because i was doing it too early. I'm not really sure- haha
Stuff that KDE has that AsusLauncher doesn't:
Accessories: Font Viewer, PostScript Viewer, Address Book, Character Selector, Organizer, Print Jobs, Send a Fax
Graphics: Gwenview, Image Viewer, mtPaint graphic editor
Multimedia: Audio CD Ripper
System: Security, event viewer, menu editor, performance monitor, synaptic package manager
Utilities: Desktop pager, palm document converter, palm pilot tool
I'm sure there's more stuff
Let me stress for those that are gonna try it, this is a crude method of doing this all, I'm sure there's a cleaner way. It doesn't look like it's screwing up the Eee PC at all- but i'm sure it could. Regular AsusLauncher still boots after trying out KDE- it doesn't stay with KDE.
Offline
oinker wrote:
robhimself wrote:
yikes, how does one apt-get kicker?
Usually you'd just type 'apt-get install kicker' from a console window.
I did just that and this appears:
E:could not open lock file /var/lib/dpkg/lock - open (13 permission denied)
E: unable to lock the administration directory (/var/lib/dpkg/), are you root?
Offline
robhimself wrote:
I did just that and this appears:
E:could not open lock file /var/lib/dpkg/lock - open (13 permission denied)
E: unable to lock the administration directory (/var/lib/dpkg/), are you root?
You'll normally see that if you don't have administrator permissions.
You can try this instead, which will ask for a password to upgrade your permissions:
sudo apt-get install kicker
Offline
oinker wrote:
robhimself wrote:
I did just that and this appears:
E:could not open lock file /var/lib/dpkg/lock - open (13 permission denied)
E: unable to lock the administration directory (/var/lib/dpkg/), are you root?You'll normally see that if you don't have administrator permissions.
You can try this instead, which will ask for a password to upgrade your permissions:
sudo apt-get install kicker
yep, just happened to run into it as well, but something else popped up.
it's too much to type out since I'm using another computer but it definitely does have something to do with the fact that I have a taiwanese EEE.
Offline
robhimself wrote:
yep, just happened to run into it as well, but something else popped up.
it's too much to type out since I'm using another computer but it definitely does have something to do with the fact that I have a taiwanese EEE.
Hmm, I'm not sure. I wish I had an Eee to try it myself. :-)
There's another thread on the board where someone gives steps on setting up apt-get to work properly:
http://forum.eeeuser.com/viewtopic.php?id=630
It may be worth your while to try steps 3 through 6 in the first post of that thread, then try to install kicker again.
Offline
