Bug 439005 – "backend error: text contains a double space"

Bug 439005 - "backend error: text contains a double space"

Summary:	"backend error: text contains a double space"

Status:	CLOSED UPSTREAM

Aliases:	None

Product:	Fedora
Classification:	Fedora
Component:	PackageKit (Show other bugs)
Sub Component:
Version:	rawhide
Hardware:	All Linux

Priority	low Severity low
Target Milestone:	---
Target Release:	---
Assigned To:	Robin Norwood
QA Contact:	Fedora Extras Quality Assurance
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2008-03-26 10:51 EDT by Michal Schmidt
Modified:	2008-03-26 13:02 EDT (History)
CC List:	2 users (show)

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2008-03-26 13:02:41 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)
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description Michal Schmidt 2008-03-26 10:51:50 EDT

Description of problem:
Useless (but harmless) error message pops up when selecting some packages in
Add/Remove Software. It says: "backend error: text contains a double space"

Version-Release number of selected component (if applicable):
PackageKit-0.1.9-2.fc9.x86_64

How reproducible:
always

Steps to Reproduce:
1. Run pk-application.
2. Find "nmap" package.
3. Click on it to display its description.

Actual results:
The popup error notification appears.

Expected results:
There should be no error.


Additional info:
It is true that nmap's description contains a double space. There are more
packages like this. The double space in the package description is nothing to
worry about and should not be reported as an error.

Comment 1 Richard Hughes 2008-03-26 13:02:41 EDT

Agreed, I've already nuked the double space warning in git a few days ago -- it
was there mainly for debugging. They'll be a new release in a few days which
should stop this harmless message. Thanks.

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