[11:32] <webmind> Hi, trying to upgrade to 21.04 on my gpd pocket2, I followed the steps on https://ubuntu-mate.org/blog/ubuntu-mate-hirsute-hippo-final-release/ but at 'update-manager -c' is says my system is up to date and /usr/lib/ubuntu-release-upgrader/check-new-release-gtk gives a timeout?
[11:33] <webmind> WARNING:root:timeout reached, exiting
[11:34] <webmind> 'sudo do-release-upgrade -d' seems to work
[11:35] <webmind> But I've told it to notify me for 'For any new version'
[11:37] <Maik> it's not recommended to force the update due a bug https://lists.ubuntu.com/archives/ubuntu-devel/2021-April/041448.html
[11:38] <Maik> https://www.omgubuntu.co.uk/2021/04/why-you-cant-upgrade-to-ubuntu-21-04-for-now
[11:38] <Maik> that's why it won't notify you webmind
[11:39] <Maik> i also was told that the -d option puts you on a development release
[12:16] <webmind> yeah, I was told to try that last time it didn't work
[12:17] <webmind> shouldn't this be on the release page? that's currently recommending you to upgrade
[12:18] <webmind> but uhm yeah, I now only see my background with sometimes the terminal flipping in
[12:23] <Maik> webmind: they mentioned it here: https://discourse.ubuntu.com/t/hirsute-hippo-release-notes/19221#heading-release-upgrades
[12:23] <Maik> quote: Release Upgrades - Upgrades from Ubuntu 20.10 to Ubuntu 21.04 are not enabled as it is possible for some systems to end up in an unbootable state if they use EFI version 1.10 - bug 1925010. 580 Release upgrades will be enabled once an updated version of shim is available which is compatible with EFI version 1.10.
[12:23] <ubottu> bug 1925010 in shim (Ubuntu Hirsute) "shim-signed 15.4 does not boot on EFI 1.10 systems" [High,In progress] https://launchpad.net/bugs/1925010
[12:35] <webmind> I ended up here: https://ubuntu-mate.org/blog/ubuntu-mate-hirsute-hippo-final-release/ not even in the known issues
[12:36] <webmind> Do you need to read both before installing ubuntu-mate ?
[12:38] <webmind> my pocket 2 is now showing my background and one in a while blinking my terminal, I can get a new terminal ctrl-alt-f1, but what is now the best tactic to not end up completely broken?
[12:40] <Maik> webmind: of course, if Ubuntu MATE doesn't mention it then check the Ubuntu releasenotes too
[12:40] <Maik> the base is after all Ubuntu
[12:42] <webmind> if ubuntu mate -doesn't- mention? how do I know if it's not mentioning it?
[12:44] <Maik> i meant to say just check both release notes
[12:44] <Maik> it's their fault not to mention this important bug imho
[12:45] <webmind> it is, but when ubuntu-mate knowns, shouldn't the page be updated?
[12:45] <webmind> *knows
[12:46] <Maik> you can notify them about it on either their forum or on discord
[12:51] <Maik> webmind: i asked them why it wasn't included in the UM release notes
[13:05] <webmind> thank you
[13:05] <webmind> but my current bug doesn't look efi related, and do you have any idea how to save my currently running upgrade?
[13:12] <Maik> upgrades can't be saved afaik, just let it finish
[13:14] <Maik> imo Ubuntu should have waited on releasing 21.04. Fedora doesn't release when they found a possible show stopper bug.
[13:15] <Maik> they postpone a release by one week to make sure such bugs are squashed
[13:22] <webmind> it's waiting for me to answer a question, but the terminal is only there for 1 second and then I get my background again
[13:22] <webmind> I tried just typing it in, but the terminal doesn't seem to have the focus
[13:22] <webmind> alt-tab doesn't do anything
[13:26] <webmind> looks like marco is crashing
[13:26] <webmind> keeps having new pid's
[13:30] <webmind> yep, giving errors that it can't load themes
[13:36] <webmind> export DISPLAY=:0 and compiz --replace gave me something working again
[13:37] <webmind> (on tty0)
[13:54] <alkisg> It's possible to redirect a tty into another process. E.g. to migrate an upgrade process inside mate-terminal, to another process started via ssh.
[13:56] <alkisg> http://manpages.ubuntu.com/manpages/hirsute/man1/reptyr.1.html
[14:06] <webmind> that's pretty cool
[14:07] <webmind> installation finished, but does this mean I shouldn't reboot until it's fixed?
[14:08] <webmind> also compiz --replace, doesn't stop marco from trying to start anyway. It got into a restart loop eating a lot of cpu
[17:16] <Maik> webmind: according to the team the shim bug was mentioned in the Ubuntu MATE release notes
[17:19] <superkuh> I wish the MATE team would patch the gtk3 they link against to bring back the ability to paste filepaths and type into into File->Open dialogs.
[17:20] <superkuh> Without a patched gtk3 MATE is pretty much just modern GNOME.
[17:22] <superkuh> Last MATE release before gtk3 got GNOME'd was ~ 2013 with 1.8.
[19:09] <alkisg> superkuh: hm? I go to pluma > file > open, type / to show the path edit box, and I can paste paths there...
[19:16] <superkuh> Yes, after you type ~ , /  or .
[19:16] <superkuh> But if you just try to paste it errors out.
[19:17] <superkuh> Whereas with older gtk3 you can just paste the file path.
[19:17] <superkuh> http://erewhon.superkuh.com/gtkfilechooserwidget-paste-fail.jpg
[19:17] <alkisg> Oh I completely agree that gnome is heading to the wrong direction... I'm actually looking at Debian+KDE lately
[19:18] <superkuh> I tried kate in Qt as a text editor but it's gtk imitation so was good it had the same bugs as the gtk3 application.
[19:18] <superkuh> For a while I thought it was doing xdg-desktop-portal stuff.
[19:19] <alkisg> Unfortunately MATE doesn't have control over gtk3... I doubt they could patch the libs, as all Ubuntu flavors share the same repository
[19:19] <superkuh> Ah. Dang.
[19:19] <alkisg> For text editing, I moved to vscode
[19:33] <tomreyn> webmind: first topic under "known issues": https://discourse.ubuntu.com/t/hirsute-hippo-release-notes/19221#heading--release-upgrades
[19:34] <tomreyn> the blog post points to these release notes.
[19:35] <tomreyn> Indeed, the blog post states "You can upgrade to Ubuntu MATE 21.04 from Ubuntu MATE 20.10. " which makes it sound like you can do so *now*, which is misleading.
[19:36] <tomreyn> the "known issues" section of the blog post does point to the blocking bug.
[19:38] <tomreyn> Wimpress: you may want to consider editing the blog post to point out the 20.10 -> 21.04 upgrade path is not yet supported.