[kate] [Bug 463856] AppImage fails to run: undefined symbol

2023-01-14 Thread Christoph Cullmann
https://bugs.kde.org/show_bug.cgi?id=463856

Christoph Cullmann  changed:

   What|Removed |Added

 CC||cullm...@kde.org
 Resolution|--- |DUPLICATE
 Status|REPORTED|RESOLVED

--- Comment #7 from Christoph Cullmann  ---


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

-- 
You are receiving this mail because:
You are watching all bug changes.

[kate] [Bug 463856] AppImage fails to run: undefined symbol

2023-01-09 Thread Charles Huber
https://bugs.kde.org/show_bug.cgi?id=463856

--- Comment #6 from Charles Huber  ---
Possibly related issues:
https://bugs.kde.org/show_bug.cgi?id=459682
https://bugs.kde.org/show_bug.cgi?id=461509

-- 
You are receiving this mail because:
You are watching all bug changes.

[kate] [Bug 463856] AppImage fails to run: undefined symbol

2023-01-09 Thread Charles Huber
https://bugs.kde.org/show_bug.cgi?id=463856

--- Comment #5 from Charles Huber  ---
Created attachment 155168
  --> https://bugs.kde.org/attachment.cgi?id=155168=edit
LD_DEBUG=bindings run of kate-master-741-linux-gcc-x86_64.AppImage showing
usage of system libKF5KIOFileWidgets.so

Using LD_DEBUG=bindings it looks like the AppImage is loading symbols from the
distro-provided version of libKF5KIOFileWidgets.so instead of (I assume) the
newer version in the AppImage.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kate] [Bug 463856] AppImage fails to run: undefined symbol

2023-01-05 Thread Charles Huber
https://bugs.kde.org/show_bug.cgi?id=463856

--- Comment #4 from Charles Huber  ---
Hmm, KDirOperator::action() is listed as "Since 5.100":

https://api.kde.org/frameworks/kio/html/classKDirOperator.html#ac33c8bcd26b115ee5cebbef81edbed19

...but CMakeLists.txt only specifies 5.90.0:

https://invent.kde.org/utilities/kate/-/blob/v22.12.1/CMakeLists.txt#L13

-- 
You are receiving this mail because:
You are watching all bug changes.

[kate] [Bug 463856] AppImage fails to run: undefined symbol

2023-01-05 Thread Charles Huber
https://bugs.kde.org/show_bug.cgi?id=463856

--- Comment #3 from Charles Huber  ---
Dropping the kdesrc-build version back to the last release tag (v22.12.1)
doesn't help:

genpfault@gpf:~/Workspace/kde/src$ kate --version
kate 22.12.1
genpfault@gpf:~/Workspace/kde/src$ kate
kf.service.services: The desktop entry file
"/usr/share/applications/qemu.desktop" has Type= "Application" but no Exec line
kf.service.sycoca: Invalid Service :  "/usr/share/applications/qemu.desktop"
Hspell: can't open /usr/share/hspell/hebrew.wgz.sizes.
kf.sonnet.clients.hspell: HSpellDict::HSpellDict: Init failed
kate: symbol lookup error:
/home/genpfault/Workspace/kde/usr/lib/x86_64-linux-gnu/plugins/ktexteditor/katefilebrowserplugin.so:
undefined symbol: _ZNK12KDirOperator6actionENS_6ActionE

Demangled: KDirOperator::action(KDirOperator::Action) const

-- 
You are receiving this mail because:
You are watching all bug changes.

[kate] [Bug 463856] AppImage fails to run: undefined symbol

2023-01-05 Thread Charles Huber
https://bugs.kde.org/show_bug.cgi?id=463856

--- Comment #2 from Charles Huber  ---
Using the system kate (20.12.2) to disable the File System Browser plugin
allows both the nightly AppImage and the kdesrc-build binary to successfully
start.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kate] [Bug 463856] AppImage fails to run: undefined symbol

2023-01-05 Thread Charles Huber
https://bugs.kde.org/show_bug.cgi?id=463856

--- Comment #1 from Charles Huber  ---
I get the same missing symbol error as the nightly AppImage when trying run
kate after building with kdesrc-build:

genpfault@gpf:~/Workspace/kde/src$ kate --version
kate 23.03.70
genpfault@gpf:~/Workspace/kde/src$ kate
kate: symbol lookup error:
/home/genpfault/Workspace/kde/usr/lib/x86_64-linux-gnu/plugins/ktexteditor/katefilebrowserplugin.so:
undefined symbol: _ZN12KDirOperator11setViewModeEN5KFile8FileViewE

Demangled: KDirOperator::setViewMode(KFile::FileView)

-- 
You are receiving this mail because:
You are watching all bug changes.