KDE_3_3_BRANCH: kdeedu/debian

CVS commit by benb: Prepare 3.3.2 upload. M +8 -0 changelog 1.16.2.12 --- kdeedu/debian/changelog #1.16.2.11:1.16.2.12 @@ -1,2 +1,10 @@ +kdeedu (4:3.3.2-1) unstable; urgency=low + + * New upstream bugfix release. + * The moon images are now licensed under the GPL (closes: #266404)

KDE_3_3_BRANCH: kdeedu/debian

CVS commit by benb: Sanity tests for boost scripting. M +2 -0 changelog 1.16.2.13 M +9 -1 rules 1.14.2.6 --- kdeedu/debian/changelog #1.16.2.12:1.16.2.13 @@ -4,4 +4,6 @@ * The moon images are now licensed under the GPL (closes: #266404). * Built against boost 1.32.0.

KDE_3_3_BRANCH: kdeedu/debian

CVS commit by benb: Re-enable boost.python scripting under arm. M +3 -1 changelog 1.16.2.14 M +1 -1 control 1.20.2.8 M +10 -8 rules 1.14.2.7 --- kdeedu/debian/changelog #1.16.2.13:1.16.2.14 @@ -4,6 +4,8 @@ * The moon images are now licensed under the GPL (closes:

Patch: Ignore autofs in Konqueror 'devices:/'

This Patch removes autofs-filesystems from Konqueror's 'devices:/' view. To apply use 'patch -p1 < ignore-autofs.diff'. autofs is a virtual filesystem used by the kernelbased autofs-automounter. Devices managed by the autofs-automounter appear as subdirectories of an autofs-filesystem. So autof

Bug#280175: kmail: KMail ceased to bea able to decrypt it's own messages without gpgagent

Package: kmail Version: 4:3.3.1-3 Followup-For: Bug #280175 It seems KMail is no longer able to decrypt mails encrypted by KMail (At least that's the result I'm getting.) without installing gpgagent (wich AFAICS is not contained in Debian). I consider this a serious bug. See http://bugs.kde.org/s

Bug#267578: marked as done (KDE 3.3 in Debian is based on pre-release CVS tree.)

Your message dated Sun, 16 Jan 2005 21:43:32 +0100 with message-id <[EMAIL PROTECTED]> and subject line KDE 3.3 is now official 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 responsibi

KDE_3_3_BRANCH: kdetoys/debian

CVS commit by benb: Prepare 3.3.2 upload. M +6 -0 changelog 1.76.2.5 --- kdetoys/debian/changelog #1.76.2.4:1.76.2.5 @@ -1,2 +1,8 @@ +kdetoys (4:3.3.2-1) unstable; urgency=medium + + * New upstream bugfix release. + + -- Ben Burton <[EMAIL PROTECTED]> Mon, 17 Jan 2005 08:53:18 +11

Processing of kdelibs_3.3.2-1_i386.changes

kdelibs_3.3.2-1_i386.changes uploaded successfully to localhost along with the files: kdelibs_3.3.2-1.dsc kdelibs_3.3.2-1.diff.gz kdelibs-bin_3.3.2-1_i386.deb kdelibs4_3.3.2-1_i386.deb kdelibs4-dev_3.3.2-1_i386.deb kdelibs_3.3.2-1_all.deb kdelibs-data_3.3.2-1_all.deb kdelibs4-doc_3.

Bug#287566: marked as done (KAccel handling causes mass konqueror segfaults on russian systems)

Your message dated Sun, 16 Jan 2005 17:02:25 -0500 with message-id <[EMAIL PROTECTED]> and subject line Bug#287566: fixed in kdelibs 4:3.3.2-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#290191: marked as done (Improper copyright file)

Your message dated Sun, 16 Jan 2005 17:02:25 -0500 with message-id <[EMAIL PROTECTED]> and subject line Bug#290191: fixed in kdelibs 4:3.3.2-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#290190: marked as done (Improper copyright file)

Your message dated Sun, 16 Jan 2005 17:02:25 -0500 with message-id <[EMAIL PROTECTED]> and subject line Bug#290190: fixed in kdelibs 4:3.3.2-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#286521: marked as done (kdelibs: CAN-2004-1145: Konqueror Java Vulnerability)

