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
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
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
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
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
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
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
