From: ng0 <ng0@infotropique.org>
To: Arun Isaac <arunisaac@systemreboot.net>,
Thomas Danckaert <thomas.danckaert@aeronomie.be>,
help-guix@gnu.org
Subject: Re: networkmanager hostname woes
Date: Fri, 15 Sep 2017 12:34:19 +0000 [thread overview]
Message-ID: <20170915123219.smp45l7r6kf4zo55@abyayala> (raw)
In-Reply-To: <20170915121449.vkikuqpcstotovv7@abyayala>
[-- Attachment #1: Type: text/plain, Size: 1487 bytes --]
ng0 transcribed 2.3K bytes:
> Arun Isaac transcribed 0.8K bytes:
> >
> > Thomas Danckaert writes:
> >
> > > Hi Guix,
> > >
> > > since the change to networkmanager, I've been running into the
> > > following problem: when I connect to a wireless network using
> > > networkmanager, I can no longer start graphical applications
> > > (starting any program fails with “cannot open display :0.0” and
> > > similar messages).
> > >
> > > AFAIU, the cause is that networkmanager changes my hostname (after
> > > DHCP?), in my case to “new-host2” or something similar, and this
> > > seems to break the X session. When I manually restore the hostname
> > > with “sudo hostname <original-hostname>”, the problem is solved. Is
> > > there anyway to disable this behaviour for networkmanager?
> >
> > I have the exact same problem too. If somebody has a solution, I'd like
> > to hear about it.
>
> I don't understand your problem. This is public documented behavior of
> NM.
> Assuming that we build networkmanager with dhclient option/configure:
>
> add to /etc/dhcp/dhclient.conf:
>
> send host-name "yourhostname";
>
>
> This always worked for me on Gentoo.
I read the full thread again, our problem might be different
but providing this file might be a fix which could work.
--
ng0
GnuPG: A88C8ADD129828D7EAC02E52E22F9BBFEE348588
GnuPG: https://krosos.org/dist/keys/
https://www.infotropique.org https://www.krosos.org
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2017-09-15 12:35 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-13 10:05 networkmanager hostname woes Thomas Danckaert
2017-09-13 17:01 ` Christopher Baines
2017-09-13 23:27 ` Arun Isaac
2017-09-14 6:38 ` Christopher Baines
2017-09-15 12:14 ` ng0
2017-09-15 12:34 ` ng0 [this message]
2017-09-16 6:57 ` Thomas Danckaert
2017-09-16 8:11 ` ng0
[not found] ` <87h8w6ha74.fsf@gmail.com>
2017-09-14 7:50 ` Thomas Danckaert
2017-09-14 8:17 ` Ludovic Courtès
2017-09-15 10:12 ` Thomas Danckaert
2017-09-15 20:34 ` Ludovic Courtès
2017-09-16 12:03 ` Thomas Danckaert
2017-09-19 12:06 ` Ludovic Courtès
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170915123219.smp45l7r6kf4zo55@abyayala \
--to=ng0@infotropique.org \
--cc=arunisaac@systemreboot.net \
--cc=help-guix@gnu.org \
--cc=thomas.danckaert@aeronomie.be \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).