| bluesabre | ochosi: just the one | 00:37 |
|---|---|---|
| bluesabre | ochosi: latest daily packages, brightness icon is white again | 01:45 |
| ochosi | bluesabre: yeah, it's possible that i haven't pushed the brightness icon yet, don't remember right now | 07:51 |
| slickymasterWork | morning everyone :) | 10:06 |
| ochosi | morning | 10:09 |
| slickymasterWork | hey ochosi. I'm back :) | 10:09 |
| slickymasterWork | everything that's good it's bound to have an end :( | 10:10 |
| slickymasterWork | so did my holidays | 10:10 |
| ochosi | sorry to hear | 10:10 |
| ochosi | hope you enjoyed yourself | 10:10 |
| slickymasterWork | from the look of my email I see that I have a lot to catch on | 10:10 |
| slickymasterWork | yes I did. Three weeks of nothing but surfing and biking | 10:11 |
| ochosi | slickymasterWork: sounds awesome | 10:48 |
| slickymasterWork | ochosi: I've just finished 2014-07-29 meeting log and starting the 2014-08-14 one | 10:49 |
| slickymasterWork | do you know if knome has started on pkexec yet? | 10:49 |
| ochosi | not sure, haven't talked to him about it yet | 10:50 |
| slickymasterWork | ok, I'll ping him about it | 10:50 |
| slickymasterWork | I see there's also the new NetworkManager item to be worked on | 10:51 |
| bluesabre | slickymasterWork, wb | 10:54 |
| bluesabre | ochosi: thing is, the icon was correctly colored, at least for a day | 10:55 |
| ochosi | bluesabre: hm, fun :) | 10:55 |
| ochosi | lemme check | 10:55 |
| bluesabre | ochosi: also, trying to add properties to the indicators with the greeter, e.g. ~separator:expand:nohide | 10:56 |
| bluesabre | er | 10:56 |
| bluesabre | :nodraw | 10:56 |
| bluesabre | and :center | 10:56 |
| bluesabre | ~spacer has the same issue as the xfce panel, can't really center anything | 10:56 |
| slickymasterWork | hey bluesabre, thanks. It's good to be back | 10:57 |
| ochosi | mm, i see | 10:57 |
| ochosi | bluesabre: tbh i'm not sure why it's not working | 10:58 |
| bluesabre | if I can't accomplish that, we'll just make the login panel look like the desktop panel (which, maybe we should do anyway) | 10:58 |
| ochosi | as far as i can see, the icon is there in the correct size in the icontheme | 10:59 |
| ochosi | could you check whether anything changes if you switch to -dark or elementary-xfce? | 10:59 |
| ochosi | (i'm on a desktop here atm, so can't test anything) | 10:59 |
| bluesabre | elementary-xfce is correct | 10:59 |
| ochosi | i could actually drop the icon for the brightness plugin from the icon theme, that'd make things a lot easier... | 11:01 |
| ochosi | so how about -dark? (i presume you were using -darker) | 11:02 |
| bluesabre | -dark is white | 11:02 |
| bluesabre | -darker is white | 11:02 |
| ochosi | argh | 11:03 |
| ochosi | just found the issue i think | 11:03 |
| bluesabre | maybe just drop the white ones from 16/22/24 ? | 11:03 |
| bluesabre | er | 11:03 |
| bluesabre | keep them for those sizes | 11:03 |
| bluesabre | still early | 11:03 |
| ochosi | yeah, i could, that'd mean not supporting the brightness plugin anymore | 11:04 |
| ochosi | ok, could you quickly edit elementary-xfce-dark/index.theme | 11:04 |
| ochosi | change "MinSize=24" (or whatever it is) to MinSize=33 | 11:05 |
| ochosi | and then sudo gtk-update-icon-cache | 11:05 |
| ochosi | these panel icons are really tricky | 11:05 |
| bluesabre | no good | 11:08 |
| ochosi | i guess you're using -dark now, right? | 11:08 |
| ochosi | cause it could be that the icon-cache doesn't work if you update -dark but use -darker | 11:08 |
| ochosi | you can also set the minsize to 48 | 11:08 |
| ochosi | or drop Min and MaxSize | 11:09 |
| bluesabre | updated -dark, switched to -dark | 11:10 |
| bluesabre | trying 48 | 11:10 |
| ochosi | hm, that's really the only reasonable explanation i can think of right now | 11:11 |
| bluesabre | 48 failed, dropping min and max failed | 11:12 |
| bluesabre | I'll let you work it out ;) | 11:12 |
| ochosi | argh | 11:12 |
| ochosi | does the brightness icon have a shadow below it or not? | 11:13 |
| ochosi | i mean the white version | 11:13 |
| bluesabre | yes | 11:13 |
| ochosi | ok, then it | 11:13 |
| bluesabre | otherwise I'd think there was no icon | 11:13 |
| ochosi | 's the 22px version | 11:13 |
| ochosi | so the min/maxsize approach couldn't have helped anyway | 11:13 |
| ochosi | btw, what are the chances of getting xfpm's 1.4 release into utopic? | 11:16 |
| ochosi | (there won't be too many new features, mostly bugfix i think) | 11:16 |
| bluesabre | ochosi: depends when it lands | 11:17 |
| bluesabre | but we should be able to if its reasonable soonish | 11:18 |
| ochosi | ok | 11:26 |
| ochosi | well we're targetting debian i think | 11:26 |
| ochosi | so might need a FFe for that | 11:28 |
| ochosi | and i guess it'll help that we already have 1.3.1 | 11:29 |
| bluesabre | yeah | 11:50 |
| ochosi | we're waiting for translators and new bugreports atm | 11:58 |
| bluesabre | cool | 12:00 |
| bluesabre | Heading to work, bbl | 12:01 |
| ochosi | and trying to fix a few remaining issues | 12:01 |
| ochosi | hf | 12:01 |
| === brainwash_ is now known as brainwash | ||
| elfy | and roundabout now in #xubuntu is exactly why ditching gksu for a non-working pkexec is a big fail | 14:21 |
| ochosi | yeah well, users who don't know what they're doing at all are not really a super-cool argument for shipping gksu... | 14:22 |
| elfy | so I give up caring about the end user? - who IS likely to have no idea at all, because some people in *buntu decided it's not a good idea and then nothing replaces it | 14:24 |
| ochosi | that's really not what my argument was about... | 14:25 |
| elfy | I'd love to see the logs of the discussion from when it was decide to remove it, and how that took into consideration the user | 14:25 |
| ochosi | ok, overstating it a bit so that it's clear: i think a user who doesn't know how to install gksu should probably not use it | 14:26 |
| elfy | because frankly I can't see how it's better for the end user to go from something that worked to nothing at all | 14:26 |
| slickymasterWork | ochosi: thing is that your argument is also valid for pkexec | 14:27 |
| elfy | and beforehand they didn't need to do that did they, they could just be told to use gksudo thunar to do a taks | 14:27 |
| ochosi | slickymasterWork: thing is, pkexec doesn't just execute any random command with superuser rights, but specific apps that potentially need superuser rights | 14:28 |
| elfy | not for us in 14.04 it doesn't ochosi | 14:28 |
| ochosi | we can ship a profile for thunar and pkexec in 14.04.2 | 14:28 |
| elfy | and now we've got someone telling someone to use sudo thunar instead of sudo -H or something | 14:29 |
| ochosi | no need to be so upset (or if you are, let's channel that into more constructive ways) | 14:29 |
| elfy | I'm not upset - it just annoys me that the discussion that was had didn't deal with this then I guess | 14:30 |
| ochosi | i think at least within xubuntu we didn't have much of a discussion, or if we did, i don't remember | 14:30 |
| ochosi | and anyways, complain to knome about it. 14.04 is his responsibility ;) | 14:30 |
| elfy | lol | 14:30 |
| elfy | was before my time I think - I certainly don't remember anything | 14:33 |
| ochosi | either way, we can either whine about it or try to get a pkexec profile for thunar and e.g. terminal included in 14.10 at least | 14:33 |
| elfy | or reuse gksu | 14:33 |
| ochosi | i | 14:34 |
| ochosi | i'd prefer to try to make pkexec work first | 14:34 |
| ochosi | i personally don't see that profiles are needed for that many apps | 14:34 |
| elfy | I'd personally guessed at the 3 I did profiles for here | 14:35 |
| elfy | though the thunar one's now not working | 14:35 |
| elfy | nor mousepad - both cannot open display | 14:36 |
| ochosi | well after creating the profiles for the apps we need, step 2 is to bug bluesabre about including the profiles in the packages and upload then | 14:36 |
| ochosi | s/then/them | 14:36 |
| elfy | yep - well it appears that the ones in the roadmap page are not longer working | 14:40 |
| * elfy starts the long winded task of checking out -core again ... | 14:41 | |
| ochosi | hm, why are they not working anymore? | 14:41 |
| elfy | no idea ochosi - I get Cannot Open Display now :| | 14:41 |
| elfy | for all 3 | 14:42 |
| ochosi | right, but why? | 14:43 |
| elfy | no idea ochosi - I didn't work out the syntax I just amended it to suit | 14:44 |
| brainwash | ochosi: found something interesting, please take a look at bug 1325675 | 15:00 |
| ubottu | bug 1325675 in xfce4-indicator-plugin (Ubuntu) "Indicator Plugin Area Refuses to Match Xfce Themes & Certain Icons are Cut Off" [Undecided,Confirmed] https://launchpad.net/bugs/1325675 | 15:00 |
| brainwash | not sure about 2., but 1. may be caused by the gtk theme not supporting gtk3, right? | 15:01 |
| ochosi | 2. is known | 15:02 |
| ochosi | ubuntu changed their indicator api shortly before the release | 15:02 |
| ochosi | because they wanted to support hidpi displays | 15:02 |
| ochosi | so the indicator icons (which used to be hardcoded to 22px) come in any size now | 15:02 |
| ochosi | and the plugin doesn't handle this anymore, because it still assumes that the icons are always 22px | 15:03 |
| ochosi | putting that icon in a folder that is defined as fixed size in index.theme in the icon-theme fixes the issue btw | 15:03 |
| ochosi | "fixes" = works around it | 15:03 |
| brainwash | mmh, yeah, you should tell the affected people about this workaround :) | 15:04 |
| ochosi | and yeah, issue 1 is probably what you suggested | 15:04 |
| ochosi | feel free to quote me ;) | 15:04 |
| brainwash | argh :D | 15:04 |
| brainwash | so it's a dupe of bug 1313531 | 15:05 |
| ubottu | bug 1313531 in xfce4-indicator-plugin (Ubuntu) "Huge Wallch icon in Xubuntu 14.04" [Undecided,Confirmed] https://launchpad.net/bugs/1313531 | 15:05 |
| ochosi | yup | 15:06 |
| brainwash | ok | 15:06 |
| ochosi | and yeah, andrzejr gave the explanation there | 15:08 |
| elfy | ochosi: so they used to work in the old install, but because I use gksu I didn't know they were missing from this one ... once they are there - they all work fine | 15:12 |
| ochosi | elfy: err, so what, the files in the wiki work after all? | 15:14 |
| elfy | indeed they do | 15:15 |
| ochosi | ok, then let's add an item to development for bluesabre to upload them | 15:15 |
| elfy | we going to sru this back to 14.04 at some point too? | 15:15 |
| ochosi | yeah, we can, but first step is to get it into 14.10 either wa | 15:15 |
| ochosi | y | 15:15 |
| elfy | not so sure we need to bother with terminal tbh - sudo -i or any number of other options for that | 15:16 |
| ochosi | right, so only thunar and..? | 15:17 |
| elfy | mousepad is the only other one | 15:17 |
| ochosi | right, makes sense | 15:18 |
| ochosi | so those two bluesabre should have access to | 15:18 |
| ochosi | or even Noskcaj | 15:18 |
| elfy | the files are all on the roadmap for it | 15:18 |
| elfy | added to trello and features blueprint | 15:19 |
| ochosi | cool, thanks | 15:19 |
| elfy | those files might need tidying up - not sure, but they all work | 15:19 |
| ochosi | could you report a bug against mousepad and one against thunar adding those files? | 15:20 |
| elfy | okey doke | 15:20 |
| ochosi | ideally link them to the features blueprint | 15:20 |
| ochosi | then things should go ahead smoothly | 15:20 |
| elfy | yep | 15:20 |
| elfy | ochosi: launchpad only - or bugzilla? | 15:22 |
| ochosi | for now launchpad is fine, although mousepad is more active than thunar, so you could give that a try | 15:22 |
| elfy | ochosi: ok - both done on LP, mpad on bugzilla and linked, both added to blueprint | 15:31 |
| ochosi | sweet, thanks a lot elfy | 15:31 |
| elfy | s'ok :) | 15:34 |
| lullis | Hi. I have a few questions regarding the AppIndicator on xubuntu. I am trying to write an indicator applet (using python), and documentation is sparse, to say the least. The few source samples I found, I was expecting to see an indicator showing up, but no dice. Will the best way to take a look into an existing indicator (I found indicator-weather who seems to be a single 3kLoC python program) and reverse engineer the API? | 15:51 |
| rowboatn1ck | isnt the indicator bar just a gtk widget? | 15:59 |
| rowboatn1ck | lullis: statusicon? | 16:01 |
| ochosi | lullis: yeah, i think the docs are scarce. i guess people who have written indicators have used other indicators as examples | 16:06 |
| ochosi | also, not that the api changes a lot | 16:06 |
| ochosi | if you wanna do something just for the xfce panel, a plugin would be better, and it's actually not that hard to do (and there's a sample plugin) | 16:07 |
| brainwash | bug 1293287 should be fixed in utopic, but what about trusty? could or should it be fixed via backports at some point? | 16:21 |
| ubottu | bug 1293287 in xfdesktop4 (Ubuntu) "xubuntu 14.04 'xfdesktop --reload' no longer cycles wallpaper image" [Undecided,Confirmed] https://launchpad.net/bugs/1293287 | 16:21 |
| brainwash | by backporting the new dev release 4.11.7 | 16:21 |
| lullis | ochosi, it will have to be an indicator. Basically I have an application that deals with authentication through sd cards, and I need to put this indicator on both the desktop panel and on the login greeter. | 16:22 |
| ochosi | lullis: i see. then i guess you have no choice but to look at existing examples. you might also want to ask around in #ubuntu-desktop | 16:23 |
| lullis | Ok, thanks. | 16:24 |
| elfy | Unit193: https://sigma.unit193.net/~unit193/core.html so Install gets you the tasksel, command-line doesn't - but currently BOTH still require the apt-get install command, - core is missing from selection | 17:28 |
| elfy | ochosi bluesabre ^^ | 17:28 |
| elfy | ochosi: so what's the plan with this and utopic - or are we going to revisit it in valiant vampire ? | 17:31 |
| ochosi | elfy: i'm waiting for Unit193's feedback on this. have no idea what it would take to fix that so it's hard to judge for me whether we can fix it in time for 14.10 | 17:58 |
| elfy | ok - well I'm just drafting testcase(s) | 18:00 |
| elfy | Unit193: if you could have a look http://pad.ubuntu.com/xubuntu-core thanks | 18:08 |
| Unit193 | ochosi, elfy: Right, both require you to install xubuntu-core^ right now because tasksel hasn't been updated, I've pinged the person a couple times, but he's been on vacation I believe so that won't help much. | 18:33 |
| ochosi | Unit193: who's "the person"? | 18:34 |
| elfy | okey doke - thought it was something like that | 18:34 |
| ochosi | so i guess we can get that fixed after FF, right? (i mean tasksel being updated) | 18:34 |
| Unit193 | ochosi: cjwatson. | 18:38 |
| elfy | ahh | 18:38 |
| knome | slickyma1ter, haven't, i've been busy with stuff, like laying around the summer cottage ;) | 20:50 |
| brainwash | shouldn't xubuntu-default-settings provide the pkexec policy files for thunar and co? | 21:18 |
| === halfie_ is now known as halfie | ||
| knome | wouldn't it be better if they were shipped with the application packages itself? that way *anybody* using thunar could get that policy... | 21:20 |
| knome | i mean of course it's a fair fallback *for now* to ship them in the default settings package | 21:20 |
| brainwash | so it has be included upstream? | 21:21 |
| brainwash | has to be | 21:21 |
| brainwash | bug 1358361 | 21:23 |
| ubottu | bug 1358361 in thunar (Ubuntu) "Thunar needs a pkexec policy" [Undecided,New] https://launchpad.net/bugs/1358361 | 21:23 |
| brainwash | is targeting ubuntu | 21:23 |
| knome | well, i'd imagine getting it included in upstream *xfce* would be the most ideal situation, but that's unlikely to happen/propagate for 14.10 at least | 21:24 |
| knome | i was referring to the thunar package in ubuntu | 21:25 |
| brainwash | right, kinda late | 21:25 |
| knome | late and practically we'd have to get 1) policy added in the repository 2) release for all appropriate packages 3) aforementioned landed in debian and 4) synced to ubuntu | 21:26 |
| brainwash | but still, xubuntu users will expect pkexec to work like gksu for every app, won't they? | 21:26 |
| knome | so that might be a stretch even vrt. 15.04.. | 21:26 |
| knome | of course they will. | 21:26 |
| brainwash | oce it works for thunar, mosuepad and ... | 21:26 |
| brainwash | once | 21:26 |
| knome | that's why it's a fair fallbac *for now* to go the default settings route | 21:27 |
| knome | and sure, they'll expect it to work in non-default apps too | 21:27 |
| ochosi | that's one of the reasons why i prefer pkexec over gksu, it doesn't *just work* for any app that might not even need it | 21:27 |
| knome | when it doesn't - well, then they'll have to file a bug and wait for the change to land to the package | 21:27 |
| knome | hey ochosi ;) | 21:27 |
| ochosi | people who know what they're doing can be trusted to install gksu | 21:27 |
| brainwash | sudo xfdesktop4 :D | 21:27 |
| knome | ochosi, and when you say that, everybody becomes one who can be trusted ;) | 21:28 |
| ochosi | well i don't care what users do to their systems willingly | 21:28 |
| brainwash | people just fall back to sudo | 21:28 |
| ochosi | but i prefer to ship sane defaults | 21:28 |
| brainwash | sudo works every time and breaks everything :) | 21:28 |
| knome | brainwash, that's their pick, and they live with the consequences | 21:28 |
| brainwash | and spam the forums and chats with questions about their broken user accounts :/ | 21:30 |
| knome | aren't they doing that with PPA's already? | 21:30 |
| ochosi | actually we asked via the mailinglist for users to submit apps they need to use with superuser rights | 21:30 |
| ochosi | not the huge turnout | 21:30 |
| knome | i mean, sure, it's stupid, but there are *already* a dozen ways to break your installation | 21:30 |
| Unit193 | So we should add more, cool. | 21:31 |
| knome | how are we adding more? | 21:32 |
| knome | i thought we were introducing something that was less prone to break stuff. | 21:33 |
| brainwash | just noticed that the daily iso only ships firefox-locale-en | 21:36 |
| brainwash | did something change? | 21:36 |
| brainwash | should we be worried? :) | 21:37 |
| ochosi | wow, here's one for all the folks who complain about light-locker: https://bugs.launchpad.net/bugs/1358504 | 21:55 |
| ubottu | Launchpad bug 1358504 in unity (Ubuntu) "Screensaver leaks password key-presses through to applications" [Undecided,New] | 21:55 |
| knome | great.. | 21:55 |
| ochosi | well, nobody said writing a secure lockscreen from scratch was easy (which is why we didn't with light-locker) :p | 21:56 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!