[06:10] <didrocks> good morning
[06:10] <jibel> Hi everyone
[06:12] <didrocks> salut jibel
[06:22] <jibel> Bonjour didrocks
[06:23] <oSoMoN> good morning desktoppers
[06:23] <pieq> Salut tout le monde !
[06:24] <pieq> jibel, is 19.10 beta out yet? Is it the same image as in http://iso.qa.ubuntu.com/qatracker/milestones/406/builds ?
[06:24] <didrocks> hey oSoMoN, salut pieq
[06:42] <jibel> pieq, yeah but it's broken, we need a new gnome-shell
[06:42] <jibel> pieq, bonjour :)
[06:43] <pieq> jibel, so should we wait to start testing?
[06:47] <jibel> pieq, actually latest image with the fix of ubiquity seems to be working so you can start testing.
[06:47] <jibel> pieq, it's build 20190926 on the tracker
[06:47] <jibel> (id 406)
[06:50] <oSoMoN> salut pieq, didrocks, jibel
[06:51] <pieq> jibel, merci ! downloading now
[06:56] <dupondje> Any idea's why a Qt software (keepassxc) resolution is broken on a HiDPi screen since 2-3 days (not many updates last days)
[06:56] <pieq> dupondje, on what version of Ubuntu?
[06:56] <pieq> and what version of keepassxc?
[06:57] <dupondje> Eoan
[06:57] <dupondje> 2.4.3+dfsg.1-1
[06:57] <dupondje> On Wayland btw, if that matters
[06:58] <pieq> dupondje, that's a lot of new software there :)
[06:58] <pieq> and Eoan is not even released yet, so it's moving a lot I assume
[06:59] <dupondje> its not moving that much anymore :)
[07:01] <dupondje> QT_AUTO_SCREEN_SCALE_FACTOR=0 keepassxc
[07:01] <dupondje> fixes it btw. weird
[07:04] <dupondje> aha found the cause :) nvm
[07:09] <pieq> dupondje, what was it?
[07:12] <dupondje> pieq: I had export QT_AUTO_SCREEN_SCALE_FACTOR=0 in my .profile, but some script created .bash_profile 2 days ago... which causes .profile not to be rread
[07:12] <dupondje> ah well :)
[07:15] <pieq> whoo, kernel panic on latest Eoan image
[07:26] <marcustomlinson> morning desktoppers
[07:27] <oSoMoN> morning marcustomlinson
[07:29] <didrocks> hey marcustomlinson
[07:31] <seb128> gooood morning desktopers
[07:31] <didrocks> salut seb128
[07:31] <marcustomlinson> hey seb128
[07:32] <seb128> lut didrocks, hey marcustomlinson, how are you today?
[07:32] <marcustomlinson> good thanks, it's friday :)
[07:33] <oSoMoN> salut seb128
[07:33] <didrocks> seb128: I'm fine, yourself?
[07:34] <seb128> lut oSoMoN, en forme ?
[07:34] <seb128> didrocks, I'm good, as marcustomlinson said it's sort of friday for me too :)
[07:35] <oSoMoN> la nuit fut courte, mais ça va plutôt bien
[07:35] <seb128> :-/
[07:35] <seb128> short night, long day, right? good luck!
[07:36] <oSoMoN> nah, days are always too short
[07:37] <seb128> they can also feel long when you lack sleep, but yeah
[07:38] <oSoMoN> I'm not feeling so badly sleep-deprived, fortunately
[07:52] <willcooke> moin
[07:53] <seb128> hey willcooke, how are you?
[07:53] <willcooke> hey seb128, feeling good that Trevinho found that lock up bug :)
[07:53] <willcooke> good work!
[07:53] <seb128> he's the man!
[07:53] <seb128> he and Laney rocked the fixes this week
[07:54] <willcooke> \m/  what a team
[07:54] <didrocks> hey willcooke
[07:54] <oSoMoN> good morning willcooke
[07:55] <willcooke> hihi
[07:55] <oSoMoN> I second this, great work by Trevinho and Laney
[08:00] <oSoMoN> chrisccoulson, thanks for publishing the firefox update!
[08:00] <Laney> morning
[08:00] <oSoMoN> and a reminder that the chromium-browser update for xenial and bionic is ready for publication
[08:01] <oSoMoN> hi Laney
[08:09] <Laney> hey oSoMoN
[08:09] <Laney> you well?
[08:09] <oSoMoN> yeah, all good on this side of the Pyrenees
[08:09] <oSoMoN> you?
[08:09] <seb128> hey Laney, how is it going?
[08:10] <Laney> hey seb128, you good too?
[08:10] <Laney> nice here, it is kind of sunny today for a change :>
[08:10] <seb128> Laney, I'm good :-)
[08:11] <seb128> still raining here, going to be that way for a while apparently...
[08:11] <Laney> :(
[08:12] <seb128> Laney, thx for ubiquity & gdm fixes you worked on this week, with the Trevinho fixes it feels like you are on top of the issues mostly atm :)
[08:14] <Laney> thanks
[08:14] <Laney> it's been a good one for fixing bugs that we introduced ;-)
[08:14] <Laney> I asked for ftp access to the gnome server, going to have to make upstream releases for gdm and stuff
[08:15] <seb128> ah, nice
[08:15] <seb128> halfline is on paternity leave I think (if I remember correctly what I read on IRC some days ago)
[08:15] <Laney> yes
[08:16] <Laney> so we sort of take over his stuff
[08:16] <Laney> 😈
[08:16] <seb128> b:)
[08:19] <seb128> (changing location, brb)
[08:53] <seb128> oSoMoN, what's the issue with the jsunit tests? it's not listed red on anything on update_excuses
[08:54] <seb128> why do we need to retry them?
[08:56] <oSoMoN> seb128, only the enigmail tests, not the jsunit ones
[08:56] <oSoMoN> but the trigger for the retry needs to be jsunit
[08:57] <seb128> oh, right, I read that the wrong way for some reason, sorry
[08:58] <oSoMoN> nw
[08:58] <seb128> oSoMoN, should that automatically happen as a reaction of the new version upload though?
[08:59] <seb128> ah, but the new jsunit is only in proposed
[08:59] <seb128> ignore that, doing the trigger :p
[08:59] <oSoMoN> thanks
[08:59] <seb128> done now
[09:36] <Trevinho> morning!
[09:36]  * Laney nods Trevinho 
[09:38] <Trevinho> Laney: hhhhheeeeyy
[09:39] <Laney> what is up
[09:42] <Trevinho> Laney: good, happy to be able to find the cause for the lockup... thanks to your broken setup :-).
[09:42] <Trevinho> on that, do we have time to prepare salsa + ubuntu?
[09:42] <Trevinho> I quickly did a ppa but I can shape if we want in now
[09:43] <Laney> not for the beta I don't think
[09:43] <Laney> the iso works anyway, can wait for first reviews
[09:43] <Laney> imho
[09:44] <Laney> good work on that
[09:44] <Laney> 🤘
[09:45] <Trevinho> yeah ir does not reliably but should mostly do. up to you guys
[09:45] <Laney> go ping Carlos or someone ;-)
[09:46] <oSoMoN> Trevinho, I confirmed that packages in the silo fix the grab for me
[09:46] <oSoMoN> (and good morning, too!)
[09:47] <Trevinho> oSoMoN: buen día!
[09:47] <Trevinho> and good to hear
[10:01] <Laney> laney@nightingale> ssh iainl@master.gnome.org
[10:01] <Laney> Creating home directory for iainl.
[10:01] <Laney> got the elite access now
[10:17] <seb128> hey Trevinho, how are you? well done on figuring out the issue!
[10:17] <seb128> Trevinho, did you check if it also fix the 'dialog not responding' case from L_aney?
[10:19] <Trevinho> Laney: yeah it's nice... sometimes I would like to use it for doing releases that are waiting maintainers for ages, but I never risked 😅
[10:20] <seb128> Laney, welcome in the club :-)
[10:20] <Trevinho> seb128: nope, but hardly can be the same.
[10:20] <seb128> Trevinho, right...
[10:27] <Laney> unfortunate!
[10:27] <Laney> and it means I'm 10€ down ;-)
[10:53] <jibel> in 19.10 we removed the snap of gnome-system-monitor but in previous release the upgrader was installing the snap and removing the deb. What do we do now?
[10:55] <jibel> remove it from the list of snaps to transition and reinstall the deb is the snap is installed?
[10:55] <jibel> if*
[10:55] <Laney> does the normal release upgrade install the .deb?
[10:55] <jibel> no
[10:55] <Laney> because.......
[10:56] <Laney> it has a static list?
[10:56] <jibel> yes, and we have no way to know if the snap have been installed during an upgrade or manually and intentionally
[10:57] <seb128> if the deb and the snap are installed the deb is first in the path right?
[10:58] <jibel> let me check on a default installation
[10:59] <Laney> the code in ubuntu-release-upgrader checks if it is tracking the stable/ubuntu-XX.YY channel
[10:59] <Laney> which is good enough for 'was installed automatically'
[11:00] <Laney> (at least from a quick reading of it)
[11:00] <jibel> seb128, /snap/bin is last in $PATH; so the deb should be launched first
[11:02] <seb128> ignore me, Laney's reply is more useful :)
[11:02] <Laney> well it doesn't have support for removing snaps
[11:03] <Laney> but I think it could do that if it was decided that is work worth doing
[11:03] <jibel> or we keep the snap, just remove the package from the list.
[11:03] <Laney> yes of course
[11:03] <jibel> much simpler
[11:04] <jibel> and safe
[11:04] <Laney> half arsed
[11:04] <Laney> but sure
[11:04] <jibel> seb128, willcooke ^ WDYT ?
[11:05] <jibel> I'll file a bug anyway
[11:07] <seb128> kenvandine, ^ since you are the one who triggered the change :p
[11:07] <seb128> as long as we install the deb the users at least get the right experience
[11:08] <willcooke> hmm
[11:08] <seb128> I don't have a strong opinion on snap clean, if we can do it without too much work that would be nice, it's probably not important enough to make it a priority though
[11:08] <willcooke> I think making the upgrader remove the snap is better, but feels too late to make that work reliably?
[11:09] <Laney> because?
[11:10] <willcooke> just seems like a big change at this point
[11:10] <willcooke> but if you think its doable...
[11:10] <Laney> for snap in remove list: if snap installed, if snap tracking ubuntu/..., remove snap
[11:10] <Laney> dunno, might turn out to eb harder, but it doesn't *feel* like it would be to me
[11:10] <willcooke> oh
[11:10] <willcooke> well
[11:10] <willcooke> I thought it would be harder than that :)
[11:11] <Laney> that's basically what it is for upgrades
[11:11] <Laney> one second
[11:11] <Laney> https://bazaar.launchpad.net/~ubuntu-core-dev/ubuntu-release-upgrader/trunk/view/head:/DistUpgrade/DistUpgradeQuirks.py#L815
[11:12] <seb128> jibel, do you feel like having a go at doing the change to remove it?
[11:14] <jibel> please add your conclusion to bug 1845485
[11:14] <jibel> seb128, yeah after beta
[11:14] <Laney> do we have a comment in the seeds to sync that list in there btw?
[11:14] <Laney> not sure I knew about it before now
[11:14] <seb128> jibel, thx
[11:14] <Laney> yes
[11:14] <Laney> good!
[11:15] <jibel> in the seed it's just snap:<package>
[11:15] <seb128> jibel, thx for fixing the emoji font in minimal btw, I think it makes sense to have those even in 'corporate' installs nowadays
[11:16] <Laney> yeh, I was just wondering if the seed told you to update the upgrader as well
[11:16] <Laney> and it does :>
[11:17] <seb128> keeeeennnnn
[11:17] <Laney> maybe every snap line should have a comment on it :p
[11:18] <jibel> and a git hook to send you a reminder when one changed a line with snap:
[11:19] <Laney> yes, now we're thinking smart
[11:19] <jibel> well, in a few month AI will fix it for us
[11:20] <Laney> git hook to trigger a sentient robot to copy the text over
[11:22] <seb128> Laney, do you mind if I re-purpose your pango ffe bug as a version-blocker-ff one? (and if it's fine can you just unsubscribe release team so they don't get spammed)
[11:22] <seb128> I can open a new one if you prefer
[11:23] <Laney> yes sure, can you give me the number so I can unsubscribe the team?
[11:23] <seb128> Laney, https://bugs.launchpad.net/ubuntu/+source/pango1.0/+bug/1842643
[11:23] <seb128> thx
[11:23] <Laney> GONE
[11:23] <seb128> excellent! :)
[12:25] <Wimpress> didrocks jibel Is ZFS support going to feature in the beta?
[12:28] <jibel> Wimpress, no, not in the beta
[12:28] <jibel> Laney, did you have time to start reviewing the MP for zfs in ubiqutiy?
[12:33] <Wimpress> jibel: Thanks. Will it make final?
[12:47] <jibel> I hope so
[13:00] <GunnarHj> Hello seb128, Great that ubiquity is in shape again. :)
[13:00] <GunnarHj> But I'm still bothered by this attempt to add a language:
[13:00] <GunnarHj> https://launchpad.net/ubuntu/+source/localechooser/2.71ubuntu4
[13:00] <GunnarHj> It doesn't show up. Probably there is more into it. Do you possibly know what that would be?
[13:02] <seb128> GunnarHj, sorry but I don't, maybe check with #ubuntu-installer, or look to the /var/log/install/dm log? (there are some wsarnings there about languages iirc)
[13:03] <GunnarHj> seb128: Ok, I'll try those ways. Thanks.
[13:07] <seb128> np
[13:24] <Laney> jibel: not yet, been fixing other things, likely to be tomorrow
[13:32] <kenvandine> sigh...
[13:32] <willcooke> hi kenvandine!
[13:32] <kenvandine> hey willcooke
[13:33] <marcustomlinson> hey kenvandine, why the sigh?
[13:33] <kenvandine> the deb to snap to deb transition issue
[13:36] <marcustomlinson> ah right
[13:39] <GunnarHj> seb128: I was wrong: "Ślůnski" does show up in Ubiquity, and I could "Try Ubuntu" with it. :)
[13:39] <GunnarHj> As you said there are indeed a couple of complaints in /var/log/installer/debug, and AFAICT that's the usual Python complaints about certain locales. In this case it complains about bn_BD and szl_PL, and it's bug #1646260.
[13:39] <seb128> k
[13:42] <seb128> on that note I drop offline for some hours for travelling, see you later
[14:32] <hellsworth> good morning btw
[14:33] <didrocks> hey hellsworth
[14:35] <hellsworth> how are things didrocks?
[14:45] <didrocks> hellsworth: things are going well, yourself? :)
[14:46] <hellsworth> quite good. enjoying my mornnig coffee :)
[14:50] <didrocks> heh
[15:26] <hellsworth> my laptop is on 19.10. It's plugged into the power and I can tell that at least physically the power is recognized since the led next to the power port on the laptop is lit up. However, the battery icon in the top bar doesn't indicate that it's charging at all. Shouldn't there be some indication?
[15:26] <Laney> yes
[15:27] <Laney> does upower know it is (upower -d)?
[15:27] <hellsworth> nope. it says state: discharging
[15:28] <hellsworth> i have a meeting in 3 min and i think the battery will be fine either way for the 45 min duration
[15:29] <Laney> /sys/class/power_supply/BAT0/status ?
[15:29] <mgedmin> hellsworth: what does upower -d say about when the status was last updated?
[15:30] <mgedmin> I once had a scare when upower showed me low battery for about 60 seconds right after resuming my laptop from suspend (it was plugged in while suspended and was actually charged to 100%)
[15:47] <oSoMoN> I'm calling it a day, back for more tomorrow, those of you who are out tomorrow have a great week-end!
[16:07] <hellsworth> Laney, mgedmin here's the output of upower -d
[16:07] <hellsworth> https://pastebin.com/AuhkFFSV
[16:08] <hellsworth> so during my hangouts meeting, the battery icon didn't change and still says 97%. so i know that it IS charging.
[16:08] <hellsworth> otherwise the percentage would have dropped
[16:10] <hellsworth> Laney, $ cat /sys/class/power_supply/BAT0/status
[16:10] <hellsworth> Unknown
[16:10] <Laney> suspicious!
[16:10] <hellsworth> indeed
[16:21] <ogra> encrypted battery !
[16:22] <hellsworth> a reboot with power plugged in, shows that the battery is at 100% and charging. if I unplug the power, the charging icon goes away and it says the battery is at 97%
[16:22] <hellsworth> plugging the power back in, shows the battery is at 100% and charging again.
[16:23] <hellsworth> rebooting without the power plugged in reproduces the situation where there is no change if you plug in the power
[16:23] <hellsworth> i'm going to file a bug
[16:32] <hellsworth> https://bugs.launchpad.net/ubuntu/+source/upower/+bug/1845532
[16:35] <Laney> I'd say to start with the kernel if the kernel's state is not right
[17:16] <hellsworth> Laney, I found lots of logs in journalctl that look like they could point to the root cause and attached them to the bug. Indeed many of them are kernel logs.
[17:37] <hellsworth> can i not edit my comments in launchpad?
[17:46] <sarnold> hellsworth: I don't think so, just the description and title. there's a 'hide' button but I've heard that it might only hide your posts from you. I've not been brave enough to click it on a 'real bug' to find out what happpens..
[18:20]  * kenvandine just filled a warranty claim on the SSD.  So annoying
[19:12] <hellsworth> sarnold, it looks like if i hide one of my comments, then that comment alone is just not displayed to others. i still see my hidden comment but it's grey'd out
[19:17] <sarnold> hellsworth: aha! thanks for testing :D
[19:25] <hellsworth> my pleasure! if i can't edit my comments, I want to at least be able to hide the ones that turn out to not be as helpful as I once thought it was :)
[21:32] <hellsworth> kenvandine, https://gitlab.gnome.org/GNOME/quadrapassel/merge_requests/15
[21:32] <gitbot> GNOME issue (Merge request) 15 in quadrapassel "snap: Update yaml to use GNOME extension" [Opened]
[21:38] <kenvandine> hellsworth: needs rebasing
[21:48] <hellsworth> done
[21:51] <willcooke> The new desktop beta iso is ready for testing if anyone has a mo
[21:51] <kenvandine> Thanks
[21:52] <hellsworth> ooh i'd like to give it a whirl
[21:52] <willcooke> ace, thanks hellsworth
[21:52] <willcooke> go here:  http://iso.qa.ubuntu.com/qatracker/milestones/406/builds/200088/testcases
[21:53] <willcooke> download the ISo from the link on that page to make sure you get the right one
[21:53] <willcooke> then pick a test from the list
[21:53] <willcooke> you can click on the test for instructions, and to see if anyone else is already doing it
[21:53] <willcooke> if you pick one, mark it as in progress, so we dont dupe too much
[21:54] <hellsworth> sounds good!
[21:56] <hellsworth> testing in qemu is ok?
[21:56] <hellsworth> or do all of these need to be on baremetal?
[21:57] <willcooke> vm is fine
[21:57] <willcooke> its good to get a mi
[21:57] <willcooke> mix
[21:57] <willcooke> I'd doing it on metal though
[21:58] <willcooke> ((I'm
[21:58] <willcooke> gah
[21:58] <willcooke> **I'm
[22:00] <hellsworth> how do you mark a line item as being in progress?
[22:02] <willcooke> click on the test and then at the bottom should be a form to fill in
[22:02] <willcooke> its possible that we need to add you to some more groups before that will work
[22:02] <willcooke> e.g. http://iso.qa.ubuntu.com/qatracker/milestones/406/builds/200088/testcases/1305/results
[22:02] <willcooke> scroll to the bottom, what do you see
[22:02] <hellsworth> oh i see. i was able to mark one as in progress
[22:04] <willcooke> oops, alt f4 the wrong keyboard :)
[22:15] <willcooke> hmmmm, either my USB stick is hosed, or something is very wrong
[22:15] <hellsworth> yeah i got a failed to boot from device
[22:15] <willcooke> hmm
[22:15] <hellsworth> but this is in virt-manager
[22:16] <hellsworth> i *just* setup qemu and virt-manager so i'm downloading 19.04 iso now to make sure that the vm setup is good, to be sure
[22:19] <hellsworth> no i had made a silly mistake pointing to the wrong iso. the build 200088 you pointed me to seems to boot
[22:21] <willcooke> hmm, well that wasnt good either.  My session crashed
[22:21] <sarnold> willcooke: you missed this while you were crashing < hellsworth> no i had made a silly mistake pointing to the wrong iso. the build 200088 you pointed me to seems to boot
[22:21] <willcooke> sarnold, ah!  nice one, thanks
[22:31] <hellsworth> willcooke, i'm trying http://iso.qa.ubuntu.com/qatracker/milestones/406/builds/200088/testcases/1307/results but when i boot the image i am booted to the "try ubuntu" or "install ubuntu" screen. F6 does nothing if i go down either path so i feel like i'm missing something here..
[22:32] <willcooke> hellsworth, ah, that's probably because you have or don't have secure boot enabled
[22:32] <hellsworth> do i need secure boot?
[22:32] <willcooke> I think that menu will only show up in non secure boot mode
[22:33] <willcooke> s'fine, let me test it on read hardware, it's probably easier
[22:33] <hellsworth> hmm ok i'll go look for another test case then
[22:34] <hellsworth> actually, i didn't realize the time. i need to go pick up my daughter from daycare. but i'll gladly pick up a test case tomorrow
[22:34] <willcooke> np, cheers hellsworth
[22:35] <hellsworth> "Install (manual partitioning re-using home partition) in Ubuntu Desktop amd64 in Eoan Daily " seems like a good one for non-secure boot vms :)
[22:36] <willcooke> yeah ,good plan
[22:37] <hellsworth> wait willcooke i'm off tomorrow (swap day)
[22:37] <hellsworth> i over volunteered myself
[22:37] <hellsworth> sorry about that
[22:38] <willcooke> np hellsworth, have a good one
[22:38] <sarnold> woot long weekend :D
[22:38] <hellsworth> in general though, i'm happy to test beta isos :)
[22:38] <willcooke> you say that now
[22:38] <willcooke> ....
[22:38] <willcooke> :)
[22:39] <hellsworth> i enjoy testing. girl scouts honor :)
[22:39] <willcooke> wait 'til it's the day before release at 4am
[22:39] <hellsworth> seriously though, next week i can help test the isos if you still need additional hands
[22:39] <hellsworth> :)
[22:39] <willcooke> cool, thanks
[22:39] <hellsworth> ok cheers!
[22:46] <willcooke> jibel, is the casper crash I just got when trying to use luks the one you mentioned earlier?
[22:55]  * willcooke 's house echos with the sound of "screenreader on"
[22:56] <willcooke> jibel, correction, the FDE does seem to work, it's "free software only" that shits the bed
[23:51] <willcooke> I give up, I can't think straight anymore.
[23:51] <willcooke> Thanks for testing Wimpress
[23:51] <willcooke> I think it's good enough for beta
[23:51] <willcooke> probably going to start late tomorrow