Bug 457614 - Plasmashell crashes in ShellCorona::screenForContainment()
Summary: Plasmashell crashes in ShellCorona::screenForContainment()
Status: RESOLVED FIXED
Alias: None
Product: plasmashell
Classification: Plasma
Component: generic-multiscreen (show other bugs)
Version: 5.25.4
Platform: Fedora RPMs Linux
: NOR crash
Target Milestone: 1.0
Assignee: Plasma Bugs List
URL:
Keywords: drkonqi
Depends on:
Blocks:
 
Reported: 2022-08-08 06:00 UTC by Thomas Pasch
Modified: 2023-01-03 11:38 UTC (History)
5 users (show)

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


Attachments
New crash information added by DrKonqi (4.07 KB, text/plain)
2022-10-09 22:03 UTC, Adirson Silva
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Thomas Pasch 2022-08-08 06:00:31 UTC
Application: plasmashell (5.25.4)

Qt Version: 5.15.5
Frameworks Version: 5.96.0
Operating System: Linux 5.18.15-200.fc36.x86_64 x86_64
Windowing System: X11
Distribution: "Fedora release 36 (Thirty Six)"
DrKonqi: 5.25.4 [KCrashBackend]

-- Information about the crash:
KDE problems with fedora 36 on with nvidia 515.65.01 driver

For same days now, it seems there are problems on fedora 36 with nvidia support. This bug is a result of this.

The reporter is unsure if this crash is reproducible.

-- Backtrace:
Application: Plasma (plasmashell), signal: Segmentation fault

[KCrash Handler]
#4  0x00007f99cdf9ed84 in PlasmaQuick::ContainmentView::containment() const () from /lib64/libKF5PlasmaQuick.so.5
#5  0x000055b6c1bfd54d in ShellCorona::screenForContainment(Plasma::Containment const*) const ()
#6  0x000055b6c1bfab68 in ShellCorona::createContainmentForActivity(QString const&, int) ()
#7  0x000055b6c1bf1893 in ShellCorona::addOutput(QScreen*) ()
#8  0x00007f99cbadb8c6 in void doActivate<false>(QObject*, int, void**) () from /lib64/libQt5Core.so.5
#9  0x000055b6c1c0c31e in ScreenPool::handleScreenAdded(QScreen*) ()
#10 0x00007f99cbadb8c6 in void doActivate<false>(QObject*, int, void**) () from /lib64/libQt5Core.so.5
#11 0x00007f99cbf5ddf6 in QGuiApplication::screenAdded(QScreen*) () from /lib64/libQt5Gui.so.5
#12 0x00007f99b9b1bfcf in QXcbConnection::createScreen(QXcbVirtualDesktop*, xcb_randr_output_change_t const&, xcb_randr_get_output_info_reply_t*) () from /lib64/libQt5XcbQpa.so.5
#13 0x00007f99b9b1e919 in QXcbConnection::updateScreens(xcb_randr_notify_event_t const*) () from /lib64/libQt5XcbQpa.so.5
#14 0x00007f99b9af2ab7 in QXcbConnection::handleXcbEvent(xcb_generic_event_t*) () from /lib64/libQt5XcbQpa.so.5
#15 0x00007f99b9af3856 in QXcbConnection::processXcbEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib64/libQt5XcbQpa.so.5
#16 0x00007f99b9b19e47 in xcbSourceDispatch(_GSource*, int (*)(void*), void*) () from /lib64/libQt5XcbQpa.so.5
#17 0x00007f99c9fe5faf in g_main_context_dispatch () from /lib64/libglib-2.0.so.0
#18 0x00007f99ca03b2c8 in g_main_context_iterate.constprop () from /lib64/libglib-2.0.so.0
#19 0x00007f99c9fe3940 in g_main_context_iteration () from /lib64/libglib-2.0.so.0
#20 0x00007f99cbaf8f5a in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib64/libQt5Core.so.5
#21 0x00007f99cbaa6c7a in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib64/libQt5Core.so.5
#22 0x00007f99cbaaed42 in QCoreApplication::exec() () from /lib64/libQt5Core.so.5
#23 0x000055b6c1bcd165 in main ()
[Inferior 1 (process 4835) detached]

