Dolphin, the KDE file manager, does not start correctly on startup. The affected version is 23.04.2-1, running under KDE Plasma 5.108.0-1 with the latest version of the KDE libraries, 22.12.3-2. This bug causes the Dolphin window to appear briefly, then close unexpectedly. To reproduce this bug start the application from KDE Plasma. The application will appear for a moment in the bar and then disappear. When launched from the console, Dolphin produces the following message: [giovanni@localhost ~]$ dolphin KCrash: Application 'dolphin' crashing... QSocketNotifier: Invalid socket 5 and type 'Read', disabling... QSocketNotifier: Invalid socket 17 and type 'Read', disabling... QSocketNotifier: Invalid socket 18 and type 'Read', disabling... KCrash: Attempting to start /usr/libexec/drkonqi [1]+ Fermato dolphin [giovanni@localhost ~]$ The bug manager on KDE Plasma 5 instead reports the following: Application: Dolphin (dolphin), signal: Segmentation fault [KCrash Handler] #4 0x000056240d8a6f3b in DolphinViewContainer::setActive(bool) () #5 0x000056240d905b5c in DolphinTabPage::restoreState(QByteArray const&) [clone .isra.0] () #6 0x000056240d8921cd in DolphinMainWindow::readProperties(KConfigGroup const&) () #7 0x00007f2e1c2f4618 in KMainWindow::readPropertiesInternal(KConfig*, int) () from /lib64/libKF5XmlGui.so.5 #8 0x00007f2e1c2f467a in KMainWindow::restore(int, bool) () from /lib64/libKF5XmlGui.so.5 #9 0x000056240d8905b9 in main () [Inferior 1 (process 116647) detached]
Fedora Linux 38 entered end-of-life (EOL) status on 2024-05-21. Fedora Linux 38 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 Linux please feel free to reopen this bug against that version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see the version field. If you are unable to reopen this bug, please file a new report against an active release. Thank you for reporting this bug and we are sorry it could not be fixed.