[11:44] <D4RKS1D3> Hi, I want to know why when I put the command "juju add-machine <machinenameinmaas>" is too slow
[11:45] <D4RKS1D3> when I had the old version of juju works quickest!!
[11:45] <D4RKS1D3> Any suggestion?
[19:31] <kwmonroe> cory_fu: i seem to recall you having an issue with travis.. was it by chance calling proof?  i'm not sure what i'm missing here:  https://travis-ci.org/juju-solutions/layer-apache-bigtop-base/builds/262305210?utm_source=github_status&utm_medium=notification
[19:33] <kwmonroe> in that scenario, my travis.yml is calling make sysdeps lint, which works fine until it gets to proof on line 24: https://github.com/juju-solutions/layer-apache-bigtop-base/blob/9fca22db0e3f77921dcfa5058c3402d32e5ea1cb/Makefile#L19
[19:34] <cory_fu> kwmonroe: I saw that error with the charm-tools snap when it was unconfined because there was a version conflict between the library provided by the system and one of the CT deps
[19:34] <cory_fu> kwmonroe: It looks like sysdeps isn't using the snapped version of charm-tools
[19:34] <kwmonroe> cory_fu: how'd you fix it?
[19:35] <cory_fu> The charm-tools snap is now confined, so it doesn't care what libs are installed at the system level
[19:35] <kwmonroe> cory_fu: "now confined" as in the edge version?
[19:35] <cory_fu> I'd recommend switching to the charm-tools snap
[19:35] <cory_fu> Pretty sure it's released to stable
[19:35] <cory_fu> Let me check
[19:35] <kwmonroe> hm, i got this when i tried to snap install the snap without --classic:  https://travis-ci.org/juju-solutions/layer-apache-bigtop-base/builds/262285702?utm_source=github_status&utm_medium=notification
[19:36] <cory_fu> Hrm.  Yeah, apparently it wasn't released to stable
[19:36] <kwmonroe> oooooh.. charm-tools vs charm?  i didn't know there were 2 things
[19:36] <cory_fu> No, it should just be charm, it seems
[19:36] <kwmonroe> ack, charm edge ftw.
[19:36] <cory_fu> marcoceppi: What's the process for moving that up to stable?
[19:36] <kwmonroe> marcoceppi: you in charge of charm snaps moving....
[19:36] <kwmonroe> :)
[19:36] <cory_fu> heh
[20:03] <marcoceppi> cory_fu: which revision?
[20:04] <cory_fu> marcoceppi: 17 is currently in edge, and that's the fully confined one we came up with in Warsaw
[20:05] <cory_fu> stable is currently on 15
[20:05] <marcoceppi> cory_fu: does it currently corrospond to a release in charm-tools repo? or is it all snap fixes?
[20:05] <cory_fu> Just snap changes, as far as I can recall
[20:06] <cory_fu> It does double the size of the snap, though, unfortunately
[20:06] <cory_fu> We could investigate paring it back down
[20:07] <marcoceppi> cory_fu: I just moved it to candidate to bake for a day or two
[20:08] <cory_fu> k
[23:11] <hloeung> marcoceppi, cory_fu: so is the charm snap the recommended path forward now, with the deb package no longer supported?
[23:11] <hloeung> marcoceppi, cory_fu: I'm using the snap (currently 15) but just thought I'd ask
[23:11] <marcoceppi> hloeung: yes, the deb is being deprecated
[23:11] <hloeung> marcoceppi, cory_fu: also, any ideas if there will be a bundletester snap?
[23:11] <marcoceppi> hloeung: good question, cory_fu would be best to field that question
[23:12] <marcoceppi> well, cory_fu and tvansteenburgh
[23:12] <hloeung> ah thanks. It's just a bit of work to get an environment set up for charming. "Install some of these packages", "install some snaps", "pip install bundletester"


