/srv/irclogs.ubuntu.com/2018/10/02/#ubuntu-desktop.txt

=== Class7_ is now known as Class7
=== ecloud is now known as ecloud_wfh
didrocksgood morning06:36
didrockshum, my gdm GNOME Shell went crazy CPU wise06:48
didrockscan't reproduce it now though06:49
dufluMorning didrocks06:50
dufluGood or bad06:50
oSoMoNgood morning desktoppers06:51
dufluHi oSoMoN06:52
didrockshey duflu & oSoMoN06:53
dufludidrocks, my user session gnome-shell used to do that occasionally. Stayed high for some time before dropping.06:53
didrocks:(06:53
dufluMaybe it was the old deferred garbage collection. And it hasn't happened since we started using much more frequent collection06:55
oSoMoNhey duflu, salut didrocks07:02
oSoMoNpopey, is there a way to get rid of borders around small images in posts on discourse.ubuntu.com ? https://discourse.ubuntu.com/t/monday-1st-october-2018/8203/10 looks kind of ugly07:02
=== pstolowski|afk is now known as pstolowski
dufluoSoMoN, may try switching between inline and reference syntax?? https://daringfireball.net/projects/markdown/syntax#img07:06
duflu+be07:07
dufludidrocks, I wonder in 19.04 if using the Ubuntu purple wallpaper for the login screen might look nice, or terrible07:11
oSoMoNduflu, nah, I even tried BBCode and HTML tags, I guess the border is a CSS property applied to all small images, regardless of how they are defined07:12
dufluoSoMoN, including the old style <img .... border=0> ?07:13
dufluwhich is apparently deprecated in HTML 507:13
oSoMoNah, I didn't try that07:18
oSoMoNlet's see07:18
didrocksduflu: we can't use wallpapers, due to multimonitor handling in gnome-shell/gdm being bad07:21
oSoMoNduflu, doesn't work either, nor style="border: 0", which I suppose makes sense, the CSS takes precedence over style attribute in HTML07:22
WimpressMorning desktopers07:26
dufluHi Wimpress. Can you answer oSoMoN's question about discourse? ^07:27
oSoMoNgood morning Wimpress07:34
seb128good morning desktopers07:41
TrevinhoMorning folks07:42
oSoMoNsalut seb12807:42
oSoMoNbuon giorno Trevinho07:42
seb128lut oSoMoN, en forme ?07:42
jibelduflu, hi, any idea about the problem with Optimus systems upgraded from 17.10 reported on https://community.ubuntu.com/t/cosmic-cuttlefish-18-10-beta-testing/8132/17 ?07:43
seb128hey Trevinho, how was Lille btw, I forgot to ask yesterday07:43
seb128lut jibel07:43
jibelSalut seb12807:43
TrevinhoMerci oSoMoN y seb07:43
didrockshey seb12807:43
oSoMoNseb128, peu dormi, mais oui, le contrecoup viendra après le déjeuner…07:43
didrocksmorning Trevinho07:43
seb128lut didrocks07:43
seb128oSoMoN, siesta! :)07:43
oSoMoNI wish…07:43
seb128:(07:43
seb128good luck, they eventually do their nights one day :p07:44
willcookeandyrock, jamesh - updates please:  https://discourse.ubuntu.com/t/monday-1st-october-2018/820307:45
willcookemorning07:45
jameshwillcooke: writing it now07:45
willcookemerci jamesh07:45
jibelI like this new format to report status updates BTW07:46
willcookeExcellent!  Me too.  I like oSoMoN's icons especially :)07:46
dufluAlso, you can write your reports almost in changelog format. Only the third indent needs to be - and not .07:48
oSoMoNseb128, can't even blame the baby, I just went to bed late and then I couldn't sleep for some reason07:48
duflujibel, I usually assume I know nothing about Optimus but will check that bug again07:48
seb128oSoMoN, ah ok, those happens too!07:49
willcookeanyone will a Dell E6430?  https://bugs.launchpad.net/nouveau/+bug/1683445  The OEM team don't have one07:50
ubot5Ubuntu bug 1683445 in OEM Priority Project "E6430 brightness control not working" [Critical,Confirmed]07:50
Trevinhoseb128: very nice... Sunny and tasty salamis there 😂. But really liked. Not touristy, and the place we had was really nice.07:50
seb128great07:50
seb128willcooke, I've a 6410 but it's intel only so I guess not good enough to test that bug07:50
seb128willcooke, why did they flag it "oem priority" if they can't even test it?07:51
willcookeseb128, No worries. I'm not sure what we do in this case,  the OP (I think) says he hasnt got the hardware, OEM dont have the hardware, so...07:51
willcookeindeed07:51
willcooke(brb, supermarket delivery)07:51
seb128we do validate that it has no regression I guess07:51
seb128the fix might not work but if it doesn't make things work07:52
seb128and it's supposed to work in theory...07:52
oSoMoNseb128, how would you feel about pushing LO 6.1.2 to cosmic now? (as opposed to SRUing it after release, which might end up being a SRU of 6.1.3, skipping 6.1.2)07:52
oSoMoNIIRC Bjoern used to play it safe and prepare a SRU for just after the release07:53
seb128oSoMoN, +1 from me for uploading now, I think Bjoern was over-cautious, especially for non LTS cycles07:57
oSoMoNok, I'll prepare and upload today07:58
seb128great07:58
oSoMoNricotz, FYI ^07:58
ricotz+1 :)07:59
seb128you also know libreoffice better than me, how is their testing/the stability of their stable serie updateS?07:59
* Laney nods08:01
willcookewhat up Laney08:01
oSoMoNhey Laney08:04
oSoMoNseb128, pretty good in my limited experience, stable series updates are really bugfix-only releases08:05
seb128hey Laney, how are you?08:06
seb128oSoMoN, good then :)08:06
duflujibel, done and done08:07
jibelduflu, thanks08:08
didrockspopey: hey! do you mind adding jagger to the yaru / communitheme team? He did some good work on icons and the team +1 on his inclusino08:09
didrocksinclusion*08:09
Laneyhi willcooke oSoMoN seb12808:14
didrockseven if he has some insane proposal sometimes: https://discourse.ubuntu.com/t/call-for-participation-an-ubuntu-default-theme-lead-by-the-community/1545/1798 (IMHO :p)08:15
Laneyhad an early night so i'm good today #thuglyf08:15
Laneysup08:15
seb128early night ftw!08:15
seb128(I did the same ;-)08:15
willcooke:)08:20
* duflu looks forward to not being jet lagged08:21
duflu#hazylyf08:21
Laneycoldlyf too08:22
Laneystupid autumn08:22
didrocks:(08:24
* didrocks isn't completely out of it yet08:24
seb128of the jetlag between Lyon and Brussel? ;)08:25
seb128Lyon is so far south that it takes a while to adjust :p08:25
didrocksno, the cold :p08:25
seb128ah08:25
seb128:)08:25
didrocksstill coughing08:25
seb128:(08:26
seb128get better!08:26
seb128the kid started sneezing this morning, it's that season again. I hope I'm not next on the list :/08:26
didrocksthx! yeah, good luck :(08:27
jibeldoes ubuntu-bug xserver-xorg works for anyone on cosmic?08:39
didrocksjibel: got the password prompt twice, but I'm on the send/don't send dialog08:42
didrocksand it seems the included info are correct08:42
jibelhm, it hangs forever here08:42
jibeldidrocks, did you accept to attach DM logs?08:44
didrocksjibel: yes, I accepted both08:44
jibelweird, it's blocked on the execution of pkexec /usr/share/apport/root_info_wrapper /tmp/tmpo_kbx2jf/:script:08:45
jibeland :script: is empty08:45
didrocksDM logs is the first prompt, correct?08:45
didrocks(I have 2)08:45
didrocksso, first prompt -> yes -> password; second prompt (for nvidia) -> yes -> password08:47
jibelk, seems to be just me then. i'll search a bit08:48
jibelthx08:48
didrocksyw08:49
willcookeSuddenly my Cosmic machine wont boot to a greeter09:39
ograit wants to be a server but is too shy to tell you09:40
willcooke:)09:40
willcookeReinstall sorted10:08
willcookeI will do more testing10:08
Trevinhojibel: as per https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1794292 have you been able to reproduce this again? As I can't anymore it seems now while I lost my /var/crash file :-(10:12
ubot5Ubuntu bug 1794292 in plymouth (Ubuntu Cosmic) "plymouthd crashed with SIGSEGV in /sbin/plymouthd:11 in ply_renderer_set_handler_for_input_source -> ply_keyboard_stop_watching_for_renderer_input -> ply_keyboard_stop_watching_for_input -> ply_device_manager_deactivate_keyboards -> on_deactivate" [High,Confirmed]10:12
jibelTrevinho, I haven't tried since last week. Let me start a VM with latest cosmic10:13
jibelTrevinho, I explained cypher_mox yesterday how to reproduce it but no news since then10:14
willcookejibel, I'm seeing a segfault in network manager on Cosmic at start up - did you ever see that?10:21
willcookeit restarts and then seems ok10:23
jibelwillcooke, no, I didn't10:23
willcookedifferent topic, why is colord lookin for MIB files?!10:24
RAOFwillcooke: If I had to guess, it would be libsane doing something not quite.10:37
* willcooke digs in the logs10:38
tjaaltondidrocks: replied to vulkan review10:38
Trevinhojibel: ah, I got it again10:40
jibelTrevinho, me too10:46
jibelgnome-initial-setup is broken10:47
jibelit shows the online account page and skip or next buttons do nothinh10:48
jibelg10:48
jibelis it known?10:48
jibelandyrock, ^10:49
andyrockjibel: let me check10:49
andyrockjibel: last iso?10:50
jibelandyrock, fresh installation10:50
jibelandyrock, yes10:50
Trevinhojibel: also got it...10:51
andyrockjibel: i'll take a look10:52
andyrockworks here when tested on a vm10:52
andyrockbut not from the last iso10:52
Trevinhojibel: also found the issue :)10:54
willcookeheh, when I could finally get in to a working session g-i-s worked ok for me.  Odd.11:01
willcookeHowever, I can't get to a log in screen in a normal boot.11:02
willcookejibel - before I do digging, you think that is known?  I boot and just get a flashing cursor11:02
willcooketty on 211:02
willcookeok, I think that network manager issues was just a thing.  It looks ok now11:07
willcookeseb128, do you have your Inspiron to hand?11:10
willcookeHere's what I'm seeing:  Installed daily from yesterday  - all fine.  Boot machine, get to a black screen with a flashing cursor.  Got to tty2 look at syslog, all seems OK.  Got to tty<something between 3 and 7> a mouse pointer appears.  Go back to 1 and there is gdm.11:11
andyrockjibel: works fine here11:11
willcookeWithout moving ttys, I just stick at the black screen11:11
andyrockjibel: I installed the last iso on a VM11:12
willcookelogout gets back to gdm11:12
willcookeandyrock, g-i-s working fine here too11:12
* willcooke -> sandwich11:13
willcooke<- sandwich11:13
andyrockjibel: maybe something is preventing the click to go through?11:14
andyrockjibel: otherwise I'm happy to debug the issue if you send me the vm image11:14
popeydidrocks: did you ping me somewhere? I saw it when on the train this morning, but can't find it now11:23
dupondjenetwork-manager-gnome broke since the update this morning :(11:28
dupondjeanyone e noticed this already? :)11:28
willcookedupondje, ah, I noticed a segfault in n-m11:31
willcookebut might be unrelated.11:31
willcookeHow is it broken for you?11:31
dupondjewillcooke: dropdown doesn't show wifi networks anymore11:32
willcookechecking11:32
willcookehuh, and this time when I booted my machine I did get to gdm11:32
dupondjeand I have VPN connections for example, those show, but if I click on one, it suddenly connected to another wifi network11:32
dupondjeseems like something got randomized :D11:32
popeyoSoMoN: fixed, no borders round images now. how does that look? :) https://community.ubuntu.com/t/monday-1st-october-2018/8203/10?u=popey11:32
dupondjeneither it does show that I'm connected to a VPN, while I am (connected via the settings)11:33
willcookedupondje, drop down not showing wifi networks - in GNOME Shell?11:33
willcooke'cos I dont think the drop down ever did11:33
dupondjewillcooke: gnome-shell / wayland yes :)11:34
dupondjewell you can connect to another wifi via the dropdown ... ?11:34
willcookeFrom the indicator?11:35
dupondjewillcooke: ofcourse? like https://i.stack.imgur.com/QVr1V.png11:41
dupondjehttps://dflinux.frama.io/thebeginnershandbook/img/deb9-wifi-gnome-1.png11:41
dupondjeWiFi is gone now here :) in the indicator11:42
willcookedupondje, can you check the logs and see if network manager crashed?11:44
willcookeI saw a seg fault this morning, but it seems OK now, and the indicator is working as expected11:44
dupondjewillcooke: NetworkManager[1826]: corrupted double-linked list11:45
dupondjebut it restarted afterwise :)11:45
dupondjeseems to be something else. Yesterday it was fine, today its broken. Seems like only network-manager-gnome package could be the cause?11:46
willcookeI need to get my cosmic machine booting to gdm again and then I can look at this a bit more11:47
willcookebear with me11:48
Laneydupondje: which version of gnome-shell?11:51
dupondjehttp://ubuntu.dupondje.be/bug.jpg -> this it how it looks like here :)11:52
dupondjeLaney: 3.30.0-1ubuntu211:53
Laneythere were some fixes to network status reporting in 3.30.0-3ubuntu111:53
oSoMoNpopey, perfect, thanks!11:53
dupondjeLaney: still in proposed I guess?11:55
Laneyit'll migrate shortly11:55
andyrockcan I propose a branch to only show desktop file from session-shortcut only in Unity?11:56
andyrockseb128, Laney ^^^11:57
Laneygnome-shell has its own versinos of those right?11:59
dupondjeLaney: confirmed that resolved it! thx11:59
dupondjewillcooke: ^11:59
andyrockLaney: yep, they got an-all-in-one button11:59
Laneyok with me then12:00
Laneydupondje: nice12:00
seb128andyrock, unity only sounds fine to me yes12:03
andyrockkk preparing a debdiff12:03
seb128willcooke, I do have the inspiron, I'm going to download the daily iso and do test installs on it12:03
seb128willcooke, that sounds a timing bug from what you describe, might have to do/be a bug in the new gdm which is stopping the greeter when not needed now (to not have another session in memory for nothing)12:04
seb128Trevinho, you got a fix for that plymouth issue? well done!12:04
jibelandyrock, I cannot send a VM image12:04
jibelit's several GB and will take days to upload12:05
seb128do you get any error on the command line if you start it manually?12:05
jibelandyrock, actually it seems to be a problem with xorg, the screen is not refreshing completely12:07
jibelif I minimize/restore the window it's as expected12:08
andyrockjibel: ah, yeah I wrote before that maybe something was preventing the click to go through12:08
andyrocktry also to just move the window around12:09
willcookeseb128, yeah switching to tty2 and then back to tty1 brings up gdm12:12
Laneya debug log would be good (turn it on in /etc/gdm3/custom.conf, reproduce the bug and then grab the journal)12:13
seb128willcooke, can you maybe enable Debug=true in /etc/gdm3/gdm.conf, reboot, get the issue and open a bug with ubuntu-bug gdm3?12:13
LaneyIW IN12:13
seb128or what Laney said for the filename :p12:13
LaneyAHAHAHAH12:13
seb128:)12:13
willcookedupondje, Laney @ n-m: ack, thanks12:14
Laneythat sounds related to this work in 3.30 though12:14
Laneyif so it'll be one to file upstream as well probably, for halfline to have a look at12:15
Laneywe already fixed a few like that12:15
* Laney sammich12:15
seb128willcooke, bonus point if you file the bug with log on gitlab: )12:15
* willcooke gives it a go12:15
=== pstolowski is now known as pstolowski|lunch
willcookehm, I dont see anything obvious in the logs12:24
didrockspopey: yeah, I was asking if you can add jaggers to the communitheme/yaru team group please12:29
seb128willcooke, no need for it to be obvious, it should be verbose is the debug=true worked and hopefully include the details upstream needs12:36
willcookek, updating to proposed seems to have fixed it12:59
willcookesorry12:59
willcookeI will retest a few times12:59
=== pstolowski|lunch is now known as pstolowski
* didrocks is fighting still on gsconnect…13:07
jbichawillcooke: I'm unable to reply to the team report community thread13:08
jbichaI have a concern about the tracker MIR13:09
didrockstseliot: you could have written that in the description :/13:12
didrockstseliot: so basically I've spent the whole morning reviewing the MIR for nothing?13:12
tseliotdidrocks: wrong ping?13:13
didrockstseliot: sorry, was for tjaalton :)13:13
tseliotgood :)13:13
didrockstoo many t*13:13
didrockstjaalton: please have a look ^ and you didn't explain why the split (I requested this) and the difference: what would be in vulkan vs vulkan-loaders, what the MIR will use then13:14
didrocksand as long as it's not NEWed, I don't think I'm going to rereview it, as those questions aren't answered :/13:14
popey@didrocks done13:15
didrocks(if I understand correctly, vulkan is going to be an empty package, split in 4 sources, but only -loader would need a MIR)13:15
didrockspopey: thanks!13:15
didrockswould like a confirmation still, quite unclear13:15
seb128jbicha, the hub topic is not supposed to be for discussion, that's by design13:17
seb128we discuss topics on IRC during the meeting13:17
seb128or we said we would have a "discussion" post for comments13:17
jbichaso I should just start a regular desktop topic for the tracker issue?13:19
seb128or raise it to discuss during the IRC meeting13:19
seb128as you prefer13:19
seb128or talk about it here now13:19
jbichaopening a topic since it's easier to read there13:19
seb128good13:19
jbichahttps://community.ubuntu.com/t/tracker-stuck-in-cosmic-proposed/822413:21
tjaaltondidrocks: the split was mentioned in the description13:21
willcookejbicha, ah.  My bad.  popey please could you grant jbicha permission to post to the weekly updates topic?13:21
tjaaltondidrocks: only loader will need the MIR13:21
jbichawe can discuss elsewhere but that gives background easier13:21
tjaaltondidrocks: upstream did the split, so it had to be repackaged13:22
didrockstjaalton: right, but you could have said to not review vulkan then13:22
didrocksMIR is already unfun, we were supposed to have 2 people from the desktop team but seems the plan was cancelled, and I'm not really fond of loosing a morning on things like that :/13:23
willcookejbicha, caught up with backlog now - so yeah, that list is for weekly updates, which you might still want to post to,  so we should still sort that, but as seb said, discussion should be in a new topic and/or the meeting13:23
didrockstjaalton: so, basically, only -loaders, once NEWed will need a MIR review?13:23
didrockswhich is a subpart of vulkan13:23
didrockscorrect?13:23
jbichaI didn't prepare an update for this week so unless I type really fast…13:23
tjaaltondidrocks: correct13:24
popeywillcooke: done13:24
willcookethanks popey13:24
didrockstjaalton: ok, and as you said, the vendoring will not be part of the package anymore13:24
willcookejbicha, you can add it later if you like13:24
tjaaltonno way to file it against vulkan-loader before it's in the archive, my mistake for subscribing ubuntu-mir then, it was meant to be a placeholder13:24
didrockstjaalton: so, I suggest that you look at my comments, and already fix some I had if that applied to the new package13:24
didrocksso that already this is done and we win a loop13:25
didrockshowever, we'll need someone to NEW the package first13:25
tjaaltonI've tried13:25
didrocks(I don't want to cumulate NEWing and MIRing, better having someone else having a look)13:26
didrocksjbicha: the tracker code is very different than the one we used to have in main13:28
didrocksand as I have written, I already have doubt security-wise on file permissions13:28
didrocksI don't think telling "double guessing what the MIR team applied and bypass security" is a good option13:28
seb128it's too late in the cycle to promote/add to default install anyway13:29
willcookeIt's meeting time13:29
willcookeDo you want a few mins to wrap that up? ^13:29
willcookeOr we can do it in the meetnig13:30
didrocksI guess in meeting if needed is good13:31
willcookeLaney, seb128, just before we start - now running proposed at I've got gdm up 4 times out of 4 so far13:31
willcookegoing for #5 now13:31
willcookeok, goingt to start then13:31
willcooke#startmeeting Desktop Team Weekly Meeting - 2018-10-0213:31
meetingologyMeeting started Tue Oct  2 13:31:59 2018 UTC.  The chair is willcooke. Information about MeetBot at http://wiki.ubuntu.com/meetingology.13:32
meetingologyAvailable commands: action commands idea info link nick13:32
=== meetingology changed the topic of #ubuntu-desktop to: Home of the Desktop Team, https://wiki.ubuntu.com/DesktopTeam | For help or questions, try #ubuntu | Work (read-only for non-developers): https://trello.com/b/3VYBPFaR/ubuntu-desktop-1810-cycle | Amaterasu watches over you benevolently | Desktop Team Weekly Meeting - 2018-10-02 | Current topic:
seb128:)13:32
willcookeRoll call: andyrock, dgadomski, didrocks, duflu (out), jbicha, jamesh (out), jibel/heber, kenvandine, laney, oSoMoN, seb128, tkamppeter, trevinho, robert_ancell (out), tjaalton, tseliot13:32
seb128hey13:32
andyrocko/13:32
didrockso/13:32
kenvandine\o13:32
tselioto/13:32
oSoMoNo/13:32
jibelo/13:32
willcookeNew format this week then everyone.  You should have had a chance to review people's updates.  I've had no messages for anyone in far away places that they want to raise any topics.13:32
hebero/13:33
jbichao/13:33
willcooke#topic Round table13:33
=== meetingology changed the topic of #ubuntu-desktop to: Home of the Desktop Team, https://wiki.ubuntu.com/DesktopTeam | For help or questions, try #ubuntu | Work (read-only for non-developers): https://trello.com/b/3VYBPFaR/ubuntu-desktop-1810-cycle | Amaterasu watches over you benevolently | Desktop Team Weekly Meeting - 2018-10-02 | Current topic: Round table
willcookeBy a show of hands, does anyone have anything they want to raise based on the updates from the rest of the team, or otherwise?13:33
willcookei.e. if no one wants to talk about anything, then we can move on to rls bugs13:33
tjaaltono/13:33
didrocksjust that I'm fighting with gsconnect extension13:34
didrocksupstream is really responsive13:34
didrocksI hope to upload a new snapshot soon13:34
willcooketjaalton, is that "I want to talk about something" or just a "I'm here!"?13:34
didrocksit will still be in universe, but if people want to give a test13:34
willcookedidrocks, that's great to hear, thanks!13:34
tjaaltonwillcooke: I'm here :)13:34
didrocksthe idea is that the code will be close to what we want to ship by default next cycle13:34
Laneybetter13:34
didrocksso, the earlier you test with your phone, the better :)13:35
seb128just for next time, maybe standardize on a round of "o/ I've a topic"13:35
didrocksthat's it for me13:35
seb128then we can go round between those who said that13:35
seb128with the chair giving the turn to each13:35
seb128otherwise it's going to be cahos13:35
willcookethat's what I was going for here13:35
didrocksseb128: +113:35
seb128willcooke, right13:35
LaneyNM's definitely being crashy here too, took me a while to get online after rebooting just then13:35
seb128but tjaalton did an unclear o/13:35
seb128and didrocks just wrote13:35
didrocksyeah, better to standardize13:36
jbichao/13:36
seb128lol13:36
seb128see jbicha also :p13:36
willcookeI have a question as well13:36
willcookeok, let's start with jbicha13:36
willcooke#topic jbicha13:36
=== meetingology changed the topic of #ubuntu-desktop to: Home of the Desktop Team, https://wiki.ubuntu.com/DesktopTeam | For help or questions, try #ubuntu | Work (read-only for non-developers): https://trello.com/b/3VYBPFaR/ubuntu-desktop-1810-cycle | Amaterasu watches over you benevolently | Desktop Team Weekly Meeting - 2018-10-02 | Current topic: jbicha
seb128was that a raise of hand or an "hey"?13:36
jbichaI had a tracker question but it was late so maybe discuss that on the community site?13:36
seb128we can discuss it now13:37
seb128imho13:37
jbichaok: https://community.ubuntu.com/t/tracker-stuck-in-cosmic-proposed/822413:37
jbichacan we fast track the tracker mir?13:37
seb128no13:38
didrocksdidn't we just discuss how bad the idea of fast tracking the tracker mir ?13:38
kenvandinegotta track the tracker13:38
seb128security team has some backlog, we have no impact on that, and in fact we are more import MIRs we want to get through (portals)13:38
jbichadidrocks: sorry, I might have missed that discussion13:38
seb128and it's not a good idea to add a feature that late13:38
didrockson the MIRing side, this is my view:13:39
didrocksjbicha: the tracker code is very different than the one we used to have in main13:39
didrocksand as I have written, I already have doubt security-wise on file permissions13:39
jbichaok, maybe I'll talk to mbiebl about letting the package split in13:39
didrocksI don't think telling "double guessing what the MIR team applied and bypass security" is a good option13:39
seb128would need a ffe at least13:39
seb128I would be fine deleting the new tracker from cosmic-proposed13:39
seb128it didn't migrate out and we don't need that update13:39
seb128but if you have an easy fix that works too13:39
seb128it's getting a bit late to land a new version now (having it not migrated out of proposed yet means it virtually haven't landed/got testing)13:40
jbichalet's see if the split works, otherwise I'm fine with dropping it from -proposed13:40
seb128wfm13:40
jbicha /next topic13:40
willcookecool, thanks. We know where we're going then13:40
willcooke#topic willcooke13:40
=== meetingology changed the topic of #ubuntu-desktop to: Home of the Desktop Team, https://wiki.ubuntu.com/DesktopTeam | For help or questions, try #ubuntu | Work (read-only for non-developers): https://trello.com/b/3VYBPFaR/ubuntu-desktop-1810-cycle | Amaterasu watches over you benevolently | Desktop Team Weekly Meeting - 2018-10-02 | Current topic: willcooke
willcooketjaalton, I'm keen to hear if you're any closer to understanding why virtualbox machines won't start without nomodeset13:41
willcookeThat's a release blocker for me13:41
tjaaltonwillcooke: the kernel driver init takes 25-30s on initial boot, probably because the driver is not in the installer initrd13:42
tjaaltonthis triggers a weird race in xserver which has been there for some time already13:42
seb128"probably because the driver is not in the installer initrd"13:42
seb128how can we get that "probably" out of the sentence?13:43
jibelhas the vbox driver already been in the installer initrd?13:43
seb128that13:43
seb128and if it was, when/why has it been removed?13:43
Trevinhoseb128: is not according to lsinitrd13:43
jibeland if it was not why is it failing now?13:43
Trevinholsinitramfs13:43
Trevinhomaybe we're faster in doing something else and thus....13:44
Trevinhothe issue.13:44
=== Class7_ is now known as Class7
Trevinholike we try to start x when things are not ready yet, while before this was delayed by something else. This sometimes happen.13:44
seb128$ lsinitramfs /boot/initrd.img-4.4.0-116-generic | grep virtual13:44
seb128lib/modules/4.4.0-116-generic/kernel/drivers/regulator/virtual.ko13:44
seb128on xenial13:44
seb128so it was in the initramfs13:45
Trevinhoas per listing initrd there's no x11 related video drivers there13:45
seb128or is that a different one?13:45
didrockslib/modules/4.18.0-8-generic/kernel/drivers/regulator/virtual.ko13:45
didrocksit's still in the initramfs13:45
tjaaltonseb128: vboxvideo13:45
seb128didrocks, wrong name, sorry :p13:45
seb128tjaalton, that was not in xenial either13:45
didrocksthis one is not, was it in xenial?13:45
didrocksok13:45
Trevinhoyeah, no video driver is there iirc13:45
andyrockis it possible to add it and test  if it works?13:45
tjaaltonseb128: maybe X started later then13:46
Trevinhoah, some are.13:46
seb128tjaalton, but the foundamental issue is an xorg one right?13:46
Trevinhobut just lowlevel fb stuff13:46
tjaaltonthere's a window of like 3s.. X starts at 25s (here), vboxvideo init done at 27s13:46
tjaaltonTrevinho: huh? my initrd has all from drivers/gpu/drm13:47
Trevinhotjaalton: oh, yeah... sorry. Not vbox though13:47
tjaaltonvbox is in staging13:47
seb128I'm not sure that discussion is actually productive working toward a resolution13:48
willcooketjaalton, is this issue on your radar? Are you activly looking in to it?13:48
seb128tjaalton, is a team owning the problem/actively working on resolving it?13:48
willcookeDo you need something from us to help?13:48
seb128and which team does/should own it13:49
tjaaltonI don't know how to fix this13:49
seb128?13:49
seb128well, what changed compared to bionic13:49
seb128is the vboxvideo init slower?13:49
TrevinhoAlso, this is related also to the one on kvm with std driver, isn't it?13:49
Trevinhowhile it has a different way of applying, but might be related to the same xorg issue in not trying better to reload or what?13:49
seb128tjaalton, is that a kernel regression? like does it work using the bionic kernel?13:50
tjaaltonTrevinho: somewhat, but it's fixable by enabling drm/bochs13:50
tjaaltonseb128: I don't know13:50
Trevinhogdm-wise we could change something as trying to load things for more time or what?13:50
Trevinhoreload*13:50
seb128k13:50
seb128I suggest that's not a topic that's going to be resolved in the meeting13:51
seb128it needs actual debugging and understanding of the problem13:51
Trevinhowell, at least to have a pointer I mean...13:51
Trevinhonot details, but a direction.13:51
willcookeYeah, seb128, jibel - lets chat about how we can try and get more of an understanding about what's going on later on13:51
seb128that's 10 min we are on the topic and I don't feel like we got anything useful out of it13:51
willcooke /next topic13:51
tjaaltonseb128: testing an older kernel would mean building the installer image with cosmic userland13:52
willcooketjaalton, we can chat more about this after the meeting13:52
tjaaltonsure13:53
willcookeWe're not going to solve it now13:53
willcookethanks13:53
willcookeI dont think anyone else had any topics, so we can move on to rls bugs13:53
Trevinhowell13:53
TrevinhoI've few branches for review and I'd like to get the SRU on XUbuntuCancel for search provider in, so reviews would be appreciated. There's also a silo to test and in case to publish in seconds if all fine13:53
Trevinhoso... just an heads up on that. Ah, and also a gnome-calculator fix.13:54
willcookeLinks are in your post on the hub right Trevinho?13:54
Trevinhoyep13:54
willcookethx13:54
seb128k13:54
TrevinhoI wanted to mention in the 1st part but I didn't know how things were organized yet :)13:54
Trevinhoand suddently topic changed :)13:55
willcookeok, any more before we review rls bugs?13:55
andyrocko/13:55
willcooke#topic andyrock13:55
=== meetingology changed the topic of #ubuntu-desktop to: Home of the Desktop Team, https://wiki.ubuntu.com/DesktopTeam | For help or questions, try #ubuntu | Work (read-only for non-developers): https://trello.com/b/3VYBPFaR/ubuntu-desktop-1810-cycle | Amaterasu watches over you benevolently | Desktop Team Weekly Meeting - 2018-10-02 | Current topic: andyrock
andyrockI got 2-3 MPs in salsa13:56
andyrockthey have been there for a while13:56
andyrockis anyone willing to review them?13:56
andyrocknot sure it fit here13:56
seb128I can help with some13:56
andyrockkk thanks I'll send you the links later13:56
willcookethx13:56
Laneytwo things13:56
Laney#debian-gnome is better for debian sponsoring13:57
Laneyand I don't know that using this round for "please review my stuff" is good13:57
Laney(that is feedback)13:57
andyrockkk thanks13:57
seb128andyrock, duflu usually list the things he's waiting for sponsoring in his update, I think that's a good place13:57
seb128I try to unblock things he has listed13:57
andyrockmakes sense13:57
andyrockthanks for the feedback13:57
seb128I would have done the same for yours (in fact I spotted the g-c-c one and have a tab opened on it)13:57
seb128yw13:57
seb128Trevinho, ^ you as well13:57
Trevinhoindeed13:58
seb128but yeah, similar to Laney13:58
seb128I think we derailed the purpose13:58
seb128those "those needs <...>" should be in the summaries13:58
willcooke+113:58
seb128or we recreate a round table of updates on IRC13:58
willcookelet's do that for next week13:58
willcooke /next topic13:58
Trevinhono, no... that's fine to define a strategy here and then we follow in the updates.13:58
willcookeany one else?13:58
seb128can we do rls now? ;)13:58
willcookeyes13:59
seb128thx :)13:59
TrevinhoSince we had not, better to define one13:59
willcooke#topic Release Bugs13:59
=== meetingology changed the topic of #ubuntu-desktop to: Home of the Desktop Team, https://wiki.ubuntu.com/DesktopTeam | For help or questions, try #ubuntu | Work (read-only for non-developers): https://trello.com/b/3VYBPFaR/ubuntu-desktop-1810-cycle | Amaterasu watches over you benevolently | Desktop Team Weekly Meeting - 2018-10-02 | Current topic: Release Bugs
seb128right13:59
willcookeOk, we're going to skip the rls-bb-tracking bugs this week only, because the list is very long and Seb wants to spend some time tidying it up before we review13:59
willcookerls-bb-incoming is empty (enough)14:00
willcookeso rls-cc-incoming first, why not14:00
willcookehttp://reqorts.qa.ubuntu.com/reports/rls-mgr/rls-cc-incoming-bug-tasks.html14:00
willcooke1 issue: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/179542114:00
ubot5Ubuntu bug 1795421 in gnome-control-center (Ubuntu) "[cosmic] sidebar requires scrolling" [Low,Confirmed]14:00
willcookeNice to have but not a blocker IMO14:01
seb128rls-cc-notfixing imho14:01
seb128it's a minor cosmic issue14:01
seb128we should fix it but it's not a release blocker14:02
willcooke2 votes for notfixing14:02
willcookeanyone opposed?14:02
willcookegoing once14:02
willcooketwice14:02
willcookegone14:03
willcookebug updated and commented14:03
willcookerls-cc-tracking now:14:03
willcookehttp://reqorts.qa.ubuntu.com/reports/rls-mgr/rls-cc-tracking-bug-tasks.html14:03
willcookehttps://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/179428014:04
ubot5Ubuntu bug 1794280 in xorg-server (Ubuntu Cosmic) "gdm doesn't start on a fresh installation of Cosmic Desktop" [Critical,Confirmed]14:04
didrocksthis is the vbox issue?14:04
* didrocks opens14:04
willcookeI think that might be the same bug I saw earlier and is fixed in proposed afaict14:04
willcookedidrocks, no, different thing14:04
Trevinhodidrocks: not only, also on kvm..14:04
jibelthis is qemu and hw14:04
LaneyMarco got assigned that bug last week, it's a different task on the same one14:04
Trevinhoyep, I've spent time in debugging, but something gdm specific, is as the vbox one something related to the init14:05
willcookeTrevinho, so WIP still?14:05
Trevinhoso... not much desktop stuff, unless we decide to change gdm way of starting up14:05
seb128Trevinho, on https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1794292/comments/11 (which is linked) you wrote "the patch should be fine", what patch is that?14:05
ubot5Ubuntu bug 1794292 in plymouth (Ubuntu Cosmic) "plymouthd crashed with SIGSEGV in /sbin/plymouthd:11 in ply_renderer_set_handler_for_input_source -> ply_keyboard_stop_watching_for_renderer_input -> ply_keyboard_stop_watching_for_input -> ply_device_manager_deactivate_keyboards -> on_deactivate" [High,Confirmed]14:05
Laneydifferent bug?14:06
Trevinhoseb128: as per https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1794292/comments/1014:06
seb128that doesn't have a patch :p14:06
Trevinhoseb128: https://launchpad.net/ubuntu/+source/plymouth/0.9.3-1ubuntu914:07
seb128Laney, could be, it's unclear to me, sounds like we are conflicting vbox/plymouth/other issues14:07
Trevinhoyep... these are two different things14:07
seb128anyway14:07
seb128that should be assigned to Trevinho, as Laney said that was the outcome from the previous meeting14:07
seb128so let's do that and move on?14:07
willcookeTrevinho, can you update the bug pls?14:07
seb128we can discuss technical details after the meeting if needed14:07
Trevinhoseb128: as said, not really much i can do on that...14:07
willcookek, lets talk about it more later14:08
willcookehttps://bugs.launchpad.net/ubuntu/+source/gnome-calculator/+bug/179495114:08
ubot5Ubuntu bug 1794951 in gnome-calculator (Ubuntu Cosmic) "Calculator (snap) is slow to start on a freshly installed Cosmic machine" [High,Confirmed]14:08
TrevinhoI had this assigned, but I marked the gdm as invalid. So I can assign to myself if you want me to look at other places I don't know exaclty14:08
willcookeI raised that one, but having spoken to Ken earlier today there are other more important things and that issue is probably not a release blocker14:08
Laneylooks like that one skipped the process :P14:08
willcookeso I'm happy to untag14:09
willcookeLaney, yeah I should have incoming that one, sorry14:09
Trevinhowillcooke: fixing that would be quite easy though, it's just few lines of snapcraft if he's busy It takes few minutes.14:09
willcookekenvandine, could you chat to Trevinho about that? ^14:09
kenvandineyeah14:09
willcookeTrevinho, I'm not so sure, but would be interesting to see14:09
willcookenext:14:10
willcookehttp://launchpad.net/bugs/179293214:10
ubot5Ubuntu bug 1792932 in xorg-server (Ubuntu Cosmic) "Cosmic Desktop fails to boot in vbox: Xorg assert failure: Xorg: ../../../../dix/privates.c:384: dixRegisterPrivateKey: Assertion `!global_keys[type].created' failed." [High,Triaged]14:10
willcookeThats the virtualbox bug which we already talked about14:10
willcookenext: https://bugs.launchpad.net/ubuntu/+source/perl/+bug/174321614:10
ubot5Ubuntu bug 1743216 in xdg-utils (Ubuntu Cosmic) "perl crashed with SIGABRT in _dbus_abort()" [High,In progress]14:10
* Trevinho is pretty sure this and 1794292 are two different faces of the same medal14:10
willcookeLooks like it might be fixed already, but is in progresss14:10
Trevinho[previous one]14:10
seb128the fix is in the queue yes14:11
seb128needs to be approved by someone from r-t (other than L_aney)14:11
willcookeI can validiate that one I think14:11
willcookenext: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/178524014:11
Laneyit's fine, that one is on track14:11
ubot5Ubuntu bug 1785240 in gnome-software (Ubuntu Cosmic) "Cancelling snapd authorization triggers error notification" [Low,In progress]14:11
andyrockis this really a release blocker?14:11
andyrock:)14:11
andyrockbtw the fix is upstream (both in gnome-software, snapd-glib, and snapd)14:12
andyrockin cosmic Robert needs to take care of gnome-software14:12
andyrockthe rest has already been uploaded14:12
willcookeyeah not a release blocker14:13
andyrocknot so much I can do also because I don't understand how Robert deals with gnome-software uploading14:13
willcookethe last one is a security issue:14:13
willcookehttps://bugs.launchpad.net/ubuntu/+source/evince/+bug/178892914:13
ubot5Ubuntu bug 1788929 in evince (Ubuntu Bionic) "Debian/Ubuntu AppArmor policy gaps in evince" [Undecided,Triaged]14:13
willcookeand that's the end of the list14:13
seb128looks like jd_strand is on it14:13
willcookeAny comments on rls bugs before we move on?14:14
didrocksnope14:14
seb128no14:14
willcookeok, moving on14:14
willcooke#topic Trevinho14:14
=== meetingology changed the topic of #ubuntu-desktop to: Home of the Desktop Team, https://wiki.ubuntu.com/DesktopTeam | For help or questions, try #ubuntu | Work (read-only for non-developers): https://trello.com/b/3VYBPFaR/ubuntu-desktop-1810-cycle | Amaterasu watches over you benevolently | Desktop Team Weekly Meeting - 2018-10-02 | Current topic: Trevinho
willcookeTrevinho, you had something you wanted to raise14:14
Trevinhoyeah, as per SRU of mutter/gnome-shell to bionic... despite the upstream pings it looks like a point version for 2.28 is taking ages14:15
Trevinhothere are still some relevant issues like http://launchpad.net/bugs/1727356 that should be pushed14:15
ubot5Ubuntu bug 1727356 in mutter (Ubuntu Bionic) "Login screen never appears on early generation Intel GPUs (Core2 and Atom etc)" [High,Triaged]14:15
Trevinhobut waiting for a stable...14:15
seb128I'm not sure that's a team topic?14:15
TrevinhoI'm happy to cherry-pick, but... should I go with that or what?14:16
seb128like it's fine to have as a channel discussion with me/your usual sponsors at any time14:16
seb128no?14:16
TrevinhoI want to know how to proceed...14:16
seb128right14:16
seb128I'm just saying you don't need the full team attention for that14:16
seb128let's discuss it out of the meeting?14:16
Trevinhook, as you prefer.14:16
willcookeok, last topic:14:17
willcooke#topic AOB14:17
=== meetingology changed the topic of #ubuntu-desktop to: Home of the Desktop Team, https://wiki.ubuntu.com/DesktopTeam | For help or questions, try #ubuntu | Work (read-only for non-developers): https://trello.com/b/3VYBPFaR/ubuntu-desktop-1810-cycle | Amaterasu watches over you benevolently | Desktop Team Weekly Meeting - 2018-10-02 | Current topic: AOB
willcookeAnyone got anything?14:17
LaneyI'd be interested to know who is still watching now14:17
andyrocko/14:17
Laneyafter all this format was less boring14:17
Laney:-)14:17
didrockso/14:17
jibelI am14:17
NafalloI'm mostly confused :-)14:17
Trevinho👀14:18
seb128o/14:18
willcookeComment: we need to find a better way than waiting for "anyone... anyone... Bueller"14:18
seb128less boring, but that one didn't feel as smooth as I was expecting14:18
oSoMoNo/14:18
Laneyyes indeed14:18
seb128I guess that's normal for a first try though14:18
Laneywhere can we give our Useful Feedback™?14:18
didrocksseb128: agreed14:18
oSoMoNgotta get used to the new format, I like the new format with a post on the hub a lot more14:19
didrocks(is it time to list those who didn't answer that they are following? :p)14:19
seb128same14:19
seb128Laney, feedback here or by reply to willcooke's email I would say?14:19
seb128willcooke, ^ wdyt?14:19
andyrocklol14:20
Laneyok14:20
LaneyI'd prefer rls tracking updates in the status posts themselves14:20
Laneythat bit disrupted the flow a lot for me and I think could have been done offline14:20
seb128me too, at least for the -tracking review part14:20
willcookewas just typing, yeah, I think email is right, then we dont generate noise here waiting for everyone's feedback14:20
seb128I didn't really understand why we did/did it this way14:20
Laneyand getting into the discussion of bug details should be avoided more imho, but that's not a new issue14:20
Laneyotherwise I like it more14:20
seb128like most are assigned, post ff we used to just have people listing their bugs in a section with the status of each14:21
willcookeok, please summarise your feedback via email and next meeting will the FTW14:21
willcooke*be14:21
seb128Laney, yeah, we keep falling back into discussing the issues :/14:21
seb128:)14:21
seb128thx!14:21
willcookeSo we still need to talk more about the virtualbox issue14:22
Laneyeom?14:22
seb128wrap?14:22
seb128we also need to talk to Trevinho about his SRUs :)14:22
willcookejust checking if there was anything else we still need to talk about14:22
willcookethat14:22
willcookeok, EOM14:22
willcooke#endmeeting14:22
=== meetingology changed the topic of #ubuntu-desktop to: Home of the Desktop Team, https://wiki.ubuntu.com/DesktopTeam | For help or questions, try #ubuntu | Work (read-only for non-developers): https://trello.com/b/3VYBPFaR/ubuntu-desktop-1810-cycle | Amaterasu watches over you benevolently
meetingologyMeeting ended Tue Oct  2 14:22:46 2018 UTC.14:22
meetingologyMinutes:        http://ubottu.com/meetingology/logs/ubuntu-desktop/2018/ubuntu-desktop.2018-10-02-13.31.moin.txt14:22
Trevinhohonestly I don't see that as a problem. Or maybe we should also add a post-section were we analyze the things14:22
andyrockthanks lunch time for me14:22
kenvandine👍14:22
didrocksthx!14:22
oSoMoNthanks everyone!14:23
Laneytoo late kenvandine14:23
LaneyBUSTED14:23
seb128andyrock, enjoy!14:23
Trevinhoas this is the moment where more eyes are around and so easier to have better ideas. More than just a 1:1 thing14:23
seb128Trevinho, what are you refering to?14:23
oSoMoNandyrock, man, it's almost dinner time in the UK, you're terribly jet-lagged ;)14:23
Trevinhodiscussing the issues14:23
Trevinhoso that who's interested can check the details...14:23
willcookeNext week's post is here: https://discourse.ubuntu.com/t/monday-8th-october-2018/822114:24
Trevinholike... issue #12345678, need more talking... -> #aftermeeting.14:24
Trevinhoso we do it know, but having this as a procedure.14:24
seb128Trevinho, it's fine to discuss work like the vbox one imho, but it's not useful to try to discuss bugs we didn't read/try to understand yet (the incoming list) or that are being handled and don't need discussion14:24
Trevinhothanks willcooke14:24
Trevinhoeh, so there's no much point in even trying to assing them in the meeting imho.14:25
seb128Trevinho, if you want to discuss a bug & it's solution I would expect you to raise an hand in the roundtable section at the start14:25
seb128and add it as a topic14:25
Trevinhoif we don't go into details it's generally not always 1/0 decision.14:25
Trevinhoyeah, that was the idea when asking how to solve things (both tecnically speaking or from managemen point of view), indeed there might be things where not all the team is interested, but there are topics where more than two people are and this might be the moment. At least to define when to talk about it.14:27
seb128we usually manage to decide on most bugs14:27
seb128well it's always fine to raise a topic14:28
seb128worth thing you get told that it's better to discuss after the meeting14:28
seb128and the people interested can stick for that14:28
Trevinhoanyway, just it's ok. let's now get into the deep of the remaining tasks.14:28
seb128right14:28
seb128so vbox/init/xserver14:29
seb128tjaalton, I'm unclear how much you investigated/figured out and how much is guessing that needs to be backed up by fact at this point?14:29
Laneywillcooke: how did you notice that you got network-manager crashing?14:30
willcookeI need to go to another meeting, I will follow along and post when I can14:30
seb128tjaalton, you said the vbox driver got dropped from the initramfs and it's creating the issue, was that guess or fact? (it didn't seem to be included in xenial?)14:30
LaneyI tried searching on errors but there's 0 crashes in 18.10 for n-m apparently14:30
Laneywhich is suspicious to me14:30
seb128Laney, willcooke, n-m didn't change recently14:30
Laneyso?14:30
willcookeLaney, it was in syslog, but it went away. I'll try and reproduce14:30
seb128Laney, don't trust errors :p14:30
seb128it could just fail to retrace by missing symbols or something14:30
Laneyright...14:31
tjaaltonseb128: I'd need to boot in windows to check vbox, my guess is that the building the initrd adds vboxvideo if the system is vbox. otherwise it'll just have all the normal drm drivers14:31
seb128Laney, well, I was typing, sorry I hit enter too fast ... n-m didn't change so it's not the obvious candidate for a regression (unless the issue is not new), having a bt would be useful if one of you still have the .crash14:31
LaneyIf the crash was in network-manager that's where it would be bucketed on errors - this is the question I was asking.14:32
LaneyI'm not really trying to investigate it (yet).14:32
seb128tjaalton, but the initrd is not built on the fly is it?14:32
tjaaltonsure is14:32
seb128ah14:32
seb128I don't know that part of the boot well14:33
tjaaltonnot on the fly14:33
LaneyIt's bug #1794966 though14:33
ubot5bug 1794966 in network-manager (Ubuntu) "Network manager crashes and restarts 2 seconds after establishing a VPN connection" [Undecided,New] https://launchpad.net/bugs/179496614:33
LaneyOr at least my one is14:33
tjaaltonbut for the installed system it'll build one14:33
seb128tjaalton, did you try to get foundations in the loop for that discussion?14:33
tjaaltonkernel doesn't ship one, it's built on the system14:33
tjaaltonseb128: no, spent more on the qemu thing and tried to get bochs enabled again. compared it with debian and they have it all working14:34
tjaaltonbut I guess the kernel is frozen now as of yesterday14:34
seb128Laney, from experience, e.u.c can missing a bucket can be due to failing retracings or apport failing to write/send the report (we had case when custom handlers would hijack apport, unsure if n-m does that)14:35
seb128tjaalton, jibel, willcooke, what's the reference bug for that vbox issue?14:36
LaneyOK thanks, I really just wanted to know if w_illcooke had tried to submit it to errors, but thanks for the extra information.14:36
seb128np14:36
tjaaltonhttps://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/179293214:36
ubot5Ubuntu bug 1792932 in xorg-server (Ubuntu Cosmic) "Cosmic Desktop fails to boot in vbox: Xorg assert failure: Xorg: ../../../../dix/privates.c:384: dixRegisterPrivateKey: Assertion `!global_keys[type].created' failed." [High,Triaged]14:36
didrocksLaney: https://launchpad.net/ubuntu/+source/nautilus/1:3.26.4-0ubuntu414:40
willcookeLaney, is this any use?  https://paste.ubuntu.com/p/6TGCkW48XX14:40
didrocksnautilus-folder-handler.desktop is still used, as least associated to default mime type for inode/directory14:40
didrocksxdg-mime query default inode/directory14:40
didrocksnautilus-folder-handler.desktop14:40
seb128willcooke, do you have a .crash in /var/crash?14:42
willcookeseb128, nope, sorry.  I've rebooted a lot since then14:42
willcookeI'll do a fresh install14:42
jbichawillcooke: sorry I didn't follow context or know the details but there was some kind of network fix in today's gnome-shell update14:43
oSoMoNI just filed bug #1795674, is that a known issue by any chance?14:43
ubot5bug 1795674 in gnome-shell (Ubuntu) "cosmic live session: no text/icon for network entry in shell menu" [Undecided,New] https://launchpad.net/bugs/179567414:43
jbicha^14:43
willcookeoSoMoN, could that be a theme issue?14:43
jbichamaybe try with tomorrow's iso?14:44
jibelit's there on hw14:45
didrocksLaney: I'm fine setting nautilus.desktop as the default if needed and it's a good fit14:46
Laneyjbicha: it's a crash in network-manager itself (so no)14:46
Laneydidrocks: ah, sorry, that should be org.gnome.Nautilus.desktop, I thought that was the case already14:46
jbichaok14:47
Laneywhere does it come from can you remember?14:47
seb128Laney, https://bazaar.launchpad.net/~ubuntu-desktop/desktop-file-utils/ubuntu/view/head:/debian/defaults.list#L19514:47
didrocksLaney: no worry, I'll do it :) it's in desktop-file-utils (/usr/share/applications/defaults.list)14:47
Laneythx14:47
LaneyI forgot the details of that thing14:47
didrockseasy to spot14:47
willcookeback from meeting14:47
LaneyI checked the default list in gnome-session14:47
didrockswas blaming the software with "open in folder" first :p14:47
Laneygnome-mimeapps.list14:47
seb128Laney, that's a Debian thing14:47
Laneyok14:48
didrocksbut their fault, no log it's failing ;)14:48
seb128well, we have a diff, ours is in desktop-file-utils14:48
seb128we should maybe look at getting ride of that delta14:48
didrocksyeah, gnome-mimeapps.list vs defaults.list vs gio mimetype…14:48
kenvandineTrevinho: so what was your theory14:48
didrocksETOOMANYPLACES14:48
seb128we put it there because it's a component easier to rebuild and less likely to break things on a rebuild14:48
Trevinhokenvandine: this works fine https://github.com/3v1n0/telegram-snap/blob/master/snapcraft.yaml#L15814:48
jdstrandwillcooke, seb128, et al: I'm working on https://bugs.launchpad.net/ubuntu/+source/evince/+bug/178892914:49
ubot5Ubuntu bug 1788929 in evince (Ubuntu Bionic) "Debian/Ubuntu AppArmor policy gaps in evince" [Undecided,Triaged]14:49
willcookejdstrand, thanks!14:49
seb128jdstrand, ah, good, thanks14:49
jdstrandI uploaded to cosmic already. wanted to see if people ran into anything first14:49
kenvandineTrevinho: so the slowness is updating the icon cache or mime database?14:50
jdstrandI also did submittodebian on it14:50
Trevinhokenvandine: yeah, takes the most of it14:52
kenvandineTrevinho: why is that different for 18.10 though?14:52
Trevinhoah, mh,.. I thought it was always like that even before.14:52
TrevinhoSo, I didn't profile cosmic differently though.14:53
TrevinhoSo i might be wrong. I just thought it was the same issue14:53
kenvandineno, this issue is the same snap is much slower to start fresh on 18.10 than 18.0414:53
jbichajdstrand: Debian GNOME accepts merge requests now. I don't know if that's easier or harder for you than submittodebian https://salsa.debian.org/gnome-team/evince14:53
didrocksah, "opening folder" works way better now :)14:56
Laney:314:56
jdstrandjbicha: in that moment submittodebian was, but noted14:57
Trevinhokenvandine: I see... Mh, we should profile the launching script then. For sure that operation was the one taking the most of the times14:58
Trevinhoalso parsing the fonts was, but might be different.14:58
kenvandinewe fixed the font issue14:58
Trevinhoseb128: as per those SRU what would you suggest?14:58
kenvandineat least for snaps built with the gnome backports PPA run on bionic hosts14:59
kenvandineTrevinho: that was the slowdown14:59
oSoMoNthe welcome page of the installer slideshow is a beaver, not a cuttlefish, are we waiting on design to provide the screenshot?14:59
kenvandinebut cosmic should have the same fontconfig cache version14:59
seb128Trevinho, I'm not sure to understand the issue. Waiting for an incoming upstream point release when there is one coming makes sense, if there is none coming or if it's taking to long it's fine to cherry pick or do a git snapshot tarball imho14:59
Trevinhoseb128: well, it was said to be soon, but still it's not coming. And so cherry-picking everything would make the verification harder I guess15:01
Trevinhosame for a git snapshot, no?15:01
Trevinhobut at least that fix for mutter imho is something we should land asap. We waited for a point release even too much imho.15:01
willcookeoSoMoN, @ installer slideshow - I did new graphics the other day.  jibel approved the merge. https://code.launchpad.net/~willcooke/ubiquity-slideshow-ubuntu/ubiquity-slideshow-ubuntu15:02
seb128Trevinho, I would do a snapshot of the stable branch and handle it as if it was a point update SRU15:03
oSoMoNwillcooke, cool, so it's just pending an upload?15:03
willcookeoSoMoN, yeah I think so.15:03
Trevinhoseb128: is that something we can do in the same way? In terms of SRU handling... I dindn't know...15:04
oSoMoNwillcooke, but we're way past UI freeze, does this require a UIFe ?15:05
willcookeoSoMoN, quite possibly.  I need to make one fix now, so I'll sort it15:05
seb128Trevinho, up to the SRU team to be fine or not but I think we can make our case for it15:05
oSoMoNwillcooke, ack, thanks15:06
TrevinhoI'll ping upstream again btw15:07
seb128andyrock, I sponsored g-c-c to Debian, did you plan to handle the Ubuntu rebase/update as well?15:07
andyrockseb128: yep :)15:08
seb128great, thx15:08
andyrockI looked at it because it contains the fix for a crash I sent upstream15:08
seb128and you are supposed to lunch :p15:08
seb128k15:08
seb128well let me know when the Ubuntu side is ready and I can sponsor that as well15:08
andyrockkk thanks :)15:08
seb128stepping back for a bit, bbl15:10
oSoMoNseb128, remembered that bug we looked into at the beginning of the week in Brussels, where the shell menu was only partially localized in French? I'm still seeing it but can't find the bug number, it was a language pack thing, right?15:11
oSoMoNah, too late… that can wait till you're back though15:11
willcookeLaney, fresh install, no segfaults15:31
willcookeLaney, red herring I think15:31
willcookere: n-m that is15:31
Laneyok, thanks, I'm still seeing it a bit though15:36
Laneysome kind of memory management problem15:36
willcookeLaney, anything I can do to confirm/test?  How can I reproduce?15:46
Trevinho17:08:10 <Trevinho> fmuellner: hey, any free slot for a point 3.28 release? :)15:46
Trevinho17:08:47 <fmuellner> Trevinho: yeah, but as it's the last one, I'd like to take a look on what might be a good idea to include still15:46
TrevinhoI guess we should go for git snapshots later... (seb128)15:46
Laneywillcooke: dunno yet, don't worry about it15:47
willcookeLaney, ack15:52
Trevinhoseb128: also for that gdm crash on kvm, what can I do? I mean, if you want me to poke around gdm to see if we can make it try harder, its something I can check, but if I should look at lower levels, I need to study things a bit. Not sure if someone else can be faster, then.15:53
Laneythink it happens more when I'm on the usb ethernet thing maybe15:54
LaneyTue 2018-10-02 16:53:43 BST   24566     0     0   6 error     /usr/sbin/NetworkManager15:54
Laneyjust hotplugged it and then NM crashed15:54
willcookeerk15:54
* willcooke takes his laptop for a walk. 16:05
willcookeI wonder if going out of range of the wifi is what crashed it16:05
willcookeLaney, ok, got some more crashes16:13
Laneynod16:16
Laneysome wonkiness here16:17
andyrockdidrocks: I'm preparing the update to gnome-control-center. Do we still need the "ubuntu-volume-amplification-to-gnome" migration thing?16:17
didrocksandyrock: I think not, but let me look16:18
andyrockwas the switch from com.ubuntu.sound to org.gnome.desktop.sound16:19
didrocksyeah, just checking that was done in bionic16:19
didrocksandyrock: 1:3.29.90-1~ubuntu1 in cosmic16:20
didrocksso we need it until next LTS16:20
didrocks(included)16:21
andyrocknot sure I'm following you but I trust you :D16:21
didrockswell, we need people to migrate their old settings to the new one16:21
didrocksand people on bionic have the old settings16:21
andyrockI guess to allow migration from lts to lts ?16:21
didrocksso whatever bionic -> <distro version> upgrade needs the migration scripts16:21
didrockswhich are:16:21
didrocks1. bionic -> cosmic16:22
didrocks2. bionic -> next LTS16:22
andyrockkk thanks :)16:22
didrocksyw! :)16:22
=== pstolowski is now known as pstolowski|afk
Laneythe patch could get a note, sounds like that's not obvious16:22
didrockswe should maybe add a "can be removed…"16:22
didrocksyeah, whatever Laney told16:22
LaneyHIGH FIVE16:22
* didrocks high five back16:22
andyrockI'll add it in the upload16:22
didrocksandyrock: you can say post f* (if f* is the next LTS)16:23
didrocksjust add that to the migration script, would be a lot of *f*un :p16:23
Laneywillcooke: want to see if 1.12.4 is better? https://people.canonical.com/~laney/package-junkyard/16:34
Laneyat least I didn't make it crash yet16:34
willcookeLaney, wack.  Installing16:34
Laneysuper sick safe solid sound16:35
Laneyeven if not this is a better basis for a bug report16:36
willcookeruh roh.  My gdm issue is back, even with proposed16:36
Laneyif you could, https://gitlab.gnome.org/GNOME/gdm/issues would be good w/the journal from a failed situation16:40
willcookeLaney, will do.  Just installing the n-m stuff16:40
Laneythx16:40
willcookeand then will do more on that one16:40
willcooke(it's possible that enabling debug is what fixed it :) )16:41
willcookek, nm installed16:41
* Laney does 20 minutes of queue reviews16:43
willcookeLaney, anecdotally, it seems to restore network connectivity from resume faster16:49
* willcooke takes his laptop for another walk16:49
willcookeit gets out more than I do16:49
willcookeLaney, well, same tests as earlier, suspend/resume when in range of different access points now doesnt segfault, and yeah, it does feel faster to reconnect on resume.16:55
willcookeship it16:55
willcookeI'll keep an eye on it16:55
willcookenow, gdm3....16:56
Laneykool16:56
willcookeohhhh, and now I think I see why I wasnt seeing more useful logging from gdm316:57
willcookeMore verbose logs16:57
willcookeI thought that was just a comment, but I think that's the actual config16:57
Laneyit's Enable=true or something16:58
Laneyclimbing -> pub quiz -> bed -> breakfast -> IRC17:01
LaneyLATERS!17:01
willcookel8r Laney17:03
willcookegdm3 upstream bug: https://gitlab.gnome.org/GNOME/gdm/issues/42817:18
gitbotGNOME issue 428 in gdm "Ubuntu 18.10 boots to black screen with flashing cursor, no gdm. Switching to tty2 and back to 1 fixes it." [Opened]17:19
willcooke<- dinner17:19
andyrockLaney: I just built gnome-control-center and I got the python-script-but-no-python-dep from the lintian, should I fix it using the way suggested here? https://lintian.debian.org/tags/python-script-but-no-python-dep.html17:37
andyrockit has been ignored for a while, that's why I'm asking17:37
andyrockas a side-note I noticied that 08_lowercase_user_names.patch ( Disallow upper-case letters in user names for compliance with adduser) has never been ported to debian, so I'm planning to do so, if that's ok17:40
Trevinhowillcooke: in that gdm issue, you get also a crash, or just doesn't show up?17:43
TrevinhoAlso maybe xorg logs might help or the ones in `/var/lib/gdm3/.local/share/xorg/`17:44
Trevinhowhile might be the same of /var/log, but... just to check..17:44
xnoxsomehow i have different gdm3 bugs too17:45
xnoxnot as severe, but somehow my tty1 is left in framebuffer mode and gdm3 cannot handle that17:45
xnoxwhatever that means17:45
tjaaltonso echoing here too, that the xserver crash is due to mesa enabling a feature on the software fallback driver, which makes glamor init pass now (didn't succeed in bionic), so adding a patch to the xserver should fix the vbox/qemu issues17:45
andyrock\o/17:46
tjaaltonhmm17:47
Trevinhotjaalton: lovely17:47
tjaaltonhmm hang on, need to verify it17:49
willcooketjaalton, \o/17:49
willcooke(well, potentially \o/)17:49
willcookeTrevinho, no crash that I can see, just doesnt seem to start17:50
Trevinhomh, I see... willcooke also jouralctl log might help so that we can also see gnome-shell logs in case17:50
willcookeTrevinho, in case it's useful I just added the log for when I switch to tty1 and things kick in to life: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/179563717:51
ubot5Ubuntu bug 1795637 in gdm3 (Ubuntu) "No login screen when booting Cosmic" [Undecided,New]17:51
willcookeI can attach that to the upstream bug if you think it's useful17:51
willcookeI'll get the other log now17:51
Trevinholet me see17:51
willcookedamn ittttttttttttttttttt17:52
Trevinhoeven 1st log was with debugging enabled, right?17:52
willcookenow it's bloody working again17:52
Trevinhohaha17:52
willcookeTrevinho, yeah,17:52
willcookeit was enabled17:52
Trevinhoraces are racy!17:52
willcooke:))17:52
jbichaandyrock: we don't need or want to use dh_python for gnome-control-center but you can add python3 to Depends17:52
andyrockjbicha: the problem is that the offending python script is a migrations cript17:53
andyrock*script17:53
andyrockhow to handle this case?17:53
jbichaandyrock: or just ignore the lintian error since we already indirectly depend on python3 (via system-config-printer at least)17:53
andyrockkk I'll ignore for the moment but would be nice to get rid of it17:54
jbichawe'll get rid of it in F ;)17:54
andyrock:(17:55
jbichaI said you can add the python3 depends if the lintian error bothers you17:58
willcookeTrevinho, do you think that gdm issue could be related to https://gitlab.freedesktop.org/xorg/xserver/commit/0a9415cf793babed1f28c61f8047d51de04f1528 (the one t_jaalton mentions might fix vbox)18:00
Trevinhomh, don't think so as in real hw you should be able to use proper driver, not llvmpipe (sw emulation)18:02
willcookeah of course18:04
willcookecalling it a night, see you tomorrow18:28
tjaaltonhmm I'll add that patch to xserver anyway, even though I couldn't find which commit in newer mesa made glamor init succeed18:33
seb128oSoMoN, that was bug #179347618:59
ubot5bug 1793476 in pkgbinarymangler (Ubuntu) "Missing French translations for some strings" [Undecided,Fix released] https://launchpad.net/bugs/179347618:59
seb128oSoMoN, unsure we got a langpack update since g-s was rebuilt with that version though19:00
seb128Trevinho, let's talk tomorrow about the kvm one, I'm not sure to understand the details19:00
jbichaoSoMoN: there were some issues with gnome-shell 3.30.0 translation handling, should be fixed whenever they do a 3.30.1. here are some links:19:13
jbichahttps://lists.ubuntu.com/archives/ubuntu-translators/2018-October/007517.html19:13
jbichahttps://gitlab.gnome.org/GNOME/gnome-shell/issues/53719:13
gitbotGNOME issue 537 in gnome-shell "Strings are no longer extracted by gettext" [1. Bug, 8. Translation, Closed]19:13
jbichahttps://gitlab.gnome.org/GNOME/gnome-shell/issues/61419:13
gitbotGNOME issue 614 in gnome-shell "Badly unused strings in pofiles" [Opened]19:13
oSoMoNseb128, jbicha: thanks for the links!20:12

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!