Comment 7 for bug 849732

didrocks and pitti pointed me at this bug, which probably causes problems i've seen in gtimelog 0.6.1. It's not just Alt that gets eaten, but also ctrl-q, ctrl-e, ctrl-r, and ctrl-d (essentially all alt- and ctrl- accelerators defined for the app). I was confused because running it from lp:gtimelog worked fine, but a package built from the same source did not work. pitti then reminded me of debian/patches/force-gi which, as should be obvious, forces gi. Without that package-only patch, pygtk is used and everything works.