Name: lightdm State: S (sleeping) Tgid: 22156 Pid: 22156 PPid: 1 TracerPid: 0 Uid: 0 0 0 0 Gid: 0 0 0 0 FDSize: 32 Groups: 0 1 2 3 4 6 10 11 26 27 VmPeak: 208576 kB VmSize: 207796 kB VmLck: 207792 kB VmPin: 0 kB VmHWM: 204904 kB VmRSS: 204904 kB VmData: 200060 kB VmStk: 136 kB VmExe: 164 kB VmLib: 7160 kB VmPTE: 416 kB VmSwap: 0 kB Threads: 3 SigQ: 1/16060 SigPnd: 0000000000000000 ShdPnd: 0000000000000000 SigBlk: 0000000000000000 SigIgn: 0000000000001000 SigCgt: 0000000180014a03 CapInh: 0000000000000000 CapPrm: 0000001fffffffff CapEff: 0000001fffffffff CapBnd: 0000001fffffffff Seccomp: 0 Cpus_allowed: f Cpus_allowed_list: 0-3 Mems_allowed: 1 Mems_allowed_list: 0 voluntary_ctxt_switches: 73 nonvoluntary_ctxt_switches: 26 Reproducible: Always Actual Results: a bunch of locked memory that looks funny I don't get why a display manager is using 200 MB of locked memory in the first place. Aren't these programs supposed to be lightweight?
lightdm version: lightdm 1.4.0
Please post your `emerge --info x11-misc/lightdm' output in a comment.
Created attachment 363908 [details] requested
1.4.0 is really old. Try the latest version. And if it's still there, you need to report it upstream
You did not answer my question. Does the new version fixes the problem?
Sorry! >_< I thought this bug was no good anymore. I'll check the latest version now if you'd rather I not wait for stabilization.
(In reply to shentino from comment #6) > Sorry! >_< > > I thought this bug was no good anymore. > > I'll check the latest version now if you'd rather I not wait for > stabilization. if the problem is present in the latest version then the stabilization will not fix anything for you
What I meant was that I will keyword it so I can install the latest version for testing, instead of waiting for stabilization before upgrading automatically.
