[Bug 386900] Re: Auto eth0 confusing for most people
In an up-to-date Karmic, the nm-applet still says 'auto eth0'. ** Attachment added: auto eth0.png http://launchpadlibrarian.net/34900581/auto%20eth0.png -- Auto eth0 confusing for most people https://bugs.launchpad.net/bugs/386900 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 386900] Re: Auto eth0 confusing for most people
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. -- Auto eth0 confusing for most people https://bugs.launchpad.net/bugs/386900 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 386900] Re: Auto eth0 confusing for most people
How about making the connection name of auto eth0 by default Wired Connection 1, and eth1 Wired Connection 2, and so on? same could be done if we have multiple wireless adapters. -- Auto eth0 confusing for most people https://bugs.launchpad.net/bugs/386900 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 386900] Re: Auto eth0 confusing for most people
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. -- Auto eth0 confusing for most people https://bugs.launchpad.net/bugs/386900 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 386900] Re: Auto eth0 confusing for most people
Are you sure the fix is released? How about this screenshot from Ubuntu-9.10 rc? ** Attachment added: Result of a thorough fix http://launchpadlibrarian.net/34297630/Screenshot-Network%20Connections.png -- Auto eth0 confusing for most people https://bugs.launchpad.net/bugs/386900 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 386900] Re: Auto eth0 confusing for most people
In Karmic this is now Wired Network Connection Established ** Changed in: hundredpapercuts Status: In Progress = Fix Released ** Changed in: network-manager (Ubuntu) Status: Triaged = Fix Released ** Changed in: network-manager Status: New = Fix Released -- Auto eth0 confusing for most people https://bugs.launchpad.net/bugs/386900 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 386900] Re: Auto eth0 confusing for most people
I think using the name of the hardware can be even more confusing, at least for non-technical people. The recommendation of not using numbers when there is only one connection is also a valid point. -- Auto eth0 confusing for most people https://bugs.launchpad.net/bugs/386900 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 386900] Re: Auto eth0 confusing for most people
How about the title of the notification is [Wired|Wireless] Network Connected and the body has Via [Hardware name] (eth0) -- Auto eth0 confusing for most people https://bugs.launchpad.net/bugs/386900 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 386900] Re: Auto eth0 confusing for most people
Here is a list of what I think would work well and create a consistent, easily-understood interface. Wired connection (default settings): Wired network Connected Wired connection (Show Wired Connection Names in Notices enabled): Wired network Connected to [connection name] Wireless connection: Wireless network Connected to [SSID] 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. -- Auto eth0 confusing for most people https://bugs.launchpad.net/bugs/386900 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 386900] Re: Auto eth0 confusing for most people
Should it use the name of the hardware? I think NetworkManager does that already for some usb controllers. For network controllers on the PCI bus, the connection could be named from the output of the command: $ lspci | grep Ethernet | cut -d':' -f3 Attached is a screenshot of what this would look like. ** Attachment added: Network_Connections.png http://launchpadlibrarian.net/30683996/Network_Connections.png -- Auto eth0 confusing for most people https://bugs.launchpad.net/bugs/386900 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 386900] Re: Auto eth0 confusing for most people
** Changed in: hundredpapercuts Milestone: round-10 = round-9 -- Auto eth0 confusing for most people https://bugs.launchpad.net/bugs/386900 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 386900] Re: Auto eth0 confusing for most people
agreed with Mr. Mallea -- Auto eth0 confusing for most people https://bugs.launchpad.net/bugs/386900 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 386900] Re: Auto eth0 confusing for most people
forwarded upstream. ** Bug watch added: GNOME Bug Tracker #587844 http://bugzilla.gnome.org/show_bug.cgi?id=587844 ** Changed in: network-manager Importance: Undecided = Unknown ** Changed in: network-manager Status: New = Unknown ** Changed in: network-manager Remote watch: None = GNOME Bug Tracker #587844 ** Changed in: network-manager (Ubuntu) Status: Confirmed = Triaged ** Changed in: network-manager (Ubuntu) Importance: Undecided = Wishlist -- Auto eth0 confusing for most people https://bugs.launchpad.net/bugs/386900 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 386900] Re: Auto eth0 confusing for most people
** Changed in: network-manager Status: Unknown = New -- Auto eth0 confusing for most people https://bugs.launchpad.net/bugs/386900 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 386900] Re: Auto eth0 confusing for most people
** Changed in: network-manager (Ubuntu) Status: New = Confirmed -- Auto eth0 confusing for most people https://bugs.launchpad.net/bugs/386900 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 386900] Re: Auto eth0 confusing for most people
I think most people use just one connection, so the default name shouldn't include a number. It's confusing since it leads too easily to look for another connections. -- Auto eth0 confusing for most people https://bugs.launchpad.net/bugs/386900 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 386900] Re: Auto eth0 confusing for most people
On Mon, Jun 22, 2009 at 02:51:01PM -, Mat Tomaszewski wrote: Alexander, is this something you can have a look at? Cheers Current suggestion of user experience team is to name those connections Wired network [X] .. where X is a number when you have multiple wired NICs - Alexander -- Auto eth0 confusing for most people https://bugs.launchpad.net/bugs/386900 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 386900] Re: Auto eth0 confusing for most people
** Changed in: hundredpapercuts Assignee: Mat Tomaszewski (mat.t.) = (unassigned) -- Auto eth0 confusing for most people https://bugs.launchpad.net/bugs/386900 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 386900] Re: Auto eth0 confusing for most people
We should move this to a later milestone ( 8-10 ) as the expectation is that this will be fixed by upstream and picked up by us later in the Karmic cycle. Also, please note that this is related to bug #386407, that I recently entered about Auto being used as a prefix all over the place. -- Auto eth0 confusing for most people https://bugs.launchpad.net/bugs/386900 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 386900] Re: Auto eth0 confusing for most people
** Changed in: hundredpapercuts Milestone: round-1 = round-10 -- Auto eth0 confusing for most people https://bugs.launchpad.net/bugs/386900 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 386900] Re: Auto eth0 confusing for most people
** Also affects: network-manager (Ubuntu) Importance: Undecided Status: New -- Auto eth0 confusing for most people https://bugs.launchpad.net/bugs/386900 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 386900] Re: Auto eth0 confusing for most people
Alexander, is this something you can have a look at? Cheers ** Changed in: network-manager (Ubuntu) Assignee: (unassigned) = Alexander Sack (asac) -- Auto eth0 confusing for most people https://bugs.launchpad.net/bugs/386900 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
