ubuntu-bug <crashfile> exits after dialog instead of sending data

isn't that by design? we disable reporting to launchpad by default on stable series so it reports to e.u.c and that doesn't provide feedback to the users

http://launchpadlibrarian.net/596308770/apport_2.20.11-0ubuntu80_2.20.11-0ubuntu81.diff.gz

I don't think it's by design that if you explicitly run 'ubuntu-bug', it exits without giving you the opportunity to file a bug report or explaining why. Yes, it's intentional that we don't by default open bug reports on crashes, but the above seems like an accidental outcome.

From #ubuntu-meeting on 2022-05-12:

08:24 < ubottu> Bug 1972115 in apport (Ubuntu)
                "ubuntu-bug <crashfile> exits after
                dialog instead of sending data"
                [Undecided, New]
                https://launchpad.net/bugs/1972115
08:25 < bdmurray> I think that's of Low importance given
                  its been like that forever
08:25 < bdmurray> Having said that Launchpad is the only
                  way to have a conversation with a
                  crash reporter at this point in time
08:25 < bdmurray> So it might be nice
08:25 < bdrung> would it make sense to have two options
                in that case "send" and "create bug
                report"?
08:26 < bdmurray> I wouldn't want it to be that
                  accessible and have everyone clicking
                  "create bug report".
08:27 < bdrung> so then maybe a command line parameter
                to enable it?
08:28 < bdmurray> If somebody deliberately runs
                  ubuntu-bug with a crash file it should
                  go to both.
08:28 < bdmurray> Or a command line parameter.
08:28 < bdmurray> Anyway, let's go ahead and card this.

This bug seems to prevent me from providing a crash log in https://bugs.launchpad.net/bugs/1973802.

Is there any alternative way of attaching a crash log to a bug report? Attachment doesn't work, apparently because of the file size. Thanks.

On Thu, May 19, 2022 at 12:25:22PM -0000, Ralf Sternberg wrote:
> This bug seems to prevent me from providing a crash log in
> https://bugs.launchpad.net/bugs/1973802.

> Is there any alternative way of attaching a crash log to a bug report?
> Attachment doesn't work, apparently because of the file size. Thanks.

Are you running the 'apport-collect' command?

Status changed to 'Confirmed' because the bug affects multiple users.

This even happened to me on Focal (latest update) when reporting the gthumb CVE I found. I manually uploaded the crash dump, separated the big apport file and put it up. Maybe a server issue