Do you like the simple tabbed interface of Easy Mode, but want the functionality of the advanced desktop? Now you can get the best of both worlds. You can keep the simple AsusLauncher GUI and but have all the power and perks of running the KDE desktop (including using Beryl). You won't even have to give up your regular desktop to do it.
This guide will show you how to have AsusLauncher at startup of advanced desktop.
If you have not yet enabled Advanced Desktop, follow this guide
First you should experiment with AsusLauncher before committing it to startup. We'll try it out, not because it is hard to fix, but it's easier to fix problems by reseting rather than possibly mucking about with the restore function or other Linux distributions. To try AsusLauncher out, follow these steps.
sudo /opt/xandros/bin/AsusLauncher
Alternatively, if you want to be able to access the regular desktop, you will need a system tray icon to toggle the visibility of AsusLauncher. You can do this with the following command in a terminal.
ksystraycmd sudo /opt/xandros/bin/AsusLauncher
You will notice an X near the battery meter and other system tray applications. You can toggle the visibility of AsusLauncher by clicking this X.
If you want to quit AsusLauncher you will either have to reboot or run the taskmanger as root. To kill the process from a taskbar, follow these steps. If you want to quit the AsusLauncher quick test, simply press <CTRL> + 'C' in the console window.
sudo ksysguard --showprocesses
If you want to regularly switch between AsusLauncher (Easy Desktop Mode)and the Advanced Desktop without rebooting, a good alternative will be to create a shortcut, like eg: a desktop Icon, where which you can enable/disable the AsusLauncher anytime you want to.
Konsole
konsole -e sudo /opt/xandros/bin/AsusLauncher
After you doubleclicked your 'easy desktop'-icon you'll see that Konsole still is active and waiting. You can exit the easy desktop mode by closing the console window, or pressing <CTRL> + 'C' in the konsole-window.
You can copy or move the 'easy desktop'-Icon anywhere you'd like (eg. in: 'My Documents' or so…)
sudo kwrite /home/user/.kde/Autostart/AsusLauncher.desktop
[Desktop Entry] Comment= Exec=sudo /opt/xandros/bin/AsusLauncher GenericName= Icon=kcmx Name=AsusLauncher Path= StartupNotify=false Terminal=0 TerminalOptions= Type=Application X-KDE-SubstituteUID=false X-KDE-Username=
[Desktop Entry] Comment= Exec=ksystraycmd sudo /opt/xandros/bin/AsusLauncher GenericName= Icon=kcmx Name=AsusLauncher Path= StartupNotify=false Terminal=0 TerminalOptions= Type=Application X-KDE-SubstituteUID=false X-KDE-Username=
One problem with running AsusLauncher in advanced mode is that all applications run as root (the superuser). This causes some undesirable behavior, including that the application sees the home directory as /root rather than as /user/home. Described below is some rather tedious editing that will force applications to run as user rather than root.
Note: Some apparently simpler ways of accomplishing this fail to work properly. See this forum thread for details.
[Desktop Entry] Comment= Exec=sudo -u user GenericName= Icon= Name=Udo Path= StartupNotify=false Terminal=0 TerminalOptions= Type=Application X-KDE-SubstituteUID=true X-KDE-Username=user
shortcut="/home/user/.AsusLauncher/udo.desktop"
For example, the entry for File Manager should look something like this:
<parcel simplecat="Work" shortcut="/home/user/.AsusLauncher/udo.desktop" extraargs="/usr/bin/XandrosFileManager -maximized" icon="file_manager_norm.png" selected_icon="file_manager_hi.png"> <name lang="en">File Manager</name> </parcel>
Exec=run-skype.sh
to read as follows:
Exec=sudo -u user run-skype.sh
Also note that /usr/games is not in root's default path, so you have to specify the full pathname of any program that is located there or the program won't launch. For example, in the file /usr/share/applications/frozen-bubble.desktop, the line
Exec=frozen-bubble
has to become
Exec=sudo -u user /usr/games/frozen-bubble
This wiki is primarily based on http://forum.eeeuser.com/viewtopic.php?id=5741
rio sosh code rio