Yes, After 20.04 release I will agitate people to switch to Ubuntu. If
anyone fan of dead Windows 7 or Ubuntu Unity (until 17.10 release) want to
find a great alternative, he should take attention to our new stable smooth
and fast Ubuntu.
пн, 2 сент. 2019 г. в 05:15, Daniel van Vugt :
> Thanks.
Thanks.
It looks to be very CPU-busy, mostly in the gnome-shell process. We are
working to reduce the CPU load and increase the performance of gnome-
shell but it will take some time. You will see a definite improvement in
19.10 and I hope another big improvement next year in 20.04.
** Summary
I have done. Take it, please!
пт, 30 авг. 2019 г. в 12:01, Daniel van Vugt :
> Please repeat the steps in comment #11 again and try step 3 immediately
> after step 2 without delay.
>
> Then if that's inconclusive I'll have to find a similar machine some
> time in future and experiment for
Please repeat the steps in comment #11 again and try step 3 immediately
after step 2 without delay.
Then if that's inconclusive I'll have to find a similar machine some
time in future and experiment for myself.
** Changed in: gnome-shell (Ubuntu)
Status: Incomplete => New
--
You
Please, take it.
пт, 30 авг. 2019 г. в 11:00, Daniel van Vugt :
> OK, disk speed should not be a problem. It now sounds like the machine
> might be CPU-bound somehow. If you can then please:
>
> 1. Open a Terminal window and run:
>
>top -d30
>
> 2. Launch programs and reproduce the bug.
>
>
OK, disk speed should not be a problem. It now sounds like the machine
might be CPU-bound somehow. If you can then please:
1. Open a Terminal window and run:
top -d30
2. Launch programs and reproduce the bug.
3. Within 30 seconds switch to the Terminal window and see what's using
the most
ubuntenok@ubuntenok-HP-250-G6-Notebook-PC:~$ lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
loop07:00 149,9M 1 loop /snap/gnome-3-28-1804/71
loop17:10 42,8M 1 loop /snap/gtk-common-themes/1313
loop27:20 4M 1 loop /snap/gnome-calculator/406
loop37:30
Thanks. That doesn't seem to show any single recurring problem though.
So it looks like log file flushing is not the explanation for this bug.
I wonder if disk performance is a factor. Can you please run:
lsblk
and
sudo hdparm -I /dev/sda
and send the output?
--
You received this bug