[00:15] <JordyNew> i'm here superm1.  you still need a tester?
[00:15] <superm1> yes JordyNew
[00:15] <superm1> if you can activate gutsy-proposed and update to the new mythtv on there
[00:15] <superm1> and make sure it still works with your hardware
[00:15] <JordyNew> i can test as my mythtv setup is still in early stages.
[00:15] <superm1> recordings and such
[00:15] <superm1> that'd be spectacular
[00:16] <superm1> i need a few people to comment on this bug: https://bugs.edge.launchpad.net/ubuntu/gutsy/+source/mythtv/+bug/158562
[00:16] <superm1> so that it can be released from proposed
[00:16] <JordyNew> um, you may have to walk me though it superm1
[00:16] <superm1> JordyNew, if you click on system
[00:16] <superm1> or applications in mythbuntu
[00:16] <JordyNew> i do have a putty session into my myth box.
[00:16] <superm1> ah
[00:17] <superm1> well if you can VNC in, i'll walk you through gui, otherwise you comfy on terminal?
[00:17] <JordyNew> yes
[00:17] <superm1> okay edit your /etc/apt/sources.list
[00:17] <superm1> and copy and paste the line that says gutsy-updates
[00:17] <superm1> you want to change the pasted line to gutsy-proposed
[00:18] <JordyNew> got it.
[00:19] <superm1> okay once you do that
[00:19] <superm1> apt-get update
[00:19] <superm1> and apt-get upgrade
[00:19] <superm1> you should be offered a variety of updates
[00:19] <superm1> notate the ones that are myth related
[00:19] <superm1> and then hit ctrl c
[00:19] <superm1> and then run apt-get install BLAH
[00:20] <superm1> where BLAH is the myth related ones
[00:21] <JordyNew> its downloading the updates
[00:21] <JordyNew> didn't give me an option to select certain ones.
[00:22] <superm1> okay well you're updating more than you need to then :)
[00:23] <JordyNew> it's ok i can always reinstall, i hadn't gotten too far, was having remote control problems.
[00:24] <JordyNew> 80 percent done right now.
[00:25] <superm1> i see
[00:25] <JordyNew> now it put me into the setup.
[00:26] <superm1> it might ask a few debconf related questions
[00:26] <superm1> the important part is whether or not you can still record with your tuners
[00:26] <superm1> and watch your recordings
[00:27] <JordyNew> ok
[00:28] <JordyNew> looks like it's done.
[00:28] <JordyNew> do i need to reboot?
[00:29] <superm1> nope
[00:29] <superm1> just restart mythbackend
[00:33] <JordyNew> ok
[00:34] <JordyNew> it looks like it's still working.
[00:34] <JordyNew> can't do more testing now, need to go for a while.
[00:36] <Iolaus> Hey all, can anyone help me out with moving to the Trunk builds as explained here: http://www.mythbuntu.org/auto-builds
[00:36] <Iolaus> When I go to do the apt-get upgrade it lists a bunch of packages as kept back
[00:38] <superm1> JordyNew, okay when you get a few moments, please notate on the bug
[00:38] <superm1> that it still works for you
[00:38] <superm1> Iolaus, do an apt-get dist-upgrade
[00:38] <superm1> instead
[00:42] <Iolaus> thanks superm1
[00:42] <Iolaus> I'll give it a shot
[00:49] <Iolaus> superm1: The apt-get dist-upgrade bailed out with:
[00:49] <Iolaus> Errors were encountered while processing:
[00:49] <Iolaus>  /var/cache/apt/archives/libmyth-perl_0.20.99+trunk15096-0ubuntu0~mythbuntu1_i386.deb
[00:49] <Iolaus> E: Sub-process /usr/bin/dpkg returned an error code (1)
[00:49] <Iolaus> any idea what the deal is?
[01:01] <superm1> Iolaus, bad download?
[01:01] <superm1> Iolaus,
[01:07] <Iolaus> hmm
[01:08] <Iolaus> can I just run the command again or are things going to be boinked now?
[01:08] <Iolaus> I wonder if I should change to the UK repository as this same thing has happened twice
[01:15] <Iolaus> Is anyone here running from the mythbuntu trunk repository?
[01:15] <Daviey> yes
[01:16]  * Daviey runs the UK repo
[01:16] <Iolaus> hmm.. is it easy for me to switch that?
[01:16] <superm1> they are just mirrors of one another
[01:16] <Daviey> yeah, just add a uk. in your /etc/apt/sources.list
[01:17] <Iolaus> I'll give that a try.
[01:17] <Iolaus> should I be able to run the apt-get dist-upgrade again without trouble even though it crapped out once?
[01:17] <Daviey> superm1: When does the normal one resync?
[01:17] <superm1> the night after a build on the ppa
[01:17] <superm1> when i press the sync button
[01:17] <Daviey> ah
[01:18] <Daviey> uk. happens every sunday morning
[01:19] <Iolaus> guys, can I simply re-run the apt-get dist-upgrade?
[01:19] <Iolaus> or would there be some problem from the last upgrade not finishing?
[01:22] <superm1> no reason that would be trouble
[01:22] <Daviey> Iolaus: apt-get update first
[01:24] <Iolaus> Daviey: thanks :)
[01:29] <JordyNew> ok superm1 if you're still around, everything seems to still be working
[01:30] <superm1> JordyNew, great
[01:30] <superm1> can you please comment on the bug?
[01:30] <superm1> just mention that you dont have the hardware, but were testing to make sure it didn't break anything on your hardware
[01:31] <JordyNew> ok, and will you have a chance to help me with compiling lirc for my remote?  I know what I need to edit in the lirc_mceusb2.c file but every time i follow the guides that file gets rebuilt without my changes.
[01:33] <JordyNew> i do have m-a installed
[01:36] <JordyNew> i'm not a member, waiting on the email to be able to comment on the bug that you wanted me to do superm1
[01:38] <superm1> JordyNew, okay so as for compiling lirc
[01:38] <superm1> did you install lirc-modules-source?
[01:40] <JordyNew> don't know how to do that.
[01:40] <JordyNew> i do have my putty session open though
[01:40] <JordyNew> i can check if you tell me how to.
[01:40] <superm1> apt-get install lirc-modules-source
[01:41] <JordyNew> already newest version.
[01:42] <superm1> okay then you need to extract that archive in /usr/src
[01:42] <JordyNew> ok.
[01:42] <superm1> and modify the file inside it
[01:42] <superm1> once you do, it needs to be repackaged
[01:42] <JordyNew> i'm sorry for being such a newbie at this.
[01:42] <superm1> if you can do this with a gui, it really is a ton easier
[01:42] <JordyNew> ok what do i do at the gui?
[01:44] <superm1> copy the archive from /usr/src
[01:44] <superm1> to somewhere else
[01:44] <superm1> and double click it
[01:44] <superm1> extract it
[01:44] <superm1> and then modify the file and you can drag it back in
[01:44] <JordyNew> the lirc-modules-source?
[01:45] <superm1> the file in /usr/src/ related to lirc modules source
[01:45] <superm1> i dont recall the filename for it
[01:45] <superm1> but it should be recognizable
[01:48] <JordyNew> i've copied it but when i double click on the tgz file it asks me what i want to use to open it?
[01:49] <superm1> oh file-roller might not be installed
[01:49] <superm1> install that quickly
[01:49] <superm1> and you should be able to double click it
[01:50] <JordyNew> apt-get install fileroller   ?
[01:51] <JordyNew> file-roller?
[01:51] <superm1> apt-get install file-roller
[01:51] <superm1> i think
[01:54] <JordyNew> ok, i have the file edited in the directory under /tmp/modules/ ...  but i don't know how to repackage it into a tgz with all the directory structure intact
[01:58] <superm1> well thats the thing
[01:58] <superm1> if you leave file-roller open
[01:58] <superm1> you can just drag it back to the right place
[01:58] <superm1> and not need to worry about repacking in the right place
[02:01] <JordyNew> ok, i think i'm getting it.
[02:01] <JordyNew> one sec while i try this.
[02:03] <JordyNew> ok, i have the file repackaged in a tar.gz in /usr/src/
[02:03] <JordyNew> what's my next step superm1?
[02:04] <superm1> JordyNew, okay now run this
[02:04] <superm1> sudo dpkg-reconfigure lirc-modules-source
[02:05] <superm1> and pick the mceusb2 driver
[02:05] <superm1> only
[02:05] <JordyNew> ok and tell it no on automatically building?
[02:07] <JordyNew> ok, i chose no, and then what?
[02:08] <superm1> choose no
[02:08] <superm1> and let it replace the file
[02:08] <JordyNew> ok
[02:08] <superm1> check /etc/lirc/lirc-modules-source.conf
[02:08] <superm1> and make sure it is listed in there
[02:08] <superm1> in case you accidently mischose (its a common mistake)
[02:09] <JordyNew> yep, it's mceusb2
[02:11] <JordyNew> i'm guessing the next step is actually getting it to compile?
[02:11] <superm1> yup
[02:11] <JordyNew> ok
[02:11] <superm1> sudo m-a update,prepare
[02:11] <superm1> will prepare it to build
[02:11] <superm1> and then
[02:11] <superm1> sudo m-a a-i lirc
[02:11] <superm1> will build it
[02:11] <superm1> and install it
[02:13] <JordyNew> ok and then i can try irw?
[02:15] <superm1> not yet
[02:15] <superm1> once its installed, you need to go and remove the old one
[02:15] <superm1> its in /lib/modules/`uname -a` somewhere
[02:15] <superm1> so issue a find /lib/modules/`uname -a` -name lirc_mceusb2.ko
[02:15] <superm1> and once you find it, you need to rename that file
[02:16] <superm1> make sure you rename the right one (its in a ubuntu/media/lirc/lirc_mceusb2 subdirectory)
[02:21] <JordyNew> ok, i've found the lirc_mceusb2.ko file
[02:21] <JordyNew> what do i rename it to?
[02:22] <superm1> sudo mv lirc_mceusb2.ko lirc_mceusb2.ko.old
[02:23] <superm1> that will handle it
[02:23] <superm1> once you've done that, you should still have another file sitting in the misc directory
[02:23] <JordyNew> ok, then i copy my lirc_mceusb2.ko from the /usr/src dir?
[02:23] <superm1> it should already be copied over
[02:23] <superm1> after running m-a a-i lirc
[02:23] <superm1> you should have found two in /lib/modules
[02:24] <JordyNew> there was only one
[02:24] <superm1> check in /usr/src for a deb then
[02:24] <superm1> like lirc-modules-0.8.2-blah-blah-i386.deb
[02:25] <JordyNew> there's a lirc_mceusb2.ko in /usr/src/modules/lirc/drivers/lirc_mceusb2
[02:25] <superm1> there should be a .deb in there too though
[02:25] <superm1> in /usr/src
[02:25] <JordyNew> there are a couple of deb files there
[02:25] <superm1> any related to lirc though?
[02:26] <JordyNew> both are
[02:26] <superm1> what are they called?
[02:27] <JordyNew> lirc-modules-2.6.22-14-generic_0.8.2-0ubuntu8+2.6.22-14.46_amd64.deb
[02:27] <JordyNew> and all that.47_amd64.deb
[02:27] <superm1> ah
[02:27] <superm1> which kernel are you booted to?
[02:28] <JordyNew> sorry, how do i tell?
[02:28] <superm1> uname -a
[02:28] <superm1> and have you rebooted since you updated it?
[02:28] <JordyNew> i rebooted after the update that you had me do regarding the bug.
[02:28] <superm1> okay so you should be in the new one then
[02:28] <superm1> okay then install the newer .deb
[02:29] <superm1> and it should copy the .ko for you
[02:29] <JordyNew> i'm running 6.22-14
[02:29] <JordyNew> ok, how do i install it, sorry
[02:34] <JordyNew> i think i just double click on it in the gui, right?
[02:36] <JordyNew> it said it was rebuilding the lirc module but it didn't copy another .ko file into that ubuntu/media directory, still just the .ko.old file there.
[02:39] <JordyNew> looks like it's putting the new .ko file into generic instead of lirc_mceusb2
[02:40] <JordyNew> i mean misc
[02:42] <superm1> whoops sorry
[02:42] <superm1> stepped otu
[02:42] <superm1> it copies it to the misc directory
[02:42] <JordyNew> yes
[02:42] <superm1> in /lib/modules/`uname -a`
[02:42] <JordyNew> yes
[02:42] <superm1> that's fine
[02:42] <JordyNew> and also a lirc_dev.ko file there too
[02:42] <superm1> so what you do is run
[02:42] <superm1> sudo depmod -a
[02:42] <superm1> and then it will update the module list
[02:42] <superm1> you can then run
[02:42] <superm1> sudo rmmod lirc_dev
[02:43] <superm1> sudo rmmod lirc_mceusb2
[02:43] <superm1> to unload the old ones
[02:43] <superm1> and then sudo modprobe lirc_mceusb2
[02:43] <superm1> and then
[02:43] <superm1> sudo /etc/init.d/lirc restart
[02:43] <superm1> to restart lirc
[02:43] <Iolaus> Hey guys, I just started from scratch installing Mythbuntu 7.10 from the LiveCD and then changing to trunk.
[02:43] <Iolaus> I got the same error this time around.
[02:43] <superm1> Iolaus, something might be wrong with the trunk packages
[02:43] <superm1> i'll poke our guy who normally does the trunk stuff
[02:44] <superm1> any more information about it?
[02:44] <superm1> about the error?
[02:44] <Iolaus> I'm getting this error from the apt-get
[02:44] <Iolaus> Errors were encountered while processing:
[02:44] <Iolaus>  /var/cache/apt/archives/libmyth-perl_0.20.99+trunk15096-0ubuntu0~mythbuntu1_i386.deb
[02:44] <Iolaus> E: Sub-process /usr/bin/dpkg returned an error code (1)
[02:44] <Iolaus> Is there any other place I can dig deeper?
[02:44] <superm1> well you can try not installing that perl package
[02:44] <superm1> just install the others
[02:44] <superm1> and see if it lets you
[02:45] <superm1> i'm not sure how to (easily) look closer at the log though
[02:45] <superm1> /var/lib/dpkg.log
[02:45] <superm1> might tell you more
[02:45] <superm1> i'm not sure
[02:45] <Iolaus> how do I do that?  The perl package installs as part of the apt-get dist-upgrade
[02:46] <Iolaus> doesn't look like dpkg.log has anything relavent
[02:46] <JordyNew> i get an error when i try to run rmmod lirc_dev
[02:46] <JordyNew> ERROR: Module lirc_dev is in use by lirc_mceusb2
[02:48] <superm1> JordyNew, rmmod the lirc_mceusb2 first
[02:48] <superm1> then the lirc_dev then
[02:50] <JordyNew> ok superm1, it let me restart lircd
[02:51] <superm1> okay so with any luck $things should work now
[02:51] <JordyNew> do i start irw now?
[02:51] <superm1> you can
[02:51] <JordyNew> gets right back to a prompt.
[02:51] <JordyNew> guess it doesn't work
[02:51] <superm1> well check dmesg
[02:51] <superm1> and see if it loaded okay
[02:52] <superm1> and then check that lircd is still running
[02:54] <JordyNew> don't see anything in dmesg, and lircd is still running.
[02:55] <JordyNew> do i need to reboot?
[02:56] <JordyNew> going to try reboot now
[02:59] <superm1> okay
[03:01] <JordyNew> ok, rebooted, remote is not working.
[03:01] <JordyNew> how do i tell if it has the lirc_mceusb2.c changes that i made?
[03:08] <JordyNew> should i see lirc messages in my dmesg?
[03:13] <JordyNew> there is no /dev/lirc0 created.  could this be part of the problem?
[03:15] <JordyNew> i do have a /dev/lircd however
[03:18] <superm1> JordyNew, you sure you modified the lirc_mceusb2 properly
[03:18] <superm1> ?
[03:19] <JordyNew> i can send it to you but i'm pretty sure i did
[03:19] <superm1> well the only possible issues here can be mismodified
[03:19] <superm1> or modified for the wrong kernel
[03:20] <superm1> so you can double check to make sure you put it in /lib/modules/`uname -a` once more
[03:20] <superm1> otherwise your modifications appear to have not worked
[03:20] <JordyNew> in the misc directory?
[03:21] <superm1> yeah
[03:21] <superm1> that's the right place
[03:21] <JordyNew> i have 2 .ko files in the misc directory
[03:21] <superm1> yeah that's it
[03:21] <JordyNew> from about 30 minutes ago.
[03:21] <superm1> yeah
[03:22] <superm1> so double check your modifications then
[03:22] <superm1> was it just adding a vendor/product id?
[03:22] <superm1> i suspect?
[03:22] <JordyNew> yes, added a vendor line and another case
[03:22] <superm1> sure the vendor was right?
[03:22] <superm1> double checked it?
[03:22] <superm1> checked commas, spacing etc
[03:22] <JordyNew> i'll check it again.
[03:29] <JordyNew> looks fine
[03:31] <superm1> JordyNew, well not sure what to tell you then :(
[03:32] <JordyNew> i see there is a mceusb2.c file i can download from the forum that is supposed to make this remote work.
[03:32] <JordyNew> it's the pinnacle mce usb remote
[03:33] <JordyNew> that's the thread i'm reading all this stuff in.
[03:33] <JordyNew> i'm trying to get my password as i forgot it so I can download the file.
[03:38] <JordyNew> if this doesn't work, it might be easier to just get one of the remotes supported natively in ubuntu
[03:41] <superm1> well if someone files a bug on this, i can add it for hardy (using the diff in that post), but if it doesnt work for you then its a moot point
[04:00] <tazgodx> i sure hope this work.....
[04:24] <tazgodx> kind of dead in here
[04:33] <nettow0822_> hey guys
[04:34] <nettow0822_> anyone use netflix plugin?
[04:36] <tazgodx> is there a graphical text editor in mythbuntu?
[04:44] <superm1> install one
[04:44] <superm1> gedit
[04:44] <superm1> geany
[04:44] <superm1> mousepad
[04:44] <superm1> leafpad
[04:46] <Dr_willis> nano, pico, fte (my fave)
[04:47]  * Dr_willis missed the question. :)
[04:48] <tazgodx> im just useing nano for now
[04:48] <tazgodx> trying to set up my STB
[04:48] <tazgodx> firewire
[04:49] <tazgodx> so superm1 i got this new STB from my cable company, there are 2 firewire ports on the back, and they both seem to work. does that mean i can connect 2 different cables and watch 2 different channels when its all done?
[04:52] <superm1> not usually
[04:52] <superm1> but you can try
[04:56] <tazgodx> its a new box, i thought i was gonna get the 6200 but i didn't
[04:56] <tazgodx> it has HDMI on it, its weird
[04:57] <tazgodx> shit im late, ill be back to finish testing this :)
[07:45] <warriorforgod> If I have a wintv pvr-150 can I record one channel and watch another at the same time?
[07:56] <toorima> warriorforgod: no
[07:56] <warriorforgod> toorima: Ok. Next question.  What would you recommend for a digital/analog tuner card?
[07:56] <toorima> pvr-500 can do that
[07:57] <toorima> for hdtv i have the pchdtv5000
[07:57] <toorima> hdhomerun is good if u want 2 hd channels
[07:57] <warriorforgod> toorima: where did you get it?
[07:57] <warriorforgod> I can't find those on newegg.
[07:57] <toorima> from there website
[07:58] <toorima> dont think hdhomerun will do sd tho but not sure
[08:14]  * laga waves
[08:15] <laga> Iolaus: i've heard you're having issue with the trunk packages. it'd be very helpful if you can give me the _full_ error message, preferably in a pastebin. if you can't do that i'll have to try and reproduce it myself
[08:49] <superm1> laga, i'm pretty sure what i brought to you was a full error
[08:49] <superm1> as in all he was seeing
[08:54] <laga> superm1: i kinda doubt that because it's totally useless. but maybe there was an error for which dpkg didn't know what to say.
[08:54] <laga> like "oh my god that's f'ed up"
[08:54] <laga> ;)
[08:57] <tazgodx> damnit, my firewire isn't working! i hate life
[08:59] <tazgodx> nice tutorial tho, hands down one of the best ive read :)
[09:00] <tazgodx> i have one more trick up my sleeves for tomorrow, and then i give up for a day
[09:00] <tazgodx> g'night
[13:23] <Rhiadon> hello everyone
[13:39] <nettow0822> hey all
[13:39] <nettow0822> would it be better to use the opengl option over qt for the paint engine?
[13:45] <nettow0822> anyone used the netflix addon
[13:45] <nettow0822> ?
[13:45] <Dr_willis> i always remove that entry from my menus, :)
[13:48] <nettow0822> i was having trouble setting up
[16:11] <nettow0822> anyone awake?
[16:15] <nettow0822> I'm trying to setup mythflix....do I need to do this on the master backend?
[16:15] <pdragon> might try the forums if no one is answering here
[16:16] <MRH_1____> Hi,  Just installed mythbunu, but on reboot it freezes at "LIRC is not configured"   "Running local boot scripts!
[16:16] <MRH_1____> Any suggestions how to get past this point?  Thanks
[16:40] <nettow0822> how can I find out what is my root password for mysql?
[16:54] <MRH_1____> have you tried   http://keystoneit.wordpress.com/2006/10/28/resetting-mysql-root-password-in-ubuntu-dapper/
[16:58] <tgm4883> theres either no root password
[16:59] <tgm4883> or it's stored in /etc/mythtv/mysql.txt
[16:59] <tgm4883> probably the latter
[17:07] <nettow0822> i get this message after entering password...
[17:07] <nettow0822>  Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock'
[17:07] <nettow0822> i'm trying to do this on a slave backend / frontend
[17:16] <alexvd_> Hi I have a directv external tuner box connected via cable and using the channel change script. I have enabled the script and permissions.  It worked at first however now it doesnt seem to be working.  I can still run the script at command prompt with no issues and I get no errors in the logs.  How do I troubleshoot this?
[17:17] <alexvd_> The issue is when i try to change channels from another frontend with capture cards on the masterbackend
[17:17] <alexvd_> avan3944
[17:17] <alexvd_> oops
[17:17] <alexvd_> disregard that
[17:23] <arnath01> hi, we currently have digital tv here instead of good ol' analog, can mythbuntu handle that in some way?
[17:24] <tgm4883> arnath01, with a tuner, yes
[17:24] <tgm4883> where do you live
[17:24] <arnath01> belgium
[17:24] <tgm4883> hmm, not sure i know anyone from belgium
[17:24] <arnath01> tgm4883: what do you mean "with a tuner"? (i'm a bit of a noob when it comes to this particular subject :P)
[17:25] <tgm4883> well, you have to get the signal into your pc somehow
[17:25] <arnath01> yes that was my problem :)
[17:25] <tgm4883> how do you receive the signal?
[17:25] <tgm4883> ie, satellite, cable, OTA, etc
[17:25] <arnath01> i'm not entirely sure, but most of it is through coax i believe
[17:25] <arnath01> although there is an ethernet component as well
[17:26] <laga> you probably want a dvb-c card, but i'm not sure what you guys use in belgium
[17:26] <tgm4883> interesting
[17:26] <tgm4883> ah its laga
[17:26] <laga> hm, mkight be IPTv then o_O
[17:26] <tgm4883> the exact guy i was going to ping
[17:26] <laga> s/mkight/might/
[17:26] <laga> tgm4883: heh :)
[17:26] <laga> well, arnath01: you should find out how you're getting the signal :)
[17:26] <tgm4883> laga, you're my official contact for europe
[17:27] <arnath01> laga: heh, that nasty little task will have to wait i'm afraid, damned exams coming up :P
[17:27] <laga> i'd love to talk to chat more with you guys, but i need have this midterm tomorrow :)
[17:27] <arnath01> but thanks for the feedback, now at least i know where to start hehe
[17:27] <laga> arnath01: hehe :)
[17:27] <laga> s/need have/have/
[17:28] <arnath01> tgm4883: on another note -> i have most of my media (i tend to rip dvds/cds i have, because i dislike inserting dvds/cds all the time) on an external usb drive, what's the easiest way to share those files over my network to view on my tv?
[17:29] <arnath01> (i am currently running mythbuntu virtualized)
[17:31] <tgm4883> arnath01, probably NFS.  Just setup an NFS share, mount in on the mythbuntu machine, and use mythvideo to watch the videos
[17:31] <tgm4883> do you know how to setup NFS?
[17:31] <arnath01> tgm4883: ye :)
[17:31] <tgm4883> k
[17:31] <tgm4883> i'll have to go for awhile, but will be back later.  People will also check in so if you have a question, post it.
[17:31] <arnath01> though i'm having problems with my usb on NFS, as ubuntu only has a 50% chance of automatically mounting the usb when i start it up :s
[17:32] <tgm4883> hmm
[17:32] <arnath01> i haven't found a pattern in it yet, it just seems to be random luck
[17:32] <tgm4883> strange
[17:32] <arnath01> but it's massively annoying as nfs (afaik) depends on static environments
[17:33] <tgm4883> well, just NFS a directory, and force the usb drive to always mount in a subdir of that directory
[17:33] <laga> does it? so let's say you share a directory..
[17:33] <laga> yeah, what he said.
[17:33] <tgm4883> :)\
[17:33] <tgm4883> to the share, it will just look like you are adding something to the dir
[17:33] <arnath01> hmm, i tried automounting it, but this had some other problems, but it's been a while, i forgot what they were
[17:33] <tgm4883> and should work fine
[17:34] <arnath01> i shall have to delve into my nfs structure again i guess :D
[17:38] <tgm4883> can anyone recommend a USB HD tuner?
[17:47] <nettow0822> ok got mythflix working.....i had to be on the masterbackend
[18:53] <MilhousePunkRock> Hello everyone!
[18:53] <MilhousePunkRock> What's wrong when scanning for channels tells me "could not address card" and on the next page I get "Programmer error, see console"?
[19:07] <laga> you need to look at the console
[19:07] <laga> and stop cross-posting ;)
[21:36] <nettow0822> need help....
[21:36] <laga> ask a question?
[21:37] <nettow0822> I have two HD cards....pcHDTV 5500 pci and Dvico fusion rt pcie....
[21:38] <nettow0822> I just updated the drivers from the linuxtv.org site for the  Dvico fusion rt pcie
[21:38] <nettow0822> I see both cards using lspci
[21:40] <laga> and what's your question?
[21:40] <nettow0822> when trying to setup the  Dvico fusion rt pcie in mythbackend....
[21:40] <nettow0822> all I see is the pcHDTV 5500 card
[21:41] <nettow0822> is there something I am missing during the backend setup?
[21:41] <laga> does the driver load for the dvico? does it show up in dmesg?
[21:46] <nettow0822> well maybe it isn't showing in lspci....got some work to do
[21:46] <laga> k
[21:50] <directhex> is there a way to make a fully automated ubiquity-based install cd, or is that restricted only to d-i?
[21:50]  * directhex reckons you guys have experience with ubiquity fiddling
[23:42] <tazgodx> anyone have any expertise with firewire setup?


[00:41] <ubotu> New bug: #196318 in xorg (main) "small screens end up only allowing small external display resolutions" [Undecided,New] https://launchpad.net/bugs/196318
[00:44] <ubotu> New bug: #194929 in xserver-xorg-video-intel (main) "hardy alpha5, i810 fuzzy/choppy problems" [Undecided,New] https://launchpad.net/bugs/194929
[03:20] <ubotu> New bug: #196349 in xserver-xorg-video-unichrome (universe) "xserver-xorg-video-unichrome broken in hardy." [Undecided,New] https://launchpad.net/bugs/196349
[09:39] <tjaalton> hmm, i965 doesn't start a session with vesa.. x-window-manager/compiz gets stuck
[09:43] <tjaalton> bryce: what's your opinion about vmmouse? the current method of using vmmouse_detect doesn't work, and just defaulting to it instead would fall back to mouse when the (driver internal) check fails
[10:01] <tjaalton> mvo: what do you think of bug 67996, you said that /usr/X11R6/bin could be moved aside instead of failing the upgrade?
[10:01] <ubotu> Launchpad bug 67996 in xorg "x11-common preinst script fails (was: aborts /usr/X11R6/bin not empty)" [High,Confirmed] https://launchpad.net/bugs/67996
[10:07] <tjaalton> hm, my session doesn't work with intel either
[10:11] <Ng> erk
[10:12] <Ng> my laptop just suspended and on resume X was broken and green :(
[10:13] <jcristau> some suspend/resume problems on intel are fixed in .25-rc3
[10:16] <Ng> hmm
[10:20] <Ng> testing it again and I saw the same green screen flash right after it powered up, but then it was redrawn with the proper X stuff
[10:20] <tjaalton> the current kernel in hardy has the drm bits backported
[10:21] <tjaalton> but maybe rc3 has more
[10:23] <mvo> tjaalton: yes, I think it is wrong to fail here, I think what it should do is to warn the user via debconf about it but then move /usr/X11R6/bin to /usr/X11R6/bin.move_on_upgrade or something like this
[10:24] <tjaalton> mvo: ok, I'll change it and modify the message too
[10:25] <mvo> tjaalton: great, thanks
[10:26] <jcristau> are there that many problems left with that?  i don't remember many reports of broken upgrade after etch release
[10:26] <tjaalton> jcristau: shouldn't be, but..
[10:27] <tjaalton> there was at least a broken opera
[10:27] <tjaalton> this change can go right after hardy is released
[10:27] <jcristau> not from a deb then?
[10:27] <tjaalton> yes, official opera deb
[10:27] <tjaalton> upstream crap :)
[10:28] <jcristau> x11-common conflicts with opera
[10:28] <tjaalton> well, that was an example.. don't know if there are others
[10:28] <tjaalton> maybe I should just ask
[10:34] <Ng> mvo: http://bugzilla.gnome.org/show_bug.cgi?id=482354 was the firefox/wm thing I mentioned
[10:34] <ubotu> Gnome bug 482354 in general "gtk_window_present() causes full applications to move workspaces" [Normal,Unconfirmed]
[10:34] <Ng> and a simple testcase for the weird borderless bug doesn't expose it, so maybe I have a bug ;(
[10:39]  * mvo checks
[10:49] <jcristau> tjaalton: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/67996/comments/13 eg has nothing to do with that bug afaics
[10:49] <ubotu> Launchpad bug 67996 in xorg "x11-common preinst script fails (was: aborts /usr/X11R6/bin not empty)" [High,Incomplete]
[10:50] <jcristau> and the rest of the failure reports are old
[10:54] <tjaalton> yeah, era is complaining about xli
[10:55] <tjaalton> I'll hold off that change for now and upload what I have now
[10:55] <tjaalton> nownow
[13:40] <ubotu> New bug: #196560 in xorg (main) "[gutsy] X crash (low graphics mode) when logging out and in several times consecutively" [Undecided,New] https://launchpad.net/bugs/196560
[14:31] <tjaalton> jcristau: yep, you were right.. era didn't have the problem anymore, so I closed it. thanks for the push ;)
[17:04] <bdmurray> Wasn't nvidia-glx-config removed recently?
[17:19] <mario_limonciell> bryce, are you around momentarily?
[17:29] <bryce> hi mario_limonciell
[17:30] <mario_limonciell> hey bryce
[17:30] <mario_limonciell> had a few questions regarding how fn-f8 was "supposed" to be handled on intel cards
[17:31] <mario_limonciell> is acpid supposed to be catching the events for them, or all within the intel video driver?
[17:32] <jcristau> the driver doesn't deal with that afaik
[17:32] <jcristau> probably a bios thing
[17:35] <bryce> mario_limonciell: in theory acpi should be handling it all
[17:36] <mario_limonciell> bryce, so in the event that /var/log/acpid isn't showing any of these events being caught, who to start pointing fingers at likely?
[17:37] <bryce> well, I wouldn't point fingers, but mjg59 is the best guy to answer questions about it
[17:38] <bryce> sometimes the issue goes down as far as the kernel
[17:38] <mario_limonciell> okay, well on this morning's call, rtg had mentioned to poke you on it first
[17:39] <mario_limonciell> well let me put it this way though - it seems that something gets intercepted by the keypress. FN-F8 issues a whole bunch of events to xev, but nothing with the randr change on the displays
[17:40] <mario_limonciell> which was why I was thinking to point it at xserver-xorg-video-intel
[17:40] <bryce> hang on, I have a bug report about this...
[17:42] <jcristau> mario_limonciell: the driver shouldn't be involved in this at all. if you get a keypress event, then you can configure your desktop env to act on it
[17:42] <mario_limonciell> no keypress event is caught, let me get a pastebin showing you what events actually are caught by xev
[17:43] <jcristau> (seems to send XF86Display here)
[17:44] <mario_limonciell> http://paste.ubuntu.com/5106/
[17:45] <bryce> bug #144225, #133568
[17:45] <ubotu> Launchpad bug 144225 in xrandr "Fn + F8 doesn't work on Dell Inspiron 6400 to switch display to another monitor" [Low,Triaged] https://launchpad.net/bugs/144225
[17:45] <ubotu> Launchpad bug 133568 in xserver-xorg-video-intel "fn+f8 (crt/lcd switch) does nothing" [Medium,Confirmed] https://launchpad.net/bugs/133568
[17:45] <jcristau> hmm. maybe i'm wrong. the driver seems to listen to acpi stuff
[17:45] <bryce> both of those are misfiled; it's not xrandr and like jcristau it's not a video driver thing
[17:46] <mario_limonciell> they're also dated back some time - as i'd imagine behavior has changed on hardy
[17:47] <bryce> yeah could be
[17:48] <bryce> that latter one seems to not be about it not working, but not working they way they expect
[17:52] <bryce> hmm, it sounds like we need something better than just mapping to xrandr --auto
[17:52] <mario_limonciell> well but in this case, xrandr --auto isn't even being called
[17:52] <bryce> it needs to be a toggle type thing that switches between that and xrandr --output FOO --off
[17:52] <bryce> yeah, I'm just saying in general ;-)
[17:53] <mario_limonciell> yeah, i'll agree there, but that framework for querying the driver other than xrandr | grep BLAH would probably be nicer to have first before that
[17:55] <mario_limonciell> well for now i'll mark the bug with xserver-xorg-video-intel pending more information
[18:05] <ubotu> New bug: #196176 in dell "FN-F8 doesn't switch displays on M1330" [Medium,Confirmed] https://launchpad.net/bugs/196176
[18:07] <mario_limonciell> well it would appear that after a lot of presses an XF86Display key is caught by xev, but X doesn't react on that keyevent
[18:46] <jcristau> mario_limonciell: X *sends* the key event
[18:46] <jcristau> so that you can do whatever you want client-side with it
[18:47] <mario_limonciell> jcristau, well I think i've narrowed it down further.  gnome-settings-daemon is crashing
[18:47] <mario_limonciell> at when FN-F8 is pressed
[18:48] <jcristau> ah :)
[18:48] <mario_limonciell> so perhaps it wasn't ported to xrandr 1.2
[18:48] <mario_limonciell> off to CVS to look around :)
[18:49] <mario_limonciell> too bad apport doesn't catch it though
[20:04] <asac> tjaalton: hey. i have "enemy territory QW" and it plays fine with -generic fglrx, but i get rendering errors + worse: quick system crashes when using -rt. any idea?
[20:11] <tjaalton> asac: hmm, sorry no idea.. maybe abogani might know, he should be the -rt master
[20:16] <mario_limonciell> whew okay after tracking that all down, here's my update on it - g-s-d doesn't support switching displays (yet).  2.24 is the target
[20:16] <mario_limonciell> that crash that i was encountering is indeed a bug with g-s-d
[20:16] <bryce> ahh interesting
[20:16] <mario_limonciell> so perhaps we need a more local fix until 2.24
[20:17] <bryce> mario_limonciell: do we have those bugs in launchpad against gsd?
[20:17] <mario_limonciell> bryce, i just got them an unoptimized backtrace upstream
[20:17] <mario_limonciell> at bugs.gnome.org
[20:17] <mario_limonciell> i'll link a launchpad bug once i find the most appropriate one
[20:17] <bryce> great, thanks
[20:17] <mario_limonciell> so for a more local fix, i'd propose just binding fn-f8 to xrandr --auto
[20:18] <mario_limonciell> at least until it's properly implemented upstream
[20:20] <bryce> hmm, I thought we already had fn+f8 bound to xrandr --auto though?
[20:24] <bryce> hi seb128
[20:24] <mario_limonciell> maybe at one point
[20:24] <mario_limonciell> but i'm not sure where that would sit now
[20:24] <bryce> yeah me either
[20:24] <mario_limonciell> do you know when the last time that was present?
[20:24] <bryce> mario_limonciell: seb128 or mjg59 might know the details
[20:25] <mario_limonciell> seb128, well if you are aware, do you know if/when/how fn+f8 was bound to xrandr --auto?
[20:25] <bryce> mario_limonciell: I am fairly certain it was there in gutsy; I've seen bug reports referring to side effects when it's hit
[20:26] <seb128> mario_limonciell: it's a gnome-control-center shortcut, I think it was dropped in hardy on the way and I will add it back when I do the next gnome-control-center upload
[20:27] <seb128> hey bryce
[20:27] <mario_limonciell> seb128, ah that would make more sense then :)
[20:27] <bryce> mario_limonciell: btw I have another mythtv question
[20:27] <mario_limonciell> go ahead shoot
[20:28] <bryce> mario_limonciell: I installed mythfrontend on one of my laptops (which I use for a variety of things, and just sometimes mythtv), but now on each boot it's prompting me for mythtv settings, and then autologging me into mythtv
[20:28] <bryce> so I guess a two parter question
[20:28] <bryce> a) how do I get it to not prompt for the same info, and b) how do I turn off the auto-loging?
[20:29] <bryce> oh, if it matters, the front end is Hardy, the back end Gutsy
[20:30] <mario_limonciell> bryce, likely gnome is starting it up
[20:30] <mario_limonciell> er wait
[20:30] <mario_limonciell> its autologging from gdm?
[20:30] <bryce> right
[20:30] <mario_limonciell> remove the package ubuntu-mythtv-frontend
[20:31] <mario_limonciell> it creates that autologin session.  perhaps its worthwhile ditching that package to avoid confusion
[20:31] <bryce> hmm
[20:32] <bryce> maybe it's just a gdm setting?  *poking around*
[20:32] <mario_limonciell> well that package provides an override gdm config
[20:32] <mario_limonciell> so yes in a sense it is a gdm setting
[20:32] <bryce> aha, there's flags in /etc/gdm/gdm-cdd.conf for automatic and timed logins
[20:33] <bryce> awesome, thanks
[20:33] <mario_limonciell> if you aren't using the autlogin feature, just remove the package
[20:33] <mario_limonciell> that's the only useful thing it provides :)
[20:33] <bryce> oh interesting
[20:33] <bryce> it sounds so official ;-)
[20:34] <mario_limonciell> yeah hence why i think i should just nuke the package from debian/control
[20:34] <mario_limonciell> it causes confusion :)
[20:37] <bryce> btw, I checked through your mythbuntu.org site last night - great work on it, lots of really useful info :-)
[20:38] <bryce> finally I learned how to shut off the screensaver ;-)
[20:43] <mario_limonciell> thanks :)
[20:43] <mario_limonciell> ugh upstream nailed the bug -
[20:43] <mario_limonciell> its because of one of our gsd patches
[20:44] <mario_limonciell> seb128, 19_extra_keybindings.patch shouldn't be present
[20:44] <mario_limonciell> its not complete
[20:44] <mario_limonciell> or at least it should be modifying a little bit mroe
[20:46] <seb128> mario_limonciell: ?
[20:46] <mario_limonciell> seb128, gnome bug 518637
[20:47] <ubotu> Gnome bug 518637 in plugins "crash in media keys on resume?" [Critical,Resolved: notgnome] http://bugzilla.gnome.org/show_bug.cgi?id=518637
[20:47] <mario_limonciell> that was caused by 19_extra_keybindings
[20:47] <mario_limonciell> because of not having a callback to the XRANDR key
[20:48] <seb128> mario_limonciell: right, as said I'll fix the xrandr thing in the next upload
[20:49] <mario_limonciell> seb128, okay just wanted to point out its in gsd not gnome-control-center then
[20:49] <seb128> mario_limonciell: thanks
[20:49] <mario_limonciell> are you aware of where the changes need to be made?  I can summarize what i've discovered here in the last 2 hours in a bug to save you some trouble if you'd like
[20:50] <seb128> I think using what we had in gutsy should do the trick
[20:53] <seb128> mario_limonciell: no?
[20:54] <mario_limonciell> seb128,  i'm not aware of exactly what was in that patch.  the necessary change is pretty small to 19_extra_keybindings.  give me a few minutes and i'll test what i believe is necessary, and then pastebin it.  should hopefully solve things
[20:56] <seb128> mario_limonciell: http://paste.ubuntu.com/5119/
[20:57] <seb128> mario_limonciell: so basically the schemas and the code case
[20:57] <mario_limonciell> seb128, it's very similar to that yes.  i just tested it and it works
[20:57] <seb128> very similar? what is wrong in the version I copied?
[20:57] <mario_limonciell> execute() is no longer used
[20:58] <seb128> ok, will adapt to the current code style
[20:58] <seb128> but that's the idea, right?
[20:58] <mario_limonciell> yeah.  i've got the patch together.  don't worry about it.  i'll track down the bugs and put together a debdiff
[20:59] <mario_limonciell> i've been tracking this down the better part of the afternoon, it will feel good to have fixed it :)
[20:59] <seb128> what patch?
[20:59] <seb128> I'm about to do the upload with that change and a svn fix, should I wait on something elsE?
[20:59] <mario_limonciell> to update 19_extra_keybindings
[21:00] <seb128> no need to bother
[21:00] <mario_limonciell> okay, well here: http://paste.ubuntu.com/5120/
[21:01] <mario_limonciell> that's the current syntax +                execute (manager, "xrandr --auto", FALSE, FALSE);
[21:02] <seb128> mario_limonciell: is there a bug on launchpad?
[21:02] <mario_limonciell> yes
[21:02] <mario_limonciell> bug 179444
[21:02] <ubotu> Launchpad bug 179444 in gnome-control-center "gnome-settings-daemon crashed with signal 5" [Medium,New] https://launchpad.net/bugs/179444
[21:03] <seb128> mario_limonciell: can you attach the patch there?
[21:03] <mario_limonciell> sure
[21:03] <seb128> I'll use your version since you worked on it that's fair I think ;-)
[21:03] <seb128> feel free to ping before starting working next time
[21:03] <seb128> somebody pointed this one some times ago and I knew what to change
[21:03] <mario_limonciell> well i didn't realize it'd be this involved, but yeah next time i will :)
[21:19] <seb128> mario_limonciell: gsd update uploaded, thanks
[21:34] <mario_limonciell> thanks a bunch
[21:42] <seb128> thank you for looking in the issue
[21:42] <seb128> to the issue
[21:42] <seb128> rather ;-)
[23:55] <ubotu> New bug: #196802 in xserver-xorg-video-unichrome (universe) "Unichrome setup problems" [Undecided,New] https://launchpad.net/bugs/196802


[07:31] <santa_> good morning everybody
[07:31] <santa_> RikMills: about frameworks 5.77, see below
[07:33] <santa_> - the packages are "finished" and they work, but to install the packages I needed to add -proposed because of libgit2
[07:34] <santa_> - in fact these new frameworks are going to be affected by this small transition: https://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html#libgit2
[07:34] <santa_> - I would update python-pygit2 in -proposed in order to fix those failing autopkgtests
[07:41] <santa_> - golang-gopkg-libgit2-git2go.v28 needs to be updated to v30, see:
[07:41] <santa_> https://github.com/libgit2/git2go/blob/master/README.md
[08:53] <RikMills> santa_: ok, I will sees what is happening with people doing that transition. worst case, we can skip libgit support in the upload for a short time. we have done that before
[09:13] <santa_> RikMills: thank you very much, another thing I forgot to mention about libgit: some time ago the libgit support was somehow broken so we have this: "ktexteditor": [ "LibGit2" ] in cmake-ignore.json from ka-metadata; maybe we should remove it if the suport for libgit is ok now?
[09:14] <RikMills> santa_: agreed, that is useless nwo
[09:14] <RikMills> *now
[12:57] <BluesKaj> Howdy folks


[01:07] <initialize> So I wrote a shell script for bash ( http://codepad.org/Daamvs4E ). It works through ./scriptname.sh (except it appears that sudo isn't working), but trying to run it through a launcher only gives a blank terminal with nothing executing. Any help please?
[01:10] <lighta> trough launcher ? did you put it correctly in init.d ?
[01:13] <initialize> What do you mean?
[01:14] <initialize> I didn't know I had to do anything in init.d to run a launcher
[03:14] <Lord_Rahl> how do I get the volume app back in the status section? I remove pulseaudio and had to reinstall because of newer app needed it.
[03:18] <Lord_Rahl> nyone know what the package is?
[15:49] <searching> xfce4-panel freeze computer and make cpu 100%
[15:50] <leoquant> !xfce4-panel freeze
[15:50] <searching> not all time
[15:50] <leoquant> !xfce4-panel
[15:50] <searching> I press
[15:51] <searching> appear back
[15:51] <searching> but my problem is the freezing
[15:51] <charlie-tca> version of Xubuntu?
[15:51] <searching> 10.10
[15:51] <leoquant> natty?
[15:51] <searching> no
[15:51] <searching> maverick
[15:51] <charlie-tca> version of Xfce (apt-cache policy xfce4)
[15:52] <Sysi> has it been so for long?
[15:52] <searching> yes all blocks
[15:52] <Sysi> used to happen pretty often for me, in short periods
[15:53] <searching> ersion table:    4.6.2 0
[15:53] <searching> when play flash games
[15:53] <searching> like barn buddy
[15:53] <searching> freeze all
[15:53] <searching> cpu 100%
[15:53] <searching> and memory 90
[15:54] <searching> in rest may be once in a day
[15:54] <searching> I dissable xfce4-panel
[15:54] <searching> and play flash
[15:54] <searching> and no freeze
[15:55] <searching> any solutions?
[15:56] <searching> Installed: (none)
[15:56] <knome> !enter | searching
[15:56] <charlie-tca> sounds like a panel plugin to me
[15:56] <searching> what plugin to install?
[15:59] <charlie-tca> what plugins are installed?
[16:00] <charlie-tca> one of them might be causing the freeze
[16:00] <Sysi> i guess tasklist
[16:00] <searching> how to see installed plugins
[16:00] <Sysi> what do you have in your panel
[16:00] <searching> xfce menu
[16:00] <searching> places
[16:00] <searching> firefox
[16:01] <searching> connections
[16:01] <searching> updates
[16:01] <searching> clock
[16:01] <searching> and turn off restart
[16:01] <knome> searching, please, as told, do not use enter as punctuation - try to keep the lines longer
[16:02] <searching> ok
[16:10] <searching> can I remove xfce4-panel and use gnome-panel
[16:13] <searching> or what keys to press to stop freezing
[16:16] <charlie-tca> If you have not added anything to the panel, you should report a bug using
[16:17] <charlie-tca> ubuntu-bug xfce4-panel        in a terminal
[16:17] <charlie-tca> You can use gnome-panel, but it will add a lot of other things to the computer
[16:20] <searching> ok thanks
[16:20] <searching> may be the ps ax | grep weather causing problem
[16:20] <searching> 1866 pts/0    S+     0:00 grep --color=auto weather
[16:21] <charlie-tca> that is on your panel?
[16:22] <charlie-tca> take the things you added off the panel, and add them back one at time to find which one is freezing the system
[16:22] <searching> no
[16:23] <searching> ok thanks
[16:23] <searching> and then remove that plugin
[16:26] <searching> (firefox-bin:1416): Gdk-WARNING **: XID collision, trouble ahead from xsession-errors
[16:33] <searching> ok thanks bye
[18:15] <ele_> olaaa
[21:17] <mrothhh> were can I get a xen based xubuntu applaince
[23:03] <crangos> Hello. I am a bit confused with a problem I ran into trying xubuntu from a USB drive. Can someone lend me a hand?
[23:05] <Sysi> i need both hands for typing, but pope a question and somebody maybe will ansver
[23:06] <crangos> When booting I get the message about localhost.localdomain missing.
[23:06] <crangos> I am now trying to edit /etc/hosts as quite a few forum posts tell to.
[23:07] <crangos> Unfortunately the only text editor I seem to be able to start is vi... no fun.
[23:07] <crangos> But to edit, I have to use sudo, as far as I understand.
[23:07] <crangos> But I have no clue what the password is.
[23:08] <charlie-tca> what is the password you log in? that will be the same password
[23:08] <charlie-tca> do not type it here, please
[23:09] <crangos> How do I know that? i just started Xubuntu from the USB drive without installing, it never asks me to type one.
[23:09] <crangos> It must be the standard password for the user "ubuntu".
[23:09] <charlie-tca> then there isn't one,
[23:10] <charlie-tca> just type sudo vi /etc/hosts   and hit enter
[23:11] <Sysi> you tried nano?
[23:11] <Sysi> how did you made the usb stick?
[23:11] <crangos> Two errors. One about the missing localhost.localdomain, one about "can't mkdir /var/lib/sudo" no space on device, and when entering no password it tells me that "ubuntu" is not in the list of sudoers.
[23:11] <crangos> pendrivelinux
[23:11] <crangos> Worked great on my Desktop, but on the laptop it started acting up.
[23:14] <crangos> As for nano: "Error opening terminal: unknown"
[23:14] <charlie-tca> Sysi: would it have written defaults for the desktop, and now can't be changed to a different machine?
[23:14] <Sysi> i don't know how those live-thingies work
[23:14] <Sysi> "today's" method is unetbootin or usb-creator
[23:15] <crond> yep unetbootin works fine
[23:15] <crond> I just used it this morning to do an install
[23:16] <crond> just grab it and the latest 10.10 iso, or use the xubuntu / 10.10 livecd option in unetbootin
[23:18] <crangos> The laptop won't have internet, and the internet connection I have right now is so slow it would take me at least a couple hours to download a new iso, thats why I hopened I could somehow resolve it to at least do some testing.
[23:19] <crangos> But thanks anyway! :)
[23:19] <crond> np :)
[23:34] <seanlaptop> hi all
[23:35] <seanlaptop> anyone here have any issues installing itunes with wine?
[23:36] <seanlaptop> before anyone starts listing alternatives keep in mind i have an iphone and you can ONLY use it with itunes
[23:36] <Sysi> !iphone
[23:37] <Sysi> though i'm not sure about ios4
[23:37] <Sysi> afaik itunes is just impossible with wine, but google/winehq knows
[23:39] <Sysi> http://appdb.winehq.org/objectManager.php?sClass=version&iId=22647 not very bad
[23:40] <Sysi> (2am → G'night)
[23:40] <seanlaptop> i try to install itunes and it keeps crashing my session


[03:46] <fabbione> BenC: please pull me.. i have other fixes for you, including sparc stuff from davem and actually build linux-kernel-devel for real
[03:46] <fabbione> BenC: the sparc fixes also make gdb working on threaded apps
[04:16] <BenC> fabboine: ok
[04:22] <fabbione> oh you are awake :)
[04:22] <fabbione> BenC: sorry to pester you, did you get the ACPI fix from mjg59 ?
[04:23] <fabbione> if not i have the patch here
[04:28] <BenC> yeah, I have it
[04:28] <BenC> was out of town Wed/Thu, so I'm a bit behind
[04:32] <fabbione> yeah i know you were out :)
[04:32] <fabbione> great
[04:32] <fabbione> thanks a lot
[04:33] <fabbione> did you have fun?
[04:49] <BenC> yeah
[04:49] <BenC> I missed my train to come back on Thu though, so I didn't really get in till Friday morning :)
[04:49] <BenC> made some cash, played a tourney, was all good
[04:53] <fabbione> eheh
[04:53] <fabbione> you are addicted to miss trains :)
[04:54] <BenC> no shit :)
[04:55] <BenC> bad part is, the train there killed a guy, so I got hung up for about 5 hours while they cleaned that up
[04:55] <fabbione> ah
[04:55] <fabbione> suicide?
[04:55] <fabbione> or mistake?
[04:56] <BenC> not sure, it was on a part of the track where if he jumped off, he would have died at the bottom anyway, so he might have just been in the wrong place at the wrong time
[04:56] <fabbione> ok
[04:56] <BenC> was a creepy feeling after we found out that the crunching and bumping noise we just felt under the car was not rocks
[04:57] <fabbione> i can imagine
[04:57] <BenC> the conductor was like "That's what he gets for trespassing"
[04:57] <BenC> I think death is a little strong for tresspassing :)
[04:58] <fabbione> eheh
[10:08] <kosnick> sorry to interupt i am a newbie and i would like to see the code from ubuntu, just curius. Is it possible to do that on my computer?
[10:08] <crimsun> sure, but you're asking in the wrong channel.
[10:09] <crimsun> please migrate to #ubuntu, and I'll assist you.
[10:09] <kosnick> which one plz?
[10:09] <kosnick> ok
[10:09] <kosnick> thx
[11:07] <mjg59> BenC: So, do we get lots of patch goodness this week/


 Male sure you have executing permissions before running ./xxx.sh . You can do the through " chmod +x xxx.sh " command (re @lubuntu_bot: (irc) <Mat63> but it does not work)
[08:06] <jazahalka> Hi. I would like to help you, but I do not have deep technical understanding (I am here because this "No matter your skill level or your technical experience" on your web page). Maybe I could make Czech translation for you, but I do not know, what other
[08:07] <jazahalka> Maybe with some graphics - I can create vector graphics a bit.
[08:43] <guiverc> jazahalka, Thank you for offering.  Many of the team members will be sleeping now, and I know nothing about translation so I can't help there, but the Lubuntu team would LOVE any help you can offer.
[08:45] <guiverc> the team is also very short on graphics skills, so that skillset would be loved too !
[10:46] <jazahalka> So how can I join or?
[11:01] <kc2bez> jazahalka: If you are interested in helping the team please join our development channel. #lubuntu-devel
[11:43] <Alex70> Hey, I was just wrote in the devel group and was redirected here, as by the looks of things, devs are maybe not aware of this issue.
[11:44] <Alex70> So, whenever I add a openvpn connection (via import) to NM and store the password only for this user, the passwords never gets stored, and I get the following error instead: Failed to request VPN secrets #3: No agents were available for this request.
[11:44] <Alex70> Saving the password for all users does work, but that defeats the purpose of it being encrypted in the keyring.
[11:44] <guiverc> Alex70 this is Lubuntu support, Pop OS is not Lubuntu.
[11:45] <Alex70> But this happens on Lubuntu AND popOS
[11:45] <Alex70> So for lubuntu here I am
[11:45] <guiverc> which release of Lubuntu?
[11:46] <Alex70> I think it was latest, let me check
[11:48] <Alex70> lubuntu-20.10-desktop-amd64
[11:53] <guiverc> the manual page is https://manual.lubuntu.me/stable/G/AdvancedNetworking.html, sorry I have no experience with "via import", but I can't see how Lubuntu would differ to main Ubuntu (it's the same base system)
[11:55] <Alex70> Neither do I, that's why I'm asking here, though I would get some feedback. Because it seems that NM does not store in the keyring. As this only happens on lubuntu and pop os and not on debian and ubuntu.
[11:55] <Alex70> Though this should be a distro specific issue, for some odd reason.
[11:57] <guiverc> lubuntu & ubuntu are identical for all practical purposes (same base, only slightly different DE packages are installed).  Debian, Pop, Mint differ (Pop & Mint replace Ubuntu packages with their own via bumped package versions in other repos, Debian is a different system so of course diffes)
[11:58] <guiverc> If it works in Ubuntu.. you have the file you can use in Lubuntu anyway.  Lubuntu & Ubuntu are the same.
 Do you have gnome-keyring installed and running? (re @lubuntu_bot: (irc) <Alex70> So, whenever I add a openvpn connection (via import) to NM and store the password only for this user, the passwords never gets stored, and I get the following error instead: Failed to request VPN secrets #3: No agents were available for this request.)
[12:43] <Alex70> Yes
[12:43] <Alex70> As I'm able to inspect contents with the python3-keyring package and seahorse
[13:32] <Alex70> Ok so I tested this on lubuntu-18.04.5-desktop-amd64 and it worked, tested now on lubuntu-20.04.1-desktop-amd64 and it did not. Is there away to attach screenshots ?
[13:32] <Alex70> I'll try to change from nm-tray to nm-applet and see if that solves the issue.
[13:35] <kc2bez> Alex70: you can use something like imgur
[13:35] <Alex70> Ok making the change to nm-applet works.
[13:35] <kc2bez> so nm-tray doesn't have vpn support
[13:36] <kc2bez> You need to use the advanced network settings in the menu for vpn stuff.
[13:37] <Alex70> No actually it has vpn support
[13:37] <Alex70> But, it does not save the password if it is configured to store only for the user.
[13:37] <Alex70> Thus, save it in the user keyring
[13:39] <kc2bez> I think you have bumped into this issue https://github.com/palinek/nm-tray/issues/47
[13:42] <Alex70> Damn my browser froze. Did i miss something ? (is there a way to keep track of the history)
[13:43] <Alex70> But yeah as I said, to reproduce it, do the following:
[13:43] <Alex70> asd
[13:43] <kc2bez> The irc logs can always be found here https://irclogs.ubuntu.com/2021/01/05/
[13:44] <kc2bez> I think the only thing you missed was this: <kc2bez> I think you have bumped into this issue https://github.com/palinek/nm-tray/issues/47
[13:45] <kc2bez> We are bridged to Telegram here as well Alex70
[13:46] <Alex70> Hmmm yeah indeed seems to be very similar.
[13:47] <Alex70> So basically "Store this password for only this user" does not work.
[13:49] <kc2bez> It looks like it. There is an issue linked in the one I sent you that confirms that.
[13:50] <Alex70> Yeah checked it too.
[13:51] <Alex70> Thanks for the link (y)
 Help!
 I need to run a python script to generate a key to login to Netflix on my kodi box
 Following instructions on the Netflix addon dev’s GitHub, but in my Lubuntu terminal I keep getting
 Command ‘pip’ not found, but there are 18 similar ones
 Do I truly need to install pycryptodomex and websocket-client?
 Is it pip3 install ...  ?
 Aha! Apt install python3-pip
 Ok, next hurdle: I need to specify my browser path in the py script
 How do I determine where brave is hiding/living?
 how'd you install brave?
 CLI
 and how do you run it currently?
 CLI how?  from source or from like a snap or...?
 Birdie in the bottom left corner > Internet
 on the commnd line, if you execute brave-browser it opens Brave right?
 if so, then do which brave-browser to get the full path to the executable
 then use that path
 Dowhich doesn’t work
 Cmd nor found
 do isn't part of the command
 it's literally: which brave-browser
 Ah! Thank you


[08:54] <coolbhavi> hello
[08:54] <coolbhavi> I have a doubt
[08:55] <coolbhavi> How to get recognised as a Ubuntu Member in the forums?
[09:25] <ogra> coolbhavi, https://wiki.ubuntu.com/NewMemberHowto
[09:26] <coolbhavi> ogra  I too am an ubuntu member.. ;-) See my cloak.. :)
[09:27] <ogra> well, then i dont know
[09:32] <jsgotangco> coolbhavi: i believe you have to notify a forums mod/leader
[09:32] <coolbhavi> Ok..


[06:28] <flocculant> knome: ta
[06:29] <flocculant> bluesabre: 3 visual bugs during install now \o/ thankfully only 1 is us :p
[06:29] <flocculant> missing slideshow has been reported elsewhere
[06:43] <ochosi> also keep in mind that yakkety doesn't contain the latest greybird release...
[06:44] <flocculant> ochosi: that might be the 1 - not sure though
[06:47] <flocculant> bug 1617705
[06:47] <flocculant> the other 2 are slideshow and skip button issue(s) last is probably some gtk3.20/ubiquity thing
[06:51] <ochosi> oh right, yeah, that looks off
[06:51] <ochosi> stupid ubiquity custom widgets...
[06:51] <flocculant> :)
[06:51] <ochosi> i'll have to look into the installer myself for that
[06:51] <flocculant> have fun :p
[06:52] <ochosi> "thank you"
[06:52] <ochosi> :D
[06:52] <flocculant> :D
[06:52] <flocculant> I'll try not to find too much more ;)
[06:55] <flocculant> bluesabre: might be good if you remember that "bluesabre to schedule next meeting" before we're on Final Beta week :p
[06:57]  * flocculant thinks that now we have council with 3 people we should go back to the old way of running meetings
[06:57] <flocculant> I bet Unit193 could agree with me :p
[07:03] <Unit193> Ooooooh veeeery much I agree with flocculant.
[07:04] <flocculant> see - I knew it \o/
[07:05] <Unit193> Predictable, as always.
[07:06] <flocculant> lol
[10:12] <bluesabre> flocculant, indeed, was going to wait until the council results were finalized, and now they are :D
[10:15] <knome> old way being what? :P
[11:02] <flocculant> bluesabre: brave waiting for us to actually get something done ;)
[11:04] <flocculant> knome: not having to wait months for someone to set a meeting :p
[11:07] <knome> i do think that it's a fair way to split the chairing to all team leads
[11:08] <flocculant> of course you do :)
[11:08] <knome> maybe we can do something like a cycling chair, but if a meeting hasn't been held for X weeks, then the council will chair a meeting - after which we go back to the normal cycling chair
[11:08] <flocculant> not that it'll affect me for a long long time now :D
[11:09] <knome> well, i can see how not having meetings held can affect anybody
[11:09] <flocculant> do you mean can't?
[11:09] <knome> no
[11:10] <knome> i mean if we don't have meetings, it surely affects everybody
[11:10] <flocculant> oic
[11:10] <flocculant> guess so :)
[11:10] <knome> at least theoretically
[11:10] <knome> i very much think regular meetings are good
[11:11] <flocculant> yea - even if it's just a touch base thing - I'd agree with that
[11:11] <knome> because bringing back people's thoughts to thing X makes them... think about thing X and possible start working on thing X
[11:11] <knome> indeed
[11:11] <knome> and one of my arguments for regular meetings is that when they ARE regular and often enough, they won't be like 3 hour meetings
[11:11] <flocculant> ha ha
[11:11] <knome> because "finally we are back together, what about this and this and this too?"
[11:14] <flocculant> the meeting cycling needs sorting out too - cos XPL/council/you 3
[11:16] <flocculant> knome: thought you merged my strat doc changes?
[11:18] <knome> no... still needs team verification as there are some changes that are not just wording
[11:18] <knome> i'll send a mail about it soonish
[11:19] <flocculant> aah okey doke
[11:20] <flocculant> bbl
[11:24] <knome> same here
[15:18] <akxwi-dave> finally got the f**king Exchange server back up and working after 6 hours
[15:18] <akxwi-dave> sry wrong channel
[15:29] <ochosi> bluesabre: strcmp0 is fine, but you also need tolower stuff somwhow (haven't found the best way yet), otherwise the comparisons are not human-approved
[16:10] <nairwolf> Hi everyone, I hope you're fine
[16:11] <nairwolf> Unit193: I've read your message ;)
[18:11] <knome> could somebody write a short blog article about the intel cursor bug SRU? i can help with formulating, but it would be nice to get somebody who has been following the process closely to get the basic stuff in
[18:12] <pleia2> yeah
[18:12]  * pleia2 drafts
[18:13] <knome> thank you
[18:15] <knome> oh also, we should start pointing to the release pages from the front page, not the release announcement
[18:15] <knome> that way we don't have to worry about update the widget on every update
[18:15] <flocculant> might be worth mentioning that while it is fixed for xenial - same issue appears to have now shown up on trusty
[18:15] <knome> *about updating
[18:16] <flocculant> and isn't covered by the sru
[18:16] <knome> can mention, but i'm not sure how much work we will take to get it SRU'd to trusty; EOL soonish
[18:16] <knome> (eg. if it takes another few months, meh)
[18:17] <flocculant> well yea - I wasn't suggesting sru for trusty
[18:17] <knome> nope
[18:17] <flocculant> iirc bluesabre and I did discuss that a while back - but I couldn't confirm
[18:17] <knome> aaand hmm.
[18:17] <knome> we might need to flush some rewrite rules on xubuntu.org
[18:17] <knome> i wonder how that's possible...
[18:18] <knome> oh
[18:18] <knome> there we go!
[18:18] <knome> so
[18:18] <knome> http://xubuntu.org/release/16-04/
[18:18] <knome> every article with the release "16.04" (or technically, "16-04") will be appearing on that page now
[18:18] <flocculant> nice :)
[18:19] <knome> indeed!
[18:19] <knome> well, they have been doing that previously
[18:19] <knome> but we now have all kinds of other yummy stuff there as well
[18:19] <flocculant> wily is still on http://xubuntu.org/help/ btw
[18:19] <knome> hmm
[18:19] <knome> i thoguht i removed
[18:19] <knome> it
[18:19] <knome> and thought
[18:20] <knome> removed now
[18:20] <flocculant> though it's gone from docs.x - pleia2 did that almost at the same time that I said we should lose it :)
[18:20] <knome> or was it me?
[18:20]  * knome shrugs
[18:20] <knome> yeah, it might have been that.
[18:20] <flocculant> don't think so
[18:20] <knome> either way, i remember removing it from somewhere
[18:20] <flocculant> :)
[18:21]  * flocculant reboots after gtk update ...
[18:22] <flocculant> once upon a time I used to reboot after kernel upgrades
[18:22] <pleia2> ok, someone can beautify it http://xubuntu.org/?p=4107&preview=true
[18:22] <pleia2> and publish
[18:23] <knome> also
[18:23] <flocculant> sigh
[18:23] <knome> http://xubuntu.org/release/16-04/ is now updated with download and documentation links that disappear on EOL date
[18:23] <knome> well, the day after...
[18:23] <flocculant> got that stupid login to x.org fail again :(
[18:24] <knome> pleia2, taking over your lock
[18:24] <pleia2> knome: yeah, I'm out of it
[18:24] <pleia2> wp is a bit aggressive :)
[18:24] <flocculant> knome: let me read it before you publish :p
[18:25] <knome> ok
[18:25] <flocculant> ta
[18:25] <nairwolf> hi, if flocculant is right (intel cursor bug on Trusty), don't you think that could help users to publish a workaround somewhere in the website ?
[18:25] <flocculant> knome: just in case is all :)
[18:25] <pleia2> nairwolf: the workaround is in all the release announcements...
[18:26] <pleia2> and bug reports
[18:26] <flocculant> nairwolf: perhaps it would help them to report it for trusty instead of adding to a bug report that's marked fix released
[18:26] <pleia2> not sure how much more we can do
[18:26] <flocculant> not that I'm saying we'd do anything - which is unlikely given the time scale
[18:27]  * pleia2 nods
[18:27] <nairwolf> I'm talking about the trusty version. I'm looking for the workaround in trusty pages actually
[18:27] <pleia2> we don't really want to be encouraging people to use trusty
[18:28] <nairwolf> https://xubuntu.org/release/14-04/
[18:28] <nairwolf> I don't see any mention of that, if this bug is actually present on Trusty
[18:28] <flocculant> nairwolf: you won't find it there
[18:28] <nairwolf> Yeah, but some people might have their reason to stay on 14.04
[18:29] <nairwolf> flocculant: where, please ?
[18:29] <flocculant> I didn't say it was anywhere - I said you won't find it there
[18:29]  * flocculant thinks that we should think about only supporting LTS to release of nextLTS.1
[18:30] <nairwolf> pleia2: I know that's somewhere in bug reports. But normal users don't go to launchpad (I may wrong), and they start to search information in the official website. If an annoying bug like that is present, they would like to know if it will be fixed, or if it won't, they would like to have a workaround. That's all
[18:31] <nairwolf> And I agree with flocculant about supporting LTS to release of next LTS.1
[18:31] <flocculant> nairwolf: if we started putting things like that on x.org - we would need a fulltime page writer
[18:31] <pleia2> LTS.1 has been out for over a month
[18:31] <pleia2> but a 2ish release cycle isn't really an option ;)
[18:31] <pleia2> er, support
[18:32] <nairwolf> flocculant: I could help ;)
[18:32] <flocculant> pleia2: then we should support it and sru the intel thing (if it's an issue) in the same way it was for xenial
[18:32] <nairwolf> Now, where users can see bugs known ? On the release announcement ? https://xubuntu.org/news/xubuntu-16-04-1-release/
[18:33] <pleia2> flocculant: probably so, but I'm not the one who has to do the work, easy for me to say :)
[18:33] <flocculant> pleia2: ditto :)
[18:33] <pleia2> nairwolf: yes, under known issues
[18:33] <nairwolf> Do you think that would be great to add more information on this page : https://xubuntu.org/release/16-04/
[18:33] <pleia2> no, it changes too much as we fix things
[18:33] <flocculant> knome: biab
[18:33] <nairwolf> I could help by providing a draft if you want
[18:34] <pleia2> it's not just a once off :) we need to keep it updated for every bug fix that comes out
[18:34] <pleia2> I can't really commit the time to staying on top of that
[18:34] <pleia2> the only reason we're doing a blog post about this fix is that it's pretty major and people complain a lot
[18:35] <nairwolf> okay, okay, I'm a newbie here.
[18:35] <pleia2> I do appreciate the ideas
[18:35] <nairwolf> my first impression was it doesn't need so much job, but maybe I'm wrong.
[18:36]  * flocculant washes screen - just imagined bluesabre's face reading pleia2 and flocculant talking about sru's :p
[18:36] <pleia2> lol
[18:36] <nairwolf> I was looking for something to do to help
[18:36] <nairwolf> anyway, I need to go right now, I will be back later
[18:36] <flocculant> nairwolf: one job is never too much - but this one job would be a never ending cycle of words :)
[18:37] <flocculant> nairwolf: you are helping - you just haven't realised it yet ;)
[18:37] <flocculant> really biab now
[18:38] <nairwolf> flocculant: The aim isn't to summarize ALL known bugs, and ALL bug fixes, but the most important. The ones about xubuntu specific package for example.
[18:38] <nairwolf> see you later
[18:40] <nairwolf> flocculant: if you have time, can you confirm this bug on Yakkety ? #1567556
[18:41] <nairwolf> And I've seen this bug yesterday, but apparently, it will be fixed in the next version of greybird-gtk-theme : #1619059
[18:53] <fg01> Hi, Is some working on this https://bugzilla.xfce.org/show_bug.cgi?id=12763- Incorrect behavior of [Space] keyboard key in Thunar file-list?
[18:58] <knome> sorry, was on phone
[18:59]  * knome releases lock
[18:59] <knome> bbabl
[19:29] <flocculant> knome pleia2 - looking at the intel bug - there are 2 mentions of trusty there - and one of those is me saying I can't confirm it
[19:30] <flocculant> other 'trusty' mentions actually seem to be elementary
[19:30] <flocculant> oh hang on
[19:30] <flocculant> I'll look for 14.04 as well :p
[19:31] <flocculant> add 2 more
[19:31] <pleia2> I haven't confirmed it either
[19:31] <pleia2> might drop from the post and just let people ask
[19:33] <flocculant> I did drop it - with my hat on :p
[19:34] <pleia2> ty
[19:34] <flocculant> if people want to ask - we can tell them it needs reporting properly from trusty
[19:34] <flocculant> not piggybacked on a fixed xenial bug
[19:34]  * pleia2 nods
[19:35] <flocculant> I can publish - checked it for stranglish now too
[20:17] <knome> publish is ok, but please make sure it has the 16.04 release term
[20:19] <flocculant> knome: mm that's new on me - tick the 16.04 release box?
[20:19] <knome> yep
[20:19] <knome> same for every article that's related to releases
[20:19] <knome> gets stuff linked on the release page automatically
[20:20] <flocculant> right - just not seen it yet :)
[20:20] <knome> yup, no worries
[20:20] <knome> i've been ticking them here and there
[20:21] <flocculant> :)
[20:21] <flocculant> published
[20:21] <knome> thanks
[20:21] <knome> aaand as you can see: http://xubuntu.org/release/16-04/
[20:21] <flocculant> yup - was just looking :p
[20:22] <knome> i think this is working great now
[20:22] <flocculant> looks to be
[20:22] <knome> with all the press stuff, links and screenshots too
[20:22] <flocculant> yea - nice one for sure :)
[20:23] <knome> now the next thing is to consider the sidebar in those pages
[20:23] <flocculant> I assume you saw coversation re trusty above
[20:23] <knome> i don't think this is the one we want to use any more
[20:23] <knome> yes i did
[20:23] <nairwolf> flocculant: do you need I test if the intel bug is present with Trusty ?
[20:23] <nairwolf> I have real hardware for that
[20:23] <knome> which is why i said somebody who has been following should be involved with the article :)
[20:24] <flocculant> :)
[20:24] <pleia2> knome: good to social media it?
[20:24] <flocculant> nairwolf: YOU CAN IF YOU LIKE, NEEDS TO BE REPORTED THOUGH
[20:24] <flocculant> oops
[20:24] <knome> pleia2, yep - and i can tweet
[20:25] <flocculant> knome: I see what you mean - sidebar looks a bit odd in the context of 'just xenial stuff'
[20:25] <knome> yep
[20:25] <knome> it was much better when we only had the article stuff
[20:25] <knome> then that page was just one of the archive pages
[20:26] <nairwolf> okay, I'm downloading Xubuntu 14.04
[20:26] <nairwolf> I'll tell you later
[20:26] <flocculant> nairwolf: don't expect lots of clamouring on it - we're not sure we'll do anything
[20:26] <flocculant> that's down to tech
[20:27] <flocculant> who's going to be so happy that I'll be using xenial for 6 months soon :p
[20:28] <nairwolf> flocculant: Yes, of course, I understand
[20:29] <nairwolf> It's just to verify by someone else
[20:29] <flocculant> knome: just one point re the 16.04 'page' I wonder if we need the blurb between EOL date and Official Links?
[20:30] <flocculant> similarly for 14.04
[20:31] <knome> i think yeah - it's a nice way to summarize the release
[20:32] <flocculant> not sure I'd pick gnome software ;)
[20:32] <knome> feel free to improve it
[20:32] <flocculant> not that bothered - was just comment :)
[20:32] <knome> a few days ago it said 16.04 is the current development release ;)
[20:32] <flocculant> heh
[20:33] <flocculant> I'll say again that it's nice to see it all in one place though
[20:33] <knome> indeed
[20:38] <knome> booting up desktop...
[20:40] <pleia2> knome: and should it be on the front page?
[20:41] <nairwolf> flocculant: had you time to check my bug report ?
[20:43] <flocculant> nairwolf: yea sorry - forgot to say, as ochosi said login is greybird everyone will see it in yakkety atm, the fix will land at some point
[20:43] <flocculant> can't confirm the imgur bug - works fine here
[20:45] <flocculant> nairwolf: there are other greybird issues as well
[20:46] <nairwolf> You can't confirm the imgur bug ? this is weird, because I've tested it twice from my test computer, and from my actual computer.
[20:46] <nairwolf> and in both case, I couldn't upload to imgur
[20:47] <nairwolf> which other issue ?
[20:47] <flocculant> ok so perhaps it's something to do with isp's rather than xfce
[20:47] <nairwolf> ochosi said there will be soon a new version.
[20:48] <flocculant> input box outline(s) some are thick, some are thin, progress indicators during install
[20:48] <nairwolf> I can go on imgur.com with the normal way (browser). I should check how the upload is done
[20:48] <nairwolf> oh,this bug, I've seen your report. Badly, I didn't pay attention to that yesterday
[20:48] <flocculant> nairwolf: well all I can do is try using it - and it works fine for me
[20:49] <flocculant> such is the way of bugs - some people see them some don't - at which point it's got to be something external influencing
[20:50] <flocculant> could be anything, hardware for example
[20:50] <flocculant> anyway - time for me to wander
[20:50] <nairwolf> that's work today, on my actual computer
[20:51] <nairwolf> so I suppose you right, that was something related to isp
[20:51] <flocculant> could be - don't take my word for it there :)
[20:52] <nairwolf> it's funny to say that because I've tested twice at two times differently, and between them, I've uploaded a picture on imgur in the classic way (save picture then upload with browser)
[20:52] <nairwolf> I should retest that on the test computer
[20:57] <nairwolf> someone complain about the intel bug on 14.04
[20:57] <nairwolf> on facebook
[20:58] <flocculant> when it's on launchpad I'll read it
[20:59] <nairwolf> which "it" ?
[21:00] <flocculant> people complaining about intel in 14.04
[21:00] <flocculant> we certainly can't do anything without that
[21:00] <flocculant> and re what I said (and pleia2) above
[21:02] <nairwolf> okay, so the best answer is to share them the workaround or to tell them to upgrade, right ?
[21:02] <flocculant> does the workround work?
[21:03] <flocculant> don't tell people to upgrade - they'll have to do that eventually - but they might have reason to be using 14.04
[21:03] <flocculant> and finally - anyone who's talking about elementary based on 14.04 I have no interest in at all
[21:04] <nairwolf> I agree with elementary
[21:04] <nairwolf> I'm talking about one guy at facebook, which seemed to talk about xubuntu
[21:05] <nairwolf> but, yeah, maybe we'll see taht on launchpad also
[21:07] <flocculant> nairwolf: if you want to test this issue properly I would install 14.04, test for issue, upgrade to 14.05, test for issue, reinstall 14.04, upgrade to new hwe then test again
[21:07] <flocculant> one sensible report I saw said it was hwe upgrade issue
[21:08] <flocculant> with that - day done - night all :)
[21:09] <nairwolf> you mean, from 14.04.0 to upgrade to 14.04.5 ?
[21:09] <nairwolf> okay, maybe I'll do that this week-end.
[21:09] <nairwolf> good night flocculant !
[21:35] <bluesabre> ochosi, https://developer.gnome.org/glib/stable/glib-String-Utility-Functions.html#g-strncasecmp gives a bit of detail on sorting without case
[23:21] <knome> pleia2, no, we don't push news items to front page...
[23:22] <pleia2> yeah, just curious :)
[23:23] <knome> basically my idea was/is to replace the link to the release announcement with a link to the release page
[23:23] <knome> that should serve users better too
[23:23] <knome> while allowing a different sidebar for the release pages, i kind of got involved with a huge revamp of the sites css >__<
[23:24] <knome> it's so much sleeker already
[23:24] <knome> ...but there are a few things that aren't working yet


