** Changed in: mono (upstream)
Status: Confirmed = Fix Released
--
crash on colour adjustments
https://launchpad.net/bugs/37412
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
i can confirm this is fixed with 0.3.2 in feisty
thanks
** Changed in: f-spot (Ubuntu)
Status: Fix Committed = Fix Released
--
crash on colour adjustments
https://launchpad.net/bugs/37412
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
0.3.1 was released today. once this makes it into ubuntu i can test if
it is fixed.
--
crash on colour adjustments
https://launchpad.net/bugs/37412
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
From upstream
--- Comment #5 from Larry Ewing 2006-12-01 23:30 UTC ---
I took another look at where we are actually using this and worked around the
issue. It should be fixed CVS and will be released in 0.3.1.
i expect this will make it into feisty. maybe then we can ask for a
** Changed in: mono (upstream)
Status: Unknown = Confirmed
--
crash on colour adjustments
https://launchpad.net/bugs/37412
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
this is still present in edgy as of 20060929.
Can i recommend that the the priority be increased, as this is a crasher
in a default application when using a very user visible feature.
lcms: Error #12288; Corrupted memory profile
System.Exception: Invalid Profile Data
at Cms.Profile..ctor
