Mathieu, _before_ I even tried to connect from the other machine, it was the "server" that was (apparently) failing to create it! That's the problem.
If, like you say, the logs say that the connection was properly established, then it means that there is a problem in network manager that doesn't realise the connection is established and keeps waiting (and showing the connecting icon) forever. Now I'm not sure I even tried to connect to the network from the other machine, because when the first computer (the "server") apparently failed to connect (i.e. "create" the network, being the first), I assumed it had truly failed. When I create an ad hoc network, usually I do the following: 1. On computer A (the one with the issue, the one of the logs), I click on Network Manager's icon, I select "connect to hidden wirless network, I select the ad-hoc network from the list (previously created in edit connections) and I click Connect. 2. From computer B, I usually see the network listed among the available networks, and I select it and connect to it almost as if it was an access point network. The problem is that step 1 sometimes fails, which is nonsense, because no condition needs to be met in order for it to succeed: you're not trying to connect to a network that can be available or unavailable, you're trying to create it. When I say it fails I mean that Network Manager shows the "connecting" icon forever. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/786368 Title: fail to connect to its own ad-hoc wireless network To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/786368/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
