[05:32] <alkisg> Didn't it go from khtml (=konqueror) to webkit (=epiphany) to blink (=chrome)? Different forks from the same origin...
[08:06] <lotuspsychje> bug #1967163 fixed
[08:13] <lotuspsychje> software-properties-gtk crash on tab additional drivers bug, also fixed on my side
[10:09] <ravage> hi all. i had some trouble upgrading from 20.04 to 22.04 yesterday and wanted to try it again today on a VM. now on my fully upgraded VM i get "authenticate 'jammy.tar.gz' against 'jammy.tar.gz.gpg'"
[10:10] <ravage> Authenticating the upgrade failed. There may be a problem with the network or with the server.
[10:14]  * alkisg googles what kind of upgrades involve jammy.tar.gz and sees some arm images...
[10:14] <ravage> do-release-upgrade -d
[10:14] <alkisg> That downloads a .tar.gz?! Since when?!
[10:14] <ravage> since always
[10:15]  * alkisg tests in a vm...
[10:15] <ravage> https://p.haxxors.com/jfvvass4.txt is the full output
[10:18] <alkisg> Ah OK it's so fast that I never noticed that part. For me it correctly verified the file and continued
[10:18] <ravage> very strange
[10:19] <ravage> i installed the VM from the latest desktop iso
[10:19] <ravage> did all package updates and now it cant upgrade
[10:19] <ravage> it "worked" yesterday on my thinkpad. but as i said i had an error i wanted to investigate
[10:20] <alkisg> ravage: http://termbin.com/s989
[10:20] <alkisg> Check if your md5sums are the same as mine
[10:21] <ravage> now it gets really strange
[10:21] <ravage> tried the command again and it worked
[10:21] <ravage> maybe there is a bad mirror somewhere
[10:21] <alkisg> Yeah
[10:22] <alkisg> I've noticed glitches with mirror updates in the past as well, they don't appear to be atomic
[10:22] <ravage> ok then. will carry on and see if i get to my real error :)
[10:23] <ravage> germany has too many mirrors and i dont know if they are all in the archive rotation. too lazy to test the file on all of them now
[10:33] <ravage> still breaks the DE and goes to a blinking cursor. but that was also not the bug i wanted to check
[10:33]  * ravage tries again on a screen in console
[10:56] <ravage> firefox migration to snap failed again like yesterday with timeouts. will keep going manually 
[10:57] <ravage> y
[10:58] <ravage> but my actual error with a svg file from the yaru gnome-shell theme did not occur.
[10:59] <ravage> all in all i would describe my upgrade experience as "leaves much to be desired" :)
[12:01] <lotuspsychje> ravage: saw a few upgrade bugs passby on -announce
[12:05] <guiverc> ravage, was your upgrade from focal to jammy, or impish to jammy... 
[12:08] <ravage> focal->jammy
[12:09] <ravage> thats the only upgrade i need really. i could try from impish
[12:11] <ravage> I know there will be no official upgrades until the point release but the wiki article at least mentioned it 
[12:12] <ravage> So i thought I give it a try
[12:13] <guiverc> firefox/snap issue is I believe fixed with impish->jammy, but not yet for focal->jammy, why I asked.
[12:14] <ravage> I think the biggest problem is that the DE gets killed at some point
[12:17] <lotuspsychje> at this stage upgrades should surely be tested :p
[12:18] <ravage> i will reinstall my work laptop anyway. and i had backups. no big deal so far. 
[12:18] <ravage> was just a little difficult to mount my borg backup from a half upgraded system :D
[12:20] <ravage> lets fire up the 21.10 VM and see how that goes. im feeling lucky today
[12:20] <lotuspsychje> lol
[12:21] <lotuspsychje> bug #1967479
[12:22] <ravage> +1 :)
[12:22] <lotuspsychje> bug #1967517
[12:22] <ravage> wow nice
[12:22] <ravage> :D
[12:22] <lotuspsychje> think i saw a few flavours upgrade bugs too
[12:24] <lotuspsychje> bug #1965652
[12:57] <ravage> 21.10 does the snap migration before you can do the actual upgrade to jammy
[13:04] <ravage> but the DE crashes too
[13:05] <lotuspsychje> yikes ravage 
[13:07] <ravage> love my zfs snapshots :D
[13:07] <ravage> back to 21.10 in 2 seconfs
[13:08] <ravage> *seconds
[13:09] <lotuspsychje> cool