https://bugzilla.novell.com/show_bug.cgi?id=658040
https://bugzilla.novell.com/show_bug.cgi?id=658040#c5 Guido Van Hoecke <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|[email protected] | --- Comment #5 from Guido Van Hoecke <[email protected]> 2010-12-13 15:12:12 UTC --- Maybe I should mention that these asp.net applications all use a local or remote mysql database. Form the stack trace it appears that mono is trying to write to a unix version of the registry. It seems to do this at a location where it does not have write access. I can not deduce from the stack trace where exactly this is. (I'd give it write access it I knew). I am so sorry that I can not cook up a small test application with an apache server and a mysql server carrying a public database with credentials that can be published. But this very same problem has been reported by Mr Abe Gillespie on Mon Nov 22 09:20:14 EST 2010. And at http://lists.ximian.com/pipermail/mono-list/2010-November/046160.html Mr Gonzalo Panigua Javier replied on Mon Nov 22 09:20:14 EST 2010 'I fixed this in master and mono-2-8 a couple of days ago. It should be in the next 2.8.x series release and 2.10.' And indeed, you can find it at https://github.com/mono/mono/commit/d326d51789cf39012b55bc31dc6945249ac442c6 Also Mr Robert Abram reported this problem. I'd already be grateful if somebody could tell me where mono is trying to write this registry so that I can temporarily provide write access! -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug. _______________________________________________ mono-bugs maillist - [email protected] http://lists.ximian.com/mailman/listinfo/mono-bugs
