[08:19] <tonim> I uploaded my source packages to my ppa yesterday and the build was successful. however the binary packages don't show kn the ppa. What can I do? https://launchpad.net/~tonimelisma/+archive/ubuntu/ppa
[08:49] <tonim> Cpuld anyone point me to relevant documentation on how to set up the PPA properly? Best I can find is https://help.launchpad.net/Packaging/PPA/Uploading which seems to be from 2009 and doesn't explain any steps after dput
[08:53] <ginggs> tonim: what do you mean they don't show up?
[08:54] <ginggs> I see binary packages after clicking on View package details
[08:55] <ginggs> also
[08:55] <ginggs> http://ppa.launchpad.net/tonimelisma/ppa/ubuntu/pool/main/v/vips/
[12:14] <snecklifter> I'm getting an OOPS when I try to log into Launchpad, is there anyone who can take a look?
[12:14] <snecklifter>  (Error ID: OOPS-7b126e10cfeca2c17b0ea46bdf7a18e6)
[12:20] <cjwatson> ilasc: ^
[12:25] <ilasc> snecklifter: I'm looking at this now
[12:36] <ilasc> snecklifter: you should be able to log in now
[13:13] <snecklifter> ilasc, many thanks, thats sorted
[13:13] <ilasc> snecklifter: you're welcome, thanks for letting us know


[00:30] <ryanakca> newz2000: ping, Do you have any idea why the exact same theme (I'm told that canonical did not modify it when installing) would give two different results? http://wiki.kubuntu.org/PackagingGuide/Complete vs. http://wiki.ryanak.ca/kubuntu/test (theme: lp:~kubuntu-website/kubuntu-website/kubuntu-wikitheme )
[00:31] <ryanakca> The community help wiki has the same theme (well, almost, colors are changed, JS for rounding and moved the edit bar to the top of the screen) and it appears to work fine there...
[00:33] <SiDi> you're lacking a CSS file imho
[00:41] <ryanakca> SiDi: Oh?
[00:42] <SiDi> it looks like you're lacking the file that gives the shape of the corners and several other things
[00:42] <SiDi> its only a supposition though, didnt look at the sources :)
[00:44] <ryanakca> SiDi: file that gives the shape of the corners? As in the corners of the container? We do it with JS :)
[00:45] <SiDi> then one of your js files is screwed on your server ^.^
[00:45] <SiDi> the common.css files of both websites are not identical, too, but it doesnt seem to have many differences
[01:02] <MT-> newz2000: you ever get a chance to check out the email?
[13:36] <ryanakca> SiDi: You're right, it's the JS that's breaking something, look at http://ryanak.ca/~ryan/working-wiki.png vs ~ryan/broken-wiki.png
[13:37] <knome> the contents div should have a z-index of, say, 50
[13:44] <ryanakca> knome: .table-of-contents has it
[13:46] <knome> hmm.
[13:53]  * ryanakca is stumped
[13:53] <ryanakca> The script works fine on http://www.kubuntu.org/ , I wonder why it doesn't like the wiki.
[13:53] <ryanakca> or why the wiki doesn't like the script :)
[16:15] <MT-> newz2000: ping
[20:29] <MT-> newz2000: reping
[20:34] <SiDi> MT-, ICMP Error : Host unreachable
[20:34] <MT-> SiDi: lol
[20:37]  * newz2OOO IRC Error : Host too busy
[20:37] <jpds> ID theft!
[20:38] <jpds> And 'ping' is so overrated.
[20:38] <MT-> jpds: no... only imitated
[20:38] <jpds> MT-: ICMP ECHO REQUEST
[20:38] <MT-> jpds: TACO
[20:40] <MT-> that's right, isn't it?
[20:40] <MT-> which canonical employee do I need to bug next+
[20:40] <MT-> ?*
[20:43] <MT-> stu!
[20:43] <SiDi> stu yourself !
[20:44] <MT-> um?
[20:46] <jpds> MT-: For what?
[20:47] <MT-> the Luanchpad OpenID stuff
[20:50] <MT-> jpds: so, you you been?
[20:52] <jpds> I what been?
[20:52] <MT-> how have you been? **
[20:52] <SiDi> Is that me or this conversation doesn't make sense and doesn't even try to ?
[20:52] <MT-> how did I do that? :S
[20:52] <SiDi> jar jar binks !?
[21:01] <MT-> jpds: no opinion on how you're doing?
[21:02] <MT-> SiDi: those darned busy busy beaver canonical guys
[21:02] <SiDi> MT-, contrarily to us, they work :D
[21:03] <MT-> I work, I just make up for the time I'm not doing anything, doing homework, or at work by not sleeping :P
[21:04] <MT-> SiDi: you ever used CVS?
[21:04] <SiDi> I use git and bzr
[21:05] <MT-> I've been figuring out the challenge that is cvs - I find it similar to learning how to slit my wrists in a specific order at specific lengths and which type of blade is needed at each stage
[21:06] <MT-> bzr is about as hard as learning how to use ssh :P


[07:39] <jibel> pitti, thanks for fixing the small issues I reported in autopkgtest.
[07:40] <jibel> pitti, another one http://paste.ubuntu.com/11075181/
[07:41] <pitti> jibel: bonjour !
[07:42] <pitti> jibel: I just got a mail notification this morning (just one), that got fixed apparently?
[07:42] <jibel> pitti, apparently. I thought you talked to CI
[07:43] <pitti> jibel: no, I didn't yet; I just saw your "fw rule changed" in backscroll this morning
[07:43] <pitti> jibel: I can't reproduce/understand the "trailing space" yet, I set that to incomplete with a comment
[07:44] <jibel> pitti, I attached the a config file to reproduce with latest git rev
[07:44] <jibel> s/the a/a/
[07:44] <pitti> jibel: http://paste.ubuntu.com/11075181/ applied, thanks!
[07:45] <jibel> pitti, it happens if the space is after -d
[07:45] <pitti> jibel: aah, thanks
[07:45] <jibel> pitti, or after the name of the package
[07:47] <jibel> pitti, I'm almost done with 'dep8ification' of dkms tests. It was pretty straightforward.
[07:47] <pitti> jibel: oh, cool! what did you change now, compared to what we had in Austin?
[07:47] <pitti> jibel: err, London, but all thes ame
[07:47] <jibel> pitti, but I don't use autodep8. dkms-autopkgtest in dkms needs fixing first
[07:48] <pitti> jibel: I saw that it fails on trusty as we don't have the test script in dkms there yet
[07:48] <jibel> pitti, I've a setup command to install any kernel and enable the pockets/ppa I need, and I changed the test to install only the dkms module and collect all the artifacts I need
[07:49] <jibel> pitti, right, but it also fails if the source package build other binaries than only a dkms module
[07:49] <jibel> pitti, see blcr for example
[07:49] <jibel> in that case it install a binary package that doesn't depend on dkms and fails
[07:51] <jibel> so with this setup command and test, the test runs on any release.
[07:51] <jibel> I'll do more tests, deploy and we can remove previous version and old style VMs
[07:52] <pitti> \o/
[07:53] <pitti> jibel: blcr didn't run in wily yet
[07:53] <jibel> pitti, I tried in vivid
[07:54] <jibel> so I can compare with current tests
[07:54] <pitti> http://d-jenkins.ubuntu-ci:8080/job/vivid-adt-blcr ?
[07:54] <pitti> (404)
[07:54] <jibel> blcr-dkms
[07:55] <pitti> that's the binary name
[07:55] <pitti> well, I guess you ran it on the CLI, not through jenkins
[07:56] <jibel> pitti, ah sorry, I was talking about the current DKMS tests http://d-jenkins.ubuntu-ci:8080//job/dkms-vivid-release-generic-blcr_dkms/
[07:57] <jibel> pitti, I'm replacing these tests
[07:57] <jibel> pitti, once it's done, I'll propose to replace dkms-autopkgtest
[07:58] <jibel> pitti, how did you run blcr on the CLI? it fails for me with 'cannot cd to /var/lib/dkms'
[07:59] <pitti> jibel: I thought you did; with just autopkgtest/run-from-checkout bclr ...
[08:00] <pitti> jibel: I thought you meant that the autodep8'ified ones fail in CI
[08:00] <jibel> pitti, yeah it'll fail in CI with http://paste.ubuntu.com/11075465/
[08:01] <pitti> jibel: ok, that looks fixable
[08:01] <jibel> pitti, so I'm converting the DKMS tests for the kernel team first, then I'll propose the test script because autodep8 are just small a subset of the kernel team's tests
[08:02] <jibel> pitti, indeed it is not difficult to fix. It's because the test script install blcr-utils which doesn't depends on dkms
[08:02] <jibel> pitti, it shouldn't install non-dkms modules at all
[08:03] <pitti> jibel: so binaries which don't have DKMS bits should just get skipped
[08:03] <jibel> pitti, is ADT_ARTIFACTS removed on reboot?
[08:04] <jibel> pitti, right
[08:04] <pitti> jibel: no, it survives
[08:04] <pitti> jibel: /tmp/autopkgtest-reboot saves it and restores it after reboot
[08:46] <bip> Ehy ;-)
[13:50] <elopio_> good morning.
[14:10] <elopio> sjcazzol: https://code.launchpad.net/ubuntu-sanity-tests
[14:11] <sjcazzol> elopio: thanks!
[14:11] <elopio> sjcazzol: let me quickly show you how I have my bzr branches in the filesystem. You can choose a different layout of course.
[14:12] <sjcazzol> elopio: ok
[14:12] <elopio> mkdir -p ~/workspace/canonical
[14:12] <elopio> cd ~/workspace/canonical
[14:12] <elopio> bzr init ubuntu-sanity-tests
[14:13] <elopio> cd ubuntu-sanity-tests
[14:13] <elopio> mkdir bugs
[14:13] <elopio> mkdir experimental
[14:13] <elopio> mkdir reviews
[14:13] <elopio> bzr branch lp:ubuntu-sanity-tests trunk
[14:13] <elopio> then cd trunk and take a look at the README.
[14:14] <sjcazzol> elopio: great, I'll try that
[14:20] <elopio> fgimenez: hey, the phonedations planning was cancelled.
[14:20] <fgimenez> hi elopio, ok thx, will it be rescheduled?
[14:21] <elopio> fgimenez: I know nothing. I will tell you if I find out something else.
[14:22] <fgimenez> elopio, ok
[14:24] <elopio> ubuntu-qa: have you met sjcazzol ?
[14:24] <davmor2> no
[14:25] <davmor2> hello sjcazzol
[14:27] <rhuddie> sjcazzol, hello!
[14:29] <fgimenez> hi sjcazzol! welcome to the team
[14:29] <jfunk> hey sjcazzol :) welcome to our team
[14:30] <sjcazzol> Thanks! I hope to make a good job as part of this team
[14:30] <brendand_> sjcazzol, we met before :)
[14:30] <sjcazzol> brendand_: yes! :)
[14:31] <vila> elopio: s/bzr init ubuntu-sanity-tests/bzr init-repo buntu-sanity-tests/
[14:31] <vila> sjcazzol: welcome !
[14:32] <elopio> vila: good to know. Can you explain the difference?
[14:33] <vila> elopio: the later setup a shared repository so all branches below share the common revisions which speeds up most operations (otherwise each branch gets its own branch so, for example, you download the whole history when creating a new branch)
[14:33] <elopio> :) thanks.
[14:51] <fgimenez> elopio, i've pushed a branch with the python-selenium code for the ppa https://code.launchpad.net/~fgimenez/+junk/python-selenium, as far as i know this wasn't versioned
[14:51] <fgimenez> elopio, i've taken the opportunity to tweak the debian directory, changing the source format to quilt so tht the patches are applied at build time, etc
[14:53] <fgimenez> elopio, i've also applied vila's comments for making a recipe, and now it seems to be building fine
[14:54] <fgimenez> elopio, this can be pushed to canonical-platform-qa if needed, and the ppa can be build from there, let me know what do you think
[15:07] <balloons> hey hey sjcazzol
[15:15] <elopio> fgimenez: I think it's awesome.
[15:16] <elopio> thank you. I'm wondering what else we need to send this to debian.
[15:16] <elopio> I think that we need a separate package with the binaries that we stripped out.
[15:16] <elopio> or maybe not as firefox has marionnette embedded, so now the binaries are not really needed.
[15:17] <fgimenez> elopio, thx :) right now it's using the pristine source code from 2.44, i've turned the modifications in setup.py into a quilt patch, perhaps this can be removed?
[15:18] <fgimenez> elopio, that modifications where about firefox .so files, are you refering to that?
[15:20] <elopio> fgimenez: yes, the problem with this package in debian is that you can't easily build those .so files.
[15:20] <fgimenez> elopio, http://bazaar.launchpad.net/~fgimenez/+junk/python-selenium/view/head:/debian/patches/remove_x_ignore_nofocus.patch
[15:21] <fgimenez> elopio, ok, this was previously modified in the setup.py file itself, iirc there was a debian bug?
[15:23] <elopio> fgimenez: there are some bugs, overlapping: https://bugs.debian.org/cgi-bin/pkgreport.cgi?pkg=python-selenium;dist=unstable
[15:36] <sjcazzol> balloons: Hi, thanks
[16:02] <elopio> sjcazzol: almost done here. Are you ok meeting in 1 hour?
[16:02] <sjcazzol> yes, no problem
[16:35] <balloons> elopio, I'm going to undertake updating the qml testing template in the SDK again based on the changes I made for Rick's app with launching. Is there anything else you'd want to change in the default template?
[16:37] <elopio> balloons: I don't think so. Please add me as a reviewer, to make sure we are all writing following the same template.
[16:52] <vila> elopio: is there a project group for qa ?
[16:53] <elopio> vila: I don't understand your question.
[16:57] <vila> elopio: see https://launchpad.net/bzr , it's part of https://launchpad.net/bazaar (In Porject information, Part of:)
[16:57] <vila> elopio: I want to make uci-{config,tests,vms} part of ???
[16:58] <elopio> vila: yeah, we don't have that I think.
[16:58] <elopio> it would be good to get one.
[16:58] <vila> elopio: so that I can go to ??? and see active reviews (for example) for all projects that are part of ???
[16:58] <vila> elopio: ok
[17:23] <elfy> balloons: any idea when the wily old release schedule is going to make itself known?
[17:24] <elfy> it's being much too wily imo
[17:24] <wxl> oh, i see what he did there
[17:24] <elfy> hey wxl :)
[17:24] <wxl> hai :)
[17:29] <balloons> nice!
[17:29] <balloons> i'll need to update things
[17:32] <elopio> sjcazzol: that was a looong meeting, I'm sorry.
[17:32] <elopio> do you want to do a google hangout?
[17:33] <sjcazzol> ok
[17:36] <elopio> sjcazzol: https://plus.google.com/hangouts/_/canonical.com/qa
[17:36] <elopio> ubuntu-qa: welcome party for sjcazzol  ^
[18:07] <elopio> sjcazzol: I don't know what happened, my monitor just died.
[18:07] <sjcazzol> Ok, no problem
[18:07] <elopio> but anyway, I was talking too much. I will let you go and play with the emulator and stuff, and have lunch in the meantime.
[18:07] <elopio> sjcazzol: ping me, fgimenez or ubuntu-qa in case you need a hand.
[18:08] <sjcazzol> elopio: good, I have a lot to read and try
[18:08] <sjcazzol> elopio: thanks for the support
[18:09] <elopio> sjcazzol: thanks to you.
[20:44] <elopio> veebers: http://paste.ubuntu.com/11084721/
[20:44] <elopio> those are my quick notes.
[20:44] <elopio> first is the list of packages that get installed to their latest version, so if it worked before and it doesn't work now, it could be one of those packages fault.
[20:44] <veebers> elopio: awesome, cheers
[20:44] <elopio> I'm not yet sure it worked before.
[20:45] <veebers> elopio:  how did you get the event information?
[20:45] <elopio> the second part is the events that the input device gets when you touch the screen.
[20:45] <elopio> the third is what it gets when you do it through autopilot.
[20:45] <elopio> what I see is that with autopilot, it never receives x and y, so I got stuck trying to dig more about that.
[20:45] <elopio> veebers: http://python-evdev.readthedocs.org/en/latest/
[20:45] <elopio> it shows and example with a read loop.
[20:46] <veebers> ah cool, cheers
[20:46] <elopio> just change that for the autopilot finger path, and it will print the events.
[20:47] <elopio> I wanted to compare the events that krillin receives to see if it was something weird in there, and here I am.
[20:47] <elopio> so pending, try with older autopilot, which is a little hard because I also have to get older dependencies that are no longer on the archive.
[20:48] <elopio> and try on krillin to compare.
[20:48] <elopio> oh, and talk to sergio again to see if he has more ideas.
[20:49] <veebers> elopio: ack, good luck :-)
[23:12] <elopio> veebers: this might get us somewhere, http://paste.ubuntu.com/11086470/
[23:12] <elopio> the arale is indeed missing the x and y events.
[23:15] <elopio> it makes no sense, as from the autopilot side this is just writing to a file.
[23:25] <veebers> elopio: interesting, good find.
[23:29] <veebers> elopio: I'm not so sure how to proceed though. Perhaps autopilot is writing the x/y events incorrectly? But the other events are received so that might not hold up


