"Text will be here" is displayed in the tray and nothing happens by clicking on it. about gnome-shell-extension-clipboard-indicator

[sounddrill31]

+1

"Hier erscheint der Text" or "Text will be here" is displayed in the tray and nothing happens by clicking on it.

OS: Arch Linux x86_64 DE: Gnome 46 on Wayland Extension version: 61

OS: OpenSUSE Tumbleweed with 6.8.4
DE: Gnome 46 with wayland
Extension Version: 61

Edit: I deleted cache(and disabled and enabled extension) and it's fixed!

rm -rf cat ~/.cache/[email protected]

[alephnull]

What worked for me:

• change UTF8_STRING in ~/.cache/[email protected]/registry.txt to text/plain;charset=utf-8
• disable and enable the extension
  It appears to be a problem only on Wayland.

[MeirKriheli]

@sounddrill31 Thanks, deleting the cache and re-enabling the extension helped here as well.

[DerPate]

@Tudmotu can confirm the update to Version 62 fixed the problem for me

[Tudmotu]

Can everyone here please try updating to version 62 and see if it fixes the issue for you?

Thanks! 🙏

[Tudmotu]

Thank you for testing it out @tanjilbhuiyan !

To update the extension you must log out and back in. This is true every time you update — it only updates after the next login.

[gentoo-root]

I figured that it happens when mimetype becomes UTF8_STRING for one or more entries in registry.txt. It still happens sometimes on version 62 during regular work (not upgrade). Could the issue be reopened?

[AmeyaVS]

I changed the UTF8_STRING to text/plain type, and reloaded the extension it seems to work.
Can this issue be reopened @Tudmotu ?

[Snorch]

If someone still experiences the problem on latest master, please give a try to #480 and say if it helps or not. (Probably you need to fully reboot to properly reload extension.)

It looks like just doing replacement in registry.txt didn't fix the problem completely, at least for me, as UTF8_STRING continues to appear there again and again (I see it appearing when I'm actively copying between Firefox and Tilix in both directions).

It also looks that the problem has other manifestation: sometimes the entries with mimetype==UTF8_STRING just silently disappear instead of causing the 'stuck extension' problem mentioned in this issue.

[MeirKriheli]

Same issue (and setup)

[Tudmotu]

Possibly related to this?
#458

[tanjilbhuiyan]

Thanks, it seems the issue is fixed. But faced a weird issue. i uninstalled previous one. then installed again. Got error in Gnome extension page. though the extension was downloaded. Had to log out and log in again. It seems working now.

[sounddrill31]

Works so far for me!

Thanks for the fix

[arturo-source]

Hello @Tudmotu,
I had the same problem when I updated to 61, then I updated to 62 and the problem kept.
Unfortunately I already deleted cache, as @sounddrill31 recommended and it started working again, so I cannot test anymore.

[Tudmotu]

Thank you for confirming @sounddrill31 !

@arturo-source apologies you had to remove your cache file 😕 Hope this won't have to happen again but if it does, next time I recommend renaming the file instead of deleting it, so that you can restore it later on.

[MeirKriheli]

Same here: removed the cache (was not that important anyway), so can't check.

[Tudmotu]

Thanks everyone, closing this issue 🙂

[dmnmsc]

This is still present here. Extension version 62. Archlinux up-to-date with wayland session.

[tanjilbhuiyan]

Clear the cache mentioned by @sounddrill31 . Things should work.

[dmnmsc]

But @Tudmotu said this should work without deleting cache. I'm just reporting the bug :)

[AmeyaVS]

Same here on Fedora 40 after updating the system.
I backed up my .cache as I still use some of the clipboard data.
Clearing the directory does work, but then I loose all the clipboard data.
I have the Extension version: 62 installed.

Update: Deleted all the content from .cache/[email protected], the clipboard indicator was working fine. Till the next reboot where the issue came back.

[djfjeff]

I have the same problem using the latest version on Fedora 40. Sometime, the issue arise and I need to clear cache for it to work again. Please reopen as this is definitely not solved.

[Tudmotu]

Reopening.
Can anyone clarify the steps to reproduce this issue?

1. Delete cache file
2. Copy some stuff
3. Log out, log in
4. Clipboard is broken?

[djfjeff]

It seems random on my end. Sometime when I unlock my session, I get the "Text will be here" issue, most of the time everything is alright...

I then delete the cache file and restart the extension and I am good for a while.

[HeroBrine1st]

It appears to be a problem only on Wayland.

No, it doesn't. Also I did not have UTF8_STRING in that file, I had to remove that folder to fix extension instead.
I am on NixOS unstable with GNOME 46.1 via X11+nvidia (and extension version is 62).

On the contrary, I did not face this issue on both Arch Linux and NixOS unstable (installed literally yesterday so i'm not sure) on another machine, which uses wayland.

[ewh]

I'm using Ubuntu 23.10, Gnome 45.2, Wayland. I'm using Clipboard Indicator 57 (installed from extensions.gnome.org). Version 57 seems to be the latest version on extensions.gnome.org for Gnome 45. Should the "Text will be here" issue be fixed in version 57. If not, will version 62 work correctly in Gnome 45?

[rebelinux]

What worked for me:

• change UTF8_STRING in ~/.cache/[email protected]/registry.txt to text/plain;charset=utf-8
• disable and enable the extension
  It appears to be a problem only on Wayland.

Solution works for me. thanks!

[ma0shu]

If someone still experiences the problem on latest master, please give a try to #480 and say if it helps or not. (Probably you need to fully reboot to properly reload extension.)

It looks like just doing replacement in registry.txt didn't fix the problem completely, at least for me, as UTF8_STRING continues to appear there again and again (I see it appearing when I'm actively copying between Firefox and Tilix in both directions).

It also looks that the problem has other manifestation: sometimes the entries with mimetype==UTF8_STRING just silently disappear instead of causing the 'stuck extension' problem mentioned in this issue.

#480 Works fine for me, thx