Bug 438227 - System Settings freeze when opened after KSystemLog
Summary: System Settings freeze when opened after KSystemLog
Status: RESOLVED WAITINGFORINFO
Alias: None
Product: systemsettings
Classification: Applications
Component: general (other bugs)
Version First Reported In: 5.21.90
Platform: Kubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords: efficiency-and-performance
Depends on:
Blocks:
 
Reported: 2021-06-07 21:17 UTC by Bruno
Modified: 2024-09-16 11:06 UTC (History)
3 users (show)

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

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Bruno 2021-06-07 21:17:58 UTC 
SUMMARY
When open "System Settings" after KSystemLog, "System Settings" freeze.

STEPS TO REPRODUCE
1. Open KSystemLog and enter the password
2. Open "System Settings"

OBSERVED RESULT
"System Settings" not respond.


EXPECTED RESULT
"System Settings" respond correctly.

SOFTWARE/OS VERSIONS
Operating System: Kubuntu 21.10
KDE Plasma Version: 5.21.90
KDE Frameworks Version: 5.82.0
Qt Version: 5.15.2
Kernel Version: 5.11.0-16-generic (64-bit)
Graphics Platform: X11
Processors: 4 × Intel® Core™ i5-4200U CPU @ 1.60GHz
Memory: 9.6 GiB of RAM
Graphics Processor: Mesa DRI Intel® HD Graphics 4400

ADDITIONAL INFORMATION
Comment 1 Nate Graham 2021-06-08 19:22:40 UTC 
Cannot reproduce. Can you please attach a backtrace of what System Settings is doing when it hangs? To do this, you would need to launch the app using gdb, like so:

`gdb /usr/bin/systemsettings5`

Then type "run". When it freezes, type "bt" and then paste the full output in here.
Comment 2 Bruno 2021-06-09 01:08:36 UTC 
(gdb) run
Starting program: /usr/bin/systemsettings5 
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x7ffff1469640 (LWP 4806)]
[New Thread 0x7fffebfff640 (LWP 4807)]
[New Thread 0x7fffe9be4640 (LWP 4808)]
[New Thread 0x7fffe93e3640 (LWP 4809)]
[New Thread 0x7fffe8be2640 (LWP 4810)]
[New Thread 0x7fffdbfff640 (LWP 4811)]
[New Thread 0x7fffdad94640 (LWP 4812)]
[New Thread 0x7fffda593640 (LWP 4813)]
[New Thread 0x7fffd9d92640 (LWP 4814)]
[New Thread 0x7fffd9591640 (LWP 4815)]
[New Thread 0x7fffd8b65640 (LWP 4816)]
[New Thread 0x7fffbe992640 (LWP 4817)]
QQmlEngine::setContextForObject(): Object already has a QQmlContext
[Detaching after fork from child process 4819]
[Detaching after fork from child process 4820]
[New Thread 0x7fffbd4d3640 (LWP 4821)]
QQmlEngine::setContextForObject(): Object already has a QQmlContext
QQmlEngine::setContextForObject(): Object already has a QQmlContext
bt
[Thread 0x7fffd9591640 (LWP 4815) exited]
[Thread 0x7fffd9d92640 (LWP 4814) exited]
[Thread 0x7fffda593640 (LWP 4813) exited]
[Thread 0x7fffdad94640 (LWP 4812) exited]
Comment 3 Nate Graham 2021-06-09 14:48:23 UTC 
Hmm, that doesn't tell us much. :/
Comment 4 David Edmundson 2024-09-16 11:06:07 UTC 
It could be the issue of an existing systemsettings not exiting properly that we've seen with the GHNS issue. Please reopen if an issue persists with Plasma 6.2