Repository navigation
[3.3.0] Ctrl+C shows backtrace, handling of KeyboardInterrupt could be improved #814
Description
Hi!
I just pressed Ctrl+C on SafeEyes and saw this:
# safeeyes
^CTraceback (most recent call last):
File "/usr/lib/python-exec/python3.11/safeeyes", line 8, in <module>
sys.exit(main())
^^^^^^
File "/usr/lib/python3.11/site-packages/safeeyes/__main__.py", line 38, in main
safe_eyes.run(sys.argv)
File "/usr/lib/python3.11/site-packages/gi/overrides/Gio.py", line 40, in run
with register_sigint_fallback(self.quit):
File "/usr/lib/python3.11/contextlib.py", line 144, in __exit__
next(self.gen)
File "/usr/lib/python3.11/site-packages/gi/_ossighelper.py", line 239, in register_sigint_fallback
signal.default_int_handler(signal.SIGINT, None)
KeyboardInterruptIt's not a major issue, but I consider it a bug still. I can make a pull request as needed.
Best, Sebastian
Activity
archisman-panigrahi commentedon Dec 21, 2025
If you know how to fix this, please send a PR. Thanks!
hartwork commentedon Dec 21, 2025
@archisman-panigrahi if you press it early enough, there is no cure I believe. Pull request #816 improves things a bit.
Merge pull request slgobinath#816 from hartwork/issue-814-bin-safeeye…