Bug 434033 - Download of KNewStuff files fails for zip files
Summary: Download of KNewStuff files fails for zip files
Status: RESOLVED NOT A BUG
Alias: None
Product: frameworks-knewstuff
Classification: Frameworks and Libraries
Component: general (show other bugs)
Version: 5.79.0
Platform: Microsoft Windows Microsoft Windows
: NOR major
Target Milestone: ---
Assignee: Alexander Lohnau
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-03-06 00:06 UTC by Jasem Mutlaq
Modified: 2021-03-06 19:27 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jasem Mutlaq 2021-03-06 00:06:46 UTC
SUMMARY

We are receiving many reports in KStars that catalog addons cannot be installed under Windows 10. The same catalogs are installed fine on KStars Linux & MacOS versions.

This is the error:

 [2021-03-05T16:53:12.308 Arab Standard Time WARN ][ default] - QMimeDatabase: Error loading internal MIME data
An error has been encountered at line 1 of <internal MIME data>: Premature end of document.:
[2021-03-05T16:53:12.308 Arab Standard Time CRIT ][ kf.newstuff.core] - Could not determine type of archive file ' "C:/Users/mutla/AppData/Local/Temp/asBMsq-abell_pn_1.0.zip" '

When checking the zip file above, it's a valid ZIP file and I can open it just fine.

STEPS TO REPRODUCE
1. Open KStars on Windows 10
2. Go to Data --> Download New Data
3. Try to download any catalog and it would say "File not found" error.

OBSERVED RESULT

Catalog downloaded but not installed.

EXPECTED RESULT

Catalog downloaded and installed.

SOFTWARE/OS VERSIONS

KStars built using KDE Binary Factory, so whatever used by KDE Binary Factory as of March 1st, 2021.

Windows: 10
macOS: 
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version:

ADDITIONAL INFORMATION
Comment 1 Jasem Mutlaq 2021-03-06 10:21:54 UTC
Could this be related to QMimeDatabase error? We're getting tons of reports on this so it would be great if we can work on resolving the underlying issue.
Comment 2 Jasem Mutlaq 2021-03-06 19:27:38 UTC
Turns out it was a mime blacklisting issue.