Bug 488316 - Plasmashell Crash During grsync
Summary: Plasmashell Crash During grsync
Status: RESOLVED DUPLICATE of bug 482887
Alias: None
Product: plasmashell
Classification: Plasma
Component: generic-crash (show other bugs)
Version: 6.0.5
Platform: Fedora RPMs Linux
: NOR crash
Target Milestone: 1.0
Assignee: Plasma Bugs List
URL:
Keywords: drkonqi
Depends on:
Blocks:
 
Reported: 2024-06-10 17:59 UTC by Wayne E. Nail
Modified: 2024-06-10 20:47 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments
New crash information added by DrKonqi (133.48 KB, text/plain)
2024-06-10 17:59 UTC, Wayne E. Nail
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Wayne E. Nail 2024-06-10 17:59:47 UTC
Application: plasmashell (6.0.5)

Qt Version: 6.7.1
Frameworks Version: 6.3.0
Operating System: Linux 6.8.11-300.fc40.x86_64 x86_64
Windowing System: X11
Distribution: "Fedora Linux 40 (KDE Plasma)"
DrKonqi: 6.0.5 [CoredumpBackend]

-- Information about the crash:
~15 windows open on one of three desktop monitors, running rsync on ~6GB fileset over 1G ethernet. Brave browser (only one open) with ~100 tabs. One video in pop-out window playing. Plasmashell suddenly died and disappeared, as it has once before with this setup, two days ago, then came back. Video, IRC etc. continued without loss. Something made plasma switch to software rendering, which sucked until I logged out and back in.
Desktop effects: Translucency (custom settings), focus follows mouse (mouse precedence), four desktops, three monitors, two GPUs (onboard RS880, RX 570) . It's a Frankensystem with Asus AGM78-LE and Phenom II X4 955, 8GB DDR2-800 running at 533 because BIOS. Not production system.
There is an X11 use issue that may be related, as I am holding off dnf updates (  --exclude=plasma* ) until updated plasma-workspace-x11 is updated to match. I cannot use Wayland unless and until they allow a corner of the titlebar to raise focus on hover; I 'reverse cascade' windows to the left and down, use translucency to see what is going on up to four windows deep, and focus each window on hover without having to click. Wayland cannot do this. Phonecentric bias?

The reporter is unsure if this crash is reproducible.

-- Backtrace (Reduced):
#5  0x00007f8ad36b08a7 in KAStatsFavoritesModel::Private::Private(KAStatsFavoritesModel*, QString const&)::{lambda()#1}::operator()() const (__closure=0x555c34131f00) at /usr/src/debug/plasma-workspace-6.0.5.1-1.fc40.x86_64/applets/kicker/plugin/kastatsfavoritesmodel.cpp:196
#6  QtPrivate::FunctorCall<QtPrivate::IndexesList<>, QtPrivate::List<>, void, KAStatsFavoritesModel::Private::Private(KAStatsFavoritesModel*, QString const&)::{lambda()#1}>::call(KAStatsFavoritesModel::Private::Private(KAStatsFavoritesModel*, QString const&)::{lambda()#1}&, void**) (f=..., arg=<optimized out>) at /usr/include/qt6/QtCore/qobjectdefs_impl.h:137
#7  QtPrivate::FunctorCallable<KAStatsFavoritesModel::Private::Private(KAStatsFavoritesModel*, QString const&)::{lambda()#1}>::call<QtPrivate::List<>, void>(KAStatsFavoritesModel::Private::Private(KAStatsFavoritesModel*, QString const&)::{lambda()#1}&, void*, void**) (f=..., arg=<optimized out>) at /usr/include/qt6/QtCore/qobjectdefs_impl.h:345
#8  QtPrivate::QCallableObject<KAStatsFavoritesModel::Private::Private(KAStatsFavoritesModel*, QString const&)::{lambda()#1}, QtPrivate::List<>, void>::impl(int, QtPrivate::QSlotObjectBase*, QObject*, void**, bool*) (which=<optimized out>, this_=0x555c34131ef0, r=<optimized out>, a=<optimized out>, ret=<optimized out>) at /usr/include/qt6/QtCore/qobjectdefs_impl.h:555
#9  0x00007f8b0e5ebdeb in QObject::event (this=0x555c340f9e90, e=0x555c38206550) at /usr/src/debug/qt6-qtbase-6.7.1-2.fc40.x86_64/src/corelib/kernel/qobject.cpp:1452


Reported using DrKonqi
Comment 1 Wayne E. Nail 2024-06-10 17:59:55 UTC
Created attachment 170353 [details]
New crash information added by DrKonqi

DrKonqi auto-attaching complete backtrace.
Comment 2 Nate Graham 2024-06-10 20:47:06 UTC

*** This bug has been marked as a duplicate of bug 482887 ***