On Fri, May 18, 2012 at 11:28 AM, Fabian Moser <915...@bugs.launchpad.net> wrote: > btw.: to reproduce the reported problem "live", one has to move the last > child of any sub-tree and that child must be displayed (and selected in > the treeview) before being moved. Then the treepath (the tuple of ints) > becomes invalid and crashes the treeview update when it tries to get an > iter for the invalid tuple. When another child is used, the treepath > remains valid (it just refers to the wrong page, which isn't noticed). > When the moved page isn't displayed, the critical treeview line isn't > touched in the problematic update.
OK, the fact that it needs to be the last page in a sub-tree is probably the reason why I was not able to reproduce before. May need a deeper fix by tracing where the wrong index comes from. Either the "select_page" should not happen for a non-existing page, or at least it should not find a treepath for this page... Your patch at least will stop the exceptions and resulting bug reports :) -- Jaap -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/915037 Title: zim crashed with ValueError in select_page(): invalid tree path To manage notifications about this bug go to: https://bugs.launchpad.net/zim/+bug/915037/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
