Bug 447764 - Configure Firewall crashed while viewing connections
Summary: Configure Firewall crashed while viewing connections
Status: RESOLVED WORKSFORME
Alias: None
Product: systemsettings
Classification: Applications
Component: kcm_firewall (other bugs)
Version First Reported In: 5.23.4
Platform: unspecified Linux
: NOR crash
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords: drkonqi
Depends on:
Blocks:
 
Reported: 2022-01-01 06:45 UTC by ptsd
Modified: 2022-02-11 04:37 UTC (History)
3 users (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description ptsd 2022-01-01 06:45:54 UTC
Application: kcmshell5 (5.23.4)

Qt Version: 5.15.2
Frameworks Version: 5.89.0
Operating System: Linux 5.15.12-arch1-1 x86_64
Windowing System: Wayland
Distribution: EndeavourOS
DrKonqi: 5.23.4 [KCrashBackend]

-- Information about the crash:
- What I was doing when the application crashed:
First install of ufw and after enabling firewall with the Firewall Status checkbox, pressing View Connections crashes the Configure Firewall System Settings Module every time

- Unusual behavior I noticed:
none

- Custom settings of the application:
first install enabling and starting ufw.service

The crash can be reproduced every time.

-- Backtrace:
Application: System Settings Module (kcmshell5), signal: Segmentation fault

[KCrash Handler]
#4  0x00007f9885c2521f in  () at /usr/lib/libQt5Core.so.5
#5  0x00007f9885c17802 in QString::split(QChar, QFlags<Qt::SplitBehaviorFlags>, Qt::CaseSensitivity) const () at /usr/lib/libQt5Core.so.5
#6  0x00007f987c4d7307 in  () at /usr/lib/qt/plugins/kcms/kcm_firewall.so
#7  0x00007f987c4d75cd in  () at /usr/lib/qt/plugins/kcms/kcm_firewall.so
#8  0x00007f9885d723e3 in  () at /usr/lib/libQt5Core.so.5
#9  0x00007f9885ccd73d in QProcess::finished(int, QProcess::ExitStatus) () at /usr/lib/libQt5Core.so.5
#10 0x00007f9885cc9f42 in  () at /usr/lib/libQt5Core.so.5
#11 0x00007f9885cce006 in  () at /usr/lib/libQt5Core.so.5
#12 0x00007f9885d7242f in  () at /usr/lib/libQt5Core.so.5
#13 0x00007f9885d740a4 in QSocketNotifier::activated(QSocketDescriptor, QSocketNotifier::Type, QSocketNotifier::QPrivateSignal) () at /usr/lib/libQt5Core.so.5
#14 0x00007f9885d741ef in QSocketNotifier::event(QEvent*) () at /usr/lib/libQt5Core.so.5
#15 0x00007f98869161a6 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5
#16 0x00007f9885d4189a in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib/libQt5Core.so.5
#17 0x00007f9885d8b8b6 in  () at /usr/lib/libQt5Core.so.5
#18 0x00007f9883cc952c in g_main_context_dispatch () at /usr/lib/libglib-2.0.so.0
#19 0x00007f9883d1d7b9 in  () at /usr/lib/libglib-2.0.so.0
#20 0x00007f9883cc6c11 in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0
#21 0x00007f9885d8ca8a in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib/libQt5Core.so.5
#22 0x00007f9885d39a9b in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib/libQt5Core.so.5
#23 0x00007f9885d452c7 in QCoreApplication::exec() () at /usr/lib/libQt5Core.so.5
#24 0x000055f46f9a63fa in  ()
#25 0x00007f988570cb25 in __libc_start_main () at /usr/lib/libc.so.6
#26 0x000055f46f9a757e in  ()
[Inferior 1 (process 85190) detached]

Possible duplicates by query: bug 391363, bug 390491, bug 390214.

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

> #6  0x00007f987c4d7307 in  () at /usr/lib/qt/plugins/kcms/kcm_firewall.so
> #7  0x00007f987c4d75cd in  () at /usr/lib/qt/plugins/kcms/kcm_firewall.so

Could you please install debug symbols for the Firewall KCM's 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-01-27 04:38:00 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-02-11 04:37:36 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!