[01:21] <GridCube> knome, ping
[01:24] <Unit193> Bleh.
[01:24] <GridCube> bleh?
[01:24] <GridCube> D: 
[01:24] <Unit193> Yeah, blues says we did switch to xfce4-datetime-plugin, but then back to orage. :/
[07:03] <elfy> knome: so we've got 3 tests done on the b2 again since it was respun - I'm at work till ~17:00
[07:06] <Noskcaj> elfy, Let me know if there's any bugs that need confirming. There's not much i can do other than that
[07:06] <elfy> bugs we saw are all listed on http://pad.ubuntu.com/Xubuntu1310Beta2Release
[07:08] <elfy> Noskcaj: did you catch that last message from me
[07:08] <Noskcaj> no
[07:08] <elfy> bugs we saw are all listed on http://pad.ubuntu.com/Xubuntu1310Beta2Release
[07:09] <Noskcaj> ok, thanks. I'll see if that page will load
[07:10] <elfy> I can mail it to you if you want
[08:46] <ochosi> brainwash: quick update, robert_ancell suggested digging indicator-session for bug #1226509
[08:51] <brainwash> ochosi: but the strange policy difference will remain
[08:52] <ochosi> indeed
[08:52] <brainwash> and that is the core issue
[08:53] <brainwash> why is it different?
[08:53] <ochosi> ask the polkit guys (i guess)
[08:53] <brainwash> why is there a difference between reboot and poweroff
[08:53] <ochosi> robert also didn't know an answer
[08:53] <brainwash> hmpf
[08:54] <ochosi> yup
[08:55] <brainwash> indicator-session is not installed by default, so it would need to be added to xubuntu
[08:56] <ochosi> no, the idea is to investigate why it allows reboot
[08:56] <ochosi> see what it does differently
[08:58] <brainwash> http://cgit.freedesktop.org/systemd/systemd/tree/src/login/org.freedesktop.login1.policy.in
[08:58] <brainwash> no change in upstream
[09:00] <brainwash> or maybe something else is wrong here, why does the multiple-sessions rule apply after logging out completely?
[09:00] <brainwash> s/rule/policy/
[09:01] <ochosi> not sure either
[09:01] <ochosi> so far the greeter was only using lightdm's interface to check this kind of stuff
[09:01] <ochosi> so we never really dealt with it
[09:02] <brainwash> looks like a real expert is needed here
[09:02] <brainwash> for this systemd/logind issue
[09:13] <ochosi> yeah, seems like it
[09:16] <bluesabre> good luck finding one of those
[09:18] <brainwash_> file a bug report upstream?
[09:19] <brainwash_> file a bug report upstream?
[09:20] <brainwash_> and ask about the different policy rules and why logind thinks that multiple sessions are running
[09:24] <ochosi> i guess asking people who use the greeter on a non-ubuntu distro with systemd could help
[09:25] <bluesabre> soooo... Corsac?
[09:29] <ochosi> i was actually thinking about cavalier
[09:29] <ochosi> not sure debian uses systemd atm
[09:30] <ochosi> and morning bluesabre 
[09:30] <ochosi> congrats on yet another sponsored upload
[09:33] <knome> g'day
[09:36] <knome> so we were respun for a new ubiquity
[09:36] <knome> and no need to lose our sleep for getting all the tests in again
[09:39] <bluesabre> ochosi: oh, something got uploaded?
[09:39] <ochosi> bluesabre: catfish 0.8.2
[09:39] <bluesabre> woop!
[09:41] <brainwash> ochosi: maybe pitti could help us with logind
[09:43] <bluesabre> ochosi: have you been getting update notifications in saucy?
[09:43] <ochosi> possible, dunno
[09:43] <ochosi> you mean as an indicator?
[09:44] <bluesabre> as in anything outside of manually checking for updates
[09:44] <ochosi> nope
[09:44] <ochosi> brainwash: feel free to get in touch with him!
[09:44] <ochosi> brainwash: also: i'm considering to revamp a few style elements of the greeter, which is why the patch for the context-menu is still only local
[09:44] <bluesabre> I'm not sure the update manager actually works by itself anymore once they got rid of the auto-launch key
[09:45] <ochosi> hm, no clue tbh
[09:45] <ochosi> but i have to admit i always disable that
[09:45] <ochosi> because i hate the update-checking process spontaneously eating up my cpu
[09:45] <ochosi> so maybe it's also a good thing ;)
[09:46] <bluesabre> except, you know, for security updates :D
[09:46] <ochosi> :)
[09:46] <ochosi> anyway, gotta go, bbl
[09:46] <bluesabre> seeya
[09:46] <brainwash> but an autostart entry still exists, doesn't it?
[09:47] <bluesabre> yeah, it does
[09:47] <bluesabre> I wonder what the update frequency is
[09:47] <brainwash> ochosi: do you "know" him? I don't
[09:59] <brainwash> bug 947008
[10:24] <brainwash> ochosi: regarding the greeter revamp, will (or can) it be included before final release?
[12:33] <brainwash> ochosi: there is a black border in the import dialog of seahorse, maybe it's related to the abiword black border?
[12:35] <knome> brainwash, what revamp?
[12:41] <brainwash> knome: just minor changes -> bug 1227735
[12:42] <knome> aha
[12:42] <knome> maybe.
[12:43] <knome> linked it to the development blueprint
[12:43] <knome> and fixed statuses
[12:43] <elfy> afternoon
[12:43] <knome> hey elf
[12:43] <knome> y
[12:43] <elfy> for a short while
[12:44] <knome> elfy, the respin was due to a new ubiquity upload
[12:44] <knome> elfy, no worries re: getting all images tested again
[12:44] <elfy> yea - sort of got that in the end
[12:44] <elfy> yep
[12:44] <elfy> I wanted to do one to see if I got that odd kernel message
[12:45] <knome> i've got that with some images sometimes, but ignoring has always worked
[12:45] <brainwash> odd kernel message?
[12:45] <elfy> yep - same
[12:45] <elfy> I say - same - but I'd never seen it prior to saucy
[12:45] <brainwash> most of them are odd.. and strange.. and weird :)
[12:46] <knome> brainwash, bug 1220165
[12:46] <elfy> knome: shall I mark them ready then
[12:46] <knome> elfy, sure
[12:47] <elfy> done then
[12:47] <knome> that's definitely a common bug though
[12:48] <knome> so we don't have to worry about linking to that, it should be mentioned in the common infra notes, and if not, then it's probably not critical enough
[12:48] <elfy> and lots of different bugs it should be - mine was not xfs partitions 
[12:48] <knome> i would imagine it's a single bug
[12:48] <elfy> yep - but people keep reporting against specific things like xfs/lvm 
[12:48] <elfy> is what I meant 
[12:48] <knome> yep
[12:49] <elfy> so - beta 2 testing - there were 83 test results recorded for us - I think that is a win \o/ 
[12:49] <knome> yep, definitely
[12:49] <knome> now let's double that for RC ;)
[12:50] <knome> or at least hit 100
[12:50] <knome> anyway, i'm off
[12:50] <knome> see you later :)
[12:50] <elfy> I has an idea - but not enough time to go over it now - we've got some time until then
[12:50] <knome> (release notes are prepared in the wiki, release announcement in the website, just needs publishing)
[12:51] <knome> ->
[12:51] <elfy> get 30 minutes for lunch 
[12:51] <elfy> officially 
[12:51] <knome> heh
[12:51] <knome> bon appetit
[12:51] <elfy> never eat until the evening - just drink gallons of tea
[12:57] <brainwash> ah dammit, nobody cares about my logind question in #ubuntu-devel
[12:58] <elfy> no-one cares or no-one has answered yet ... 
[12:59] <brainwash> both, maybe I should address the question to someone directly
[13:14] <brainwash> ochosi: wait, I can only reproduce the black border in the import dialog of seahorse on one machine (graybird-git)
[14:06] <ochosi> brainwash: what black border do you mean?
[14:07] <ochosi> brainwash: and no, i don't "know" pitti either
[14:23] <brainwash> ochosi: http://oi41.tinypic.com/21owiyp.jpg
[14:24] <ochosi> brainwash: are you using the overlay-scrollbars?
[14:24] <brainwash> yes
[14:24] <ochosi> btw, that doesnt look like a standard widget to me
[14:24] <ochosi> well overlay-scrollbars only work with a patch that is not in git, but only in the ubuntu package (for obvious reasons)
[14:24] <ochosi> so that bugreport would be marked as invalid
[14:26] <brainwash> ok, thanks for clarifying
[14:26] <ochosi> no problem
[14:26] <ochosi> the border-lines in the sidebar are a bit ooto as well
[14:26] <brainwash> so it's not related to abiword
[14:26] <ochosi> nope
[14:29] <ochosi> so ppl on archlinux have the same issue with systemd and the greeter
[14:29] <brainwash> that's great :D
[14:29] <ochosi> yeah...
[14:30] <brainwash> do you want to file a bug report upstream?
[14:30] <brainwash> or do you consider switching to indicator-session anyway?
[14:51] <ochosi> nah, depending on indicators sucks because the greeter should also be used outside of ubuntuland
[14:57] <ochosi> theoretically we could try to work around the issue currently in xubuntu by using indicator-session
[14:58] <ochosi> but it would probably need a patch to work properly
[14:58] <brainwash> yea, we need a working solution for 13.10
[15:00] <brainwash> requesting a change of the affected policy rule might take some time
[15:01] <brainwash> and backporting the changes to systemd 204
[15:02] <ochosi> yeah
[15:02] <ochosi> i know, that's why i wanted to ask whether a workaround in the greeter would be acceptable
[15:02] <ochosi> but if robert_ancell doesn't know i don't know whom to ask
[15:03] <brainwash> on top of that, it's not clear who maintains the ubuntu systemd packages
[15:03] <ochosi> :/
[15:06] <brainwash> why didn't I think of this earlier... #systemd
[15:07] <brainwash> the right channel for our question
[15:08] <PsynoKhi0> Hi, I'm trying to install 13.10 beta 1 on a laptop with a broadcom wireless card, BCM4318, ubiquity gets stuck at "configuring bcmwl-kernel-source"
[15:24] <ochosi> PsynoKhi0: you can get support in #xubuntu, this is the development channel
[15:24] <knome> ochosi, he was pointed here from there :P
[15:24] <ochosi> oh, i see you got sent here
[15:25] <ochosi> well, i can't help anyway ;)
[15:25] <knome> PsynoKhi0, i suppose first download the daily (since you're running a non-stable version anyway), and if it persists, ask #ubuntu+1 and if they can't help, file a bug
[15:33] <PsynoKhi0> knome: will do
[15:34] <knome> PsynoKhi0, thanks
[15:35] <knome> (official beta 2 images should be out todya)
[15:35] <knome> *today
[15:35] <PsynoKhi0> hmm ok
[15:41] <knome> basically, the last daily image is the beta 2 image, unless it gets respun, which is unlikely but always possible
[16:23] <skellat> I'm not sure where to go with LP Bug #1231219
[16:26] <knome> you can't confirm it?
[16:26] <skellat> Haven't got a VM set up yet
[16:27] <knome> hmm, that's a missing icon -icon
[16:27] <skellat> When something like that appears, usually it means you need to mouse over and click for more info
[16:27] <knome> yep, we should know what indicator it is
[16:27] <skellat> I was out handling firewood at The Farm yesterday 
[16:27] <knome> wondering if they are using the default icon theme
[16:28] <skellat> knome: Without a tooltip or anything showing...what was showing could be any of a number of possible indicators
[16:28] <knome> yep.
[16:29] <knome> commented. unless he gives more information, we can pretty safely dismiss.
[16:29] <skellat> That's why I flagged it incomplete
[16:29] <knome> yep
[16:30] <skellat> Are we ready to mark off the ISOs as ready?
[16:30] <knome> they are marked as ready
[16:31] <pleia2> happy beta 2 day
[16:31] <knome> yay
[16:31] <knome> it is happy, now that pleia2 is here
[16:32] <skellat> I'm still trying to read through backlogs
[16:32] <skellat> What's our final count on "Known Issues"?
[16:33] <pleia2> hah
[16:33] <knome> i linked four
[16:33] <pleia2> our beta2 wiki page is lovely
[16:33] <pleia2> https://wiki.ubuntu.com/SaucySalamander/Beta2/Xubuntu
[16:33] <knome> there are obviously more bugs in the xubuntu product
[16:33]  * knome bows
[16:36] <skellat> And it isn't even necessarily software we directly control either
[16:36] <skellat> That takes skills
[16:36] <skellat> :-)
[16:36]  * skellat heads to the kitchen
[16:37] <knome> you have multiple heads?
[16:37] <knome> what are you going to cook with them?
[16:37] <knome> :P
[16:39] <GridCube> heads, he is cooking heads
[16:39] <GridCube> knome, got some minutes?
[16:39] <knome> yup.
[16:39] <knome> cooking heads and tails..
[16:40] <GridCube> can we see the desktop of the week issue? :)
[16:40] <knome> pleia2, have some minutes?
[16:40] <knome> let me open up the admin interface for xubuntu.org
[16:41] <knome> bah, permission problems.
[16:41] <GridCube> yes
[16:41] <knome> no, i mean file access
[16:41] <knome> who shall kick IS this time?
[16:43] <GridCube> P: i dunno
[16:45] <knome> pleia2, RT #23091
[16:45] <knome> what else?
[16:46] <elfy> evening all
[16:46] <GridCube> hi
[16:47] <GridCube> knome, so we can go over the things?
[16:47] <knome> GridCube, sure
[16:48] <GridCube> ok, so i got a few images, mine, unit193, and some others that dont have problems, or shouldnt have
[16:48] <knome> yup
[16:48] <knome> we should prepare the page on xubuntu.org
[16:48] <knome> pending on canonical IS :P
[16:49] <pleia2> thanks knome 
[16:49] <knome> np
[16:49] <knome> poked them, might get fixed in a minute
[16:50] <knome> it is a trivial issue altogether
[16:51] <elfy> knome: just a small point re the beta2 notes at wiki - we tell people that abiword has a black ruler - which is easy enough to deal with - but don't say anything about user admin crashing when adding users, not particularly worried just not seeing the logic in it :)
[16:52] <knome> elfy, let me tell you a secret... there is no logic in it
[16:52] <elfy> ok - that's sorted then :)
[16:53] <knome> elfy, if you think the users-admin bug is worth mentioning, feel free to go ahead and add it to the list - i'm fine with that
[16:53] <elfy> I might later aqfter some thought :)
[16:53] <knome> just don't think we want to list all bugs we've had, because that would pretty much defeat the purpose
[16:54] <knome> the list needs to be only so long that people actually read it
[16:54] <elfy> I understand that :)
[16:56] <brainwash> nm-applet and xfce4-indicator-plugin tend to "crash" alot on login
[16:56] <brainwash> it's like every 2nd login they decide to trigger apport :)
[17:06] <GridCube> knome, https://wiki.ubuntu.com/Xubuntu/Marketing/Projects/DesktopOfTheWeek
[17:07] <GridCube> updated the wiki list, the last two just need the users to update their licence, but they should be OK 
[17:07] <knome> okay
[17:08] <knome> i need to document a plugin.
[17:15] <knome> http://xubuntu.org/?page_id=1801&preview=true
[17:16] <knome> we probably want bigger and more visible captions (and desciption in addition to title), right?
[17:16] <elfy> I'm sorry, but you're looking for something that is not here.
[17:16] <elfy> couldn't say :)
[17:16] <knome> elfy, login in at /wp-admin/
[17:16] <knome> then reload the page
[17:17]  * elfy has no idea about that - think I've done it once :)
[17:17] <knome> now you have some idea? ;)
[17:18] <elfy> yep :)
[17:19] <elfy> I'd agree with your comment ^^
[17:20] <knome> that needs some css updates
[17:20]  * elfy wanders of into the corner of the room muttering about voodoo 
[17:21] <knome> heh
[17:23] <knome> i'm off now. i'll work on the general site updates and this when i have some time for that
[17:23] <knome> see you
[17:23] <elfy> cya later
[17:23] <elfy> knome: when we're both about in the nearish future - I'd like to grab 10 minutes - nothing urgent though 
[17:24] <knome> well i can have that 10mins now, i have nothing i have to run to
[17:24] <elfy> ok - I can do it now 
[17:25] <elfy> I'm just looking forward to testing etc for T cycle - I know we have social media things we can shout on - I'd like to see that happen, but I don't do so myself 
[17:25] <knome> sure
[17:26] <knome> they are administrated by various people
[17:26] <elfy> also what's the chances of getting something a bit more prominent on xubuntu.org 
[17:26] <knome> we should probably look into extending the admin groups for each during the T cycle
[17:26] <knome> pleia2, ^
[17:26] <elfy> like kubuntu do - maybe announcements or links to the social things? 
[17:26] <knome> well we have links on the footer
[17:27] <knome> and we can post blog articles
[17:27] <knome> i should go through some scenarios while i update the site looks
[17:27] <elfy> http://www.kubuntu.org/   the latest news/announcements thing
[17:27] <elfy> just a thought 
[17:27] <elfy> I know we have links etc 
[17:27] <knome> yeah, it's just about writing stuff and then publishing
[17:28] <knome> you can prepare articles yourself, people on ~xubuntu-web can help with publishing
[17:28] <knome> making everything a bit more readable is what the update is supposed to do
[17:28] <knome> http://xstaging.lallinaho.fi/ is the staging site where i test various things
[17:28] <elfy> ok - that's good - I'm happy to look at writing things QA related that we can put there
[17:29] <knome> that still lacks various updates, but hey, it's something ;)
[17:29] <elfy> I just want to try and get QA/testing a bit more front of house than it is somehow
[17:29] <knome> yep, i understand that
[17:29] <elfy> wanted to get the conversation started 
[17:30] <knome> so basically, just login to the site via wp-admin/
[17:30] <knome> start a new article
[17:30] <knome> and poke me (or others in ~xubuntu-web) when you are somewhat ready to get that out
[17:30] <elfy> ok - that's enough for the moment then - thanks knome :)
[17:30] <knome> then we can prepare for publishing
[17:30] <elfy> ok - thanks :)
[17:30] <knome> when we publish news, we always push them to social media
[17:31] <knome> so that gets covered as well
[17:31] <elfy> right - wasn't sure of the way we did these things 
[17:31] <knome> a lot of it is done by me and pleia2 some way or another, depending how much publicity we need
[17:32] <elfy> I understand that - I'll try not to bore you both with excessive demands :p
[17:33] <knome> no, that's fine
[17:33] <knome> as long as somebody else prepares the articles, i'm fine with pushing whatever
[17:33] <elfy> :) you can wander off now then 
[17:33] <knome> hehe :)
[17:34] <knome> ok, have fun and catch you later
[17:34] <elfy> yep - proactive :)
[18:03] <ochosi> brainwash: btw, did you ask around on #systemd?
[18:05] <brainwash> ochosi: yea, but no activity in that channel
[18:05] <ochosi> mkay
[18:06] <ochosi> brainwash: have you tried to edit the policy, then logout and then use the restart-menuitem?
[18:07] <ochosi> i mean, does it even restart or does it ask for an admin pwd or anything?
[18:07] <brainwash> ochosi: of course, changed it and everything works like expected
[18:07] <ochosi> ok, thanks, will discuss the course of action with bluesabre once he's around
[18:09] <ochosi> and anyway, we'll have to test whether it also works if we just tweak the greeter, without touching the policy
[18:11] <brainwash> yes, it almost looks like lightdm-gtk-greeter is the only app relying on these policies
[18:12] <brainwash> oh nice, the session logout delay is getting fixed
[18:17] <ochosi> darn, it can't be fixed just in the greeter
[18:18] <brainwash> lightdm
[18:18] <ochosi> not really either
[18:19] <ochosi> i really have to check what they do in indicator-session... :s
[18:20] <brainwash> but lightdm evaluates the state of logind and its policies
[18:20] <ochosi> right, but it returns the policy correctly
[18:20] <ochosi> it'd be weird to break that
[18:20] <brainwash> yea, dirty workaround
[18:21] <ochosi> dirty dirty
[18:21] <brainwash> and maybe even risky
[18:22] <brainwash> nice, just installed ubuntu-desktop without recommended packages and unity appears to be broken
[18:22] <brainwash> (installed every desktop environment except kde)
[18:30] <brainwash> ochosi: poettering │ brainwash: well, is this logind on ubuntu? please talk to them, we don't support that upstream
[18:30] <ochosi> oh, the great poettering himself...
[18:31] <ochosi> but what does that mean?
[18:31] <ochosi> and also: the same thing happens on archlinux
[18:31] <ochosi> what did you ask him exactly?
[18:32] <brainwash> "why do the logind policy rules for "power-off-multiple-sessions" and "reboot-multiple-sessions" differ? and why does logind think that multiple sessions are running after logging out completely?"
[18:32] <brainwash> + bug report link
[18:32] <ochosi> ok cool
[18:33] <brainwash> are you in that channel also?
[18:33] <ochosi> yup
[18:33] <ochosi> just joined later than you asked
[18:33] <brainwash> ok, you can do the talk now
[18:34] <ochosi> we'll see...
[18:37] <brainwash> http://cgit.freedesktop.org/systemd/systemd/commit/?id=299404a19f26aa4f203042d8285ee0b7afa5bf40
[18:37] <brainwash> ^ !!!
[18:37] <ochosi> :)
[18:37] <brainwash> success
[18:38] <ochosi> ok, wanna link to the commit in the bugreport?
[18:38] <ochosi> after all you figured it out
[18:38] <ochosi> (now we "only" have to find out who's responsible for pk on ubuntu and get in touch with them)
[18:38] <brainwash> how can I do it properly?
[18:39] <brainwash> no, the policy file is shipped with system
[18:39] <brainwash> systemd
[18:40] <brainwash> so we need to backport this commit =S
[18:41]  * ochosi starts chatting up mdeslaur
[18:44] <brainwash> added a comment about the fix
[18:44] <ochosi> great, thanks!
[18:45] <ochosi> am already in touch with the systemd maintainer
[18:48] <ochosi> mdeslaur$ ochosi: ok, give me 10 minutes, and I'll upload a fix
[18:48] <ochosi> brainwash: ^
[18:49] <brainwash> suddenly everything goes super fast :D
[18:49] <ochosi> haha
[18:49] <ochosi> indeed
[18:49] <ochosi> well done brainwash 
[18:49] <ochosi> o/
[18:50] <brainwash> hooray
[18:50] <ochosi> (that's an attempt to high5 you.. ;))
[18:50] <brainwash> o/
[18:50] <ochosi> \o
[18:51] <Unit193> o/\o
[18:51] <ochosi> and there i was, thinking that we wouldn't get this fixed for 13.10 a few minutes ago
[18:51] <ochosi> thanks Unit193 for highlighting the concept (:
[18:51] <brainwash> that means more time to fix the abiword ruler :P
[18:52] <ochosi> oh that...
[18:52] <ochosi> yeah, i started reading the source, not very much fun as it's cpp and cross-platform
[18:53] <ochosi> but i'm on it, is what i'm saying, i guess
[18:53] <brainwash> the 10 people on this planet who actually use abiword and xubuntu will be very grateful :)
[18:54] <ochosi> abiword+xubuntu+greybird|bluebird
[18:54] <ochosi> if they use albatross or numix, it works
[18:55] <brainwash> isn't numix the black theme?
[18:55] <ochosi> it's darkish yeah
[18:55] <ochosi> dark menubar
[18:56] <brainwash> and the border around the document is black too, but the ruler is visible?
[18:56] <ochosi> no, it's all fine
[18:56] <ochosi> you have to switch theme first, and then start abiword
[18:56] <ochosi> gtk3 apps need restarts after theme-changes
[18:56] <ochosi> maybe that'll get fixed at some point
[18:57] <brainwash> ok, I'll test it on my test machine
[18:57] <ochosi> <cool
[19:11] <brainwash> yes, confirmed
[19:12] <brainwash> xfsettingsd stopped working (partially) due to installing all these desktop environments side by side
[19:14] <brainwash> and numix looks nice
[19:15] <brainwash> overall I mean
[19:17] <ochosi> yup, which is why we included it by default
[19:18] <ochosi> and i love that you can easily change the red to e.g. greybird's blue by using gtk-theme-config
[20:08] <ochosi> hmpf, even after reading the abiword source and getting a diff of the commit that supposedly fixed the colors in the rulers and page-background, i still don't know why it's not working...
[20:09] <brainwash> :(
[20:10] <brainwash> did you enable proposed? you should test the systemd fix
[20:10] <ochosi> cause judging from the code alone, it should work
[20:10] <ochosi> yeah, i'm about to test it, just updated the packages
[20:10] <pleia2> I need to run out for a couple hours, looks like our announcement is pretty much prepped (thanks knome!) and just need to hit publish on zee blog when it's out
[20:10] <ochosi> brb
[20:11]  * pleia2 wanders toward the bay
[20:14] <ochosi> brainwash: yup, works as expected
[20:30] <brainwash> ochosi: great, regarding the stupid abiword ruler, did you figure out why numix and greybird behave differently?
[20:30] <ochosi> nope
[20:30] <ochosi> no idea
[20:31] <ochosi> we (as in: satya and me) both compared the codebases of the themes and didn't find anything
[20:31] <ochosi> so not sure really what's going on there
[20:32] <brainwash> too bad I don't know much about css
[20:32] <brainwash> I could only test it with trial&error
[20:34] <ochosi> well as things stand, that's all we can do as well
[20:34] <ochosi> knowing css doesn't help much if you have no clue what to look for
[20:39] <brainwash> actually not worth the time, low priority bug
[20:40] <brainwash> workaround: use numix
[20:41] <brainwash> I fell in love with numix (and unity and unity-tweak-tool)
[20:41] <ochosi> well thing is that it's a default app with our default theme...
[20:42] <ochosi> but yeah, i'll leave it for a rainy day
[20:42] <ochosi> night everyone!
[20:42] <brainwash> good night
[20:49] <ali1234> brainwash: systemd fix? you mean upstart right?
[20:49] <brainwash> systemd/logind
[20:50] <brainwash> bug 1226509
[20:50] <brainwash> ah yes, james hunt also fixed the upstart delay thingy
[20:50] <brainwash> bug 1227212
[20:51] <ali1234> yeah there's a patch, dunno if it is available anywhere built
[20:53] <brainwash> I'm fine without the "benefits" of upstart user sessions, so I leave it disabled :P
[20:53] <ali1234> i prefer an orderly shutdown
[20:54] <ali1234> when i shutdown it is usually a last resort anyway
[20:55] <brainwash> now with the pending fix things should work normally again I hope
[22:07] <brainwash> abiword ruler mystery [solved]
[22:08] <brainwash> wasn't even that hard to find the "buggy" style element
[22:24] <brainwash> ochosi: http://lpaste.net/93462
[22:33] <brainwash> any thoughts regarding this issue bug 1221809 ?
[22:35] <brainwash> it might affected people who somehow removed systemd-shim and upgrade from 13.04 to 13.10 
[22:36] <brainwash> should be a rare case I guess
[23:16] <ali1234> ochosi: the abiword rulers are too dark with orion as well. probably the same thing
[23:33] <knome> pleia2, see -offtopic, "release" if you wish :)
[23:33] <knome> ->
[23:33] <pleia2> I'm awake for a long time
[23:33] <pleia2> only 4:30 pm here :)
[23:34] <pleia2> I don't mind waiting until all the dust settles everywhere
[23:34] <brainwash> ali1234: yes, see https://bugs.launchpad.net/ubuntu/+source/shimmer-themes/+bug/1031137/comments/5
[23:35] <brainwash> ali1234: did you test my fix for greybird?
[23:35] <ali1234> no but i looked at it and i don't understand why it fixes it
[23:35] <ali1234> the gradient should evaluate to almost exactly the same
[23:36] <ali1234> maybe the widget doesn't support background-image?
[23:37] <brainwash> I have no clue.. just did some trial&error debugging
[23:42] <brainwash> suspending for a longer time frame seems to cause some unexpected behavior on my laptop, logind won't permit any operation (suspend, reboot, shutdown) after successfully resuming
[23:43] <brainwash> maybe anyone else can confirm this