Bug#511063: Possible cause of problem

2009-01-07 Thread Park Shinjo
Rene Engelhard wrote: Hi, Park Shinjo wrote: I have downgraded nabi from 0.99.3-1 to 0.99.2-2, same problem remains. 15:28 < hdu_hh> rene: what happens with SAL_USE_VCLPLUGIN=gen [...] 15:33 < hdu_hh> rene: my suggestion was an "educated guess" that nabi's GTK handlin

Bug#511063: Possible cause of problem

2009-01-07 Thread Rene Engelhard
Hi, Park Shinjo wrote: > I have downgraded nabi from 0.99.3-1 to 0.99.2-2, same problem remains. 15:28 < hdu_hh> rene: what happens with SAL_USE_VCLPLUGIN=gen [...] 15:33 < hdu_hh> rene: my suggestion was an "educated guess" that nabi's GTK handling conflicts with OOo's GTK-plugi

Bug#511063: Possible cause of problem

2009-01-07 Thread Park Shinjo
Rene Engelhard wrote: Park Shinjo wrote: Ah, strace'ing ooffice was my mistake. I am using Korean XIM nabi. My environment variable includes this. declare -x XMODIFIERS="@im=nabi" When I undefine this one, OpenOffice.org runs. My OO.o worked in version 1:3.0.0-4, some changes related to XIM

Bug#511063: Possible cause of problem

2009-01-07 Thread Rene Engelhard
Park Shinjo wrote: > Ah, strace'ing ooffice was my mistake. I am using Korean XIM nabi. My > environment variable includes this. > > declare -x XMODIFIERS="@im=nabi" > > When I undefine this one, OpenOffice.org runs. My OO.o worked in version > 1:3.0.0-4, some changes related to XIM in later vers

Bug#511063: Possible cause of problem

2009-01-07 Thread Park Shinjo
Ah, strace'ing ooffice was my mistake. I am using Korean XIM nabi. My environment variable includes this. declare -x XMODIFIERS="@im=nabi" When I undefine this one, OpenOffice.org runs. My OO.o worked in version 1:3.0.0-4, some changes related to XIM in later version might made the situation.