[15:39] <ronj> Hi! Quick notice that amd64/i386 mainline kernel builds are broken, see for example https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.2.1/ . Thanks for the mainline builds, hope they're fixed soon :)
[15:57] <Eickmeyer> Any opinions on bug 1787857?
[16:00] <TJ-> Eickmeyer: is the rtl_pci module sharing the same interupt as the USB controller? if so, when "Disabling IRQ #18" hits you'd expect some issues :)
[16:02] <Eickmeyer> TJ-: I don't know, this isn't my bug, and I don't experience the problems being described. It showed up as a bug filed directly against Ubuntu Studio nearly a year ago, and even after I moved it to the right package, it's received no attention.
[16:04] <Eickmeyer> TJ-: That said, I have reason to believe it is definitely a hardware-specific issue.
[16:11] <TJ-> Eickmeyer: in the case of user lassi, IRQ 21 is shared between USb OHCI and the GPU (nvkm)
[16:23] <Eickmeyer> TJ-: So, this person has some hardware IRQ conflicts?
[16:25] <TJ-> Eickmeyer: not sure; it could be an edge-case bug in the preempt code. Looking at the info in the bug logs the only thing that occurs to me is the CPU affinity of the IRQ handler... in the lassi case (where there a lot of logs) if I recall correctly /proc/interrupts shows IRQ 21 handled on CPU 2 only. If somehow an IRQ 21 is dispatched to another core... "no one cares" "unhandled interrupt"
[16:27] <Eickmeyer> TJ-: Ok, not sure how to get this one out of my hair. Seems like it needs to be moved upstream to the Linux kernel if that's the case.
[16:58] <richi235> Hi, If I would now open a SRU for this commit: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=503d90b30602a3295978e46d844ccc8167400fe6 , what are the changes it would be included in the linux-generic-18.04-hwe kernel released with 18.04.3 on August, 1st ?
[17:13] <connor_k> richi235: the last day for commits for the august 12th release is July 17, so the patch would need to be sent by this wednesday with SRU justification for it to be included in that release (source: https://kernel.ubuntu.com/)
[17:19] <richi235> hmm, even that would not solve our problem because, if i get you correctly from august first to august 12th, all users using    linux-generic-18.04-hwe would nevertheless get 5.0.0-21.22~18.04.1
[17:19] <richi235> so 12 days with broken audio^^
[17:20] <richi235> I guess we will ship a dkms with the module than
[17:20] <richi235> but thanks for the info
[18:52] <jackpot51> Hello, has anyone else experienced suspend/resume regressions on NVIDIA RTX 2000 series laptops with the 5.0.0-21 kernel?
[18:52] <jackpot51> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1836630


[00:07] <rick_h_> time to hide
[00:07] <rick_h_> the wife is having a bachlorette party at the house so hiding in the office
[00:07] <rick_h_> phew, what an exhausting day, everyone else partying hard?
[00:10] <snap-l> rick_h_: Ugh, sorry to hear that.
[00:10] <rick_h_> all good, means I can hack on bookie without guilt
[00:30] <greg-g> I just woke up from 3 hour nap, and I'm still tired
[00:30] <snap-l> greg-g: Ugh, sorry to hear that.
[00:30] <rick_h_> heh, with you there
[00:30] <rick_h_> when the boy went for his nap I took one as well
[00:30] <rick_h_> he ran me ragged today
[00:32] <greg-g> nice
[00:33] <rick_h_> snap-l: got my mic pre-amp. Will have to test it out later on
[00:33] <rick_h_> crazy how much it can amp this mic
[00:33] <snap-l> How much distortion does it add?
[00:33] <rick_h_> a lot out of the box
[00:34] <rick_h_> had to tweak it down
[00:34] <rick_h_> but seems cool
[00:34] <snap-l> yeah, that's what I was afraid of. :)
[00:34] <snap-l> Very cool.
[00:35] <rick_h_> what sucks is that it sounds a bit different between a skype test call and the audacity recording
[00:35] <rick_h_> I guess I need to actually record the calls and see what makes it to disk
[00:35] <snap-l> Well, Skype has their own filtering
[00:35] <snap-l> also make sure it's using the mic input. ;)
[00:36] <rick_h_> yea, I turned off the "let skype do stuff" checkbox
[00:36] <rick_h_> yea, I definitely checked that
[00:37] <snap-l> I <3 eMusic's site
[00:37] <snap-l> Looking up "Everybody's Haydn" just to see if they have some reviews
[00:38] <snap-l> The conductor is Sir Charles Mackerras, who passed away recently (within a year)
[00:38] <snap-l> Upcoming Shows: This artist is not currently on tour
[00:38] <snap-l> Pretty sure neither the composer nor the conductor are touring. :(
[00:40] <rick_h_> heh, good call
[00:41] <jrwren> everybody's haydn eh?
[00:41] <snap-l> Don't be Haydn
[00:41] <snap-l> It's a dumb name for what essentially are Telarc reissues.
[00:42] <snap-l> but it was $10 with 40% off at Borders
[00:42]  * snap-l cleaned up pretty nicely.
[00:43] <snap-l> 6 discs, pllus a bunch of magazines
[00:44] <snap-l> Had $15 in Borders bucks, a handful of 40% discs, and a 20% off everything else.
[00:44] <snap-l> Saved 57.22
[00:44] <rick_h_> yay! tests finding bugs
[00:44] <jrwren> nice
[00:45] <rick_h_> easily amused tonight heh
[00:48] <snap-l> heh
[03:55] <snap-l> Wow, this is bullshit:
[03:55] <snap-l> http://www.naxos.com/catalogue/item.asp?item_code=9.80530
[03:55] <snap-l> Distribution Note(s):
[03:55] <snap-l> Not available in the United States due to possible copyright restrictions. Available for streaming and download only. Not available on CD
[03:59] <snap-l> The mind boggles how a Detriot Orchestra can record something that can't be released in the US.
[12:16] <brousch> snap-l: http://www.grmuseum.org/node/3872
[14:18] <snap-l> brousch: Nice!
[14:28] <brousch> hm, i just found a diaper stuffed into our wine rack
[14:28] <brousch> luckily it's not used
[14:31] <rick_h_> brousch: heh, know how that feels
[14:32] <brousch> pull-ups regularly become hats round here
[14:32] <rick_h_> I can't wait
[14:33] <snap-l> Heh
[14:36] <brousch> potty training sucks
[18:21] <TeamXlink> I also experience mouse glitches with hyperthreading on.
[18:54] <greg-g> TeamXlink: that seems, odd
[18:54] <greg-g> (mouse glitches with HT on)
[18:55] <TeamXlink> Yeah.
[18:55] <TeamXlink> I've lessend the problem by turning mouse filtering off, raw input on, and vsync on, but it still glitches.
[21:03] <snap-l> Are you using a USB mouse?
[23:45] <brousch> i love the open source culture
[23:45] <brousch> i took jcastro's unity keyboard shortcuts and made a handout/cheat sheet for a wmlug meeting. someone else took my cheat sheets and translated them into spanish


[22:04] <MarkDude> 	Google Glass has been hacked to run Ubunutu! At Google I/O, Google employees demonstrated how to root Google Glass and then run Ubuntu on it
[22:04] <MarkDude> http://twit.tv/show/tech-news-today/756
[22:04] <darthrobot`> Title: [Tech News Today 756 | TWiT.TV]
[22:04] <MarkDude> The episode is called Ubuntu on your face
[22:05] <pleia2> http://www.engadget.com/2013/05/16/google-glass-rooted-and-hacked-to-run-ubuntu-live-at-google-i-o/ is a more text-based version :)
[22:05] <darthrobot`> Title: [Google Glass rooted and hacked to run Ubuntu live at Google I/O]
[22:05] <MarkDude> Sure.
[22:05] <akk> Nice to hear!
[22:06]  * MarkDude shared it since EVERY time Ubuntu gets mentioned in non-FOSS circles- the better IMHO
[22:06] <MarkDude> Its not on FLOSS weekly
[22:06] <MarkDude> Its the general interest tech show
[22:06] <MarkDude> Yay!
[22:06] <MarkDude> Tom Merrit is a big Ubuntu supporter
 He is very open to Ubuntu folks reaching out to him <hint>
[22:07] <MarkDude> STRONG supporter of Linux.
[22:08] <MarkDude> If some Ubuntu folks go to TWIT studios he will treat you very nice- and allow a plug on the show
[22:08]  * MarkDude would be willing to invite him (and other TWIT folks) to an Ubuntu Hour
[22:09] <MarkDude> Prolly better tho - if someone else does it tho :)
[22:10] <MarkDude> Think about it Ubuntu Hours being mentioned to future FOSS geeks. Just an idea. I can send an email on this and see who is willing to do it :)
[22:10] <MarkDude> If no one, I can invite


