-
Notifications
You must be signed in to change notification settings - Fork 84
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Hot keys not working since 1.4.4-2 on Debian testing 64-bit #97
Comments
Same problem here.. I've done a little investigation and found out that it throws some errors instead showing GUI. Unfortunately I wasn't able to solve them.
|
Update: There is another issue thanks to this hotkeys' complexity. When you go to As soon as you delete the empty line, it automatically deletes the immediate next line. This behavior is rather critical in my humble opinion. |
I have the same problem, but could not reproduce the error when custom building from the debian package source directory (https://salsa.debian.org/debian/clipit.git). Looks like it is an issue of the build itself... |
@swillner When you say custom building, what exactly did you change comparing the original build? |
I build directly from the debian source repo (using |
@swillner ah OK, cool. Hmm...I wonder what's causing this problem with the existing package. |
Hi! My version: The same error:
|
Same issue here |
Same issue with version 1.4.4-8 on Manjaro/Arch linux
had to rollback on version 1.4.3-2. ldd $(which clipit)
linux-vdso.so.1 (0x00007ffc475b2000)
libgtk-x11-2.0.so.0 => /usr/lib/libgtk-x11-2.0.so.0 (0x00007f90814c4000)
libgdk-x11-2.0.so.0 => /usr/lib/libgdk-x11-2.0.so.0 (0x00007f9081210000)
libgobject-2.0.so.0 => /usr/lib/libgobject-2.0.so.0 (0x00007f9080fbc000)
libglib-2.0.so.0 => /usr/lib/libglib-2.0.so.0 (0x00007f9080ca5000)
libappindicator.so.1 => /usr/lib/libappindicator.so.1 (0x00007f9080a98000)
libX11.so.6 => /usr/lib/libX11.so.6 (0x00007f9080759000)
libc.so.6 => /usr/lib/libc.so.6 (0x00007f9080593000)
libgmodule-2.0.so.0 => /usr/lib/libgmodule-2.0.so.0 (0x00007f908038f000)
libpangocairo-1.0.so.0 => /usr/lib/libpangocairo-1.0.so.0 (0x00007f9080182000)
libXfixes.so.3 => /usr/lib/libXfixes.so.3 (0x00007f907ff7c000)
libatk-1.0.so.0 => /usr/lib/libatk-1.0.so.0 (0x00007f907fd56000)
libcairo.so.2 => /usr/lib/libcairo.so.2 (0x00007f907fa33000)
libgdk_pixbuf-2.0.so.0 => /usr/lib/libgdk_pixbuf-2.0.so.0 (0x00007f907f80d000)
libgio-2.0.so.0 => /usr/lib/libgio-2.0.so.0 (0x00007f907f46d000)
libpangoft2-1.0.so.0 => /usr/lib/libpangoft2-1.0.so.0 (0x00007f907f258000)
libpango-1.0.so.0 => /usr/lib/libpango-1.0.so.0 (0x00007f907f011000)
libfontconfig.so.1 => /usr/lib/libfontconfig.so.1 (0x00007f907edce000)
libm.so.6 => /usr/lib/libm.so.6 (0x00007f907ec49000)
libpthread.so.0 => /usr/lib/libpthread.so.0 (0x00007f907ec26000)
libXrender.so.1 => /usr/lib/libXrender.so.1 (0x00007f907ea1b000)
libXinerama.so.1 => /usr/lib/libXinerama.so.1 (0x00007f907e818000)
libXi.so.6 => /usr/lib/libXi.so.6 (0x00007f907e607000)
libXrandr.so.2 => /usr/lib/libXrandr.so.2 (0x00007f907e3fc000)
libXcursor.so.1 => /usr/lib/libXcursor.so.1 (0x00007f907e1f2000)
libXcomposite.so.1 => /usr/lib/libXcomposite.so.1 (0x00007f907dfed000)
libXdamage.so.1 => /usr/lib/libXdamage.so.1 (0x00007f907ddea000)
libXext.so.6 => /usr/lib/libXext.so.6 (0x00007f907dbd8000)
libffi.so.6 => /usr/lib/libffi.so.6 (0x00007f907d9cf000)
libpcre.so.1 => /usr/lib/libpcre.so.1 (0x00007f907d75d000)
libindicator.so.7 => /usr/lib/libindicator.so.7 (0x00007f907d54f000)
libdbusmenu-gtk.so.4 => /usr/lib/libdbusmenu-gtk.so.4 (0x00007f907d339000)
libdbusmenu-glib.so.4 => /usr/lib/libdbusmenu-glib.so.4 (0x00007f907d11d000)
libfreetype.so.6 => /usr/lib/libfreetype.so.6 (0x00007f907ce54000)
libxcb.so.1 => /usr/lib/libxcb.so.1 (0x00007f907cc2b000)
libdl.so.2 => /usr/lib/libdl.so.2 (0x00007f907cc26000)
/lib64/ld-linux-x86-64.so.2 => /usr/lib64/ld-linux-x86-64.so.2 (0x00007f9081b4c000)
libpixman-1.so.0 => /usr/lib/libpixman-1.so.0 (0x00007f907c97c000)
libpng16.so.16 => /usr/lib/libpng16.so.16 (0x00007f907c746000)
libxcb-shm.so.0 => /usr/lib/libxcb-shm.so.0 (0x00007f907c542000)
libxcb-render.so.0 => /usr/lib/libxcb-render.so.0 (0x00007f907c334000)
libz.so.1 => /usr/lib/libz.so.1 (0x00007f907c11d000)
librt.so.1 => /usr/lib/librt.so.1 (0x00007f907c113000)
libresolv.so.2 => /usr/lib/libresolv.so.2 (0x00007f907c0f8000)
libmount.so.1 => /usr/lib/libmount.so.1 (0x00007f907be9f000)
libharfbuzz.so.0 => /usr/lib/libharfbuzz.so.0 (0x00007f907bdea000)
libthai.so.0 => /usr/lib/libthai.so.0 (0x00007f907bbe0000)
libfribidi.so.0 => /usr/lib/libfribidi.so.0 (0x00007f907b9c4000)
libexpat.so.1 => /usr/lib/libexpat.so.1 (0x00007f907b792000)
libuuid.so.1 => /usr/lib/libuuid.so.1 (0x00007f907b589000)
libbz2.so.1.0 => /usr/lib/libbz2.so.1.0 (0x00007f907b379000)
libXau.so.6 => /usr/lib/libXau.so.6 (0x00007f907b175000)
libXdmcp.so.6 => /usr/lib/libXdmcp.so.6 (0x00007f907af6f000)
libblkid.so.1 => /usr/lib/libblkid.so.1 (0x00007f907ad1c000)
libgraphite2.so.3 => /usr/lib/libgraphite2.so.3 (0x00007f907aaf0000)
libdatrie.so.1 => /usr/lib/libdatrie.so.1 (0x00007f907a8e9000) glib2 is 2.56.1-1 |
Same issue with version 1.4.4-2 after upgrading Ubuntu from 18.04 to 18.10. Temporary fixed by reinstalling lower version (1.4.2-1.2) of ClipIt from pkgs.org |
I got similar errors as @emjayko:
I found out, that if I hold the hotkey long enough, the history window appears. |
Exact same issue for me with the latest master (looks like version string has been updated to 1.4.5), built with --with-gtk3. There were some deprecation warnings during configure but it finished fine. But I guess this particular issue is still to be fixed. |
THANK YOU! |
I now have this issue in Debian Stable 10 … unsurprisingly I guess. ClipIt version 1.4.4 from debian buster repo. Problem exactly as described above, hotkeys do not work. Terminal shows error: Possibly related: If I interact with the tray icon and pull up preferences, about, etc. they work fine. However if I try to use, for instance the History hotkey (as usual nothing happens on key press), but if I then try to open one of the dialogue/windows such as preferences or the about page, etc I will get a small black rectangle in the upper left portion of my screen, the intended window never appears and ClipIt must be killed to get rid of the black rectangle. |
So is this project dead or what? Completely broken across many distributions and not a peep :( |
I cannot speak for the ClipIt project in any way and cannot comment on whether the project has any life in it at this time or not. For what it's worth, I personally have moved over to using GPaste. Which is in the Debian repos and works very well. I post this, not to impugn the ClipIt project in any way, or even to claim that GPaste is the best alternative (indeed, there seem to be many) … but only in the hopes that it may help users who are presently encountering a functionality breaking issue and looking for a relatively quick & painless fix. |
I hesitate to continue hijacking this thread discussing replacements, but I'm not sure what you've said is really true. I'm not running gnome, just a window manager on top of X and I don't recall GPaste pulling in a significant number of dependencies. Of course, I habitually choose the application that works best for me—I don't disregard anything solely on the basis of what libraries it uses, so perhaps my system is just massively bloated and all those Gnome dependencies were already present. Since I'm no expert, I just did a quick check of dependencies using apt (obviously the specifics are a bit Debian centric, but the general trend should hold regardless of system): Depencies list
Do let me know if I'm failing to understand something here, I'm always trying to learn! |
Seems like we have some progress... On my system, version 1.4.5 is installed and when I press If I press |
fwiw I liked the project and it did everything I wanted, but I've moved on to parcellite, which is worse but better because it works. :/ I get that it's OSS and we're all busy people, but I'm honestly pretty confused that this change wasn't just rolled back. "Hotkeys don't work" is a showstopper. |
Where dou you got the 1.4.5 Version from? Have not seen any release yet. |
Please read my ticket's title. |
@CristianHenzel @stefanos82 So I try to increase the POPUP_DELAY, and then every thing ok, amazing. |
I'd like to increase POPUP_DELAY, but failed to compile it from source. |
Try to configure with gtk3
|
Same issue here with Fedora 31, kernel-5.3.13-300, and clipit-1.4.4-5.fc31.x86_64 |
@stefanos82 I recently came across: https://extensions.gnome.org/extension/779/clipboard-indicator/. That has been working pretty well for me. |
I decided to use the XFCE4 clipboard and it's quite easy to use. It has its own history mechanism that you can use much like clipit. All you need to do is to assign it to a hotkey shortcut and that would be it, really. |
Do either of those allow for keeping clipboard and primary in sync ? |
@mckellyln When you say primary, what exactly do you mean? Can you explain it to me please as I'm not a native English speaker? |
Many clipboard managers keep the primary and selection clipboard "in sync" at least as an option. |
I am not sure, it does not seem clear to me from the words above. |
When I hovered over
Does this help a bit more this time? |
Yes, that does seem more like the same as keeping the clipboards in sync. Thanks! |
This is fixed in 1.4.5. |
@afelinczak On GDM 3.36.2 in my case |
Hey, I may prepare second deb package, but for next 2-3 weeks Im very busy and cant promise any date. |
Thank you for your quick answer No problem, we will do as in for a few weeks We're very grateful for your fix, keep your time :) |
@Darcidride uploaded deb file with app indicator flag on. |
@afelinczak Still no icon in my side I'm using this version of clipit from your personal repo (focal version)
Some more information if it can help :
But clipit is working great, I'm using it with shortcuts, just no gdm3 status icon |
hey @Darcidride |
Hi @afelinczak I needed to force install since the semversioning is older than the other one I installed, and I Well, everything is working perfectly in my side, thank you very much for your fix ! |
Did anyone have luck with the fixed package on Ubuntu 19.10? I tried both packages from the launchpad site and both posted on the github release page but no luck - I get a warning that the binding of the hotkeys failed and nothing else - no icon, no error message. |
Im not sure if anyone tested on 19.10 @SuzanaK but from the error message I would check if any other app is not using same hotkeys as clipit. |
yes I used this deb file from above but also this deb file https://github.com/CristianHenzel/ClipIt/releases/download/v1.4.5/clipit_1.4.5_amd64.deb and both from the ppa. None of them worked, I also don't get an icon where I could change the hotkeys. According to the Keyboard Shortcuts, no other application is using e.g. Ctrl+Alt+H which I used for displaying the history. After installing and clicking on "Launch", nothing happens. When I start clipit in the terminal, I get the warning for the hotkeys and then nothing else. |
Please verify all bindings are free: History | Ctrl + Alt + h |
Yes, everyone of those is free. But I don' t think that's the problem - the whole app won't start but there's no error message. |
Sorry, the failure to start had nothing to do with clipit, I had a problem with my display manager. |
@SuzanaK I tried to test this Today, but 19.10 has reached end of life and I was unable to install clipit as ubuntu repos are not active anymore. |
Maybe someone can add a comment on this project readme, under discontinued, to inform that we can use this package instead of moving to another tool |
@Darcidride good idea, I have PR open related to meson, will add note to readme. |
On Debian buster, you need to hold down your shortcut for more time in order for it to be activated (as stated by one of the commenters above). Indeed, it seems the Is there a way to configure |
Since 2018-07-12 that
clipit
got upgraded to version 1.4.4-2, its hotkeys are not working at all.When I press
Ctrl-Alt-F
to openManage History
, it doesn't do anything at all.When I press
Ctrl-Alt-H
to openHistory
, I get the following window:Can we do something about it?
The text was updated successfully, but these errors were encountered: