Red Hat Bugzilla – Bug 491123
(xfce4-appfinder:22504): Gtk-WARNING **: Failed to set text from markup due to error parsing markup
Last modified: 2013-03-07 21:05:38 EST
Description of problem: Start Appfinder, works OK, but produces this to std{err,out}: (xfce4-appfinder:22504): Gtk-WARNING **: Failed to set text from markup due to error parsing markup: Error on line 1: Character ' ' is not valid at the start of an entity name; the & character begins an entity; if this ampersand isn't supposed to be an entity, escape it as & Version-Release number of selected component (if applicable): xfce4-appfinder-4.6.0-1.fc11.x86_64 How reproducible: always
I think this is due to desktop files that are not following the spec, but I am not sure how to locate which one in particular is at fault. Can you look for something with a leading space in your /usr/share/applications/*.desktop files or any in your home dir?
Created attachment 336097 [details] Problems making desktop file When I remove this file, there are no warnings. Dunno if there's any problem in that file, please investigate.
Yeah, the "Date & Time" there should be likely "Date & Time" to comply. Perhaps we should reassign this to the system-config-date package? Of course it might be good to look at all the desktop files for more issues...
(In reply to comment #3) > Yeah, the "Date & Time" there should be likely "Date & Time" to comply. Good catch! > Perhaps we should reassign this to the system-config-date package? I guess so... > Of course it might be good to look at all the desktop files for more issues... I checked what I have installed, the rest passed.
According to the desktop file spec[1], the "Name" entry is a localestring and its encoding is plain UTF-8, so my take is that it's the responsibility of the application reading the desktop file to transcode this to proper markup before letting gtk at it. [1]: http://standards.freedesktop.org/desktop-entry-spec/latest/ar01s03.html
NB: Jonathan Blandford told me this on IRC: <jrb> use g_markup_escape_text() if you're trying to display it in g_markup, and the & is messing things up
Filed bug http://bugzilla.xfce.org/show_bug.cgi?id=5141 upstream.
This bug appears to have been reported against 'rawhide' during the Fedora 11 development cycle. Changing version to '11'. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
This message is a reminder that Fedora 11 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 11. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '11'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 11's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 11 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Fedora 11 changed to end-of-life (EOL) status on 2010-06-25. Fedora 11 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. Thank you for reporting this bug and we are sorry it could not be fixed.