Created attachment 1508357 [details]
Description of problem:
Version-Release number of selected component (if applicable):
Steps to Reproduce:
kdeinit5 does not provide a bug reporting address.
Executable: kdeinit5 PID: 30552 Signal: Segmentation fault (11) Time: 24.11.2018 14:26:19
steps to reproduce:
1. Start Dolphin.
2. Change folder.
3. Open any file.
to me it happens sporadically with annoying crash messages like "Executable: kdeinit5 PID: 28617 Signal: Segmentation fault (11) Time: 31.08.19 11:39:42"
also another message states that I cannot report this issue because kdeinit5 doesn't provide a bug reporting address
no dev information is attached to the crash report and debugger quits unexpectedly while trying to generate a trace.
This message is a reminder that Fedora 29 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 29 on 2019-11-26.
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 '29'.
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 29 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 29 changed to end-of-life (EOL) status on 2019-11-26. Fedora 29 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.