In Jaunty, at least, the login sound is a separate item in the 'startup programs' or whatever page of the 'Sessions' dialogue.
If that item, rather than _directly_ running a sound just ran a small bash/python/whatever script that checked if XF86Mute was pressed and then only played the sound if it WAS.
Is there any reason wrapping the startup sound like this is a bad idea?
I have a proposed solution.
In Jaunty, at least, the login sound is a separate item in the 'startup programs' or whatever page of the 'Sessions' dialogue.
If that item, rather than _directly_ running a sound just ran a small bash/python/ whatever script that checked if XF86Mute was pressed and then only played the sound if it WAS.
Is there any reason wrapping the startup sound like this is a bad idea?