Bug 1329999 - As-WARNING **: failed to rescan: Failed to parse [path] file: cannot process file of type text/plain
Summary: As-WARNING **: failed to rescan: Failed to parse [path] file: cannot process ...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-software
Version: 24
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Richard Hughes
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-04-25 09:10 UTC by Christian Stadelmann
Modified: 2016-05-25 13:34 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-05-25 13:34:18 UTC
Type: Bug


Attachments (Terms of Use)

Description Christian Stadelmann 2016-04-25 09:10:37 UTC
Version-Release number of selected component (if applicable):
gnome-software-3.20.1-1.fc24.x86_64
on Fedora 23

How reproducible:
on different F23 and F24 systems

Steps to Reproduce:
1. run gnome-software 
2. have a look at your logs

Actual results:
Hundreds of warnings. Have a look at [1] for more details. Some examples:

Apr 24 14:15:01 fedie gnome-software-service.desktop[2385]: (org.gnome.Software:2385): As-WARNING **: failed to rescan: No valid root node specified
Apr 24 14:15:01 fedie gnome-software-service.desktop[2385]: (org.gnome.Software:2385): As-WARNING **: failed to rescan: Failed to parse /usr/share/applications/transmission-gtk.desktop;571c4844 file: cannot process file of type text/plain

Expected results:
No warnings for files that are not wrong

Additional info:
See https://ask.fedoraproject.org/en/question/86941/many-packages-do-not-appear-in-the-software-app-is-there-a-way-to-fix-this/

[1] https://gist.githubusercontent.com/anonymous/d49ee8ed980995f58e2f2128cf925649/raw/5e1629294b04b5ac0f61ed7a242420b259d50ada/log

Comment 1 Richard Hughes 2016-05-25 13:34:18 UTC
I'm pretty sure F24 is a lot less shouty for random files, please re-open if it still happens with a new build.


Note You need to log in before you can comment on or make changes to this bug.