I had the same problem as Lionel reports. I have tried dasher on xubuntu hardy 32 bits with compiz, and in a virtualbox machine without any compiz or 3D stuff (this time xfwm4 was used) and neither worked at the beginning. The program would behave erratically and crash. I tried several control forms and the problem persisted. However, eventually it started to work ok. I think the option that made it all work was to explicitely select the mouse as input device.
The following is the kind of error it would leave on the terminal after a crash: $ dasher ** Message: Glade file is: /usr/share/dasher/dasher.traditional.glade Adding lock Training Dasher Releasing Lock ** Message: 1 ** Message: 2 ** (dasher:9125): WARNING **: AT_SPI_REGISTRY was not started at session startup. ** (dasher:9125): WARNING **: Could not locate registry ** Message: Could not initialise SPI - accessibility options disabled Adding lock Training Dasher Rendering lock Releasing Lock Fallo de segmentación This last sentence is spanish for "Segmentation fault". -- Dasher just doesn't work at all https://bugs.launchpad.net/bugs/244828 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
