KNotify = Rediculous

Ryan ryan at crystaldawn.net
Tue Dec 20 19:00:47 GMT 2005


I have this problem with KNotify with ANY distro that I install with any 
version of KDE.  KNotify ALWAYS DISABLES ITSELF.  It's really been 
pissin me off the last few days because it's been turning my own 
~/.kde/share/knotifyrc file off even when the sound system ISNT crashed 
or down.  The only way to stop it is to chown the file to root, or 
change the permisions to be read only, but that is WRONG I dont care who 
says it's the "correct" way to fix it, it just plain shouldnt be turning 
things false without at least ASKING you to let it change to false.  
This has really been a nightmare for anyone that I've ever tried to get 
to use Linux because every single day (it never fails, it always 
happens), they call me and ask how to get sound running because it just 
suddenly stopped working.  Every time it's always the KnotifyRC that is 
the problem and I've just about had it myself. 

My question, is there ANY possible way to stop this from happening other 
than changing the permissions of the file.  Here's an example of what I 
did to test it today on my own machine.

I woke up this mornin, starting messing with some stuff in Konsole and 
noticed the damn beeps were off yet AGAIN.  So as usual, I opened the 
knotifyrc file and changed:

[StartProgress]
Arts Init=false
KNotify Init=true
Use Arts=false

to

[StartProgress]
Arts Init=true
KNotify Init=true
Use Arts=true

I then tested the sound in Konsole, and sure enough, there was none.   
So, what do I do?  Open knotify AGAIN and low and behold, its set to 
false!!!!!!!!!!!!!!!!!!!!!!  So, I set it again thinking maybe I didnt 
save the file.  Repeat, and whatya know, its False again!.  So this 
time, I get pissed and chown it to root, use root to change the file, 
test the sound again, and guess what happens.  I get this window from 
KNotify saying that it cant write to the knotifyrc file.  So I say to 
myself GOOD YOU LOUSY NO GOOD PIECE OF *****, you shouldnt be writting 
to it!  Then, right after I close that window, I HEARD THE KONSOLE 
SYSTEM NOTIFICATION SOUND!!  I'm like OMG WTF$%^*@#*$%^&*^#$%%^#@!T$%&^T&^%&

Now, why in the world is Knotify turning its self off when I just proved 
to it that that sound WAS on?  Is there a bug about this anywhere on the 
KDE site?  Because if there isnt, there should be.  It's been like this 
for me from version 3.0 to 3.5 and it's never once been fixed in KDE.  
Is it just me and my clients, or does everyone else have this problem?  
And DO NOT tell me that the fix for it is to just change the 
permissions, that's the stupidest response ever.  If you do that, then 
every time you login to KDE, you'll be greeted with an error window, and 
when you are one of my clients, you dont like error windows because they 
are scary.  There has to be an option somewhere where you can set it to 
NOT write to the file at all, or at least tell you that its going to do 
so and give you a chance to tell it that it's full of **** and doesnt 
know what its doing, and give you the chance to skip the write process.

___________________________________________________
This message is from the kde mailing list.
Account management:  https://mail.kde.org/mailman/listinfo/kde.
Archives: http://lists.kde.org/.
More info: http://www.kde.org/faq.html.




More information about the kde mailing list