Bug#477770: [PATCH] improve SIGINT handling
From: Nathaniel W. Turner n...@houseofnate.net
This addresses the case where a Ctrl-C is intended for a process running
in the chroot; before, schroot would always exit without cleaning up
(the most visible symptom being left-over bind-mounts in
/var/lib/schroot/mount). Now, cleanup occurs, and an appropriate error
message is displayed (E: Child terminated by signal ‘Interrupt’).
This patch does not cover all the cases described by bug 40, but I
think it is a step in the right direction.
Bug-Debian: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=40
Signed-off-by: Nathaniel W. Turner n...@houseofnate.net
---
sbuild/sbuild-session.cc | 52 +-
sbuild/sbuild-session.h | 16 ++
2 files changed, 67 insertions(+), 1 deletions(-)
diff --git a/sbuild/sbuild-session.cc b/sbuild/sbuild-session.cc
index 9d83ca1..685a0bd 100644
--- a/sbuild/sbuild-session.cc
+++ b/sbuild/sbuild-session.cc
@@ -184,6 +184,7 @@ namespace
}
volatile bool sighup_called = false;
+ volatile bool sigint_called = false;
volatile bool sigterm_called = false;
/**
@@ -199,6 +200,29 @@ namespace
}
/**
+ * Handle the SIGINT signal.
+ *
+ * @param ignore the signal number.
+ *
+ * We explicitly do nothing with SIGINT, and rely on the exit status of child
+ * processes to determine if we should care. We want to make sure any child
+ * process (which will also have received SIGINT) has exited before we do
+ * anything, and some child processes (for example, emacs) may expect SIGINT
+ * during normal operation. See http://www.cons.org/cracauer/sigint.html for
+ * a good discussion of SIGINT handling.
+ */
+ void
+ sigint_handler (int ignore)
+ {
+/*
+ * Allows us to detect if an interrupted waitpid() was interrupted due to
+ * SIGINT or something else. We may also want to use this at exit time to
+ * see if we should re-kill ourselves with SIGINT.
+ */
+sigint_called = true;
+ }
+
+ /**
* Handle the SIGTERM signal.
*
* @param ignore the signal number.
@@ -242,6 +266,7 @@ session::session (std::string const service,
session_id(),
force(false),
saved_sighup_signal(),
+ saved_sigint_signal(),
saved_sigterm_signal(),
saved_termios(),
termios_ok(false),
@@ -571,6 +596,8 @@ session::run_impl ()
{
sighup_called = false;
set_sighup_handler();
+ sigint_called = false;
+ set_sigint_handler();
sigterm_called = false;
set_sigterm_handler();
@@ -695,6 +722,7 @@ session::run_impl ()
catch (error const e)
{
clear_sigterm_handler();
+ clear_sigint_handler();
clear_sighup_handler();
/* If a command was not run, but something failed, the exit
@@ -705,6 +733,7 @@ session::run_impl ()
}
clear_sigterm_handler();
+ clear_sigint_handler();
clear_sighup_handler();
}
@@ -1268,6 +1297,14 @@ session::wait_for_child (pid_t pid,
while (1)
{
+ /*
+ * If we (the parent process) gets SIGHUP or SIGTERM, pass this signal on
+ * to the child (once). Note that we do not handle SIGINT this way,
+ * because when a user presses Ctrl-C, the SIGINT is sent to all
+ * processes attached to that TTY (so the child will already have gotten
+ * it). In any case, once the child gets the signal, we just have to
+ * continue waiting for it to exit.
+ */
if ((sighup_called || sigterm_called) !child_killed)
{
if (sighup_called)
@@ -1290,7 +1327,7 @@ session::wait_for_child (pid_t pid,
if (waitpid(pid, status, 0) == -1)
{
- if (errno == EINTR (sighup_called || sigterm_called))
+ if (errno == EINTR (sighup_called || sigterm_called ||
sigint_called))
continue; // Kill child and wait again.
else
throw error(CHILD_WAIT, strerror(errno));
@@ -1305,6 +1342,7 @@ session::wait_for_child (pid_t pid,
sigterm_called = false;
throw error(SIGNAL_CATCH, strsignal(SIGTERM));
}
+ /* no need to handle the SIGINT case here; it is handled correctly below
*/
else
break;
}
@@ -1372,6 +1410,18 @@ session::clear_sighup_handler ()
}
void
+session::set_sigint_handler ()
+{
+ set_signal_handler(SIGINT, this-saved_sigint_signal, sigint_handler);
+}
+
+void
+session::clear_sigint_handler ()
+{
+ clear_signal_handler(SIGINT, this-saved_sigint_signal);
+}
+
+void
session::set_sigterm_handler ()
{
set_signal_handler(SIGTERM, this-saved_sigterm_signal, sigterm_handler);
diff --git a/sbuild/sbuild-session.h b/sbuild/sbuild-session.h
index 888fbfe..9179a29 100644
--- a/sbuild/sbuild-session.h
+++ b/sbuild/sbuild-session.h
@@ -417,6 +417,20 @@ namespace sbuild
clear_sighup_handler ();
/**
+ * Set the SIGINT handler.
+ *
+ * An error will be thrown on failure.
+ */
+void
+set_sigint_handler
Bug#401482: vdso patch doesn't work against 2.6.18.dfsg.1-13etch1
Hi Sam, I found this problem in the stock upstream 2.6.18.8 kernel, and for me the fix involved the following: 1. apply the attached patch (taken from the RHEL 5 kernel source package) 2. build the kernel with CONFIG_COMPAT_VDSO disabled 3. use an older version of gcc (I had been testing with 6.6; stock 6.4 worked) Without all of those things, I would usually see useless stack traces when attaching to running processes or analyzing core dumps of multithreaded programs. (The original RedHat patch, linux-2.6-misc-fix-vdso-in-core-dumps.patch, does not apply cleanly to a stock kernel, so I've also attached the same patch with conflicts against a stock 2.6.18.8 kernel resolved as fix-vdso-in-core-dumps-rediff.patch.) I'd be interested to see if these steps solve this problem for you with a Debian etch kernel. Nate -- Nathaniel W. Turner http://aardvarque.com/ linux-2.6-misc-fix-vdso-in-core-dumps.patch Description: Binary data fix-vdso-in-core-dumps-rediff.patch Description: Binary data
Bug#356304: NMU patch
Thank you for the NMU. If I can't make more time for konversation soon, I'll file an RFA. Martin Michlmayr wrote: tags 356304 + pending thanks I've uploaded the following NMU to delayed-2. diff -u konversation-0.19/debian/changelog konversation-0.19/debian/changelog --- konversation-0.19/debian/changelog +++ konversation-0.19/debian/changelog @@ -1,3 +1,11 @@ +konversation (0.19-1.1) unstable; urgency=low + + * NMU as part of the GCC 4.1 transition. + * patches/debian_01_channel.diff: Remove extra qualification from C++ +header file. (Closes: #356304) + + -- Martin Michlmayr [EMAIL PROTECTED] Thu, 25 May 2006 21:55:25 +0200 + konversation (0.19-1) unstable; urgency=low * New upstream release. (Closes: #350562) only in patch2: unchanged: --- konversation-0.19.orig/debian/patches/debian_02_gcc41.diff +++ konversation-0.19/debian/patches/debian_02_gcc41.diff @@ -0,0 +1,12 @@ +--- a/konversation/src/searchbar.h~2006-03-11 00:24:00.0 + b/konversation/src/searchbar.h 2006-03-11 00:24:04.0 + +@@ -55,7 +55,7 @@ + + void focusInEvent(QFocusEvent* e); + virtual void showEvent(QShowEvent* e); +-bool SearchBar::focusedChild(); ++bool focusedChild(); + public slots: + + virtual void hide(); + -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#348747: [pkg-fetchmail-maint] Bug#348747: fetchmail: segfault when submitting dsn to local postmaster
On Wednesday 18 January 2006 9:59 pm, Matthias Andree wrote: Turns out we need a 2nd patch to fix a 2nd occurrence of this bug. This patch goes on top of the previous. Thank you for the quick response. Your patches do indeed fix the problem I was seeing. Cheers, nate -- Nathaniel W. Turner http://houseofnate.net/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#348747: fetchmail: segfault when submitting dsn to local postmaster
Package: fetchmail Version: 6.3.1-4 Severity: important After upgrading to 6.3.1-4, fetchmail dies with a segmentation fault after trying to process the first message. The transcript of the session, a sanitized fetchmailrc, and the message in question are attached to this report. -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.14-2-k7 Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Versions of packages fetchmail depends on: ii adduser 3.80 Add and remove users and groups ii debianutils 2.15.1 Miscellaneous utilities specific t ii gettext 0.14.5-2 GNU Internationalization utilities ii libc6 2.3.5-8.1 GNU C Library: Shared libraries an ii libssl0.9.8 0.9.8a-5 SSL shared libraries Versions of packages fetchmail recommends: ii ca-certificates 20050804 Common CA Certificates PEM files -- no debconf information # vim: syn=fetchmail set postmaster [EMAIL PROTECTED] set nobouncemail set no spambounce poll mail63.csoft.net with proto IMAP envelope Delivered-To qvirtual canprev-cancerprev.org- localdomains cancerprev.org user 'canprev' there with password 'XXX' is 'journal' '*' here options fetchall forcecr 14:22:39 [EMAIL PROTECTED](~)$ sudo -u fetchmail -H fetchmail - -f /etc/fetchmailrc fetchmail: removing stale lockfile fetchmail: 6.3.1 querying mail63.csoft.net (protocol IMAP) at Wed 18 Jan 2006 02:23:03 PM EST: poll started fetchmail: IMAP * OK [CAPABILITY IMAP4rev1 UIDPLUS CHILDREN NAMESPACE THREAD=ORDEREDSUBJECT THREAD=REFERENCES SORT QUOTA IDLE ACL ACL2=UNION XCOURIEROUTBOX=INBOX.Outbox] Courier-IMAP ready. Copyright 1998-2004 Double Precision, Inc. See COPYING for distribution information. fetchmail: IMAP A0001 CAPABILITY fetchmail: IMAP * CAPABILITY IMAP4rev1 UIDPLUS CHILDREN NAMESPACE THREAD=ORDEREDSUBJECT THREAD=REFERENCES SORT QUOTA IDLE ACL ACL2=UNION XCOURIEROUTBOX=INBOX.Outbox fetchmail: IMAP A0001 OK CAPABILITY completed fetchmail: Protocol identified as IMAP4 rev 1 fetchmail: IMAP A0002 LOGIN canprev * fetchmail: IMAP A0002 OK LOGIN Ok. fetchmail: selecting or re-polling default folder fetchmail: IMAP A0003 SELECT INBOX fetchmail: IMAP * FLAGS (\Draft \Answered \Flagged \Deleted \Seen \Recent) fetchmail: IMAP * OK [PERMANENTFLAGS (\Draft \Answered \Flagged \Deleted \Seen)] Limited fetchmail: IMAP * 8946 EXISTS fetchmail: IMAP * 0 RECENT fetchmail: IMAP * OK [UIDVALIDITY 1136513867] Ok fetchmail: IMAP * OK [MYRIGHTS acdilrsw] ACL fetchmail: IMAP A0003 OK [READ-WRITE] Ok fetchmail: 8946 messages waiting after first poll fetchmail: IMAP A0004 EXPUNGE fetchmail: IMAP A0004 OK EXPUNGE completed fetchmail: 8946 messages waiting after expunge 8946 messages for canprev at mail63.csoft.net. fetchmail: IMAP A0005 FETCH 1:100 RFC822.SIZE fetchmail: IMAP * 1 FETCH (RFC822.SIZE 14972) fetchmail: IMAP * 2 FETCH (RFC822.SIZE 3064) fetchmail: IMAP * 3 FETCH (RFC822.SIZE 2116) fetchmail: IMAP * 4 FETCH (RFC822.SIZE 880) fetchmail: IMAP * 5 FETCH (RFC822.SIZE 3120) fetchmail: IMAP * 6 FETCH (RFC822.SIZE 1011) fetchmail: IMAP * 7 FETCH (RFC822.SIZE 15323) fetchmail: IMAP * 8 FETCH (RFC822.SIZE 2002) fetchmail: IMAP * 9 FETCH (RFC822.SIZE 11581) fetchmail: IMAP * 10 FETCH (RFC822.SIZE 840) fetchmail: IMAP * 11 FETCH (RFC822.SIZE 3727) fetchmail: IMAP * 12 FETCH (RFC822.SIZE 2766) fetchmail: IMAP * 13 FETCH (RFC822.SIZE 1977) fetchmail: IMAP * 14 FETCH (RFC822.SIZE 826) fetchmail: IMAP * 15 FETCH (RFC822.SIZE 2272) fetchmail: IMAP * 16 FETCH (RFC822.SIZE 3069) fetchmail: IMAP * 17 FETCH (RFC822.SIZE 1812) fetchmail: IMAP * 18 FETCH (RFC822.SIZE 1841) fetchmail: IMAP * 19 FETCH (RFC822.SIZE 15021) fetchmail: IMAP * 20 FETCH (RFC822.SIZE 1931) fetchmail: IMAP * 21 FETCH (RFC822.SIZE 2269) fetchmail: IMAP * 22 FETCH (RFC822.SIZE 1767) fetchmail: IMAP * 23 FETCH (RFC822.SIZE 2361) fetchmail: IMAP * 24 FETCH (RFC822.SIZE 3131) fetchmail: IMAP * 25 FETCH (RFC822.SIZE 1288) fetchmail: IMAP * 26 FETCH (RFC822.SIZE 1746) fetchmail: IMAP * 27 FETCH (RFC822.SIZE 2918) fetchmail: IMAP * 28 FETCH (RFC822.SIZE 21986) fetchmail: IMAP * 29 FETCH (RFC822.SIZE 3928) fetchmail: IMAP * 30 FETCH (RFC822.SIZE 7281) fetchmail: IMAP * 31 FETCH (RFC822.SIZE 10745) fetchmail: IMAP * 32 FETCH (RFC822.SIZE 3841) fetchmail: IMAP * 33 FETCH (RFC822.SIZE 2911) fetchmail: IMAP * 34 FETCH (RFC822.SIZE 3927) fetchmail: IMAP * 35 FETCH (RFC822.SIZE 5412) fetchmail: IMAP * 36 FETCH (RFC822.SIZE 23630) fetchmail: IMAP * 37 FETCH (RFC822.SIZE 22279) fetchmail: IMAP * 38 FETCH (RFC822.SIZE 2253) fetchmail: IMAP * 39 FETCH (RFC822.SIZE 19766) fetchmail: IMAP * 40 FETCH (RFC822.SIZE 5425) fetchmail: IMAP * 41 FETCH (RFC822.SIZE 732) fetchmail: IMAP * 42 FETCH (RFC822.SIZE 1530) fetchmail: IMAP * 43 FETCH (RFC822.SIZE 727)
Bug#348747: fetchmail: segfault when submitting dsn to local postmaster
I should add that downgrading to fetchmail 6.2.5.4-1 makes the problem go away. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#337126: [Pkg-zope-developers] Bug#337126: zope2.8: adding Plone Site fails with reauthentication loop
This problem persisted until I created a new zope2.8 instance using the latest packages. I was able to sucessfully add a Plone Site inside this new instance. -- Nathaniel W. Turner http://houseofnate.net/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#340808: zope-cmfplone uninstallable in sid (missing dependency)
Package: zope-cmfplone Version: 2.1.1-1 Severity: serious 00:00:18 [EMAIL PROTECTED](~)$ sudo apt-get install zope-cmfplone Reading package lists... Done Building dependency tree... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. Since you only requested a single operation it is extremely likely that the package is simply not installable and a bug report against that package should be filed. The following information may help to resolve the situation: The following packages have unmet dependencies: zope-cmfplone: Depends: zope-archetypes (= 1.3.5) but it is not going to be installed E: Broken packages 00:09:29 [EMAIL PROTECTED](~)$ apt-cache policy zope-archetypes zope-archetypes: Installed: (none) Candidate: 1.2.5-rc5-4 Version table: 1.2.5-rc5-4 0 500 http://http.us.debian.org unstable/main Packages 00:09:42 [EMAIL PROTECTED](~)$ I don't see zope-archetypes 1.3.5 in incoming either. Cheers, nate -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#338007: [pkg-fetchmail-maint] Bug#338007: fetchmail: certain messages cause client/server synchronization error while fetching ...
On Monday 07 November 2005 08:27 pm, Matthias Andree wrote:
Does the problem also affect 6.2.9-rc7?
Yes, I see the same problem with 6.2.9-rc7. The results of running fetchmail
6.2.9-rc7 against the same test messages are attached to this message.
Cheers,
nate
--
Nathaniel W. Turner
http://www.houseofnate.net/
Tel: +1 508 579 1948 (mobile)
09:40:28 [EMAIL PROTECTED](fetchmail-6.2.9-rc7)$ sudo -u fetchmail -H
./bin/fetchmail -vv -f /etc/fetchmailrc
fetchmail: 6.2.9-rc7 querying mail63.csoft.net (protocol IMAP) at Wed 09 Nov
2005 09:45:16 AM EST: poll started
fetchmail: mail63.csoft.net key fingerprint:
BE:6E:98:B9:4F:CC:0E:1F:E6:D1:E0:48:67:20:BA:9A
fetchmail: Server certificate verification error: self signed certificate
fetchmail: IMAP * OK [CAPABILITY IMAP4rev1 UIDPLUS CHILDREN NAMESPACE
THREAD=ORDEREDSUBJECT THREAD=REFERENCES SORT QUOTA IDLE AUTH=PLAIN ACL
ACL2=UNION XCOURIEROUTBOX=INBOX.Outbox] Courier-IMAP ready. Copyright 1998-2004
Double Precision, Inc. See COPYING for distribution information.
fetchmail: IMAP A0001 CAPABILITY
fetchmail: IMAP * CAPABILITY IMAP4rev1 UIDPLUS CHILDREN NAMESPACE
THREAD=ORDEREDSUBJECT THREAD=REFERENCES SORT QUOTA IDLE AUTH=PLAIN ACL
ACL2=UNION XCOURIEROUTBOX=INBOX.Outbox
fetchmail: IMAP A0001 OK CAPABILITY completed
fetchmail: Protocol identified as IMAP4 rev 1
fetchmail: IMAP A0002 LOGIN canprev *
fetchmail: IMAP A0002 OK LOGIN Ok.
fetchmail: selecting or re-polling default folder
fetchmail: IMAP A0003 SELECT INBOX
fetchmail: IMAP * FLAGS (\Draft \Answered \Flagged \Deleted \Seen \Recent)
fetchmail: IMAP * OK [PERMANENTFLAGS (\Draft \Answered \Flagged \Deleted
\Seen)] Limited
fetchmail: IMAP * 2 EXISTS
fetchmail: IMAP * 1 RECENT
fetchmail: IMAP * OK [UIDVALIDITY 1050373950] Ok
fetchmail: IMAP * OK [MYRIGHTS acdilrsw] ACL
fetchmail: IMAP A0003 OK [READ-WRITE] Ok
fetchmail: 2 messages waiting after first poll
fetchmail: IMAP A0004 EXPUNGE
fetchmail: IMAP A0004 OK EXPUNGE completed
fetchmail: 2 messages waiting after expunge
2 messages for canprev at mail63.csoft.net.
fetchmail: IMAP A0005 FETCH 1:2 RFC822.SIZE
fetchmail: IMAP * 1 FETCH (RFC822.SIZE 429)
fetchmail: IMAP * 2 FETCH (RFC822.SIZE 22123)
fetchmail: IMAP A0005 OK FETCH completed.
fetchmail: IMAP A0006 FETCH 1 RFC822.HEADER
fetchmail: IMAP * 1 FETCH (RFC822.HEADER {429}
reading message [EMAIL PROTECTED]:1 of 2 (429 header octets)
About to rewrite To: [EMAIL PROTECTED]
Rewritten version is To: [EMAIL PROTECTED]
About to rewrite From: [EMAIL PROTECTED]
Rewritten version is From: [EMAIL PROTECTED]
fetchmail: passed through [EMAIL PROTECTED] matching cancerprev.org
fetchmail: SMTP 220 codeine.cancerprev.org ESMTP
fetchmail: SMTP EHLO codeine.cancerprev.org
fetchmail: SMTP 250-codeine.cancerprev.org Ok.
fetchmail: SMTP 250-STARTTLS
fetchmail: SMTP 250-XVERP=Courier
fetchmail: SMTP 250-XEXDATA
fetchmail: SMTP 250-XSECURITY=NONE,STARTTLS
fetchmail: SMTP 250-PIPELINING
fetchmail: SMTP 250-8BITMIME
fetchmail: SMTP 250-SIZE
fetchmail: SMTP 250 DSN
fetchmail: forwarding to mail.cancerprev.org
fetchmail: SMTP MAIL FROM:[EMAIL PROTECTED] SIZE=429
fetchmail: SMTP 250 Ok.
fetchmail: SMTP RCPT TO:[EMAIL PROTECTED]
fetchmail: SMTP 250 Ok.
fetchmail: SMTP DATA
fetchmail: SMTP 354 Ok.
#
fetchmail: IMAP This is the message body. The preceding blank line ends with
\r\n, as do
fetchmail: IMAP all the other lines in this message.
fetchmail: IMAP This line contains the word OK somewhere in it.
fetchmail: IMAP A0007 FETCH 1 BODY.PEEK[TEXT]
fetchmail: IMAP
fetchmail: IMAP This message will cause fetchmail to choke.
fetchmail: IMAP )
fetchmail: IMAP A0006 OK FETCH completed.
fetchmail: IMAP A0008 LOGOUT
fetchmail: IMAP * 1 FETCH (BODY[TEXT] {213}
fetchmail: IMAP This is the message body. The preceding blank line ends with
\r\n, as do
fetchmail: IMAP all the other lines in this message.
fetchmail: IMAP This line contains the word OK somewhere in it.
fetchmail: IMAP
fetchmail: IMAP This message will cause fetchmail to choke.
fetchmail: IMAP )
fetchmail: IMAP A0007 OK FETCH completed.
fetchmail: IMAP * BYE Courier-IMAP server shutting down
fetchmail: IMAP A0008 OK LOGOUT completed
fetchmail: client/server synchronization error while fetching from
mail63.csoft.net
fetchmail: 6.2.9-rc7 querying mail63.csoft.net (protocol IMAP) at Wed 09 Nov
2005 09:45:21 AM EST: poll completed
fetchmail: Query status=7 (ERROR)
fetchmail: Deleting fetchids file.
fetchmail: normal termination, status 7
fetchmail: Deleting fetchids file.
09:49:25 [EMAIL PROTECTED](fetchmail-6.2.9-rc7)$ sudo -u fetchmail -H
./bin/fetchmail -vv -f /etc/fetchmailrc
fetchmail: 6.2.9-rc7 querying mail63.csoft.net (protocol IMAP) at Wed 09 Nov
2005 09:49:29 AM EST: poll started
fetchmail: mail63.csoft.net key fingerprint:
BE:6E:98:B9:4F:CC:0E:1F:E6:D1:E0:48:67:20:BA:9A
fetchmail: Server certificate verification error: self signed certificate
fetchmail: IMAP * OK [CAPABILITY IMAP4rev1 UIDPLUS CHILDREN NAMESPACE
THREAD=ORDEREDSUBJECT THREAD=REFERENCES SORT
Bug#338007: fetchmail: certain messages cause client/server synchronization error while fetching ...
Package: fetchmail Version: 6.2.5-18 Severity: important I have done some debugging, and determined that with my setup, fetchmail always fails if two conditions are met. My setup: - messages arrive on box-A via qmail - fetchmail on box-B fetches messages via courier-imap on box-A Conditions required for failure (both must be met): 1. the message being fetched must have DOS-style line endings (at least for the blank line between the headers and the message body). 2. the message body must contain (anywhere in it) the two character string OK. If these conditions are met, fetchmail will choke while fetching this message, and quit, leaving it and any other message on the server. I have minimal test messages and the output of running fetchmail -vv for each of them, which I will attach to this report. (I don't think this bug has security implications other than a basic DoS, but that might be worth investigating, as it seems fetchmail is interpreting data from an untrusted user as though it were data from a (potentially trusted) mail server.) I don't think my particular /etc/fetchmailrc is relevant here, but I can provide a sanitized copy if needed. Cheers, nate -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.14-1-k7 Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Versions of packages fetchmail depends on: ii adduser 3.77 Add and remove users and groups ii base-files3.1.9 Debian base system miscellaneous f ii debianutils 2.15.1 Miscellaneous utilities specific t ii libc6 2.3.5-7GNU C Library: Shared libraries an ii libssl0.9.7 0.9.7g-5 SSL shared libraries Versions of packages fetchmail recommends: ii ca-certificates 20050804 Common CA Certificates PEM files -- no debconf information tests.tar.gz Description: Binary data
Bug#337126: zope2.8: adding Plone Site fails with reauthentication loop
Package: zope2.8 Version: 2.8.3-1 Severity: important I've been using Plone with a Zope 2.7 instance, and this works fine. I can add new Plone sites at will. I was considering migrating to Zope 2.8, so I created a 2.8 instance with dzhandle, started it up on a different port, connected to it (this worked; I got the welcome page), entered the ZMI (ok), went to add a Plone Site, got the expected form, filled in the site id, hit the button, and... was prompted for my credentials. I entered the same credentials, but they were not accepted, and after several tries, I hit Cancel and got this error page: Site Error An error was encountered while publishing this resource. Error Type: Unauthorized Error Value: Cannot create Large Plone Folder Troubleshooting Suggestions * The URL may be incorrect. * The parameters passed to this resource may be incorrect. * A resource that this resource relies on may be encountering an error. For more detailed information about the error, please refer to the error log. If the error persists please contact the site maintainer. Thank you for your patience. Since this works with zope2.7, I'm filing it on zope2.8 rather than zope-cmfplone. Any ideas? Has anyone else tried using plone with zope2.8 on Debian? Cheers, nate -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.14-1-k7 Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Versions of packages zope2.8 depends on: ii debconf [debconf-2.0] 1.4.58 Debian configuration management sy ii libc6 2.3.5-7GNU C Library: Shared libraries an ii lsb-base 3.0-11 Linux Standard Base 3.0 init scrip ii python2.3 2.3.5-8An interactive high-level object-o ii python2.3-xml 0.8.4-1XML tools for Python (2.3.x) ii zope-common 0.5.13 common settings and scripts for zo zope2.8 recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#323508: konversation: DCC downloads not work when using a XDCC server and files is sort by packs
Hello Héctor, On Tuesday 16 August 2005 11:55 pm, Héctor Delcourt (Armonth) wrote: Package: konversation Version: 0.17-1 Can you try installing the latest konversation snapshot from my personal repository, and check to see if the bug still exists? See http://debian.houseofnate.net/ for details on my repository, or just add the following line to your /etc/apt/sources.list file: deb http://debian.houseofnate.net/ experimental main ... and run (as root): apt-get update; apt-get install konversation/experimental Let me know how this goes for you. Cheers, nate -- Nathaniel W. Turner http://houseofnate.net/
Bug#266591: initrd-tools: mkinitrd assumes /dev/mapper/* == LVM device
Hi, On Thursday 28 April 2005 04:43 am, you wrote: current initrd-tools 0.1.76 seems to have cryptsetup support. can you please report back if aboves pain still subsist? I'm very sorry I haven't followed up sooner. Here's the result of attempting to install a new kernel-image now: Selecting previously deselected package kernel-image-2.6.10-1-386. (Reading database ... 139937 files and directories currently installed.) Unpacking kernel-image-2.6.10-1-386 (from .../kernel-image-2.6.10-1-386_2.6.10-6_i386.deb) ... Setting up kernel-image-2.6.10-1-386 (2.6.10-6) ... File descriptor 3 left open File descriptor 4 left open File descriptor 5 left open File descriptor 6 left open File descriptor 7 left open Finding all volume groups Finding volume group vg02 ldd: /lib/libdevmapper.so.1.00: No such file or directory Failed to create initrd image. dpkg: error processing kernel-image-2.6.10-1-386 (--configure): subprocess post-installation script returned error exit status 9 Errors were encountered while processing: kernel-image-2.6.10-1-386 E: Sub-process /usr/bin/dpkg returned an error code (1) 12:29:08 [EMAIL PROTECTED](~)$ I'm not sure if the problems above are due to mkinitrd or some other part of the kernel-image postinst; hopefully someone reading this will have a better idea. Note that on my system, there is a /lib/libdevmapper.so.1.01, so perhaps there is a dependency problem here. Cheers, nate -- Nathaniel W. Turner http://www.houseofnate.net/ Tel: +1 508 579 1948 (mobile) pgpV2XwsAgwCV.pgp Description: PGP signature
Bug#305830: konversation: New upstream release
On Friday 22 April 2005 5:40 am, Modestas Vainius wrote: On your home page http://debian.houseofnate.net, you claim that you will upload 0.17-1 to unstable once 0.16-1 enters testing. 0.16-1 has already got into testing, so it would be great if you uploaded 0.17-1 to unstable. Thanks! Thanks for the reminder. I have now asked my sponsor to do an upload; 0.17-1 will probably go in soon. Cheers, nate -- Nathaniel W. Turner http://houseofnate.net/ pgphjLGTS61xE.pgp Description: PGP signature
Bug#303508: pinentry-qt: Hangs when pressing Menu key then Esc
Package: pinentry-qt Version: 0.7.2-1 Severity: normal Good morning, To reproduce this bug, you must have a keyboard with a Menu key (or some other key, I suppose) that is mapped to open a context menu. I believe this is the default mapping for this key, if you have it. (On my keyboard, the Menu key is between the right Logo key and the right Ctrl key.) 1. from a terminal, run pinentry-qt 2. type getpinEnter (a pin entry dialog box should appear) 3. in the dialog box, press the Menu key (a context menu should appear) 4. press Esc At this point, the dialog box will dissappear, but no response will be returned to the terminal. (If you omit step 3, you will get the response ERR 111 canceled, which is what we want.) This bug manifested itself to me as kmail hanging after I accidentally mistyped my passphrase (by hitting the Menu key instead of Shift, which is right above it) and then hitting Esc to get a fresh start. At this point the context menu was showing, and it hung as described, and kmail hung too because it was still waiting for a response. (Note that if you get the context menu for the line edit using the right mouse button instead of the Menu key, this bug does not appear.) Also, other apps that use a line edit do not behave this way; for example, to see the expected behaviour, do this: 1. run kdialog --inputbox test 2. follow steps 3-4 above Cheers, nate -- System Information: Debian Release: 3.1 APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.10-1-k7 Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Versions of packages pinentry-qt depends on: ii libc62.3.2.ds1-20GNU C Library: Shared libraries an ii libgcc1 1:3.4.3-12 GCC support library ii libice6 4.3.0.dfsg.1-12.0.1 Inter-Client Exchange library ii libncurses5 5.4-4 Shared libraries for terminal hand ii libqt3c102-mt3:3.3.3-8 Qt GUI Library (Threaded runtime v ii libsm6 4.3.0.dfsg.1-12.0.1 X Window System Session Management ii libstdc++5 1:3.3.5-12 The GNU Standard C++ Library v3 ii libx11-6 4.3.0.dfsg.1-12.0.1 X Window System protocol client li ii libxext6 4.3.0.dfsg.1-12.0.1 X Window System miscellaneous exte ii xlibs4.3.0.dfsg.1-12 X Keyboard Extension (XKB) configu -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#303090: docs are installed in wrong place
Thanks for the heads up! I'll be sure to get this sorted out for 0.17, which will be released soon. -- Nathaniel W. Turner http://houseofnate.net/ pgpyZuk1oAg9n.pgp Description: PGP signature
Bug#291503: CAN-2005-0129/130/131: Multiple vulnerabilities in Konversation
On Friday 21 January 2005 02:09 am, Martin Schulze wrote: These problems have been discovered by Wouter Coekaerts in the konversation IRC client. Affected are version 0.15, CVS until 18-19/01/2005, and some older versions too. They are fixed in 0.15.1. Fixed in 0.15-3, which needs to be uploaded by a DD. I mailed Riku Voipio (who usually sponsors my konversation uploads) about it a couple days ago. For now, the fixed package can be found at my repository: deb http://debian.houseofnate.net/ unstable main deb-src http://debian.houseofnate.net/ unstable main -- Nathaniel W. Turner Web Coordinator Cancer Detection and Prevention http://www.cancerprev.org/ pgpq3fnuiBTvO.pgp Description: PGP signature
Bug#291503: CAN-2005-0129/130/131: Multiple vulnerabilities in Konversation
On Friday 21 January 2005 03:45 pm, Joey Hess wrote: I'll sponsor this upload to get the security fix in quickly. Thank you. -- Nathaniel W. Turner http://www.houseofnate.net/ Tel: +1 508 579 1948 (mobile) pgpkriuDByw8m.pgp Description: PGP signature
Bug#289914: konversation's build failure on ia64
[CC'ing debian-qt-kde in search of an uploader for a fixed package] Hi Christopher, On Tuesday 11 January 2005 02:41 pm, Christopher Martin wrote: Your latest konversation package doesn't build on ia64, and so unfortunately isn't heading for Sarge. Looking at the log, I see: Thanks for the bug report. I actually noticed this last week, and sent a 0.15-2 with that very patch to my sponsor this past Thursday. I'm beginning to suspect that he may be on vacation or busy with other (hopefully more fun) things, though. If any DD's reading this message are willing to sponsor this one-time upload to get konversation 0.15 moving toward Sarge, I'm sure I won't be the only person who is grateful. You can grab the package from my personal repository: deb http://debian.houseofnate.net/ unstable main deb-src http://debian.houseofnate.net/ unstable main Cheers, nate -- Nathaniel W. Turner Web Coordinator Cancer Detection and Prevention http://www.cancerprev.org/ pgp3gvdCSFt2Q.pgp Description: PGP signature
