/srv/irclogs.ubuntu.com/2015/04/09/#ubuntu-desktop.txt

=== tmpRAOF is now known as RAOF
=== tmpRAOF is now known as RAOF
robert_ancellRAOF, do you know any history behind DRI3 and xserver-xorg-video-intel?03:45
RAOFrobert_ancell: You mean - why we've disabled it?03:48
robert_ancellRAOF, yeah. Well, not enabled it (it is disabled by default)03:48
RAOFrobert_ancell: I didn't follow closely, but it caused bugs.03:48
robert_ancellThat was my assumption - just not ready for prime time.03:48
robert_ancellRAOF, do you know which clients make use of it?03:48
RAOFMesa03:49
robert_ancellRAOF, do you know if anyone is shipping with it enabled yet?03:50
RAOFNope.03:50
RAOFMaarten would be your man there.03:50
robert_ancellRAOF, cool, thanks for the info03:51
robert_ancellRAOF, hmm, I enabled DRI3 and nothing blew up. Any way of confirming that it's actually being used and not DRI2?04:00
RAOFXorg.0.log should say something about DRI304:04
RAOFFor 100% confirmation I think you could try xtrace?04:04
robert_ancellRAOF, bingo. xtrace for the win04:07
robert_ancellRAOF, do you know if xtrace is alive upstream? It often doesn't know opcodes but the last time I looked at it I wasn't sure how to send a patch04:08
RAOFNo idea, sorry.04:08
didrocksgood morning05:47
=== thumper is now known as thumper-afk
pittiGood morning06:11
didrockshey pitti06:14
pittibonjour didrocks !06:17
larsubonjour!07:14
didrockspitti: still having some hope on the systemd fsckd thing? Seems like last email was pretty clear…07:17
pittididrocks: from Kay? yeah :/07:17
pittibonjour larsu!07:17
didrockspitti: I guess the best course of action is to rationalize our patch with the additional fixes (all that in one patch)07:17
pittididrocks: so it seems we'll have to move fsckd to the Debian branch then07:17
larsumorgen pitti! Wie geht's?07:17
didrocksand apply it against v21907:17
didrockspitti: I can do the first draft, then, you can review?07:18
pittididrocks: yeah; I hope that we don't have to patch s-fsck so much but that this can stay07:18
pittididrocks: sure!07:18
didrockspitti: let's see what the diff would be (it's mostly removals in s-fsck)07:18
pittididrocks: btw, I tried with the fsck mock on my laptop yesterday, and I didn't see any progress :/07:18
pittididrocks: it's not the "fixes from trunk" which I added yesterday, happens with either07:19
didrockspitti: at boot?07:19
pittiyes07:19
didrocksweird07:19
pitti(with real plymouth)07:19
pittiI only saw the "Ctrl-C" message07:19
didrockswas working 2 days again with a real fsck here07:19
didrocksago*07:19
didrockshum07:19
pittiah, good07:19
pittiwell, I don't know what I messed up, at some point I need to reinstall my laptop07:19
didrockspitti: anyway, with the rationalized patch, I'll give some try…07:20
pittididrocks: maintaining the translations will be the most ugly part, I figure07:20
didrocksyeah07:20
didrocksnot sure what we can do here…07:20
didrocks(already keeping that in a separate patch maybe?)07:20
pittididrocks: what did we do in the plymouth themes? were these translatable at all?07:23
pittididrocks: but yes, separate patch for those sounds better07:23
didrockspitti: our plymouth themes are .script files07:24
didrockspitti: no i18n support07:24
didrocksthat's why in addition to the machine parsable data, we send the l10n strings07:24
pittididrocks: right; I meant it wouldn't be too much of a regression if we would drop them in the future07:26
pittialthough it'd be a shame07:26
didrockspitti: yeah, that's a possibility, but still a regression from the user POV07:26
didrockspitti: should we revert to "c" btw?07:26
didrocksfor cancelling07:26
didrocksas we did in the past07:26
didrocksas upstream doesn't care anymore, this change is now useless07:26
seb128hey didrocks larsu pitti07:27
didrocks(shame for ctrl+c, took some time to figure out how the protocole handled it specially… as it was requested upstream)07:27
didrocksre seb12807:27
pittididrocks: I don't mind much TBH; if you want to switch back to C, please do07:31
didrockspitti: ok, I'll try to handle this07:32
didrockspitti: on the cancel only showing, it was with our ubuntu theme, right, not a debian one?07:32
didrocks(in that case, it's normal that you didn't get any progress)07:33
willcookeo/07:33
didrockshey willcooke07:33
pittididrocks: right, standard vivid desktop07:34
seb128hey willcooke07:36
seb128seb128q, hey07:43
willcooke???07:44
larsuseb128 greets his alter-ego07:45
didrockswillcooke: he's broken07:45
didrocksneed to reboot him07:46
larsumorning willcooke :)07:46
seb128lol07:46
TheMusoHey folks. :)07:46
larsudidrocks: can you reach the power button from where you are?07:46
larsuhi TheMuso!07:46
didrockslarsu: pushing it for 5s right now07:46
seb128larsu, trying to reproduce that "notify-osd notification doesn't go away" people reported07:46
seb128seems it's quassel irc users07:46
larsudidrocks: lol07:46
larsuseb128: oh?07:46
* larsu mumbles something about dreading to look at that code base again07:47
willcookehey TheMuso07:48
seb128larsu, you are safe07:52
seb128$ dbus-monitor interface=org.freedesktop.Notifications | grep quassel07:52
seb128   string "quassel"07:52
seb128         variant             string "quassel"07:52
seb128   string "quassel"07:52
seb128         variant             string "quassel"07:52
seb128   string "quassel"07:52
seb128         variant             string "quassel"07:52
seb128quassel sends notifications several time a second for ever07:52
larsuseb128: quassel quassels too much07:52
seb128seems so07:53
larsu(quassel is chatting in German)07:53
larsubut you knew that ;)07:53
seb128:-)07:53
seb128cyphermox, ^ just a fyi, your notify-osd issue from the other day, it's a quassel bug07:54
seb128cyphermox, https://bugs.launchpad.net/ubuntu/+source/quassel/+bug/144200508:02
ubot5Ubuntu bug 1442005 in quassel (Ubuntu) "Notifications are shown forever" [Undecided,New]08:02
willcookeg'night TheMuso08:04
TheMusowillcooke: Later. :)08:05
didrockspitti: keeping debian/patches/Add-gettext-support.patch separated for now, unsure if they are not going to keep it08:05
pittididrocks: yes, sounds good08:06
Laneyhey ho08:06
pittihey Laney, how are you?08:06
didrocksmorning Laney08:06
Laneyfeeling alright thanks pitti08:06
Laneyalthough!08:06
LaneyI went to donate blood last night and got denied because my iron was too low08:07
Laneyand the shocking thing is that the person suggested this may be because I drink too much tea08:07
Laneywhich apparently affects iron absorption08:07
Laneyhey didrocks08:08
Laneywhat's up?08:08
pittiLaney: oh, wow08:08
pittiLaney: weren't you in that program to test whether the interval between donations could be reduced?08:08
seb128didrocks, pitti, https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1441883 might be something for you?08:08
ubot5Ubuntu bug 1441883 in lightdm (Ubuntu) "15.04 Vivid Vervet won't boot after uninstalling lightdm" [Undecided,New]08:08
seb128Laney, hey08:09
pittiseb128: boot bugs? go away! :-)08:09
seb128lol08:09
pittij/k, /me looks08:09
seb128"Failed to isolate default target, freezing."08:09
seb128pitti, danke08:09
Laneypitti: indeed, so could also be related to going more frequently08:10
seb128Laney, time for coffee man:08:10
pittiah, probably some fallout from the /e/X/default-display-manger handling08:10
Laneybut they'll only have an idea of that when looking at the whole dataset I suppose08:10
pittiLaney: yeah, I had trouble keeping up my iron even with 3 month intervals08:10
seb128pitti, yeah, what I though08:10
* Laney is reading a study from the tea advisory council which is trying to rubbish this theory ;-)08:11
seb128lol08:13
didrockspitti: deleting lightdm should empty /e/X/d-d-m, right?08:13
pittididrocks: ideally yes; I'll try to reproduce this in a bit08:13
pittidisabling the login screen should be easier (like, just removing /e/X/ddm), but  I guess installing the package should still not render the system unbootable08:14
pittiI figure it's trying to start display-manager.service and fails08:14
didrockspitti: it's Wants=display-manager.service08:16
didrocksthough08:16
didrocksah08:17
didrockspitti: I think I get it08:17
didrocksit's the failsafe mode08:17
didrocksRequires=display-manager.service08:17
didrocksOnFailure=failsafe-graphical.target08:17
didrocks(for graphical target)08:17
didrocksI wonder how we can make this elegant08:17
didrocksas the main point is "you wanted to have a graphical system (graphical.target), no graphics -> failsafe"08:18
pittididrocks: hm, perhaps some Condition? could we make it ConditionFileNotEmpty=/e/X/d-d-dm or so?08:21
pittididrocks: oh, d-d-m still has lightdm even after purging08:21
didrockspitti: ok, so double issue :p08:23
didrockspitti: ConditionFileNotEmpty? you can't express that to tell "only fallback if file not empty"08:23
didrocksit will not executed graphical.target is /e/X/d-d-m empty08:24
didrockswhich is the default target, so I guess it will fail and trigger failsafe as well, no?08:24
pittididrocks: I mean, if removing all display managers woudl make d-d-m empty, we could check on that and not run the fallback at all08:26
pitti(I have some trouble understanding what you meant to say, sorry)08:26
pittididrocks: how is the fallback implemented right now, OOI? perhaps we did that wrong?08:27
didrockspitti: shouldn't then multi-users.target be the default, rather?08:27
didrockspitti: so, graphical.target Requires=display-manager.service/OnFailure=failsafe-graphical.target08:27
pittiit feels like display-manager.service should have something like OnFailure=ourfallback.service ?08:27
pittididrocks: well, maybe, but graphical.target only Wants=display-manager.service, so if that doesn't exist, it ought to be ok08:28
* pitti needs to read the error in more detail08:28
didrockspitti: not sure we can extends display-manager.service though, it needs a try08:28
pittididrocks: oh, requires; I thought it's wants08:28
didrocksas display-manager.service is in /etc08:28
didrocksand our extension for OnFailure would be in /lib08:28
didrockslet me give it a try08:29
pittididrocks: that should work08:29
pitti systemctl cat display-manager.service08:29
pitti# /lib/systemd/system/lightdm.service08:29
pittididrocks: ah right, cat resolves symlinks08:29
didrockspitti: let me give it a try08:29
didrockspitti: seems to work08:31
didrocksso, /lib/systemd/system/display-manager.service.d/xdiagnose.conf containing OnFailure=failsafe-graphical.target08:31
didrocksand this extends the Alias display-manager.service, in /etc08:31
didrockspitti: I'll handle the failsafe part of the bug, but /e/X/d-d-m needs to be empty still08:32
didrocksI guess08:32
pittididrocks: ok, I can handle that part08:32
* didrocks stops his systemd/fsckd rebasing08:32
pittididrocks: but if display-manager.service doesn't exist at all, why would d-d-m need to be empty? if we just make it OnFailure=, display-manager.service wouldn't start at all?08:33
pittididrocks: nah, don't interrupt stuff, it's not *that* urgent08:33
didrockspitti: well, I'm in that context08:33
didrockspitti: display-manager.service will exist, by the generator08:33
didrockshum, or maybe not08:34
didrocksone sec08:34
didrocksneeds to check, I guess I check for the unit08:34
pittididrocks: the boot fails because it doesn't exist :)08:34
pittididrocks: I added an xdiagnose task with a very short summary08:34
didrockspitti: yeah, but then, I shouldn't create the symlink08:34
didrocksthx!08:34
* pitti hugs didrocks, thanks for that (I'm not that familiar with xdiagnose)08:35
didrockspitti: ok, we don't create display-manager.service if /e/X/d-d-m does refer to garbage (an non existing unit)08:36
* didrocks hugs pitti back08:36
didrockspitti: so, would be better to clean it up, I guess, but not required08:36
didrockspitti: uploading the fix09:00
pitti\o/09:00
=== vrruiz_ is now known as rvr
seb128happyaron, hey, are you looking at https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1439202 ?09:35
ubot5Ubuntu bug 1439202 in ibus (Ubuntu) "/usr/lib/ibus/ibus-ui-gtk3:11:XKeysymToKeycode:keybinding_manager_bind:panel_keybinding_manager_bind:panel_bind_switch_shortcut:panel_construct" [High,Confirmed]09:35
seb128happyaron, it's in the top 5 vivid issues for the week09:35
seb128cyphermox, https://errors.ubuntu.com/problem/91da1afe1d626059f88ff4a6f225718a2e20ed3d ... seems like your fix didn't really fix it?09:36
happyaronseb128: I'm trying to sort out my ticket issue...10:28
happyarongetting some trouble10:28
happyaronthat's on the top on my list10:29
happyaron(means the bug)10:29
happyaronwill deal with it this night10:29
GunnarHjCan somebody please sponsor bug #1441629? (The queue is long, and it's soon final freeze.)10:31
ubot5bug 1441629 in fonts-android (Ubuntu) "Change prefix number of symlink 69-droid-sans-fallback.conf to 65" [High,In progress] https://launchpad.net/bugs/144162910:31
ricotzhey desktopers :)10:41
ricotzdidrocks, hi, would you mind proposing bamf in *debian* to be maintained by pkg-mate? By sending a proposal to "MATE Packaging Team <pkg-mate-team@lists.alioth.debian.org>"10:43
didrocksricotz: sure, can do10:43
didrocksany formal template or free-form is enough?10:44
ricotzdidrocks, thanks, no idea if there is a formal process to change owner-ship of an package10:44
Laneyjust get someone to upload it and change the maintainer10:45
didrockssounds easier this way then, ricotz, doing this? ^10:45
ricotzdidrocks, i guess just a few lines regarding the fact isn't updated and outdated10:45
Laneyit is orphaned, they can just do it10:45
Laneyhttps://bugs.debian.org/cgi-bin/bugreport.cgi?bug=77956510:45
ubot5Debian bug 779565 in wnpp "O: bamf -- Window matching library" [Normal,Open]10:45
didrocksyeah, I got it orphaned recently10:45
ricotzdidrocks, debian-mate wants some kind of on-the-record statement to not step on someones toes10:46
Laneyunnecessary10:46
Laneythey should just adopt the package10:46
didrocksemail sent, if that can make them happy :)10:47
ricotzLaney, didrocks, thanks!10:47
didrocksyw!10:47
Laneyhttps://www.debian.org/devel/wnpp/#l310:47
* didrocks is all about people feeling confortable10:47
Laneythey should know how the procedures work10:48
Laneyorphaned package -> someone take this10:48
Laneyinteresting that mate wants bamf ...10:49
didrockswell, wnck isn't enough for windows matching10:49
didrocksthey propbably wants better icons in the status bar :)10:49
didrocksand so matching desktop files10:49
Laneyyes i'm sure they want to do matching with it10:50
Laneystill interesting10:50
ricotzLaney, it is required by plank ;)10:50
Laneywhat is that?10:51
ricotza dock/launcher application10:51
Laneyi see10:52
=== thumper-afk is now known as thumper
=== MacSlow is now known as MacSlow|lunch
didrockspitti: I'm almost done, but I'll do multiple checks first. More complex due to recent trunk changes11:43
seb128happyaron, thanks11:44
=== alan_g is now known as alan_g|lunch
=== MacSlow|lunch is now known as MacSlow
Laneyheh12:16
Laneyre-debugging a FTBFS that I fixed in October12:16
Laneybring back daily landing!12:16
didrocksYEAH \o/12:21
* didrocks has some FTBFS issues as well, I wonder if it's not an autotool dep12:21
Laneywhat kind?12:21
Laneyi'm just browsing the archive rebuild + fixing stuff12:22
didrocksLaney: I think it's a -j4 issue (and so a dep), I'm rebuilding without it12:24
didrocksit's still this fsckd-out-of-trunk followup12:24
seb128Laney, what was defined that datadir in g-t and stopped doing so?12:24
seb128Laney, just to know if we can look for similar cases12:24
Laneydidn't find where it came from12:26
Laneyall the autotools stuff is the same version :(12:26
* Laney diffs the build deps12:33
=== pstolowski is now known as pstolowski|lunch
nessitahello everyone, quick question about LXC's in vivid: I just installed all updates, and the running LXC I had was killed by:12:42
nessitaThe system is going down for halt NOW!12:42
nessitaSIGPWR received12:42
nessitaI re-started it, and lxc-ls says is running, but it has no IP12:42
nessitasca-trusty                 RUNNING  -     -     -       NO12:43
nessitaso I can not ssh into it. Any ideas?12:43
Laneyseb128: aha, intltool12:45
Laneyi'll see if there are more of these12:47
seb128k12:48
Laneylooks like they didn't consider that intltool.m4 is an interface12:48
seb128Laney, should I try looking if there are some desktop build issues I can work on? or having several of us doing that is just going to lead to duplicating work?12:48
seb128Laney, they = dobey? ;-)12:49
Laney^o)12:49
Laneywas in 2013, probably can forgive him12:50
seb128hehe12:50
Laneyseb128: if you want to look at this stuff, there's a gcc5 test build too12:53
Laneyi'm looking at the normal toolchain one12:53
seb128Laney, ok, I can have a look to that12:54
dobeyhuh?12:57
seb128dobey, http://launchpadlibrarian.net/202626076/gnome-bluetooth_3.8.2.1-0ubuntu11_3.8.2.1-0ubuntu12.diff.gz13:01
dobeyhmm that's odd13:02
Laneyhttps://bazaar.launchpad.net/~intltool/intltool/trunk/revision/74213:03
=== alan_g|lunch is now known as alan_g
didrockspitti: hum, I can build successfully with -j1, but can't with -j4…13:07
dobeyLaney: ah, so the problem is that the gnome-bluetooth build is running autoreconf, but isn't re-running intltoolize i guess; so you end up with a configure script that contains the newer macro bits, but you have the old Makefile.in.in13:07
didrockslinking issue (probably an order thing)13:07
didrocksI wonder why, doesn't seem I changed Makefile.am at all13:08
didrockspitti: did you get this kind of issues with gpb (like timestamp?)13:09
* didrocks does a boot test13:13
Laneydobey: ya, I went for this one but intltoolize would also work13:14
* Laney goes to lunch13:14
pittididrocks: no, I always build with -j4, I never ran into issues13:22
pittididrocks: what's the particular output?13:22
didrockspitti: just that it doesn't find fsckd.o, will paste now that I rebase on experimental in some minutes13:24
didrockspitti: otherwise, all works well: cancellation (kept Control+C), translations, progress report…13:24
didrocks(with the binaries compiled with -j1)13:25
didrockspitti: http://paste.ubuntu.com/10782782/13:44
didrockspitti: works fine with a clean -j1 though :/13:44
didrocksas you can see, src/fsckd/fsckd.o builds successfully…13:45
didrockspitti: oh, I think I got it, fixing…13:47
=== pstolowski|lunch is now known as pstolowski
pittididrocks: hm, that indeed looks like a missing dep somehwere in the makefile?13:49
didrockspitti: yeah, found and fixed I guess13:50
didrocksrebuilding to ensure13:50
seb128larsu, back?14:12
seb128larsu, can you have a look to https://code.launchpad.net/~yuningdodo/unity-control-center/unity-control-center.lp1248720-block-power-callback-unless-its-triggered-by-user/+merge/255041 and comment on whether you think it's right (the associated bugs as some details about GNOME versions and how upstream is (not) impacted (anymore)14:13
ochosiLaney: btw, could you ping me if you decide on whether to ship the patch from this bug or not? https://bugzilla.gnome.org/show_bug.cgi?id=74622214:18
ubot5Gnome bug 746222 in .General "Improve CSD windows without a compositor" [Normal,Resolved: fixed]14:18
Laneyochosi: aye aye, I think larsu was going to check it out14:18
ochosiLaney: thing is, we should probably add an additional class/style to our themes for that, otherwise it won't look very good14:19
ochosiokeydokey14:19
Laneyfeel free to build a test package and do this in advance14:19
Laneyyou'll definitely need it at 3.16 time in any case14:19
seb128larsu, Laney, ochosi, Trevinho, btw, is bug #1441975 a gtk or a theme or a compiz issue?14:19
ubot5bug 1441975 in nautilus (Ubuntu) "have not shadows" [Undecided,Confirmed] https://launchpad.net/bugs/144197514:19
seb128context menus issue14:19
ochosimy money is on compiz14:20
seb128lol14:20
ochosii think without compositor, you can't get those shadows14:22
ochosibut theoretically it could also be a theme issue. i wonder though why it would be limited to nautilus then14:22
seb128it's not14:22
seb128it just got reported there14:22
ochosioh, so no shadows underneath any context menus in gtk3?14:22
seb128right14:22
seb128works with gtk2 apps though14:22
Trevinhoseb128: hmmhmh14:23
ochosithen if it's for all gtk3 apps it's likely the theme14:23
seb128larsu, ^14:23
ochosi(sorry for the flip-flop :))14:23
seb128hehe14:23
seb128no worry14:23
Trevinhoseb128: should be gtk theme issue, as gtk3 now does that client side14:23
ochosilemme test that in xubuntu real quick...14:24
seb128Trevinho, ochosi, thanks14:24
ochosiyes, definitely a theme issue14:24
Trevinhoseb128: so, the fact is that we should add client shadows only to menus it seems14:24
Trevinhoor... We make sure that compiz does that again14:24
ochosii have shadows there with greybird in gtk3, but not with ambiance14:24
Trevinhoochosi: yeah, that's doing it on client side14:24
ochosii think that is the way to go14:24
ochosiyou can really tweak those shadows nicely with css14:25
ochosiif i'm not mistaken, this should be it: https://github.com/shimmerproject/Greybird/commit/b9f9b0826195ad115b56724326aa0d3e91063dd414:27
ochosiyup14:28
ochosithat's it, just tested it successfully with ambiance14:29
ochosiseb128: ^14:29
ochosialso, CSD is quite unusable outside of Unity (or: without compiz) with Ambiance/Radiance14:29
ochosino shadows, no borders...14:29
ochosithat's a bit sad, other than that, Ambiance works great with Xfce14:30
seb128ochosi, thanks14:30
seb128ochosi, is that a theme issue as well?14:30
ochosibut i guess you guys stuck to compiz drawing all those shadows14:31
ochosiyeah14:31
ochosiit is14:31
seb128Laney, larsu, ^ can you add your list to look at getting something similar to that in our themes for vivid?14:31
Laneymakes sense14:31
ochosiAmbiance: http://i.imgur.com/BZqbCOr.png14:31
ochosiGreybird: http://i.imgur.com/51Sz1SF.png14:32
didrocksrebooting for finale testing14:32
ochosithe difference is a few lines in your gtk-widgets.css14:32
ochosi(plus disabling compiz' shadows for CSD apps i guess)14:33
Trevinhoochosi: we can't disable compiz shadows yet14:34
didrockspitti: ok, seems to work well (direclty copied the binaries from the experimental branch), the set of patch is at http://people.canonical.com/~didrocks/fsckd-out-trunk/14:34
Trevinhoochosi: but you can add a css rule only for menus14:34
didrockspitti: this includes the new workflow that I implemented a month ago (the patch which was never reviewed by upstream…)14:35
ochosiTrevinho: i see. well the commit in greybird i pointed you to does only that, so it's all you really need.14:35
didrockspitti: that + flattening all the patches while keeping gettext support and translations separated for easyness (and taking latest potential trunk changes, reverting some post-219 changes that they made with library moves)14:35
didrockspitti: so, all in all, should be good, I can rebase on the ubuntu branch, I will need anyway, as I think one or two autopkgtests are impacted by the direct fsck -> systemd-fsckd connection14:36
didrockspitti: but I would appreciate a first quick look by ourself so stamp that all looks good first!14:36
* didrocks now goes for a run14:36
didrocks(phew)14:36
seb128didrocks, enjoy!14:38
seb128I'm going to do the same in a bit14:38
* ochosi tries not to be a copycat while at the same time going for the run which he planned too...14:38
didrocksseb128: enjoy as well :)14:39
seb128ochosi, :-)14:39
seb128didrocks, thanks14:39
pittididrocks: rebasing> that's ok, I usually do it the other way around (rebasing ubuntu changes on top of experimental)14:40
pittididrocks: so landing this in exp only is fine14:40
Laneymardy: yo, any chance you could take a look at the libsignon-glib build (test) failure in vivid?14:40
didrockspitti: ok, so mind doing this, then I pull and fix eventual failing autopkgtests?14:40
didrockspitti: yeah, I know you rebase everytime the ubuntu branch, my git reset origin/ubuntu --hard I have to do with the git branch are there to proove it :p14:41
pittididrocks: 0001-Add-fsckd-patch-prepared-to-get-out-of-upstream-trun.patch  removes the old patches from the series, but not actually from debian/patches/ ?14:44
pittiah, that's in 000314:44
pittiI think the removal should be in 0001, and 0003 just the fuzz14:44
pittibut I can do that14:45
pittididrocks: ok; I still hope that at least some parts of s-fsck.c will stay, it's a rather intrusive diff that way14:48
pittididrocks: pushed (with 0003 merged into 0001), many thanks!14:49
Laneymardy: (filed bug, assigned you)14:51
larsuseb128: ya back for a while but was just having a tea with faina (lots to talk about)15:00
larsuseb128: the shadow thing is moot if we disable csd on unity, like Trevinho suggested15:00
seb128larsu, no hurry, enjoy your tea :-)15:00
larsudone now :)15:00
seb128larsu, saw the theme change ochosi suggested?15:01
seb128I've no real opinion on how to fix it, but seems like we should address it for vivid15:01
seb128it's quite visible (once you got told about it, show how much we look at UI details in our daily use here :p)15:01
larsuno shadows under context menus you mean?15:02
seb128yes15:02
larsuya indeed :)15:02
seb128well around menus rather15:02
larsuis there a patch?15:02
seb128byt yeah15:02
seb128larsu, https://github.com/shimmerproject/Greybird/commit/b9f9b0826195ad115b56724326aa0d3e91063dd415:02
seb128larsu, ochosi said it applies to our theme and should fix it15:02
LaneyI am copying ochosi's patch into a branch already15:02
larsuawesome, thanks Laney15:03
seb128Laney, thanks :-)15:03
larsuand thanks seb128 :)15:03
seb128yw!15:03
larsuhaving a look at the MR you linked as well15:03
seb128larsu, just in case you missed it, ... thanks ;-)15:03
larsualso I figured out the gedit squiggly line problem15:03
seb128no hurry, should be easy enough to review (I think)15:03
=== alan_g is now known as alan_g|afk
seb128just want another sanity check15:03
seb128oh, great!15:03
larsutrying to fix in gtk, but maybe we don't need that15:04
seb128if that's a theme one maybe sync with Laney to include the fixes in the same landing15:04
larsuchanging the color to a literal one is enough (i.e., don't use @color_name)15:04
larsuwill do15:04
seb128thanks15:04
larsuthere's still a problem with the underline not being drawn properly when it's on the last lin15:04
larsubut with the ubuntu font15:05
larsunot sure what's going on there and haven't been able to find the issue15:05
seb128is it not displayed at all?15:05
seb128or like cut?15:05
larsucut. Only one row or pixels15:06
larsuresizing the window or pressing enter to add a new line makes it work15:06
seb128hum, k, well at least it's better than not displayed at all :-)15:06
larsudefinitely15:06
seb128don't spend too much effort on it I would say15:06
larsuagreed15:06
ochosibtw, i would be surprised if my patch would have any regressions in unity, it should actually "just work"(TM)15:07
mardyLaney: I'll have a look at it tomorrow, thanks15:10
Laneythanks to you!15:10
larsuseb128: ugh, that patch is really ugly :/15:10
seb128larsu, the theme one from ochosi?15:10
larsuno, the bluetooth switch one15:11
seb128larsu, oh, the control center one15:11
seb128yeah, sorry15:11
seb128larsu, do you have a better idea/suggestion? ;-)15:11
larsuseb128: I remember fixing it in my bz5 branch15:12
larsunot sure though...15:12
larsubasically, gtkswitch has a way of handling stuff like this15:13
larsuit's a bit hard to use, but at least you don't need to block signals15:13
larsuthat said, I'm fine adding it downstream for V and fixing it with the bz5 update15:13
larsuit will work fine from the looks of it15:13
larsujust wouldn't want it in the actual code15:13
flexiondotorgochosi, larsu seb128 I'm very interested in this CSD conversation.15:15
flexiondotorgAre you planning to add the require patch to GTK3 in vivid?15:15
seb128larsu, basically you said "not nice but should do the job, we should get it in vivid"?15:16
larsuseb128: ya. sorry for rambling :)15:16
ochosiflexiondotorg: the patches are specific to the ubuntu themes, so unless you use Ambiance or Radiance, you'll likely not be affected/interested15:16
seb128larsu, no worry, thanks for the review ;-)15:16
* larsu will get seb128 to write executive summaries for him from now on :P15:16
flexiondotorgochosi, I have forks of Ambiance and Radiance call Ambiant-MATE and Radiant-MATE.15:17
larsuochosi: I think flexiondotorg means the patches for the non-composited case15:17
larsuoh, interesting15:17
ochosioh, those ones15:17
flexiondotorgochosi, So, I'll be keen add update them with the required fixes.15:17
ochosiwell those patches need theme changes too fwiw15:17
larsuseb128: I'll comment on the MR15:17
flexiondotorglarsu, Where is the MR?15:17
ochosibut i already prepared them locally for our themes15:17
flexiondotorgochosi, Is there a bug I can subscribe to for this?15:18
larsuflexiondotorg: unrelated.15:18
flexiondotorgk15:18
seb128larsu, thanks15:19
flexiondotorgochosi, Do you have a diff for the changes you made to Ambiance and Radiance?15:20
ochosiflexiondotorg: it really depends on what CSD related things you're referring to now. the most recent conversation was about gtk3 menus not having shadows, so i pointed to a commit that fixes that. i haven't submitted any changes for the other stuff (CSD without compositor)15:22
flexiondotorgochosi, OK, so the menus not having shadows is fixed with - https://github.com/shimmerproject/Greybird/commit/b9f9b0826195ad115b56724326aa0d3e91063dd415:22
* qengho is afk a bit.16:09
didrockspitti: hum, I wanted to avoid merging the 2 to have a clearer view for you about what changed16:11
didrockspitti: but as you wish :)16:12
didrockspitti: tell me once you rebased the ubuntu branch on top of it and I'll work on the autopkgtests16:12
pittididrocks: ah, you don't have a sid VM?16:16
didrockspitti: no off hand16:16
didrocksnot*16:16
pittididrocks: can do, but I don't plan an upload just for this as it's no effective change16:16
didrockspitti: well, it is16:16
pittioh?16:16
didrockspitti: as stated in the patch, now fsck talks directly to systemd-fsckd16:17
didrocksI've merged the changes that were planned with latest discussion in the ML16:17
pittiah16:17
didrocksso there is a workflow changes16:17
didrocks(I tried to be explicit about that in the commit message and in changelog, not enough apparently, sorry)16:17
didrocksso the sooner would be the better to avoid last minute accident if any16:18
didrocks(even if I tested heavily a month ago and today)16:18
pittididrocks: rebasing now16:20
TrevinhoMirv: hey, I've just fixed tests in https://code.launchpad.net/~3v1n0/libdbusmenu/custom-stock-item-label/+merge/251840 (vivid builds now, check http://s-jenkins.ubuntu-ci:8080/job/libdbusmenu-vivid-amd64-ci/2/), can you approve the MP?16:37
LaneyTrevinho: Funny, I already did that in silo 2716:38
Laneywant to merge with  lp:~laney/libdbusmenu/libtool-and-gi ?16:39
TrevinhoLaney: ah ok16:41
Laneythen we should be able to add that there16:41
TrevinhoLaney: mh, is ity really needed to call libtool there?16:41
Laneydon't know, but there is a way to keep on doing it16:41
Laneyso why not?16:41
TrevinhoLaney: mh, I've removed it and it's working well...16:41
TrevinhoI'd prefer to remove that, as I don't see the benefit of that16:42
TrevinhoLaney: anyway, I'm merging mine with yours, so we merge both?16:42
Laneyone way is fine, then set it as a pre requisite in the MP16:43
Trevinhoindeed16:43
* willcooke -> EOD16:44
willcookeo/16:44
* Trevinho Laney: for your love https://code.launchpad.net/~3v1n0/libdbusmenu/custom-stock-item-label/+merge/25570916:45
=== alan_g|afk is now known as alan_g
pittididrocks: rebased and pushed16:51
didrockspitti: excellent, thanks! will workon that tomorrow16:53
didrockswork on*16:53
pittididrocks: oui, c'est l'heure du dîner .. et de la glace !16:53
didrockspitti: un peu tard pour la glace :p16:53
didrocks(je sais, il n'est jamais trop tard pour une glace ;))16:54
pittididrocks: pourquoi ? il y a encore beaucoup du soleil dehors :)16:54
didrockspitti: julie est d'accord :-)16:54
* didrocks waves good evening and good glace to everyone!16:54
pittididrocks: c'est notre dessert !16:54
pittididrocks: and you, à demain !16:54
didrockspitti: à demain ;)16:55
LaneyTrevinho: can't approve, I'm going to land my thing and you can do it again once you get someone to do it16:56
=== alan_g is now known as alan_g|EOD
robert_ancellSweet5hark, how are you testing snaps?21:07
=== CrazyMelon is now known as CrazyLemon

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