Mailinglist Archive: opensuse (4288 mails)

["Robert C. Paulsen Jr." <robert@xxxxxxxxxxxxxxxxx>]

I have suddenly started having trouble with Yast Online Update, which I
run as console mode via ssh.

The current symptom is that when I launch the YOU module from Yast, it
crashes back to a command line and puts out the following message:

  sbin/yast line 149: 22497 Aborted /usr/lib/Yast2/bin/y2base $module "$@" ncurses

I am hoping there is some file lying around I can delete to get Yast's YOU
back to a normal state -- anyone have any ideas?

====================[ background info ]=================================
SuSE 8.0.

Here is how I think I got into this mess... YOU displayed the following
messages (overwriting the normal ncurses screen):

  Could not find valid trust path to the key. Let's see whether we can
  assign some missing owner trust values. No path leading to one of our
  keys found.

Note that root's .gnupg directory does contain the suse-supplied keys:

  # gpg --list-keys
  /root/.gnupg/pubring.gpg
  ------------------------
  pub  2048R/3D25D3D9 1999-03-06 SuSE Security Team <security@xxxxxxx>

  pub  1024D/9C800ACA 2000-10-19 SuSE Package Signing Key <build@xxxxxxx>
  sub  2048g/8495160C 2000-10-19 [expires: 2006-02-12]

I suspected the problem might be that I upgraded GPG from 1.06 (as
installed by SuSE 8.0) to 1.07. I think one of the differences from 1.06
to 1.07 is stricter rules about read access on files in the .gnupg
directory, so I fixed that and tried again. Now I got the error messages
described in http://sdb.suse.de/en/sdb/html/swiegra_you-gpg.html:

   Warning.
   It is not possible to check the patch xxx (xxx represents the patch
   name) as no GPG package is installed or the patch description is
   damaged.  For this reason SuSE can not guarantee that the patch
   originates from SuSE.

I hit ctrl-C to cancel so I could ponder the suggested solutions to that
one. I decided to reactivate GPG 1.06 and try again.  From that point on, I
now only get the "aborted" problem at the beginning of this note.

I think I shouldn't have hit ctrl-C!

-- 
Robert C. Paulsen, Jr.
robert@xxxxxxxxxxxxxxxxx