Sync Update for Week 38, 2023

bubba66 Yeah, that working was a side effect of me modifying signon-ui to use qt5-webengine instead of qt5-webkit. Honestly I didn't even realize it didn't work before but I'm glad it's working now. Thanks for noticing that it's been fixed!

elfprince yeah, looks very busy but in HTOP navigating the bottom menu to search for the process to kill then navigating that bottom menu again for the right F-Command then putting your eyes back to the jumpy middle output to see what text got highlighted then looking down again to see the F command hasn't timed out...HTOP makes killing processes un-necessarilty cumbersome.

@WetGeek have you tried killing a process in btop? easy peasy?

brent have you tried killing a process in btop? easy peasy?

I haven't needed to do that so far, but I'm sure it will be WAY easier than in htop. The only way I could do it in htop was to try to spot and memorize the process ID, and then go to the terminal to issue a kill command. I never even tried to do it in htop with everything boucing around. Sometimes it wasn't even easy to find the process to kill.

That's why I said it was love at first sight when I saw btop.

brent yea, same experience with killing processes in htop

There should be a more efficient way to do it I guess, never had time to explore it more

Solarmass you are right. if I could find a frozen process with the terminal and learn how to kill it in the terminal (I still don't know the diff betweenkill andkillall)--in what @WetGeek up there described as a 2-part/2-app process and make it a one-part process in terminal--- then I could use htop for better things. I've used this program for many years, still like it, but kill-a-process is a pita in it..no worries, apps don't freeze that often.

Usually I use System Monitor, then Process to kill a frozen application (this happens to me sometimes with Firefox).
I just did a test with btop by selecting Firefox, then typing k to kill the application, which happened indeed after validating the confirmation. When I restarted Firefox, the application window displayed the tabs already open before launching the command.
Interesting.

brent I haven't used btop and do not have a need at this time, since I used others quite happily, I might add. In glances the processes jump every 5 seconds or so, so it is not bad. I am certain that you can set the 'jump interval', if you check the man pages for glances, htop and perhaps even btop. Just makes sense. I also use ps aux where things stay still, like a snapshot of the system. Then, if I am looking for a certain item, I do grep the output.

brent Yes, that happens sometimes with other posters as well. I just highlight with my mouse.

elfprince It's bizarre. I'm at work now and I can see my output in blue ^ just fine more or less. And home it's just a bunch of dark blue unreadable mud that cannot be rescued by highlighting the text with a mouse.
....looks like someone needs a new big screen monitor.

elfprince that occurred to me but I thought it was a longshot--but a few weeks ago I started using budgie nightlight as an all day thing...great tip. that's probably it.

brent I use 'night' mode all the time as well. Sometimes though, I need to switch when reading a particularly 'dark' web page.

There is a problem with Cisco Secure Client VPN AnyConnect. I must go back in eopkg history before such upgrade. I think it could be a problem with the new openssl. I'm currently using ciscos anyconnect in version 5.0.02075.
After go back in history, the vpn client works as expected.

It's not the whole upgrade, the problem occurs if I upgrade glibc & libcrypt only. By eopkg upgrade libgcrypt --ignore-safety.
After this "micro" upgrade Ciscos vpn doesn't work as expected any longer.
A eopkg history -t 577 restores the old status and Ciscos vpn works as expected.
JM2C