[Bug 786368] Re: fail to connect to its own ad-hoc wireless network

2011-08-16 Thread matteo sisti sette
I can't understand why bugs expire at all. If nobody fixes them within a period of time, then they are not worth fixing? -- 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

[Bug 786368] Re: fail to connect to its own ad-hoc wireless network

2011-08-15 Thread Launchpad Bug Tracker
[Expired for network-manager (Ubuntu) because there has been no activity for 60 days.] ** Changed in: network-manager (Ubuntu) Status: Incomplete = Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 786368] Re: fail to connect to its own ad-hoc wireless network

2011-06-16 Thread Mathieu Trudel-Lapierre
matteo, I can see nothing wrong with what's going on in the logs you added. I believe this was taken from the server machine which created the ad- hoc connection? It would be helpful if you could also attach /var/log/syslog from the machine from which you try to connect to the ad-hoc network, so

[Bug 786368] Re: fail to connect to its own ad-hoc wireless network

2011-06-16 Thread matteo sisti sette
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

[Bug 786368] Re: fail to connect to its own ad-hoc wireless network

2011-06-16 Thread Mathieu Trudel-Lapierre
No, adhoc connections can fail. For instance, not all wireless devices supporting sending the IBSS beacons necessary to advertise adhoc networks. The fact that the icon shows as connecting forever is probably an indication that this is the case. Regardless, the network should remain in some form

[Bug 786368] Re: fail to connect to its own ad-hoc wireless network

2011-06-16 Thread matteo sisti sette
But this only happens some times, randomly. Then I abort, I try again and most of the times it works. I guess this discards the first hipothesis: For instance, not all wireless devices supporting sending the IBSS beacons necessary to advertise adhoc networks. -- You received this bug

[Bug 786368] Re: fail to connect to its own ad-hoc wireless network

2011-05-21 Thread matteo sisti sette
-- 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 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com

[Bug 786368] Re: fail to connect to its own ad-hoc wireless network

2011-05-21 Thread Kangarooo
Yes thats true been like that for at least 1y when i tryd to make thrue Edit connections its doesnt work and doesnt start automaticaly. Left clicking and making new connection Works and connects immidiatly and i can connect from other laptops to it and from even from not good doongles and