Thanks for taking the time to report this issue and make Ubuntu better.
To confirm, did you restart your machine after changing /etc/hostname
and /etc/hosts? Generally speaking changing the hostname without a
restart can cause the issues you're describing, because the previous
hostname is cached in
** Tags added: precise
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1168139
Title:
hostname: No protocol specified and Can't open display errors.
To manage notifications about this bug go to:
http
** Summary changed:
- Changing hostname: *No protocol specified* and *Can't open display* errors.
+ hostname: No protocol specified and Can't open display errors.
** Tags added: display protocol
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed t
** Description changed:
Hi. During trying to change hostname with 'sudo hostname daniel1'
command and after re enable console (hostname is changed), I can not
open any application or edit any files, because of this error;
,-[ hostname error ]
| No protocol specified
| Can't open
** Description changed:
- Hi. During trying to change the hostname in the console with 'sudo
- hostname daniel1' command and after re enable console (hostname is
- changed), I can not open any application or edit any file (through
- console), because of this error;
+ Hi. During trying to change ho
** Project changed: launchpad => ubuntu
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1168139
Title:
hostname: No protocol specified and Can't open display errors.
To manage notifications about thi
