Bug 383032

Summary: multiple knetworkmanager icons
Product: [openSUSE] openSUSE 11.0 Reporter: Quentin Jackson <quentin.jackson>
Component: NetworkAssignee: Will Stephenson <wstephenson>
Status: RESOLVED FIXED QA Contact: E-mail List <qa-bugs>
Severity: Minor    
Priority: P5 - None CC: aidanjt, amantia, aos, forgotten_zhFaldehF_, fvzwieten, spiffytech, stefan1975, wstephenson, zeiglerr
Version: Factory   
Target Milestone: ---   
Hardware: x86-64   
OS: openSUSE 11.0   
Whiteboard:
Found By: Customer Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---

Description Quentin Jackson 2008-04-23 21:38:21 UTC
I didn't notice it yesterday, but today I have three knetwork manager icons.  One has 'disable wireless' and switch to offline mode' in it (its a green planet), one is for eth0 and one has a whole bunch of wireless networks in it (which don't work anyway) and also has deactivate device in it (though it's greyed out for some reason).  Forgive me if this is some decision that has been made but I don't see the need to go from one icon to three, one for each device maybe, but three?
Comment 1 Helmut Schaa 2008-04-24 07:46:40 UTC
One icon for each device and one icon for inter-device-stuff (e.g. "Disable Wireless" will disable all wireless devices). It is not uncommon to have more then the typical two devices (Wired + Wireless).

"Deactivate Device" is grayed out because you do not have an active connection.

Perhaps we are going to change the icon layout but there are more severe issues to work on first.
Comment 2 Helmut Schaa 2008-05-02 18:40:32 UTC
Lowering severity.
Comment 3 Helmut Schaa 2008-05-19 06:40:54 UTC
*** Bug 391789 has been marked as a duplicate of this bug. ***
Comment 4 Stephan Binner 2008-05-21 08:33:11 UTC
*** Bug 392975 has been marked as a duplicate of this bug. ***
Comment 5 Will Stephenson 2008-05-21 08:35:34 UTC
*** Bug 392788 has been marked as a duplicate of this bug. ***
Comment 6 Will Stephenson 2008-05-21 16:56:00 UTC
*** Bug 393220 has been marked as a duplicate of this bug. ***
Comment 7 Will Stephenson 2008-05-21 16:56:58 UTC
maybe this will help people find this bug report
Comment 8 Andrew Sorensen 2008-05-21 17:07:38 UTC
> maybe this will help people find this bug report
hope so
Comment 9 Fred van Zwieten 2008-05-21 17:57:05 UTC
Look at Windows for inspiration. In the network configuration screen, one can specify per interface is a tray icon must be shown. From these icons, the same config screen is accessable. If there a no knetwork icons in the tray, the config screen is accesable as a module in system settings. Much better and more logical imho.
Comment 10 Stephan Binner 2008-06-01 08:02:57 UTC
*** Bug 395841 has been marked as a duplicate of this bug. ***
Comment 11 stefan van ruiten 2008-06-01 19:52:01 UTC
i was about to file a bug report for this when I noticed this one. What I see is that a lot of duplicates are being closed, but will something be done about this? I would REALLY like just one NM tray icon, with that insane panel that is KDE4 and 4 virtual desktops, a Huge clock, etc, etc. space is sparce as it is and I can view just two/three active apps in my panel. Further I like my tray icons as clean as possible, so could we be informed if anything will be done about this please? And if yes are we aiming for a 11 GM release date or later on?

thanks a lot,
stefan
Comment 12 Stephan Binner 2008-06-02 04:33:56 UTC
*** Bug 396249 has been marked as a duplicate of this bug. ***
Comment 13 Forgotten User zhFaldehF_ 2008-06-02 15:03:48 UTC
I honestly don't think enough is made of this bug and really hope that it is fixed for 11.0 GM. 

So many users will be confused w/ 3 different knetworkmanager management points (1 for Wireless, 1 for Wired, 1 for KNetworkManager configuration). 
Comment 14 Will Stephenson 2008-06-02 22:08:45 UTC
Fixed for GMC
Comment 15 Forgotten User zhFaldehF_ 2008-06-03 02:03:07 UTC
(In reply to comment #14 from William Stephenson)
> Fixed for GMC
> 

Any idea when this will show up in the oss factory repo? I would like to test to see if there are any regressions on my system since there is no other scheduled RC's. 

Thank you

Ben
Comment 16 Novell Build 2016-05-10 19:18:31 UTC
This fix is in the Messenger Linux Client 3.0.4 build 20160510131611.  Source revision 6084.