LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Slackware (https://www.linuxquestions.org/questions/slackware-14/)
-   -   [ANN] xdm-slackware-theme 2019.0628 (https://www.linuxquestions.org/questions/slackware-14/%5Bann%5D-xdm-slackware-theme-2019-0628-a-4175656722/)

phenixia2003 07-02-2019 05:00 AM

[ANN] xdm-slackware-theme 2019.0628
 
3 Attachment(s)
Hello,

A new version of xdm-slackware-theme is available with many improvements and features.


Here are some screenshots :

Attachment 30826

Attachment 30827

Attachment 30828

Here are some videos :

Full documentation is available here.

You can get slackware package here (tested on 14.2 & -current). The source tarball and the slackbuild are available here.

If you upgrade from an earlier version (ex. 2018.1026), do not forget to install the following .new configuration files before restarting xdm, otherwise some features will not work properly :

Code:

Xbuttons_bar.conf.new
Xresources.new
Xsetup.conf.new

Cheers.


--
SeB

BigTig 07-03-2019 01:52 AM

Awesome! Thanks! The videos really helped.

phenixia2003 07-03-2019 02:09 AM

Hello,

Quote:

Originally Posted by BigTig (Post 6011418)
Awesome! Thanks! The videos really helped.

you're welcome.

let me know if you encounter any issues.

--
SeB

Gerard Lally 07-03-2019 02:34 AM

A great addition to Slackware. The Conky option is superb.

rworkman 07-03-2019 03:49 AM

This is indeed interesting. I took alienBOB's xdm theming from his livecd and put it on SBo, so maybe you can "claim" that build and integrate your stuff into that? https://slackbuilds.org/repository/1...are-xdm-theme/

phenixia2003 07-03-2019 07:53 AM

Hello,

Quote:

Originally Posted by rworkman (Post 6011446)
This is indeed interesting. I took alienBOB's xdm theming from his livecd and put it on SBo, so maybe you can "claim" that build and integrate your stuff into that? https://slackbuilds.org/repository/1...are-xdm-theme/

I don't think it is a good idea to put these themes in a same package. Since they don't have same name, I guess I can submit xdm-slackware-theme to slackbuilds.org. I'll think about that.

--
SeB

bamunds 07-04-2019 10:51 PM

Seb, you've been very active at development of these wonderful xdm slackware themes. I love the video introductions. You assisted me with a two monitor different size, two session configuration with 2018.1026 version. www.linuxquestions.org/questions/showthread.php?p=5969200#post5969200

Since it appears you've fixed the buttonbar on second screen issue, I'm wondering if I should removepkg and start from scratch again?
Cheers,

gus3 07-05-2019 12:42 AM

bamunds, please indulge me as I butt in, briefly.

This project seems to be quite the project for you. Do you have a file of notes outlining goals and methods, ideas and potential mistakes? If not, I highly recommend putting some notes together as a sort of "R&D repository." As you organize your thoughts, you'll discover areas of further research, preliminary tests to run (plus their results), and maybe even the point when you've taken enough notes to start working on the actual project.

(BTW, I call my file of notes "notes.txt". Not very imaginative, but it's very easy to type "vi notes.txt" or "nedit notes.txt".)

phenixia2003 07-05-2019 02:36 AM

Hello,

Quote:

Originally Posted by bamunds (Post 6012072)
Seb, you've been very active at development of these wonderful xdm slackware themes. I love the video introductions. You assisted me with a two monitor different size, two session configuration with 2018.1026 version. www.linuxquestions.org/questions/showthread.php?p=5969200#post5969200

yes, I remember well of that. Actually, it's one of the reason I developed this version.

Quote:

Originally Posted by bamunds (Post 6012072)
Since it appears you've fixed the buttonbar on second screen issue, I'm wondering if I should removepkg and start from scratch again?
Cheers,

Since you have manually changed some files, I suggest to do the following :
  • 1. Make backup of /etc/X11/xdm/slackware
  • 2. remove xdm-slackware-theme, then delete (or rename) /etc/X11/xdm/slackware
  • 3. install the xdm-slackware-theme-2019.0628-noarch-1_SeB.tgz
  • 4. edit /etc/X11/xdm/slackware/Xservers and uncomment the line below (to enable the secondary X server on :1) :

    Quote:

    #:1 local /usr/bin/X :1 vt8
  • 5. restart xdm (ie. pkill xdm). Note that sometimes, xdm might fails to restart correctly when Xservers file has changed: one of the sesssion might be unavailable. In this case, try to restart xdm 2 or 3 times. If that does not work, simply reboot your system.
  • 6. if you want to have different background on each X session, look at this video (maybe you already seen it), and/or read this.

Since the buttons-bar is now on top of screen by default, you should not encounter the issue you had with previous version.

However, on systems with two sessions and two monitor, if you have an nVidia video card and the proprietary driver in use, there's chance to encounter this issue.

Let me know if you encounter any other issue.

Hope this helps.

--
SeB

bamunds 07-05-2019 08:33 AM

Thanks again SeB. I'll follow the advice and report back later. Cheers

bamunds 09-01-2019 01:29 PM

Seb finally upgraded during the long weekend here in the USA and everything works as you described. Even conky and analog clock are working nicely. Thanks for setting the cairo to 1.0 interval in the extension.d conf file. I'm looking forward to the additional enhancements you see possible. It would be nice if PV considered this a standard package with the next release. Cheers, BrianA_MN

bamunds 10-19-2019 12:07 PM

SEB, I'm finding that my xserver is growing over time by 5 meg each time a session is started and terminated. I've set both servers for "DisplayManager._1.terminateServer: true" in Xresources. Since I primarily use server 1 it grows while _2 stays at the initial size. The Xresources file first commands are:
DisplayManager._2.terminateServer: true
DisplayManager._1.terminateServer: true

Then the X cursor theme and configs are executed.

Any suggestions on what to change or attempt next?

phenixia2003 10-19-2019 01:18 PM

Hello,

Quote:

Originally Posted by bamunds (Post 6048595)
SEB, I'm finding that my xserver is growing over time by 5 meg each time a session is started and terminated. I've set both servers for "DisplayManager._1.terminateServer: true" in Xresources. Since I primarily use server 1 it grows while _2 stays at the initial size. The Xresources file first commands are:
DisplayManager._2.terminateServer: true
DisplayManager._1.terminateServer: true

Then the X cursor theme and configs are executed.

Any suggestions on what to change or attempt next?

if you have 2 X servers, this should be _0 and _1, not _1 and _2. About memory leak, this might be related to xdm or xserver, not xdm-slackware-theme.

--
SeB

bamunds 10-19-2019 01:35 PM

SEB thanks. I don't know why I didn't realize that as I was pasting from Xresources to this thread. Sorry for the time waste. Cheers.

igadoter 10-20-2019 08:45 AM

Great job! Keep going. Yet another thing to love Slackware. Simplicity is just like breeze of fresh fragrant air.

igadoter 10-22-2019 09:32 AM

It does not work for me. When xdm starts there is warning message Warning setxdmbg failed to display /etc/X11/xdm/slackware/pixmaps/default-wallpaper.pixmap.

bamunds 10-22-2019 09:53 AM

Did you view all the videos? They are excellent in how to setup and begin using xdm-slackware-themes.
Are you setting up for one or two monitors? You'll have to provide more information to answer your somewhat vague error message. Cheers

igadoter 10-22-2019 10:18 AM

It seems that lack of feh program was missing dependency. Although I didn't notice in movies that feh is requirement. Yet I found it in configuration files so I started to suspect that the lack of feh is the source of problem. I built feh from slackbuild script - and now background is being displayed. Yet it still not clear why I need feh.

Edit: It just came to me. Maybe now background is displayed by feh. I mean in presence of feh - it is used to display background, if feh is absent - setxdmbg is used.

phenixia2003 10-22-2019 10:54 AM

1 Attachment(s)
Hello,

Quote:

Originally Posted by igadoter (Post 6049586)
It does not work for me. When xdm starts there is warning message Warning setxdmbg failed to display /etc/X11/xdm/slackware/pixmaps/default-wallpaper.pixmap.

Well, I reproduced that issue. When feh is not installed, setxdmbg uses the command 'display' (from imagemagick) to display the image on the root window. Unfortunately 'display' returns 1 (even when the image is correctly displayed) which is interpreted as an error by setxdmbg which automatically set the root window to black and print that error message.

The easiest way to fix this, is to install feh (requires imlib2). Note that feh is a requirement if you consider using a compositor like compton.

Otherwise, you can apply, as root, the attached patch as below :
Code:

$ cd /usr/libexec/setxdmbg
$ patch -p0<setxdmbg-consume-display-exit-code.patch.txt

P.S: I will submit a new version with this fix to SBo, asap.

--
SeB

igadoter 10-22-2019 11:28 AM

Thanks for reply. I am now trying to set up all the candies - clock and conky. I just have built compton for cairo-clock - but I understand that compton needs to be started before xdm screen appears, so how to set this?

phenixia2003 10-22-2019 12:29 PM

Hello,

Quote:

Originally Posted by igadoter (Post 6049626)
Thanks for reply. I am now trying to set up all the candies - clock and conky. I just have built compton for cairo-clock - but I understand that compton needs to be started before xdm screen appears, so how to set this?

compton is automatically started by /etc/X11/xdm/slackware/Xsetup when : compton is installed, the property WITH_COMPTON (in /etc/X11/xdm/slackware/Xsetup.conf) is set to on (or 1 or yes or true), and feh is installed.

for more about Xsetup configuration, read this (or type 'man Xsetup.conf'). If you want to setup multiple XDM logins (with multiple Xsetup configurations), read this.

--
SeB

bamunds 11-09-2019 04:06 PM

SeB, sbotools caught me off guards when it wanted to update xdm-slackware-theme to 2019.1023. Thanks for the patch. Any special steps to take when upgrading to the latest version from 2019.0628? Maybe the title of this thread could be updated also? Cheers, Brian

phenixia2003 11-10-2019 03:58 AM

[ANN] xdm-slackware-theme
 
Hello,

Quote:

Originally Posted by bamunds (Post 6055969)
Thanks for the patch.

You're welcome.

Quote:

Originally Posted by bamunds (Post 6055969)
Any special steps to take when upgrading to the latest version from 2019.0628?

No. I didn't make change to the configuration files. If you have changed some of them, there must be .new files in /etc/X11/xdm/slackware and/or /etc/X11/xdm/slackware/extensions.d. You can ignore (or delete) them.

--
SeB

bamunds 11-10-2019 02:41 PM

Done and everything is working without issues. Yes there were .new files which I removed and left my original configs in place. Cheers again. BrianA_MN

GazL 11-12-2019 03:12 PM

What do you think to the idea of adopting a dedicated /etc/X11/xdm/themes/ directory to drop themes in? IMO having the extra directory level as a standardised location for theme directories will make having multiple themes a little tidier and won't clutter the main /etc/X11/xdm directory.

full disclosure:
I've already been doing this with my own theme, so I have a vested interest here. I start it with:
/usr/X11R6/bin/xdm -config "/etc/X11/xdm/themes/$xdm_theme/xdm-config" -nodaemon

phenixia2003 11-13-2019 03:44 AM

1 Attachment(s)
Quote:

Originally Posted by GazL (Post 6056921)
What do you think to the idea of adopting a dedicated /etc/X11/xdm/themes/ directory to drop themes in? IMO having the extra directory level as a standardised location for theme directories will make having multiple themes a little tidier and won't clutter the main /etc/X11/xdm directory.

Yes that's good idea. This only requires small changes to xdm-slackware-theme. I will add this to my todo-list.

Quote:

Originally Posted by GazL (Post 6056921)
full disclosure:
I've already been doing this with my own theme, so I have a vested interest here. I start it with:
/usr/X11R6/bin/xdm -config "/etc/X11/xdm/themes/$xdm_theme/xdm-config" -nodaemon

This requires to change /etc/rc.d/rc.4, which I want to avoid.

I prefer the way xdm-slackware-theme works: replacing the original /etc/X11/xdm/xdm-config file (saved beforehand) by a symlink which points the xdm-config file of selected theme.

This symlink can be manually set by user, or with a simple TUI, which could looks like this:

Attachment 31830

--
SeB

GazL 11-13-2019 04:24 AM

Quote:

Originally Posted by phenixia2003 (Post 6057114)
Yes that's good idea. This only requires small changes to xdm-slackware-theme. I will add this to my todo-list.

Great. Thanks SeB. :)


Quote:

Originally Posted by phenixia2003 (Post 6057114)
This requires to change /etc/rc.d/rc.4, which I want to avoid.

I prefer the way xdm-slackware-theme works: replacing the original /etc/X11/xdm/xdm-config file (saved beforehand) by a symlink which points the xdm-config file of selected theme.

This symlink can be manually set by user, or with a simple TUI, which could looks like this:

Attachment 31830

--
SeB

Yep, no problem. Current supports a rc.4.local, which is what I use, but I wasn't suggesting messing with the rc files in your package (it was just an example showing the theme subdir in action). I agree, your symlink solution is likely to be the better solution for most folk.

bamunds 01-17-2020 08:28 PM

Update version available for 2020.0101? What were the fixes or upgrades? Cheers, BrianA_MN

phenixia2003 01-18-2020 03:30 AM

Hello,

Quote:

Originally Posted by bamunds (Post 6079807)
Update version available for 2020.0101? What were the fixes or upgrades? Cheers, BrianA_MN

This version fixes an issue with imagemagick 7 (comes with -current). You don't need to upgrade to 2020.0101 unless you're using -current, or if you have upgraded imagemagick to 7 on -14.2.

Since this fix does not break xdm-slackware-theme on 14.2 with imagemagick 6, I chose to publish it instead of waiting for 15.0.

--
SeB

bamunds 01-19-2020 01:40 PM

Thanks for the update. Just for grins, I applied the latest under 14.2 and all is well still.

In fact xdm-slackware-themes is better than SDDM 0.18.0. SDDM will start only a single session on VT7 and only on invoking "switch user" from KDM or XFCE do you get a session on VT8. The only nice feature of SDDM is that of avatars and iconified buttons for shutdown, reboot, suspend, switch to another user which has no avatar. But I have not seen SDDM with conky and clock like xdm-slackware-themes. I would guess that all the iconified buttons could be created with XDM, but having them in the upper corner is sufficient for my work. The avatar is cool, only because my wife isn't using the Linux machine daily and forgets what to do when looking at username: (she is so use to the Win10 login, Win10 needed because our financial investment firm refuses to support Linux and builds everything on Win10).

Just as a curiosity, have you ever considered adding avatars to the XDM Login? Cheers, BrianA_MN

phenixia2003 01-20-2020 01:00 PM

Hello,

Quote:

Originally Posted by bamunds (Post 6080443)
Thanks for the update. Just for grins, I applied the latest under 14.2 and all is well still.

In fact xdm-slackware-themes is better than SDDM 0.18.0. SDDM will start only a single session on VT7 and only on invoking "switch user" from KDM or XFCE do you get a session on VT8. The only nice feature of SDDM is that of avatars and iconified buttons for shutdown, reboot, suspend, switch to another user which has no avatar. But I have not seen SDDM with conky and clock like xdm-slackware-themes. I would guess that all the iconified buttons could be created with XDM, but having them in the upper corner is sufficient for my work. The avatar is cool, only because my wife isn't using the Linux machine daily and forgets what to do when looking at username: (she is so use to the Win10 login, Win10 needed because our financial investment firm refuses to support Linux and builds everything on Win10).

Just as a curiosity, have you ever considered adding avatars to the XDM Login?

yes, but this requires too much work. sorry.

I also had the idea to add a sub-menu "users" in the main menu to allows to select a user, but this requires to be able to communicate the name of the selected user to xdm, and there is, unfortunately, no real way for that (unless maybe, by sending fake keyboard events ... but, once again, this requires too much work).

--
SeB

bamunds 01-20-2020 08:53 PM

Quote:

Originally Posted by phenixia2003 (Post 6080791)
Hello,

yes, but this requires too much work. sorry.

SeB

Totally understand. xdm-slackware-themes is great the way it is. Thank you for the work that you do.
Cheers, BrianA_MN

bamunds 05-23-2020 05:22 PM

@phenixia2003 On what errors does xdm-slackware-theme write to xdm-xsession? Is there a reason you don't use .xsession-errors? Cheers, BrianA_MN

phenixia2003 05-24-2020 04:03 AM

Hello,

Quote:

Originally Posted by bamunds (Post 6126444)
@phenixia2003 On what errors does xdm-slackware-theme write to xdm-xsession? Is there a reason you don't use .xsession-errors? Cheers, BrianA_MN

The file in which xsession errors are redirected is specified by property XSESSION_ERRFILE in /etc/X11/xdm/slackware/Xsession.conf.

By default, this should be in ~/.xsession-errors._0 in case of X server :0, ~/.xsession-errors._1 in case of X server :1, and so on.

This is to ensure that errors from different X servers are not mixed in one single file. But, if you don't like that / don't use multiple X server, feel free to change XSESSION_ERRFILE.


--
SeB


All times are GMT -5. The time now is 10:55 AM.