Notice (2018-05-24): bugzilla.xamarin.com is now in
Please join us on
Visual Studio Developer Community and in the
Mono organizations on
GitHub to continue tracking issues. Bugzilla will remain
available for reference in read-only mode. We will continue to work
on open Bugzilla bugs, copy them to the new locations
as needed for follow-up, and add the new items under Related
Our sincere thanks to everyone who has contributed on this bug
tracker over the years. Thanks also for your understanding as we
make these adjustments and improvements for the future.
Please create a new report on
GitHub or Developer Community with
your current version information, steps to reproduce, and relevant error
messages or log files if you are hitting an issue that looks similar to
this resolved bug and you do not yet see a matching new report.
Description of Problem:
libgdiplus.dylib in 3.0.9 is linked to no longer existing libraries, so e.g. opening http://localhost:8080/2.0/menu/menu1.aspx (xsp test-app) will result in a DllNotFoundException
Steps to reproduce the problem:
1. Starting test-web apps from xsp,
2. Opening http://localhost:8080/2.0/menu/menu1.aspx
Page returns a DllNotFoundException, although path to gdiplus.dll is mapped correctly in /Library/Frameworks/Mono.framework/Versions/Current/etc/mono/config
Page should show some results
How often does this happen?
3. see: otool -L /Library/Frameworks/Mono.framework/Versions/Current/lib/libgdiplus.dylib
/Library/Frameworks/Mono.framework/Versions/3.0.9/lib/libgdiplus.0.dylib (compatibility version 1.0.0, current version 1.0.0)
/Library/Frameworks/Mono.framework/Versions/3.0.9/lib/libglib-2.0.0.dylib (compatibility version 3601.0.0, current version 3601.0.0)
/Library/Frameworks/Mono.framework/Versions/3.0.9/lib/libintl.8.dylib (compatibility version 10.0.0, current version 10.2.0)
/usr/lib/libiconv.2.dylib (compatibility version 7.0.0, current version 7.0.0)
/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 125.2.11)
/Library/Frameworks/Mono.framework/Versions/3.0.9/lib/libcairo.2.dylib (compatibility version 11203.0.0, current version 11203.14.0)
/Library/Frameworks/Mono.framework/Versions/3.0.9/lib/libpixman-1.0.dylib (compatibility version 29.0.0, current version 29.2.0)
/Library/Frameworks/Mono.framework/Versions/3.0.9/lib/libtiff.5.dylib (compatibility version 8.0.0, current version 8.0.0)
/Library/Frameworks/Mono.framework/Versions/3.0.8/lib/liblzma.5.dylib (compatibility version 6.0.0, current version 6.4.0)
/Library/Frameworks/Mono.framework/Versions/3.0.8/lib/libjpeg.8.dylib (compatibility version 9.0.0, current version 9.0.0)
/Library/Frameworks/Mono.framework/Versions/3.0.8/lib/libgif.4.dylib (compatibility version 6.0.0, current version 6.6.0)
/Library/Frameworks/Mono.framework/Versions/3.0.8/lib/libpng14.14.dylib (compatibility version 27.0.0, current version 27.0.0)
/Library/Frameworks/Mono.framework/Versions/3.0.9/lib/libfontconfig.1.dylib (compatibility version 8.0.0, current version 8.2.0)
/Library/Frameworks/Mono.framework/Versions/3.0.8/lib/libfreetype.6.dylib (compatibility version 17.0.0, current version 17.0.0)
/usr/lib/libz.1.dylib (compatibility version 1.0.0, current version 1.2.3)
/usr/lib/libbz2.1.0.dylib (compatibility version 1.0.0, current version 1.0.5)
/Library/Frameworks/Mono.framework/Versions/3.0.8/lib/libexpat.1.dylib (compatibility version 7.0.0, current version 7.2.0)
link /Library/Frameworks/Mono.framework/Versions/3.0.8 to existing 3.0.9 directory.
Duncan, I think this is the issue we discussed a while ago (and was fixed in 3.0.10) right ?
Closing old bug, looks like it was fixed long ago.