| Summary: | systemsettings crashes in BaseConfig::setActiveView() | ||
|---|---|---|---|
| Product: | [Applications] systemsettings | Reporter: | guenter <guenter.k> |
| Component: | generic-crash | Assignee: | Plasma Bugs List <plasma-bugs> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | crash | CC: | akselmo, arcadiy, guenter.k, kde, nate |
| Priority: | NOR | Keywords: | drkonqi |
| Version: | 5.20.2 | ||
| Target Milestone: | --- | ||
| Platform: | openSUSE | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
| Attachments: |
New crash information added by DrKonqi
New crash information added by DrKonqi |
||
|
Description
guenter
2020-11-12 17:07:30 UTC
>I set up Plasma Look&Feel trying to get back my "Task bar".
Trace implies something else.
Are you sure you hadn't opened the Configure System Settings dialog?
The one with the "Icon View" and "Sidebar View" selection
May be. I was looking/clicking around to find out how to get back my panel. Don't remember exactly which configurable item I was in. No more info available ATM. Correct: It was the Configure systemsettings dialog. It crashed again when doing nothing jaust hitting 'ok'-Button: systemsettings5 KCrash: Application 'systemsettings5' crashing... KCrash: Attempting to start /usr/lib64/libexec/drkonqi [1]+ Angehalten systemsettings5 guenter@prag:~> QSocketNotifier: Invalid socket 7 and type 'Read', disabling... QSocketNotifier: Invalid socket 8 and type 'Read', disabling... Unable to start Dr. Konqi Re-raising signal for core dump handling. Crash reproduceable. * run systemsettings5 * click "Configure" at the top * Click "Ok" ' Crash. Created attachment 133263 [details]
New crash information added by DrKonqi
systemsettings5 (5.20.2) using Qt 5.15.1
- What I was doing when the application crashed:
Crash reproduceable.
* run systemsettings5
* click "Configure" at the top
* Click "Ok"
' Crash.
-- Backtrace (Reduced):
#4 0x00007fd6e67d6190 in std::__atomic_base<int>::load (__m=std::memory_order_relaxed, this=<optimized out>) at /usr/include/c++/10/bits/atomic_base.h:420
#5 QAtomicOps<int>::loadRelaxed<int> (_q_value=...) at ../../include/QtCore/../../src/corelib/thread/qatomic_cxx11.h:239
#6 QBasicAtomicInteger<int>::loadRelaxed (this=<optimized out>) at ../../include/QtCore/../../src/corelib/thread/qbasicatomic.h:107
[...]
#8 QString::operator= (this=0x562fe04f3c00, other=...) at text/qstring.cpp:2408
#9 0x0000562fde72f98e in BaseConfig::setActiveView (v=...) at /usr/src/debug/systemsettings5-5.20.3-285.1.x86_64/build/app/BaseConfig.h:52
#9 0x000056094db8a98e in BaseConfig::setActiveView(QString const&) (v=...) at /usr/src/debug/systemsettings5-5.20.3-285.1.x86_64/build/app/BaseConfig.h:52 #10 BaseConfig::setActiveView(QString const&) (v=...) at /usr/src/debug/systemsettings5-5.20.3-285.1.x86_64/build/app/BaseConfig.h:49 #11 SettingsBase::configUpdated() (this=0x56094fa8af60) at /usr/src/debug/systemsettings5-5.20.3-285.1.x86_64/app/SettingsBase.cpp:295 Created attachment 133650 [details]
New crash information added by DrKonqi
systemsettings5 (5.18.4) using Qt 5.12.8
- What I was doing when the application crashed:
* Open "Configure"
* Click "OK"
* Crash (Note: Hitting "Cancel" is fine!)
-- Backtrace (Reduced):
#6 0x00007f7ce23201f4 in std::__atomic_base<int>::load (__m=std::memory_order_relaxed, this=<optimized out>) at /usr/include/c++/9/bits/atomic_base.h:413
#7 QAtomicOps<int>::load<int> (_q_value=...) at ../../include/QtCore/../../src/corelib/thread/qatomic_cxx11.h:227
#8 QBasicAtomicInteger<int>::load (this=<optimized out>) at ../../include/QtCore/../../src/corelib/thread/qbasicatomic.h:103
[...]
#10 QString::operator= (this=0x557ce8771050, other=...) at tools/qstring.cpp:2416
#11 0x0000557ce67d9dfe in BaseConfig::setActiveView (v=...) at ./obj-x86_64-linux-gnu/app/BaseConfig.h:52
>BaseConfig::setActiveView(possibleViews.keys().at(viewSelection.checkedId()));
That obviously isn't safe.
*** Bug 440847 has been marked as a duplicate of this bug. *** Have you encountered this bug again? 🐛🧹 ⚠️ This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information, then set the bug status to REPORTED. If there is no change for at least 30 days, it will be automatically closed as RESOLVED WORKSFORME. For more information about our bug triaging procedures, please read https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging. Thank you for helping us make KDE software even better for everyone! (In reply to Akseli Lahtinen from comment #11) > Have you encountered this bug again? I switched away from Plasma/KDE. So I cannot try the issue and do not need it any more. |