Bug#380740: cannot connect to icq server - icq server thinks my client is too old

Package: kopete Version: 4:3.5.4-1 Severity: important I've upgraded to the new kdenetwork today and after restarting kde I cannot connect to the icq server anymore. The error text is (translated from german message): """ xxx disconnected, the icq server thinks you're using an outdated client "

Bug#380740: cannot connect to icq server - icq server thinks my client is too old

Bastian Venthur wrote: > I know the kopete version was upgraded since the last kdenetwork update but > it > worked yesterday and does not work anymore after the upgrade. Ooops I meant: I know the kopete version was *not* upgraded ... -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subjec

Bug#380751: kdebase: Print key taken by global action "AccessKey" -- cannot be changed

Package: kdebase Version: 4:3.5.4-2 Severity: normal Hi all, since I have updated last night a lot of kde to 3.5.4-2, the Print key, which I had mapped to show yakuake is no longer under my control. Instead it always starts Ksnapshot. I can take it back temporarily by issuing "Block Global Shor

Bug#380740: Further info

Downgrading kopete to 3.5.3-1 fixes this problem. Michael -- Michael Meskes Email: Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org) ICQ: 179140304, AIM/Yahoo: michaelmeskes, Jabber: [EMAIL PROTECTED] Go SF 49ers! Go Rhein Fire! Use Debian GNU/Linux! Use PostgreSQL! -- To UN

Bug#380740: cannot connect to icq server - icq server thinks my client is too old

Package: kopete Version: 4:3.5.4-1 Tags: patch, sid Followup-For: Bug #380740 Hi, there is a bug report at http://bugs.kde.org/show_bug.cgi?id=131598 which points to information at http://www.kde-forum.org/artikel/15097/Kopete-ICQ-protocol-changed-again-solved.html and a patch linked from th

Re: [Pkg-xfce-devel] Debian sid and etch artwork.

On Mon, 2006-07-31 at 12:19 -0300, Gustavo Franco wrote: > [ Unfortunately the cross-posting is necessary, but hopefully after a > online meeting we will have a separated mailing list ] > > I would like to discuss with you the Debian sid and etch artwork > infrastructure and after that the artwork

Re: [Pkg-xfce-devel] Debian sid and etch artwork.

On 8/1/06, Yves-Alexis Perez <[EMAIL PROTECTED]> wrote: On Mon, 2006-07-31 at 12:19 -0300, Gustavo Franco wrote: > [ Unfortunately the cross-posting is necessary, but hopefully after a > online meeting we will have a separated mailing list ] > > I would like to discuss with you the Debian sid and

Bug#381032: kruler: has window decorations under GNOME

Package: kruler Version: 4:3.5.2-1+b2 Severity: minor When starting kruler under GNOME, kruler comes up with window decorations (it doesn't under KDE). I already reported this on bugs.kde.org: http://bugs.kde.org/show_bug.cgi?id=131661 -- System Information: Debian Release: testing/unstable

Processed: kruler: has window decorations under GNOME

Processing commands for [EMAIL PROTECTED]: > forwarded 381032 http://bugs.kde.org/show_bug.cgi?id=131661 Bug#381032: kruler: has window decorations under GNOME Noted your statement that Bug has been forwarded to http://bugs.kde.org/show_bug.cgi?id=131661. > End of message, stopping processing he

Select Alabama

revert lengthy tomes lyric rhyme Rhyming Law Politics basic skinny CIA Factbook laws Delaware Columbia Florida Georgia Hawaii Idaho Illinois Indiana Iowa Kansas Kentucky Math Ask Office. Roberts Column column Los Angeles Times. Along Political Money Trail Where Mouse Sites Ease Pain D

Processed: Update email address

Processing commands for [EMAIL PROTECTED]: > submitter 307602 ! Bug#307602: exim: postinst scripts complains about db3_update Changed Bug submitter from Rémi Denis-Courmont <[EMAIL PROTECTED]> to Rémi Denis-Courmont <[EMAIL PROTECTED]>. > submitter 347946 ! Bug#347946: akregator segfaults at s

[bts-link] source package kdegraphics

# # bts-link upstream status pull for source package kdegraphics # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html # user [EMAIL PROTECTED] # remote status report for #381032 # * http://bugs.kde.org/show_bug.cgi?id=131661 # * remote status changed: (?) -> UNCONFIRMED use

Bug#378402: krdc: Backtrace info for segfault

Package: krdc Version: 4:3.5.3-1 Followup-For: Bug #378402 Using host libthread_db library "/lib/tls/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread -1497393472 (LWP 17182)] [New Thread -1498858576 (LWP 17256)] [KCrash handler] #5 0x0805b169 in vidmodeFullscreenSwit

kdelibs_3.5.4-3_i386.changes ACCEPTED

Accepted: kdelibs-data_3.5.4-3_all.deb to pool/main/k/kdelibs/kdelibs-data_3.5.4-3_all.deb kdelibs-dbg_3.5.4-3_i386.deb to pool/main/k/kdelibs/kdelibs-dbg_3.5.4-3_i386.deb kdelibs4-dev_3.5.4-3_i386.deb to pool/main/k/kdelibs/kdelibs4-dev_3.5.4-3_i386.deb kdelibs4-doc_3.5.4-3_all.deb to poo

Processing of kdelibs_3.5.4-3_i386.changes

kdelibs_3.5.4-3_i386.changes uploaded successfully to localhost along with the files: kdelibs_3.5.4-3.dsc kdelibs_3.5.4-3.diff.gz kdelibs_3.5.4-3_all.deb kdelibs-data_3.5.4-3_all.deb kdelibs4-doc_3.5.4-3_all.deb kdelibs4c2a_3.5.4-3_i386.deb kdelibs4-dev_3.5.4-3_i386.deb kdelibs-dbg_

Processing of kdenetwork_3.5.4-2_i386.changes

kdenetwork_3.5.4-2_i386.changes uploaded successfully to localhost along with the files: kdenetwork_3.5.4-2.dsc kdenetwork_3.5.4-2.diff.gz kdenetwork_3.5.4-2_all.deb kdenetwork-doc-html_3.5.4-2_all.deb dcoprss_3.5.4-2_i386.deb kdenetwork-kfile-plugins_3.5.4-2_i386.deb kdenetwork-files

kdenetwork_3.5.4-2_i386.changes ACCEPTED

Accepted: dcoprss_3.5.4-2_i386.deb to pool/main/k/kdenetwork/dcoprss_3.5.4-2_i386.deb kdenetwork-dbg_3.5.4-2_i386.deb to pool/main/k/kdenetwork/kdenetwork-dbg_3.5.4-2_i386.deb kdenetwork-dev_3.5.4-2_i386.deb to pool/main/k/kdenetwork/kdenetwork-dev_3.5.4-2_i386.deb kdenetwork-doc-html_3.5.4-

Bug#380740: marked as done (cannot connect to icq server - icq server thinks my client is too old)

Your message dated Tue, 01 Aug 2006 17:49:40 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#380740: fixed in kdenetwork 4:3.5.4-2 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is n