Bug 2713 - Drakconnect connection error message is an inappropriate time out.
Summary: Drakconnect connection error message is an inappropriate time out.
Status: RESOLVED OLD
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: All Linux
Priority: Normal enhancement
Target Milestone: ---
Assignee: Olivier Blin
QA Contact:
URL:
Whiteboard: MGA2TOO
Keywords:
Depends on:
Blocks:
 
Reported: 2011-09-12 12:49 CEST by Thomas Lottmann
Modified: 2015-04-19 14:13 CEST (History)
1 user (show)

See Also:
Source RPM: drakx-net
CVE:
Status comment:


Attachments

Description Thomas Lottmann 2011-09-12 12:49:29 CEST
Hello,
 
Drakroam and Draknetcenter show very frequently an error message while the tool still tries to connect to a wireless hotspot. 

Whatever happens, if the tool has not connected to the hotspot in a setted amount of seconds, it would show the very explicit 'Connection error' message. Generally, the little NetApplet dialog telling we are finally conencted to the hotspot appears soon after. 

Solution:
Drakconnect (or whatever wireless tool that is) should *listen* to NetApplet, as he should know :
- when the connection attempt has started
- at what state the connection process is
- when the connection has succeeded or failed. 

Thank you.
Thomas Lottmann 2011-09-14 12:18:39 CEST

Summary: Error message is an inappropriate time out. => Drakconnect connection error message is an inappropriate time out.

Comment 1 Manuel Hiebel 2011-10-25 11:02:07 CEST
Bug assigned to the package maintainer.

Assignee: bugsquad => mageia

Manuel Hiebel 2012-10-31 20:12:23 CET

Version: 1 => Cauldron
Whiteboard: (none) => MGA2TOO

Comment 2 Marja Van Waes 2015-04-19 14:13:24 CEST
Sorry, but this bug saw no action since more than 2 yrs ago. 
No cauldron package has stayed the same since then.

Closing as OLD

Please reopen if this report is still valid for _current_ cauldron and/or fully
updated Mageia 4

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


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