Bug 448308

Summary:	Crash if katefilebrowserplugin is enabled
Product:	[Applications] kate	Reporter:	Pozsgay Máté <matthew.linux>
Component:	application	Assignee:	KWrite Developers <kwrite-bugs-null>
Status:	RESOLVED DUPLICATE
Severity:	crash	CC:	mhamant, pho13ton, waqar.17a
Priority:	NOR
Version:	21.12.1
Target Milestone:	---
Platform:	Appimage
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Pozsgay Máté 2022-01-12 11:11:54 UTC

SUMMARY
As soon as the FileBrowser plugin enabled Kate crashes in the AppImage distribution:
/tmp/.mount_kate-2mnvpnF/AppRun.wrapped: symbol lookup error: /tmp/.mount_kate-2mnvpnF/usr/plugins/ktexteditor/katefilebrowserplugin.so: undefined symbol: _ZN13KBookmarkMenuC1EP16KBookmarkManagerP14KBookmarkOwnerP5QMenu


STEPS TO REPRODUCE
1. Download AppImage version, add execution permission, and start.
2. If the plugin is already enabled in your settings Kate crashes as soon as the session is loaded
3. If not enabled, then turn it on at Settings -> Configure Kate -> Plugins -> Filesystem Browser plugin. As soon as you enable it crashes

OBSERVED RESULT
Crash

EXPECTED RESULT
Do not crash :)

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Ubuntu 30.04.3 LTS
OS / AppImage
KDE Plasma Version: 5.18.5
KDE Frameworks Version: 5.68.0 / 5.89.0
Qt Version: 5.12.8 / 5.15.2

ADDITIONAL INFORMATION
Maybe this is just a symptom of a more generic packaging problem, because the SQL extension also crashes:
Cannot mix incompatible Qt library (5.12.8) with this library (5.15.2)

Comment 1 Pozsgay Máté 2022-01-13 21:08:11 UTC

*** Bug 447511 has been marked as a duplicate of this bug. ***

Comment 2 Pozsgay Máté 2022-01-13 21:12:48 UTC

You can work around the startup crash by disabling the affected plugins by editing the session file ~/.local/share/kate/anonymous.katesession
Set the following lines to false:
katefilebrowserplugin=false
katesqlplugin=false

Repeat these steps for all of your sessions: ~/.local/share/kate/sessions/, and do not enable file browser and SQL plugins.

Comment 3 Pozsgay Máté 2022-07-11 12:35:13 UTC

Updated to Ubuntu 22.04, the problem no longer reproducable.

Comment 4 Waqar Ahmed 2022-08-12 12:33:35 UTC

Marking as fixed. This is a packaging issue though

Comment 5 Martinus 2023-03-07 13:29:56 UTC


*** This bug has been marked as a duplicate of bug 459682 ***