Bug 7551 - systemd: upower& Networkmanager inactive after resume
Summary: systemd: upower& Networkmanager inactive after resume
Status: RESOLVED OLD
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: x86_64 Linux
Priority: Normal major
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on: 7498
Blocks: 7557
  Show dependency treegraph
 
Reported: 2012-09-23 06:34 CEST by Valery Pipin
Modified: 2015-04-14 20:19 CEST (History)
5 users (show)

See Also:
Source RPM:
CVE:
Status comment:


Attachments

Description Valery Pipin 2012-09-23 06:34:28 CEST
I found that services  upower and Networkmanager are inactive after resume. So I have to restart them manually to get the internet or to use suspend&hibernate.

I'm using KDE. In LXDE I have similar problems
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

Comment 1 Frank Griffin 2012-10-29 13:24:10 CET
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.
Comment 2 Frank Griffin 2012-10-29 14:53:32 CET
(In reply to comment #1)

n/a here

CC: (none) => ftg

Comment 3 Marja Van Waes 2015-04-14 20:19:28 CEST
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
Resolution: (none) => OLD


Note You need to log in before you can comment on or make changes to this bug.