Your message dated Sun, 16 Jan 2005 17:02:24 -0500 with message-id <[EMAIL PROTECTED]> and subject line Bug#286521: fixed in kdelibs 4:3.3.2-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#285128: marked as done (CAN-2004-1165: FTP command injection bug)

Your message dated Sun, 16 Jan 2005 17:02:24 -0500 with message-id <[EMAIL PROTECTED]> and subject line Bug#285128: fixed in kdelibs 4:3.3.2-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#263430: marked as done (kaddprinterwizard overwrites cups admin group)

Your message dated Sun, 16 Jan 2005 17:02:24 -0500 with message-id <[EMAIL PROTECTED]> and subject line Bug#263430: fixed in kdelibs 4:3.3.2-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#287097: marked as done (Experimental kdelibs-data conflicts with Sarge openoffice.org-mimelnk)

Your message dated Sun, 16 Jan 2005 17:02:25 -0500 with message-id <[EMAIL PROTECTED]> and subject line Bug#287097: fixed in kdelibs 4:3.3.2-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#287201: marked as done (KIOSlave FTP client can be made to send email)

Your message dated Sun, 16 Jan 2005 17:02:24 -0500 with message-id <[EMAIL PROTECTED]> and subject line Bug#285128: fixed in kdelibs 4:3.3.2-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#288653: marked as done (kdelibs-data fails to install because of a clash with kjscmd)

Your message dated Sun, 16 Jan 2005 17:02:25 -0500 with message-id <[EMAIL PROTECTED]> and subject line Bug#288653: fixed in kdelibs 4:3.3.2-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#289164: marked as done (kdelibs-bin: Please relax dependency on perl-suid)

Your message dated Sun, 16 Jan 2005 17:02:25 -0500 with message-id <[EMAIL PROTECTED]> and subject line Bug#289164: fixed in kdelibs 4:3.3.2-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

kdelibs_3.3.2-1_i386.changes ACCEPTED

Accepted: kdelibs-bin_3.3.2-1_i386.deb to pool/main/k/kdelibs/kdelibs-bin_3.3.2-1_i386.deb kdelibs-data_3.3.2-1_all.deb to pool/main/k/kdelibs/kdelibs-data_3.3.2-1_all.deb kdelibs4-dev_3.3.2-1_i386.deb to pool/main/k/kdelibs/kdelibs4-dev_3.3.2-1_i386.deb kdelibs4-doc_3.3.2-1_all.deb to poo

Bug#290815: korn: doesn't warn on wrong password

Package: korn Version: 4:3.3.1-3 Severity: normal I spent a lot of time trying to find a mail checker for KDE, and when it worked, realized the reason for which korn didn't work was very simple : I had the wrong password in mind, and korn did nothing to warn me, always showing "0" new mails. Appar

Bug#271954: marked as done (Adding new file associations under Konqueror is broke)

Your message dated Mon, 17 Jan 2005 00:39:55 +0100 with message-id <[EMAIL PROTECTED]> and subject line File associations are working correctly now 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

Bug#255646: marked as done (kdebase: New upstream version fixes various focus issues.)

Your message dated Mon, 17 Jan 2005 00:38:49 +0100 with message-id <[EMAIL PROTECTED]> and subject line KDE 3.2.3 was uploaded months ago 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

Bug#237472: marked as done (kdebase depends on tomcat???)

Your message dated Mon, 17 Jan 2005 00:37:42 +0100 with message-id <[EMAIL PROTECTED]> and subject line The problem was in the user system 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

Bug#255750: marked as done (probably misses build-depends on xlibs-static-dev)

Your message dated Mon, 17 Jan 2005 00:45:22 +0100 with message-id <[EMAIL PROTECTED]> and subject line kdebase already build depends on xlibs-static-pic 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

Bug#265574: marked as done (kdebase: systray (and superkaramba systray!) crash on quit apps)

Your message dated Mon, 17 Jan 2005 00:42:27 +0100 with message-id <[EMAIL PROTECTED]> and subject line systray doesn't crash anymore 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 resp

