Your message dated Tue, 20 May 2014 10:44:19 -0700 (PDT)
with message-id <[email protected]>
and subject line Re: Bug#254620
has caused the Debian Bug report #254620,
regarding emacs21: server for emacsclient dies every few minutes
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.)
--
254620: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=254620
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: emacs21
Version: 21.3+1-5
Severity: normal
Subject: emacs21: server for emacsclient dies every few minutes
Package: emacs21
Version: 21.3+1-5
Severity: normal
It seems that the server for emacsclient on my computer has been dying
from a few minutes to half an hour after it starts, since about a week
ago. I have to do "M-x server-start" to restart it. There is never
anything in *Messages* related to this, and I'm not sure what else I
can do to debug the problem since I'm not experienced with elisp. I've
tried uninstalling and reinstalling emacs, and the problem persists.
Even if the direct cause is something unrelated to emacs, I think it
is a bug that more troubleshooting information is not provided to the
user when problems occur.
-- System Information:
Debian Release: testing/unstable
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing')
Architecture: i386 (i686)
Kernel: Linux 2.6.2-1-686
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8
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-13 GNU C Library: Shared libraries an
ii libice6 4.3.0.dfsg.1-4 Inter-Client Exchange library
ii libjpeg62 6b-9 The Independent JPEG Group's JPEG
ii libncurses5 5.4-4 Shared libraries for terminal hand
ii libpng12-0 1.2.5.0-6 PNG library - runtime
ii libsm6 4.3.0.dfsg.1-4 X Window System Session Management
ii libtiff3g 3.6.1-1 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-4 X Window System protocol client li
ii libxext6 4.3.0.dfsg.1-4 X Window System miscellaneous exte
ii libxmu6 4.3.0.dfsg.1-4 X Window System miscellaneous util
ii libxpm4 4.3.0.dfsg.1-4 X pixmap library
ii libxt6 4.3.0.dfsg.1-4 X Toolkit Intrinsics
ii xaw3dg 1.5+E-6 Xaw3d widget set
ii xlibs 4.3.0.dfsg.1-4 X Window System client libraries m
ii zlib1g 1:1.2.1.1-3 compression library - runtime
-- no debconf information
-- System Information:
Debian Release: testing/unstable
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing')
Architecture: i386 (i686)
Kernel: Linux 2.6.2-1-686
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8
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-13 GNU C Library: Shared libraries an
ii libice6 4.3.0.dfsg.1-4 Inter-Client Exchange library
ii libjpeg62 6b-9 The Independent JPEG Group's JPEG
ii libncurses5 5.4-4 Shared libraries for terminal hand
ii libpng12-0 1.2.5.0-6 PNG library - runtime
ii libsm6 4.3.0.dfsg.1-4 X Window System Session Management
ii libtiff3g 3.6.1-1 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-4 X Window System protocol client li
ii libxext6 4.3.0.dfsg.1-4 X Window System miscellaneous exte
ii libxmu6 4.3.0.dfsg.1-4 X Window System miscellaneous util
ii libxpm4 4.3.0.dfsg.1-4 X pixmap library
ii libxt6 4.3.0.dfsg.1-4 X Toolkit Intrinsics
ii xaw3dg 1.5+E-6 Xaw3d widget set
ii xlibs 4.3.0.dfsg.1-4 X Window System client libraries m
ii zlib1g 1:1.2.1.1-3 compression library - runtime
-- no debconf information
--- End Message ---
--- Begin Message ---
So much time has passed that this report is not useful any more, sorry.
If it is still a problem with the current release, 24.3, I suggest making
a new report directly with upstream.
--- End Message ---