[09:40] <Tm_T> to share tiblits from other medium of Ubuntu community, https://plus.google.com/u/0/116332967182123293599/posts/7mQ5jBHZUvY
[14:11] <jose> IRCC: hey, I'd like to request permissions on the #ubuntu-lococouncil channel, is private atm and can't check who's an op or who isn't
[14:16] <Pici> jose: let me take a look...
[14:16] <jose> sure :)
[14:16] <Pici> jose: also, I just updated your factoid.
[14:16] <jose> great, thanks!
[14:22] <Pici> jose: Do you need to be able to make changes to the access list?
[14:22] <jose> yep
[14:22] <Pici> okay
[14:23] <jose> Pici: thanks a bunch!
[14:24] <Pici> jose: okay, you're all set.
[14:24] <jose> also, if I could have +F it'd be good
[14:24] <Pici> jose: do you need +F? you have +f
[14:24] <Pici> (I removed the +F from laura)
[14:25] <jose> Pici: we wanted to make the channel private (as per private conversations), and wanted to have only members of the LC on the list
[14:25] <jose> though, if it's needed we can keep +F on the IR-CC account
[14:26] <Pici> jose: Eh... you got it.  We can always request it from freenode if we need access to the channel for some weird reason.
[14:27] <jose> I'll make sure that if I ever drop my account +F gets transferred to the IR CC account
[14:27] <jose> !cookie > pici
[14:27] <Pici> jose: don't worry about it. freenode has our back ;)
[14:32] <jose> Pici: oh, also, if you could grant me ops at #ubuntu-locoteams it'd be great
[14:32] <jose> the ACL needs some updating in terms of LC members, and I need to set up a forward :)
[14:33] <Pici> jose: you should have it already. I gave you +AFRfiorstv
[14:33] <jose> Pici: that was for #ubuntu-lococouncil, I was talking about #ubuntu-locoteams
[14:33] <Pici> uh
[14:34] <Pici> oh
[14:35] <Pici> jose: I gave you enough access to change the access list there
[14:35] <jose> that's ok, thanks!
[15:08] <Pricey> Hmm why aren't you showing as identified on my screen...
[15:08] <Pricey> Ah different account. *trundles off*
[15:23] <jose> Pricey: if you're willing to drop jose so I can group it, then it'd be great :)
[15:35] <Pricey> jose: Taking a look.
[15:46] <Pricey> jose: Don't suppose you've asked the current owner/
[15:47] <jose> Pricey: I have, multiple times. I've sent memos with no replies (even though he's read some of them)
[16:23] <jose> Pricey: anything?
[16:30] <Myrtti> he's running home from work
[16:30] <jose> oh, got it :)
[16:57] <Pricey> jose: Just talking with other staff first. We don't often rush.
[16:58] <jose> sure thing :)
[19:38] <jose> Pricey: if anything pops up please let me know, feel free to PM at any time. jose goes to do some school stuff right now :)
[19:38] <Pricey> jose: ack, i'll not do anything without verifying you're still here
[19:39] <jose> ok!
[19:46] <Pricey> jose: I'm afraid the nick isn't expired.
[20:06] <jose> Pricey: I understand it from the point that the account isn't expired yet, but isn't there an exception in case the nick hasn't been used for more then 150 weeks (10 times the limit) and the owner doesn't reply memos?
[20:06] <jose> maybe the accountname can be changed to the nick he usually uses, and we can all be happy
[20:07] <Pricey> jose: http://freenode.net/faq.shtml#userexpirations "If the nick you want is someone's NickServ account name, it is considered expired only when the account itself is expired."
[20:08] <jose> well, I think I'll just leave like this anyways. thanks a lot, Pricey!
[20:09] <Pricey> jose: Sorry!


