https://bugs.kde.org/show_bug.cgi?id=503551
Thomas Baumgart <tbaumg...@kde.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|REPORTED |NEEDSINFO
Resolution|--- |WAITINGFORINFO
--- Comment #1 from Thomas Baumgart <tbaumg...@kde.org> ---
I am unable to reproduce this. Things I tried using master branch build:
1. run kmymoney with gdb and option -n, open a file and exit gdb without
closing the file
2. verify .lck file is still present
3. restart kmymoney -> no message, file is opened
1. run kmymoney with gdb no option to open last used and exit gdb without
closing the file
2. verify .lck file is still present
3. restart kmymoney -> no message, file is opened
1. run kmymoney opening last used file
2. copy the lock file
3. quit kmymoney and make sure original lock file is gone
4. move copy of lock file back to original name
5. restart kmymoney -> no message, file is opened
1. run kmymoney with gdb no option to open last used and interrupt to get to
gdb's cli. Don't quit
2. start kmymoney in second console -> message file is opened is shown (which
is correct here)
3. quit gdb (which leaves the lock file on disk)
4. use running second instance of kmymoney to open file -> no message, file is
opened
1. run kmymoney opening last used file
2. copy the lock file
3. quit kmymoney and make sure original lock file is gone
4. move copy of lock file back to original name
5. modify content of .lck file (first char on line 4)
6. restart restart kmymoney -> message file is opened is shown (which is
correct here)
7. revert modification of step 5
8. use running second instance of kmymoney to open file -> no message, file is
opened
SOFTWARE/OS VERSIONS (identical to yours)
Operating System: openSUSE Leap 15.6
KDE Plasma Version: 5.27.11
KDE Frameworks Version: 5.115.0
Qt Version: 5.15.12
Conclusion: is this something that is only happening on your system? And why?
--
You are receiving this mail because:
You are watching all bug changes.
