# Gramps.exe Crash: CTRL-C in Console

**URL:** <https://gramps.discourse.group/t/gramps-exe-crash-ctrl-c-in-console/5141>\
**Category:** Help\
**Created:** [March 18, 2024, 4:47am UTC](https://gramps.discourse.group/t/gramps-exe-crash-ctrl-c-in-console/5141 "2024-03-18T04:47:30Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![lmstearn](https://yyz2.discourse-cdn.com/free1/user_avatar/gramps.discourse.group/lmstearn/32/2879_2.png) [@lmstearn](https://gramps.discourse.group/u/lmstearn)\
**Post date:** [March 18, 2024, 4:47am UTC](https://gramps.discourse.group/t/gramps-exe-crash-ctrl-c-in-console/5141/1 "2024-03-18T04:47:30Z")

</div>

5.2, W11.

Ran gramps.exe instead of grampsw.exe, user blue, as no issue of course with Grampsw.exe. 🤦‍♂️  
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](https://gramps.discourse.group/t/bizarre-active-person-home-person-pointer-animation/2570/8), 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](https://stackoverflow.com/a/21460045/2128797) will also do the job.

---

<div class="post-metadata">

**Author:** ![ennoborg](https://yyz2.discourse-cdn.com/free1/user_avatar/gramps.discourse.group/ennoborg/32/4659_2.png) [@ennoborg](https://gramps.discourse.group/u/ennoborg)\
**Post date:** [March 18, 2024, 11:18am UTC](https://gramps.discourse.group/t/gramps-exe-crash-ctrl-c-in-console/5141/2 "2024-03-18T11:18:41Z")

</div>

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.

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/free1/uploads/gramps/original/1X/2ac1e712b7adf612e31ca08a55419f4cf37c0158.png) [@system](https://gramps.discourse.group/u/system)\
**Post date:** [April 17, 2024, 11:19am UTC](https://gramps.discourse.group/t/gramps-exe-crash-ctrl-c-in-console/5141/3 "2024-04-17T11:19:23Z")

</div>

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