Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

bug#5299: 23.1.91; Cannot send bug report - get error no such file /bin/bash

0 views
Skip to first unread message

Drew Adams

unread,
Jan 3, 2010, 1:54:13 PM1/3/10
to emacs-pr...@gnu.org
emacs -Q

I tried to send a bug report using Help > Send bug report. When I hit C-c C-c, I
got this error:

Searching for program: no such file or directory, /bin/bash.

So I'm typing this into my mail client, Outlook, directly (copying and pasting
the version info etc.).

I would like to know a workaround soon, so I can send other bug reports in the
normal way. I have no problem sending bug reports in any Emacs release (20
through 23.1), and I've never previously had a problem sending a report for any
pretest version.


In GNU Emacs 23.1.91.1 (i386-mingw-nt5.1.2600)
of 2010-01-02 on PRETEST
Windowing system distributor `Microsoft Corp.', version 5.1.2600
configured using `configure --with-gcc (3.4)'

Drew Adams

unread,
Jan 3, 2010, 2:29:07 PM1/3/10
to Eli Zaretskii, 52...@debbugs.gnu.org
> > emacs -Q
> >
> > I tried to send a bug report using Help > Send bug report.
> > When I hit C-c C-c, I got this error:
> >
> > Searching for program: no such file or directory, /bin/bash.
>
> Does the below help?
> (setq mail-user-agent 'sendmail-user-agent)

No, unfortunately. That raises this error:

Sending...failed with exit value 1

And this is all there is in the *Messages* buffer about this:

Sending...
sendmail-send-it: Sending...failed with exit value 1

Eli Zaretskii

unread,
Jan 3, 2010, 2:21:56 PM1/3/10
to Drew Adams, 52...@debbugs.gnu.org
> From: "Drew Adams" <drew....@oracle.com>
> Date: Sun, 3 Jan 2010 10:54:13 -0800
> Cc:
>
> emacs -Q
>
> I tried to send a bug report using Help > Send bug report. When I hit C-c C-c, I
> got this error:
>
> Searching for program: no such file or directory, /bin/bash.
>
> So I'm typing this into my mail client, Outlook, directly (copying and pasting
> the version info etc.).
>
> I would like to know a workaround soon, so I can send other bug reports in the
> normal way. I have no problem sending bug reports in any Emacs release (20
> through 23.1), and I've never previously had a problem sending a report for any
> pretest version.

Does the below help?

