diff options
Diffstat (limited to 'zarb-ml/mageia-dev/2011-August/007588.html')
-rw-r--r-- | zarb-ml/mageia-dev/2011-August/007588.html | 131 |
1 files changed, 131 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/2011-August/007588.html b/zarb-ml/mageia-dev/2011-August/007588.html new file mode 100644 index 000000000..977d7319b --- /dev/null +++ b/zarb-ml/mageia-dev/2011-August/007588.html @@ -0,0 +1,131 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <TITLE> [Mageia-dev] systemd + udev 173 + gnome-shell + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20systemd%20%2B%20udev%20173%20%2B%20gnome-shell&In-Reply-To=%3C4E5900D1.40602%40colin.guthr.ie%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="007573.html"> + <LINK REL="Next" HREF="007592.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] systemd + udev 173 + gnome-shell</H1> + <B>Colin Guthrie</B> + <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20systemd%20%2B%20udev%20173%20%2B%20gnome-shell&In-Reply-To=%3C4E5900D1.40602%40colin.guthr.ie%3E" + TITLE="[Mageia-dev] systemd + udev 173 + gnome-shell">mageia at colin.guthr.ie + </A><BR> + <I>Sat Aug 27 16:36:01 CEST 2011</I> + <P><UL> + <LI>Previous message: <A HREF="007573.html">[Mageia-dev] systemd + udev 173 + gnome-shell +</A></li> + <LI>Next message: <A HREF="007592.html">[Mageia-dev] Handling GNOME 2.x Broken Dependencies +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#7588">[ date ]</a> + <a href="thread.html#7588">[ thread ]</a> + <a href="subject.html#7588">[ subject ]</a> + <a href="author.html#7588">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>'Twas brillig, and Colin Guthrie at 27/08/11 00:46 did gyre and gimble: +><i> Hi, +</I>><i> +</I>><i> OK, so this combo is currently broken! +</I>><i> +</I>><i> Here is the explanation. +</I>><i> +</I>><i> With udev 172, udev-acl would apply ACLs to devices (such as the DRI +</I>><i> device) when console-kit registers a new session. +</I>><i> +</I>><i> This included the gdm user at the login manager. +</I>><i> +</I>><i> systemd is gradually taking over the job of consolekit. This means that +</I>><i> systemd now handles the ACL writing and login sessions should be +</I>><i> visiible via systemctl-loginctl (as opposed to ck-list-sessions). +</I>><i> +</I>><i> +</I>><i> With udev 172, both systemd and console-kit would trigger ACL writes. +</I>><i> Normally this is fine, they both ultimately do the same thing. +</I>><i> +</I>><i> But, it seems that in actual fact, systemctl-logind wasn't ever +</I>><i> registering the gdm session. Thankfully console-kit did, and thus gdm +</I>><i> user got the ACLs it needed. +</I>><i> +</I>><i> +</I>><i> Now this is where the problem arises. With udev 173, udev-acl knows +</I>><i> whether or not systemd is running and if it is, it it won't write the +</I>><i> ACLs. This means that even tho' gdm is still registered with +</I>><i> console-kit, this will never actually trigger an ACL write. +</I>><i> +</I>><i> This means that gdm does not have access to /dev/dri/card0 and thus +</I>><i> cannot determine if the device is capable of 3D accel. This then sets an +</I>><i> atom on the root window which the gnome-session-check-accelerated binary +</I>><i> looks for. This atom acts as a little cache. If it doesn't exist, it +</I>><i> does a full probe and then writes the atom. The next time it runs it +</I>><i> finds the atom and skips the actual checks. But as the atom was written +</I>><i> by gdm when it couldn't access dri, it says no accel is available, even +</I>><i> although the user can actually access it. +</I>><i> +</I>><i> +</I>><i> I've not yet sussed out gdm is not registering with systemd... it should +</I>><i> all be automatic via pam... but something somewhere is failing :s +</I> +OK, sussed it out eventually (I was looking in fedora's "master" branch +rather than "f16" branch so missed some patches :() + +gdm patched to make it all work now. I'm not really sure how kdm will +behave but I wouldn't be surprised if it's broken. + +Col + + + +-- + +Colin Guthrie +mageia(at)colin.guthr.ie +<A HREF="http://colin.guthr.ie/">http://colin.guthr.ie/</A> + +Day Job: + Tribalogic Limited [<A HREF="http://www.tribalogic.net/">http://www.tribalogic.net/</A>] +Open Source: + Mageia Contributor [<A HREF="http://www.mageia.org/">http://www.mageia.org/</A>] + PulseAudio Hacker [<A HREF="http://www.pulseaudio.org/">http://www.pulseaudio.org/</A>] + Trac Hacker [<A HREF="http://trac.edgewall.org/">http://trac.edgewall.org/</A>] +</PRE> + + + + + + + + + + + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="007573.html">[Mageia-dev] systemd + udev 173 + gnome-shell +</A></li> + <LI>Next message: <A HREF="007592.html">[Mageia-dev] Handling GNOME 2.x Broken Dependencies +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#7588">[ date ]</a> + <a href="thread.html#7588">[ thread ]</a> + <a href="subject.html#7588">[ subject ]</a> + <a href="author.html#7588">[ author ]</a> + </LI> + </UL> + +<hr> +<a href="https://www.mageia.org/mailman/listinfo/mageia-dev">More information about the Mageia-dev +mailing list</a><br> +</body></html> |