Home | Docs | Forums | Lists | Bugs | Planet | Store | GMN | Get Gentoo!
Not eligible to see or edit group visibility for this bug.
View Bug Activity | Format For Printing | XML | Clone This Bug
I global use "xcb",after emerge libxcb,libX11,xcb-proto, in any apps ,I press <ctrl> + <space> to switch The Chinese input methord fcitx, The app crash. $ QT_IM_MODULE=xim kwrite ScimInputContextPlugin() QMultiInputContext::changeInputMethod(): index=0, slave=xim kwrite: xcb_xlib.c：50：xcb_xlib_unlock: 断言
I global use "xcb",after emerge libxcb,libX11,xcb-proto, in any apps ,I press <ctrl> + <space> to switch The Chinese input methord fcitx, The app crash. $ QT_IM_MODULE=xim kwrite ScimInputContextPlugin() QMultiInputContext::changeInputMethod(): index=0, slave=xim kwrite: xcb_xlib.c：50：xcb_xlib_unlock: 断言c->xlib.lock失败。 KCrash: Application 'kwrite' crashing... KCrash cannot reach kdeinit, launching directly. archers have the same problem,they use a "xcb_xlib-no-assert-on-lock.patch" to resolve it.
Uhm, can you please try to get the error with LC_MESSAGE=C ? Although this seems to be yet another of those cases for which we need newer versions of libraries.
Please make sure that if these packages are installed, you have at least these versions: libXcomposite-0.3.1 libXdamage-1.0.4 libXfixes-4.0.3 libXi-1.1.0 libXinerama-1.0.1 libXrandr-1.1.2 x11-libs/libX11-1.1
$ LC_MESSAGES=C QT_IM_MODULE=xim kwrite ScimInputContextPlugin() QMultiInputContext::changeInputMethod(): index=0, slave=xim kwrite: xcb_xlib.c:50: xcb_xlib_unlock: Assertion `c->xlib.lock' failed. KCrash: Application 'kwrite' crashing... KCrash cannot reach kdeinit, launching directly. now,this bug is still unfixed.
Please respond to comment #2 indicating that you are using at least those versions, and preferably with information specifying the versions you are using.
(In reply to comment #2) > Please make sure that if these packages are installed, you have at least these > versions: > > libXcomposite-0.3.1 > libXdamage-1.0.4 > libXfixes-4.0.3 > libXi-1.1.0 > libXinerama-1.0.1 > libXrandr-1.1.2 > x11-libs/libX11-1.1 > x11-libs/libX11-1.1.1 x11-libs/libxcb-1.0 x11-proto/xcb-proto-1.0
(In reply to comment #2) > Please make sure that if these packages are installed, you have at least these > versions: > > libXcomposite-0.3.1 > libXdamage-1.0.4 > libXfixes-4.0.3 > libXi-1.1.0 > libXinerama-1.0.1 > libXrandr-1.1.2 > x11-libs/libX11-1.1 > I use "~amd64",I have all you asked.
cf. http://www.fcitx.org/main/?q=node/113
I wonder if it's a locking bug in qt. I didn't see any calls of LockDisplay or UnlockDisplay anywhere in fcitx or scim.
You're welcome to try the libxcb ebuild from: http://bugs.gentoo.org/show_bug.cgi?id=176839#c1 Somewhat ugly, but best way I could see of solving the problem until clients are updated for the new xcb locking.
This turns out to be an upstream bug in libX11 that was just fixed. We'll try to get a revision bump in -- the commit is at http://gitweb.freedesktop.org/?p=xorg/lib/libX11.git;a=commit;h=c2f88cdf5cd9c94b77e5bfdac572b5ac06ab4aa8
its libX11 issue.
Not to waste a libX11 rev bump since I'm already fixing bug #181707, I'll just lump this one in there since after reviewing the patch it seems proper. Upstream feels this is the fix for this issue as well. Fixed in libX11-1.1.2-r1
(In reply to comment #13) > Not to waste a libX11 rev bump since I'm already fixing bug #181707, I'll just > lump this one in there since after reviewing the patch it seems proper. > Upstream feels this is the fix for this issue as well. > > Fixed in libX11-1.1.2-r1 > Thanks, Cardoe, I appreciate you taking care of this.
