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