Skip to content

clipse --listen on login starts but doesnt listen to system copy events #41

@BrayanLope5

Description

@BrayanLope5

I am on Linux/gnome. I love this tool btw
I have a systemd user service that does successfully start clipse, but clipse doesn't record system copy events. If I run clipse --listen on the terminal, it works as expected and records all copy events.
This is my systemd service.

[Service]
Type=oneshot
RemainAfterExit=true
StandardOutput=journal
ExecStart=/home/brayan/Applications/bin/clipse/clipse_0.0.71_linux_amd64/clipse --listen
[Install]
WantedBy=default.target

Thank you for any help you can offer:)

EDIT:
After some tests I've found the following:

  1. The user service, WILL start clipse on boot/login. But clipse won't record system copy events like I mentioned above.
  2. Stopping and then starting the service again FROM the terminal AFTER login, starts clipse and clipse successfully records system copy events.
  1. Checking details about the two different processes, one started from systemd and the other from the terminal I get the following.

Clipse started from the terminal AFTER login
Started From Service

Clipse started from systemd service. (clipse is added to my path only when opening a terminal emulator.)
Started in terminal

I don't know enough about this but the difference I see is in one having a tty listed but not the other.

Metadata

Metadata

Assignees

Labels

No labels
No labels

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions