has anyone tried this?
has anyone tried this?
I just followed the steps listed on
http://www.akyl.net/Network+Manager+...in+Ubuntu+8.04
It worked perfectly. I was trying to avoid having to enter a password after autologon (desktop computer). This solved my problem.
Thanks
I saw that, but I'm not sure if it's what I need since I don't have a wireless network. I simply want to stop Evolution from asking for my password on my computer with autologin. (I'm the only one who uses this box so I don't need the added security of entering my password on boot.) Can someone tell me if this would work for me before I go through the hassle of installing something that may do nothing to resolve my issue?
For an OSX look check out Mac4Lin (updated support thread)
Follow me on Twitter | My Blog
The Search tool is your friend.
This may be a bit too simple, but I'd just like to mention it for completeness. My computer did not start asking for the keyring password until I enabled my first password keyring item named "default." By simply removing this item, "default" form the keyring item list, the annoying screen stopped appearing at computer start-up. Then if keyrings are required to be stored, I simply do not give a password to be used. The "default" keyring item is still created once again; but, no screen ever pops up at start-up asking for a password. Obviously there is no password protection if you use this method.
If you use another dm like slim, it suffices to copy the gdm entry in /etc/pam.d dir to slim.
After restart you also wont be asked for keyring-password anymore.Code:cd /etc/pam.d cp gdm slim
Works at least in intrepid.
Far easier solution is to reset your password to blank (on Intrepid 8.10):
Do a search (Places / search) for Seahorse (on file system)
Start up Seahorse
Select Edit/Preferences
Select default and select change unlock password
after entering your odl password, for new password just hit line return twice
there will be a warning message that security is low, but this will allow you to connect to Wifi without problem at boot (without being asked!).
Just dont save your other passwords on this keyring if you dont want anyone to access eg your emails!
![]()
Hi I'm getting an error when I try to configure --prefix blah blah
I've installed all the needed packages but I keep getting this error:
Anyone know whats going on?checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for gawk... no
checking for mawk... mawk
checking whether make sets $(MAKE)... yes
checking for gcc... gcc
checking for C compiler default output file name... a.out
checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables...
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ANSI C... none needed
checking for style of include used by make... GNU
checking dependency style of gcc... gcc3
checking for a BSD-compatible install... /usr/bin/install -c
configure: error: cannot run /bin/bash ./config.sub
Ok so i follow the code all the way and right when i type in the code i get this:
.......@.......-desktop:~/pam_keyring-0.0.8$ ./configure --prefix=/usr --libdir=/lib
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for gawk... no
checking for mawk... mawk
checking whether make sets $(MAKE)... yes
checking for gcc... gcc
checking for C compiler default output file name... a.out
checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables...
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ANSI C... none needed
checking for style of include used by make... GNU
checking dependency style of gcc... gcc3
checking for a BSD-compatible install... /usr/bin/install -c
configure: error: cannot run /bin/bash ./config.sub
.......@......-desktop:~/pam_keyring-0.0.8$
what an i doing wrong?? ssoooo frustrating![]()
Hi, don't know whether this is solved or not, but your problem is that the symbolic links pointing to config.guess, config.sub, and ltmain.sh are broken..
I just moved these files to a new folder, and in a terminal typed in:
Code:/pam_keyring-0.0.8$ ln -s /usr/share/libtool/config/ltmain.sh /pam_keyring-0.0.8$ ln -s /usr/share/libtool/config/config.guess /pam_keyring-0.0.8$ ln -s /usr/share/libtool/config/config.sub
Bookmarks