Bug 30803 - kmail is not working after update dated 02/09/2022 (Cauldron 9 X86_64)
Summary: kmail is not working after update dated 02/09/2022 (Cauldron 9 X86_64)
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: All Linux
Priority: Normal critical
Target Milestone: ---
Assignee: KDE maintainers
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-09-02 10:35 CEST by Fabrice LINARES
Modified: 2022-09-03 13:25 CEST (History)
1 user (show)

See Also:
Source RPM: kmail-22.04.3-1.mga9
CVE:
Status comment:

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

Description Fabrice LINARES 2022-09-02 10:35:06 CEST 
Description of problem:


Version-Release Cauldron (MGA9)

How reproducible:


Steps to Reproduce:
Update from 02/09/2022 , kmail still in version 22.04.3 while other pim packages are now in 22.08.0 
2. As a result, kmail does not work anymore, (With or without kontact)
3.when launched from Konsole: 
Cannot initialize model with data QJsonObject(). missing: QJsonValue(string, "urls")
kmail: symbol lookup error: /lib64/libkmailprivate.so.5: undefined symbol: _ZN9PimCommon20LogActivitiesManager4selfEv
Comment 1 Marja Van Waes 2022-09-02 13:37:41 CEST 
(In reply to Fabrice LINARES from comment #0)

> 
> 
> Steps to Reproduce:
> Update from 02/09/2022 , kmail still in version 22.04.3 while other pim
> packages are now in 22.08.0 
> 2. As a result, kmail does not work anymore, (With or without kontact)
> 3.when launched from Konsole: 
> Cannot initialize model with data QJsonObject(). missing: QJsonValue(string,
> "urls")
> kmail: symbol lookup error: /lib64/libkmailprivate.so.5: undefined symbol:
> _ZN9PimCommon20LogActivitiesManager4selfEv

Assigning to the KDE maintainers

Assignee: bugsquad => kde
CC: (none) => marja11
Source RPM: (none) => kmail-22.04.3-1.mga9

Comment 2 Marja Van Waes 2022-09-02 20:44:45 CEST 
neoclust pushed kmail-22.08.0-1.mga9 almost three hours ago, so this should be fixed .

Please reopen if you still have problems with that version

Status: NEW => RESOLVED
Resolution: (none) => FIXED

Comment 3 Fabrice LINARES 2022-09-03 13:25:36 CEST 
yes it's working now , thanks
Note You need to log in before you can comment on or make changes to this bug.