Bug 502060 - Kmail crashes when adding PDF attachment
Summary: Kmail crashes when adding PDF attachment
Status: REPORTED
Alias: None
Product: kmail2
Classification: Applications
Component: composer (show other bugs)
Version: 6.3.3
Platform: Other Linux
: NOR crash
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2025-03-27 09:50 UTC by piedro
Modified: 2025-04-01 16:33 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description piedro 2025-03-27 09:50:29 UTC
***
If you're not sure this is actually a bug, instead post about it at https://discuss.kde.org

If you're reporting a crash, attach a backtrace with debug symbols; see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports

Please remove this comment after reading and before submitting - thanks!
***

SUMMARY


STEPS TO REPRODUCE
1. Open mail to answer
2. Press "attach file" 
3. choose file and confirm

OBSERVED RESULT
immediate crash

EXPECTED RESULT
not crashing

SOFTWARE/OS VERSIONS
Operating System: openSUSE Tumbleweed 20250321
KDE Plasma Version: 6.3.3
KDE Frameworks Version: 6.12.0
Qt Version: 6.8.2
Kernel Version: 6.13.7-1-default (64-bit)
Graphics Platform: Wayland
Processors: 12 × AMD Ryzen 5 7600 6-Core Processor
Memory: 31.1 GiB of RAM
Graphics Processor: AMD Radeon RX 6700 XT

ADDITIONAL INFORMATION
After deleting the autosaves in ~/.local/share/kmail/autosave I can attach the file and send the mail. 
Eventually with another mail kmail crashes again - rinse, repeat.
Comment 1 Stefan Galinski 2025-04-01 16:33:06 UTC
I can confirm that, but this happens for each file attachment and even attachment downloads in my case. Sending one mail with an attachment works fine, sending another one -> crash. Restarting kmail works and I can send the crashed/restored mail with an attachment, but it crashes simply again by the next one. Pretty annoying and the behavior started to be an issue 1-2 weeks ago (KDE Neon user who is installing updates almost daily).