Bug#862717: [Pkg-ime-devel] Bug#862717: ibus-daemon often crashes on suspend/resume
Hi, >> What is mozc? > > It's another IM method used for ibus/uim/fcitx... for Japanese. I see. > Your comment in another mail that patching kde fixed some of the problem > is interesting. > > For missing panel, did you install libqt5gui5 > i A --\ libqt5gui55.7.1+dfsg-3+b > 5.7.1+dfsg-3+b > Description: Qt 5 GUI module > Qt is a cross-platform C++ application framework. Qt's primary feature is > its rich set of widgets that provide standard GUI functionality. > > The QtGui module extends QtCore with GUI functionality. > > Since it is a part of recommends, it is not installed by default. KDE depends on libqt5gui5, so yes, I do have that installed. Any chance you could point me to where in /etc/X11/Xsession.d/70im-config_launch or /usr/bin/im-launch starting the daemon and the panel are supposed to happen? When I start ibus-daemon in a running session, that starts the panel correctly. Maybe the auto-started daemon works differently, or maybe the problem is simply that the daemon launches so early that Plasma doesn't run yet, so there is no systray that the panel could register with, and then it just gives up. Kind regards, Ralf
Bug#862717: [Pkg-ime-devel] Bug#862717: ibus-daemon often crashes on suspend/resume
On Tue, May 16, 2017 at 08:43:02PM +0200, Ralf Jung wrote: > > The way this bug is happening, this looks like a bug on plasma-workspace > > or mozc. > What is mozc? It's another IM method used for ibus/uim/fcitx... for Japanese. Your comment in another mail that patching kde fixed some of the problem is interesting. For missing panel, did you install libqt5gui5 i A --\ libqt5gui55.7.1+dfsg-3+b 5.7.1+dfsg-3+b Description: Qt 5 GUI module Qt is a cross-platform C++ application framework. Qt's primary feature is its rich set of widgets that provide standard GUI functionality. The QtGui module extends QtCore with GUI functionality. Since it is a part of recommends, it is not installed by default. Osamu
Bug#862717: [Pkg-ime-devel] Bug#862717: ibus-daemon often crashes on suspend/resume
Hi, > I now realize: > >> default-display-manager: /usr/bin/sddm > > I use GDM3 without problem for ibus. Right, I am using KDE5 and SDDM. > I hear KDE user are suffering strange IM problem with uim too. > > http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=862558 > > KDE used to work without problem. So something changed on sddm side how > it run's its start up. Maybe how sddm is started by systemd. > > One user reported that by SSH into the problematic system via SSH, he > sees: > > 1861 tty2 Rl+0:09 ksplashqml Breeze --pid > 1871 tty2 Sl+0:00 \_ /usr/lib/mozc/mozc_server > 1877 tty2 Sl+0:00 \_ /usr/lib/x86_64-linux-gnu/uim/uim-candwin-qt5 > -v > > Strange thing is why ksplashqm calling IM? He killed > /usr/lib/mozc/mozc_server and got to log into system. > > The way this bug is happening, this looks like a bug on plasma-workspace > or mozc. What is mozc? To me it looks like ibus-daemon is terminating for no good reason. So far I can't even find anything about this in any log anywhere. :/ I tried passing -R to ibus-daemon to make it restart, but that did not help. Is there anything I can do that would help figuring out what is going on? ; Ralf
Bug#862717: [Pkg-ime-devel] Bug#862717: ibus-daemon often crashes on suspend/resume
Hmmm... I now realize: > default-display-manager: /usr/bin/sddm I use GDM3 without problem for ibus. I hear KDE user are suffering strange IM problem with uim too. http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=862558 KDE used to work without problem. So something changed on sddm side how it run's its start up. Maybe how sddm is started by systemd. One user reported that by SSH into the problematic system via SSH, he sees: 1861 tty2 Rl+0:09 ksplashqml Breeze --pid 1871 tty2 Sl+0:00 \_ /usr/lib/mozc/mozc_server 1877 tty2 Sl+0:00 \_ /usr/lib/x86_64-linux-gnu/uim/uim-candwin-qt5 -v Strange thing is why ksplashqm calling IM? He killed /usr/lib/mozc/mozc_server and got to log into system. The way this bug is happening, this looks like a bug on plasma-workspace or mozc. (This looks like mozc starting without regard to the other program. This may help some mozc user by letting them to skip configuration but certainly this is non-optimal way.) Regards, Osamu