[10:21] <riosd252> Hello everyone, I'm a new Ubuntu user. I'm learning as much as I can, but it's been only a couple of days. I'm having some issues with my wifi chipset, seems to be not compatible with Ubuntu 20.04
[10:22] <riosd252> Thing is, I read of some other computers which support natively the right drivers
[10:23] <riosd252> Mine is a dell inspiron 7386, but I know the same model, just 15 inches, has the same wifi card and it works seamlessly


[07:41] <xu-irc81w> Hello!
[11:09] <Nander> Hi, I have a fresh Xubuntu install, and it crashes randomly after somewhere between 15 and 30 minutes of working
[11:10] <Nander> Hardware: 11th gen i9, 96GB Ram, 4k laptop display, 2x 1440p display secondary (also happens on purely the 4k display, also if the display renders at 1080p)
[11:11] <Nander> Does anyone know what this can be / how to debug this?
[11:11] <Nander> The screen just does a little bit of a black flash, and then everything is frozen
[11:12] <Nander> no mouse movement, no ctrl-alt-fx to switch to a terminal, no nothing
[15:33] <Rocket_MapacheNo> hola, ¿alguien habla español?
[15:35] <Rocket_MapacheNo> adios
[15:44] <lemler> echo echo echoo!
[18:38] <osboxes> hellllo
[20:46] <mevla> Hello.  I've assigned the keys Alt1 to Alt-8 for desktop switching.  As I always do since 18.04.  In 22.04 it does not switch desktops but instead makes the windows minimize.  Is there a parameter for this bahaviour ?
[20:58] <mevla> The default values for switching desktops, eg. Ctrl-Alt-<number> do not work neither.  I have 8 desktops defined.


[13:59] <Martiini> Can I contact linux kernel developer and ask them to build kernel for my laptop?
[14:08] <TJ-> Martiini: please stop cross-posting the same question when you've already received answers in other channels


 (Photo, 1920x1080) https://irc.ubports.com/2jBAy0iw.png
 (Photo, 1920x1080) https://irc.ubports.com/p19Fn0Cz.png
 @Sconio [<reply to media>], looks to that rdnis is activated correctly
 <IP_ADDRESS> is your rdnis ip
 if you do ip addr show on your pc you should see an ip of 10.42.0.x
[01:43] <ubptgbot> johnnie fujita was added by: johnnie fujita
[01:47] <ubptgbot> <johnnie fujita> hi people i am a developer of solutions for democratic virtual identity. Which i believe can only  be achieved, if regular people can check if the algorithms and systems that they use to interact with the surrouding world are not tampered with some biased instruction on behalf of other parties that have exclusive access to the code
[01:47] <ubptgbot> .
[01:49] <ubptgbot> <johnnie fujita> i am new to ubuntu touch, but as i got deeper developing my platforms of end-to-end transactions and such, i always have to trust the underlying layers for some activities. At least, if i wish to keep the usecases to feel normal at some extent.
[01:51] <ubptgbot> <johnnie fujita> i will read more now in the website, but does the ubuntu touch is really connected to the kernel level instructions, or does it run as a subsystem over some other layer that is provided by google for example?
[01:52] <ubptgbot> <johnnie fujita> if anybody could give me this info straight ahead before i dive into the manuals, it would be neat!
[01:52] <ubptgbot> <johnnie fujita> thanks guys
[01:57] <ubptgbot> <johnnie fujita> already got to the good stuff guys, thanks. ubuntu touch is what i was looking indeed.
 Hello guys
 A manual to get Spotify up un running on Ubuntu touch devices
 https://forums.ubports.com/topic/2925/how-to-use-spotify-on-ubuntu-touch
 😜
 [Edit] A manual to get Spotify up and running on Ubuntu touch devices
 👍😀
[10:11] <ubptgbot> shafiqmustapa was added by: shafiqmustapa
 Loading module: 'libubuntu_application_api_touch_mirclient.so.3.0.0' … library "libubuntu_application_api.so" not found … dlsym failed: library handle is null … dlsym failed: library handle is null … Segmentation fault
 ?
