Bug 7358

Summary:	Mga3 alpha1 DVD i586 GNOME Enabling network in installer causes gnome to show no connection
Product:	Mageia	Reporter:	claire robinson <eeeemail>
Component:	RPM Packages	Assignee:	Mageia Bug Squad <bugsquad>
Status:	RESOLVED OLD	QA Contact:
Severity:	normal
Priority:	Normal	CC:	ftg, mageia
Version:	3
Target Milestone:	---
Hardware:	i586
OS:	Linux
Whiteboard:
Source RPM:		CVE:
Status comment:
Bug Depends on:
Bug Blocks:	7557
Attachments:	screenshot showing nm

Description claire robinson 2012-09-05 16:04:37 CEST

Pre-release Mga3 alpha 1 DVD i586 with a default Gnome installation. (4th set)

I'm not sure this is actually a bug but it would be confusing for those not aware of the two network tools.

If the network is enabled in the installer then Gnome shows no connection, even though it is actually connected. See screenshot.

The mageia network tool (draknetcentre ?) can be found running at the bottom of the screen, but it isn't immediately obvious and will cause confusion/complaints. It would be better if it was shown at the top, instead of or beside the networkmanager icon.

Comment 1 claire robinson 2012-09-05 16:05:31 CEST

Created attachment 2752 [details]
screenshot showing nm

Manuel Hiebel 2012-09-23 21:20:34 CEST

Blocks: (none) => 7557

Comment 2 Frank Griffin 2012-10-29 13:24:07 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 3 Frank Griffin 2012-10-29 14:28:10 CET

(In reply to comment #2)

n/a here

CC: (none) => ftg

Comment 4 Sander Lepik 2013-02-13 09:04:42 CET

AFAIK installer doesn't know how to use NetworkManager. So the only option to enable network during install is with old tools. But as GNOME can't connect with them then i have no idea how we could fix this. Only option seems to be FAQ/Errata. I hope Mageia 4 will be NM only..

CC: (none) => sander.lepik

Comment 5 claire robinson 2013-02-13 13:33:21 CET

It just needs net applet to display at the top where NM does, rather than hidden at the bottom. Not sure if it's possible but it would save people thinking they had no connection when they likely really do.

Manuel Hiebel 2013-11-30 17:06:24 CET

Version: Cauldron => 3

Comment 6 Marja Van Waes 2015-03-31 16:06:15 CEST

Mageia 3 changed to end-of-life (EOL) status 4 months ago.
http://blog.mageia.org/en/2014/11/26/lets-say-goodbye-to-mageia-3/ 

Mageia 3 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of Mageia
please feel free to click on "Version" change it against that version of Mageia
and reopen this bug.

Thank you for reporting this bug and we are sorry it could not be fixed.

--
The Mageia Bugsquad

Status: NEW => RESOLVED
Resolution: (none) => OLD