Comment #14 makes sense: the dasher package was compiled to use the accessibility bus. It communicates with other programmes using it, so that is the way it delivers characters to e.g. gedit. If the accessibility bus is switched off, it can't. dasher can be built after configuring with --disable-a11y to not use the accessibility bus, but to use libXtst instead.
Comment #17 is worrying - and of course, I can't reproduce it: I just had dasher running with the cursor all the way to the right and left it running for over 20minutes outputting into gedit. This was on a core duo laptop - just mentioning that given "TimerEvent" in your backtrace. In the source head we have since made simplifications in that area, so RecursiveOutput has actually already been removed, but AFAIK those changes weren't actually bug fixes, just refactorings. What hardware have you got? (Still assuming there is some sort of event race condition...) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/637747 Title: dasher crashed with SIGSEGV in Dasher::CDasherModel::HandleOutput() -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
