[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#966423: inkscape: Copy & Paste of objects is broken



On Thu, Jul 30, 2020 at 03:22:16PM +0200, Alex wrote:
> This happens in every document for me.
> 
> - Open Inkscape
> - Create a rectangle
> - Try to copy & paste it.

I confirm, I really can't see anything like that happening. :(
I also don't get anything at all in the terminal.

> > however, this error message is known:
> I am not sure if those are useful. The error looks like it belongs to
> some smart pointer library or something similar and isn't too helpful
> except someone knows which pointers may be the problem when copying/pasting.

The error message comes from a function dealing with ref-counting
internal to inkscape.  I'm sure there are many callers to it though, so
yes, it's not incredibly useful.

> I can see if I should open an issue, I am just thinking if it affects
> upstream it would be already known. Is the Debian testing package a
> release or a snapshot from the upstream?

It's the official tarball of 1.0 from upstream, plus two very innoucus
patches (one of which is even accepted upstream):
https://sources.debian.org/src/inkscape/1.0-3/debian/patches/

> I'd like to test 1.0-4 soon, but I cannot get it from Debian unstable
> without installing a lot more unstable packages.

I doubt 1.0-4 changes anything, it's only adding this new trivial patch:
https://sources.debian.org/src/inkscape/1.0-4/debian/patches/fix-crash-missing-cursor.patch/
and 1.0-5 that I'm uploading today likewise adds a tiny irrelevant
patch.

Hence I'm positive if it's anything it's on the upstream side :)

-- 
regards,
                        Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540      .''`.
More about me:  https://mapreri.org                             : :'  :
Launchpad user: https://launchpad.net/~mapreri                  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-

Attachment: signature.asc
Description: PGP signature


Reply to: