| Summary: | frozen session after swiching sessions when using two sessions | ||
|---|---|---|---|
| Product: | [Unmaintained] ksmserver | Reporter: | Martin Steigerwald <martin.steigerwald> |
| Component: | general | Assignee: | Lubos Lunak <l.lunak> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | crash | CC: | Martin |
| Priority: | NOR | ||
| Version First Reported In: | 5.7.3 | ||
| Target Milestone: | --- | ||
| Platform: | Other | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
Dear Bug Submitter, This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond. Thank you for helping us make KDE software even better for everyone! I did not see this issue since a long time. Thus closing. Thanks Andrew for reminding. |
Using Plasma 5.7.4 on KF 5.25. I use two Plasma sessions. One for the private user on tty7 and one for the work related user on tty8. On work breaks I switch between sessions. Sometimes it happens that either the work related or the private session is "frozen" then (see below). I seek help what I can do to find out what is going wrong with that frozen session in order to provide more helpful details for this bug report. Reproducible: Always Steps to Reproduce: 1. Have to Unix users 2. Use two Plasma sessions 3. After a while switch between them Note, it does not happen all the time. Actual Results: Sometimes it happens that either the work related or the private session is frozen then. "Frozen" means: It does not react to any user input. I cannot move windows, I cannot open menus, I cannot type text. I want to get back to work with the session quickly then, thus I then try to stop all processes of the "frozen" session from the other, still working session. Like this: merkaba:~> killall -u workuser merkaba:~> killall -u workuser merkaba:~> killall -u workuser merkaba:~> killall -u workuser merkaba:~> killall -u workuser merkaba:~> killall -u workuser merkaba:~> killall -u workuser merkaba:~> killall -u workuser merkaba:~> killall -u workuser merkaba:~> killall -u workuser merkaba:~> killall -u workuser merkaba:~> killall -u workuser merkaba:~> killall -u workuser Yet ksmserver remains: merkaba:~> ps aux | grep workuser root 45 0.0 0.0 0 0 ? S< 09:51 0:00 [vmstat] privateuser 2263 0.0 0.0 70088 4880 ? S 09:51 0:00 kwrapper5 / usr/bin/ksmserver privateuser 2264 0.0 0.1 618136 28000 ? Sl 09:51 0:00 /usr/bin/ ksmserver workuser 21169 0.0 0.0 618160 9148 ? S 13:21 0:00 /usr/bin/ ksmserver root 21303 0.0 0.0 12724 1028 pts/0 S+ 13:21 0:00 grep workuser And only goes away after: merkaba:~> killall -9 -u workuser Expected Results: Both sessions keep working over the whole duration I use them. This happens regardless of whether I use the Intel xorg driver or as recently the modesetting driver. On Debian Unstable on this ThinkPad T520: > phoronix-test-suite system-info Phoronix Test Suite v5.2.1 System Information Hardware: Processor: Intel Core i5-2520M @ 3.20GHz (4 Cores), Motherboard: LENOVO 42433WG, Chipset: Intel 2nd Generation Core Family DRAM, Memory: 16384MB, Disk: 300GB INTEL SSDSA2CW30 + 480GB Crucial_CT480M50, Graphics: Intel 2nd Generation Core Family IGP, Audio: Conexant CX20590, Monitor: P24T-7 LED, Network: Intel 82579LM Gigabit Connection + Intel Centrino Advanced-N 6205 Software: OS: Debian unstable, Kernel: 4.8.0-rc6-tp520-btrfstrim+ (x86_64), Desktop: KDE Frameworks 5, Display Server: X Server 1.18.4, Display Driver: modesetting 1.18.4, OpenGL: 3.3 Mesa 12.0.2, Compiler: GCC 6.2.0 20160901, File-System: btrfs (ecryptfs), Screen Resolution: 3840x1080