Search Results for 'lightdm desktop-session'

[Moderator BobC]

So on my respin, without slim or lightdm, here is what I do…

in ~/.bashrc

xrunning=$(ps -ef | grep "/usr/lib/xorg/Xorg" | wc -l)
if [[ "$xrunning" -lt 2 ]]; then  
  # x not running
  echo ""
  echo "Starting X-Windows for antixbc..."
  antixbc
fi

and antixbc is

#!/bin/bash

. $HOME/.desktop-session/desktop-session.conf
. /usr/local/bin/desktop-session icewm
startx

• This reply was modified 2 years, 11 months ago by BobC.

[Moderator BobC]

I was hoping Dave would chime in, as I found some posts which I tried to follow on how to do it. BTW, lightdm is different I think, than lxdm.

I think this is really related to how lightdm decides to put up is session list and what it calls based on which you select. My optimal solution is to add desktop-session icewm to that list, and just select it 🙂 But I am very simple minded…

[Member Xecure]

About icewm not using .icewm/startup, I have no experience with this. It should do it out of the box when loging in to icewm. First make sure the file is executable. If this continues to not respond, you could use the “bad” solution, that is editing the /usr/share/icewm/startup file and adding the launch commands there. It is a very bas solution, but it will keep you out of trouble for some time.

About lightdm. It has been a miss and miss experience for me with lightdm and default-session. I tried and tried but I gave up and went back to SLiM. The farthest I got editing /etc/lightdm/Xsession. I didn’t do it correctly as it never worked for me.
aledosim opened a thread trying to do the same with lxdm, and seems to have it work properly.

aledosim wrote:

…
Replaced this line on /etc/lxdm/Xsession:

# mandriva, debian, ubuntu
	exec /etc/X11/Xsession "$LXSESSION"

with this one:

# mandriva, debian, ubuntu
        exec /usr/local/bin/desktop-session "$LXSESSION"

I will try returning someday to lightdm and following aledosim’s example, but I really am not looking forward to it right now.

If you get it to work properly for you, BobC, please come back and report how you got it to work. I am sure I’m not the only one interested in this.

• This reply was modified 2 years, 11 months ago by Xecure. Reason: wording

antiX Live system enthusiast.
General Live Boot Parameters for antiX.

I installed from core and trying to duplicate the functionality of my normal full installs. The reason for trying to run from core is so I can suspend, hibernate and resume. I have that working correctly. I haven’t had much luck getting those to work with antiX full, but had no problem with them on core.

I would like to use lightdm instead of slim because I have 2 machines with weird video that need 35 mb for slim, but a console login which does work and avoids slim is pretty ugly. I am just trying to get lightdm to run desktop-session to start a normal antiX icewm session, including running ~/.desktop-session/startup and ~/.icewm/startup so that my system is setup as normally as possible.

I have lightdm with either icewm or xfce working now, but it doesn’t run the desktop-session system ( which includes ~/.desktop-session/startup). It does run icewm, but not ~/.icewm/startup. The system is somewhat usable, but not good as a result.

I have tried modifying /etc/lightdm/lightdm.conf but can’t seem to get anything to try to execute at all.

The lightdm screen has options for default session, icewm and xfce. Nothing seems able to change that. I can’t see where the list comes from. Lightdm doesn’t have a man entry and the website isn’t any help. I don’t know what the .conf file options are supposed to do.

Maybe I should just give up on lightdm and just login manually?

• This topic was modified 2 years, 11 months ago by BobC.

I installed from core and then added xfce and icewm and lightdm, plus a few other applications like geany and meld and gnome games

Then I added upower, pm-utils and uswsusp to try to get the ability to suspend, resume and hibernate. That does work even on my most finnicky Dell M2400 laptop.

In my attempt to get IceWM menus, I installed menu, menu-manager-antix, menu-icewm-antix, desktop-defaults-icewm-antix, desktop-session-antix and menu-xdg. But I cant get apps to add to the menu automatically.

When I add a package at the end it says

Writing Menu: icewm

But even if I restart icewm, the options don’t appear…

What did I miss????

TIA

• This topic was modified 2 years, 11 months ago by BobC.

[Anonymous]

maybe #31725 is intended as “instruction, specific to this case, to get it working”.
I drafted a long post prior to reading that, and my post recommends a cmd_login line which matches that seen in default antiX 19 full.
Here, I’m prefacing the long post by mentioning that I am not contradicting the instruction provided in #31725 ~~ I’m just covering how the dots are connected to work in the as-shipped antiX full.
___________________________

