Bug 417389 - security/kleopatra: Right click entries are greyed out
Summary: security/kleopatra: Right click entries are greyed out
Status: RESOLVED DUPLICATE of bug 415168
Alias: None
Product: kleopatra
Classification: Applications
Component: general (show other bugs)
Version: 3.1.8
Platform: Other FreeBSD
: NOR normal
Target Milestone: ---
Assignee: Andre Heinecke
URL: https://bugs.freebsd.org/bugzilla/sho...
Keywords:
Depends on:
Blocks:
 
Reported: 2020-02-10 15:31 UTC by Gerard Seibert
Modified: 2020-02-12 11:19 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Gerard Seibert 2020-02-10 15:31:15 UTC
SUMMARY
Right-clicking on an item shows all the options greyed out and unusable


STEPS TO REPRODUCE
1. Start Kleopatra
2. Right-click on an item
3. 

OBSERVED RESULT
Items greyed out

EXPECTED RESULT
Choices would be selectable

Operating System: FreeBSD 11.3
KDE Plasma Version: 5.17.5
KDE Frameworks Version: 5.66.0
Qt Version: 5.13.2
Kernel Version: 11.3-RELEASE-p6
OS Type: 64-bit
Processors: 4 × ACPI CPU
Memory: 31.7 GiB of RAM


ADDITIONAL INFORMATION
Comment 1 Andre Heinecke 2020-02-11 07:51:51 UTC
Items are greyed out if they do not apply to a specific key. For example if it is S/MIME OpenPGP Options are greyed out or the secret key options are unavailable if you only have the public key.

