[01:31] <starrats> Don't know if this is a 'bug report' or not but I'm still experiencing a 'lock-out on login/password screen after a major update/upgrade when it rerquests a re-start to complete the action.
[01:32] <bluesabre> Unit193... it works O.O
[01:32] <Unit193> bluesabre: Of course it does, I'm better than Logan_. ;)
[01:33] <bluesabre> lol
[01:33] <Unit193> (Hah, juuust kidding, he wins.)
[01:33] <bluesabre> what did you change? :)
[01:34] <Unit193> I was on the right track, just wrong change.  dpkg-buildflags uses -Wl,-Bsymbolic-functions in Ubuntu but not Debian, so in the rules file I exported LDFLAGS=-Wl,-z,relro and rebuilt.  (Spotted it in the diff he linked to.)
[01:34] <bluesabre> aha
[01:34] <Unit193> (Note, that may not be the proper change, but it's a test at least.)
[01:35] <bluesabre> if it works, its better than what we have now ;)
[01:35] <Unit193> Now, I need to bookmark that site, because that's a nice diff tool.
[01:36] <bluesabre> well, if we are happy with it, I can toss it into a PPA and request some testing
[01:37] <Logan_> Unit193: I figured it had something to do with that
[01:37] <Unit193> bluesabre: See? ^  Already knew.
[01:37] <bluesabre> :)
[01:39] <Unit193> http://paste.openstack.org/show/75380 This is what I used.
[01:41] <Unit193> Logan_: Another oddity, the libdrm include.
[01:43] <Logan_> Unit193: that's because it's a B-D of something else in Debian but not in Ubuntu
[01:44] <Unit193> Yes, but adding the dep didn't include it, not even sure it's needed for anything.
[01:46] <Unit193> bluesabre: Is there a need to test it?
[01:47] <bluesabre> I don't think so
[01:47] <bluesabre> I mean, it works :D
[01:48] <bluesabre> I'll make a branch with that and poke Logan_ to merge it ;)
[01:49] <Logan_> sure :)
[01:49] <Unit193> Is this something we can push to Corsac? :/
[01:49]  * Unit193 liked that parole would sync.
[01:50] <bluesabre> we can try
[01:58] <bluesabre> done, poked Corsac
[01:59] <bluesabre> and put the ball in Unit193's court
[01:59] <Unit193> Hah, like I know anything. :P
[01:59] <bluesabre> :D
[01:59] <bluesabre> more than I do in this instance
[01:59] <Unit193> So, I'm done with the parole thing right?  I don't need to do anything else with it since you seem to have it from here?
[02:00] <bluesabre> most likely
[02:00] <bluesabre> I might poke/ping you two more times
[02:02] <starrats> should i file a bug report?
[02:03] <bluesabre> hey starrats
[02:04] <bluesabre> what do you mean by that 'lock-out'?
[02:05] <bluesabre> brb, rebooting my server to fix ssl
[02:05] <starrats> well my cursor is free but when I try to put in my password it won't let me just a flashing line then goes solid
[02:10] <bluesabre> starrats, that sounds odd
[02:11] <bluesabre> go ahead and file a bug, we'll look into it
[02:11] <starrats> okay
[02:12] <starrats> I know it's odd and only happens after a large update/upgrade session on term
[06:29] <jhenke> good morning
[06:47] <brainwash> ochosi: did you test the new xfpm upload?
[06:49] <Noskcaj> Can someone please propose https://code.launchpad.net/~noskcaj/ubuntu/trusty/xfdesktop4/4.11.6 for merging?
[06:49] <Noskcaj> My launchpad won't log in
[06:50] <brainwash> lp broken?
[06:50] <brainwash> Invalid OpenID transaction
[06:51] <Noskcaj> yep
[06:56] <brainwash> now it worked
[07:11] <elfy> brainwash: no inviscursor on this - can't help with that one ... 
[07:11] <brainwash> but you are a black screen expert :)
[07:12] <brainwash> I've uploaded power-manager + ochosi's test patch
[07:13] <elfy> ok - when I'm on a real install I will look at that then :)
[07:13] <brainwash> but he claimed that it's somewhat broken, because suspend via power-amaner stopped working for him
[07:14] <elfy> ok - well I'm all up for breaking it if at all possible :D
[07:14] <brainwash> so I've rebuilt and re-uploaded the same thing
[07:15] <elfy> lol
[07:17] <Noskcaj> Unit193, That patch for parole could end rather badly
[07:17] <Noskcaj> since you broke hardening, and the various existing flags
[07:18] <brainwash> did he reveal the patch? :)
[07:19] <Unit193> Noskcaj: That's kind of the point, "breaking" existing flags.
[07:20] <Noskcaj> ok. because relro is on anyway.
[07:20] <Unit193> Did you check?  Is hardening disabled?
[07:21] <Noskcaj> Unit193, I didn't check, i'm just looking at your patch
[07:21] <Noskcaj> And pretty much repeating what corsac said
[07:22] <Unit193> ...He hasn't said anything.  Also, I did kind of say this was good enough to test, but beyond that...
[07:23] <Noskcaj> Unit193, https://bugzilla.xfce.org/show_bug.cgi?id=9904#c10
[07:24] <Unit193> Right, he missed that it's trying to disable a default flag, I think.  But yes, I was hoping for a better way to disable it.
[07:26] <Noskcaj> ok
[07:40] <Unit193> Is indicator-messages broken with the latest update?
[08:37] <elfy> brainwash ochosi : installed xfpm from brainwash's ppa, still black screen where it was failing yesterday
[09:31] <brainwash> elfy: I assume that you've restarted xfpm before doing the test run, right?
[09:36] <elfy> machine had been out of xubuntu and into windows and out again
[09:46] <bluesabre> Unit193: want to proceed on that?
[09:46] <bluesabre> ;)
[09:47] <Unit193> Not quite, still waiting for a better way. :/
[09:49] <bluesabre> :(
[10:03] <Unit193> bluesabre: Could try to push it anyway, can't think of a better way.
[10:04] <bluesabre> want to comment on the bug? Corsac is pretty stubborn about his packages and I really don't "get" what's going on
[10:05]  * Unit193 wonders if bluesabre, the upstream, can fix it so it compiles with -Bsymbolic-functions :P
[10:06]  * bluesabre wouldn't even know where to start
[10:08] <Unit193> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=570617
[10:11] <Unit193> bluesabre: Does https://lists.ubuntu.com/archives/ubuntu-devel/2008-May/025367.html help you at all?
[10:13] <bluesabre> O.o
[10:13] <bluesabre> I think weak symbols is how parole's plugin system is designed
[10:14] <bluesabre> yeah
[10:15] <bluesabre> it creates a plugin instance
[10:15] <bluesabre> then drops in the plugins functionality, overriding the previously defined methods
[10:16] <Unit193> That's weird, but alright.
[10:16] <bluesabre> I didn't design it
[10:16] <bluesabre> if it were up to me, I'd use totem's python plugin system
[10:16]  * Unit193 blames bluesabre for not changing it. :P
[10:16] <bluesabre> and I suppose it is
[10:16] <Unit193> Eww, python. :P
[10:16] <bluesabre> but thats a lot of work
[10:16] <Unit193> bluesabre: Read about pyston?
[10:17] <bluesabre> nope
[10:17] <Unit193> (Also, think I came up with something I like out of a test env.  Trying it now.)
[10:17] <bluesabre> wait a sec
[10:18] <bluesabre> pyston is a new thing
[10:18] <bluesabre> yet they target python 2.7
[10:18] <bluesabre> kill me
[10:18] <bluesabre> kill -9 1
[10:18] <Unit193> killall5 ?
[10:19] <bluesabre> oh, but its being developed by the dropbox folks
[10:19] <bluesabre> so thats a good thing
[10:22] <Unit193> bluesabre: Fixed it in a way I'd feel OK pushing to the Archive and to Corsac. :)
[10:22] <bluesabre> oh
[10:24] <Unit193> bluesabre: http://paste.openstack.org/show/v1RMkdv0fJ8JNCU6i3Yk/ push that to Log an?
[10:25] <bluesabre> I'll ping Corsac with the new version :)
[10:25] <Unit193> Okay.
[10:37] <bluesabre> sound reasonable?
[10:37] <bluesabre> So, with the above rules, -Bsymbolic-functions flag is removed as it breaks parole.
[10:37] <bluesabre> Referring to this write-up, https://lists.ubuntu.com/archives/ubuntu-devel/2008-May/025367.html
[10:37] <bluesabre> Rewriting Parole's plugin architecture would be a huge undertaking.  Parole relies on weak symbols to initialize a plugin.  Here, a base plugin's interface is overridden by the actual plugin's functionality. the -Bsymbolic-functions flag completely breaks that. Adding this protection to the packaging ensures that plugins will continue to build correctly even when default build flags are altered (as they are in Ubuntu).
[10:38] <brainwash> Noskcaj: finally xfdesktop4 4.11.6, thanks!
[10:39] <brainwash> you can close bug 1302101 then
[10:39] <bluesabre> brainwash, Noskcaj: huzzah! :)
[10:39] <Unit193> bluesabre: As long as it's helpful to link to that, sure.
[10:39] <bluesabre> it is for me
[10:40] <bluesabre> that helped me understand the source of the issue
[10:40] <Unit193> Great!  Glad I could be helpful. :)
[10:40] <bluesabre> and why it never happens when building normally
[10:40] <Unit193> Also, see x-dev?
[10:45] <brainwash> elfy: looks like we need a different approach to fix this, I've uploaded xfpm + another patch which tweaks the timings when triggering the lock screen
[10:46] <Unit193> brainwash: Status of xfce4-indicator-plugin and indicator-service-start event?
[10:46] <brainwash> waiting to be merged, bluesabre prepared the branch
[10:47] <brainwash> https://code.launchpad.net/~smd-seandavis/ubuntu/trusty/xfce4-indicator-plugin/upstart-init
[10:48] <brainwash> instead of hardcoding it, we could use an upstart job to start the indicator services
[10:49] <brainwash> but our current solution works fine too
[10:56] <bluesabre> Unit193: <Corsac> also, would it not be possible to remove the linker flag from the build systems itself, so it gets removed only for plugins, not for the whole stuff (or would it need to be removed for the main binary, actually?)
[10:56] <bluesabre> I'm thinking no, but how would something like that be done from the d/rules?
[11:06] <brainwash> wow, so many uploads (thunar, xfdesktop4, xfwm4)
[11:08] <Unit193> bluesabre: That'd be somehow in the makefile, no?
[11:09] <Unit193> http://paste.openstack.org/show/sy6gQIx34EWDeXxJe3Ds works for me.
[11:19] <Unit193> Upstart job does make sense, unless you don't use a user session (can you do this?)
[11:30] <bluesabre> if yes, dunno where or how :)
[11:32] <bluesabre> I'll check it out tonight
[11:32] <bluesabre> RC tomorrow, let me know if there is anything I need to focus my efforts on next
[11:32] <bluesabre> bbl
[12:20] <ochosi> brainwash: sorry, no testing for me until maybe next week, i'll be mostly afk
[12:25] <brainwash> ochosi: ok :/
[13:28] <RFleming> Good day!
[13:33] <RFleming> Quick question.  Lately it seems when I apply updates, I'm losing my wallpaper and am left with plain grey
[13:34] <RFleming> I'm using the default 14.04 xubuntu-wallpaper
[13:38] <starrats> RFleming this is also happening to me but i have imported a few photos to be my wallpaper. 
[13:38] <elfy> RFleming: fix is in pipeline
[13:39] <starrats> so I need not to add to my bug report on this elfy?
[13:39] <elfy> me too existing bugs where they exist please
[13:40] <RFleming> elfy, what's the bug #?
[13:40]  * RFleming REALLY needs to learn how to use launchpad
[13:41] <starrats> I filed a bug report last night per bluesabres request on my problem and the plain gray screen is part of that, just forgot to add it in the comment section of the report
[13:41] <RFleming> elfy, starrats I've been using the lack of a background as a 'notice' to reboot :)
[13:43] <brainwash> please install the latest updates
[13:45] <starrats> brainwash who?
[13:46] <brainwash> both of you
[13:46] <starrats> ok
[13:46] <brainwash> after doing so and relogging once bug 1302101 should be fixed
[13:51] <starrats> updaste is finished for me, but when i run upgrade right after update that's when my screen will turn 'dirty white' and then i get locked out from logging back in and it takes afew times 
[13:51] <starrats> to get bak on
[13:52] <starrats> that is the bug report i filed last night
[13:52] <elfy> I think that you have got serious issues if you still have this being locked out issue
[13:52] <starrats> this is of course after i re-started my comp from running those two in term.
[13:53] <starrats> my cursor is 'free' now so i don't know
[13:53] <starrats> this morning I got on te first time so i think there's another issue elfy
[13:55] <brainwash> Logan_: hey, are you in the mood to prepare yet another bugfix release?
[13:58] <brainwash> Logan_: if yes, please take a look at https://bugs.launchpad.net/ubuntu/+source/abiword/+bugs?orderby=-id&start=0 - we got 3 patches for abiword
[13:59] <elfy> hi brainwash 
[14:00] <brainwash> hey elfy :)
[14:00] <elfy> not sure where we got to with this suspend thing - to recap, I upgraded to your ppa version - logged out - no difference with lid close
[14:01] <brainwash> apt-cache policy xfce4-power-manager?
[14:01] <brainwash> which version
[14:01] <elfy> you want me to turn it on again lol
[14:02]  * elfy wanted to debug with a guessing game today :D
[14:02] <brainwash> check your apt-get history then
[14:03] <elfy> 1.2.0-3ubuntu4
[14:03] <brainwash> ok, thanks
[14:03] <elfy> it's not this machine :) this is like yours - no lid ;)
[14:04] <starrats> just finished my upgrade and the screen went dirty white half way through the upgrade.  
[14:04] <mzr1> a laptop....with no lid....*mind blown*...
[14:04] <elfy> starrats: yes it will - just do it and then logout/in and it will be fixed
[14:05] <starrats> ok
[14:05] <brainwash> desktop pc
[14:05] <brainwash> :D
[14:05] <starrats> why though elfy does it do that?
[14:05] <starrats> tell me after I log back in
[14:06] <elfy> brainwash: afaik that's the one from your ppa
[14:13] <xnox> so the debian splash is comming from usr/share/wallpapers/joy_inksplat/contents/screenshot.png
[14:13] <brainwash> it's the fallback option, or?
[14:13] <xnox> where is the desired background?
[14:14] <xnox> (on the cd)
[14:14] <Logan_> brainwash: I'll take a look at abiword later today
[14:16] <xnox> found it in /usr/share/xfce4/backdrops
[14:16] <brainwash> Logan_: thanks :)
[14:17] <brainwash> xnox: installed by the package xubuntu-artwork
[14:20] <brainwash> xnox: did http://bazaar.launchpad.net/~ubuntu-installer/ubiquity/trunk/revision/6044 break it?
[14:31] <xnox> brainwash: elfy: who/what/where paints the background on a full xubuntu session these days?
[14:32] <xnox> the debian swoosh is painted by unity-settings-daemon, which doesn't have any key set and it looks like in inherited schemas from debian they do paint backgrounds with gnome-settings-daemon (or at least synchronise the settings there)
[14:33] <xnox> if there is a xubuntu gsettings schemas overrides package we could fix it there
[14:33] <elfy> xnox: I'm not sure tbh
[14:33] <xnox> alternatively we should be loading the desktop wallpaper natively, i thought xsettingsd should do it
[14:33] <brainwash> xnox: there is, in xubuntu-default-settings
[14:33] <xnox> but it only loads up a black screen.
[14:35] <brainwash> http://bazaar.launchpad.net/~xubuntu-dev/xubuntu-default-settings/trunk/files/head:/debian/
[14:35] <xnox> thanks looking.
[14:39] <brainwash> xnox: so I guess all flavors which don't use gsettings to specify the background should be affected by this problem, or?
[14:39] <xnox> elfy: brainwash: the "background" override pointing at debian image is comming from desktop-base package which seems to be xfce4 dependency
[14:39] <xnox> previously there was no unity-settings-daemon nor gnome-settings-daemon on the xubuntu images, and thus something Xfcish painted the background.
[14:43] <brainwash> sounds rather confusing
[14:44] <brainwash> so overriding the background value won't help in this case?
[14:45] <xnox> so i've launched xfce4-settings-manager and it shows that my background is correct - e.g. the mouse picture
[14:45] <xnox> yet my background is black
[14:45] <xnox> how come?
[14:45] <brainwash> in a normal session?
[14:46] <xnox> no, ubiquity
[14:46] <brainwash> xfdesktop4 usually paints the desktop background
[14:47] <brainwash> does "xfdesktop --reload" restore the background?
[14:49] <xnox> brainwash: that works, but i get icons on the desktop =))))
[14:49] <brainwash> that means that xfdesktop4 isn't being used in the first place
[14:49] <xnox> any key i can set to disable icons?
[14:50] <brainwash> will this affect the live session?
[14:51] <xnox> no, i'll revert the key
[14:51] <brainwash> http://bazaar.launchpad.net/~xubuntu-dev/xubuntu-default-settings/trunk/view/head:/etc/xdg/xdg-xubuntu/xfce4/xfconf/xfce-perchannel-xml/xfce4-desktop.xml
[14:51] <brainwash> this is the config file for xfdesktop4
[14:52] <brainwash> now it's getting really confusing :)
[14:54] <brainwash> and what about lubuntu and co? shouldn't there be solution which works for every flavor?
[14:54] <brainwash> sadly I'm not familiar with ubiquity at all
[14:54] <xnox> well it used be gnome-settings-daemon that painting the background. let's tinker further.
[14:56] <brainwash> what about something simple like feh or hsetroot?
[14:56] <xnox> oh, there is xsetroot codepath and feh codepaths but i don't want to use them =)
[14:56] <xnox> i'd rather drop them.
[14:56] <xnox> let me see.
[14:58] <brainwash> anything that works would be fine.  we don't want to ship a LTS release and confuse the user with a debian background :)
[15:09] <elfy> indicator-messages appears to have taken a hit like indicator-sound did
[15:11] <brainwash> it disappeared?
[15:15] <elfy> yep - after the recent update/grade - deactivated in autostart apps
[15:16] <brainwash> kinda expected change
[15:16] <elfy> because?
[15:17] <elfy> I thought we were using -messages?
[15:18] <brainwash> we do, but the autostart launchers for the different indicators have been or will be changed
[15:19] <brainwash> https://code.launchpad.net/~smd-seandavis/ubuntu/trusty/xfce4-indicator-plugin/upstart-init/+merge/214713
[15:19] <brainwash> ^
[15:21] <brainwash> xnox: the init process does not exit immediately, we need to save the PID to kill it on logout
[15:22] <brainwash> initially we called the init process twice (copy&paste failure), this resulted in an init process still running after logout and there keeping the session alive
[15:22] <brainwash> therefore
[15:23] <brainwash> btw lightdm-gtk-greeter and unity-greeter do it the same way
[15:25] <xnox> brainwash: i'm not involved in that at all.
[15:25] <xnox> brainwash: i dislike starting indicators via upstart user session only. Imho they should have stayed dbus-activatable.
[15:25] <brainwash> xnox: indeed :(
[15:25] <brainwash> but we need to fix this now asap
[15:26] <xnox> brainwash: also I'm Dimitri and I'm not Dmitry Shachnev (mitya57)  =)
[15:26] <brainwash> xnox: oh... my fault, sorry
[15:26] <brainwash> got it mixed up
[15:26] <xnox> figured as much =)
[15:27] <brainwash> really stressful days before the final release :D
[15:32] <elfy> and we still have to finallyt decide to throw ibus out today 
[16:12] <brainwash> xnox: wow, you've already uploaded x-d-s 14.04.4, thanks a lot :)
[16:14] <brainwash> ochosi: maybe we should migrate <control> to <primary> before release, see bug 1299637
[17:26] <elfy> knome: so it's i-day - my vote is remove ibus 
[17:33]  * starrats is not a happy camper at this moment, when Trusty tahr is released on the 17th, next week, I will be burning a new image and do a total install hoping all is fixed
[17:41] <Pwnna> are we fixing that issue with no screen after login anytime soon? i like lightlocker and wish to reenable it
[17:43] <elfy> what bug number is that?
[17:44] <elfy> Pwnna: you mean the black screen after suspend one?
[17:48] <Pwnna> yeah
[17:48] <Pwnna> power manager doesn't get power.
[17:48] <Pwnna> elfy: that one
[17:49] <Pwnna> it's an upstream one
[17:49] <elfy> if it's the same one as the one we've spent hours on lately - do you get the issue if you suspend from menu? 
[17:50] <elfy> I can only replicate it as suspend with lid close 
[17:59] <brainwash> can anyone please re-enable the xfce4-power-manager try icon (settings manager > power manager > show icon always) and then suspend the system via the new tray icon?
[17:59] <brainwash> someone who can reproduce the black screen issue
[18:02] <brainwash> elfy: I've noticed that if you set the keyboard layout manually (e.g. setxkbmap de) and then start ibus-daemon, ibus will pick the correct kb layout just fine
[18:02] <brainwash> so a workaround is possible
[18:03] <elfy> brainwash: that's as maybe - there are other workarounds possible - at the moment though we cannot use it and it just work 
[18:03] <elfy> my vote won't be changing ;)
[18:03] <elfy> if it's fixed by .1 then I don't mind it being put back
[18:04] <brainwash> we read the system layout config and re-set it via setxkbmap on an early stage of the session startup
[18:05] <brainwash> sadly it is a bit late for experiments
[18:06] <brainwash> but a workaround seems to be possible, maybe even a proper solution with this information in minde
[18:06] <brainwash> mind
[18:06] <elfy> suspend from tray icon works fine here 
[18:06] <elfy> bbl
[18:23] <brainwash> elfy: I've installed light-locker on my main system (13.10) and suspend via lid close managed by xfpm works fine here
[18:28] <elfy> ok 
[18:33] <brainwash> elfy: can you check light-locker-settings please
[18:35] <brainwash> is "automatically lock the session" set to "... is deactivated"?
[18:36] <elfy> auto lock session is set to never
[18:37] <brainwash> ok
[18:39] <brainwash> time to watch soccer, cya :)
[18:39] <elfy> cya 
[20:20] <ochosi> ali1234: comments on the comment from mitya on https://code.launchpad.net/~smd-seandavis/ubuntu/trusty/xfce4-indicator-plugin/upstart-init/+merge/214713 ?
[20:20] <Unit193> ochosi: You see the upstart job I created this morning?
[20:20] <ochosi> sry, no, was busy/away all day
[20:20] <ochosi> only have a few minutes now, then i have to run off again
[20:21] <ochosi> so you wanna fix this outside the plugin?
[20:21] <Unit193> That was the idea brainwash had, I just tried it and it's not bad.
[20:22] <ochosi> the downside is that then indicators get started no matter what
[20:22] <ochosi> so if you don't have the plugin in the panel, the services still start
[20:22] <ochosi> that's a bit meh
[20:22] <ochosi> and that was the main reason i seconded the inclusion of the job in the plugin
[20:30] <Unit193> Also, no, it doesn't quit.
[20:30] <ochosi> yeah
[20:30] <ochosi> we'd have to patch xfce4-session to send that signal
[20:30] <ochosi> so meh, let's stick with the plugin solution for now
[20:31] <ochosi> unless you guys come up with another solution that is nicer
[20:36] <Unit193> "You guys" :P
[20:40] <brainwash> you can write a better upstart job
[20:40] <brainwash> not such a basic one
[20:40] <brainwash> but there is no need for it :)
[20:41] <ali1234> bluesabre: i just spotted a bug in the indicator patch...
[20:41] <ochosi> oh, good that it hasn't been uploaded then
[20:42] <ali1234> it's a trivial bug that won't actually affect anything
[20:42] <ochosi> still time to update the merge-request
[20:42] <ali1234> i will fix the error message too
[20:42] <ochosi> well there are also those comments about storing PID and error message
[20:42] <ochosi> so we can amend the patch
[20:42] <ali1234> libupstart is a bit of a big change this close to release
[20:42] <ali1234> storing the pid is a requirement
[20:42] <ochosi> yeah, i think they're aware of that
[20:42] <Unit193> ochosi: But, he's wrong on that point as it doesn't exit.
[20:42] <ali1234> yeah ^
[20:43] <ochosi> right, i didn't read the comment very closely, tbh
[20:43] <Unit193> Also, anyone else getting resolvconf failing to write any nameserver in /etc/resolv.conf and just blanking it? ;/
[20:43] <ochosi> mostly wanted to forward it to ali1234 as i wasn't sure whether he's subscribed to it
[20:44] <ochosi> Unit193: what was the result on parole btw?
[20:44] <ochosi> only saw some backlog, but not enough time to read it all
[20:44] <Unit193> ochosi: Uhh, I made it so I like the change now, I don't see why it can't be uploaded.
[20:45] <ochosi> that sounds good
[20:45] <Unit193> http://paste.openstack.org/show/9bRq11DcdahwuW5A7pJv/ something like that (drop the prefixed space.)
[20:45] <ochosi> bbl
[20:56] <Unit193> Logan_: Ready for upload: http://paste.openstack.org/show/CA7tPtWrKXWZ5txofePk or https://sigma.unit193.net/source/parole_0.6.1-0ubuntu2.dsc depending on what you like.
[20:59] <Logan_> Unit193: tarball plz
[20:59] <Logan_> meh, I guess it's okay
[20:59] <Unit193> It's there, dget should find it fine...
[21:04] <Unit193> Anything else needed?
[21:06] <Logan_> Unit193: no, not at the moment
[21:06] <Logan_> although, do you know why it works?
[21:07] <Unit193> Yes.
[21:07] <Unit193> https://bugzilla.xfce.org/show_bug.cgi?id=9904#c12  And, \o/
[21:12] <Logan_> ah, I see
[21:15]  * Unit193 seemingly actually knows something, even if he doesn't use parole at all. :D
[21:37] <Logan_> Unit193: uploaded
[21:37] <Logan_> thanks for your help, Unit :)
[21:39] <Unit193> Logan_: Thanks for all your help!
[21:39] <Logan_> yup, no problem
[21:39] <Logan_> I should really study for this exam ugh
[21:39] <Logan_> #collegeproblems
[21:39] <Unit193> Hah, before it hits #ohcrapnotthattimeagain. :P
[21:40] <Logan_> yup :/
[21:40] <Logan_> I'm thinking of improving my description on Launchpad
[21:40] <Logan_> but then again no
[22:01] <Noskcaj>  Logan_ once you give up studying, can you look at lp:~noskcaj/ubuntu/trusty/xfce4-xkb-plugin/lp-733563  ?
[22:12] <knome> can agree with elfy; we should probably drop ibus and reintroduce it for .1 if it seems to make any sense (eg. the bug is fixed and there are actually people who are bothered by it not being installed)
[22:22] <ochosi> knome: +1
[22:22] <ochosi> thanks a lot for the fix Unit193 
[22:22] <ochosi> and thanks for uploading, Logan_ 
[22:23] <knome> if we want to dig a bit deeper, we could talk with somebody who actually uses ibus with xubuntu
[22:24] <knome> and ask them how big inconvenience it would be to have to install ibus
[22:24] <ochosi> yeah, i guess those ppl will get in touch with us anyhow if ibus isn't there anymore :)
[22:24] <knome> we don't even seed any languages that would need ibus to input, i guess
[22:27] <ochosi> does the whole section "input methods" go?
[22:27] <ochosi> http://bazaar.launchpad.net/~xubuntu-dev/ubuntu-seeds/xubuntu.trusty/view/head:/desktop#L30
[22:27] <ochosi> i mean is im-config good for anything without ibus?
[22:28] <ochosi> oh right, seems unrelated
[22:28] <ochosi> so only the ibus stuff would go
[22:30] <brainwash> let it go, let it go!
[22:38] <brainwash> ochosi: I've installed light-locker on 13.10 and suspend via lid close managed by xfpm works fine for me
[22:38] <ochosi> hm, is that good news?
[22:38] <ochosi> sorry that i have to take off again
[22:39] <brainwash> dunno
[22:48] <Unit193> ochosi: Sure thing, glad I could help.
[22:48] <knome> thanks Unit193 
[22:48] <ochosi> Unit193: since you've tampered with seed files before, in case you wanna take a look at the desktop-seed merge i proposed...
[22:49] <ochosi> just to be sure
[22:49] <ochosi> thanks and night!
[22:49] <Unit193> Sure, but not right now.  Checked to see what depends on it?
[22:49] <ochosi> nope, that's exactly why i'm asking others to review it ;)
[22:50] <ochosi> (because i wouldn't have thought of that, not because i didn't want to do the work)
[23:59] <bluesabre> ali1234: would you say its worthy of a separate merge?
[23:59] <bluesabre> or has mine been merged yet
[23:59]  * bluesabre needs to get his ideas in order