[15:47] <ubptgbot> Alexandre Milani was added by: Alexandre Milani
 @hadrianweb [https://forums.ubports.com/topic/2925/how-to-use-spotify-on-ubuntu-touch], cool, i like the idea of running it local
 @hadrianweb [https://forums.ubports.com/topic/2925/how-to-use-spotify-on-ubuntu-touch], Nice one 👍
 Thanks for the messages
 Hi guys, in UT 16.04, is anyone able to run the desktop apps, I installed the latest available scope for the desktop apps, but non is appearing after installing in the container, any thoughts?
 @mofota [Hi guys, in UT 16.04, is anyone able to run the desktop apps, I installed the la …], Go to the app screen and then swipe up from the bottom, do you see them then? If you can press the star to then make the scope 'swipeable' from left on the apps screen,
[17:09] <ubptgbot> xixian was added by: xixian
 Apologies for the late reply, yes I did it already, feels as the scope is not reading the apps
 Is there a way to read the log related to the scope?
[17:46] <ubptgbot> Marius S was added by: Marius S
 The only other thing I can think off is to drag down form the top to see if that refreshes the app list. Failing that have you rebooted?
 @mofota [Apologies for the late reply, yes I did it already, feels as the scope is not re …], what are you trying to install?
 @mofota did you by any chance make the libertine container and/or scope in UT 15.04 and then upgrade to 16.04? That might cause the problem. Are there any apps you can’t afford losing? If this mismatch is the problem, then removing the scope, and removing the container and start fresh. Latest libertine on 16.04 does have a few problems
[18:26] <ubptgbot>  though
 [Edit] @mofota did you by any chance make the libertine container and/or scope in UT 15.04 and then upgrade to 16.04? That might cause the problem. Are there any apps you can’t afford losing? If this mismatch is the problem, then removing the scope, and removing the container and start fresh may help. Latest libertine on 16.04 does hav
[18:27] <ubptgbot> e a few problems though
 I installed Ubuntu touch 16.04 using the installer fresh, then I created a container using libertine-container-manager, tried also using Libertine in settings, then installed fresh libreoffice, gedit, I thought the apps will show in the scopes between the apps directly, as the Desktop Apps scope from the store is not compatible with 16.04,
[19:39] <ubptgbot>  I found a post with a link to the latest version <IP_ADDRESS>, after installing I swipe up in the scopes apps list and favorite the Desktop Apps to swipe from the right, trying to refresh the list, or adding any new apps in Libertine still doesn't show any apps
 @mofota [I installed Ubuntu touch 16.04 using the installer fresh, then I created a conta …], That is super weird
 (Photo, 960x1280) https://irc.ubports.com/0T6jdk4q.png This is what it shows when I try using the terminal, I'm not sure if there is any other command to use to launch the desktop apps
 file not found, indeed I'm using the wrong command :D
 @mofota [file not found, indeed I'm using the wrong command :D], hi and welcome. yes, you'll need to launch GUI apps in libertine from terminal using `ubuntu-app-launch` command. you can use `ubuntu-app-launch-appids` to see the apps you can launch
 @mofota [I installed Ubuntu touch 16.04 using the installer fresh, then I created a conta …], the legacy ([sic] desktop) apps scope does not need to be installed separately in 16.04. you just need to swipe up from bottom edge when looking at apps scope, and then select it from the list. you can tap the star next to it, to pin it to the lis
[20:39] <ubptgbot> t and swipe left/right at apps screen to switch between the two scopes
 (Document) https://irc.ubports.com/xhFzKh02.mp4
 what channel did you install? stable, rc, devel, or edge?
 From the stable channel
 hmm, what device is this on?
 It's the Nexus 5
 Feels maybe I missed up something when I reinstalled the Desktop Apps scope from a click file, also I enabled image write as I needed vim to be in terminal using apt
 ah; should work, but libertine is still quite experimental, and many apps don't work. and i think there have been more issues on nexus 5 (though i'm not sure why that would be)
 @mofota [Feels maybe I missed up something when I reinstalled the Desktop Apps scope from …], `vi` is already installed, but not full vim. if you really need full vim for some reason, it'd probably be better to install it in libertine too; you can then run it in terminal with `libertine-launch vim`
 @mofota [<reply to media>], Libreoffice is broken on libertine in the N5 now, you can use gnumeric and abiword as replacement in the meantime
[21:09] <ubptgbot> <F C> How many apps are there open store ?
 @malditobastardo [Libreoffice is broken on libertine in the N5 now, you can use gnumeric and abiwo …], OMG! It's a dream come true! gnumeric worked! abiword had the same behavior as libreoffice apps
 I will test out more and share my findings here, thanks guys for the help
 It's amazing to see it work even in basics, I'm excited for the future of Ubuntu Touch
 I think there's a thread on the forum about it. And perhaps some issues on GitHub
 @mofota [It's amazing to see it work even in basics, I'm excited for the future of Ubuntu …], thanks! these encouraging words go a long way for many people.  Don't forget we're always looking for people to help.  there are only a small number of really hard working devs here so if any of you are able to help, please do.  We aren't t
[22:05] <ubptgbot> hat far away from a victory.  :)
[22:15] <ubptgbot> <F C> Date of the next UT launch
[22:21] <ubptgbot> <F C> Android developers as we could contribute to Ubuntu touch


[03:45] <robert_ancell> RAOF, do you know any history behind DRI3 and xserver-xorg-video-intel?
[03:48] <RAOF> robert_ancell: You mean - why we've disabled it?
[03:48] <robert_ancell> RAOF, yeah. Well, not enabled it (it is disabled by default)
[03:48] <RAOF> robert_ancell: I didn't follow closely, but it caused bugs.
[03:48] <robert_ancell> That was my assumption - just not ready for prime time.
[03:48] <robert_ancell> RAOF, do you know which clients make use of it?
[03:49] <RAOF> Mesa
[03:50] <robert_ancell> RAOF, do you know if anyone is shipping with it enabled yet?
[03:50] <RAOF> Nope.
[03:50] <RAOF> Maarten would be your man there.
[03:51] <robert_ancell> RAOF, cool, thanks for the info
[04:00] <robert_ancell> RAOF, hmm, I enabled DRI3 and nothing blew up. Any way of confirming that it's actually being used and not DRI2?
[04:04] <RAOF> Xorg.0.log should say something about DRI3
[04:04] <RAOF> For 100% confirmation I think you could try xtrace?
[04:07] <robert_ancell> RAOF, bingo. xtrace for the win
[04:08] <robert_ancell> RAOF, 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 patch
[04:08] <RAOF> No idea, sorry.
[05:47] <didrocks> good morning
[06:11] <pitti> Good morning
[06:14] <didrocks> hey pitti
[06:17] <pitti> bonjour didrocks !
[07:14] <larsu> bonjour!
[07:17] <didrocks> pitti: still having some hope on the systemd fsckd thing? Seems like last email was pretty clear…
[07:17] <pitti> didrocks: from Kay? yeah :/
[07:17] <pitti> bonjour larsu!
[07:17] <didrocks> pitti: I guess the best course of action is to rationalize our patch with the additional fixes (all that in one patch)
[07:17] <pitti> didrocks: so it seems we'll have to move fsckd to the Debian branch then
[07:17] <larsu> morgen pitti! Wie geht's?
[07:17] <didrocks> and apply it against v219
[07:18] <didrocks> pitti: I can do the first draft, then, you can review?
[07:18] <pitti> didrocks: yeah; I hope that we don't have to patch s-fsck so much but that this can stay
[07:18] <pitti> didrocks: sure!
[07:18] <didrocks> pitti: let's see what the diff would be (it's mostly removals in s-fsck)
[07:18] <pitti> didrocks: btw, I tried with the fsck mock on my laptop yesterday, and I didn't see any progress :/
[07:19] <pitti> didrocks: it's not the "fixes from trunk" which I added yesterday, happens with either
[07:19] <didrocks> pitti: at boot?
[07:19] <pitti> yes
[07:19] <didrocks> weird
[07:19] <pitti> (with real plymouth)
[07:19] <pitti> I only saw the "Ctrl-C" message
[07:19] <didrocks> was working 2 days again with a real fsck here
[07:19] <didrocks> ago*
[07:19] <didrocks> hum
[07:19] <pitti> ah, good
[07:19] <pitti> well, I don't know what I messed up, at some point I need to reinstall my laptop
[07:20] <didrocks> pitti: anyway, with the rationalized patch, I'll give some try…
[07:20] <pitti> didrocks: maintaining the translations will be the most ugly part, I figure
[07:20] <didrocks> yeah
[07:20] <didrocks> not sure what we can do here…
[07:20] <didrocks> (already keeping that in a separate patch maybe?)
[07:23] <pitti> didrocks: what did we do in the plymouth themes? were these translatable at all?
[07:23] <pitti> didrocks: but yes, separate patch for those sounds better
[07:24] <didrocks> pitti: our plymouth themes are .script files
[07:24] <didrocks> pitti: no i18n support
[07:24] <didrocks> that's why in addition to the machine parsable data, we send the l10n strings
[07:26] <pitti> didrocks: right; I meant it wouldn't be too much of a regression if we would drop them in the future
[07:26] <pitti> although it'd be a shame
[07:26] <didrocks> pitti: yeah, that's a possibility, but still a regression from the user POV
[07:26] <didrocks> pitti: should we revert to "c" btw?
[07:26] <didrocks> for cancelling
[07:26] <didrocks> as we did in the past
[07:26] <didrocks> as upstream doesn't care anymore, this change is now useless
[07:27] <seb128> hey didrocks larsu pitti
[07: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] <didrocks> re seb128
[07:31] <pitti> didrocks: I don't mind much TBH; if you want to switch back to C, please do
[07:32] <didrocks> pitti: ok, I'll try to handle this
[07:32] <didrocks> pitti: on the cancel only showing, it was with our ubuntu theme, right, not a debian one?
[07:33] <didrocks> (in that case, it's normal that you didn't get any progress)
[07:33] <willcooke> o/
[07:33] <didrocks> hey willcooke
[07:34] <pitti> didrocks: right, standard vivid desktop
[07:36] <seb128> hey willcooke
[07:43] <seb128> seb128q, hey
[07:44] <willcooke> ???
[07:45] <larsu> seb128 greets his alter-ego
[07:45] <didrocks> willcooke: he's broken
[07:46] <didrocks> need to reboot him
[07:46] <larsu> morning willcooke :)
[07:46] <seb128> lol
[07:46] <TheMuso> Hey folks. :)
[07:46] <larsu> didrocks: can you reach the power button from where you are?
[07:46] <larsu> hi TheMuso!
[07:46] <didrocks> larsu: pushing it for 5s right now
[07:46] <seb128> larsu, trying to reproduce that "notify-osd notification doesn't go away" people reported
[07:46] <seb128> seems it's quassel irc users
[07:46] <larsu> didrocks: lol
[07:46] <larsu> seb128: oh?
[07:47]  * larsu mumbles something about dreading to look at that code base again
[07:48] <willcooke> hey TheMuso
[07:52] <seb128> larsu, you are safe
[07:52] <seb128> $ dbus-monitor interface=org.freedesktop.Notifications | grep 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] <seb128>    string "quassel"
[07:52] <seb128>          variant             string "quassel"
[07:52] <seb128> quassel sends notifications several time a second for ever
[07:52] <larsu> seb128: quassel quassels too much
[07:53] <seb128> seems so
[07:53] <larsu> (quassel is chatting in German)
[07:53] <larsu> but you knew that ;)
[07:53] <seb128> :-)
[07:54] <seb128> cyphermox, ^ just a fyi, your notify-osd issue from the other day, it's a quassel bug
[08:02] <seb128> cyphermox, https://bugs.launchpad.net/ubuntu/+source/quassel/+bug/1442005
[08:04] <willcooke> g'night TheMuso
[08:05] <TheMuso> willcooke: Later. :)
[08:05] <didrocks> pitti: keeping debian/patches/Add-gettext-support.patch separated for now, unsure if they are not going to keep it
[08:06] <pitti> didrocks: yes, sounds good
[08:06] <Laney> hey ho
[08:06] <pitti> hey Laney, how are you?
[08:06] <didrocks> morning Laney
[08:06] <Laney> feeling alright thanks pitti
[08:06] <Laney> although!
[08:07] <Laney> I went to donate blood last night and got denied because my iron was too low
[08:07] <Laney> and the shocking thing is that the person suggested this may be because I drink too much tea
[08:07] <Laney> which apparently affects iron absorption
[08:08] <Laney> hey didrocks
[08:08] <Laney> what's up?
[08:08] <pitti> Laney: oh, wow
[08:08] <pitti> Laney: weren't you in that program to test whether the interval between donations could be reduced?
[08:08] <seb128> didrocks, pitti, https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1441883 might be something for you?
[08:09] <seb128> Laney, hey
[08:09] <pitti> seb128: boot bugs? go away! :-)
[08:09] <seb128> lol
[08:09] <pitti> j/k, /me looks
[08:09] <seb128> "Failed to isolate default target, freezing."
[08:09] <seb128> pitti, danke
[08:10] <Laney> pitti: indeed, so could also be related to going more frequently
[08:10] <seb128> Laney, time for coffee man:
[08:10] <pitti> ah, probably some fallout from the /e/X/default-display-manger handling
[08:10] <Laney> but they'll only have an idea of that when looking at the whole dataset I suppose
[08:10] <pitti> Laney: yeah, I had trouble keeping up my iron even with 3 month intervals
[08:10] <seb128> pitti, yeah, what I though
[08:11]  * Laney is reading a study from the tea advisory council which is trying to rubbish this theory ;-)
[08:13] <seb128> lol
[08:13] <didrocks> pitti: deleting lightdm should empty /e/X/d-d-m, right?
[08:13] <pitti> didrocks: ideally yes; I'll try to reproduce this in a bit
[08:14] <pitti> disabling the login screen should be easier (like, just removing /e/X/ddm), but  I guess installing the package should still not render the system unbootable
[08:14] <pitti> I figure it's trying to start display-manager.service and fails
[08:16] <didrocks> pitti: it's Wants=display-manager.service
[08:16] <didrocks> though
[08:17] <didrocks> ah
[08:17] <didrocks> pitti: I think I get it
[08:17] <didrocks> it's the failsafe mode
[08:17] <didrocks> Requires=display-manager.service
[08:17] <didrocks> OnFailure=failsafe-graphical.target
[08:17] <didrocks> (for graphical target)
[08:17] <didrocks> I wonder how we can make this elegant
[08:18] <didrocks> as the main point is "you wanted to have a graphical system (graphical.target), no graphics -> failsafe"
[08:21] <pitti> didrocks: hm, perhaps some Condition? could we make it ConditionFileNotEmpty=/e/X/d-d-dm or so?
[08:21] <pitti> didrocks: oh, d-d-m still has lightdm even after purging
[08:23] <didrocks> pitti: ok, so double issue :p
[08:23] <didrocks> pitti: ConditionFileNotEmpty? you can't express that to tell "only fallback if file not empty"
[08:24] <didrocks> it will not executed graphical.target is /e/X/d-d-m empty
[08:24] <didrocks> which is the default target, so I guess it will fail and trigger failsafe as well, no?
[08:26] <pitti> didrocks: I mean, if removing all display managers woudl make d-d-m empty, we could check on that and not run the fallback at all
[08:26] <pitti> (I have some trouble understanding what you meant to say, sorry)
[08:27] <pitti> didrocks: how is the fallback implemented right now, OOI? perhaps we did that wrong?
[08:27] <didrocks> pitti: shouldn't then multi-users.target be the default, rather?
[08:27] <didrocks> pitti: so, graphical.target Requires=display-manager.service/OnFailure=failsafe-graphical.target
[08:27] <pitti> it feels like display-manager.service should have something like OnFailure=ourfallback.service ?
[08:28] <pitti> didrocks: well, maybe, but graphical.target only Wants=display-manager.service, so if that doesn't exist, it ought to be ok
[08:28]  * pitti needs to read the error in more detail
[08:28] <didrocks> pitti: not sure we can extends display-manager.service though, it needs a try
[08:28] <pitti> didrocks: oh, requires; I thought it's wants
[08:28] <didrocks> as display-manager.service is in /etc
[08:28] <didrocks> and our extension for OnFailure would be in /lib
[08:29] <didrocks> let me give it a try
[08:29] <pitti> didrocks: that should work
[08:29] <pitti>  systemctl cat display-manager.service
[08:29] <pitti> # /lib/systemd/system/lightdm.service
[08:29] <pitti> didrocks: ah right, cat resolves symlinks
[08:29] <didrocks> pitti: let me give it a try
[08:31] <didrocks> pitti: seems to work
[08:31] <didrocks> so, /lib/systemd/system/display-manager.service.d/xdiagnose.conf containing OnFailure=failsafe-graphical.target
[08:31] <didrocks> and this extends the Alias display-manager.service, in /etc
[08:32] <didrocks> pitti: I'll handle the failsafe part of the bug, but /e/X/d-d-m needs to be empty still
[08:32] <didrocks> I guess
[08:32] <pitti> didrocks: ok, I can handle that part
[08:32]  * didrocks stops his systemd/fsckd rebasing
[08:33] <pitti> didrocks: 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] <pitti> didrocks: nah, don't interrupt stuff, it's not *that* urgent
[08:33] <didrocks> pitti: well, I'm in that context
[08:33] <didrocks> pitti: display-manager.service will exist, by the generator
[08:34] <didrocks> hum, or maybe not
[08:34] <didrocks> one sec
[08:34] <didrocks> needs to check, I guess I check for the unit
[08:34] <pitti> didrocks: the boot fails because it doesn't exist :)
[08:34] <pitti> didrocks: I added an xdiagnose task with a very short summary
[08:34] <didrocks> pitti: yeah, but then, I shouldn't create the symlink
[08:34] <didrocks> thx!
[08:35]  * pitti hugs didrocks, thanks for that (I'm not that familiar with xdiagnose)
[08:36] <didrocks> pitti: 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 back
[08:36] <didrocks> pitti: so, would be better to clean it up, I guess, but not required
[09:00] <didrocks> pitti: uploading the fix
[09:00] <pitti> \o/
[09:35] <seb128> happyaron, hey, are you looking at https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1439202 ?
[09:35] <seb128> happyaron, it's in the top 5 vivid issues for the week
[09:36] <seb128> cyphermox, https://errors.ubuntu.com/problem/91da1afe1d626059f88ff4a6f225718a2e20ed3d ... seems like your fix didn't really fix it?
[10:28] <happyaron> seb128: I'm trying to sort out my ticket issue...
[10:28] <happyaron> getting some trouble
[10:29] <happyaron> that's on the top on my list
[10:29] <happyaron> (means the bug)
[10:29] <happyaron> will deal with it this night
[10:31] <GunnarHj> Can somebody please sponsor bug #1441629? (The queue is long, and it's soon final freeze.)
[10:41] <ricotz> hey desktopers :)
[10:43] <ricotz> didrocks, hi, would you mind proposing bamf in *debian* to be maintained by pkg-mate? By sending a proposal to "MATE Packaging Team<EMAIL_ADDRESS>[10:43] <didrocks> ricotz: sure, can do
[10:44] <didrocks> any formal template or free-form is enough?
[10:44] <ricotz> didrocks, thanks, no idea if there is a formal process to change owner-ship of an package
[10:45] <Laney> just get someone to upload it and change the maintainer
[10:45] <didrocks> sounds easier this way then, ricotz, doing this? ^
[10:45] <ricotz> didrocks, i guess just a few lines regarding the fact isn't updated and outdated
[10:45] <Laney> it is orphaned, they can just do it
[10:45] <Laney> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=779565
[10:45] <didrocks> yeah, I got it orphaned recently
[10:46] <ricotz> didrocks, debian-mate wants some kind of on-the-record statement to not step on someones toes
[10:46] <Laney> unnecessary
[10:46] <Laney> they should just adopt the package
[10:47] <didrocks> email sent, if that can make them happy :)
[10:47] <ricotz> Laney, didrocks, thanks!
[10:47] <didrocks> yw!
[10:47] <Laney> https://www.debian.org/devel/wnpp/#l3
[10:47]  * didrocks is all about people feeling confortable
[10:48] <Laney> they should know how the procedures work
[10:48] <Laney> orphaned package -> someone take this
[10:49] <Laney> interesting that mate wants bamf ...
[10:49] <didrocks> well, wnck isn't enough for windows matching
[10:49] <didrocks> they propbably wants better icons in the status bar :)
[10:49] <didrocks> and so matching desktop files
[10:50] <Laney> yes i'm sure they want to do matching with it
[10:50] <Laney> still interesting
[10:50] <ricotz> Laney, it is required by plank ;)
[10:51] <Laney> what is that?
[10:51] <ricotz> a dock/launcher application
[10:52] <Laney> i see
[11:43] <didrocks> pitti: I'm almost done, but I'll do multiple checks first. More complex due to recent trunk changes
[11:44] <seb128> happyaron, thanks
[12:16] <Laney> heh
[12:16] <Laney> re-debugging a FTBFS that I fixed in October
[12:16] <Laney> bring back daily landing!
[12:21] <didrocks> YEAH \o/
[12:21]  * didrocks has some FTBFS issues as well, I wonder if it's not an autotool dep
[12:21] <Laney> what kind?
[12:22] <Laney> i'm just browsing the archive rebuild + fixing stuff
[12:24] <didrocks> Laney: I think it's a -j4 issue (and so a dep), I'm rebuilding without it
[12:24] <didrocks> it's still this fsckd-out-of-trunk followup
[12:24] <seb128> Laney, what was defined that datadir in g-t and stopped doing so?
[12:24] <seb128> Laney, just to know if we can look for similar cases
[12:26] <Laney> didn't find where it came from
[12:26] <Laney> all the autotools stuff is the same version :(
[12:33]  * Laney diffs the build deps
[12:42] <nessita> hello everyone, quick question about LXC's in vivid: I just installed all updates, and the running LXC I had was killed by:
[12:42] <nessita> The system is going down for halt NOW!
[12:42] <nessita> SIGPWR received
[12:42] <nessita> I re-started it, and lxc-ls says is running, but it has no IP
[12:43] <nessita> sca-trusty                 RUNNING  -     -     -       NO
[12:43] <nessita> so I can not ssh into it. Any ideas?
[12:45] <Laney> seb128: aha, intltool
[12:47] <Laney> i'll see if there are more of these
[12:48] <seb128> k
[12:48] <Laney> looks like they didn't consider that intltool.m4 is an interface
[12:48] <seb128> Laney, 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:49] <seb128> Laney, they = dobey? ;-)
[12:49] <Laney> ^o)
[12:50] <Laney> was in 2013, probably can forgive him
[12:50] <seb128> hehe
[12:53] <Laney> seb128: if you want to look at this stuff, there's a gcc5 test build too
[12:53] <Laney> i'm looking at the normal toolchain one
[12:54] <seb128> Laney, ok, I can have a look to that
[12:57] <dobey> huh?
[13:01] <seb128> dobey, http://launchpadlibrarian.net/202626076/gnome-bluetooth_<IP_ADDRESS>-0ubuntu11_<IP_ADDRESS>-0ubuntu12.diff.gz
[13:02] <dobey> hmm that's odd
[13:03] <Laney> https://bazaar.launchpad.net/~intltool/intltool/trunk/revision/742
[13:07] <didrocks> pitti: hum, I can build successfully with -j1, but can't with -j4…
[13:07] <dobey> Laney: 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.in
[13:07] <didrocks> linking issue (probably an order thing)
[13:08] <didrocks> I wonder why, doesn't seem I changed Makefile.am at all
[13:09] <didrocks> pitti: did you get this kind of issues with gpb (like timestamp?)
[13:13]  * didrocks does a boot test
[13:14] <Laney> dobey: ya, I went for this one but intltoolize would also work
[13:14]  * Laney goes to lunch
[13:22] <pitti> didrocks: no, I always build with -j4, I never ran into issues
[13:22] <pitti> didrocks: what's the particular output?
[13:24] <didrocks> pitti: just that it doesn't find fsckd.o, will paste now that I rebase on experimental in some minutes
[13:24] <didrocks> pitti: otherwise, all works well: cancellation (kept Control+C), translations, progress report…
[13:25] <didrocks> (with the binaries compiled with -j1)
[13:44] <didrocks> pitti: http://paste.ubuntu.com/10782782/
[13:44] <didrocks> pitti: works fine with a clean -j1 though :/
[13:45] <didrocks> as you can see, src/fsckd/fsckd.o builds successfully…
[13:47] <didrocks> pitti: oh, I think I got it, fixing…
[13:49] <pitti> didrocks: hm, that indeed looks like a missing dep somehwere in the makefile?
[13:50] <didrocks> pitti: yeah, found and fixed I guess
[13:50] <didrocks> rebuilding to ensure
[14:12] <seb128> larsu, back?
[14:13] <seb128> larsu, 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:18] <ochosi> Laney: 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=746222
[14:18] <Laney> ochosi: aye aye, I think larsu was going to check it out
[14:19] <ochosi> Laney: thing is, we should probably add an additional class/style to our themes for that, otherwise it won't look very good
[14:19] <ochosi> okeydokey
[14:19] <Laney> feel free to build a test package and do this in advance
[14:19] <Laney> you'll definitely need it at 3.16 time in any case
[14:19] <seb128> larsu, Laney, ochosi, Trevinho, btw, is bug #1441975 a gtk or a theme or a compiz issue?
[14:19] <seb128> context menus issue
[14:20] <ochosi> my money is on compiz
[14:20] <seb128> lol
[14:22] <ochosi> i think without compositor, you can't get those shadows
[14:22] <ochosi> but theoretically it could also be a theme issue. i wonder though why it would be limited to nautilus then
[14:22] <seb128> it's not
[14:22] <seb128> it just got reported there
[14:22] <ochosi> oh, so no shadows underneath any context menus in gtk3?
[14:22] <seb128> right
[14:22] <seb128> works with gtk2 apps though
[14:23] <Trevinho> seb128: hmmhmh
[14:23] <ochosi> then if it's for all gtk3 apps it's likely the theme
[14:23] <seb128> larsu, ^
[14:23] <ochosi> (sorry for the flip-flop :))
[14:23] <seb128> hehe
[14:23] <seb128> no worry
[14:23] <Trevinho> seb128: should be gtk theme issue, as gtk3 now does that client side
[14:24] <ochosi> lemme test that in xubuntu real quick...
[14:24] <seb128> Trevinho, ochosi, thanks
[14:24] <ochosi> yes, definitely a theme issue
[14:24] <Trevinho> seb128: so, the fact is that we should add client shadows only to menus it seems
[14:24] <Trevinho> or... We make sure that compiz does that again
[14:24] <ochosi> i have shadows there with greybird in gtk3, but not with ambiance
[14:24] <Trevinho> ochosi: yeah, that's doing it on client side
[14:24] <ochosi> i think that is the way to go
[14:25] <ochosi> you can really tweak those shadows nicely with css
[14:27] <ochosi> if i'm not mistaken, this should be it: https://github.com/shimmerproject/Greybird/commit/b9f9b0826195ad115b56724326aa0d3e91063dd4
[14:28] <ochosi> yup
[14:29] <ochosi> that's it, just tested it successfully with ambiance
[14:29] <ochosi> seb128: ^
[14:29] <ochosi> also, CSD is quite unusable outside of Unity (or: without compiz) with Ambiance/Radiance
[14:29] <ochosi> no shadows, no borders...
[14:30] <ochosi> that's a bit sad, other than that, Ambiance works great with Xfce
[14:30] <seb128> ochosi, thanks
[14:30] <seb128> ochosi, is that a theme issue as well?
[14:31] <ochosi> but i guess you guys stuck to compiz drawing all those shadows
[14:31] <ochosi> yeah
[14:31] <ochosi> it is
[14:31] <seb128> Laney, larsu, ^ can you add your list to look at getting something similar to that in our themes for vivid?
[14:31] <Laney> makes sense
[14:31] <ochosi> Ambiance: http://i.imgur.com/BZqbCOr.png
[14:32] <ochosi> Greybird: http://i.imgur.com/51Sz1SF.png
[14:32] <didrocks> rebooting for finale testing
[14:32] <ochosi> the difference is a few lines in your gtk-widgets.css
[14:33] <ochosi> (plus disabling compiz' shadows for CSD apps i guess)
[14:34] <Trevinho> ochosi: we can't disable compiz shadows yet
[14:34] <didrocks> pitti: 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] <Trevinho> ochosi: but you can add a css rule only for menus
[14:35] <didrocks> pitti: this includes the new workflow that I implemented a month ago (the patch which was never reviewed by upstream…)
[14:35] <ochosi> Trevinho: i see. well the commit in greybird i pointed you to does only that, so it's all you really need.
[14:35] <didrocks> pitti: 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:36] <didrocks> pitti: 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 connection
[14:36] <didrocks> pitti: but I would appreciate a first quick look by ourself so stamp that all looks good first!
[14:36]  * didrocks now goes for a run
[14:36] <didrocks> (phew)
[14:38] <seb128> didrocks, enjoy!
[14:38] <seb128> I'm going to do the same in a bit
[14:38]  * ochosi tries not to be a copycat while at the same time going for the run which he planned too...
[14:39] <didrocks> seb128: enjoy as well :)
[14:39] <seb128> ochosi, :-)
[14:39] <seb128> didrocks, thanks
[14:40] <pitti> didrocks: rebasing> that's ok, I usually do it the other way around (rebasing ubuntu changes on top of experimental)
[14:40] <pitti> didrocks: so landing this in exp only is fine
[14:40] <Laney> mardy: yo, any chance you could take a look at the libsignon-glib build (test) failure in vivid?
[14:40] <didrocks> pitti: ok, so mind doing this, then I pull and fix eventual failing autopkgtests?
[14:41] <didrocks> pitti: 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 :p
[14:44] <pitti> didrocks: 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] <pitti> ah, that's in 0003
[14:44] <pitti> I think the removal should be in 0001, and 0003 just the fuzz
[14:45] <pitti> but I can do that
[14:48] <pitti> didrocks: ok; I still hope that at least some parts of s-fsck.c will stay, it's a rather intrusive diff that way
[14:49] <pitti> didrocks: pushed (with 0003 merged into 0001), many thanks!
[14:51] <Laney> mardy: (filed bug, assigned you)
[15:00] <larsu> seb128: ya back for a while but was just having a tea with faina (lots to talk about)
[15:00] <larsu> seb128: the shadow thing is moot if we disable csd on unity, like Trevinho suggested
[15:00] <seb128> larsu, no hurry, enjoy your tea :-)
[15:00] <larsu> done now :)
[15:01] <seb128> larsu, saw the theme change ochosi suggested?
[15:01] <seb128> I've no real opinion on how to fix it, but seems like we should address it for vivid
[15:01] <seb128> it's quite visible (once you got told about it, show how much we look at UI details in our daily use here :p)
[15:02] <larsu> no shadows under context menus you mean?
[15:02] <seb128> yes
[15:02] <larsu> ya indeed :)
[15:02] <seb128> well around menus rather
[15:02] <larsu> is there a patch?
[15:02] <seb128> byt yeah
[15:02] <seb128> larsu, https://github.com/shimmerproject/Greybird/commit/b9f9b0826195ad115b56724326aa0d3e91063dd4
[15:02] <seb128> larsu, ochosi said it applies to our theme and should fix it
[15:02] <Laney> I am copying ochosi's patch into a branch already
[15:03] <larsu> awesome, thanks Laney
[15:03] <seb128> Laney, thanks :-)
[15:03] <larsu> and thanks seb128 :)
[15:03] <seb128> yw!
[15:03] <larsu> having a look at the MR you linked as well
[15:03] <seb128> larsu, just in case you missed it, ... thanks ;-)
[15:03] <larsu> also I figured out the gedit squiggly line problem
[15:03] <seb128> no hurry, should be easy enough to review (I think)
[15:03] <seb128> just want another sanity check
[15:03] <seb128> oh, great!
[15:04] <larsu> trying to fix in gtk, but maybe we don't need that
[15:04] <seb128> if that's a theme one maybe sync with Laney to include the fixes in the same landing
[15:04] <larsu> changing the color to a literal one is enough (i.e., don't use @color_name)
[15:04] <larsu> will do
[15:04] <seb128> thanks
[15:04] <larsu> there's still a problem with the underline not being drawn properly when it's on the last lin
[15:05] <larsu> but with the ubuntu font
[15:05] <larsu> not sure what's going on there and haven't been able to find the issue
[15:05] <seb128> is it not displayed at all?
[15:05] <seb128> or like cut?
[15:06] <larsu> cut. Only one row or pixels
[15:06] <larsu> resizing the window or pressing enter to add a new line makes it work
[15:06] <seb128> hum, k, well at least it's better than not displayed at all :-)
[15:06] <larsu> definitely
[15:06] <seb128> don't spend too much effort on it I would say
[15:06] <larsu> agreed
[15:07] <ochosi> btw, i would be surprised if my patch would have any regressions in unity, it should actually "just work"(TM)
[15:10] <mardy> Laney: I'll have a look at it tomorrow, thanks
[15:10] <Laney> thanks to you!
[15:10] <larsu> seb128: ugh, that patch is really ugly :/
[15:10] <seb128> larsu, the theme one from ochosi?
[15:11] <larsu> no, the bluetooth switch one
[15:11] <seb128> larsu, oh, the control center one
[15:11] <seb128> yeah, sorry
[15:11] <seb128> larsu, do you have a better idea/suggestion? ;-)
[15:12] <larsu> seb128: I remember fixing it in my bz5 branch
[15:12] <larsu> not sure though...
[15:13] <larsu> basically, gtkswitch has a way of handling stuff like this
[15:13] <larsu> it's a bit hard to use, but at least you don't need to block signals
[15:13] <larsu> that said, I'm fine adding it downstream for V and fixing it with the bz5 update
[15:13] <larsu> it will work fine from the looks of it
[15:13] <larsu> just wouldn't want it in the actual code
[15:15] <flexiondotorg> ochosi, larsu seb128 I'm very interested in this CSD conversation.
[15:15] <flexiondotorg> Are you planning to add the require patch to GTK3 in vivid?
[15:16] <seb128> larsu, basically you said "not nice but should do the job, we should get it in vivid"?
[15:16] <larsu> seb128: ya. sorry for rambling :)
[15:16] <ochosi> flexiondotorg: the patches are specific to the ubuntu themes, so unless you use Ambiance or Radiance, you'll likely not be affected/interested
[15:16] <seb128> larsu, no worry, thanks for the review ;-)
[15:16]  * larsu will get seb128 to write executive summaries for him from now on :P
[15:17] <flexiondotorg> ochosi, I have forks of Ambiance and Radiance call Ambiant-MATE and Radiant-MATE.
[15:17] <larsu> ochosi: I think flexiondotorg means the patches for the non-composited case
[15:17] <larsu> oh, interesting
[15:17] <ochosi> oh, those ones
[15:17] <flexiondotorg> ochosi, So, I'll be keen add update them with the required fixes.
[15:17] <ochosi> well those patches need theme changes too fwiw
[15:17] <larsu> seb128: I'll comment on the MR
[15:17] <flexiondotorg> larsu, Where is the MR?
[15:17] <ochosi> but i already prepared them locally for our themes
[15:18] <flexiondotorg> ochosi, Is there a bug I can subscribe to for this?
[15:18] <larsu> flexiondotorg: unrelated.
[15:18] <flexiondotorg> k
[15:19] <seb128> larsu, thanks
[15:20] <flexiondotorg> ochosi, Do you have a diff for the changes you made to Ambiance and Radiance?
[15:22] <ochosi> flexiondotorg: 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] <flexiondotorg> ochosi, OK, so the menus not having shadows is fixed with - https://github.com/shimmerproject/Greybird/commit/b9f9b0826195ad115b56724326aa0d3e91063dd4
[16:09]  * qengho is afk a bit.
[16:11] <didrocks> pitti: hum, I wanted to avoid merging the 2 to have a clearer view for you about what changed
[16:12] <didrocks> pitti: but as you wish :)
[16:12] <didrocks> pitti: tell me once you rebased the ubuntu branch on top of it and I'll work on the autopkgtests
[16:16] <pitti> didrocks: ah, you don't have a sid VM?
[16:16] <didrocks> pitti: no off hand
[16:16] <didrocks> not*
[16:16] <pitti> didrocks: can do, but I don't plan an upload just for this as it's no effective change
[16:16] <didrocks> pitti: well, it is
[16:16] <pitti> oh?
[16:17] <didrocks> pitti: as stated in the patch, now fsck talks directly to systemd-fsckd
[16:17] <didrocks> I've merged the changes that were planned with latest discussion in the ML
[16:17] <pitti> ah
[16:17] <didrocks> so there is a workflow changes
[16:17] <didrocks> (I tried to be explicit about that in the commit message and in changelog, not enough apparently, sorry)
[16:18] <didrocks> so the sooner would be the better to avoid last minute accident if any
[16:18] <didrocks> (even if I tested heavily a month ago and today)
[16:20] <pitti> didrocks: rebasing now
[16:37] <Trevinho> Mirv: 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:38] <Laney> Trevinho: Funny, I already did that in silo 27
[16:39] <Laney> want to merge with  lp:~laney/libdbusmenu/libtool-and-gi ?
[16:41] <Trevinho> Laney: ah ok
[16:41] <Laney> then we should be able to add that there
[16:41] <Trevinho> Laney: mh, is ity really needed to call libtool there?
[16:41] <Laney> don't know, but there is a way to keep on doing it
[16:41] <Laney> so why not?
[16:41] <Trevinho> Laney: mh, I've removed it and it's working well...
[16:42] <Trevinho> I'd prefer to remove that, as I don't see the benefit of that
[16:42] <Trevinho> Laney: anyway, I'm merging mine with yours, so we merge both?
[16:43] <Laney> one way is fine, then set it as a pre requisite in the MP
[16:43] <Trevinho> indeed
[16:44]  * willcooke -> EOD
[16:44] <willcooke> o/
[16:45]  * Trevinho Laney: for your love https://code.launchpad.net/~3v1n0/libdbusmenu/custom-stock-item-label/+merge/255709
[16:51] <pitti> didrocks: rebased and pushed
[16:53] <didrocks> pitti: excellent, thanks! will workon that tomorrow
[16:53] <didrocks> work on*
[16:53] <pitti> didrocks: oui, c'est l'heure du dîner .. et de la glace !
[16:53] <didrocks> pitti: un peu tard pour la glace :p
[16:54] <didrocks> (je sais, il n'est jamais trop tard pour une glace ;))
[16:54] <pitti> didrocks: pourquoi ? il y a encore beaucoup du soleil dehors :)
[16:54] <didrocks> pitti: julie est d'accord :-)
[16:54]  * didrocks waves good evening and good glace to everyone!
[16:54] <pitti> didrocks: c'est notre dessert !
[16:54] <pitti> didrocks: and you, à demain !
[16:55] <didrocks> pitti: à demain ;)
[16:56] <Laney> Trevinho: can't approve, I'm going to land my thing and you can do it again once you get someone to do it
[21:07] <robert_ancell> Sweet5hark, how are you testing snaps?


