Hi Tim, > > Sound in X was normally all done through the XBell(3) protocol > > request from the client to the server. Simple X clients like > > xterm(1) still use that, so she should find that typing > > > > printf \\a > > > > in an xterm that's running on your machine but displaying on hers > > beeps for her and not you. That would be a good first test to make > > sure that side of things is working as expected. > > The Xlauch, program is always running on her PC, she runs putty to > establish the link between her PC and my PC, once the putty window > appears she then logs in with her own username and password which is > an account on my linux machine, once logged in she types the command > "kmymoney" (which is the application she is running) at the prompt > which then opens up in its own window with the putty window running in > the background. > > She exits the program in the normal manner then logout of my PC > > I am not sure she is running an xterm, unless that what the putty > window is?? I assume that she would type the printf \\a after logging > into my PC??
What I mean is, if she was to do the same as normal but instead of running `kmymoney' she runs `xterm' then a new terminal window, an xterm, will appear on her PC. If, in that instead of the putty one, it was typed `printf \\a' then I'd hope to hear her PC beep and not yours. That would prove sound in the old X way was working fine, i.e. audible on her machine, which would mean that the problem with kmymoney's sound is down to KDE, and the new sound servers that are about. In other words, you've still have the problem, just the scope of it would have been narrowed a little. Cheers, Ralph. -- Next meeting: Bournemouth, Wednesday 2009-08-05 20:00 Dorset LUG: http://dorset.lug.org.uk/ Chat: http://www.mibbit.com/?server=irc.blitzed.org&channel=%23dorset List info: https://mailman.lug.org.uk/mailman/listinfo/dorset