[03:04] <Perigee> Anyone have any tips for getting Netflix to run in Firefox? I've enabled DRM in the preferences, Widevine plugin is activated, but still get thrown to the system requirements page when trying to play. Netflix says to use Chrome. :(
[16:13] <axarix> spricht hier jemand deutsch?
[16:14] <Pici> !de
[18:31] <xubuntu45w> I have problems with Thunar crash & loss of network from screenlock/powersave
[22:26] <eric1234> Hello! How does this work?


[20:13] <xnox> How to use persistent-storage in my charm?
[21:14] <xnox> can a charm request a nova volume to be added?
[21:16] <xnox> (as in juju  machine instance for a service to have a nova volume mounted, not like deploy a nova-volume charm)
[23:58] <marcoceppi> xnox: no. not at this time


[07:01] <vi390> hi, how can I get openVZ kernels with jaunty
[09:22] <slytherin> Is ATI KMS configured/enabled in karmic kernels? The kernel upstream changelog says it is enabled for non-x86.
[09:27] <mdz> slytherin, the config used is in /boot/config-`uname -r`
[09:31] <mdz> slytherin, I believe the relevant option is CONFIG_DRM_RADEON_KMS
[09:31] <mdz> it doesn't seem to be set at the moment in Karmic
[09:32] <mdz> though I believe apw has a kernel build with it enabled
[09:33] <apw> that code comes in the 2.6.31-rc1 update, which is the next kernel for karmic.  where it is enabled by default
[09:34] <slytherin> mdz: I haven't installed karmic yet. I plan to upgrade my ibook (powerpc) once the KMS is enabled.
[09:35] <slytherin> apw: thanks for info.
[09:35] <apw> there is an older KMS enabled kernel available in one of my PPAs
[09:35] <slytherin> apw: my machine is powerpc arch, hence PPAs are not useful to me.
[09:36] <apw> the powerpc kernels in karmic are lagging somewhat right now
[09:36] <slytherin> apw: by the way, the changelog for linux package in karmic says that it is rebased on 2.6.31-rc1. So I believe once it builds properly it will have KMS.
[09:37] <apw> right, it does have the code but the ports architectures don't seem to be building right now
[09:38] <slytherin> apw: anyway I can help to fix it?
[09:38] <apw> to be honest i've not even looked yet at why they arn't building.  the ports maintainers normally sort that out
[09:39] <slytherin> which means I have to bug NCommander
[09:53] <apw> yeah there are a couple of them i think
[10:15] <apw> Keybuk, hey ... the moving from 486 to 586 discussion for i386 architecture, where has that gotten to?  i am trying to work out if i need to re-integrate the 386 kernel flavour
[10:19] <Keybuk> apw: still waiting on a 586 build to test with
[10:22] <apw> thanks for the info
[10:56] <bullgard4> Since upgrading from 2.6.24-24-generic to 2.6.28-13-generic the number of loaded kernel modules almost cut in half. Why?
[10:57] <smb> bullgard4, because most drivers are built-in
[11:03] <bullgard4> smb: Thank you.
[11:57] <vi390> can somebody tell me if there is any openVZ kernels for jaunty ?
[12:27]  * hyperair doesn't think so
[12:27] <hyperair> you could dig around the PPAs and see, though
[14:04] <smb> manjo, look at the makefile of dmraid as it is before. you only get one .ko
[14:05] <manjo> smb, I did not change the makefile ... and it produced many kos
[14:05] <apw> yeah i think he is right, its makeing a .ko per .c there
[14:05] <manjo> dm-raid45.ko  dm-message.ko dm-region-hash.ko
[14:05] <smb> after importing the new version or before?
[14:05] <apw> before for sure
[14:05] <apw> obj-$(CONFIG_DM_RAID45) += dm-raid4-5.o dm-mem-cache.o dm-region_hash.o dm-message.o
[14:05] <smb> obj-$(CONFIG_DM_RAID45) += dm-raid4-5.o dm-mem-cache.o dm-region_hash.o dm-message.o
[14:05] <apw> that is adding them raw, so each is a separate module
[14:05] <smb> that is one .ko
[14:05] <apw> smb, nope
[14:05] <apw> you see
[14:06] <apw> dmraid-obj = foo.o bar .o
[14:06] <apw> if you merge .o's to make a .ko
[14:06] <smb> so?
[14:06] <apw> obj-$(CONFIG_TLSUP) := tlsup.o
[14:06] <apw> tlsup-objs := tlsup_mod.o tlsup_acpi.o tlsup_backlight.o tlsup_hotkeys.o tlsup_radios.o
[14:07] <apw> that construction makes one .ko out of a bunch of .o's
[14:07] <apw> obj-$(CONFIG_DM_RAID45) += dm-raid4-5.o dm-mem-cache.o dm-region_hash.o dm-message.o
[14:07] <apw> that form makes one .ko per .o
[14:07] <smb> Hm, ok , you are right here. Not sure we actually wanted that
[14:08] <apw> yeah if it worked using the first form, then things seem less worrying
[14:08] <manjo> apw, I thought we changed it to be that way... so that was a mistake you say ?
[14:09] <apw> i don't know for sure one way or the other right now
[14:09] <manjo> ok how about this ?
[14:09] <manjo> I use the makefile that came with the patch
[14:09] <manjo> and build the ko in ubuntu ?
[14:09] <manjo> throw away the old make file
[14:09] <apw> what does that one look like
[14:09] <manjo> I wanted to do that originally
[14:09] <smb> The problem to me seems that drivers/md also produces similar modules.
[14:10] <manjo> yes it does
[14:10] <smb> I guess the renaming is the critical part here
[14:10] <apw> yes they have been renamed there may be some other renames in the code we cannot see
[14:10] <smb> But probably it would make much more sense to use the form to produce only the dm-raid module including all the code
[14:11] <apw> manjo, can you pastebin the new Makefile
[14:11] <manjo> yes
[14:11] <apw> so we can see what its like, its likely an external module build job, whjich is not usable without mod in the kernel
[14:11] <manjo> apw, heh the new Makefile does the same thing
[14:12] <manjo> +obj-$(CONFIG_DM_RAID45)                += dm-raid45.o dm-log.o dm-memcache.o \
[14:12] <manjo> +                                  dm-region-hash.o dm-message.o
[14:12] <smb> I believe it produced modules differently named
[14:12] <smb> dm-region-hash.o in drivers
[14:12] <smb> and dm-region_hash.o in ubuntu
[14:13] <apw> manjo, can you pint me at the original patch
[14:13] <manjo>  http://people.redhat.com/~heinzm/sw/dm/dm-raid45/
[14:14] <manjo> smb, when you apply the patch it no longer produces dm-region_hash.c
[14:14] <manjo> but produces  dm-region-hash.c
[14:14] <smb> apw, I guess what happened was exactly that. Take the patch and the files. And to avoid duplicated rename on
[14:14] <smb> but that still leaves the risk of duplicate symbols
[14:14] <apw> yeah ... is a little worrying
[14:14] <smb> So IMO the simples solution is to import it the other way
[14:15] <smb> replace the makefile to build one module
[14:15] <manjo> also does not produce dm-mem-cache.c but it produces dm-memcache.c
[14:15] <apw> which one?  the old?
[14:16] <manjo> I think this is what we need to do .. throw away the old ones
[14:16] <manjo> use the new patch to produce one module
[14:16] <smb> Neither dm-mem-cache nor dm-message are in drivers/md, but this might be preparations to get it merged upstream
[14:17] <manjo> right ... apw smb  are you in agreement with throwing away the old stuff in /ubuntu/ and makeing dmraid as one module ?
[14:17] <apw> dmraid4-5 as one module
[14:17] <smb> yep
[14:17] <apw> if so, thats the thing to try yes
[14:17] <manjo> so we will not have many kos under dmraid4-5
[14:18] <apw> apply the patch, copy the changed/new files over
[14:18] <apw> and then use the -objs form to make one .ko
[14:18] <smb> manjo, one more second, let me check something
[14:18] <apw> then see if it will build/boot/load
[14:18] <manjo> yeah actually I have done all that ... just need to make one module ..
[14:18] <apw> the tlsup module is a good example of how to do that
[14:18] <smb> dm-raid45-objs :=       dm-raid4-5.o dm-log.o dm-mem-cache.o \
[14:18] <smb>                         dm-region_hash.o dm-message.o
[14:18] <smb> obj-m                   += dm-raid45.o
[14:18] <smb> that is the makefile in Hardy lum for it
[14:19] <apw> heh
[14:19] <apw> so we know that that works then ... good
[14:19] <manjo> ok one module it is ... one line change in makefile
[14:19] <apw> the second entry should be obj-$(CONFIG_...) += dm-raid45.o
[14:19] <smb> I laso renamed it from dm-raid4-5 to dm-raid45 because at that time the module registered itself with that name and
[14:20] <smb> there is some dm rules that normally load a module if you request a function's name
[14:20] <manjo> yeah I like to call it dm-raid45 instead of 4-5
[14:20] <smb> manjo, check the module code for the name it registers, to be on the safe side
[14:22] <smb> static struct target_type raid_target = {
[14:22] <smb>         .name = "raid45",
[14:22] <smb> At least the version in Jaunty did still name itself like this
[14:23] <apw> manjo, so you have a plan?
[14:23] <manjo> .name = "raid45",
[14:23] <manjo> yeah
[14:55] <manjo> smb, apw ok now built as one module ...
[14:55]  * smb pats manjo on the shoulder
[14:55] <manjo> a simple boot & load module test will be ok ?
[14:56] <smb> manjo, I would say for the first step. But be prepared for the Inquisition as soon as apw uploads it. ;-)
[14:56] <manjo> heh
[14:57] <manjo> yeah I figured that is bound to happen
[14:58] <manjo> apw, smb, btw there are no changes to iscsitarget
[14:58] <manjo> no new version out there
[14:59] <manjo> and looks like the same case with compcache
[14:59] <manjo> although in the case of compcache there is some effort going on to get it upstream
[14:59] <smb> manjo, Well ok, so there is nothing to do. Except maybe, get in touch with some server guys and ask them whether they would prefer to have it as dkms module
[15:00] <manjo> for iscsi ?
[15:00]  * smb nods
[15:00]  * manjo nods twice
[15:01]  * smb goes to fill another cup with dark liquid
[15:02] <hyperair> does anyone know why acpi-cpufreq has been built into the kernel rather than as a module since jaunty?
[15:02] <hyperair> i mean, does it make much difference in loading time?
[15:07] <smb> hyperair, That was the intention then. We are aware of the issues you got and we will think about it. Just cannot tell any outcome.
[15:08] <hyperair> smb: the phc-linux issue? okay then, thanks =)
[15:08] <hyperair> as long as it is given attention
[15:08] <smb> hyperair, Yes, it is. It is correct that this is a different gouvernor/driver which cannot get active as the built-in acpi-cpufreq is always there before.
[15:09] <hyperair> smb: in actuality, the phc linux module is just a patch on the acpi-cpufreq module. some implementations of the install turn it into a differently named module, but it's essentially acpi-cpufreq that's patched
[15:10] <hyperair> smb: or the amd one, which i can't remember the name of
[15:10] <smb> likely powernow-k8
[15:11] <smb> Hm, ok. So it would not help you, just to have an option to prevent acpi-cpufeq from getting active.
[15:11] <mjg59> Use ksplice
[15:11] <smb> mjg59, Don't let the security people hear ;-)
[15:13] <amitk> hyperair: is this code unlikely to go upstream?
[15:13] <smb> But in general I am a bit against this approach of having patched external modules replacing kernel modules...
[15:13] <hyperair> amitk: unlikely. it's been rejected before, because "it allows users to shoot themselves in the foot"
[15:13] <smb> amitk, It makes use of non-standard voltages and frequencies. What would you think=
[15:13] <smb> ?
[15:14] <mjg59> cpufreq upstream have rejected it, yes
[15:14] <amitk> fair enough.
[15:14] <hyperair> smb: well, if acpi-cpufreq is prevented from getting active, i think it's possible to inject the patched acpi-cpufreq module into the kernel via insmod
[15:14] <hyperair> smb: no, only non-standard voltages.
[15:15] <mjg59> It's not so much that it allows users to shoot themselves in the foot, it means that you're operating the kernel outside normal parameters and could cause all kinds of subtle failures which may appear to be kernel or app bugs
[15:15] <hyperair> smb: and it doesn't allow you to overvolt, only undervolt
[15:15] <mjg59> So you also get to shoot other people in the foot
[15:15] <bjf_afk> NOTICE: There will be a kernel team meeting on #ubuntu-meeting today at 17:00 UTC
[15:15] <mjg59> Tainting would deal with the kernel side, but it's like overclocking - it may be fine for everything except a very specific set of instructions, so it may seem like an application issue
[15:15] <smb> Yes, and being a replacement module also add to the maintenance nightmare
[15:17] <hyperair> perhaps a nice large warning by the phc guides =p
[15:17] <hyperair> or a huge warning in the dmesg log when the phc values are changed
[15:18] <amitk> hyperair: not good enough. We don't want to deal with such bugs _at all_ - whether kernel or app space. And app-space reports don't always ask for dmesg
[15:18] <smb> hyperair, The second sounds like a minimum.
[15:18] <hyperair> smb: what second?
[15:19] <smb> hyperair, A big dmesg warning. But as amitk says, that would not help if strange things happen in app space
[15:19] <hyperair> amitk: yeah it's true. well either way, it was rejected by upstream, and is probably not going in, so let's not worry about that issue. what i'm more concerned with is the ability to just recompile the module with the headers installed instead of having to recompile the whole kernel.
[15:20] <hyperair> in my case, my cpu + fan was going haywire so a kernel compile would cause it to overheat and shutdown
[15:21] <hyperair> undervolting the cpu did a great job at reducing the temperature though, and now i can deal with kernel compiles without having to go through a ^Z + fg cycle
[15:23] <mjg59> It's debatable whether it's actually an OS's job to make it easy for you to deal with broken hardware
[15:24] <smb> I can understand it to a degree from the user side, but as a distro that sort of thing sounds slightly scary
[15:25] <smb> I run one of my laptops with a upper frequency limit due to the fact that the fan cannot cope with it running full speed
[15:31] <hyperair> mjg59: a lot of hardware is broken, especially those with particularly stupid BIOSes. are you saying that we shouldn't support those because their hardware is stupid?
[15:32] <hyperair> smb: acpi-cpufreq compiled as a module; that's all i'm asking.
[15:32] <hyperair> smb: that's all is required to make it that much easier to set up phc-linux
[15:32] <hyperair> +that
[15:32] <mjg59> Compiling acpi-cpufreq as a module means compiling all of cpufreq as modules
[15:33] <hyperair> is that so?
[15:33] <smb> yes
[15:33] <hyperair> the tarball only contains a acpi-cpufreq.c
[15:33] <hyperair> and it can be compiled on the spot with just the kernel headers installed, if acpi-cpufreq is compiled as a module
[15:34] <hyperair> but either way, compiling all of cpufreq can't take more than a few minutes; maybe ~5 minutes or less on some decent hardware
[15:34] <hyperair> compare that to taking nearly an hour, or more to compile the kernel
[15:34] <smb> The sequence of probing can change the used driver. If you want to have control over that you have to compile them either all as modules or in
[15:34] <hyperair> the *entire* kernel, just because you want changes in that tiny part
[15:35]  * hyperair fires up menuconfig
[15:36] <hyperair> menuconfig doesn't seem to agree
[15:37] <smb> menuconfig does not care about policy
[15:38] <smb> If you want to prefer acpi-cpufreq over powernow-k7 for example, you cannot have powernow-k7 built in and acpi-cpufrq as a module
[15:38] <hyperair> what about both of them as modules?
[15:39] <hyperair> it's one or the other, isn't it?
[15:39] <hyperair> if you use acpi-cpufreq, you won't use powernow, and vice versa?
[15:39] <mjg59> No
[15:39] <hyperair> don't tell me you use both?
[15:39] <mjg59> No
[15:39] <hyperair> then?!
[15:39] <mjg59> But there are other drivers that may bind
[15:39] <hyperair> bind?
[15:39] <mjg59> To the processor
[15:39] <hyperair> blargh
[15:40] <mjg59> And if they're built into the kernel, you'll end up with that driver instead
[15:40] <mjg59> Hence, all built in or all modular
[15:40] <hyperair> let's look at it this way: intrepid and previous versions of ubuntu had acpi-cpufreq/powernowwhatever compiled as a module. why can't we revert the cpu freq scaling part back to that stage?
[15:41] <smb> As the decision was made in favour of boot time (and module loads at least had a bad impact on that), this depends on whether there might be less or no such penalty now.
[15:42] <hyperair> okay, so the deciding factor is now basically how much delay there is, am i right?
[15:42] <bjf> amitk, the other differences between my tree and yours is that I also rebased to the 2.6.31 karmic changes over the weekend
[15:43] <bjf> amitk, but I think those changes are in the same files (fewer of them)
[15:43] <bjf> amitk, any additional fixups were done as separate commits (which I was going  to squash before submitting)
[15:44] <smb> More or less. And probably too how the common feeling is to change a configuration for a, maybe not uncommon, corner case.
[15:44] <amitk> bjf: sure, I'm not worried about the state of the patches right now. I have a kernel the compiles from your tree currently. We can rework the patches later.
[15:44] <smb> hyperair, But the main part is the boot delay, yes
[15:45] <bjf> amitk, was just letting you know my thinking
[15:45] <hyperair> smb: so all i have to do is benchmark?
[15:45] <amitk> bjf: did you get your pegatron or b2 board booting with anything apart from your kernel?
[15:45] <hyperair> smb: in that case, which kernel version would you prefer me benchmark?
[15:46] <amitk> bjf: ack.
[15:46] <bjf> amitk, I got the b2 board booting with files from Freescale, The "P" board got shipped out and I never tried booting it.
[15:46] <bjf> amitk, don't have a "P" board now
[15:46] <smb> hyperair, At the moment, let us do a bit of research. There might be changes to user space that improve things too. So it is not only the kernel
[15:47] <amitk> bjf: ok, so we have different boards now.
[15:48] <bjf> amitk, you don't have a b2? (right, I remember now)
[15:48] <amitk> bjf: nope. And it took me all day today to chase down the right redboot image for my board.
[15:48] <hyperair> smb: alright, keep me updated then? =)
[15:49] <smb> hyperair, sure, I got the bug number and you are usually around ;-)
[15:49] <amitk> bjf: I am working towards a SD image where I can change kernels on the fly
[15:50] <bjf> amitk, I'd like that as well
[15:51]  * smb has them (sd cards) nearly all for i386 series
[15:53] <hyperair> smb: thanks =)
[15:55] <manjo> smb, zul from server is ok with dkm on iscsitarget... so I am going to go ahead and do it
[15:56] <manjo> currently testing dm-raid45
[15:56] <smb> manjo, I won't hold you back then. :)
[17:02] <manjo> smb, as you suspected ... building it as one module wont work... due to duplicate symbols
[17:02] <manjo> dm-raid45 wont load
[17:02] <manjo> smb, apw revert back to separate kos ?
[17:02] <smb> manjo, You might want to look at the hardy-lum
[17:03] <manjo> ok
[17:03] <smb> You can remove exports from those other modules
[17:03] <manjo> yeah that is what I was just thinkig
[17:05] <apw> yeah worth a try, we really only want that one loading that code for the raid45 versions
[17:05] <smb> And that got it linked, so it won't need the exports
[17:16] <Keybuk> apw: around?
[17:16] <apw> hello
[17:16] <Keybuk> could you cook me up a custom kernel with http://git.kernel.org/?p=linux/kernel/git/gregkh/patches.git;a=blob;f=driver-core/driver-core-devtmpfs-driver-core-maintained-dev-tmpfs.patch;h=22e58d1616d256d7fdd6c2c6365eea11de0123be;hb=6fcc499f41d83b8870b74f024aa906b85b700cb4 applied?
[17:18] <apw> Keybuk, looks interesting ... will do
[18:01]  * hyperair scratches his head regarding inotify issues in the current git kernel
[18:02] <hyperair> inotify_init()                          = -1 EMFILE (Too many open files)
[18:02] <hyperair> damn strange
[19:05] <Keybuk> hyperair: checked the available watches?
[19:05] <Keybuk> there are per-user limits on such things
[19:05] <hyperair> Keybuk: how do i check?
[19:05] <hyperair> Keybuk: i noticed it happened after restarting nautilus a few times
[19:05] <hyperair> i was testing nautilus-share, see
[19:05] <Keybuk> see if inotify_init() returns -EMFILE ;)
[19:06] <Keybuk>        EMFILE The user limit on the total number of inotify instances has been
[19:06] <Keybuk>               reached.
[19:06] <Keybuk> cat /proc/sys/fs/inotify/max_user_instances
[19:06] <Keybuk> then try poking a larger number than 128 into it
[19:06] <Keybuk> echo -n 1024 > /proc/sys/fs/inotify/max_user_instances
[19:06] <Keybuk> is a good start
[19:07] <Keybuk> you may want to increase /proc/sys/fs/inotify/max_user_watches at the same time (number of directories you can watch)
[19:07] <hyperair> hmmm
[19:07] <hyperair> well i do know that inotify_init definitely returned EMFILE
[19:07] <hyperair> strace of conky showed it
[19:07] <Keybuk> increase the maximum then
[19:08] <hyperair> too late. i already rebooted
[19:08] <Keybuk> :p
[19:08] <hyperair> logging out and logging back in didnt help for some reason =\
[19:08] <Keybuk> yeah, something was holding onto them
[19:08] <Keybuk> usually it's something like tracker, beagle, banshee, etc.
[19:08] <hyperair> banshee has no inotify support just yet
[19:08] <Keybuk> a session-bus activated service most likely
[19:08] <Keybuk> since they won't go necessarily away when you log out
[19:08] <hyperair> tracker and beagle don't run on my notebook
[19:08] <hyperair> i'm pretty sure banshee goes away though
[19:09] <hyperair> i should have done a killall -u hyperair then
[19:09] <hyperair> is there any way to check which processes are holding which inotify handles?
[19:09] <Keybuk> I tend to do kill -TERM -1
[19:09] <Keybuk> then kill -KILL -1
[19:09] <Keybuk> after logging in as me
[19:09] <hyperair> what's -1?
[19:09] <Keybuk> lsof will tell you
[19:09] <Keybuk> hyperair: "all"
[19:09] <hyperair> ah
[19:09] <Keybuk> if you don't do it as root, it just kills all yours
[19:10] <hyperair> yeah i know
[19:10] <hyperair> never thought of doing that
[19:22] <apw> Keybuk, the kernel  you wanted is uploading to: http://people.ubuntu.com/~apw/tmpfsdev-karmic/ ... should be complete shortly
[19:29] <manjo> smb, apw dm-raid45 loads as a module
[19:29] <manjo> single module
[19:29] <manjo> tested on karmic
[19:29] <manjo> 64 bit
[19:29] <apw> excellent, is that after removing the exports?
[19:30] <manjo> well had to remove the file entirely coz its already building in /drivers/md
[19:30] <manjo> and nothing was using it in ubuntu/
[19:30] <smb> which one
[19:30] <apw> which file?
[19:30] <manjo> dm-region-hash.c
[19:30] <smb> sorry I lost my crystal ball
[19:31] <smb> but the patch makes changes to region hash
[19:31] <apw> manjo, but the only reason thats there is cause it got changed ... what smb said
[19:32] <manjo> I left the changes in /drivers/md... are you guys thinking of having 2 copies of the same ?
[19:32] <apw> no the changes should have been moved over
[19:32] <apw> and the original restored
[19:33] <manjo> the changes cannot be moved over coz there are dependcies
[19:33] <apw> i mean apply the changes, copy the
[19:33] <apw> whole of the changes file
[19:33] <apw> changed file
[19:33] <apw> and then restore the original?
[19:33] <manjo> ah yes then you will have 2 copies of the same file
[19:33] <manjo> coz the patch changes the header file as well
[19:34] <apw> yes, we will but at least the original is unchanged, and cannot regress
[19:34] <apw> bring the .h file over to the same place too
[19:34] <manjo> ok I see what you mean... heh that is hack
[19:34] <apw> yes, but it is the safe hack
[19:34] <manjo> okies
[19:34] <apw> the normal people with the original dm get the original code
[19:34] <manjo> will do that now
[19:35] <apw> and 0 chance of a regression, the people who opt in to the new driver get the risk
[19:35] <apw> we are risk averse
[19:36] <manjo> hmm some how its botched way of doing it ... but less risky ofcourse
[19:36] <apw> yes it is indeed botched, but that is the risk averse way
[19:36] <manjo> k I am on it
[20:07] <mahfouz> I had a problem today with 2.6.30-10-generic in jaunty
[20:08] <mahfouz> talked to the people in #kernel but they only started a distro flame war
[20:08] <mahfouz> starting up with 2.6.30-10-generic, I get the splash screen all the way to the end but then an unresponsive black screen
[20:08] <mahfouz> it worked yesterday, but today it didn't anymore, even though there were no updates afaik
[20:32] <maxb> mahfouz: Well the obvious response is "If a karmic kernel doesn't work in jaunty, how about trying *Jaunty's* kernel with Jaunty?
[20:32] <mahfouz> because it screws up my intel video
[20:33] <mahfouz> I downloaded 2.6.30-10-generic from jaunty repo, you know?
[20:33] <maxb> No, you didn't.
[20:33] <mahfouz> It was in there temporarily, but now seems to be removed
[20:33] <mahfouz> I did
[20:33] <mahfouz> maybe it was xorg-edgers
[20:43] <mahfouz> yes, I downloaded 2.6.30-10-generic from the xorg-edgers ppa
[20:43] <mahfouz> but it worked at first and today it didn't boot anymore
[21:18] <amitk> bjf_afk: did you solve your xmodem problem?
[21:19] <bjf_afk> amitk, yes I did, user error
[21:43] <pgraner> dtchen: ping... when your around :-)
[22:05] <amitk> bjf_afk: http://pastebin.ubuntu.com/207169/ this is bad right? (size of uploaded kernel vs. size of default kernel partition in redboot)
[22:11] <bjf> amitk, yes, that looks wrong
[22:11] <bjf> amitk, got to look at my notes
[22:12] <bjf> amitk, no
[22:13]  * amitk is not too familiar with redboot
[22:17] <bjf> amitk, the size you uploaded is 0x1C5463 which fits
[22:19] <amitk> bjf: duh, I was forgetting the '1' in the start address
[22:19] <bjf> amitk, :-)