[19:34] <dobey> how can i build a source tree into a click, from the terminal, without having to install and use the full sdk?
[19:34] <dobey> in particular, an armhf click
[20:06] <popey> dobey: I use this:- http://paste.ubuntu.com/17305169/ which has one argument, you sit in the source tree and run it with the arch you want built for
[20:06] <popey> requires that you have the relavent click chroots
[20:08] <dobey> well, the directory in /var/lib/schroot/chroots suggest i have the right chroot
[20:08] <dobey> but trying to do something with "click chroot foo" wasn't happy
[20:12] <popey> In the immortal words of flavor flav, "Can't do nuttin for ya man"


[10:18] <cpaelzer> Hi, I'm looking for an advice as I feel to be too blind to see the obvious :-/
[10:19] <cpaelzer> lp api has the great searchTasks method which I used a lot in the past
[10:19] <cpaelzer> but now I happened to want to "get the tasks of a known bug number"
[10:19] <cpaelzer> and by ignorance or not knowing what term to look for I couldn't find an argument to searchTasks looking for bug numbers
[10:20] <cpaelzer> not too much of a problem I thought as I could get the bug directly and use the bug_tasks_collection_link
[10:20] <cpaelzer> like
[10:20] <cpaelzer> launchpad.bugs[1955009].bug_tasks_collection_link
[10:20] <cpaelzer> which gives (in the example): https://api.launchpad.net/devel/bugs/1955009/bug_tasks
[10:20] <cpaelzer> and then - per doc - https://help.launchpad.net/API/launchpadlib#Persistent_references_to_Launchpad_objects
[10:21] <cpaelzer> I thought I could just load it to get my list of tasks that I originally wanted tom searchTasks
[10:21] <cpaelzer> but launchpad.load() on that URL fails badly falling into some recursion death
[10:22] <cpaelzer> so I'm puzzled and pretty sure I'm just overlooking the better way to "get a task from a known bug number"
[10:22] <cpaelzer> any hints welcome
[10:23] <cpaelzer> cjwatson: ^^ I expect you read this channel anyway, but since the topic lists you on-duty a ping can't hurt
[10:24] <cpaelzer> oh - it seems to be as silly as I expected, the fetch works and the debug printing it triggers this
[10:24] <cpaelzer> let me rework that ...
[10:38] <rbasak> cpaelzer: in general, if the API spec says something that ends in _link, then you can get the object by accessing the Python attribute name that just misses off the _link suffix
[10:38] <cjwatson> cpaelzer: You could just use bug_tasks rather than bug_tasks_collection_link
[10:38] <cjwatson> snap-ish
[10:38] <rbasak> So try launchpad.bugs[1955009].bug_tasks_collection to get the object
[10:38] <cjwatson> bug_tasks *not* bug_tasks_collection
[10:39] <cjwatson> _collection_link is additionally special :)
[10:39] <rbasak> Ah, sorry
[10:40] <cpaelzer> interesting, so like launchpad.bugs[1955009].bug_tasks ?
[10:41] <rbasak> Yep
[10:43] <cjwatson> cpaelzer: There's a relevant example of exactly this on https://help.launchpad.net/API/launchpadlib#Collections
[10:44] <cpaelzer> thank you cjwatson and rbasak - yes this makes me see what was hidden to me before
[10:45] <cpaelzer> that exmaple helps, but I'd have expected that https://launchpad.net/+apidoc/1.0.html#bug would then have a "bug_tasks" entry
[10:45] <cpaelzer> or rather "example"
[10:46] <cjwatson> The apidoc describes the generic HTTP-level interface rather than launchpadlib's client-specific wrapping of it
[10:46] <cjwatson> (or rather lazr.restfulclient's)
[10:47] <cpaelzer> ok, thanks for filling in the puzzle pieces
[14:55] <blaker> I am unable to reset my launchpad.net password, the login.launchpad.net gives me an "Invalid OpenID transaction" error after submitting my new password, and its not reset. Can't really file a bug, because I cannot login to file the bug.
[15:11] <cjwatson> blaker: Despite the hostname, login.launchpad.net isn't something we maintain directly.  Could you email<EMAIL_ADDRESS>?  That goes into the SSO support queue and is usable without a working account
[20:31] <RikMills> seem to be getting an awful lot of build fail with no log
[20:32] <cjwatson> Yes, there's a known issue with bos02, let me add that to the topic
[20:33] <cjwatson> (I don't know exactly what the problem is.  IS has been investigating)
[20:33] <RikMills> thanks!


[08:48] !christel:*! It's that time of year again, the europeans get together to celebrate the eurovision song contest. Personally I'll be sporting the winning costumes from 1986 to celebrate with friends, but you may find Terry Wogan and friends in #eurovision