summaryrefslogtreecommitdiffstats
path: root/zarb-ml/mageia-dev/2011-September/007841.html
diff options
context:
space:
mode:
Diffstat (limited to 'zarb-ml/mageia-dev/2011-September/007841.html')
-rw-r--r--zarb-ml/mageia-dev/2011-September/007841.html166
1 files changed, 166 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/2011-September/007841.html b/zarb-ml/mageia-dev/2011-September/007841.html
new file mode 100644
index 000000000..b264a9949
--- /dev/null
+++ b/zarb-ml/mageia-dev/2011-September/007841.html
@@ -0,0 +1,166 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
+<HTML>
+ <HEAD>
+ <TITLE> [Mageia-dev] Problem with gdm metacity again
+ </TITLE>
+ <LINK REL="Index" HREF="index.html" >
+ <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Problem%20with%20gdm%20metacity%20again&In-Reply-To=%3C4E676319.2000309%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="007834.html">
+ <LINK REL="Next" HREF="007853.html">
+ </HEAD>
+ <BODY BGCOLOR="#ffffff">
+ <H1>[Mageia-dev] Problem with gdm metacity again</H1>
+ <B>Colin Guthrie</B>
+ <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Problem%20with%20gdm%20metacity%20again&In-Reply-To=%3C4E676319.2000309%40colin.guthr.ie%3E"
+ TITLE="[Mageia-dev] Problem with gdm metacity again">mageia at colin.guthr.ie
+ </A><BR>
+ <I>Wed Sep 7 14:27:05 CEST 2011</I>
+ <P><UL>
+ <LI>Previous message: <A HREF="007834.html">[Mageia-dev] Problem with gdm metacity again
+</A></li>
+ <LI>Next message: <A HREF="007853.html">[Mageia-dev] Problem with gdm metacity again
+</A></li>
+ <LI> <B>Messages sorted by:</B>
+ <a href="date.html#7841">[ date ]</a>
+ <a href="thread.html#7841">[ thread ]</a>
+ <a href="subject.html#7841">[ subject ]</a>
+ <a href="author.html#7841">[ author ]</a>
+ </LI>
+ </UL>
+ <HR>
+<!--beginarticle-->
+<PRE>'Twas brillig, and JA Magallon at 07/09/11 12:03 did gyre and gimble:
+&gt;<i> On Wed, 7 Sep 2011 13:01:39 +0300
+</I>&gt;<i> Shlomi Fish &lt;<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">shlomif at shlomifish.org</A>&gt; wrote:
+</I>&gt;<i>
+</I>&gt;&gt;<i> Hi J. A.,
+</I>&gt;&gt;<i>
+</I>&gt;&gt;<i> On Wed, 7 Sep 2011 11:42:33 +0200
+</I>&gt;&gt;<i> JA Magallon &lt;<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">jamagallon at ono.com</A>&gt; wrote:
+</I>&gt;&gt;<i>
+</I>&gt;&gt;&gt;<i> On Wed, 7 Sep 2011 11:15:21 +0200
+</I>&gt;&gt;&gt;<i> JA Magallon &lt;<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">jamagallon at ono.com</A>&gt; wrote:
+</I>&gt;&gt;&gt;<i>
+</I>&gt;&gt;&gt;&gt;<i> Hi...
+</I>&gt;&gt;&gt;&gt;<i>
+</I>&gt;&gt;&gt;&gt;<i> This old problem has surfaced again:
+</I>&gt;&gt;&gt;&gt;<i>
+</I>&gt;&gt;&gt;&gt;<i> .xsession-errors:
+</I>&gt;&gt;&gt;&gt;<i>
+</I>&gt;&gt;&gt;&gt;<i> ...
+</I>&gt;&gt;&gt;&gt;<i> Window manager warning: Screen 0 on display &quot;:0&quot; already has a window manager; try using the --replace option to replace the current window manager.
+</I>&gt;&gt;&gt;&gt;<i> Window manager warning: Screen 0 on display &quot;:0&quot; already has a window manager; try using the --replace option to replace the current window manager.
+</I>&gt;&gt;&gt;&gt;<i> ...
+</I>&gt;&gt;&gt;&gt;<i>
+</I>&gt;&gt;&gt;&gt;<i> I get only the nautilus desktop, with two black bars on top and bottom of the screen.
+</I>&gt;&gt;&gt;&gt;<i> If I launch a terminal, 'gnome-shell --replace' works fine.
+</I>&gt;&gt;&gt;&gt;<i>
+</I>&gt;&gt;<i>
+</I>&gt;&gt;<i> I reported this bug here:
+</I>&gt;&gt;<i>
+</I>&gt;&gt;<i> <A HREF="https://bugs.mageia.org/show_bug.cgi?id=2628">https://bugs.mageia.org/show_bug.cgi?id=2628</A>
+</I>&gt;&gt;<i>
+</I>&gt;&gt;<i> I can reproduce it here on my x86-64 Mageia Linux Cauldron laptop.
+</I>&gt;&gt;<i>
+</I>&gt;&gt;<i> Regards,
+</I>&gt;&gt;<i>
+</I>&gt;&gt;<i> Shlomi Fish
+</I>&gt;&gt;<i>
+</I>&gt;&gt;&gt;&gt;<i> Any idea ?
+</I>&gt;&gt;&gt;&gt;<i> Can it be some personal setting ?
+</I>&gt;&gt;&gt;&gt;<i>
+</I>&gt;&gt;&gt;&gt;<i> TIA
+</I>&gt;&gt;&gt;<i>
+</I>&gt;&gt;&gt;<i> Digging a bit more, something is wrong detecting acceleration.
+</I>&gt;&gt;&gt;<i> In GDM log:
+</I>&gt;&gt;&gt;<i>
+</I>&gt;&gt;&gt;<i> gnome-session[4752]: DEBUG(+): fill: *** Looking if /usr/share/gnome-session/sessions/gdm-shell.session is a valid session file
+</I>&gt;&gt;&gt;<i> gnome-session[4752]: DEBUG(+): fill: *** Launching helper 'bash -c &quot;gnome-shell --help | grep -q gdm-mode &amp;&amp; /usr/lib64/gnome-session-check-accelerated&quot;' to know if session is runnable
+</I>&gt;&gt;&gt;<i> gnome-session-is-accelerated: No hardware 3D support.
+</I>&gt;&gt;&gt;<i> gnome-session-check-accelerated: Helper exited with code 256
+</I>&gt;&gt;&gt;<i> gnome-session[4752]: WARNING: Session 'gdm-shell' runnable check failed: Exited with code 1
+</I>&gt;&gt;&gt;<i> gnome-session[4752]: DEBUG(+): fill: *** Session is not runnable
+</I>&gt;&gt;&gt;<i> gnome-session[4752]: DEBUG(+): fill: *** Getting session 'gdm-fallback'
+</I>&gt;&gt;&gt;<i>
+</I>&gt;&gt;&gt;<i> This is for GDM's own session.
+</I>&gt;&gt;&gt;<i> The same happens for user.
+</I>&gt;&gt;&gt;<i>
+</I>&gt;&gt;&gt;<i> Any ideas ? How can I check why this fails ?
+</I>&gt;&gt;&gt;<i> Its a netbook with Intel graphics, so it uses Mesa.
+</I>&gt;&gt;&gt;<i>
+</I>&gt;&gt;&gt;<i> Will check on an nvidia system too.
+</I>&gt;&gt;&gt;<i>
+</I>&gt;<i>
+</I>&gt;<i> I did, and everything works fine. I even discovered that GDM looks different
+</I>&gt;<i> when acceleration is available ;)).
+</I>&gt;<i>
+</I>&gt;<i> So these are two separate problems:
+</I>&gt;<i>
+</I>&gt;<i> - Acceleration detection on some systems, from my limited tests, it works on
+</I>&gt;<i> nVidia (32bit, will check 64 shortly), and fails on intel (mesa???) graphics.
+</I>&gt;<i> This can be a bug report for gnome-session (/usr/lib64/gnome-session-check-accelerated*)
+</I>&gt;<i> or for Mesa if it's it what breaks things.
+</I>&gt;<i>
+</I>&gt;<i> - In full mode, gnome-shell from the user replaces gnome-shell from gdm.
+</I>&gt;<i> But in fallback mode, gnome-shell can't replace GDM's metacity.
+</I>
+It's almost certainly a permissions thing.
+
+I'm not sure GDM registers itself with consolekit anymore. And
+in-so-doing, will not get permissions on the DRI device and thus will
+not be able to run the nice new shell.
+
+
+If you run systemd then all should be well.
+
+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="007834.html">[Mageia-dev] Problem with gdm metacity again
+</A></li>
+ <LI>Next message: <A HREF="007853.html">[Mageia-dev] Problem with gdm metacity again
+</A></li>
+ <LI> <B>Messages sorted by:</B>
+ <a href="date.html#7841">[ date ]</a>
+ <a href="thread.html#7841">[ thread ]</a>
+ <a href="subject.html#7841">[ subject ]</a>
+ <a href="author.html#7841">[ 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>