clipboard-manager icon indicating copy to clipboard operation
clipboard-manager copied to clipboard

Can't use anymore as of yesterday

Open dodalovicgran opened this issue 2 months ago • 20 comments

Just seeing this:

Image

I copied, installed this env var, but even after restart, removing and adding the applet again, it always shows that same message

dodalovicgran avatar Oct 31 '25 13:10 dodalovicgran

Just seeing this: Image

I copied, installed this env var, but even after restart, removing and adding the applet again, it always shows that same message

which distro are you using? On arch a system update fixed it for me as the cosmic de version got bumped to 1.0.0.beta.4-1 from 1.0.0.beta.1.1-1

domahet avatar Oct 31 '25 15:10 domahet

I am having the exact same issue.

skostojohn avatar Oct 31 '25 15:10 skostojohn

Looks like it will just not work with flatpak anymore (see this commit https://github.com/pop-os/cosmic-comp/commit/d2d7c655acf6a9ce10d66773410e49ef216a4211).

We need to find a way to fix this, or change the way this applet is packaged :(

wiiznokes avatar Oct 31 '25 17:10 wiiznokes

same for me on ubuntu 25.10 arm64

celproject avatar Oct 31 '25 23:10 celproject

https://gitlab.freedesktop.org/wayland/wayland-protocols/-/issues/294

wiiznokes avatar Oct 31 '25 23:10 wiiznokes

I removed the flatpak version, compiled from source and it works I guess will do for now.

celproject avatar Nov 01 '25 09:11 celproject

@celproject can you publish it ? I am still stucked with no clipboard manager.

dominix avatar Nov 04 '25 22:11 dominix

I should have everything

cat /etc/profile.d/data_control_cosmic.sh
export COSMIC_DATA_CONTROL_ENABLED=1

but nonetheless

journalctl -p 3 -xb --user  |grep  clipboard-manager
nov. 04 19:48:10 pop cosmic-panel[3286]: io.github.cosmic_utils.cosmic-ext-applet-clipboard-manager: exited with code 137
nov. 04 19:48:11 pop cosmic-ext-applet-clipboard-manager[29217]: clipboard: A required Wayland protocol (zwlr_data_control_manager_v1 version 1) is not supported by the compositor

still showing that data control protocol is not active ... what should I do Next ?

dominix avatar Nov 04 '25 23:11 dominix

This does not work after a flatpak install. But it does if you build and install from scratch:

sudo apt install libxkbcommon-dev
sudo apt install just
just build-release && sudo just install

jeetsukumaran avatar Nov 04 '25 23:11 jeetsukumaran

This does not work after a flatpak install. But it does if you build and install from scratch:

sudo apt install libxkbcommon-dev
sudo apt install just
just build-release && sudo just install

sudo apt install libxkbcommon-dev doesn't work:

Unable to detect release version (use '--releasever' to specify release version)
Error: There are no enabled repositories in "/etc/yum.repos.d", "/etc/yum/repos.d", "/etc/distro.repos.d".

dodalovicgran avatar Nov 05 '25 05:11 dodalovicgran

This does not work after a flatpak install. But it does if you build and install from scratch:

sudo apt install libxkbcommon-dev
sudo apt install just
just build-release && sudo just install

sudo apt install libxkbcommon-dev doesn't work:

Unable to detect release version (use '--releasever' to specify release version)
Error: There are no enabled repositories in "/etc/yum.repos.d", "/etc/yum/repos.d", "/etc/distro.repos.d".

The sudo apt install part will only work on systems that use the Debian package manager: Debian, Ubuntu, PopOS (which I'm running).

In your case I think it might be yum something something, though I'm not sure.

The library name part is the second piece of the puzzle. You need to figure the equivalent package name in what looks to be a yum based OS (Fedora? RedHat?) if it's not the same

-- jeet

jeetsukumaran avatar Nov 05 '25 07:11 jeetsukumaran

Cloned the git and ran the above commands. Still fails : cargo build --release sh: 1: cargo: not found

copyq not working either (does not seem to track Ctrl+C or Copy) . Becoming a bit of a serious problem. Thinking about ditching POP-OS 24.04 completely

biton13 avatar Nov 05 '25 07:11 biton13

Cloned the git and ran the above commands. Still fails : cargo build --release sh: 1: cargo: not found

Install cargo

jeetsukumaran avatar Nov 05 '25 07:11 jeetsukumaran

Cloned the git and ran the above commands. Still fails : cargo build --release sh: 1: cargo: not found

Install cargo

Thanks ... now I feel like ... :)

So steps for people like me:

  • Install git (check it out)
  • clone repo and then in local folder:
sudo apt install cargo
sudo apt install libxkbcommon-dev
sudo apt install just
just build-release && sudo just install

biton13 avatar Nov 05 '25 07:11 biton13

This does not work after a flatpak install. But it does if you build and install from scratch:

sudo apt install libxkbcommon-dev
sudo apt install just
just build-release && sudo just install

yes, it works for me too this way

dominix avatar Nov 05 '25 13:11 dominix

Hi @wiiznokes,

What about #132 ?

Thanks

KaKi87 avatar Nov 07 '25 09:11 KaKi87

Same issue on PopOS 24 Cosmic

installing these packages didn't solve the problem.

sudo apt install libxkbcommon-dev
sudo apt install just
just build-release && sudo just install

hoffmanlucas avatar Nov 10 '25 15:11 hoffmanlucas

Can confirm it's also a problem on cachyOS 6.17.7-3. I think it's possible that there's been a change in cosmic-comp regarding the data control protocol or a flatpak sandboxing issue.

kit-foxboy avatar Nov 13 '25 20:11 kit-foxboy

This should be made available to be installed with apt if Flatpak is iffy.

dandrei avatar Nov 16 '25 09:11 dandrei

This should be made available to be installed with apt if Flatpak is iffy.

Yep, that's #132

KaKi87 avatar Nov 16 '25 14:11 KaKi87