Besides your defunct(?) MultiClutch InputManager (time to uninstall it? ;-) nothing unexpected in the log:
> 2009-10-07 12.17.01 [0x0-0x2e02e].org.inkscape.Inkscape[783] what : Failed to open 'inkscape_pasted_image_20091007_121701.png' for writing: Read-only file system
There are two bugs in your report that lead to the crash:
1) due to the clipboard issue with X11 every 'copy' command inside Inkscape actually creates a 'Bitmap Copy' which is stored externally as PNG and inserted as linked bitmap.
related report (+ duplicates): upstream XQuartz issue Bug #307005 in Inkscape: “copy command always does bitmap copy”
2) Inkscape doesn't have permission to write the 'inkscape_pasted_image_xxx.png' to the default location (depending on Inkscape version and platform it's in $TMP, in $HOME or - on OS X - sometimes inside the application bundle 'Inkscape.app'). An unhandled exception (type Glib::Error) then causes the crash (terminate called after throwing an instance of 'Glib::FileError'). There seem to be many different causes for this file error - maybe you have installed Inkscape as Admin and run it as User, or you run Inkscape from a write-protected medium/location.
related bug reports to ''Glib::FileError'': Bug #211607 in Inkscape: “Crashes when attempting to use "Paste objects from clipboard..."” Bug #272192 in Inkscape: “Clicking "Edit->Paste" causes an internal error” Bug #308456 in Inkscape: “copy/paste crashes Inkscape” Bug #328597 in Inkscape: “Inkscape crashes when copying and pasting picture from openoffice document” Bug #381301 in Inkscape: “copy, paste, crash” Bug #418832 in Inkscape: “Crashes after clipboard paste”
Since the XQuartz workaround described in the FAQ works to prevent the crash I mark this as duplicate of bug #307005. If you don't agree or the crash re-occurs please add a comment and revert the duplicate status.
(the bug reports about crashes caused by "Glib::FileError" when 'copy&paste'ing a bitmap need yet to be triaged and marked as duplicate of the first reported case…)
Besides your defunct(?) MultiClutch InputManager (time to uninstall it? ;-) nothing unexpected in the log:
> 2009-10-07 12.17.01 [0x0-0x2e02e] .org.inkscape. Inkscape[ 783] what : Failed to open 'inkscape_ pasted_ image_20091007_ 121701. png' for writing: Read-only file system
There are two bugs in your report that lead to the crash:
1) due to the clipboard issue with X11 every 'copy' command inside Inkscape actually creates a 'Bitmap Copy' which is stored externally as PNG and inserted as linked bitmap.
related report (+ duplicates): upstream XQuartz issue
Bug #307005 in Inkscape: “copy command always does bitmap copy”
2) Inkscape doesn't have permission to write the 'inkscape_ pasted_ image_xxx. png' to the default location (depending on Inkscape version and platform it's in $TMP, in $HOME or - on OS X - sometimes inside the application bundle 'Inkscape.app'). An unhandled exception (type Glib::Error) then causes the crash (terminate called after throwing an instance of 'Glib::FileError'). There seem to be many different causes for this file error - maybe you have installed Inkscape as Admin and run it as User, or you run Inkscape from a write-protected medium/location.
related bug reports to ''Glib: :FileError' ':
Bug #211607 in Inkscape: “Crashes when attempting to use "Paste objects from clipboard..."”
Bug #272192 in Inkscape: “Clicking "Edit->Paste" causes an internal error”
Bug #308456 in Inkscape: “copy/paste crashes Inkscape”
Bug #328597 in Inkscape: “Inkscape crashes when copying and pasting picture from openoffice document”
Bug #381301 in Inkscape: “copy, paste, crash”
Bug #418832 in Inkscape: “Crashes after clipboard paste”
Since the XQuartz workaround described in the FAQ works to prevent the crash I mark this as duplicate of bug #307005. If you don't agree or the crash re-occurs please add a comment and revert the duplicate status.
(the bug reports about crashes caused by "Glib::FileError" when 'copy&paste'ing a bitmap need yet to be triaged and marked as duplicate of the first reported case…)