-
-
Notifications
You must be signed in to change notification settings - Fork 81
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Can't Write to Clipboard (Possibly Linux-related) #48
Comments
Original bug report in my extension, just for context... |
The other bug reporter mentioned that his OS is Linux x64 4.20.6 (Gentoo). |
Seems to be some problem with reading the |
@jdall @Sembiance can you offer any more info to help reproduce the issue? |
Sure, @gazugafan - if you can tell me what you need, and how to produce it. You know your plugin, and the ecosystem it is installed in. I'm a mere user, knowing nothing about either. |
@sindresorhus any chance you can try (or already did try) reproducing this on Gentoo or SolydX? I can certainly try myself, but even if I'm successful I'm not sure what else I could do besides give you the same error log. Do you think we should report this issue somewhere else? |
@IssueHunt has funded $40.00 to this issue.
|
@gazugafan When #50 and sindresorhus/execa#212 get released, it will allow you to see the root error. |
@gazugafan BTW, if it is a problem vscode introduces, not your packaging, please tell us, it might make sense to introduce handling of such condition right in library, as it should only require a couple of code lines. |
Thanks @stroncium !! Yeah you were definitely on the right track. I was packaging the extension on Windows, so your question about executable permissions on the xsel binary made me raise an eyebrow. Turns out, packaging under Windows would remove any executable permissions. I just had to package the extension under Linux to make sure the execute permission sticks. I think that's going to solve it :D |
I've just released a new version which I think is going to solve this for the users that originally reported the problem. As soon as I hear back from them, I'm pretty sure I'll be closing this. |
We're good. Thanks again! |
@sindresorhus has rewarded $36.00 to @stroncium. See it on IssueHunt
|
I've gotten a couple bug reports on my VS Code extension that uses Clipboardy. It seems that there's sometimes a problem calling clipboardy.write(). I haven't been able to reproduce it myself, but both users are running Linux. One in particular is running:
Linux x64 4.9.0-8-amd64 (SolydX 9 / Debian Stretch)
One of them gave the following error log...
... the line in my extension triggering this error (
out/src/extension.js:96:24
) is calling clipboardy.write(). It looks like this...... which seems to be really straightforward to me. Not sure what's going wrong, but according to the error log it could be up in clipboardy or execa. Any ideas? Are there any known issues with clipboardy on certain flavors of Linux?
IssueHunt Summary
stroncium has been rewarded.
Sponsors (Total: $40.00)
Tips
The text was updated successfully, but these errors were encountered: