<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
<!DOCTYPE bugzilla SYSTEM "https://bugs.kde.org/page.cgi?id=bugzilla.dtd">

<bugzilla version="5.0.6"
          urlbase="https://bugs.kde.org/"
          
          maintainer="sysadmin@kde.org"
>

    <bug>
          <bug_id>396991</bug_id>
          
          <creation_ts>2018-07-30 19:19:01 +0000</creation_ts>
          <short_desc>History feature</short_desc>
          <delta_ts>2026-01-28 20:52:40 +0000</delta_ts>
          <reporter_accessible>1</reporter_accessible>
          <cclist_accessible>1</cclist_accessible>
          <classification_id>2</classification_id>
          <classification>Applications</classification>
          <product>Discover</product>
          <component>Updates</component>
          <version>5.13.3</version>
          <rep_platform>Other</rep_platform>
          <op_sys>Linux</op_sys>
          <bug_status>CONFIRMED</bug_status>
          <resolution></resolution>
          
          
          <bug_file_loc></bug_file_loc>
          <status_whiteboard></status_whiteboard>
          <keywords></keywords>
          <priority>NOR</priority>
          <bug_severity>wishlist</bug_severity>
          <target_milestone>---</target_milestone>
          
          
          <everconfirmed>1</everconfirmed>
          <reporter name="Nate Graham">nate</reporter>
          <assigned_to name="Aleix Pol">aleixpol</assigned_to>
          <cc>bugseforuns</cc>
    
    <cc>elrefaei.omar</cc>
    
    <cc>john.kde</cc>
    
    <cc>yvan</cc>
          
          <cf_commitlink></cf_commitlink>
          <cf_versionfixedin></cf_versionfixedin>
          <cf_sentryurl></cf_sentryurl>
          <votes>0</votes>

      

      

      

          <comment_sort_order>oldest_to_newest</comment_sort_order>  
          <long_desc isprivate="0" >
    <commentid>1769489</commentid>
    <comment_count>0</comment_count>
    <who name="Nate Graham">nate</who>
    <bug_when>2018-07-30 19:19:01 +0000</bug_when>
    <thetext>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.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>1769550</commentid>
    <comment_count>1</comment_count>
    <who name="Aleix Pol">aleixpol</who>
    <bug_when>2018-07-31 01:50:20 +0000</bug_when>
    <thetext>Maybe, I guess you&apos;re specifically talking about packagekit or any? Because the strategies that every system suggests to recover from an issue is different: snap it&apos;s channels, flatpak it&apos;s sources and internal versioning, distros it largely depends, on opensuse they have a cool stuff going on with btrfs.

I&apos;m afraid that the history would only be useful for reporting, but nothing one could do there.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>1769641</commentid>
    <comment_count>2</comment_count>
    <who name="Nate Graham">nate</who>
    <bug_when>2018-07-31 13:46:57 +0000</bug_when>
    <thetext>That&apos;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.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>1793508</commentid>
    <comment_count>3</comment_count>
    <who name="Aleix Pol">aleixpol</who>
    <bug_when>2018-10-11 17:06:18 +0000</bug_when>
    <thetext>Muon has the history feature ad-hoc for apt. I&apos;d say people can just use that if they need to interact with history.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>1793514</commentid>
    <comment_count>4</comment_count>
    <who name="Nate Graham">nate</who>
    <bug_when>2018-10-11 17:45:24 +0000</bug_when>
    <thetext>But I don&apos;t want to use Muon...</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>1823341</commentid>
    <comment_count>5</comment_count>
    <who name="Omar">elrefaei.omar</who>
    <bug_when>2018-11-30 10:05:48 +0000</bug_when>
    <thetext>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 &amp; snaps

&lt;toMySelf&gt;
MAN THIS FRAGMENTATION IS FRUSTRATING
&lt;/toMySelf&gt;

On a serious note: this is not the first time I see different packaging/distribution mechanism holding back feature development</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>2489470</commentid>
    <comment_count>6</comment_count>
    <who name="John Veness">john.kde</who>
    <bug_when>2026-01-28 20:52:40 +0000</bug_when>
    <thetext>A user story giving additional confirmation of this issue (if that is needed):

I just now clicked Update All while I had an openSUSE Tumbleweed system upgrade pending (which I think uses the PackageKit backend) with 150-something updates in it. I realised I had not yet done what I normally like to do, which is to view the list of updates first (by clicking on the More Information button). Annoyingly, the More Information button had been greyed out after I had clicked Update All (which is BUG 431719), and the Cancel button seemed to have no effect (possibly BUG 457205 although that&apos;s about Flatpak). So I could only wait for the update to finish. Now I cannot retrospectively see in Discover what the 150 updates were, which is annoying, as that is exactly the place I would think to look.</thetext>
  </long_desc>
      
      

    </bug>

</bugzilla>