Linux - Software This forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum. |
Notices |
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
|
 |
09-29-2003, 07:37 AM
|
#1
|
Member
Registered: Jul 2003
Location: Bedford, UK
Distribution: Slackware 11.0, LFS 6.1
Posts: 519
Rep:
|
knotify - what is it, and why is it getting up my nose?
Hi all,
I find from time to time that when an application I am using closes the audio device and reopens it (say xmms has just finished playing one song and moves onto the next), in the intervening time a process called aplay belonging to knotify opens the audio device and starts hogging lots of cpu time. In the meantime, the audio application I was using now cannot open the audio device, and says something like "/dev/dsp cannot be opened".
I usually solve the problem by forcibly killing this aplay process. If I kill its parent, knotify, then it simply restarts itself soon after.
My question is, what is this knotify thing? And why is it doing what I am describing here? Also, is killing the process as I am doing a safe way to solve the problem?
Many thanks!
|
|
|
11-04-2003, 12:58 PM
|
#2
|
Member
Registered: Jan 2002
Location: Montreal
Distribution: Ubuntu 8.10
Posts: 178
Rep:
|
I too have come across a similar problem with knotify. It takes up to 95% of the CPU. From what I have found on the Net, kdeinit is involved. I have also been coming across about kdeinit and memory leaks. I have yet solved the problem.
|
|
|
11-04-2003, 01:09 PM
|
#3
|
Member
Registered: Jul 2003
Location: Bedford, UK
Distribution: Slackware 11.0, LFS 6.1
Posts: 519
Original Poster
Rep:
|
It hasn't done it to me for quite a while now. Haven't done anything to fix it though.
Completely unrelated to the thread, but I gotta share this with someone before I burst: I've just written a program to play Archimedes tracker tunes (similar to soundtracker mods) on my linux machine! Not finished yet but essentially working. Permission to feel chuffed, captain?
|
|
|
11-07-2003, 06:56 AM
|
#4
|
Member
Registered: Jul 2003
Location: Bedford, UK
Distribution: Slackware 11.0, LFS 6.1
Posts: 519
Original Poster
Rep:
|
I may have figured it out. If you go into the KDE configurer, and look at LookNFeel-->System Notifications, this is the same icon that knotify has when it appears in the task list in KDE system guard.
I went and turned sound off for every notification that was set to play a sound, since there's clearly a bug in the aplay program (it doesn't close the sound device and keeps running, hogging lots of cpu time) and maybe this will be an end to the problem?
I wonder what the notification was that was triggering it? No message was ever displayed.
|
|
|
04-23-2004, 02:25 PM
|
#5
|
Member
Registered: Jul 2003
Location: Bedford, UK
Distribution: Slackware 11.0, LFS 6.1
Posts: 519
Original Poster
Rep:
|
I finally worked it out!
The reason aplay didn't let go of the sound device was because it uses the aRts sound server. The sound server goes idle after a preset length of time, unless you have it in full-duplex mode, in which case it keeps running all the time. Needless to say, I had it running in full-duplex mode. Turn that off and the problem disappears. Alternatively, set all sound applications to use their aRts outputs, if they have them; that also works.
I expect the particular notification that was triggering it was probably email arriving.
|
|
|
03-11-2014, 01:33 AM
|
#6
|
Member
Registered: Apr 2011
Distribution: slackware64-current
Posts: 563
Rep:
|
Disable all KDE Notifications?
Is there away to completely disable notifications in KDE?
|
|
|
All times are GMT -5. The time now is 10:02 PM.
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|