[17:14] <jamie1> hey how do i get wayland running?
[21:38] <craysiii> anyone know of a guide for migrating data to a new OS installation
[22:13] <darkxst> craysiii, just copy your home folder into new install
[22:13] <craysiii> right, but im wondering if there will be any negative side effects from doing it so blindly
[22:22] <darkxst> craysiii, no shouldnt be, although there can be issues if you go backwards i.e. 16.04 home back to 14.04 maybe problematic
[22:22] <craysiii> ah i see
[22:23] <craysiii> well my drive is coming in tonight, its going to be a long one :P
[22:23] <craysiii> where can i download the newest 16.04 image?
[22:23] <darkxst> cdimage.u.c
[22:24] <craysiii> you had me confused for a moment, wondering when they let c be a TLD
[22:27] <craysiii> im reading that people recommend rsync over cp because of permissions, do you think i can just get away with cp?
[22:28] <darkxst> `cp -a` would probably work
[22:28] <darkxst> or use tar
[22:34] <darkxst> I think its timestamps that are the issue with a plain 'cp'
[22:59] <Azarus> Heyo.
[23:01] <Azarus> My Ubuntu Gnome is crashing because the Intel driver and doesn't work.  I would like to know how I can install Nvidia drivers from the command line.
[23:02] <craysiii> one set
[23:02] <craysiii> sec
[23:02] <Azarus> Okay
[23:03] <craysiii> sudo add-apt-repository ppa:graphics-drivers/ppa ; sudo apt-get install nvidia-{version}
[23:03] <craysiii> https://launchpad.net/~graphics-drivers/+archive/ubuntu/ppa
[23:04] <craysiii> oh you need to apt-get update before you install
[23:04] <Azarus> Can't connect to the Internet...
[23:05] <Azarus> Can't fetch lists
[23:07] <Azarus> Will an Ethernet connection help?
[23:08] <craysiii> wait
[23:08] <craysiii> are you on the same machine now
[23:08] <Azarus> Negative
[23:08] <craysiii> ok lol
[23:08] <craysiii> yes ethernet
[23:08] <Azarus> :p
[23:08] <Azarus> Will try
[23:08] <Azarus> Brb
[23:14] <Azarus> Got an Ethernet connection, still can't connect... How do I enable you to the connection?
[23:14] <Azarus> Enable the connection *
[23:16] <craysiii> what do you have in /etc/network/interfaces
[23:18] <Azarus> Auto lo, Iface lo inet loopback
[23:19] <Azarus> And a comment
[23:19] <craysiii> you need to add your eth
[23:20] <Azarus> Eth0?
[23:20] <craysiii> https://help.ubuntu.com/community/NetworkConfigurationCommandLine/Automatic go to "Configuring an interface"
[23:20] <craysiii> yeah
[23:20] <craysiii> i would assume
[23:23] <Azarus> Cannot find device Eth0 or eth1...
[23:25] <craysiii> o.O i just checked on my machine and its eno1
[23:25] <craysiii> ifconfig
[23:25] <craysiii> this is also more a general linux question you might have more luck there ##linux
[23:26] <Azarus> Okay thanks 👍


[00:48] <belkinsa> I might try that layout idea on another page that might need it
[12:51] <knome> belkinsa, sure, or you can poke me to work on that page as well.
[12:53] <knome> the wiki markup for that isn't the cleanest, so you probably want to avoid that for pages that are edited a lot
[16:57] <knome> belkinsa, also online on irc.
[16:57] <belkinsa> Hmmm?
[16:57] <knome> if you want to follow up on the mailing list discussion faster
[16:58] <belkinsa> True, true, but I think I want to have everyone able to read what we are talking about at their own pace.
[16:58] <knome> or we can discuss in irc and send the outcome to the mailing list. but both ways work for me :)
[16:59] <belkinsa> Sure.
[17:13] <belkinsa> And I ended up changing my siggy to something better then just having my User Wiki page link.
[17:14] <knome> :)
[17:15] <knome> i guess i should think about including that in my sig
[17:23] <belkinsa> knome, I understand now the differnce from what you want and the Recent Changes page
[17:29] <knome> do you think that is something that would help you track what you originally wanted without having to update the tags for every release?
[17:29] <belkinsa> Yeah.
[17:29] <knome> ok, cool
[17:30] <belkinsa> Might make clean up and editing easier
[17:30] <belkinsa> We just need some system that works for us the team members and the users also
[17:31] <knome> if there's a new page, it's easy to tag that
[17:31] <knome> becuase it's always the current month
[17:31] <belkinsa> But wouldn't that create too many tags?
[17:34] <knome> one per month
[17:34] <knome> what is "too many"?
[17:34] <knome> the idea would obviously to keep the tags to minimum
[17:34] <belkinsa> One per month maybe too many in the long run.
[17:35] <knome> we wouldn't want a page that's 5 years old
[17:35] <knome> so it would either be deleted, or marked as reviewed
[17:35] <belkinsa> Yeah, but think what will happen in five years.
[17:35] <belkinsa> Or ten.
[17:36] <knome> i don't think it's a problem even if we have 50 tags if they're all useful,
[17:37] <belkinsa> Heh.  Also, another issue that I see that how many users who work on wiki pages will tag their pages.  By users, I mean the ones who are outside of the team.
[17:37] <knome> not many i suppose
[17:37] <knome> but that will always be a problem
[17:38] <knome> once we have all pages tagged with months (and ideally with other meaningful tags), it's easy to keep on tagging new pages
[17:38] <belkinsa> Unless it was restricted for the users in the team, but is that what we want?
[17:38] <knome> why should it be?
[17:38] <belkinsa> It is*
[17:38] <belkinsa> but is that we don't want*
[17:39] <belkinsa> My reasoning behind is to keep everything under *OUR* control and to our standards.
[17:39] <knome> i don't see a reason why we would want to restict tagging to team as long as people know the guidelines
[17:39] <knome> that means there will be much more work burden for the team
[17:39] <belkinsa> Yeah, but I think they are not visble or something.
[17:40] <knome> and the non-team members will never learn tagging
[17:40] <knome> and the threshold to join the team and start tagging is bigger
[17:40] <belkinsa> Ah.
[17:41] <knome> in the same way as the wiki is editable by anyone, so should be the tags
[17:41] <belkinsa> Well, I know that wiki admins are notified of changes, right?
[17:41] <knome> i'm quite sure people who do not know about tagging won't tag
[17:41] <knome> are if they are subscribed to pages
[17:41] <knome> you can subscribe as well
[17:41] <belkinsa> Yes, but I think I would like to have a digest or something instead.
[17:42] <belkinsa> AFK-Lunch
[17:48] <knome> i don't think there are digest deliveries, but you could subscribe to part of the pages
[17:48] <knome> and share the whole wiki in smaller parts for the team
[17:51] <knome> what's the CategoryDocumentation used for?
[17:51] <knome> that doesn't seem to be a large, or logical group
[17:52] <belkinsa> I like that idea using categories to split up the work, but still that could be a large sum of pages.
[17:56] <belkinsa> I agree, WTF is CategoryDocumentatio.
[17:56] <belkinsa> +n
[17:56] <belkinsa> Should I ask on the list?
[18:00] <knome> i don't know. doesn't hurt to.
[18:00] <belkinsa> Thanks, on it!
[18:18] <belkinsa> Wow, another month with 100 threads in our mailing list and fast filling in the first two weeks.
[18:23] <knome> front page for https://help.ubuntu.com/community/ updated.
[18:36] <belkinsa> Thumbs up! X2
[18:42] <knome> if you are bored, go through the list of pages at https://help.ubuntu.com/community/Tag/Deletion/List
[18:42] <belkinsa> I will, but I'm studying for my finals.
[20:13] <knome> http://open.knome.fi/2013/12/07/efforts-on-documentation/
[20:14] <belkinsa> You rock.
[20:15] <belkinsa> And this is what I tweeted: Svetlana Belkin @Barsookain now
[20:15] <belkinsa> knome of the Doc-Team posted his reasons for joining and working with us:http://open.knome.fi/2013/12/07/efforts-on-documentation/ …
[20:16] <knome> ta
[20:16]  * knome bows
[20:19] <belkinsa> Speaking of blogging, I need to post something in The Ubuntu Sense.  But what.
[20:20] <cprofitt> nice to see so much work being done... I am dealing with a sick kid today.
[20:21] <knome> cprofitt, get well soons for your kid
[20:22] <belkinsa> Ditoo
[20:22] <belkinsa> ditt*
[20:22] <belkinsa> ditto**
[21:29] <belkinsa> knome: You think your layout could work for this page: https://wiki.ubuntu.com/DocumentationTeam/Wiki ?
[21:29] <knome> i guess, i don't know if it needs that though
[21:30] <belkinsa> Or is it just hard to follow in general?
[21:32] <knome> that might be it
[21:32] <belkinsa> Yeah, I think nskaggs said that in the vUDS.
[21:32] <knome> i think the header for those pages could be improved.
[21:32] <belkinsa> It's his action item to work on that, not mine.
[21:32] <belkinsa> Yeah, that too.
[21:33] <belkinsa> nskaggs = ballons?
[21:33] <knome> yep
[21:34] <belkinsa> I was rewatching the vUDS session and I was thinking about what I added to the action items...I still don't get where or what I was thinking when I added my item
[21:35] <knome>  maybe the pad?
[21:35] <belkinsa> Could be.
[21:37] <belkinsa> But for the Ubuntu Docs, themselves, I agree that we need a workflow of what we do in each cycle, but someone else has to take that since I'm not doing system docs
[21:38] <knome> you could document the rest
[21:38] <belkinsa> As in?
[21:38] <knome> the non-system docs related tasks
[21:38] <belkinsa> Gotcha and yeah, I can.
[21:39] <belkinsa> I updated the action item to say workflow of the wiki part.
[21:41] <belkinsa> I will make a copy of the page that I linked to my sandbox so we can work on it.
[21:41] <knome> sure
[21:43] <belkinsa> https://wiki.ubuntu.com/belkinsa/sandbox/wikiworkflow
[21:44]  * belkinsa goes back studying
[22:49] <belkinsa> God, I feel sad for the folks who need to check their e-mails in the team.
[22:49] <knome> what images are you referring to in your email?
[22:49] <belkinsa> The ones that were included in each box
[22:50] <knome> can't see any in the current menu banner
[22:50] <belkinsa> Yeah, I forgot that there wasn't any.
[22:50] <belkinsa> But I  like the idea, it's more modern.
[22:50] <belkinsa> and cleaner


