Open schmjop opened 3 weeks ago
Thanks for the report. I have not had that issue at all, but I don't use it with CopyQ. Don't think I will be able to help without a stack trace. You can find that in ~/.local/share/ulauncher/last.log for Ulauncher v5 or ~/.local/state/ulauncher/last.log for Ulauncher v6 (assuming you don't restart after the crash).
It does not seem to be very helpful. If it helps, I could add the -v
flag to my unlauncher.desktop
temporarily to get more verbose logs for when the extension crashes next time.
No need. The crash message is not there because you haven't had a crash in that session yet.
The extension has crashed a few times since. As far as I can tell, the crashed state only occurs directly after logging in. However, the log after reboot does not contain any more information than the one I've already sent last time.
dde8e6c
from 2023-11-27 (see screenshot)ulauncher -v
ulauncher -v
The extension crashes around 1-2 times a week for me. I have not found a way to reproduce it while running with verbose output. Please let me know of log files that could be of interest.