/srv/irclogs.ubuntu.com/2018/11/22/#ubuntu-desktop.txt

=== Class7_ is now known as Class7
seb128good morning desktopers06:03
seb128cyphermox, thx for the wip casper vcs06:23
dufluUmm hi seb12806:31
seb128hey there duflu :)06:31
didrocksgood morning07:23
=== ecloud is now known as ecloud_wfh
dufluMorning didrocks07:29
didrockshey duflu07:36
oSoMoNgood morning desktoppers07:48
dufluHi oSoMoN07:53
oSoMoNhey duflu07:53
=== pstolowski|afk is now known as pstolowski
willcookeHappy Black Friday Eve, consumers08:55
* Laney buys something09:02
willcookemorning Laney09:03
Laneywhat is up willcooke09:03
willcookenot much.09:03
willcookeHad the heating on before getting out of bed this morning09:03
Laneythe humanity09:04
willcooke:)09:04
willcookeThe new carpet in my office is helping though, it's pretty warm in here now and I dont have to wrap a blanket around me09:05
Laneyhahah09:05
Laneyyou did that?09:05
willcookenah, a man09:05
willcookeI tried doing carpet once, it was a bit of a mess09:05
LaneyI mean the blanket thing09:05
Laneymy mum once did the carpet in my bedroom09:06
willcookeOh, ha09:06
Laneyit sucked09:06
Laneydon't think she used any carpet grips so it sort of shrank09:06
willcookeYeah, it was reallllly cold in here before09:06
dufluOh, morning willcooke and Laney09:07
willcookehi duflu09:07
seb128re09:11
seb128hey willcooke Laney didrocks oSoMoN09:11
seb128how is everyone today?09:11
oSoMoNhey seb12809:12
oSoMoNI'm good, how are you?09:13
didrockshey seb128!09:14
Laneyhey duflu seb128 oSoMoN didrocks!!!09:14
Laneyall people who I would pick for my football team09:14
* Laney wonders if that is a transferrable cultural reference or not09:14
willcookehi seb12809:15
seb128it makes sense translated in french I think09:15
seb128oSoMoN, ça va, a bit tired, I've been trying to get up at 6:45am to start early and shift some hours, it makes for more productive days but man, waking up early is not my thing :/09:16
oSoMoNheh09:19
oSoMoNI’ve been waking up at 6am for the past month or so, to get work done before the rest of the family wakes up, but it's hard, and the 1.5 hours it buys me go by way too fast, I'd have to wake up at 5am to feel like I'm getting stuff done09:21
oSoMoNdidrocks, I'd welcome your opinion on https://github.com/ubuntu/snapcraft-desktop-helpers/issues/167 , when you have a moment (not urgent)09:25
gitbotubuntu issue 167 in snapcraft-desktop-helpers "File open/save dialogs show $SNAP_USER_DATA instead of $HOME when selecting the home shortcut" [Open]09:25
seb128oSoMoN, need more hours in the day :)09:30
oSoMoNyeah, and a couple more at night wouldn't hurt either :)09:31
oSoMoNor maybe I just need to be more efficient09:32
seb128I don't think you are being un-efficient, it's just tricky to fit so much to do in a day09:34
seb128oSoMoN, I commented on the desktop helper issue, to me it sounds like it's not desktop specific but rather deciding what's the right userdir to point to by default and that also apply to command line utilities09:37
seb128I mean the right default when the real user dir is available through an interface09:38
didrocksoSoMoN: yeah, I was wondering about that one for a while, still in a HO with j_ibel working on the installer. Mind if I think about it for EOW?09:38
didrockswe need to think about potential impacts though, but I agree with seb12809:38
didrocksunsure about impacts in "HOME"/.* files09:39
seb128oSoMoN, it would be the same question to ask where a screenshot application should store the file by default for example09:39
oSoMoNyeah09:39
seb128yeah, also ~/.<nnn> are blocked by default I think09:39
seb128so changing the return of the glib function might lead to have apps trying to write configs to dir they can't access09:39
didrocksexactly09:40
didrockshence "we need to test/think about the impacts" ;)09:40
didrocksbut in the file opener, that would be great09:40
didrocksunsure how we can decorellate those09:40
seb128gtk patch :p09:41
oSoMoNsnaps connected to the home plug would expect files to be save to the real $HOME by default I guess, but we need to be wary of this interfering with writing/reading config files (many apps still check/fallback to $HOME/.config instead of using the XDG user dirs spec)09:41
didrocksdecorrelate*09:41
didrocksyeah… patch09:41
oSoMoNa gtk patch for just the file dialogs would be easy and self-contained, but how likely is it to be accepted upstream?09:42
seb128we can try suggesting one09:42
seb128I've a feeling it's going to be "thanks but no thanks" though :p09:42
didrocksyeah, they will say, it's a portal thing09:42
didrocksand everyone should use the standard API for getting through the portal09:43
didrocksso your java app or whatever… :/09:43
juliankTrevinho: I actually prepared a fix for the nautilus crash, but I get all sorts of hunk formatting changes due to using quilt vs whatever you used, so I'll leave it to you to remove the extra g_object_unref at the end of recent_thread_func11:25
juliankseems you forgot to remove the unref when converting the declaration of the variable to autoptr11:26
Laneyit's gbp-pq11:26
juliankLaney: i thought so11:29
* juliank should have looked at Vcs-git11:29
Laney:>11:30
juliankLet me upload that fix then11:30
Laneymight want to do a merge proposal to get it reviewed11:32
juliankdoing so11:35
Laney😘11:36
juliankLaney: did you type an emptyl ine, or do I have a unicode problem?11:37
LaneyI'd say the second one11:37
juliankugh11:37
Laneyit could be that *I* have one of those though11:38
juliankI'm running weechat from stretch-backports in a tmux, and both of that is in a proot on a centos6 system11:38
juliankI see it in the log file11:39
Laney🤷11:39
Laneyif you want to be fully millenial compliant then you should fix that :P11:41
juliankI'll try11:41
Laneythat setup sounds interesting though11:42
juliankhere's the merge: https://code.launchpad.net/~juliank/ubuntu/+source/nautilus/+git/nautilus/+merge/35918811:42
juliankLaney: it is11:42
juliankLaney: I'm considerign switching from shared hosting to a vps11:42
Laneythx, I'll request Marco on that11:43
juliankoh it's my tmux11:46
juliankhell, it's actually mosh11:47
=== cpaelzer__ is now known as cpaelzer
andyrockseb128: I was taking a look at https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/179662212:43
ubot5Ubuntu bug 1796622 in network-manager (Ubuntu) "NetworkManager IPv6 DAD lifetime behavior introduce security risk" [High,Confirmed]12:43
andyrockwouldn't be better to wait for upstream to release 1.12.6 ?12:44
andyrocknot sure what's their timeline12:44
seb128andyrock, that's not their current stable serie so unsure they plan to even do that12:46
seb128andyrock, there has been a CVE fix is there so maybe it would make sense to ask them if they plan to get a .6 out?12:48
andyrocklet me ask12:48
andyrockkk I asked on #nm if they're planning a new 1.12 release and what's the timeline (if any)12:51
andyrockseb128: "let's do 1.12.6 then either tomorrow or next week." that's what they told me13:02
seb128andyrock, \o/13:02
seb128andyrock, where did you ask? they have an irc channel?13:03
andyrockseb128: #nm13:03
seb128ah, you said that, #nm13:03
andyrockseb128: do you know if we're going to switch to nm 1.14 in disco?13:03
seb128yes13:03
seb128possibly directly 1.1513:03
andyrockhe just said that 1.16 is close13:04
andyrockwe might consider it13:04
seb128I was expecting them to follow GNOME's schedule and just start on 1.15?13:05
andyrockfor what I understand 1.15 is a dev release?13:06
andyrockseb128: so bionic is using nm 1.10.6 and there is already a nm 1.10.14 release with the fix13:10
andyrockwhat should we do?13:11
andyrockrelease the new version or keep the changes to the minimum (so releasing  1.10.6-2ubuntu2)13:11
seb128andyrock, we should update n-m to current 1.10 in bionic, unsure if we consider that ipv6 bug important enough to go by itself in a SRU round before though, I would like to get willcooke's/security team opinion about that13:24
seb128andyrock, I can handle the 1.10 update in bionic if we go for the full version update directly13:24
willcookeReading along in #nm sounds like that 1.10 update could be done pretty soon, right?13:25
andyrockit's already released so should be quick13:28
willcookeIf there won't be weeks of delay, then seems reasonable to go directly to the new nm instead of SRUing and then SRUing again13:31
seb128willcooke, you clearly having more confidence than me than doing a jump of 6 versions including new feature is going to go smoothly through without any regression/verification issue on the way :)13:37
Laneynot covered by the SRU exception though, so you get to do separate convincing of the team that it should go in13:39
willcookeWell, that's makes the decision a bit easier then :)13:42
seb128willcooke, you just changed your mind? ;)13:43
willcookeyeah13:43
seb128haha13:43
willcookeI'm sure that the ipv6 issue was important, so lets move forward with that at least13:43
seb128k, good13:44
willcookeI'm running o_SoMoN's  PPA, so far it's been ok, except for some wifi funnies yesterday.  I need to go mobile though and test on a few different wifi Aps13:44
willcookeAPs13:45
willcookeperhaps a trip to the office and back13:45
willcookeTrain wifi, coffee wifi, office wifi, and back again13:45
seb128:)13:45
willcookeI'll do that next week13:45
willcookeI nice little day out13:45
oSoMoNandyrock, seb128: 1.10.14 for bionic is in https://launchpad.net/~osomon/+archive/ubuntu/nm-lp1754671/+packages , if you feel adventurous and want to give it some testing13:48
willcookeplease do :)13:48
andyrockseb128: I created a gbp repo for network manager13:48
andyrockshould we use it?13:49
seb128andyrock, https://git.launchpad.net/network-manager/log/?h=bionic ?13:51
seb128or what do you mean "created"?13:51
seb128you mean you have a branch for the update?13:51
seb128oSoMoN, was that the one to test the other fix you handed to will yesterday?13:51
oSoMoNseb128, yes13:52
seb128k13:52
andyrockseb128: ah there is already one nice. I could not find it13:53
seb128my pesonal preference would go to do several rounds, starting by one including just important/safe changes that can be verified13:53
oSoMoNthat sounds reasonable13:53
seb128andyrock, tip on that, usually you can start by looking to Vcs- info in debian/control13:54
seb128(or use debcheckout which does that)13:54
oSoMoNthe fix for bug #1754671 requires pretty intrusive changes that cannot be easily cherry-picked on top of 1.10.6, though13:54
ubot5bug 1754671 in network-manager (Ubuntu Bionic) "Full-tunnel VPN DNS leakage regression" [High,Confirmed] https://launchpad.net/bugs/175467113:54
oSoMoNbut maybe bug #1796622 is easier in that regard?13:55
ubot5bug 1796622 in network-manager (Ubuntu) "NetworkManager IPv6 DAD lifetime behavior introduce security risk" [High,Confirmed] https://launchpad.net/bugs/179662213:55
andyrockoSoMoN: it's not super-clear which commits need to be cherry-picked13:58
seb128andyrock, oSoMoN, k, I try to have a look to what we can include in that first round of SRU, I probably do that next week14:00
seb128I let you know14:00
Laneyit's risky in a different way, that gives you combinations of changes that haven't been tested together - and if the cherry-picks aren't clean then you have the chance of introducing new bugs14:04
seb128right, it depends of what you include in the SRU14:06
seb128I was going to do a first one with some segfault & obvious fixes14:06
seb128landing more complex changeset is trickier indeed14:06
seb128also easy/selected fixes make it easy to go through SRU review & validations14:07
seb128when including new versions with a stack of changes without LP bugs is going to be more challenging14:07
seb128especially without ffe14:07
seb128standaing exception I mean14:07
Laneyk14:07
Laneysounds from what the people who looked at the bugs that are targetted were saying like they are not easy to take in isolation14:09
seb128yeah, that's probably true for the main ones we discussed in the rls- bugs reviews14:09
seb128looking at the NEWS from those updates there are also a bunch of other LP bugs fixes that are segfaults and such14:09
seb128no ideal situation, maybe trying to go for the full set directly is more efficient (though more likely to lead to nothing landing and the obvious bugs to not get fixed soon)14:10
Laneynot sure about the bracketed part, I would think that something could be worked out with the SRU team14:11
Laneyor on the other side confirmation that it would be a problem14:11
Laneyanyway, it's not me doing the work, so just my empty opinion14:12
seb128thx for the input14:15
seb128but yeah, I'm not too concerned about the SRU team14:15
seb128it's just a matter of doing enough paperwork to please them basically14:15
seb128it's just that we don't have high confidence atm that some of those complex changesets are going to be validated without regression14:16
seb128if it turns out they break some usecase/have some issues that's going to rightly block the SRU14:16
seb128we really need to find/hire a n-m maintainer :)14:17
Laneyk, I would argue that taking a random mix of commits is also quite risky too14:17
Laneygoing for lunch now, see you14:17
seb128true14:17
seb128enjoy!14:17
seb128tjaalton, unsure if you saw, but the xserver-xorg-video-intel sync from Debian is blocked in disco-proposed because it makes xserver-xorg-video-intel-hwe-18.04-dbg uninstallable ... unsure if that should be delete from disco, updated, ...?14:30
tjaaltonseb128: I'll check14:31
seb128thx14:31
tjaalton-dbg should probably be removed14:31
tjaaltonnew xorg-lts-transitionals uploaded, should fix this14:37
seb128tjaalton, thx!14:40
andyrockdidrocks: do you mind creating an ubuntu-dock-cosmic branch?14:54
andyrockI don't have write permissions14:54
didrocksandyrock: sure, one sec15:28
didrocksandyrock: based on which commit?15:28
didrockssorry, still in the HO, so not responsive :p15:28
andyrockhttps://github.com/micheleg/dash-to-dock/commit/73297451a0941a4c5bd98760bfd860ce7f284701 ?15:29
didrocksack15:29
didrocksoh15:29
didrocksI can't either btw15:29
didrocksyou need to ask Michele15:29
didrocksas he's the branch owner15:29
andyrockkk I'll send him an email15:29
seb128willcooke, did you have issues on bionic with your iphone, like it not being detected/properly handled if you disconnect it from the computer and plug it in again?15:56
seb128jbicha, congrats for making it to lwn :p15:56
seb128the man who screwed the debian non-main-arches :)15:57
willcookeseb128, nope, it just worked16:01
willcookeseb128, as far as browsing photos went16:01
seb128willcooke, :/16:01
willcookeI'll see if elmo is in the office next week when/if I go in, he's not replied to my mails16:01
seb128willcooke, well, the device should not be seen after being disconnected/reconnected, but that's for those which needs ubmuxd which might be only more recent models16:01
seb128willcooke, the issue I was talking about is another one I just did a SRU for (bug #1778767)16:02
ubot5bug 1778767 in usbmuxd (Debian) "iPhone doesn't charge when plugged in after disconnect" [Unknown,New] https://launchpad.net/bugs/177876716:02
seb128or maybe it's the same and I didn't understand the problem from elmo when you described it16:02
willcookeone sec, let me try it16:07
* willcooke goes to look for a cable16:07
willcookePlugged in phone, phone told me to unlock to use the accessory16:10
willcookeunlocked and phone is chargine16:10
willcookeg16:10
willcookeand I can see photos16:11
seb128I guess by "doesn't charge" it means "isn't being handled"16:11
seb128good16:11
seb128can you eject/disconnect and try to plug it again now?16:11
willcookeI need to reconnect it now to see if it will still charge16:11
willcookeah16:11
willcookeit made the charging noise, but it isnt actually charging16:12
willcooketrying the work around from: https://ubuntuforums.org/showthread.php?t=2376741&p=13722029#post1372202916:13
willcookeand yes, the work around makes it charge again16:13
willcookeso legit16:13
willcookeIt could be that's what elmo's problem was all along16:13
willcookeI will verify that fix once it's in proposed16:13
seb128great, thx for testing16:17
seb128will ping you again once the SRU is approved :)16:17
willcookeglad to be of service16:17
jbichaseb128: I sign autographs for a nominal charge ;)16:23
seb128hehe16:24
=== caravena_ is now known as caravena
willcookenight all18:23
=== pstolowski is now known as pstolowski|afk

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