KDE 3.4 and System Notification Problem SOLVED
Well, it's solved on my system anyway. Like several others on this list, after updating to KDE 3.4, I could play sounds, but the System notifications didn't work. I found the answer on linuxquestions.org Open /opt/kde3/bin/startkde and find the line that reads: "LD_BIND_NOW=true kdeinit +kcminit" That should be on two lines like this: "LD_BIND_NOW=true kdeinit+kcminit" Now, add the line: "KNotify Init=true" to the [StartProgress] section of ~/.kde/share/config/knotifyrc. That worked for me! -- __________ CorvusE Linux User #370082
CorvusE wrote:
Well, it's solved on my system anyway. Like several others on this list, after updating to KDE 3.4, I could play sounds, but the System notifications didn't work.
I found the answer on linuxquestions.org
Thanks for the searching. ;-)
Open /opt/kde3/bin/startkde and find the line that reads:
"LD_BIND_NOW=true kdeinit +kcminit"
That should be on two lines like this:
"LD_BIND_NOW=true kdeinit+kcminit"
I did that, it was as you said.
Now, add the line:
"KNotify Init=true"
This was already in mine correctly.
to the [StartProgress] section of ~/.kde/share/config/knotifyrc.
That worked for me!
It still didn't fix mine (and I was so hopeful. I then went into System Notifications in Control Center, Sound & Multimedia (KDE System Notifications section). Even though sounds were on, it still didn't work. I then went to the Player Settings, and tried to adjust the volume (it was at 100%). The slider moved but the percentage didn't, so I changed it back to 100%, hit Apply, then OK, and tried the sounds again. They worked. Logged out and back in, and it worked (but later than it used to be. Anyway, hopefully it is fixed now. -- Joe Morris New Tribes Mission Email Address: Joe_Morris@ntm.org Registered Linux user 231871
On Friday 18 March 2005 14:06, Joe Morris (NTM) wrote:
It still didn't fix mine (and I was so hopeful. I then went into System Notifications in Control Center, Sound & Multimedia (KDE System Notifications section). Even though sounds were on, it still didn't work. I then went to the Player Settings, and tried to adjust the volume (it was at 100%). The slider moved but the percentage didn't, so I changed it back to 100%, hit Apply, then OK, and tried the sounds again. They worked. Logged out and back in, and it worked (but later than it used to be. Anyway, hopefully it is fixed now.
Yes, I should have included the KDE restart, shouldn't I have! I had a moment of panic when I suddenly realized (just after firing off the SOLVED message, that I no longer had 3d acceleration. I was momentarily convinced that my audio solution was going to muck everyone up but good. fortunately, a quick reapplication of the fetchnvidia via YaST got me straightened back out. Perhaps tomorrow I'll reinstall the latest drivers, but for now I'm just happy to have gone through a KDE upgrade that didn't completely bring me to my knees in despair! Incidently, my startup ogg plays later too. -- __________ CorvusE Linux User #370082
On Friday 18 March 2005 20:18, CorvusE wrote:
Incidently, my startup ogg plays later too.
Probably a result of the missing 'LD_BIND_NOW=true' in front of the 'kdeinit +kcminit'. See my other reply to your initial message. Cheers, Leen
Joe Morris (NTM) wrote:
Open /opt/kde3/bin/startkde and find the line that reads:
"LD_BIND_NOW=true kdeinit +kcminit"
That should be on two lines like this:
"LD_BIND_NOW=true kdeinit+kcminit" I just tried it back the way it was originally, and it still works, so it appears that is not the fix. (If someone knows programming and could check this line and verify if they are different or what). It still didn't fix mine (and I was so hopeful. I then went into System Notifications in Control Center, Sound & Multimedia (KDE System Notifications section). Even though sounds were on, it still didn't work. I then went to the Player Settings, and tried to adjust the volume (it was at 100%). The slider moved but the percentage didn't, so I changed it back to 100%, hit Apply, then OK, and tried the sounds again. They worked. Logged out and back in, and it worked (but later
CorvusE wrote: than it used to be. Anyway, hopefully it is fixed now. Well, comparing ~/.kde/share/config/knotifyrc to yesterdays backup only saw the volume go from 99 to 100, so I don't know why it is now working. I did also clean out the temp directories. -- Joe Morris New Tribes Mission Email Address: Joe_Morris@ntm.org Registered Linux user 231871
On Friday 18 March 2005 18:53, CorvusE wrote:
Well, it's solved on my system anyway. Like several others on this list, after updating to KDE 3.4, I could play sounds, but the System notifications didn't work.
I found the answer on linuxquestions.org
Open /opt/kde3/bin/startkde and find the line that reads:
"LD_BIND_NOW=true kdeinit +kcminit"
That should be on two lines like this:
"LD_BIND_NOW=true kdeinit+kcminit"
Seems this is just dead wrong. See http://dot.kde.org/1059469759/1059488101/
Now, add the line:
"KNotify Init=true"
to the [StartProgress] section of ~/.kde/share/config/knotifyrc.
This is not necessary. Just changing the line LD_BIND_NOW=true kdeinit +kcminit into kdeinit +kcminit" and not more has the same effect. But, like I said, this is IMO the *wrong* solution. But I think LD_BIND_NOW has indeed something to do with the failing system sounds and the arts-built-at-home-is-ok-solution. Sorry, CorvusE. I have to admit, it is a way to get the system sounds working, but it is - IMO - not the /right/ solution. Cheers, Leen
On Friday 18 March 2005 14:20, Leendert Meyer wrote:
That should be on two lines like this:
"LD_BIND_NOW=true kdeinit+kcminit"
Seems this is just dead wrong. See http://dot.kde.org/1059469759/1059488101/
This is not necessary. Just changing the line
LD_BIND_NOW=true kdeinit +kcminit
into
kdeinit +kcminit"
and not more has the same effect.
But, like I said, this is IMO the *wrong* solution. But I think LD_BIND_NOW has indeed something to do with the failing system sounds and the arts-built-at-home-is-ok-solution.
Sorry, CorvusE. I have to admit, it is a way to get the system sounds working, but it is - IMO - not the /right/ solution.
No need to be sorry, I'm still pretty new at the Linux side of things. The audio system, in particular, gives me fits. I did try compiling the arts package myself, and it didn't fix my problem, which is why I kept looking and stumbled onto this. -- __________ CorvusE Linux User #370082
On Friday 18 March 2005 20:38, CorvusE wrote:
The audio system, in particular, gives me fits.
Gives you fits? I do not understand, what does 'fits' mean in this context? (English is not my native language - sometimes that gives me a tiny problem, like now ;)
I did try compiling the arts package myself, and it didn't fix my problem,
If you did rpmbuild --rebuild arts-1.4.0-8.src.rpm you also need to logout of KDE, and do as root: cd /usr/src/packages/RPMS/i586 rpm -Uhv --oldpackage arts-1.4.0-8.i586.rpm SuSEconfig and login again in KDE.
which is why I kept looking and stumbled onto this.
Of course, understandable. ;) BTW, I looked for it on linuxquestions.org, but could not find it. Can you give me a pointer? Cheers, Leen
On Friday 18 March 2005 02:48 pm, Leendert Meyer wrote:
On Friday 18 March 2005 20:38, CorvusE wrote:
The audio system, in particular, gives me fits.
Gives you fits? I do not understand, what does 'fits' mean in this context?
(English is not my native language - sometimes that gives me a tiny problem, like now ;)
No worries, Leen. There are English speakers who stare at me blankly as well. What I meant to say was that dealing with audio configuration between ALSA, arts, and applications that require OSS, makes me want to tear out my hair and throw a fit, or temper tantrum.
I did try compiling the arts package myself, and it didn't fix my problem,
If you did
rpmbuild --rebuild arts-1.4.0-8.src.rpm
you also need to logout of KDE, and do as root:
cd /usr/src/packages/RPMS/i586 rpm -Uhv --oldpackage arts-1.4.0-8.i586.rpm SuSEconfig
and login again in KDE.
Those aren't the steps I took, but I think I wound up in the same place. That process, though, is quite useful. Thank you for that!
Of course, understandable. ;) BTW, I looked for it on linuxquestions.org, but could not find it. Can you give me a pointer?
Well, remembering similar issues with my last KDE upgrade, I widened my search beyond 3.4 and found this thread: http://www.linuxquestions.org/questions/history/295250 -- __________ CorvusE Linux User #370082
Corvus, On Friday 18 March 2005 11:38, CorvusE wrote:
On Friday 18 March 2005 14:20, Leendert Meyer wrote:
...
But, like I said, this is IMO the *wrong* solution. But I think LD_BIND_NOW has indeed something to do with the failing system sounds and the arts-built-at-home-is-ok-solution.
Sorry, CorvusE. I have to admit, it is a way to get the system sounds working, but it is - IMO - not the /right/ solution.
No need to be sorry, I'm still pretty new at the Linux side of things. The audio system, in particular, gives me fits. I did try compiling the arts package myself, and it didn't fix my problem, which is why I kept looking and stumbled onto this.
Keep in mind you may have needed _both_ the rebuilt arts packages _and_ the modification(s) to the configuration file(s). For me, the rebuilt packages fixed the symptom, but my config files already held the two configuration details you originally posted.
CorvusE
Randall Schulz
On Friday 18 March 2005 20:50, Randall R Schulz wrote:
Corvus,
On Friday 18 March 2005 11:38, CorvusE wrote:
On Friday 18 March 2005 14:20, Leendert Meyer wrote:
...
But, like I said, this is IMO the *wrong* solution. But I think LD_BIND_NOW has indeed something to do with the failing system sounds and the arts-built-at-home-is-ok-solution.
Sorry, CorvusE. I have to admit, it is a way to get the system sounds working, but it is - IMO - not the /right/ solution.
No need to be sorry, I'm still pretty new at the Linux side of things. The audio system, in particular, gives me fits. I did try compiling the arts package myself, and it didn't fix my problem, which is why I kept looking and stumbled onto this.
Keep in mind you may have needed _both_ the rebuilt arts packages _and_ the modification(s) to the configuration file(s).
For me, the rebuilt packages fixed the symptom, but my config files already held the two configuration details you originally posted.
I tried those, but I reverted to the original startkde (from kdebase-3.4.0), and to the recompiled arts packages. That works for me (tm). Cheers, Leen
On Friday 18 March 2005 02:50 pm, Randall R Schulz wrote:
Keep in mind you may have needed _both_ the rebuilt arts packages _and_ the modification(s) to the configuration file(s).
For me, the rebuilt packages fixed the symptom, but my config files already held the two configuration details you originally posted.
Randall Schulz
Of course! That makes me feel slightly less stupid. So, the upshot of all this for me is that with LD_BIND_NOW=true being on the same line as kdeinit +kcminit, I don't have system sounds. With them on separate lines, I have system sound. So it may not be a fix, but it's a workaround. I'll try rebuilding the RPM, as suggested by Leen. If that doesn't fix it, I'll go back underground and keep my eyes peeled. Thanks for the feedback everyone! -- __________ CorvusE Linux User #370082
Hooray! I now have working System Notifications without an error in my kdestart file. Thanks for the steps to my success, Leen. -- __________ CorvusE Linux User #370082
participants (4)
-
CorvusE -
Joe Morris (NTM) -
Leendert Meyer -
Randall R Schulz