Search Results for 'lightdm desktop-session'

[Member Xaver]

So far I have not thought about getting rid of dbus too. Inspired by this thread I have done some research.
Dbus seems to be a severe security risk: https://vulmon.com/searchpage?q=dbus&sortby=byriskscore

Therefore I have checked, if my antiX-21-runit-sid (no elogind, polkitd policykit-1 or gvfs) would run without dbus too.
[compare: https://www.antixforum.com/forums/topic/antix-21-net-runit-sid_x64-with-seatd-3-problems-encoutered/ ]

First step was do put the runit debus service down. But this did not change much. dbus-daemon and dbus-launch were still running after reboot. Then I simulated a purge of dbus-daemon and dbus-x11:

# apt purge -s dbus-daemon dbus-x11

This would deinstall all xorg and most of my system – obviously not a good idea.

dbus-daemon and dbus-launch are running independently from the runit dbus service. How can I stop them.?
I have used a quite brutal method: disable them by changing their names:

renamed in /usr/bin/
dbus-launch –> dbus-launch_X
dbus-run-session –> dbus-run-session_X
dbusdaemon –> dbusdaemon_X 
then:
# apt-mark hold dbus dbus-daemon dbus-x11

Now no dbus is running, but all the dependencies to it are fufilled. Most software can be installed.
If needed, I can easily switch back to dbus.

What are the limitations?
Connman had to be replaced by Ceni. XFCE4-panel would not start (too bad – nice panel apps). Plank does work, but cannot be configured. Concerning the openbox desktop these are all the limitations which I have discovered so far.
My desktop consists of openbox, tint2, rofi, wmdrawer (a good and lighter replacement for plank) and spacefm (gtk2-version) with udevil.
Jgmenu does work fine too, but I prefer the openbox menu configured with obmenu2.
Login only works with .xinitrc – lxdm does not work.

Poweroff/Reboot with desktop-session-exit does not work regularly. I have to logout first and then shut down:

$ bash -c "openbox --exit && sudo poweroff"

Since polkitd is absent, there are dummies needed to fulfill policykit dependencies.
For that I have created and installed two dummies: policykit-1_99.9.9-9dummy and libpolkit-qt5-1-1_99.9.9-9dummy.
Most application can be installed now, even KDE stuff. But k3b cannot be installed, because it needs libsystemd0 and udisks2, which needs dbus.

Iso snapshot and persist do not show any problems.
Firefox-ESR and even Falkon are working fine and seem to be faster than on my antix-sysv-sid with dbus.
The whole system is a fully functional antiX and semms to be very fast and stable.

Only a few questions are still unresolved:

(1) Is there a more elegant way to keep dbus-daemon and dbus-launch from running than by renaming them?

(2) If I boot an iso-snapshot from usb, there is no network connection. I have to run Ceni in order to connect. Which setting have I missed?

(3) @ anticapitalista
You have stated, that LXDM would work without dbus. I get an error message:
[“Warning: dbus disabled by local settings”]
What is your trick to make LXDM work?

(4) lightdm gave me a hard time to deinstall it (pre-install script error). ‘dpkg-reconfigure lxdm’ still lists lightdm as an option. Where is this stored?

(5) Running from usb I sometimes notice high cpu load, when the system should be idle. The cause: lxtask indicates multiple instances of udevd. A restart of udevd service and then starting udevd again brings the system back to normal.
Research in the web clarfies, that this is a general udevd problem.
Is there any general cure?

• This reply was modified 8 months, 4 weeks ago by Xaver.
• This reply was modified 8 months, 4 weeks ago by Xaver.
• This reply was modified 8 months, 4 weeks ago by Xaver.

[Member Xecure]

Hi, @locosporlinux

Could you share with us what version of antiX (core, base or full) are you starting with to build the LXDE respin? Are you replacing slimski with some other Login Manager? Are you using desktop-session to start the custom LXDE spin or are you running it with the default lxde-session only?

Are you replacing elogind with consolekit (as the message may be implying) and require libpolkit-gobject-consolekit-1-0?

EDIT: Are you using lightdm? If (using lightdm-greeter), did you edit /etc/pam.d/lightdm-greeter to use elogind (as described here)? lightdm in Debian is ready for systemd’s logind, and needs some changes to use elogind instead.

Regards.

• This reply was modified 1 year, 5 months ago by Xecure.

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

[Member Xecure]

Search for topics like “antix core fluxbox” “antix core icewm”, etc.

Some pointers:
desktop-session-antix is the package that manages the antiX session and makes it work like a desktop environment.
desktop-menu-antix is the package that generates the Applications menus automatically every time you install a new package.
desktop-defaults-antix is the package needed for setting preferred applications and making it easy to change default edito, browser, file manager, etc.
desktop-defaults-base-antix bring the general program default configurations.
antix-goodies brings lots of antiX scripts that make life easier.
desktop-defaults-jwm-antix is the package with the antiX defaults
papirus-antix/papirus-mini-antix brings the default icon theme in antiX 19/21

Those are the basics. There are some dependencies that you may need to figure out (read the topics that mention this), and experiment and try things out.

Note: Using lightdm, you may have to edit the exec options in /usr/share/xsessions so the window managers launch using desktop-session.

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

[Member rej]

Thanks so much for your help!

OK. Does the command work if you run it manually in terminal?

•No [does not restore the wallpaper]

Do other items in the startup file run?

• No none of them run.

A few things
Maybe post the contents of /home/rj/.icewm/startup; you may have a malformed line prior to the nitrogen one.

•

#!/bin/bash
#Turn on xscreensaver
xscreensaver &
# Auto suspend after 15 min
xautolock -time 10 -locker "sudo /usr/sbin/pm-suspend" -detectsleep &
sleep 1 &&
nitrogen --restore &

Make sure lightdm is running icewm-session not icewm. Otherwise the startup file is not even called.

• Not sure where that is –

[usr-share-xsessions] icewm-session (File)?

[Desktop Entry]
Encoding=UTF-8
Type=XSession
Name=IceWM Session
Name[da]=IceWM-session
GenericName=Window Manager
GenericName[da]=Vindueshåndtering
GenericName[fr]=Gestionnaire de Fenêtres
GenericName[pt]=Gestor de Janelas
Comment=This session logs you into IceWM
Comment[az]=Bu iclas sizi IceWM'a daxil edəcək
Comment[be]=Гэтая сэсыя завядзе вас у IceWM
Comment[ca]=Aquesta sessió entra en IceWM
Comment[cs]=Toto sezení vás přihlásí do IceWM
Comment[cy]=Mae'r sesiwn hwn yn eich mewngofnodi i IceWM
Comment[da]=Denne session logger dig ind på IceWM
Comment[de]=Diese Sitzung meldet Sie an IceWM an
Comment[el]=Αυτή η συνεδρία σας εισάγει στο IceWM
Comment[es]=Con esta sesión accede a IceWM
Comment[fi]=Tämä istunto kirjaa sisään IceWMen
Comment[fr]=Cette session vous connectera dans IceWM
Comment[he]=תצורת הפעלה זו מחברת אותך ל IceWM
Comment[hi]=यह सत्र गनोम में लॉगिन होगा
Comment[hu]=Ez a munkamenet a IceWM-ba jelentkeztet be
Comment[it]=Sessione di lavoro con IceWM
Comment[ja]=IceWM セッションにログインします
Comment[ko]=IceWM세션으로 로그인합니다
Comment[ms]=Sesi ini akan log anda  ke IceWM
Comment[nl]=Deze sessie meldt u aan bij IceWM
Comment[nn]=Denne økta loggar på IceWM
Comment[no]=Denne sesjonen logger deg inn til IceWM
Comment[pl]=Sesja logowania do IceWM
Comment[pt]=Esta sessão inicia-o no IceWM
Comment[pt_BR]=Logar no ambiente IceWM
Comment[ro]=Această sesiune vă va loga în IceWM
Comment[sk]=Toto sedenie vás prihlási do prostredia IceWM
Comment[sl]=Ta seja vas prijavi v IceWM
Comment[sq]=Kjo seancë do t'ju fusë në IceWM
Comment[sr@Latn]=Ova sesija vas prijavljuje na IceWM
Comment[sr]=Ова сесија вас пријављује на IceWM
Comment[sv]=Denna session loggar in dig i IceWM
Comment[tr]=Bu oturum ile IceWM'a giriş yaparsınız
Comment[uk]=Сеанс роботи в середовищі IceWM
Comment[vi]=Session này cho bạn đăng nhập vào IceWM
Comment[zh_CN]=此会话使您登录到 IceWM
Comment[zh_TW]=選取這個作業階段後會進入 IceWM 環境
Icon=icewm
TryExec=/usr/bin/icewm-session
Exec=icewm-session
NoDisplay=false
Hidden=false
Categories=WindowManager;Application;System;
StartupNotify=false
X-GNOME-Autostart-Notify=false
X-GNOME-Autostart-Phase=WindowManager
X-GNOME-Provides=windowmanager
X-GNOME-WMName=icewm
DesktopNames=ICEWM
X-LightDM-DesktopName=icewm

[Window Manager]
Name=icewm
SessionManaged=true
StartupNotification=false

If I recall correctly the startup file will need to have execute permissions. Make sure it does and/or try with execute permissions if it does not have them.

• It looks as though it has executable permissions.

Any particular feature in nitrogen vs the default wallpaper app that you are looking for? Otherwise you could add desktop-session-wallpaper & to the icewm startup file to use the default one.

•Using LightDM, the wallpaper option in the control center doesn’t function (black or “debian” background). I also prefer Nitrogen, because it has many features and is fast.

• This reply was modified 1 year, 10 months ago by rej.

Attachments:

1. 

   Startup-permissions.png
   

2. 

   Startup-Properties.png
   

3. 

   usr-share-xsessions-icewm-session.desktop.png
   

[Forum Admin Dave]

OK. Does the command work if you run it manually in terminal?
Do other items in the startup file run?

A few things
Maybe post the contents of /home/rj/.icewm/startup; you may have a malformed line prior to the nitrogen one.
Make sure lightdm is running icewm-session not icewm. Otherwise the startup file is not even called.
If I recall correctly the startup file will need to have execute permissions. Make sure it does and/or try with execute permissions if it does not have them.

Any particular feature in nitrogen vs the default wallpaper app that you are looking for? Otherwise you could add desktop-session-wallpaper & to the icewm startup file to use the default one.

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

[Member Xecure]

Hello, ricewithpig.
You said

ricewithpig wrote:

change wallpaper and session manager background

Does this mean you installed a different session manager (e.g. lightdm) or that you changed the slim background from the control centre?
I know that changing the login manager from slim to lightdm has brought problems launching the desktop-session program designed specifically for antiX and slim, so it is not strange if you are now experiencing problems with startup programs.
Could you let us know if you also changed the login manager? Or maybe you have selected some “minimal” desktop session option (like minimal-icewm) which disables all extra startup functions?

We will try to help based on the answers to these questions.

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

[Member seaken64]

Adding IceWM to antiX-19.3 CORE

In my continuing effort to learn more about how antiX works behind the scenes I am attempting to add the IceWM Window Manager to antiX CORE. I have started with a successful installation of antiX-19.3 CORE using the cli-installer. After the installation I logged in as root and ran the update and dist-upgrade routines. I tested the system from the console and everything is working fine in text mode only.

My next goal is to add the X window system and then add IceWM as my “GUI”. I do not want to add a Desktop Environment system such as Xfce or Mate. My goal is to learn more about how to setup the IceWM Window Manager to mimic what antiX BASE already has setup by default.

It would be easier to just install antiX BASE. But this is a learning exercise. I am hoping to learn how to setup IceWM from scratch, but using the antiX framework that has already been created for the BASE system. I have added IceWM to my regular Debian installs and I am always disappointed in how it looks and how the menus are setup. I like the antiX implementation of IceWM and I want to learn how it is done.

I have watched all of the videos from Dolphin_Oracle on adding an X windows system to antiX CORE. Unfortunately he does not specifically mention how to add IceWM, but instead shows how to add Xfce and KDE. There are quite a few threads on the forum about adding a WM or DE to the antiX CORE system. I have read them all and have tried to follow along and imitate the steps each user has taken to achieve their new “spin” on antiX. Brian Masnick also had a nice blog entry on how to setup Xfce on CORE using the SID repos. I have attempted to follow his instructions but I am not interested in Xfce. I want IceWM.

I am still working through some forum message threads and they have been helpful as I learn. But I am still hitting some roadblocks. Here is what I have accomplished so far and what I am missing.

I modified D_O’s apt install command string to try to install IceWM instead of Xfce. I do not want a Desktop Manager/Login Manager like Slim or LightDM, etc. I would like to have it setup to use “startx” to start up IceWM. Here’s is my first attempt at installing the missing packages:

apt-get install xserver-xorg x11-xserver-utils xfonts-base x11-utils icewm icewm-common

I rebooted (as root) and tried “startx” but it didn’t work. I added the xorg package and tried again. After reboot (as root) I tried “startx” again, it worked! I was now in IceWM. The menu was sparse and there were no Applications. But there was a “Terminal” entry. I clicked on that and it launched the xterm. I was able to launch mc, antiX-cli-cc, and cli-aptiX.

So, at this point I have a plain vanilla IceWM and no applications or anything resembling the “antiX” setup. So I started looking around to see if I could add the antiX stuff. I used cli-aptiX and added the following packages:

icewm-base-themes-antix icewm-icons-papirus-antix icewmcc rox-filer roxterm-common roxterm-gtk2 spacefm spacefm-common smbclient cifs-utils connectshares-antix control-centre-antix menu-icewm-antix menu-manager-antix xdg-utils desktop-session-antix desktop-defaults-base-antix

I have logged in as my user and I have the same plain IceWM as I did in root. I was able to change the “theme”. But the menu has not changed. There are no Applications. And I created a “startup” file in ~/.icewm/startup but it is not being used. I made an entry to change the default resolution using xrandr but it does not work. I do this on all of my antiX systems and it always works. But it appears that this IceWM is not reading the ~/.icewm/startup file.

How do I find out where IceWM is looking for the startup file and preferences? If it is looking somewhere else, how do I set it to look in my ~/.icewm folder? Did I make a mistake by using root to install? Should I have installed IceWM using my user?

The Control Centre comes on screen but is missing most of the tools and when I tried using the change Date&Time tool it failed. SpaceFM and Rox-filer are working. ROXterm also works. Connectshares fails to connect to my share. But I can use the mount command from the command line to connect to my share.

When I ran menu manager it seems to work. But the menu does not change. When installing from apt-get I do get the ‘setting up IceWM menu’ (not sure of the exact wording) and it completes with no error. I can see the menu-applications file in /usr/share/desktop-menu/.icewm/menu-applications. And it does seem to be the current menu generated and has all the applications. But it does not show on the main IceWM menu.

How do I get my main IceWM menu populated with my apps? I seem to be missing some script that modifies the IceWM menu file in my ~/.icewm folder.

I’m stuck. Thank you for any tips you can share to help me get unstuck.
Seaken64

[Forum Admin Dave]

Ah yes, I knew there was a reason to start avoiding ~/ in favour of $HOME.
I do not recall exactly the reason for the alteration to minimal- to min-. I think it came around with fixing menu duplication for alternate desktops. While correcting the menu duplication it made sense/was requested to expand from min- to minimal- for clarification. This was to better work with /usr/share/xsessions/ and using other login managers (lightdm) which would need desktop-session specified on the exec line in the various .desktop files. It should be easy enough to add min- back to desktop-session to account for backward compatibility.

Edit:
As a note the min- options were added as a disable everything in case all the started options (or one bad option / bug) are too much for your system so you can disable them and return back to the normal/rox-/space- option.

• This reply was modified 2 years, 5 months ago by Dave.

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

[Member Xecure]

No need to import from DVD to get the pinboard.
Open ~/.icewm/startup (you can get there navigating or from Control centre > Desktop > Edit IceWM Settings)
Add this line if you want the rox pinboard:
rox --pinboard=antiX-icewm &

or add this line if you want spacefm to control the desktop:
spacefm --desktop &

If after relogging in it doesn’t launch, it means that you need to edit the icewm.desktop in /usr/share/xsessions so that TryExec says:
TryExec=icewm-session

I am trying to avoid lightdm until I fully understand how desktop-session-antix works, so I cannot help with that right now.
For your case, if you keep experiencing other strange things apart from this, try reinstalling and see if this also happens in vanilla antiX.

By the way, did this also happen in antiX live (DVD) session?

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

[Member Xecure]

The problem lies here:

Red_Fir wrote:

Installed LightDM

Changing from slim to lightdm has given problems to many, including myself. You will have to check if you have to replace the instructions for the session files in /usr/share/xsessions.

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

[Member Xecure]

No worries. You are not using slim, but light-dm, so you don’t need to worry.

If you experience any problem loging in, you may have to look at this thread:
https://www.antixforum.com/forums/topic/trying-to-get-lightdm-to-run-desktop-session-icewm/

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

[Member Xecure]

SliM is very integrated with antiX. With the original slim login manager, all desktop-session options work when launched, but ither login managers don’t. You must have noticed that you no longer have a volume icon in the toolbar (that was managed by antiX’s desktop session). This desktop session even manages the wallpaper, so what you are experiencing is a non working wallpaper.

Fortunetly there is a solution.
You just need to edit the icewm-session file in /usr/share/xsession to launch antiX desktop session
See this answer:

Dave wrote:

I am not sure anymore; it has been a while since I looked. I say this as lightdm is supposed to do session management in a way, which is what desktop-session is trying to do as well.
Perhaps the quickest and easiest way is to make a bunch of files in /usr/share/xsessions similar to what is there but one for each antiX session. In the newly made files you could put on the exec line desktop-session rox-icewm. For example using above.

[code]

[Desktop Entry]
Name=DS Rox-IceWM
Comment=Rox and Icewm with desktop-session
Exec=desktop-session rox-icewm
Terminal=false
TryExec=desktop-session rox-icewm
Type=Application

[X-Window Manager]
SessionManaged=true
[/code]

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

[Forum Admin Dave]

BobC wrote:

I’m no expert, but it looks like the problem is in /usr/local/lib/desktop-session/desktop-session-update-wm-menus, in the 2nd grep line below, IceWM lines get removed. If I remove that line, I get some duplications, which I recall happening at one point, and I suspect that the fix for that wasn’t quite right.

raw_wm_list() {
    grep -h ^Name= $xs_dir/*.desktop \
        | sed -r -e 's/^Name=//' -e 's/ (desktop|session)$//i' -e 's/ +/_/g' \
        | grep -v "IceWM" \
        | sort -f  
}

PS: and yes, anti’s fix as root did get it back to normal
apt-get install --reinstall desktop-session-antix

Indeed you are correct with this section of code filtering out IceWM. It used to be that there where duplicate menu entries. This was caused by the existence of two .desktop files for IceWM in the /usr/share/xsessions directory. One was named icewm.desktop another icewm-session.desktop. In the icewm.desktop file the line was set to Name=icewm, whereas in the icewm-session.desktop file the line was set to Name=IceWM. So filtering the one out fixed it. Could you make a tarball of your /usr/share/xsessions directory to look at? I noticed in another lightdm thread that you also said that the extra “session” .desktop files where also there.

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

[Moderator BobC]

Dave, This happened again to me, but I noticed it after I installed lightdm, not sure if it was happening before that or not. It was writing the files, but when I turn on verbose, I see that its writing the file wrong. It refuses to run as the user.

Dave wrote:

For others who may see this issue could they try running as root (note that the force option is a double dash)
/usr/local/lib/desktop-session/desktop-session-update-wm-menus –force
Before reinstalling desktop-session-antix to see if this works or what errors may appear?

If no errors show and the menu is still not fixed after reloading the window manager/menu could you try the same command but run as the regular user?

[Forum Admin Dave]

I am not sure anymore; it has been a while since I looked. I say this as lightdm is supposed to do session management in a way, which is what desktop-session is trying to do as well.
Perhaps the quickest and easiest way is to make a bunch of files in /usr/share/xsessions similar to what is there but one for each antiX session. In the newly made files you could put on the exec line desktop-session rox-icewm. For example using above.

[code]

[Desktop Entry]
Name=DS Rox-IceWM
Comment=Rox and Icewm with desktop-session
Exec=desktop-session rox-icewm
Terminal=false
TryExec=desktop-session rox-icewm
Type=Application

[X-Window Manager]
SessionManaged=true
[/code]

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