Bug#259695: marked as done (Desktop switching while dragging windows does not work)

2004-11-08 Thread Debian Bug Tracking System
Your message dated Tue, 9 Nov 2004 06:44:45 +0100 with message-id <[EMAIL PROTECTED]> and subject line Bug#259695: Desktop switching while dragging windows does not work has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If thi

Bug#280184: juk: crashes after an empty search

2004-11-08 Thread Adeodato Simó
tag 280184 = upstream pending stop here * Fidel Ramos [Sun, 07 Nov 2004 22:45:01 +0100]: > Package: juk > Version: 4:3.3.0-1 > Severity: normal hi Fidel, > Steps to make Juk crash: > 1) Click in the search bar. > 2) Make a search with no matches, i.e. the songlist appears emtpy. > 3) Press

Processed: Re: Bug#280184: juk: crashes after an empty search

2004-11-08 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]: > tag 280184 = upstream pending Bug#280184: juk: crashes after an empty search There were no tags set. Tags set to: upstream, pending > stop here Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrat

Bug#280373: kfax libtiff vulnerabilities

2004-11-08 Thread Ben Burton
> Did you happen to look at the source after > debian/patches/01_kdegraphics_branch.diff.uu is applied? The orig.tar.gz > is not patched directly of course... An understandable mistake. With many (most, I suspect) packages, the debian diffs are applied upon dpkg-source -x. For the KDE modules t

Bug#248865: marked as done (kde: cdrom auto-icon forces noexec option)

2004-11-08 Thread Debian Bug Tracking System
Your message dated Tue, 9 Nov 2004 05:12:37 +0100 with message-id <[EMAIL PROTECTED]> and subject line Bug#248865: kde: cdrom auto-icon forces noexec option 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 c

Processed: remove tag

2004-11-08 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]: > tags 280373 - sid Bug#280373: kfax libtiff vulnerabilities Tags were: sarge sid security Tags removed: sid > stop Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs

Bug#280373: kfax libtiff vulnerabilities

2004-11-08 Thread Adeodato Simó
* Chris Cheney [Mon, 08 Nov 2004 21:13:02 -0600]: > > It is not fixed in kdegraphics 3.3.1-1. I just downloaded the source > > (apt-get source kdegraphics), and the kfax.cpp is the version dated July > > 12, 2004 which is in the tagged KDE_3_3_1_RELEASE. The fix was committed > > to both KDE_

Bug#280373: kfax libtiff vulnerabilities

2004-11-08 Thread Chris Cheney
On Mon, Nov 08, 2004 at 09:35:30PM -0500, Josh Metzler wrote: > On Monday 08 November 2004 07:46 pm, Chris Cheney wrote: > > On Tue, Nov 09, 2004 at 12:37:55AM +0100, Andreas Mueller wrote: > > > Package: kfax > > > Version: 4:3.3.1-1 > > > Severity: normal > > > > > > > > > -- cut from the inoffic

Bug#280373: kfax libtiff vulnerabilities

2004-11-08 Thread Josh Metzler
On Monday 08 November 2004 07:46 pm, Chris Cheney wrote: > On Tue, Nov 09, 2004 at 12:37:55AM +0100, Andreas Mueller wrote: > > Package: kfax > > Version: 4:3.3.1-1 > > Severity: normal > > > > > > -- cut from the inoffical KDE Security Advisory -- > > > > kfax, a small utility for displaying fax f

Bug#280373: kfax libtiff vulnerabilities

2004-11-08 Thread Chris Cheney
On Tue, Nov 09, 2004 at 12:37:55AM +0100, Andreas Mueller wrote: > Package: kfax > Version: 4:3.3.1-1 > Severity: normal > > > -- cut from the inoffical KDE Security Advisory -- > > kfax, a small utility for displaying fax files, contains > for historic reasons a private copy of libtiff. > There

Processed: your mail