Bug#270702: marked as done (Ignores .desktop file names starting with letter k)

Your message dated Mon, 17 Jan 2005 00:46:03 +0100 with message-id <[EMAIL PROTECTED]> and subject line kino is appearing correctly in the K Menu now 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

Bug#290815: Acknowledgement (korn: doesn't warn on wrong password)

retitle 290815 POP3 doesn't warn on wrong password thank I forgot to say this happens using POP3 checks. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Processed: Re: file conflicts in libsmokeqt1 libsmokeqt-dev libqt-perl

Processing commands for [EMAIL PROTECTED]: > tags 274779 -sarge Bug#274779: file conflicts in libsmokeqt1 libsmokeqt-dev libqt-perl Tags were: sarge patch Tags removed: sarge > tags 274779 +fixed Bug#274779: file conflicts in libsmokeqt1 libsmokeqt-dev libqt-perl Tags were: patch Tags added: fixe

Processed: kdebase 4:3.3.1-4 in sarge

Processing commands for [EMAIL PROTECTED]: > tags 286516 -sarge Bug#286516: kdebase: CAN-2004-1158: Konqueror Window Injection Vulnerability Tags were: security sarge Tags removed: sarge > close 286516 Bug#286516: kdebase: CAN-2004-1158: Konqueror Window Injection Vulnerability 'close' is depreca

Bug#274779: file conflicts in libsmokeqt1 libsmokeqt-dev libqt-perl

tags 274779 -sarge tags 274779 +fixed thanks The 3.008-1.3 NMU version of libqt-perl has reached testing today, fixing this bug. Thanks, -- Steve Langasek postmodern programmer signature.asc Description: Digital signature

Bug#243590: marked as done (kdm is segfaulting on start)

Your message dated Sun, 16 Jan 2005 20:28:11 -0500 with message-id <[EMAIL PROTECTED]> and subject line kdm is segfaulting on start 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 respon

Bug#247406: marked as done (kcontrol doesn't show any configuration modules)

Your message dated Sun, 16 Jan 2005 20:30:49 -0500 with message-id <[EMAIL PROTECTED]> and subject line kcontrol doesn't show any configuration modules 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 i

Bug#244065: marked as done (konqueror: opens new window every time I click a html link)

Your message dated Sun, 16 Jan 2005 20:29:24 -0500 with message-id <[EMAIL PROTECTED]> and subject line konqueror: opens new window every time I click a html link 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

Bug#256720: marked as done (kdeprint: error printing with CUPS -- no filter)

Your message dated Sun, 16 Jan 2005 20:36:22 -0500 with message-id <[EMAIL PROTECTED]> and subject line CUPS "print error happened. Error message received from system:" 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

Bug#253028: marked as done (konqueror unable to print)

Your message dated Sun, 16 Jan 2005 20:36:22 -0500 with message-id <[EMAIL PROTECTED]> and subject line CUPS "print error happened. Error message received from system:" 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

Bug#261909: marked as done ((no subject))

Your message dated Sun, 16 Jan 2005 20:32:34 -0500 with message-id <[EMAIL PROTECTED]> and subject line kcontrol: kcminit crashes on startup 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 yo

Bug#272211: marked as done (KDM crashes when right "start" button pressed)

Your message dated Sun, 16 Jan 2005 20:37:34 -0500 with message-id <[EMAIL PROTECTED]> and subject line KDM crashes when right "start" button pressed 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

Bug#276487: marked as done (konqueror: crash when loading http://conit.com/)

Your message dated Sun, 16 Jan 2005 20:39:20 -0500 with message-id <[EMAIL PROTECTED]> and subject line crash when loading http://conit.com/ 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 yo

Bug#253700: marked as done (konqueror history exposure of username and password)

Your message dated Sun, 16 Jan 2005 21:03:18 -0500 with message-id <[EMAIL PROTECTED]> and subject line Bug no longer relevant, so closing 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

Bug#243956: marked as done (konqueror: Locks up consistently)

Your message dated Sun, 16 Jan 2005 21:03:18 -0500 with message-id <[EMAIL PROTECTED]> and subject line Bug no longer relevant, so closing 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

