Bug 396991 - History feature
Summary: History feature
Status: REPORTED
Alias: None
Product: Discover
Classification: Applications
Component: Updates (interactive) (show other bugs)
Version: 5.13.3
Platform: Other Linux
: NOR wishlist
Target Milestone: ---
Assignee: Aleix Pol
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-07-30 19:19 UTC by Nate Graham
Modified: 2024-07-09 11:48 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Nate Graham 2018-07-30 19:19:01 UTC
It would be nice if Discover could display the update history, with each individual update transaction shown separately, and the list of all update transactions sorted by date.

This is especially useful for the case where something regressed on your computer after the last update and you want to see what got updated for troubleshooting purposes.
Comment 1 Aleix Pol 2018-07-31 01:50:20 UTC
Maybe, I guess you're specifically talking about packagekit or any? Because the strategies that every system suggests to recover from an issue is different: snap it's channels, flatpak it's sources and internal versioning, distros it largely depends, on opensuse they have a cool stuff going on with btrfs.

I'm afraid that the history would only be useful for reporting, but nothing one could do there.
Comment 2 Nate Graham 2018-07-31 13:46:57 UTC
That's currently true, but un-actionable information can still be useful--not only for troubleshooting, but also just making the user feel more informed and in control.

Also, an Update History page would support and be a prerequisite for the potential future features of error recovery and/or package/app version rollbacks.
Comment 3 Aleix Pol 2018-10-11 17:06:18 UTC
Muon has the history feature ad-hoc for apt. I'd say people can just use that if they need to interact with history.
Comment 4 Nate Graham 2018-10-11 17:45:24 UTC
But I don't want to use Muon...
Comment 5 Omar 2018-11-30 10:05:48 UTC
If we are trying to streamline workflow:
1) Moun is a bit a more than the average user would be comfortable with.
2) This does not solve it for flatpaks & snaps

<toMySelf>
MAN THIS FRAGMENTATION IS FRUSTRATING
</toMySelf>

On a serious note: this is not the first time I see different packaging/distribution mechanism holding back feature development