Bug 919713 - TBD: I don't think we can deal with colorspace != RGB
Summary: TBD: I don't think we can deal with colorspace != RGB
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: xastir
Version: 18
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Lucian Langa
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-03-09 18:14 UTC by Rob Riggs
Modified: 2014-02-03 02:44 UTC (History)
3 users (show)

Fixed In Version: xastir-2.0.0-9.fc19
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-02-01 04:04:18 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Rob Riggs 2013-03-09 18:14:37 UTC
Description of problem:
Cannot use online maps because of error "TBD: I don't think we can deal with colorspace != RGB"

Version-Release number of selected component (if applicable):
xastir-2.0.0-4.fc17.x86_64

How reproducible:
Always

Steps to Reproduce:
1. Start Xastir from a terminal
2. Select Map|Map Chooser; a map chooser window will open
3. Select Expand Dirs
4. Select Online/OSM_cloudmade_1.geo
5. Select Apply
  
Actual results:
The map screen shows no map.  The terminal window displays:

TBD: I don't think we can deal with colorspace != RGBTBD: I don't think we can deal with colorspace != RGBTBD: I don't think we can deal with colorspace != RGB

Expected results:
The map is downloaded and displayed in Xastir

Additional info:
This is possibly due to a new incompatibility with ImageMagick.  Xastir developers recommend building against GraphicsMagick instead.

See the bottom of this message: http://www.mail-archive.com/xastir@lists.xastir.org/msg06480.html

Comment 1 Fedora End Of Life 2013-07-03 21:28:46 UTC
This message is a reminder that Fedora 17 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 17. 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 '17'.

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 17'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 17 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, you are encouraged  change the 
'version' to a later Fedora version prior to Fedora 17's end of life.

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.

Comment 2 Fedora End Of Life 2013-12-21 12:00:20 UTC
This message is a reminder that Fedora 18 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 18. 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 '18'.

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 18's end of life.

Thank you for reporting this issue and we are sorry that we may not be 
able to fix it before Fedora 18 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, you are encouraged  change the 'version' to a later Fedora 
version prior to Fedora 18's end of life.

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.

Comment 3 Alessio Caiazza 2014-01-21 15:56:19 UTC
Same problem on F19 and F20.

The patch provided in #1036204 fixes this issue.

Comment 4 Fedora Update System 2014-01-24 09:59:58 UTC
xastir-2.0.4-6.fc20 has been submitted as an update for Fedora 20.
https://admin.fedoraproject.org/updates/xastir-2.0.4-6.fc20

Comment 5 Fedora Update System 2014-01-24 10:01:33 UTC
xastir-2.0.0-9.fc19 has been submitted as an update for Fedora 19.
https://admin.fedoraproject.org/updates/xastir-2.0.0-9.fc19

Comment 6 Fedora Update System 2014-01-25 02:17:46 UTC
Package xastir-2.0.0-9.fc19:
* should fix your issue,
* was pushed to the Fedora 19 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing xastir-2.0.0-9.fc19'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2014-1462/xastir-2.0.0-9.fc19
then log in and leave karma (feedback).

Comment 7 Fedora Update System 2014-02-01 04:04:18 UTC
xastir-2.0.4-6.fc20 has been pushed to the Fedora 20 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 8 Fedora Update System 2014-02-03 02:44:50 UTC
xastir-2.0.0-9.fc19 has been pushed to the Fedora 19 stable repository.  If problems still persist, please make note of it in this bug report.


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