https://bugs.kde.org/show_bug.cgi?id=475674
--- Comment #5 from Thomas Baumgart ---
I analyzed the problem and it turns out that QSysInfo::machineUniqueId
(https://doc.qt.io/qt-5/qsysinfo.html#machineUniqueId) is returning the same ID
on both systems (ac37039462fe4d0ab453b92a7b496f83). Diving int
https://bugs.kde.org/show_bug.cgi?id=475674
--- Comment #12 from Thomas Baumgart ---
There was no lock file prior to this change. It was handled using calls over
D-Bus between the KMyMoney processes. This sure does only work on systems that
have a D-Bus instance and only on the local host not ove
https://bugs.kde.org/show_bug.cgi?id=475674
--- Comment #9 from Brendan ---
KMM already handled the case when you try to open the same file on the same
computer and that still works after this change. The error message for both
attempting to open the file a second time on the same system and on a
https://bugs.kde.org/show_bug.cgi?id=475674
--- Comment #6 from Brendan ---
That was the problem. They are cloned systems.
Is it possible to display the hostname from the lck file in the error message?
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.kde.org/show_bug.cgi?id=475674
--- Comment #11 from Brendan ---
Where was the lck file stored? I never saw that before the recent change.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.kde.org/show_bug.cgi?id=475674
--- Comment #10 from Thomas Baumgart ---
> Not sure how KMM detects that the local file is already opened.
> It seems like different mechanisms with the same error message.
Not really. All handled by QLockFile. On the same machine it takes the process
https://bugs.kde.org/show_bug.cgi?id=475674
--- Comment #8 from Jonatan Cloutier ---
I haven't look in deep into the mr, but since the dbus check seems to be
removed, if the lock file contains the same machine ID, shouldn't it prevent
opening it, otherwise it would now allow opening or twice on t
https://bugs.kde.org/show_bug.cgi?id=475674
--- Comment #7 from Thomas Baumgart ---
That's a Qt feature I don't have control over.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.kde.org/show_bug.cgi?id=475674
--- Comment #4 from Brendan ---
I just tested this change and it does not appear to be working correctly. When
I run KMM, it does create a file named FileName.kmy.lck which then appears on
my other system after Syncthing syncs the folder.
When I try to
https://bugs.kde.org/show_bug.cgi?id=475674
Thomas Baumgart changed:
What|Removed |Added
Resolution|--- |FIXED
Version Fixed In|
https://bugs.kde.org/show_bug.cgi?id=475674
Bug Janitor Service changed:
What|Removed |Added
Ever confirmed|0 |1
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=475674
--- Comment #1 from Thomas Baumgart ---
*** Bug 499729 has been marked as a duplicate of this bug. ***
--
You are receiving this mail because:
You are the assignee for the bug.
12 matches
Mail list logo
