Comment 1 for bug 990004

Well, I think the main change w.r.t. the MainWindow from 0.2 to 0.2.2beta2 is that it is created on the heap instead of the stack but I don't how that could make a difference. (And did not yet change in 0.2.2alpha1.)

But I also have to admit that I do not posses a detailed knowledge of all these configurations options. (Some of them seem contradictory, i.e. "-no-sm" in Core but "-sm" in GUI? But as I said, I just don't really know.)

I also have to admit that I pretty much have no idea what could cause this and the most helpful information would probably be provided by a debugging session to find out how far exactly the initialization of the MainWindow class comes. (Because it does not exit, I assume it enters the main event loop at least.)

(One very far fetched idea would be to remove the folder "~/.config/qpdfview" as the program tries to restore its window state on startup. Maybe something got messed up there?)