Comment 3 for bug 98989

luke

Thanks for your efforts on debugging this problem. If you can reproduce this bug reliably it would be a big help if you can generate a backtrace with the appropriate debugging symbols installed as described here https://wiki.ubuntu.com/DebuggingProgramCrash

After adding the appropriate repositories if you search for 'adept' in adept manager you will see new packages with names like adept-foo-dbg. If you install those and then generate the backtrace it should replace all those 'no debugging symbols found' messages with useful information. I can't replicate your problem unfortunately or I'd do it myself.

thanks,
Rich