[00:12] <maas_noob> Hi there.. looking for a little help.. I've just setup a "vanilla" maas server following the instructions here: http://maas.io/get-started... my nodes are connected to IPMI so I reboot into pxe and the node itself seems to get a DHCP response from the maas server and proceeds to start the boot process. but then it gets stuck with: http://<IP_ADDRESS>/2009-04-04/meta-data/instance-id' failed. error.
[00:13] <maas_noob> the error message says "Failed to establish new connection".
[00:14] <maas_noob> after cloud-init fails out I end up at an ubuntu login screen but I don't see any nodes getting added into maas.
[00:46] <mup> Bug #1635069 opened: [web UI] subnet settings are dangerously easy to change <docteam> <MAAS:New> <https://launchpad.net/bugs/1635069>
[03:44] <mup> Bug #1635097 opened: Can't assign SSH-Keys to user via maas-cli <MAAS:New> <https://launchpad.net/bugs/1635097>
[03:47] <mup> Bug #1635097 changed: Can't assign SSH-Keys to user via maas-cli <MAAS:New> <https://launchpad.net/bugs/1635097>
[03:50] <mup> Bug #1635097 opened: Can't assign SSH-Keys to user via maas-cli <MAAS:New> <https://launchpad.net/bugs/1635097>
[04:14] <mup> Bug #1635107 opened: maas.power Error changing power state (on) while commissioning the node <MAAS:New> <https://launchpad.net/bugs/1635107>
[04:17] <mup> Bug #1635107 changed: maas.power Error changing power state (on) while commissioning the node <MAAS:New> <https://launchpad.net/bugs/1635107>
[04:20] <mup> Bug #1635107 opened: maas.power Error changing power state (on) while commissioning the node <MAAS:New> <https://launchpad.net/bugs/1635107>
[05:14] <sk_> hi , I have setup MAAS(version 1.9) using VM's (ubuntu 14.04). I want to deploy a juju charm on the node having storage disk attached. I have created one called sdb.
[05:15] <sk_> But when i deploy the charm, I see that the status in MAAS UI us Failed Deployment for the node
[05:15] <sk_> I see the below errror in the MAAS install logs
[05:15] <sk_> Installing for i386-pc platform. grub-install : error: unable to identify a filesystem in hostdisk//dev/sdb; safety check cant be performed failed to install grub! Command: ['install-grub', 'tmp/tmpqwTtyG/target', '/dev/sdb]'
[05:15] <sk_> can anyone please help me in debugging this issue
[05:23] <Mohit> Hello
[14:14] <sk_> Hi team, I deployed a charm with MAAS as cloud provider, the charm got deployed successfully, but in the installation logs on MAAS console, i see this error message : Error: /dev/sdb: unrecognised disk label
[14:14] <sk_> can anyone please help me on this
[15:15] <mup> Bug #1635298 opened: Ability to assign deployed MAAS nodes to a "group" or "project" would be helpful <MAAS:New> <https://launchpad.net/bugs/1635298>
[18:03] <mup> Bug #1633468 changed: [Subnets page, DD] Add a warning message when Device discovery is disabled <ui> <MAAS:In Progress by newell-jensen> <https://launchpad.net/bugs/1633468>
[18:42] <swjen> Looking for some help. I've setup a new MAAS server and enabled my hosts to network boot (PXE). upon booting, they get a DHCP response from maas and start the "Booting under MAAS..." process.. but I never see the new machine pop up in the MAAS machine list.
[20:01] <brendand> swjen, which version?
[20:30] <swjen> Hi brendand. I am running MAAS 2.0.0
[20:35] <brendand> swjen, what do you see in /var/log/maas/rsyslog/ on the maas server?
[20:43] <swjen> brendend: I don't see anything actually. the directory is empty.
[20:43] <brendand> swjen, not even maas-enlisting-node?
[20:44] <swjen> nope.. completely empty./
[20:48] <swjen> brendand: if a little backstory helps, All I have done is follow the "quick start" steps here: http://maas.io/get-started. I did notice that the maas server has "maas_region_controller" installed, but it does not have "maas_cluser_controller" installed. from some googling I wasn't sure if this was necessary or not.
[21:10] <spaok> does anyone know if you can set the upstream DNS and NTP for MAAS 2.0 via the maas commandline
[21:11] <spaok> ah, found it
[21:34] <swjen> brendand: are you still here?
[21:38] <brendand> swjen, if you can get console access to the machine you should watch what that's doing. even better if you can copy it somewhere and show us
[21:38] <brendand> it's a bit late for me so i might stop responding
[21:42] <brendand> swjen, try back tomorrow if i don't
[21:43] <swjen> brendand: thanks! I do have IPMI access and have been watching the systems that way.. difficult to copy out stuff during the process but I have taken some screen shots.. basically.. immediately after the PXE boot I see "Booting under MAAS direction..."


