Your message dated Fri, 6 Jul 2012 16:43:19 +0100
with message-id 
<capq4b8n+5zkqc3qpkrfpwhggxuuc9a5az1kgwy54unk0jq3...@mail.gmail.com>
and subject line Closing orphan/obsolete bugs (emacs21 with tag fixed-upstream)
has caused the Debian Bug report #252243,
regarding emacs21: Keys stop working properly (with careful description and 
steps to reproduce)
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 [email protected]
immediately.)


-- 
252243: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=252243
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: emacs21
Version: 21.3+1-5
Severity: normal

If you put the following ELisp into a file:

--- cut here ---
(mouse-avoidance-mode 'banish)
(setq tooltip-gud-tips-p t)
(menu-bar-mode 0)
--- cut here ---

and then perform these steps:

1. Start emacs with emacs -q -l <file.el>
2. C-x C-f foo.c RET
3. C-x b

you will find that the C-x b, instead of switching buffer, inserts a
"b". Other weird things happen: prefix keystrokes in general stop
working, and if you do "undo" more than once, it will repeatedly undo
and redo the same edit.

Commenting out any one of the three lines in the elisp file fixes the
problem.

I found this problem by whittling down my .emacs.d files; I noticed it
when trying to edit a C++ file (seems to be a problem in c++-mode
too).

This problem seems to be specific to this build: it does not occur in
Emacs 21.3.1 in Fedora Core 2.

Since the symptoms suggest memory corruption to me, I tried running
Emacs under valgrind, but it doesn't work on Emacs as packaged in
Debian (indeed, a thread on emacs-devel from earlier this year showed
that the Emacs developers couldn't get it to work either).

-- System Information:
Debian Release: testing/unstable
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: i386 (i686)
Kernel: Linux 2.4.26
Locale: LANG=en_GB, LC_CTYPE=en_GB

Versions of packages emacs21 depends on:
ii  emacs21-bin-common        21.3+1-5       The GNU Emacs editor's shared, arc
ii  libc6                     2.3.2.ds1-12   GNU C Library: Shared libraries an
ii  libice6                   4.3.0.dfsg.1-1 Inter-Client Exchange library
ii  libjpeg62                 6b-9           The Independent JPEG Group's JPEG 
ii  libncurses5               5.4-3          Shared libraries for terminal hand
ii  libpng12-0                1.2.5.0-6      PNG library - runtime
ii  libsm6                    4.3.0.dfsg.1-1 X Window System Session Management
ii  libtiff3g                 3.5.7-2        Tag Image File Format library
ii  libungif4g                4.1.0b1-6      shared library for GIF images (run
ii  libx11-6                  4.3.0.dfsg.1-1 X Window System protocol client li
ii  libxext6                  4.3.0.dfsg.1-1 X Window System miscellaneous exte
ii  libxmu6                   4.3.0.dfsg.1-1 X Window System miscellaneous util
ii  libxpm4                   4.3.0.dfsg.1-1 X pixmap library
ii  libxt6                    4.3.0.dfsg.1-1 X Toolkit Intrinsics
ii  xaw3dg                    1.5+E-6        Xaw3d widget set
ii  xlibs                     4.3.0.dfsg.1-1 X Window System client libraries m
ii  zlib1g                    1:1.2.1.1-3    compression library - runtime

-- no debconf information


--- End Message ---
--- Begin Message ---
Hello,

Thanks for your interest in improving Debian, and sorry that the bugs
were not fully resolved or closed in due time.

emacs21 packages have been removed from testing in 2009 [1], not
present even in the current stable.  Consequently, these bugs are now
orphan (without maintainer assigned) so they probably will not be
attended/noticed further.

[1] http://packages.qa.debian.org/e/emacs21.html

The bugs deemed valid are going to be verified and reassigned, but the
current bugs that I'm closing now are very ancient (more than 10 years
sometimes) and marked as fixed-upstream years ago, with no recent
input, and are supposed to be fixed in emacs22 at the latest.

Please comment if you want think that some of the raised questions are
still pending and need to be addressed differently (e.g., reassigned
to other packages, etc.).

Cheers.


--- End Message ---

Reply via email to