Bug 24577 - Kontact Settings (SIGSEGV)
Summary: Kontact Settings (SIGSEGV)
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: aarch64 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: KDE maintainers
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-03-28 16:49 CET by Deri James
Modified: 2019-04-05 15:48 CEST (History)
2 users (show)

See Also:
Source RPM: kontact-18.12.3-1.mga7.src.rpm
CVE:
Status comment:


Attachments

Description Deri James 2019-03-28 16:49:50 CET
Description of problem:

kontact -> settings -> configure kontact 

causes core dump.

Version-Release number of selected component (if applicable):

18.12.3-1

How reproducible:

Always (using new user)

Steps to Reproduce:
1. Start kontact from terminal
2. Click Settings
3. Click Configure Kontact

See it core dump
Comment 1 David GEIGER 2019-03-28 19:59:04 CET
Yeah I can reproduce here, so I'm awaiting for a new kf5 and plasma release to rebuild all against new Qt 5.12.2, I'm pretty sure we have some others similar issues since new Qt 5.12.2 as no kde packages were rebuilt against it.

CC: (none) => geiger.david68210

Marja Van Waes 2019-03-30 09:17:53 CET

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

Comment 2 Deri James 2019-04-03 22:20:27 CEST
I assume kf5 has now been compiled against QT 5.12.2 but I am still seeing this problem. Kontact is now:-

Source RPM  : kontact-18.12.3-2.mga7.src.rpm

Kinfocentre shows:-

Operating System: Mageia 7
KDE Plasma Version: 5.15.3
KDE Frameworks Version: 5.56.0
Qt Version: 5.12.2
Kernel Version: 5.0.5-desktop-2.mga7
OS Type: 64-bit
Processors: 2 × Intel® Core™ i5-2500 CPU @ 3.30GHz
Memory: 3.9 GiB of RAM
Comment 3 David GEIGER 2019-04-04 00:12:08 CEST
Ok can reproduce here!

Should be fixed in next kcmutils-5.56.0-3.mga7 update!

For upstream reference:

https://bugs.kde.org/show_bug.cgi?id=405440
Comment 4 David GEIGER 2019-04-05 04:14:48 CEST
Fixed!

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

Comment 5 Deri James 2019-04-05 15:48:07 CEST
Confirmed now working, thank you.

Note You need to log in before you can comment on or make changes to this bug.