Bug 338952 - Unable to access NM plasmoid from System Tray if icon is hidden
Summary: Unable to access NM plasmoid from System Tray if icon is hidden
Status: RESOLVED DUPLICATE of bug 301424
Alias: None
Product: plasma-nm
Classification: Plasma
Component: applet (show other bugs)
Version: 0.9.3.4
Platform: Debian testing Linux
: NOR normal
Target Milestone: ---
Assignee: Jan Grulich
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-09-09 16:39 UTC by Brendon Higgins
Modified: 2014-09-11 08:06 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Brendon Higgins 2014-09-09 16:39:53 UTC
Hi,

Not sure if my terminology is correct, but I'll describe best I can: I wish to hide the NM icon from my System Tray as I use it infrequently on my desktop. But I don't want to remove it completely, because sometimes I need to log in to a VPN. So in the System Tray settings under "Entries" I set the visibility of Network Management to "Hidden". The icon then goes out of the main tray and into the menu that pops up when I left-click the little up-arrow at the right of the System Tray.

This would be perfect, except that if I click the up-arrow and then left-click the NM icon, nothing happens. I would expect the NM plasmoid to pop up like it does when the icon is not hidden. Compare to e.g. the Device Notifier, which does pop up when left-clicked. The way it currently works, hiding the NM icon has as much usefulness as removing the icon entirely.

Reproducible: Always

Steps to Reproduce:
1. In System Tray settings, Entries, set Network Management visibility to Hidden.
2. Bring up the hidden icons (press the little up arrow).
3. Left click on the NM icon.

Actual Results:  
Nothing happens.

Expected Results:  
The NM plasmoid window should pop up like it does when the icon is not hidden from the system tray. The Device Notifier does it this way.
Comment 1 Jan Grulich 2014-09-11 08:06:04 UTC

*** This bug has been marked as a duplicate of bug 301424 ***