| Summary: | systemd: upower& Networkmanager inactive after resume | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Valery Pipin <pip> |
| Component: | RPM Packages | Assignee: | Mageia Bug Squad <bugsquad> |
| Status: | RESOLVED OLD | QA Contact: | |
| Severity: | major | ||
| Priority: | Normal | CC: | dmorganec, ftg, mageia, mitya, olav |
| Version: | Cauldron | ||
| Target Milestone: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | CVE: | ||
| Status comment: | |||
| Bug Depends on: | 7498 | ||
| Bug Blocks: | 7557 | ||
|
Description
Valery Pipin
2012-09-23 06:34:28 CEST
Manuel Hiebel
2012-09-23 20:44:58 CEST
CC:
(none) =>
dmorganec, mageia, mitya, olav
Manuel Hiebel
2012-09-23 20:59:04 CEST
Depends on:
(none) =>
7498
Manuel Hiebel
2012-09-23 21:20:34 CEST
Blocks:
(none) =>
7557 Please refer to the discussion in bug#7873 and bug#2160 and see if your problems with NM go away if you either allow GNOME (if you have it installed) to activate it or you install plasma-network-management under KDE, add it to your panel, and use it to configure your SSID. For NM to handle wireless correctly, it needs to create SSID-specific files of its own by parsing the ifcfg files produced by drakconnect. GNOME's nm-applet does this automatically, since it has no option to *not* use NM, but since NM isn't the default yet for other desktops, it doesn't happen automatically there. You'll need to install NM and let it start, and recreate your wireless interface with drakconnect specifying "Allow NM to control this interface". Please test and post your results, as whether NM works for all the chips involved when it's properly configured will have a significant impact on how it needs to be handled for non-GNOME desktops in MGA3. No action since over 2 yrs ago and still assigned to Bug Squad Closing as OLD Please reopen if this report is still valid for _current_ cauldron and/or fully updated Mageia 4 Status:
NEW =>
RESOLVED |