Re: gaim problem

From: Joseph A. Nagy, Jr. (pagan_prince_at_bigfire-hsv.org)
Date: 12/30/03

  • Next message: Alex Malinovich: "Re: "best practices" on debian"
    Date: Tue, 30 Dec 2003 15:12:57 -0600
    To: Scarletdown <gsutton9503@charter.net>
    
    

    Scarletdown wrote:
    > Joseph A. Nagy, Jr. wrote:
    >
    >> panda wrote:
    >>
    >>> Hi,
    >>>
    >>> I am not very sure I should be sending this on this list. Please tell
    >>> me if I am wrong.
    >>>
    >>> I installed gaim ( version 0.72 ) using aptitude. It shows my
    >>> contacts on YM and MSN but the moment I click on one of them ( off or
    >>> online ) gaim shuts down. I would send in a bug report but the
    >>> message asks me if I am using the most recent version which I am not
    >>> ( 0.74 )
    >>
    >>
    >>
    >> How did you manage to get .72 (even using aptitude)? I can't find any
    >> packages higher then .62 (from unstable).
    >>
    >> As for the problem, I have the same problem with the official Yahoo
    >> client so I too am interested in the solution.
    >>
    >>>
    >>> Checking for new version with apt-get -t unstable does not find
    >>> anything.
    >
    >
    > I'm running 0.72 just fine. I got it from here:
    >
    > ftp://ftp.debian.org/debian/dists/unstable/main/binary-i386/
    >
    >

    W: GPG error: http://download.kde.org stable Release: Unknown error
    executing gpgv
    W: GPG error: http://mirrors.kernel.org stable Release: The following
    signatures couldn't be verified because the public key is not available:
    NO_PUBKEY B629A24C38C6029A
    W: GPG error: http://ftp.us.debian.org stable Release: The following
    signatures couldn't be verified because the public key is not available:
    NO_PUBKEY B629A24C38C6029A
    W: GPG error: http://ftp.debian.org stable Release: The following
    signatures couldn't be verified because the public key is not available:
    NO_PUBKEY B629A24C38C6029A
    W: GPG error: http://non-us.debian.org stable/non-US Release: The
    following signatures couldn't be verified because the public key is not
    available: NO_PUBKEY B629A24C38C6029A
    W: You may want to run apt-get update to correct these problems

    That's after running apt-get update about three dozen times.

    -- 
    Joseph A. Nagy, Jr.
    Student at Motlow State Community College
    Political Activist Extrodinaire
    The only fallacy is the inaction on our part to stave off the worst of 
    horrors, the stripping of personal freedom.
    -- 
    To UNSUBSCRIBE, email to debian-user-request@lists.debian.org 
    with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
    

  • Next message: Alex Malinovich: "Re: "best practices" on debian"

    Relevant Pages

    • Problems with apt-get update
      ... signatures couldn't be verified because the public key is not available: ... W: GPG error: http://non-us.debian.org stable/non-US Release: The ...
      (Debian-User)
    • Re: PUBKEY errors
      ... These following errors were shown with the "apt-get update" command. ... signatures couldn't be verified because the public key is not available: ... W: GPG error: http://security.debian.org testing/updates Release: The ...
      (Debian-User)
    • Re: apt-get update GPG error
      ... W: GPG error: http://www.debian-multimedia.org etch Release: The ... following signatures couldn't be verified because the public key is ...
      (Debian-User)
    • apt-get update GPG error
      ... W: GPG error: http://www.debian-multimedia.org etch Release: The ... following signatures couldn't be verified because the public key is ...
      (Debian-User)
    • GPG:Error non-us.debian.org
      ... W: GPG error: http://non-us.debian.org stable/non-US Release: The following ... signatures couldn't be verified ... To UNSUBSCRIBE, email to debian-user-REQUEST@xxxxxxxxxxxxxxxx ...
      (Debian-User)