Summary: | Crash while loading a feed | ||
---|---|---|---|
Product: | [Applications] konqueror | Reporter: | Benoit Leffray <benoit.leffray.kde> |
Component: | khtml | Assignee: | Konqueror Developers <konq-bugs> |
Status: | RESOLVED WORKSFORME | ||
Severity: | crash | CC: | asturm |
Priority: | NOR | ||
Version: | 4.9.3 | ||
Target Milestone: | --- | ||
Platform: | Ubuntu | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: | |||
Attachments: | akregator kcrash log on trying to open a feed |
Description
Benoit Leffray
2012-12-04 00:57:36 UTC
This also happens to me in 4.10 RC3 (while RC2 was fine). I tried with a completely new user and fresh homedir, started akregator standalone - and it crashed as soon as clicking onto a feed. Created attachment 76871 [details]
akregator kcrash log on trying to open a feed
Other than that, I get akregator also randomly crashing when:
- right after the window appearing without clicking anything
- the restore session dialog appears after one of the above crashes - instant crash without click even there
So right now, for me, akregator is a total wreck.
My apologies. Trouble was caused by using -fgraphite-identity on kdelibs... Dear Bug Submitter, This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond. Thank you for helping us make KDE software even better for everyone! Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! |