[01:41] <jbailey> doko: ping?
[01:48] <doko> jbailey: pong
[01:49] <jbailey> doko: I'm having a bitch of a time tracing down this last error from ld, hoping you can suggest something.
[01:50] <jbailey> When I install the libc6{-dev}-amd64 packages, ld tells me:
[01:50] <jbailey> /usr/bin/ld: warning: ld-linux-x86-64.so.2, needed by /lib64/libc.so.6, not found (try using -rpath or -rpath-link)
[01:51] <jbailey> The NEEDED section doesn't list a path in libc.so.6, so the implicit -L/lib../lib64 that collect2 hands over ought to be enough, I think.
[01:51] <jbailey> If I make a symlink in /lib to /lib64/ld-linux-x86-64.so.2, it compiles, and I can remove it after, so there's no runtime requirement.
[01:51] <jbailey> Just that for some reason ld beleives that there's a link time requirement.
[01:52] <jbailey> If I add an -rpath line to it, it works fine, but I think that it shouldn't be needed.
[01:53] <jbailey> (The warning is follow by some symbol errors which are in the ld-...so.2 - so it's not just randomly warning me)
[01:54] <doko> hmm, look at the i386-biarch patch in gcc-3.4. LINK_SPEC wants /lib64/libc.so.6
[01:54] <jbailey> Which is right.
[01:56] <jbailey> is it possible to get ld to dump out a list of what it thinks are the available libraries and howit resolved them?
[01:57] <jbailey> It seems almost certainly like a glibc problem, the same collect2 line done with amd64-libs works fine, but readelf -a looks basically the same between the two.
[01:57] <doko> hmm, not that I know of
[01:58] <doko> you see this with gcc-3.4 or gcc-4.0 ?
[01:58] <jbailey> -3.4
[01:58] <jbailey> So far I'm onyl working with that until I get the glibc built.
[01:58] <doko> and does the link step work with 4.0 (if you're doing only this one with 4.0)?
[01:59] <jbailey> Dunno.  I'll dig up a biarch gcc-4.0 to try that with.
[01:59] <jbailey> glibc doesn't build with gcc-4.0, so I hadn't been looking at that at all.
[01:59] <doko> just compared the biarch patches. 4.0 is missing the LINK_SPEC chunk
[02:00] <jbailey> Oh, hmm.
[02:19] <jbailey> YAR
[02:19] <jbailey> I wish I smoked so that I could stomp off and have one.
[02:19] <jbailey> It seems that biarch amd64 wants /lib64 and /usr/lib64 added to ld.so.conf
[02:20] <jbailey> doko: So my glibc is fine.  I just need to either put this hackery into ld.so.conf, I guess. =(
[02:21] <jbailey> Or fix it properly in the linker, I guess.
[04:42] <doko> jbailey: How is this solved for amd64 native?
[04:43] <doko> or isn't this an issue, because lib is a symlink to lib64?
[04:43] <jbailey> amd64 native has hackery in glibc to mke this all just work.
[04:43] <jbailey> My current build has the hackery in for i386 too.
[04:43] <jbailey> amd64 will need additional hackery to deal with /lib32 correctly.
[04:44] <jbailey> (but it's all in the same .h file in glibc)
[04:44] <doko> oh, fine.
[06:44] <elmo> fuck's sake
[06:44] <elmo> does anyone know how CONFIG_MAC gets defined?
[06:46] <jbailey> elmo: Context?
[06:46] <elmo> powerpc kernel builds
[06:46] <elmo> it's not mentioned in .config, but I'm getting some compile errors with breezy kernel and a custom config
[06:46] <jbailey> elmo: Try #ubuntu-kernel, better audience there.
[06:46] <elmo> meh
[06:46] <elmo> i'm about ubuntu'ed out of channels, never mind
[06:47] <jbailey> I'm thinking specifically zul, who does alot of kernel stuff with Fabio
[06:53] <fabbione> hey elmo
[06:54] <fabbione> elmo: iirc CONFIG_MAC is defined only on PPC32..
[06:55] <fabbione> if you need, i can check but arch/ppc/Kconfig (grep for MAC) is a good place to start
[07:09] <doko_> fabbione: gettext on sparc: please look at the config.log file to see, why the jar test fails.
[07:10] <fabbione> doko_: thanks i will :)
[09:52] <doko_> fabbione: do you have a sparc live CD, either hoary or breezy?


[06:45] <mborzecki> morning
[07:53] <mardy> mborzecki: hi!
[08:29] <mup> PR snapd#11305 closed: systemd: actually test the function passed as a parameter <Simple 😃> <Skip spread> <Created by bboozzoo> <Merged by bboozzoo> <https://github.com/snapcore/snapd/pull/11305>
[08:59] <zyga> o/
[10:22] <mup> Bug #1620771 opened: when /home is somewhere else, snaps don't work <link> <snap> <symlink> <Snappy:Triaged> <https://launchpad.net/bugs/1620771>
[10:25] <mup> Bug #1620771 changed: when /home is somewhere else, snaps don't work <link> <snap> <symlink> <Snappy:Triaged> <https://launchpad.net/bugs/1620771>
[10:28] <mup> Bug #1620771 opened: when /home is somewhere else, snaps don't work <link> <snap> <symlink> <Snappy:Triaged> <https://launchpad.net/bugs/1620771>
[10:31] <jamesh> mvo: from the discussion earlier: https://github.com/snapcore/snapd/pull/11312
[10:31] <mup> PR #11312: cmd/snap-update-ns: convert some unexpected decimal file mode constants to octal <Created by jhenstridge> <https://github.com/snapcore/snapd/pull/11312>
[10:35] <mup> PR snapd#11312 opened: cmd/snap-update-ns: convert some unexpected decimal file mode constants to octal <Created by jhenstridge> <https://github.com/snapcore/snapd/pull/11312>
[10:50] <mup> PR snapd#11308 closed: asserts: start splitting out attrMatcher for reuse to constraint.go <Skip spread> <authority-delegation> <Created by pedronis> <Merged by pedronis> <https://github.com/snapcore/snapd/pull/11308>
[11:19] <mvo> jamesh: \o/
[11:19] <jamesh> mvo: are we still using Go < 1.13 anywhere? If not, we could make the more invasive change of moving all octal constants to 0oNNN syntax
[11:20] <jamesh> which would be harder to screw up
[11:24] <mvo> jamesh: 1.13 everywhere
[11:37] <mardy> mborzecki: I'm having a hard time trying to figure out how and when Changes are created out of a Task. Most of the calls to NewChange seem to be in the unit tests, and those who are not seem to be very specific to some use-cases
[11:43] <mborzecki> mardy: quick call?
[11:45] <mardy> mborzecki: sure
[12:55] <mup> PR snapd#11288 closed: o/snapstate: write state when undoing migration <Created by MiguelPires> <Closed by MiguelPires> <https://github.com/snapcore/snapd/pull/11288>
[13:05] <mup> PR snapd#11313 opened: o/snapstate: re-write state after undo migration <Created by MiguelPires> <https://github.com/snapcore/snapd/pull/11313>
[13:46] <mup> PR snapd#11304 closed: snap/quota: add positive tests for the quota.Resources logic <Skip spread> <Created by Meulengracht> <Merged by bboozzoo> <https://github.com/snapcore/snapd/pull/11304>
[13:46] <mup> PR snapd#11310 closed: tests: skip version check on lp-1871652 for sru validation <Squash-merge> <Created by sergiocazzolato> <Merged by bboozzoo> <https://github.com/snapcore/snapd/pull/11310>
[14:20] <mborzecki> ijohnson: found this one related to connections: https://github.com/snapcore/snapd/pull/10814
[14:20] <mup> PR #10814: o/ifacestate: don't lose connections if snaps are broken <Squash-merge> <Bug> <cherry-picked> <Created by stolowski> <Merged by mvo5> <https://github.com/snapcore/snapd/pull/10814>
[14:56] <mup> PR snapd#11294 closed: tests: use system ubuntu-21.10-64 in nested tests <Run nested> <Created by sergiocazzolato> <Merged by mvo5> <https://github.com/snapcore/snapd/pull/11294>
[15:01] <ijohnson[m]> bboozzoo: thanks I'll have a look
[15:46] <mup> PR snapd#11314 opened: systemd: batched operations <Created by bboozzoo> <https://github.com/snapcore/snapd/pull/11314>
[17:57] <gloin> Hey, it's been 24 hours and am still seeing "too many requests" trying to connect to the API.
[17:58] <gloin> https://api.snapcraft.io/api/v1/snaps/names?confinement=strict%2Cclassic
[17:58] <gloin> try connecting to that and see ^^
[17:58] <gloin> this is causing snapd.failure.service to fail to start on an EL7 box
[18:03] <gloin> Anyone? Please? It's been an entire day.
[18:04]  * gloin apologizes for this, but
[18:04] <gloin> mardy: you've got the canonical tag. Can you please help?
[18:47] <mup> PR snapd#11312 closed: cmd/snap-update-ns: convert some unexpected decimal file mode constants to octal <Created by jhenstridge> <Merged by mvo5> <https://github.com/snapcore/snapd/pull/11312>
[18:49] <ogra> gloin, use the store category in the forum to get store people attention ..
[19:02] <mup> PR snapd#11177 closed: many: add altlinux support <Created by shaba> <Merged by mvo5> <https://github.com/snapcore/snapd/pull/11177>
[20:22] <mup> PR snapd#11251 closed: devicestate: ensure permissions of /var/lib/snapd/void are correct <Test Robustness> <Created by mvo5> <Merged by mvo5> <https://github.com/snapcore/snapd/pull/11251>
[20:27] <mup> PR snapd#11301 closed: tests: ensure the ca-certificates package is installed <Simple 😃> <Created by mvo5> <Merged by mvo5> <https://github.com/snapcore/snapd/pull/11301>
[20:48] <mup> PR snapd#11315 opened: lp1844776 fix snap run command auto completion <Created by patriciadomin> <https://github.com/snapcore/snapd/pull/11315>


[02:20] <Sarvatt> RAOF: we're on the same flight from LHR to BUD
[02:24] <Sarvatt> australia to london then 3 hours back to budapest. silly flight :)
[02:30] <bryce> Sarvatt, think he's left already?
[22:12] <FernandoMiguel> evening


[01:08] <ailo> paultag, Hey.
[01:09] <ailo> I was just looking into Python libraries. python-pam and python-gksu. Stuff that I should have used over the shell scripts I used for the -controls
[01:10] <ailo> Anyway, seems like you've been very busy lately.


[21:56] <gorgonizer> jimdb: my system is currently running a mixture of the experimental and project-neon packages.. after adding the nightly packages, the system does seem more stable, I admit.. would you recommend removing the experimental repo and just using the project-neon packages alone?
[21:57] <jimdb> gorgonizer: if you know how.
[21:57] <jimdb> i have left mine alone.
[21:57] <martijn81> when i connect two usb hard disks, only one is recognized by kde
[21:57] <martijn81> what can i do about this?
[21:59] <hubar> jimdb, what is project neon?
[22:01] <gorgonzola> hello. i am trying to install kimldonkey on kde 4.2, but apt complains that kmldonkey dependes on libplasma2, which has been deprecated by kde 4.2. is there any way to install the package? (download and change the deps?)
[22:01] <wrt_> Hi )))
[22:01] <jimdb> hubar:  though it doesn't have nightly builds it does have regular updates.  it is essentially kde 4.2 without having to use kubuntu's repositories.
[22:04] <martijn81> gorgonzola: yeah, you could compile from source
[22:04] <jimdb> does anyone know how to get the systray widget to update more frequently?  it appears to have a bug where, if you remove a program from it (by closing the program) the icon to the left of the one you closed will sit atop the remnant icon from the one you closed.
[22:04] <hubar> jimdb, It has its own repository?
[22:04] <gorgonzola> . . .
[22:05] <jimdb> hubar:  http://www.cyberciti.biz/faq/ubuntu-linux-install-kde-42/
[22:05] <gorgonizer> hubar: yes it does,     deb http://ppa.launchpad.net/project-neon/ppa/ubuntu/ intrepid main
[22:05] <gorgonzola> matijn81: you mean download the source with apt and build a custom deb?
[22:05] <jimdb> hubar:  yes
[22:05] <gorgonzola> gorgonizer: dude where did you get your nick from?
[22:06] <gorgonizer> gorgonzola: A band from Nottingham called Iron Monkey performed a song called Supagorgonizer..
[22:06] <gorgonizer> hubar: gpg --keyserver keyserver.ubuntu.com --recv-keys 778978B00F7992B0 && gpg --export -a 778978B00F7992B0 | apt-key add -   will add the auth-key for it I believe..
[22:07] <jimdb> gorgonizer:  key for what?
[22:08] <gorgonizer> jimdb: to stop the authentication warning for packages from the project-neon repository
[22:09] <gorgonizer> jimdb: to be honest, I shoehorned that command together, but it seemed to work :)
[22:11] <jimdb> i have k/ubuntu installed on may 7 machines here and have been migrating them to kde 4.2.  On this machine I must have had it in place, so I got an error.  On a couple other machines I get that warning.  Now to get that command issued on each machine.
[22:11] <jimdb> gorgonizer:  that was meant for you  :)
[22:11] <gorgonzola> ok, new question: how can i modify the dependencies of a souorce package?
[22:12] <jimdb> gorgonizer:  this machine is my multimedia box.  i have it attached to a 32" TV using a DVI to HDMI cable.  I use it with boxee, xbmc, vlc, my iphone remote apps, and use it as a phone via skype.
[22:12] <gorgonizer> jimdb: thought so, hope it is the right command, if so, that warning will be a thing of the past :)
[22:13] <jimdb> it look awesome and is awesome.
[22:13] <gorgonizer> jimdb: that sounds one hell of a setup :)
[22:14] <jimdb> gorgonizer: i used parts I had laying around.  I only had to buy the dvi to hdmi cable, the iphone apps ($2.00 a piece) and the TV (which I essentially already had)...so it didn't cost much.
[22:14] <jimdb> it worked well under gnome, but it looks awesome and works well under kde 4.2
[22:15] <gorgonizer> jimdb: I can imagine teat KDE 4.2 must look superb on a screen that size :)
[22:16] <ikazmi> hi every1
[22:17] <ikazmi> has any1 been able to get a pcmcia card working under 9.04?
[22:17] <ikazmi> i got a audigy 2 zs pcmcia sound card and its not working
[22:18] <jessie> Hey, can you guys hear me?
[22:18] <jimdb> gorgonizer:  my main box is a linux box also with a 24" HD lcd widescreen monitor. it looks very good there too. but I use this one for hulu, boxee, xbmc, dvds, AVIs.  I was reading a slashdot.org post the other day where they were discussing someone's project to create something similar to this.  my costs were 1/2 of his.
[22:18] <ikazmi> (it doesnt even seem to trigger any remove or insert events)
[22:19] <ikazmi> ?
[22:19] <jimdb> ikazmi:  i believe you have to compile the sound driver from source which you get at creativelabs website.
[22:19] <jimdb> ikazmi:  and I don't believe linux has the same sort of triggered events like winxp/vista has.
[22:20] <ikazmi> jimdb: but shouldn't lspci or dmesg have something to show that new hardware was added
[22:21] <ikazmi> jimdb: i remember from slackware days that when a usb was plugged in but there was something wrong with it, dmesh would have kernel messages
[22:21] <ikazmi> jimdb: in this case there is nothing...as if i haven't even plugged it in, same with lspci
[22:22] <ikazmi> ?
[22:24] <jimdb> ikazmi:  i have a creativelabs card and was able to get the sound to work by compiling the drivers.  i don't remember if lspci showed it listed.
[22:24] <jimdb> ikazmi:  though I have a card similar to yours I don't use it.
[22:26] <ikazmi> jimdb: which version of kubuntu are you using?
[22:33] <wildbat> Hihi
[22:34] <theunixgeek> How do I set up Kmail to display HTML messages properly?
[22:35] <carpii> what do you mean, properly ?
[22:36] <carpii> try settings -> configure kmail -> security tab -> reading -> prefer html tickbox
[22:36] <wildbat> >.>b use Thunderbird ! XD
[22:37] <carpii> kmail is pretty nice. I used thunderbird on windows for a coupla years but it always felt klunky :/
[22:37] <theunixgeek> carpii: so it actually displays HTML formatting
[22:38] <carpii> ok well try what i said above
[22:38] <carpii> that should do it
[22:38] <theunixgeek> carpii: oh, I didn't see that; I'll try it
[22:39] <theunixgeek> ah, that's better :)
[22:39] <theunixgeek> thanks, carpii
[22:39] <carpii> np :)
[22:40] <theunixgeek> :)
[22:40] <derdui> hi, does anybody know, if oovoo runs under linux? didnt find anything with google
[22:40] <wildbat> neverone here know about smb? ~ i am trying to auto mounting the all the sharepoints ~ is that a program or script can do that ?
[22:40] <zer0o> hi, how do i format completely in ext3 or fat32 an external hard drive?
[22:41] <carpii> wildbat, you can put it in your /etc/fstab if you install package smbfs
[22:43] <zer0o> hi, how do i format completely in ext3 or fat32 an external hard drive? from a terminal
[22:43] <carpii> use mkfs
[22:44] <wildbat> carpii: yea but what i mean auto is it detect and smbshares and mount it ~
[22:44] <zer0o> carpii: could u plz explain further?
[22:45] <carpii> wildbat, ok i dont know how to autodetect samba shares, sorry
[22:45] <carpii> zer0 try something like this http://www.ehow.com/how_1000631_hard-drive-linux.html
[22:45] <zer0o> kk
[22:46] <wildbat> carpii: is ok ^^
[22:47] <wildbat> guess i have to figureout a script..... hmmmm
[22:49] <carpii> the problem is if you have a samba share and it suddenly goes offline, things tend to lock up
[22:49] <carpii> so i only really use samba for locations i know will always be available really
[22:50] <wildbat> yea ~ that give me headache XD
[22:52] <psyco> hey, im trying to install kde 4.2 on 8.10 but in adept i get this error
[22:53] <psyco> http://pastebin.com/mb2f7271
[22:53] <psyco> and i click OK and get this
[22:53] <psyco> http://pastebin.com/m68c1bbcc
[22:54] <cjae> !virtualbox
[22:55] <psyco> libplasma3 isn't in my repos
[22:57] <zer0o> carpii: ok after having it formatted there's a folder in it called lost+found that i cant open, whatz that?
[22:57] <cjae> psyco: http://www.kubuntu.org/news/kde-4.2-beta-2
[22:57] <Dr_Willis> psyco,  thats normal - leave lost+found alone.
[22:58] <zer0o> Dr_Willis: ok ok but i'd like to no what it is
[22:58] <Dr_Willis> Its used by the fsck tools
[22:58] <KWGoD> ASSERT: *** Search: _installLocation: engine has no file!
[22:59] <KWGoD> Stack Trace:
[22:59] <KWGoD> 0:ENSURE_WARN(false,_installLocation: engine has no file!,2147500037)
[22:59] <KWGoD> 1:()
[22:59] <KWGoD> 2:()
[22:59] <KWGoD> 3:()
[22:59] <KWGoD> 4:epsGetAttr([object Object],hidden)
[22:59] <KWGoD> 5:()
[22:59] <KWGoD> 6:()
[22:59] <KWGoD> 7:currentEngine()
[22:59] <KWGoD> 8:get_currentEngine()
[22:59] <KWGoD> 9:updateDisplay()
[22:59] <KWGoD> 10:init()
[22:59] <KWGoD> 11:([object XULElement],11)
[22:59] <KWGoD> help?
[22:59] <jasonR> Hey Gang. Issues with sound on an HP Pavilion 061. the snd_intel_hda driver is loaded, but the mixer (don't matter which) does not have a volume slider. It only shows... IEC958
[23:00] <psyco> cjae: I know that, thats what I used
[23:00] <psyco> Dr_Willis: so should I just ignore it?
[23:00] <cjae> psyco: hang on
[23:01] <zer0o> Dr_Willis: i didnt ask who or what uses it, i asked what it is
[23:01] <carpii> KWGod, dont paste big blocks
[23:01] <zer0o> nevermind
[23:01] <psyco> !pastebin
[23:01] <Dr_Willis> zer0o,  its where lost and found files by fsck go.
[23:02] <psyco> brb gonna reboot X
[23:03] <zer0o> Dr_Willis: ok so its a system folder, got it
[23:03] <cjae> psyco: I just had those issues on another box, but cant remember the steps I used to fix, I had to sudo apt-get -f install, then sudo dpkg --configure -a, then... I have to find the website again I had to just get to the login page and then reconfigure kde but can't remember the command
[23:04] <Dr_Willis> 'system folder' another vague term. that means very little - heh.
[23:04] <zer0o> is anyone able to help with XANDROS?
[23:04] <cjae> wow
[23:04] <Dr_Willis> Xandros should ahve their own channel. Last i used xandos was years+ ago.. and it wasent very impressive then.
[23:05] <zer0o> "system folder" to me means a folder that has to be where it is, not something coming from the previous winxp s**t :D
[23:05] <jasonR> Dr_Willis, you any good at trouble-shooting hardware issues? :-)_  This sound card is kickin' my butt!
[23:05] <Dr_Willis> Hmm.. from Distrowatch homepage.. last xandros release was in 2006 - Ick
[23:05] <Dr_Willis> jasonR,  depends on the issue i guess.
[23:05] <jasonR> Oops! Wrong Nick! I'm shelled into his machine. Let's 'fix' that...
[23:06] <zer0o> it isnt on my machine, it's a friend's i run kubuntu, she's got this mini eeepc. ridiculous but she needs some help and thus im here on google, forums and chats LOL
[23:06] <Dr_Willis> Xandros Acquires Linspire, 07-02-2008 - Hmm.. i never noticed that. :)
[23:06] <KWGoD> i ned help with firefox
[23:06] <KWGoD> need*
[23:06] <Zirg> Dr_Willis, it's an HP box that DID have sound on the first install, but KDE4 was buggy so we stepped back to 8.04.
[23:07] <Dr_Willis> I use the eeebuntu variant on my Net-book. it works very well.
[23:07] <Zirg> Dr_Willis, it has the snd_hda_intel driver loaded, but the mixers (all) do NOT have a slider to adjust the audio (yes, /dev/mixer exists and no others) and the only thing showing in the mixer is  IEC958
[23:07] <zer0o> this one is superslow its a mini pc i'll show u www.eeeuser.com
[23:08] <Dr_Willis> xandros homepage shows one also. :)
[23:08] <Dr_Willis> I find my AcerAspireOne to be quite snappy in Ubuntu+gnome.
[23:08] <Dr_Willis> it even does XP very well.
[23:08] <zer0o> sure :D its pretty much the only pc on earth where they put it lol
[23:08] <Zirg> Dr_Willis, http://pastebin.com/f472109d    is the output of lsmod | grep snd
[23:09] <Dr_Willis> Zirg,  so has sound ever worked on this thing in 8.04? Try a 8.04 live cd/ubuntu cd?
[23:09] <Zirg> Dunno. Let me ask....
[23:09] <Dr_Willis> Zirg,  its possible its just some mixer/slider setting. you could try that console based alsa-mixer tool instead of the kde ones
[23:10] <Zirg> Dr_Willis, hmmm. seems he's unsure if it EVER worked. :-(  Okay, wished there was a way to shell into his BIOS screens with him! :-(
[23:11] <zer0o> Dr_Willis: so r u able to help me in mounting this external hard drive on xandros? is driving me nuts!
[23:12] <carpii> zer0, do you know the device name of it?
[23:12] <zer0o> carpii: before it was sdc
[23:12] <carpii> before what?
[23:13] <Zirg> Dr_Willis, Thanks. I  will get him into the CMOS again and try some other settings. Good Coding, Dawg!
[23:13] <zer0o> carpii: when i plug it in (and ive just format it with ext3 on my kubuntu on another machine) it says "the path /home/user/1600BEV External does not exist" i dont get it
[23:14] <zer0o> carpii: anyway i just gave an mkdir "/home/user/1600BEV External" lets see what happens
[23:14] <Dr_Willis> zer0o,  when in doubt - fall back to the command line and mount it manually. look for errors.
[23:14] <Dr_Willis> zer0o,  you DID make the mount point directory?
[23:14] <Dr_Willis> DONT use spaces in the filename/directory name.. it will cause issues
[23:14] <zer0o> Dr_Willis: im trying but it seems this Xandros has different commands
[23:15] <Dr_Willis> xandros is based on debian..it better have the 'mount' command
[23:15] <zer0o> i haven't decided it myself its what it pops out when plugged it in
[23:15] <zer0o> yes it does have it
[23:15] <Dr_Willis> HAL/the automounting stuff may be trying tobe cute with the path name. if the volume name has a Space in the name.
[23:15] <Dr_Willis> It just makes life MUCH easier if you eliminate such spaces.
[23:16] <zer0o> just to make sure ive done a mkdir "/home/user/1600BEV External" since before it was saying it wasnt finding it i created it lets see (just plugged in)
[23:16] <zer0o> Dr_Willis: i haven't decided it myself its what it pops out when plugged it in
[23:17] <Dr_Willis> thats HAL deciding to do things.. You can still mount it manually i imagine whever you want
[23:17] <zer0o> i dunno the name of it otherwise i'd had done a "pmount sdX"
[23:17] <Dr_Willis> Im suprised its trying to mount to /home/USERNAME/anything
[23:18] <Dr_Willis> seems that /mnt or /media would be the proper place for it to mount stuff to
[23:19] <zer0o> i agree
[23:19] <zer0o> so what should i do? litterally
[23:19] <Dr_Willis> sudo mkdir /media/THEDRIVE
[23:19] <Dr_Willis> sudo mount /dev/WHATEVER /media/THEDRIVE
[23:20] <Dr_Willis> and see if it mounts
[23:20] <zer0o> yes i no that but i dunno the name Doc
[23:20] <Dr_Willis> sudo fdisk -l
[23:20] <Dr_Willis> to see all attatched drives
[23:20] <Dr_Willis> or chedk 'dmesg' command whenya plug it in
[23:24] <zer0o> Dr_Willis: ok this is really weird, when plugged in i gave "fdisk -l" and 4 devices came out sde1-2-3-4 and relative info bout them, then i unplugged it, re-gave "fdisk -l" and it says bas: fdisk: command not found" what the heck???
[23:24] <Dr_Willis> use sudo fdisk -l ?
[23:25] <Dr_Willis> usb drives might be shown by a user running fdisk.
[23:25] <Dr_Willis> sounds liek the thing may be sde## in your case
[23:27] <zer0o> alright it says "Disk /dev/sda: 4001mb, 4000....... bytes" 255 heads, 63 sectors/track, 486 cylinders"
[23:27] <zer0o> then Device Boot
[23:27] <Dr_Willis> sda is proberly the internal hard drive.
[23:27] <Dr_Willis> sdb+ will be what others you got plugged in
[23:28] <zer0o> i dont think so cuz after this one it shows its own partitions
[23:28] <zer0o> sda1
[23:28] <zer0o> sda2
[23:28] <zer0o> till 4
[23:28] <zer0o> and each one START at some number and END and some other consequentially with the others
[23:29] <Dr_Willis> a hard drive can have up to 4 primary partitions normally.
[23:29] <Dr_Willis> 1 hard drive = sda1 through whatever...
[23:29] <zer0o> okokok after a long amount of time
[23:29] <zer0o> its finally appeard
[23:29] <zer0o> its name si sdc
[23:29] <zer0o> as before
[23:29] <Dr_Willis> it takes a few sec for a usb drive ti get seen after its plugged in.
[23:30] <zer0o> actually it says Disk /dev/sdc: 160 gb etc etc
[23:30] <zer0o> and below it goes
[23:30] <zer0o> dev/sdc1
[23:30] <zer0o> whatz itz name then?
[23:30] <zer0o> :D
[23:30] <zer0o> LOL
[23:30] <Dr_Willis> sdc1
[23:30] <Dr_Willis> logically :)
[23:30] <zer0o> ok cool
[23:30] <zer0o> sorry im not that logical with linux
[23:31] <Dr_Willis>  sdc is the drive.. sdc1 is the partition ON THE DRIVE
[23:31] <zer0o> started to use it like 2 moths ago :D
[23:31] <Dr_Willis> thats the thing to rember
[23:31] <zer0o> ok thanks
[23:31] <zer0o> so now its mounted
[23:31] <Dr_Willis> a cdrom would be just 'sdc'
[23:31] <zer0o> cuz theres no partition
[23:35] <zer0o> Dr_Willis: alright i went to /dev/disks/Removable/ where there are "sdb" which i dunno what it is and "sdc" (not sdc1 though) tried to open sdc with double click it asks me with what i choose among the applications File Manager and while trying to the terminal give this output "QmetaObject::findSignal:CrightPanle: Conflict with QlistView::selectionChanged()" what the heck does this mean?
[23:37] <jefferai> hey guys
[23:37] <jefferai> how scary is upgrading to jaunty right now?
[23:37] <jefferai> and also, how scary is creating your own package?
[23:37]  * jefferai is inexperienced in the apt world
[23:37] <Dr_Willis> zer0o,  you dont want to be double clicking in /dev/disks/ at ALL i imagine.. those are not the mount points.
[23:38] <Dr_Willis> zer0o,  you access the mountpoint. not the device.
[23:38] <Dr_Willis> zer0o,  if you mounted the thing to /media/THEDRIVE  then access that locatiion with the filemanager
[23:39] <zer0o> ok let me try
[23:45] <kalib> Hi people.. I just intalled kubuntu.. the last one..
[23:45] <kalib> But, my broadcom wireless is not working.. Hav any idea?
[23:45] <Dr_Willis> first read up pn the wireless docs.. and determine your exact chipset.
[23:45] <Dr_Willis>  broadcom makes a lot :)
[23:46] <Dr_Willis> !wireless
[23:47] <kalib> ;]
[23:50] <Dr_Willis> for my woreless card i just had to install the b43-fwcutter package.
[23:57] <kalib> Dr_Willis, it's broadcom?
[23:57] <Dr_Willis> b43Xx yes.
[23:58] <Dr_Willis> broadcom makes a LOT of chipsets
[23:58] <kalib> yeah.. I know.. that's my girlfriend's laptop..
[23:59] <kalib> I'm installing it for her..
[23:59] <kalib> I never had this kind of problem with mine... My laptop's wireless chipset is Atheros
[23:59] <kalib> works fine..


