[04:19] <pitti> Good morning
[04:22] <darkxst> pitti, hey
[04:22] <pitti> hey darkxst
[04:22] <darkxst> pitti, do you know if there are really still cases where plymouth can get stuck with a 16color framebuffer?
[04:23] <pitti> darkxst: I don't know (I've never worked on plymouth/graphical boot), but it seems unlikely
[04:24] <pitti> with KMS it of course doesn't happen, with fbdev it shouldn't either, and the next fallback is plain text mode
[04:24] <darkxst> pitti, right, and pretty much everything on intel platforms is using KMS these days?
[04:25] <pitti> I don't know about the proprietary nvidia/amd drivers
[04:25] <pitti> nvidia had used plaintext boot for a long time, not sure if that's still the case
[04:25] <darkxst> nvidia have KMS, but its not the standard one, think they are porting over to that though
[04:26] <pitti> oh, they do? I thought KMS was GPL-only, so you can't legally have a KMS-capable proprietary driver
[04:26] <pitti> but maybe that changed now
[04:26] <darkxst> I think they blacklisted the graphical plymouth, because it causing problems with their framebuffer
[04:27] <darkxst> pitti, they are doing a big restructure of their kernel side to support wayland etc
[04:27] <pitti> or that; but then you also wouldn't run into a graphical 16 color fb
[04:27] <darkxst> yeh exactly that is just text
[04:27] <pitti> or are you talking about the classical text mode?
[04:27] <pitti> that happens all the time, and must be supported
[04:27] <darkxst> no the ubuntu theme, has fallback to 16color
[04:28] <darkxst> (graphical)
[04:28] <darkxst> but that is a pain for what we want to do since there is no alpha channel then
[04:29] <darkxst> and I guess worst case is they won't see the animation if it really happens, other things like passwords etc are all the same as per ubuntu theme
[04:40] <darkxst> pitti, btw I think nividia are going to register their own KMS service that than emulates the GPL-only API's from within their driver
[04:41] <pitti> heh -- kernel license wars :)
[04:44] <darkxst> indeed
[04:47] <darkxst> and nothing ever happens to the companies that just blatantly abuse GPL code
[04:48] <pitti> aside from being shown the finger, but they can surely live with that :)
[04:49] <darkxst> there are far worse companies out there than nvidia!
[05:36] <didrocks> good morning
[05:42] <pitti> bonjour didrocks, ça va ?
[05:49] <didrocks> ça va bien pitti, et toi ?
[07:52] <larsu> seb128, morning!
[07:52]  * larsu didn't see you come in
[07:52] <seb128> good morning desktopers!
[07:52] <seb128> hey larsu, how are you?
[07:52] <larsu> seb128, great thanks! convincing quilt to take changes to my patch
[07:52] <larsu> how are you?
[07:52] <didrocks> good morning seb128
[07:53] <seb128> quilt refresh!
[07:53] <larsu> ya...
[07:53] <seb128> I'm good thanks ;-)
[07:53] <seb128> hey didrocks
[07:53] <larsu> but quilt add, too
[07:53] <larsu> seb128, we miss you in that certain other channel
[07:57] <pitti> hey seb128!
[07:57] <pitti> hello larsu
[07:57] <seb128> hey pitti
[07:57] <larsu> "morning" pitti
[07:57] <seb128> larsu, oh, right, removed that from my list yesterday and I'm not really looking at IRC yet today ;-)
[07:57] <pitti> larsu: yeah, almost lunchtime :)
[07:58] <larsu> hehe
[07:58] <larsu> seb128, no worries :)
[07:58] <larsu> fyi: I'm off this afternoon
[07:58] <pitti> seb128: did you notice that the new bluetooth indicator regressed again? if you disable bluetooth it disappears entirely instead of graying out
[07:58] <pitti> didn't we fix this like three times already?
[07:58] <larsu> isn't that by design?
[07:59] <seb128> larsu, oh? have fun!
[07:59] <didrocks> pitti: you meant *run*time
[07:59] <larsu> seb128, helping a friend move to Hamburg :)
[07:59] <pitti> didrocks: cą aussi !
[08:00] <larsu> ah, pitti is right, it should be insensitive instead of disappearing: https://wiki.ubuntu.com/Bluetooth#PC
[08:01] <pitti> that's how it worked with bluez4
[08:01] <larsu> it should only disappear when the computer doesn't have bluetooth
[08:01] <pitti> I think with bluez5 it went away entirely, and the new version from yesterday didn't fix that yet
[08:01] <pitti> although it should really only look at rfkill, not at bluez
[08:01] <pitti> this bug keeps coming back :(
[08:01] <pitti> (we do have a mock for rfkill, just saying..)
[08:01] <seb128> larsu, hope it's not raining ;-)
[08:02] <larsu> thanks. looks fine so far
[08:02] <larsu> very sunny
[08:02] <larsu> pitti, maybe it can't differentiate between "bluetooth is off" and "no bluetooth hw available"
[08:02] <seb128> pitti, https://wiki.ubuntu.com/Bluetooth#Indicator_and_menu states
[08:02] <seb128> "When Bluetooth is off, to save space the Bluetooth indicator should not be present at all. "
[08:03] <seb128> talk to mpt about it I guess?
[08:03] <larsu> seb128, this is on the phone, though
[08:03] <seb128> larsu, convergence? ;-)
[08:03] <larsu> seb128, yes, I agree, but the spec says otherwise for the desktop
[08:03] <pitti> larsu: sure it can; check rfkill list, you'll have a soft blocked bluetooth device
[08:03] <pitti> that's how it was fixed previously
[08:03] <larsu> pitti, just thinking out loud :)
[08:03] <Laney> hai
[08:04] <larsu> L.a.n.e.y!
[08:04] <pitti> it's really wrong for a desktop to disappear -- you have no (obvious) way to reenable it
[08:04] <seb128> hey Laney
[08:04] <pitti> hey Laney, how are you?
[08:04] <larsu> pitti, same on the phone, no?
[08:04] <seb128> pitti, did that fix you mention ever landed?
[08:04] <seb128> I though we had issues when robert_ancell previously tried to do that
[08:04] <pitti> seb128: sure, it has worked fine since vivid
[08:04] <larsu> pitti, I tend to agree though - and we have more than enough space in the menu bar
[08:04] <Laney> GREAT!
[08:04] <pitti> bug 1126108
[08:04] <Laney> yeah this worked before
[08:05] <seb128> pitti, k, dunno then, patches are welcome ;-) that indicator is basically on low maintainance, I doubt anyone is actively looking at it
[08:05]  * larsu slowly walks away
[08:05] <didrocks> good morning Laney
[08:06] <larsu> Laney, how was climbing?
[08:06] <Laney> good try
[08:06] <Laney> but incorrect
[08:06] <Laney> tuesday -> pub quiz
[08:06] <larsu> hm?
[08:06] <larsu> ah. damn. sorry :)
[08:06] <larsu> how was the pub quiz?
[08:09] <willcooke> didrocks, am trying to move that meeting now
[08:11] <didrocks> willcooke: thanks!
[08:11] <larsu> morning willcooke
[08:11] <willcooke> hey larsu
[08:11] <larsu> how's the sprint?
[08:16] <Laney> larsu: we came (joint) second, but 4(!!!) points behind the winners
[08:16] <Laney> was fun
[08:16] <larsu> Laney, the correct German term for this is "ärgerlich"
[08:17] <larsu> (there's no good english translation)
[08:19] <Laney> I know es ärgert mich
[08:19] <larsu> yeah that works as well but sounds a bit stronger to me
[08:20] <Laney> well I don't know the difference
[08:20] <Laney> but I know what my one means :P
[08:20] <Laney> does it mean "I really hope they weren't using their mobile phones"? :)
[08:20] <larsu> hahaha
[08:21] <larsu> it's the adjective to "ärgern"
[08:21] <larsu> so in theory it's very similar
[08:21] <larsu> but it's used with weaker meaning
[08:42] <larsu> I love bug #401692
[08:42] <larsu> we've carried a patch since '09 for this...
[08:43] <seb128> :-)
[08:43] <seb128> we can drop the patch now?
[08:43] <larsu> no!
[08:43] <seb128> so "we carry ..."
[08:43] <larsu> the upstream bug even has comments from this year
[08:43] <larsu> seb128, true :)
[08:43]  * larsu makes them a proper patch and comments
[08:43] <seb128> well at least it's an easy to maintain change
[08:43] <larsu> it's also stupid
[08:43] <larsu> but yeah...
[08:44] <larsu> easily applied
[08:44] <seb128> right
[08:44] <seb128> still woth it imho, it's confusing that your saved documented are name unsaved document by default
[08:44] <larsu> yes of course!
[08:45] <larsu> unsaved is so stupid that I don't even begin to understand how they didn't change it upstream yet
[08:45]  * larsu goes all mpt on them and makes a list of apps and their default file names
[08:46] <seb128> lol
[08:46] <robert_ancell> larsu, Simple Scan is "Scanned Document"
[08:46] <larsu> robert_ancell, thanks!
[09:01] <didrocks> tjaalton: hey, is there any way to ensure that UXA is chosen as the AccelMethod before I report the new crash?
[09:01] <didrocks> (intel driver regular crash)
[09:06] <tjaalton> didrocks: check x log
[09:09] <didrocks> tjaalton: ok, seems I'm still using SNA then
[09:10]  * didrocks changes capital letter and wait for next crash to check logs
[09:11] <didrocks> hum, seems that even setting it in non capital letter doesn't work for some users: http://askubuntu.com/questions/638231/how-can-i-switch-graphic-card-acceleration-from-sna-to-uxa
[09:11] <didrocks> tjaalton: any idea what's wrong with the syntax? ^
[09:13] <tjaalton> is it all quoted?
[09:13] <tjaalton> the very beginning and end
[09:15] <didrocks> tjaalton: ah yeah, this user sounded to have it wrong
[09:15] <didrocks> anyway, let's see after my next crash, will keep you posted :)
[09:15] <didrocks> (seems like the bug started to be popular btw)
[09:15] <tjaalton> do you use chromium?
[09:15] <TheMuso> query willcooke
[09:16] <TheMuso> Wquery willcooke Whoops. :)
[09:16] <willcooke> TheMuso, :)
[09:16] <Laney> doh
[09:18] <didrocks> tjaalton: chrome, indeed
[09:18] <didrocks> that's how I saw that pattern
[09:20] <tjaalton> guess something changed in chromium then that triggers this
[09:20] <tjaalton> since the driver stack didn't
[09:21] <tjaalton> and vivid got the same update
[09:31]  * larsu yells at quilt
[09:31] <larsu> (and remembers `exit 0` from now on)
[09:34] <didrocks> larsu: classical :p
[09:34] <larsu> it could at least ask!
[09:34] <didrocks> quilt refresh first ;)
[09:34] <didrocks> (and it's bzr bd-do)
[09:34] <larsu> ya, indeed
[09:34] <didrocks> but if you don't run bzr bd-do first now
[09:34] <didrocks> you can still access it
[09:34] <didrocks> in ../build-area/package-name_version
[09:34] <larsu> I really yelled at that workflow. sorry quilt!
[09:35] <didrocks> then quilt refresh
[09:35] <didrocks> cp your patch
[09:35] <larsu> didrocks, ah, right
[09:36] <tjaalton> didrocks: I'll build -intel from current master with debug symbols on
[09:36] <tjaalton> it looks like https://bugs.freedesktop.org/show_bug.cgi?id=91658
[09:37] <didrocks> tjaalton: interesting, that can be, however, I definitively got many crashes when I wasn't watching a video
[09:51] <larsu> oh wow, we have ubunut.com!
[09:51] <larsu> just typoed that and wondered why it worked :)
[10:32] <pitti> didrocks: *maintenant* c'est l'heure de courier :)
[10:36] <didrocks> pitti: héhé, pareil ici (bientôt)
[10:39] <seb128> pitti, bon sport ;-)*
[10:39] <seb128> didrocks, toi aussi :-)
[10:39] <pitti> merci !
[10:40] <seb128> pitti, tu ne manges pas à midi ?
[10:40] <pitti> I think I tamed the ppc64el workers enough, /me releases the autopkgtest flood upon them and runs away to evade the splinters :)
[10:40] <pitti> seb128: pas encore, après le courier
[10:40] <seb128> k
[10:40] <seb128> enjoy!
[10:41] <larsu> Laney, (and maybe seb128), I've got a first gedit 3.16 branch up if you're interested: https://code.launchpad.net/~larsu/gedit/update-316
[10:42] <larsu> it's missing a few bits and it has a headerbar
[10:42] <seb128> larsu, good, I'm running the gnome3 ppa version since yesterday
[10:42] <seb128> let me try yours
[10:42] <larsu> most importantly the menubar patch
[10:42] <seb128> I was close from reverting to 3.8
[10:42] <seb128> I'm not getting used to the new ui when maximized :-(
[10:42] <larsu> menubar patch is definitely coming (but won't have time today, have to leave)
[10:43] <seb128> the titlebar showing under the panel and the double decorations are really annoying :-/
[10:43] <larsu> seb128, headerbar is not yet decided. I'll add a patch if we don't
[10:43] <larsu> seb128, yeah... I have the same issue. We could theme it differently when maximizefd
[10:43] <didrocks> seb128: merci ;)
[10:43] <Laney> we can't do this headerbar stuff for 15.10 surely
[10:43] <larsu> seb128, but I've got to run now. See you all tomorrow!
[10:44] <Laney> bye!
[10:44] <seb128> larsu, good luck with the moving ;-)
[10:44] <didrocks> see you larsu!
[10:44] <larsu> thanks :)
[10:44] <didrocks> don't break anything while moving and don't break anything on you as well :)
[10:45]  * larsu tries
[11:08] <popey> didrocks: http://blogs.unity3d.com/2015/08/26/unity-comes-to-linux-experimental-build-now-available/
[11:13] <didrocks> popey: waow, excellent!
[11:13]  * didrocks can't wait for this day to happen
[11:13] <didrocks> (when it's more marked as stable)
[11:13] <didrocks> I'll have a try though :)
[11:17] <seb128> tseliot, Laney, can you merge&clean silo9 (usd)?
[11:18] <seb128> it's in proposed but there is a checkbox to say to ignore that it didn't migrate
[11:18] <seb128> there are no silo available atm, that seems an obvious one we could claim back
[11:18] <Laney> Are you in there? do it
[11:18] <Laney> I didn't publish it
[11:19] <seb128> k
[11:19] <Laney> otherwise I've got to go get the yubikey :P
[11:19] <seb128> did it
[11:19] <seb128> thanks
[11:19] <Laney> ta
[11:21] <Laney> brb, dell man is here
[11:52] <Laney> i haz speakers
[12:13] <Laney> is g_bus_unown_name supposed to call the name_lost callback?
[13:40] <willcooke> Trevinho, hey!  Going through old bugs....
[13:40] <willcooke> uhhh ohhhhh
[13:40] <willcooke> :)
[13:40] <willcooke> https://bugs.launchpad.net/unity/+bug/798445
[13:41] <Trevinho> _o
[13:41] <willcooke> Just had a v. quick chat with JohnLea
[13:41] <Trevinho> :o
[13:41] <willcooke> Just to let you know, I've put it on the list for consideration
[13:41] <willcooke> if you have any good ideas, let me know
[13:41] <Trevinho> yeah, that's actually something I noticed as well
[13:42] <willcooke> JohnLea said pretty much the only option is to put it in to the right-click screen
[13:42] <willcooke> preview I guess it's called :)
[13:42] <Trevinho> mh, yeah I was thinking exactly the same
[13:42] <Trevinho> yes preview
[13:42] <Trevinho> but... Well, having a quick look is also soemthing that can help
[13:42] <willcooke> but anyway, just ponder it at your leisure, if you think of anything cool, let me know
[13:42] <Trevinho> maybe... Something on mouse hover such as showing a collapsed path
[13:43] <willcooke> we spoke about that, adding a whole new thing in hover seems like a bad idea, but I think it's a better solution than having to click
[13:43] <willcooke> so, dunnno
[13:43] <Trevinho> but indeed preview should state it
[13:43] <willcooke> oki, well - it's on the list :)
[13:44] <Trevinho> No I didn't want things such as pop-ups, but something like that the name changes once you're hovering for a certain amount of time
[13:44] <willcooke> ohh, nice
[13:44] <willcooke> hover over it and the full path could scroll by?
[13:44] <willcooke> in place of the name
[13:44] <Trevinho> something like that
[13:44] <willcooke> iiiinnnnnteresting
[13:47] <Trevinho> what was the tag name?
[13:47] <Trevinho> ah ok I see it
[13:48] <Trevinho> willcooke: also a way to go trough the approved backlog, just browse bugs in the ayatana-design side. Some were commited and still there :)
[13:49] <willcooke> thanks Trevinho
[13:49] <Trevinho> willcooke: I had collected these http://pastebin.ubuntu.com/12199413/
[13:50] <Trevinho> (and others, but need to do the tagging properly)
[13:51]  * willcooke reviews
[13:51] <willcooke> thanks
[14:23] <willcooke> anyone having issues with LP?  I keep getting timeouts trying to comment on bugs, and for once I don't think it's related to wifi
[14:23] <qengho> I got some new Http 500 page yesterday.
[14:24] <qengho> Mine was too quick to be a normal timeout, though.
[14:24] <qengho> Er, maybe it was a "down for upgrade" page, now that I think about it.
[14:25] <willcooke> meh, now it works
[14:25]  * willcooke blames wifi again
[14:27] <seb128> works for me
[14:53] <degorenko> hello here! Is here anyone around, who can help me? I want to fix this bug: https://bugs.launchpad.net/ubuntu/+source/sahara/+bug/1452698 I found this instruction: http://packaging.ubuntu.com/html/fixing-a-bug.html is it correct?
[14:55] <seb128> degorenko, hey, try #ubuntu for user issues
[14:55] <degorenko> seb128, ok, thanks
[15:06] <mitya57> Actually that doesn't sound like an user issue
[15:07] <mitya57> degorenko, ping coreycb or jamespage on #ubuntu-devel, they touched it last
[15:09] <degorenko> mitya57, ok, will do :)
[16:39] <willcooke> going to check in to the hotel
[16:46] <Trevinho> seb128: I've made this (so I can apply the same to dash as well): https://code.launchpad.net/~3v1n0/ubuntu-themes/osd-scrollbars-improvements/+merge/269245
[16:46] <Trevinho> do you prefer I wait larsu for checking that?
[16:46] <seb128> Trevinho, yes, I need to go now, we have a sprint dinner tonight and meeting is in 30 min
[16:47] <Trevinho> seb128: oh, right... I forgot you were in london :)
[16:47] <seb128> indeed
[16:47] <seb128> your video looks good :-)
[16:48] <Trevinho> seb128: I've also this https://transfer.sh/YLymC/out-19.ogv but it needs gtk patching (small theming thing)
[16:48] <Trevinho> and probably some transitions, which - for some reason -doesn't work
[16:49]  * Trevinho also wonders why all the theming stuff inside gtkscrolledwindow is hardcoded :o
[17:10] <Laney> bye!