[03:35] <jbicha> duflu: there are reports of h264 videos being broken
[03:36] <duflu> jbicha, I think I'm on top of such bugs. Which ones?
[03:36] <jbicha> not sure the guys complaining have filed bugs yet :(
[03:38] <duflu> jbicha, maybe check these first: https://bugs.launchpad.net/ubuntu/+source/gstreamer-vaapi/+bugs?field.tag=radeon
[03:38] <jbicha> ok
[03:39] <duflu> jbicha, or generally https://trello.com/c/evbZkeCj
[03:41] <duflu> jbicha, please also forgive me for assigning these to you. I think I was just copying Marco... https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bugs?field.tag=fixed-in-3.28.2
[06:29] <seb128> good morning desktopers
[06:34] <willcooke> hey seb128
[06:37] <didrocks> good morning
[06:37] <seb128> hey willcooke :)
[06:37] <seb128> lut didrocks
[06:37] <seb128> had a good w.e?
[06:38] <didrocks> salut seb128, good week-end, and yourself?
[06:38] <didrocks> how was the travel?
[06:40] <seb128> quite nice, train FTW
[06:42] <didrocks> heh, well, once you skipped the TER :)
[06:42] <didrocks> how is Berlin?
[06:42] <seb128> Sunny
[06:43] <seb128> but didn't see much of it, I arrived at 23h yesterday
[06:44] <didrocks> ah, indeed… Coffee FTW as well thus?
[06:44] <didrocks> :)
[06:44] <duflu> Morning seb128, willcooke, didrocks
[06:44] <seb128> didrocks, indeed!
[06:44] <seb128> hey duflu, how are you?
[06:45] <oSoMoN> good morning desktoppers
[06:45] <duflu> seb128, going OK. I was pleased to see upstream already fixed my login failure. But then less pleased to find myself and others can't install bionic on some systems: bug 1767874
[06:45] <ubot5> bug 1767874 in ubiquity (Ubuntu) "ubiquity crashed with ValueError: invalid literal for int() with base 10: ''" [Critical,Confirmed] https://launchpad.net/bugs/1767874
[06:45] <seb128> lut oSoMoN
[06:46] <duflu> Hi oSoMoN
[06:46] <didrocks> hey duflu, salut oSoMoN
[06:46] <willcooke> hey duflu oSoMoN
[06:46] <willcooke> and didrocks
[06:46] <seb128> duflu, nice for the login bug, sounds like a good SRU candidate?
[06:46] <seb128> duflu, do you have details/ideas about what makes ubiquity unhappy on this machine?
[06:46] <duflu> seb128, it's on the list: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bugs?field.tag=fixed-in-3.28.2
[06:47] <seb128> duflu, the issue is different from https://gitlab.gnome.org/GNOME/gnome-shell/issues/227 ?
[06:47] <duflu> seb128, No idea. Just one laptop the installer keeps failing on. And 887 other reports from others
[06:47] <ubot5-ng`> GNOME bug 227 in gnome-shell "Login fails when preceded by incorrect password" (comments: 11) [Opened]
[06:47] <ubot5> Error: Gnome bug 227 could not be found
[06:47] <duflu> seb128, yes it's separate
[06:47] <seb128> k
[06:48] <duflu> Seems it only happens to people whose password starts with Shift+...
[06:48] <didrocks> hey willcooke
[06:48] <didrocks> ~7600 communitheme snaps installed!
[06:49] <willcooke> didrocks, \m/  that's amazing
[06:49] <oSoMoN> hey seb128, duflu, didrocks, willcooke, how are you?
[06:49] <seb128> oSoMoN, good! you? how was ubucon?
[06:49] <willcooke> oSoMoN, good conf?  How did your talk go?
[06:49] <duflu> I'm OK. You oSoMoN?
[06:49] <seb128> duflu, "traps: ubiquity[3581] trap int3 ip:7fd2ca14ec41 sp:7fffd3ffdfa0 error:0 in libglib-2.0.so.0.5600.1[7fd2ca0fd000+113000]" ... can you try to get a bt from that?
[06:49] <oSoMoN> I'm good, UbuCon was great, I enjoyed it very much
[06:50] <oSoMoN> and the talk went fine, it was well received apparently
[06:50] <oSoMoN> the ubuntu-fr loco team wants me to do it again next month at their Ubuntu Party in Paris
[06:51] <willcooke> oSoMoN, nice!! well done and thank you
[06:54] <seb128> duflu, could be the same as bug #1751252
[06:54] <ubot5> bug 1751252 in ubiquity (Ubuntu Bionic) "ubiquity crashed with signal 5 in _XEventsQueued()" [High,Triaged] https://launchpad.net/bugs/1751252
[06:57] <duflu> seb128, yeah maybe. Hard to verify as the version of glib changed
[07:02] <duflu> afk
=== pstolowski|eow is now known as pstolowski
[07:10] <seb128> didrocks, thanks for looking at/commenting on the initial setup issue
[07:16] <didrocks> seb128: yw!
[07:20] <seb128> it's annoying that the individual reports don't contain enough content to tell us if https://errors.ubuntu.com/problem/32345bd88e1c6091a5af096d1a5b22c13bdab1b6 is still bug #1723365
[07:20] <ubot5> bug 1723365 in gnome-session (Ubuntu) "/usr/share/session-migration/scripts/unity-gnome-shell-migration.17.10.py:5:g_settings_set_property:object_set_property:g_object_new_internal:g_object_new_valist:g_object_new" [Undecided,Fix released] https://launchpad.net/bugs/1723365
[07:20] <seb128> well still "Settings schema 'org.gnome.shell.extensions.dash-to-dock' is not installed\n"
[07:21] <seb128> did we ever safeguard that key usage?
[07:23] <didrocks> normally, we did
[07:23]  * didrocks looks
[07:24] <didrocks> ah, that one is not guarded
[07:25] <didrocks> seb128: I'll open a bug and assign it to me
[07:25] <seb128> didrocks, thx
[07:25] <seb128> I think we have a bug?
[07:25] <didrocks> seb128: well, it's duplicate to a fix release on another schema, correct?
[07:25] <seb128> didrocks, bug #1720310
[07:25] <ubot5> bug 1720310 in gnome-session (Ubuntu) "unity-gnome-shell-migration.18.08.py crashed with signal 5 in g_object_new_valist() due to gnome-shell-extension-ubuntu-dock not installed" [Medium,Confirmed] https://launchpad.net/bugs/1720310
[07:25] <didrocks> so it's a bad duplication, correct?
[07:26] <seb128> yes
[07:26] <seb128> e.u.c/apport can't tell "abort on a missing key" for different schemas/keys appart
[07:26] <didrocks> yeah, that's why it needs a new bug IMHO
[07:26] <seb128> it just has the stack of functions not the arguments
[07:26] <seb128> well ^
[07:26] <seb128> is that one no?
[07:26] <didrocks> ah
[07:26] <didrocks> second one
[07:26] <didrocks> good, yeah :)
[07:26] <didrocks> thx!
[07:27] <seb128> yw!
[07:27] <seb128> sorry for forgetting about it during the cycle
[07:27] <seb128> we said it was weird cases/wouldn't be important
[07:27] <didrocks> well, upgrades from 16.04 aren't supported yet :p
[07:27] <seb128> but e.u.c metrics shows quite some users hits it, so better to silent the error
[07:27] <didrocks> ah, from 17.10…
[07:27] <seb128> yes
[07:27] <didrocks> people force removing the dock? weird
[07:28] <seb128> or upgrading with apt without having ubuntu-desktop installed
[07:28] <seb128> such not getting the dock
[07:28] <didrocks> yeah, apt cowboying instead of d-r-u
[07:28] <seb128> likely
[07:28] <seb128> but it's still noise which is easy to fix
[07:29] <didrocks> anyway, I'll handle it
[07:29] <didrocks> correct
[07:29] <seb128> thx
[07:31] <seb128> oSoMoN, bug #1729963 is the most non-snap reported e.u.c, do you know if there is any way to communicate that upstream to motive them to look into the issue?
[07:31] <ubot5> bug 1729963 in chromium-browser (Ubuntu) "chromium-browser crashed in OnConnectionDisconnectedFilter()" [High,Confirmed] https://launchpad.net/bugs/1729963
[07:31] <seb128> bionic/weekly view
[07:32] <oSoMoN> seb128, yes, I reported it upstream already, lemme check the status there
[07:32] <seb128> right, I saw, I just don't know if we can tell them that it's hitting quite some users to motivate them to raise importance
[07:32] <oSoMoN> not much progress upstream
[07:33] <oSoMoN> yeah, I'll comment on the bug
[07:33] <seb128> thx
[07:56] <duflu> Ugh, morning in UK. And Launchpad gives up
[07:59] <seb128> duflu, I think they do live rollout around that time that impact it for 15 min or so often
[07:59] <seb128> more than U.K/europe waking up
[08:45] <didrocks> popey: hey, do you mind adding frederik-f to the communitheme group?
[08:45] <popey> didrocks: done
[08:47] <didrocks> thanks! :-)
[08:51] <czajkowski> Aloha
[08:53] <didrocks> hey czajkowski, how goes?
[09:00] <czajkowski> didrocks: it goes ok
[09:00] <czajkowski> upgraded last night to 18.04
[09:00] <czajkowski> :)
[09:01] <czajkowski> didrocks: and yourself ?
[09:02] <didrocks> czajkowski: upgraded a longgggggggg time ago :p
[09:02] <didrocks> czajkowski: going well ;)
[09:03] <czajkowski> didrocks: figured everyone would be on holidays now :)
[09:06] <didrocks> czajkowski: I wish! We have anyway a lot of days off in May, so it should work out
[09:09] <czajkowski> didrocks: are you still in France?
[09:09] <czajkowski> paris?
[09:09] <didrocks> czajkowski: I live in Lyon actually
[09:09] <didrocks> way better than Paris :p
[09:10] <czajkowski> didrocks: ah so not as badly affected with the evil strikes I faced 2 weeks ago when over there for deovxx france
[09:10] <czajkowski> didrocks: https://twitter.com/Czajkowski/status/990650246295379968  I ran into that issue on upgrade
[09:10] <czajkowski> currently fighting iwth my login into launchpad to log the issue
[09:12] <didrocks> czajkowski: well, the strikes are in the whole country, so impacted in some way, but don't need to commute at least :p
[09:12] <didrocks> czajkowski: yeah, please file a bug, we'll have a look
[09:31] <Laney> HI!
[09:31]  * Laney has been giving a tutorial :-)
[09:31] <seb128> hey Laney
[09:31] <seb128> what did you teach people about?
[09:31] <didrocks> hey Laney! What tutorial? ;)
[09:31] <Laney> autopkgtest
[09:32] <Laney> <- juliank sil2100 ->
[09:32] <seb128> oh, right
[09:32] <Laney> bus factor is being reduced
[09:32] <juliank> yes
[09:32] <Laney> or increased?
[09:32] <Laney> which way does that go?
[09:32] <didrocks> heh, I don't think juliank and sil2100 have seen the trap :p
[09:32] <Laney> how's it going?
[09:33] <seb128> Laney, do you know how to debug issues about "GNOME doesn't prompt for ssh passphrase" issues?
[09:33] <sil2100> It's a trap!
[09:35] <Laney> seb128: not so much, check $SSH_AUTH_SOCK is right?
[09:36] <Laney> seb128: try ueno on #gnome-hackers, that's the guy who mainly worked on this stuff last cycle
[09:36] <seb128> Laney, yeah, env is set and right
[09:37] <Laney> gnome-keyring starts a real SSH agent now and proxies for that
[09:37] <Laney> so there should be a process for it
[09:37] <Laney> with '-a <that directory>/.ssh'
[09:37] <seb128> yeah, it's for Simon, it's weird, he has the same processes/env that I get
[09:38] <seb128> like an ssh-agent pointing to /run/...keyring/.ssh
[09:38] <Laney> after that I don't know, sry, try ueno or get him to
[09:38] <seb128> k
[09:38] <seb128> thx
[09:38] <Laney> he's been quite responsive with me a couple of times
[09:38] <seb128> thx, he's going to ping him
[09:39] <Laney> cool
[09:39] <Laney> #techsupportsprint
[09:57] <cpaelzer> tkamppeter: hiho, I always had http://www.bchemnet.com/suldr/ for my printer so far, i wonder if for 18.04 I should expect dropping it would be fine?
[09:57] <cpaelzer> any info on what I should assume?
[09:58] <cpaelzer> if you think it should work I'd drop the old packages before the release upgrade and try to setup in 18.04
[10:37] <Laney> :q
[10:37] <Laney> NO!
[10:37] <Laney> :w:w:w
[13:27] <seb128> Wimpress, https://errors.ubuntu.com/problem/e85d2c87e86374f341f8ae14944592a3b9c9724c looks like one for you
[13:27] <seb128> they seem to be from your -welcome snap
[13:28] <seb128> the individual reports seems to be lot of reports from the same system(s), um1804 and hossam-Satellite-C50-A538
[13:28] <seb128> popey, ^ or maybe you?
[13:32]  * popey looks
[13:39] <seb128> those logs also have loops of "canonical-livepatch: permission denied"
[13:40] <popey> he's at the airport catching a flight home, I've pinged him about it on telegram tho
[13:55] <Wimpress> Thanks seb128 I'll take a look when I'm home.
[13:56] <Wimpress> I've taken a look at the errors links earlier, nothing immediately obvious.
[14:10] <seb128> Wimpress, popey, thanks
[15:05] <cyphermox> oi
[15:05] <cyphermox> I was pinged about https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1767720
[15:05] <ubot5> Launchpad bug 1767720 in ubiquity (Ubuntu) "Ubiquity crashed during install of 18.04 with error 'BadAccess (attempt to access private resource denied)'" [Critical,Confirmed]
[15:05] <cyphermox> looks like something odd maybe in GLib, any idea if there's something that might have caused it?
[15:06] <cyphermox> for one thing I find in a log Apr 28 20:12:59 ubuntu kernel: [  583.586561] traps: ubiquity[3853] trap int3 ip:7f2cd9202c41 sp:7fff6cb4df40 error:0 in libglib-2.0.so.0.5600.1[7f2cd91b1000+113000]
[15:06] <cyphermox> (but I'm not reproducing, and support has been unable to reproduce either)
[15:22] <willcooke> What does "Custom Bionic Beaver" mean in the LiveMediaBuild section?  Does that smell fishy?
[15:30] <kenvandine> willcooke, where?
[15:31] <willcooke> in the cyphermox posted to ^
[15:31] <kenvandine> oh
[15:34] <seb128> cyphermox, same as https://bugs.launchpad.net/bugs/1751252 ?
[15:34] <ubot5> Launchpad bug 1751252 in ubiquity (Ubuntu Bionic) "ubiquity crashed in debconf.py:104 with ValueError: invalid literal for int() with base 10: ''" [High,Triaged]
[15:35] <slashd> I missed cyphermox post, but I think he is refering to -> https://bugs.launchpad.net/bugs/1767720
[15:35] <ubot5> Launchpad bug 1767720 in ubiquity (Ubuntu) "Ubiquity crashed during install of 18.04 with error 'BadAccess (attempt to access private resource denied)'" [Critical,Incomplete]
[15:39] <seb128> yeah, seems the same as the one I mentioned
[15:39] <seb128> Apr 28 20:12:59 ubuntu kernel: [  583.586561] traps: ubiquity[3853] trap int3 ip:7f2cd9202c41 sp:7fff6cb4df40 error:0 in libglib-2.0.so.0.5600.1[7f2cd91b1000+113000]
[15:39] <seb128> Apr 28 20:13:09 ubuntu /install.py: ValueError: invalid literal for int() with base 10: ''
[15:39] <cyphermox> seb128: could be the same
[15:39] <seb128> cyphermox, the syslog has ^
[15:39] <seb128> which sounds the same issue
[15:39] <cyphermox> to be clear, the "invalid literal" is a red herring, I think
[15:40] <cyphermox> ubiquity crashes in some weird way, then debconf can't continue, it lost its input.
[15:42] <seb128> can anyone reproduce?
[15:42] <seb128> sounded like duflu could, we can ask him more tomorrow
[15:42] <cyphermox> seeing as jibel files 1751252, he might too
[15:43] <cyphermox> that was in february, though
[15:44] <seb128> whoever who can reproduce, would be useful to install libgtk-3-0-dbgsym and start ubiquity under gdb with --sync and "b gdk_x_error"
[15:44] <seb128> see https://stackoverflow.com/questions/30078005/how-to-break-on-gdk-x-error-using-gdb
[15:47] <willcooke> heading out, night all
[15:49] <Laney> SLACKER!
[15:49] <slashd> seb128, I can't reproduce but I have a crash in hand
[15:51] <slashd> seb128, https://pastebin.ubuntu.com/p/BgGsN3hNXv/
[15:52] <didrocks> Laney: :p
[16:03] <seb128> slashd, that's not very useful, xerror are async so it doesn"t tell us what is the error and who is the caller, we need to reproduce when --sync is used
[16:04] <slashd> seb128, gotcha
=== pstolowski is now known as pstolowski|off
[19:06]  * oSoMoN goes offline, have a good evening everyone, see you on Wednesday
[20:05] <d33tah> hi! i'm looking for someone who could help me debug my issue with 18.04 not initializing my motherboard gpu in xorg. any ideas where/who to look for?
[20:08] <Trevinho> seb128: hey, since tomorrow is 1st of may I guess we'll skip the meeting, right?
[20:08] <seb128> Trevinho, I don't think so, please send your weekly summary
[20:08] <seb128> it's not an holiday in the U.K or U.S afaik
[20:08] <Trevinho> ah ok...
[20:09] <seb128> Trevinho, hey btw :)
[20:09] <seb128> Trevinho, also I assigned you some bugs on launchpad, please triage/comment as appropriate
[20:10] <Trevinho> seb128: yeah, sure... I was swapping today so I'll look them better on 2nd
[20:10] <seb128> yeah, no hurry
[20:10] <seb128> enjoy the long w.e!
[20:10] <seb128> Trevinho, feel free to skip the weekly summary sending since you are off today/tomorrow
[20:11] <seb128> just pretend you didn't know :)
[20:11] <d33tah> is there a channel dedicated to xorg/lowlevel display aspect of ubuntu?
[20:11] <Trevinho> ahaha, well I can write a few lines
[20:15] <seb128> Trevinho, thx
[20:16] <seb128> Trevinho, enjoy the days off today and tomorrow :)
[20:16] <seb128> Trevinho, when are you back in Europe?
[20:16] <Trevinho> seb128: on 2nd
[20:16] <Trevinho> so tomorrow will be travelling
[20:16] <seb128> oh ok
[20:16] <seb128> safe travel!
[20:16] <sarnold> d33tah: none that I know of. it might be easier to file a bug report, tha way anyone who does work on it won't have to be active the same time you are
[20:16] <Trevinho> thanks
[20:18] <d33tah> sarnold: sounds like a solution, thanks. it's just that i was hoping for a synchronous experimentation
[20:19] <sarnold> d33tah: heh, yeah, when that works out it can be *way* faster ...
[20:20] <d33tah> sarnold: any chance you have some guidelines to reporting xorg regressions for ubuntu?
[20:21] <sarnold> d33tah: nothing specific to xorg, just the usual "report what you see, what you expected, include details" advice
[20:22] <sarnold> *loads* of xorg bugs are automatically filed with nearly no information on what went wrong, so a bug report with details would be a welcome change :)
[20:22] <d33tah> sarnold: it might me my first ubuntu bug. is there some tool that'd gather the usual info and add it as attachments?
[20:22] <sarnold> d33tah: the ubuntu-bug command line tool can collect whatever's most useful for a given package
[20:23] <d33tah> sarnold: danke!
[20:27] <d33tah> sarnold: awesome, broken
[20:27] <sarnold> d33tah: woot, you're on a roll :)
[20:28] <sarnold> d33tah: can you file a bug for *that* one too? :) if ubuntu-bug ubuntu-bug doesn't work, you can file on the website and maybe try to use apport-collect after the fact to collect the logs and so on
[20:28] <sarnold> https://bugs.launchpad.net/ubuntu/+source/xorg/+filebug
[20:28] <d33tah> sarnold: i'm afraid of filing a bug for my keyboard firmware in the laptop where i'm reporting a bug for my pc's kb not working ultimately
[20:29] <d33tah> if you get the joke
[20:29] <sarnold> I think so :)
[20:30] <d33tah> yay, worked for the second time
[20:38] <d33tah> sarnold: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1768128
[20:38] <ubot5> Launchpad bug 1768128 in xorg-server (Ubuntu) "Regression: monitor connected via motherboard GPU is not initialized, but one connected to Nvidia is" [Undecided,New]
[20:38] <d33tah> good bug report?
[20:39] <sarnold> d33tah: not bad, except for the 18.10 mention :D
[20:39] <d33tah> if they don't fix that, it'll be true in six months
[20:39] <sarnold> lol
[20:39] <d33tah> sarnold: thanks, clarified
[20:40] <sarnold> hrm some virtualbox stuff installed.. double-check that you don't have the virtualbox guest tools installed
[20:40] <sarnold> d33tah: time for me to run, good luck :D
[20:40] <d33tah> "dpkg -l | grep virtualbox | awk '{ print $2 }' | xargs sudo apt remove"?
[20:40] <sarnold> probably that's a bit drastic
[20:40] <d33tah> thanks sarnold. have a good one!
[20:41] <sarnold> just make sure the guest tools arent installed on real hardware :)
[20:41] <d33tah> it's not drastic, it's missing -y
[23:58] <jbicha> robert_ancell: I wonder if there's a way we can force gnome-initial-setup to be updated (assuming internet access) at the end of the install
[23:59] <jbicha> otherwise your SRU won't do much good until 18.04.1 for the common single user use case
[23:59] <robert_ancell> jbicha, does that not get covered by the "download updates" checkbox in the installer?
[23:59] <jbicha> technically that checkbox doesn't install updates, only downloads them
[23:59] <jbicha> that confused me for years and I'm sure it confuses a lot of other people