Bug 501002

Summary: Kontact crashes when screen is locked
Product: [Applications] kontact Reporter: Philippe ROUBACH <philippe.roubach>
Component: generalAssignee: kdepim bugs <pim-bugs-null>
Status: REPORTED ---    
Severity: normal CC: kde, nate
Priority: NOR    
Version First Reported In: 6.3.2   
Target Milestone: ---   
Platform: openSUSE   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:
Attachments: valgrind log

Description Philippe ROUBACH 2025-03-03 13:14:59 UTC
SUMMARY


STEPS TO REPRODUCE
1. wait for the lock screen
2. unlock the screen
3. 

OBSERVED RESULT

Kontact is no more there. It is closed. You must relaunch it.

EXPECTED RESULT

Konyact is always there and nor closed.

Operating System: openSUSE Tumbleweed 20250301
KDE Plasma Version: 6.3.2
KDE Frameworks Version: 6.11.0
Qt Version: 6.8.2
Kernel Version: 6.13.4-1-default (64-bit)
Graphics Platform: Wayland
Processors: 8 × 12th Gen Intel® Core™ i3-12100
Memory: 15.3 Gio of RAM
Graphics Processor 1: Mesa Intel® UHD Graphics 730
Graphics Processor 2: llvmpipe
Manufacturer: ASRock
Product Name: B760M-HDV/M.2 D4

ADDITIONAL INFORMATION
Comment 1 Nate Graham 2025-03-05 16:36:38 UTC
Did it crash? Does `coredumpctl --reverse` show a crash log for it?

This needs a lot more information if we're going to debug it, so please prepare yourself for answering a lot of questions. :)
Comment 2 Philippe ROUBACH 2025-03-05 16:56:32 UTC
(In reply to Nate Graham from comment #1)
> Did it crash? Does `coredumpctl --reverse` show a crash log for it?
> 
> This needs a lot more information if we're going to debug it, so please
> prepare yourself for answering a lot of questions. :)

Not really, it is simply closed. A not clean close for akregator when kontact closes
Comment 3 Nate Graham 2025-03-05 16:57:35 UTC
So you are telling me there are no crash logs for it?
Comment 4 Philippe ROUBACH 2025-03-05 16:58:59 UTC
where is the crash log ?
Comment 5 Nate Graham 2025-03-05 17:03:39 UTC
I told you already: in `coredumpctl --reverse` That's a terminal command; you need to run it in a terminal window. Run it and see if there are any crashes from Kontact in the top few entries, or around the time it happened.
Comment 6 Philippe ROUBACH 2025-03-05 17:17:01 UTC
Tue 2025-03-04 16:11:28 CET  42793 1000 1000 SIGTRAP present  /usr/bin/kontact  
Tue 2025-03-04 15:37:40 CET  30861 1000 1000 SIGTRAP present  /usr/bin/kontact                        27M
Tue 2025-03-04 14:14:02 CET   3185 1000 1000 SIGTRAP present  /usr/bin/kontact  
Mon 2025-03-03 20:45:18 CET   3214 1000 1000 SIGTRAP present  /usr/bin/kontact                      19.9M
Mon 2025-03-03 13:14:07 CET  44828 1000 1000 SIGTRAP present  /usr/bin/kontact                      25.4M
Mon 2025-03-03 12:09:18 CET  41284 1000 1000 SIGTRAP present  /usr/bin/kontact                      17.6M
Mon 2025-03-03 12:00:48 CET  23440 1000 1000 SIGTRAP present  /usr/bin/kontact                      30.8M
Mon 2025-03-03 10:07:05 CET   3275 1000 1000 SIGTRAP present  /usr/bin/kontact                      52.8M
Sun 2025-03-02 17:31:19 CET  74190 1000 1000 SIGTRAP present  /usr/bin/kontact                      30.1M
Sun 2025-03-02 13:53:43 CET  40339 1000 1000 SIGTRAP present  /usr/bin/kontact     
Mon 2025-03-03 12:00:48 CET  23440 1000 1000 SIGTRAP present  /usr/bin/kontact                      30.8M
Mon 2025-03-03 10:07:05 CET   3275 1000 1000 SIGTRAP present  /usr/bin/kontact                      52.8M
Sun 2025-03-02 17:31:19 CET  74190 1000 1000 SIGTRAP present  /usr/bin/kontact                      30.1M
Sun 2025-03-02 13:53:43 CET  40339 1000 1000 SIGTRAP present  /usr/bin/kontact                        39M
Sun 2025-03-02 10:55:41 CET   3232 1000 1000 SIGTRAP present  /usr/bin/kontact                      26.8M
Sat 2025-03-01 20:26:12 CET  55769 1000 1000 SIGTRAP present  /usr/bin/kontact                      20.9M
Sat 2025-03-01 18:45:44 CET   3149 1000 1000 SIGTRAP present  /usr/bin/kontact                      24.4M
Fri 2025-02-28 11:19:28 CET   3210 1000 1000 SIGTRAP present  /usr/bin/kontact                      59.5M
Comment 7 Nate Graham 2025-03-05 17:18:56 UTC
So yeah, it looks like it's crashing a bunch.

Please follow the instructions in https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports#Retrieving_a_backtrace_using_coredumpctl to extract a text backtrace of one of the crashes so the Kontact maintainers can investigate. Moving over there.
Comment 8 Philippe ROUBACH 2025-03-05 18:04:32 UTC
Created attachment 179149 [details]
valgrind log

i run "valgrind --log-file=kontact kontact"

this does not launch kontact.

see the valgrind log.
Comment 9 Philippe ROUBACH 2025-03-06 11:09:07 UTC
valgrind does not work with Wayland you nned the command :

QT_QPA_PLATFORM=xcb valgrind --log-file=kontact --leak-check=yes kontact
Comment 10 Philippe ROUBACH 2025-03-07 08:39:29 UTC
I met the case.

Here is the link to download program ctash data kontact.core.16931

https://transfert.free.fr/x1PB92E
Comment 11 Philippe ROUBACH 2025-03-07 08:43:42 UTC
You have one month to download the file
Comment 12 Bug Janitor Service 2025-03-22 03:46:38 UTC
🐛🧹 ⚠️ This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information, then set the bug status to REPORTED. If there is no change for at least 30 days, it will be automatically closed as RESOLVED WORKSFORME.

For more information about our bug triaging procedures, please read https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging.

Thank you for helping us make KDE software even better for everyone!
Comment 13 Philippe ROUBACH 2025-03-22 06:22:03 UTC
I supplied the info
Comment 14 Philippe ROUBACH 2025-04-23 13:31:00 UTC
Problem still there
Operating System: openSUSE Tumbleweed 20250420
KDE Plasma Version: 6.3.4
KDE Frameworks Version: 6.13.0
Qt Version: 6.9.0
Kernel Version: 6.14.2-1-default (64-bit)
Graphics Platform: Wayland
Processors: 8 × 12th Gen Intel® Core™ i3-12100
Memory: 15.3 Gio of RAM
Graphics Processor 1: Intel® UHD Graphics 730
Graphics Processor 2: llvmpipe
Manufacturer: ASRock
Product Name: B760M-HDV/M.2 D4
Comment 15 Philippe ROUBACH 2025-06-26 09:21:57 UTC
When I restart kontact, I have to restore akregator.

Maybe kontact crashes because of akregator.