The topic linked from post #1 discusses antix19core-LXDE —} lightDM + lxdm + (presumably) lxsession.
That line (in post #1 here) is suitable only for use with a full-blown DE (desktop environment, e.g. LXDE, Xfce, Mate) .

lightDM and SLiM serve only as “display manager” aka “login manager”.
— starts Xorg server
— checks user+password login credentials
— uses a PAM (kernel pluggable authentication module) mechanism to register a “seat”
(your tty, er console, input {–} output display hardware marshalled by xserver)
— invokes the “session manager of choice” component… and then it just waits, serving as a idle wrapper
(idle until logout/login is requested, or exit/shutdown)

Upon installation of any display manager package, the DM is registered with rc.d to be automatically started for runlevels 2 and 5.
If, during installation, another DM is found already present on the system, you are asked to choose which of the DMs will be enabled.
^—v
During a session, if you logout (or you kill the DM process, or it crashes) the rc.d will automatically*** restart the DM.

*** a sysadmin is free to install multiple DMs and manually change which one (or none) is started for each runlevel.

The “startx” command is supposed to be (provide) a convenience… but, as an abstraction, it muddies the water.
Users are resigned to not knowing / caring which display manager and auth mechanism and session manager components will be invoked in order to create their “desktop session”.

We probably cannot put much weight in the terms “standard” vs NON-standard”.
— some distros do not use, nor provide, a “startx” command
— some distros are configured to only start a DM when entering runlevel 5
— some distros replace rc.d with systemd
— some distros ship only one DesktopEnvironment or WM
— the sessionmanager component of a given DesktopEnvironment may demand use of its own WM
____________________________________________

login_cmd setsid /usr/local/bin/desktop-session %session
https://gitlab.com/antiX-Linux/Build-iso/blob/master/Themes/full/misc/slim.conf

This SLiM login_cmd line (as seen in antiX full) calls a “session manager” utility named desktop-session which, in turn,
invokes whichever “session” has been chosen via F1, e.g. “rox-icewm” (and passed as a commandline argument).
Additionally, and in place of (instead of) sourcing ~/.Xsession, the utility sources both an “all cases” .startup file
and (depending on which WM has been requested for this session) ~/.fluxbox/startup or ~/icewm/startup or…

rox desktop manager (and spacefm -d) are windowmanager agnostic.
Further, either of them can be manually invoked (and killed), at will during the course of a “desktop session”.

When the antiX “session manager” utility (the desktop-session command) parses the commandline args for a given session request, it selectively starts the requested “desktop manager” (or none) along with the requested “window manager”… and each of those can be (and typically are) configured to autostart additional processes. Along the way, ~/.xinitrc is never sourced. (IIRC, by default, on an antiX full system that file isn’t even present)

____________________________________________

re: “startx [..] error message & restarting”

https://www.antixforum.com/forums/topic/antix-19-1-based-on-debian-sid-available/

It seems that if you use startx, you need to also install xserver-xorg-legacy, but it is not needed if you use slim.
If user does chooses slim login manager, you MUST edit /etc/slim.conf as shown above otherwise you get the error reported by Koo.

[Anonymous]

requires clarification?

Similar to macondo’s recent adventure (start with core
add ratpoison WM), SLiM
inclusion of a graphical login manager may not be necessary ^or desirable.

https://gitlab.com/skidoo/slim-antix
Demonstrably, skidoo is among SLiM’s most enthusiastic proponents. Given a context of “building up from antiX Base Edition”, across various prior topics I have explained how/why SLiM represents a “lesser evil” compared to LightDM and other available graphical login managers.

…you might find bspwm very similar in look
[..]
don’t get rid of Slim; installs of desktops will complain if you do.
[..]
Also be aware that lightdm-gtk-greeter-settings has a problem in antiX19

^— faff, and such distraction is disrectpectful of the OP’s clearly expressed goal.

.
re: “don’t get rid of Slim; installs of desktops will complain if you do.”
We should expect that only JWM, fluxbox, iceWM — the 3 window managers whose packages and settings are tampered by antiX — would “complain”, and presence/absence of SLiM isn’t the deciding factor. For jwm/fluxbox/icewm sessions launched via startx or SLiM or otherwise, if launch is not chained via /usr/local/bin/desktop-session, you must be prepared to accept responsibility for manually (tailoring and/or) maintaining a suitable keys file, startup file, menu file {ellipsis}…

package: “desktop-session-antix”
package “desktop-defaults-antix”
package: “desktop-defaults-*-antix”
macondo’s recent post accurately described the antiX desktop-session stuff as being “endemic”.
A decision to forego inclusion of these will have broad (sweeping) consequences.
Vis macondo’s case, it’s absolutely “do-able”. Unfortunately, a gap exists, in terms of supporting such cases.

[Member oops]

… FI: This solution work here. (/usr/share/lightdm/lightdm.conf.d/01_my.conf — instead to: — /etc/lightdm/lightdm.conf)

If you decide to install LightDM, it would ignore the ~/desktop-session/startup file

A workaround here:
https://www.antixforum.com/forums/topic/converting-antix-to-an-xfce4-based-distro-a-tutorial-test/#post-22050

[Anonymous]

Maybe it’s better to add into an other file (free of future updates of /etc/lightdm/lightdm.conf)

antiX doesn’t ship LightDM.
If you decide to install LightDM, it would ignore the ~/desktop-session/startup file… so you would need to come up with another plan. (I don’t use LightDM, so can’t assist with that)

[Member oops]

Good tuto manyroads.
I did some changes too here for a multi-users ability, but without XFCE, iceWM is nice too.
lightdm , lightdm-gtk-greeter , lightdm-gtk-greeter-settings , ~/.xsessionrc

#!/bin/sh
#
#http://blog.rnstlr.ch/switching-from-slim-to-lightdm.html
#http://blog.rnstlr.ch/setting-up-the-awesome-window-manager-in-ubuntu-1604.html
# sudo apt install awesome
# ~/.xsessionrc
#
case $1 in
awesome)
#    export $(gnome-keyring-daemon -s -c pkcs11,secrets,ssh,gpg)
    ;;
