[07:34] <ochosi> brainwash: woot
[07:36] <ochosi> holy smokes, but why?
[07:39] <ochosi> btw, it's sufficient to add a background-color, you can leave the background-image set as it is
[08:10] <ochosi> anyway, pushed the fix to bluebird, greybird and orion
[08:32] <ochosi> the weird thing is that the background-color should be inherited by that widget anyway, but it seems the weird way abiword creates a testwidget to get the themecolors involves an entry
[08:32] <knome> hoi
[08:32] <ochosi> and it only gets the background-color attribute, not the -image
[08:32] <ochosi> it's a bit silly but tbh i don't care about abiword enough to investigate this to the bottom
[08:33] <ochosi> hoi knome 
[08:33] <ochosi> knome: so the first three known issues of b2 have fixes in the pipe
[08:33] <knome> nice
[08:34] <ochosi> i mean 1,2 and 4
[08:34] <ochosi> indicator-plugin is still in limbo, i assume
[08:34] <knome> heh
[08:36] <Noskcaj> ochosi, Someone needs to find a way to get micah to finish packaging that. 
[08:37] <ochosi> well he doesn't seem to be around much atm
[09:01] <brainwash> ochosi: o/
[09:01] <ochosi> hey
[09:02] <brainwash> we need to push that fix
[09:02] <brainwash> :P
[09:04] <ochosi> i wanna try and get it in in one upload with the greeter fix
[09:05] <brainwash> ok
[09:09] <brainwash> ochosi: any idea regarding bug 1221809 ? we both were affected after upgrading from 13.04 to 13.10
[09:09] <ochosi> well it needs to be set as a depend
[09:10] <ochosi> but we'd need to talk to either mr_pouit or micahg about this issue
[09:10] <knome> depend to what?
[09:10] <brainwash> consolekit was set as recommended, and recommended packages don't get pulled in when upgrading, or?
[09:10] <knome> they normally do
[09:11] <knome> but if you have uninstalled before upgrading, they don't
[09:11] <knome> or if you use --no-install-recommends (or something else to make that setting permanent)
[09:11] <brainwash> yes, this is the case, people might have removed "systemd-shim"
[09:12] <brainwash> but adding to the list of recommended packages might be still a good idea
[09:13] <knome> should be added to depends, so people can't remove that.
[09:13] <brainwash> (just checking all my bookmarked launchpad report, and this one is still open without confirmation from a maintainer)
[09:14] <brainwash> reports
[09:33] <knome> b2 is out, published announcement and tweeted
[09:33] <knome> pleia2, 
[10:21] <brainwash> added the upstream bug report to bug 1229486
[10:28] <brainwash> I think this issue has been around since forever
[10:30] <ochosi> we might be able to get rid of that with light-locker in 14.04
[10:30] <ochosi> because it locks before suspend by default
[10:32] <brainwash> ochosi: remember when I asked you about this when talking about light-locker weeks ago? it did bother me that light-locker wasn't able to lock the session immediately after suspend :)
[10:33] <ochosi> yeah, true
[10:33] <ochosi> but it listens to the signals
[10:33] <ochosi> so not that much more we can do about it
[10:33] <ochosi> unless it gets better integration into powermanager or session
[10:34] <brainwash> so question might be, why does the execution of xflock4 get delayed in some cases? hardware-specific?
[10:35] <brainwash> the suspend process can differ alot, also the needed time to fully suspend
[10:36] <ochosi> i think that the session would have to handle it
[10:36] <brainwash> the session calls xflock4
[10:36] <ochosi> but the question is, can the session still execute things like suspend after it is locked
[10:37] <ochosi> i really don't know enough about sessions
[10:37] <ochosi> but as ubuntu plans to integrate light-locker by default we can see how they handle it ;)
[10:37] <brainwash> damn vt switching =S
[10:38] <ochosi> yeah, we'll also see about that
[10:38] <ochosi> that used to be the blocker for light-locker
[10:38] <ochosi> or for something like light-locker
[10:38] <ochosi> ofc no-one likes the flickering
[10:39] <brainwash> I can't use slock or i3lock in saucy, because it tends to corrupt the screen (xorg) after unlocking
[10:39] <brainwash> so I'm using gnome-screensaver now
[10:41] <brainwash> I'll check the xfce4-session source code, maybe there is something which could be improved
[10:44] <baizon> hi, just wanted to mention http://xubuntu.org/news/saucy-salamander-b2/ , link  https://wiki.ubuntu.com/SaucySalamander/Beta2/Xubuntu got a wrong url
[10:44] <baizon> it has: https://wiki.ubuntu.com/SaucySalamander/Beta2/Xubuntu?action=edit&editor=text
[10:44] <baizon> but i think it should be : https://wiki.ubuntu.com/SaucySalamander/Beta2/Xubuntu
[10:44] <baizon> when i click on the link i get: "You are not allowed to edit this page. "
[10:51] <ochosi> baizon: thanks, fixed!
[10:59] <ochosi> brainwash: fix for bug #1227735 pushed to git
[11:25] <brainwash> ochosi: context menu [ok], abiword ruler [ok]
[11:26] <brainwash> the xfce4 settings daemon is causing some trouble on my test system
[11:27] <brainwash> can anyone confirm, that xfce4-terminal crashes when you navigate to Menu bar > Terminal > Set Encoding ?
[11:28] <brainwash> it does on both installations here
[11:29] <ali1234> yes, it crashed
[11:35] <brainwash> can you upload the apport report? don't feel like enabling apport anytime soon
[11:37] <ali1234> i have non-standard packages installed so it won't let me
[11:38] <ali1234> launchpad will just mark it invalid
[11:39] <ali1234> it is already reported
[11:39] <ali1234> https://bugs.launchpad.net/ubuntu/+source/xfce4-terminal/+bug/1206739
[11:42] <brainwash> yes
[11:43] <brainwash> unable to connect to ibus
[11:44] <brainwash> I enabled apport, but the terminal did not trigger it
[11:47] <brainwash> ibus-ui-gtk3 did trigger apport (gtk3 indicator I guess)
[11:47] <ali1234> this may be related to the keyboard indicator not working
[11:48] <brainwash> right
[11:48] <brainwash> this gtk2/gtk3 transition did break much stuff
[11:52] <brainwash> bug 1224496
[12:04] <ochosi> brainwash: yeah, i can confirm that too
[12:04] <ochosi> bbl
[13:06] <ToZ> anyone know why pm-utils is not installed by default on 13.10? 
[13:25] <brainwash> ToZ: nice find, strange indeed
[13:25] <brainwash> http://cdimage.ubuntu.com/xubuntu/releases/saucy/beta-2/xubuntu-13.10-beta2-desktop-amd64.manifest
[13:26] <GridCube> its there any test needed?
[13:27] <ToZ> brainwash, installing it fixes bugs 1229486 & 1229478 that I noticed during testing.
[13:30] <brainwash> ToZ: no clue, why xubuntu is the only spin not shipping pm-utils anymore
[13:31] <brainwash> maybe a dependency for it needs to be added (xubuntu-desktop)
[13:38] <brainwash> ToZ: "System does successfully suspend when lid closed or "sudo pm-suspend"."
[13:39] <brainwash> so pm-suspend was not missing?
[13:43] <ToZ> pm-suspend was missing, yes
[13:44] <ToZ> oops, I'll correct that in the report.
[13:45] <brainwash> I suggest filing a bug report against xubuntu-meta and requesting pm-utils to be included by default
[13:47] <ToZ> Interesting. "sudo pm-suspend" doesn't lock the screen. Suspend from the menu or lid close does.
[13:48] <brainwash> kinda expected I guess
[13:48] <ToZ> why?
[13:49] <brainwash> xfce4-screensaver does not detect suspend/resume and will not lock the screen automatically
[13:49] <ToZ> "xubuntu-meta" does not exist? Can't file bug report.
[13:49] <brainwash> gnome-screensaver on the other hand is able to
[13:49] <knome> that'd be xscreensaver
[13:50] <brainwash> yea
[13:50] <knome> we're about to make changes to the locking on 14.04, i don't think we will dig too deep in this with 13.10
[13:50] <brainwash> xscreensaver
[13:50] <brainwash> https://bugs.launchpad.net/ubuntu/+source/xubuntu-meta
[13:51] <brainwash> knome: getting a bit confused by the terminology :D
[13:51] <knome> that happens
[13:53] <ToZ> https://bugs.launchpad.net/ubuntu/+source/xubuntu-meta/+bug/1232027
[13:55] <brainwash> knome: can you triage the bug report and assign a priority please?
[14:01] <knome> done.
[14:02] <brainwash> thanks
[14:04] <brainwash> knome: could also add bug 1206739 to the list of known beta bugs please?
[14:04] <knome> brainwash, i don't think that's critical enough
[14:04] <knome> that happens, but there are many more crashes
[14:05] <brainwash> but the terminal geeks will be sad :/
[14:05] <GridCube>  its there any test i could to today?
[14:05] <knome> brainwash, we can't list everybody xubuntu has, can we?
[14:05] <knome> *every bug
[14:05] <knome> GridCube, well, b2 is released but you can always test the daily
[14:05] <brainwash> knome: yea, we better don't do that :)
[14:07] <knome> besides, b2 is released, that's already missing :P
[14:08] <knome> can't keep on adding new bugs
[15:58] <pleia2> knome: thanks g+ed too (and it x-posted to fb as expected, yay)
[16:30] <knome> :)
[16:38] <pleia2> happy beta2 day for real
[16:41] <knome> you too
[16:52] <knome> off
[16:53] <knome> see you later
[17:00] <pleia2> enjoy
[18:00] <brainwash> ochosi: remember that we talked about the appfinder showing up with a noticeable delay? I told you that it shows up instantly on my test system, now few days later I can confirm this issue
[18:01] <elfy> I can confirm that it's still immediate here :)
[18:02] <brainwash> yes, on my main system it's still instant
[18:10] <brainwash> bug 1048805
[18:10] <brainwash> the last 2 comments are amazing
[18:12] <olbi> hello all :D
[18:21] <brainwash> elfy: just curious, do you run xubuntu saucy on a laptop/notebook?
[18:22] <elfy> brainwash: not in general 
[18:23] <elfy> I use a laptop to test iso's mostly
[18:23] <elfy> hi olbi 
[18:28] <pleia2> hmm, i think it's time to formally upgrade my laptop
[18:31] <olbi> pleia2: which Xubuntu do you have on laptop?
[18:31] <pleia2> olbi: I have 13.04 on 2 laptops and 2 desktops, 12.04 on my netbook
[18:32] <pleia2> going to upgrade non-work laptop to 13.10 today
[18:32] <olbi> I think that 13.10 isn't stable yet :)
[18:33] <olbi> I have sometimes crash with USC :P
[18:33] <elfy> use it to install synaptic ... :p
[18:35] <pleia2> olbi: if you're not already, can you submit bug reports for issues you find so we can tackle them before release?
[18:35] <pleia2> we depend on folks like you using it to catch things :)
[18:35] <baizon> elfy: then a question. I have a strange behavior... while my laptop shuts down, if i close him the system gets into suspend instead of finishing the shutdown process. You have the same behavior maybe?
[18:36] <olbi> hmm, I gave it :)
[18:36] <baizon> not sure if only me is affected
[18:36] <elfy> baizon: I can check that 
[18:37] <baizon> thank you
[18:39] <olbi> https://bugs.launchpad.net/ubuntu/+source/software-center/+bug/1230123
[18:40] <olbi> and the most annoying is that sound menu :P
[18:40] <elfy> olbi: the sound notification issue? 
[18:41] <olbi> yes
[18:41] <baizon> olbi: there is a simple workaround
[18:41] <olbi> I have found temporary fix at launchpad and it's working
[18:42] <elfy> baizon: ok - what I am seeing is this - Shutdown, close lid, open lid, press power button - shutdown not finished but interrrupted, finishes shutdown
[18:43] <baizon> elfy: yes so its a bug
[18:43] <elfy> seems so 
[18:44] <elfy> baizon:  you going to report it ? 
[18:44] <baizon> no, will do in a sec
[18:44] <elfy> ok - let me know and I'll me too it
[18:44] <brainwash> shutdown takes 1 sec on my main system, not much time to actually close the lid that fast
[18:44] <elfy> :)
[18:45] <baizon> brainwash: some for me
[18:45] <olbi> hmm, which files are responsible for translation items from Settings Manager?
[18:45] <baizon> but when i "click" log out, i close the lid and it can happen then
[18:46] <brainwash> logout?
[18:46] <brainwash> weren't we talking about shutdoen? :)
[18:46] <elfy> we were 
[18:50] <brainwash> I noticed some strange behavior when suspending for a longer time frame, after resuming the session won't let me perform actions like reboot/shutdown/.. and the network manager remains in an idle state (deactivated)
[18:52] <brainwash> hard to tell if it is a reproducible issue, or some race condition occurring after resume
[18:52] <baizon> brainwash: i ment the log out dialog
[18:53] <brainwash> you open the dialog, hit the shutdown button and close the lid?
[18:54] <baizon> brainwash: yes
[18:55] <elfy> I'm not sure it suspends so much as interrupts the shutdown 
[18:55] <elfy> because opening the lid and hitting the power button just lets the shutdown continue
[18:58] <elfy> like this one 
[18:58] <elfy> https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/138194
[18:59] <baizon> elfy: well it is the same bug
[19:00] <elfy> baizon: yea - seems to be an old hanging one then
[19:00] <baizon> but this bug didn't occur on my 13.04 system
[19:01] <baizon> wait a sec
[19:01] <elfy> well I can't comment on that as I never reaqlly use the laptop for long enough to notice 
[19:03] <baizon> ok, so the problem is, i set my laptop to do nothing when i close the lid but it gets into suspend
[19:05] <elfy> https://bugs.launchpad.net/bugs/1232103
[19:05] <elfy> that's on AC
[19:16] <baizon> ok got a fix/workaround
[19:19] <baizon> elfy: posted it
[19:20] <elfy> number?
[19:20] <knome> elfy, see same bug
[19:21] <elfy> oh right
[19:25] <baizon> ok, the only bug i have is that my sessions are getting saved
[19:32] <brainwash> once again some systemd shenanigans
[19:36] <brainwash> however, I start to like systemd :)
[19:39] <brainwash> elfy: can you share the link to the xubuntu developer pad please?
[19:41] <elfy> brainwash: which one - I've got a bunch of them
[19:42] <brainwash> the interactive pad
[19:42] <elfy> you mean an empty one?
[19:42] <brainwash> no, the xubuntu beta one
[19:43] <elfy> http://pad.ubuntu.com/Xubuntu1310Beta2Release
[19:43] <elfy> brainwash: I've got loads of different xubuntu ones kicking about :)
[19:43] <brainwash> elfy: thanks :)
[19:52] <knome> we're not following the beta one too much any more, maybe you should start another one with the bugs if you want to have some kind of list
[19:56] <brainwash> so no plans to continue this sort of bug tracking?
[19:56] <knome> that depends
[19:57] <knome> the critical bugs should be listed in the blueprints
[19:57] <knome> the rest... people who work on them should keep a track of them (and that's easily done when you're the assignee on LP=
[19:57] <knome> )
[19:57] <knome> there are ways to find all the bugs reported via the iso tracker to xubuntu from LP
[19:58] <knome> the launchpad advanced search is really powerful
[19:58] <knome> if people explain and argument why tracking bugs elsewhere is better and it makes sense, then let's do it
[19:59] <knome> elfy, any arguments for doing something else than LP tracking since we last talked? ^
[19:59] <elfy> none - once I could see how to do it 
[20:00] <elfy> and that it worked
[20:01] <knome> i suppose ultimately, even if you wanted to do some manual tracking, the easiest way is keep tagging stuff
[20:01] <elfy> yep
[20:01] <knome> xubuntu-1310 or so
[20:01] <knome> then just filter out the bugs with those tags
[20:01] <elfy> worth thinking about perhaps - but it'll need to be a proper system for tags
[20:01] <brainwash> https://blueprints.launchpad.net/ubuntu/+spec/xubuntu-s-development
[20:02] <elfy> no good each of us using different tags 
[20:02] <brainwash> this one here?
[20:02] <knome> i don't know about the thinking; the purpose should make it obvious what the tag should be
[20:02] <knome> brainwash, that's the blueprint.
[20:02] <knome> elfy, you have the iso-tracker filtered bugs around handy or should i recreate that?
[20:02] <elfy> knome: I agree - but if we've a bunch of people all thinking this makes sense 
[20:03] <knome> heh, sure
[20:03] <elfy> 2 secs
[20:03] <elfy> http://tinyurl.com/qzxv9t7
[20:05] <elfy> knome: that list? 
[20:05] <knome> yep
[20:05] <knome> brainwash, ^ that's the bugs from iso testing
[20:06] <Noskcaj> knome, Did you ever get time to look at the new debian release of xfwm4? It's a (rather important) doc fix
[20:06] <brainwash> knome: ok, thanks :)
[20:07] <knome> Noskcaj, as i said back then, i'm fine with getting them both in, but somebody needs to take care of that, and thought you would be up for it
[20:07] <Noskcaj> knome, I was waiting for micahg and mr_pouit to reply. I've already made the sync bug, i'll make a branch today
[20:08] <elfy> brainwash: pads are great for collaborative stuff - but without the link they're no good to anyone else :)
[20:08] <knome> Noskcaj, as i also said back then, you shouldn't count on them doing the work
[20:08] <knome> Noskcaj, thanks for taking care
[20:08] <Noskcaj> ok
[20:08] <Noskcaj> no problem
[20:10] <Noskcaj> looks like i've got a kernal upgrade to do first
[20:24] <olbi> Xubuntu will have Linux 3.10 or we go for 3.11 in plans?
[20:38] <Noskcaj> olbi, I've just had 3.11 installed, but that might be from proposed
[20:39] <olbi> me too have 3.11 :D
[20:39] <olbi> after upgrading :)
[20:39] <olbi> no proposal repo
[20:39] <elfy> I've had 3.11 for ages
[20:39] <brainwash> ^ since forever
[20:40] <elfy> well - I've told you a million times ;)
[20:40] <brainwash> 3.2, 3.5, 3.8, 3.11
[20:47] <olbi> https://01.org/linuxgraphics/downloads/2013/2013q3-intel-graphics-stack-release - yuppi :D
[20:47] <olbi> I will check it soon :)
[21:23] <ochosi> brainwash: hm, meh, not good...
[21:24] <brainwash> ochosi: after fixing some bugs new ones appear out of nowhere :/
[21:24] <brainwash> never ending cycle
[21:25] <ochosi> yeah
[21:25] <ochosi> this cycle is quite unstable (again)
[21:26] <brainwash> yea, mainly due to the systemd/logind and gtk3 transition
[21:26] <brainwash> gtk3 indicators
[21:29] <ochosi> well the gtk3 indicators have been coming ournway a few releases now
[21:30] <ochosi> it's just getting gradually worse
[21:31] <brainwash> the Xfce team isn't making any noticeable progress with gtk3
[21:33] <brainwash> and glib 2.37 is causing some trouble too
[21:34] <ochosi> aha.
[21:34] <ochosi> ?
[21:34] <brainwash> bug 1206739
[21:34] <ochosi> (thatdot should've been a question mark)
[21:35] <ochosi> ah, that's a glib bug? didnt get a chance to read the report after confirming it
[21:35] <brainwash> I'm trying to debug this one, but gdb crashes
[21:35] <ochosi> is it reported upstream too?
[21:35] <brainwash> did not check yet
[21:36] <brainwash> maybe ubuntu specific
[21:36] <ochosi> :/
[21:38] <brainwash> I'm trying to fix another pending bug.. sadly I might lack some knowledge about debugging properly
[21:45] <ochosi> what other vug.
[21:45] <brainwash> what?
[21:45] <ochosi> (ipad keyboard fail..)
[21:46] <ochosi> what other bug?
[21:47] <brainwash> oh, my mistake
[21:47] <brainwash> s/fix/find
[21:47] <ochosi> haha
[21:47] <brainwash> most of my bookmarked bug reports are closed now
[21:48] <ochosi> poor you! :)
[21:49] <brainwash> got any bug reports you could need help with?
[21:57] <ochosi> well there are a few things we wanna fix in the greeter
[21:58] <ochosi> e.g. when the userlist is disabled, make 'enter' go to the password field
[21:58] <ochosi> also, possibly add alt+f4 for the shutdown dialog
[21:58] <ochosi> and improve kb support in that dialog too
[21:59] <ochosi> and always set a default button
[21:59] <brainwash> sounds interesting
[21:59] <ochosi> (btw, really awesome work so far, thanks for all your contributions,)
[22:00] <ochosi> s/,/!/
[22:00] <brainwash> (glad I could help a bit)
[22:00] <brainwash> :D
[22:00] <ochosi> :)
[22:01] <brainwash> I guess I'll put the greeter on my todo list, to test and try things, basically to learn how everything works
[22:02] <ochosi> sweet
[22:02] <brainwash> and the greeter isn't that complex either
[22:02] <ochosi> yup
[22:03] <brainwash> but first I'll try to debug the terminal encoding menu thingy :)
[22:03] <ochosi> cool :)
[23:00] <brainwash> there is a nice discussion about pm-utils over at #ubuntu-devel
[23:01] <brainwash> don't miss it :)