Сегодня, после обновления плазмы, стал падать dolphin. Проверил на вновь созданном пользователе, тоже самое. ----- Application: Dolphin (dolphin), signal: Segmentation fault [KCrash Handler] #4 0x00007f25072865b4 in QAction::setWhatsThis(QString const&) () from /usr/lib64/libQt5Widgets.so.5 #5 0x000055cbf90624c8 in ?? () #6 0x00007f2505f0918c in ?? () from /lib64/libc.so.6 #7 0x00007f2505f09245 in __libc_start_main () from /lib64/libc.so.6 #8 0x000055cbf9062f91 in ?? () [Inferior 1 (process 7635) detached] --------- -------- xsession-errors ------- kf.service.services: KApplicationTrader: mimeType "x-scheme-handler/file" not found KCrash: Application 'dolphin' crashing... KCrash: Attempting to start /usr/libexec/kf5/drkonqi Could not find the Plasmoid for Plasma::FrameSvgItem(0x555cfec987f0) QQmlContext(0x555cfbc53530) QUrl("file:///usr/ share/kf5/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/global/Globals.qml") Could not find the Plasmoid for Plasma::FrameSvgItem(0x555cfec987f0) QQmlContext(0x555cfbc53530) QUrl("file:///usr/ share/kf5/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/global/Globals.qml") file:///usr/share/kf5/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/NotificationItem.qml:222:21: QML Se lectableLabel: Binding loop detected for property "implicitWidth" file:///usr/share/kf5/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/NotificationItem.qml:222:21: QML Se lectableLabel: Binding loop detected for property "implicitWidth" file:///usr/share/kf5/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/NotificationItem.qml:222:21: QML Se lectableLabel: Binding loop detected for property "implicitHeight" QFont::setPointSizeF: Point size <= 0 (0.000000), must be greater than 0 Unable to find file for pid 7925 expected at "kcrash-metadata/7925.ini" QSocketNotifier: Invalid socket 5 and type 'Read', disabling... QSocketNotifier: Invalid socket 18 and type 'Read', disabling... QSocketNotifier: Invalid socket 19 and type 'Read', disabling... ----------------
*** This bug has been marked as a duplicate of bug 44956 ***