[00:19] <bluesabre> evening all
[00:21] <Unit193> Hello, bluesabre.
[00:21] <bluesabre> flocculant, should be fine, also going to hit all of the tests tonight
[00:21] <bluesabre> hey Unit193 :)
[00:24] <bluesabre> Unit193, how's it going?
[00:25] <Unit193> bluesabre: Watching a bit of something before heading out to a social thing tonight. :3  (IE, nothing for Xubuntu. :P )
[00:25] <bluesabre> :)
[00:26] <bluesabre> good for you, its nice to be social once in a while ;)
[00:28] <Unit193> Oh?  Huh, news to me.
[00:34] <bluesabre> :D
[00:39] <Unit193> How 'bout you, bluesabre?
[00:40] <bluesabre> Pretty good, got home a bit later than desired but going to try to be productive the rest of the night
[02:39] <bluesabre> flocculant, importantish package updates, somewhat relevant bugs between xenial and yakkety (it's been a slow cycle), http://paste.ubuntu.com/23315791/
[02:47] <krytarik> bluesabre: LP #1529689 was fixed in Xenial already too though: http://changelogs.ubuntu.com/changelogs/pool/universe/i/inxi/inxi_2.2.35-0ubuntu1/changelog
[02:48] <bluesabre> darn
[02:48] <bluesabre> :D
[06:18] <flocculant> bluesabre: thanks
[07:35] <flocculant> did some hardware and vm this morning on 32bit - ready to mark them
[07:35] <flocculant> knome: x.org announcement mostly done now
[11:01] <flocculant> marked them ready now
[12:21] <ochosi> thanks flocculant!
[16:13] <bluesabre> hey everyone
[16:14] <flocculant> everyone left about 3 months ago
[16:14] <flocculant> the rest of us are still here :)
[16:15] <bluesabre> darn it
[16:15] <bluesabre> :p
[16:15] <flocculant> how's Thursday treating you?
[16:15] <bluesabre> pretty good
[16:16] <bluesabre> are we officially released now?
[16:16] <flocculant> added bugs to release note - added inxi
[16:16] <flocculant> nah
[16:16] <flocculant> not released yet
[16:16] <bluesabre> :D
[16:16] <bluesabre> k
[16:16] <bluesabre> need anything from me?
[16:16] <flocculant> nope - all good as far as I know
[16:17] <flocculant> we can edit the announcement later when you know what you want to say :D
[16:17] <bluesabre> couldn't really think of what to say, but your bit at the end seemed good
[16:17] <flocculant> I wrote something?
[16:17] <bluesabre> thought so :D
[16:18] <flocculant> oh
[16:18] <flocculant> I didn't write that ... I  copied it from whatever knome wrote last time :p
[16:18] <bluesabre> "Thanks to all who have contributed to Xubuntu, not least those who test for us when called upon, and generally anyone can do that for us all.  Thank you on behalf of all installing Xubuntu – you all rock!" seemed like something
[16:19] <bluesabre> aha
[16:19] <flocculant> *I* wrote the gtk3 bit at the beginning :p
[16:19]  * bluesabre claps
[16:20] <flocculant> tried to make it sound like you did something in the last 6 months :D
[16:20] <bluesabre> I had to grab at straws for the release announcement on my site as well
[16:21] <bluesabre> "oh, I did this, and Simon wrote about that"
[16:21] <flocculant> we'll need to sort the get xubuntu page out before too long - if no-one else gets to it, I'll make something that works
[16:21] <bluesabre> cool
[16:22] <bluesabre> I won't do any editing right now, but I can follow up tonight as needed
[16:22] <flocculant> bank sent me a txt - which I nearly spam banned - apparently fraud ...
[16:22] <flocculant> yup - ok - if you can prettify - we needs peoples on the announcement that'll be cool
[16:23] <flocculant> I think website team does stuffs too
[16:23] <bluesabre> yeah
[16:23]  * bluesabre reminds knome that its release day
[16:27]  * flocculant doesn't know if he can change getxubuntu page and it saves but doesn't publish :D
[16:28] <flocculant> knome: I hates the openid thing with our website - keep getting issues with it :|
[16:28] <flocculant> blames pleia2 for a change :)
[16:28] <bluesabre> alrighty, out for now, bbl
[16:28] <bluesabre> have fun with the *official* release
[16:29] <flocculant> cya later - might still be around when you are
[16:44] <flocculant> and we're published now
[16:49]  * flocculant looks at getxubuntu and wanders off again
[16:50] <flocculant> akxwi-dave: good luck then :D
[17:22] <nairwolf> hi ;)
[17:22] <nairwolf> if there is anything I can help
[17:23] <nairwolf> tell me
[17:26] <flocculant> nairwolf: stuff left to do now is for specific xubuntu teams - other than support which you can do in #xubuntu :)
[17:26] <nairwolf> ok ;)
[17:26] <nairwolf> I'm currently writing some notes for a collaborative french website linuxfr.org
[17:27] <nairwolf> the final version will be the same iso than 20161012.2 ?
[17:28] <flocculant> http://cdimage.ubuntu.com/xubuntu/releases/16.10/release/
[17:47] <nairwolf> youpi !!!
[17:52] <nairwolf> The Release Notes for 16.10 will be the same as this page ? https://wiki.ubuntu.com/YakketyYak/FinalRelease/Xubuntu
[17:53] <flocculant> http://xubuntu.org/news/xubuntu-16-10-release/
[17:56] <nairwolf> Thank you flocculant ;)
[18:44] <flocculant> knome: temporarily added yak as a seperate section below the lts stuff - at least it's now listed there for people
[18:51] <knome> ta, i'll try to get the website in order today..
[18:52] <flocculant> knome: ok - just wanted to get a download somewhere on x.org :)
[18:53] <knome> yup
[18:53] <flocculant> docs obviously needs updating
[18:53] <knome> yep
[18:53] <knome> i'll look at that too
[18:54] <flocculant> yea - on the process I remember
[18:54] <knome> i've been sick all week - enterovirus - which is why i haven't done much...
[18:54] <flocculant> basically - just letting you (and everyone else) where we were :)
[18:54] <flocculant> oh nasty :~(
[18:55] <knome> it's annoying, but i'm not feeling very sick any more
[18:55] <flocculant> :)
[18:59] <knome> ok, bbl
[19:00] <flocculant> cya tomorrow or something
[19:18] <nairwolf> what does that mean this sentence ?
[19:18] <nairwolf> however much has been done towards supplying Xubuntu with Xfce packages built with GTK3, including the porting of many plugins and Xfce Terminal to GTK3. Those GTK3 ports can, if one wishes to test them, be installed from one of the team’s development PPAs
[19:19] <nairwolf> Does that mean Xfce Terminal doesn't use GTK3 yet, at 16.10 ?
[19:19] <flocculant> people have been working on gtk3 ports - they are available at the ppa
[19:21] <nairwolf> ok
[19:24] <nairwolf> but they aren't available directly on the OS.
[19:24] <nairwolf> Why ? (it's just to know). Is it still considered unstable ?
[19:36] <flocculant> not sure - not necessariyl about stability - just that it's something people are working on
[19:37] <flocculant> time to rest now
[19:37] <knome> nighty flocculant
[19:37] <flocculant> not bed resting - just not worrying about 16.10 anymore :)
[19:37] <knome> heh
[19:38] <knome> just updating the website and docs
[19:38] <flocculant> oh cool - thanks :)
[19:38] <knome> np
[19:38] <knome> the download page is up already
[19:38] <knome> now building docs on the dev server
[19:38] <flocculant> didn't really know what we wanted to do about these standard releases on getxubuntu tbh
[19:38] <nairwolf> okay, thank you flocculant
[19:38] <flocculant> good that we shout the lts at the top
[19:38] <knome> yep, i think LTS is always the first one
[19:39] <flocculant> on there yea for sure
[19:39] <flocculant> on *here* - not so much :D
[19:39] <knome> now that we have this nice release thing going on, maybe we can try to improve the updating of the download page as well
[19:39] <flocculant> oh yea that
[19:39] <knome> eg. only show the latest LTS by default, then link to the release pages for other downloads or sth
[19:39] <nairwolf> knome: something really really not critical, but you forget a dot at the end of the second paragraph of this page : https://xubuntu.org/news/xubuntu-16-10-release/
[19:40] <flocculant> that took me a while to figure out :p
[19:40] <nairwolf> " if one wishes to test them, be installed from one of the team’s development PPAs"
[19:40] <nairwolf> I supposed you wrote this
[19:40] <knome> nairwolf, i didn't :P
[19:40] <flocculant> nairwolf: that's cos punctuation is for foreigners :p
[19:40] <nairwolf> oh
[19:40]  * flocculant goes to remove all punctuation from the internet
[19:40] <flocculant> bbl
[19:41]  * flocculant sets up krytarik to nairwolf aliases
[19:42] <flocculant> knome: if you can think of how to say something, bluesabre wanted (a while back) to use the announcement to call for contributors
[19:42] <flocculant> and my head was just in getting *something* down for today
[19:42] <knome> aha
[19:42] <knome> so append it somehow?
[19:43] <flocculant> maybe a paragraph after the gtk3 bit ?
[19:43] <flocculant> before the get the release warble
[19:44] <knome> dunno
[19:44] <knome> :)
[19:44] <knome> docs.x.o is updated
[19:44] <flocculant> :)
[19:45] <flocculant> should copyright include 2016?
[19:45] <knome> i guess so
[19:46] <knome> and the support page updated
[19:46]  * nairwolf thinks flocculant need rest !
[19:48] <knome> pleia2, press
[19:48] <knome> have we social mediaed either?
[20:06] <flocculant> knome: not sure how having the release thing would make updating something easier? surely however it's done someone has to actually build the 'new' stuff
[20:07] <pleia2> social medias are done
[20:08] <flocculant> ahah - now you've updated get page I see div class="hb white"/regular :p
[20:08] <knome> flocculant, well imagine this: every mirror is entered into a database, with variables in the urls, like "http://mirror.url/xubuntu/$codename/"
[20:08] <flocculant> hi pleia2 and thanks :)
[20:09] <knome> flocculant, now you simply tell the website to print all mirror URLs for the release, and for example in this case the link would be "http://mirror.url/xubuntu/yakkety/" without manually having to create the list
[20:09] <flocculant> oh right - that 'stuff'
[20:09] <knome> so linking a new release in the download page would be theoretically as simple as s/16.10/17.04/
[20:09] <flocculant> yea I can see that being a whole lot easier :p
[20:10] <knome> AND
[20:10] <knome> with all the release dates and EOL dates in the database *already*
[20:10] <flocculant> then we would lose eol links :)
[20:10] <knome> it wouldn't be hard to tell the website to show the latest LTS and the latest regular release if it's not EOL
[20:10] <flocculant> yep
[20:10] <knome> so - yeah - we could make this much easier indeed
[20:11] <knome> not sure we completely want to automate it all, since there's always wiggly stuff, but at least the download link listing...
[20:11] <flocculant> that said the eol date seems to be a moveable feast - nothing to stop us saying some date - as long as it's not after the date -release say
[20:12] <flocculant> yea - that is what stopped me doing more than I did :)
[20:12] <knome> sure, that's totally in our control in both the actual support and on the website
[20:12] <knome> it's just a field to enter into the DB
[20:12] <flocculant> (plus didn't want to screw the page up)
[20:12] <knome> that's ok
[20:12] <flocculant> yea - nothing wrong with us fixing 9 months as 9 months imo
[20:13] <flocculant> not 9 months and a week cos someone hasn't done something outside
[20:13] <knome> lol
[20:13] <flocculant> you know the discussions that happen in u-release :)
[20:13] <knome> yeah
[20:14] <flocculant> and they would NOT make it 8 months and 3 weeks I'm sure
[20:14] <knome> otoh, one thing why we might want to align is if there are any problems with upgrading before the EOL...
[20:14] <knome> but that's just completely unrelated to this all anyway, so... ;)
[20:14] <flocculant> yea :)
[20:15] <flocculant> knome: oh yea - a thing I discovered with the Releases side bit
[20:15] <knome> yep?
[20:15] <flocculant> it has Show EOL releases - which does - but you can't unshow them
[20:15] <knome> in admin?
[20:16] <flocculant> well - refreshing does
[20:16] <knome> yeah, it's designed to be like that
[20:16] <flocculant> no - I mean looking at the website
[20:16] <knome> i mean, who cares if they are open already...
[20:16] <knome> :)
[20:16] <flocculant> oh
[20:17] <knome> you usually don't want to see them anyway
[20:17] <knome> so they are hidden
[20:17] <flocculant> that didn't happen last time I'm sure - I was looking for old release note with <includes>
[20:17] <knome> but in case you do, we offer them to you
[20:17] <flocculant> seems that if you then go *there* list goes back to current
[20:17] <knome> any refresh resets
[20:18] <flocculant> yea I guess so - people like me would be odd cases :P
[20:18] <knome> yep
[20:18] <flocculant> wth you would want to look at 2012 stuff for ...
[20:18] <knome> ;))
[20:18] <knome> this could be a cookie option - but then we'd have to tell people we are using cookies
[20:18] <knome> so meh
[20:18] <flocculant> yea meh
[20:18] <knome> or sth
[20:19] <knome> and as we both said, people don't usually want to even look at those
[20:19] <flocculant> yup
[20:20] <flocculant> mostly mentioned it just in case :)
[20:20] <knome> yup
[20:30]  * flocculant is looking forward to 'is it out yet' in October - I can join in with them :D
[20:31] <flocculant> thanks for everything over the last few cycles people - time for me to rest now :)
[20:31] <knome> o/
[20:31] <knome> you've deserved it
[20:33] <flocculant> :)
[22:20] <bluesabre> evening all
[22:21] <Unit193> Howdy.
[22:21] <knome> dy.
[22:22] <nairwolf> hi
[22:23] <bluesabre> hey Unit193, knome, nairwolf
[22:23] <bluesabre> knome, feel better
[22:24] <knome> feel, yes, look, no
[22:24] <bluesabre> good enough :)
[22:25] <knome> yeah, fortunately the awful throat sores are off
[23:05] <nairwolf> gnome-software doesn't have 'GIMP' inside, did you know that ?
[23:05] <nairwolf> Apparently, the problem is since 16.04
[23:06] <Unit193> Synaptic does. :>
[23:06] <nairwolf> as I never use gnome-software, I hadn't noticed that
[23:06] <nairwolf> Yes synaptic does
[23:06] <nairwolf> I don't see this bug at launchpad.
[23:06] <knome> well neither of them has GIMP "inside", they are not *that* bloated software... yet
[23:06] <nairwolf> gnome-software is a shame...
[23:06] <Unit193> I'm not sure who in the Xubu team actually uses it either, if anyone.
[23:07] <knome> <- apt(-get)
[23:07] <nairwolf> knome, sorry for my english. How should I say that ?
[23:07] <Unit193> nairwolf: s/ame/am/ ;P
[23:07] <knome> i'm just kidding.
[23:08] <nairwolf> :p
[23:08] <nairwolf> I can't imagine gimp dev be satisfied with this situation...
[23:11] <nairwolf> I can't imagine this bug not reported yet...
[23:12] <nairwolf> I only see this bug from pleia2 : https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1553629
[23:12] <nairwolf> Tomorrow, I'll try to find someone for this bug.
[23:13] <knome> bug 1567883
[23:15] <nairwolf> thank you knome
[23:16] <knome> btw, google "gimp gnome-software", this is the fifth result for me
[23:18] <nairwolf> That's because I used the search bar of Launchpad
[23:18] <nairwolf> if you search 'Gimp' at this page, you only find pleia2's bug
[23:18] <nairwolf> thank you btw
[23:19] <knome> yes, because this bug is marked "fix released", and those bugs are hidden by default
[23:22] <nairwolf> that's right !
[23:23] <nairwolf> Do you think it's better to open a new bug, in order to make the new bug visible by default ?
[23:23] <nairwolf> oh, I can change status by myself apparently
[23:23] <nairwolf> oh, non...
[23:25] <knome> i'd confirm the bug with somebody first in any case
[23:27] <nairwolf> I'm not the one to have seen this bug
[23:27] <nairwolf> I've seen that from a french reviewer of 16.10
[23:27] <knome> and you can't confirm it?
[23:27] <nairwolf> I can confirm
[23:28] <nairwolf> I woudn't have talked about this bug if I couldn't confirm.
[23:28] <nairwolf> I verified obviously