Bug#237042: marked as done (lanbrowsing tree in konq sidebar should not be visible unless lisa is installed)

Your message dated Sun, 16 Jan 2005 21:03:18 -0500 with message-id <[EMAIL PROTECTED]> and subject line Bug no longer relevant, so closing 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

Bug#238813: marked as done (konqueror: Locks at http://www.sharpusa.com/)

Your message dated Sun, 16 Jan 2005 21:03:18 -0500 with message-id <[EMAIL PROTECTED]> and subject line Bug no longer relevant, so closing 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

Bug#234111: marked as done (konqueror: [armv4l] PNG image on search.cpan.org crashes konqueror)

Your message dated Sun, 16 Jan 2005 21:03:18 -0500 with message-id <[EMAIL PROTECTED]> and subject line Bug no longer relevant, so closing 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

Bug#231688: marked as done (kicker fail some minutes after start)

Your message dated Sun, 16 Jan 2005 21:03:18 -0500 with message-id <[EMAIL PROTECTED]> and subject line Bug no longer relevant, so closing 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

Bug#222662: marked as done (konqueror: Segfaults)

Your message dated Sun, 16 Jan 2005 21:03:18 -0500 with message-id <[EMAIL PROTECTED]> and subject line Bug no longer relevant, so closing 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

Bug#219906: marked as done (kcontrol: /usr/bin/fileshareset broken)

Your message dated Sun, 16 Jan 2005 21:03:18 -0500 with message-id <[EMAIL PROTECTED]> and subject line Bug no longer relevant, so closing 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

Bug#217717: marked as done (kcontrol: unable to set clock)

Your message dated Sun, 16 Jan 2005 21:03:18 -0500 with message-id <[EMAIL PROTECTED]> and subject line Bug no longer relevant, so closing 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

Bug#216929: marked as done (konqueror: clicking out of file rename crashes)

Your message dated Sun, 16 Jan 2005 21:03:18 -0500 with message-id <[EMAIL PROTECTED]> and subject line Bug no longer relevant, so closing 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

Bug#212925: marked as done (konqueror: renaming a file on the desktop is necessary twice)

Your message dated Sun, 16 Jan 2005 21:03:18 -0500 with message-id <[EMAIL PROTECTED]> and subject line Bug no longer relevant, so closing 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

Bug#216073: marked as done (kdm 3.1.4 woody backport: Doesn't work with fontconfig 2.1)

Your message dated Sun, 16 Jan 2005 21:03:18 -0500 with message-id <[EMAIL PROTECTED]> and subject line Bug no longer relevant, so closing 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

Bug#211542: marked as done (konqueror: columns wrong rendered (not wide enough) and overlapping)

Your message dated Sun, 16 Jan 2005 21:03:18 -0500 with message-id <[EMAIL PROTECTED]> and subject line Bug no longer relevant, so closing 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

Bug#207556: marked as done (konqueror-nsplugins: Acroread plugin does not work)

Your message dated Sun, 16 Jan 2005 21:03:18 -0500 with message-id <[EMAIL PROTECTED]> and subject line Bug no longer relevant, so closing 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

Bug#209305: marked as done (fonts problem in kde after recent upgrade)

Your message dated Sun, 16 Jan 2005 21:03:18 -0500 with message-id <[EMAIL PROTECTED]> and subject line Bug no longer relevant, so closing 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

Bug#203709: marked as done (konsole: cannot use Ctrl+something for keyboard shortcuts)

Your message dated Sun, 16 Jan 2005 21:03:18 -0500 with message-id <[EMAIL PROTECTED]> and subject line Bug no longer relevant, so closing 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

Bug#201189: marked as done (kdebase-bin: kxkb crashes when KDE is started through VNC)

Your message dated Sun, 16 Jan 2005 21:03:18 -0500 with message-id <[EMAIL PROTECTED]> and subject line Bug no longer relevant, so closing 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

Bug#198306: marked as done (kicker: Kicker freezes for some seconds after executing a program)

