nm-no-connection icon should not be wireless / signal strength if system has no (activated) wireless device

Bug #356448 reported by Nicolas DERIVE
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
network-manager-applet (Ubuntu)
Won't Fix
Low
Alexander Sack

Bug Description

In latest jaunty, network-manager gnome displays an inappropriate icon when there are no network available. It's the one for 0% strength wireless signal with a red cross on it, but in the case of an ethernet only computer (without wireless), it's a non-sense to use it. Maybe should it be a different one in this specific but very frequent case ? No need of a very complex one, but the appropriate one.

Revision history for this message
Alexander Sack (asac) wrote :

yes, this is an explicit design decision which was also discussed on mailing list; in the end its nothing that will be fixed for jaunty as similar argument was true if you didnt use wired before (and nowadays lots of users dont get their hands on wired anymore).

We will most likely redesign lots of things for karmic (9.10); at least we will ensure that if there is no wireless device, that you will get something more "wired"-like as disconnect icon.

summary: - No network icon shoudn't be linked to an idea of signal strength or
- wireless
+ nm-no-connection icon should not be wireless / signal strength if system
+ has no (activated) wireless device
Changed in network-manager-applet (Ubuntu):
assignee: nobody → Alexander Sack (asac)
importance: Undecided → Low
status: New → Triaged
milestone: none → later
status: Triaged → In Progress
Revision history for this message
Mat Tomaszewski (mat.t.) wrote :

This problem seems to have reoccurred in Karmic.

Changed in network-manager-applet (Ubuntu):
status: In Progress → New
Revision history for this message
Alexander Sack (asac) wrote :

problem is that we just use nm-no-connection for disconnected; human-icon-theme overrides that with the wireless + red cross icon. IMO it was never fixed.

Do we really want a solution? I don't think upstream would buy into such a change and carrying around another patch forever does not sound like the best way to move forward.

Revision history for this message
Alexander Sack (asac) wrote :

setting to wont fix according to previous comment.

Changed in network-manager-applet (Ubuntu):
status: New → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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