Bug 514636

Summary:	Empty Titel and Date for Feed from www.michaelcrump.net
Product:	[Applications] akregator	Reporter:	Tobias Sekan <tobias.sekan>
Component:	feed parser	Assignee:	kdepim bugs <pim-bugs-null>
Status:	RESOLVED WORKSFORME
Severity:	normal	CC:	aacid, kdedev, montel
Priority:	NOR
Version First Reported In:	6.6.1
Target Milestone:	---
Platform:	Arch Linux
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:
Attachments:	RSS Feed XML

Description Tobias Sekan 2026-01-15 08:05:55 UTC

Created attachment 188545 [details]
RSS Feed  XML

***
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
After fetch the RSS feed from https://www.michaelcrump.net/feed.xml, i got a list of entries, but the title and date are empty. Only the content and the author is present.

STEPS TO REPRODUCE
1. Add Feed from https://www.michaelcrump.net/feed.xml
2. Fetch Feed

OBSERVED RESULT
List of entries, but without title and date

EXPECTED RESULT
List of entries, with title and date

SOFTWARE/OS VERSIONS
Operating System: Arch Linux 
KDE Plasma Version: 6.5.5
KDE Frameworks Version: 6.22.0
Qt Version: 6.10.1
Kernel Version: 6.18.5-arch1-1 (64-bit)
Graphics Platform: Wayland
Processors: 16 × AMD Ryzen 7 5800X3D 8-Core Processor
Memory: 64 GB of RAM (62.7 GB usable)
Graphics Processor: AMD Radeon RX 7800 XT

ADDITIONAL INFORMATION

Comment 1 Tobias Sekan 2026-01-15 08:11:20 UTC

Flatpak Version from Discover

Comment 2 Laurent Montel 2026-01-15 09:32:50 UTC

Hi,
no problem here.
No idea what is your problem.
Regards

Comment 3 Tobias Sekan 2026-01-16 07:24:15 UTC

Hello, i have remove and re-added the feed now it is correct working, i have test multiple time with clear the archive, use without archive, remove and add it again, but the problem was not reproducible. So i think it was a rare edge case. Thanks for the attention. Ticket can close