Bug 10133 - cmyktool-0.1.6-pre1-1.i586.rpm
Summary: cmyktool-0.1.6-pre1-1.i586.rpm
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: New RPM package request (show other bugs)
Version: Cauldron
Hardware: i586 Linux
Priority: Normal enhancement
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL: https://dl.dropboxusercontent.com/u/1...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-05-17 18:56 CEST by Robert Ottlovich
Modified: 2014-02-23 11:57 CET (History)
1 user (show)

See Also:
Source RPM:
CVE:
Status comment:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Robert Ottlovich 2013-05-17 18:56:45 CEST 
I learned that GIMP shipped with CMYK conversion tool, but it's too complicated to use. For this reason I've compiled and packaged CMYKTool 0.1.6-pre1 in Mageia 3 RC4. It seems that no dependencies are needed because I could install onto running live CD temporarily.

(Packager was Checkinstall 1.6.2.)

CMYKTool looks perfect with Photoprint, which I wasn't able to compiled because of unknown dependencies (by me). Somebody else's request is in bug id=3839.

If this rpm package is unable to install, please create your own official rpm from this source: http://www.blackfiveimaging.co.uk/cmyktool/cmyktool-0.1.6-pre1.tar.gz

Bye






Reproducible: 

Steps to Reproduce:
Comment 1 Jani Välimaa 2014-02-22 22:25:30 CET 
Available since mga4.

Status: NEW => RESOLVED
CC: (none) => jani.valimaa
Version: 3 => Cauldron
Resolution: (none) => FIXED

Comment 2 Robert Ottlovich 2014-02-23 11:44:55 CET 
CMYKTool 0.1.6-pre1 (Mageia 4 x86_64 DVD) has a bug when I try to open Preset editor window because of segmentation error:
(cmyktool:27004): Pango-WARNING **: Invalid UTF-8 string passed to pango_layout_set_text()
Szegmentálási hiba

with closing the main window itself, too.

This application is useless because of this error.

Status: RESOLVED => REOPENED
Resolution: FIXED => (none)

Comment 3 Manuel Hiebel 2014-02-23 11:57:23 CET 
closing since you opened bug 12857 (and thanks, it's better this way)

Status: REOPENED => RESOLVED
Resolution: (none) => FIXED
Note You need to log in before you can comment on or make changes to this bug.