[SOLVED] So, there is PulseAudio... How about to begin investigating adding LinuxPAM to Slackware too?
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.
Well, now I'm baffled as to why it all seems to work okay for me!
It isn't really a bug. Gnome3 date/time functionality relied on a DBus service delivered by systemd. So systemd is missing, this DBus service is missing aswell. It is one of the purposes of systemd: create a cross-distribution layer desktops can rely on. timedated is a such layer because Date/Time control is a bit different in different distributions. And KDE seems to switch to it aswell and not to maintain hacks for diffirent distributions themselves.
The Paul Bunyan statue is over an hour's drive away in Bemidji, but I took a few hours off yesterday afternoon and headed into the snowy woods nearby. I didn't find Minnesota's most famous lumberjack there either, but here's a rare selfie anyway.
Yow! These pulseaudio/PAM threads are taking their toll! (Nervously ensures there are no photos on the web that point to self.)
The Paul Bunyan statue is over an hour's drive away in Bemidji, but I took a few hours off yesterday afternoon and headed into the snowy woods nearby. I didn't find Minnesota's most famous lumberjack there either, but here's a rare selfie anyway.
You look great Pat!
I don't think I had a mental image of you, but this would have been a good candidate!
There is a bug in KDE. There was an assumption, it is because of missing PAM. I just said there was a similar problem in Gnome because of missing systemd just to explain exactly what the problem is and why this slack-timedate thing works.
There is a bug in KDE. There was an assumption, it is because of missing PAM. I just said there was a similar problem in Gnome because of missing systemd just to explain exactly what the problem is and why this slack-timedate thing works.
My apologies, it appears that I was too terse.
What is the use case for a dbus service that provides date/time functionality? (No matter if such functionality is delivered via systemd or otherwise.)
Being required now to properly setting date and time on KDE?
There were ways to that prior to dbus and systemd. What is the use case that requires that both dbus and systemd are present? Perhaps this is a better question: "What problem was solved by moving the setting of the system date and time to a systemd service that communicates via dbus?"
There were ways to that prior to dbus and systemd. What is the use case that requires that both dbus and systemd are present? Perhaps this is a better question: "What problem was solved by moving the setting of the system date and time to a systemd service that communicates via dbus?"
As said there are some differences how these settings are handled in different distributions. I don't know anymore exactly, but there were differences how /etc/localtime worked or where are timezone settings saved or stuff like this. systemd created this dbus layer to handle the date/time settings everywhere the same. And desktops got use of it to avoid doing the same or solving these problems again.
Location: Geneva - Switzerland ( Bordeaux - France / Montreal - QC - Canada)
Distribution: Slackware 14.2 - 32/64bit
Posts: 609
Rep:
Quote:
Originally Posted by belka.ew
As said there are some differences how these settings are handled in different distributions. I don't know anymore exactly, but there were differences how /etc/localtime worked or where are timezone settings saved or stuff like this. systemd created this dbus layer to handle the date/time settings everywhere the same. And desktops got use of it to avoid doing the same or solving these problems again.
In short (as many things): to provide a standard and ease portability.
As said there are some differences how these settings are handled in different distributions. I don't know anymore exactly, but there were differences how /etc/localtime worked or where are timezone settings saved or stuff like this. systemd created this dbus layer to handle the date/time settings everywhere the same. And desktops got use of it to avoid doing the same or solving these problems again.
Thank you for the answer. (Honest!)
There's not much that I can say in response to the people who thought that was a spiffy idea other than...
EDIT: When all you have is a hammer, every problem looks like a nail. When all you have is systemd, every problem looks like....
Last edited by Richard Cranium; 01-24-2016 at 06:56 PM.
Reason: Maybe people would wonder why my head was banging against the wall.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
