[kde] [Bug 464554] New: iKVM / BMC remote desktop spawns KDE session that never close

FrostKiwi bugzilla_noreply at kde.org
Fri Jan 20 15:19:38 GMT 2023


https://bugs.kde.org/show_bug.cgi?id=464554

            Bug ID: 464554
           Summary: iKVM / BMC remote desktop spawns KDE session that
                    never close
    Classification: I don't know
           Product: kde
           Version: unspecified
          Platform: NixOS
                OS: Linux
            Status: REPORTED
          Severity: normal
          Priority: NOR
         Component: general
          Assignee: unassigned-bugs at kde.org
          Reporter: kde at frost.kiwi
  Target Milestone: ---

Created attachment 155455
  --> https://bugs.kde.org/attachment.cgi?id=155455&action=edit
HTOP showing endless kde/plasma processes

On my NixOS Server I login through the iKVM Interface's Remote Desktop of my
Supermicro H12SSL motherboard to admin the system from time to time, especially
when SSH packets are aggresively filtered on the network I'm on, making SSH
logins impossible without tunneling SSH through HTTPS. I have KDE Plasma
installed on that system. As a result of many connections over the weeks, KDE
Plasma seems (?) to open a new Desktop session each time I connect, but never
close it.

As a result I end up in a situation like the video attached. A huge list of
/bin/plasmashell, org.kde.plasma.webrowser, kscreenlock, konsole etc.
I'm not actually sure if that's the reason or how to properly debug said
situation and it may not have anything to do with KDE or it's packages. Still I
would love some tip on how to debug this.

STEPS TO REPRODUCE
1. Login multiple times over the BMC's Remote desktop
2. See sessions piling on that never close

OBSERVED RESULT


EXPECTED RESULT
No endless lists of processes of the same name.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: NixOS 22.11
(available in About System)
KDE Plasma Version: 5.26.4
KDE Frameworks Version: 5.100.0
Qt Version: 5.15.7

-- 
You are receiving this mail because:
You are the assignee for the bug.


More information about the Unassigned-bugs mailing list