Reported using DrKonqi
Comment 1 Nate Graham 2022-08-08 17:36:54 UTC
When does the crash happen? It is a result of plugging or unplugging a screen, or waking the machine up from suspend, or logging in? Or does it crash when you're not doing anything related to any of those activities?
Comment 2 Bug Janitor Service 2022-08-23 04:35:36 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 3 Bug Janitor Service 2022-09-07 04:36:13 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!
Comment 4 Adirson Silva 2022-10-09 22:03:54 UTC
Created attachment 152673 [details]
New crash information added by DrKonqi

plasmashell (5.25.4) using Qt 5.15.2

The issue started with nomal upgrade from -5.19.12-100.fc35.x86_64 to -5.19.13-100.fc35.x86_64-5.19.12-100.fc35.x86_64 (also on -5.19.14-100.fc35.x86_64)
Secure boot is enabled and no custom kernel or nvidia driver is in use. I have switched to non-gui login and whitelisted amdgpu. "startx" brings up gdm or kdm(plasma) but both crashes. Fedora starts after in this mode.

           /:-------------:\          ########
        :-------------------::        OS: Fedora 
      :-----------/shhOHbmp---:\      Kernel: x86_64 Linux 5.19.14-100.fc35.x86_64
    /-----------omMMMNNNMMD  ---:     Uptime: 15m
   :-----------sMMMMNMNMP.    ---:    Packages: 3175
  :-----------:MMMdP-------    ---\   Shell: bash 5.1.8
 ,------------:MMMd--------    ---:   Resolution: 3840x1080
 :------------:MMMd-------    .---:   DE: KDE 5.96.0 / Plasma 5.25.4
 :----    oNMMMMMMMMMNho     .----:   WM: KWin
 :--     .+shhhMMMmhhy++   .------/   WM Theme: Oxygen
 :-    -------:MMMd--------------:    GTK Theme:  [GTK2/3]
 :-   --------/MMMd-------------;     Icon Theme: breeze-dark
 :-    ------/hMMMy------------:      Disk: 222G / 501G (45%)
 :-- :dMNdhhdNMMNo------------;       CPU: AMD Ryzen 9 4900HS with Radeon Graphics @ 16x 3GHz
 :---:sdNMMMMNds:------------:        GPU: NVIDIA GeForce RTX 2060 with Max-Q Design
 :------:://:-------------::          RAM: 4415MiB / 15302MiB
 :---------------------://        
$ supergfxctl -S -g
dedicated
active
sudo grubby --info=0
index=0
kernel="/boot/vmlinuz-5.19.14-100.fc35.x86_64"
args="ro supergfxd.mode=dedicated rhgb quiet rd.driver.blacklist=nouveau modprobe.blacklist=nouveau initcall_blacklist=simpledrm_platform_driver_init nvidia-drm.modeset=0"

-- Backtrace (Reduced):
#4  0x00007f4a53e50174 in PlasmaQuick::ContainmentView::containment() const () from /lib64/libKF5PlasmaQuick.so.5
#5  0x0000561521c5094a in ShellCorona::screenForContainment(Plasma::Containment const*) const ()
#6  0x0000561521c4df48 in ShellCorona::createContainmentForActivity(QString const&, int) ()
#7  0x0000561521c44aee in ShellCorona::addOutput(QScreen*) ()
#8  0x00007f4a51c777d9 in void doActivate<false>(QObject*, int, void**) () from /lib64/libQt5Core.so.5
Comment 5 David Edmundson 2023-01-03 11:38:56 UTC
Should be fixed in Plasma 5.27.0