Version-Release number of selected component: meld-3.19.0-3.fc29 Additional info: reporter: libreport-2.9.5 cmdline: /usr/bin/python3 /usr/bin/meld /home/kparal/.config/gtk-3.0/ home/.config/gtk-3.0/ crash_function: inorder_search_up exception_type: StopIteration executable: /usr/bin/meld interpreter: python3-3.7.0-4.fc29.x86_64 kernel: 4.18.0-0.rc8.git2.1.fc29.x86_64 runlevel: N 5 type: Python3 uid: 1000 Truncated backtrace: treehelpers.py:122:get_previous_next_paths:RuntimeError: generator raised StopIteration Traceback (most recent call last): File "/usr/lib/python3.7/site-packages/meld/treehelpers.py", line 111, in inorder_search_up raise StopIteration() StopIteration The above exception was the direct cause of the following exception: Traceback (most recent call last): File "/usr/lib/python3.7/site-packages/meld/dirdiff.py", line 1090, in on_treeview_cursor_changed prev, next = self.model._find_next_prev_diff(cursor_path) File "/usr/lib/python3.7/site-packages/meld/tree.py", line 173, in _find_next_prev_diff return self.get_previous_next_paths(start_path, match_func) File "/usr/lib/python3.7/site-packages/meld/treehelpers.py", line 122, in get_previous_next_paths for it in self.inorder_search_up(start_iter): RuntimeError: generator raised StopIteration Local variables in innermost frame: self: <dirdiff.DirDiffTreeStore object at 0x7fa287e038b8 (meld+dirdiff+DirDiffTreeStore at 0x56208ce201c0)> path: <Gtk.TreePath object at 0x7fa287e07468 (GtkTreePath at 0x56208cfafca0)> match_func: <function DiffTreeStore._find_next_prev_diff.<locals>.match_func at 0x7fa287dea620> prev_path: None next_path: None start_iter: <Gtk.TreeIter object at 0x7fa287e070a8 (GtkTreeIter at 0x56208c609520)>
Created attachment 1476128 [details] File: backtrace
Created attachment 1476129 [details] File: cgroup
Created attachment 1476130 [details] File: cpuinfo
Created attachment 1476131 [details] File: environ
Created attachment 1476132 [details] File: mountinfo
Created attachment 1476133 [details] File: namespaces
Created attachment 1476134 [details] File: open_fds
*** Bug 1638399 has been marked as a duplicate of this bug. ***
I had same issue on fc29 with meld 3.19.0-3.fc29.noarch
*** Bug 1627785 has been marked as a duplicate of this bug. ***
This bug appears to have been reported against 'rawhide' during the Fedora 31 development cycle. Changing version to '31'.
This bug appears to have been reported against 'rawhide' during the Fedora 31 development cycle. Changing version to 31.
This message is a reminder that Fedora 31 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 31 on 2020-11-24. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '31'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 31 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 31 changed to end-of-life (EOL) status on 2020-11-24. Fedora 31 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.