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

            Bug ID: 489628
           Summary: After resume, there is a small to medium chance
                    plasmashell will crash
    Classification: Plasma
           Product: plasmashell
           Version: 6.1.1
          Platform: Fedora RPMs
                OS: Linux
            Status: REPORTED
          Keywords: drkonqi
          Severity: crash
          Priority: NOR
         Component: generic-crash
          Assignee: plasma-b...@kde.org
          Reporter: farch...@gmail.com
  Target Milestone: 1.0

Application: plasmashell (6.1.1)

Qt Version: 6.7.1
Frameworks Version: 6.3.0
Operating System: Linux 6.9.6-200.fc40.x86_64 x86_64
Windowing System: Wayland
Distribution: "Fedora release 40 (Forty)"
DrKonqi: 6.1.1 [CoredumpBackend]

-- Information about the crash:
This crash is part of an ongoing annoyance since plasma 6.1's release.

First, this is a dual screen setup, with two screens side-by-side. Each screen
has an identical layout, I got a mac-like bar on top containing an application
launcher, global menu, large spacer and then the system tray. The bottom part
is a mac-like dock (minus the magnification effects) that auto-hides,
containing my currently running application icons, and some other pinned apps.
Please do note that, for those, I use nothing but default widgets, nothing is
custom.

I have had an issue since 6.1 where, if I put my computer on standby, once I
resume, there is a high chance (~60-80%) that my bottom "dock" bar will no
longer show when I hover over the bottom area. Usually, in order to fix this, I
have to go and put the desktop in "Edit mode" (i.e. Right-click on the top bar,
and click on "Add widgets"), and then simply cancel out of it.

The crash that this bug is created from though happens maybe 15-20% of the time
when I resume and the dock doesn't show, and I click on the top bar to go back
in "Edit mode". Except, right-clicking does nothing, and 5 seconds later,
plasmashell just crashes.

The crash can be reproduced sometimes.

-- Backtrace (Reduced):
#5  0x00007f468f032e18 in QScreen::devicePixelRatio (this=0x55769ef48310) at
/usr/src/debug/qt6-qtbase-6.7.1-2.fc40.x86_64/src/gui/kernel/qscreen.cpp:288
#6  0x00007f468f042858 in QWindowPrivate::updateDevicePixelRatio
(this=0x5576a3c21060) at
/usr/src/debug/qt6-qtbase-6.7.1-2.fc40.x86_64/src/gui/kernel/qwindow.cpp:1404
#7  0x00007f468e7fa752 in QtPrivate::QSlotObjectBase::call
(this=0x5576a3cd21d0, r=<optimized out>, a=0x7fff53341eb0) at
/usr/src/debug/qt6-qtbase-6.7.1-2.fc40.x86_64/src/corelib/kernel/qobjectdefs_impl.h:469
#8  doActivate<false> (sender=0x7f46740e9260, signal_index=3,
argv=0x7fff53341eb0) at
/usr/src/debug/qt6-qtbase-6.7.1-2.fc40.x86_64/src/corelib/kernel/qobject.cpp:4086
[...]
#10 0x00007f468f03d251 in QWindow::screenChanged
(this=this@entry=0x7f46740e9260, _t1=<optimized out>, _t1@entry=0x55769ef48310)
at
/usr/src/debug/qt6-qtbase-6.7.1-2.fc40.x86_64/redhat-linux-build/src/gui/Gui_autogen/include/moc_qwindow.cpp:817


Reported using DrKonqi

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to