| Summary: | Add to Network Manager plasmoid Killswitch-Manager functional | ||
|---|---|---|---|
| Product: | [Plasma] plasma4 | Reporter: | RussianNeuroMancer <russianneuromancer> |
| Component: | widget-misc | Assignee: | Will Stephenson <wstephenson> |
| Status: | RESOLVED FIXED | ||
| Severity: | wishlist | CC: | evotopid, lamarque, nate |
| Priority: | NOR | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Ubuntu | ||
| OS: | Unspecified | ||
| Latest Commit: | Version Fixed In: | ||
| Attachments: | Acer Launch Manager | ||
|
Description
RussianNeuroMancer
2010-03-29 09:39:46 UTC
The "Enable Wireless" button calls NetworkManager which calls rfkill to enable wireless cards. Created attachment 63063 [details]
Acer Launch Manager
Please look carefully into this feature request once again: > The "Enable Wireless" button calls NetworkManager which calls rfkill to enable wireless cards. Yes, I know that. But from user point of view this is wrong scenario for most of laptops. "Wireless" button shouldn't just enable/disable WiFi. If laptop have not only WiFi but also Bluetooth (and maybe Mobile Broadboand (3G/4G/WiMax) modem) in Windows this button call utility where user can enable or disable WiFi, Bluetooth or Mobile Broadboand modem. Examples: Lenovo IdeaPad: http://forum.lenovo.com/t5/image/serverpage/image-id/3425iE2C3E089BE7158CA/image-size/original?v=mpbl-1&px=-1 Lenovo ThinkPad: http://img-novosib.fotki.yandex.ru/get/4312/kgmobile.7/0_411aa_94d5b12f_XL http://regmedia.co.uk/2008/05/01/lenovo_x300_8.jpg Sony VAIO: http://www.notik.ru/img/Sony_VAIO_VPC-EE3M1R_BQ_VAIO_Smart_Network_b.png Acer: attached screenshoot. So I propose to implement something similar in Network Management plasmoid - window that should appear on the screen when user press XF86WLAN hardware button - please open attached screenshoot. Sure when there is only WiFi, and no Bluetooth or Mobile Broadboand modem we can just enable/disable WiFi and not show any window on the screen (because there is only one item anyway). I didn't sure, maybe Network Management plasmoid is not the right place to implement such functional and that should be implemented as separate plasmoid or as Plasma feature. In this case can you please reassign this feature request to the right project? Plasma NM is not the right place to implement this and such plasmoid will conflict with NM: if you have wireless working, block the wifi card with rfkill the NM's auto-connect feature will not work until you unblock it. NM will not send any information to Plasma NM as to why the auto-connect is not working. > if you have wireless working, block the wifi card with rfkill
the NM's auto-connect feature will not work until you unblock it
So then WiFi should be enabled/disabled not with rfkill but with Network Manager (if it's available in the system). I am correct?
(In reply to comment #5) > > if you have wireless working, block the wifi card with rfkill > the NM's auto-connect feature will not work until you unblock it > > So then WiFi should be enabled/disabled not with rfkill but with Network > Manager (if it's available in the system). I am correct? Yes, using only one program to control wifi is the best option in my oppinion. Wireless toggle functionality seems to have been implemented in the current version of Plasma, and is triggered by the XF86WLAN key, however it is not user configurable as of now. Also see bug #349744. (I don't think it's an exact duplicate, since this bug is asking for a fully featured killswitch-manager and the other is about the by now present airplane mode toggle.) Yep, a basic version is now implemented in Plasma 5. Please file new tickets against it with specific bug reports/feature requests. |