[00:58] <jcastro> czajkowski, it's just charles
[00:58] <jcastro> czajkowski, don't worry, he's way cooler than me
[01:48] <mhall119> popey: you're already going to XDA:DevCon aren't you?
[06:58] <dholbach> good morning
[17:07] <pleia2> mhall119: please read my emails in the Users thread :) you did manage to answer my questions from 2 days ago, but asked the identical question about flavors that I answered in the thread 2 days ago
[17:10] <mhall119> pleia2: I remember you asking (which is why I answered) :) I don't recall getting an answer about the flavors sessions though
[17:10] <pleia2> So there should be two types of Flavors sessions, one about getting
[17:10] <pleia2> involved (Community track) and one about *using* them (our User
[17:10] <pleia2> Track), as User Days always has a Flavors segment.
[17:10] <pleia2> Can you clarify to make sure that's clear to the Community track leads too?
[17:10] <mhall119> the past 2 days have been busy for me with personal stuff
[17:10] <pleia2> ^^ I asked balloons to clarify, not sure if he did
[17:11] <mhall119> pleia2: sure, they're registered by belkinsa though, so I'm guessing they're community-focused
[17:11] <pleia2> and afaik, no one reached out for User sessions, but Lubuntu was kind of wishy washy about doing a session, Xubuntu can't (UOW lands at bad timezone for team members)
[17:12] <pleia2> so I don't think we'll have "how to use $x flavor" sessions
[17:12] <mhall119> pleia2: too early in the day or too late?
[17:13] <mhall119> ok, we need to find some others then, maybe "how to use $x application"?
[17:13] <pleia2> I've sent many emails, not having much luck
[17:13] <mhall119> yeah, that's true on several tracks
[17:13] <pleia2> people are busy, don't have time to prepare, but mostly just silence
[17:14] <pleia2> as for xubuntu, too "middle of the day" - everyone is at work :)
[17:14] <pleia2> we're having our team meeting at 2000 next tuesday
[17:14] <mhall119> pleia2: that's just after out last slot, can anybody make 1900 UTC?
[17:14] <pleia2> no
[17:15] <pleia2> and I have a work meeting at that time, so I can't do it either
[17:16] <pleia2> xubuntu doesn't really participate in vUDS due to timezones, so this is nothing new :)
[17:16] <pleia2> (and this one is too late for any cycle planning, all our blueprints are already in)
[17:17] <pleia2> so we just do IRC meetings, works fine for us
[18:05] <popey> pleia2: you looking for membership board people?
[18:05] <elfy> popey: yes we are
[18:05] <elfy> specifically people that can do the 12:00UTC board
[18:06] <popey> I can probably do that. Where do I apply?
[18:06] <elfy> membership board popey
[18:06] <elfy> ubuntu-membership-boards at lists.ubuntu.com
[18:06] <pleia2> published call here: http://fridge.ubuntu.com/2014/06/05/renewed-call-for-1200-utc-membership-board-nominees/
[18:06] <pleia2> thanks popey :)
[18:06] <popey> np
[18:07] <elfy> absolutely ty popey :)
[18:07] <elfy> last bit of the call is a bit depressing - hope we don't have to do that
[20:16] <mhall119> pleia2: balloons: Rick is going to do a Q&A on the User track, I just put it on the schedule
[20:17] <pleia2> mhall119: yay, thanks!
[20:20] <balloons> mhall119, the road to phone q & a, or generic?
[20:21] <mhall119> balloons: an "ask anything" kind of session
[20:21] <mhall119> balloons: I was asking pmcgowen about a road to phone session, but then my IRC server had to be rebooted so I lost the conversation
[20:22] <mhall119> but I think he agreed to do one
[20:22] <mhall119> that's how I choose to remember the conversation ending anyway :)
[20:23] <mhall119> pleia2: balloons: I scheduled rick's Q&A, can I leave the rest of the Users sessions to you guys (and valorie) to schedule?
[20:23]  * mhall119 doesn't like to step on track lead's toes when it comes to their schedule
[20:23] <balloons> mhall119, good answer
[20:49] <popey> mhall119: who was fixing the urls at http://summit.ubuntu.com/uos-1406/review/ ?
[20:49] <popey> e.g. http://summit.ubuntu.com/uos-1406/meeting/22259/lubuntu-panel/ is the ubuntu studio one
[20:49] <popey> http://summit.ubuntu.com/uos-1406/meeting/22260/lubuntu-panel/ is the ubuntu touch one
[20:51] <popey> are you able to edit them as I can't.
[21:32] <benonsoftware> Sorry I won't be able to do any User Days/UOS sessions, past couple weeks have been a nightmare + the tmezone doesn't help that much. :P


