public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Dale <rdalek1967@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Yahoo and strange traffic.
Date: Wed, 25 Aug 2010 17:34:13 -0500	[thread overview]
Message-ID: <4C759A65.3010702@gmail.com> (raw)
In-Reply-To: <AANLkTikK81mLNj2hi8q7vXML-v8aw98fhe_CVFw9FB8_@mail.gmail.com>

Joshua Murphy wrote:
> Yep, but... just from a glance at their bug tracker and their commits
> list... they made quite a few changes to the Yahoo plugin's handling
> of avatars and such in January that're in 4.4... so their go-to answer
> on Yahoo avatar related issues seems to be "Try it on 4.4, then come
> back if it's still broken."
>
> So... to save a little time and effort when that answer's thrown
> around... might be best to test with that. I don't have QT or anything
> that depends on it on any of my boxes (the only box I actually have X
> on right now's my netbook, so adding's not even a feasable option) and
> my yahoo account went dead a few years ago, so I'm not much use for
> testing.
>
>    

Then I guess they would have to look at the bug report then.

[ebuild   R   ] kde-base/kopete-4.4.5-r1  USE="addbookmarks autoreplace 
contactnotes groupwise handbook highlight history nowlistening pipes 
privacy ssl statistics texteffect translator urlpicpreview yahoo 
zeroconf (-aqua) -debug -gadu -jabber -jingle (-kdeenablefinal) 
(-kdeprefix) -latex -meanwhile -msn -oscar -otr -qq -skype -sms -testbed 
-v4l2 -webpresence -winpopup"

Since I am on 4.4.5 already, I am using their preferred version.  My 
current fix, just close Kopete.  I'll see if that keeps it from doing 
this.  lol   I bet that works too.

Maybe 4.5.* will be better.

Dale

:-)  :-)



  reply	other threads:[~2010-08-25 22:35 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-15 20:34 [gentoo-user] Yahoo and strange traffic Dale
2010-08-15 20:55 ` Paul Hartman
2010-08-15 21:18   ` BRM
2010-08-15 21:35     ` Dale
2010-08-15 22:25       ` Peter Humphrey
2010-08-15 22:48         ` Dale
2010-08-15 21:29   ` Alan McKinnon
2010-08-16 22:55     ` Dale
2010-08-16 23:39       ` Adam Carter
2010-08-17  1:20         ` Dale
2010-08-17  1:32           ` Adam Carter
2010-08-17  5:46             ` Dale
2010-08-17  6:09               ` Adam Carter
2010-08-17 10:23                 ` Dale
2010-08-17 11:15                   ` Jake Moe
2010-08-17 11:26                     ` Dale
2010-08-17 14:29                   ` BRM
2010-08-17 16:10                     ` Mick
2010-08-17 20:15                       ` Dale
2010-08-17 21:11                         ` Mick
2010-08-17 21:32                           ` Dale
2010-08-18  2:09                             ` BRM
2010-08-18  2:18                               ` Dale
2010-08-18  2:18                               ` Dale
2010-08-25  2:36                     ` Dale
2010-08-25  8:08                       ` Joshua Murphy
2010-08-25  9:58                         ` Dale
2010-08-25 13:21                           ` BRM
2010-08-25 13:57                             ` Joshua Murphy
2010-08-25 22:34                               ` Dale [this message]
2010-08-15 21:32 ` Mick

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4C759A65.3010702@gmail.com \
    --to=rdalek1967@gmail.com \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox