[10:58] <mup> PR operator#791 opened: Typing charm.py <Created by PietroPasotti> <https://github.com/canonical/operator/pull/791>


[07:16] <didrocks> good morning
[07:19] <duflu> Hi didrocks  (#firstpost)
[07:21] <didrocks> \o/
[07:49] <oSoMoN> good morning desktoppers, happy Friday!
[07:52] <duflu> Hi oSoMoN
[07:52] <oSoMoN> hey duflu
[07:54] <didrocks> salut oSoMoN
[07:54] <oSoMoN> salut didrocks
[08:51] <willcooke> morning
[09:01] <Laney> pew
[09:01] <Laney> happy friday!
[09:07] <duflu> pew pew
[09:07] <duflu> Morning willcooke, Laney
[09:08] <willcooke> happy Friday afternoon duflu
[09:08] <duflu> Also thanks to Laney for getting important stuff done while I slept
[09:09] <ogra> they allow you to sleep ?!? ... what kind of manager do you have ?!
[09:09] <seb128> hey willcooke Laney duflu
[09:10] <duflu> Shit. He didn't know
[09:10] <seb128> happy friday indeed
[09:10] <duflu> Oh hi seb128 :)
[09:10] <willcooke> hey ogra!  I was reading about the new Orange Pi yesterday, nice specs.  Do you know if there are any plans for Ubuntu Core support in the works?
[09:11] <ogra> none that i know of, nope ... what SoC is it ?
[09:11] <willcooke> Allwinner S <something>  7 I think
[09:11] <willcooke> maybe 11
[09:11] <ogra> nice
[09:12] <ogra> chances are good that it is supported by my linux-generic-allwinner snap
[09:12] <willcooke> Correction, H6
[09:12] <willcooke> ogra, https://www.tomshardware.co.uk/orange-pi-3-specs-pricing,news-59817.html
[09:13] <willcooke> USB3, 2GB RAM, eMMC, gigabit eth, mini pci
[09:13] <willcooke> Claims it comes with Ubuntu
[09:15] <Laney> hey duflu seb128 ogra willcooke
[09:15] <ogra> yeah, likely classic with a BSP kernel
[09:15] <willcooke> Hey Laney, how's the tooth?
[09:15] <Laney> duflu: np
[09:15] <Laney> sweet dreams young prince
[09:15] <Laney> same ol
[09:15] <willcooke> ogra, neat!  I'll get one
[09:17] <duflu> willcooke, before anyone gets confused, the Australia Day holiday on Monday is not on Australia Day. We just have a cultural need to allocate a Monday off for all holidays that fall on weekends
[09:17] <willcooke> duflu, ack, makes sense
[09:19]  * Laney approves of that
[09:26] <willcooke> hrm
[13:23] <jbicha> happy Friday
[13:39] <seb128> hey jbicha, happy friday to you as well!
[13:39] <seb128> mdeslaur, bah, not you as well! What's up with people adding ubuntu delta/tech debt with workarounds like disabling features or tests instead of fixing the problems :/
[13:40] <mdeslaur> seb128: I couldn't figure it out, you'll welcome to help if you'd like :)
[13:41] <seb128> mdeslaur, not today sorry, but still that's swipping dust under the carpet and adding technical debt
[13:41] <mdeslaur> seb128: I completely agree, hopefully I can revert it before release
[13:42] <seb128> what's wrong with letting things blocked in proposed until they get fixed?
[13:43] <mdeslaur> seb128: but but but, it messes with our kpis!
[13:43] <seb128> we need a new kpi for "tech debt" :)
[13:44] <seb128> joke aside it's a trend I don't like
[13:44] <seb128> doko did the same this week by just disabling automake tests and adding delta over Debian for that
[13:44]  * seb128 notes to raise that as an issue in Malta
[13:45] <seb128> or if we just workaround things being blocked in proposed by disabling features/tests then why do we bother having that infra as well, let's go back to just have things just land in the archive
[13:48] <mdeslaur> hey, I agree with you
[13:49] <mdeslaur> I've now TIL, so I'll be the one fixing it
[13:49] <mdeslaur> but the security fixes did need to go in, so it couldn't wait
[13:51] <seb128> mdeslaur, k, thanks. The security fix point makes sense, that was not obvious from the changelog though. Would be nice in those cases to state as "workaround to unblock due to <....>, that can be reverted once the current version migrates"
[13:51] <seb128> so if it goes sitting there and someone wants to deal with it then they know the context of why it was done
[13:51] <mdeslaur> ah yes, good idea
[13:51] <seb128> anyway, enough on the topic, thx for responding!
[16:58] <seb128> jbicha, good to see that mathias removed the libflatpak depends from the xdg portal just before 1.2.0 :)
[16:58] <seb128> willcooke, ^
[16:58] <willcooke> cool!
[16:58] <willcooke> thanks
[16:59] <seb128> np!
[17:02] <jbicha> seb128: yes, he beat me to it :)
[17:02] <jbicha> I wasn't expecting 1.2 today though
[17:03] <jbicha> last I heard was a vague "early 2019" I think
[17:04] <seb128> what did they add to it?
[17:09] <jbicha> maybe easiest for me to just link you to https://github.com/flatpak/xdg-desktop-portal/blob/master/NEWS if I understand your question right
[17:25] <kenvandine> i was surprised by 1.2
[17:41] <sergiusens> kenvandine: hey, I am trying out Disco and noticed that Ubuntu Software is marking every snap as unconfined. Is there a bug for that or should I log one?
[17:41] <kenvandine> sergiusens: oh it is?
[17:41] <kenvandine> i haven't seen a bug for that
[17:42] <kenvandine> so please file it
[17:42] <sergiusens> gotcha
[17:42]  * sergiusens waits for the "Software catalog is being loaded message" to go away, tic toc
[17:43] <sergiusens> kenvandine: I have this installed on my Surface Pro 4, have to say, performance feels better even if it might be a placebo, but most of all, touch has really improved, the osk works a lot better now.
[17:44] <kenvandine> oh good to hear
[17:44] <sergiusens> the only miss is the dock, if you hint a drag, it is hard to get out of it and the shell just goes wonky
[17:51] <jbicha> sergiusens: how are you running Ubuntu Software?
[17:52] <jbicha> we patch out the kudos stuff
[17:52] <sergiusens> jbicha: by clicking on the icon, I just killed the process which stayed after GUI closing and it moved on to "Software Catalog is being downloaded",  for the past 5 minutes
[17:52] <jbicha> there are some open bugs in Debian about that software catalog is being downloaded issue too
[17:53] <jbicha> we didn't used to have that problem :( (maybe newer 3.30 releases)
[18:00] <willcooke> I'm calling it a week.  Have a good weekend all o/
[19:29] <seb128> have a nice w.e desktopers!
[19:34] <sergiusens> kenvandine: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1813352
[19:35] <kenvandine> sergiusens: thanks
[21:25] <oSoMoN> have a good week-end everyone!


[07:02] <dpm> good morning all
[07:03] <happyaron> morning!
[07:05] <dpm> morning happyaron :)
[07:05] <dpm> well, good afternoon to you :)
[07:09] <happyaron> dpm: thanks :)
[12:20] <kelemengabor> Gwaihir: ping. could you submit a merge proposal for bug #923345 too? I think it would put it up onto the radar of developers.
[12:22] <dpm> bug 923345
[12:23] <dpm> oh, bugbot not running?
[12:25] <kelemengabor> https://bugs.launchpad.net/ubuntu-translations/+bug/923345
[12:36] <Gwaihir> kelemengabor, will look into it tonight :)
[12:36] <kelemengabor> thanks!
[12:43] <kelemengabor> dpm: could you help me a little with bzr branch management?
[12:44] <kelemengabor> for bug https://bugs.launchpad.net/ubuntu-translations/+bug/923762
[12:44] <dpm> kelemengabor, I can try :) What's the question?
[12:44] <kelemengabor> so, the devs asked me to update the proposed branch
[12:44] <kelemengabor> because upstream changed
[12:45] <kelemengabor> so, I did bzr uncommit, bzr pull, bzr commit the new changes
[12:45] <kelemengabor> and bzr push to the same branch fails
[12:45] <kelemengabor> bzr: ERROR: These branches have diverged.
[12:46] <kelemengabor> I don't want to merge it into the previous, but overwrite it with the new
[12:46] <kelemengabor> how do I do that?
[12:47] <dpm> let me read the bug first
[12:49] <kelemengabor> nevermind, --overwrite is the solution :)
[12:49]  * kelemengabor is a potato :(
[12:49] <dpm> s/potato/awesome :)
[12:50] <dpm> kelemengabor, I think the only issue here was the 'bzr uncommit' part. Generally, you'd simply do a 'bzr pull' to pull the latest upstream changes
[12:50] <dpm> then manually fix any conflicts if there are any
[12:50] <dpm> then commit
[12:50] <dpm> and then resubmit the merge proposal
[12:55] <kelemengabor> okay, resubmit is done, let's hope they will be quicker to review it this time :)
[12:57] <dpm> cool


[00:05] <jsalisbury> phillw, it would be best if you could open a launchpad bug, so we can track all the appropriate information.  You can open a bug using a web browser on any system(It doesn't have to be the system exhibiting the bug).  Again, just go to the following link: https://bugs.launchpad.net/ubuntu/+source/linux/+filebug
[00:06] <jsalisbury> Any system with Internet access that is.
[00:07] <phillw> jsalisbury: my VM does not want to to play......
[00:10] <phillw> jsalisbury: where do you need me to pull logs from? as it is a KVM I can pull any data you need.
[00:14] <jsalisbury> phillw, the following commands will collect all the appropriate data:
[00:14] <jsalisbury> 1) uname -a > uname-a.log
[00:14] <jsalisbury> 2) dmesg > dmesg.log
[00:14] <jsalisbury> 3) sudo lspci -vvnn > lspci-vvnn.log
[00:14] <jsalisbury> 4) cat /proc/version_signature > version.log
[00:15] <jsalisbury> phillw, what happened after you ran:  apt-get install linux-generic
[00:21] <phillw> jsalisbury: there seems to have been a drop of support for kernel (and motu). We do have people who want to make community re-spins but some of the tools that they used are no longer there.
[00:22] <phillw> jsalisbury: Hi Joe, this is the last I got from the VM
[00:22] <phillw> root@amjjawad:/home/ali/src/linux-3.13-rc8# make oldconfigscripts/kconfig/conf --oldconfig Kconfig
[00:22] <phillw> #
[00:22] <phillw> # configuration written to .config
[00:22] <phillw> #
[00:22] <phillw> root@amjjawad:/home/ali/src/linux-3.13-rc8#
[00:23] <phillw> root@amjjawad:/home/ali/src/linux-3.13-rc8# apt-get install linux-generic
[00:23] <phillw> Reading package lists... Done
[00:23] <phillw> Building dependency tree
[00:23] <phillw> Reading state information... Done
[00:23] <phillw> linux-generic is already the newest version.
[00:23] <phillw> 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
[00:23] <phillw> root@amjjawad:/home/ali/src/linux-3.13-rc8#
[00:25] <jsalisbury> phillw, Are you now running the 3.13.0-3-generic kernel (After a reboot) ?
[00:27] <phillw> jsalisbury: the VM I'm working with is Linux amjjawad 3.13.0-3-generic #18-Ubuntu SMP Mon Jan 13 19:11:13 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
[00:27] <phillw>  my machine is phillw@piglet:~$ uname -a
[00:27] <phillw> Linux piglet 3.13.0-3-generic #18-Ubuntu SMP Mon Jan 13 19:11:13 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
[00:30] <jsalisbury> phillw, ok, to summarize, you upgraded a server flavor from Precise running the 3.8 backport kernel to Trusty, but the kernel remained at 3.8.  But you were able to upgrade to 3.13.0-3-generic manually?
[00:31] <phillw> I did a -d to ask the server to jump to 14.04.
[00:31] <phillw> jsalisbury: correct
[02:46] <infinity> jsalisbury: As it turns out, rtg just fixed that bug. :P
[07:13] <ppisati> TGIF
[09:26]  * apw yawns mightily
[09:27] <smb> I am sure RAOF has mighty AUS BEEEES
[09:40] <apw> who stole my bees?
[09:41]  * apw notes .au does have above average bees
[10:36] <eagles0513875> hey apb1963
[10:36] <eagles0513875> i mean apw
[10:36] <eagles0513875> are you around
[10:36] <eagles0513875> apw: i stole them i forgot to tell you
[10:36] <eagles0513875> lol
[11:59] <apw> Sarvatt, was it you i was talking to about the gm45 "character square corruption" which looked like fence issues?
[11:59] <apw> Sarvatt, as i have just upgraded userspace from S to T and it has gone away now
[12:56] <apw> Sarvatt, though the tearing is appaling in chromium
[12:57] <eagles0513875> apw: finally got a reply to the email about the multitouch track pad
[12:58] <eagles0513875> apw: and the response is You mean that one?   http://www.spinics.net/lists/linux-input/msg26869.html  It never got applied, would be nice to hear whether that bug still exist and have it resubmitted.  Thanks David
[13:21] <apw> eagles0513875, sounds like movement, was the original submitter on the thread, if not maybe time to poke them
[13:22] <apw> the patch has a lot of questions you might hope that the maintainers would reply on
[13:22] <eagles0513875> apw: the original submitter i think is MIA
[13:22] <apw> but ... seemingly not
[13:22] <eagles0513875> i dunno if you could step in or not
[13:24] <apw> it is very hard to own a patch when you don't have the h/w to test changes on
[13:25] <eagles0513875> apw: i can test it but I have no idea what i would need to do to patch the kernel and recompile
[13:25] <eagles0513875> well i have a site on how to do that but not sure how to go about it
[13:26] <eagles0513875> apw: Would you be willing to help me out in this regard or am i a bit on my own
[13:40] <apw> eagles0513875, we may have a amchine with the same h/w will investigate
[13:40] <eagles0513875> apw: thanks I would though like to apply the patch for now to my existing kernel on 13.10
[13:41] <eagles0513875> apw: going to update the bug from the response i got in the email
[14:07] <apw> eagles0513875, canyou confirm this is a lenovo L530
[14:08] <eagles0513875> im not on a lenovo
[14:08] <eagles0513875> im on a toshiba sattelite s75-A7221
[14:08] <apw> and you know htat patch fixes your issue ?
[14:11] <apw> eagles0513875, ^^
[14:12] <eagles0513875> apw: i need help patching the existing kernel to test it as i dont know how to patch my kernel as well as recompile it
[14:19] <eagles0513875> apw: would it be possible for you to provide a testing kernel somewhere for me to install and test
[14:35] <apw> eagles0513875, is there a bug number for this?
[14:36] <eagles0513875> apw: for the upstream bug
[14:36] <eagles0513875> the only bug i have is the launchpad one linking to the discussion upstream previously
[14:38] <apw> which is which one
[14:40] <eagles0513875> apw: this is upstream http://www.spinics.net/lists/linux-input/msg26869.html
[14:41] <eagles0513875> on launch pad its bug 967399
[14:41] <ubot2> Launchpad bug 967399 in linux (Ubuntu) "[11.10] Elantech trackpoint does not work Lenovo " [High,In progress] https://launchpad.net/bugs/967399
[14:49] <rtg> smb, have you been running trusty kvm sessions lately ? I just upgraded from 12.04.2 to trusty and it appears to have wedged.
[14:50] <smb> rtg, KVM installs only not upgrades
[14:50] <rtg> smb, hmm
[14:50] <smb> I mean Trusty server installs
[14:51] <rtg> smb, right, thats all I'm doing to
[14:51] <rtg> guess I'd bettercheck that the daily works
[14:51] <smb> rtg, You are using a raid1 by chance?
[14:51] <rtg> nope
[14:52] <smb> Ok, that was one piece that has issues currently. Otherwise my installs were using a daily iso from the 15th
[15:03] <phillw> (15:00:07) phillw: hi, do we expect the bug that does not use the 3.13 kernel as a an upgrade from 12.04 LTS?
[15:06] <phillw> aka, when updating from 12.04 lts, we do not get the kernel release for 14.04
[15:06] <eagles0513875> phillw: O_o not like you to be in here
[15:07] <phillw> eagles0513875: the people here are proffessional.
[15:07] <eagles0513875> i know im working on getting a multi touch track pad issue solved
[15:07] <phillw> I need them to to fix an issue
[15:10] <phillw> eagles0513875:  joe salisbury is afk, as is bodhi-zazen.... I'm stuck until the kernel team fix it :)
[15:10] <apw> phillw, no we expect something upgraded to use the correct kernel
[15:11] <phillw> apw
[15:11] <eagles0513875> apw: how should i proceed with the issue of the multitouch track pad?
[15:11] <phillw> apw: it did not.... how do I fix it?
[15:12] <apw> phillw, if it was an update-manager update then (unintuitvly) the thing to do is to file a bug against update-manager and say "yes" to the during an update from a previous release
[15:12] <phillw> it's really good to catch this error so early :)
[15:12] <apw> as that gets the appropriate logs from the update
[15:13] <phillw> apw: the VM is non GUI.... so I cannot file a bug :(
[15:13] <apw> eagles0513875, we need to find out that this patch even has a thing to do with your issue, which would mean i need to spin a kernel (as you don't seem to be able to), and that'll happen when i get to it
[15:13] <apw> phillw, you can file a bug, its just harder
[15:13] <eagles0513875> apw: if you can give me the steps on what i need to do I can do it
[15:14] <apw> phillw, iirc you can just do the same thing, and it uploads it and then gives you the URL for it to continue on another machine
[15:15] <phillw> apw: the VM is there... tell me what you need & I will do it. Just recall that I am a tester not a coder and you will have to give me step by step instructions.
[15:15] <ikonia> if you need step by step instructions, he may as well just do it himself
[15:17] <eagles0513875> ikonia: i just really need help with patching. if http://www.howopensource.com/2011/08/how-to-compile-and-install-linux-kernel-3-0-in-ubuntu-11-04-10-10-and-10-04/ works then i can follow those instructions to apply
[15:17] <eagles0513875> compile*
[15:17] <phillw> ikonia:  I have offered them root access to the VM. More than that I cannot do :)
[15:17] <apw> phillw, "ubuntu-bug update-manager" should work GUI or not
[15:17] <apw> phillw, i think ikonia was talking to eagle
[15:18] <ikonia> eagles0513875: I'm missing background here - but what kernel version are you trying to build ?
[15:18] <eagles0513875> ikonia: the one that comes with 13.10
[15:18] <eagles0513875> forget that that article is for older kernels and release. are the steps to compile it the same?
[15:18] <apw> if you arn't confident building it then a negative test will not be conclusive anyhow
[15:18] <eagles0513875> ok
[15:19] <phillw> ikonia: I'm building the kernel for 14.10
[15:19] <ikonia> phillw: so ?
[15:19] <phillw> sorry... 14.04
[15:19] <eagles0513875> apw: ill leave it in your hands
[15:19] <eagles0513875> phillw: i think that was directed at me btw
[15:20] <ikonia> eagles0513875: is there a bug logged for this ?
[15:20] <phillw> eagles0513875: that communities can not make respins is an issue.
[15:20] <ikonia> communities can make respins
[15:20] <eagles0513875> ikonia: my issue has nothing to do with what phillw is doing
[15:20] <ikonia> who said they can't ?
[15:21] <ikonia> ahh
[15:21] <eagles0513875> wait a min we are on two different wave lengths here
[15:21] <ikonia> I'm missing background/context for both issues
[15:21] <eagles0513875> ikonia: my issue is relating to my multitouch track pad on my laptop
[15:21] <eagles0513875> i found https://launchpad.net/bugs/967399
[15:21] <ubot2> Launchpad bug 967399 in linux (Ubuntu) "[11.10] Elantech trackpoint does not work Lenovo " [High,In progress]
[15:21] <phillw> ikonia: https://answers.launchpad.net/ubuntu/+source/debian-cd/+question/240037
[15:21] <eagles0513875> and this laptop has an elantech multitouch track pad but that bug is geared specifically for lenovo so I was wanting to patch my kernel to see if that fixes my track pad not working at all.
[15:22] <ikonia> eagles0513875: is that your exact bug ?
[15:22] <eagles0513875> btw apw thanks for offering to compile a test kernel with the patch
[15:22] <eagles0513875> ikonia: yes that my track pad doesnt work at all right now.
[15:22] <apw> phillw, when something is hard to do, that doesn't make it easy to document, cd creation is such a beast, it has evolved over some 12 years
[15:22] <ikonia> eagles0513875: ok - so it's the same bug but on version 13.10 ?
[15:22] <eagles0513875> correct
[15:23] <ikonia> eagles0513875: ok, cool, so the bug is valid.
[15:23] <ikonia> eagles0513875: so where are you getting the patch from ?
[15:23] <eagles0513875> the bug
[15:23] <eagles0513875> there is one as well as a diff
[15:23] <apw> ikonia, though this bug is for a lenovo, and that isn't what he has
[15:23] <ikonia> what ???
[15:23] <ikonia> the patch isn't even for the 13.10 kernel
[15:23] <eagles0513875> the patch is for a lenovo lapto mine is a toshiba
[15:23] <ikonia> eagles0513875: why are you talking to upstream ???
[15:23] <phillw> apw: I do have people to help.... what is needed is kernel for server edition to up grade to the 14.04 edition (3.13)
[15:23] <ikonia> what the debvil.....
[15:24] <eagles0513875> apw asked me to see what happened to it as it had initially been filed upstream for inclusion into mainline
[15:24] <eagles0513875> and basically the last comment i got today about it.
[15:24] <ikonia> eagles0513875: so what is the model of track pad you have ?
[15:24] <eagles0513875> how would i check that
[15:25] <ikonia> you don't even know the model ???
[15:25] <ikonia> you're assuming the lenovo track pad has the same model as yours and the lenovo patch will fix it
[15:25] <apw> phillw, and hopefully the log as to why the upgrade didn't complete will be in the logs from the bug you're filing with the ubuntu-bug command
[15:25] <phillw> apw: I cannot file a bug :(
[15:25] <ikonia> eagles0513875: how are you following bugs looking at patches, when you don't know the model of the hardware that's failing ????
[15:26] <phillw> apw:  it is a server with no X
[15:27] <ikonia> you can manually look at the logs ?
[15:27] <ikonia> log the bug manually on launchpad.net ?
[15:28] <apw> phillw, you do not need X to file a bug, i just did it here by doing a DISPLAY= ubuntu-bug ... and it does it all in ascii
[15:28] <apw> did you even try it ?
[15:29] <eagles0513875> ikonia: i found out how to determine which track pad i have but not the model
[15:30] <eagles0513875> ⎡ Virtual core pointer                          id=2    [master pointer  (3)] ⎜   ↳ Virtual core XTEST pointer                id=4    [slave  pointer  (2)] ⎜   ↳ ETPS/2 Elantech Touchpad                  id=11   [slave  pointer  (2)]
[15:34] <phillw> apw and what is the name of the bug you want?
[15:35] <apw> ubuntu-bug update-manager
[15:35] <apw> and say Yes to the "during an upgrade from a previous release" prompt
[15:38] <phillw> runnig
[15:39] <phillw> apw: The collected information can be sent to the developers to improve the
[15:39] <phillw> application. This might take a few minutes.
[15:39] <phillw> ..[15:39] <phillw> Authentication is needed to run `/bin/cat' as the super user
[15:39] <phillw> Multiple identities can be used for authentication:
[15:39] <phillw>  1.  ali,,, (ali)
[15:39] <phillw>  2.  Jason,,, (jason)
[15:39] <phillw>  3.  eagles,,, (eagles)
[15:39] <phillw>  4.  Kris,,, (kris)
[15:39] <phillw>  5.  bipul
[15:39] <phillw>  6.  dan
[15:39] <phillw> Choose identity to authenticate as (1-6): ................
[15:40] <ikonia> eagles0513875: you're on shacky ground
[15:40] <ikonia> eagles0513875: it seems a very random approach
[15:40] <eagles0513875> ok
[15:40] <eagles0513875> i guess ill just wait it out. for apw
[15:41] <ikonia> eagles0513875: I would try to get some factual information together
[15:41] <ikonia> eg: your hardware make/model - the hardware make/model that this patch fixes/support would be a good start
[15:41] <ikonia> before pushing/wasting peoples time for tests
[15:41] <ikonia> do you even known if it uses the same module to drive the touchpad as this bug ?
[15:41] <eagles0513875> ok. thing is the bug doesnt specify which elantech model it fixes either
[15:42] <ikonia> eagles0513875: right - so you finding out would be a good start
[15:42] <eagles0513875> ikonia: that is why im asking for help to patch my kernel
[15:42] <eagles0513875> to test and see if it truly does fix the issue.
[15:42] <ikonia> eagles0513875: why are you patching the kernel when you don't know the scope
[15:42] <ikonia> eagles0513875: you're running before waling
[15:42] <ikonia> walking
[15:43] <eagles0513875> how am i supposed to determine the scope by looking at the patch and determining my model?
[15:43] <phillw> eagles0513875: do you have a profile at https://wiki.ubuntu.com/QATeam/Hardware ? makes life a lot easier to the devs :)
[15:43] <eagles0513875> phillw: no
[15:43] <phillw> eagles0513875:  then do it :)
[15:43] <ikonia> eagles0513875: a good basic check would be "what is the target kernel that patch is aimed at"
[15:44] <ikonia> eagles0513875: that patch maybe for 3.1.8 - and the changed between 3.1.8 and 3.1.12 make it useless
[15:44] <eagles0513875> from the looks in the bug report 11.10
[15:44] <eagles0513875> im guessing what ever kernel was on that
[15:44] <ikonia> eagles0513875: right, so quite old - so probably not going to be targeting / compatible with the same kenrel you are using
[15:45] <ikonia> 3 years is a long time
[15:45] <ikonia> a lot gets changed in 3 years
[15:45] <eagles0513875> ikonia: if that is the case besides filing a bug report with all the appropriate bug information
[15:45] <ikonia> ?
[15:45] <phillw> apw: I have no idea what it is up to.....
[15:46] <eagles0513875> ikonia: what i need to do is file a bug report against 13.10 instead
[15:46] <eagles0513875> with the version of my track pad in that case
[15:46] <ikonia> yeah, I think that's a good thing to do, reference the other bug if you want, but a lot has changed
[15:46] <ikonia> try to get solid factual information though
[15:46] <ikonia> nothing half hearted or guessed, facts only
[15:47] <phillw> eagles0513875: have a read of https://wiki.ubuntu.com/QATeam/Overview/Install_Bugs
[15:47] <ikonia> why are you giving him an installer bug link ?
[15:47] <ikonia> I thought this was a problem after the install, with the running OS
[15:48] <eagles0513875> phillw: O_o not sure what that has to do with anythign im experiencing plus im not on 14.04
[15:48] <eagles0513875> ikonia: do you mind if we take this discussion back to kubuntu
[15:48] <ikonia> no problem at all
[15:48] <ikonia> phillw: I'd suggest focusing on your own problem
[15:48] <phillw> eagles0513875: I give people all options.
[15:48] <ikonia> you give bad information
[15:48] <ikonia> that is random and not helpful
[15:48] <ikonia> so I'd sugget focusing on your own problem only
[15:50] <phillw> ikonia: that, my friend, is something I do not give.... a bug is a bug, the dev's need what is available. Having the the hardware is always handy :) But, we will not fall out @P
[15:51] <ikonia> you're giving bad information and bad links to people, please don't
[15:51] <ikonia> focus on your own bug please.
[15:54] <phillw> ikonia: I'd like to query as to a link given that is run by a canonical person can be seen as you as a bad link? https://launchpad.net/~nskaggs
[15:55] <ikonia> for the exact reasons I said earlier
[15:55] <ikonia> it's nothing to do with the installer
[15:55] <ikonia> he's not running 14.04
[15:55] <ikonia> seems pretty clear giving a link to installer bugs for non-installer problems is "bad"
[15:56] <phillw> ikonia: and I didn't know that... as to how updates break installed systems is "bad" :)
[15:56] <ikonia> sorry, I don't understand your last statement
[16:14] <phillw> ikonia: I'm chatting with eagels, chatting on two channels does get confusing! I'm awaiting the fix to have the 3.13 kernel installed onto 12.04 lts :) Please do not take my frustrations personally, it is just somewhat frustrating at times :)
[16:17] <apw> phillw, earlier you said you were upgrading this machine and didn't get 3.13, are you saying you are doing 'update' of 12.04lts and expecting to get the 3.13 kernel
[16:18] <phillw> apw indeed, i expected an lts to lts upgrade actually bring the new kernel :)
[16:19] <apw> phillw, so the machine is now running 14.04 yes?
[16:20] <apw> (just confirming that that is right, as that makes the bug i asked you for the right thing)
[16:21] <apw> eagles0513875, ok a saucy kernel with that patch applied is here: http://people.canonical.com/~apw/lp967399-saucy/
[16:21] <eagles0513875> thanks apw :) will give it a try
[16:23] <phillw> apw: you know something... I've got lot a lot of apologising and self kicking to do.... although reminding us in upgrades that we need to reboot twice instead of trying to remember. :D
[16:24] <apw> one doesn't need to reboot twice in an upgrade, i just did one on my other computer, S->T not half an hour ago, and only rebooted once
[16:25] <phillw> apw I had to on the KVM virtual machine
[16:26] <apw> that may be an artifact of the way the kvm images are maintained there, not something i have seen on any of mine
[16:27] <phillw> it *may* be worth a release note for any server people running kvm.... but is more a #ubuntu-server issue. I'm only here to build the non-pae 13.03 kernel :)
[16:27] <infinity> phillw: I told you yesterday that the upgrade from a non-3.2 kernel wouldn't upgrade you to 3.13, and told you how to work around it.
[16:27] <infinity> phillw: As it turns out, rtg fixed that bug last night, so it should work now.
[16:27] <infinity> phillw: I'm not sure why you're still talking about this.
[16:28] <phillw> infinity: i was aware the the bug was in progress, and then got asked to raise a bug......
[16:28] <infinity> Where's the bug you filed?
[16:29] <phillw> infinity: I was still in the process of trying to file it! the server is cli and has sat for 60 minutes '''collecting data'''
[16:30] <rtg> smb, just installed the trusty server amd64 daily. same result. gets stauck right after /scripts/init-bottom
[16:30] <infinity> phillw: Okay, or you could not file it.  Since the bug is "there's not path for precise+lts-backport upgrades to to 14.04" and, like I said, this was (a) a known bug, and (b) fixed 6 hours after you tripped on it.
[16:30] <smb> rtg, weird...
[16:31] <rtg> I wonder why it would boot the installer....
[16:33] <phillw> infinity: if the bug is fixed, no need to report... unless some one wants bug fixing points :P As I have the VM with 3.13 I can use it to build the non-pae kernel. To the other wonderful people on here, a massive thank-you.
[16:35] <infinity> phillw: Is this just a one-time kernel build for yourself, or something you're hoping to upload to the archive?
[16:35] <infinity> phillw: Cause as I've told many people, many times, I won't accept a non-pae kernel in the archive without it also coming with a (believable) statement of support intent, like I have for lowlatency.
[16:35] <phillw> infinity: it is going to be a 14.04 lts kernel for any flavour that needs it.
[16:35] <infinity> phillw: Throwing a rotting corpse of an unmaintainer kernel in the archive so people can have unpatches security holes on their old hardware isn't a win.
[16:36] <infinity> phillw: It is, is it?  According to whom?  And who will maintain it?
[16:36] <infinity> s/unmaintainer/unmaintained/
[16:36] <infinity> phillw: Who's going to rebase it against master every 3 weeks?
[16:36] <infinity> phillw: Who's going to test those rebases to make sure they still boot and work?
[16:37] <infinity> phillw: Since I'm pretty sure this isn't you, who are yo uvolunteering to do work that they didn't sign up for?
[16:38] <phillw> infinity: "we" the people will maintain it. on http://phillw.net/isos/ and as bodhi-zazen has agreed to teach us http://bodhizazen.net/Tutorials/kernel we are secure in how we support this.
[16:40] <phillw> infinity: https://answers.launchpad.net/ubuntu/+source/debian-cd/+question/240037 what you seem to forget, is that with some help... communities can co-ordinate and make spins.
[16:40] <infinity> phillw: If this isn't going to be in the primary archive, you can do whatever you like.
[16:42] <phillw> infinity: the kernel will be in a ppa (so I'm told) and any community can use it as a build / update area. I've now to build my first kernel :)
[16:42] <psivaa> smb: rtg: i think we are seeing the same issue that you are discussing, today's trusty server installs being broken... just confirming if it helps
[16:43] <rtg> psivaa, change your display from cirrus to vga
[16:43] <smb> psivaa, Turns out broken means only that in kvm the default cirrus card causes framebuffer issues
[16:43] <smb> psivaa, The guest gets up just the screen stops getting updated
[16:44] <phillw> smb: I'm sure we discussed this last night? https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1080674
[16:44] <ubot2> Launchpad bug 1080674 in cairo "[QEMU] Corrupted desktop screen for raring desktop installation in QEMU guest (Cirrus graphics). Affects KVM but not VBox." [Medium,Confirmed]
[16:45] <psivaa> smb: rtg: ok, just to confirm... does that tally with the following log:
[16:45] <psivaa> Jan 17 07:32:43 anna[8496]: corrupted status flag!!: 0
[16:45] <psivaa> Jan 17 07:32:43 anna[8496]: (process:10447): tar: write error: No space left on device
[16:45] <psivaa> Jan 17 07:32:43 anna[8496]: (process:10447): tar: write error: No space left on device
[16:45] <smb> psivaa, No that rather sounds obviously like disk too small?
[16:46] <psivaa> smb: no disk size is no different to what we used yesterday, 8G
[16:46] <phillw> rtg: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1080674/comments/43
[16:46] <ubot2> Launchpad bug 1080674 in cairo "[QEMU] Corrupted desktop screen for raring desktop installation in QEMU guest (Cirrus graphics). Affects KVM but not VBox." [Medium,Confirmed]
[16:46] <smb> phillw, No it is not. That is an x driver bug
[16:47] <phillw> okies :)
[16:47] <smb> rtg, https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1269401
[16:47] <ubot2> Launchpad bug 1269401 in linux (Ubuntu) "[Trusty] Switching framebuffers fails on VMs using cirrus" [Medium,Confirmed]
[16:57] <rtg> jjohansen, bug #1270215 looks like an AA issue, e.g., trusty LTS prevents dhclient from running.
[16:57] <ubot2> Launchpad bug 1270215 in Ubuntu "kernel 3.13.0-4.19~precise1-generic: no internet" [Undecided,New] https://launchpad.net/bugs/1270215
[17:16] <jrr> what should I try next on this?: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1269986
[17:17] <ubot2> Launchpad bug 1269986 in linux (Ubuntu) "kernel oops - unable to handle kernel NULL pointer dereference; probe_monitoring_device / nouveau_i2c_identify" [Undecided,Confirmed]
[17:26] <jsalisbury> rtg, shall I hold off on bisecting bug 1270215 ?  since it may be an AA issue?
[17:26] <ubot2> Launchpad bug 1270215 in linux (Ubuntu Precise) "kernel 3.13.0-4.19~precise1-generic: no internet" [High,New] https://launchpad.net/bugs/1270215
[17:27] <rtg> jsalisbury, yeah, it'll be a waste of your time. lets get jjohansen to look at it first.
[17:27] <jsalisbury> rtg, ack
[17:38] <rtg> jsalisbury, However, bug #1270218 looks like a good bisect candidate.
[17:38] <ubot2> Launchpad bug 1270218 in linux (Ubuntu) "3.13.0-4-generic [Radeon HD 7950] No Display at Login Screen" [Medium,Confirmed] https://launchpad.net/bugs/1270218
[17:39] <jsalisbury> rtg, heh, looking at that one right now :-)
[17:39] <rtg> there just weren't that many commits between -3 and -4
[17:40] <jsalisbury> rtg, looks like it was introduced between v3.13-rc8 and commit 85ce70f
[17:40] <rtg> yup
[17:41] <jsalisbury> rtg, although there were a few branch merges
[17:41] <eagles0513875> apw: trying to install the kernel headers and its complaining  about missing dependencies
[17:48] <jsalisbury> rtg, Should be a quick bisect, I'm guessing it's one of these:
[17:48] <jsalisbury> git log --pretty=oneline b25f3e1c358434bf850220e04f28eebfc45eb634..85ce70fdf48aa290b4845311c2dd815d7f8d1fa5 -S radeon
[17:48] <jsalisbury> f244d8b623dae7a7bc695b0336f67729b95a9736 ACPIPHP / radeon / nouveau: Fix VGA switcheroo problem related to hotplug
[17:48] <jsalisbury> 59aebe2b32466f7ed5b79f18646be6dddc926a6d Revert "drm/radeon: Implement radeon_pci_shutdown"
[17:48] <jsalisbury> 9c57a6bd3ea4a9870a7ce2fd961da6ef4986bbc1 drm/radeon: add radeon_vm_bo_update trace point
[17:48] <jsalisbury> 84d597b74b58dd52621abf5f052a81370ace1816 drm/radeon: add VMID allocation trace point
[17:48] <jsalisbury> ec39f64bba3421c2060fcbd1aeb6eec81fe0a42d drm/radeon/dpm: Convert to use devm_hwmon_register_with_groups
[17:48] <rtg> jsalisbury, seems likely
[17:54] <Sarvatt> hmm, the kernel apport hook should probably have /var/log/kern.log in it so it doesn't just have the successful boot dmesg attached like that bug
[17:58] <rtg> Sarvatt, doesn't bdmurray own apport ?
[18:00] <bdmurray> rtg: that's pitti but I work on it some
[19:11] <eagles0513875> apw: sadly that didnt fix the problem for me :(
[20:13] <rtg> BenC, from LKML: Kernel stack overflows due to  "powerpc: Remove ksp_limit on ppc64" with v3.13-rc8 on ppc32 (P2020)
[20:15] <apw> rtg, nice catch ...
[20:15] <rtg> apw, just drifting thru LKML...
[20:16] <apw> we do rely on it :)
[20:16] <rtg> hopefully it'll pop out for 3.13 final
[20:17] <jjohansen> rtg: yep 1270215 looks like a policy issue
[20:17] <rtg> jjohansen, ack
[20:27] <rtg> bjf, from LKML: 'Baytrail problems (was Re: Linux 3.13-rc8)' talks about a stable patch that might give you fits.
[20:35] <bjf> ARGH!
[23:30] <stgraber> sforshee: https://www.stgraber.org/2014/01/17/lxc-1-0-unprivileged-containers/


[01:29] <hggdh> micahg: you will be mentoring Dustin?
[01:30]  * micahg will try
[01:48] <DustinAmodeo> hey micahg, around?
[01:48] <micahg> yeah
[01:48] <micahg> but I'm still trying to figure something out...
[01:48] <micahg> DustinAmodeo: PM?
[02:14] <XDevHald> BTS is not working for reporting bugs, need to know how to gather ubuntu-bug from the apport.
[02:15] <micahg> XDevHald: are you trying to submit a bug to debian or ubuntu?
[02:16] <XDevHald> Hey micahg: I am fixing/reporting/triaging
[02:16] <micahg> XDevHald: you want to report to ubuntu?
[02:17] <micahg> DustinAmodeo: ok, which FF version are you using?
[02:17] <XDevHald> My apologies micahg as I wasn't able to understand the question.
[02:17] <micahg> XDevHald: that was going to be my line :)
[02:17] <XDevHald> Hehe
[02:18] <XDevHald> I was using the Debian BTS software to report/fix the bugs from launchpad but BTS is no longer supported. Claims I need to use ubuntu-bug from the apport
[02:18] <micahg> ok, to report to Ubuntu, it's ubuntu-bug PKGNAME
[02:18] <XDevHald> ah
[02:19] <XDevHald> Thank you micahg, I appreciate the clarification :-)
[02:19] <micahg> np XDevHald
[02:21] <XDevHald> micahg: What about a tool to fix the bugs?
[02:21] <micahg> XDevHald: fix? how?
[02:22] <XDevHald> Say if there is a bug from launchpad and I want to contribute on fixing it. How would I go about gathering the package that they want fixed on my desktop to triage and then fix
[02:22] <XDevHald> bbiab, PM if you can micahg.
[02:22] <micahg> XDevHald: depends on the package
[02:24] <micahg> DustinAmodeo: I'm assuming you've read the triaging guides?
[02:24] <DustinAmodeo> i have
[02:24] <micahg> ok
[02:24] <micahg> so, why don't you grab a bug from the firefox-3.0 package
[02:24] <micahg> and we can look at it
[02:27] <DustinAmodeo> can i sort bugs by package?
[02:28] <micahg> you can go to a specific package
[02:28] <micahg> https://edge.launchpad.net/ubuntu/+source/firefox-3.0
[02:31] <DustinAmodeo> i'm still here
[02:31] <DustinAmodeo> just sorting through this
[02:33] <DustinAmodeo> so i'm looking at Bug #327943
[02:33] <ubot4`> Launchpad bug 327943 in firefox-3.0 "firefox crashed with SIGSEGV in sqlite3_column_int64()" [Medium,New] https://launchpad.net/bugs/327943
[02:35] <micahg> hmmm
[02:35] <micahg> DustinAmodeo: maybe try one that's not a crash...
[02:39] <DustinAmodeo> looking at Bug #340032
[02:39] <ubot4`> Launchpad bug 340032 in firefox-3.0 "Jaunty: Firefox crashes while using plugin finder service" [Undecided,New] https://launchpad.net/bugs/340032
[02:40] <micahg> DustinAmodeo: ok, what do you think abotu this?
[02:42] <DustinAmodeo> micahg: from a straight triage perpective, it seems to have all of the initial relevant data
[02:44] <micahg> ok, but how old is the bug?
[02:44] <micahg> and what version was it reported against?
[02:45] <DustinAmodeo> ahh...over 6 months old and alpha 9.04
[02:46] <micahg> yep
[02:46] <micahg> so, now what do you think?
[02:48] <DustinAmodeo> that i would be unable to duplicate the bug, so a message should be sent to the bug reporter to confirm that it is no longer an issue?
[02:49] <micahg> yes, there should be a paragraph about obsolete versions on the responses page
[02:50] <DustinAmodeo> "
[02:50] <DustinAmodeo> Thank you for taking the time to report this bug and helping to make Ubuntu better. However, according to this report, you are not using the most recent version of this package for your Ubuntu release. Please upgrade to the most recent version and let us know if you are still having this issue. Thanks in advance. "
[02:50] <DustinAmodeo> so i'll just add that to the comments?
[02:51] <micahg> DustinAmodeo: normally pastebin is better for such things...but yes, and you might want to tweak it to say not using the release version of Jaunty
[02:52]  * micahg remembers pastebining lots of comments to be evaluated :)
[02:56] <DustinAmodeo> now i would also want to change the status of it?
[03:00] <micahg> yes DustinAmodeo
[03:00] <micahg> what do you think it should be?
[03:00] <DustinAmodeo> incomplete
[03:01] <micahg> yep[
[03:01] <micahg> and BTW, text looks great
[03:03] <DustinAmodeo> and this is where i go to the wait 4 weeks period? then a reminder, then 2 weeks later invalidate it?
[03:03] <micahg> yep
[03:03] <micahg> BTW, I suggest subscribing to the bug
[03:04] <DustinAmodeo> right. i was just about to ask if i had to note it and manually go back to it
[03:05] <micahg> if you click the down arrow next to the task, you can do it all at once (set status, respond, subscribe)
[03:05] <test34> Can someone look at https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/434121 and tell me if it should really be invalid? because I think it is very confusing that this checkbox ("Use message indicators") shows the icon in the notification area.  And also, it probably should be enabled by default
[03:05] <ubot4`> Launchpad bug 434121 in empathy "no notification area for new empathy update" [Undecided,Invalid]
[03:05] <DustinAmodeo> oh cool
[03:07] <micahg> test34: yes, it seems more like a support request than a bug
[03:09] <test34> ok then thanks micahg
[03:11] <DustinAmodeo> so for now i'm done with this bug?
[03:11] <micahg> yep
[03:12] <DustinAmodeo> thanks
[03:15] <micahg> DustinAmodeo: you want to grab another?
[03:16] <DustinAmodeo> absolutely
[03:17] <DustinAmodeo> is it beneficial for me to go through these ones that were created with alpha jaunty?
[03:21] <DustinAmodeo> i'm looking at Bug #425764
[03:21] <ubot4`> Launchpad bug 425764 in firefox-3.0 "Tools-->Downloads-->"Open in containing folder" opens the file itself and not the folder!" [Undecided,New] https://launchpad.net/bugs/425764
[03:21] <micahg> DustinAmodeo: if there are a lot of them
[03:22] <micahg> DustinAmodeo: can you duplicate it?
[03:22] <DustinAmodeo> and i've already attempted to duplicate the problem with 3.0.14
[03:22] <DustinAmodeo> and thje program is running as expected
[03:22] <micahg> DustinAmodeo: you mean it opens the file manager?
[03:23] <DustinAmodeo> it does
[03:23] <micahg> DustinAmodeo: what flavor of Ubuntu
[03:23] <DustinAmodeo> 9.04
[03:24] <micahg> yes, but what desktop env?
[03:24] <DustinAmodeo> gnome
[03:24] <DustinAmodeo> sorry
[03:24] <micahg> KDE, Gnome, Xfce?
[03:24] <micahg> ah
[03:24] <micahg> ok
[03:24] <micahg> well
[03:24] <micahg> the reported is most likely using KDE
[03:24] <micahg> *reported
[03:24] <micahg> *reporter
[03:25] <DustinAmodeo> what leads you to make that inference? is KDE more commonly used?
[03:25] <micahg> no
[03:26] <micahg> the user references Dolphin which is the KDE4 file manager
[03:26] <DustinAmodeo> the nautilus equivalent?
[03:26] <DustinAmodeo> i see.
[03:26] <micahg> yes
[03:28] <DustinAmodeo> so then i would leave this bug alone for someone running KDE?
[03:28] <DustinAmodeo> or make a note saying that i couldn't duplicate it in Gnome with FF 3.0.14?
[03:29] <micahg> or you can try to find someone running KDE on Jaunty to duplicate it?
[03:30] <DustinAmodeo> the few friends i have running ubuntu are all in gnome
[03:31] <DustinAmodeo> if that's what you mean
[03:31] <micahg> DustinAmodeo: I think this is an upstream issue :)
[03:35] <micahg> mozilla bug 266600
[03:35] <ubot4`> Mozilla bug 266600 in Download Manager "Open containing folder function does nothing (KDE)" [Normal,New] http://bugzilla.mozilla.org/show_bug.cgi?id=266600
[03:37] <micahg> DustinAmodeo: take a look at the responses page for upstreaming issues
[03:38] <micahg> DustinAmodeo: actually hold on
[03:38] <micahg> just found the duplicate :)
[03:38] <micahg> bug 133133
[03:38] <ubot4`> Launchpad bug 133133 in firefox ""Open containing folder" is only working if nautilus is present" [Unknown,Confirmed] https://launchpad.net/bugs/133133
[03:39] <DustinAmodeo> nice :)
[03:42] <micahg> DustinAmodeo: you want to mark it?
[03:43] <DustinAmodeo> i just did
[03:43] <DustinAmodeo> confirm i did it right?
[03:44] <micahg> DustinAmodeo: looks good
[03:45] <DustinAmodeo> thanks for your help
[03:45] <DustinAmodeo> :)
[03:45] <DustinAmodeo> i have to get caught up on some work
[03:45] <DustinAmodeo> but clearly still need some more help
[03:45] <micahg> np, feel free to come back
[03:45] <DustinAmodeo> so i'll catch you in here another time and go through a few more
[03:45] <micahg> you did great!
[03:45] <DustinAmodeo> appreciate it
[03:45] <DustinAmodeo> :)
[03:45] <DustinAmodeo> have a good evening
[04:08] <micahg> bdmurray: hi, it seems like it's not processing the stats right...the list you posted shows I did many bugs yesterday (UTC based)
[04:08] <micahg> bdmurray: nevermind :( it wasn't UTC 00:00 when it was posted
[06:55] <alkisg> Hello, I reported a bug in 8.10, then it was triaged, and now (9.04) it's fixed. Can I mark it as "Fix released" even though I don't know exactly when it was fixed?
[06:55] <alkisg> https://bugs.launchpad.net/ubuntu/+source/ltsp/+bug/212802
[06:55] <ubot4`> Launchpad bug 212802 in ltsp "Server brightness popup window shown in clients" [Undecided,Incomplete]
[06:56] <micahg> alkisg: generally not
[06:56] <alkisg> micahg: invalid, then?
[06:56] <micahg> We generally mark the bug invalid if we do not know what fixed it
[06:56] <alkisg> It was the newer gnome-power-manager version :)
[06:56] <alkisg> OK, I'll mark it as invalid
[06:57] <alkisg> (gnome-power-manager was completely redesigned, but it would take a lot of testing to see in which version exactly it was fixed...)
[06:57] <alkisg> micahg: thsnk
[06:57] <alkisg> *thanks
[06:57] <micahg> np alkisg
[07:08] <dholbach> good morning
[07:34] <thekorn> hello bugsquad ;)
[09:21] <slacker_nl> hello to all
[09:21] <slacker_nl> https://bugs.launchpad.net/ubuntu/+source/guessnet/+bug/433677 << debian has just released a new version of guessnet, would that make karmic?
[09:21] <ubot4`> Launchpad bug 433677 in guessnet "Unknown pcap error" [Undecided,New]
[09:21] <micahg> slacker_nl: check in #ubuntu-motu
[09:21] <slacker_nl> micahg: will do
[12:28] <Luit> not sure where to file this bug: somehow my laptop shows a charge rate of +700W when connected to the charger...
[12:29] <Luit> is this a bug or just a misconfiguration?
[12:34] <Luit> (the discharge rate is 15W max, and charging is about twice as fast I guess, so it should be around 35W charge rate instead)
[12:35] <Luit> so the charge rate shows about 20x the real rate...
[12:37] <Luit> looks like it can' t even be 35W, considering the charger only rates 30W
[12:37] <Luit> so it shouldn' t be 718,4 W, that' s for sure
[13:34] <joaopinto> I have this funny bug of only getting sound from firefox+flash and nothing else, it seems to have happened after installing the flash player package
[13:34] <joaopinto> any tipos how to debug/report it ?
[15:56] <Personne> Hi
[15:56] <Personne> I encount a problem using Samba
[15:57] <Personne> I don't understand why, when I create a file, this one is 644 mode
[15:59] <Personne> I add this in my smb.conf : http://pastealacon.com/5919
[15:59] <Personne> (on the server)
[16:00] <Personne> On my Ubuntu, I use Autofs, with this command : administration -fstype=cifs,credentials=/etc/auto.partage.auth,iocharset=utf8,uid=1000,gid=100,file_mode=760,dir_mode=775,workgroup=BUREAU ://<IP_ADDRESS>/administration
[16:01] <Personne> And it always change the created file in 644 :(
[16:01] <Personne> I test on a Windows client, and a NuTyx client (another linux), it works.
[16:01] <Personne> So I consider it's a bug of smbfs package
[16:05] <hggdh> Personne: this channel is not a support channel, but a bug-work (triage, control) one. Please try #ubuntu, or (in your case) #ubuntu-fr
[16:07] <Personne> They don't have skills to respond on #ubuntu-fr  :'(
[16:07] <Personne> I read the bug page but I don't find how to give the report of this bug
[16:07] <Personne> He is similar to http://fixunix.com/samba/244438-samba-ubuntu-7-10-64-bit-server-cant-write-shares.html
[16:07] <hggdh> Ok
[16:08] <hggdh> Personne: what version of Ubuntu are you running?
[16:08] <Personne> I do not have a well spell english to explain my problem in english I think
[16:08] <Personne> jaunty
[16:08] <Personne> (i'm french, that's why I encount some problems speaking english)
[16:09] <hggdh> Personne: no problem (and yes, this is why I suggested -fr ;-))
[16:09] <Personne> What could I do ?
[16:09] <hggdh> Personne: it does sound like a bug. Are you up-to-date on Jaunty?
[16:10] <Personne> hum, a moment, I try a apt-get update && apt-get upgrade to tell you this ;)
[16:10] <hggdh> merci
[16:11] <Personne> Hum, it seems that i'm not utd (up to date), but that's the package which I have to load : apport apport-gtk linux-headers-2.6.28-15 linux-headers-2.6.28-15-generic linux-image-2.6.28-15-generic linux-libc-dev python-apport python-problem-report
[16:11] <Personne> I think it's not "important"
[16:12] <Personne> I search with rgrep in some files (which contains the word "samba"), and it reveals something like usershare_acl variable
[16:13] <Personne> I think that the compilation change this variable to 644
[16:13] <hggdh> Personne: open a bug on this: run, on a terminal, 'ubuntu-bug smbfs'
[16:13] <hggdh> and point to your findings
[16:14] <CarlFK> I can't figure out how to report a bug...
[16:14] <Personne> hggdh: in a console I can explain my problem with annoting something ?
[16:14] <Personne> hggdh: I try this with the alt+f2 shortcut
[16:14] <CarlFK> https://edge.launchpad.net/ubuntu  click 'Report a bug" takes me to https://help.ubuntu.com/community/ReportingBugs
[16:15] <hggdh> Personne: 'ubuntu-bug' will collect the necessary data for the smbfs package, and open a browser on LP.net for you to enter more details
[16:15] <CarlFK> "you can file one via Launchpad." which takes me back to https://edge.launchpad.net/ubuntu
[16:15] <Personne> CarlFK: It's seems that I just have read it :D
[16:15] <Personne> CarlFK: but I'm not so "good" in english ;)
[16:15] <hggdh> CarlFK: hum. This loop is not good :-(
[16:17] <CarlFK> Personne:  I was not directing that to you. your english is pretty good
[16:18] <hggdh> CarlFK: I just tried it, and I cannot repeat: when I click on 'report a bug', I am taken to the +filebug page
[16:18] <hggdh> this is on Edge
[16:18] <Personne> Oh really ? oÔ
[16:18] <hggdh> Personne: this is only on edge.launchpad.net, which you may (or may not) have access
[16:20] <CarlFK> hggdh: are you hitting:
Get Involved

       Report a bug
[16:20] <greg-g> html doesn't really work in IRC :)
[16:20] <Personne> I always comme on https://help.ubuntu.com/community/ReportingBugs
[16:20] <Personne> when I click on "report a bug" -__-
[16:21] <hggdh> Personne: yes, this is why I asked you to run 'ubuntu-bug'
[16:21] <Personne> "If you need help in finding the right package or providing appropriate information ask someone on #ubuntu-bugs on the Freenode IRC server or on the bugsquad mailing list. "
[16:21] <Personne> hggdh: ok I try in a console
[16:22] <hggdh> CarlFK: I will have to look at the source, but yes, I clicked on 'report a bug' under the "Get Involved" header
[16:23] <Personne> "644 permissions on fresh file creating" <= is that a good summary ?
[16:24] <greg-g> Personne: yes. It can be changed later if needed.
[16:25] <Personne> ok.
[16:26] <Personne> Oh, some others bugs look like the mine :)
[16:26] <Personne> (I really have some problems understanding launchpad and the english language :s)
[16:26] <CarlFK> @#$@  something funky going on.  https://bugs.edge.launchpad.net/ubuntu/+source/nautilus/+bug/439419  click "Report another bug about nautilus in ubuntu" https://bugs.edge.launchpad.net/ubuntu/+source/nautilus/+filebug
[16:26] <ubot4`> Launchpad bug 439419 in nautilus "E: /var/cache/apt/archives/linux-image-2.6.24-22-lpia_2.6.24-22.45netbook9_lpia.deb: files list file for package `libxcb-shape0' is missing final newline" [Undecided,New]
[16:27] <CarlFK> get redirected to https://help.ubuntu.com/community/ReportingBugs
[16:27] <CarlFK> is there some setting to tell firefox to tell me about redirects?
[16:28] <CarlFK> wget tells me I need to log in.. I am logged into lp... maybe I should turn off edge
[16:28] <hggdh> maybe a cache issue?
[16:34] <Personne> oh my bug seems to be here : https://bugs.launchpad.net/ubuntu/+source/samba/+bug/263228
[16:34] <ubot4`> Launchpad bug 263228 in samba "problems with file-permissions using linux-cifs-client" [Undecided,Invalid]
[16:35] <Personne> but the dev said they don't have the information for changing this
[16:35] <Personne> But what I see is that there was a bug : https://bugs.launchpad.net/ubuntu/+source/samba/+bug/332431 , changed by a patch creation : http://www.nabble.com/ACLs-under-Samba-3.3.0-td21753941.html
[16:35] <ubot4`> Launchpad bug 332431 in samba "9.04 Jaunty Samba 2:3.3.0-3ubuntu2: files (permissions set to a=rwx) can only be renamed by owner although their content can be changed by all" [High,Fix released]
[16:36] <Personne> And so, I think that the patch affect the permissions
[16:37] <CarlFK> hggdh:  (10:38:05 AM) Ursinha: CarlFK, yes, the ubuntu process to file a bug changed, so you have to append the no-redirect for it to go to lp
[16:37] <hggdh> CarlFK: I am sure I did not append no-redirect ;-)
[16:37] <CarlFK> maybe a cache issue?  :)
[16:51] <hggdh> CarlFK: no, it is membership in the bug(squad|control) groups
[18:22] <ebroder> I'm helping run a local event for the global jam on Saturday, and I'm expecting to have a lot of people with, at best, a knowledge of how to use Ubuntu but not much development background. Are there any docs on how to find bugs that would be good for them to work on?
[18:22] <ebroder> Or things for them to test, or whatever
[18:40] <trijntje> what should i do when i want to retract a bug-report?
[19:07] <yofel> :q
[19:08] <yofel> argh... wrong window -.-
[20:01] <sandberg> Anyone experienced X-crashed while upgrading from Jaunty to Karmic?
[20:01] <sandberg> Think X crashed while the fglrx package was upgraded... :(
[21:18] <joaopinto> hi
[21:18] <joaopinto> how do I link an LP bug to a bugzilla ?
[21:19] <BUGabundo> hey joaopinto
[21:19] <BUGabundo> joaopinto: click on affect project
[21:19] <BUGabundo> LP edge or production?
[21:19] <BUGabundo> UIs are diff
[21:20] <joaopinto> LP prod
[21:24] <BUGabundo> did you manage to find the button joaopinto?
[21:24] <joaopinto> yes, it's linked
[21:24] <joaopinto> now I need to check that someone of the -desktop team will pick it up
[21:26] <BUGabundo> seb128: are you here?
[21:26] <BUGabundo> can you look at joaopinto bug?
[21:26] <BUGabundo> joaopinto: or try #u-dekstop :)
[21:26] <joaopinto> done :P
[21:30] <BUGabundo> YAY


[12:55] <ohmega_> is there a maintainer or something like that for the dapper distribution?
[12:56] <bhale> there are only Stable Release Updates, done by anyone, and security updates by security team
[12:59] <ohmega_> hm. i reported a bug a long time ago that causes dapper to fail to boot randomly, but persistentently once it has failed, depending on the number of free inodes you happen to have on your root filesystem.
[01:01] <ohmega_> i think it's kind of weird that this never got fixed.
[01:04] <ohmega_> or isn't that considered serious enough? it seems like most people who run into it have to reinstall since they can't figure out what went wrong.
[01:06] <ohmega_> LP: 37528
[01:06] <bryce> ohmega_: I haven't seen the bug you've described, but I know in general there's a number of pretty serious bugs in various open source projects, that ubuntu suffers from.  Ubuntu fixes as many as they can with the manpower they have, but they try to keep tightly to the regular release schedule
[01:07] <bryce> I think the thinking is, rather than wait a long time to make a perfect release, to make a series of increasingly better releases on a reliable schedule
[01:07] <ohmega_> bryce: well, there is even a link to a patch in launchpad so this shouldn't be too tough.
[01:08] <Kmos> bug 37528
[01:08] <ubotu> Launchpad bug 37528 in klibc "Dapper: persistent boot failure - ext3 filesystem not detected" [Medium,Confirmed]  https://launchpad.net/bugs/37528
[01:08] <Mithrandir> looks easy enough to test.
[01:08] <Mithrandir> uh, fix
[01:08] <ohmega_> the fix is in edgy since it was fixed in upstream
[01:09] <jovans> hello it woud be nice when the ubuntu team prepare backport for Faisty thunderbird 2 i think Feisty's support is 18 Month. I don't want thunderbird-1.5-10ubuntu_1_"__$_% i want thunderbird 2
[01:09] <bryce> ohmega_: ok if it's a kernel thing, you should talk with BenC
[01:09] <Mithrandir> bryce: it's klibc.
[01:09] <ohmega_> it's klibc, not the kernel.
[01:10] <bryce> well the patch in that LP ticket is from kernel.org
[01:11] <ohmega_> the klibc repository is just on the same server
[01:11] <bryce> (I don't know who is in charge of klibc)
[01:11] <bryce> ok I'll shut up now.
[01:12] <Mithrandir> bryce: the kernel team, as of this cycle.
[01:13] <ohmega_> hm, isn't Dapper LTS, then there should be an LTS team or at least _someone_?
[01:13] <Mithrandir> ohmega_: no, there is not a single person dedicated to 6.06 maintenance.
[01:14] <mjg59> Mithrandir: Uh, I think that's a slightly unfortunate phrasing
[01:14] <mjg59> You make it sound like nobody carries out any LTS maintenance
[01:14] <Mithrandir> mjg59: true.  English is hard.
[01:14] <crimsun> s/not a/no one/
[01:14] <mjg59> ohmega_: LTS support is handled by the entire maintenance team, depending on who seems appropriate for a specific issue. There are no people who are dedicated to LTS support.
[01:15] <bhale> 'no single person' is pretty much what you meant
[01:15] <ohmega_> OK
[01:15] <Mithrandir> bhale: indeed.  I blame it being after 1 o'clock in the middle of the night.
[01:17] <ohmega_> So who should I talk to?
[01:22] <Mithrandir> I'll take a look at it tomorrow.
[01:22] <ohmega_> Nice :)
[01:22] <ohmega_> Thanks.
[06:10] <fabbione> morning guys
[06:11] <gouki> Hi
[07:32] <pitti> Good morning
[08:30] <siretart> anyone using ndiswrapper around?
[08:37] <dholbach> good morning
[08:42] <Mithrandir> pitti: what do you think about getting bug 64695 fixed in an SRU?  It's a one-line change.
[08:42] <ubotu> Launchpad bug 64695 in kdebase "If GDM is the default display manager KDE logout dialog is missing shutdown and restart options" [Medium,Confirmed]  https://launchpad.net/bugs/64695
[08:44] <pitti> Mithrandir: hm, title doesn't sound particularly urgent to me; those options are in gdm/kdm as well, and sometimes people don't see the logout dialog at all; but if it's confusing many people, I'm ok with it
[08:44] <pitti> Mithrandir: I'd like to see a patch before, though
[08:45] <Mithrandir> it's a regression though, which is mainly why I think it's reasonable to get it fixed.
[08:45] <Mithrandir> just a moment, I'll boot my laptop
[08:47] <pitti> I agree to the regression part
[08:48] <Hobbsee> it's certainly annoying, it seems
[08:51] <Treenaks> Hobbsee: yes, you can
[08:51] <Hobbsee> ah, good
[08:52] <Treenaks> you can also reboot.. don't know about suspend
[08:53] <pitti> Treenaks: sure, you can do that as well
[08:54] <Treenaks> pitti: I just close my laptop lid for suspend ;)
[08:54] <pitti> so do I :)
[08:57] <Mithrandir> pitti: http://err.no/patches/kdebase_fix_gdm_socket_path.diff is a debdiff
[08:57] <pitti> Mithrandir: aah, it's *that* change
[08:58] <pitti> Mithrandir: yes, I'm all for fixing that, since it also looks like a (very  small) DoS
[08:58] <pitti> and we did it for a bunch of other programs
[08:59] <pitti> Mithrandir: please mention the SRU bug # in the changelog, though
[09:00] <Mithrandir> pitti: sure, I just wanted to run it past you first.
[09:00] <pitti> Mithrandir: and a short explanation of the impact in the changelog would be nice, since it's read by many users
[09:01] <pitti> Mithrandir: thanks for prep'ing
[09:13] <Mithrandir> pitti: should I just upload it or do you want to see the debdiff before?
[09:13] <Mithrandir> Riddell: ^^ ; you should make sure to fix this in gutsy too.
[09:14] <pitti> Mithrandir: if you just beautified the changelog, just go ahead and upload it
[09:20] <Mithrandir> pitti: ok, uploaded.
[09:38] <mario> siretart, poke?
[09:39] <siretart> hi pygi
[09:39] <pygi> siretart, I have three debdiffs for main, needed in feisty-updates and gutsy probably
[09:39] <pygi> possible? :)
[09:39] <pitti> Mithrandir: btw, the patch that you attached to bug 64695 is not at all about kde ;)
[09:39] <ubotu> Launchpad bug 64695 in kdebase "If GDM is the default display manager KDE logout dialog is missing shutdown and restart options" [Medium,Confirmed]  https://launchpad.net/bugs/64695
[09:39] <siretart> depends. your bug nos?
[09:40] <pygi> siretart, gksu, libgksu, and software-properties
[09:40] <pygi> ah, numbers!
[09:40] <pygi> sec :)
[09:40] <siretart> yes :)
[09:40] <Mithrandir> pitti: indeed.   That's what I get for not paying attention
[09:40] <pygi> siretart, I'll have a couple more coming in today :)
[09:41] <pygi> bug #66518
[09:41] <ubotu> Launchpad bug 66518 in gksu "[Edgy + Feisty]  Startup Notification broken" [Medium,Confirmed]  https://launchpad.net/bugs/66518
[09:41] <pygi> bug #111137
[09:41] <ubotu> Launchpad bug 111137 in software-properties "Software properties has duplicate gksu" [Undecided,Confirmed]  https://launchpad.net/bugs/111137
[09:41] <pygi> siretart, those ^_^
[09:41] <Mithrandir> pitti: thanks, fixed.
[09:41] <siretart> pygi: I don't think I'm the best qualified person to sponsor gnome SRU uploads, perhaps seb128 or someone can help out?
[09:42] <pygi> siretart, sure, I'll bug him then :P
[09:42] <pygi> when he's around :)
[09:42] <pygi> siretart, what about brasero fixes that I'll have ready today?
[09:42] <siretart> I just want to be sure that gnome upstream is informed, maybe they'll handle them in a point release.
[09:42] <pygi> got it
[09:43] <siretart> pygi: your bugo to brasero?
[09:43] <pygi> bug #107499
[09:43] <ubotu> Launchpad bug 107499 in brasero "Brasero will not burn " [High,Confirmed]  https://launchpad.net/bugs/107499
[09:43] <pygi> one of them :)
[09:43] <pygi> that's universe tho
[09:43] <pygi> for now^_^
[09:44] <siretart> sure. please attach your debdiff. looks like brasero is looking for a not installed mkisofs, right?
[09:44] <siretart> oh, and we should fix it in gutsy first!
[09:44] <pygi> siretart, for gutsy, I'll have new packages ready today/tomorrow
[09:44] <pygi> (new release)
[09:45] <pygi> siretart, problem is that current brasero doesn't depend n-c-b, genisoimage, and wodim
[09:45] <pygi> siretart, sure, thanks. I'll attach my debdiff today
[09:46] <pygi> siretart, did you upload libburn 0.3.6 and libisofs 0.3.4 in gutsy? I'd need those for brasero
[09:47] <pygi> but oh well, I guess you should expect to see even more bug fixes over time :P
[09:47] <siretart> yes, libburn&libisofs is in my todo pipe for today
[09:47] <pygi> great, thanks
[09:48] <pygi> ergh, it was libisofs 0.2.4, not 0.3.4 o.O
[09:49] <siretart> ah, so only libburn is new, ok
[09:52] <pygi> nod ^_^
[09:53] <siretart> pygi: and you're going to stay with soname 4? ;)
[09:53] <pygi> siretart, ;)
[09:53] <pygi> siretart, as long as I don't break ABI, sure :P
[09:53] <siretart> great! :) - I'm going to rename the packages then, it will go through NEW therefore
[09:53] <pygi> siretart, great :)
[09:54] <pygi> siretart, now that I learned how to actually make it stay the same ... ^_^
[09:54] <siretart> pygi: what's up with libburn version 0.2-2. do we want to keep or replace it?
[09:54] <pygi> siretart, nah, 0.2 is three years old, not mine, and isn't working
[09:55] <siretart> ok, then let's break the world :)
[09:55] <pygi> siretart, you can remove every all the current libisofs, libburn and stuff we currently have in archives for gutsy
[09:55] <pygi> haha ^_^
[09:56] <pygi> ergh, for new brasero I need to pull a couple of patches from svn
[09:56] <pygi> that scsi lib is a bit unstable in the release :(
[09:59] <pygi> I'm afraid I gotta run soon, but I'll be sure to bug you later today
[10:01] <pygi> siretart, and please do tell seb I've got an idea how we can workaround that hal bug in n-c-b for gutsy until hal applies the patch in their BTS
[10:01] <siretart> pygi: I'd suggest you subscribe him to the relevant bugno
[10:02] <pygi> siretart, he is subscribed already, and he knows what I'm talking about ^_^
[10:02] <siretart> he'll see it then, I'm sure :)
[10:18] <siretart> pygi: libburn currently doesn't build on gutsy because of linux-headers b0rkage. will retry when its fixed. the packages themselves do build fine, I've just pushed my changes to launchpad
[10:18] <siretart> at least on debian/lenny
[10:50] <dholbach> pitti: I plan to upload a python-launchpad-bugs (source) to the archive soon - can you move that to main without a MIR? and maybe move bughelper to universe?
[10:51] <dholbach> (separate source package)
[10:51] <pitti> dholbach: of course; it's not new code after all
[10:52] <dholbach> a few changes are in there, but nothing earth shatterin
[10:52] <dholbach> g
[10:52] <dholbach> i'll let you know, when i uploaded it
[10:52] <dholbach> pitti: you rock
[11:23] <saispo> ho
[11:23] <saispo> s/ho/hi/
[11:23] <saispo> gutsy debootstrap will be backported to feisty ?
[11:23] <cjwatson_> saispo: yes; I tried to do it the other day but something's broken in Launchpad so it failed
[11:24] <saispo> ok, thanks cjwatson
[11:24] <saispo> it's for building gutsy iso :p
[11:24] <cjwatson> in the meantime it's utterly trivial to build the source from gutsy
[11:24] <cjwatson> and don't even bother building a gutsy CD image; you're wasting your time
[11:25] <Mithrandir> or just copy the feisty script to gutsy.
[11:25] <Mithrandir> cjwatson: failed as in, wasn't accepted or failed to build?
[11:25] <cjwatson> Mithrandir: wasn't accepted
[11:25] <Mithrandir> hm, maybe the pockets aren't open yet?
[11:25] <cjwatson> looks like there's some .changes parsing which breaks on the ~ in the version number
[11:25] <cjwatson> no, it's much weirder than that
[11:26] <cjwatson> 09:25:20 DEBUG   Rejected:
[11:26] <cjwatson> 09:25:20 DEBUG   Mismatch in sourcefulness. (arch) True != (files) False
[11:26] <cjwatson> 09:25:20 DEBUG   Mismatch in binaryfulness. (arch) False != (files) True
[11:26] <cjwatson> 09:25:20 DEBUG   Sourceful upload without a diff or native tar
[11:26] <cjwatson> 09:25:20 DEBUG   Unsupported custom section name 'admin'
[11:26] <cjwatson> 09:25:20 DEBUG   Unsupported custom section name 'admin'
[11:26] <cjwatson> 09:25:20 DEBUG   Unable to find the dsc file in the sourceful upload?
[11:26] <Mithrandir> ugh, ok.
[11:30] <cjwatson> ah, the custom upload format checks are wrong
[11:30] <cjwatson> it thinks that priority "-" in a .changes file must mean a custom upload, whereas actually it can be produced by a source package that doesn't have Priority in the first stanza of debian/control
[11:32] <dholbach> pitti: uploaded :)
[11:57] <cbx33> kbrooks: so...onto the config problem....hi all
[11:57] <cbx33> eek
[11:57] <cbx33> ignore
[11:57] <cbx33> dholback pointed me here after I asked a question ;)
[11:58] <cjwatson> https://bugs.launchpad.net/soyuz/+bug/111202 describes the problem preventing debootstrap backports, FWIW
[11:58] <ubotu> Launchpad bug 111202 in soyuz "custom upload test is broken and catches some source packages" [Undecided,Unconfirmed]
[11:58] <cbx33> my GSoC student mentioned it would be great if he and the other GSoC students could either blog on planetubuntu or have an ubuntu GSoC blog...so people could read about their progress
[11:58] <cbx33> is this a possibility?
[12:00] <cjwatson> cbx33: yes, that's been done before; any Ubuntu member can add to Planet Ubuntu
[12:00] <cjwatson> 'bzr checkout sftp://bazaar.launchpad.net/~planet-ubuntu/config/main/' and edit
[12:00] <cjwatson> ... and commit, obviously
[12:01] <cbx33> but some of these guys are not ubunutu members
[12:01] <cjwatson> they're not, but presumably the mentors are
[12:01] <cbx33> yes
[12:01] <cbx33> I am
[12:01] <cjwatson> well then
[12:01] <cjwatson> the mentor can add their student's feed and leave a comment in the file indicating that they're a GSoC student
[12:02] <cbx33> ahhh
[12:02] <cbx33> awesome
[12:02] <cbx33> is there a file for that?
[12:03] <Nafallo> cbx33: bzr branch :-)
[12:03] <cbx33> no no
[12:03] <cbx33> I meanthe comment
[12:04] <Nafallo> there is a bzrbranch for the config. just add a comment in there :-)
[12:08] <cjwatson> Nafallo: 'bzr checkout' is more convenient than 'bzr branch' here
[12:09] <cjwatson> (there's no point having a branch with a separate existence here; you want centralised revision control)
[12:09] <cjwatson> # Google Summer of Code student, mentored by kamion
[12:09] <cjwatson> [http://www.evalicious.com/blog/feed/]
[12:09] <cjwatson> name = Evan Dandrea
[12:09] <cjwatson> nick = evand
[12:09] <cbx33> ok
[12:09] <cbx33> thats cool
[12:10] <cjwatson> e.g. - though this is no longer true and Evan's a member in his own right, so I'll change that
[12:11] <Nafallo> cjwatson: ah. right. I meant launchpad has a bzr branch though... :-)
[12:11] <cjwatson> ah
[12:50] <Riddell> Mithrandir, seb128: is that gdm fix in kdm a change in gdm upstream so it should go in kdm upstream too?
[12:52] <seb128> Riddell: what gdm fix in kdm?
[12:52] <cjwatson> the gdm socket path
[12:52] <seb128> kdm uses the gdm socket?
[12:52] <seb128> no, it's a distro change
[12:53] <Mithrandir> no, but the kde logout dialogue does.
[12:53] <Riddell> seb128: apparantly so, see Mithrandir's fix here http://librarian.launchpad.net/7474982/kdebase_fix_gdm_socket_path.diff
[12:53] <seb128> upstream uses /tmp/.gdm_socket
[12:53] <Riddell> right, ksmserver then
[12:53] <Riddell> seb128: why the change in ubuntu?
[12:53] <seb128> because /tmp is not secure
[12:54] <seb128> /var/run is the right location for the socket
[12:54] <Riddell> ok, let me know if that changes upstream (or you change it again in ubuntu) :)
[12:54] <seb128> will do
[12:54] <seb128> I did try to update package using it
[12:54] <seb128> I didn't think that KDE was looking for the gdm socket though :/
[12:55] <Riddell> it's a newish feature, it didn't used to
[12:55] <seb128> ok
[12:56] <Riddell> Mithrandir: how come feisty-proposed unapproved packages don't appear at http://people.ubuntu.com/~ubuntu-archive/queue/feisty/unapproved/ ?
[12:56] <cjwatson> it's a different queue
[12:57] <cjwatson> Riddell: I can make that be published
[12:58] <ogra> gs-job.c:110: error: 'EINTR' undeclared (first use in this function)
[12:58] <ogra> grmbl
[12:58] <cjwatson> unfortunately it's a bit expensive to publish the lot - connecting to the LP queue is pretty slow
[12:59] <StevenK> ogra: Known.
[12:59] <cjwatson> ogra: I posted to ubuntu-devel explaining this
[12:59] <StevenK> ogra: Although the FTBFS logs are pretty amusing.
[12:59] <ogra> cjwatson, ah, ok i thougt that was only for the buildds ...
[01:00] <cjwatson> if you've upgraded to gutsy locally, you have the same problem
[01:00] <ogra> but indeed why should my pbuilder do better :)
[01:00] <Nafallo> ogra: you're working on that one? in that case, should I update DesktopTeam/TODO for you? :-)
[01:00] <cjwatson> the buildds are building the fixed linux-source-2.6.22 now
[01:00] <StevenK> cjwatson: Actually, I had a question about that. Did linux-source-2.6.22 1.5 actually fail to build due to the problem it is trying to fix?
[01:00] <ogra> Nafallo, whats that ?
[01:00] <cjwatson> StevenK: yes, but it's been worked around
[01:00] <Nafallo> ogra: https://wiki.ubuntu.com/DesktopTeam/TODO
[01:00] <Nafallo> :-)
[01:00] <cjwatson> StevenK: (manual downgrade of linux-libc-dev in the buildd chroot)
[01:01] <StevenK> cjwatson: Ahhh. Sneaky. :-)
[01:01] <cjwatson> we knew that was going to happen
[01:01] <ogra> Nafallo, hmm, was that announced somewhere ?
[01:01] <cjwatson> you hose the system compiler, you get to bootstrap :)
[01:02] <Nafallo> ogra: topic of -desktop atleast :-P
[01:02] <ogra> heh, well
[01:02] <Nafallo> ogra: that's where I found it :-)
[01:02] <StevenK> cjwatson: Yup. :-)
[01:02] <cjwatson> Riddell: http://people.ubuntu.com/~ubuntu-archive/queue/feisty-proposed/unapproved/ is there now
[01:02] <Nafallo> cjwatson: hi! care to sponsor new irssi? you were the last one on it :-)
[01:03] <Nafallo> http://home.nafallo.info/debdiffs/
[01:03] <Riddell> cjwatson: ooh, thanks
[01:03] <cjwatson> Nafallo: not especially :)
[01:03] <StevenK> Nafallo, cjwatson: I can do it, if you like.
[01:04] <Nafallo> StevenK: please :-)
[01:04] <ogra> seb128, any particular reason that gnome-power-manager is not on https://wiki.ubuntu.com/DesktopTeam/TODO ?
[01:04] <cjwatson> I have a load of performance reviews to do that I've been procrastinating - probably don't need more distractions ;)
[01:04] <seb128> ogra: the list is a copy of packages to which ones desktop-bugs is subscribed
[01:04] <ogra> ah, k
[01:05] <seb128> ogra: gnome-power-manager gets enough bug to justify having its own team ;)
[01:05] <seb128> especially than most bugs there are linux, acpi and other things not really desktopish
[01:05] <ogra> lol, yes
[01:05] <Nafallo> seb128: then we might want to remove ekiga? isn't that the voip-team now? :-)
[01:06] <seb128> Nafallo: yeah, that's the goal, there is a discussion running on the mailing list
[01:06] <Riddell> ogra: gnome-screensaver looks compiled according to launchpad
[01:06] <Nafallo> seb128: right. no answers on your mail yet :-)
[01:07] <ogra> Riddell, ??
[01:07] <seb128> Nafallo: which one?
[01:07] <ogra> Riddell, who built a new package ?
[01:07] <Riddell> ogra: I presume there's a new version somewhere though that I'm not seeing?
[01:07] <Riddell> ogra: nobody, it's just the version from feisty
[01:07] <ogra> should be 2.19.x
[01:07] <seb128> Nafallo: Ekiga mail sent on saturday
[01:07] <seb128> Nafallo: there is a voip team npw
[01:07] <seb128> now
[01:07] <Nafallo> seb128: "Call for Desktop Team contributors" :-)
[01:08] <Nafallo> seb128: seems to mention those teams in it :-)
[01:08] <seb128> Nafallo: there is a new Ekiga thread on desktop-list
[01:08] <vciaglia> hello *
[01:08] <seb128> anyway, lunch time
[01:08] <Nafallo> :-)
[01:08] <ogra> Riddell, thats an old version, i just built the package from the new upstream source on the weekend
[01:09] <Riddell> ogra: ok
[01:11] <StevenK> Nafallo: This has to wait for the new linux-libc-dev. If I uploaded it, it would get requeued, and I'd rather see it sucessfully build here first.
[01:11] <Nafallo> StevenK: oh. I built it before the b0rkage then... :-)
[01:11] <Nafallo> StevenK: or rather, aurora isn't updated ;-)
[01:12] <Nafallo> which is a GoodThing(tm) :-)
[01:12] <Amaranth> that reminds me
[01:12] <StevenK> Although the failure of "network.c:296: error: 'SO_REUSEADDR' undeclared (first use in this function)
[01:12] <StevenK> " does make me giggle.
[01:12] <Amaranth> since gnome-power-manager development is stalled will we have 2.18 or try to make the 2.19.x stuff work?
[01:13] <StevenK> Nafallo: Maybe imbrandon's mirror isn't updating?
[01:13] <StevenK> Nafallo: You mean you don't have a fast machine to build on sitting ~40cm to your right? :-P
[01:14] <Nafallo> StevenK: yes I do, but I'm to lazy to set up a pbuilder :-)
[01:14] <Nafallo> StevenK: I meant pbuilder-gutsy update isn't run for a while :-)
[01:21] <StevenK> Nafallo: I can throw you a base tarball and a set of scripts if you like. :-)
[01:22] <Nafallo> StevenK: hehe. I actually have everything needed to set it up, I'm just to lazy :-)
[01:22] <Nafallo> StevenK: and it would be i386 instead of amd64 and kind of pointless to do atm ;-)
[01:22] <Nafallo> StevenK: what I really need to do is to work some magic on the box :-)
[01:22] <StevenK> Nafallo: I can do both amd64 and i386.
[01:23] <Nafallo> StevenK: but you have amd64 as a base, right?
[01:23] <Nafallo> StevenK: my plan is to reinstall to amd64 and start playing with virtual instances :-)
[01:23] <StevenK> Nafallo: The base install on this machine is 64-bit, yes. I have a 32 bit chroot for mplayer.
[01:24] <lifeless> mmm, my new 64 bit machine is coming up well
[01:24] <lifeless> PITA migrating settings though
[01:24] <Nafallo> StevenK: fix it :-)
[01:25] <StevenK> I've been planning on.
[01:36] <mario> hi folks
[01:36] <pygi> seb128, around?
[01:39] <Nafallo> morning sabdfl
[01:40] <pygi> o Nafallo is around again :P
[01:40] <Nafallo> pygi: always here, never says anything :-)
[01:40] <Nafallo> ;-)
[01:42] <pygi> Nafallo, ^_^
[01:43] <Nafallo> morning Keybuk :-)
[01:43] <Keybuk> morniing
[01:43] <pygi> ha, Keybuk !
[01:47] <sabdfl> moin moin Nafallo
[01:47] <Nafallo> sabdfl: that a wiki ;-)
[01:47] <sabdfl> have a wiki wiki day!
[01:47] <Nafallo> hehe :-)
[01:47] <Keybuk> sabdfl: you're up early
[01:48] <seb128> pygi: sort of, why?
[01:49] <sabdfl> Keybuk: my laptop clock says it's 50 to 1 in the afternoon!
[01:49] <sabdfl> erk
[01:49] <sabdfl> 12:49 PM, that is
[01:49] <pygi> seb128, I need three uploads to main (for now, will have more)
[01:49] <Keybuk> "50 to 1", that sounds like a gameshow
[01:49] <Mithrandir> sabdfl: your laptop believes you are in the UK, then.  I have some things to discuss with you as wel
[01:53] <pygi> well*
[02:00] <sabdfl> wow, Ubuntu Weekly News is amazing this week
[02:03] <seb128> pygi: I'm around now, what do you want to discuss?
[02:03] <pygi> seb128, I have fixes for software-properties, libgksu, and gksu that I want in feisty. That's one.
[02:03] <seb128> please ping mvo about them
[02:04] <pygi> seb128, second, I've got an idea how can we temporarily workaround hal bug in n-c-b for gutsy until hal upstream fixes it
[02:04] <pygi> seb128, I will ^_^
[02:04] <seb128> or ping me on wednesday
[02:04] <pygi> nah, I'll bug mvo for that :)
[02:04] <seb128> I'm on holiday today and I don't want to spend the afternoon working ;)
[02:04] <pygi> ah! Ok, sorry then ^^
[02:04] <seb128> ah, cool
[02:04] <seb128> that's ok, I would not be on IRC otherwise ;)
[02:04] <pygi> the hal thingy can wait then ^_^
[02:05] <seb128> can't we get the hal patch used in gutsy?
[02:05] <pygi> seb128, we could, yes :)
[02:05] <seb128> something to discuss with pitti then
[02:05] <pygi> ok, ok :)
[02:05] <pygi> but I guess not today :)
[02:06] <pygi> I have a lot of patches targeting main ready, and a few more in preparation
[02:06] <seb128> just open bugs and attach them ;)
[02:06] <pygi> will see what I can do with gnomebaker in this cycle as well, since it's unmaintained
[02:06] <pygi> but I do have access to the upstream repository, so ...
 will see what I can do with gnomebaker in this cycle as well, since it's unmaintained
 but I do have access to the upstream repository, so ...
[02:11] <seb128> pygi: just take over it ;)
[02:11] <pygi> seb128, no point since brasero is actively developed and no time.
[02:12] <seb128> k, makes sense then
[02:12] <pygi> + the burning arena is bad since everybody wants everything, and nobody wants to contribute :P
[02:12] <saispo> hi all :)
[02:12] <pygi> but that's how everything is :)
[02:13] <seb128> lu saispo
[02:13] <pygi> seb128, we just need to make sure to iron some existing bugs. I hope the debian package can help there. texeira has a lot of patches in his package, perhaps I can roll them in and make a point release of GB.
[02:13] <pygi> need to mail him, he's trying to join ubuntu burning team
[02:13] <seb128> cool
[02:13] <pygi> seb128, o yes, I had another question :)
[02:13] <pygi> can we blacklist packages that we DON'T want imported from debian?
[02:13] <seb128> yes
[02:14] <pygi> great, who do I bug about that?
[02:14] <seb128> Mithrandir or cjwatson probably
[02:14] <pygi> ok, thanks
[02:14] <Mithrandir> pygi: sure, which one?
[02:14] <pygi> Mithrandir, brasero for now
[02:15] <pygi> Mithrandir, their packaging is very ugly, don't want them to ruin the work we did here
[02:15] <Mithrandir> blacklisted
[02:15] <pygi> thanks
[02:16] <pygi> I hope new brasero will fix a lot of bugs we have, it should at least
[02:18] <pygi> well, enough of bugging for now
[02:18] <pygi> thanks seb128 and Mithrandir
[02:19] <seb128> no problem ;)
[02:24] <cjwatson> dholbach: at-spi in gutsy as Maintainer: Maintainer: Ubuntu Accessibility Developers<EMAIL_ADDRESS>[02:24] <cjwatson> s/as/has/
[02:25] <doko> pitti: please promote the gfortran and gfortran-4.1 binaries to main
[02:25] <dholbach> cjwatson: thanks, will fix that
[02:25] <pitti> doko: ugh, fortran in main?
[02:26] <doko> pitti: gutsy goal, and you already did move gfortran-4.2 to main ;-p
[02:26] <dholbach> fixed
[02:26] <cjwatson> pitti: g77 has always been in main
[02:27] <ogra> we already have gutsy goals ?
[02:27] <cjwatson> pitti: this is just replacing that ...
[02:27] <cjwatson> ogra: for the toolchain, yes
[02:27] <ogra> ah, right
[02:27] <pitti> dholbach: alright, thanks; promoted
[02:31] <dholbach> pitti: thanks A LOT
[02:32] <Amaranth> doesn't gfortran break ABI?
[02:32] <dholbach> pitti: the API is still the same - I'll notifiy you if there are changes
[02:32] <pitti> dholbach: erk, sorry, that was supposed to go to doko
[02:32] <pitti> dholbach: I'll handle your's in a bit
[02:32] <dholbach> ah ok
[02:32] <dholbach> pitti: take your time
[03:03] <zyga> hello, has anyone noticed any regressions with regards to python2.5 and gettext under feisty with default language packs?
[03:03] <zyga> it seems tht lp patch breaks translation lookup as lp takes precedense over anything else
[03:04] <zyga> lp == langpack patch
[03:05] <Fujitsu> lp == launchpad, so best not to use that abbreviation in that context.
[03:06] <pygi> pitti, be prepared for hal bugging :P
[03:06] <zyga> ok
[03:06] <pitti> pygi: no problem; poke me about it, I'm slow ATM with keeping up to date in Malone
[03:07] <pygi> pitti, no worries, I have some patches that we'll need for now in gutsy
[03:08] <zyga> pitti: do you know who patched python2.5 to grok language packs?
[03:08] <pitti> zyga: not off-hand, can you please check the changelog?
[03:08] <zyga> oh, good idea!
[03:10] <zyga> doko did
[03:10] <zyga> and mvo wrote it initially
[03:10] <zyga> :-)
[03:19] <zyga> hmm, it's buggy all right, I can reproduce it now :)
[04:03] <pitti> dholbach: p-lp-bugs NEWed into main; it shouldn't need binary/NEW
[04:03] <Hobbsee> hiya pitti
[04:03] <siretart> pygi: do you happen to have some brasero 0.5.0 package for my to try?
[04:05] <Mithrandir> hiya Hobbsee
[04:06] <Hobbsee> hey Mithrandir!
[04:07] <Solarion> so, what do I need to do to figure out why gnome-panel is eating my RAM for breakfast?
[04:08] <Solarion> I'm capable of fixing and providing patch, but I want to find where that sucker is lurking, and I am not certain how to get a stack trace from it
[04:10] <Hobbsee> no idea, sorry.  seb128/dholbach should know, but arent here
[04:10] <Hobbsee> or some others
[04:11] <Solarion> I also can't get a crash report out of OOo 2.2; is there something I need to enable to get it?  It just pops a file recovery dialog
[04:13] <Solarion> if anyone knows, please msg me and I'll read it when I get back to the kb.
[04:13] <Solarion> like I said, I'll fix it if I can get some help to do so.
[04:14] <Solarion> and as a bonus, I'll be that much more able to help fix bugs in the future, so it's a win-win.
[04:15] <Solarion> Hobbsee: thanks for your response at least.  It's better than I've gotten for a while.  :(
[04:16] <cjwatson> doko: can you point Solarion in the right direction?
[04:19] <doko> Solarion: when do you see this crash?
[04:23] <sladen> wow, a Simira.
[04:23] <Hobbsee> yay, Simira!
[04:30] <dholbach> Solarion: I'd install the relevant -dbgsym packages (http://wiki.ubuntu.com/DebuggingProgramCrash) and use valgrind to find out what happens (http://wiki.ubuntu.com/Valgrind)
[04:30] <sbalneav> elmo: Quick question for you, does the Canonical asterisk server support video connections via ekiga?
[04:30] <dholbach> Solarion: also, can you try if it happens with a new user?
[04:31] <Hobbsee> heya dholbach
[04:31] <dholbach> hey Hobbsee
[04:33] <smithj> so the file(s) /usr/share/doc/splat/copyright - do you have some magic policy to put those there, or is it a manual process for every package?
[04:34] <Hobbsee> smithj: it's sourcedir/debian/copyright, for each sourcepackage, which is done manually for every source package.
[04:34] <Hobbsee> (it's installed automatically, yes)
[04:34] <smithj> so how do you keep it up to date if the license changes? just update manually?
[04:35] <Mithrandir> yes
[04:35] <smithj> i was kind of hoping there was some magic method already in existance to do it without manual munging :)
[04:35] <Hobbsee> nope
[04:35] <smithj> ok, thanks all
[04:37] <elmo> sbalneav: err, I don't know to be honest, AFAIK, no one's ever tried
[04:48] <pygi> siretart, brasero 0.5.0? hm?
[04:48] <pygi> why?
[04:50] <pygi> (sorry, was away
[04:50] <pygi> )
[04:52] <ogra> cjwatson, do you have the ubuntu-server-thin-client spec on LP somewhere ? i'd like to subscribe to it
[04:53] <ogra> (and i know a bunch of others that are intrested)
[04:53] <cjwatson> ogra: we haven't gone through and registered everything from the core schedule on LP yet
[04:53] <ogra> ok
[04:53] <cjwatson> though since you're listed as an attendee on that on the core schedule, we'll probably subscribe you in the process
[04:53] <pygi> siretart, I'll look around, perhaps I've got them somewhere
[04:53] <pygi> siretart, once you're back ,poke
[04:59] <siretart> pygi: oh, I just looked at the brasero page and noticed that 0.5.0 seems to be the current upstream version
[04:59] <siretart> pygi: I tought I could give braser a try with the new libburn
[04:59] <pygi> siretart, which page?
[04:59] <siretart> pygi: http://perso.orange.fr/bonfire/
[04:59] <pygi> I think you were looking at wrong page siretart ^_^
[04:59] <pygi> siretart, I'll have new packages ready with libburn & libisofs in two days
[04:59] <siretart> first google hit. what would have been the correct one?
[05:00] <pygi> siretart, he correct one?
[05:00] <pygi> ergh
[05:00] <pygi> sec
[05:00] <pygi> siretart, http://www.gnome.org/projects/brasero/
[05:00] <pygi> please allow me to package those, I think I'll need to include a couple of patches
[05:00] <pygi> + it's my job to do those anyway :P
[05:01] <pygi> well, not job, but heh
[05:01] <pygi> siretart, 0.5.90 supports newest libburn and libisofs
[05:06] <Enola_Gay> hi all
[05:07] <Enola_Gay> Is there any replacement for the xserver-xorg-core-dbg in Feisty?
[05:07] <Enola_Gay> Xserver seems to have no dbg packages anymore at least I find no one.
[05:09] <tkamppeter> pitti, ping
[05:10] <Enola_Gay> tkamppeter: Do you know if there is a replacement for xserver-xorg-core-dbg in Feisty? I ask because you seem to be the one of the modesetting bug report.
[05:11] <Enola_Gay> I would like to create a crash dump of X but the Debian Wiki entry doesn't work for Ubuntu.
[05:20] <siretart> pygi: superb!
[05:21] <siretart> pygi: do you manage these packages in bzr? if so, please push them to your team's branches
[05:21] <siretart> s/your/our/
[05:21] <pygi> siretart, I don't, but I could ^_^
[05:22] <pygi> I guess if that'll help us test bzr builddeb stuff, I could play around a bit with it
[05:25] <Enola_Gay> cu all
[05:26] <mrmonday> Hi there, Are there any developers who would be interested in doing an article on how ubuntu is developed for fullcirclemagazine?
[05:28] <siretart> pygi: ok, just ping me again if you have some working packages
[05:29] <pygi> siretart, ofcourse :)
[05:34] <mrmonday> no takers?
[05:37] <codingmaster> Hello Ubuntu Developers!
[05:37] <codingmaster> I am participating this year in the Summer of Code for Ubuntu.
[05:37] <codingmaster> I am working on the Ubuntu Firewall Configuration.
[05:37] <codingmaster> I hope you can help me by adding suggestions for a good project name, using this wiki:
[05:37] <codingmaster> https://wiki.ubuntu.com/UbuntuFirewallConfiguration/Name
[05:37] <codingmaster> Thanks in advance to all of you!!!
[05:38] <pygi> codingmaster, Indpap ^_^
[05:38] <pygi> codingmaster, and it's you again :)
[05:38] <codingmaster> hey :)
[05:39] <codingmaster> would be great to see some suggestions from you all in the wiki :)
[05:39] <tkamppeter> Enola_Gay: I don't know, I have reported the i810-modesetting bug. The problem was that the standard i810 driver needs a high effort of manual configuration to work with not so common resolutions, and the proposed solution was to use i810-modesetting (which works for me), but there was nothing in my problem which has to do with xserver-xorg-core-dbg. Later on people talked about crashes of i810-modesetting, but I have nothing to do wit
[05:39] <tkamppeter> h that.
[05:39] <Solarion> *sigh*  how does Network-Manager do authentication?
[05:39] <mjg59> With wpa_supplicant
[05:39] <pygi> Solarion, wpa_supplicant
[05:39] <Solarion> It seems to totally forget that the AP requires Dynamic WEP inbetween bouts
[05:39] <pygi> codingmaster, I just told you an idea :P
[05:39] <Solarion> which is a problem if there's low signal
[05:40] <Solarion> heya mjg
[05:40] <codingmaster> @pygi: I know
[05:40] <Solarion> who is in charge of determining what method to use then?
[05:41] <Solarion> does N-M tell wpa_supplicant to auth using method foo, credentials bar, or does wpa_supplicant remember these things and is failing to remember correctly?
[05:41] <mjg59> N-M tells it things
[05:41] <Solarion> between the two of 'em, someone is forgetting
[05:41] <mjg59> To the best of my knowledge, anyway. The interaction is complicated.
[05:41] <Solarion> (from googling, it sounds like the APs are misconfigured.  It's shocking, I know, but it's the way it is)
[05:41] <Solarion> where should I go to push this further?
[05:42] <Solarion> 'cause this annoys the heck outta me
[05:44] <pygi> submit a bug, but n-m is a bit ...
[05:44] <pygi> :-/
[05:44] <Solarion> there's already a bug, which needs some love
[05:44] <pygi> codingmaster, how's the coding going?
[05:44] <pygi> Solarion, sadly I don't wanna play with n-m bugs anymore ... I did it for dapper too much
[05:45] <pygi> hi jdong
[05:45] <Solarion> pygi: who else is doing it?
[05:46] <pygi> Solarion, dunno (I do actually, just not sure it's the right time for bugging right now ^_^)
[05:46] <Solarion> pygi: "right time for bugging" means what?
[05:46] <codingmaster> @pygi: hacking on python :) with gtk :)
[05:47] <pygi> Solarion, means vacation :p
[05:48] <Solarion> ah.  Well, queue it up then or something.  If I find a solution, I'll post a patch
[05:48] <Solarion> pygi: where would I look in the source for the decision-making portion of things?
[05:48] <pygi> Solarion, out of hand, no idea, sorry
[05:48] <pygi> it's a bit more complicated then that I'm afraid
[05:49] <Solarion> hervorragend
[05:49] <Solarion> is there a n-m channel?
[05:51] <pygi> Solarion, nop
[05:51] <Solarion> well, that sucks
[05:52] <pygi> there is mailing list for n-m tho
[05:52] <Solarion> I've got enough mailing lists in my life.  :(
[05:54] <Solarion> If I have to enter all of my craptastic auth information one more time, I'm gonna scream.
[05:54] <Solarion> I think it's now 10 or 15 times in half an hour
[05:56] <Solarion> is odd, because sometimes it seems to re-auth; sometimes it doens't.
[05:56] <pygi> well, I use personally created shell script
[05:56] <Solarion> 11/16
[05:56] <pygi> that seems to do the trick :P
[05:58] <Solarion> 12/17.  shell script that does what?
[06:00] <Solarion> 13/18.  shell script that does what?
[06:03] <sn0> mrmonday im not a developer but just incase you haven't got a reponse, this might not be the best place to ask , maybe post on the mailing list(s) to get it seen
[06:07] <mrmonday> sn0, I have had a response thanks
[06:07] <sn0> mrmonday no prob, would be nice to see an article :)
[06:11] <Solarion> so, what are the chances of getting 2.6.21 (dynticks) in feisty?
[06:11] <Solarion> or do I have to DIM (Do It Myself)
[06:12] <mrmonday> sn0, keep your eye on the fullcirclemagazine site,
[06:13] <sn0> already doo thx mrmonday :)
[06:21] <Solarion> I think it's 20/25.  :(
[06:22] <bddebian> Heya
[06:30] <keescook> pirast: 110066> thanks, I've approved the nominations (still working through a big back-log of stuff...)
[06:31] <jdong_> !omgjdong
[06:31] <pygi> :P
[06:31] <ubotu> jdong: You're going to hell.
[06:31] <jdong_> grr wrong channel
[07:32] <mquy> hello
[07:35] <mquy> can anyone tell me how to become an Ubuntu developer?
[07:35] <infinity> -> #ubuntu-motu
[07:35] <mquy> thanks
[07:36] <geser> infinity: any progress on the xmms2 build failure (bug #87077)?
[07:36] <ubotu> Launchpad bug 87077 in launchpad-buildd "The build of xmms2 fails because of HASH(0x82db558)="" in the environment" [Undecided,Unconfirmed]  https://launchpad.net/bugs/87077
[07:37] <infinity> geser: Haven't looked at it for a while, was far too concerned with releasing feisty and opening/bootstrapping gutsy, etc.
[07:58] <thomS> Are the yellow popup bubbles (e.g for NetworkManager applet) part of the GTK toolkit or something Ubuntu have added themselves?
[07:59] <geser> afaik it's done by libnotify1
[08:59] <mthaddon> Launchpad is going down in 15 mins for a code update. Estimated downtime is 10 mins or less.
[09:11] <pirast> keescook, great, thanks
[09:12] <jdong> hmm... why does ssh <command> cause remote command to hang when local ssh is killed?
[09:13] <jdong> I would expect / desire the remote command to be killed when connection is severed
[09:18] <shawarma> jdong: It'll probably die once it tries to write something to the client (SIGPIPE magic).
[09:18] <Kmos> bug 105859
[09:18] <ubotu> Launchpad bug 105859 in app-install-data-commercial "Opera 9.2 is out with many bug fixes" [Undecided,Confirmed]  https://launchpad.net/bugs/105859
[09:19] <jdong> shawarma: good idea!
[09:20] <shawarma> jdong: You could also pass '-t' to ssh. That makes it allocate a controlling terminal on the server in effect sending the ctrl-c (if that's how you kill it) down the line make it send SIGINT to the remote app rather than your local ssh client.
[09:21] <jdong> shawarma: yet another good idea :D
[09:22] <shawarma> jdong: Heh. It looks like it worked. :-)
[09:22] <jdong> lol don't get excited too fast :D
[09:23] <jdong> shawarma: the ssh -t flaw.. can't pipe from it...
[09:24] <jdong> but I think I have an idea why SIGPIPE isn't caught
[09:25] <jdong> AHAHAHA
[09:26] <jdong> yep... catching IOError too broadly is not a good idea
[09:51] <robertj_> are packages in commercial tracked in launchpad as well?
[09:51] <Kmos> robertj_: you need to set it to package: app-install-data-commercial
[09:56] <mario> anyone around willing to be bugged for a few secs?
[09:56] <robertj_> are vmware-server's deps messed up? it claims to depend on libssl .9.7 but .9.8 is what is in feisty
[09:57] <robertj_> also the kernel modules package doesn't seem to provide appropriately
[09:57] <mario> jdong, poke? :)
[09:58] <jdong> mario: sup?
[09:58] <mario> jdong, mind checking for me in brasero deps if it doesn't have wodim && genisofs or nautilus-cd-burner dependency?
[09:59] <jdong> which brasero?
[10:00] <mario> jdong, the one in feisty
[10:00] <jdong> libnautilus-burn4,
[10:00] <jdong> that's the only burning related dep I see
[10:01] <mario> jdong, oki, that means it's wrong :P
[10:01] <jdong> lol
[10:01] <mario> thanks, I thought I was hallucinating
[10:02] <agraveley> hi. so i'm getting the feeling something on my machine has a May1 backdoor programmed in ;-)
[10:03] <mario> agraveley, why? :)
[10:03] <mario> jdong, ^_^
[10:03] <agraveley> i'm getting "BUG: soft lockup detected on cpu#0!" on booting both latest 2.6.11 and older 2.6.10
[10:03] <mjg59> 2.6.11?  Known bug, fixed in later versions of the driver.
[10:04] <agraveley> err, sorry!  2.6.17-11.  both this kernel and the older 2.6.17-10 worked fine until this morning
[10:05] <mario> hehe :)
[10:05] <mario> any updates this morning?
[10:05] <agraveley> nope
[10:05] <mjg59> agraveley: It's the temperature calibration routine in the driver
[10:05] <agraveley> wouldn't explain the older kernel not working too
[10:05] <mjg59> So, yeah, it's plausible that weather changes will affect it
[10:05] <mjg59> Computers are great
[10:05] <agraveley> omfg, you're kidding! :-)
[10:06] <Kmos> agraveley: update to feisty =)
[10:06] <Kmos> *upgrade
[10:07] <agraveley> is there an easy way to get newer kernels without upgrading just yet?  we're very close to a software freeze.
[10:07] <mjg59> agraveley: My recollection is that the hardware may block for some time before calibrating fully. Older versions of the driver would spin while this was happening, and the kernel detects this as a hang
[10:08] <mjg59> If you leave your machine for long enough, it /might/ carry on booting anyway, though I'm not sure of that
[10:08] <agraveley> mjg59: it's san francisco!  every day is the same! so that doesn't seem likely ;)
[10:08] <mjg59> agraveley: Dude, it rained on me there last week. Don't tell me it's /always/ the same.
[10:08] <agraveley> oh interesting.  maybe i've always just happened to leave it alone long enough?
[10:08] <mjg59> As I said, environmental factors may affect it
[10:09] <mjg59> You'll probably need the initramfs-tools as well, but if those dependencies are satisfied you ought to be good
[10:10] <ogra> probably udev too
[10:10] <ogra> no ?
[10:17] <agraveley> sweet! feisty has tomboy 0.6.3.
[10:17] <bhale> hi, agraveley
[10:18] <agraveley> howdy :)
[11:11] <agraveley> hey.  okay, the kernel update fixed the boot halt problems, but wireless no longer works.  i'm seeing "Kill switch must be turned off for wireless networking to work.", but wireless is certainly turned ON in the bios (otherwise i didn't see the problem at all)
[11:12] <agraveley> this is on an IBM x60
[11:12] <agraveley> anyone have advice?
[11:13] <mjg59> agraveley: And the kill switch on the front of the laptop is switched on?
[11:13] <mjg59> agraveley: Oh!
[11:14] <agraveley> WHOA
[11:14] <mjg59> agraveley: Now that you mention that - the bug only manifests itself when the kill switch is on, as far as I remember
[11:14] <mjg59> agraveley: So what changed was probably that you flicked that switch accidently...
[11:14] <agraveley> wait wait wait
[11:14] <agraveley> WHO PUT A SWITCH THERE?!
[11:14] <mjg59> Alex loses
[11:15] <agraveley> hah.  this is comical.  rebooting again.
[11:26] <pochu> hey all! any archive admin can give back wxwidgets2.8? it failed to build because of that kernel issue.
[11:26] <pochu> https://beta.launchpad.net/ubuntu/+source/wxwidgets2.8/<IP_ADDRESS>-0ubuntu1
[11:32] <agraveley> moral of the story: know where all the poorly placed switches are on your laptop, bozo.
[11:33] <agraveley> thanks guys :-)
[11:55] <pygi> siretart, around?