Bug#244715: "Use system bell" doesn't use system bell (and kills everything else)

[Phil Edwards <pme@devphil.com>]

Package: arts
Version: 1.2.2-1
Severity: grave

My first thought was 'critical', following its description of "makes
unrelated software on the system break," but surely this can't be that
hard to fix...


On this box, the hardware beep /must/ work.  And it works fine, outside
of KDE.  But once KDE starts up, artsd takes over the system beep, and
artsd doesn't work.  The "System Bell" module has its checkbox next to
"use the system bell instead of the little notification sounds", but the
Test botton on that dialog does nothing, and the system beep never happens.

Reading the logfiles, I can see artsd messages every time the hardware
beep is supposed to go off.  So clearly it's still being intercepted and
notification sounds are still trying to be played; that's the bug.

Toggling the checkboxes, enabling/disabling the sound system, deleting
cache files, rebooting, etc, etc, doesn't help.  It seems to be write-only.


I don't really care for the moment that no sounds or music can play.  That's
a different problem and one that I don't ever expect to solve.  But the
hardware beep needs to keep working, not get silently (ha) killed when a
user logs into the desktop.



-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing')
Architecture: i386 (i686)
Kernel: Linux 2.4.22-lac13
Locale: LANG=C, LC_CTYPE=C

Versions of packages arts depends on:
ii  libarts1                      1.2.2-1    aRts Sound system
ii  libartsc0                     1.2.2-1    aRts Sound system C support librar

-- no debconf information