git-cola doesn't start about git-cola HOT 3 CLOSED

models.gitrepo: Use a custom event type for GitRepoInfoEvents

We now give GitRepoInfoEvents a custom type() so that we can
tell them apart from builtin Qt events.

Closed by 2234cb2

Signed-off-by: David Aguilar [email protected]

from git-cola.

OK after some testing i figure it out that it doesn't "Segmentation fault" on all my repos and that it doesn't seg faults on fresh pulls. So after some exploring in which case it seg faults I found that untracked files are the problem. I can reproduce it on any repo that I got. Here is example of it in git-cola repo:

bor@bik git-cola 0 $ git status
# On branch master
nothing to commit (working directory clean)
bor@bik git-cola 1 $ bin/git-cola
bor@bik git-cola 0 $ echo "bla bla" > bla
bor@bik git-cola 0 $ git status
# On branch master
# Untracked files:
#   (use "git add ..." to include in what will be committed)
#
#       bla
nothing added to commit but untracked files present (use "git add" to track)
bor@bik git-cola 1 $ bin/git-cola
Segmentation fault
bor@bik git-cola 139 $ rm bla
bor@bik git-cola 0 $ bin/git-cola
bor@bik git-cola 0 $

That number is exit status. So the first time I run bin/git-cola it starts just fine and works. But after I add untracked file it doesn't work. After removing the file it works again.

from git-cola.

I just pushed a commit that fixes this and retains the classicdockwidget.
Let me know if it works for ya.

I was able to reproduce the segfault on F11 w/ PyQt4 4.5.4

from git-cola.