Bug 146014 - problem with session management when running contact and standalone akregator
Summary: problem with session management when running contact and standalone akregator
Status: RESOLVED WORKSFORME
Alias: None
Product: akregator
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords: triaged
Depends on:
Blocks:
 
Reported: 2007-05-27 08:23 UTC by m.wege
Modified: 2018-10-27 04:15 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 m.wege 2007-05-27 08:23:11 UTC
Version:           1.2.7 (using KDE 3.5.7, Kubuntu (feisty) 4:3.5.7-0ubuntu1~feisty2)
Compiler:          Target: i486-linux-gnu
OS:                Linux (i686) release 2.6.20-15-generic

Since I have activated session management in KDE I have the following problem: I run Akregator in the standalone version and have Kontact running. While shutting down I get an error message from Kontact/Akregator saying that the database is already accessed by someone else, asking what to do (do not use database or use it anyway). It seems like that Kontact is starting a second instance of Akregator during shut down in order to save its session. This does not work when I have Akregator stand alone running.
Comment 1 Adrián Chaves (Gallaecio) 2012-10-27 20:50:29 UTC
Does this bug report still applies to KDE 4.x?
Comment 2 Andrew Crouthamel 2018-09-23 02:22:42 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 3 Andrew Crouthamel 2018-10-27 04:15:49 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!