Your message dated Sun, 16 Jan 2005 21:03:18 -0500 with message-id <[EMAIL PROTECTED]> and subject line Bug no longer relevant, so closing 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

Bug#197369: marked as done (Bug with Luxi Mono font)

Your message dated Sun, 16 Jan 2005 21:03:18 -0500 with message-id <[EMAIL PROTECTED]> and subject line Bug no longer relevant, so closing 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

Bug#196723: marked as done (konqueror: segfault when opening an xml file (included))

Your message dated Sun, 16 Jan 2005 21:03:18 -0500 with message-id <[EMAIL PROTECTED]> and subject line Bug no longer relevant, so closing 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

Bug#194398: marked as done (Kicker eats 20% cpu on 1.3ghz athlon)

Your message dated Sun, 16 Jan 2005 21:03:18 -0500 with message-id <[EMAIL PROTECTED]> and subject line Bug no longer relevant, so closing 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

Bug#193124: marked as done (khelpcenter: Second window opens on session restore)

Your message dated Sun, 16 Jan 2005 21:03:18 -0500 with message-id <[EMAIL PROTECTED]> and subject line Bug no longer relevant, so closing 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

Bug#180352: marked as done (pixel droppings in konsole)

Your message dated Sun, 16 Jan 2005 21:03:18 -0500 with message-id <[EMAIL PROTECTED]> and subject line Bug no longer relevant, so closing 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

Bug#156949: marked as done (konqueror: manpage browser doesn't understand roff character sequences)

Your message dated Sun, 16 Jan 2005 21:03:18 -0500 with message-id <[EMAIL PROTECTED]> and subject line Bug no longer relevant, so closing 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

Bug#116585: marked as done (konqueror settings: searching for cookies)

Your message dated Sun, 16 Jan 2005 21:03:18 -0500 with message-id <[EMAIL PROTECTED]> and subject line Bug no longer relevant, so closing 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

Bug#121933: marked as done (konq crashes when following network tree)

Your message dated Sun, 16 Jan 2005 21:03:18 -0500 with message-id <[EMAIL PROTECTED]> and subject line Bug no longer relevant, so closing 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

Bug#121344: marked as done (kdebase: kcontrol - large cursor cannot be set)

Your message dated Sun, 16 Jan 2005 21:03:18 -0500 with message-id <[EMAIL PROTECTED]> and subject line Bug no longer relevant, so closing 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

Bug#107756: marked as done (printing some webpages gives white sheets)

Your message dated Sun, 16 Jan 2005 21:03:18 -0500 with message-id <[EMAIL PROTECTED]> and subject line Bug no longer relevant, so closing 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

Bug#145376: marked as done (gtk2.0-examples: "Button Boxes" demo: ugly vertical resizing)

Your message dated Sun, 16 Jan 2005 21:03:18 -0500 with message-id <[EMAIL PROTECTED]> and subject line Bug no longer relevant, so closing 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

Bug#131545: marked as done (title ignored in imagemaps)

Your message dated Sun, 16 Jan 2005 21:03:18 -0500 with message-id <[EMAIL PROTECTED]> and subject line Bug no longer relevant, so closing 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

Bug#123535: marked as done (konqueror inserts line breaks where there's no whitespace)

Your message dated Sun, 16 Jan 2005 21:03:18 -0500 with message-id <[EMAIL PROTECTED]> and subject line Bug no longer relevant, so closing 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

Bug#196679: marked as done (kdebase: all kde chars are boxes)

Your message dated Sun, 16 Jan 2005 21:03:18 -0500 with message-id <[EMAIL PROTECTED]> and subject line Bug no longer relevant, so closing 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

Bug#198152: marked as done (konqueror: crashes on first launch. subequent launches succeed)

Your message dated Sun, 16 Jan 2005 21:03:18 -0500 with message-id <[EMAIL PROTECTED]> and subject line Bug no longer relevant, so closing 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

Bug#197425: marked as done (kicker: Clock applet doesn't like Central Daylight Time)

Your message dated Sun, 16 Jan 2005 21:03:18 -0500 with message-id <[EMAIL PROTECTED]> and subject line Bug no longer relevant, so closing 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