For general support the best mailing lists etc. for Kleopatra is the Gpg4win community. Even if you are on FreeBSD Gpg4win users are Kleopatra users. https://www.gpg4win.org/community.html
Comment 2 Gerard Seibert 2020-02-11 17:34:41 UTC
(In reply to Andre Heinecke from comment #1)

Every item is greyed out. Even my own key elicits a greyed out response when right-clicked on. Interestingly enough, I have Kleopatra installed on a Win 10 machine, and it is working perfectly. The problem is specific, in most likelihood, to FreeBSD. I doubt that reporting it to the Windows community will help, but I'll give it a try.
Comment 3 groot 2020-02-11 21:34:33 UTC
Downstream bug is https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=242670 ; I never did get around to checking the RMB behavior.
Comment 4 Andre Heinecke 2020-02-12 08:45:50 UTC
Thanks Adrian,

in that case indeed it is correct to have an issue here. I thought this was user confusion at first from the very short report.

@Gerard in that case it makes indeed no sense to communicate it to the KDE Windows community, I was just pointing you there for user support.

Can you please enable debug output. E.g. by creating a file with the content

[Rules]
org.kde.pim.*=true


And put the path to this file in the environment variable: QT_LOGGING_CONF and start Kleopatra from the command line to see the debug output and paste it here. This might point me in the right direction. On the top of my hat I can't think of a reason why all items should be disabled when the keylisting works in general.
Comment 5 Christophe Marin 2020-02-12 09:01:07 UTC
(In reply to Andre Heinecke from comment #4)
> Thanks Adrian,
> 
> in that case indeed it is correct to have an issue here. I thought this was
> user confusion at first from the very short report.
> 
> @Gerard in that case it makes indeed no sense to communicate it to the KDE
> Windows community, I was just pointing you there for user support.
> 
> Can you please enable debug output. E.g. by creating a file with the content
> 
> [Rules]
> org.kde.pim.*=true
> 
> 
> And put the path to this file in the environment variable: QT_LOGGING_CONF
> and start Kleopatra from the command line to see the debug output and paste
> it here. This might point me in the right direction. On the top of my hat I
> can't think of a reason why all items should be disabled when the keylisting
> works in general.

Using kdebugsettings will do the same thing :)
Comment 6 Gerard Seibert 2020-02-12 10:37:49 UTC
(In reply to Andre Heinecke from comment #4)

I followed your instructions and started Kleopatra from the command line. I proceeded to highlight an entry, my own one, and right-click on the item. As usual, all of the choices were greyed out. I then closed the program. This is the output displayed.

/usr/home/gerard $ kleopatra       
org.kde.pim.libkleo: adding
  "/home/gerard/.gnupg" 
/end
org.kde.pim.kleopatra: Startup timing: 0 ms elapsed: Service created
org.kde.pim.libkleo: adding
  "/home/gerard/.gnupg\n /home/gerard/.gnupg/gpg.conf\n /home/gerard/.gnupg/pubring.kbx\n /home/gerard/.gnupg/trustdb.gpg\n /home/gerard/.gnupg/trustlist.txt" 
/end
org.kde.pim.kleopatra: Startup timing: 293 ms elapsed: Application initialized
org.kde.pim.kleopatra: Startup timing: 293 ms elapsed: Application created
org.kde.pim.kleopatra: Startup timing: 293 ms elapsed: GPGME Initialized
org.kde.pim.kleopatra: gpgConfListDir: starting  /usr/local/bin/gpgconf  --list-dirs
org.kde.pim.kleopatra: gpgConfListDir: found  /usr/local/bin  for ' bindir 'entry
org.kde.pim.kleopatra: Startup timing: 323 ms elapsed: UiServer created
org.kde.pim.kleopatra: Startup timing: 324 ms elapsed: UiServer started
org.kde.pim.kleopatra: Checking gpg installation...
org.kde.pim.kleopatra: Checking gpgsm installation...
org.kde.pim.kleopatra: Checking gpgconf installation...
org.kde.pim.kleopatra: Checking configuration of:
org.kde.pim.kleopatra: Checking configuration of: gpg
org.kde.pim.kleopatra: Checking configuration of: gpg-agent
org.kde.pim.kleopatra: Checking configuration of: scdaemon
org.kde.pim.kleopatra: Checking configuration of: gpgsm
org.kde.pim.kleopatra: Checking configuration of: dirmngr
org.kde.pim.kleopatra: Parsed 2.2.19 as:  2 . 2 . 19 .
org.kde.pim.kleopatra: ArchiveDefinition[ "tar" ] ("tar", "cf", "-", "--null", "-T-")
org.kde.pim.kleopatra: ArchiveDefinition[ "tar" ] find -print0 |  "/usr/bin/tar" ("cf", "-", "--null", "-T-")
org.kde.pim.kleopatra: ArchiveDefinition[ "tar" ] ("tar", "cfz", "-", "--null", "-T-")
org.kde.pim.kleopatra: ArchiveDefinition[ "tar" ] find -print0 |  "/usr/bin/tar" ("cfz", "-", "--null", "-T-")
org.kde.pim.kleopatra: ArchiveDefinition[ "tar" ] ("tar", "xf", "-")
org.kde.pim.kleopatra: ArchiveDefinition[ "tar" ] "/usr/bin/tar" ("xf", "-") "%f" ()
org.kde.pim.kleopatra: ArchiveDefinition[ "tar" ] ("tar", "xfz", "-")
org.kde.pim.kleopatra: ArchiveDefinition[ "tar" ] "/usr/bin/tar" ("xfz", "-") "%f" ()
org.kde.pim.kleopatra: ArchiveDefinition[ "bzip2" ] ("tar", "cfj", "-", "--null", "-T-")
org.kde.pim.kleopatra: ArchiveDefinition[ "bzip2" ] find -print0 |  "/usr/bin/tar" ("cfj", "-", "--null", "-T-")
org.kde.pim.kleopatra: ArchiveDefinition[ "bzip2" ] ("tar", "cfj", "-", "--null", "-T-")
org.kde.pim.kleopatra: ArchiveDefinition[ "bzip2" ] find -print0 |  "/usr/bin/tar" ("cfj", "-", "--null", "-T-")
org.kde.pim.kleopatra: ArchiveDefinition[ "bzip2" ] ("tar", "xfj", "-")
org.kde.pim.kleopatra: ArchiveDefinition[ "bzip2" ] "/usr/bin/tar" ("xfj", "-") "%f" ()
org.kde.pim.kleopatra: ArchiveDefinition[ "bzip2" ] ("tar", "xfj", "-")
org.kde.pim.kleopatra: ArchiveDefinition[ "bzip2" ] "/usr/bin/tar" ("xfj", "-") "%f" ()
org.kde.pim.libkleo: ChecksumDefinition[ "sha256sum" ] ("xargs", "-0", "gsha256sum", "--")
org.kde.pim.libkleo: ChecksumDefinition[ "sha256sum" ] find -print0 |  "/usr/bin/xargs" ("-0", "gsha256sum", "--")
org.kde.pim.libkleo: ChecksumDefinition[ "sha256sum" ] ("gsha256sum", "-c", "--")
org.kde.pim.libkleo: ChecksumDefinition[ "sha256sum" ] "/usr/local/bin/gsha256sum" ("-c", "--") "%f" ()
org.kde.pim.libkleo: ChecksumDefinition[ "sha1sum" ] ("xargs", "-0", "gsha1sum", "--")
org.kde.pim.libkleo: ChecksumDefinition[ "sha1sum" ] find -print0 |  "/usr/bin/xargs" ("-0", "gsha1sum", "--")
org.kde.pim.libkleo: ChecksumDefinition[ "sha1sum" ] ("gsha1sum", "-c", "--")
org.kde.pim.libkleo: ChecksumDefinition[ "sha1sum" ] "/usr/local/bin/gsha1sum" ("-c", "--") "%f" ()
org.kde.pim.libkleo: ChecksumDefinition[ "sha512sum" ] ("xargs", "-0", "gsha512sum", "--")
org.kde.pim.libkleo: ChecksumDefinition[ "sha512sum" ] find -print0 |  "/usr/bin/xargs" ("-0", "gsha512sum", "--")
org.kde.pim.libkleo: ChecksumDefinition[ "sha512sum" ] ("gsha512sum", "-c", "--")
org.kde.pim.libkleo: ChecksumDefinition[ "sha512sum" ] "/usr/local/bin/gsha512sum" ("-c", "--") "%f" ()
org.kde.pim.libkleo: ChecksumDefinition[ "md5sum" ] ("xargs", "-0", "gmd5sum", "--")
org.kde.pim.libkleo: ChecksumDefinition[ "md5sum" ] find -print0 |  "/usr/bin/xargs" ("-0", "gmd5sum", "--")
org.kde.pim.libkleo: ChecksumDefinition[ "md5sum" ] ("gmd5sum", "-c", "--")
org.kde.pim.libkleo: ChecksumDefinition[ "md5sum" ] "/usr/local/bin/gmd5sum" ("-c", "--") "%f" ()
org.kde.pim.kleopatra:
org.kde.pim.kleopatra:
org.kde.pim.kleopatra: Startup timing: 1750 ms elapsed: SelfCheck completed
org.kde.pim.kleopatra: openOrRaiseMainWindow
org.kde.pim.kleopatra: ReaderStatusThread[2nd]: new iteration command= "__update__"  ; nullSlot= true
org.kde.pim.kleopatra: get_card_status( 0 , 0x81fc0d030 )
org.kde.pim.kleopatra: gpgagent_transact( SCD SERIALNO )
org.kde.pim.kleopatra: gpgagent_transact( SCD SERIALNO ): "Operation not supported by device"
org.kde.pim.kleopatra: agent_getattr_status( SCD SERIALNO ): t == NULL
org.kde.pim.kleopatra: ReaderStatusThread[2nd]: slot 0 : card Changed
org.kde.pim.kleopatra: ReaderStatusThread[2nd]: waiting for commands
org.kde.pim.libkleo: final filter count is 16
org.kde.pim.kleopatra: you need to register view QTreeView(0x81fe3fc40, name="m_view") before trying to set it as the current view!
org.kde.pim.kleopatra: Startup timing: 1848 ms elapsed: new instance created
org.kde.pim.kleopatra:
org.kde.pim.kleopatra:
org.kde.pim.kleopatra: invalid model
org.kde.pim.kleopatra:
org.kde.pim.kleopatra: 0x81fe3fc40
org.kde.pim.kleopatra: ReaderStatusThread[2nd]: new iteration command= "__quit__"  ; nullSlot= true
Comment 7 Andre Heinecke 2020-02-12 11:03:18 UTC
Thanks, someone in my office is also using FreeBSD and I was able to see the same behavior on his system so I can debug / analyze it here.
Comment 8 Andre Heinecke 2020-02-12 11:19:37 UTC
It's the "invalid model" in the debug output that is the issue here and that has the same reason as the crash in 415168 so I'm closing this as duplicate to have the discussion only in one place.

*** This bug has been marked as a duplicate of bug 415168 ***