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