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.
Would you mind elaborating on what features are missing?
All features shipped in:
ccsm
compiz-bcop
compiz-plugins-main
compizconfig-python
libcompizconfig
plus extra plugins.
Attached is a pic of compiz running in MATE and the CCSM
As an aside in Mate mate-tweaks allows to easy switch the window manager, here choosing between marco, metacity and compiz, the formers with or whithout compositor.
The lifetime of the directory MUST be bound to the user being logged in. It MUST be created when the user first logs in and if the user fully logs out the directory MUST be removed. If the user logs in more than once he should get pointed to the same directory, and it is mandatory that the directory continues to exist from his first login to his last logout on the system, and not removed in between. Files in the directory MUST not survive reboot or a full logout/login cycle.
I just checked, both without and with a display manager (in runlevels 3 and 4, in Slackware parlance).
After a reboot there is no directory /dev/shm/didier.
It is created as soon as I log in as didier.
Its content is preserved after I log out.
Its content is preserved after a new log in.
It seems me that it is exactly the specified behavior.
Of course if you never reboot you'll have to clean the house yourself but this is a desktop specification, not a server one.
@Didier Spaier Thanks for the details, but that doesn't really help me understand the use cases that aren't possible with the older compiz.
Also I don't think compiz would need to be removed for someone to update it at slackbuilds.org. My understanding is that it would be fine as long as the info file contains REQUIRES="%README%" and the README explicitly explains that it conflicts with the compiz package included in the main tree. You can look at pkgconf for a example which conflicts with and replaces pkg-config in the main tree.
@Didier Spaier Thanks for the details, but that doesn't really help me understand the use cases that aren't possible with the older compiz.
I am not sure I can give a good response. I have been told that the new one is more accessible to visually impaired users using the Orca screen reader or a Braille device but am not able to elaborate on that right now.
I will just add that as a packages provider it's less work for me to maintain just one package
Well, I don't know what exactly is a "full log out".
Does it means that the user is no more recorded in /var/run/utmp? But not all apps write this file, and after having logged out and killed all processes owned by didier with "killall -u didier", "users" only output "root" but "grep didier /var/run/utmp" still matches.
In my understanding "fully log out" should practically mean that there is no remaining process owned by didier.
One could check that periodically in a cron job, that would then remove or propose to remove /dev/shm/didier and its content. However I think that would rather be the admin's duty to write it than done by something shipped in Slackware. I could be wrong of course, that's just an opinion and I am ready to hear other ones.
Last edited by Didier Spaier; 03-19-2018 at 09:22 AM.
Well, I don't know what exactly is a "full log out".
Does it means that the user is no more recorded in /var/run/utmp? But not all apps write this file, and after having logged out and killed all processes owned by didier with "killall -u didier", "users" only output "root" but "grep didier /var/run/utmp" still matches.
In my understanding "fully log out" should practically mean that there is no remaining process owned by didier.
One could check that periodically in a cron job, that would then remove or propose to remove /dev/shm/didier and its content. However I think that would rather be the admin's duty to write it than done by something shipped in Slackware. I could be wrong of course, that's just an opinion and I am ready to hear other ones.
Hoo Boy ...
That is a tough question to answer, let alone being a tough programming nut to crack
The XDG Base Directory Specification requirement that you and atelszewski posted is pretty clear ( It MUST be created when the user first logs in and if the user fully logs out the directory MUST be removed. )
But as you said, the hard part is what does 'fully logged out' really mean ?
ick.
-- kjh
Last edited by kjhambrick; 03-19-2018 at 11:57 AM.
Reason: default
The lifetime of the directory MUST be bound to the user being logged in. It MUST be created when the user first logs in and if the user fully logs out the directory MUST be removed. If the user logs in more than once he should get pointed to the same directory, and it is mandatory that the directory continues to exist from his first login to his last logout on the system, and not removed in between. Files in the directory MUST not survive reboot or a full logout/login cycle.
I think that part of the xdg specification is written to work specifically for one reason
I'm a bit ignorant. Would you mind elaborating on what features are missing?
My personal limited use case for compiz is to stop screen tearing with some wine games that have a broken native vsync when not using a window manager (Where I would use compton instead).
As Dider mentioned, he is using the 0.9 branch which does combine all of companion packages and extras into a single source. However Slackware is using the 0.8 branch which still splits all of the extra packages mentioned above into their own separate sources. Compiz alone isn't necessarily "missing" anything, it is just that the full suite of compiz packages make for a more robust experience. As far as the new 0.8.14 version of compiz, there hasn't been any ABI changes to the code so you can still use the older 0.8.8 with the newer packages if you want, but the newer version of compiz has better support for things like Mate, gtk3/metacity themes, emerald, and various bug fixes.
Also I have used both 0.9 and the 0.8 branches of compiz on 14.2 and in my experience 0.8 is still the more stable of the two, but YMMV if you wanted to try it. I will say that I do like that 0.9 combines everything into one package.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
