From: Chris G. <cl...@is...> - 2013-01-25 15:09:30
|
On Thu, Jan 24, 2013 at 01:54:44PM -0500, John Cirillo wrote: > On 1/24/2013 12:07 PM, Chris Green wrote: > > On Thu, Jan 24, 2013 at 11:04:58AM -0500, John Cirillo wrote: > >> I seem to remember this happened a few years ago and in my > >> case was caused by the KDE > >> notification timeout defaulting to something too long, like > >> 5 seconds or so. > >> Because of that, the audio system really was temporarily > >> busy, but for no useful reason. > >> After I changed the KDE event notification timeout to 1 > >> second, all was well from then on. > >> Something to check. Not sure if other window managers have > >> something similar. > >> > > I don't run KDE but I do have a KDE application (k3b) so it *might* be > > the KDE event notification. Do you know where I might be able to see > > and/or change the KDE event notification timeout without the KDE GUI > > running? > > > I don't think that the KDE sound system nor notification > system is running if you aren't using KDE. Doesn't matter > if you have some KDE apps installed. But as to where KDE > sets this, I couldn't find it. I tried changing my timeout > from within the GUI and couldn't find any altered config > file either in the .kde directory under my user, or in > /usr/share/kde4. Sorry. > OK, thanks for looking anyway. -- Chris Green |