the upgrade tool from 19.04 to 19.10 failed badly

Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Freenode.

To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/1846842/+editstatus and add the package name in the text box next to the word Package.

[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]

Thank you for taking the time to report this bug and helping to make Ubuntu better.

Unfortunately, we cannot work on this bug because your description didn't include enough information. It actually reads like you wanted the chance to complain, where bug reports are not the appropriate place in my opinion.

You may find it helpful to read "How to report bugs effectively" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem.

We have instructions on debugging some types of problems at http://wiki.ubuntu.com/DebuggingProcedures.

At a minimum, we need:

1. The specific steps or actions you took that caused you to encounter the problem.
2. The behavior you expected.
3. The behavior you actually encountered (in as much detail as possible).

I've marked this bug as incomplete, as it contains no actual messages, or details of problems (packages), or specifics. If you believe I'm in error, please feel free to leave a comment as to why, or even better provide the specific details as to problems (apport or details from logs) and you can change status back to "New".

I have determined the the package was the ubuntu-release-upgrader

also if you read what I wrote properly you would see that there were no messages: the entirety of gnome-shell was stuffed by the faulty upgrade, all I had was a blank screen.

Fortunately I was able to login by ssh from my good machine and fix things on the command line.
ok to format the data the way you want it.

1. The specific steps or actions you took that caused you to encounter the problem.

    I ran update-manager -d on a ubuntu 19.04 box and followed the steps, there were some problems, in short the buttons of the upgrader did not respond to the mouse, I used tab and enter to solve this.

2. The behavior you expected.

   I expected the upgrader to cleanly upgrade my system.

3. The behavior you actually encountered (in as much detail as possible).

   The screen locked some way into the upgrade, I found it like this during the night, I attempted to unlock it and after some time I was confronted with a blank screen.

So I loggedin from my good machine by ssh, I found that the release upgrader was still running but doing nothing as far as I could tell, I gave it an hour, still nothing so I killed it using "sudo kill -1 pid1 pid2"; where pid1 was the pid of the of the python program doing the upgrade and pid2 was a shell wrapper for it I think, I obtained these pid's from "pgrep --full --list-full upgrade".