(setq mail-user-agent 'sendmail-user-agent)


Drew Adams

unread,
Jan 3, 2010, 2:55:19 PM1/3/10
to Eli Zaretskii, 52...@debbugs.gnu.org
> > > > emacs -Q
> > > >
> > > > I tried to send a bug report using Help > Send bug report.
> > > > When I hit C-c C-c, I got this error:
> > > >
> > > > Searching for program: no such file or directory, /bin/bash.
> > >
> > > Does the below help?
> > > (setq mail-user-agent 'sendmail-user-agent)
> >
> > No, unfortunately. That raises this error:
> >
> > Sending...failed with exit value 1
> >
> > And this is all there is in the *Messages* buffer about this:
> >
> > Sending...
> > sendmail-send-it: Sending...failed with exit value 1
>
> Then I don't understand how did it work for you in previous versions,
> in "emacs -Q". Did it?

Yes. It did and it still does. It works for emacs -Q in Emacs 20, 21, 22, and
23.1. And it has always worked for pretest binaries as well. I used `emacs -Q
--debug-init'.

Normally, when I hit C-c C-c it asks me if I want to send the bug and I answer
`yes'. It then opens a new Outlook message with the To and Subject fields
filled, and with text in the body telling me that my bug report is on the
clipboard. I just use C-a C-v in the body to replace that text with the report,
then click Send.

In the Emacs 23.1.91 pretest, , when I answer `yes' it raises the error.

Eli Zaretskii

unread,
Jan 3, 2010, 2:47:09 PM1/3/10
to Drew Adams, 52...@debbugs.gnu.org
> From: "Drew Adams" <drew....@oracle.com>
> Date: Sun, 3 Jan 2010 11:29:07 -0800

Lennart Borgman

unread,
Jan 3, 2010, 3:28:08 PM1/3/10
to Drew Adams, 52...@debbugs.gnu.org
On Sun, Jan 3, 2010 at 8:55 PM, Drew Adams <drew....@oracle.com> wrote:
>> > > > emacs -Q
>> > > >
>> > > > I tried to send a bug report using Help > Send bug report.
>> > > > When I hit C-c C-c, I got this error:
>> > > >
>> > > > Searching for program: no such file or directory, /bin/bash.
>> > >
>> > > Does the below help?
>> > >   (setq mail-user-agent 'sendmail-user-agent)
>> >
>> > No, unfortunately. That raises this error:
>> >
>> >  Sending...failed with exit value 1
>> >
>> > And this is all there is in the *Messages* buffer about this:
>> >
>> >  Sending...
>> >  sendmail-send-it: Sending...failed with exit value 1
>>
>> Then I don't understand how did it work for you in previous versions,
>> in "emacs -Q".  Did it?
>
> Yes. It did and it still does. It works for emacs -Q in Emacs 20, 21, 22, and
> 23.1. And it has always worked for pretest binaries as well. I used `emacs -Q
> --debug-init'.
>
> Normally, when I hit C-c C-c it asks me if I want to send the bug and I answer
> `yes'. It then opens a new Outlook message with the To and Subject fields
> filled, and with text in the body telling me that my bug report is on the
> clipboard. I just use C-a C-v in the body to replace that text with the report,
> then click Send.
>
> In the Emacs 23.1.91 pretest, , when I answer `yes' it raises the error.


Didn't we make a special workaround on w32 for this to work? I thought
that workaround was needed. It did put the content of the bug report
on the clipboard etc.

Is that what you have been using before, Drew, or?


Lennart Borgman

unread,
Jan 3, 2010, 4:10:41 PM1/3/10
to Drew Adams, 52...@debbugs.gnu.org
On Sun, Jan 3, 2010 at 9:58 PM, Drew Adams <drew....@oracle.com> wrote:
>> Didn't we make a special workaround on w32 for this to work? I thought
>> that workaround was needed. It did put the content of the bug report
>> on the clipboard etc.
>>
>> Is that what you have been using before, Drew, or?
>
> Sorry, I don't know what you are referring to, Lennart.
>
> I have always used vanilla Emacs with `emacs -Q' to report bugs.  I have,
> personally, never employed any "special workaround on w32".  I don't know
> anything about such a workaround.
>
> Or perhaps you are referring to something that Emacs did under the covers? If
> so, I know nothing about it - I've never tried to follow the `report-emacs-bug'
> code or the Emacs mail code.


If you were using it you should have noticed because it was not
totally transparent. The trouble was the restriction on the command
line length in w32. Because of this we could not send the message this
way to the default mail client. Instead we did a two step workaround:

1) We first put the message on the clipboard and then created a
shorter mail message that said that the real content was on the
clipboard.

2) This shorter message was sent to the default mail client and should
up for editing before sending.

I do not know if this works any more however. I do not use it myself
anymore since using it with web mail (gmail) is a bit clumsy. I just
cut and paste instead.

But for those using a w32 mail client it should still be usable I
believe. Or has someone found a workaround for the problem with the
command line length restriction?


> Are you able to reproduce the bug using Jason's pretest build and `emacs -Q'?
>
> There is nothing special at my end, AFAIK. I have Windows XP SP3. I do have
> Cygwin installed on my computer, but I don't tell Emacs that in any way when I
> use `emacs -Q'. I use Outlook 2003 as mail client.


Drew Adams

unread,
Jan 3, 2010, 3:58:41 PM1/3/10
to Lennart Borgman, 52...@debbugs.gnu.org
> Didn't we make a special workaround on w32 for this to work? I thought
> that workaround was needed. It did put the content of the bug report
> on the clipboard etc.
>
> Is that what you have been using before, Drew, or?

Sorry, I don't know what you are referring to, Lennart.

I have always used vanilla Emacs with `emacs -Q' to report bugs. I have,
personally, never employed any "special workaround on w32". I don't know
anything about such a workaround.

Or perhaps you are referring to something that Emacs did under the covers? If
so, I know nothing about it - I've never tried to follow the `report-emacs-bug'
code or the Emacs mail code.

Are you able to reproduce the bug using Jason's pretest build and `emacs -Q'?

Drew Adams

