Your message dated Sat, 11 Oct 2008 17:41:14 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Done: reportbug-ng: Fails to launch Icedove
has caused the Debian Bug report #499130,
regarding reportbug-ng: Fails to launch Icedove
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.)


-- 
499130: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=499130
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: reportbug-ng
Version: 1.1.1
Severity: important

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Since the latest update reportbug-ng fails to launch Icedove for editing
and sending bugreports:

> Unhandled exception in thread started by <function prepareMail at
> 0x9585c34>
> Traceback (most recent call last):
>   File "/var/lib/python-support/python2.5/rnghelpers.py", line 182, in 
> prepareMail
>     status, output = callMailClient(command)
>   File "/var/lib/python-support/python2.5/rnghelpers.py", line 498, in 
> callMailClient
>     status, output = commands.getstatusoutput(command)
>   File "/usr/lib/python2.5/commands.py", line 54, in getstatusoutput
>     text = pipe.read()
> IOError: [Errno 4] Interrupted system call

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

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

Versions of packages reportbug-ng depends on:
ii  python                        2.5.2-2    An interactive high-level object-o
ii  python-debianbts              0.2.1      Python interface to Debian's Bug T
ii  python-qt4                    4.4.3-1    Python bindings for Qt4
ii  python-support                0.8.6      automated rebuilding support for P
ii  xdg-utils                     1.0.2-6    desktop integration utilities from

reportbug-ng recommends no packages.

reportbug-ng suggests no packages.

- -- no debconf information

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)

iEUEARECAAYFAkjPqUMACgkQYfUFJ3ewsJjLIwCffOnCrPSmkTOJ1xJU8Ycy5ab0
ZUYAmMyeA25n/GlBwyIpLTvr/2z5a4c=
=QHPz
-----END PGP SIGNATURE-----



--- End Message ---
--- Begin Message ---
Package: reportbug-ng
Version: 1.2

Hi, this is probably not a bug in rng but in the commands module of
python2.5 (as the backtrace suggests). I'm still not able to reproduce
this bug. It looks like rng is doing exaclty what it is requested to,
those log-lines:


ReportbugNG  DEBUG    Just before the MUA call: xdg-email --utf8
--subject "[reportbug-ng] test" --body "Package: reportbug-ng
Version: 1.1.1
Severity: normal

[snip]

" "[EMAIL PROTECTED]"


look pretty fine. If you still encounter this bug, please try to call

xdg-email --utf8 --subject "subject-test" --body "body-test"
"[EMAIL PROTECTED]"

and check if this will start icedove prefilled with a body, subject and
to-field.

If not, this is probably a bug in xdg-email.


Cheers,

Bastian



--- End Message ---

Reply via email to