SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I just did a fresh install of Slackware 11 a few days ago. I have my home directory on another partition so my personal data is the same from when I was running slackware 10.2.
I started up KGPG and created a new public/private key pair.
I can do everything in KGPG as before expect I can't decrypt the contents of the clipboard. For example, I encrypt some text in the editor provided with KGPG, I then try to decrypt it. After I type in my passphrase KGPG crahses and KDE 3.5 gives me the error output. I don't have that output with me at the moment but I can post it later.
Has anyone else had this problem with KGPG in Slackware 11?
Note, GPG decrypts the encrypted text fine on the command line.
Yes I see the same crash when I encrypt a piece of text in the editor with my own public key and then try to decrypt it. After I type my GPG passphrase, Kgpg crashes.
This is a known kgpg bug. It's fixed in KDE 3.5.5. Don't have the link handy at present, but I looked it up a few days back. Don't know what would be involved in a Slackware 11.0 patch.
This is a known kgpg bug. It's fixed in KDE 3.5.5. Don't have the link handy at present, but I looked it up a few days back. Don't know what would be involved in a Slackware 11.0 patch.
Cool, thanks for the reply. I plan to install slapt-get soon so when I do that I can upgrade kde to 3.5.5 from the "current" folder on the slackware FTP sites.
This is a known kgpg bug. It's fixed in KDE 3.5.5. Don't have the link handy at present, but I looked it up a few days back. Don't know what would be involved in a Slackware 11.0 patch.
Definitely fixed in 3.5.5 it used to annoy the hell out of me one thing you do can as a work around is use kgpg -s encryped_file from the command line to get the file in the editor then it decrypts/encrypts fine.
Definitely fixed in 3.5.5 it used to annoy the hell out of me one thing you do can as a work around is use kgpg -s encryped_file from the command line to get the file in the editor then it decrypts/encrypts fine.
Thanks for the tip. Slackware-current isn't updated with KDE 3.5.5 yet so this will help nicely.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.