Bug 340974 - Handle existing lockfile better
Summary: Handle existing lockfile better
Status: RESOLVED UPSTREAM
Alias: None
Product: kmymoney
Classification: Applications
Component: general (show other bugs)
Version: git (master)
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: KMyMoney Devel Mailing List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-11-15 01:49 UTC by Daniel Hahler
Modified: 2014-11-17 10:17 UTC (History)
0 users

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

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Daniel Hahler 2014-11-15 01:49:38 UTC 
KMyMoney failed to startup, but showed the empty outline of the "Did you know?" dialog only.

After stracing the process, I've found out that it was looking for / waiting on ~/.kde/share/config/kmymoneyrc.lock.

It would have been more helpful, if there was a message about this - preferably in the GUI, but even on the console output it would have helped.

Reproducible: Always
Comment 1 Thomas Baumgart 2014-11-17 10:17:09 UTC 
The file in question is maintained by the KSharedConfig object, which is part of the base KDE classes. KMyMoney does not access (create, write, read, delete) this file and all access to the config system is encapsulated by the above mentioned KDE base object. Thus this is more of an upstream problem..