Hi!
I have one basic installation (v 13 beta 2 updraded to 3) with icewm.
I think that icewm not is the right desktop for my mother, so I will try with LXDE, that not comes installed on the .iso
To install LXDE and get full integration with Antix is just"apt-get install lxde" or I need to tweak something more?
topic title: Install LXDE on antix basic instalalation
13 posts
• Page 1 of 1
-
Posts: 74
- Joined: 21 Apr 2013
-
Posts: 765
- Joined: 27 Dec 2011
#2
I just tried, and lxde is in"metapackage-installer"
It seems to work just fine!
It seems to work just fine!
-
Posts: 765
- Joined: 27 Dec 2011
#4
I have been using lxde since the last post, and I have not had any problems yet...
Just saying..
Just saying..
-
Posts: 765
- Joined: 27 Dec 2011
#6
Lxde does use a bit more ram than fluxbox, but not too bad, In my case, lxde uses around 100+ a few, and fluxbox uses 65-70 ish.
-
Posts: 74
- Joined: 21 Apr 2013
#8
I have done"apt-get install lxde" and now I have some minor issues
-LXDE not appears pressing F1 on the login menu
-I can't find the antix configuration panel. Maybe I have remove it by mistake?
-If I click on the ScreenLock icon (right side on the task bar) the screen goes back and never come back.
Any ideas?
-LXDE not appears pressing F1 on the login menu
-I can't find the antix configuration panel. Maybe I have remove it by mistake?
-If I click on the ScreenLock icon (right side on the task bar) the screen goes back and never come back.
Any ideas?
-
Posts: 765
- Joined: 27 Dec 2011
#9
1 antixcc-session-edit login options, and select lxde (I am sure there is an other way, but I don't remember)
2 try typing antixcc.sh in a terminal
3 sorry, I have no idea, but I would think simply apt-get-ing lxde might not set it up properly?
I think you might want to try to use the metapackage installer (menu/applications/accessories/metapackage-installer) would be a better idea, at least that way works fine for me?
2 try typing antixcc.sh in a terminal
3 sorry, I have no idea, but I would think simply apt-get-ing lxde might not set it up properly?
I think you might want to try to use the metapackage installer (menu/applications/accessories/metapackage-installer) would be a better idea, at least that way works fine for me?
-
Posts: 2,238
- Joined: 16 Dec 2007
#10
the lxde session start commands need added to slim.conf and to .xintrc. They are not included by default.
this info may help
========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"http://wiki.lxde.org/en/Arch_Linux#SLIM"
linktext was:"http://wiki.lxde.org/en/Arch_Linux#SLIM"
====================================
this info may help
========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"http://wiki.lxde.org/en/Arch_Linux#SLIM"
linktext was:"http://wiki.lxde.org/en/Arch_Linux#SLIM"
====================================
-
Posts: 1,308
- Joined: 31 Aug 2009
#11
The application update-default-desktop should do exactly what you want. If installing lxde creates a /usr/share/xsessions/*.desktop file then running update-default-desktop will add lxde to both slim.conf and your .xinitrc.
edit: SLiM is very lightweight but compared to most other desktop managers (like gdm or kdm, or lightdm) it is rather brain-dead. The update-default-desktop program is a crutch to help SLiM behave like other desktop managers by creating an entry in slim.conf and in ~/.xinitrc for every file in /usr/share/xsessions/. You just have to manually run update-default-desktop after you've installed or removed a window manager or desktop environment.
edit2: The update-default-desktop program also deals with the rox- and space- prefixes creating new"virtual" windows managers that have desktop icons. Actually, update-default-desktop is just a user-friendly wrapper around /usr/share/antiX/lib/make-xinitrc. Here is it's usage:
BTW: there is a bug in the current version of update-default-desktop that causes it to fail if the default desktop name has a space in it. This has been fixed for the antiX-13 final release. The underlying make-xinitrc program already deals with spaces in desktop names correctly.
edit: SLiM is very lightweight but compared to most other desktop managers (like gdm or kdm, or lightdm) it is rather brain-dead. The update-default-desktop program is a crutch to help SLiM behave like other desktop managers by creating an entry in slim.conf and in ~/.xinitrc for every file in /usr/share/xsessions/. You just have to manually run update-default-desktop after you've installed or removed a window manager or desktop environment.
edit2: The update-default-desktop program also deals with the rox- and space- prefixes creating new"virtual" windows managers that have desktop icons. Actually, update-default-desktop is just a user-friendly wrapper around /usr/share/antiX/lib/make-xinitrc. Here is it's usage:
Code: Select all
Usage: make-xinitrc [options] default-desktop|[slim.conf]
Output an xinitrc file to stdout that contains entries for all of the
.desktop files found in the directory: /usr/share/xsessions.
Include <icon>-<wm> versions as applicable.
Options:
-h --help show this help
-l --list list available desktops on one line
-L --long list available desktops, one per line
-p --prefix= Set prefix for finding xsessions dir and slim.conf
-s --slim update slim.conf instead of outputing xinitrc
Default SLiM conf file: /etc/slim.conf
Return success if xinitrc was created without error or if the slim.conf
file was updated without error. In all other cases return failure.
-
Posts: 74
- Joined: 21 Apr 2013
#12
I think that something is broke on my system
Also antixcc not is found
What is the correct process to install lxde?
What is the correct process to remove other desktop environments?
Code: Select all
root@antiX1:/usr/share/antiX/lib# ./make-xinitrc -s lxde
make-xinitrc Error: SLiM conf file does not exist: lxde
What is the correct process to install lxde?
What is the correct process to remove other desktop environments?
-
Posts: 1,308
BitJam - Joined: 31 Aug 2009
#13
You were directing make-xinitrc to update a file called"lxde" as if it were /etc/slim.conf. It errored out because it could not find the file you specified.
If you want it to update slim.conf then just give it a -s with no other parameters.
Contrary to what you might expect, SLiM does not use the first window manager as the default. SLiM's default is to give no window manager and let the .xinitrc script figure it out. This is why you must specify a default window manager when creating .xinitrc but not when updating slim.conf.
Having make-xinitrc error out easily is a feature not a bug. If what you ask it to do is clear and unambiguous, it will do it, otherwise it will error out. This is useful when it is used as part of the automated process of creating a Live antiX iso file. There are many steps involved in creating a Live antiX iso and if any of them fails (or might have failed) you want the process to stop immediately so you can address the issue.
This is why we have the more user friendly update-default-desktop wrapper script. What users' want is sometimes diametrically opposed to what is useful for automation. In order to avoid code duplication, we put the core functionality into make-xinitrc that is designed to be used inside of an automated system and then we created a update-default-desktop wrapper to provide are more user friendly interface to that same functionality.
If you want it to update slim.conf then just give it a -s with no other parameters.
Contrary to what you might expect, SLiM does not use the first window manager as the default. SLiM's default is to give no window manager and let the .xinitrc script figure it out. This is why you must specify a default window manager when creating .xinitrc but not when updating slim.conf.
Having make-xinitrc error out easily is a feature not a bug. If what you ask it to do is clear and unambiguous, it will do it, otherwise it will error out. This is useful when it is used as part of the automated process of creating a Live antiX iso file. There are many steps involved in creating a Live antiX iso and if any of them fails (or might have failed) you want the process to stop immediately so you can address the issue.
This is why we have the more user friendly update-default-desktop wrapper script. What users' want is sometimes diametrically opposed to what is useful for automation. In order to avoid code duplication, we put the core functionality into make-xinitrc that is designed to be used inside of an automated system and then we created a update-default-desktop wrapper to provide are more user friendly interface to that same functionality.