esac
bash /home/$USER/.desktop-session/startup_for_lightdm &

[Member oops]

Thank you Dave for these accurate information, I will do some tests and try to keep Slim (only 9MB – slim)(at least= 9MB+5MB- lightdm),

echo "------------------------------------" && mem=0 && while read -r rss comm ; do mbs=$((rss/1024)); mem=$((mbs + mem)); echo $mbs"MB - $comm"; done <<< "$(ps -u $USER -wo rss=,comm= --sort -rss)" && echo "------------------------------------" && echo $mem"MB: Memory used by user '$USER'"
------------------------------------
26MB - Xorg
9MB - slim
6MB - cupsd
5MB - console-kit-dae
5MB - polkitd
4MB - bash
3MB - haveged
...

FOR MX18 ( at least= 9MB+5MB- lightdm:
echo "------------------------------------" && mem=0 && while read -r rss comm ; do mbs=$((rss/1024)); mem=$((mbs + mem)); echo $mbs"MB - $comm"; done <<< "$(ps -u $USER -wo rss=,comm= --sort -rss)" && echo "------------------------------------" && echo $mem"MB: Memory used by user '$USER'"
------------------------------------
32MB - Xorg
13MB - smbd
12MB - NetworkManager
10MB - ModemManager
9MB - cups-browsed
9MB - udisksd
9MB - polkitd
9MB - lightdm
7MB - lpqd
7MB - cupsd
7MB - upowerd
6MB - bash
5MB - lightdm
5MB - accounts-daemon
5MB - nmbd
5MB - smbd-notifyd
4MB - su
4MB - wpa_supplicant
4MB - bluetoothd
4MB - cleanupd
4MB - haveged
3MB - systemd-logind
3MB - rsyslogd
3MB - dhclient
3MB - ps
2MB - systemd-udevd
2MB - cgmanager
2MB - cron
1MB - rpcbind
1MB - getty
1MB - init
...

… Or maybe just as a workaround, to show at the login slim prompt, the list of the available users.

cat /etc/passwd | grep “:/bin/bash” | sort | cut -d: -f1
User1
User2
User3
…

PS: Slim is interesting into antiX, because only few process are actives :

inxi -Sxxx
System:    Host: antix1 Kernel: 5.0.0 i686 bits: 32 compiler: gcc v: 6.3.0 Desktop: IceWM 1.4.2 
           info: icewmtray dm: SLiM 1.3.4 Distro: antiX-17.4.1_386-full Helen Keller 28 March 2019 
           base: Debian GNU/Linux 9 (stretch) 

pgrep -ox slim | xargs pstree -p
slim(2349)─┬─Xorg(2357)───{InputThread}(2428)
           └─desktop-session(2655)───icewm-session(2703)─┬─icewm(2708)───nemo(4539)─┬─{dconf worker}(+
                                                         │                          ├─{gdbus}(4542)
                                                         │                          ├─{gmain}(4541)
                                                         │                          └─{pool}(5068)
                                                         ├─icewmbg(2707)
                                                         └─icewmtray(2718)

… Compared to Lightdm

pgrep -ox lightdm | xargs pstree -p
lightdm(2825)─┬─Xorg(2915)───{InputThread}(3034)
              ├─lightdm(3269)─┬─sh(4643)─┬─ssh-agent(4717)
              │               │          └─xfce4-session(4727)───xfce4-session(4728)─┬─applet.py(4805)───{gmain}(4+
              │               │                                                      ├─clipit(4784)─┬─{gdbus}(4842+
              │               │                                                      │              └─{gmain}(4832+
              │               ├─{gdbus}(4627)
              │               └─{gmain}(4626)
              ├─{gdbus}(2852)
              └─{gmain}(2838)

• This reply was modified 4 years ago by oops.
• This reply was modified 4 years ago by oops.
• This reply was modified 4 years ago by oops.

[Anonymous]

why don’t you provide an “agnostic” SLiM package, with a further package for its configuration, like slim-antix.deb?

Why == because striving to side-patch the code is a tail-chasing excercise toward frustration.
The disparity between forks has become too extreme.
Patches atop patches atop patches, they do not merge cleanly and require manual cherrypicking and manual merging
Here’s my personal build, tailored to antiX: https://gitlab.com/skidoo/slim-antix

is there a way to use the newer and surely better supported SLiM of antiX, configuring it like the Stretch one?

It’s linux, so the answer to nearly any question is “yes”. Unfortunately, I don’t have a clear sense of what you are asking here.
.

is there a fast and light alternative to SLiM for automatic login, already available in antiX repository?

As Dave explained in another recent topic, you can opt to forgo use of a (xdm,SLiM,lightdm) display manager altogether.
I don’t recall the exact the exact launchstring syntax, but it would be something like “startx desktop-session openbox”

In the end I solved it in a fast, ignorant way, simply replacing SLiM provided by antiX repository with SLiM of Stretch.

is my solution valid or are there drawbacks?

One drawback is that you’re “off the reservation”, maybe running an assemblage that few others have tested to confirm those components//versions interoperate well.

[Forum Admin Dave]

You can look in /var/log/ at the xorg log and the slim log. There should also be a log in your home folder for xorg if you start things manually. If you want to try startx… run like this
startx /usr/local/bin/desktop-session rox-icewm
To get a normal antix type session.

Follow skidoo suggestions first. Also one more stupid sounding suggestion. When you turn the computer on just leave it for 5-10 minutes and see if the slim log in comes up. I have had it twice now after upgrading to testing in the last few days that this long wait makes it work. I have yet to figure out why other than slim is waiting for the x server to start excepting connections. I could get slim to come up sooner by doing service slim stop && service slim start but am not able to login. Running startx would not work (or rather would take 5min). And the very curious thing was trying lightdm as the login manager which comes up right away….

Computers are like air conditioners. They work fine until you start opening Windows. ~Author Unknown

[Forum Admin Dave]

ssh into the machine as root and run
apt-get purge lightdm gdm kdm
Which should get rid of the most common login managers and leave you with the default slim login manager (which is the press f1 option).

If that only gets you to a text login chances are slim is not instead or setup funny from installing the other login manager.
First Purge slim in case it has remaining buggered files
Apt-get purge slim
Then install
Apt-get -f install slim

Alternatively from the command line you could run
startx /usr/local/bin/desktop-session space-icewm
To get one of the default desktops.
From there you can select the one you want from the desktops menu and then drop space-icewm from the command or change space-icewm to the variant you would like.

Computers are like air conditioners. They work fine until you start opening Windows. ~Author Unknown

[Forum Admin dolphin_oracle]

is your greeter even installed? I suggest lightdm-gtk-greeter

the lightdm .conf files are just text files. copy and paste in the entries you want.

the “other desktops” in the icewm menu is built by desktop-session, an antiX exclusive. That isn’t’ really needed if you are trying to build a mate desktop. Its also independent from the lightdm configuration.

I suggest focusing on one problem at a time. building from scratch (or nearly scratch) can be fun, but change to many things at once can get confusing. I think you just have miss- or under-configured lightdm display manager. Fix that so that you can choose which window environment/desktop to use and I think you’ll find it easier going from there.

start with making sure the lightdm-gtk-greeter package is installed (and is the only greeter installed)

• This reply was modified 5 years, 1 month ago by dolphin_oracle.