Skip to content
This repository has been archived by the owner on Dec 16, 2021. It is now read-only.

Consistent Copy Message error code #244

Closed
4 tasks
gloatoriginal opened this issue Feb 5, 2020 · 6 comments
Closed
4 tasks

Consistent Copy Message error code #244

gloatoriginal opened this issue Feb 5, 2020 · 6 comments

Comments

@gloatoriginal
Copy link

How have you installed cordless

  • Arch User Repository
  • [ x] Snap
  • scoop
  • brew
  • go get

What happened

I navigate to messages with "alt+t" than press "c" on selected message to copy, than am greeted with an error

How do you reproduce this bug

This happened to me on Debian Stretch 9.11 and aswell on Debian Buster 10.2

Highlight a message in private messages and press "c" to copy the selected message

Error output

An error occurred - Error copying message: exit status 1

How to fix

Not sure

System information

Debian Stretch 9.11 Tested on first
Debian Buster 10.2 Tested on second

Key Value
OS TODO
Architechture TODO
@Bios-Marcel
Copy link
Owner

Are you on wayland?

@gloatoriginal
Copy link
Author

I'm not sure I fully understand what that means? I ssh into my linux computer from windows 10.
I havn't installed anything called wayland manually. I updated to Buster and tested right after update

@Bios-Marcel
Copy link
Owner

This won't work anyway, because it will copy the cobtent to your remotemachine clipboard.

@Bios-Marcel
Copy link
Owner

Bios-Marcel commented Feb 5, 2020

The workaround is to disable mouse support, hit ctrl-b, select the message in your terminal via text selection and copy how you'd normaly copy

@Bios-Marcel
Copy link
Owner

Bios-Marcel commented Feb 5, 2020

However, I can't do much with "exit status 1". I am assuming that it can't find x11 / wayland utils for copying, because you are running on a headless machine. You need to have either xclip or wl-copy on your machine. If you forward the X-Session / Wayland session to your local machine, then theoretically you could be able to have a shared clipboard, not sure though.

@gloatoriginal
Copy link
Author

no worries, I thought about the goofiness more once i remembered I was ssh into the machine.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants