Bug 16360 - Ad-Hoc WiFi access points not usable
Summary: Ad-Hoc WiFi access points not usable
Status: RESOLVED OLD
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 5
Hardware: x86_64 Linux
Priority: Normal major
Target Milestone: ---
Assignee: GNOME maintainers
QA Contact:
URL:
Whiteboard:
Keywords: NEEDINFO
Depends on:
Blocks:
 
Reported: 2015-07-12 21:06 CEST by Dag Nygren
Modified: 2018-10-07 16:39 CEST (History)
2 users (show)

See Also:
Source RPM: networkmanager
CVE:
Status comment:


Attachments

Description Dag Nygren 2015-07-12 21:06:31 CEST
Have an Ad-Hoc Wifi accesspoint with WEP access. Recently upgraded Mageia 5 cannot connect to this. Mageia 4 was perfectly fine.
Comment 1 Dag Nygren 2015-07-13 23:05:50 CEST
Some more testing:
- Tried booting with mga4 kernel - No difference
- Turned off "Manage by Networkmanager" and reboot: Then it works

So it seems like the supplied version of Networkmanager does the
wrong things.
Comment 2 Dag Nygren 2015-07-17 20:03:56 CEST
Also just found that "systemctl disable networkmanager" doesn't disable it for all users. Had to rename the binary.... Sigh...
Comment 3 Marja Van Waes 2016-11-01 17:17:27 CET
@ Dag Nygren,

Sorry for the very late reply. We are short on active BugSquad members.

Could you please attach /root/drakx/report.bug from the time of the upgrade? (It'll need to be compressed, first)

It is unlikely that you still have log files from right after upgrading, but if that doesn't give an nearly empty file, then please do also attach journal.txt that is the result of running, as root:

    journalctl --since=2015-07-12 --until=2015-07-13 > journal.txt

Keywords: (none) => NEEDINFO
CC: (none) => marja11
Assignee: bugsquad => mageiatools

Comment 4 Dag Nygren 2016-11-01 18:35:58 CET
It is really more than a year ago and the logs have been cleaned out a long time ago, so unfortunately I cannot provide either of them. But I can verify that Networkmanager is still not able to connect to an "Ad-Hoc" wireless station.
Killing Networkmanager and resorting to drakconf the connection will work.
Comment 5 Marja Van Waes 2018-05-20 17:31:00 CEST
(In reply to Dag Nygren from comment #4)
> It is really more than a year ago and the logs have been cleaned out a long
> time ago, so unfortunately I cannot provide either of them. But I can verify
> that Networkmanager is still not able to connect to an "Ad-Hoc" wireless
> station.
> Killing Networkmanager and resorting to drakconf the connection will work.

So I had assigned wrongly :-(

Anyway, thank you, Dag Nygren, for having taken the needed time to report this issue and update the report!

Did this bug get fixed? If so, please change its status to RESOLVED - FIXED

If it didn't, then we regret that we weren't able to fix it in Mageia 5. Mageia 5 has officially reached its End of Life on December 31st, 2017 https://blog.mageia.org/en/2017/11/07/mageia-5-eol-postponed/
It only continued to get important security updates since then, because we were waiting for the big Plasma5 update in Mageia 6, that fixed many of the Mageia 5 => 6 upgrade issues.

If you haven't seen that this bug got fixed, then please check whether this bug still exists in Mageia 6. If it does, then please change the Version (near the top, at the left) to "6". If you know it exists in Cauldron, then change Version to Cauldron. If you see it in both Cauldron and Mageia 6, then please set Version to Cauldron and add MGA6TOO on the Whiteboard.

Thanks,
Marja

(In case this report needs to stay open for a supported release: 
Reassigning to the gnome maintainers, since NetworkManager is a Gnome tool.
CC'ing the base system maintainers, because it has "Group: System/Base")

Assignee: mageiatools => gnome
Source RPM: (none) => networkmanager
Component: Release (media or process) => RPM Packages
CC: sysadmin-bugs => basesystem

Comment 6 Marja Van Waes 2018-10-07 16:39:42 CEST
No reply, so closing as OLD since Mageia 5 is no longer maintained.

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


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