Bug#242519: Workaround

2004-04-23 Thread Christoph Pohl
Chris Cheney wrote: kdepim 3.2.2 is already in sid. If the bug isn't fixed yet it won't likely be fixed anytime soon. That bug seems to imply the upstream author doesn't feel like fixing bugs in the 3.2 branch. Perhaps if you bug him some more he will fix it? Well, I'm not so sure about this.

Bug#242519: Workaround

2004-04-23 Thread Chris Cheney
On Fri, Apr 23, 2004 at 10:00:44AM +0200, Christoph Pohl wrote: > Chris Cheney wrote: > >kdepim 3.2.2 is already in sid. If the bug isn't fixed yet it won't > >likely be fixed anytime soon. That bug seems to imply the upstream > >author doesn't feel like fixing bugs in the 3.2 branch. Perhaps if yo

Bug#220110: marked as done (noatun: Library contains undefined non-weak symbols)

2004-04-23 Thread Debian Bug Tracking System
Your message dated Fri, 23 Apr 2004 04:28:14 -0500 with message-id <[EMAIL PROTECTED]> and subject line noatun: Library contains undefined non-weak symbols 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 ca

Bug#235025: marked as done (FTBFS: kdemultimedia-dev should depend on libxine-dev)

2004-04-23 Thread Debian Bug Tracking System
Your message dated Fri, 23 Apr 2004 04:28:58 -0500 with message-id <[EMAIL PROTECTED]> and subject line FTBFS: kdemultimedia-dev should depend on libxine-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

Bug#236443: marked as done (package juk build-depends on gcc-3.2/g++-3.2)

2004-04-23 Thread Debian Bug Tracking System
Your message dated Fri, 23 Apr 2004 04:30:02 -0500 with message-id <[EMAIL PROTECTED]> and subject line package juk build-depends on gcc-3.2/g++-3.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 i

Bug#240015: marked as done (Undeclared conflict with juk)

2004-04-23 Thread Debian Bug Tracking System
Your message dated Fri, 23 Apr 2004 04:31:48 -0500 with message-id <[EMAIL PROTECTED]> and subject line Undeclared conflict with juk 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 respo

Bug#241259: marked as done (kdemultimedia: missing build-depends on libflac-dev)

2004-04-23 Thread Debian Bug Tracking System
Your message dated Fri, 23 Apr 2004 04:33:00 -0500 with message-id <[EMAIL PROTECTED]> and subject line kdemultimedia: missing build-depends on libflac-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 ca

Bug#240015: acknowledged by developer (Undeclared conflict with juk)

2004-04-23 Thread Mark Brown
On Fri, Apr 23, 2004 at 02:48:06AM -0700, Debian Bug Tracking System wrote: > This problem is fixed with kdemultimedia 3.2.2-1 that is now in sid. > Actually this was never a problem with kdemultimedia but was the fact > that kde-i18n needed to Replaces: juk (<< 4:3.2.1) or something > similiar.

Bug#245494: ksvg: svgdisplay gets signal 11 on some images

2004-04-23 Thread Markus Schaber
Package: ksvg Version: 4:3.2.2-1 Severity: important Tags: sid Hi, on some SVG images (e. G. the attached one or the SVGAbout.svg that comes with Adobe SVG Plugin) svgdisplay gets killed with signal 11. The DrKonqi backtrace that shows up after the crash seems to be rather useless because of a la

Bug#240015: acknowledged by developer (Undeclared conflict with juk)

2004-04-23 Thread Chris Cheney
On Fri, Apr 23, 2004 at 11:40:07AM +0100, Mark Brown wrote: > On Fri, Apr 23, 2004 at 02:48:06AM -0700, Debian Bug Tracking System wrote: > > > This problem is fixed with kdemultimedia 3.2.2-1 that is now in sid. > > Actually this was never a problem with kdemultimedia but was the fact > > that kd

Bug#244715: "Use system bell" doesn't use system bell (and kills everything else)

2004-04-23 Thread Phil Edwards
On Fri, Apr 23, 2004 at 03:52:19PM -0500, Chris Cheney wrote: > It works perfect here on 2.6.6-rc1 I'm running a 2.4 kernel. All was well until KDE 3.2 decided to annihilate anything in the computer which could make sound. (I wanted a quieter system, but not this quiet.) > but I had to make su

Bug#244715: "Use system bell" doesn't use system bell (and kills everything else)

2004-04-23 Thread Chris Cheney
severity 244715 normal tags 244715 + unreproducible stop It works perfect here on 2.6.6-rc1 but I had to make sure I had the pcspkr kernel module loaded first. Beeps at console still work with KDE running as well. Chris signature.asc Description: Digital signature

Processed: "Use system bell" doesn't use system bell (and kills everything else)

2004-04-23 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]: > severity 244715 normal Bug#244715: "Use system bell" doesn't use system bell (and kills everything else) Severity set to `normal'. > tags 244715 + unreproducible Bug#244715: "Use system bell" doesn't use system bell (and kills everything else) There

Bug#244715: "Use system bell" doesn't use system bell (and kills everything else)

2004-04-23 Thread Chris Cheney
On Fri, Apr 23, 2004 at 05:00:07PM -0400, Phil Edwards wrote: > On Fri, Apr 23, 2004 at 03:52:19PM -0500, Chris Cheney wrote: > > but I had to make sure I had the > > pcspkr kernel module loaded first. Beeps at console still work with > > KDE running as well. > > I have a feeling this is going to

Bug#244715: "Use system bell" doesn't use system bell (and kills everything else)

2004-04-23 Thread Phil Edwards
On Fri, Apr 23, 2004 at 04:09:14PM -0500, Chris Cheney wrote: > > It should still work on 2.4 as well but I don't run 2.4.x anymore > since I moved to the amd64 arch. I will try to build a recent 2.4 > kernel for my box to see if I can test it. Which 2.4 kernel are you > using? 2.4.22, and kde fr

Bug#245588: kthemestyle.so gives warnings/errors on every program -- what am I supposed to do?

2004-04-23 Thread Phil Edwards
Package: kdelibs4 Version: 4:3.2.2-1 Severity: minor File: kdecore Trying to running any KDE 3.1 or 3.2 binary causes these messages to flood the screen (or the .xsession-errors file, depending on how they're started): KThemeStyle cache seems corrupt! kdecore (KIconLoader): WARNING: Icon

KDE_3_2_BRANCH: kdeaddons/debian

2004-04-23 Thread Ben Burton
CVS commit by benb: Prepare 3.2.2 upload. M +6 -0 changelog 1.26.2.6 --- kdeaddons/debian/changelog #1.26.2.5:1.26.2.6 @@ -1,2 +1,8 @@ +kdeaddons (4:3.2.2-1) unstable; urgency=low + + * New upstream bugfix release. + + -- Ben Burton <[EMAIL PROTECTED]> Sat, 24 Apr 2004 08:53:43 +1

KDE_3_2_BRANCH: kdetoys/debian

2004-04-23 Thread Ben Burton
CVS commit by benb: Prepare 3.2.2 upload. M +6 -0 changelog 1.72.2.6 --- kdetoys/debian/changelog #1.72.2.5:1.72.2.6 @@ -1,2 +1,8 @@ +kdetoys (4:3.2.2-1) unstable; urgency=low + + * New upstream bugfix release. + + -- Ben Burton <[EMAIL PROTECTED]> Sat, 24 Apr 2004 08:53:43 +1000