[05:49] <karora> morning :-)
[05:49] <ajmitch> almost :)
[08:12] <ojwb> hmm, mythtv seems to have deleted all its recording rules
[08:39] <hads> Not seen that before
[08:50] <ojwb> i guess i may have clicked the wrong button, but it seems surprising if there's a simple "delete all the rules" without confirmation
[08:51]  * ojwb decides to poke the logs
[10:24] <ojwb> oh hang on
[10:24] <ojwb> the rules are there, but aren't showing any upcoming recordings
[10:26] <ojwb> and restoring the previous database backup didn't help there
[10:42] <ojwb> hmm, i don't see the rules in mythfrontend, but I do in mythweb
[13:02] <ojwb> aha, new kernel version, so the hand built module for the DVB-T stick needs rebuilding
[13:05] <ojwb> yes, that seems to have fixed it
[18:49] <snail> morning
[18:52] <ibeardslee> morning
[19:18] <hads> Morning
[19:18] <Atamira> mornin
[19:25] <ajmitch> morning
[20:09] <mwhudson> good morning
[21:56] <ojwb> morning
[22:12] <hads> Morning
[22:14] <ojwb> hads: the mythtv issue turned out to be a newer kernel which meant the hand built module for the dvb-t stick wasn't working
[22:14] <ojwb> the db was actually fine
[22:37] <hads> Ah
[22:37] <hads> Annoying that