1 |
Hi, |
2 |
|
3 |
On 04/09/2013 05:05 PM, Yuri K. Shatroff wrote: |
4 |
> On 09.04.2013 17:13, João Matos wrote: |
5 |
>> |
6 |
>> |
7 |
>> |
8 |
>> 2013/4/9 Yuri K. Shatroff <yks-uno@××××××.ru <mailto:yks-uno@××××××.ru>> |
9 |
>> |
10 |
>> Hello gentoo-users, |
11 |
>> |
12 |
>> Yesterday I completed a world update (amd64, unstable) and now I |
13 |
>> can't login with kdm. |
14 |
>> (I have kdm set as display manager in /etc/conf.d/xdm, and started |
15 |
>> from default runlevel) |
16 |
>> After booting, the login screen appears as usual. I type |
17 |
>> login/password and then a glimpse of X's default x-shaped pointer on |
18 |
>> black background appears, returning to the login screen. |
19 |
>> I don't get any sensible errors, neither in kdm.log nor in messages, |
20 |
>> all I see is: |
21 |
>> |
22 |
>> [/var/log/kdm.log] |
23 |
>> ----------------------------- |
24 |
>> klauncher(21958) kdemain: No DBUS session-bus found. Check if you |
25 |
>> have started the DBUS server. |
26 |
>> kdeinit4: Communication error with launcher. Exiting! |
27 |
>> kdmgreet(21952)/kdecore (K*TimeZone*): KSystemTimeZones: ktimezoned |
28 |
>> initialize() D-Bus call failed: "Not connected to D-Bus server" |
29 |
>> |
30 |
>> kdmgreet(21952)/kdecore (K*TimeZone*): No time zone information |
31 |
>> obtained from ktimezoned |
32 |
>> ----------------------------- |
33 |
>> |
34 |
>> But I guess this is unrelated, since dbus is running (and restarting |
35 |
>> it doesn't help, nor does restarting xdm) |
36 |
>> |
37 |
>> Each time login fails I also see this in |
38 |
>> [/var/log/messages] |
39 |
>> ----------------------------- |
40 |
>> Apr 9 11:33:53 localhost kdm: :0[20396]: pam_unix(kde:session): |
41 |
>> session opened for user yks by (uid=0) |
42 |
>> Apr 9 11:33:54 localhost kdm: :0[20396]: pam_unix(kde:session): |
43 |
>> session closed for user yks |
44 |
>> ----------------------------- |
45 |
>> |
46 |
>> No other logs appear to change. |
47 |
>> |
48 |
>> Needless to say that kdm 4.10.1 and earlier worked properly, and no |
49 |
>> configuration files were changed during the last update. |
50 |
>> |
51 |
>> As a workaround, I just typed startx on the console (with startkde |
52 |
>> in .xinitrc) and KDE started up, so I assume the problem is |
53 |
>> somewhere around kdm. |
54 |
|
55 |
|
56 |
I' m exactly in the same situation. In two different machines I had the |
57 |
same result upgrading world. The upgrade included kde 4.10.2, but I also |
58 |
udev-201 and more ebuilds. |
59 |
|
60 |
On one of the machines I tried downgrading udev but didn' t work. |
61 |
|
62 |
|
63 |
Xdm doesn't work neither, but gdm does! |
64 |
startx with "startkde" also works. |
65 |
|
66 |
|
67 |
Did you found something more? |
68 |
|
69 |
|
70 |
|
71 |
Best regards, |
72 |
Natanael. |
73 |
|
74 |
|
75 |
>> |
76 |
>> Any ideas? |
77 |
>> |
78 |
>> P.S. I had no problem with networking and udev which got updated |
79 |
>> from 197-r9 to 200 and the network interface name didn't change from |
80 |
>> eth0 (the 80-*rules file was a regular file full of commented text) |
81 |
>> |
82 |
>> -- |
83 |
>> Best wishes, |
84 |
>> Yuri K. Shatroff |
85 |
>> |
86 |
>> |
87 |
>> Hi. I have a similar problem here, since the last update from kde 4.9. |
88 |
>> But I can login with my user, I just cant using any new user. I found |
89 |
>> this problem easily, because I have a guest account, and I erase |
90 |
>> "/home/guest/*" once in a while. Since two months ago this account is |
91 |
>> useless. |
92 |
> |
93 |
> that's a little different problem ;) I remember the related discussion |
94 |
> on this mailing list. |
95 |
> |
96 |
>> But my kde is istill 4.10.1. It seemed nobody had the same problem, and |
97 |
>> my problem was not that bad because my own account was working pretty |
98 |
>> well. |
99 |
>> |
100 |
>> The error is exactly the same of yours, when I try to login the guest |
101 |
>> account, but when I try "startx" a get the following: |
102 |
>> |
103 |
>> /etc/X11/xinit/xinitrc line 63: exec: xterm: not found |
104 |
> |
105 |
> Can this be solved by putting an executable .xinitrc into the user's |
106 |
> home dir? |
107 |
> As for me, I had to put |
108 |
> ----- |
109 |
> exec /usr/bin/startkde |
110 |
> ----- |
111 |
> so that startx would start kde. |
112 |
> |
113 |
>> I don't think it will help, because I get the same error if I try the |
114 |
>> "working account". |
115 |
>> |
116 |
>> I'm using systemd, so I tried to remove consolkit support from kdm, but |
117 |
>> it didn't help. |
118 |
> |
119 |
> I also have a suspicion it has to do with consolekit, but there is no |
120 |
> simple way to make sure. |
121 |
> |
122 |
>> |
123 |
>> Is anyone else facing a similar problem? |
124 |
>> |
125 |
>> |
126 |
>> -- |
127 |
>> João de Matos |
128 |
>> Linux User #461527 |
129 |
>> Graduado em Engenharia de Computação |
130 |
>> UEFS - Universidade Estadual de Feira de Santana |
131 |
> |
132 |
> |