Bug 22513

Summary:	drakconnect picks wrong key when switching to another WiFi AP
Product:	Mageia	Reporter:	Pierre Fortin <pf>
Component:	RPM Packages	Assignee:	Mageia tools maintainers <mageiatools>
Status:	RESOLVED OLD	QA Contact:
Severity:	normal
Priority:	Normal	CC:	marja11, ouaurelien
Version:	6
Target Milestone:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Source RPM:	drakxnet	CVE:
Status comment:

Description Pierre Fortin 2018-02-03 20:27:38 CET

Description of problem:  Working on a network issue; I am switching between 2 routers' WiFi.  When accessing drakconnect via mcc, in case it matters, I see this on the konsole:
Too late to run INIT block at /usr/lib/perl5/vendor_perl/5.22.2/x86_64-linux-thread-multi/Glib/Object/Introspection.pm line 257.
Ignore the following Glib::Object::Introspection & Gtk3 warnings
Subroutine Gtk3::main redefined at /usr/lib/perl5/vendor_perl/5.22.3/Gtk3.pm line 525.

Checking the processes, this is the one:
root     30986  1.9  0.2 296236 74884 pts/3    S    14:10   0:00 /usr/bin/perl /usr/libexec/drakconnect --wizard --embedded 77603253

Version-Release number of selected component (if applicable):
$ drakconnect -v
Drakxtools version 17.88.1


How reproducible: very often


Steps to Reproduce:
1. disconnect from one SSID
2. use mcc->drakconnect to point to another SSID
3. if wrong key appears, going forward will also change the key in /etc/wpa_supplicant.conf
   It must be corrected to continue w/o changing wpa.

Comment 1 Marja Van Waes 2018-02-04 12:08:38 CET

Can't check whether there's an existing bug report about this issue, my connection is too slow. It sounds familiar.

CC: (none) => marja11
Assignee: bugsquad => mageiatools
Source RPM: (none) => drakxnet

Comment 2 Aurelien Oudelet 2020-08-16 16:02:08 CEST

Mageia 6 changed to end-of-life (EOL) status on 2019-09-30. It is no longer 
maintained, which means that it will not receive any further security or bug 
fix updates.

Package Maintainer: If you wish for this bug to remain open because you plan 
to fix it in a currently maintained version, simply change the 'version' to 
a later Mageia version.

Bug Reporter: Thank you for reporting this issue and we are sorry that we 
weren't able to fix it before Mageia 6's end of life. If you are able to 
reproduce it against a later version of Mageia, you are encouraged to click 
on "Version" and change it against that version of Mageia.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a more recent
Mageia release includes newer upstream software that fixes bugs or makes them
obsolete.

If you would like to help fixing bugs in the future, don't hesitate to join the
packager team via our mentoring program [1] or join the teams that fit you 
most [2].

[1] https://wiki.mageia.org/en/Becoming_a_Mageia_Packager
[2] http://www.mageia.org/contribute/

Best regards,
Aurélien
Bugsquad Team

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