Then I rebooted the box with sudo shutdown -r +1 , when it came up again I still had a broken box so I sshed in again, ran "sudo apt upgrade" this failed but told me to run "dpkg --configure -a" as there was stuffed messed up with the package system, (I forget it's exact words) so I ran "sudo dpkg --configure -a" it installed many many packages between 4000 and 5000 I think it exited cleanly but things still were not right, I could login graphically again but gnome shell was still at version 3.32.2 not 3.34 and some of the plugins were not working, so I ran "update-manager -d &" again and it gave me a partial upgrader, but that did not work.

So I ran "sudo apt-get dist-upgrade" that cleaned up some stuff and deleted one package at least. then I ran update-manager and it pulled down many more packages and fixed the system.

After all that I seam to be on a clean copy of 19.10:

$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu Eoan Ermine (development branch)
Release: 19.10
Codename: eoan

obviously this needs looking into before 19.10 proper comes out

P.S. sorry if I sounded snappy, looking over what I wrote first some of the words are missing, I guess I was tired when I wrote that.

I ran ubuntu-bug update-manager I thought it should have added some data to this ?? has something gone wrong

Thank you again for taking the time to report this bug, plus the time taken to provide extra details in your efforts to help make Ubuntu better.

Can I please ask you to provide another detail; specs about your machine using apport-collect. Please execute the following command (on the box the upgrade was performed on) only once, and it will automatically gather debugging information, in a terminal:

apport-collect 1846842

When reporting bugs, please try and use apport by using 'ubuntu-bug' and the name of the package affected. This step provides the details that process would have provided.

Thanks again for your time in helping make Ubuntu better.

apport information

apport information

apport information

apport information

apport information

apport information

From VarLogDistupgradeAptlog.txt

Investigating (0) kde-style-breeze-qt4:amd64 < 4:5.15.4.1-0ubuntu1 @ii mK Ib >
Broken kde-style-breeze-qt4:amd64 Depends on kde-style-breeze:amd64 < 4:5.15.4.1-0ubuntu1 -> 4:5.16.5-0ubuntu1 @ii umU > (= 4:5.15.4.1-0ubuntu1)

Qt4 is OLD/depreciated & likely expected on upgrade (https://packages.ubuntu.com/search?suite=all&searchon=names&keywords=kde-style-breeze-qt4)

https://packages.ubuntu.com/disco/kde-style-breeze-qt4 shows "kde-style-breeze (= 4:5.15.4.1-0ubuntu1)" which is a problem I suspect so leaving it..

I suspect this MAY impact other users upgrading from 19.04 to 19.10

-- Other issues that may be 3rd party related

Investigating (0) libomp-9-dev:amd64 < none -> 1:9-1 @un uN Ib >
Broken libomp-9-dev:amd64 Conflicts on libomp-x.y-dev:amd64 < none @un H >
Looks like 3rd party packages; possibly a reason to reject,

"ERROR:root:Package seamonkey-mozilla-build has no priority set
ERROR:root:not handled exception:"
is likely 3rd party/PPA & reject.. but ignoring

are you saying these 3 party packages caused the problem, because I am running gnome-shell (i.e not kde) does gnome-shell depend on kde ??????, also shouldn't it have either worked around these problems or refused to upgrade??? in the past it coped with such stuff

No sorry Grizzly, my prior comment was TRIAGE related... and for any subsequent reader.

It was my thoughts on bug from your upgrade log and not directed to you, but any future reader.

The added and now deprecated KDE/Qt package was added at some prior time to your system which was 1 of the 3 issues I saw. That package is not available in 19.10; KDE used Qt4 in 14.04 and both Qt4/Qt5 in 14.10. You probably installed a Qt based app that pulled the package in.

The other two issues were non-Ubuntu sourced packages I concluded. These are NOT bugs in the Ubuntu code, but packaging issues created by 3rd parties who don't follow Ubuntu packaging versioning rules. 3rd parties usually don't consider release-upgrade time, just the release they initially package for.

Only the Qt4 package issue could be bug related was my 2c.

Just upgraded from 19.04 to 19.10 via "sudo do-release-upgrade -d". No problems with buttons of course, but apparently the lock screen had not been disabled in contrast to what the updater announced. So screen kind of locked w/ message something like "Something went wrong, please log out and log in again" only one button displayed ("logout"). W/o thinking I clicked on that button, screen went kind of black with blinking underline cursor in the top left corner. Alt+Fx didn't work, so I hard rebooted. Using recovery kernel and some "dpkg --configure -a" and such I managed to kind of recover and now have 19.10 running.

Oh, actually on 19.04 I did not use automatic screen locking, only blanking after 10 min. Automatic login is enabled for my main user.

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

/var/log/dist-upgrade/main.log.partial

2019-10-18 13:21:04,170 INFO Using config files '['/usr/share/ubuntu-release-upgrader/DistUpgrade.cfg']'
2019-10-18 13:21:04,170 INFO uname information: 'Linux generic 5.0.0-32-generic #34-Ubuntu SMP Wed Oct 2 02:06:48 UTC 2019 x86_64'
2019-10-18 13:21:05,144 INFO apt version: '1.9.4'
2019-10-18 13:21:05,144 INFO python version: '3.7.5rc1 (default, Oct 8 2019, 16:47:45)
[GCC 9.2.1 20191008]'
2019-10-18 13:21:05,148 INFO release-upgrader version '19.10.15' started
2019-10-18 13:21:05,153 INFO locale: 'en_US' 'UTF-8'
2019-10-18 13:21:05,223 DEBUG Using 'DistUpgradeViewText' view
2019-10-18 13:21:05,282 DEBUG enable dpkg --force-overwrite
2019-10-18 13:21:05,373 DEBUG lsb-release: 'eoan'
2019-10-18 13:21:05,374 DEBUG _pythonSymlinkCheck run
2019-10-18 13:21:05,375 DEBUG openCache()
2019-10-18 13:21:05,375 INFO not running quirks in partialUpgrade mode
2019-10-18 13:21:05,375 WARNING dpkg interrupted, calling dpkg --configure -a

@ramennoodles - could you please submit a new bug report about your upgrade issue?

Hi all guys,

I tried to upgrade from 19.04 to 19.10 (ubuntu, italian) and have the same problem:

rollsappletree@mazinga:~$ sudo do-release-upgrade
[sudo] password di rollsappletree:
Riprovare.
[sudo] password di rollsappletree:
Verifica un nuovo rilascio di ubuntu
Il rilascio di Ubuntu in uso non è più supportato.
ERROR:root:incorrect translation for message 'For upgrade information, please visit:
%(url)s
' to 'Per informazioni sull'avanzamento consultare:
$(url)s
' (wrong number of arguments)
For upgrade information, please visit:
http://www.ubuntu.com/releaseendoflife

Installare tutti gli aggiornamenti per la versione attuale prima di eseguire l'avanzamento di versione.

How can i help?
thanks
C

Just had a similar experience running do-release-upgrade -d from a terminal and upgrading from 18.04 to 20.04. The upgrade ran until after the packages had been downloaded, the screen went grey I couldn't change to a TTY. I was forced to reboot. On reboot the machine could not reboot normally however, I could start in an old kernel I the used a TTY to run the command dpkg --configure -a. All the remaining packages (several thousand) installed and after running apt-get autoremove the upgrade completed satisfactorily.