Summary: | there is no sound/bell | ||
---|---|---|---|
Product: | [Applications] konsole | Reporter: | James <bjlockie> |
Component: | general | Assignee: | Konsole Developer <konsole-devel> |
Status: | RESOLVED WORKSFORME | ||
Severity: | normal | ||
Priority: | NOR | ||
Version: | 1.2 | ||
Target Milestone: | --- | ||
Platform: | Gentoo Packages | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: |
Description
James
2003-02-13 18:55:05 UTC
The normal "bell" event. Check your "Regional & Accessbility/Accessbility" settings for "Bell" and/or "Sound & Multimedia/System Bell" like volume. Under "KDE System Notifications": "Something Special Happened in the Program" is the only event with a sound next to it. It seems as if that is the default. "A print error has occured" has a spelling mistake, my spell checker says it should be spelled "occurred" I'm having the same problem with konsole. As soon as artsd is running it kills all beeps, even in xterm. I compiled KDE 3.1 on LFS with gcc 3.2.1, XFree 4.2.1 I have this same issue, Debian unstable/stable, KDE 3.1 stable/unstable (tried both, today). As history point, I've migrated 2.2->3.0->3.1. The accessibility and bell pages are in default settings, sounds in general through arts work, and even the 'play' button for various notifications works. What does not work, though, is 'Test' button in 'Use system bell instead of system notification'; no sound at all. Reporting it because it might be related. (Noatun et al work fine as well through arts) I compiled kde 3.1 on Red Hat 8.0 using the compiler that came with the distribution (that would be gcc version 3.2). I also compiled it on SuSE 8.0, using the default compiler as well (gcc 2.95.3). By default (without changing any configurations in control panel or konsole), the konsole just beeps using the internal speaker, that is, no sound is played via artsd. I can't get konsole to play a sound via System Notifications either, even by setting the same sound for all System Notifications in control panel. Can someone confirm this bug for KDE 3.2? Doesn't happen anymore. |