Alexander, great instructions. I had to sudo a little bit more, and do an apt-get update before it would install all the build dependencies. The only other errors I got were not having your private GPG key to sign the packages! It would be great if such simple instructions were obvious and available to everyone on launchpad.
I ran it all from the live CD, and built a new network manager and installed it (ubuntu4). I assume this is OK - you don't have to do this from a hard disk install? It installed cleanly over the existing one, maintaining my network connection to an unhidden network. I changed the network back over to hidden, and it stayed connected. However, when I disconnected and tried to reconnect, it failed to re-connect, with the same issues. This is on a thinkpad T43 using ipw2200. Attached is the dmesg and syslog outputs. Matt On Mon, Mar 31, 2008 at 11:21 AM, Alexander Sack <[EMAIL PROTECTED]> wrote: > Gene, Matt. sorry if my instructions where not appropriate. Though this > package is already in the archive, I'll try harder to post better > instructions next time. I certainly want developers to be able to test > these. But its much easier to request tests on a branch than rolling out > debs for each individual issues i want to track potential fixes for. > > So please review if the following steps are detailed enough for you to > tests: > > # install build requirements/dependencies > 1. sudo apt-get build-dep network-manager > 2. sudo apt-get install bzr devscripts > > # branch the sources > 3. bzr branch > https://code.edge.launchpad.net/~ubuntu-core-dev/network-manager/ubuntu.0.6.x.ap_scan<https://code.edge.launchpad.net/%7Eubuntu-core-dev/network-manager/ubuntu.0.6.x.ap_scan>network-manager.ubuntu > > # build the sources: > 4. cd network-manager.ubuntu > 5. debuild -b > > # install the bits for testing > 6. cd ../; dpkg -i network-manager*deb libnm-*deb > > Is that good enough? > > Thanks for your input, > - Alexander > > -- > can't connect to hidden network > https://bugs.launchpad.net/bugs/50214 > You received this bug notification because you are a direct subscriber > of the bug. > > Status in NetworkManager: Fix Released > Status in Source Package "network-manager" in Ubuntu: Fix Released > Status in Source Package "knetworkmanager" in Baltix GNU/Linux: Invalid > > Bug description: > Since I installed dapper clean from CD, NM won't connect to my own hidden > network., however it did before. The network was even in the list after a > few seconds, the new feature of reverse mac scanning in 0.6.2. > > Now even if I use "connect to other network" and I enter everything in > there, the connection won't be a success. Not hiding the SSID solves the > problem immediately, just as manually connecting to the AP with iwconfig > eth1 essid <mine> ... > ** Attachment added: "unnamed" http://launchpadlibrarian.net/13004539/unnamed ** Attachment added: "syslog" http://launchpadlibrarian.net/13004541/syslog ** Attachment added: "dmesg" http://launchpadlibrarian.net/13004544/dmesg -- can't connect to hidden network https://bugs.launchpad.net/bugs/50214 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
