If you run 'bitbake some-recipe -g -u depexp' and there are any errors, the GTK window will pop up and then just sit there - forever. For example, if 'some-recipe' does not exist. I found this by making a simple typo when trying to run depexp on a busy system. I thought it was just slow until I killed it and ran 'bitbake -g some-recipe' without depexp and saw my typo. A little better feedback would be useful (expected).
I've got a small patch for the NoProvider case, can send in my next set.
The NoProvider patch was merged in bitbake eee9231a543f1d0b9ef3cd8377fc46fd23afb97b.
(In reply to comment #2) > The NoProvider patch was merged in bitbake > eee9231a543f1d0b9ef3cd8377fc46fd23afb97b. Oops sent to wrong list then, thanks RP for sorting that out. I'm marking this resolved as I don't think there are other error events that should be handled.