[dolphin] [Bug 451474] New: Dolphin crash after screen unlock

Justin Zobel bugzilla_noreply at kde.org
Sun Mar 13 23:48:28 GMT 2022


https://bugs.kde.org/show_bug.cgi?id=451474

            Bug ID: 451474
           Summary: Dolphin crash after screen unlock
           Product: dolphin
           Version: 21.12.2
          Platform: Fedora RPMs
                OS: Linux
            Status: REPORTED
          Keywords: drkonqi
          Severity: crash
          Priority: NOR
         Component: general
          Assignee: dolphin-bugs-null at kde.org
          Reporter: justin.zobel at gmail.com
                CC: kfm-devel at kde.org
  Target Milestone: ---

Application: dolphin (21.12.2)

Qt Version: 5.15.2
Frameworks Version: 5.91.0
Operating System: Linux 5.17.0-0.rc5.102.fc36.x86_64 x86_64
Windowing System: X11
Distribution: "Fedora release 36 (Thirty Six)"
DrKonqi: 5.24.2 [KCrashBackend]

-- Information about the crash:
- What I was doing when the application crashed:
Unlocked device, immediate crash of dolphin.

Operating System: Fedora Linux 36
KDE Plasma Version: 5.24.2
KDE Frameworks Version: 5.91.0
Qt Version: 5.15.2
Kernel Version: 5.17.0-0.rc5.102.fc36.x86_64 (64-bit)
Graphics Platform: X11
Processors: 12 × AMD Ryzen 5 3600 6-Core Processor
Memory: 31.3 GiB of RAM
Graphics Processor: NVIDIA GeForce GTX 1060 6GB/PCIe/SSE2

The reporter is unsure if this crash is reproducible.

-- Backtrace:
Application: Dolphin (dolphin), signal: Segmentation fault

[KCrash Handler]
#4  0x00007fb536e24193 in QObject::property(char const*) const () from
/lib64/libQt5Core.so.5
#5  0x00007fb5388dc334 in KUiServerV2JobTracker::registerJob(KJob*) () from
/lib64/libKF5JobWidgets.so.5
#6  0x00007fb5388d94f9 in
QtPrivate::QFunctorSlotObject<KUiServerV2JobTracker::registerJob(KJob*)::{lambda()#1},
0, QtPrivate::List<>, void>::impl(int, QtPrivate::QSlotObjectBase*, QObject*,
void**, bool*) () from /lib64/libKF5JobWidgets.so.5
#7  0x00007fb536e2dbb6 in void doActivate<false>(QObject*, int, void**) () from
/lib64/libQt5Core.so.5
#8  0x00007fb536e2dbb6 in void doActivate<false>(QObject*, int, void**) () from
/lib64/libQt5Core.so.5
#9  0x00007fb5371566bc in QDBusServiceWatcher::serviceOwnerChanged(QString
const&, QString const&, QString const&) () from /lib64/libQt5DBus.so.5
#10 0x00007fb537157002 in QDBusServiceWatcher::qt_static_metacall(QObject*,
QMetaObject::Call, int, void**) () from /lib64/libQt5DBus.so.5
#11 0x00007fb5371574bb in QDBusServiceWatcher::qt_metacall(QMetaObject::Call,
int, void**) () from /lib64/libQt5DBus.so.5
#12 0x00007fb537107f2b in QDBusConnectionPrivate::deliverCall(QObject*, int,
QDBusMessage const&, QVector<int> const&, int) () from /lib64/libQt5DBus.so.5
#13 0x00007fb536e24584 in QObject::event(QEvent*) () from
/lib64/libQt5Core.so.5
#14 0x00007fb5379930e2 in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() from /lib64/libQt5Widgets.so.5
#15 0x00007fb536dfa2ea in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() from /lib64/libQt5Core.so.5
#16 0x00007fb536dfd664 in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) () from /lib64/libQt5Core.so.5
#17 0x00007fb536e4b687 in postEventSourceDispatch(_GSource*, int (*)(void*),
void*) () from /lib64/libQt5Core.so.5
#18 0x00007fb534b4f1bf in g_main_context_dispatch () from
/lib64/libglib-2.0.so.0
#19 0x00007fb534ba44b8 in g_main_context_iterate.constprop () from
/lib64/libglib-2.0.so.0
#20 0x00007fb534b4cb40 in g_main_context_iteration () from
/lib64/libglib-2.0.so.0
#21 0x00007fb536e4b17a in
QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) ()
from /lib64/libQt5Core.so.5
#22 0x00007fb536df8d2a in
QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from
/lib64/libQt5Core.so.5
#23 0x00007fb536e00e1e in QCoreApplication::exec() () from
/lib64/libQt5Core.so.5
#24 0x0000562e8f09871d in main ()
[Inferior 1 (process 1169796) detached]

Possible duplicates by query: bug 387203, bug 378470, bug 375526, bug 372452,
bug 366235.

Reported using DrKonqi

-- 
You are receiving this mail because:
You are on the CC list for the bug.


More information about the kfm-devel mailing list