| Summary: | Kgpg cannot sign files | ||
|---|---|---|---|
| Product: | [Applications] kgpg | Reporter: | cjao |
| Component: | general | Assignee: | Rolf Eike Beer <kde> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | normal | Keywords: | investigated, triaged |
| Priority: | NOR | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Arch Linux | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
|
Description
cjao
2010-06-03 02:14:49 UTC
Please try if you can sign a text using KGpg's editor. If that doesn't work try using "gpg --sign foo". For me all three methods work. I can sign text using the editor and I can sign with "gpg --sign". But "kgpg -S" returns the error I posted above. Please try to build your KGpg from current 4.4 branch (see http://der- dakon.net/blog/KDE/building-kdeutils.html) and run this from gdb: gdb ./kgpg run -S foo When it crashes, stops or quits any other way please call "bt" to get a backtrace. Make sure you quit any other instance of KGpg before starting the one from the debugger. Okay, I just built the latest svn branch of kgpg in debug mode. Here is the GDB output. Unfortunately I can't get a backtrace. Reading symbols from /home/cjao/abs/kgpg/kdeutils/build/kgpg/kgpg...done. (gdb) run -S ~/Desktop/test.txt Starting program: /home/cjao/abs/kgpg/kdeutils/build/kgpg/kgpg -S ~/Desktop/test.txt [Thread debugging using libthread_db enabled] Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString) <unknown program name>(10794)/: Communication problem with "kgpg" , it probably crashed. Error message was: "org.freedesktop.DBus.Error.NoReply" : " "Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken." " Program exited with code 0377. (gdb) bt No stack. I also recently updated to KDE 4.4.4, if that makes a difference. I noticed there is an error in the above command: you need "run --nofork -S foo". Does this still happen with recent versions? Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days, the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please set the bug status as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! |