https://bugs.kde.org/show_bug.cgi?id=432526
Bug ID: 432526
Summary: Appimage hardcodes QT_PLUGIN_PATH in AppRun, can't add
plugins path using QT_PLUGIN_PATH
Product: digikam
Version: 7.2.0
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: Bundle-AppImage
Assignee: [email protected]
Reporter: [email protected]
Target Milestone: ---
SUMMARY
Appimage hardcodes QT_PLUGIN_PATH in AppRun, I can't add plugins like IMEs,
except unpack and repack the appimage
In file AppRun, QT_PLUGIN_PATH is coded this way:
69 export LD_LIBRARY_PATH=$DIR/usr/lib/:$LD_LIBRARY_PATH
70 export QT_PLUGIN_PATH=$DIR/usr/plugins/
71 export XDG_DATA_DIRS=$DIR/usr/share/:$XDG_DATA_DIRS
As a result, my IME, fcitx, doesn't work because it relys on a file located in
/usr/lib/x86_64-linux-gnu/qt5/plugins/platforminputcontexts/libfcitxplatforminputcontextplugin.so
The IME problem is easy to solve, since the bundled qt is newer than the system
one, I only need to unpack image, copy the file, and repack.
I can also solve the IME problem by changing line 70 in AppRun to
QT_PLUGIN_PATH=$DIR/usr/plugins:$QT_PLUGIN_PATH, and setting
QT_PLUGIN_PATH=/usr/lib/x86_64-linux-gnu/qt5/plugins before running digikam.
Yet both require unpacking and repacking.
But my question is, is there any specific reason that in AppRun, QT_PLUGIN_PATH
is dealt with differently from, e.g., XDG_DATA_DIRS and LD_LIBRARY_PATH ?
Can it be ,like, QT_PLUGIN_PATH=$DIR/usr/plugins:$QT_PLUGIN_PATH, so that users
can add plugins using QT_PLUGIN_PATH without unpacking and repacking ?
SOFTWARE/OS VERSIONS
OS: ubuntu 20.04
software: digikam appimage 7.2.0-rc
--
You are receiving this mail because:
You are watching all bug changes.
