1 |
Okay, my bad. This email is extremely confusing to me, with so many tab |
2 |
levels. What I posted would have been in response to Yuri, I think. |
3 |
|
4 |
| |
5 |
//--------------------------------------------------------------------------------------------------------------// |
6 |
| But my kde is istill 4.10.1. It seemed nobody had the same |
7 |
problem, and |
8 |
| my problem was not that bad because my own account was working |
9 |
pretty |
10 |
| well. |
11 |
|
12 |
| |
13 |
| The error is exactly the same of yours, when I try to login the |
14 |
guest |
15 |
| account, but when I try "startx" a get the following: |
16 |
| |
17 |
| /etc/X11/xinit/xinitrc line 63: exec: xterm: not found |
18 |
| |
19 |
//-------------------------------------------------------------------------------------------------------------// |
20 |
|
21 |
It sounds like this person needs to add/move xterm to a PATH which xinitrc |
22 |
is capable of reading. |
23 |
|
24 |
What problems specifically are you having, Natanael? |
25 |
|
26 |
Forrest |
27 |
|
28 |
On Thu, Apr 11, 2013 at 4:35 PM, Forrest Schultz <f.schultz0@×××××.com>wrote: |
29 |
|
30 |
> To be fair, I really don't know much about either of these processes. |
31 |
> However, it looked like the log was describing a situation where, due to a |
32 |
> lack of timezone information, the two processes were unable to communicate |
33 |
> properly. Is it at all possible that this is caused by some processes |
34 |
> defaulting to different time zones? DBUS certainly sounds like a program |
35 |
> where correct time information would be important. On the other hand, I |
36 |
> would think that they would both pull system time if that was the case. |
37 |
> Also, none of things you did sound like they would have fixed that. It also |
38 |
> seems possible that the library/package rebuild fixed something that was |
39 |
> wrong with ktimezoned specifically. Well, there's my two cents. |
40 |
> |
41 |
> |
42 |
> On Thu, Apr 11, 2013 at 4:16 PM, Natanael Olaiz <nolaiz@×××××.com> wrote: |
43 |
> |
44 |
>> Ooops, I sent it by error without finishing it... sorry. |
45 |
>> |
46 |
>> |
47 |
>> After some cleanup on both machines KDM is working again! |
48 |
>> |
49 |
>> The cleanup consisted in: |
50 |
>> - revdep-rebuild |
51 |
>> - python-updater |
52 |
>> - perl-cleaner |
53 |
>> - an upgrade of the few new outdated packages |
54 |
>> |
55 |
>> I triggered all the commands in chain this morning and I see now that is |
56 |
>> working without knowing what was the problem. |
57 |
>> I only see on /var/log/portage/elog on one of the machines that |
58 |
>> kdelibs-4.10.2 was reinstalled (I guess by revdep-rebuild, there was no |
59 |
>> upgrade for kdelibs), but as far I see it was not reinstalled in the |
60 |
>> other... |
61 |
>> |
62 |
>> |
63 |
>> Anyway, the same chain on both systems solved the problem. |
64 |
>> |
65 |
>> |
66 |
>> Do you know any other file I can use to backtrace the cleanup command's |
67 |
>> actions? I cannot found more useful logs, and I lost the console buffer. |
68 |
>> |
69 |
>> |
70 |
>> Can you try them? |
71 |
>> |
72 |
>> |
73 |
>> Best regards, |
74 |
>> Natanael. |
75 |
>> |
76 |
>> |
77 |
>> |
78 |
>> El 04/11/2013 10:00 PM, Natanael Olaiz escribió: |
79 |
>> |
80 |
>> |
81 |
>> |
82 |
>> |
83 |
>> |
84 |
>> |
85 |
>> On 04/10/2013 10:28 PM, Natanael Olaiz wrote: |
86 |
>> |
87 |
>> I forgot: I'm using sysvinit, and policykit is enabled for kdelibs. |
88 |
>> |
89 |
>> So I also tried reinstalling consolekit and polkit (the day I tried I |
90 |
>> had to patch polkit 0.110 in order to compile !!! :-/). Nothing changed. |
91 |
>> |
92 |
>> |
93 |
>> Natanael. |
94 |
>> |
95 |
>> |
96 |
>> On 04/10/2013 10:11 PM, nael wrote: |
97 |
>> |
98 |
>> Hi, |
99 |
>> |
100 |
>> On 04/09/2013 05:05 PM, Yuri K. Shatroff wrote: |
101 |
>> |
102 |
>> On 09.04.2013 17:13, João Matos wrote: |
103 |
>> |
104 |
>> 2013/4/9 Yuri K. Shatroff <yks-uno@××××××.ru <mailto:yks-uno@××××××.ru> <yks-uno@××××××.ru>> |
105 |
>> |
106 |
>> Hello gentoo-users, |
107 |
>> |
108 |
>> Yesterday I completed a world update (amd64, unstable) and now I |
109 |
>> can't login with kdm. |
110 |
>> (I have kdm set as display manager in /etc/conf.d/xdm, and started |
111 |
>> from default runlevel) |
112 |
>> After booting, the login screen appears as usual. I type |
113 |
>> login/password and then a glimpse of X's default x-shaped pointer on |
114 |
>> black background appears, returning to the login screen. |
115 |
>> I don't get any sensible errors, neither in kdm.log nor in messages, |
116 |
>> all I see is: |
117 |
>> |
118 |
>> [/var/log/kdm.log] |
119 |
>> ----------------------------- |
120 |
>> klauncher(21958) kdemain: No DBUS session-bus found. Check if you |
121 |
>> have started the DBUS server. |
122 |
>> kdeinit4: Communication error with launcher. Exiting! |
123 |
>> kdmgreet(21952)/kdecore (K*TimeZone*): KSystemTimeZones: ktimezoned |
124 |
>> initialize() D-Bus call failed: "Not connected to D-Bus server" |
125 |
>> |
126 |
>> kdmgreet(21952)/kdecore (K*TimeZone*): No time zone information |
127 |
>> obtained from ktimezoned |
128 |
>> ----------------------------- |
129 |
>> |
130 |
>> But I guess this is unrelated, since dbus is running (and restarting |
131 |
>> it doesn't help, nor does restarting xdm) |
132 |
>> |
133 |
>> Each time login fails I also see this in |
134 |
>> [/var/log/messages] |
135 |
>> ----------------------------- |
136 |
>> Apr 9 11:33:53 localhost kdm: :0[20396]: pam_unix(kde:session): |
137 |
>> session opened for user yks by (uid=0) |
138 |
>> Apr 9 11:33:54 localhost kdm: :0[20396]: pam_unix(kde:session): |
139 |
>> session closed for user yks |
140 |
>> ----------------------------- |
141 |
>> |
142 |
>> No other logs appear to change. |
143 |
>> |
144 |
>> Needless to say that kdm 4.10.1 and earlier worked properly, and no |
145 |
>> configuration files were changed during the last update. |
146 |
>> |
147 |
>> As a workaround, I just typed startx on the console (with startkde |
148 |
>> in .xinitrc) and KDE started up, so I assume the problem is |
149 |
>> somewhere around kdm. |
150 |
>> |
151 |
>> I' m exactly in the same situation. In two different machines I had the |
152 |
>> same result upgrading world. The upgrade included kde 4.10.2, but I also |
153 |
>> udev-201 and more ebuilds. |
154 |
>> |
155 |
>> On one of the machines I tried downgrading udev but didn' t work. |
156 |
>> |
157 |
>> |
158 |
>> Xdm doesn't work neither, but gdm does! |
159 |
>> startx with "startkde" also works. |
160 |
>> |
161 |
>> |
162 |
>> Did you found something more? |
163 |
>> |
164 |
>> |
165 |
>> |
166 |
>> Best regards, |
167 |
>> Natanael. |
168 |
>> |
169 |
>> |
170 |
>> |
171 |
>> Any ideas? |
172 |
>> |
173 |
>> P.S. I had no problem with networking and udev which got updated |
174 |
>> from 197-r9 to 200 and the network interface name didn't change from |
175 |
>> eth0 (the 80-*rules file was a regular file full of commented text) |
176 |
>> |
177 |
>> -- |
178 |
>> Best wishes, |
179 |
>> Yuri K. Shatroff |
180 |
>> |
181 |
>> |
182 |
>> Hi. I have a similar problem here, since the last update from kde 4.9. |
183 |
>> But I can login with my user, I just cant using any new user. I found |
184 |
>> this problem easily, because I have a guest account, and I erase |
185 |
>> "/home/guest/*" once in a while. Since two months ago this account is |
186 |
>> useless. |
187 |
>> |
188 |
>> that's a little different problem ;) I remember the related discussion |
189 |
>> on this mailing list. |
190 |
>> |
191 |
>> |
192 |
>> But my kde is istill 4.10.1. It seemed nobody had the same problem, and |
193 |
>> my problem was not that bad because my own account was working pretty |
194 |
>> well. |
195 |
>> |
196 |
>> The error is exactly the same of yours, when I try to login the guest |
197 |
>> account, but when I try "startx" a get the following: |
198 |
>> |
199 |
>> /etc/X11/xinit/xinitrc line 63: exec: xterm: not found |
200 |
>> |
201 |
>> Can this be solved by putting an executable .xinitrc into the user's |
202 |
>> home dir? |
203 |
>> As for me, I had to put |
204 |
>> ----- |
205 |
>> exec /usr/bin/startkde |
206 |
>> ----- |
207 |
>> so that startx would start kde. |
208 |
>> |
209 |
>> |
210 |
>> I don't think it will help, because I get the same error if I try the |
211 |
>> "working account". |
212 |
>> |
213 |
>> I'm using systemd, so I tried to remove consolkit support from kdm, but |
214 |
>> it didn't help. |
215 |
>> |
216 |
>> I also have a suspicion it has to do with consolekit, but there is no |
217 |
>> simple way to make sure. |
218 |
>> |
219 |
>> |
220 |
>> Is anyone else facing a similar problem? |
221 |
>> |
222 |
>> |
223 |
>> -- |
224 |
>> João de Matos |
225 |
>> Linux User #461527 |
226 |
>> Graduado em Engenharia de Computação |
227 |
>> UEFS - Universidade Estadual de Feira de Santana |
228 |
>> |
229 |
>> |
230 |
>> |
231 |
>> |
232 |
> |