Bug 408296

Summary:	KDEInit could not launch /usr/bin/kile
Product:	[Applications] kile	Reporter:	Alexander Kernozhitsky <sh200105>
Component:	general	Assignee:	Michel Ludwig <michel.ludwig>
Status:	CONFIRMED ---
Severity:	minor	CC:	jscott, malvin, r087r70
Priority:	NOR
Version First Reported In:	2.9.92
Target Milestone:	---
Platform:	Debian testing
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description Alexander Kernozhitsky 2019-06-04 14:37:18 UTC

SUMMARY

STEPS TO REPRODUCE
1. Open Kile
2. Open any TeX document from Dolphin (Kile must be associated with TeX files)

OBSERVED RESULT
You will see a dialog saying smth like "KDEInit could not launch /usr/bin/kile" (my locale is not English, so the translation of the message may be not precise). The document is opened.

EXPECTED RESULT
No such dialog appears. The document is opened.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 5.14.5
KDE Frameworks Version: 5.54.0
Qt Version: 5.11.3

Comment 1 Roberto 2019-09-04 13:46:05 UTC

Confirmed on debian/sid

Kile Version 2.9.92
KDE Frameworks 5.54.0
Qt 5.11.3

Comment 2 John Scott 2019-12-07 17:24:55 UTC

Also with 2.9.93 on Debian Buster

Comment 3 malvin 2020-03-27 18:41:11 UTC

This still happens on Debian Buster with kile 2.9.92.

It seems to be related to a DBUS setting the /usr/share/applications/org.kde.kile.desktop file.

Workaround:

1. cp /usr/share/applications/org.kde.kile.desktop ~/.local/share/applications/org.kde.kile.desktop

2. In the file ~/.local/share/applications/org.kde.kile.desktop change "X-DBUS-StartupType=Multi" to "X-DBUS-StartupType=none". Deleting this line should also work.

3. Log out and back in.

(Editing /usr/share/applications/org.kde.kile.desktop directly is also possible of course, but needs root and is probably not recommended.)

References:
https://bugs.launchpad.net/kde-baseapps/+bug/184337
https://bbs.archlinux.org/viewtopic.php?id=231274

Comment 4 Alexander Kernozhitsky 2020-05-01 16:47:19 UTC

On the recent Debian testing, it seems that I am not able to reproduce this bug.