If all blogs are removed, blogtk2 will not start properly
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
BloGTK |
In Progress
|
High
|
JayReding |
Bug Description
I downloaded BlogTK2 a few minutes ago, and tried to get it set up. I came across numerous hang-ups, in which the program would seem to go into an endless loop, such as when accessing with the wrong blog ID - then, once that was fixed, downloading pre-existing blog entries - and once I had forced quit and re-opened, creating a new blog entry.
Finally, I thought the blog account might have become corrupted, and deleted it (using the "-" on-screen button in the Settings dialog). This caused another crash. Then, ever since, when I've tried to re-open blogtk2, I get this response:
Traceback (most recent call last):
File "/usr/bin/blogtk2", line 7, in <module>
main()
File "/usr/bin/
blogtk.main()
File "/usr/bin/
self.
File "/usr/bin/
self.
File "/usr/bin/
accountID = self.model.
TypeError: iter must be a GtkTreeIter
and an on-screen report that the program quit unexpectedly.
I'm running Lucid with the latest publicly released updates, if that helps. (Incidentally, I'm surprised that it was as unstable as it has proved to be. Maybe my machine is running something that conflicts with it.)
Further to my complaints about hangs when refreshing posts, creating new entries, etc.:
The one with refreshing posts, at least, appears to be related to threading. If I comment out the "@threaded" and "gtk.gdk. threads. enter() /leave( )" from refreshPosts, the hang no longer occurs when doing that. But I'm not sure whether that's safe to do. I suspect the same problem, in other methods, may be responsible for the other hangs. Any ideas why threading might go crazy on my machine?
By the way, I was able to get some functionality back by throwing away my ~/.BloGTK directory. But it would still be ideal if deleting all blogs doesn't cause BloGTK to stop working, even though a workaround has now been demonstrated.