Dear Maintainer,

I cannot report any bugs using M-x debian-bug at all. After entering the bug
summary, I get the following error message, and cannot correctly reach the page
where I should write the actual bug report.

  Getting package information from reportbug...
  debian-bug-prefill-report: Reportbug did not produce expected output!
Bailing out.
  Reportbug may have sent an empty report!


Thanks, Salman

Salman Mohammadi <salman@smoha.org> writes:

I can't reproduce this behaviour. I guess it might be related to
something in your reportbug configuration. Can you share your .reportbugrc?

By the way, this bug by itself does not "render package unusable", since
the package provides other functionality.

Salman Mohammadi <salman@smoha.org> writes:

I can't reproduce this behaviour. I guess it might be related to
something in your reportbug configuration. Can you share your .reportbugrc?

By the way, this bug by itself does not "render package unusable", since
the package provides other functionality.

I have no .reportbugrc bit instead use the following configuration in my
.emacs:

   (setq user-mail-address "salman@smoha.org"
         user-full-name "Salman Mohammadi")

   (setq send-mail-function 'mailclient-send-it)


I had no problem in Debian 10 (stable) but as I upgraded to Sid, I get
the mentioned error message.


Thanks, Salman

I have no .reportbugrc bit instead use the following configuration in my
.emacs:

   (setq user-mail-address "salman@smoha.org"
         user-full-name "Salman Mohammadi")

   (setq send-mail-function 'mailclient-send-it)


I had no problem in Debian 10 (stable) but as I upgraded to Sid, I get
the mentioned error message.


Thanks, Salman

Salman Mohammadi <salman@smoha.org> writes:

I tried setting send-mail-function to mailclient-send-it (which by the
way tends to mangle attachements, but I guess that's not the issue here)
I still can't duplicate your issue.

You can try duplicating the problem with "emacs -q". You will
need to run M-x load-library <return> debian-el-autoloads <return>.

If that works, then your issue is most likely an interaction with some
other emacs addon package. You can try removing them one by one, or
loading them manually into emacs -q.

Dear David,

I could reproduce this bug under this environment:

   1. clean install debian stable in a vm

   2. upgrade debian to sid

   3. install emacs and debian-el: $ sudo apt -y install emacs
elpa-debian-el


Now, M-x debian-bug command does not work correctly.


Thanks, Salman

Hi Salman,

Salman Mohammadi <salman@smoha.org> writes:

I tried this:
1. With a clean chroot, 'sudo apt install emacs-nox elpa-debian-el'
   * Given that Emacs was not installed in the stable VM until
     post-upgrade, I don't think my digression is a relevant variable.
2. Start Emacs
3. M-x debian-bug
4. Everything appears to work fine.  After composing the full text of
   the bug, I hit C-c C-c, and then see the *Emacs Mail Setup Help*
   window appear, along with a minibuffer prompt.  From the original bug
   report email it sounds like this is farther along then you were able
   to get?

a. My hostname is a real FQDN (however no longer functional due to
expired dyndns subscription--post-Oracle acquisition is a rip-off).
It's possible that this bug only exists on hosts that don't have a FQDN
hostname.
b. Reportbug has not been configured.

Regards,
Nicholas

Hi Nicholas,

what makes me wonder is that the same procedure works on Debian 10 but
not on Debian Sid. To clarify the encountered bug, I once recorded my
screen on a clean installed Debain 10 (which works fine).

https://peertube.nogafa.org/videos/watch/9156c6dd-a46a-436a-9ba3-527c97c2ea71

and also on a clean installed Debian Sid (which doesn't work).

https://peertube.nogafa.org/videos/watch/7f8a31ec-52d8-42ac-8a01-2e2a92dae592


Regards, Salman