I'm batch converting a lot of svg files to pdf using Inkscape.
What happens:
The conversions happens just fine and runs as expected.
What also happens:
There is interference with the keyboard, specifically the various shift keys. The system behaves as if they were pressed randomly (or at least randomly as far as I can tell).
How to reproduce:
Make a small batch file to convert a bunch of random svg files. Open up notepad. Run the batch file, and as it runs, just tap the A key repeatedly. Some of the a's will come out with various umlauts and other extras.
Variant command lines I've tried, all with the same behaviour:
I've tried running both the Inkscape exe and com, with and without the --without-gui switch. Other programs run from the same batch doesn't do this. Behaves the same on another computer. OS is Windows 10 and Windows 7.
Why is this a problem:
This batch is a 10 hour run, which I run at least once a week. It's very impractical if I can't use my computer with it running in the background.
That's a bit bizarre, but honestly I'd get a spare computer to do one or the other. I find orphaned Win 7 and Mac computers and run Inkscape under Linux Mint without issue.
What I'm doing:
I'm batch converting a lot of svg files to pdf using Inkscape.
What happens:
The conversions happens just fine and runs as expected.
What also happens:
There is interference with the keyboard, specifically the various shift keys. The system behaves as if they were pressed randomly (or at least randomly as far as I can tell).
How to reproduce:
Make a small batch file to convert a bunch of random svg files. Open up notepad. Run the batch file, and as it runs, just tap the A key repeatedly. Some of the a's will come out with various umlauts and other extras.
Variant command lines I've tried, all with the same behaviour:
inkscape.exe input.svg --export-pdf=output.pdf
inkscape.exe --without-gui input.svg --export-pdf=output.pdf
inkscape.com input.svg --export-pdf=output.pdf
inkscape.com --without-gui input.svg --export-pdf=output.pdf
What I've tried:
I've tried running both the Inkscape exe and com, with and without the --without-gui switch. Other programs run from the same batch doesn't do this. Behaves the same on another computer. OS is Windows 10 and Windows 7.
Why is this a problem:
This batch is a 10 hour run, which I run at least once a week. It's very impractical if I can't use my computer with it running in the background.
Any advice?
That's a bit bizarre, but honestly I'd get a spare computer to do one or the other. I find orphaned Win 7 and Mac computers and run Inkscape under Linux Mint without issue.
I might, but currently, that batch file is a mess that is reliant on four external programs, so I'd prefer to keep it where it works...
This is a known bug in gtk3 (the windowing toolkit Inkscape uses), see https://gitlab.gnome.org/GNOME/gtk/-/issues/1033.
Well, then at least that means that I'm not imagining things (at least not this...). I'll just have to wait until GTK fixes it...