Version-Release number of selected component:
pkg_fingerprint: 4089 D8F2 FDB1 9C98
pkg_vendor: Fedora Project
runlevel: N 5
Thread no. 1 (10 frames)
#0 Read_Directory at src/easytag.c:932
#1 Browser_Tree_Node_Selected at src/browser.c:926
#2 _g_closure_invoke_va at gclosure.c:867
#5 _gtk_tree_selection_internal_select_node at gtktreeselection.c:1593
#6 gtk_tree_selection_select_path at gtktreeselection.c:895
#7 et_browser_select_dir at src/browser.c:1172
#8 et_application_window_select_dir at src/application_window.c:1958
#9 et_application_open at src/application.c:451
#10 ffi_call_unix64 at ../src/x86/unix64.S:76
#11 ffi_call at ../src/x86/ffi64.c:525
Created attachment 1236839 [details]
Created attachment 1236840 [details]
Created attachment 1236841 [details]
Created attachment 1236842 [details]
Created attachment 1236843 [details]
Created attachment 1236844 [details]
Created attachment 1236845 [details]
Created attachment 1236846 [details]
Created attachment 1236847 [details]
Created attachment 1236848 [details]
Created attachment 1236849 [details]
Created attachment 1236850 [details]
Created attachment 1236851 [details]
Please provide exact steps to reproduce the problem, and a description of what happens at each step.
It happensI have a slower computer with some music files.
This error occurs sometimes when I close easyTag during the startup procedure while it is parsing the existing files.
Thanks for the information. I fixed one aspect of the crash, involving the status bar:
However, a complete fix will take a while, as it involves blocking the quit action from being invoked during long-running actions, which is currently not done.
Thank you very much.
Is blocking the quit action the right approach from a user perspective?
When I accidentally open this application I would have to wait quite a bit, till closing it would be possible.
Different handling would be needed for all of the long-running actions, such as network access for CDDB queries, reading files on startup and saving tags to files as requested by the user. Until that is done (and it would be an invasive change, probably best done as part of moving those long-running actions to be handled asynchronously), the best approach is to block the quit action.
This message is a reminder that Fedora 25 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 25. 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'
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 25 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 25 changed to end-of-life (EOL) status on 2017-12-12. Fedora 25 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
Thank you for reporting this bug and we are sorry it could not be fixed.