Bug 451624 - Lines are changing its description in g-s-properties
Lines are changing its description in g-s-properties
Status: CLOSED RAWHIDE
Product: Fedora
Classification: Fedora
Component: gnome-session (Show other bugs)
rawhide
All Linux
low Severity low
: ---
: ---
Assigned To: Ray Strode [halfline]
Fedora Extras Quality Assurance
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2008-06-16 05:30 EDT by Zdenek Kabelac
Modified: 2008-07-08 14:15 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2008-07-08 14:15:13 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Zdenek Kabelac 2008-06-16 05:30:27 EDT
Description of problem:

When I run gnome-session-properties - I'm seeing the lines to change magically
in the GUI with this error line:

(gnome-session-properties:25615): Gtk-WARNING **: Failed to set text from markup
due to error parsing markup: Error on line 2: 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 &


Happens as well in Czech locales (thought the line number is slightly different)
(gnome-session-properties:25218): Gtk-WARNING **: Failed to set text from markup
due to error parsing markup: Chyba na řádku 2: Znak " " není platný na začátku
názvu entity; počátečním znakem entity je &; v případě, že nemá být entitou, je
zapotřebí ho napsat jako &

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


How reproducible:
always

Steps to Reproduce:
1. start g-s-p
2. browse over all elements in the Startup Programs
3. find the one which generate error message and changes its name
  
Actual results:
Seeing copy of some other line instead of the real name

Expected results:
Seeing the real name

Additional info:

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