1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
|
<!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=%3C4E689FF4.4020407%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="007853.html">
<LINK REL="Next" HREF="007894.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=%3C4E689FF4.4020407%40colin.guthr.ie%3E"
TITLE="[Mageia-dev] Problem with gdm metacity again">mageia at colin.guthr.ie
</A><BR>
<I>Thu Sep 8 12:59:00 CEST 2011</I>
<P><UL>
<LI>Previous message: <A HREF="007853.html">[Mageia-dev] Problem with gdm metacity again
</A></li>
<LI>Next message: <A HREF="007894.html">[Mageia-dev] Problem with gdm metacity again
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#7860">[ date ]</a>
<a href="thread.html#7860">[ thread ]</a>
<a href="subject.html#7860">[ subject ]</a>
<a href="author.html#7860">[ author ]</a>
</LI>
</UL>
<HR>
<!--beginarticle-->
<PRE>'Twas brillig, and JA Magallon at 07/09/11 18:18 did gyre and gimble:
><i> On Wed, 07 Sep 2011 13:27:05 +0100
</I>><i> Colin Guthrie <<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">mageia at colin.guthr.ie</A>> wrote:
</I>><i>
</I>>><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>><i>
</I>><i> Yup, thats the problem.
</I>><i> Booting into systemd gives this:
</I>><i>
</I>><i> one:~# ll /dev/dri*
</I>><i> total 0
</I>><i> crw-rw----+ 1 root video 226, 0 2011.09.07 15:12 card0
</I>><i> crw-rw-rw- 1 root video 226, 64 2011.09.07 15:12 controlD64
</I>><i> one:~# getfacl /dev/dri/card0
</I>><i> getfacl: Removing leading '/' from absolute path names
</I>><i> # file: dev/dri/card0
</I>><i> # owner: root
</I>><i> # group: video
</I>><i> user::rw-
</I>><i> user:gdm:rw-
</I>><i> group::rw-
</I>><i> mask::rw-
</I>><i> other::---
</I>><i>
</I>
OK, can you try this:
Can you edit and add the line: /etc/pam.d/gdm-welcome
-session optional pam_ck_connector.so
BEFORE the line:
session include system-auth
And then reboot... see if that helps?
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="007853.html">[Mageia-dev] Problem with gdm metacity again
</A></li>
<LI>Next message: <A HREF="007894.html">[Mageia-dev] Problem with gdm metacity again
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#7860">[ date ]</a>
<a href="thread.html#7860">[ thread ]</a>
<a href="subject.html#7860">[ subject ]</a>
<a href="author.html#7860">[ 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>
|
