Now, lo and behold, it looks like that bug is no longer present, at least as of the latest version of Karmic. I’m performing more tests to confirm that the bug has been wiped out, but it looks like the crashes with the WSIWYG system aren’t happening any more.

If the segfault bug is gone, that will mean less time trying to trace that annoying crash and more time working on the next iteration of BloGTK.

With luck, BloGTK 2.1 will have WSIWYG editing; support for image uploads to your blogging system, Flickr, or Picasa; and some under the hood fixes as well.

Thanks to everyone who has submitted bug reports lately — I always appreciate the feedback.

From what I’ve been able to tell, BloGTK will crash when more than two windows have been opened. Why, I’ve no idea. My guess is that there’s some garbage collection problems that are causing problems. Whether that’s due to something in BloGTK itself or the underlying Python libraries isn’t known yet. Given that BloGTK works just fine on Jaunty, my guess is that there’s a bug with one of the libraries.

A bug report has already been added to the Launchpad project. If anyone has a better idea of where the problem may be, please post the information either in the bug report or on this blog.

I apologize for the problem, and hopefully the bug will be fixed as Karmic heads towards formal release.

UPDATE: It appears that the crash is related to the WebKit bindings. Investigation into this bug is continuing.

UPDATE – Sept 24: Some more digging has revealed that the crash happens when one editor window is closed and then another is opened. There is a bug report filed with the pywebkitgtk package that seems to deal with a similar issue, if not the same one. I will continue to see if there’s anything I can do with the BloGTK codebase to prevent the crashes.

I apologize for the problems, and hopefully this issue will be resolved before Karmic is formally released next month.

UPDATE: Nov. 5: Still testing this crash on Karmic. I’m hoping to be able to either find a fix or a workaround shortly. Thank you for your patience.

Also, keep the bug reports coming—there are definitely outstanding issues that need to get fixed with the 2.0 codebase, and the more that get squashed, the better BloGTK 2.0 will be.