tag 906987 + moreinfo thanks Hi,
On Wed, Aug 22, 2018 at 10:53:41PM +0200, Rainer Dorsch wrote: > I do not know what these instances are doing or who started them, since > libreoffice itself is not even running You yourself once? lo_kde5filepicker is the current workaround for getting a KDE5 native filepicker in LO. It does interprorcess communication.. > rd@b370:~$ ps uaxwww|grep libreoffice > rd 1793 92.3 0.5 676972 83884 ? Rl 18:46 226:30 > /usr/lib/libreoffice/program/lo_kde5filepicker -session > 1062333730000153384636900000015520089_1534956113_564848 > rd 1834 92.3 0.5 676944 84012 ? Rl 18:46 226:30 > /usr/lib/libreoffice/program/lo_kde5filepicker -session > 1062333730000153384640800000015520090_1534956113_565286 > rd 14964 0.0 0.0 2368 808 pts/2 S+ 22:48 0:00 sh -c > /usr/bin/sensible-editor > '/tmp/reportbug-libreoffice-kde5-20180822-14898-bpdkewiq' > rd 14965 0.0 0.0 2368 808 pts/2 S+ 22:48 0:00 /bin/sh > /usr/bin/sensible-editor > /tmp/reportbug-libreoffice-kde5-20180822-14898-bpdkewiq > rd 14974 0.0 0.0 10416 6360 pts/2 S+ 22:48 0:00 nano > /tmp/reportbug-libreoffice-kde5-20180822-14898-bpdkewiq > rd 15048 0.0 0.0 5084 936 pts/3 S+ 22:51 0:00 grep > libreoffice > rd@b370:~$ .. so if there is no LO anymore it probably tries to communicate with a LO which isn't there anymore? But it was once and you opened/saved files? > I saw a similar report for gentoo: > > https://forums.gentoo.org/viewtopic-t-1083586.html?sid=76f37e6cfa80566337f52334669e0d04 Which doesn't say anything. > As a workaround I try to deinstall libreoffice-kde5 again.... :-/ Or just kill those processes if no LO is running? (btw, looking for LO is better done with soffice.bin, not libreoffice) Regards, Rene
