Bug 343086 - Akregator annoying behaviour
Summary: Akregator annoying behaviour
Status: RESOLVED WORKSFORME
Alias: None
Product: akregator
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Debian testing Linux
: NOR crash
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords: triaged
Depends on:
Blocks:
 
Reported: 2015-01-20 15:47 UTC by Hans-J. Ullrich
Modified: 2018-10-27 02:16 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Hans-J. Ullrich 2015-01-20 15:47:38 UTC
Dear maintainers,

I am using akregator for many xears, and I am mainly happy with it. However, there is one thing, that is rather annoying. Maybe it can be changed. 

The problem:
I am running akregator in the taskbar of KDE and it is automatically started when KDE is started.
But whenever I shut down the computer and leave KDE, akregator is telling me, it has crashed, and I must confirm the crash window. Otherwise the computer will not proceed with the shutdown procedure. This is annoying and inhibits also time controlled shutdown procedure.

When I start KDE, then akregator is annoying again with a popup-window, telling me, that it has crashed the last time (of course, because of the behaviour above), and wants again an action by me. 

Could you add a funtion, that let akregator safely stop, when the computer is going to shutdown no matter if it was called by power-off-button, by a shell command, by leaving with one of the KDE-options whatever? This would be very nice!

Rest of akregator is working like a charme!

Best regards

Hans-J. Ullrich

 



Reproducible: Always
Comment 1 Hans-J. Ullrich 2015-01-20 15:49:29 UTC
I did this as a "wishlist", but maybe it could also be a bug, "normal" or "crash"! Please feel free, to
change the status.

Best

Hans
Comment 2 Christoph Feck 2015-01-23 20:57:54 UTC
I guess it is bug 336417, which is fixed in version 4.14.3.

If you are using that version, or a newer version, we need the backtrace to investigate the bug. For more information, please see https://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports
Comment 3 Andrew Crouthamel 2018-09-25 03:49:52 UTC
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 set the bug status 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!
Comment 4 Andrew Crouthamel 2018-10-27 02:16:41 UTC
Dear Bug Submitter,

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!