https://bugs.kde.org/show_bug.cgi?id=421662
--- Comment #1 from Gabriel Marcano <gabemarc...@yahoo.com> --- I've been able to hack something on my end, by making QDBusInterface objects and using them to send a synchronous message to release the active Inhibit cookie. I'm still a little uneasy, as I'm afraid of a collision between a pending async job and the destructor (I don't know how all of these threads work together). Ideally, I think, it would be a good idea to make sure all pending async tasks are done, and then prevent them from starting once the destructor is going. There's also the added problem of what happens if Elisa is forcibly killed by a signal... this would leave the Inhibit in place, still. I would share what I have hacked together, but I'm under contract to not share any code I write while employed at my current employer without explicit permission from them (yay USA /s). -- You are receiving this mail because: You are watching all bug changes.
