System and Network configuration • is it a bug.. or a feature.. it is a problem either way. :-/

Try some journalctl. If your user has problems using it, adding yourself to group 'adm' I think still does the trick.

Code:

$ journalctl -b 0 --no-pager -g "something good" -n 10 

substitute something good with a search term for its last 10 log entries.
'error' 'polkit' 'sleep' 'runaway' etc.

Are there any user created polkit rules?

Thanks for the terminal command, but it is to hard to read in terminal and i dont know what to search for. When i read my logs in the old log files i open the file and scroll to the time i know i had an issue and then start reading before and after.
I would like a GUI with flags for information, warnings and errors so it is easy to scroll thru 1000nd of entry's to find a problem... yeah i know I'm spoiled by windows.

as far as i know.. i dont have any user polkit rules.. i have not created any rules on this computer.. the only rules in this one is debian default and that installed program might have made.. This laptop is only for basic usage.. email forums and reading news and i use my network to sorting old data files i have on other computers in my network and on my server.. when the samba network like/feel for working.


I think it is better to create a workaround then finding the problem.. It cant be the polkit rules as then it should happen on every wake up..
So i think how to add that polkit.service restart every time it wakes up from hibernation?? .. is the solution for time being and then some bug hunters can look in to it.
I think that is the fastest solution for me as restarting that service kills all zombies.... even if it dont happen every time the computer wakes up.. it dont hurt to restart the service every time..
I have never created a function to restart services after the system have woken up... i have not even don that in windows
Du you know how to do that?
I looked in to the polkit.service file, and it hasi saw in another file that had
Restart=on-failure
but the polkitd never becomes a zombie, so i guessing polkit.service dont fail fail but ends up in some half not responding state.
hmmm.. i might try to add Restart=on-failure.. and then restart the service and see if it keeps on restarting to prevent next pkla-check-auth zombie on next upcoming hibernation wake ups


as for the network feel for working... as i discovered in 2018.. samba win/linux networking sucks and it still does 6years later ... it is like walking in a minefield.. working... working.... working... KABOOM it stops working without any reason... sometime it works for a day.. some time a week before it crashes.. and if you leave it be it start working on it's own withing a few weeks or when you have rebooted the linux computer a few times.. some time it works by restarting smb service and shut down the file-manager then killall gvfsd.. and if you lucky it start working again.. if you lucky.. that only work 2 out of 10times.

Statistics: Posted by Marie SWE — 2024-01-08 04:15 — Replies 4 — Views 94

---