https://bugs.kde.org/show_bug.cgi?id=391370
--- Comment #16 from Kevin Kofler <kevin.kof...@chello.at> --- So I think I see where the issue is. First, we construct the QtSingleApplication with the default appId, which calls sysInit() once. Then, setAppId is called, which calls sysInit(appId) and creates a new socket, without deleting the old one first. I would blame the modifications from QupZilla/Falkon adding that setAppId method. But the bundled version in QupZilla/Falkon has that too, so I don't see why you are not seeing this bug with that version. -- You are receiving this mail because: You are watching all bug changes.
