[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#485456: marked as done (kmail: S/Mime signature fails)

Your message dated Thu, 18 Jan 2018 16:02:03 +0100
with message-id 
and subject line Re: kmail: S/Mime signature fails
has caused the Debian Bug report #485456,
regarding kmail: S/Mime signature fails
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
485456: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=485456
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: kmail
Version: 4:3.5.9-2
Severity: normal

I just tried to sign messages with Kmail using S/Mime. When trying to
send a message it says:

"Signing failed: General error"
Clicking the "Show Audit Log" button triggers
"No GnuPG Audit Log available for this operation."

In the account setup I have specified a key for S/Mime signing and in 
the cryptographic preferences the gpgsm module with S/Mime support in
enabled.

I have no idea if the following commandline output might be related to
the problem:
dirmngr[11613]: error opening
`/home/dave/.gnupg/dirmngr_ldapservers.conf': No such file or directory
gpgconf: warning: can not open list file
/home/dave/.gnupg/dirmngr_ldapservers.conf: No such file or directory


Any help is appreciated. I also reported this bug in the KDE bugtracker:
http://bugs.kde.org/show_bug.cgi?id=163638

- David


-- System Information:
Debian Release: lenny/sid
  APT prefers testing
  APT policy: (600, 'testing'), (300, 'unstable'), (250, 'experimental')
Architecture: i386 (i686)

Kernel: Linux 2.6.25-2-686 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages kmail depends on:
ii  kdebase-kio-plugins  4:3.5.9.dfsg.1-2+b1 core I/O slaves for KDE
ii  kdelibs4c2a          4:3.5.9.dfsg.1-4    core libraries and binaries for al
ii  kdepim-kio-plugins   4:3.5.9-2           KDE pim I/O Slaves
ii  libart-2.0-2         2.3.20-2            Library of functions for 2D graphi
ii  libaudio2            1.9.1-2             Network Audio System - shared libr
ii  libc6                2.7-10              GNU C Library: Shared libraries
ii  libfontconfig1       2.5.0-2             generic font configuration library
ii  libfreetype6         2.3.5-1+b1          FreeType 2 font engine, shared lib
ii  libgcc1              1:4.3.0-5           GCC support library
ii  libice6              2:1.0.4-1           X11 Inter-Client Exchange library
ii  libidn11             1.8-1               GNU libidn library, implementation
ii  libjpeg62            6b-14               The Independent JPEG Group's JPEG 
ii  libkcal2b            4:3.5.9-2           KDE calendaring library
ii  libkdepim1a          4:3.5.9-2           KDE PIM library
ii  libkleopatra1        4:3.5.9-2           KDE GnuPG interface libraries
ii  libkmime2            4:3.5.9-2           KDE MIME interface library
ii  libkpimidentities1   4:3.5.9-2           KDE PIM user identity information 
ii  libksieve0           4:3.5.9-2           KDE mail/news message filtering li
ii  libmimelib1c2a       4:3.5.9-2           KDE mime library
ii  libpng12-0           1.2.27-1            PNG library - runtime
ii  libqt3-mt            3:3.3.8b-5          Qt GUI Library (Threaded runtime v
ii  libsm6               2:1.0.3-1+b1        X11 Session Management library
ii  libstdc++6           4.3.0-5             The GNU Standard C++ Library v3
ii  libx11-6             2:1.0.3-7           X11 client-side library
ii  libxcursor1          1:1.1.9-1           X cursor management library
ii  libxext6             2:1.0.4-1           X11 miscellaneous extension librar
ii  libxft2              2.1.12-2            FreeType-based font drawing librar
ii  libxi6               2:1.1.3-1           X11 Input extension library
ii  libxinerama1         2:1.0.3-2           X11 Xinerama extension library
ii  libxrandr2           2:1.2.2-2           X11 RandR extension library
ii  libxrender1          1:0.9.4-1           X Rendering Extension client libra
ii  libxt6               1:1.0.5-3           X11 toolkit intrinsics library
ii  perl                 5.10.0-10           Larry Wall's Practical Extraction 
ii  zlib1g               1:1.2.3.3.dfsg-12   compression library - runtime

Versions of packages kmail recommends:
pn  procmail                      <none>     (no description available)

-- no debconf information

--- End Message ---
--- Begin Message --- 
Dear bug submitter,

Thank you for reporthing this issue.  The bug has been determined not to be
Debian specific, and therefore was reported in the KDE bugtracker; see
https://bugs.kde.org/show_bug.cgi?id=163638.

We are sorry it has not been resolved.  However, the version in which the
issue was reported is now obsolete and the upstream tracker has closed the
issue. Thus we are also closing the issue in Debian bug tracker.

If you think the bug is still relevant to a KDE Pim version in Debian stable
(aka Stretch) or newer -- i.e. part of KDE Applications 15.08.0 or newer --
then please open a new bugreport upstream and add your new information in the
upstream bugreport.

Again, thank you for reporting the issue. If there are any questions feel free
to ask.

KDE upstream bug tracker closed their bug with following statement:

"This bug has only been reported for versions before 15.08.0, which have been
unsupported for at least two years now. Can anyone tell if this bug still
present?

If noone confirms this bug for a Framework-based version of kontact
(version 5.0 or later, as part of KDE Applications 15.08 or later),
it gets closed in about three months.

Just as announced in my last comment, I close this bug.
If you encounter it again in a recent version (at least 5.0 aka 15.08),
please open a new one unless it already exists. Thank you for all your input."

--- End Message ---
Reply to: