Bug 456560 - KDE Crashes when changing the theme in system settings
Summary: KDE Crashes when changing the theme in system settings
Status: RESOLVED WORKSFORME
Alias: None
Product: Discover
Classification: Applications
Component: discover (show other bugs)
Version: 5.25.2
Platform: openSUSE Linux
: NOR crash
Target Milestone: ---
Assignee: Dan Leinir Turthra Jensen
URL:
Keywords: drkonqi
Depends on:
Blocks:
 
Reported: 2022-07-10 18:07 UTC by paulflaherty5
Modified: 2022-09-21 04:47 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
New crash information added by DrKonqi (2.58 KB, text/plain)
2022-08-06 21:24 UTC, Adrian Constantin
Details
attachment-30635-0.html (1.42 KB, text/html)
2022-08-22 04:57 UTC, paulflaherty5
Details

Note You need to log in before you can comment on or make changes to this bug.
Description paulflaherty5 2022-07-10 18:07:18 UTC
Application: plasma-discover (5.25.2)

Qt Version: 5.15.5
Frameworks Version: 5.95.0
Operating System: Linux 5.18.9-1-default x86_64
Windowing System: X11
Distribution: openSUSE Tumbleweed
DrKonqi: 5.25.2 [KCrashBackend]

-- Information about the crash:
When changing the theme from the openSUSE default theme to breeze dark when clicking the button right after the action the entire plasma desktop crashes. But Kwin stays open and then plasma relaunches. I am using openSUSE tumbleweed with KDE.

The crash can be reproduced every time.

-- Backtrace:
Application: Discover (plasma-discover), signal: Segmentation fault

[KCrash Handler]
#4  0x00007eff254b63ab in QTextStream::operator<<(char) () from /lib64/libQt5Core.so.5
#5  0x00007eff044ec13d in ?? () from /usr/lib64/qt5/plugins/discover/flatpak-backend.so
#6  0x00007eff045020d9 in ?? () from /usr/lib64/qt5/plugins/discover/flatpak-backend.so
#7  0x00007eff2545ae6f in ?? () from /lib64/libQt5Core.so.5
#8  0x00007eff2734840e in Transaction::statusChanged(Transaction::Status) () from /usr/lib64/plasma-discover/libDiscoverCommon.so
#9  0x00007eff2734ebac in Transaction::setStatus(Transaction::Status) () from /usr/lib64/plasma-discover/libDiscoverCommon.so
#10 0x00007eff2544f760 in QObject::event(QEvent*) () from /lib64/libQt5Core.so.5
#11 0x00007eff2667441e in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib64/libQt5Widgets.so.5
#12 0x00007eff25423fb8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib64/libQt5Core.so.5
#13 0x00007eff25426f51 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /lib64/libQt5Core.so.5
#14 0x00007eff2547bc53 in ?? () from /lib64/libQt5Core.so.5
#15 0x00007eff23c18ea0 in g_main_context_dispatch () from /lib64/libglib-2.0.so.0
#16 0x00007eff23c19258 in ?? () from /lib64/libglib-2.0.so.0
#17 0x00007eff23c192ec in g_main_context_iteration () from /lib64/libglib-2.0.so.0
#18 0x00007eff2547b456 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib64/libQt5Core.so.5
#19 0x00007eff25422a2b in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib64/libQt5Core.so.5
#20 0x00007eff2542ab96 in QCoreApplication::exec() () from /lib64/libQt5Core.so.5
#21 0x000055672fb99edf in ?? ()
#22 0x00007eff24d2b5b0 in __libc_start_call_main () from /lib64/libc.so.6
#23 0x00007eff24d2b679 in __libc_start_main_impl () from /lib64/libc.so.6
#24 0x000055672fb9a895 in ?? ()
[Inferior 1 (process 6173) detached]

Reported using DrKonqi
Comment 1 Nate Graham 2022-07-13 19:19:15 UTC
Thank you for the bug report! Unfortunately the backtrace is incomplete and missing debug symbols for the following lines that we need to figure out exactly what's going wrong:

> #5  0x00007eff044ec13d in ?? () from /usr/lib64/qt5/plugins/discover/flatpak-backend.so
> #6  0x00007eff045020d9 in ?? () from /usr/lib64/qt5/plugins/discover/flatpak-backend.so

Could you please install debug symbols for Discover's flatpak backend package, reproduce the crash, and attach a new symbolicated backtrace? See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports

Thanks again!
Comment 2 Bug Janitor Service 2022-07-28 04:35:59 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 Adrian Constantin 2022-08-06 21:24:21 UTC
Created attachment 151156 [details]
New crash information added by DrKonqi

plasma-discover (5.25.4) using Qt 5.15.5

To me this Discover has crashed when I installed WhatsApp client for Linux flatpack, at the end of the installation. I do have a custom theme selected (Harmony-Global, that I very much like). The newly installed WhatsApp application appears to work properly, so maybe the installation completed successfully before Discover crashed.

-- Backtrace (Reduced):
#4  0x00007fda1fb1c3ab in QTextStream::operator<<(char) () from /lib64/libQt5Core.so.5
[...]
#8  0x00007fda219b639e in Transaction::statusChanged(Transaction::Status) () from /usr/lib64/plasma-discover/libDiscoverCommon.so
#9  0x00007fda219bca8c in Transaction::setStatus(Transaction::Status) () from /usr/lib64/plasma-discover/libDiscoverCommon.so
#10 0x00007fda1fab5760 in QObject::event(QEvent*) () from /lib64/libQt5Core.so.5
#11 0x00007fda20cda41e in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib64/libQt5Widgets.so.5
Comment 4 Bug Janitor Service 2022-08-21 04:35:31 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 5 paulflaherty5 2022-08-22 04:57:37 UTC
Created attachment 151493 [details]
attachment-30635-0.html

The issue still happens

Sent from Proton Mail for iOS

On Sun, Aug 21, 2022 at 12:35 AM, Bug Janitor Service <bugzilla_noreply@kde.org> wrote:

> https://bugs.kde.org/show_bug.cgi?id=456560
>
> --- Comment #4 from Bug Janitor Service <bug-janitor@kde.org> ---
> 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!
>
> --
> You are receiving this mail because:
> You reported the bug.
Comment 6 Bug Janitor Service 2022-09-06 04:36:13 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 7 Bug Janitor Service 2022-09-21 04:47:22 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!