Bug 11166 - kde 4.10.5 spams stderr with message "Reading ras files from sequential devices not supported"
Summary: kde 4.10.5 spams stderr with message "Reading ras files from sequential devic...
Status: RESOLVED OLD
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 3
Hardware: i586 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-09-05 00:49 CEST by Ethan Merritt
Modified: 2015-03-31 16:04 CEST (History)
2 users (show)

See Also:
Source RPM:
CVE:
Status comment:


Attachments

Description Ethan Merritt 2013-09-05 00:49:51 CEST

    
Comment 1 Ethan Merritt 2013-09-05 00:50:37 CEST
Since recent update from kde 4.10.

Summary: kde4.10 spams stderr with message "Reading ras files from sequential devices not supported" => kde 4.10.5 spams stderr with message "Reading ras files from sequential devices not supported"

Comment 2 Ethan Merritt 2013-09-05 00:58:47 CEST
Since recent update from kde 4.10.2 to 4.10.5, running user applications linked against qt4 can trigger annoying junk message "Reading ras files from sequential devices not supported" on stderr.  This message is apparently generated by the kde plugin component kimg_ras.so in routine RASHandler::canRead().  This bug has a history on the web for various builds of KDE in other distros, but has only now shown up on my Mageia machines. 

Note: The message seems to trigger whenever the user app accesses a pixmap buffer using QPixmap::fromImage(image).  But I do not really understand why a KDE plugin is involved in this process.  Possibly there is another source for this message besides king_ras.so?
David Walser 2013-09-06 15:05:37 CEST

CC: (none) => balcaen.john, nicolas.lecureuil

Comment 3 Marja Van Waes 2015-03-31 16:04:31 CEST
Mageia 3 changed to end-of-life (EOL) status 4 months ago.
http://blog.mageia.org/en/2014/11/26/lets-say-goodbye-to-mageia-3/ 

Mageia 3 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of Mageia
please feel free to click on "Version" change it against that version of Mageia
and reopen this bug.

Thank you for reporting this bug and we are sorry it could not be fixed.

--
The Mageia Bugsquad

Status: NEW => RESOLVED
Resolution: (none) => OLD


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