[14:52] <cornfeedhobo> hellloooo
[14:52] <cornfeedhobo> i am using AWS + centos 7. could someone tell me why this snippet, pretty much stolen straight from the docs, is not executing? https://gist.github.com/cornfeedhobo/35d60eca0a09ec4bbfb94a957d7520ff
[14:54] <smoser> cornfeedhobo, could you paste /var/log/cloud-init.log and /var/log/cloud-init-output.log if there is anythign interesting there.
[14:56] <utlemming> cornfeedhobo: for CentOS? likely a dependency problem. I don't think CentOS includes growpart and sfdisk by default (I reserve the right to be wrong here...)
[14:57] <cornfeedhobo> smoser: coming up
[14:57] <cornfeedhobo> utlemming: interesting point
[14:57] <cornfeedhobo> (i'll double check that too)
[15:00] <cornfeedhobo> smoser: gist updated
[15:00] <utlemming> cornfeedhobo: how about a dump of 'journalctl' too?
[15:01] <smoser> well thats pretty useless
[15:01] <utlemming> centos is a bit dense when it comes to logging on disk for Cloud-init, sadly
[15:01] <smoser> normally cloud-init.log shoudl have debug level output, which is quite noisy
[15:02] <utlemming> you'd think so...but on CentOS/RH/Fedora, there is a packaging issue where the logs are supposed to be owned by 'adm' (as in Debian/Ubuntu) but the user is not created
[15:02] <utlemming> the result is cloud-init.log is there, but empty
[15:04] <cornfeedhobo> oh yeah, journalctl output is really verbose. updated again.
[15:06] <cornfeedhobo> i'm going through it all now, hadn't thought to check journal.
[15:06] <utlemming> cornfeedhobo: how about /etc/cloud/cloud.cfg? and /etc/cloud/cloud.cfg.d/*
[15:06] <utlemming> looks like its not configured to setup the disks
[15:06] <cornfeedhobo> yeah, i can paste those, but fwiw, this is just the stock AMI for centos7 ... oh interesting. incoming.
[15:10] <cornfeedhobo> okay. updated. .d/* only has a logging cfg, but pasted
[15:11] <utlemming> cornfeedhobo: yup, that's the problem...the default config doesn't setup disks
[15:13] <smoser> cornfeedhobo, you should be able to run (and i'd be interested in the output of)
[15:13] <cornfeedhobo> ah, i saw growpart and mounts and assumed
[15:13] <smoser> sudo cloud-init single --debug --name=disk_setup --frequency=always
[15:13] <smoser> er... maybe --debug before single
[15:13] <cornfeedhobo> okay, let me make sure that module is on disk
[15:14] <utlemming> cornfeedhobo: I just confirmed that the default config doesn't include that
[15:14] <smoser> it'll be there. just disable.d
[15:14] <utlemming> I would argue that this should be a bug in CentOS
[15:15] <cornfeedhobo> hmmm, i cant find the modules folder on disk
[15:16] <cornfeedhobo> sorry, i'm super new to cloud init
[15:16] <cornfeedhobo> repoquery to the rescue, maybe
[15:17] <cornfeedhobo> okay. testing.
[15:18] <cornfeedhobo> https://gist.github.com/cornfeedhobo/64bcf6e2b760af27ddf16889b9849686
[15:19] <cornfeedhobo> it doesn't seem to be loading it, but i see the python module in site-packages
[15:22] <smoser> cornfeedhobo, look in /var/log/cloud-init.log see if you see
[15:22] <smoser>   Running module disk_setup
[15:25] <cornfeedhobo> okay. one sec. question first: is there a way to specify, in my aws userdata, that i want to add fs
[15:25] <cornfeedhobo> fs_setup module to cloud_config_modules  **
[15:26] <cornfeedhobo> from what i can tell, if i add a cloud_config_modules section, it overrides the one in cloud.cfg
[15:28] <utlemming> cornfeedhobo: my $0.02 ZWD....copy /etc/cloud/cloud.cfg to /etc/cloud/cloud.cfg.d/99-me.cfg and add "- disk-setup" to the modules section
[15:31] <cornfeedhobo> hmm, but that means i would have to create a custom AMI with that copied file in place, or kick off cloud-init again, after aws has executed it?
[15:38] <utlemming> cornfeedhobo: there are other ways to convince cloud-init....
[15:40] <cornfeedhobo> well, question: does cloud-init re-process the yaml files between init, config, and final?
[15:42] <smoser> cornfeedhobo, yes.
[15:42] <smoser> so you can feed that list in as user-data
[15:42] <smoser> but it really should have run when you ran it with single there.
[15:43] <cornfeedhobo> hmmm
[15:45] <smoser> i might have to resort to littering /usr/lib/python3/dist-packages/cloudinit/config/cc_disk_setup.py with LOG.info or LOG.warn messages
[15:47] <cornfeedhobo> maybe AWS invokes with more flags? something that pulls from http://<IP_ADDRESS>/latest/user-data ?
[15:51] <cornfeedhobo> no, i dont see anythnig special in the service files
[15:51] <cornfeedhobo> i'm going to retry with utlemming's $0.02, utilizing bootcmd
[15:59] <cornfeedhobo> muhahahahaha, it worked
[15:59] <cornfeedhobo> sed 's@cloud_config_modules:@cloud_config_modules:\n - disk-setup@' -i /etc/cloud/cloud.cfg
[16:00] <cornfeedhobo> is fs_setup wrapped up in disk-setup?
[16:08] <smoser> cornfeedhobo, the module name is 'disk_setup' (or disk-setup). that handles both top level config entries 'disk_setup' and 'fs_setup'
[16:09] <cornfeedhobo> that is what i thought, especially after looking at the modules in site-packages. hmmm, i must just have an error in the fs_setup i just tried. i'm going to look around some logs
[16:19] <cornfeedhobo> ah, interesting. "Unable to convert swap to a device"
[16:28] <smoser> powersj, https://code.launchpad.net/~powersj/cloud-init/+git/cloud-init/+merge/320994
[16:29] <powersj> smoser: sup
[16:29] <smoser> can you tell me why i dont want to just pull that ? and why is the bug referenced there (1669306) ?
[16:30] <powersj> 1) I need to update source and remove source-branch those are pointing at my branch (that was me testing it and forgetting to change it back
[16:30] <smoser> yeah. just saw that and pushed a coment
[16:30] <powersj> 2) the LP is a refrence to "command: usr/bin/python3 $SNAP/bin/cloud-init" which is not the normal line
[16:30] <powersj> it should have been as simple as command: cloud-init
[16:31] <powersj> but there are some python3 issues with classic confined snaps documented in that LP I refrence
[16:31] <powersj> reference*
[16:32] <powersj> smoser: oh and do you want the source to be the master git url or to be '.'
[16:33] <powersj> pointing at master i.e. https://git.launchpad.net/cloud-init made sense, but wanted to confirm
[16:33] <smoser> powersj, id ont know what do you think ?
[16:34] <smoser> what is the "right snap" way to do it.
[16:34] <smoser> i had this general question once looking at snaps
[16:35] <powersj> smoser: well if we use '.' we don't checkout cloud-init yet again, however if you use '.' you can try snapping local changes. As far as convention, I didn't feel there was overarching best practice from what I saw.
[16:35] <powersj> I do like using the git master URL though as it prevents you from doing something silly like making a local change and then having that make it somewhere
[16:37] <smoser> well, you can pick one. and we can figure out why it was wrong later ;)
[16:38] <powersj> hahaha
[16:40] <powersj> smoser: updated with the URL
[16:44] <cornfeedhobo> okay, got that sorted out. thanks for the help smoser & utlemming!!
[17:17] <smoser> powersj, https://code.launchpad.net/~powersj/cloud-init/+git/cloud-init/+merge/322137 how can i see the pylint warings ?
[17:18] <powersj> smoser: edit the .pylint rc
[17:18] <smoser> i jsut removed it.
[17:19] <smoser> and i dont see anyting
[17:19] <powersj> that works too ;) but you may get even more messages
[17:21] <smoser> sure. but i dont see ones, like if i run 'pylint tools/mock-meta' i see a buch of errors, but nothing about the log.warning
[17:21] <smoser> oh. now id o
[17:23] <powersj> did you change something?
[17:24] <smoser> just wasnt looking right
[18:11] <devicenull> hey, we've started to run into issues with this change https://lists.ubuntu.com/archives/ubuntu-devel/2017-February/039697.html
[18:11] <devicenull> basically, we used to use cloud-init, and dropped it ~4-6 months ago
[18:11] <devicenull> however, a bunch of our customers had created OS images back when we used it
[18:11] <devicenull> and now they're starting to run into error messages when they boot up from those images
[18:11] <devicenull> and I don't really see any way for us to address that, given that the images already exist
[18:11] <devicenull> backporting that to 16.04 seems like an issue
[18:14] <devicenull> I'm guessing we'll probably resort to pretending to be ec2 if this ends up becoming a bigger issue
[18:15] <nacc> if you stopped using cloud-init 4-6 months ago, how woudl a change in cloud-init from 2 months ago be affecting your images?
[18:15] <nacc> devicenull: --^
[18:15] <devicenull> customers still have images with cloud-init built in
[18:15] <rharper> I think they're old images which still have cloud-init inside them
[18:15] <devicenull> and that's getting updated (automatically?), which then triggers the message on next boot
[18:15] <devicenull> correct
[18:16] <rharper> sure, a dist-upgrade would update the cloud-init in them
[18:16] <nacc> ah i thought they weren't able to boot the image
[18:16] <nacc> so i wasn't sure how cloud-init was updating
[18:16] <rharper> well, they're getting the warning
[18:16] <rharper> it's bootable in xenial
[18:16] <nacc> rharper: oh i see
[18:17] <nacc> i read 'error message' as fatal
[18:17] <devicenull> yea, we've only had a couple reports of it so far, so I'm not sure how big of a problem it's going to turn into
[18:17] <rharper> the error message should include the cloud-config that the user can emit in to the image to disable the warning and the check
[18:17] <rharper> it can also be a boot parameter
[18:18] <devicenull> yea, it throws this https://gist.githubusercontent.com/devicenull/63f96ecf5a84c0c9163c09002726d204/raw/b4d0f508382fe4de9a33e5eaf19e7ac92fed8e23/gistfile1.txt
[18:18] <devicenull> which then they end up reporting to us
[18:18] <rharper> ack
[18:21] <devicenull> we've just been telling them to remove cloud-init, but I thought I'd bring this up here
[18:22] <rharper> thanks for reporting;   if possible filing a bug for the issue with the details requested w.r.t the provide; that might help users find that it's been reported
[18:23] <devicenull> yea, we'll probably add some documentation on it too
[18:23] <rharper> we could also in there point back to you're recommendation that best fits the cloud;  alternatively we could explore whether you could expose an identifier (ideall through SMBIOS settings )
[18:26] <devicenull> I'm not sure you really want to be adding code detecting us, when we really don't use cloud-init anymore?
[18:29] <rharper> possibly not; I suppose it may depend on the customer images


[10:46] <yellabs> hello all you good folks
[10:46] <yellabs> any news around the topic ubuntu dash and privacy ?
[11:01] <yellabs> http://www.jonobacon.org/2012/12/10/on-being-childish-an-apology/


[00:00] <bdmurray> ddstreet: in the meantime can we unsubscribe sponsors? or should we just upload it and leave it in -proposed for them?
[00:16] <mwhudson> vorlon: so for https://bugs.launchpad.net/ubuntu/+source/rustc/+bug/1943842 how important is it that the new packages are co-installable?
[00:17] <mwhudson> one of the packages that needs backporting is libarchive and the SONAME is the same in the version i want to backport
[00:17] <mwhudson> do i make it install to some private directory?
[00:26] <vorlon> mwhudson: coinstallable> not at all important
[00:28] <mwhudson> oh good
[01:34] <ItzSwirlz> bdmurray: about the cinnamon thing there isn't even a branch version for JJ, so why are we all talking about it now?
[01:35] <ItzSwirlz> if you argue "well now it's fixed in JJ" then you could argue that since cinnamon 5.0 was uploaded to unstable in debian but anyways, Impish is affected and when JJ opens I'll template up
[02:38] <bdmurray> ItzSwirlz: I thought since nothing else pressing was going on it would be a good time to look at the sponsorship queue and try and get some of it addressed
[02:39] <bdmurray> ItzSwirlz: You don't really need to wait for JJ to open but do as you wish
[20:40] <ItzSwirlz> ok
[20:40] <ItzSwirlz> thanks, gonna get to work (#1919026)
[21:15] <ItzSwirlz> bdmurray: Done


[18:03] <mdeslaur> FYI, security team meeting cancelled because of US holiday
[18:05] <chrisccoulson> slackers
[18:05] <chrisccoulson> :)
[18:07] <mdeslaur> chrisccoulson: I'm all alone :)
[18:17] <zul> mdeslaur: im here to keep you company
[18:18] <mdeslaur> hehe
[21:00] <cjwatson> well, I'm here for TB having belatedly noticed it; dunno if anyone else is
[21:01] <cjwatson> I know it's a US holiday
[21:02] <cjwatson> not much on the agenda though
[21:02] <MrChrisDruif> I'm not aware if the Technical Board meeting will proceed as usual. Also in Europe it's a holiday
[21:03] <soren_> o/
[21:03] <cjwatson> there was nothing on the TB list indicating cancellation
[21:03] <cjwatson> MrChrisDruif: only parts of Europe
[21:04] <soren_> Not Britain?
[21:04] <cjwatson> Not the UK this year, no
[21:04]  * stgraber waves
[21:04] <MrChrisDruif> Holland it's every year
[21:04] <cjwatson> It's moved in the UK this year due to the Queen's diamond jubilee
[21:05] <cjwatson> anyway, just saying, the UK is part of Europe too so generalising holidays is difficult :)
[21:05] <soren> Indeed.
[21:05] <cjwatson> who's chair this week?  agenda is out of date but I infer probably stgraber
[21:05] <cjwatson> unless soren's carried over from last time
[21:06] <stgraber> not sure :)
[21:06] <soren> That'd be three ties in a row :)
[21:06] <soren> This one seems as easy as the last two, though.
[21:06] <stgraber> #startmeeting
[21:06] <meetingology> Meeting started Mon May 28 21:06:18 2012 UTC.  The chair is stgraber. Information about MeetBot at http://wiki.ubuntu.com/meetingology.
[21:06] <meetingology> Available commands: #accept #accepted #action #agree #agreed #chair #commands #endmeeting #endvote #halp #help #idea #info #link #lurk #meetingname #meetingtopic #nick #progress #rejected #replay #restrictlogs #save #startmeeting #subtopic #topic #unchair #undo #unlurk #vote #voters #votesrequired
[21:06] <stgraber> fine :)
[21:06] <stgraber> #topic Action Review
[21:06] <cjwatson> the main thing I see not on the agenda is the Mythbuntu LTS plan
[21:06] <cjwatson> FWIW
[21:07] <stgraber> wiki doesn't list anything, so I guess we're good there?
[21:08] <stgraber> #topic Mythbuntu LTS plan
[21:08] <stgraber> https://lists.ubuntu.com/archives/technical-board/2012-May/001258.html
[21:08] <stgraber> we don't have quorum but I guess we can at least look at it and discuss it
[21:08] <cjwatson> three is quorate
[21:09] <stgraber> oh right, forgot we're just 6
[21:10] <cjwatson> I've just rather belatedly followed up to the list with my thoughts
[21:10] <soren> Yeah, without superm here, I'd rather do e-mail as well.
[21:10] <soren> superm1, I mean.
[21:10] <cjwatson> basically that I can see some possible problems but it seems a reasonable thing to try
[21:10] <cjwatson> https://lists.ubuntu.com/archives/technical-board/2012-May/001277.html
[21:12] <soren> It'll be interesting to see. If it works out well, I wouldn't be surprised if we saw more like this.
[21:12] <cjwatson> I do worry a bit about intermediate bitrot; there is some devil in the detail.
[21:13] <cjwatson> Probably not enough to scupper the idea in the case of Mythbuntu.  A flavour with wider focus might have more difficulty, I feel.
[21:13] <stgraber> if we decide to allow it, we'll need to update https://wiki.ubuntu.com/RecognizedFlavors to reflect this as they'll by definition won't meet the "Must have a proven track record of participating in at least 2 non-LTS releases before applying to TechnicalBoard for LTS designation."
[21:14] <cjwatson> Huh?  Mythbuntu has participated in considerably more than two non-LTS releases.
[21:14] <cjwatson> I don't think it would be a brilliant idea to allow it for entirely new flavours.
[21:14] <cjwatson> Two years is too long a period for any kind of agility in trying out new things.
[21:15] <stgraber> hmm, indeed, reading it again, I didn't interpret this properly ;) For some reason I parsed that as we want them to release two consecutive release prior to an LTS, but that's indeed not what it says :)
[21:17] <cjwatson> No, it was intended as "must not be total newcomers" really
[21:18] <stgraber> right, so should we just continue the discussion with Mario on the mailing-list?
[21:18] <cjwatson> Sounds good.
[21:19] <stgraber> #topic Select a chair for the next meeting
[21:19] <cjwatson> At least he's had a reply now :)
[21:19] <stgraber> cjwatson: so I guess next chair in the list is you?
[21:19] <cjwatson> Yep
[21:19]  * cjwatson checks the calendar
[21:20] <cjwatson> And I believe I'm even around that day
[21:20] <stgraber> #action cjwatson to chair the next TB meeting (11th of June)
[21:20] <meetingology> ACTION: cjwatson to chair the next TB meeting (11th of June)
[21:20] <stgraber> #topic AOB
[21:20] <stgraber> anything?
[21:20] <soren> Not from me.
[21:20] <cjwatson> Nor I
[21:21] <stgraber> alright
[21:21] <stgraber> #endmeeting
[21:21] <meetingology> Meeting ended Mon May 28 21:21:04 2012 UTC.
[21:21] <meetingology> Minutes (wiki):        http://ubottu.com/meetingology/logs/ubuntu-meeting/2012/ubuntu-meeting.2012-05-28-21.06.moin.txt
[21:21] <meetingology> Minutes (html):        http://ubottu.com/meetingology/logs/ubuntu-meeting/2012/ubuntu-meeting.2012-05-28-21.06.html
[21:21] <cjwatson> Thanks
[21:21] <soren> \o/&
[21:21] <stgraber> thanks everyone for attending!


[07:25] <wickedpuppy2> hi , how long before *@ubuntu/member/* nick is unregistered? Is it controlled by Ubuntu IRC Council or Freenode staff?
[07:26] <IdleOne> The Ubuntu IRC Council are who make sure that Ubuntu members get the cloak.
[07:27] <IdleOne> not sure what you mean about unregistered
[07:29] <wickedpuppy2> Freenode FAQ says : We consider IRC nicks expired after they have not been used for 10 weeks plus (at staffer discretion) one additional week per full year of registration, up to a maximum of five additional weeks.
[07:29] <IdleOne> *@ubuntu/member/* isn't a nick
[07:29] <wickedpuppy2> but I am seeing this from the ubuntu/member --> [15:23] -NickServ- Last seen  : Aug 26 07:02:08 2012 (25 weeks, 4 days, 00:21:17 ago)
[07:30] <IdleOne> what nick specifically?
[07:30] <wickedpuppy2> I am awared that it isn't a nick .. I don't want to say whose nick is that thats why .. I am just checking why this particular nick has "last seen" value more than 25 weeks
[07:32] <wickedpuppy2>  I am checking if its Ubuntu IRC Council policy or Freenode policy so I could ask for help from appropriate dept
[07:32] <IdleOne> well without knowing specifically which nick it would be difficult to say. The reason why the nick hasn't been dropped is because nicks don't automatically expire. You need to ask a staff member in #freenode to drop the nick and that is at staff discretion if they want to drop it
[07:33] <wickedpuppy2> I see. Thanks for your advise. Not from Ubuntu side then.
[07:33] <IdleOne> right.
[07:33] <IdleOne> but your question was a little confusing because you mentioned an ubuntu cloak
[07:33] <IdleOne> sneeky is always helpful
[07:35] <IdleOne> I wonder if staff would drop sabdfl for me. 27 weeks since it was last seen
[07:35] <Unit193> Should try it.
[07:35] <IdleOne> lol
[07:36] <IdleOne> I'm pretty sure this is why nicks don't auto expire
[17:14] <hggdh> hello folks -- we can kill the #ayatana-bugs channel, it has been superseeded by the #ubuntu-unity (which carries a bot to show bugs). I have already killed eeeBotu there.
[17:21] <AlanBell> hi hggdh, we can sort that out no problme
[17:22] <hggdh> AlanBell: great, thank you
[22:36] <mainerror> Hello
[22:36] <mainerror> We've got a bit of a situation in #ubuntu-phone
[22:37] <mainerror> There's a user called 'jackel' talking rubbish and spamming the channel.
[22:37] <Myrtti> you are a bit late on the report it seems
[22:37] <mainerror> Just figured.


[12:39] <DaSkreech> is there a link form kdesu -> kdesudo ?
[12:43] <Riddell> no, a dpkg redirect
[12:47] <DaSkreech> so they will be no kdesu?
[12:48] <Riddell> you can run kdesu.distrib or apt-get remove kdesudo
[12:49] <DaSkreech> ok
[12:50] <DaSkreech> Just worried about the hundreds of walkthroughs that say kdesu suddenly having a non working command
[12:51] <Riddell> why would it be non working?
[12:52] <DaSkreech> I thought that kdesudo was replacing kdesu
[12:53] <Riddell> yes, in /usr/bin/kdesu
[12:58] <DaSkreech> ah ok :)
[01:06] <gnomefreak> is there a kde app in repos to remove the DRM for a .wma
[01:11] <DaSkreech> gnomefreak: I don't know there is a windows program for that.
[01:12] <gnomefreak> there is?
[01:23] <DaSkreech> gnomefreak: No I don't think that there is a windows program that does that. the new wmf is pretty well encrypted
[01:25] <gnomefreak> ok ty i have idea run to library take out the cd and use soundjuicer
[03:01] <ryanakca> Riddell: Hmm. When you wake up, mind loging into egroupware and telling me if there's anybody else who needs an account (I've got all the kubuntu-members)? I'm sending you username/pass/etc...
[03:40] <ryanakca> bug 439357
[04:12] <nixternal> what about it?
[04:12] <nixternal> :)
[06:09] <manchicken> Is mvo normally on kubuntu-devel or ubuntu-devel or neither?
[06:10] <ScottK> manchicken: I've seen him on ubuntu-devel and ubuntu-bugs.
[06:10] <manchicken> I don't see him now...
[06:10] <manchicken> I hear he was wanting to do a package manager in Python that would use common code between Kubuntu and Ubuntu.
[06:11] <manchicken> I should probably pick up python sooner or later.
[06:13] <manchicken> Or is Ruby the language that all the cool kids are using for KDE4 stuff?
[10:31] <mhb> hi folks
[10:58] <allee> morning.  Anyone known show to see which 'events' media managers sees?  (Me tries to figure out how to start kdeblueooth when BT stick is inserted)
[11:00] <mhb> hello yet again :o)
[11:03] <allee> hi mhb
[11:03] <Riddell> allee: it listens to hal, kdebase/kioslave/media/mediamanager/halbackend.cpp
[11:03] <allee> Riddell: isn't there a tool to monitor kde's media manager events?
[11:07] <Riddell> allee: you could try asking ervin
[11:10] <allee> ah #solid
[11:10] <allee> Riddell: thx
[11:24] <allee> Riddell: ervin told me that there will be no media-manager events.  So either listen to hal directly or listen to bluez dbus events.   Would be a little autostart script python that waiting in background for device insert/removal be acceptable/makes sense for gutsy?
[11:44] <allee> python-bluez in universe :(
[11:55] <Riddell> allee: that would make sense sure
[11:55] <Riddell> we can get things promoted if they are needed
[11:57] <allee> Riddell: mhm, k.  I've currently looking into dbus-x11 (not installed by default, but in main) if it can be done via scripting too.  Thx for info
[12:05] <gnomefreak> anyone know what " text " in C is? i know */ text /* is comment but not sure what the " are for
[12:06] <allee> Tonio_: kbt autostart on bt insert/remove: ervin told me that there no media manager events for it in KDE3.  So the options are small python-bluez (universe) script autostarted waiting for insert/unplug. Alternatively maybe shell script?;  Listen to hal events (argl ;).  Not sure if I can find more time this weekend.
[12:08] <allee> Tonio_: independently please consider  'Exec=hciconfig | grep -q . && kdeblueooth'  works around disturbing warning when no BT device is available
[12:08] <allee> bye
[12:38] <mhb> today is a bad day for IRC
[12:40] <Hobbsee> mhb: oh?
[12:42] <mhb> Hobbsee: irssi keeps reconnecting all the time (not sure why, it's fine usually) and the fabbione logs are dead, too
[12:42] <Hobbsee> mhb: ahh
[01:36] <vprints> does guidance share code with displayconfig-gtk ?
[02:53] <ris> i hope by release, gutsy is going to decide whether it's going to be blue-green or blue-purple, because hovering on the border or having a mix of the two is quite ugly
[02:53] <ris> case in point - new kdm in tribe5
[02:55] <Riddell> ris: I think artists kwwii is away for the weekend
[02:56] <Riddell> you can discuss it on ubuntu-art mailing list or on irc with him on monday
[02:56] <ris> Riddell: tch, cowboy
[02:57] <vprints> Riddell, does guidance share code with displayconfig-gtk ?
[02:59] <Riddell> vprints: yes displayconfig-gtk uses the guidance backend
[03:01] <vprints> will guidance also get the Home / Office/ ... / settings grouping in gutsy ?
[03:04] <Riddell> vprints: unlikely, it would need someone to work on it
[05:30] <nixternal> Jucato is coming back!!!
[05:31] <nosrednaekim> where was he? I noticed he hasn't been around.
[05:33] <nixternal> he took a little break
[05:41] <nixternal> robotgeek: dude, those transparent screens are cool
[06:13] <tmske> what's the default search program in kubuntu gutsy, tracker or strigi?
[06:14] <ScottK> strigi
[06:14] <ScottK> tracker is a Gnome program for eating up all your CPU time.
[06:14] <tmske> :-)
[06:17] <nixternal> hehe
[06:17] <jjesse> afternoon :)
[06:17] <nixternal> all strigi needs is a nice user friendly ui...other than that, it is pretty good actually
[06:17] <nosrednaekim> excellent observation.....it is afternoon.
[06:17] <nixternal> howdy jjesse
[06:18] <nixternal> not here it isn't
[06:18] <nixternal> still have 40+ minutes :)
[06:18] <jjesse> silly central time zone people
[06:18] <nosrednaekim> yeah,,,
[06:18] <nixternal> Chicago Standard Time!
[06:18] <jjesse> i'm sure that's what it stands for
[06:18] <nixternal> hehe
[06:18] <nixternal> it is now!
[06:22] <nixternal> jjesse: you gonna be helping out on some kde4 doc work?
[06:22] <jjesse> nixternal: sure is there a lot to do?
[06:22] <nixternal> oh ya
[06:22] <nixternal> Phil and I are starting to discuss it a bit and you aren't around which is odd :)
[06:22] <jjesse> nixternal: ok
[06:23] <jjesse> nixternal: i've been swamped w/ work
[06:23] <nosrednaekim> I can help with docs..
[06:23] <jjesse> nosrednaekim: #kde-docs :)
[06:24] <nosrednaekim> ok
[06:31] <tmske> is the kbfx version of kubuntu gutsy compiled with strigi support?
[06:58] <jjesse> so those jerks at dell limit my laptop to 3.2 gig via something in the hardware even though i can purchase 4 gigs of RAM
[07:00] <nixternal> that is cool
[07:01] <jjesse> yeah too bad i bought the extra memory before I new i would never bee able to use it
[07:06] <OculusAquilae> Hi
[07:07] <OculusAquilae> Is anybody working on the backup system Keep?
[07:12] <jjesse> i'm doing some work on the documentation
[07:14] <OculusAquilae> jjesse: of Keep?
[07:16] <jjesse> OculusAquilae: yes
[07:18] <OculusAquilae> jjesse: are you in contact with JRe, I would like to do porting to kde4 and so on
[07:18] <jjesse> OculusAquilae: i posted somethings on the bug in regards to this on kde's bugtracker but haven't had further contact
[07:18] <jjesse> do you have an email address?
[07:19] <OculusAquilae> jjesse: I wrote the the address in the about page
[07:20] <jjesse> about keep page?
[07:20] <OculusAquilae> yes
[07:21] <jjesse> ok i'll contact him
[07:21] <OculusAquilae> I wrote an E-mail already
[07:21] <OculusAquilae> no answer till now
[07:22] <OculusAquilae> jjesse: the web page: http://jr.falleri.free.fr/keep/
[07:22] <jjesse> OculusAquilae: thanks
[07:23] <jjesse> is there a way i can tell the version of a kubuntu disk when i forget to label it besides booting from it? :)
[07:24] <OculusAquilae> jjesse: I think if you put it into a running system it shows it (or is it a development release?)
[07:25] <jjesse> i htink it is a development release and currently booted into xp
[07:26] <OculusAquilae> Hm, I don't know if dev releases now their build date
[07:28] <jjesse> cleaning out laptop bavg for my trip
[07:29] <jjesse> found 2 kubuntu cds, 2 blank dvd-r and a vista businness edition install ;)
[07:34] <TheInfinity> strange collection ...
[07:37] <jjesse> yeah, well my cd case has visio 2007, office 2007, win 2k3, sql 2005, 3 games, 2 music cds and 3 kubuntu installs
[07:37] <jjesse> oh yeah, plus xp pro and win2k pro
[07:37] <jjesse> life of a consultant
[07:38] <jjesse> plus in my bag i have 3 2 gig usb sticks and 2 120 gig usb drives
[07:39] <OculusAquilae> jjesse: I try to write to JRe via Jabber


[02:57] <Ellsworth> I installed Xubuntu on a USB, whenever I boot it just brings me to BusyBox. Any suggestions?
[02:58] <branau> Ellsworth: How did you install it?
[03:02] <Ellsworth> put a cd with xubuntu in my pc, along with a 128gb flash, did the standard setup'
[03:04] <branau> Ellsworth: Did you set up the live USB?
[03:06] <Ellsworth> Not sure I'm understanding your question.
[03:06] <Ellsworth> I went through the install process, and chose the USB drive as the installation target
[03:07] <branau> Ah, you installed Xubuntu to the USB drive? You didn't just use the live iso?
[03:08] <Ellsworth> branau: hmm, indeed
[03:08] <Ellsworth> branau: can I get persistence on the live version?
[03:09] <branau> Interesting
[03:09] <branau> Ellsworth: Yeah, you can set up the live image to store data
[03:09] <Ellsworth> branau: Alrighty, I'll try using the live version.
[03:12] <branau> Ellsworth Which OS are you using to set up your USB?
[03:12] <Ellsworth> Xubuntu.
[03:13] <branau> Cool, I'd use the startup disk creator then, it's pretty simple to use and you can set aside the storage space for persistent file storage
[04:31] <total_> How do I revert a change in lightdm if it doesn't load?
[05:33] <cihhan> hi all! i am trying to install xfce to my ubuntu server -- i installed by apt-get install xfce4; however it doesnt auto start and i have to write startxfce4 everytime.
[05:33] <cihhan> is there a way to make it run at automatically at boot time?
[10:03] <xubuntu383> Hello, how can i close this window? i am installing xubuntu.
[10:20] <xubuntu88i> hi
[10:20] <Chofi> hi
[10:20] <Chofi> so I my xubuntu 15.10 installer crashed for an unspecified reason
[10:20] <Chofi> s/I my/my
[10:21] <Chofi> and now the reinstallation process is taking forever because of this saving installed packages process
[10:21] <Chofi> is there a way I can safely abort this saving installed packages process, format the partially installed xubuntu partition and do a fresh install, which is what I wanted in the first place ?
[10:29] <Chofi> yay
[10:29] <Chofi> it finished saving installed packages and began copying files
[10:31] <Chofi> oh great
[10:31] <Chofi> installer crashed again
[10:32] <Chofi> go figure what went wrong
[10:36] <flocculant> you sure it's crashed - or just too slow for you?
[10:36] <flocculant> you sure that the download was good ? cd or usb?
[10:36] <Chofi> well it said "the installer crashed" so I guess it crashed
[10:37] <Chofi> im on a live usb
[10:37] <Chofi> i'm trying for the third time and now it somehow looks better
[10:37] <flocculant> what's on the PC currently? You say 'abort and start again'
[10:38] <flocculant> is it crashing at the same point?
[10:38] <Chofi> oh god
[10:38] <Chofi> again
[10:38] <Chofi> installer crashed
[10:38] <Chofi> while "checking for packages to install"
[10:38] <flocculant> did you check the download before you put it on the cd?
[10:38] <Chofi> no, I did not
[10:38] <Chofi> I may try on a different USB drive
[10:39] <flocculant> I'd make sure the download is good first - what are you doing this from? linux or windows machine?
[10:39] <Chofi> windows
[10:39] <flocculant> https://help.ubuntu.com/community/HowToMD5SUM#MD5SUM_on_Windows
[10:40] <Chofi> let's try again
[10:40] <Chofi> thank you flocculant
[10:41] <flocculant> Chofi: actually - did you grab the iso with a torrent - if you did then no need to check it - should be fine
[15:45] <knob> Anybody has a problem with Dropbox's icon?   A la : http://askubuntu.com/questions/732967/dropbox-icon-is-not-working-xubuntu-14-04-lts-64
[15:45] <knob> I am running into that same problem... yet the posts there are less than a day old.  Still no solution
[16:14] <xubuntu71w> Hey there! How can I get new NOTIFICATION STYLES for Xubuntu 15.10? Thanks in advance :)
[19:35] <cihhan> hi all! i have installed xfce4 on my ubuntu server and then x11vnc. i am able to connect to my machine; however the gui user is root and lock-screen (leaves the screen blank and unlocked by mouse move without passwd) & switch user doesnt work (does not exist)
[19:35] <cihhan> any ideas?
[19:39] <branau> cihhan: What exactly is the issue? That the root account is accessible via GUI without a password?
[19:40] <cihhan> branau: yeah, that s the main problem :(
[19:41] <branau> Is it only unlocked without a password or can you connect and login without a password?
[19:42] <cihhan> right now, using my vnc password i login directly as root -- no other passwords or login screen
[19:47] <cihhan> branau: any suggestions?
[19:48] <branau> cihhan: http://www.karlrunge.com/x11vnc/faq.html#faq-users-opt
[19:48] <branau> Take a look at that
[19:49] <cihhan> branau: wow, how did i miss that. let me check and try. thanks a lot :)
[19:49] <branau> No worries, but it says that it could be a potential security issue to allow multiple users, so I'd take a look at it pretty carefully to make sure that you set it up right
[19:52] <branau> cihhan: As for the password not being required on unlocking the session, that should be configurable from the settings within the GUI
[19:56] <cihhan> branau: thanks a lot, i will check it right after the user login issue. thank you very much
[19:57] <branau> Sure thing!
[19:57] <branau> Let me know if you run into any more troubles!
[19:57] <heoyea> yelo
[19:59] <heoyea> anyone know where the "Disk Image Mounter" mounts to?
[20:02] <flocculant> heoyea: here it mounts to /dev/loop1p1 on /media/wolf/Xubuntu
[20:03] <flocculant> use it and type mount in a terminal to show you what you have mounted
[20:04] <heoyea> flocculant: oh these are archive://paths
[20:04] <heoyea> so im not sure where is mounted at
[20:05] <heoyea> i try looking in ~/.gvfs
[20:05] <heoyea> but nothing there
[20:24] <jfaust> heoyea: my gvfs mounts are here: /run/user/$(id -u)/gvfs
[20:27] <heoyea> jfaust: Thank you sir =)
[20:29] <jfaust> heoyea: no problem
[20:50] <cihhan> branau: unfortunately, x11vnc users parameter didnt solve the issue somehow..
[20:51] <cihhan> and im running x11vnc as 'ubuntu' user, instead of 'root'
[20:53] <branau> cihhan: The users parameter didn't allow to change users once you connected?
[20:54] <cihhan> unfortunately it directly started as root again, instead of user ubuntu
[20:57] <branau> Which command are you using to start the connection?
[21:17] <cihhan> branau: you mean the x11vnc?
[21:17] <branau> cihhan: yep
[21:18] <cihhan> branau: /usr/bin/x11vnc -xkb -noxrecord -noxfixes -noxdamage -users ubuntu -display :0 -rfbauth /etc/x11vnc.pass  -forever -bg -rfbport 5900
[21:20] <cihhan> branau: and i m running it as ubuntu, not root
[21:20] <branau> I think you need to prepend ubuntu with a +, so that part should read -users +ubuntu
[21:20] <cihhan> branau: actually i tried that one too but let me try again
[21:21] <branau> cihhan: let me know how that goes
[21:22] <cihhan> branau: the same, i still login as root (and it directly logins without any passwd asked)
[21:28] <cihhan> branau: initiall i had ubuntu server and i install xfce4 xfce4-goodies xvfb x11vnc lightdm  on it
[21:29] <cihhan> branau: i dont know if that would help
[21:31] <branau> cihhan: how do you have it configured on the server? Have you taken a look at the Arch Linux wiki for x11vnc? Theyve got some good info in there
[21:32] <branau> See here: https://wiki.archlinux.org/index.php/x11vnc
[21:32] <cihhan> i have actually. in fact i checked a couple of tutorials and all are very similar (mostly the same)
[21:33] <branau> So what command did you run on your server to start the VNC server?
[21:34] <cihhan> branau: /usr/bin/x11vnc -xkb -noxrecord -noxfixes -noxdamage -users ubuntu -display :0 -rfbauth /etc/x11vnc.pass  -forever -bg -rfbport 5900
[21:37] <branau> cihhan which client are you using? Is it storing your password for you? Or can you login from various machines with no password?
[21:38] <cihhan> branau: im using gtkvncviewer and it has username and password and i use ubuntu as the username
[21:45] <branau_> cihhan I'd post on the Ubuntu forums if I were you. I'm away from my computer so I can't test things out ATM but ping me the link to your post and I'll spin up am EC2 instance to test it when I'm in front of my comp again, provided you can't find a solution before then
[21:45] <cihhan> thanks a lot branau_, i really appreaciate that
[21:45] <branau_> Sure thing!
[21:53] <cihhan> branau_, at last.... Based on the configurations I used, it was supposed to use lightdm-gtk-greeter -- however it seems that it wasnt installed at all...
[21:54] <branau_> cihhan: that fixed it then huh? Interesting. Glad you got it working though!
[21:58] <cihhan> branau_" yeah that fixed the problem. it seems that it wasnt a part of the lightdm
[22:39] <branau_> cihhan: interesting, seems like it should be a dependency but I'm sure there's a reason for it not being there
[22:40] <cihhan> branau_, most prob.. but nobody was mentioning about it -- or i didnt see it
[22:41] <branau_> cihhan: it may be worth filing it as a bug report. If it is a bug, it'll get fixed. If not, then they'd at least be able to explain it
[22:42] <cihhan> branau_, you are right. where to fill it?
[22:43] <branau_> cihhan launchpad would be my best bet, let me see where the package is maintained
[22:44] <branau_> cihhan: https://bugs.launchpad.net/lightdm
[22:44] <branau_> I'd report it there
[22:45] <cihhan> branau_, thanks a lot, i will fill a report now
[22:46] <branau_> Sure thing, glad everything worked out!
[23:54] <xubuntu534> Can anyone see this?


[02:41] <mfisch> robert_ancell: I ran info an issue merging manpages, bzr claims the branches have diverged
[02:41] <robert_ancell> mfisch, merging which manpages?
[02:41] <mfisch> robert_ancell: the manpages package
[02:42] <robert_ancell> oh, that package is fun
[02:43] <mfisch> bzr gave up halfway through the mege
[02:43] <mfisch> I did spend some time cleaning up the bug list, resolved a bunch, incompleted a bunch more
[02:44] <mfisch> I'm going to take debian and try to merge our stuff on top of it instead
[03:01] <mfisch> robert_ancell: I'm going to propose that we drop the Ubuntu modifications, I'll email you and see what you think
[03:01] <mfisch> it would make everyone's life easier not to hold these changes and they're mostly incorporated upstream
[04:01] <Mirv> morn
[06:00] <didrocks> cyphermox: hey, you didn't update your WI. Had to do it for you :/
[06:41] <didrocks> jibel: salut (quand tu seras là). No more magners :/
[06:46] <jibel> didrocks, Hello, I noticed that :/
[06:47] <jibel> didrocks, riding my kids to school, back in 10min
[06:48] <didrocks> jibel: ttyl :)
[06:48] <didrocks> magners still pong though)
[06:51] <mlankhorst> morning
[06:51] <didrocks> hey mlankhorst
[06:51] <mlankhorst> oh excusez-moi, bonjour!
[06:51] <mlankhorst> riri
[06:53] <didrocks> héhé
[07:04] <jibel> didrocks, similar problem than last Monday
[07:05] <mlankhorst> didrocks: at what point will unity land in saucy?
[07:07] <jibel> didrocks, there is no good option right now, if we keep it in this state there is a chance the machine will completely hang in the next few hours, if I restart it there is 99% chance to completely lose connectivity to the lab.
[07:07] <jibel> didrocks, I'll go for option 1 and wait for someone with a hammer in Lex around 10:00UTC
[07:10] <highvoltage> AAAA/win 21
[07:17] <didrocks> mlankhorst: at the same time than touch will be able to land in saucy
[07:17] <didrocks> mlankhorst: which is now blocked on the phone fundation team
[07:17] <didrocks> jibel: yeah
[07:18] <didrocks> jibel: seems like it's our better chance
[07:55] <Laney> morning
[07:56] <seb128> hey Laney, hey desktopers
[07:56] <seb128> Laney, how are you?
[07:57] <mlankhorst> morning laney
[07:57] <Laney> seb128: good thanks
[07:57] <Laney> you?
[07:57] <Laney> g'day mlankhorst
[07:57] <seb128> I'm good as well
[07:58] <seb128> Laney, since Sweetshark got libreoffice to build I was thinking of uploading the new poppler, mitya57 prepared the transition in a ppa so it should be an easy one to get through ... any objection?
[08:01] <Laney> seb128: no, not that I can think of
[08:01] <Laney> tkamppeter__: ^?
[08:12] <tkamppeter> Laney, seb128, go ahead with the Poppler update, nothing bad of it is known to me, and it solves the filled-form-saving bug.
[08:18] <mitya57> The PPA was only to ensure that everything builds, please don't copy from there but reupload
[08:19] <Laney> mitya57: were patches required?
[08:19] <seb128> mitya57, you can't copy from a virtual ppa (missing archs) and I was not planning to do that
[08:19] <Laney> you can copy source only
[08:19] <Laney> one reason I've been using 'archive' version numbers in the evo-3.8 PPA
[08:19] <seb128> right
[08:20] <Laney> but yeah, you should intend to do that beforehand
[08:20] <mitya57> Okular and inkscape need some unrelated to poppler fixes
[08:20] <mitya57> (branches linked to the bug)
[08:21] <Laney> ok
[08:21] <Laney> I want to do empathy 3.8 first and then can start helping out on that if needed
[08:22] <seb128> Laney, it should be fine, I will start on it and let you know if I need help this afternoon
[08:23] <Laney> cool
[08:24] <mitya57> Note that I haven't tested libreoffice with new poppler yet
[09:54] <mitya57> seb128: looks like Riddell uploaded fixed okular, so only inkscape needs not rebuild-only upload
[09:55] <mitya57> Riddell: btw, it ftbfs on armhf, looks like one more line should be removed from libokularcore2abi1.symbols
[10:14] <Riddell> mitya57: ok thanks, I'm going to review all my kde merges today
[10:15] <seb128> Riddell, will you fix/reupload okular then? (just asking since we will need it to build to complete the poppler transition)
[10:16] <Riddell> seb128: yeah I'll get onto it shortly
[10:16] <seb128> Riddell, thanks
[10:20] <seb128> chrisccoulson, hey, how much do you hate ppc today? ;-)
[10:20] <chrisccoulson> hey seb128
[10:20] <chrisccoulson> how come?
[10:20] <chrisccoulson> i hate it as much as ever ;)
[10:21] <seb128> chrisccoulson, I saw that firefox is stucked in saucy-proposed because it failed to build on ppc
[10:21] <chrisccoulson> it's going to be stuck there forever then ;)
[10:21] <seb128> :-(
[10:22] <chrisccoulson> it sucks that we block migration because of ppc
[10:22] <seb128> right, I argued about that in the past
[10:24] <chrisccoulson> i wonder whether to just turn off the powerpc build entirely
[10:26] <seb128> I guess that wouldn't be the end of the world
[10:26] <seb128> the efforts spent to fix it don't seem worth the benefit
[11:14] <xnox> Laney: based on errors, saucy's currently top crasher is libproxy, where pxgsettings core dumps when run (without or any args, even e.g. --help)
[11:14] <xnox> have you tried poking it yet?
[11:15] <seb128> xnox, yes, the code is stupid and the patch trivial
[11:15] <Laney> I was hoping for upstream to reply
[11:15] <seb128> Laney, let's just drop that loop, it's cleaning on exit which is not required...
[11:16] <seb128> Laney, do you want me to upload that?
[11:16] <Laney> sure or I will later after my epic battle with empathy results in my victory
[11:17] <xnox> seb128, Laney: cool.
[11:17]  * xnox goes back to testing updated lvm2
[11:17] <Laney> I've been submitting that crash every time I get it btw so I may be responsible for a lot of the instances
[11:22] <seb128> it's weird, I never saw it here
[11:23] <Laney> nobody else complained to me about it which is why I didn't fix it urgently
[11:23] <Laney> figuring it's config dependent
[11:23] <seb128> well I get the segfault if I run that command
[11:23] <seb128> I suspect you have proxy somewhat enabled that's why you see it
[11:25] <Laney> shouldn't do
[11:25] <seb128> Laney, xnox: fix uploaded
[11:26] <Laney> ty
[11:26] <seb128> Laney, gsettings list-recursively org.gnome.system.proxy
[11:26] <seb128> can you pastebin that?
[11:27] <Laney> seb128: http://paste.ubuntu.com/5716409/
[11:27] <Laney> the localhost:8080 socks proxy is probably something I did
[11:28] <Laney> s/socks/http/
[11:28] <seb128> Laney, seems similar to my config, maybe I'm just not using a program using proxy through gio here ;-)
[11:28] <seb128> Laney, anyway I verified the fix works with the pxgsettings command line
[11:28] <Laney> oh well
[11:28] <Laney> great
[11:28] <seb128> Laney, I'm using pidgin and not empathy, which might be it :p
[11:31] <Laney> hmm
[11:31] <Laney> does it make sense to keep having all the account-plugins-* packages now that you don't need a .so for each of them?
[11:32] <seb128> what do you need?
[11:32] <seb128> I'm not familiar with how uoa works
[11:32] <seb128> what changed?
[11:32] <seb128> maybe better to ask ken when he will be online
[11:33] <Laney> you just need one plugin afaict
[11:33] <Laney> rather than having /usr/lib/libaccount-plugin-1.0/providers/*.so for each service
[11:35] <Laney> I suppose to not have them all listed by default
[11:37] <seb128> Laney, is that a change in 3.8..?
[11:38] <Laney> yep
[11:38] <seb128> on my saucy system, account-plugin-jabber: /usr/lib/libaccount-plugin-1.0/providers/libjabber.so for example
[11:38] <seb128> oh
[11:38] <Laney> it was done by m ardy
[11:39]  * Laney tries a build without them but with the same package structure
[11:40] <seb128> Laney, http://bugzilla.gnome.org/691418 I see
[11:40] <ubot2> Gnome bug 691418 in UOA "Use a shared plugin for all empathy providers" [Normal,Resolved: fixed]
[11:40] <Laney> yeah
[11:43] <seb128> Laney, does it still have the .service files?
[11:43] <seb128> e.g /usr/share/accounts/services/jabber-im.service
[11:44] <seb128> Laney, one thing to avoid would be to have all the "small/non usual providers" cluttering the accounts list, atm we only have the one installed listed in the control center
[11:44] <seb128> we probably want to avoid having 15 items in that list including stuff nobody use
[11:46] <Laney> seb128: yes, .service and .provider are still there
[11:46] <Laney> I'll keep the split for now
[11:46] <seb128> k
[11:49] <asac> seb128: who owns "Networking & Telephony story" on your side?
[11:49] <asac> cypher or stgraber?
[11:50] <seb128> asac, cyphermox
[11:51] <xclaesse> When upgrading the kernel, I get that error: cp: cannot stat '/module-files.d/libpango1.0-0.modules': No such file or directory
[11:51] <xclaesse> could be broken because of gnome3 ppa
[11:51] <xclaesse> anyone knows a workaround for that?
[11:51] <xclaesse> it happens when doing update-initramfs: Generating /boot/initrd.img-3.8.0-22-generic
[11:54] <seb128> xclaesse, is that saucy ?
[11:54] <xclaesse> seb128, raring
[11:55] <xclaesse> with some ppa like https://launchpad.net/~ubuntu-desktop/+archive/ppa and https://launchpad.net/~gnome3-team/+archive/gnome3
[11:56] <seb128> xclaesse, dpkg -l | grep pango?
[11:57] <xclaesse> seb128, http://pastebin.com/MhSx4rHL
[11:57] <seb128> shrug
[11:58] <seb128> you got bitten by ricotz's ppa, check with him
[11:58] <seb128> he tends to have packages pretty much on the "edge" side
[11:58] <seb128> I would avoid that ppa if I was you
[12:00] <xclaesse> yeah, I probably shouldn't have added those ppa :(
[12:01] <seb128> xclaesse, try to ppa-purge it
[12:01] <xclaesse> all I wanted is EDS 3.8 for the UOA integration
[12:01] <seb128> or at least re-install pango from raring
[12:11] <ricotz> xclaesse, if you have gnome3-stating ppa enabled you can wait for the plymouth update
[12:17] <ricotz> seb128, hi :), thanks for pinging me, but you could try to avoid scaring people away
[12:18] <seb128> ricotz, hey, did I scare people away?
[12:18] <ricotz> seb128, not sure, he doesnt answer ;)
[12:18] <seb128> ricotz, but that error seems to suggest you took the debian packaging change from pango which impact on initramfs and plymouth and pushed to a stable serie, that's probably something most users don't want to opt in for
[12:20] <ricotz> seb128, yes, i am fine with that in the staging ppa
[12:21] <seb128> ricotz, I wouldn't want to opt in for a ppa which impact on my initramfs, userspace is fine, boot stuff a bit less ... but just my opinion
[12:21] <ricotz> seb128, ok
[12:22] <sil2100> didrocks: if anything, I pushed an updated python-evdev to the packaging branch of mine, you can take a look when you have a moment ;)
[12:22] <sil2100> https://code.launchpad.net/~sil2100/python-evdev/debian
[12:22] <sil2100> Now I disappear, so see you later guys!
[12:41] <mitya57> cyphermox: can you please review (the fixed version of) https://code.launchpad.net/~abelloni/ubuntu-themes/3.8_fixes/+merge/161439 ?
[13:11] <seb128> hum
[13:11] <seb128> mitya57, you forgot packages in your poppler rdepends list, e.g xpdf is not in there and doesn't build with a simple rebuild :/
[13:13] <mitya57> seb128: oh it depends on libpoppler-private-dev which I didn't check
[13:13] <seb128> mitya57, shrug
[13:13] <mitya57> let me look at the build log
[13:13] <seb128> mitya57, rdepends libpoppler18 is what I did
[13:14] <mitya57> seb128: was it a local build? can you please paste the log somewhere?
[13:15] <seb128> mitya57,
[13:15] <seb128> -c -o build/GlobalParams.o build/GlobalParams.cc
[13:15] <seb128> build/GlobalParams.cc: In constructor ‘GlobalParams::GlobalParams(char*)’:
[13:15] <seb128> build/GlobalParams.cc:656:37: error: ‘getHomeDir’ was not declared in this scope
[13:15] <seb128>    baseDir = appendToPath(getHomeDir(), ".xpdf");
[13:23] <mitya57> getHomeDir() was removed in http://cgit.freedesktop.org/poppler/poppler/commit/?id=44bf99a7b8
[13:24] <seb128> mitya57, can you work on a build fix?
[13:24] <mitya57> seb128: sure
[13:24] <seb128> mitya57, thanks
[13:49] <mitya57> tsdgeos: is it safe to replace getHomeDir() with just getenv("HOME") in Ubuntu? (^)
[13:50] <tsdgeos> mitya57: what do you need it for?
[13:51] <mitya57> tsdgeos: xpdf uses it (see seb128's message above_
[13:51] <tsdgeos> ah
[13:51] <tsdgeos> well, don't break xpdf then :D
[13:51] <tsdgeos> xpdf != popplre
[13:52] <tsdgeos> if i was xpdf author i'd complain to people packaging something they call xpdf but is not, but obviously i'm not the xpdf author :D
[14:06] <cyphermox> mitya57: looking...
[14:06] <seb128> mitya57, hum, gdcm fails to build as well, though I'm not sure if that's due to poppler (https://launchpad.net/ubuntu/saucy/+source/gdcm/2.2.3-1ubuntu1)
[14:06] <Laney> mitya57: reverse-depends -b src:poppler for future reference
[14:06] <Laney> maybe without -b too to pick up indirect bds
[14:07] <attente> seb128, do you know how to properly update the .po files in g-c-c?
[14:07] <seb128> attente, you mean?
[14:07] <seb128> attente, the po are not in g-c-c, we export translation from launchpad ... or do you mean the template?
[14:08] <mitya57> seb128: this looks like gcc 4.8
[14:08] <seb128> :-(
[14:08] <mitya57> let me fix xpdf first, and then I'll maybe look
[14:08] <seb128> thanks
[14:09] <attente> seb128, to add new msgid's to the po files extracted from the source code of the changes to the panel i've made
[14:09] <seb128> attente, in a nutshell:
[14:09] <seb128> - use _() around your strings
[14:09] <seb128> - lists the source in po/POTFILES.in
[14:10] <seb128> - you can generate a template to check if your strings are listed with "cd po: intltool-update --pot"
[14:10] <seb128> that gives you a .pot in po/ which lists all the strings marked for translation
[14:10] <seb128> - that template is generated at build time, imported in launchpad
[14:11] <seb128> - translators do their work
[14:11] <seb128> - we export the translations in language packs
[14:11] <seb128>
[14:11] <attente> _() is only for c code, right? what does one do if the string is in a GtkBuilder ui file for example?
[14:11] <seb128> attente, so basically just do the first 3 steps, if your string is listed you are all set, the buildd magic will do the work for you
[14:11] <seb128> attente, translation=yes
[14:12] <attente> seb128, awesome, thanks :)
[14:12] <seb128> ups
[14:12] <seb128> attente, translatable="yes" rather
[14:12] <seb128> attente, see e.g /usr/share/gnome-control-center/ui/gnome-region-panel.ui
[14:12] <seb128>     <property name="title" translatable="yes">Region and Language</property>
[14:12] <seb128> same for labels, etc
[14:13] <attente> heh, glade already puts those in automatically it seems
[14:13] <seb128> yes
[14:13] <Laney> speaking of translations, is it normal to have LP push back to trunk or a separate branch when setting a project up for translating?
[14:13] <seb128> Laney, it depends how the project is set up
[14:13] <seb128> some want direct commit
[14:13] <seb128> some prefer to manually merge the translation before doing a release
[14:13] <cyphermox> mitya57: approved.
[14:14] <Laney> I set it up for ubuntu-release-upgrader but going to another branch
[14:14] <Laney> seems like it would be easier to have it just go to trunk
[14:14] <seb128> yeah, lightdm seems to do that
[14:14] <seb128> maybe ask dpm, he probably knows better the details
[14:14] <dpm> hey
[14:15] <seb128> dpm, hey ;-)
[14:15] <Laney> the magic three letters
[14:15] <dpm> hello desktop folks :)
[14:16] <mitya57> cyphermox: thanks!
[14:16] <dpm> Laney, seb128, I always recommend setting the exports branch to trunk. This makes it much easier, as then the full process is automated and no one has to go and manually merge the translations branch to trunk, which in my experience tends to be forgotten
[14:17] <Laney> dpm: that's what I just noticed
[14:17] <Laney> will do that, assuming I can find the option again
[14:18] <dpm> Laney, yeah the UI is a bit difficult to navigate, it also often takes me a while to find it. The thing to remember is that translation exports are set for a given series
[14:18] <Laney> yep, got it
[14:18] <dpm> cool
[14:18] <dpm> Laney, also, if translations are done in LP, the best setting for imports is "Templates only"
[14:19] <dpm> unless you want to do a one-off import of existing PO files that were done outside of LP
[14:19] <dpm> then you'd choose "Template and translations"
[14:20]  * dpm has a todo to document translations setup best practices
[14:20] <Laney> I had it on templates and translation files
[14:45] <mitya57> seb128: I think the less ugly solution will be to have a cut down version of getHomeDir() inside GlobalParams.cc
[14:46] <mitya57> seb128: I'm on a sid machine now, so can't test locally, so pushed to ppa
[14:46] <mitya57> and to lp:~mitya57/ubuntu/saucy/xpdf/fix-for-poppler-0.22
[14:46] <seb128> mitya57, copy works for me
[14:46] <seb128> mitya57, ok, I can try it here
[14:58] <seb128> mitya57, fails to build
[14:58] <seb128> build/XPDFViewer.cc: In member function ‘void XPDFViewer::initOpenDialog()’:
[14:58] <seb128> build/XPDFViewer.cc:2978:52: error: ‘makePathAbsolute’ was not declared in this scope
[14:58] <seb128>         core->getDoc()->getFileName()->getCString()));
[15:00] <mitya57> :(
[15:05] <mitya57> I will now try to force including of xpdf's gfile.h instead of poppler's one, maybe that'll be easier
[15:13] <tsdgeos> seb128: mitya57: yes basically we removed lots of stuff from the gfile and stuff that was unused
[15:20] <seb128> I'm out for some exercice, back in ~1h
[15:31] <mitya57> tsdgeos: anything except makePathAbsolute and getHomeDir?
[15:31] <tsdgeos> mitya57: not sure what you mean
[15:33] <mitya57> tsdgeos: these are two functions you definitely removed, and both were used by Xpdf
[15:33] <tsdgeos> yes
[15:33] <mitya57> *by Ubuntu's Xpdf
[15:34] <tsdgeos> xpdf should not be using poppler
[15:34] <mitya57> tsdgeos: I think this is the only way to have it maintained, as upstream seems dead
[15:34] <tsdgeos> mitya57: it's not dead, just veeeeeeeeeeery slow on releases
[15:35] <tsdgeos> mitya57: anyway, if you are patching xpdf to use poppler, you may as well patch xpdf and add the functions poppler removed
[15:36] <mitya57> tsdgeos: those functions are there, but debian/rules prepends "pkg-config --cflags poppler" to build args, so it tries to use Poppler's headers
[15:48]  * Laney watches kenvandine's epic fight with PS Jenkins bot
[15:48] <kenvandine> indeed
[15:49] <kenvandine> it says xvfb-run failed to start
[15:49] <kenvandine> that can't be because of laney's branch :)
[15:50] <Laney> you'd hope so :P
[16:03] <mitya57> seb128: back?
[16:07] <mitya57> bad /me. 43min != 1h
[16:15] <kenvandine> Laney, i'm at a loss... tests run fine in pbuilder but not in jenkins anymore... grrrr
[16:15] <kenvandine> Laney i guess i need to summon the jenkins masters :)
[16:16] <Laney> bah!
[16:16] <Laney> I assume it's going to affect more than just this project though
[16:17] <kenvandine> yeah... :/
[16:18] <kenvandine> it's worked fine for months...
[16:19] <kenvandine> fginther, do you have any ideas why suddenly running tests that use xvfb-run in jenkins fails?
[16:19] <kenvandine> xvfb-run: error: Xvfb failed to start
[16:19] <kenvandine> is the error
[16:21] <kenvandine> fginther, it's autolanding for the friends stack that started to fail, which we did just change the ci_defaults from raring to saucy
[16:25] <fginther> kenvandine, hmmm, perhaps there's something broken in saucy?
[16:26] <fginther> kenvandine, we can try a few tests with raring and comparing the results
[16:26] <kenvandine> works in pbuilder
[16:26] <kenvandine> for saucy
[16:26] <kenvandine> i have no idea what to try next...
[16:29] <seb128> mitya57, back
[16:30] <mitya57> seb128: do you think we can do what tsdgeos says?
[16:30] <mitya57> (drop all poppler-related patches and build without poppler)
[16:31] <mhr3> kenvandine, do you run xvfb-run with -a?
[16:31] <mitya57> otherwise I'll give you another patch that copies makePathAbsolute to XPDFViewer.cc
[16:31] <seb128> mitya57, what did he suggest?
[16:31] <kenvandine> mhr3, nope
 well, don't break xpdf then :D
 if i was xpdf author i'd complain to people packaging something they call xpdf but is not, but obviously i'm not the xpdf author :D
[16:32] <mhr3> kenvandine, you should :)
[16:32] <seb128> mitya57, I would prefer to use copy those functions of that works
[16:32] <mitya57> ok
[16:32] <kenvandine> mhr3, good point :)
[16:32] <fginther> kenvandine, I'll look into it, maybe there is something wrong on the host
[16:32] <kenvandine> but it has always worked
[16:32] <seb128> mitya57, or check with the security team, the reason we made xpdf use poppler was easier security maintenance since xpdf doesn't keep on top of their issues
[16:33] <seb128> mitya57, but for what I'm concerned we could stop maintaining xpdf or drop it from the archive
[16:33] <seb128> it was important 10 years ago but we got some better viewers since
[16:34] <fginther> kenvandine, we could be running into port resource issues. I'll take a look after lunch
[16:34] <kenvandine> fginther, thx
[16:34] <kenvandine> i'll give it a try with -a too
[16:38] <seb128> Sweetshark, grararr, libreoffice failed to build with
[16:38] <seb128> "Checking correctness of source dependencies...
[16:38] <seb128> After installing, the following source dependencies are still unsatisfied:
[16:38] <seb128> libhsqldb-java(inst 2.2.9+dfsg-3ubuntu1 >= conflicted 1.8.1~)"
[16:43] <mitya57> seb128: branch updated, please try to build this
[16:43] <mitya57> (but +1 to dropping xpdf completely)
[16:44] <mitya57> seb128: will look at gdcm tomorrow
[16:44] <seb128> mitya57, thanks, no hurry we will be blocked on libreoffice for a while it seems
[16:44] <seb128> cf what I just copied
[16:44] <Laney> err
[16:44] <seb128> well "while"
[16:45] <seb128> need Sweetshark to be back (today is an holiday for him) and then we will need at least a day for the builds
[16:45] <Laney> does it really Build-Conflict on a version which is implied by the Build-Depends?
[16:45] <seb128> mitya57, http://paste.ubuntu.com/5717337/
[16:45] <Laney> I don't understand how that ever built if so
[16:45] <Laney> must be misreading
[16:46] <seb128> Laney, that's the diff of that upload: https://launchpadlibrarian.net/141103518/libreoffice_1%3A4.0.2-0ubuntu1_1%3A4.0.2-0ubuntu2.diff.gz
[16:46] <Laney> ah, no, 1.8.1 vs <IP_ADDRESS>
[16:46] <Laney> so as soon as that package was upgraded LO was broken
[16:46] <Laney> still ...
[16:46] <seb128> it built in a ppa
[16:46] <seb128> I don't get it
[16:47] <Laney> see https://launchpad.net/ubuntu/+source/hsqldb
[16:47] <mitya57> seb128: so let's wait until tomorrow when I'll be at my saucy machine
[16:47] <seb128> mitya57, ok
[16:47] <seb128> Laney, shrug, I guess the ppa doesn't use proposed :/
[16:47] <seb128> nor do I
[16:47] <Laney> apparently not, it's not the default
[16:48] <seb128> so we didn't see that before upload
[16:48] <seb128> "fun"
[16:48] <mitya57> I wanted to check if xpdf is popular in Ubuntu and noticed that popcon.ubuntu.com is still not working :/
[16:48] <Laney> "For safety, add a build-conflicts against libhsqldb-java (>> 1.8.1~)"
[16:48] <Laney> that's quite some safety
[16:49] <seb128> it's protecting you to have a chance to have libreoffice to ever build
[16:49] <seb128> :p
[16:49] <Laney> saving buildd time :P
[16:54] <seb128> Laney, http://anonscm.debian.org/gitweb/?p=pkg-openoffice/libreoffice.git;a=commitdiff;h=bf27df32a74473a045605a8e7b02b5586a6ebcd8
[16:54] <Laney> yeah
[16:54] <seb128> it seems like that's a buggy conflicts and should just be dropped
[16:55] <seb128> I think I will drop the
[16:55] <seb128> ifneq (,$(filter hsqldb, $(SYSTEM_STUFF)))
[16:56] <seb128>         perl -pi -e "s/(Build-Conflicts: .*)/\1,libhsqldb-java (>= $(HSQLDB_TOONEWVER)~),/" debian/control
[16:56] <seb128> endif
[16:56] <jbicha> seb128: howdy
[16:56] <seb128> jbicha, hey
[16:57] <jbicha> seb128: is there anything else I should do to coordinate handling bug 1185869 ?
[16:57] <ubot2> Launchpad bug 1185869 in gnome-shell (Ubuntu) "Update gnome-shell to 3.8" [Undecided,New] https://launchpad.net/bugs/1185869
[16:58] <Laney> does it work with the new eds?
[16:59] <Laney> seb128: Digging slightly it seems that the modified build-dep is because _rene_ uploaded a forked source package of the old version of hsqldb
[16:59] <jbicha> Laney: yes as we've had gnome-shell 3.8 in the staging ppa with e-d-s 3.8 for a while
[16:59] <Laney> so it keeps using the old series
[16:59] <mitya57> jbicha: are you going to update gsettings-desktop-schemas also?
[16:59] <Sweetshark> seb128: heh, java guys doing updates in proposed, creating pain? welcome to my world.
[16:59] <Laney> we might want to upload that thing too
[17:00] <Laney> that's hsqldb1.8.0 source package
[17:00] <jbicha> mitya57: yes, there's two schemas that were dropped that we're patching back in since we're still using them
[17:01] <Laney> where does the transition come from?
[17:02] <Laney> it might be safer to wait until after eds to avoid entangling things
[17:02] <seb128> jbicha, nothing special, can gsettings-desktop-schemas be uploaded first or does it break things?
[17:02] <mitya57> jbicha: this will break metacity, please commit the patch from gnome #697801 then (at least upstream, and I'll then cherry-pick it)
[17:02] <ubot2> Gnome bug 697801 in general "Alt+Tab doesn't work in Metacity with gsettings-desktop-schemas 3.8" [Normal,Unconfirmed] http://bugzilla.gnome.org/show_bug.cgi?id=697801
[17:03] <seb128> Sweetshark, what do you recommend doing? just dropping the lines I pointed
[17:03] <mitya57> (ther first one, second is not too necessary)
[17:03] <seb128> Laney, you seem to have a better grasp that me in that libreoffice issue ... what do you recommend doing
[17:03] <jbicha> Debian has the schemas break gnome-shell << 3.7.90 because of http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=701619
[17:03] <ubot2> Debian bug 701619 in gsettings-desktop-schemas "gsettings-desktop-schemas: Updating gnome-themes-standard to 3.7.90 broke switching windows in gnome-shell 3.6" [Normal,Fixed]
[17:03] <Laney> I think we have to take that hsqldb1.8.0 package
[17:03] <seb128> (sorry just back from exercice and catching up with backlog)
[17:03] <mitya57> jbicha: I know, as I'm the reporter :)
[17:03] <jbicha> but I can drop that change as we know that gnome-shell is broken anyway if we want to just update the schemas separately
[17:04] <Sweetshark> seb128: mom, checking git blame for those lines.
[17:04] <seb128> Laney, will that fix the conflict? how so?
[17:04] <Laney> it will not, but if you look at the LO commit he updated the BD too to use a package from it
[17:04] <Laney> I assume because the new series doesn't work
[17:04] <seb128> jbicha, no, that's ok, I just like to have things landing in chunks when possible rather than all together
[17:04] <seb128> easier for testing and debugging
[17:04] <Sweetshark> seb128: do you know why that hsqldb stuff is stuck so long in proposed?
[17:05] <Laney> let me go and ask jamespage if he'll do the update
[17:05] <Sweetshark> seb128: because there might be extra fun in for us, if building lo against it doesnt run against the 1.8 in saucy (non-proposed) ...
[17:05] <Laney> it's a transition
[17:06] <seb128> Sweetshark, if I read http://people.canonical.com/~ubuntu-archive/proposed-migration/update_output.txt  correctly, because libreoffice needs to transition to use the new one :p
[17:06] <seb128> skipped: hsqldb (538 <- 132)
[17:06] <seb128>     got: 91+0: i-91
[17:06] <seb128>     * i386: jodconverter, libjodconverter-java, libreoffice, libreoffice-base, libreoffice-report-builder, libreoffice-report-builder-bin, libreoffice-subsequentcheckbase
[17:06] <jbicha> mitya57: I can sponsor metacity for you
[17:07] <Laney> pinged jamespage in #ubuntu-devel
[17:07] <seb128> thanks
[17:08] <mitya57> There's some chance I get MOTU permissions on Monday, so that won't be needed
[17:08] <Laney> could probably manage to do it myself tomorrow though if necessary
[17:08] <mitya57> ah, no, it's in main, probably because compiz uses libmetacity
[17:09] <mitya57> jbicha: so, "sponsor" it upstream please :)
[17:14] <mitya57> jbicha: thanks (though you decided to commit the second one also for some reason)
[17:14] <jbicha> mitya57: does it need to be reverted?
[17:15] <mitya57> jbicha: no, but it's pointless for me
[17:15] <Sweetshark> seb128: http://anonscm.debian.org/gitweb/?p=pkg-openoffice/libreoffice.git;a=commitdiff;h=6cc45869;hp=c7d7b35581a0d730a20684b02a28e5605ff99eea <- seemed to have been a better-be-safe-than-sorry commit, waaay back then.
[17:15] <mitya57> anyway Florian requested it, so let's keep it
[17:16] <seb128> Sweetshark, Laney, what's the issue if we just drop that conflicts?
[17:16] <jbicha> Laney: ok I'll do the transition after the e-d-s one is finished
[17:17] <Laney> seb128: I think the issue is that it doesn't work against hsqldb 2
[17:17] <Laney> otherwise _rene_ wouldn't have bothered to fork the package
[17:17] <Laney> that's just a guess though
[17:19] <Sweetshark> seb128: upstream LibreOffice configure checks hard on hsqlsb >= <IP_ADDRESS> and < 1.8.1 even with the upcoming LibreOffice 4.1.x.
[17:19] <Laney> It's OK, I'm preparing the upload
[17:20] <Laney> so we'll just be able to take the renamed build-dep
[17:20] <Sweetshark> seb128: How can such an update land in -proposed, and I havent even heard about that? That completely breaks LibreOffice Base -- hard, I assume.
[17:21] <seb128> Sweetshark, that's why it didn't go out of proposed :p
[17:21] <seb128> Sweetshark, I guess jamespages didn't notice it would break libreoffice
[17:21] <seb128> it's not obvious from outside
[17:22] <Laney> it's a good idea to make your archive PPAs and distro chroots build against -proposed to notice this kind of thing early
[17:24] <Sweetshark> seb128: Long term, there are these options: a/ kill that update with fire (I like this option) b/ patch out the tests in LO configure and hope it works a little bit (I hate this option) c/ use the internal copy of hsqldb in libreoffice (meh, break all tries to use system integration, or people using the system hsqldb to open LO Base files)
[17:25] <seb128> Sweetshark, well, it seems like debian/rene reuploaded the old version of hsqlsb as a separate source (what Laney is doing for us)
[17:25] <seb128> but I'm not sure if that's any better than using the libreoffice copy...
[17:26] <Sweetshark> Laney: I usually do so that on the last build before upload, I wont do it for every build as that would kill build time when you depend on 1/3 of main ....
[17:26] <xnox> Sweetshark: i did point out updated hsqlsb in saucy-proposed to you a few times.... ever since I was poking it after holiday =)
[17:27] <xnox> but it was hard to notice with all the other things breaking libreoffice build in saucy already.
[17:30] <Sweetshark> seb128: so, to resolve this emergency, using the internal copy is surely the quickest way. We still should seriously discuss if that hsqldb thing should go in saucy for real though ...
[17:31]  * didrocks waves good evening
[17:31] <Laney> It's fine, I've got the package upload ready so it's just a matter of updating LO to use the new package name (that git patch)
[17:32] <seb128> Laney, want to do that?
[17:32] <Laney> yes, just waiting for cjwatson to reply to me
[17:32] <seb128> Laney, great, thanks
[17:32] <Laney> he was debugging why the autosyncer didn't get it
[17:32] <seb128> it can wait tomorrow
[17:32] <seb128> though if we upload today we might win half a day of build time
[17:35] <seb128> Sweetshark, btw I hate libreoffice, I had to make 6GB of free space to run debuild -S and it maxed out io on my ssd for over 5 minutes to pack the source
[17:36] <Sweetshark> xnox: If I manually check every of the 1000 LibreOffice deps on every update of them, we would never see a release, so without a big fat "this will break stuff" (read: at least an email) warning, it flies under the radar.
[17:37] <Sweetshark> seb128: heh, 6GB? why dont you pack in RAM? its faster and with 32GB you will barely notice ... ;P
[17:38] <xnox> Sweetshark: sure. but at least with hsqlsb case, libreoffice had tight build-conflicts which are easy to check for statically =) (without actually building libreoffice)
[17:38] <seb128> lol
[17:38] <seb128> Sweetshark, I'm 28GB short of that bar :p
[17:42] <Sweetshark> xnox: that yields quite a lot false positives though, as the update to a new LO major (4.0->4.1) solves a lot of those (and makes _me_ need some updates in dependencies). Fixing Deps for 4.0, when we aim for 4.1 is thus a lot of wasted ressources. Yeah, I know 'rolling releases' yaddayadda ;) -- LibreOffice sure isnt rolling wrt its dependencies ...
[17:43] <seb128> some days it seems like libreoffice is more complicated that the rest of the desktop united :p
[17:43] <czajkowski> seb128: +1
[17:43] <czajkowski> some days...:)
[18:11] <mhr3> seb128, we still support powerpc?
[18:36] <asac> this facebook online accounts feature ... is that officially buggy?
[18:36] <asac> it seems to annoy me more than it does :)
[18:37] <asac> it seems to open browser for authentication regularly without being asked
[18:37] <asac> and then if i log in, i get a SECURITY WARNING PAGE
[18:37] <asac> "Success
[18:37] <asac> SECURITY WARNING: Please treat the URL above as you would your password and do not share it with anyone.
[18:37] <asac> "
[18:37] <asac> looks buggy, but sounds like success. but in fact it didnt really succeed :)
[18:38] <kenvandine> asac, yeah... facebook is doing something evil
[18:38] <asac> online accuonts still offline and opens browser again in a couple of minutes :)
[18:38] <kenvandine> redirects to a non-ssl page during login
[18:38] <kenvandine> https://developers.facebook.com/bugs/449221825171392
[18:38] <kenvandine> is the bug
[18:39] <asac> is that the only way to do this auth
[18:39] <asac> >
[18:39] <asac> ?
[18:39] <kenvandine> yes
[18:39] <asac> maybe we use one of a few variants
[18:39] <kenvandine> the only way we could work around it is to allow non-ssl
[18:39] <asac> and the one we use is something they disregard
[18:39] <kenvandine> which is not cool...
[18:39] <asac> ok... so its the official way to do it according to their api docs?
[18:39] <kenvandine> yes
[18:39] <asac> is that  risk for all applications that auth?
[18:39] <kenvandine> they've fixed it before
[18:40] <kenvandine> and it regressed
[18:40] <asac> why doesnt this go out to vendor sec etc. as a big deadl?
[18:40] <kenvandine> apparently
[18:40] <asac> feels like it might mean that now all facebook apps
[18:40] <asac> from 3rd party might reveal secrets that might allow folks to continue the session
[18:40] <asac> in clear text
[18:40] <kenvandine> right
[18:40] <asac> jdstrand: ^^
[18:40] <asac> jdstrand: is there a real risk?
[18:40] <kenvandine> jdstrand, this is why you wanted to enforce ssl :)
[18:41] <asac> if so, why hasn't this getting thorough news coverage :)
[18:41] <kenvandine> last time it happened they fixed it in just a couple days
[18:41] <kenvandine> not so responsive this time
[18:41] <sarnold> perhaps no on accesses facebook through apis?
[18:41] <asac> i am sure thats not the case
[18:41] <kenvandine> yeah, lots of people do
[18:41] <asac> that api is prominently documented
[18:42] <sarnold> asac: and if you're going to raise a stink, full-disclosure is probably the better ranting ground :)
[18:42] <asac> and its the most important web service in the world
[18:42] <asac> there must be loads of users :)
[18:42] <sarnold> so it's not just us? :)
[18:42] <kenvandine> sarnold, nope... can't be
[18:42] <asac> thats whaty i found interesting to hear
[18:42] <kenvandine> but we enforce ssl
[18:42] <asac> that there is a real sniffing risk
[18:42] <kenvandine> so it fails
[18:42] <asac> and lots of people use it ... still its not getting a big hype :)
[18:42] <asac> so i hoped we use a weird way of doing things
[18:43] <kenvandine> i think most people just don't notice the http redirect
[18:43] <kenvandine> it then gets another redirect to https
[18:43] <kenvandine> but there is one insecure redirect in the middle
[18:44] <asac> and that redirect really has private info?
[18:44] <kenvandine> during the security review this was raised as a concern and they made sure we fail on non-ssl connections
[18:44] <asac> guess so :)
[18:44] <asac> hmm
[18:44] <asac> i dont think we should just make our users believe
[18:44] <asac> that its a bug in our system
[18:44] <asac> if we break stuff like that we might want to replace it with a dialog telling people that facebook was turned off because its inseure :)|
[18:45] <asac> anyway... off ... thanks for explaining, will probably get reminded to talk more soon anyway :)
[18:45] <kenvandine> good idea
[18:45] <kenvandine> :)
[18:46] <seb128> mhr3, hey, powerpc: yes
[18:46] <jdstrand> hrmmm
[18:46] <jdstrand> I thought that https was supposed to be officially supported by them? I seem to remember them blogging about it or something
[18:48] <kenvandine> jdstrand, it is
[18:48] <kenvandine> they broke something in their login process
[18:48] <seb128> jdstrand, it's a bug, they fixed it already once but it's back
[18:48] <kenvandine> it happened a few months ago too
[18:48] <jdstrand> that sucks
[18:48] <kenvandine> and they fixed it
[18:48] <kenvandine> and now regressed
[18:48] <jdstrand> https://developers.facebook.com/bugs/449221825171392
[18:48] <jdstrand> that is a big bug number :)
[18:48] <kenvandine> hehe
[19:11] <fginther> kenvandine, xvfb issue appears to be resolved for now. The problem was that the build of another package failed, but the xvfb process was left hung (and therefore held on to port 99)
[19:12] <kenvandine> whew
[19:12] <kenvandine> thanks fginther!
[19:12] <fginther> kenvandine, no problem. it is likely to happen again someday, test should use -a when possible
[19:13] <kenvandine> fginther, i added that
[19:14] <kenvandine> but that branch failed too...
[19:14] <kenvandine> CI did rather
[19:14] <fginther> hmmm
[19:14] <kenvandine> different error
[19:14] <kenvandine> aborted after satisfy depends
[19:38] <rostam> Hi the pthread library in Ubuntu 12.04 is located at /usr/lib/x86_64-linux  for 64 bit and /usr/lib/i386-linux-gnu for 32 bit.   I am creating multi-threaded application, how could I write a generic linker command so it link to appropriate library? thx
[19:39] <sarnold> rostam: wouldn't that be gcc ... -lpthread  ?
[19:40] <rostam> sarnold: yes but the -L<path to library directory>  is my question?
[19:41] <sarnold> rostam: ah. I've never needed that, so never looked. heh.
[19:41] <sarnold> sorry :)