Check 1: Is the daemon running?
pgrep -a clipseNo output → start it:
clipse -listen &Check 2: Does the history file exist?
ls -la ~/.config/clipse/clipboard_history.jsonIf missing, the daemon hasn't captured anything yet. Copy any text, then check again.
Check 3: Is clipse_dir pointing at the right place?
If you customized clipse's data directory, mirror that in [General] clipse_dir in settings.ini.
Copy works, but nothing pastes into the target window.
Wayland:
which wtypeIf missing: install via your package manager. Arch: sudo pacman -S wtype.
X11:
which xdotoolInstall if missing: sudo pacman -S xdotool (or equivalent).
Both: check enter_to_paste behavior. Copy might be working while paste simulation fails silently. Try increasing paste_simulation_delay_ms to 300 — some compositors race the keystroke with the clipboard write.
clipse-guiInstall PyGObject:
# Arch
sudo pacman -S python-gobject gtk3
# Debian/Ubuntu
sudo apt install python3-gi gir1.2-gtk-3.0GTK3 introspection data missing. Install gir1.2-gtk-3.0 (Debian) or gtk3 (Arch).
Run from a terminal with debug logging:
G_MESSAGES_DEBUG=all clipse-guiLook for CSS parse errors or missing dependencies.
Your GTK theme may conflict with the app's CSS. Test with the default theme:
GTK_THEME=Adwaita clipse-guiIf it renders correctly, the theme is the culprit — either switch themes or edit get_app_css() in clipse_gui/constants.py to override the conflicting rules.
Set:
GDK_SCALE=2 clipse-guiOr globally via your WM.
See tray.md.
With histories > 10k items, filtering can lag. Tune:
[General]
search_debounce_ms = 500
[Performance]
initial_load_count = 50
load_batch_size = 30Higher debounce = fewer re-renders but less responsive feel.
If the app crashes on launch after a config edit, back up and reset:
mv ~/.config/clipse-gui/settings.ini ~/.config/clipse-gui/settings.ini.bak
clipse-guiA fresh default config regenerates.
Clipse GUI uses Python's logging module. To see detail:
CLIPSE_GUI_LOG=DEBUG clipse-gui 2>&1 | lessOr:
clipse-gui 2>&1 | grep -i errorWhen filing an issue at github.com/d7omdev/clipse-gui/issues, include:
- Output of
clipse-gui --version - Your desktop environment / window manager
- Wayland or X11
- Output of
pgrep -a clipse - Contents of
settings.ini(redact paths if needed) - Any error output with
G_MESSAGES_DEBUG=all