Bug#200314: marked as done (konqueror: CSS bug)

Your message dated Sun, 16 Jan 2005 21:03:18 -0500 with message-id <[EMAIL PROTECTED]> and subject line Bug no longer relevant, so closing 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

Bug#202685: marked as done (konqueror: Konq crashes when right clicking out of the window while selecting a group of files)

Your message dated Sun, 16 Jan 2005 21:03:18 -0500 with message-id <[EMAIL PROTECTED]> and subject line Bug no longer relevant, so closing 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

Bug#205009: marked as done (klipper: vim on x-terminal in visual mode)

Your message dated Sun, 16 Jan 2005 21:03:18 -0500 with message-id <[EMAIL PROTECTED]> and subject line Bug no longer relevant, so closing 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

Bug#217300: marked as done (konqueror very slow when I move a lot of files)

Your message dated Sun, 16 Jan 2005 21:03:18 -0500 with message-id <[EMAIL PROTECTED]> and subject line Bug no longer relevant, so closing 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

Bug#227199: marked as done (keditbookmarks do not start with my bookmarks)

Your message dated Sun, 16 Jan 2005 21:03:18 -0500 with message-id <[EMAIL PROTECTED]> and subject line Bug no longer relevant, so closing 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

Bug#232501: marked as done (konsole uses bad default Unicode font)

Your message dated Sun, 16 Jan 2005 21:03:18 -0500 with message-id <[EMAIL PROTECTED]> and subject line Bug no longer relevant, so closing 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

Bug#234656: marked as done (konqueror: Wrong layout when rendering Koha's MARC acquisition screen)

Your message dated Sun, 16 Jan 2005 21:03:18 -0500 with message-id <[EMAIL PROTECTED]> and subject line Bug no longer relevant, so closing 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

Bug#89622: marked as done (session manager works with all dockapps except 'wmusic -w')

Your message dated Sun, 16 Jan 2005 21:03:18 -0500 with message-id <[EMAIL PROTECTED]> and subject line Bug no longer relevant, so closing 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

Bug#280826: marked as done (kdelibs4: shlibs not increased when new symbols introduced)

Your message dated Sun, 16 Jan 2005 21:21:01 -0500 with message-id <[EMAIL PROTECTED]> and subject line Bugs fixed in 3.3.2-1 upload to unstable 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 no

Bug#263372: marked as done (kcontrol: crashes on start)

Your message dated Sun, 16 Jan 2005 21:21:01 -0500 with message-id <[EMAIL PROTECTED]> and subject line Bugs fixed in 3.3.2-1 upload to unstable 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 no

Bug#250631: marked as done (kdelibs-bin: Please mention kdcop in man page of dcop)

Your message dated Sun, 16 Jan 2005 21:21:01 -0500 with message-id <[EMAIL PROTECTED]> and subject line Bugs fixed in 3.3.2-1 upload to unstable 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 no

Bug#279851: marked as done (move kdewidgets.so to kdelibs4-dev)

Your message dated Sun, 16 Jan 2005 21:50:36 -0500 with message-id <[EMAIL PROTECTED]> and subject line move kdewidgets.so to kdelibs4-dev 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

Processed: Re: Bug#243590 acknowledged by developer (Re: kdm is segfaulting on start)

Processing commands for [EMAIL PROTECTED]: > reopen 243590 Bug#243590: kdm is segfaulting on start Bug reopened, originator not changed. > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database)

Bug#243590: acknowledged by developer (Re: kdm is segfaulting on start)

* Zed Pobre [Sun, 16 Jan 2005 23:40:39 -0600]: > but please do not > close it while it is still possible for someone to "apt-get install > kdm" and end up with a system where he or she cannot log into a > graphical session. may I assume, then, that the following still is true? * Zed Pobre [Wed

Bug#243590: acknowledged by developer (Re: kdm is segfaulting on start)

* Zed Pobre [Mon, 17 Jan 2005 01:11:00 -0600]: > I have a couple machines left in the department that haven't been > upgraded yet, so I'll try to do a partial upgrade on a couple and see > if I can nail down the exact break to confirm this. ok, thanks. > That can't happen until tomorrow at