Gramps.exe Crash: CTRL-C in Console

5.2, W11.

Ran gramps.exe instead of grampsw.exe, user blue, as no issue of course with Grampsw.exe. :man_facepalming:
Hit CTRL-C in the Gramps console to copy the following selected text:

gtk_tree_view_scroll_to_point: assertion ‘gtk_widget_get_realized (GTK_WIDGET (tree_view))’ failed

Turned out this assertion is known, however the CTRL-C in the console caused the following:
:

50837653: ERROR: grampsgui.py: line 664:
Gramps failed to start. Please report a bug about this.
This could be because of an error in a (third party) View on startup.
To use another view, don’t load a Family Tree, change view, and then load your Family Tree.
You can also change manually the startup view in the gramps.ini file
by changing the last-view parameter.
Traceback (most recent call last):
File “C:\Users\User\AppData\Local\Programs\GrampsAIO64-5.2.0\gramps\gui\grampsgui.py”, line 635, in startgramps
if app.run():
^^^^^^^^^
File “AIO/gi/overrides/Gio.py”, line 40, in run
File “AIO/contextlib.py”, line 144, in exit
File “AIO/gi/_ossighelper.py”, line 237, in register_sigint_fallback
KeyboardInterrupt

Restarted Gramps.exe, and repro’d CTRL-C again, this time with no text in the console- same crash.
Looks like the combination in the console disrupts the Python Process in Windows, probably other CTRL combinations in Windows mentioned here will also do the job.

This is not a crash but normal behavoir. Ctrl-C is a standard way to stop a program running in console mode. I used it more than 40 years ago in unix.

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.