[Bug 4048] qgo segmentation fault

2006-03-14 Thread Ming Hua
Public bug report changed: https://launchpad.net/malone/bugs/4048 Task: ubuntu scim Status: Unconfirmed = Rejected Comment: From the reporter's comments, it seems scim is not related to this bug. Rejecting on the scim side. -- universe-bugs mailing list universe-bugs@lists.ubuntu.com

[Bug 4048] qgo segmentation fault

2006-02-24 Thread Reinhard Tartler
Public bug report changed: https://launchpad.net/malone/bugs/4048 Also affects: scim (Ubuntu) Severity: Normal Priority: (none set) Status: Unconfirmed -- universe-bugs mailing list universe-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/universe-bugs

[Bug 4048] qgo segmentation fault

2006-02-24 Thread Loïc
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

[Bug 4048] qgo segmentation fault

2006-02-23 Thread Loïc
Public bug report changed: https://launchpad.net/malone/bugs/4048 Comment: Thanks to upstream advices, I was able to compile a debug enabled version of last version of qGo. Same problem, the program crashes at startup. I sent upstream every information I could get (using Kdevelop) but it turned

[Bug 4048] qgo segmentation fault

2006-01-18 Thread Phil Bull
Public bug report changed: https://launchpad.net/malone/bugs/4048 Task: ubuntu qgo Severity: Critical = Normal Status: Unconfirmed = Needs Info -- universe-bugs mailing list universe-bugs@lists.ubuntu.com http://lists.ubuntu.com/mailman/listinfo/universe-bugs

[Bug 4048] qgo segmentation fault

2006-01-16 Thread Loïc
Public bug report changed: https://launchpad.net/malone/bugs/4048 Comment: An update to the situation : qGo 1.0.2 was really unstable (frequent crashes when observing games, to the extent that I didn't even dare to start a game). Then, without any (apparent) change in the system it stopped

[Bug 4048] qgo segmentation fault

2005-12-26 Thread Loïc
Public bug report changed: https://launchpad.net/malone/bugs/4048 Comment: Thanks for the information. However, with GTK_IM_MODULE=xim I can't input chinese in Open Office (and other apps like Thunderbird). So qgo will still segfault. Is there a way to start qgo wihle export GTK_IM_MODULE=scim

[Bug 4048] qgo segmentation fault

2005-12-26 Thread freeflying
Public bug report changed: https://launchpad.net/malone/bugs/4048 Comment: 在 星期二 27 十二月 2005 00:12,您写道: Public bug report changed: https://launchpad.net/malone/bugs/4048 Comment: Hi, On a clean breezy install, with scim installed from http://svn.ubuntu.org.cn/ubuntu-cn/d...n/binary-i386/

[Bug 4048] qgo segmentation fault

2005-12-25 Thread Loïc
Public bug report changed: https://launchpad.net/malone/bugs/4048 Description changed to: In Ubuntu 5.10 Breezy qgo version 1.0.0-r2.2 (and and qgo-1.03-R2) exit at launch reporting a segmentation fault. Even qgo -debug doesn't give anything else. I can confirm segfault is caused

[Bug 4048] qgo segmentation fault

2005-12-25 Thread Loïc
Public bug report changed: https://launchpad.net/malone/bugs/4048 Comment: I can confirm segfault is caused by scim. Not just a scim install (qgo stills works here with scim installed on a clean Ubuntu 5.10 Breezy install) but when configuring scim (that is, configuring chinese locale and

[Bug 4048] qgo segmentation fault

2005-12-25 Thread Loïc
Public bug report changed: https://launchpad.net/malone/bugs/4048 Comment: Just to correct a possible mistake. scim is not necessarily the one causing the problem, it could be related to the configuration necessary to get scim running on breezy (locales? or maybe these lines : export

[Bug 4048] qgo segmentation fault

2005-12-25 Thread Ming Hua
Public bug report changed: https://launchpad.net/malone/bugs/4048 Comment: As noted in malone bug #2246, GTK_IM_MODULE=scim can cause problems if scim is loaded in an app linked to libstdc++5. GTK_IM_MODULE=xim would be a workaround. Also [EMAIL PROTECTED] is WRONG and useless. The correct way