copy/paste broken

Bug #1325447 reported by philodygmn on 2014-06-02
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Inkscape
Undecided
Unassigned

Bug Description

Both under X11 and XQuartz on Mac OS X Snow Leopard 10.6.8 on my 32-bit Intel iMac (metal stand, ~2006), copy/paste does some kind of image render, __ex_tr__e___mely_ slowly_, such that if anything does paste it is opaque and rendered with an opaque background within its bounding box (any transparency being applied as luminosity instead). This, needless to say, is a crippling, catastrophic bug or issue, perhaps with the XWindows integration, but nonetheless it renders the program virtually useless under this, the latest available configuration. Because my machine is 32-bit, I cannot upgrade my OS further.

My X11 about box says:
XQuartz 2.3.6 (xorg-server 1.4.2-apple56)

My XQuartz about box says:
XQuartz 2.7.6 (xorg-server 1.14.6)

My version of Inkscape is 0.48.2

su_v (suv-lp) wrote :

> if anything does paste it is opaque and rendered with an
> opaque background within its bounding box

Known conflict between XQuartz and vector applications like Inkscape and Fontforge which causes vector information to be copy&pasted as bitmap images. A workaround is described in the FAQ:
<http://wiki.inkscape.org/wiki/index.php/FAQ#Copying_and_pasting_in_Inkscape_creates_pixellated_images_instead_of_copying_the_vector_objects>
and shown in this screenshot:
<https://bugs.launchpad.net/inkscape/+bug/307005/+attachment/1760181/+files/X11-pasteboard-preferences.png>

The changes take effect immediately (no need to restart X11/XQuartz or Inkscape, however, earlier copy&pasted objects have to be redone (if the original vector version still exists).

Linking as duplicate to
- Bug #307005 “[OS X] copy & paste inserts a bitmap copy instead of the vector object”
  <https://bugs.launchpad.net/inkscape/+bug/307005>

tags: added: clipboard osx

I really appreciate the swift reply, suv-lp--and late on a weekend! Silly me had presumed the age of my machine had most to do with it, and that something like this couldn't possibly be known yet still released (I could swear the duped bug wasn't in the list of candidates when I submitted mine), I didn't even think to check the FAQ, but its explanation squares everything neatly into perspective. I'm already working again! Thanks a ton, and enjoy the rest of your weekend!

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers