| Summary: | plasma session doesn't clear tty it uses. | ||
|---|---|---|---|
| Product: | [Plasma] kwin | Reporter: | Bhushan Shah <bhush94> |
| Component: | platform-drm | Assignee: | KWin default assignee <kwin-bugs-null> |
| Status: | RESOLVED UPSTREAM | ||
| Severity: | normal | CC: | arjan, azrdev, bsmith7581, bugseforuns, gplm+kde, jcdopsec, nate, notuxius, piotr.mierzwinski, smpoole7, vkrevs, xaver.hugl |
| Priority: | NOR | ||
| Version: | git master | ||
| Target Milestone: | --- | ||
| Platform: | Other | ||
| OS: | Linux | ||
| Latest Commit: | https://github.com/sddm/sddm/pull/1273/commits/0f7f98975beb20f7408e8c89327322ed0c1442d8 | Version Fixed In: | SDDM 0.19 |
|
Description
Bhushan Shah
2015-11-26 07:35:58 UTC
is that still the case? I assume it might have been related to kwin crashing on tear down. So with a clean shutdown: does it work? Yes, I guess its still case. But I haven't tried in while.. will do and report later. I can confirm it's still the case with plasma 5.10 beta. The TTY2 remain unusable after logging out of a plasma wayland session. Is that problem also reproducable with Weston? Can't logout from Weston session - logging out hangs with blank screen
Distribution: Netrunner Rolling
Kernel: 4.18.0-1-MANJARO
Plasma: 5.13.3
Apps: 18.04.3
Qt: 5.11.1
Frameworks: 5.48.0
Wayland: 1.15.0
Graphics: Card-1: Intel Haswell-ULT Integrated Graphics driver: i915 v: kernel bus ID: 00:02.0
chip ID: 8086:0a16
Display: wayland server: X.Org 1.20.0 driver: intel unloaded: modesetting alternate: fbdev,vesa
compositor: kwin wayland tty: N/A
OpenGL: renderer: Mesa DRI Intel Haswell Mobile v: 4.5 Mesa 18.1.4 compat-v: 3.0 direct render: Yes
This problem persists with plasma 5.15 on Arch linux. Every time I restart Wayland session, the next TTY becomes unusable with cursor blinking in the upper left corner. I restart Wayland session, TTY2 becomes unusable, so I restart plasma Wayland again and TTY3 becomes unusable, etc. This still happens on Plasma 5.18.2. I used the Wayland session, logged out, and switched back to Xorg. If I switch to TTY2, it is unusable, just a lot of "@" symbols followed by a blinking cursor. If I create another Plasma Wayland session, it uses TTY3, then TTY4, and so on. Same here but for some reason a lot of processes keep file descriptors open to multiple terminals at the same time.
What is shown here is the result of Wayland Plasma after 2 logouts en 3 loggins
Where tty4 is the current wayland terminal.
I'm using Kubuntu 20.04 KDE Plasma 5.18.5.
But maybe it is not KDE Plasma but a Kubuntu integration problem.
--
user@adelaide:~$ who -la
system boot Jun 10 17:33
run-level 5 Jun 10 17:33
tty2 Jun 10 17:42 1569 id= term=0 exit=0
user + pts/0 Jun 10 17:44 00:01 3605 (:1)
tty3 Jun 10 17:44 2544 id= term=0 exit=0
user - pts/1 Jun 10 17:45 . 4094 (:1)
user + tty4 Jun 10 17:44 00:12 3479
user@adelaide:~$ lsof /dev/tty3
COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
dbus-run- 3479 user 25u CHR 4,3 0t0 24 /dev/tty3
dbus-daem 3487 user 25u CHR 4,3 0t0 24 /dev/tty3
startplas 3488 user 25u CHR 4,3 0t0 24 /dev/tty3
Xwayland 3522 user 25u CHR 4,3 0t0 24 /dev/tty3
startplas 3581 user 25u CHR 4,3 0t0 24 /dev/tty3
plasma_se 3682 user 25u CHR 4,3 0t0 24 /dev/tty3
ksmserver 3688 user 25u CHR 4,3 0t0 24 /dev/tty3
baloo_fil 3712 user 25u CHR 4,3 0t0 24 /dev/tty3
plasmashe 3715 user 25u CHR 4,3 0t0 24 /dev/tty3
xembedsni 3717 user 25u CHR 4,3 0t0 24 /dev/tty3
gmenudbus 3755 user 25u CHR 4,3 0t0 24 /dev/tty3
DiscoverN 3757 user 25u CHR 4,3 0t0 24 /dev/tty3
kdeconnec 3790 user 25u CHR 4,3 0t0 24 /dev/tty3
agent 3796 user 25u CHR 4,3 0t0 24 /dev/tty3
org_kde_p 3807 user 25u CHR 4,3 0t0 24 /dev/tty3
at-spi-bu 3817 user 25u CHR 4,3 0t0 24 /dev/tty3
kmix 3827 user 25u CHR 4,3 0t0 24 /dev/tty3
ksysguard 3897 user 25u CHR 4,3 0t0 24 /dev/tty3
konsole 4070 user 25u CHR 4,3 0t0 24 /dev/tty3
bash 4094 user 25u CHR 4,3 0t0 24 /dev/tty3
user@adelaide:~$ lsof /dev/tty2
COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
baloo_fil 2784 user 28u CHR 4,2 0t0 23 /dev/tty2
agent 2868 user 28u CHR 4,2 0t0 23 /dev/tty2
dbus-run- 3479 user 28u CHR 4,2 0t0 23 /dev/tty2
dbus-daem 3487 user 28u CHR 4,2 0t0 23 /dev/tty2
startplas 3488 user 28u CHR 4,2 0t0 23 /dev/tty2
Xwayland 3522 user 28u CHR 4,2 0t0 23 /dev/tty2
startplas 3581 user 28u CHR 4,2 0t0 23 /dev/tty2
plasma_se 3682 user 28u CHR 4,2 0t0 23 /dev/tty2
ksmserver 3688 user 28u CHR 4,2 0t0 23 /dev/tty2
baloo_fil 3712 user 28u CHR 4,2 0t0 23 /dev/tty2
plasmashe 3715 user 28u CHR 4,2 0t0 23 /dev/tty2
xembedsni 3717 user 28u CHR 4,2 0t0 23 /dev/tty2
gmenudbus 3755 user 28u CHR 4,2 0t0 23 /dev/tty2
DiscoverN 3757 user 28u CHR 4,2 0t0 23 /dev/tty2
kdeconnec 3790 user 28u CHR 4,2 0t0 23 /dev/tty2
agent 3796 user 28u CHR 4,2 0t0 23 /dev/tty2
org_kde_p 3807 user 28u CHR 4,2 0t0 23 /dev/tty2
at-spi-bu 3817 user 28u CHR 4,2 0t0 23 /dev/tty2
kmix 3827 user 28u CHR 4,2 0t0 23 /dev/tty2
ksysguard 3897 user 28u CHR 4,2 0t0 23 /dev/tty2
konsole 4070 user 28u CHR 4,2 0t0 23 /dev/tty2
bash 4094 user 28u CHR 4,2 0t0 23 /dev/tty2
user@adelaide:~$ lsof /dev/tty4
COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
dbus-run- 3479 user 0u CHR 4,4 0t0 25 /dev/tty4
startplas 3488 user 0u CHR 4,4 0t0 25 /dev/tty4
user@adelaide:~$
This bug is not a KWin bug but a sddm one and has been fixed with 0.19: https://github.com/sddm/sddm/pull/1273 I tested it on Manjaro and ttys are no longer being used up. *** Bug 407305 has been marked as a duplicate of this bug. *** I'm on openSUSE 15.2 with sddm-0.19.0-lp152.96.6.x86_64 and the issue is still present. Or does it also require "ReuseSession=true" to work? Probably, yeah. *** Bug 426980 has been marked as a duplicate of this bug. *** *** Bug 416557 has been marked as a duplicate of this bug. *** *** Bug 364499 has been marked as a duplicate of this bug. *** |