[Bug 1718658] Re: ecryptfs-mount-private fails to initialize ecryptfs keys
I just upgraded from 16.04 to 18.04 and I'm seeing the same/similar issue. I have the same messages in the log, and I have an encrypted home folder. When I *first* try to log in after a reboot, I get bounced back to the login screen. It then logs in on the second attempt (so far - but this makes me nervous). None of the fixes above have worked for me so far. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1718658 Title: ecryptfs-mount-private fails to initialize ecryptfs keys To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ecryptfs-utils/+bug/1718658/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 50214] Re: can't connect to hidden network
Alexander, thanks. I wasn't sure it was correct either - it seemed to be showing AP_SCAN 1 in the log files, and I thought the replacement should have changed that to AP_SCAN 2. However, dpkg did seem to do a replacement, and Synaptic showed an ubuntu2 version before, and an ubuntu4 version afterward. I will play with these things a bit more when I find time. In the meantime, I will check out the archive deb package and see how I go with that. Matt On Tue, Apr 1, 2008 at 11:01 AM, Alexander Sack [EMAIL PROTECTED] wrote: Matt, i cannot tell if you are really running the right network manager package as i miss some log output i would expect to see in the latest packages. Anyway, the branch is now available as .deb package in the archive, so you can test the prebuild debs directly. If you still have issues connecting to hidden SSID (or connecting at all), please file a new ipw2200 bug. For the signing error during build: the failure to sign is not a problem for local tests. I think the error message would not have popped up if you build like: debuild -b -uc -- 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/13016043/unnamed -- 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
Re: [Bug 50214] Re: can't connect to hidden network
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_scanhttps://code.edge.launchpad.net/%7Eubuntu-core-dev/network-manager/ubuntu.0.6.x.ap_scannetwork-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
Re: [Bug 50214] Re: can't connect to hidden network
Gene, oops, yes, I meant the reply to you! I've also been using linux for 4 years, and I know enough to figure things out - I don't need step-by-step instructions (although they certainly help!). Having said that, I use Ubuntu precisely because it doesn't force me to become an O/S expert - but I'm still free to tinker with the bits I find interesting. I'll continue to try out betas and submit bugs related to my hardware - it's in my interest after all! I would like to be able to build and test patches running from the beta cd, not installed, as I also don't have a spare testing machine or unlimited bandwidth. I don't know if that's even possible. cheers, Matt On Sun, Mar 30, 2008 at 4:10 AM, Gene Caldwell [EMAIL PROTECTED] wrote: Matt, Correct me if I'm wrong here but I think you meant your address to me, not to Alexander. Alexander is the guy who is providing the patches and is trying to get this bug fixed for all of us, he's the guy who knows how to do all this stuff. It's funny tho, you seem to have the very same background as I do. however I am no longer able to work in my chosen profession. I choose to try to stay involved however I can. And like you, I have found it very difficult to gain enough of the requested talent that is needed to provide feed back to these guys on the patches et-al. locating the much needed details or how-to's has also been been hopeless for me. I continue trying tho much like your self. its been over 4 years now for me since I started using linux and I still consider myself a newbie. lol, I guess since I cannot patch my own system shows I still am a newbie. Gene -- 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/12977137/unnamed -- 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
Re: [Bug 50214] Re: can't connect to hidden network
Alexander, you are not alone! I happily submitted a bug for the ipw2200 chipset having used the beta cd, but didn't have the first clue about building branches, patches or whatever.I actually work in software development - I'm just not familiar with these tools or procedures, and I don't have endless hours to spend figuring it out. I spent about an hour trying to find help, but could find no documentation on what to do at all. Some concise newbie help for technically minded beta testers would be very useful. Regards, Matt On Sat, Mar 29, 2008 at 7:04 PM, Gene Caldwell [EMAIL PROTECTED] wrote: Alexander, I am truly sorry, I cannot. The computer I have the problem with is a production machine, not a test machine. Its my Girl Friends work computer, I simply cannot take a work computer out of commission for beta testing as much as I really would like to try to provide you feed back on so this issue can be fixed. Thats the first problem. The second problem is that I'm totally clueless as to what you need me to do to test your patch, I read every post you guys have made for the last several days and I simply do not know enough about linux to know how to get the patch installed or even know if messed up during the process. I can however install a .deb package...duh, like its something troublesome or complicated :) but as I did not see anyone asking for deb packages from you to try, I have been just hoping that someone with my same chipset will provide you the needed feedback. I'm sorry, I don't know how to do as you ask and feel you are trying at the moment and don't want to interfere with your efforts by asking for special just for me. I do have another computer I can test with tho that has a different chipset that has the very same hidden SSID problem, however I still have the same problem, I don't know how to install a patch if it is not delivered in a deb package. I would love to help and provide feed back ( I love testing things out ) if I only knew how to install your patch. Just so you know, I really did try, I'm not a dummy, I just can't figure out the linux way of doing things, I guess I spent too many years in windows. production machine: Dell C800 with prism54 wireless pcmcia card does not yet work except for what Dave Ward helped out with several months back, there were still problems with his patch tho. no automatic re-connection etc. other testable machine I CAN test on has atheros wifi card. but as I said, I know nothing about patches. -- 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/12972803/unnamed -- 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
Re: [Bug 50214] Re: can't connect to hidden network
The branch is right at the top of the bug report web page, not in the email. cheers, Matt. On Mon, Mar 24, 2008 at 10:42 PM, Gene Caldwell [EMAIL PROTECTED] wrote: Alexander Sack wrote 1 hour ago: (permalink) please test the branch above. instructions on how to get it to your disc can be found at the branch url given to build you can just run $ debuild -b out of the branch directory. use dpkg -i to install the packages for testing. If you still cannot connect to hidden SSID, please attach your complete /var/log/syslog to the bug and state clearly if you could connect to hidden networks in gutsy. I see no branch above that you are referring to in this post will the latest beta release not work ? -- 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: Confirmed 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 ... -- 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
[Bug 50214] Problem on Hardy Beta, Thinkpad T43 (ipw2200)
I have this problem using Thinkpad T43 (ipw2200). Works fine in Gutsy, not in Hardy (running from live CD). Unhide the SSID on my access point, and the network connects fine (posting using hardy beta on the same machine!). The syslog shows it tries to connect, but times out. I've attached the relevant extract. ** Attachment added: syslog showing connection attempt to hidden SSID network http://launchpadlibrarian.net/12809939/syslog -- 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
