Bug 425434

Summary: Network Manager Icon and details of Applet
Product: [openSUSE] openSUSE 11.0 Reporter: Scott Couston <scott>
Component: NetworkAssignee: Will Stephenson <wstephenson>
Status: RESOLVED FIXED QA Contact: E-mail List <qa-bugs>
Severity: Normal    
Priority: P5 - None CC: scott
Version: Final   
Target Milestone: ---   
Hardware: x86-64   
OS: openSUSE 11.0   
Whiteboard:
Found By: Customer Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---
Bug Depends on:    
Bug Blocks: 508513    
Attachments: screen shot

Description Scott Couston 2008-09-11 10:26:25 UTC
The new Network Manager Desktop icon no longer shows IP number, Subnet Number,Active Link or any other usable information - It has changed into a way of configuration of Network Manager which is done via Yast.
The Desktop Applet can now change the Network IP, wired or wireless connections etc.
How about the applet being able to show some meaningful data without forcing us to the command line again!!

This Desktop Applet has gone backwards as an Applet in it offers no current information about the PC.
Comment 2 Christian Zoz 2008-10-15 13:25:24 UTC
This does not look like a bug report but more like a feature request.
Tambet, please have a look at it.

Scott, I would recommend you to ask that directly on the NM-developers mailing list.
Comment 3 Tambet Ingo 2008-10-15 13:35:25 UTC
I don't really understand the problem. There's no removed functionality, everything you mention is still there.
Comment 4 Scott Couston 2008-10-15 20:39:29 UTC
Agree if the was no loss in functionality I have no issue.
Its a bug because of removal of functionality - The icon that sits in the system tray does not provide any information that was present in 10.3 - It does not even provide an IP number and netmask and DNS servers that are configured by Network Manager in Yast.
If you want to retain current and past functionality this could be done easily by right and left click on Applet
Comment 5 Scott Couston 2008-10-15 20:41:01 UTC

*** This bug has been marked as a duplicate of bug 423881 ***
Comment 6 Scott Couston 2008-10-15 20:41:55 UTC
Re comment 3 - What rubbish!
Comment 7 Tambet Ingo 2008-10-20 06:55:56 UTC
Comment #3 was about NetworkManager-gnome.
Comment 9 Scott Couston 2009-04-26 04:22:02 UTC
Dependant on bugs 
https://bugzilla.novell.com/show_bug.cgi?id=423881
https://bugzilla.novell.com/show_bug.cgi?id=489542
https://bugzilla.novell.com/show_bug.cgi?id=498307
If this bug had been actioned in 10.3 we would not be having all the dependant and consequential bugs listed above bugs above.

This was the first bug opened that would restore the Network Manager's Original Applet and above details and we would not be facing continual issues with current bugs where there is no control over the Network Connection if a user chooses Network Manager in stead of IFUP.

I have re-opened purely so that current programers can see what functions the original Applet had and how they were removed in 10.3 to create the horrible situation we are in with other dependant bugs. We can start by restoring the 10.2 applets design and then go to fix the other issues associated with Network Manager in the above references.
Comment 10 Scott Couston 2009-04-26 18:02:55 UTC
Created attachment 288225 [details]
screen shot
Comment 11 Scott Couston 2009-04-26 18:06:12 UTC
#10 ...There is yet another way of controlling the Network Connection via Kcontrol....Our problem now is which one do we focus on an fix to be able to use Network Manager and have it auto connect and has the ability to provide right click meaning data as in 10.2
Comment 12 Scott Couston 2009-05-27 22:08:36 UTC
*** Bug 423881 has been marked as a duplicate of this bug. ***
Comment 13 Scott Couston 2009-07-07 23:13:07 UTC
QA - Bug seems to be inactive in Assignment
Comment 14 Will Stephenson 2009-09-16 09:36:33 UTC
knetworkmanager4 can show the following information in the tooltip


 "interface:type" <<
 "interface:name" << 
"interface:driver" << 
"interface:status"
"interface:designspeed" << 
"interface:hardwareaddress" << 
"interface:bitrate"
 "ipv4:address" << 
"ipv4:nameservers" << 
"ipv4:domains" << 
"ipv4:routes"
"wired:carrier"
 "wireless:strength" << 
"wireless:ssid" << 
"wireless:mode" << 
"wireless:accesspoint"
"wireless:security"
<< "wireless:rsnflags"
"wireless:frequency"
 "cellular:strength"
"cellular:network"
Comment 15 Scott Couston 2009-09-16 10:23:34 UTC
By Tooltip do you mean a simple right clock on the Icon in the system tray that was removed back in 10.3 and replaced by no relevant information what so ever.
In 10.3 NM Icon a simple right click displayed
Eth0 connection if only active but included VPN or WIFI depending on the active connection type.
DHCP or Manual IP
IP number
Subnet
DNS Servers x 2 if Present
Gateway IP if present
RX packets received
TX packets sent

All this information disappeared without reason between 10.3-11.0 from memory. This bug has been progressiveness open since I believe 10.3 in one form or another, simply to replace the information that the right click offered which was removed without technical reasoning.
Regards - I am happy to have this left as resolved an fixed as you have indicated. From a person perspective I can still not believe it has taken such a lengthy process just to put back what information was removed without logical nor functional reason for over 3 different releases of Opensuse. I am sure you can realise the user frustration at very simple requests to reinstate what what once present by a simple right click.
Comment 16 Will Stephenson 2009-09-16 10:54:47 UTC
I have posted https://bugs.kde.org/show_bug.cgi?id=207425 as a Junior Job to reimplement this dialog containing the RX/TX bytes and connection time.  The rest of the info is shown as a tooltip on active connections - click the system tray icon to show the status popup, then simply hover the mouse over the connection.  When there can be multiple connections active at the same time, this is IMO a more elegant and less clicky solution than a top level menu item showing a dialog containing a tab for each connection.
Comment 17 Scott Couston 2009-09-17 08:36:35 UTC
I could not agree more Will in comment #16 and I am so glad that after much personal effort and disappointed by having this issue open since the details vanished in 10.3, is has now been corrected. Many Thanks