GNU bug report logs - #1471
23.0.60; Visiting GnuPG-encrypted file yields "file exists, but cannot be read"

Previous Next

Full log

View this message in rfc822 format

From: help-debbugs <at> gnu.org (Emacs bug Tracking System)
To: Eric Hanchrow <eric.hanchrow <at> gmail.com>
Subject: bug#1471 closed by Daiki Ueno <ueno <at> unixuser.org> (Re: bug#1471: 
 23.0.60; Visiting GnuPG-encrypted file yields "file exists, but cannot be 
 read")
Date: Wed, 17 Dec 2008 07:10:21 +0000

[Message part 1 (text/plain, inline)]

This is an automatic notification regarding your bug report
which was filed against the emacs package:

#1471: 23.0.60; Visiting GnuPG-encrypted file yields "file exists, but cannot be read"

It has been closed by Daiki Ueno <ueno <at> unixuser.org>.

Their explanation is attached below along with your original report.
If this explanation is unsatisfactory and you have not received a
better one in a separate message then please contact Daiki Ueno <ueno <at> unixuser.org> by
replying to this email.


-- 
1471: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=1471
Emacs Bug Tracking System
Contact help-debbugs <at> gnu.org with problems

[Message part 2 (message/rfc822, inline)]

From: Daiki Ueno <ueno <at> unixuser.org>
To: Rudi Schlatte <rudi <at> constantly.at>
Cc: 1471-done <at> debbugs.gnu.org
Subject: Re: bug#1471: 23.0.60; Visiting GnuPG-encrypted file yields "file exists, but cannot be read"
Date: Wed, 17 Dec 2008 11:21:35 +0900

>>>>> In <84E12317-4EF9-48A6-9D17-F9ABAB090617 <at> constantly.at> 
>>>>>	Rudi Schlatte <rudi <at> constantly.at> wrote:
> Just as additional datapoint: I saw the reported behavior too, at
> roughly the same time as the original report, but not in an emacs
> compiled from yesterday's git mirror.  Opening a file encrypted with
> gpg works as expected again for me again.

Thanks for the information.  I also got the same report from Eric
privately.  He said that the bug seems like fixed at some time between
the following dates:

Date:   Tue Dec 2 01:12:39 2008 +0000
Date:   Wed Dec 3 21:57:10 2008 +0000

Since I had not added any change (except a wording patch) in that time
span, I suspect other part of Emacs affected the behavior.

Now I'm trying to close this bug.

Regards,
-- 
Daiki Ueno

[Message part 3 (message/rfc822, inline)]

From: Eric Hanchrow <eric.hanchrow <at> gmail.com>
To: emacs-pretest-bug <at> gnu.org
Subject: 23.0.60; Visiting GnuPG-encrypted file yields "file exists, but cannot be read"
Date: Tue, 02 Dec 2008 08:48:54 -0800

Please write in English if possible, because the Emacs maintainers
usually do not have translators to read other languages for them.

Your bug report will be posted to the emacs-pretest-bug <at> gnu.org mailing list.

Please describe exactly what actions triggered the bug
and the precise symptoms of the bug:

At the shell:

  $ cd /usr/local/src/emacs-via-git/src/

create a tiny encrypted file.

  $ echo Fee fi fo fum | gpg --symmetric > decrypt-me.gpg
  gpg: gpg-agent is not available in this session

You can't see it in this transcript, but I typed a very short passphrase: "foo"

Proof that the file is indeed encrypted:

  $ cat decrypt-me.gpg 
  -----BEGIN PGP MESSAGE-----
  Version: GnuPG v1.4.9 (GNU/Linux)

  jA0EAwMCJkAO8t1a89pgySSta9bxO023orfaXtK+Y0RuUP+8ohMfpLLgVlYWiTeN
  sX8mKnE=
  =HGzp
  -----END PGP MESSAGE-----

Proof that I haven't forgotten the passphrase:

  $ gpg --decrypt < decrypt-me.gpg 
  gpg: CAST5 encrypted data
  gpg: gpg-agent is not available in this session
  Enter passphrase:                   gpg: encrypted with 1 passphrase
  Fee fi fo fum
  gpg: WARNING: message was not integrity protected

Now let's visit the file in emacs:
  $ ./emacs -Q -nw

I then typed C-x C-f decrypt-me.gpg RET.  Emacs prompted me for the
passphrase for symmetric encryption, as I'd expect.  I entered it, and
then instead of seeing "Fee fi fo fum" in the buffer, as I'd expected, I
saw an error in the echo area: "File exists, but cannot be read".

If Emacs crashed, and you have the Emacs process in the gdb debugger,
please include the output from the following gdb commands:
    `bt full' and `xbacktrace'.
If you would like to further debug the crash, please read the file
/usr/local/src/emacs-via-git/etc/DEBUG for instructions.


In GNU Emacs 23.0.60.9 (i686-pc-linux-gnu, GTK+ Version 2.14.4)
 of 2008-12-01 on debian
configured using `configure  '--enable-maintainer-mode' '--with-xpm=yes' '--with-jpeg=no' '--with-gif=no' '--with-tiff=no' '--with-xft' '--with-x-toolkit=gtk''

Important settings:
  value of $LC_ALL: nil
  value of $LC_COLLATE: nil
  value of $LC_CTYPE: nil
  value of $LC_MESSAGES: nil
  value of $LC_MONETARY: nil
  value of $LC_NUMERIC: nil
  value of $LC_TIME: nil
  value of $LANG: nil
  value of $XMODIFIERS: nil
  locale-coding-system: utf-8-unix
  default-enable-multibyte-characters: t

Major mode: Emacs-Lisp

Minor modes in effect:
  erc-ring-mode: t
  erc-pcomplete-mode: t
  erc-netsplit-mode: t
  smerge-mode: t
  eldoc-mode: t
  erc-button-mode: t
  erc-fill-mode: t
  erc-stamp-mode: t
  erc-autojoin-mode: t
  erc-track-mode: t
  erc-track-minor-mode: t
  erc-match-mode: t
  erc-log-mode: t
  erc-services-mode: t
  erc-networks-mode: t
  erc-irccontrols-mode: t
  erc-noncommands-mode: t
  erc-readonly-mode: t
  desktop-save-mode: t
  recentf-mode: t
  display-time-mode: t
  global-auto-revert-mode: t
  diff-auto-refine-mode: t
  shell-dirtrack-mode: t
  iswitchb-mode: t
  tooltip-mode: t
  mouse-wheel-mode: t
  file-name-shadow-mode: t
  global-font-lock-mode: t
  font-lock-mode: t
  global-auto-composition-mode: t
  auto-composition-mode: t
  auto-encryption-mode: t
  auto-compression-mode: t
  line-number-mode: t
  transient-mark-mode: t

Recent input:
RET C-x k RET ESC x r e p o r t - e m a c s - b TAB 
RET C-g C-x b i n i RET ESC < C-s g p g C-s C-s C-s 
C-s C-a C-s e a s y C-s C-a ESC x ESC p RET

Recent messages:
Partially completed
/home/erich/private/: 0% (0/19181)
File exists, but cannot be read
/home/erich/private/: 0% (0/19181)
File exists, but cannot be read
/home/erich/private/: 0% (0/19181)
File exists, but cannot be read
Quit
Mark set
Mark saved where search started [2 times]

-- 
If you can't change your underwear, can you be sure you have any?

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.