[03:13] <JJ__> hi
[03:18] <JJ__> Hello?
[09:22] <rvba> bigjools: please have another look at my branch (https://code.launchpad.net/~rvb/maas/retry-power-changes/+merge/227884);  I've kept the hardcoded list of power types that support querying for now.  The way we're using the power type registry is a bit nasty: the objects it stores are JSON representation of the fields the power type requires, not proper objects that can be extended cleanly.  If we're going to
[09:22] <rvba> extend this, I think it's worth taking a step back and seeing if we can't refactor this a bit before we had more cruft on top of what we have now.
[09:22] <bigjools> rvba: sure
[09:23] <bigjools> gimme a few, just writing an email
[09:23] <rvba> No worries
[09:24] <rvba> bigjools: also, if you have time after that, I'd like to talk about error reporting with you.
[09:38] <bigjools> rvba: first comment - the test_change_power_state_marks_the_node_broken_if_exception test won't fail if there's no Failure.  You need to do d.addBoth() and check the result is a Failure.
[09:39] <bigjools> did you ever get the test to fail?  :)
[09:47] <bigjools> rvba: see self.assert_fails_with() which does what you want
[09:49] <rvba> bigjools: I actually *did* get the test to fail…
[09:49] <rvba> bigjools: if you apply http://paste.ubuntu.com/7846674/ the test fails.
[09:51] <bigjools> rvba: wrong kind of failure
[09:51] <bigjools> if there is no failure at all, the test will pass
[09:51]  * bigjools writes on MP
[09:51] <rvba> bigjools: I get http://paste.ubuntu.com/7846676/, that's what I'm expecting
[09:52] <rvba> i.e. the node not being marked as broken
[09:52] <bigjools> rvba: wait for my MP comments, the test needs a simple fix, that's all
[09:55] <rvba> bigjools: oh, I see what you mean now
[09:55] <bigjools> :)
[09:55] <bigjools> rvba: there is a test helper that does it all in one line
[09:55] <rvba> Right.
[09:59] <bigjools> rvba: see email
[10:04] <bigjools> also a useful nugget is that you can pass debug=True to make_factory() which gives you a bunch of info about Deferreds when debugging your tests (full stack trace of where they were created is tremendously useful)
[10:06] <rvba> bigjools: hum, looks like you need to "return" assert_fails_with()
[10:06] <bigjools> rvba: ah yes
[10:06] <bigjools> returns the deferred to the reactor
[10:08] <rvba>         d = power.change_power_state(
[10:08] <rvba>             system_id, power_type, power_change, context)
[10:08] <rvba>         d.addErrback(check)
[10:08] <bigjools> rvba: well what you can do, since you're adding an extra check is this (let me just write it down)
[10:08] <rvba>         return assert_fails_with(d, Exception)
[10:08] <rvba> bigjools: this ^ works.
[10:08] <rvba> And check is:
[10:08] <rvba>         def check(failure):
[10:08] <rvba>             # The node has been marked broken.
[10:08] <bigjools> rvba: you don't need the check func you can do a lambda
[10:08] <rvba>             self.assertThat(
[10:08] <rvba>                 client.mark_node_broken, MockCalledOnceWith(system_id))
[10:08] <rvba>             raise failure.value
[10:09] <bigjools> d.addErrback(self.assertThat, ...)
[10:09] <bigjools> not a lambda... heh
[10:10] <bigjools> rvba: ok?
[10:10] <rvba> Having a cleanly defined check() method is easier on the eyes.
[10:10] <rvba> I think.
[10:10] <bigjools> rvba: I massively disagree
[10:10] <bigjools> inline funcs are to be avoided at all costs
[10:10] <bigjools> well, not all, but they are hideous
[10:11] <rvba> Not in tests when they encapsulate a tiny bit of logic that is nice to see isolated from the rest of the code.
[10:12]  * bigjools continues to disagree
[10:12] <rvba> bigjools: in this case, I need to do two things in check(): the test itself and then re-raise the exception
[10:12] <bigjools> rvba: no you don't need to re-raise
[10:12] <bigjools> if you add the errbacks in the right order, anyway
[10:12] <rvba> bigjools: if I don't re-raise, the exception is swalled and assert_fails_with fails
[10:13] <rvba> oh, I see.
[10:13] <bigjools> rvba: d = self.assert_fails_with ...
[10:13] <rvba> assert_fails_with returns a deferred
[10:13] <rvba> bigjools: yeah
[10:13] <bigjools> d.addErrback(...
[10:17] <rvba> bigjools: so that's what you're suggesting then? http://paste.ubuntu.com/7846751/
[10:17] <bigjools> rvba: no need to re-assign d
[10:18] <bigjools> but basically, yeah
[10:18] <rvba> It's not failing properly when no exception is raised…
[10:19]  * rvba reads the documentation for d.addErrback…
[10:20] <rvba> bigjools: http://paste.ubuntu.com/7846769/ that's better
[10:21] <bigjools> ah yes sorry, forgot the extra arg :)
[10:21] <bigjools> normally it's not needed but because you have other callbacks ...
[10:23] <rvba> Right.
[10:43] <bigjools> rvba: that;s interesting.  The test func where you added the yield doesn't have inlinecallbacks
[10:43] <rvba> bigjools: ah!
[10:44] <bigjools> It's fine, but ...
[10:44] <bigjools> rvba: is assert_fails_with not on the testcase?
[10:44] <bigjools> self.assert_fails_with ... ?
[10:44] <rvba> No, it's not.
[10:45] <bigjools> huh, weird.  Someone must have patched it in on the LP tests then
[10:46] <bigjools> rvba: I reckon we should change our test cases to have it
[10:47] <rvba> bigjools: it's only used in two places now (including the one I'm adding) so the fix should be tiny.
[10:49] <rvba> bigjools: how do you explain "yield method()" works without the inlinecallbacks decorator?
[10:49] <bigjools> it's a generator...
[10:50] <rvba> But how come the test runner deals with that transparently?
[10:51] <bigjools> I suspect you don't need the run_tests_with
[10:51] <bigjools> it's never hitting the reactor
[10:53] <rvba> bigjools: when I call power.change_power_state() without explicitly passing a reactor, the default one gets used…
[10:53] <bigjools> I mean the tests are not relying on it
[10:55] <rvba> But when 'yield pause(waiting_time, reactor)' gets called, this should hit the reactor shouldn't it?
[11:08] <bigjools> rvba: not if inlinecallbacks is missing it's not :)
[11:09] <rvba> bigjools: but I've got other test methods with inlinecallbacks.  They pass with or without it.
[11:09] <bigjools> meh, the lack of an easy way to run a quick image import on canonistack is annoying
[11:09] <bigjools> need a sources file now
[11:09] <bigjools> rvba: right, because the tests are not relying on the reactor spinning, just the clock
[11:12] <rvba> bigjools: but the clock defaults to twisted.internet.reactor
[11:12] <bigjools> rvba: not the one you're relying on
[11:13] <rvba> bigjools: I'm talking about other tests which don't use Clock() at all.
[11:13] <bigjools> I'm not doing a good job of explaining, sorry
[12:27] <jtv> Who wants to review my database migration fix for trunk?  https://code.launchpad.net/~jtv/maas/bug-1347579/+merge/228099
[12:27] <bigjools> jtv: I would be delighted to
[12:27] <jtv> Thank you.
[13:40] <allenap> Please can a review get I? https://code.launchpad.net/~allenap/maas/rpc-get-preseed-data-helper/+merge/228086
[13:40] <rvba> allenap: I'll look at it in a sec
[13:40] <allenap> rvba: Thanks.
[13:52] <bigjools> allenap: pserv logging.  it's, erm, not doing a lot
[13:52] <bigjools> is the python logger wired up?
[13:53] <bigjools> to twisted's, I mean
[13:56] <allenap> bigjools: What’s happening specifically?
[14:08] <bigjools> allenap: two problems:
[14:09] <bigjools> 1. logger.info() is not appearing in the log
[14:09] <bigjools> 2. the log is swamped with RPC connection reporting which is annoying
[14:13] <roaksoax> bigjools: so I was thinking, would it be a good idea to start working on Unified Logging?
[14:13] <roaksoax> since most of the new logging that we will be doing in all of the work
[14:13] <roaksoax> will need to end up in a unified log
[14:13] <bigjools> roaksoax: that's a terrible idea right now, but when everything else in progress is done, it will be an excellent idea
[14:15] <roaksoax> bigjools: right, but we need to start consolidating logs in a single location anyway, instead of creating new logs for new stuff
[14:16] <allenap> bigjools: I shall look.
[14:16] <bigjools> roaksoax: there is nothing that I know of that is going to require a new log
[14:17] <allenap> roaksoax: Yeah, let’s just clean up what we have for now, get over the hump, no new development right now. In a month we can do something a bit more structured.
[14:18] <bigjools> allenap: thanks.
[14:23] <allenap> bigjools: logger.info() probably not appearing because we’re not configuring the standard lib's logging in pserv.
[14:23] <bigjools> allenap: I think we need to build some retrying backoff algorithm into getClient()
[14:23] <bigjools> allenap: yes that;s what I guessed at 14:52
[14:24] <bigjools> getClient fails hard and quick, and this is not a normal situation, we expect RPC to always be up.  It could be that we're trying to access too quickly after startup.
[14:25] <allenap> bigjools: We can wire up Twisted’s log to the standard lib’s logging with PythonLoggingObserver.
[14:25] <allenap> And that’s probably a good thing to do.
[14:25] <bigjools> yes
[14:27] <bigjools> allenap: how evil would it be to put inlineCallbacks on __init__ ? :)
[14:27] <bigjools> I need a startup pause for the image checking service because of this getClient thing
[14:30] <allenap> bigjools: We could add a queue to ClusterClientService for getClient requests.
[14:30] <allenap> bigjools: inlineCallbacks on __init__ won’t work.
[14:30] <bigjools> yeah I figured
[14:45] <bigjools> allenap: client(GetBootSources) is returning a string.  Is that right?
[15:03] <allenap> bigjools: Nope, it returns a {“sources”: {…lots of stuff…}}. See GetBootSources.response for the schema.
[15:03] <bigjools> allenap: I am getting a very very weird error
[15:03] <bigjools> let me paste
[15:04] <bigjools> allenap: http://paste.ubuntu.com/7848044/
[15:04] <bigjools> the returned data looks ok
[15:05] <bigjools> oh no.... do I really have to do returned_data['sources'] ...
[15:09] <allenap> bigjools: Yep, that’s it.
[15:09] <bigjools> allenap: so did that, got further: http://paste.ubuntu.com/7848059/
[15:09] <bigjools> I feel we're lacking in some integration tests
[15:11] <allenap> Yep :)
[15:12] <bigjools> allenap: seriously - there's too much connection mocking, we really need end-to-end tests
[15:12] <allenap> bigjools: I’m not sure that the response that GetBootSources gives was designed to exactly slot into existing code. It was designed to make sense first of all :)
[15:12] <rvba> bigjools: I know you're busy right now but here is the MP that implements what we talked about earlier: https://code.launchpad.net/~rvb/maas/improve-broken-state/+merge/228132
[15:13] <bigjools> roaksoax: ack
[15:13] <allenap> bigjools: You’re the one wiring it up for the first time, so you get to write the integration tests.
[15:13] <bigjools> rvba: ack
[15:13] <bigjools> ffs
[15:13] <bigjools> allenap:yay?
[15:18] <allenap> bigjools: Think of how good you’ll feel when it’s done :)
[15:19] <bigjools> allenap: I always enjoy finishing someone else's work ;)
[15:21] <allenap> bigjools: Great, I think I have some more for you :)
[15:23] <bigjools> allenap: arf!
[15:23] <bigjools> allenap: do we have any infra to set it up in a test?
[15:32] <allenap> bigjools: There’s ClusterRPCFixture for the other direction. You could replicate that for cluster->region.
[15:43] <bigjools> allenap: right
[15:45] <bigjools> allenap: so I see the problem
[15:45] <bigjools> the keyring data is returned in sources, but the importer code wants it in a file
[15:45] <bigjools> I love it when the rabbit hole deepens like this
[15:46] <bigjools> so I can't just pass that sources obj that rpc returns
[15:46] <bigjools> what I want to know is, how is the file written normally when the celery job runs
[15:49] <bigjools> argh
[15:50] <allenap> bigjools: That’s done in boot_resources.import_images, right? write_all_keyrings
[15:50] <bigjools> argh arfg argf
[15:52] <bigjools> allenap: the rpc code has a bug
[15:52] <bigjools> it's returning the data in a field with an incorrect name
[15:52] <bigjools> "keyring" is the filename, "keyring_data" is the, well, data
[15:52] <bigjools> but the call uses the former for the latter
[15:54] <bigjools> allenap:
[15:54] <bigjools>         keyring_data = source.pop("keyring_data")
[15:54] <bigjools>         source["keyring"] = b64decode(keyring_data)
[15:54] <bigjools> why!
[15:55] <bigjools> thinko or deliberate?
[15:59] <allenap> bigjools: Deliberate. BootSource.to_dict() is the one smoking crack for the benefit of Celery. The cluster never needs to know the filename. To the cluster the keyring is the keyring, it does not need to be qualified with a _data suffix. Once the Celery task is gone we can fix BootSource.to_dict().
[15:59] <bigjools> allenap: I'm changing it back to keyring_data, because it's the least path of resistance
[16:00] <allenap> (It’s smoking crack because the model is where the base-64 encoding is happening, instead of where the task is dispatched.)
[16:00] <bigjools> the code in import_resources relies on all of this
[16:00] <bigjools> it's not just celery
[16:00] <allenap> bigjools: Jumping off a cliff is a quick way to the bottom.
[16:00] <bigjools> \o/
[16:01] <bigjools> I prefer keyring_data tbh.  I doesn't leave me wondering if it's a filename or the data
[16:01] <bigjools> keyring on its own is ambiguous
[16:01] <bigjools> and in fact more confusing because the gpg executable uses --keyring=<filename>
[16:02] <allenap> bigjools: Either way, fix BootSource.to_dict() when you delete the import_boot_images task.
[16:03] <allenap> bigjools: Note that everything assumes that keyring_data is base-64 too. You’ll need to disabuse everything of that notion.
[16:05] <bigjools> allenap: sigh :(
[16:05] <bigjools> allenap: for now I am going to ensure that everything RPC is bytes and not b64
[16:05] <bigjools> it's a good cutpoint.
[16:06] <allenap> Yeah.
[16:43] <bigjools> allenap: I have a dilemma
[16:44] <bigjools> there's a time when the importer code needs to deal with both b64 and bytes for the keyring
[16:44] <bigjools> before both the scheduled job and manual import are migrated to rpc
[16:44] <allenap> The only way out is through.
[16:45]  * allenap is the font of aphorisms today.
[16:46] <allenap> bigjools: Well, you /could/ name one "keyring_data" and the other, oh, I don’t know, just “keyring”? :)
[16:46] <bigjools> allenap: fooey
[16:47] <bigjools> doesn't help anyway
[16:47] <bigjools> all the underlying code assumes b64
[16:47] <bigjools> can I detect which it is and DTRT
[16:51] <allenap> bigjools: You could try decoding base-64 and catch exceptions, but that’s not without risk.
[16:51] <bigjools> yeah
[16:51] <bigjools> I'll decode it when the task is called
[16:51] <allenap> Yeah, that works.
[16:51] <bigjools> not when pumped right into the underlying code :/
[16:51] <allenap> Perfick.
[16:52] <bigjools> then when the task gets removed eventually, all will be well
[16:59] <bigjools> allenap: so there is a slight flaw in the plan for detecting when to run a download :(
[16:59] <bigjools> although it's not the end of the world
[16:59] <bigjools> maas.meta only gets updated when there is something to download.  So once it's a week old, we run the downloads hourly :)
[17:11] <bigjools> allenap: bug 1271188 is getting more attention now, and I am also a little frustrated.  Let's stick it on the list while we're doing this work?
[17:18] <bigjools> allenap: if you want a gander I have a WIP MP, I'm offski now.  There's a bit more to do to stop that hourly checking.
[17:18] <bigjools> https://code.launchpad.net/~julian-edwards/maas/replace-celery-download-job-with-pserv/+merge/228168
[17:25] <allenap> bigjools: Ha! We could ensure that maas.meta is touched after each successful run, or use another reference file.
[17:26] <allenap> bigjools: I’ll be back online later, but I’m off now too. I’ll try to have a look at that wip.


[07:49] <IntuitiveNipple> I need some assistance packaging a plug-in - two aspects: 1) existing package has no XPI so I've got sort that, and 2) how to correctly configure the package since it builds and installs binaries?
[09:48] <asac> IntuitiveNipple: usually a  good thing is to build a .xpi
[09:48] <asac> and then let the "xpi.mk" take care of the rest
[09:49] <asac> most build systems should be able to produce such a xpi ... which should be good enough as an intermediate step
[09:49] <IntuitiveNipple> asac: I was trying to figure that bit out. I'm working on bug #146324
[09:50] <IntuitiveNipple> Am I correct in thinking that the basics for getting the binaries into the correct locations is covered here: http://developer.mozilla.org/en/Bundles
[10:23] <gnomefreak> im feeling alot better but dr=octor would like to keep me one more night to see if i have anymore problems (he said "just in case")
[10:48] <asac_> IntuitiveNipple: no. a bundle is something different
[10:48] <asac_> IntuitiveNipple: only thing you need to take care of is making a proper .xpi out of it
[10:48] <asac_> the rest will be done by xpi.mk
[10:48] <asac_> (no need for you to think about where and how to install that in the filesystem)
[10:49] <asac_> IntuitiveNipple: if you ask whether a xpi has that structure, then yes. but usually build systems of extensions that have binary components already do that
[10:50] <IntuitiveNipple> asac: OK, really? The current package does the regular debian installation thing but I've tried to use the CDBS xpi options to replace the paths it had hard-coded in debian/rules for shared-library locations and sym-links
[10:51] <asac_> IntuitiveNipple: look at upstream source. if that has a build system which can produce .xpi ... dump the packaging and do it the _modern_ way
[10:52] <asac_> you can do it the old way, but thats discouraged :)
[10:53] <IntuitiveNipple> asac: The upstream way is the 'old' way unfortunately, I'm replacing that with the wiki template XPI method, hence why I'm asking questions because bringing the two together is rather confusing
[10:54] <asac_> IntuitiveNipple: the upstream way is the old way?
[10:54] <asac_> if upstream is debian, then thats not upstream :)
[10:54] <asac_> but the debian way :-P
[10:55] <IntuitiveNipple> no, upstream is the developers of the extension; they added debian packaging in 2006
[10:56] <IntuitiveNipple> so basically I just need an install.rdf then
[10:57] <IntuitiveNipple> The package is a standalone VRML/X3D browser, with mozilla plugin interface. There's no visible 'extension' as such, in terms of chrome, etc.
[10:57] <asac_> oh you are not talking about an extension
[10:59] <IntuitiveNipple> No, its 100% plug-in, but the report asked for a XPI package. I discovered the bug-report last night whilst looking for a decent VRML plug-in, and thought I'd try and get it sorted out while I'm at it
[11:00] <asac> IntuitiveNipple: plugin != extension
[11:00] <asac> if its a plugin then you dont need to do this xpi thing
[11:02] <IntuitiveNipple> Hmmm. I did wonder, but I went by what Saša Bodiroža said in the report
[11:02] <gnomefreak> asac: what are the chances of Mozilla adding support for import/export of junk settings. I will file bug for tbird 3 if you think it is at all possible
[11:02] <asac> gnomefreak: what import/export format?
[11:03] <asac> just from and to tbird?
[11:03] <gnomefreak> any or a common one say in .csv (or whatever contact format. tbird,seamonkey, ect..
[11:04] <asac> gnomefreak: search bugzilla and if you are its not yet there file a wishlist bug
[11:04] <asac> gnomefreak: also file a bug in LP and link it to the wishlist bug ;)
[11:04] <gnomefreak> this way i can export it and inport it for when a reinstall or whatever
[11:04] <gnomefreak> asac: will do ;)
[11:06] <IntuitiveNipple> asac: Is there a standard template for installing plug-ins so they are available to all mozilla browsers, and/or alternatives ?
[11:06] <gnomefreak> IIRC plugins are packaged as debian packages like any other normal package
[11:07] <gnomefreak> example enigmail
[11:08] <gnomefreak> if nonfree something like flashplugin set up
[11:08] <gnomefreak> IntuitiveNipple: you can look at ubufox maybe to give you an idea
[11:09] <IntuitiveNipple> gnomefreak: yeah, I was thinking of the flash example, because regardless of free/non-free, the linkages are going to be the same.
[11:10] <IntuitiveNipple> As there was the XPI template, I was wondering if there was similar for a package, maybe a CDBS module
[11:10] <gnomefreak> the problem with flash is it uses a script to grab the tarball (flash names thier tarballs for each release the same. so we have to change the md5sum of tarball or you get install failed
[11:11] <gnomefreak> IntuitiveNipple: no plugins that i know of use XPI
[11:11] <IntuitiveNipple> yeah, but the install-location / sym-links part will be the same for all 'well-behaved' plug-ins
[11:12] <gnomefreak> this has got to suck :(  "openoffice.org-evolution: Depends: openoffice.org-core (= 1:2.4.1-9ubuntu2)"
[11:12] <gnomefreak> i use 3.0
[11:13] <IntuitiveNipple> Mozilla recommend 'Bundles' and give examples for plugins
[11:13] <gnomefreak> yay 3.1 updates ;)
[11:15] <gnomefreak> brb reboot
[11:39] <asac> fta: https://bugs.edge.launchpad.net/ubuntu/intrepid/+source/firefox-3.0/+bug/275410 ... could you include that fix and give credits to slangasek in changelog?
[11:47] <asac> fta: nm ... done
[13:12] <lfaraone> Hey, is there any chance of getting xulrunner 1.9 in the repos?
[13:12] <lfaraone> I have a package that requires that to function.
[13:13] <james_w> lfaraone: xulrunner 1.9 is in the repos
[13:13] <james_w> it's just called xulrunner-1.9, and doesn't build python-xpcom, which is the package you need to be >= 1.9
[13:14] <lfaraone> james_w: I'm asking upstream if their package can make do with 1.8, if not...
[13:15] <james_w> the python-xpcom stuff is now shipped in the xulrunner-1.9 package, but isn't in the standard python path, so you may be able to get it work that way
[13:15] <lfaraone> james_w: yeah, they _need_ xpcom to be >1.9
[13:15] <lfaraone> james_w: So, where exactly is it?
[13:16] <james_w> where is what?
[13:16] <lfaraone> james_w: wait, doesn't firefox3 require 1.9?
[13:17] <lfaraone> james_w: I mean where in the system is python-xpcom 1.9 located, since it's not in PYTHONPATH.
[13:17] <james_w> dpkg -L xulrunner-1.9 | grep xpcom
[13:17] <james_w> assuming you are on Intrepid
[13:17] <lfaraone> james_w: I'm not.
[13:18] <james_w> /usr/lib/xulrunner-<IP_ADDRESS>/libpyxpcom.so
[13:18] <james_w> /usr/lib/xulrunner-<IP_ADDRESS>/libxpcom.so
[13:18] <james_w> /usr/lib/xulrunner-<IP_ADDRESS>/python/xpcom
[13:18] <james_w> ...
[13:19] <james_w> In [1]: import sys
[13:19] <james_w> In [2]: sys.path.append("/usr/lib/xulrunner-<IP_ADDRESS>/python/")
[13:19] <james_w> In [3]: import xpcom
[13:19] <james_w> though I don't know if python-xpcom is co-installable with xulrunner-1.9. That could cause some problems
[15:05] <asac> fta: i have found a bug :)
[15:05] <asac> --- mozilla.orig/browser/branding/unofficial/content/jar.mn
[15:05] <asac> +++ mozilla/browser/branding/unofficial/content/jar.mn
[15:05] <asac> @@ -1,7 +1,7 @@
[15:05] <asac> -browser.jar:
[15:05] <asac> +browser-browser.jar:
[15:06] <asac> shouldnt that be browser-branding.jar ?
[16:19] <fta2> asac, indeed, yes. strange it worked anyway
[16:24] <fta2> asac, insn't NAME="${NAME%%-3.0}" a bashism ?
[16:27] <bdmurray> asac: I've updated bug 277063, do you need anything more?
[16:32] <fta2> asac, ff3.0 #359 is not mergable in the 3.1 branches
[16:33] <asac> fta2: how comes?
[16:34] <fta2> is assumes the final APPNAME is firefox
[16:34] <fta2> it
[16:36] <asac> fta2: right. isnt our APPNAME firefox-3.1?
[16:36] <fta2> it is
[16:37] <asac> fta2: also the commit didnt introduce that ... the part you are complaining about was there before
[16:37] <asac> fta2: if its firefox-3.1 then all should be fine imo
[16:37] <fta2> http://paste.ubuntu.com/55312/
[16:38] <asac> ok stupid me
[16:38] <fta2> i have an easy fix the 2 hardcoded -3.0 but line 30 is not good
[16:38] <asac> didnt look carefully ... and looked at 362 ;)
[16:41] <fta2> this whole patch will not work in 3.1, i'll think about it later today
[16:41] <asac> fta2: cant we sed the fallback APPNAME?
[16:42] <asac> e.g. if META_EXISTS use the versioned one ... otherwise the unversioned one?
[17:44] <fta2> asac, http://ubuntuforums.org/showthread.php?t=941495
[17:47] <asac> fta: cool. people already adapt the "managed" mode ;)
[17:47] <asac> most likely without a clue on what they are doing there :(
[18:00] <sebner> asac: hmm? hmm? hmm?
[18:01] <asac> sebner: whats up?
[18:01] <sebner> asac: managed mode? *confused*
[18:01] <asac> sebner: read README.Debian
[18:01] <asac> of network-manager
[18:01] <asac> or the email to ubuntu-devel i sent yesterday ;)
[18:02] <sebner> asac: I just read something about ifupdown but my english isn't that perfect and I was lazy reading to end ^^
[18:02] <asac> sebner: then try README.Debian for the short version
[18:03] <asac> :-P
[18:04] <sebner> ^^
[18:11] <sebner> asac: also not that short ^^
[18:16] <asac> sebner: managed - managed by NM ... unmanaged - unmanaged by NM
[18:16] <asac> ;)
[18:16] <sebner> asac: how, the ultra short explanation :D thx :P
[18:19] <sebner> asac: everytime dmks builds something (now nvidia) nm-applet disconnects and reconnts O_o
[18:20] <asac> sebner: most likely a driver issue. wireless?
[18:20] <sebner> asac: unfortunately
[18:21] <asac> sebner: use your phone
[18:21] <asac> :-P
[18:21] <asac> those drivers appear to be much better than what we will ever achieve for wireless
[18:22] <sebner> asac: well, intel wlan is well supported ;)
[18:22] <asac> one might think
[18:22] <asac> but it isnt
[18:22] <sebner> because?
[18:22] <asac> my opinion is that intel only gets worse
[18:22] <asac> intel had its up when ipw3945 was nwe
[18:23] <asac> since then things break more and more
[18:23] <sebner> asac: this is my wlan card so I'm fine :P
[18:23] <asac> because? ask intel, why they dont manage to fix their drivers over years
[18:23] <asac> sebner: no. ip3945 is the old driver
[18:23] <sebner> asac: iw
[18:23] <asac> the new is iwl3 and iwl4xxxx
[18:23] <asac> those are buggy as hell still
[18:23] <asac> and dont even support proper WPA-EAP
[18:23]  * sebner uses wep xD
[18:24] <asac> in hardy iwl3945 is pure luck to actually get a connection for some chipset revision
[18:24] <asac> s
[18:24]  * sebner never had problems
[18:24] <asac> lucky you
[18:24]  * sebner bought a laptop with intel wlan because my old laptop had a broadcom card -.-
[18:24] <asac> i saw plenty of folks with iwl3945 and hardy that couldnt connect at public places
[18:24] <asac> (at home usually works)
[18:25]  * sebner is only at home
[18:26]  * sebner has no RL just VL :D
[18:26] <asac> that explains it ;)
[18:26] <sebner> but what's the difference between home wlan and public wlan?
[18:29] <asac> more APs on the same essid is a big thing
[18:30] <asac> also much more noise and more devices that want to connect to your AP
[18:30] <asac> all that causing flakiness
[18:31] <sebner> I see
[18:31] <sebner> asac: you are always talking about intel und hardy problems. what's with intrepid?
[18:32] <asac> i think its better, but WPA-EAP is broken now
[18:32] <asac> i mean completely broken ;)
[18:33] <asac> e.g. real basic stuff like open and WPA-PSK works better (not sure whats up to WEP), while normal stuff like WPA-EAP which is used in companies and universities is broken
[18:33] <sebner> pff, who uses wpa-eap :P  I just knew wep, wpa, wap-psk and wpa2 ^^
[18:33] <asac> sebner: most important is universities ... appear to have a bunch of them
[18:34] <asac> together with "hidden" ESSID ... which doesnt make things better for intel
[18:34] <sebner> grr
[18:34] <asac> i think business is important too. its just that not many use ubuntu in companies
[18:34] <asac> and so the noise is much lower
[18:34] <asac> which doesnt mean its less important
[18:34] <sebner> asac: I always thought intel is Opensource fiendly and "good" at it
[18:35] <asac> if someone goes to his boss and wants to convince him to use more ubuntu
[18:35] <asac> we should support him that his thinkpad just works for his boss ;)
[18:36] <sebner> thinkbad ^^
[18:36] <asac> sebner: well. i dont say they are not opensource friendly. but still there are details about their chips that only they know and nobody else can fix
[18:36] <sebner> asac: and they don't fix or they f*** the driver up?
[18:36] <asac> sebner: they have different priorities ... add features and dont fix the most basic bugs ;)
[18:37] <asac> but thats an unqualified opinion
[18:37] <sebner> ^^
[18:37] <asac> i have no clue whats going on and why the iwl drivers still dont work
[18:37] <sebner> I trust you more than anybody else ;)
[18:37] <asac> but i am sure its a problem on intel side ;)
[18:37] <asac> priorities, incentives, customers that want other things fixed first
[18:38] <asac> and so on :-D
[18:38] <sebner> asac: so, what's now a good wlancardcompany? Apparently not intel and .. broadcom xD xD xD
[18:39] <asac> not sure ;)
[18:39] <asac> thats why i said: better skip wireless and go for 3g instead
[18:39] <sebner> I have 16mbit flat at home. f*ck 3g :P
[18:39] <asac> sebner: err. phone
[18:40] <asac> sebner: some phones can do wifi
[18:40] <asac> and then you can use your phone as a tunnel ;)
[18:40] <sebner> asac: I'm even happy to have wlan (I'm really a non-geek with such stuff). but I'll maybe buy an ipod touch with wlan :P
[18:41] <fta> http://ubuntuforums.org/showthread.php?t=941714
[18:41] <asac> sebner: i think ipod is probably the only phone thing that isnt really ubuntu friendly ;)
[18:41] <asac> err i ment iphone
[18:41] <sebner> asac: that's true and touch also not. but I want one *gg*. ubuntu wiki says how to break that stuff ^^
[18:43] <sebner> asac: https://help.ubuntu.com/community/PortableDevices/iPhone
[20:16] <fta> hm, gimp now depends on webkit
[20:20] <fta> Firefox 3 HugDay ??
[20:29] <fta> asac, firefox.sh now has inconsistent coding style.. such as `cmd` vs $()
[20:34] <asac> fta: is there a hugday?
[20:34] <fta> asac, http://paste.ubuntu.com/55388/
[20:35] <asac> wh ois dereck? e.g. what nick is he using?
[20:36] <fta> how would i know ?
[20:36] <armin76> bumb
[20:36] <fta> https://edge.launchpad.net/~dereck
[20:37] <armin76> i think its awsoonn
[20:37] <armin76> !seen aswoonn
[20:37] <armin76> bah
[20:37] <armin76> err
[20:37] <armin76> awsoonn
[20:37] <fta> IRC:  	Awsoonn  on network irc.freenode.net
[20:37] <armin76> read fail
[20:43] <asac> ok i updated the hug day page
[20:43] <asac> https://wiki.ubuntu.com/UbuntuBugDay/20081009
[20:48] <fta> asac, how come at least you were not aware of this??
[20:49] <asac> fta: most likely the guy organizing this, is from the community and maybe to new to know that there are some packages where individuals alone care a lot about
[20:49] <asac> individuals (e.g. small teams, not like motu :))
[20:49] <asac> i dont care. at least i got to know about it ;)
[20:50] <asac> bdmurray: how comes that we dont know about firefox 3 hugday ;)
[20:50] <asac> ?
[20:50] <asac> :-P
[20:51] <asac> obviously i dont read enough mails ;)
[20:51] <asac> hmm ... i dont have the initial mail
[20:51] <asac> only the reply on -discuss
[20:53] <fta> asac, do you want it ?
[20:56] <asac> fta: no its fine. i answered to the mail i had on -discuss with the info i wanted to get out
[20:57] <asac> thanks
[21:02] <fta> google chrome is having a new implementation of SafeBrowsing smoother on IO with sqlite
[21:30] <crimsun> asac: do we want Adobe Flash 10 RC (latest) in 8.10?  I can create a bzr branch of my changes.
[21:31] <crimsun> there's an existing FF exception request IIRC.
[21:31] <fta> i really think we should, the current one is almost unusable
[21:32] <fta> the RC is far bette
[21:32] <fta> r
[21:32] <crimsun> the only thing we need now is to upload a newer flashplugin-nonfree; \sh has already fixed ia32-libs.
[21:32] <crimsun> (and it was, like I said before, a missing libgnutls26)
[21:34] <asac> crimsun: we want latest flash in 8.10 yes.
[21:34] <asac> crimsun: can you do the upload (but please do a quick test ;))
[21:34] <asac> ?
[21:34] <crimsun> asac: I can only ask; remember that I'm no longer -dev.
[21:34] <asac> oh ... thought just  not core-dev
[21:35] <crimsun> and it does work on amd64; I'm using it right now.
[21:35] <fta> i had a branch but no history
[21:35] <asac> crimsun: cool.
[21:35] <asac> crimsun: if you have the branch ready, fta can also sponsor it :)
[21:35] <crimsun> does it need a FF exception, or does it fall under this team?
[21:35] <asac> i take the risk in case people complain about that
[21:36] <asac> crimsun: i am quite sure we had a ffe for that and even if not it belongs here so is covered by the delegation they gave to us
[21:36] <asac> crimsun: as i said. I take all the risk. not updating flash isnt a viable option :) and the risk is low ;)
[21:37] <crimsun> ok, then I'll trawl the bugs and create a bzr branch for it.
[21:37] <asac> crimsun: yeah. you can also open a quick FFe bug and i grant the exception there (then its clear that its my fault when someone complained :))
[21:37] <asac> crimsun: bug 257403
[21:38] <fta> http://paste.ubuntu.com/55406/
[21:38] <crimsun> asac: yes, I just changed the status of it.
[21:39] <asac> crimsun: good. i added another comment repeating the ffe for latest flash
[21:40] <asac> fta: ok so you tested it on 32bit?
[21:40] <asac> (tested the final adobe bits i mean)
[21:41] <fta> sure, i've been using it since Sep 27
[21:41] <asac> cool
[21:41]  * asac  eagerly waits to get the update through the normal archive ;)
[21:41]  * asac can then take a look how messy nspluginwrapper still is
[21:42] <fta> crimsun, did you add something else ? or was it just a bump like mine?
[21:42] <crimsun> asac: RC 2 works ok without any additional changes to intrepid's current nspluginwrapper
[21:42] <crimsun> fta: I modified debian/control as well; we're now conflicting with libflashsupport
[21:43] <asac> crimsun: right. but nspluginwrapper has stilla  bunch of issues and even crashes/stale locks for windowless plugins
[21:43] <asac> but at least upstream nspluginwrapper dev reappeared from MIA ;) ... maybe a bit late, but better than nothing
[21:43] <crimsun> asac: right, I saw the patch(es) on upstream's mailing list
[21:43] <asac> crimsun: oh you subscribed to the new mailing list ... cool
[21:44] <fta> crimsun, how come you're no longer -dev?
[21:44] <asac> but good to know that the whole instability we had didnt come from nspluginwrapper alone ;)
[21:44] <crimsun> fta: timing (mainly, moving, new job, other constraints).  I allowed them to expire.
[21:44] <fta> crimsun, oh, ok i see.
[21:45] <asac> crimsun: do you still do alsa work or did you have to take back on that too?
[21:46] <fta> crimsun, if you don't mind, i'd like to do this flash upgrade.
[21:46] <crimsun> asac: I still do work with Luke, but I no longer commit.  So, not so much has changed.
[21:46] <crimsun> fta: ok, then I'll just post the debdiff against the current intrepid source to the bug.
[21:47] <fta> ok
[21:47] <fta> crimsun, so you want a sponsor then?
[21:47] <asac> I think crimsun did all the ground work so get him the credits for the greatest and latest beta fflash work ;)
[21:47] <asac> :)
[21:47] <asac> (or the latest and grewat beta crash work :))
[21:47] <fta> ok, i don't really mind
[21:48] <crimsun> fta: err, whatever you want to do.  I'm simply providing it as a reference.  The only really important thing to me is that the Conflicts and Recommends be adjusted in debian/control.
[21:48] <asac> i think everybody just wants this in :)
[21:48] <asac> Strongest-Conflict-Event: libflashsupport :-P
[21:48] <asac> err
[21:48] <asac> Strongest-Conflict-Ever: libflashsupport :-P
[21:49] <asac> but well. ogra couldnt tell me if he still needs libflashsupport for his ltsp thing
[21:49] <crimsun> he shouldn't; we talked about it briefly a couple months ago
[21:49] <asac> ah cool
[21:49] <crimsun> alsa-plugins completely obsoletes libflashsupport
[21:49] <asac> i hoped that going through pulse should be enough
[21:50] <asac> to get networked sound
[21:50] <asac> yeah thats definitly one of the good news for intrepid
[21:50] <crimsun> Luke has 1 more additional patch to push for pulseaudio that doesn't attempt to start pulseaudio while the gdm login sound is playing
[21:51] <crimsun> err, sorry, not gdm login sound but session login sound
[21:52] <fta> asac, reading that bug, people using my ppa have issues with nss/nspr (the soname thing), you really should decide..
[21:53] <asac> fta: yeah. i think the decision happened automatically. i have to put the shame hat on and say that its too late for that unfortunately
[21:54] <asac> fta: we have to do a proper transition right at the beginning of jaunty
[21:54] <asac> and let the synching/merging do the archive rebuild for us :)
[21:54] <fta> so I will revert everything in my ppa :P
[21:54] <asac> fta: yeah. please dont uncommit
[21:54] <asac> revert
[21:54] <asac> i want to resurrect that right after release
[21:54] <fta> of course not
[21:55] <asac> fta: are the .head/.dev branches again in line with our general procedure?
[21:55] <asac> e.g. can we do one more .head -> .dev merge for final intrepid? (after you reverted the soname stuff of course)?
[21:56] <fta> i think it's in sync, i'll check after the revert
[21:58] <crimsun> fta: http://launchpadlibrarian.net/18346512/flashplugin-nonfree_<IP_ADDRESS>ubuntu1.debdiff
[22:00] <fta> crimsun, reading..
[22:02] <fta> good, i'll sponsor it
[22:03] <crimsun> fta: thanks
[22:06] <fta> done
[22:11] <asac> fta: thanks!
[22:11] <fta> subject: [ubuntu/intrepid] flashplugin-nonfree <IP_ADDRESS>ubuntu1 (Accepted)
[22:18] <fta> asac, http://ubuntulinuxtipstricks.blogspot.com/2008/10/firefox-3-hug-day-tomorrow.html
[22:25] <fta> http://formatwarcentral.com/index.php/2008/10/08/disney-goes-eula-crazy-on-sleeping-beauty-blu-ray/
[22:26] <asac> fta: cool the handbook made it on a blog ;)
[22:26] <asac> great marketing
[22:26]  * asac hugs himself ;)
[22:26] <asac> and great intelligence :)
[22:27] <fta> lol
[22:27]  * asac hugs fta
[22:27]  * fta hugs back
[22:27] <asac> next step: make the handbook accurate ;)
[22:28] <asac> from what i see it refers to a not-existing bugzilla account :/
[22:28] <fta> http://ubuntuforums.org/showthread.php?t=941865
[22:30] <asac> yeah thats a known compiz bug
[22:30] <asac> i will bug mvo about it
[22:30] <asac> hmm he is (wisely) offline
[22:31] <fta> for me, F11 != View / Full screen, this is annoying
[22:33] <bdmurray> asac: I'd thought dereck would have notified you
[22:37] <asac> bdmurray: well. not directly. maybe he just wasnt aware how much i suck at email :)
[22:38] <asac> bdmurray: so all fine. anyway. if you need info for tomorrow on the triagershandbook for example, dont hesitate to ask :)
[22:38] <asac> i will try to remebmer to look in -bugs tomorrow
[22:39] <asac> but often hug days run rather silently, with people just grabbing thigns from wiki
[22:40] <bdmurray> okay, great if I have any questions I'll ping you
[22:40] <bdmurray> any news on the n-m bug?
[22:40] <asac> bdmurray: yes. its fixed most likely
[22:40] <asac> i am waiting for the commit to sink into our bzr mirror ;)
[22:40] <asac> so tomorrow you probably could verify if its really gone
[22:41] <bdmurray> ah, great!
[22:41] <asac> bdmurray: http://svn.gnome.org/viewvc/NetworkManager/trunk/src/?view=log
[22:41] <asac> 4156/7
[22:41] <bdmurray> was there an upstream bug or was it just irc communication?
[22:41] <asac> are the commits from what i can tell
[22:42] <asac> bdmurray: just irc
[22:42] <asac> bdmurray: someone showed up who had debugged that in #nm
[22:42] <asac> and dan williams nailed it down with his info
[22:42] <asac> so quite fortunate :)
[22:43] <asac> bdmurray: it was randomness due to access of freed/uninitialized memory
[22:43] <asac> so the behaviour should have been at least a bit random ... though the chances for a positive outcome often are really low for this kind of bugs :)
[22:44] <asac> today is a good day: keyfile plugin fixed, routing bug fixed ;)
[22:44] <asac> dns list bug fix in applet :)
[22:45] <bdmurray> great!
[23:02] <fta> asac, why was that firefox.sh.in patch needed in the 1st place? i thought we had all the necessary links
[23:10] <fta> http://blog.karlt.net/2008/10/font-selection-for-web-fonts-on-linux.html
[23:10] <asac> fta: no :) ... it didnt serve arbitrary lknks
[23:10] <asac> e.g. x-www-browser, sensible-browser
[23:11] <asac> like what the bug said
[23:12] <fta> ok, but then, that name=$(name%%-3.0) is wrong
[23:31] <asac> fta: what is the problem we are getting from that?
[23:32] <asac> that a link x-www-browser -> /usr/bin/firefox would be run as firefox-3.0?
[23:35] <asac> fta: cool you fixed browser-branding.
[23:36] <fta> name=$(name%%-3.0) just drops -3.0 from the name, so if i merge that, it will drop -3.1, then it will fail
[23:36] <fta> providing we have the necessary links, there's no need to drop this even for 3.0
[23:38] <asac> hmm
[23:38] <asac> well. the idea is that firefox gets started with firefox if the link points to the unversioned thing
[23:39] <asac> its a requirement to fix the "restart" patch for real
[23:39] <fta> yes
[23:39] <asac> and also the system gconf integration patch
[23:39] <asac> at best it could also rely on what was $0
[23:39] <asac> but maybe i am just confused here :)
[23:54] <fta> fg
[23:54] <fta> oops
[23:56] <asac> where is the passphrase ;)
[23:57] <fta> http://paste.ubuntu.com/55439/


 Getting this : https://irc-attachments.kde.org/a8fc6c09/file_68938.jpg
 I need to move that file to this folder : https://irc-attachments.kde.org/29c5a5a0/file_68939.jpg
 Getting this issue  for long time : https://irc-attachments.kde.org/ec937f75/file_68940.jpg
 https://irc-attachments.kde.org/df7c047a/file_68941.jpg
