Among other things, softbeep intercepts the write() system call in order to look for BEL characters that are being written to a TTY. It strips them out and instead calls a program.
It has to intercept *every* write call, and then decide which ones are applicable. Apparently, it is not always accurate about what is a TTY and what isn't. ** Changed in: gconf2 (Ubuntu) Sourcepackagename: gconf2 => softbeep -- update-schemas: Error writing file "/var/lib/gconf/defaults/%gconf-tree.xml.new": File exists https://launchpad.net/bugs/74699 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
