Summary: | Plasma crash: #5 0x00007f6907a0fab5 in QMetaObject::activate(QObject*, int, void**) (sender=sender@entry=0x7f6907a960c0 <QHashData::shared_null>, signal_index=6, argv=argv@entry=0x0) at kernel/qobject.cpp:3759 | ||
---|---|---|---|
Product: | [Plasma] plasmashell | Reporter: | Germano Massullo <germano.massullo> |
Component: | general | Assignee: | David Edmundson <kde> |
Status: | RESOLVED DUPLICATE | ||
Severity: | crash | CC: | bhush94, plasma-bugs |
Priority: | NOR | ||
Version: | 5.5.4 | ||
Target Milestone: | 1.0 | ||
Platform: | Fedora RPMs | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Germano Massullo
2016-02-20 17:04:12 UTC
thanks Given you attached gdb does this mean you can reproduce it reliably? I'd love a valgrind trace if possible. *** This bug has been marked as a duplicate of bug 346118 *** (In reply to David Edmundson from comment #1) > thanks > > Given you attached gdb does this mean you can reproduce it reliably? I'd > love a valgrind trace if possible. > > *** This bug has been marked as a duplicate of bug 346118 *** Yes, today I had multiple crashes that occurred everytime I went back from kscreenlock login. I try to follow KDE debugging guide for a Valgrind log From konsole Kquitapp5 plasmashell valgrind plasmashell Note it will be super super slow. (In reply to David Edmundson from comment #3) > From konsole > > Kquitapp5 plasmashell > valgrind plasmashell > > Note it will be super super slow. Unfortunately I have not been able to reproduce the bug. |