 Good evening friends - just joined the group. I've installed 21.04 (Budgie flavor). So far, so good! Only issue I've seen is that the "Budgie Welcome" screen doesn't do anything when clicking on it
 welcome @theNew0rder and Matt
 @bashfulrobot has your team noticed this issue? (re @Matt: Good evening friends - just joined the group. I've installed 21.04 (Budgie flavor). So far, so good! Only issue I've seen is that the "Budgie Welcome" screen doesn't do anything when clicking on it)
 @Leokolb have you noticed the above?
 No have not seen that - running a quick test on latest ISO (re @philipz: @Leokolb have you noticed the above?)
 Budgie welcome screen works normally for me.
 New to me. HM. Trying to figure out the best way forward.  Maybe on our discourse.ubuntubudgie.org (re @philipz: @bashfulrobot has your team noticed this issue?)
[05:04] <qydw_> It seems all of the bugs that I have encountered are related to Wayland. Hope Wayland could be better when 21.10 is released.
 qydw_: as wayland is default for ubuntu 21.04, many bugs will be ironed out for the next release.
 welcome Alex
 Hi Yousuf
 did you need any info about how to test for the testing week?
 Thanks, I think I am ok. Found all the info I need over here https://discourse.ubuntu.com/t/ubuntu-21-04-testing-week/21519 👍
 great. which flavor or remix are you testing?
 Testing Xubuntu 21.04 on a Thinkpad X1 Carbon Gen 9 (Tiger Lake). Specially looking at the mesa drivers, thermal handling, acpi issues, and similar.
 great
 welcome @dasbjo
 Thx. I will upgrade my thinkpad used for work from 20.10 to 21.04 running Ubuntu Mate and take a look
 Thx. I will upgrade my thinkpad used for work from 20.10 to 21.04 running Ubuntu Mate tomorrow and take a look (edited)
[09:51] <lotuspsychje> dasbjo: devel releases best to test clean instead of upgrades until final release
[11:18] <lotuspsychje> feel free to ask here about your bug rtpg
 But e.g. possible usrmerge problems wouldn't occur on clean installs,?
 But e.g. possible usrmerge problems wouldn't occur on clean installs? (edited)
 Upgrades from 20.10 is a valuable test in itself. Sometimes catches package issues that clean  installs wouldn't.
[11:20] <lotuspsychje> i agree, but it can also give upgrade issues where devs dont need the extra work digging out the real bug
 Finding package upgrade issues before release is important... post release most upgraders would assume a smooth uplift and if it isn't could result in a broken system.
[11:24] <lotuspsychje> i agree it also has to be tested, but in the real field we often see broken previous installs trying to upgrade and then break due the user itself
[11:24] <lotuspsychje> you should see the bugs in #ubuntu-bugs-announce we need to filter these days
[11:27] <lotuspsychje> we can state that the devs these days are drowning in bugs
 I understand you don't want to be thrown with bugs which are usergenerated because they existed somehow before
 I agree - testing the upgrades is extremely important - that is why we do and have the testscases on the QA tracker site.. (re @fossfreedom: Finding package upgrade issues before release is important... post release most upgraders would assume a smooth uplift and if it isn't could result in a broken system.)
[14:05] <rtpg> I'm trying to figure out what is going on with gnome-terminal on my machine since upgraading to 21.04, right now (through an emacs shell, cuz that opens fine at least, but not Terminal or Tilix) when doing `/usr/bin/gnome-terminal` the window appears for a split second then disappears, the program returning
[14:06] <rtpg> (nothing with `-v` passed in either, and not really eseing anything in the logs either.... wondering if I can like... somehow breakpoint to just before the program exits or something
[14:08] <rtpg> (not seeing it in xwininfo -tree -root, thinking it was maybe moving somewhere else but...)
[14:12] <rtpg> (was using the proprietary nvidia drivers so was in Xorg. Set up the open source drivers, and then tried wayland, same stuff... thinking this might be an issue at the Gnome level
 didn't see the upgrade testcase for the beta. (re @Leokolb: I agree - testing the upgrades is extremely important - that is why we do and have the testscases on the QA tracker site..)
 Happy @popeydc Birth
[15:24] <rs2009> popey: Happy birthday :D
[15:27] <Maik> from me too... Happy Birtday popey.
 Upgrade testcases are for the dailys (re @philipz: didn't see the upgrade testcase for the beta.)
 Upgrade testcases are for the dailys - the betas are archived (edited) (re @philipz: didn't see the upgrade testcase for the beta.)
 thanks @Leokolb, though i was mistakenly looking in each distro, while upgrade has its own 'Prodcut (Upgrade)' section. :D
 curious why there are any i386 entries in upgrade when 20.04 and 20.10 don't have i386 releases.
[18:47] <xu-help67w> hey so for when 21.04 comes out do i have to update to 20.10 first or can you go directly from 20.04
[18:55] <Maik> probably the wrong channel to ask in
[18:56] <fossfreedom> First to 20.10 then to 21.04
[18:58] <Maik> heh... they left :/
 I had a bad experience updating from 20.04 to 20.10. The update was fine, but the upgrade to 20.10 to me to a Gnome desktop instead of Xubuntu. It was a pain getting everything in order, I suggest to take a snapshot before upgrading. (re @ubuntutesting_bot: [irc] <xu-help67w> hey so for when 21.04 comes out do i have to update to 20.10 first or can you go directly from 20.04)
 Testing the Lubuntu daily today, and when I tried to test the live session, it just skipped all the setup and went straight into launching Lubuntu. I've looked through Launchpad to try and find a bug that matches - you know, due dilligence! - but I was wondering if anyone here knew this bug off hand, or what I would run in the terminal to get useful information for this.
 Lubuntu don't have a try/install screen. (re @madhens: Testing the Lubuntu daily today, and when I tried to test the live session, it just skipped all the setup and went straight into launching Lubuntu. I've looked through Launchpad to try and find a bug that matches - you know, due dilligence! - but I was wondering if anyone here knew this bug off hand, or what I would run in the terminal to get useful information for t
 I mean booting straight to the live session is normal for them, IIRC
 I had been going off this page - http://iso.qa.ubuntu.com/qatracker/milestones/419/builds/229074/testcases/1303/results (re @RikMills: Lubuntu don't have a try/install screen.)
 But if this isn't an issue than that is totally okay with me!
 For starters that says ubiquity, but they have been using calamares for several releases now. The try install thing is also a ubiquity thing. So that test case is wrong (re @madhens: I had been going off this page - http://iso.qa.ubuntu.com/qatracker/milestones/419/builds/229074/testcases/1303/results)
 Ahhhh! Well, I helped test the testcases :)
 We need to get our test cases updated.
 I think @Leokolb made a bug for that.
 We did have a chat somewhat recently about refreshing the test cases - I am pinging @franksmcb (whenever he is free, no rush!)  if he has the info handy. And we can work on good measures in place moving forward with the next cycle to be sure the testcases are updated for stock and the flavors before testing starts in earnest.
[19:24] <rwkeating_> If you run an install on a legacy bios machine, create your own partitions (leaving no room for /boot/efi nor creating one) there is no warning.  The install will fail much later when it tries to install GRUB.  Is /boot/efi really needed on a legacy bios machine?  If so, shouldn't this be checked before you leave the partition page?
 I can't find Leó's bug on my phone. I totally agree on getting them updated I know @guiverc made a start on that and we never circled back. (re @madhens: We did have a chat somewhat recently about refreshing the test cases - I am pinging @franksmcb (whenever he is free, no rush!)  if he has the info handy. And we can work on good measures in place moving forward with the next cycle to be sure the testcases are updated for
 We'll pick it up again. 😊 But Lubuntu is looking gorgeous and installed perfectly in my VM! Marked it as passed. Have to say, Lubuntu's aesthetics are gorgeous! (re @kc2bez: I can't find Leó's bug on my phone. I totally agree on getting them updated I know @guiverc made a start on that and we never circled back.)
 As usual, if there's anything I can do in an official community rep capacity, just ping me and I'll add it to my to-do list starting Monday!
 i did the same in 20.04, many of the testcases had bugs in them and i filed bugs on the testcases (re @madhens: Ahhhh! Well, I helped test the testcases :))
 Mind looping me in on this too (re @madhens: We did have a chat somewhat recently about refreshing the test cases - I am pinging @franksmcb (whenever he is free, no rush!)  if he has the info handy. And we can work on good measures in place moving forward with the next cycle to be sure the testcases are updated for stock and the flavors before testing starts in earnest.)
 unfortunately getting fixes to the testcases was a slow process and still many of my bugs are still open - https://bugs.launchpad.net/ubuntu-manual-tests/+bugs?search=Search&field.bug_reporter=philipz85
 Let me see what I can do about that (re @philipz: unfortunately getting fixes to the testcases was a slow process and still many of my bugs are still open - https://bugs.launchpad.net/ubuntu-manual-tests/+bugs?search=Search&field.bug_reporter=philipz85)
 thanks. i see that both you and i attempted to fix this one - https://bugs.launchpad.net/ubuntu-manual-tests/+bug/1868370
 Of course! I have notes for the meeting we had with Brian on my work email. (re @cwayne: Mind looping me in on this too)
[20:11] <guiverc> bug 1922342 was originally OP reporting it won't boot; in fact it's just slow.  from grub it's ~8min 45secs before plymouth logo appears, and >10 mins before the 'try/install' appears on screen...   BUT it appears & runs; is this [slow boot] issue impacting many?
 thanks. i see that @guiverc and I attempted to fix this one - https://bugs.launchpad.net/ubuntu-manual-tests/+bug/1868370 (edited)
 Danke (re @madhens: Of course! I have notes for the meeting we had with Brian on my work email.)
 I'll have my team look at some of these open merge proposals
 \o/
 Moving over here from IRC.  My post is above posted from IRC as "rwkeating"
 welcome @rwkeating
 Thanks.  I hope to be of some value in testing.
 we are looking forward to it. which flavor/remix are you testing?
 kubuntu
 I posted an issue above while installing 21.04
 Efi partition is required even for legacy install. If you chose auto install that's what the installer does. It's same on other flavors (definitely on UM). I don't remember if there is bug report for what you asked, but we did discuss this on our community forum. Can't give more details, I am not in front of PC. (re @ubuntutesting_bot: [irc] <rwkeating_> If you run an install on a legacy bios machine, create your own par
 The first I saw this was on 20.10.  I thought it had been fixed.  Since efi is now needed, I think there should be a warning if you don't create it or if the installer can't create it for you.  Thanks for your response.  I won't keep harping on this :)   Most folks probably wont ever hit this.
 Yes I saw first on 20.10 too. Agree there should be warning before hand.
 I've noticed that the new installers make no mention of a swap file. Not have a swap file for older computers will little RAM my be a problem. (re @saivinob: Efi partition is required even for legacy install. If you chose auto install that's what the installer does. It's same on other flavors (definitely on UM). I don't remember if there is bug report for what you asked, but we did discuss this on our community forum. Can't 
 I didn't make a swap partition, but if I look using the free command it shows I have a swap, so it looks like a swap file is created automatically if there is no swap partition.
 yep, that has been default since 18.04 (re @rwkeating: I didn't make a swap partition, but if I look using the free command it shows I have a swap, so it looks like a swap file is created automatically if there is no swap partition.)
 That was a great idea. (re @Maik_aD: yep, that has been default since 18.04)