I just upgraded from 9.2 to 9.3 and now the susewatcher applet won't connect to show me whether there are updates or not. When I open susewatcher it says YOU status - Couldn't connect to update-server. When I click on the show last log button this is what I get: online_update -k -s Error retrieving patches: ERROR(You:File has invalid signature.)[Patch: fetchnvidia.sh-52062] If I start online update I am able to connect and download and install patches. I searched google and found nothing. I also tried rpm --rebuilddb and that didn't help either. If anyone's seen this I would appreciate some help. Thanks, Andy
On Tuesday 05 July 2005 7:38 pm, Andy Coleman wrote:
I just upgraded from 9.2 to 9.3 and now the susewatcher applet won't connect to show me whether there are updates or not.
When I open susewatcher it says YOU status - Couldn't connect to update-server.
When I click on the show last log button this is what I get: online_update -k -s Error retrieving patches: ERROR(You:File has invalid signature.)[Patch: fetchnvidia.sh-52062]
What worked for me was to go to the directory where YaST/YOU stores this download info and delete that file giving me trouble. In your case the fetchnvidia.sh-52062 file which was also one of the files I had trouble with. Happenend with one or two others but hasn't for weeks now. /home/login-id/.yast2/you/mnt/i386/update/9.3/patches was where I deleted the file and that fixed it. To me it appeared that whichever file was a partial or failed download and YOU choked on it. Happened several times with a couple different files. Hasn't happened for a number of weeks now.
If I start online update I am able to connect and download and install patches.
I searched google and found nothing. I also tried rpm --rebuilddb and that didn't help either.
If anyone's seen this I would appreciate some help.
Thanks,
Andy
Stan
Thanks for the info Stan, it worked great! On Tuesday 05 July 2005 21:07, Stan Glasoe wrote:
On Tuesday 05 July 2005 7:38 pm, Andy Coleman wrote:
I just upgraded from 9.2 to 9.3 and now the susewatcher applet won't connect to show me whether there are updates or not.
When I open susewatcher it says YOU status - Couldn't connect to update-server.
When I click on the show last log button this is what I get: online_update -k -s Error retrieving patches: ERROR(You:File has invalid signature.)[Patch: fetchnvidia.sh-52062]
What worked for me was to go to the directory where YaST/YOU stores this download info and delete that file giving me trouble. In your case the fetchnvidia.sh-52062 file which was also one of the files I had trouble with. Happenend with one or two others but hasn't for weeks now.
/home/login-id/.yast2/you/mnt/i386/update/9.3/patches was where I deleted the file and that fixed it. To me it appeared that whichever file was a partial or failed download and YOU choked on it. Happened several times with a couple different files. Hasn't happened for a number of weeks now.
If I start online update I am able to connect and download and install patches.
I searched google and found nothing. I also tried rpm --rebuilddb and that didn't help either.
If anyone's seen this I would appreciate some help.
Thanks,
Andy
Stan
Well, I decided to install 9.2Pro on one of my desktop machines, and since it has a 250GB HDA, I decided to make a bunch of partitions during install. And then I decided to encrypt /home, because it seemed like a good way to protect my personal information from Knoppix-style attacks. Everything works fine, *except* that, unless I'm watching the detailed boot process, and catch the prompt to enter my /home encryption password, /home ends up inaccessible and KDE can't start. Encrypting /home might not have been such a bright idea, I suppose, but it seemed like a good idea at the time... Anyway, is there a way around this? Increasing or eliminating the timeout on the encryption password prompt? Or a way to Ctl-Alt-F1 and enter the password after the boot process is complete? Right now, I can get by by rebooting and watching the pages and pages of text scroll by until the prompt comes up again, but 9.2 has a *terribly* long bootup time on this machine (3-4 times as long as XP or even SUSE 9.1).
David McMillan wrote:
Well, I decided to install 9.2Pro on one of my desktop machines, and since it has a 250GB HDA, I decided to make a bunch of partitions during install. And then I decided to encrypt /home, because it seemed like a good way to protect my personal information from Knoppix-style attacks. Everything works fine, *except* that, unless I'm watching the detailed boot process, and catch the prompt to enter my /home encryption password, /home ends up inaccessible and KDE can't start. Encrypting /home might not have been such a bright idea, I suppose, but it seemed like a good idea at the time... Anyway, is there a way around this? Increasing or eliminating the timeout on the encryption password prompt? Or a way to Ctl-Alt-F1 and enter the password after the boot process is complete? Right now, I can get by by rebooting and watching the pages and pages of text scroll by until the prompt comes up again, but 9.2 has a *terribly* long bootup time on this machine (3-4 times as long as XP or even SUSE 9.1).
Modify /etc/fstab, so that /home doesn't mount automatically. Then you could have a script start up, perhaps in boot.local, which requests the password. You problably also want to modify inittab, so that the desktop doesn't try to start at boot up. Next time, encrypt the individual user's directory.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Thursday 2005-07-07 at 10:39 -0400, David McMillan wrote: You hijacked a thread. Please, don't.
time... Anyway, is there a way around this? Increasing or eliminating the timeout on the encryption password prompt?
It is 120 seconds, I think; I know that it is 120 whatevers.
Or a way to Ctl-Alt-F1 and enter the password after the boot process is complete?
/etc/init.d/boot.crypto start as root. I think it should be possible to add a bell to the script, perhaps here: echo "Activating crypto devices using $CRYPTOTAB ... " to: echo -e "\a Activating crypto devices using $CRYPTOTAB ... " It should be possible to use more complex bells; I tried it and it is not strong enough. I have somewhere a sample, some other time. - -- Cheers, Carlos Robinson -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFCzc+atTMYHG2NR9URAnK+AJ4pBOivBTVx6xHMH+THAT1bgfv4qwCcDBsh qbD3zDSuS4k/fXlwe1TlwW4= =7zH9 -----END PGP SIGNATURE-----
participants (5)
-
Andy Coleman
-
Carlos E. R.
-
David McMillan
-
James Knott
-
Stan Glasoe