Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Prusa Slicer 2.8 rc 2 / iCCP: known incorrect sRGB profile #12920

Closed
1 of 2 tasks
Martin-Ox opened this issue Jun 27, 2024 · 7 comments
Closed
1 of 2 tasks

Prusa Slicer 2.8 rc 2 / iCCP: known incorrect sRGB profile #12920

Martin-Ox opened this issue Jun 27, 2024 · 7 comments

Comments

@Martin-Ox
Copy link

Description of the bug

When I start the new rc2 of Prusa Slicer 2.8, I get an error
iCCP: known incorrect sRGB profile , and then the sysdate & time
Because I have 2 screens there are two lines of the error.

Project file & How to reproduce

Just starting the prusa-slicer 2.8 r2 executable.

Videocard: Nvidia Geforce GTX 1660 Super
2x HP EliteDisplay E243

Drivers and firmwares are up to date.
log.txt
2024-06-27 15_33_03-PrusaSlicer Warning

Checklist of files included above

  • Project file
  • Screenshot

Version of PrusaSlicer

Version 2.8.0-rc2+win64

Operating system

Windows 10 22H2

Printer model

Prusa MK4

@mrbpoe
Copy link

mrbpoe commented Jul 1, 2024

Also experiencing the same issue with a GTX 3080 TI

@RP2090
Copy link

RP2090 commented Jul 2, 2024

Here the same problem. Maybe the custom color filament by default could be the cause? (RTX 2080Ti)

@darthgloda
Copy link

Same issue on macOS 14.5 Build 23F79, 2019 Retina 5K iMac. PrusaSlicer 2.8.0+MacOS-x64.

@ententeak
Copy link

Same with tripple screen setup - NVidia GeForce GT710 and GTX1660 - both at driver v. 27.21.14.5671 (latest for GT710)
Windows 11, build 22631.3958

@darthgloda
Copy link

The error persists for me in 2.8.1RC1. Pops up as soon as I launch the slicer and then at regular intervals.

@YuSanka
Copy link
Collaborator

YuSanka commented Sep 17, 2024

SPE-2485

lukasmatena pushed a commit that referenced this issue Sep 19, 2024
@lukasmatena
Copy link
Collaborator

Fixed in 2.8.1. Closing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

7 participants