2004-11-08 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]: > severity 280373 critical Bug#280373: kfax libtiff vulnerabilities Severity set to `critical'. > tags 280373 + security sid sarge Bug#280373: kfax libtiff vulnerabilities Tags were: sarge sid security Tags added: security, sid, sarge > End of message,

Processed: kfax libtiff vulnerabilities

2004-11-08 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]: > severity #280373 critical Bug#280373: kfax libtiff vulnerabilities Severity set to `critical'. > tags + security sid sarge Unknown command or malformed arguments to command. > End of message, stopping processing here. Please contact me if you need a

Processed: your mail

2004-11-08 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]: > tags #280373 + security sid sarge Bug#280373: kfax libtiff vulnerabilities There were no tags set. Tags added: security, sid, sarge > End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system admin

Bug#280373: kfax libtiff vulnerabilities

2004-11-08 Thread Andreas Mueller
Package: kfax Version: 4:3.3.1-1 Severity: normal -- cut from the inoffical KDE Security Advisory -- kfax, a small utility for displaying fax files, contains for historic reasons a private copy of libtiff. Therefore it is vulnerable to these issues as well. As a workaround, you can remove the k

Bug#280362: please use better description

2004-11-08 Thread Tomas Pospisek
Package: kate Version: 4:3.2.2-1 Severity: wishlist Tags: patch The attached patch provides a description for kate ripped straight from its homepage: http://kate.kde.org (with minor changes for readability). Please apply, thanks, *t -- System Information: Debian Release: 3.1 APT prefers testin

Bug#261106: kde: LANG=nl_NL@euro crashes all KDE stuff!

2004-11-08 Thread Adeodato Simó
[I sent this message a while ago to submitter address and -quiet. I'm retrying with -submitter, if it fails I'll close the bug.] > > With [EMAIL PROTECTED] all KDE stuff crashes quite quickly. KDE (and KDE > > apps) are completely unusable. hi, what's the status of this bug report? you didn

Bug#280358: Please use a better description

2004-11-08 Thread Tomas Pospisek
Package: konqueror Version: 4:3.2.2-1 Severity: wishlist Tags: patch The attached patch provides a description for konqueror ripped straight from its homepage: http://konqueror.kde.org (with minor changes for readability). Please apply, thanks, *t -- System Information: Debian Release: 3.1 APT

Bug#277194: marked as done (FTBFS: missing build-dependency on libxtst-dev)

2004-11-08 Thread Debian Bug Tracking System
Your message dated Mon, 08 Nov 2004 16:17:24 -0500 with message-id <[EMAIL PROTECTED]> and subject line Bug#276835: fixed in kdeutils 4:3.3.1-1 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 now

Bug#276835: marked as done (kdeutils: FTBFS: Missing Build-Depends on libxtst-dev)

2004-11-08 Thread Debian Bug Tracking System
Your message dated Mon, 08 Nov 2004 16:17:24 -0500 with message-id <[EMAIL PROTECTED]> and subject line Bug#276835: fixed in kdeutils 4:3.3.1-1 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 now

kdeutils override disparity

2004-11-08 Thread Debian Installer
There are disparities between your recently accepted upload and the override file for the following file(s): kgpg_3.3.1-1_i386.deb: package says section is utils, override says kde. Either the package or the override file is incorrect. If you think the override is correct and the package wrong p

kdeutils_3.3.1-1_i386.changes ACCEPTED

2004-11-08 Thread Debian Installer
Accepted: ark_3.3.1-1_i386.deb to pool/main/k/kdeutils/ark_3.3.1-1_i386.deb kcalc_3.3.1-1_i386.deb to pool/main/k/kdeutils/kcalc_3.3.1-1_i386.deb kcharselect_3.3.1-1_i386.deb to pool/main/k/kdeutils/kcharselect_3.3.1-1_i386.deb kdelirc_3.3.1-1_i386.deb to pool/main/k/kdeutils/kdelirc_3.3.1

Bug#271875: marked as done (kdessh: Does not depend on ssh)

