Created attachment 856075 [details] terminal snippet Description of problem: da-gui segfaults when $DISPLAY is unset (or probably inaccessible some other way). Version-Release number of selected component (if applicable): devassistant-0.8.0-1.fc21.noarch Steps to Reproduce: 1. unset $DISPLAY 2. da-gui Actual results: da-gui[1105]: segfault at 10 ip 00007ff793392145 sp 00007fffbc1dd210 error 4 in libpython2.7.so.1.0[7ff7932d0000+178000] Additional info: If gtk_init() is used, it terminates the process on failure. If gtk_init_check() is used, it's a caller responsibility to act accordingly.
Created attachment 856076 [details] gdb traceback
Created attachment 856091 [details] gdb traceback in GtkFileChooser Same problem elsewhere, looks like a pygobject bug in handling messages logged through g_log() Steps to repro: 1. run da-gui, start a new project 2. click the Browse button 3. in GtkFileChooser, navigate to /tmp and click the "Create folder" button 4. da-gui[1497]: segfault at 10 ip 00007f4ede6e7145 sp 00007fffe8ba3160 error 4 in libpython2.7.so.1.0[7f4ede625000+178000]
This bux is fixed by commit (https://github.com/bkabrda/devassistant/commit/e9e49d08f12088b8a87adfae2785126fce7a44ae) It is fixed in version devassistant-0.9.1