unread,
Jan 3, 2010, 4:42:43 PM1/3/10
to Lennart Borgman, 52...@debbugs.gnu.org
> >> > Are you able to reproduce the bug using Jason's pretest
> >> > build and `emacs -Q'?
> >
> > Well, are you? Have you tried using Jason's build with
> > emacs -Q and an external email client? That is the
> > first thing to try.
>
> I believed it stopped working at some time, but I thought it was due
> to some trouble I had with the gmail (additional) workaround (or maybe
> some bad merge in my patched version) so I did not look further.
>
> I have had a bit mess trying to get the gmail add-on to work. I would
> prefer not to test at the moment.

Perhaps you can determine when it stopped working. I assume you mean that it
stopped working for "CVS" Emacs, sometime after 23.1 was released. The 23.1
release works fine.

Lennart Borgman

unread,
Jan 3, 2010, 4:33:00 PM1/3/10
to Drew Adams, 52...@debbugs.gnu.org
On Sun, Jan 3, 2010 at 10:26 PM, Drew Adams <drew....@oracle.com> wrote:
>
> In that case, yes, as I already indicated in detail earlier, I pasted the true
> bug-report content to the email message prepared by Emacs (via my mail client).
> Please read my earlier message that details this.


Sorry, I missed the message where you described this. Yes, you were
using the workaround I described.


> But I don't even get to that stage now. I don't get an email-client message
> created. I doubt that Outlook is ever invoked in any way. As soon as I type
> `yes' to confirm that I want to send a bug report, the error is raised.

Drew Adams

unread,
Jan 3, 2010, 4:26:21 PM1/3/10
to Lennart Borgman, 52...@debbugs.gnu.org
> >> Didn't we make a special workaround on w32 for this to
> >> work? I thought that workaround was needed. It did put
> >> the content of the bug report on the clipboard etc.
> >>
> >> Is that what you have been using before, Drew, or?
> >
> > Sorry, I don't know what you are referring to, Lennart.
> >
> > I have always used vanilla Emacs with `emacs -Q' to report
> > bugs.  I have, personally, never employed any "special
> > workaround on w32". I don't know anything about such a workaround.
> >
> > Or perhaps you are referring to something that Emacs did
> > under the covers? If so, I know nothing about it - I've
> > never tried to follow the `report-emacs-bug'
> > code or the Emacs mail code.
>
> If you were using it you should have noticed because it was not
> totally transparent. The trouble was the restriction on the command
> line length in w32. Because of this we could not send the message this
> way to the default mail client. Instead we did a two step workaround:
>
> 1) We first put the message on the clipboard and then created a
> shorter mail message that said that the real content was on the
> clipboard.
>
> 2) This shorter message was sent to the default mail client and should
> up for editing before sending.
>
> I do not know if this works any more however. I do not use it myself
> anymore since using it with web mail (gmail) is a bit clumsy. I just
> cut and paste instead.
>
> But for those using a w32 mail client it should still be usable I
> believe. Or has someone found a workaround for the problem with the
> command line length restriction?

Apparently, you _are_ talking about something that Emacs did, and not something
that we users did. When you say "we", you apparently mean Emacs.

In that case, yes, as I already indicated in detail earlier, I pasted the true
bug-report content to the email message prepared by Emacs (via my mail client).
Please read my earlier message that details this.

But I don't even get to that stage now. I don't get an email-client message

Lennart Borgman

unread,
Jan 3, 2010, 4:45:48 PM1/3/10
to Drew Adams, 52...@debbugs.gnu.org
On Sun, Jan 3, 2010 at 10:42 PM, Drew Adams <drew....@oracle.com> wrote:
>> >> > Are you able to reproduce the bug using Jason's pretest
>> >> > build and `emacs -Q'?
>> >
>> > Well, are you? Have you tried using Jason's build with
>> > emacs -Q and an external email client? That is the
>> > first thing to try.
>>
>> I believed it stopped working at some time, but I thought it was due
>> to some trouble I had with the gmail (additional) workaround (or maybe
>> some bad merge in my patched version) so I did not look further.
>>
>> I have had a bit mess trying to get the gmail add-on to work. I would
>> prefer not to test at the moment.
>
> Perhaps you can determine when it stopped working. I assume you mean that it
> stopped working for "CVS" Emacs, sometime after 23.1 was released. The 23.1
> release works fine.


Sorry, but I can't remember at the moment. There has been too many
small troubles around this.


Drew Adams

unread,
Feb 20, 2010, 12:32:08 PM2/20/10
to 52...@debbugs.gnu.org, Lennart Borgman
This is still a bug. It prevents Windows users from filing Emacs bugs using `M-x
report-emacs-bug'.
0 new messages