How do I report a bugs against the upgrade tool from 19.04 to 19.10

[Ralf Mardorf]

On Fri, 4 Oct 2019 15:59:46 +1000, Francis Grizzly Smit wrote:
>I upgraded my old crappy box to 19.10 beta from 19.04, things did not
>go well the upgrade tool eoan did not run well I could not get many of
>the buttons to work by clicking I had to use tab and enter, then the
>thing that's supposed stop it locking fail while I was asleep; woke up
>it was locked, and when I tried to unlock it I just got a blank screen.
>
>I had to ssh in to it find out what was going on I found it was stuck
>I gave it an hour to come out of it, it didn't, so I killed the
>processes with sudo kill -1 pid-of-the-python-program
>pid-of-the-shell-script then I rebooted it by sudo shutdown, and ssh
>in again and it was still sick and half done, so I called sudo apt
>upgrade, which didn't work but gave me the dpkg (sudo dpkg --configure
>-a) command to use, I ran that and it cleaned it up a lot, and I was
>able to login to gnome-shell it was still on version 3.32.2 and was a
>little messed up but worked, I tried the update-manager -d &, that
>gave me a partial upgrade program which failed, in the end, I fixed it
>with sudo apt-get dist-upgrade and running the normal update-manager
>program till every thing was up to date, now it's fine but it took
>much drama to do it

If a release-upgrade fails in the first place, but you solved it by
additional steps, I suspect that is one of the cases when manually
reporting the bug is the best way to do, since you migrated from one,
to another release and an automated report likely would be against the
new release, while actually the tool of the old release failed.

https://help.ubuntu.com/community/ReportingBugs#Filing_bugs_manually_at_Launchpad.net

I would report it manually and exactly describe what I've done, the
developers could assign it to a more appropriate package, if you should
be uncertain and they could ask you to post log files, if you don't
know what log file/s to post.

I suspect you where using ubuntu-release-upgrader-gtk, the GUI, so
manually filing a bug against this package could be a starting point.

Btw. I'm in favour to do a release upgrade from command line by running
do-release-upgrade, from the package ubuntu-release-upgrader-core.

Actually ubuntu-release-upgrader-gtk depends on
ubuntu-release-upgrader-core. IMO avoiding a GUI layer for this and
similar jobs does reduce the risk of issues, sometimes using command
line even does reduce user errors. YMMV!