Bug 22285 - kmail fails to start due to an undefined symbol from the ksieve
Summary: kmail fails to start due to an undefined symbol from the ksieve
Status: RESOLVED OLD
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: KDE maintainers
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-12-30 16:20 CET by Nikita Krupenko
Modified: 2021-05-17 01:15 CEST (History)
2 users (show)

See Also:
Source RPM: kmail-17.08.0-1.mga7.src.rpm
CVE:
Status comment:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Nikita Krupenko 2017-12-30 16:20:00 CET 
Description of problem:
Trying to start kmail, I see the following error:

kmail: symbol lookup error: /lib64/libkmailprivate.so.5: undefined symbol: _ZTIN8KSieveUi26SieveImapInstanceInterfaceE


Version-Release number of selected component (if applicable): 17.08.0-1.mga7


How reproducible: Always
Comment 1 Marja Van Waes 2017-12-30 19:49:58 CET 
kmail will be updated to version 17.12.0, too, so please try again, _after_ neoclust mentions on dev ml, in the " [RFC] New KDE Application update in progress" thread, that that update is completed.

CC: (none) => marja11
Assignee: bugsquad => kde

Comment 2 Nikita Krupenko 2018-01-10 12:05:40 CET 
Update finished. Now I have similar fail:

kmail: symbol lookup error: /lib64/libKF5KSieveUi.so.5: undefined symbol: _ZTIN12KPIMTextEdit21SyntaxHighlighterBaseE
Comment 3 Nicolas Lécureuil 2018-01-11 09:50:59 CET 
please provide rpm -qf /lib64/libKF5KSieveUi.so.5

CC: (none) => mageia

Comment 4 Nikita Krupenko 2018-01-11 11:48:38 CET 
I see this output:

lib64kf5ksieveui5-15.12.3-2.mga6
Comment 5 Nicolas Lécureuil 2018-01-12 11:22:59 CET 
please test new lib64kf5ksieveui5
Comment 6 Aurelien Oudelet 2021-05-17 01:15:31 CEST 
Users who have experienced this problem are encouraged to upgrade to the latest update of their distribution, and if this issue turns out to still be reproducible in the latest update, please reopen this bug with additional information.

Closing as OLD.

Resolution: (none) => OLD
Status: NEW => RESOLVED
Note You need to log in before you can comment on or make changes to this bug.