On Sat, 30 Jul 2022 13:10:12 +0900 Masaru Nomiya <nom...@galaxy.dti.ne.jp> said:
> Hello, > > This is a continuation from before, but I think it would be better to > start a new thread on this. FYI there have been problem reports of sddm and e - and changing to something other than sddm fixed it. > Yesterday, on my second black screen, the sddm spit out the following > log. > > [...] > xrdb: colon missing on line 1, ignoring line > xrdb: colon missing on line 2, ignoring line > xrdb: colon missing on line 3, ignoring line > xrdb: colon missing on line 4, ignoring line > libpng warning: iCCP: known incorrect sRGB profile > CPUFREQ: pstate [min=0 max=100 turbo=1] > libpng warning: iCCP: known incorrect sRGB profile > PAUSE ! > ========================= > ========================= > FCITX 4.2.9.7 -- Get Signal No.: 1 > Date: try "date -d @1659090285" if you are using GNU date *** > ProcessID: 2612 > fcitx(+0x18a6)[0x55e785bb78a6] > /lib64/libc.so.6(+0x3d990)[0x7f5014703990] > /lib64/libc.so.6(__write+0x51)[0x7f50147c8f3f] > fcitx(+0x1648)[0x55e785bb7648] > /lib64/libc.so.6(+0x3d990)[0x7f5014703990] > /lib64/libc.so.6(__select+0x14e)[0x7f50147cfc8c] > /lib64/libfcitx-core.so.0(+0x1585f)[0x7f501490885f] > /lib64/libfcitx-core.so.0(FcitxInstanceRun+0x57)[0x7f5014908fb7] > fcitx(+0x1352)[0x55e785bb7352] > /lib64/libc.so.6(+0x275f0)[0x7f50146ed5f0] > /lib64/libc.so.6(__libc_start_main+0x8b)[0x7f50146ed6b9] > fcitx(_start+0x25)[0x55e785bb7445] > X I/O Error - fatal. Exiting > > As you probably know, FCITX 4.2.9.7 and below is the crash log of > fcitx. > > I thought this is possible, so I downgraded the fcitx and removed > the unnecessary fcitx-pinyin. > > Since then, I have logged out & logged in, shut down & powered off, > powered on & booted several times, and have never had a black screen. the above looks like the xserver crashed or was killed. it also looks like enlightenment crashed - that PAUSE says e trapped a problem. it may be a result of the xserver crashing or it may have been one of a sequence of events leading to it crashing. i don't know. not enough information to say. > Then I checked the efl's build options and found that there is an > ecore-imf-loaders-disabler, but there is no option for fcitx. > I thought of adding fcitx to the build, but there is a reason not to > include fcitx? efl (ecore) has ni img module for fcitx. someone has to write one. other toolkits may support it - efl doesn't and unless smeone writes a module for it, it won't. > I don't remember when, but ibus became hard to use, and now I think > the majority of users use fcitx? yes - ibus used to work - then began to break and not work properly anymore. i've just stuck to scim. > Regards. > > --- > ┏━━┓彡 野宮 賢 mail-to: m.nomiya @ gmail.com > ┃＼／彡 > ┗━━┛ "Bill! > You married with Computer. > Not with Me!" > "No..., with money." > > > _______________________________________________ > enlightenment-users mailing list > enlightenment-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/enlightenment-users > -- ------------- Codito, ergo sum - "I code, therefore I am" -------------- Carsten Haitzler - ras...@rasterman.com _______________________________________________ enlightenment-users mailing list enlightenment-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-users
