There are a few things going on here that I will address individually.

The main focus I went for with my samples was consistency. Rather than using the SSID of the connection as the heading for wireless status messages, "Wireless network" is used to keep consistency with the use of "Wired network". In addition, "Connection Established" is replaced with a simple "Connected" as that can stay consistent with "Connected to [connection name]". Using "Connected" in place of "Connection Established" also keeps consistency with the "Disconnected" message that currently exists.

In the Network Connections manager below the Wired connections list, a checkbox is added with the label of "Show Wired Connection Names in Notices". By default, this checkbox is not checked. When this option is not checked, a simple "Connected" message will be shown for the wired connection. When this option is checked, the Connection Name is appended to the connected/disconnected message. For example, "Connected to Home Network" and "Disconnected from Home Network".

Notice that I do have a break in consistency with the use of the SSID in the message body for wireless connections rather than the Connection Name. This is due to the fact that it is possible to encounter different networks that have the same SSID. Showing the Connection Name that may differentiate from the SSID and may have been set up by someone else would cause confusion. Thus, I believe a break of consistency will enhance understanding rather than complicate it.

The default Connection Names need to be changed. I suggest that the "Auto" portion is dropped entirely since it is redundant and not that informative. For wired connections that have only one interface, "Local Connection" can be used in place of "eth0". For wired connections that have multiple connections "Local Connection #1", "Local Connection #2", etc can be used.

In order to still provide information about which interface is being used (eth0, eth1, etc), an additional entry inside the Wired tab of the Edit dialog for wired connections could list which interface is being used. This way the information is still readily available, but isn't constantly being shown in a way that would confuse the user.

It is fixed in the notification bubbles, which is what this bug was reported about.

The window you have shown is designed to present multiple wired interfaces, if there are any. Unfortunately, as far as I know, the names like "eth0", "eth1", "eth2" etc are the only unique identifiers we have for them. If there is a better way they could be named, that is something the Linux kernel developers would need to fix.

Exactly. What kernel does is OK, and should not be changed. I meant
the other thing: user can rename NM connections (not interfaces, and I
don't want to rename interfaces!) in the dialog box on the screenshot
I attached above. What I ask is just putting "Wired Connection 1"
instead of "Auto eth0" by default there. I do it somehow manually, and
no real network interfaces are harmed in the process.

Also notification bubble must show the connection name as it is. So
that user know what exactly is connected or disconnected by name she
gave and used to.

If I understand the problem correctly, no modification to notification
bubbles code had to be done. Instead, default way of assigning a
connection name in NetworkManager had to be changed.

This bug seems to have been *wrongly* marked as fixed released.
Confirmed with others that the notifications are still eth0 and as such.
If it is working properly for anyone knidly report back. Thanks!

I really don't see what is wrong with correctly labelling the hardware interface with eth0 and eth1, which would be educational for new users and useful for others. But on my "up-to-date" Ubuntu 9.10 system, something keeps swapping the hardware names eth0 and eth1, and I can have "Auto eth1" connected to "Wired Network (eth0)" and I now have a "Wired Network (eth1rename)" which tries to connect to "eth1_rename" as well. I suspect it is udev and the kernel harware detection order mucking the names up which just confuses "Network Manager" and this user.

Hello guys!Thank you all so much with your assisting emails.I think 'eth'it's from ethernet(a refference for cable connection).Anyway,i've reinstalled Buntu and everything was fine,and now it's making sense to me more and more(to tell you the truth,i'm becoming more satisfied than Windows.Speacking of which,can i get ridd of them,or do they have to co-exist?because they're getting lots of space

Yes dimitris, you should be able to get rid of Windows partitions safely by using gparted and editing GRUB's configuration, but you should send your questions to Ubuntu Forums (ubuntuforums.org) if you need help. This place is for bug discussion only.

Yup, I'll be looking at this one; let's work to get this *really* fixed in Natty.

That said, I see a number of issues. While I agree it seems confusing to designate the connection as "Auto eth0", it really does have a reason to exist: it's an automatically added connection when NM is installed, that uses the eth0 interface to connect. This could easily be changed to something different, like "Default Wired Connection".

Looking at the latest patch applied I'm a little against making changed to tooltips (or other places for that matter) to not display the connection that is being used. In some cases, a user could have different wired connections (such as how to deal with being at work or being at home), and thus removing the connection's name would cause confusion.

Ideally you want to make sure what is written in a tooltip or notification matches the options available in the nm-applet dropdown where you choose the connection.

"Ideally you want to make sure what is written in a tooltip or notification matches the options available in the nm-applet dropdown where you choose the connection."

Yes, agree 100%.

Who cares what the notification says if there's nothing matching it in the nm-applet?

Let's just change the nm-applet words. As comment #16 says, we can all manually change the name of the connection in network manager. All we're asking here is that the default name given to a connection (the same one we can edit ourselves) is not Auto eth0.

> ** Changed in: network-manager
> Status: New => Fix Released
>
> --
> You received this bug notification because you are a member of
> Papercutters, which is subscribed to One Hundred Paper Cuts.
> https://bugs.launchpad.net/bugs/386900
>
> Title:
> "Auto eth0" in notifications is confusing
>
> Status in One Hundred Paper Cuts:
> Triaged
> Status in NetworkManager:
> Fix Released
> Status in Network Manager GNOME Applet:
> New
> Status in “network-manager” package in Ubuntu:
> Triaged
>
> Bug description:
> Hi,
>
> When I first starting using Ubuntu (a couple of years ago) I really
> had to look up what "eth0" was. And I still think this is really
> confusing and potentially scaring for non-tech people.
>
> "Connected to Auto eth0" or "Could not connect to Auto eth0" doesn't
> really sounds that good?
>
> Maybe changing Auto to Standard or Default? Maybe "Connected to wired
> network (eth0)"?
>
> There is surely a more elegant way for fixing this, but my English
> isn't that good.
>
> Thanks

Changes are upstream, the actual notification and name of the connection is in fact "Wired connection 1" (and is translatable, the translation for this has been fixed up in Precise). Closing as Fix Released.