[06:50] <enyc> hrrm. I was asking a question before ....
 How i can set the Albert hot key globally in kubuntu 23.10
 How i can set the Albert hot key globally in kubuntu 23.04
[10:02] <tomreyn> mr_honestyy: what is "the Albert hot key"?
 Ctrl + space
[10:03] <tomreyn> when you are sharing "issues", please try to use text as much as possible. just posting an image is often not enough to describe a problem. describe what you did, what you expected to happen, and what happened instead.
 Ok
 When I reboot or power off my system i get this msg and it take time like more than one minute to automatically turn off or reboot : https://irc-attachments.kde.org/df7c047a/file_68941.jpg
 . (re @mr_honestyy: )
 When I reboot or power off my system i get this msg and it take time like more than one minute to automatically turn off or reboot how i can solve this problem... : https://irc-attachments.kde.org/df7c047a/file_68941.jpg
[10:06] <tomreyn> which kubuntu version are you running?
 When I reboot or power off my system i get this msg and it take time like more than one minute to automatically turn off or reboot how i can solve this problem...Kubuntu version :- 23.04 KDE version:- 5.27.4Processor :- Intel core i5 Graphics platform:- Wayland : https://irc-attachments.kde.org/df7c047a/file_68941.jpg
 . (re @mr_honestyy: )
