View Issue Details
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0005469||SUMo||Bug||public||2019-05-07 18:53||2021-02-05 08:00|
|Summary||0005469: SUMo reporting PortableApps.com components twice instead of once|
|Description||I have SUMo Pro installed as well as PortableApps.com with several components including SUMo Portable. I've added the installation location of PortableApps.com to the folders for scanning by SUMo Pro and have run it in order to include these findings in the resulting report. There seems to be a fundamental bug in installed SUMo for such a configuration. It reports all components of the local PortableApps.com installation TWICE and those installed additionally outside that platform another time. One of the two report entries has the suffix Portable and PortableApps.com as publisher, the other one is without that suffix and with the original component publisher as publisher although with an installation path below the PortablesApps.com installation root. And in case that such a component is also installed outside in classical manner, this tool is reported a third time with the standard installation path. This happens not only for SUMo but also for some other tools on my device.|
I didn't read details for developers on how to integrate a software into the PortableApps.com platform. So it's an unverified assumptions that they do some similar adaption in the manner of a side-by-side installation resulting in various folders for the component to integrate including the unmodified original component. Because of this need of adaption around the original tool, it takes quiet some time before a tool released by the original tool publisher gets updated into PortableApps.com framework. In this mean time the original component gets reported as out of date with available update although it is not yet released by PortableApps.com for every such component!
So as long as hierarchical SUMo reports are not yet implemented, please suppress this 2nd reporting of the component with original signature keeping just the one with PortableApps.com signature, and hence preventing this kind of generic false and undue update notifications.
|Tags||No tags attached.|
||Screenshot please (+logs in debug mode if possible)|
Do you really need the complete log file?
That's not possible as even with another Windows standard default text editor, the limit of 10000 lines remains. As a work around I saved the log file three times, the first one almost 7000 lines long while the other two are each 10000 lines long. The size varies a little bit below or above 1 MByte for the latter and more than half of that for the first. So this is not supported by your MantisBT configuration. I only may send them Email if your Mail server supports it. The first log file is for SUMo startup just with debug added to my previous configuration. The 2nd log file is for scanning and the 3rd one for checking.
For the screenshots, I selected SUMo Portable with its component SUMo and SumatraPDF Portable with its component SumatraPDF as well as the SUMo report of the installed SUMo Pro version 184.108.40.2060. I'll see if I may send an extract of the debug log for scanning. (This log, not the extract, is larger than 1 MB.) Or do you need an extract of the debug log for checking?
||Is the problem only for SUMo or even other PortableApps products ?|
As reported, the issue is generic. It concerns SUMo's handling of ALL tools within the PortableApps framework. The screenshots show it for SUMo Portable, SumatraPDF and partially for Startup Sentinel. The debugging logs send by email should show it for all tools installed within the PortableApps framework.
I repeat my reminder that although this issue might be easier and quicker to fix, the related issue needs to be fixed before as otherwise the fix of the related issue can no longer be tested.
||I can't reproduce with latest release.... would you please confirm it's still applicable to 5.12.4 or later ?|
|2019-05-07 18:53||wolf||New Issue|
|2019-05-07 19:18||wolf||Issue cloned: 0005470|
|2019-05-07 19:18||wolf||Relationship added||related to 0005470|
|2019-05-07 22:26||Kyle_Katarn||Assigned To||=> Kyle_Katarn|
|2019-05-07 22:26||Kyle_Katarn||Status||new => feedback|
|2019-05-07 22:26||Kyle_Katarn||Note Added: 0003260|
|2019-05-09 11:37||wolf||File Added: sumo.portable.20190809.png|
|2019-05-09 11:37||wolf||File Added: paf.sumo.port.20190509.png|
|2019-05-09 11:37||wolf||File Added: paf.sumo.20190509.png|
|2019-05-09 11:37||wolf||File Added: paf.sumatra.port.20190509.png|
|2019-05-09 11:37||wolf||File Added: paf.sumatra.20190509.png|
|2019-05-09 11:37||wolf||Note Added: 0003265|
|2019-05-09 21:08||Kyle_Katarn||Note Added: 0003266|
|2019-05-09 21:09||Kyle_Katarn||Target Version||=> 5.12.x|
|2019-05-09 21:09||Kyle_Katarn||Status||feedback => acknowledged|
|2019-05-09 22:33||wolf||Note Added: 0003268|
|2019-05-10 21:49||Kyle_Katarn||Note Added: 0003269|
|2019-11-11 21:00||Kyle_Katarn||Target Version||5.12.x => 5.10.4|
|2019-12-08 17:22||Kyle_Katarn||Target Version||5.10.4 => 5.10.5|
|2019-12-21 14:15||Kyle_Katarn||Target Version||5.10.5 => 5.10.6|
|2019-12-30 15:19||Kyle_Katarn||Target Version||5.10.6 => 5.10.7|
|2020-01-05 12:25||Kyle_Katarn||Target Version||5.10.7 => 5.10.8|
|2020-01-26 18:46||Kyle_Katarn||Target Version||5.10.8 => 5.10.9|
|2020-02-23 15:51||Kyle_Katarn||Target Version||5.10.9 => 5.12.x|
|2021-02-05 08:00||Kyle_Katarn||Note Added: 0004158|