[02:02] <basketball> i install xscreensaver and now ctrl alt l or clicking the lock button doesnt work
[04:47] <sdale999185> Is Lubuntu or Xubuntu faster on older hardware?
[04:53] <genii> Ah, no patience.
[15:13] <wxl> is there something funky in 13.10 or is it the machine i'm on? .local addressing doesn't seem to work even though avahi is installed
[15:15] <holstein> wxl: i havent experienced anything odd. how can i test?
[15:15] <holstein> well.. NM.. i dont have 13.10 in front of me ATM
[15:15] <wxl> holstein: yeah that would help. i swear i have it on another machine that i have no trouble with
[15:16] <wxl> i do
[15:16] <wxl> hm.
[15:18] <wxl> weird, it seems to be in the discovery not the broadcast
[19:21] <xsaidx> phillw: heyy
[19:21] <xsaidx> how's you , hop everythin is good
[22:31] <wxl> anyone here have any somehwat greater than newbie experience with avahi?
[22:39] <basketball> how do i set my pc up where when i press alt then a letter it types the spanish version of the letter
[23:05] <phillw> basketball: not too sure of how to achieve that (you could make a whole new key map) but http://askubuntu.com/questions/102344/switching-keyboard-layouts-in-lubuntu-11-10 has a decent discussion on the subject
[23:56] <vinnie_> im trying to install Lubuntu on an old PC and keep getting out of range error on monitor after selecting try lubuntu or install lubuntu. Any suggestions?
[23:59] <wxl> !nomodeset | vinnie_