[10:10] <tomreyn> press escape immediately when then messages seen on https://irc-attachments.kde.org/df7c047a/file_68941.jpg is printed on screen, then see if there is some process which is taking a long time to shut down (and ultimatively failing to do so)
[10:10] <tomreyn> once you know what it is that delays the shutdown, you can focus on fixing this issue.
 I press escape many time nothing i see (re @IrcsomeBot: <tomreyn> press escape immediately when then messages seen on https://irc-attachments.kde.org/df7c047a/file_68941.jpg is printed on screen, then see if there is some process which is taking a long time to shut down (and ultimatively failing to do so))
[10:13] <tomreyn> ok in this case let's try this:
[10:14] <tomreyn> !bootlog
[10:14] <tomreyn> boot with these kernel parameters, then shut the system down - you should get more output this time.
[10:22] <tomreyn> actually if you just run    systemctl log-level info    before you shutdown, thuis may be sufficient to get more verbose output
[10:22] <tomreyn> mr_honestyy ^
 getting this error when i run this command : https://irc-attachments.kde.org/15c2fe9e/file_68945.jpg
[10:35] <tomreyn> you can just run the command with "sudo" prefixed, no need to "sudo -i"
[10:37] <tomreyn> i.e.    sudo systemctl log-level info
[10:45] <weedmic> in the end, what did the "albert hot key" turn out to be?
 not getting anything : https://irc-attachments.kde.org/d44c0d95/image_2023_09_26_16_17_40.png
[10:50] <tomreyn> mr_honestyy: on a linux shell, when there is no output for a command, it usually means the command succeeded
[10:50] <tomreyn> shutdown now, and you should get to see more (may need to hit escape again)
 Ok
[10:51] <tomreyn> weedmic: <mr_honestyy> Ctrl + space
[10:51] <tomreyn> apparently it's some application
 I get this : https://irc-attachments.kde.org/b0165a75/file_68947.jpg
[10:52] <weedmic> why call it such a name?
[10:52] <tomreyn> mr_honesty: that's after reboot, but did you get to see more during shutdown?
 I do know i a new Linux user
[10:53] <weedmic> I mean I have the "host" key - for right ctrl, and a few other weird things like that.
 I am asking for this problem (re @mr_honestyy: )
[10:54] <tomreyn> mr_honesty: you can press ctrl-alt-del to leave the grub prompt
 Ok yes I do
 Then
[10:58] <tomreyn> if you want to, you can repeat the process: boot normally, then in a konsole window, type  sudo systemctl log-level info    then type   sudo systemctl reboot   (or do whatever you did previously to cause the slow shutdown) and press escape immediately to ensure you get full output.
[10:58] <tomreyn> if this still doesn't work then i'm afraid i don't know what's wrong with my recipe.
[10:59] <tomreyn> the idea of getting more output is for you to see and understand what is the thing that is causing the shutdown to take so long
 Getting this just : https://irc-attachments.kde.org/35c8f4d5/file_68948.jpg
 https://irc-attachments.kde.org/c29aa200/file_68949.jpg
[11:47] <weedmic> but you already know <mr_honestyy> "albert toggle" = Ctrl + space
[12:07] <BluesKaj> Hi all
[17:08] <givko> I have 2 monitors. can anyone tell me how to scale only one monitor on Kubuntu?
[18:21] <gregor3000> hi, 've had nvidia driver issues at upgrade for some time but not as bad as today at my kids PC. so the issue was that PC apparently went off at some point possibly after autoupdate or triggered. anyway while it would boot i could not get the openGL to work. enabling it in settings resulted in non bootable state. and drivers were not fully upgraded. i uninstalled, reinstalled
[18:21] <gregor3000> nothing
[18:21] <gregor3000> went to older kernel worked just fine.
[18:21] <aiena> I have a kubuntu virtual machine setup in virtmanager it is getting network connectivty through a bridge configured in network manager on the host it gets the static dhcp ip from the real router and internet works but KDE shows the network with limited connectivity why does it say that?
[18:21] <gregor3000> reinstalled new kernel, nothing.
[18:22] <gregor3000> went to recovery, did some repair, booted.it was showing drivers installed. but they were not. so i installed them. PC boots. yes!! finally!! but now it takes 1. min to boot.
[18:22] <aiena> gregor3000, live boot also doesnt work?
[18:22] <gregor3000> 1.5 min
[18:23] <gregor3000> it is just strange as i had a simialr issue myself. drivers update in updater then screen goes black
[18:24] <gregor3000> at the time i saw this my quick fix was go to console TTY2, wait a bit, then reboot. but why does it turn off the screen?
[18:24] <gregor3000> this is what puzzles me as it didn't do this before.
[18:26] <gregor3000> so i was wodnering if anyone else saw this? we both have Ryzens  (7 - 2700 and 5-3600) and we both use nvidia GTX 1650 (different manufacturers) and we both have 22.04 LTS
[18:26] <gregor3000> maybe it is time for an upgrade
[18:26] <gregor3000> i mean kernel. to use HWE or something
[18:35] <gregor3000> additiuonal drivers could not install any driver version and at  same time they showed latest drivers install. so i took to console and did a manual install command and reboot. just to see what would happen. sure enough it worked. but now boot is longer +  plymouth is not working correctly. i dont' have the will to try out game so see if drivers are actually working correctyl