Bug#253127: kdecore (KIconLoader): WARNING: Icon directory group is not valid

2004-07-16 Thread Phil Edwards
On Tue, Jul 13, 2004 at 11:50:17PM +0200, Dominique Devriese wrote: > Phil Edwards writes: > > > The patch only downgrades the severity of the diagnostic. > > That is not true. The debugging output is disabled in non-debug > builds like debian's build, and the patch

Bug#253127: kdecore (KIconLoader): WARNING: Icon directory group is not valid

2004-07-13 Thread Phil Edwards
The patch only downgrades the severity of the diagnostic. I'd still like to know whst an end-user like me can do to avoid /hundreds/ of these useless messages every time a KDE program is run, especially if there's not going to be another KDE release after the current 3.2.3, which doesn't have the

Bug#214514: klipper freezes, but can be unfrozen by pressing Alt

2004-06-29 Thread Phil Edwards
This happens to me every couple of days, and a tap of Alt always gets it back. I've never used OpenOffice, though, and never noticed klipper's behavior tied to any other app in particular. (I'll try to take note in the future.) Using 3.2.2-1 here. Phil

Bug#256618: Dropping to a console prompt times out and returns to login screen

2004-06-28 Thread Phil Edwards
Package: kdm Version: 4:3.2.2-1 Severity: minor Since KDE 3.2 was first packaged, I've been seeing an annoying oddity. Normally, if you use Alt-N (or mouse through the dropdown menu) at the KDM login screen to drop to a console, KDM starts its normal countdown clock. If you don't login after a mi

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

2004-05-21 Thread Phil Edwards
On Thu, May 20, 2004 at 08:19:15PM -0700, Frank Jas wrote: > > >On this box, the hardware beep /must/ work. And it works fine, outside > >of KDE. But once KDE starts up, artsd takes over the system beep, and > >artsd doesn't work. The "System Bell" module has its checkbox next to > >"use the syste

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

2004-04-30 Thread Phil Edwards
Got desperate and moved to 2.6.5 and ALSA, all sources from sid. Built the pcspkr module into the kernel, rather than leaving it separate (when would I /not/ want it loaded?), and built all the sound modules. KDE continues to take control of the system beep. It now works at the console, even wh

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

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#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-19 Thread Phil Edwards
Package: arts Version: 1.2.2-1 Severity: grave My first thought was 'critical', following its description of "makes unrelated software on the system break," but surely this can't be that hard to fix... On this box, the hardware beep /must/ work. And it works fine, outside of KDE. But once KDE

Bug#243749: man pages are f*cking useless

2004-04-15 Thread Phil Edwards
On Thu, Apr 15, 2004 at 08:48:42AM +0200, Dominique Devriese wrote: > Phil Edwards writes: > > > I have no /idea/ what the options do. That's why I looked at the > > man page! > > Well, neither do we. Oh, wonderful. > For now, you'll have to do

Bug#243749: man pages are f*cking useless

2004-04-14 Thread Phil Edwards
On Wed, Apr 14, 2004 at 10:31:49PM +0200, Dominique Devriese wrote: > Phil Edwards writes: > > > Imagine my joy when the artsd man page lists nothing but "fixme" in > > every paragraph and for every option. You have no idea how > > frustrating this is. Why did

Bug#243749: man pages are f*cking useless

2004-04-14 Thread Phil Edwards
Package: libarts1 Version: 1.2.2-1 Severity: normal I am trying to debug a sound problem that has stumped everybody that's looked at it so far. I track it down to a running "artsd" with lots of odd-looking parameters on its command line. Imagine my joy when the artsd man page lists nothing but "

Bug#237184: deleting knotes files doesn't fix Display/Actions spawning bug

2004-04-12 Thread Phil Edwards
I also tried deleting .kde/share/apps/knotes. Upon next login, knotes still spawned a new [Display] note (but only one, instead of dozens). Changing the preferences as to default width and text font doesn't have an effect, either; I can see the correct changes are saved to .kde/config/knotesrc,

Bug#237184: Additional note for knotes spawning bug

2004-04-08 Thread Phil Edwards
I'll add that this bug has the additional feature of pegging the CPU at 100% when knotes->quit is clicked. Sending the knotes process SIGTERM seems to do no additional harm.