=== [1]amigamagic is now known as amigamagic [08:15] * ochosi notest that even weeks after the release, there has been no single complaint about the removal of ibus... [08:18] * elfy compares that to the likely result of leaving it in - so that's a win :p [08:19] Seems like it messes with chromium, from what I ehar. [08:19] then people can reinstall ibus if they need it - but chromium isn't anything I would worry about [08:20] No, I mean that ibus messes with chromium if you have both, and ditto on the second bit. :P [08:20] looking at errors.ubuntu.com, chromium is a bit messed up currently [08:30] knome: how long until we can publish the article on locking? (just asking cause right now there's someone again in #x asking for answers that are given in it) [08:43] hi folks [08:46] hey jhenke [08:46] btw, didn't you want some stuff to work on? :) [08:49] there are still some 14.04 issues that need addressing [09:10] sadly I already have too much other stuff to do right now, thats also why I have been here not so regulary the last week [09:15] I try to be of some help later when I have some more room again [09:23] ochosi, hrhr [09:23] ochosi, don't expect anything from me now, i'm not xpl :P [09:24] ochosi, i'll have to talk with pleia2, then do the changes (won't take much time as soon as i get to it) and then get them ready for the IS. [09:25] ochosi, re: question on #xubuntu right now, can light-locker get "just" the wallpaper color if there is no wallpaper? [09:27] ochosi, also, ping me when you get vback [09:27] -v [09:27] i'm around for probably an hour or so, then back late today [09:51] ok, i'm off [09:51] ochosi, ping me later anyway :) [09:55] knome: ping [09:55] jhenke: okeydokey, feel free to get in touch anytime [10:03] knome: just read up on the question on #x, that's lightdm-gtk-greeter, not the locker. and it just takes what accountsservice gives you, which is always a wallpaper and never a color. [10:03] and the fallback is the system default, which is the xubuntu wallpaper [10:04] unless you change it in the config file to a color [10:10] ali1234: quick question, you mentioned a fix/workaround for xfsettingd always miscalculating the monitor count by 1 (seems to be happening with nvidia propr drivers at least), do you still have that anywhere? [10:24] ibus is being installed in default xubuntu again [10:24] ibus is also being forced into an existing utopic install after an update/grade [10:26] http://cdimage.ubuntu.com/xubuntu/daily-live/20140511/utopic-desktop-i386.manifest [10:33] aha, dependency chain or what being the reason for that? [10:34] no idea - I've just stopped spitting feathers :( [10:34] no real idea even how to know tbh [10:35] I don't see why dependency though - I purged it and it just removed itself [10:40] yeah, but it can still be recommended by something we install [10:40] and hence get pulled but be removeable [10:40] Unit193: care to take a look why that ^ happens? [10:40] I thought we dealt with that [10:42] it can always happen that recommends of packages change and then pull in unexpected stuff [10:43] yea [10:43] probably what happened the first time around [10:43] http://pastebin.com/rLzAr2ZV [10:43] yup, can't hurt to investigate soon enough [10:44] that's the log with the offending (and it does offend me ;) ) install of it [10:44] wouldn't be so much of a pita if the thing actually worked with keyboard layouts :) [10:44] wait, gnome-settings-daemon? :( [10:51] well that certainly recommends ibus [10:51] yeah, and it's certainly something we don't want [10:52] so i guess we gotta follow the breadcrumbs from there onwards [10:53] I don't know where to look - I know there is somewhere - but didn't keep a link to it :p [10:58] ochosi: do you want me to do a bug for this so we can keep tabs on it [10:59] yeah, we should probably set up a utopic-xubuntu-bugs blueprint and then link that bugreport there too [10:59] would be great if you could do that [10:59] currently trying to look into our suspend/lid-close/lock bug again... [10:59] funnily you should mention the blueprint - I did one :p [11:00] ochosi: what to report it against though - not sure - I assume not ibus, but one of our's [11:00] yeah, good question... [11:03] elfy: for the time being, xubuntu-meta i guess [11:04] ok - I'll do that - we can deal with it later, but at least it will be on the list [11:07] exactly, thanks [11:07] ochosi: ok - all done [11:07] bug 1318319 [11:07] bug 1318319 in xubuntu-meta (Ubuntu) "Return of ibus to Xubuntu" [Undecided,New] https://launchpad.net/bugs/1318319 [11:08] and that blueprint also exists already you said? [11:13] I guess you should know now :p [11:14] https://blueprints.launchpad.net/ubuntu/+spec/xubuntu-u-bugs and https://blueprints.launchpad.net/ubuntu/+spec/xubuntu-u-qa [11:19] I thought it would help whoever ended up being xpl not having to do all the blueprints :p [11:24] thanks :) [11:24] yes, it does [11:25] we should list them all on some wiki page so ppl can find them more easily [11:25] https://wiki.ubuntu.com/Xubuntu/Roadmap something perhaps [11:26] in the utopic header - link the main blueprint when we have it - the others will link from that? [11:43] morning everyone [11:43] morning bluesabre [11:43] hows it going? [11:44] going well thanks :) [11:47] elfy, ping [11:48] bluesabre: http://pastebin.com/P7WDAzNd - was looking at things to playt music with - noticed that parole was almost constantly wanting ~15% CPU [11:48] lderan: pong [11:49] lderan: so currently on the qa blueprint I've got 'Target specific apps for autopilot during this cycle' [11:49] okay [11:50] what would be good I think is for us to actually go for gtk3 apps - they appear to be more likely to get somewhere - is that right? [11:50] yeah [11:50] theres not much we can do with the others [11:51] ok [11:51] so if the list is right - there are 6 gtk3 apps without a test - https://wiki.ubuntu.com/Xubuntu/Roadmap/Specifications/Utopic/Autopilot [11:52] as it appears that however often we ask if anyone is interested the answer is tumbleweed ... [11:52] are you going to have time to get any of those done? [11:53] because no-one's coming forward to join in [11:53] I'd help if I could [11:53] elfy, I can confirm that the cpu usage does seem high [11:53] i will do them next week, i have gotten my afternoons back from work for the next 2 weeks \o/ [11:53] want to report a bug to the bugzilla? [11:53] then im on holiday for a week after that [11:54] lderan: there's no rush - I'd rather know that we can get 1 done definitely - if you see where I'm going [11:54] yeah i do, i would like to get them done while i know i have the time to do them :) [11:55] lderan: change that blueprint line to reflect that you're doing it - maybe add a line for which you intend to do [11:55] please :) [11:55] sure thing :) [11:55] awesome [11:55] * elfy aims to get QA blueprint all DONE by end of May :p [11:56] \o/ [11:56] bluesabre: ok [11:56] thanks [11:57] we'll tackle the resource usage this cycle since we're pretty happy with the rest of the app [11:57] bluesabre: do we need a LP one as well - we can track it on blueprint then ? [11:57] sure, and then we can link the lp one to the xfce one [11:57] yep - I'll go do that then [11:58] excellent, thanks elfy [11:58] lderan: ok - so anything else that you can think of we need to worry about blueprint wise? [11:59] can't think of anything but will let you know if i do [11:59] and please keep trello current - easier to put detail there imo [12:00] ok - thanks - I'll leave you to have a good day then :) [12:00] will do [12:00] thanks :) [12:08] bluesabre: bug 1318326 [12:08] bug 1318326 in parole (Ubuntu) "High CPU usage while playing audio files" [Undecided,New] https://launchpad.net/bugs/1318326 [12:08] thanks elfy :) [12:08] and it's on the u bug blueprint as well [12:09] 2 bugs today \o/ [12:09] I'm wrapping up the main menulibre bugs and preparing for a new release today (that should hit T and U) [12:09] wewp [12:09] woohoo [12:12] hey bluesabre [12:12] hey ochosi [12:13] btw, i looked into xdg-screensaver a bit today [12:13] it's very odd, it *should* actually work and inhibit the screensaver even with the X11 extension [12:13] you can look into /usr/bin/xdg-screensaver [12:13] I find a lot of *shoulds* when working with xdg-* [12:14] it's a fairly simplistic script that checks for what screensavers are installed [12:14] a bit like xflock in fact [12:18] hm [12:19] lots of ifs and stuff [12:19] * elfy sits down to watch people running in circles [12:19] wish I could help ;) [12:19] seems like you might want to start by expanding detectDE [12:19] elfy: you already did the blueprint, that's great stuff tbh [12:20] elfy: you can also set up the other bps and email the team leads about filling them ;) [12:21] yeah, seems like we just need to add light-locker support in there [12:21] ochosi: I can if you want - sitting here thinking about making the rest of the day as lazy as the morning was :) [12:21] yup, but honestly as it doesn't detect it, it *should* do the right thing (i.e. modify the xset props) [12:21] towards the bottom: [12:21] detectDE [12:21] # Consider "xscreensaver" a separate DE [12:21] xscreensaver-command -version 2> /dev/null | grep XScreenSaver > /dev/null && DE="xscreensaver" [12:21] # Consider "gnome-screensaver" a separate DE [12:21] elfy: hehe, thanks, that'd be great! [12:21] gnome-screensaver-command -q > /dev/null 2>&1 && DE="gnome_screensaver" [12:21] yeah [12:22] but there seems to be a difference between controlling just the xscreensaver [12:23] I'd add some output to the if/else chain and figure out where its landing [12:26] bluesabre: obviously a reason for it - but cpu usage in parole when watching a video is nowhere near the usage with audio - added it to the bug report [12:26] cool, that will help figure out whats going in [12:27] and thinking about it now, I think I might know where all the cpu cycles come from [12:27] mmm - added it to both bugzilla and LP - but doesn't LP grab comments from the outside source? probably a waste of time lol [12:27] thanks bluesabre [12:29] yeah, LP will automatically display external comments after a while [12:29] i mean adding a special case for light-locker should also work... [12:29] and i hope this would not only fix parole, but all other players too [12:29] yeah, hopefully :) [12:30] well i don't think xscreensaver does anything else about it, tbh [12:30] btw, reviewed and merged that greeter MR today [12:31] it does a bit... screensaver_xscreensaver() [12:31] thanks for that ochosi [12:31] yeah, i meant: xscreensaver itself doesn't do anything in terms of listening to player-signals itself [12:31] whoops, that was a bit too much itself ) [12:31] :) [12:32] so i guess other players also at least try xdg-screensaver [12:32] in itself that's not too much too worry about :p [12:32] hehe, thanks elfy :) [12:33] :) [12:36] ochosi: so - I need to put someone in the Approver box for these things - that is you ;) [12:36] what approver box? [12:36] in the blueprint [12:36] it was knome - but he's escaped now ;) [12:37] at the moment it's not really any issue as they're not approved/registered by -release [12:38] or I can put my name in and then when you approve them you can change it - maybe that way would be better, so you know what you have approved [12:38] sounds good to me! [12:38] ok [12:46] bluesabre: btw, how are you debugging that at the moment? [12:46] debugging...? [12:46] ochosi: do you want me to do roadmap and new features blueprint as well ? [12:46] throwing lots of code at menulibre [12:46] seeing what sticks [12:46] like spaghetti noodles [12:46] oh, i thought you were looking at xdg-screensaver :) [12:47] oh, I just glanced at it [12:47] :) [12:47] you're the light-locker dev ;) [12:47] elfy: yup, please [12:47] bluesabre: awwwwh :) this isn't light-locker related though [12:47] the same should happen to anyone who doesn't use xscreensaver or gnome-screensaver [12:47] it kind of is ;) [12:48] i'm currently looking into the lid-close problem [12:48] how does unity handle it? [12:48] lid-close? [12:48] not locking [12:49] not locking? [12:49] sorry, you lost me there [12:49] when playing a bideo [12:49] *video [12:49] my guess is this: [12:49] not activating the screensaver that is [12:49] players handle it by calling xdg-screensaver [12:49] but i dunno [12:50] currently #u-desktop is dead so i can't ask there [12:50] since they no longer use gnome-screensaver, I'd be interesting in looking at the unity-locker code [12:50] maybe they also handle it by gnome/unity-settings-daemon [12:50] ah [12:50] true [12:50] cheaters [12:50] as they do with most of their stuff [12:50] it could be useful being able to "plug in" stuff into xfsettingsd [12:51] anyway, that's a different story [12:52] lemme know when you have time, then we can also look into the xdg-screensaver thing together [12:52] i'll look at xfpm meanwhile [12:54] ok [12:55] hopefully I'll actually be around today [12:55] didn't get home til 3am last night, so my wife should be asleep until noon [12:55] :) [12:57] huhu [12:57] so no photo-shoot today i suppose :) [13:12] ochosi: you has mail [13:12] yup, already acted on one of them [13:12] they are all built now [13:12] thans [13:12] ks [13:12] I meant from me :D [13:13] oh :) [13:13] hehe [13:13] haven't received that one yet then [13:13] I really don't know what mail you have :p [13:13] I just sent it :) [13:13] good good [13:15] no idea what to do with them afterwards - I know that -release do something eventually :) [13:15] and I would guess that the roadmap one has all the others as dependencies [13:16] will talk to knome about it [13:17] yea [13:17] luckily the next release will not bring so many drastic changes and not such a high amount of workitems as the last [13:17] indeed [13:32] elfy: linked up the blueprints to the https://blueprints.launchpad.net/ubuntu/+spec/topic-u-flavor-xubuntu now [13:33] thanks :) [13:33] well, thank you ;) [13:34] they just need fleshing out now then :) [13:34] indeed [13:34] except the bugs one - we don't want that one to be fleshed out :D [13:35] huhu [13:58] bluesabre: still around? [13:58] ochosi: yup [13:59] sooo [13:59] it looks like we have a real promising fix for the lid-close problem [13:59] but i guess lls will need another update for that as well [14:00] cause light-locker needs to handle lock-on-suspend again [14:00] yay! [14:01] but now that might create another headache [14:01] cause light-locker then somehow needs to "secretly" tell xfpm *not* to lock on suspend [14:03] yay [14:03] :> [14:03] (without the !) [14:04] actually eric just said that it worked for him [14:04] so maybe it'll just be fine [14:04] we need to just tell light-locker-settings to always add the "--lock-on-suspend" again when that option is set in lls [14:04] that should suffice [14:04] * ochosi knocks on wood [14:05] ow :( [14:05] that's my head [14:05] bluesabre: could i ask you to do a PPA upload of the fixed version? (will land in github) [14:05] ochosi: sure thing [14:05] and ideally a light-locker-settings version with that tiny change included [14:05] then we can really ask ppl to test it [14:06] commit that change to trunk :) [14:06] or I'll do it shortly [14:06] almost finished fixing menulibre [14:06] yay! [14:06] elfy: yeah, it's all a bit confusing and complicated, hopefully we can clean this up in the next releases [14:07] yep [14:07] but I was referring to you knocking on wood :p [14:07] haha, ok [14:07] didn't get that at first [14:07] * elfy thinks that this new team PPA thing will be really useful [14:08] yup [14:09] bluesabre: ok, here goes the xfpm thingy we need: https://github.com/EricKoegel/xfce4-power-manager/commit/21b8e5abf4e5f93c28cb964b4618b9b509780951 [14:09] did we ever finalize the team ppa idea? [14:09] we planned to talk about it in a meeting [14:09] but the discussion was heading the way of using the xubuntu-dev PPA [14:09] go carried over from last weeks meeting [14:10] so packages would need approval from someone in xubuntu-dev [14:10] I thought we were looking at having 2 ? [14:10] maybe, yeah [14:10] ok, I'll create the package in my own ppa for now until thats cleared up [14:10] one for testing things with [14:10] one for bugfix, one for new apps [14:10] that was the main idea [14:10] yea [14:10] that makes sense to me [14:13] we could also do PPAs controlled by x-dev that carry the release number they're for in the name [14:13] so ppl don't get confused easily [14:13] e.g. xubuntu-staging-14-10 [14:16] yep [14:16] xubuntu-extras-14-10 [14:16] or something like that [14:16] Unit193: thoughts ^ ? [14:31] >.< [14:32] wine apps make everything more difficult [14:32] their desktop files are installed with spaces [14:32] it seems xdg-menu-install doesn't properly parse spaces [14:33] meh [14:33] er, xdg-desktop-menu install [14:33] stupid xdg stuff [14:33] xdg-desktop-menu uninstall doesn't work at all, just freezes [14:33] need to report these bugs [14:34] and work around them in menulibre [14:35] brainwash: wanna test a fix for the lock-suspend problem? [14:36] ochosi: I cannot test it cause I'm not affected by the problem :/ [14:37] bbiab [14:37] well, I can test it, but I cannot confirm if it fixes the problem :) [14:37] brainwash: you mean lid close +lock+suspend works fine for you? with the default 14.04 setup? [14:38] still 13.10 here [14:39] elfy will gladly test it [14:40] in case the lid is still functional from all the previous testing :) [14:40] * elfy probably isn't sure what state the thing is in ... [14:49] I will have to upgrade my test system to utopic, roughly 7500 packages [14:49] this will take a while [14:49] slow connection + very very slow hdd [14:50] elfy: does parole also eat your cpu resources in 14.04? [14:53] brainwash: parole is using 7% on 14.04 with all my cpus sitting at 800Mhz (ondemand) [14:54] appears to be quite high [14:54] sound only, right? [14:55] Audio going the long way through pulse then jack. [14:55] but those are separate processes [14:55] parole on its own is 4.3% [14:56] ah [14:56] that's a different story then [14:56] brainwash: no idea of the top of my head - I don't use it generally and I've not booted 14.04 to use for a while now [14:57] elfy: ok, maybe we'll get more information later on [14:57] I only noticed it this morning [14:58] I see [14:58] and you've already assigned it to the 14.10 bugs blueprint [15:00] yes [15:01] why? [15:04] the resource usage is probably a draw function that's being rapidly fired [15:05] since its only with the audio portion [15:07] and we have custom drawing going on [15:08] that's what the issue was with the greeter earlier [15:10] ochosi: this laptop is now in a position where it is broken with suspend and lid-close again [15:46] elfy: okeyokey, depending on how long it takes bluesabre to set the PPA up, we'll have something to test for you :) [15:50] ok noss [15:50] boss even [15:50] bluesabre: maybe we can do this part of parole with gtkoverlay now? [16:08] ochosi: which part? we are using gtkoverlay [16:09] going to grab lunch, will take care of the ppa when I get back [16:15] bluesabre: i meant the audio-info box, iirc that wasn't gtkoverlay [16:46] bbl [16:46] bluesabre: btw, the normal X11 screensaver code in xdg-screensaver seems to be duplicated. no idea why. maybe that's why it doesn't work.. [19:47] ochosi, you around?