Home > Error During > Error During Cms Conversion Xsane

Error During Cms Conversion Xsane

CloudFlare Ray ID: 304eb7f0f07722a6 • Your IP: • Performance & security by CloudFlare Register All Albums FAQ Today's Posts Search Hardware & Laptops Help with your hardware, including laptop issues Google™ Search FedoraForum Search Red Hat Bugzilla Search
Search Forums Show Threads There is also an alternative hpcups driver listed in the options and changing to that made the scanner available for me. Even in black and white it's an ugly scanXsane scanSimple scan Logged PCNetSpec Administrator Hero Posts: 12917 Karma: 1473 "-rw-rw-rw-" .. his comment is here

Comment 7 Joachim Backes 2010-04-23 07:58:42 EDT (In reply to comment #0) > Description of problem:xsane scanner software showing error "Error during CMS > conversion could not open scanner ICM profile". From memory, I think I had to disable colour management via the menu Preferences > Enable Color Management (uncheck). One more step Please complete the security check to access Why do I have to complete a CAPTCHA? If you expected something different, make sure that
# you have loaded a kernel driver for your USB host controller and have setup
# the USB system correctly.

donwatson Hero Member Posts: 849 Karma: 8 Gender: Getting older SOLVED XSane startup « on: June 04, 2012, 11:21:10 pm » Hi Folks,I am back with another problem.When I try to History Link existing bug Create bug report Link to a FAQ Create a new FAQ To post a message you must log in. Otherwise, you can try installing it from the hplip site. Has been working perfectly up > > to now.

Page 1 of 2 12 Last Jump to page: Results 1 to 10 of 11 Thread: xsane problem Thread Tools Show Printable Version Subscribe to this Thread… Display Linear Mode Switch The Number Of The Beast Peppermint version(s): Peppermint Seven (7) Re: XSane scanner not working in HP 1515 printer « Reply #2 on: September 05, 2015, 02:41:51 pm » How is It works fine. Then restart xsane.

Adv Reply December 11th, 2009 #10 mjolnar View Profile View Forum Posts Private Message First Cup of Ubuntu Join Date May 2008 Location Shasta Lake, CA Beans 6 DistroUbuntu 9.10 after repeated reinstall of xsane, it has proved to not fix anything. "Play a Windows CD backwards and hear satanic messages. Re: Xsane colour problem « Reply #5 on: October 16, 2014, 02:08:24 PM » Everything sane from synaptic is installed except sane-frontends.I downloaded the sane-data from :- the site does not Have you tried unchecking Preferences/enable color management on the menu? 2.

The Number Of The Beast Peppermint version(s): Peppermint Seven (7) Re: XSane scanner not working in HP 1515 printer « Reply #9 on: September 06, 2015, 03:21:37 pm » Why make The package is in the repositories, so you just have to do a 'yum install hplip', and do the configuration after. __________________ :confused: Skull One View Public Profile Find all posts For details and our forum data attribution, retention and privacy policy, see here PCLinuxOS-Forums Main Welcome, Guest. de Oliveira (ajoliveira) said on 2009-04-06: #1 2 things 1.

At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '11'. Done
[[email protected]]# Seem now KDE64 up to date.As I understand Old-Polack suggests to install the "iscan-whatever-the-name".rpm as the directory holding the Epson rpm only has one file suitable file. What do I need to do to get it to recognize the printer so it can use the scan feature of it...thanks nitewalker View Public Profile Find all posts by nitewalker Logged WARNING: You are logged into reality as 'root' ..

Also I connected the printer after installing HPLIP and only by using cups website. Lest we forget... I do not even know how to re-install xsane. That extra step of scanning with simple scan is what I would like to eliminate.

See man sane-usb for details.

# Not checking for parallel port scanners.

# Most Scanners connected to the parallel port or other proprietary ports
# can't be detected by this program.

Lest we forget... Comment 2 James McIntyre 2010-02-23 09:01:57 EST Error started to happen after loading "gocr" and scanning text. Christopher M.

Well that my friend is good enough for me. Every time I attempt to scan something with Xsane I get this error message Error during CMS Conversion: Could not open scanner ICM Profile. I'm going to leave this thread open in case any one can think of something else(I do like fixing things).

If I try to extract it, I am asked for a sub directory.

  1. Last version is Feb 2009.
  2. If you are on a personal connection, like at home, you can run an anti-virus scan on your device to make sure it is not infected with malware.
  3. But I prefer to use XSane.
  4. If I open GIMP Editor and choose to Create from XSane, it will show the printer info and when I click on it is when I get the same error code
  5. If you are unable to change the version, please add a comment here and someone will do it for you.
  6. Reply With Quote 04-Apr-2010,02:57 #4 F_Sauce View Profile View Forum Posts View Blog Entries View Articles Wise Penguin Join Date Jun 2008 Location Sogndal, Noreg Posts 1,107 Re: xsane problem [ubuntu]
  7. logging in as 'insane' is the only safe option.Team PeppermintLinux in the UK alynur Member Posts: 246 Karma: 5 New Forum User Peppermint version(s): 7 Re: XSane scanner not working in
  8. This is so frustrating, because it has always worked flawlessly.

Thank you for your help, problem now solved by attaching an older device setting. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. DoneSelecting iscan-data for 'iscan-data-1.31.0-1.noarch.rpm'The following packages will be REMOVED: sane-backends-iscan (1.0.24-5pclos2014)The following NEW packages will be installed: iscan-data (1.31.0-1)0 upgraded, 1 newly installed, 1 removed and 62 not upgraded.Need to get Re: Xsane colour problem[SOLVED] « Reply #10 on: November 05, 2014, 07:20:55 AM » I have seen this is solved but a couple of things attracted my attention while playing around

nitewalker View Public Profile Find all posts by nitewalker Tags finding, scanner, xsane « Previous Thread | Next Thread » Thread Tools Show Printable Version Display Modes Linear Mode Switch to Thank you for reporting this bug and we are sorry it could not be fixed. Until last week it worked fine under openSuse and I really love the xsane program. Has been working perfectly up to now.

At any rate it's a box that says "Error durinc CMS conversion; Could not open scanner ICM profile" « Last Edit: September 06, 2015, 12:43:26 am by AndyInMokum, Reason: Encapsulating output The Number Of The Beast Peppermint version(s): Peppermint Seven (7) Re: XSane scanner not working in HP 1515 printer « Reply #4 on: September 05, 2015, 04:16:16 pm » OK, I'm I don't believe I changed any options accidently. 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.

The time now is 09:40 PM. But then suddenly : it seems to be impossible to get the scanner working any more; I always get the following messages three times: Error during CMS conversion Could not open I certainly was particularly interested in testing the non Synaptic process so I dove right in.Code: [Select][[email protected]]# apt-get update
Get:1 pclinuxos/64bit release [1290B]
Fetched 1290B in 0s (4602B/s)
Get:1 Could anyone give me some help, please ?

In my case I used the specific file name I don't think that matters.Code: [Select][[email protected]]# apt-get install 141105-iscan-2.30.0-1.usb0.1.ltdl7.x86_64.rpm
Reading Package Lists... Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Make sure that it has installed the libsane-hpaio package. Logged Peppermint OS Community Forum Re: XSane scanner not working in HP 1515 printer « Reply #14 on: September 07, 2015, 04:40:16 pm » Print Pages: [1] 2 Go Up «

DoneBuilding Dependency Tree... I clicked on gray and a bunch of new options opened up below this box which I didn't touch. 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

© Copyright 2017 All rights reserved.