I noticed an issue running chrome-unstable where download status wasn't
This also applied to chrome-beta.
It worked for chrome-stable and chromium.
I initially thought it had to do with the version of chrome - i.e. there
was some type of regression.
Now it appears that when the version of chrome-unstable moved into stable
the issue was resolved. The version in stable had the exact same number as
that which didn't work in unstable, which leads to to believe that instead
of there being an issue on the chrome side, instead this is an issue on the
kde side where something is coded in such a way that it is looking for a
"stable" designation for chrome in order to function.
That just seems a bit wacky to me, like why would anyone do that... but
that is how it appears.
I was wondering if anyone else has noticed this issue and is seeing the
same results? If so, I would consider this a kde bug rather than chrome.
At least twice this week when I woke up my system from sleep instead of lock screen I am presented with black screen and cursor. There is no way for me to get back to working system except go to tty and restart sddm or reboot system. Htop doesn't seem to show any obvious culprit. This is highly undesirable as I keep losing my unsaved work.
It seems like recent apps has stopped populating itself in AppDash starting
with 5.6 update. I also noticed my recent apps history was wiped out on
update. User history should never be deleted without a users permission.