2004-11-08 Thread Debian Bug Tracking System
Your message dated Mon, 08 Nov 2004 16:17:24 -0500 with message-id <[EMAIL PROTECTED]> and subject line Bug#271875: fixed in kdeutils 4:3.3.1-1 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 now

Processing of kdeutils_3.3.1-1_i386.changes

2004-11-08 Thread Archive Administrator
kdeutils_3.3.1-1_i386.changes uploaded successfully to localhost along with the files: kdeutils_3.3.1-1.dsc kdeutils_3.3.1.orig.tar.gz kdeutils_3.3.1-1.diff.gz kdeutils-dev_3.3.1-1_i386.deb ark_3.3.1-1_i386.deb kcalc_3.3.1-1_i386.deb kcharselect_3.3.1-1_i386.deb kdelirc_3.3.1-1_i386

Bug#267763: marked as done (installation problem of KDE on woody/unstable: libopenexr0 ??)

2004-11-08 Thread Debian Bug Tracking System
Your message dated Mon, 8 Nov 2004 21:54:07 +0100 with message-id <[EMAIL PROTECTED]> and subject line this bug is fixed 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 now your responsibility to

Bug#280287: Mail on NFS

2004-11-08 Thread Helmut Toplitzer
So, after some more tries I suggest that the problem is in file-handling of files contained in the ~/Mail directory. It looks like the copy process from the window to the outbox or from outbox to the kio-slave causes this problem. Maybe this should be noted somewhere in a README if not fixed be

Bug#280287: kmail not nfs safe?

2004-11-08 Thread Helmut Toplitzer
Hi again! After some testing I found out that the only difference between the two systems is the nfs-mounted homedir. I tried a user with no nfs-homedir on the same system and the problem is gone. (Tried a newly created nfs-homedir user resulting in the same problems) So it look like kmail is

Bug#280287: [kmail]: New sent messages contains content of messages sent before

2004-11-08 Thread Helmut Toplitzer
Package: kmail Version: 4:3.3.0-3 Severity: important Tags: security Writing and sending one big mail (with attach. etc.) and sending another one small after this one will result in a mail with mixed content of both. The interesting thing about this is that only the first 4KB of the old mail are

Bug#280175: pgp/mime encryption not working in kmail 1.7

2004-11-08 Thread Alejandro Exojo
package kmail tags 280175 unreproducible stop El Domingo, 7 de Noviembre de 2004 20:27, wolfgang escribió: > in kmail 3.3.0-3, pgp/mime encryption and decryption are not working > properly. Here is working perfectly. Have you followed the steps that says this page? How you have configured kmail?

Processed: Re: Bug#280175: pgp/mime encryption not working in kmail 1.7

2004-11-08 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]: > package kmail Ignoring bugs not assigned to: kmail > tags 280175 unreproducible Bug#280175: pgp/mime encryption not working in kmail 1.7 There were no tags set. Tags added: unreproducible > stop Stopping processing here. Please contact me if you need

Bug#277609: acknowledged by developer (konqueror: crash at runtime)

2004-11-08 Thread Patrizio Bruno
I didn't received any email by adeodato BTW... The bug disappeared with the latest upgrade to kdelibs On Sat, 2004-11-06 at 18:48 -0800, Debian Bug Tracking System wrote: > This is an automatic notification regarding your Bug report > #277609: konqueror: crash at runtime, > which was filed against

Bug#280223: kmail: fatal error when deleting folder during download (IMAP offline)

2004-11-08 Thread Asmund Hjulstad
Package: kmail Version: 4:3.3.0-3 Severity: normal My incoming mail server is configured as offline IMAP. One of my folders contain spam filtered by some program on the server, and typically contains lots of junk. If I choose to delete the folder, choosing Delete from the context menu of the fo

Bug#280189: marked as done (juk doesn't start (anymore))

2004-11-08 Thread Debian Bug Tracking System
Your message dated Mon, 08 Nov 2004 01:16:44 -0500 with message-id <[EMAIL PROTECTED]> and subject line Oops 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 now your responsibility to reopen the