SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
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 :
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/
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, 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,
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".)
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
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.
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
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?
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.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.