[00:01] i installed trusty here, yesterday. Congratulations for all team for this amazing version! [00:02] thanks :) [00:35] the shotwell icon is missing in 22, 24 and 24 [00:36] *32 [00:37] yeah [00:37] not too bad actually [00:38] i drew the ubiquity icon in 4 sizes very quick now [00:38] we can use the existing shotwell icons in our theme and just change parts of it [00:38] the calendar icons also need a cleanup at some point [00:38] and what annoys me a bit is the huge amount of duplication/uncertainty between status/panel/notifications [00:40] when i plug my laptop to AC, battery icon does not change [00:41] is it related to the icons? or other thing? [00:47] sergio-br2: screenshot plz [00:53] hum, it works [00:54] but only if my laptop is charging, then there is the right icon [00:54] so when does it *not* work? [00:55] if it is with 95% or higher, then the icon is not that charging/AC icon, it has that battery icon [00:55] oddd [00:55] luckily we'll have something better next cycle... [00:55] like this: http://en.zimagez.com/zimage/screenshot-27052014-024848.php [00:56] but it is connected/charging? [00:56] that the point [00:56] hmm, but then [00:56] could you quickly open the power-manager preferences [00:57] and then enable the trayicon there [00:57] it's in the first tab [00:57] just to see whether that shows the correct icon [00:57] higher than 95%, my battery does not charge. It charge to 100% only if it has less than 95 % [01:14] btw, the dialog-warning icon in upstream is also much nicer... [01:15] but it's lacking more sizes than it has [01:28] ochosi, take a look: http://www.zimagez.com/zimage/screenshot-27052014-032652.php [01:29] then it's probably a bug in upower [01:29] so nothing we can do about it [01:53] hum dialog-warning is a yellow triangle right? [01:54] yup [01:54] better [01:54] yup [01:54] but also only available in 48px and 64px [01:54] red is like stop, danger, not warning [01:54] there are other icons different too [01:55] apt-daemon-* [01:55] yes, but also those are only available in very few sizes... [01:56] maybe he will do other sizes? [01:56] well, this can be a to do list for us [01:57] i'm very slow, doing other stuff here. I think when i return to brazil, in july, i will have more time [01:57] until 14.04.1 we can do all these things [02:00] yup, maybe/hopefully [02:00] i don't really think he will do any other sizes [02:00] he only does what he needs for eOS [02:00] whatever he's not sure about, he doesn't touch [02:01] (or whatever he never sees in eOS) [02:06] sergio-br2: i think the warning thing i like enough to quickly do the other sizes... [02:07] you do? ok [02:09] yeah, the 24/22 is already done [02:17] humm, only 128px missing now [02:17] sergio-br2: if you wanna do that one ^, i'll leave it for you and push what i got now [02:17] don't think i have the energy to do another size now [02:18] but 16,22,24 and 32 are done [02:18] ok [02:18] push then [02:21] ah, nvm, i'm half-done with the 128px version [02:21] you can focus on other stuff... [02:26] sergio-br2: done. i almost *wanna* see a warning dialog now :) [02:27] working in it [02:28] alrighty, have fun, i gotta get some sleep [02:33] hum [02:37] gonna sleep to [02:37] bye! [03:11] bluesabre: sorry, I'll look at those bugs now [03:11] got sidetracked [04:12] I don't trust bots made by Unit193 [04:12] >_> [04:14] Logan_: Only one of them is here, all the others are elsewhere, don't worry. [04:14] good :P [04:22] bluesabre: ping me when you're around [08:13] morning everyone [08:13] Howdy. [09:35] knome: I don't have a clue why Trello starts with a 'T' and ends with an 'o', other than the fact that is the right way to spell the word :P [09:36] :P [09:37] and a good afternoon knome [09:37] hey slickymasterWork [09:37] hi ochosi, morning [09:37] hey slickymasterWork, ochosi [09:40] slickymasterWork: just a small reminder, please set the time for the next meeting asap [09:45] ochosi, was going to poke you on that. What are your thoughts regarding the amount of time between meetings. weekly baseed? [09:45] slickymasterWork, just schedule something for *next week* [09:45] week 23 that is [09:46] in this case, it might practically mean there's more than a week between [09:46] sorry ochosi, lost connectivity [09:48] 12:45 knome: slickymasterWork, just schedule something for *next week* [09:48] 12:45 knome: week 23 that is [09:48] 12:46 knome: in this case, it might practically mean there's more than a week between [09:48] sure, no problem slicky .) [09:48] +1 on that ^ [09:52] okay guys, let me just check my schedule regarding my kid next week and I'll do it [09:52] sure sure, no rush [09:52] knome, you do realize that this means that I'll be poking this weekend asking for some tutoring [09:52] just something we wanna get done today or tomorrow sometime [09:52] slickymasterWork, no problem. [09:53] it will be done today, I just have to be in touch with is mother [09:54] the announcement is to be made in the ML or the Meetings page? [09:55] ochosi: ^^^ [09:56] slickymasterWork: ideally both [10:04] ok, both it will then [10:16] hey Logan_, what's up? [10:36] ochosi: next meeting is scheduled to June 3rd, 20:00 UTC [10:36] okey, ty [10:36] i presume 20utc is a time that works fine for you? [10:37] cause you can schedule the meeting *whenever* you want [10:37] knome: ^^^ can you please confirm that I add this in the proper place at https://wiki.ubuntu.com/Xubuntu/Meetings [10:37] (that's actually one of the reasons for cycling chairs) [10:37] that's the best time for me, I'll be home without the connectivity constraints I have here at work [10:37] ok gerat [10:37] great [10:38] only asked cause you weren't here last night (same time) [10:40] yeah, but yesterday was due to the fact that I was with my kid, which I won't be next Tuesday [10:43] sure [10:48] slickymasterWork, when you go to the editing mode, you should always have two things there [10:48] "Next meeting isn't scheduled yet." [10:49] and the "The next Xubuntu..." [10:49] just uncomment/comment the appropriate one [10:49] and change the URL and the link text [10:49] otherwise looks good. [10:50] knome, I haven't done that though :P [10:51] I just went ahead and replaced the "Next meeting isn't scheduled yet. with The next Xubuntu Community meeting will take place at 20:00 UTC on Tuesday, June 3rd. [10:51] I'll have to roll it back [10:54] knome: think it's fixed as intended now [10:54] looks good to me :) [10:55] can you confirm, please [10:55] yep [10:55] I left the "Next meeting isn't scheduled yet" commented [10:55] yep, that's good [10:55] that way it's less work to show that [10:55] yes [13:34] meeting is in the calendar now [13:35] thanks knome [13:35] you're welcome david [13:36] :) [13:36] bad connectivity today? === qwebirc817052 is now known as slickymasterWork [13:36] the usual knome [13:36] a lousy one [13:37] hehe [13:37] I'm always with a permanent ttl above my head like a Damocles sword [13:38] so you can't access ssh from work? [13:38] no, no chances [13:39] I only can communicate through port 80 [13:39] to the exterior that is [13:39] mmh [13:39] I can use other ports within out intranet [13:39] to a several servers [17:08] ochosi: add bug 1024482 to the trusty blueprint or just to the utopic one? [17:08] bug 1024482 in unity-greeter (Ubuntu) "Mouse cursor theme does not change from default after login" [Undecided,Confirmed] https://launchpad.net/bugs/1024482 [17:08] it's about the missing busy cursor on the root background [17:09] I assume that we want this to be fixed in trusty too, many people actually complain about the missing busy cursor [17:11] just need to figure out why firefox/thunderbird don't trigger it, most other apps do [17:49] bluesabre: shouldn't lightdm-gtk-greeter depend on lightdm? [19:58] brainwash: so is anyone actually reporting that recently for us? [19:59] or is it really that old - and Ubuntu [19:59] affecting 9 people in 2 years ... [20:02] the report was not targeting the busy cursor problem in xubuntu [20:03] and is anyone reporting it for Xubuntu is what I'm saying? [20:03] I've not seen anything [20:03] bug 1323745 [20:03] bug 1323745 in xfce4-panel (Ubuntu) "Xubuntu: No startup notifications" [Undecided,New] https://launchpad.net/bugs/1323745 [20:03] :P [20:03] 1 person [20:04] if we put every Xubuntu bug on the blueprint it becomes completely pointless [20:04] well, there is some talk about it on ubuntuforums, askubuntu, xfce forum,.. [20:04] we got a fix for it already [20:05] but whatever - fill the blueprint with 100's and 100's of bugs and in 4 months 3 weeks - it'll be still full of 100's and 100's of bugs [20:05] linking it to the blueprint just helps to actually get the fix in (I hope) [20:06] whatever - nothing to do with me [20:06] it's not like I'm adding tons of reports to the blueprint :/ [20:06] no I know you aren't :) [20:06] I just really wonder about the point in even bothering with a report from 1 person [20:07] the ones that should be looked at earlier are ones like xfpm/sound indicator - that we release with and make us look ridiculous [20:08] the new filed report might only affect 1 person as of now, but the issue has been reported on forums and the debian bug tracker [20:09] well, it's just a spinning cursor after all.. nothing of importance :) [20:09] I just fail to see what a debian bug has to do with us :) [20:10] that is Xubuntu - not people in Xubuntu team :) [20:10] lol [20:10] just mentioned it to show that it's a common problem [20:10] lol [20:10] it affects you and me [20:10] sorry brainwash :) [20:11] it doesn't affect me :) [20:11] but you can confirm it [20:11] like every other xubuntu user can [20:11] no I can't [20:12] you see a spinning cursor when you launch some application? [20:12] elfy, you mean you don't consider it a bug, or you see the "working" cursor? [20:12] I don't notice this behaviour - can't confirm it [20:13] i think it might be a design decision [20:13] the bug report isn't particularly descriptive [20:14] do you mean like the 'spinning cursor' you see when you might for instance mount a partition in thunar? [20:14] no, startup notification [20:14] means nothing to me [20:15] you start some app and the busy/spinning/working cursor appears until the app is finally loaded [20:15] oh that [20:15] a visual feedback [20:15] yea don't see that - not that worried about it either :p [20:16] :) [20:17] just want to know if it's worth to fix this in our LTS release [20:17] I'd certainly not be worried enough to go looking for a bug for it - nor report it [20:17] ask the XPL :p [20:18] that's what I did :D [20:18] I was just saying that I'd not put it on the blueprint :) [20:18] as it's not a Xubuntu thing - we might be affected by it [20:20] anyway - whatever - that being something else I said :) [20:22] https://bugzilla.xfce.org/show_bug.cgi?id=10630 you probably want to fix this one first [20:22] bugzilla.xfce.org bug 10630 in General "keyboard settings panel ignores state of "startup-notification" key when resetting to defaults." [Normal,New] [20:22] because without it, startup notification won't work unless the user turns it off and then on again for every launcher [20:23] note i attached a patch to fix that... several months ago [20:25] right, maybe we could apply it downstream [20:26] there is also more stuff broken in libxfce4ui [20:26] kb shortcut related [22:24] evening [22:31] brainwash: lagging behind on the greeter quite a bit currently in terms of merges etc, too busy with other stuff. but i/we will get to it [22:31] as 1.8.5 still hasn't landed in trusty yet, i'm not sure i wanna do another (tiring) effort of backporting a single small patch/fix [22:32] but i won't veto it, if bluesabre feels like it [22:33] maybe with other potential fixes somewhat later, 1.8.6 [22:34] we got plenty of time left with 14.04 :) [22:34] do you have any idea, why the greeter package does not depend on lightdm? [22:38] hm, not really [22:38] the original packaging wasnt done by us, we just kept what was there [22:38] i never saw a need for it i guess [22:39] true, if no one complains, then there is nothing to fix :) [22:39] yeah, if there are problems that arise from it, we'll deal with it [22:45] forestpiskie: OK, so added in that feature ---v [22:45] xubutrello: due soon [22:45] -> 1. Suite B Call (id: 15) due: 2014-06-09 11:00:00 UTC from list: To Do 14.10 [23:26] btw, i never thought about this, but when we get rid of indicator-power, we won't have any battery status in the greeter/lockscreen anymore [23:26] bluesabre: ^ [23:27] unless we add something builtin ourselves [23:28] shouldn't be so hard to implement [23:28] there's a file that keeps track of battery stats and such, right? [23:28] probably not so hard, but kinda duplication of effort [23:29] I was about to implement this, because the indicator support was broken in the greeter :) [23:29] well go ahead and do it now then ;) [23:29] +1 [23:29] frankly, i'm not sure we really want/need indicators in the greeter [23:29] but why do you want to remove -power? [23:29] they seem to be a source of myriad problems [23:29] I'll start merging things soon [23:30] because we have an xfpm battery plugin for the panel now [23:30] or: we will have one in the next release [23:30] cool [23:30] so now we just have to add notification-panel support [23:30] more work! [23:30] :D [23:30] nope [23:30] it's not a systray icon anymore [23:30] oh [23:30] what is it now? [23:30] it's a regular plugin that you can add/remove [23:31] oh [23:31] and place anywhere on the panel [23:31] but there is already a battery panel plugin or? [23:31] eh [23:31] yes, but this one is integrated with xfpm [23:31] makes much more sense [23:31] that makes it less accessible for !xfce [23:31] yeah, but lubuntu is going to qt [23:31] ochosi: I'm proposing the merge of core now, want to be a reviewer? [23:32] Unit193: i can be [23:33] mmh, once unity7 is outdated what will happen with the current indicator stack? [23:33] bluesabre: not sure !xfce uses xfpm, we'll wait for the outcry because of the loss of systray icon i guess [23:34] yeah, who knows what'll happen to it [23:34] :) [23:34] nobody in fact [23:34] which is why i want us to get as independent from it as we can [23:35] will be hard to provide real alternatives to indicator-application though [23:36] partly depends on what ubuntu wants to do with core applications [23:36] most of what ubuntu depends on is gnome stuff [23:36] which, most sane people want to escape, but they really are the best available tools [23:37] since everything else starts with k [23:37] and tend to invite friends [23:37] yeah, i guess [23:37] i think ubuntu will create/use its own core ap stack [23:37] app [23:38] they're already trying the "convergence of desktop and mobile apps" [23:38] yeah [23:38] Meh, lp-propose doesn't work. :/ [23:39] honestly, the converged apps are starting to look really nice [23:39] and I'll probably pick up an ubuntu phone once they're available [23:39] the next big unity stack change will be the move to Qt [23:40] yeah, which will mean no more custom gtk3 hacks i guess [23:40] and plain upstream gtk3 madness :) [23:40] yup [23:40] brace yourselves ;) [23:40] maybe we should just give up on Gtk and join lxqt project [23:41] port everything to Qt [23:41] * ochosi senses duplication of effort [23:41] gtk doesn't seem to be useful or relevant any more [23:41] or join forces with the MATE project :) [23:41] we can always just use any other desktop instead, but luckily the world isn't falling apart just yet [23:42] ali1234: well unity quickly went for qt, i think also because of its usability in the mobile space, or why would you say gtk isn't relevant anymore? [23:43] i say it because gtk seems to only exist for the benefit of gnome now [23:43] also, i use gtk every day and i get my stuff done with it :) [23:43] actually they're starting to take elementary seriously [23:43] partly also though, because their platforms look very similar :D [23:43] no, they're not. what is actually happening is elementary is becoming more and more like gnome shell in every release [23:44] well, "every release" is easy to say when there has only been one ;) [23:44] (2) [23:44] luna and? [23:44] jupiter [23:44] ah right [23:44] i forgot [23:44] :) [23:45] i think it'd be easier to complain in #gtk about all of this if xfce were already gtk3 [23:45] maybe we're better off for now with it not being gtk3 yet, but without being there, chances of not being heard are even lower [23:46] isn't it too late for this anyway? gtk3 is pretty old already, why would they listen to Xfce? [23:47] well history tells you that they hardly ever did [23:47] i have no idea how much xfce devs tried to take influence [23:47] zero? [23:47] ofourdan is working at red hat as far as i know, so no idea why that never helped :) [23:48] brainwash: i really don't know [23:48] maybe he got brainwashed by LP [23:48] you know all about that [23:48] in fact unity didn't quickly go for qt... they had a qt port which they abandoned once already [23:49] yup [23:49] right, they went for qt several times :) [23:49] * ochosi is saying it all wrong tonight [23:50] in my opinion xfce has bigger problems that gtk2 vs gtk3... the panel is in bad shape for one [23:51] the plugin system has serious problems with events [23:52] there are many places where bugs should be fixed in xfce [23:52] too many unmaintained components [23:53] Unit193: while i'm generally +1 on the core MR, didn't you want to organize testing/feedback with elfy? [23:54] ochosi: It'd be easier to do that after it's merged, I think that was the idea at least. [23:54] ali1234: i think the only way you can effectively conquer that problem is by becoming a maintainer of some component and start fixing it up [23:54] doesn't have to be xfwm4, which generally is running okay [23:54] ochosi: The xubuntu-core task can't be created until it's actually part of the archive, so you have to pretend. [23:54] as i said, there are so many unmaintained projects there... [23:55] the problems with panel run deeper than that... they are design flaws [23:55] heh, that you'll have to discuss with NSchermer [23:55] i remember there being a long fight on the ML between him and brian about the plugin system when nick rewrote the panel [23:55] these are big problems and it's going to be xfce 5 if i start trying to fix them [23:56] at this point, anything might land for xfce 4.12 [23:56] :) [23:56] hehe, +1 [23:56] Unit193: wasn't there an iso already? [23:56] no, really. it would break all existing plugins [23:57] ah [23:57] then do it with the gtk3 port [23:57] that will also break all existing plugins [23:57] ochosi: Created using the hacky setup, but merge can wait for approval (and merged later) until tomorrow. I see that as the easiest way to test, but yeah elfy may disagree. [23:58] Unit193: ok, then if you don't mind, let's discuss it with elfy tomorrow [23:59] Yep, sounded like a good idea. (Wasn't trying to cut out testing, just that testing comes after it's in. :P ) [23:59] hehe sure [23:59] i wasn't suggesting that [23:59] i just wanted to know where we're heading