Bug 452428 - Plasma crash on startup - Loading a widget
Summary: Plasma crash on startup - Loading a widget
Status: RESOLVED WORKSFORME
Alias: None
Product: plasmashell
Classification: Plasma
Component: Calendar (show other bugs)
Version: 5.24.4
Platform: Ubuntu Linux
: NOR crash
Target Milestone: 1.0
Assignee: Plasma Bugs List
URL:
Keywords: drkonqi
Depends on:
Blocks:
 
Reported: 2022-04-09 12:00 UTC by Pivert
Modified: 2022-05-11 04:35 UTC (History)
2 users (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Pivert 2022-04-09 12:00:25 UTC
Application: plasmashell (5.24.4)

Qt Version: 5.15.3
Frameworks Version: 5.92.0
Operating System: Linux 5.15.0-25-generic x86_64
Windowing System: X11
Distribution: Ubuntu Jammy Jellyfish (development branch)
DrKonqi: 5.24.4 [KCrashBackend]

-- Information about the crash:
- What I was doing when the application crashed:
Just logging in KDE session

- Custom settings of the application:
Nothing particular, except the "calendar" widget on the desktop.

- In order to workaround the problem, I removed all references for that plugin in the plasma-org.kde.plasma.desktop-appletsrc and started plasmashell. ( using Alt+F2 ... )

pivert@pivert-X400:~/.config$ diff ../Archive/plasma-org.kde.plasma.desktop-appletsrc ./plasma-org.kde.plasma.desktop-appletsrc | grep -F '['
< [Containments][1][Applets][25]
< [Containments][1][Applets][25][Configuration]
< [Containments][1][Applets][25][Configuration][ConfigDialog]
< [Containments][1][Applets][25][Configuration][General]
< [Containments][1][Applets][25][Configuration][Google Calendar]
< [Containments][1][Applets][25][Configuration][Weather]
pivert@pivert-X400:~/.config$

The crash can be reproduced every time.

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

[KCrash Handler]
#4  0x00007f73982307eb in ?? () from /usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/plasma/calendar/libcalendarplugin.so
#5  0x00007f73dcac845e in QObject::event(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x00007f73dd791713 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#7  0x00007f73dca9ae7a in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x00007f73dca9df67 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#9  0x00007f73dcaf4aa7 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#10 0x00007f73dae76d1b in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#11 0x00007f73daecb6f8 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#12 0x00007f73dae743c3 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#13 0x00007f73dcaf40f8 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#14 0x00007f73dca9979b in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#15 0x00007f73dcaa1d34 in QCoreApplication::exec() () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#16 0x000055792f762dce in ?? ()
#17 0x00007f73dc3b6d90 in __libc_start_call_main (main=main@entry=0x55792f761f70, argc=argc@entry=1, argv=argv@entry=0x7ffd378a4cb8) at ../sysdeps/nptl/libc_start_call_main.h:58
#18 0x00007f73dc3b6e40 in __libc_start_main_impl (main=0x55792f761f70, argc=1, argv=0x7ffd378a4cb8, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7ffd378a4ca8) at ../csu/libc-start.c:392
#19 0x000055792f762ef5 in ?? ()
[Inferior 1 (process 2175) detached]

Possible duplicates by query: bug 452258, bug 452073, bug 452001, bug 451880, bug 451864.

Reported using DrKonqi
Comment 1 Nate Graham 2022-04-11 17:39:04 UTC
> #4  0x00007f73982307eb in ?? () from /usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/plasma/calendar/libcalendarplugin.so
Looks like it's crashing somewhere in some calendar plugin. Can you install full debug symbols for plasma-desktop and plasma-workspace, reproduce the crash, and attach a new backtrace that has debug symbols for this stack frame? Thanks!
Comment 2 Bug Janitor Service 2022-04-26 04:35:12 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-05-11 04:35:10 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!