| 1 |
J. Roeleveld wrote: |
| 2 |
> On 20 May 2020 17:56:29 CEST, Dale <rdalek1967@×××××.com> wrote: |
| 3 |
>> J. Roeleveld wrote: |
| 4 |
>>> Dale, |
| 5 |
>>> |
| 6 |
>>> The few times I have issues with "sddm-helper" is when I resume my |
| 7 |
>> laptop from |
| 8 |
>>> hibernate. (Not always, but occasionally) |
| 9 |
>>> The issue I see is 100% CPU-usage and a black X-display. I can switch |
| 10 |
>> to |
| 11 |
>>> console (CTRL+ALT+F1), login as root and kill the offending |
| 12 |
>> sddm-helper. |
| 13 |
>>> It gets restarted automatically and I see no issue. |
| 14 |
>>> |
| 15 |
>>> Do you tend to lock your screen a lot? As it might be related to |
| 16 |
>> screensavers. |
| 17 |
>>> (I have a simple static lock-screen, nothing remotely fancy) |
| 18 |
>>> |
| 19 |
>>> Also, you can try killing "kill -9 sddm-helper" when it goes up and |
| 20 |
>> see what |
| 21 |
>>> happens next. |
| 22 |
>>> |
| 23 |
>>> Is there anything in the sddm-logs? |
| 24 |
>>> Mine, for some reason, writes to /var/log/sddm.log |
| 25 |
>>> |
| 26 |
>>> Do you have anything special in your Xsession files and/or profiles |
| 27 |
>> (incl. |
| 28 |
>>> bash_profile and bashrc) that is non-default? |
| 29 |
>>> |
| 30 |
>>> Which login-theme do you use? |
| 31 |
>>> |
| 32 |
>>> -- |
| 33 |
>>> Joost |
| 34 |
>> Well, I didn't know I could kill that thing. I been logging out and |
| 35 |
>> back in which annoys the stuffing out of me. I have to close three |
| 36 |
>> browsers, several file managers plus whatever else I am doing before I |
| 37 |
>> can logout. Then I have to reopen all that when I log back in. On top |
| 38 |
>> of that, I have to wait for a download to stop as well. Yea, it's |
| 39 |
>> annoying, putting it mildly. lol I thought if I killed it, it would |
| 40 |
>> take the whole GUI thingy with it . Since it is still chewing away, |
| 41 |
>> makes me think about the Pacman days, I'll kill that thing in a few |
| 42 |
>> minutes, after closing important stuff first just in case. |
| 43 |
>> |
| 44 |
>> I got the last several lines of sddm.log. Here it is complete with a |
| 45 |
>> WW |
| 46 |
>> in there, about three lines from the bottom. |
| 47 |
>> |
| 48 |
>> |
| 49 |
>> [01:32:50.474] (II) DAEMON: Greeter session started successfully |
| 50 |
>> [01:32:50.499] (II) DAEMON: Message received from greeter: Connect |
| 51 |
>> [01:32:57.872] (II) DAEMON: Message received from greeter: Login |
| 52 |
>> [01:32:57.872] (II) DAEMON: Reading from |
| 53 |
>> "/usr/share/xsessions/plasma.desktop" |
| 54 |
>> [01:32:57.872] (II) DAEMON: Reading from |
| 55 |
>> "/usr/share/xsessions/plasma.desktop" |
| 56 |
>> [01:32:57.872] (II) DAEMON: Session |
| 57 |
>> "/usr/share/xsessions/plasma.desktop" selected, command: |
| 58 |
>> "/usr/bin/startplasma-x11" |
| 59 |
>> [01:32:57.948] (II) HELPER: [PAM] Starting... |
| 60 |
>> [01:32:57.948] (II) HELPER: [PAM] Authenticating... |
| 61 |
>> [01:32:57.991] (II) HELPER: [PAM] Preparing to converse... |
| 62 |
>> [01:32:57.991] (II) HELPER: [PAM] Conversation with 1 messages |
| 63 |
>> [01:32:57.997] (II) HELPER: [PAM] returning. |
| 64 |
>> [01:32:58.016] (II) DAEMON: Authenticated successfully |
| 65 |
>> [01:32:58.152] (II) HELPER: [PAM] Closing session |
| 66 |
>> [01:32:58.153] (II) HELPER: [PAM] Ended. |
| 67 |
>> [01:32:58.153] (II) DAEMON: Auth: sddm-helper exited successfully |
| 68 |
>> [01:32:58.153] (II) DAEMON: Greeter stopped. |
| 69 |
>> [01:32:58.225] (II) HELPER: Starting: "/usr/share/sddm/scripts/Xsession |
| 70 |
>> \"/usr/bin/startplasma-x11\"" |
| 71 |
>> [01:32:58.225] (WW) HELPER: Could not open stderr to |
| 72 |
>> "/home/dale/.local/share/sddm/xorg-session.log" |
| 73 |
>> [01:32:58.225] (II) HELPER: Adding cookie to "/home/dale/.Xauthority" |
| 74 |
>> [01:32:58.245] (II) DAEMON: Session started |
| 75 |
>> root@fireball / # |
| 76 |
>> |
| 77 |
>> |
| 78 |
>> |
| 79 |
>> So off I go to check into that file. I get this and change permissions |
| 80 |
>> for the second ls. |
| 81 |
>> |
| 82 |
>> |
| 83 |
>> root@fireball / # tail /home/dale/.local/share/sddm/xorg-session.log |
| 84 |
>> root@fireball / # ls -al /home/dale/.local/share/sddm/xorg-session.log |
| 85 |
>> -rw------- 1 root root 0 Mar 4 2019 |
| 86 |
>> /home/dale/.local/share/sddm/xorg-session.log |
| 87 |
>> root@fireball / # ls -al /home/dale/.local/share/sddm/xorg-session.log |
| 88 |
>> -rw------- 1 dale users 0 Mar 4 2019 |
| 89 |
>> /home/dale/.local/share/sddm/xorg-session.log |
| 90 |
>> root@fireball / # |
| 91 |
>> |
| 92 |
>> |
| 93 |
>> As you can see, the first time it was owned by root, and is empty, |
| 94 |
>> which |
| 95 |
>> I bet requires it to be dale:user so I changed it. I bet it is |
| 96 |
>> building |
| 97 |
>> a log and keeping it in memory because it can't access the file to |
| 98 |
>> write |
| 99 |
>> it. I'm going to logout and see what it does. I'll finish when I get |
| 100 |
>> back. :-D |
| 101 |
>> |
| 102 |
>> OK. Logged back in and now I get this in the sddm.log. |
| 103 |
>> |
| 104 |
>> |
| 105 |
>> [10:45:28.213] (II) HELPER: [PAM] Starting... |
| 106 |
>> [10:45:28.213] (II) HELPER: [PAM] Authenticating... |
| 107 |
>> [10:45:28.253] (II) HELPER: [PAM] Preparing to converse... |
| 108 |
>> [10:45:28.253] (II) HELPER: [PAM] Conversation with 1 messages |
| 109 |
>> [10:45:28.259] (II) HELPER: [PAM] returning. |
| 110 |
>> [10:45:28.287] (II) DAEMON: Authenticated successfully |
| 111 |
>> [10:45:28.391] (II) HELPER: Starting: "/usr/share/sddm/scripts/Xsession |
| 112 |
>> \"/usr/bin/startplasma-x11\"" |
| 113 |
>> [10:45:28.393] (II) HELPER: Adding cookie to "/home/dale/.Xauthority" |
| 114 |
>> [10:45:28.400] (II) DAEMON: Session started |
| 115 |
>> [10:45:28.416] (II) HELPER: [PAM] Closing session |
| 116 |
>> [10:45:28.417] (II) HELPER: [PAM] Ended. |
| 117 |
>> [10:45:28.418] (II) DAEMON: Auth: sddm-helper exited successfully |
| 118 |
>> [10:45:28.418] (II) DAEMON: Greeter stopped. |
| 119 |
>> root@fireball / # |
| 120 |
>> |
| 121 |
>> |
| 122 |
>> I don't see any WW lines there. If I scroll up I can see the original |
| 123 |
>> I |
| 124 |
>> posted above but no WW since. Can we all say a prayer now???? |
| 125 |
>> |
| 126 |
>> I bet when I switched to sddm, it didn't change the permissions like it |
| 127 |
>> should and that threw a wrench in the gears. I'll know for sure in a |
| 128 |
>> few hours. It chewed through memory real fast after the last login. |
| 129 |
>> Within just a very few hours, it was over 4GBs. It seems to stop |
| 130 |
>> itself |
| 131 |
>> around that number tho. I'm not sure what to think about that tho. |
| 132 |
>> |
| 133 |
>> I'll post back in a bit. Give it time to eat some Pacman dots. I |
| 134 |
>> think |
| 135 |
>> you got it tho. I really hope that was it. |
| 136 |
>> |
| 137 |
>> Dale |
| 138 |
>> |
| 139 |
>> :-) :-) |
| 140 |
>> |
| 141 |
>> P. S. Made eye Doctor appt today. Maybe this old goat will see better |
| 142 |
>> in a couple months when new glasses come in. O_O |
| 143 |
> Really quick as on mobile. |
| 144 |
> Killing "sddm-helper" doesn't kill my session when I do it. |
| 145 |
> So you might not need to log off either. |
| 146 |
> Just switch to root and hit it with kill -9 if it misbehaves |
| 147 |
|
| 148 |
|
| 149 |
Next time, that's the plan. So far tho, it is working fine. This is |
| 150 |
what ps shows: |
| 151 |
|
| 152 |
root 23338 0.0 0.0 54528 14400 |
| 153 |
|
| 154 |
It hasn't changed since I logged in. It's hasn't increased even one |
| 155 |
byte. Usually by now it would be up to a few 100MBs or so. |
| 156 |
|
| 157 |
Dale |
| 158 |
|
| 159 |
:-) :-) |
Archives