[01:34] <Kon-> Hi, I'm on 18.04. kde-config-fcitx is "installed" by default, but the "installed files" are missing
[01:38] <Kon-> I reinstalled it, let me see what happens. brb
[01:42] <Kon-> fcitx configuration UI gives a different error now. Before it couldn't find a missing /usr/share/kservices5/kcm_fcitx.desktop
[01:43] <Kon-> Now it is https://i.imgur.com/u8bHcRU.png
[06:36] <lordievader> Good morning
[07:54] <acheronuk> Kon-: both kde-config-fcitx libfcitx-qt5-1 installed?
[07:54] <acheronuk> works ok here on 18.04
[10:05] <BluesKaj> 'Morniog folks
[10:07] <lordievader> Hey BluesKaj
[10:07] <lordievader> How are you doing?
[10:09] <BluesKaj> 'Morning folks
[11:23] <daum> acheronuk, any chance you are round - heard you may be able to help with a weird issue i'm having where it seems when i login via kde my user gets it's groups stripped down to only the primary group
[12:01] <acheronuk> daum: I can't explain OR reproduce that issue
[12:02] <lordievader> I think it is somewhere with sddm or the init process of KDE. But I have no idea what is going on there.
[13:07] <Kon-> acheronuk: You were correct. libfcitx-qt5-1 is listed as installed by the package manager, but the files are not there. The same problem I had with kde-config-fcitx earlier.
[13:08] <Kon-> I'm confused as to why these packages are considered installed by default on 18.04 but are not actually present
[13:08] <Kon-> Can anyone else replicate this?
[13:09] <lordievader> Kon-: Does dpkg list it as 'rc'?
[13:12] <Kon-> lordievader: No, ii
[13:13] <lordievader> That means dpkg also thinks it is installed. Guess some script removed the files, or something.
[13:17] <Kon-> That's nice. I wonder what else from my system is mysteriously missing. So far fcitx is the only thing mysteriously broken
[13:17] <Kon-> I reinstalled libfcitx-qt5-1 and was actually able to get into the GUI for fcitx now. But it can't connect to Dbus
[13:17] <Kon-> Going to relog and see if it works
[13:19] <Kon-> Nope, still can't connect fcitx to Dbus
[13:19] <Kon-> If this is following the pattern, I'm assuming another package is missing
[13:21] <Kon-> "Cannot connect to fcitx by Dbus, is fcitx running?" is the exact error
[13:21] <Kon-> Anyone know what might be missing there?
[13:21] <lordievader> Is fcitx running? (`ps aux|grep fcitx`)
[13:22] <Kon-> Looks like the only results are kcm_fcitx and the grep highlight function. So no, it's not
[13:23] <Kon-> In which case I probably want to check the base fcitx package
[13:23] <lordievader> Kon-: What happens when you issue `fcitx` in a Konsole?
[13:25] <Kon-> lordievader: https://paste.ubuntu.com/p/zyWcHhhKxZ/
[13:26] <Kon-> Sure enough, it looks like fcitx-module-dbus is "Installed" but missing
[13:27] <lordievader> Is 'fcitx-frontend-qt5' installed? Or some other frontend?
[13:28] <Kon-> Package manager lists the following frontends installed: fbterm, gtk2, gtk3, qt4, qt5
[13:29] <Kon-> But knowing how things are going, I'd have to double check the files
[13:29] <Kon-> Indeed, /usr/lib/x86_64-linux-gnu/qt5/plugins/platforminputcontexts/libfcitxplatforminputcontextplugin.so is missing
[13:30] <Kon-> So is the qt4 frontend. Probably the others
[13:31] <lordievader> Reinstall the qt5 one and try running `fcitx` again.
[13:32] <Kon-> Same exact output
[13:32] <acheronuk> Kon-: no, I can't replicate that
[13:33] <Mylon> So my laptop isn't sleeping as it should.  The screen turns off, so I know inactivity time is being tracked properly.  But after 240 minutes, it doesn't sleep.
[13:34] <Kon-> reinstalling fcitx-module-dbus seems to have done the trick. I can access fcitx via GUI
[13:34] <Mylon> I tried using "energy saving" that was already on here, but that didn't work.  I tried downloading a daemon that's supposed to do the trick and editing it's conf.
[13:34] <Kon-> via terminal, however, it still tells me "no useable user interface," but I'm guessing that's a different package
[13:35] <Mylon> I don't remember the name of the daemon...
[13:37] <Kon-> Since I got this system, the only fcitx-related change I have made is to install fcitx-hangul and its dependencies. Is it at all possible that the installation process for that somehow mistakenly removed the KCM and qt5 frontends for fcitx?
[13:42] <acheronuk> Kon-: no. that package doesn't have any pre/post install scripts
[13:44] <Kon-> After I actually fcitx (what I wanted to do yesterday), I'll boot up the live media and see if it was on there. Very strange
[13:44] <Kon-> forgot to type all the words. set up fcitx*
[13:49] <Kon-> Not out of the woods yet, other things are still broken inside the GUI. So the terminal was correct
[14:06] <Kon-> x11 module was missing as well. That would do it
[14:07] <Kon-> So fcitx, fcitx-bin, and fcitx-data were properly installed, but every module, frontend, etc was missing
[14:08] <Kon-> Thanks for the help. I'm curious to take a look at the 18.04 manifest and the installation media and see if those modules were really supposed to be there or not
[16:43] <henk717> Hello Everyone, what is a good method of troubleshooting the technical cause of a kwin_x11 crash? Does it dump a log somewhere?
[16:46] <BluesKaj> henk717, check /var/log/syslog
[16:47] <henk717> Is that the same one KSystemLog opens? Because i could not find anything with the word kwin or kwin_x11 in there when it happened
[16:49] <henk717> Unfortunately its not something i can consistently reproduce, but while chatting i managed to trigger the crash at the 18:45 timestamp
[16:49] <BluesKaj> henk717, no i don't see KSystemLogib /var/log
[16:49] <henk717> KSystemLog is a log reading tool in Kubuntu
[16:49] <BluesKaj> in /var/log
[16:49] <henk717> I just checked the log and do not see anything in there
[16:50] <henk717> https://paste.ee/p/b9SzI
[16:51] <henk717> The crash happens when starting a steam game that disables compositing, Terraria in this case caused the crash but this log does not contain kwin_x11 related information
[20:41] <mirshafie> is it possible to use the Hyper key for shortcuts? it registers as Meta in kde?