Bug 1272042

Summary: Odd error message when finished
Product: [Fedora] Fedora Reporter: Dave P <dave.pawson>
Component: kdelibs4Assignee: Orphan Owner <extras-orphan>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 22CC: extras-orphan, jsilhan, ltinkl, mluscon, packaging-team-maint, pnemade, rdieter, smparrish, than, vmukhame
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-07-19 18:13:36 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Dave P 2015-10-15 10:44:20 UTC
Description of problem:Ran an update, dnf -y update


Version-Release number of selected component (if applicable):


How reproducible: Not, as yet


Steps to Reproduce:
1. run update
2. check terminal error message
3.

Actual results:

# kbuildsycoca4 running...
kbuildsycoca4(24842) VFolderMenu::loadDoc: Parse error in  "/home/dpawson/.config/menus/applications-merged/xdg-desktop-menu-dummy.menu" , line  1 , col  1 :  "unexpected end of file" 

Expected results:

No error message


Additional info:

Other reports indicate this is 'info'. It has not been seen on Fedora by me previously

Comment 1 Fedora End Of Life 2016-07-19 18:13:36 UTC
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.