Ubuntu

Changing hostname to hostname² prevents dcopserver from loading

Bug #346503 reported by Jon D.
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Ubuntu
Invalid
Undecided
Unassigned

Bug Description

This is in Ubuntu 8.04.2. Gnome environment.

I changed my hostname from "Redux" to "Redux²".

Upon restart of X, Akregator & Kate no longer load. They give this error in terminal:

____
/usr/bin/iceauth: /tmp/dcopPfMg8b:1: bad "add" command line
/usr/bin/iceauth: /tmp/dcopPfMg8b:2: bad "add" command line
DCOPClient::attachInternal. Attach failed Authentication Rejected, reason : None of the authentication protocols specified are supported and host-based authentication failed
ICE Connection rejected!

DCOPClient::attachInternal. Attach failed Authentication Rejected, reason : None of the authentication protocols specified are supported and host-based authentication failed
DCOPServer self-test failed.
ICE Connection rejected!

kdeinit: DCOPServer could not be started, aborting.
____

Amarok also gives the above error in the terminal, but also shows a window with the following error: (It loads in the end, but the tray icon floats out of the Gnome-tray)

____
There was an error setting up inter-process communications for KDE. The message returned by the system was:

Could no read network connection list.
~/.DCOPserver_Redux²__0

Please check that the "dcopserver" program is running!
____

Loading just dcopserver from the terminal gives me this:

____
/usr/bin/iceauth: /tmp/dcopPfMg8b:1: bad "add" command line
/usr/bin/iceauth: /tmp/dcopPfMg8b:2: bad "add" command line
DCOPClient::attachInternal. Attach failed Authentication Rejected, reason : None of the authentication protocols specified are supported and host-based authentication failed
ICE Connection rejected!

DCOPClient::attachInternal. Attach failed Authentication Rejected, reason : None of the authentication protocols specified are supported and host-based authentication failed
DCOPServer self-test failed.
ICE Connection rejected!
____

See original description
Jon D. (minig)
description: updated
Revision history for this message
Ryan Parrish (ryanparrish) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better.

Putting extended ascii characters is really not a Good Idea™, many applications will not expect this when they parse your hostname.

See RFC1178 "Choosing a Name for Your Computer" http://tools.ietf.org/html/rfc1178
Don't use non-alphanumeric characters in a name.

         Your own computer may handle punctuation or control characters
         in a name, but most others do not. If you ever expect to
         connect your computer to a heterogeneous network, you can count
         on a variety of interpretations of non-alphanumeric characters
         in names. Network conventions on this are surprisingly
         nonstandard.

and http://tools.ietf.org/html/rfc3696#section-2 for a more in depth reasoning.

If you set your hostname back to plain 'hostname' (or any other alpha-numeric name) does the issue resolve itself?

Revision history for this message
Jon D. (minig) wrote :

Ah, the linked guide makes sense. Thank you for the tip on that.

After setting my hostname back to a standard alpha-numeric name, it does resolve itself. (I did find a bug the first time that I did this, in which when changing the hostname caused /etc/rc2.d/S12dbus to be removed, but have been unable to replicate it yet. I'll report another bug, if needed, upon finding the cause though.)

Revision history for this message
Ryan Parrish (ryanparrish) wrote :

This bug report is being closed due to your last comment regarding this being fixed by changing the hostname back. For future reference you can manage the status of your own bugs by clicking on the current status in the yellow line and then choosing a new status in the revealed drop down box. You can learn more about bug statuses at https://wiki.ubuntu.com/Bugs/Status . Thank you again for taking the time to report this bug and helping to make Ubuntu better. Please submit any future bugs you may find.

Revision history for this message
Jon D. (minig) wrote :

No problem.

Out of curiosity, might there be a warning added that appears upon the input of a non-alphanumeric character when the hostname is being changed in the network manager so as to alleviate future issues?

Revision history for this message
Ryan Parrish (ryanparrish) wrote :

That's a pretty good point.
I would suggest filing a new bug under the network-manager package as there should be some sanity checks in its input fields. Please reference this bug 346503 in the new report.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.