On Thu, Mar 22, 2018 at 8:44 AM, Milan Crha <mcrha@xxxxxxxxxx> wrote:
On Thu, 2018-03-22 at 04:40 +0000, Peter Robinson wrote:
> ... to improve performance on low resource devices ...
Hi,
I only recently, like three weeks ago, had been asked to update Fedora
on a very old Dell notebook. I installed there Fedora 20 years ago and
when I've been asked to get there a newer Firefox, because that ancient
doesn't work for sites like Facebook (do not ask, it's not my machine),
then I decided to update to the recent Fedora 27. Then the user gets
all the security fixes and so on, right? Everyone wins. After
successful 'distro-sync', which was quite impressive on its own, the
gdm didn't boot quicker than in like 5 minutes, when I was lucky.
Booting to GNOME took even longer. The rescue mode booted quicker, but
that's not the production. There were caught some ABRT reports about
kernel crash, but it was just about: "hey, kernel crashed, but you've
bad luck, because from this crash kernel developers won't get anything,
thus I'll not let you report it". What are such ABRT reports good for?
Well, what do you suggest? Not to inform user at all?
ABRT tries to recognize if the report has some useful information, that would help to resolve this issue.
Users are happy to click on button and create bugzillas like "I don't know what happened and have no idea how to reproduce". If the data itself do not have any info, then it is just noise for maintainers.
We, of course, could not inform users at all about some problems, but on the other hand - you would boot and computer would act strangely and you would have no idea if it is kernel/gnome/systemd/... problem. Now you knew that there is something wrong with kernel and you have a good starting point for you later investigation. (Or still, if you are experienced enough you can take closer look into the problem details)
The ancient Fedora 20 didn't have this issue, it just worked. Long
story short, I spent half night and quite few hours the next day trying
fresh install of Fedora 27, 26, 25, but none worked that well as Fedora
20, thus I resulted in getting the ancient Fedora 20 from the archives,
install it and bring Firefox straight from Mozilla. The task
accomplished, but...
Maybe there's some regression there, kernel should not crash, but I do
not have that machine anymore, I've it only borrowed to get there new-
enough browser and then I returned it back. It's not helpful for the
community, I know, but it's the user experience I've got with one low
resource device (I'm pretty sure it had the CPU and HDD higher than the
minimum, the RAM at least 1GB too, but I'm not sure right now; did
Fedora 20 have the same requirements? It works there reasonably
well...).
Maybe you can compare such ancient Fedora, like the Fedora 20, with the
current Fedora on those low resource devices to see (and feel) the
difference. With classic "rotated disks", not SSD, that might be
important too.
Bye,
Milan
_______________________________________________
desktop mailing list -- desktop@xxxxxxxxxxxxxxxxxxxxxxg
To unsubscribe send an email to desktop-leave@lists.fedoraproject.org
--
_______________________________________________ desktop mailing list -- desktop@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to desktop-leave@xxxxxxxxxxxxxxxxxxxxxxx
