Public bug report changed: https://launchpad.net/malone/bugs/4048
Comment: Hi, I'm sorry the bugtrail looks like that - I realise I haven't been clear enough when I said it might not be scim's fault. I've discussed it with upstream, and qGo continues segfaulting even after I remove scim (which is not the case with scim related bugs). There is also a misconception about scim (I was also mistaken when my system became instable upgrading from hoary to breezy) : the "bugs" where not scim's fault, but libstdc++ ABI change between version 5 and 6 (AFAIK). BTW, qGo doesn't compile against any libstdc++. According to upstream, it looks like a bug in qGo's code : - the function MyMessageHandler (need a look at the call stack) - a variable (need to run the program step by step and put stop points to see which variable is badly initialised and make everything crash - according to upstream it might be due to the *msg chain) At the moment, qGo's code would need to be looked at by somebody who nows a bit of programming (I don't). However, upstream is just one man and he doesn't use Ubuntu nor Debian, and can't reproduce the bug. -- universe-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/universe-bugs
