![]() Doing this solved the very same issue for me a month ago, but since then, I've moved on from polybar. (It has one feature that I really like a lot, which is that you can select which screensavers to. You can also replace mate-screensaver with the original Xscreensaver, and in that case there is a GUI program called xscreensaver-demo for modifying the config file. Step 7 - Set up your xscreensaver preferences. /.xscreensaver might show up later, in which case you can edit it directly. Open Startup Applications and add a custom startup entry with no delay to run the command xscreensaver if you have multiple users you will need to do this for each user account. The problem is that some packages are still under python3.8 and not under 3.9. Step 5 - Set xscreensaver to start at user logon. It doesn't matter what the point release is, the libraries are still under /usr/lib/python3.9/site-packages regardless of whether it is 3.9.1 or 3.9.0. And python v3.9.1 is not the problem here, that has nothing to do with it. It starts to compile and when checking for dependencies it can't find xcbgen libraries, right? Since you are on python-3.9, doing this will rebuild xcb-proto against python3.9 rather than 3.8, thus providing the xcbgen libraries that polybar says are missing while compiling. That is the only thing that is failing while compiling polybar for you, I think. If you really need polybar, you could grab the PKGBUILD for xcb-proto and build it yourself. The xscreensaver installation process should update the PAM data (on Linux, by creating the file /etc/pam.d/xscreensaver for you, and on Solaris, by telling you what lines to add to the /etc/pam.conf file.) If the PAM configuration files do not know about xscreensaver, then you might be in a situation where xscreensaver will refuse to ever. ^^īesides, I realized I posted this topic in a wrong sub-forum though there's nothing like Apps & DEs as in Arch64, it would fit better into System Administration, I guess. It is a tool for editing the /. ![]() Hence I can't rebuild polybar from AUR anymore, because python v3.9.1 is necessary for this (very likely required by that mentioned "xcbgen" thingy, due to the build error) – which itself is currently still in testing even for Arch64!īut I don't mind and apply a plaster on that bleeding edge for now – as I know it's going to work again sooner or later. The xscreensaver-settings program is a graphical front-end for setting the parameters used by the xscreensaver (1) daemon. ![]() ![]() Contribute to Salamek/xscreensaver-config development by creating an account on GitHub. xscreensaver config file Python parser for. OT: Regarding patience – here's another one: Since yesterday my polybar is out of order, because since the last major update a couple of days ago, jsoncpp is to new for it. GitHub - Salamek/xscreensaver-config: Python parser for. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |