phase1geo
Annotator won't open anymore after closing it once [ubuntu 22.04]
Hi,
I just wanna thank you for such an amazing app, it's the perfect complement to the screenshot utility that comes from Gnome in Ubuntu 22.04.
Unfortunately, as mentioned in the title, the application won't open anymore after closing it once :(
Maybe it's a thing of the PPA, not sure.
Please let me know if you need anything on my side to debug/fix this
If you run the application from the terminal, do you see any error output?
I'm experiencing this same issue, too. If I reboot, it'll open again, but only once. In my case, it's been installed through elementaryOS app center. When I dig into the plank config file, I ultimately come to this command: /usr/bin/flatpak run --branch=stable --arch=x86_64 --command=com.github.phase1geo.annotator --file-forwarding com.github.phase1geo.annotator @@ %f @@
If I run the above command as is, it complains about '%f' not being found. If I substitute a valid file name, the command just completes quietly. If I grab a shell through flatpak, I can manually run 'com.github.phase1geo.annotator' but, again, it just quietly exits. Adding --help does throw the Usage dialog.
Thoughts on where to go with this?
I'm not sure how to debug flatpaks at the moment. I think there is supposed to be a way to to this, but the last time I tried it, I was not successful. I'll see what I can do. If there is any way that you can download and build Annotator from source (./app install & ./app debug in the top-most source directory), we might be able to get to the bottom of the issue. Running ./app debug will put you into a gdb debugger, so you will need to enter 'c' at the prompt to get the application to start launching. If there are any bad code issues, hopefully we will see them in the debugger output when the application dies.
It would open once after a reboot but never again (until the next reboot). I've since moved away from elementary OS so I'm not facing this issue anymore nor can of be of much help in troubleshooting it further.
For @tpandresfernandez, I'm wondering if this is some sort of case where the first time that you launch the application, the minder executable remains running (for some reason). If you attempt to run another invocation of Minder while a minder process is still running, nothing will happen -- the second invocation will simply return without doing much of anything.