diff options
Diffstat (limited to 'zarb-ml/mageia-dev/2011-September/007853.html')
| -rw-r--r-- | zarb-ml/mageia-dev/2011-September/007853.html | 190 |
1 files changed, 190 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/2011-September/007853.html b/zarb-ml/mageia-dev/2011-September/007853.html new file mode 100644 index 000000000..d55db3123 --- /dev/null +++ b/zarb-ml/mageia-dev/2011-September/007853.html @@ -0,0 +1,190 @@ +<!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=%3C20110907191830.53705c0b%40werewolf.home%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="007841.html"> + <LINK REL="Next" HREF="007860.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] Problem with gdm metacity again</H1> + <B>JA Magallon</B> + <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Problem%20with%20gdm%20metacity%20again&In-Reply-To=%3C20110907191830.53705c0b%40werewolf.home%3E" + TITLE="[Mageia-dev] Problem with gdm metacity again">jamagallon at ono.com + </A><BR> + <I>Wed Sep 7 19:18:30 CEST 2011</I> + <P><UL> + <LI>Previous message: <A HREF="007841.html">[Mageia-dev] Problem with gdm metacity again +</A></li> + <LI>Next message: <A HREF="007860.html">[Mageia-dev] Problem with gdm metacity again +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#7853">[ date ]</a> + <a href="thread.html#7853">[ thread ]</a> + <a href="subject.html#7853">[ subject ]</a> + <a href="author.html#7853">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>On Wed, 07 Sep 2011 13:27:05 +0100 +Colin Guthrie <<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">mageia at colin.guthr.ie</A>> wrote: + +><i> 'Twas brillig, and JA Magallon at 07/09/11 12:03 did gyre and gimble: +</I>><i> > On Wed, 7 Sep 2011 13:01:39 +0300 +</I>><i> > Shlomi Fish <<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">shlomif at shlomifish.org</A>> wrote: +</I>><i> > +</I>><i> >> Hi J. A., +</I>><i> >> +</I>><i> >> On Wed, 7 Sep 2011 11:42:33 +0200 +</I>><i> >> JA Magallon <<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">jamagallon at ono.com</A>> wrote: +</I>><i> >> +</I>><i> >>> On Wed, 7 Sep 2011 11:15:21 +0200 +</I>><i> >>> JA Magallon <<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">jamagallon at ono.com</A>> wrote: +</I>><i> >>> +</I>><i> >>>> Hi... +</I>><i> >>>> +</I>><i> >>>> This old problem has surfaced again: +</I>><i> >>>> +</I>><i> >>>> .xsession-errors: +</I>><i> >>>> +</I>><i> >>>> ... +</I>><i> >>>> Window manager warning: Screen 0 on display ":0" already has a window manager; try using the --replace option to replace the current window manager. +</I>><i> >>>> Window manager warning: Screen 0 on display ":0" already has a window manager; try using the --replace option to replace the current window manager. +</I>><i> >>>> ... +</I>><i> >>>> +</I>><i> >>>> I get only the nautilus desktop, with two black bars on top and bottom of the screen. +</I>><i> >>>> If I launch a terminal, 'gnome-shell --replace' works fine. +</I>><i> >>>> +</I>><i> >> +</I>><i> >> I reported this bug here: +</I>><i> >> +</I>><i> >> <A HREF="https://bugs.mageia.org/show_bug.cgi?id=2628">https://bugs.mageia.org/show_bug.cgi?id=2628</A> +</I>><i> >> +</I>><i> >> I can reproduce it here on my x86-64 Mageia Linux Cauldron laptop. +</I>><i> >> +</I>><i> >> Regards, +</I>><i> >> +</I>><i> >> Shlomi Fish +</I>><i> >> +</I>><i> >>>> Any idea ? +</I>><i> >>>> Can it be some personal setting ? +</I>><i> >>>> +</I>><i> >>>> TIA +</I>><i> >>> +</I>><i> >>> Digging a bit more, something is wrong detecting acceleration. +</I>><i> >>> In GDM log: +</I>><i> >>> +</I>><i> >>> gnome-session[4752]: DEBUG(+): fill: *** Looking if /usr/share/gnome-session/sessions/gdm-shell.session is a valid session file +</I>><i> >>> gnome-session[4752]: DEBUG(+): fill: *** Launching helper 'bash -c "gnome-shell --help | grep -q gdm-mode && /usr/lib64/gnome-session-check-accelerated"' to know if session is runnable +</I>><i> >>> gnome-session-is-accelerated: No hardware 3D support. +</I>><i> >>> gnome-session-check-accelerated: Helper exited with code 256 +</I>><i> >>> gnome-session[4752]: WARNING: Session 'gdm-shell' runnable check failed: Exited with code 1 +</I>><i> >>> gnome-session[4752]: DEBUG(+): fill: *** Session is not runnable +</I>><i> >>> gnome-session[4752]: DEBUG(+): fill: *** Getting session 'gdm-fallback' +</I>><i> >>> +</I>><i> >>> This is for GDM's own session. +</I>><i> >>> The same happens for user. +</I>><i> >>> +</I>><i> >>> Any ideas ? How can I check why this fails ? +</I>><i> >>> Its a netbook with Intel graphics, so it uses Mesa. +</I>><i> >>> +</I>><i> >>> Will check on an nvidia system too. +</I>><i> >>> +</I>><i> > +</I>><i> > I did, and everything works fine. I even discovered that GDM looks different +</I>><i> > when acceleration is available ;)). +</I>><i> > +</I>><i> > So these are two separate problems: +</I>><i> > +</I>><i> > - Acceleration detection on some systems, from my limited tests, it works on +</I>><i> > nVidia (32bit, will check 64 shortly), and fails on intel (mesa???) graphics. +</I>><i> > This can be a bug report for gnome-session (/usr/lib64/gnome-session-check-accelerated*) +</I>><i> > or for Mesa if it's it what breaks things. +</I>><i> > +</I>><i> > - In full mode, gnome-shell from the user replaces gnome-shell from gdm. +</I>><i> > But in fallback mode, gnome-shell can't replace GDM's metacity. +</I>><i> +</I>><i> It's almost certainly a permissions thing. +</I>><i> +</I> +Yup, thats the problem. +Booting into systemd gives this: + +one:~# ll /dev/dri* +total 0 +crw-rw----+ 1 root video 226, 0 2011.09.07 15:12 card0 +crw-rw-rw- 1 root video 226, 64 2011.09.07 15:12 controlD64 +one:~# getfacl /dev/dri/card0 +getfacl: Removing leading '/' from absolute path names +# file: dev/dri/card0 +# owner: root +# group: video +user::rw- +user:gdm:rw- +group::rw- +mask::rw- +other::--- + +But with init, card0 has no acl. + +As a quick hack, + +one:/dev/dri# service dm stop +Stopping display manager: [ OK ] +one:/dev/dri# chmod 666 card0 +one:/dev/dri# ll +total 0 +crw-rw-rw- 1 root video 226, 0 2011.09.07 19:15 card0 +crw-rw-rw- 1 root video 226, 64 2011.09.07 19:15 controlD64 +one:/dev/dri# service dm start +Starting display manager: [ OK ] +one:/dev/dri# + +made it work! + +><i> I'm not sure GDM registers itself with consolekit anymore. And +</I>><i> in-so-doing, will not get permissions on the DRI device and thus will +</I>><i> not be able to run the nice new shell. +</I>><i> +</I>><i> +</I>><i> If you run systemd then all should be well. +</I>><i> +</I>><i> Col +</I>><i> +</I>><i> +</I>><i> +</I> +</PRE> + + + + + + + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="007841.html">[Mageia-dev] Problem with gdm metacity again +</A></li> + <LI>Next message: <A HREF="007860.html">[Mageia-dev] Problem with gdm metacity again +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#7853">[ date ]</a> + <a href="thread.html#7853">[ thread ]</a> + <a href="subject.html#7853">[ subject ]</a> + <a href="author.html#7853">[ 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> |