Please do not reply to this email- if you want to comment on the bug, go to the URL shown below and enter your comments there.
Changed by [EMAIL PROTECTED] http://bugzilla.ximian.com/show_bug.cgi?id=82287 --- shadow/82287 2007-08-03 03:16:41.000000000 -0400 +++ shadow/82287.tmp.28813 2007-08-03 10:46:28.000000000 -0400 @@ -86,6 +86,20 @@ 6. notice that F-Spot crashed ------- Additional Comments From [EMAIL PROTECTED] 2007-08-03 03:16 ------- Created an attachment (id=19692) exception output from the f-spot crash + +------- Additional Comments From [EMAIL PROTECTED] 2007-08-03 10:46 ------- +I can't reproduce this on my amd64 box with f-spot svn trunk. The +crash is coming out of f-spot C code. I do get the same crash when I +run f-spot 0.2.2 on the same mono/gtk-sharp stack. So it looks like +this is an f-spot bug that has been fixed since 0.2.2. + +It's possible this is related to a Gtk# change. The G_CRITICALS on +the output look like the a GObject is being used after it's been +released already. We are a lot better at releasing objects in 2.10 +than in 2.8 so this could possibly expose some bugs in application +code. I don't think there is any way we can provide backward compat +for scenarios like this. + _______________________________________________ mono-bugs maillist - [email protected] http://lists.ximian.com/mailman/listinfo/mono-bugs
