1 |
Hello, |
2 |
|
3 |
thanks for your reply. This is what I suspected, but I don't use NM |
4 |
and don't recall that any of my networks try to set my hostname (I |
5 |
connect only to a dorm network, and eduroam, sometimes some dnsmasq |
6 |
driven lan). |
7 |
|
8 |
I have no idea who tries to set my hostname and will investigate it |
9 |
(it really seems that setting my hostname to empty string is the |
10 |
cause, but still I don't know why. One idea is that something is |
11 |
corrupting my memory (I would point at i915 driver, but don't really |
12 |
have time for debugging). |
13 |
|
14 |
Regards Ladislav Laska |
15 |
S pozdravem Ladislav Laska |
16 |
--- |
17 |
xmpp/jabber: ladislav.laska@××××××.cz |
18 |
|
19 |
|
20 |
|
21 |
2010/11/1 Carlos Laué <CarlosL@××××××.cz>: |
22 |
> Hello, |
23 |
> |
24 |
>> I've recently stumbled onto a problem, possibly with kde3. |
25 |
>> |
26 |
>> After some time (and I think this happens after resuming from RAM), |
27 |
>> new terminals (even text ones) have empty hostname, I can't run any X |
28 |
>> apps (cannot connect to X server :0.0), kde tells me "KDEInit could |
29 |
>> not launch 'anything'", and in .xsession-errors appears: |
30 |
>> ... |
31 |
> |
32 |
> I've seen a problem like this when I've installed networkmanager, and connected to a network that tried to set my hostname (a 3g connection). When it set the hostname I had no other way of getting back control of X / KDE3 than restarting the X server. I've solved it by adding two lines into /etc/NetworkManager/nm-system-settings.conf: |
33 |
> |
34 |
> [keyfile] |
35 |
> hostname=myhostname |
36 |
> |
37 |
> if you don't use networkmanager, there must be some option to pass to your DHCP client so it doesn't overwrite your hostname... I don't think this is kde3 related (cannot connect to X server :0.0), but I might be wrong, never tried it on other DE's. |
38 |
> |
39 |
> Regards, |
40 |
> |
41 |
> Carlos Laué |
42 |
> |