[12:13] <seb128> somerville32: it didn't change a lot
[12:13] <somerville32> lol
[12:13] <seb128> somerville32: just click on the same label
[12:13] <somerville32> I had to create a product
[12:13] <seb128> and copy and URL where you use to pick a tracker and a number
[12:14] <seb128> you had to pick a product before too
[12:14] <somerville32> Yes
[12:14] <somerville32> and I had to create the product :)
[12:14] <seb128> it has always been that way
[12:14] <seb128> maybe you didn't face a package without product before
[12:14] <somerville32> I was talking with kiko
[12:14] <somerville32> You could just provide the link before
[12:16] <seb128> somerville32: are you sure?
[12:17] <somerville32> "kiko> well, ok, you could add a bug watch, but it was unlinked" <-- yup
[12:17] <somerville32> Anyhow, I got it to work :D
[12:21] <Ubugtu> New bug: #76394 in linux-source-2.6.20 (main) "Zoran driver himem usage causing system instability." [Medium,Confirmed]  http://launchpad.net/bugs/76394
[12:35] <Ubugtu> New bug: #76815 in gdm (main) "[FEISTY]  gdmsetup doesn't start from menu" [Undecided,Unconfirmed]  http://launchpad.net/bugs/76815
[12:56] <Ubugtu> New bug: #76817 in sound-juicer (main) "edgy Sound-Juicer ejects musik-cd " [Undecided,Unconfirmed]  http://launchpad.net/bugs/76817
[01:19] <Ubugtu> New bug: #76818 in drgeo (universe) "Crash when trying to create a line" [Undecided,Unconfirmed]  http://launchpad.net/bugs/76818
[01:19] <Ubugtu> New bug: #76819 in linux-source-2.6.17 (main) "Kernel error message" [Undecided,Unconfirmed]  http://launchpad.net/bugs/76819
[01:55] <Ubugtu> New bug: #76824 in svn-buildpackage (universe) "svn-buildpackage in feisty missing dependency libsvn-perl" [Undecided,Unconfirmed]  http://launchpad.net/bugs/76824
[02:28] <cge> For bugs like bug #76803, is there anything more I can do besides describing the problem and how to fix it? Writing a patch would seem silly for such a bug.
[02:28] <Ubugtu> Malone bug 76803 in powermanga "Powermanga not " [Undecided,Confirmed]  http://launchpad.net/bugs/76803
[02:29] <cge> And of course, besides getting the title set correctly...
[02:50] <bddebian> Boo
[02:50] <Hobbsee> bee!
[02:51] <bddebian> heh
[02:52] <Jucato> heya
[02:53] <Hobbsee> cge: you do need a patch to fix that.  a little one :P
[02:53] <Hobbsee> what's setgid?
[03:03] <cge> Hobbsee: chmod g+s - like setuid except for the group.
[03:04] <Hobbsee> ah
[03:04] <Hobbsee> write a patch for it
[03:04] <Hobbsee> well, a debdiff
[03:04] <cge> ok
[03:07] <cge> The original reporter reported the bug as being that users weren't part of the games group by default. I suppose I should explain my changes to him, and that Debian and Ubuntu are so concerned about the sanctity of high scores that security updates for escalations to the games group are made. :)
[03:20] <Ubugtu> New bug: #76827 in firefox (main) "I linked to a radio stream. Firefox crashed" [Undecided,Unconfirmed]  http://launchpad.net/bugs/76827
[03:55] <Ubugtu> New bug: #76828 in firefox (main) "automatic stack collection can be annoying, especially with firefox" [Undecided,Unconfirmed]  http://launchpad.net/bugs/76828
[03:57] <Admiral_Chicago> Bug #53312
[03:57] <Ubugtu> Malone bug 53312 in glibc "tan(double x) takes excessive amount of time when x is a multiple of pi/2, x != 0" [Undecided,Needs info]  http://launchpad.net/bugs/53312
[03:57] <Admiral_Chicago> what the heck should I do with that
[03:59] <Hobbsee> Admiral_Chicago: i'd forward that upstream
[03:59] <bddebian> Admiral_Chicago: Fix it! ;-P
[03:59] <Admiral_Chicago> Hobbsee, can do.
[04:00] <Admiral_Chicago> I don't even know what the heck he wants. Or what the .3 seconds are so valuable. Is he doing parallel computing or something?
[04:00] <Ubugtu> New bug: #76507 in gnome-screensaver (main) "GNOME screensaver will not engage after DPMS has shut off the monitor" [Undecided,Unconfirmed]  http://launchpad.net/bugs/76507
[04:05] <Ubugtu> New bug: #76829 in hardinfo (universe) "hardinfo crashed after install in ubuntu 6.10" [Undecided,Unconfirmed]  http://launchpad.net/bugs/76829
[04:09] <bddebian> Admiral_Chicago: I was just kidding you :-)
[04:10] <Admiral_Chicago> bddebian, when?
[04:10] <Admiral_Chicago> oh I saw
[04:10] <Admiral_Chicago> lol
[04:15] <Ubugtu> New bug: #76830 in gaim (main) "gaim segfault on startup" [Undecided,Unconfirmed]  http://launchpad.net/bugs/76830
[04:25] <Ubugtu> New bug: #76831 in usplash (main) "Usplash prevents/blocks TTY/Terminal Access" [Undecided,Unconfirmed]  http://launchpad.net/bugs/76831
[05:42] <Admiral_Chicago> that strange bug is sent upstream thanks to Red_Herring
[05:44] <Admiral_Chicago> ash211, looks like you're following me all over the amarok bugs..
[05:44] <Admiral_Chicago> well RJ and I
[05:44] <ash211> yeah, I noticed you guys were going back through the Amarok bugs
[05:44] <ash211> thanks for helping out
[05:45] <Admiral_Chicago> me and RJ have adopted the package
[05:45] <Admiral_Chicago> form this page https://wiki.ubuntu.com/BugSquad/AdoptPackage
[05:45] <Admiral_Chicago> hopefully we can knock out the rest tonight, maybe tomorrow morning. i'm dead tired after a long day
[05:45] <ash211> yeah that'd be great
[05:46] <ash211> I didn't have a subscription to that specific wiki page,
[05:46] <ash211> so I didn't know you guys had adopted it, I just saw a ton of comments flying by via email!
[05:46] <Admiral_Chicago> it was sent out to the BS list
[05:46] <Admiral_Chicago> lol, that must have been interesting
[05:46] <Admiral_Chicago> new comment, new comment, new comment
[05:46] <ash211> all of a sudden 20+ bugs are in my inbox!
[05:46] <Admiral_Chicago> you should have seen #ubuntu-chicago
[05:47] <ash211> what went on there?
[05:47] <Admiral_Chicago> we were just linking back and foward, tossing ideas around, arguing about the best method
[06:37] <Admiral_Chicago> sfllaw, just adopted amarok, and took care of it along with RJ
[06:37] <sfllaw> Yay!
[06:37] <sfllaw> Amarok is popular, so fixing bugs will make you quite so.
[06:38] <Admiral_Chicago> it was only like 60 something, took about an hour or so
[06:38] <Admiral_Chicago> ash211 ^^  was helping a bit at the end as well
[06:45] <Ubugtu> New bug: #76833 in firefox (main) "Firefox dependence bugs" [Undecided,Unconfirmed]  http://launchpad.net/bugs/76833
[07:30] <Ubugtu> New bug: #76836 in kdepim (main) "kmail cant send mail - missing smtp kio plugin" [Undecided,Unconfirmed]  http://launchpad.net/bugs/76836
[07:55] <Ubugtu> New bug: #69447 in xserver-xgl (universe) "Xgl crashing." [Undecided,Unconfirmed]  http://launchpad.net/bugs/69447
[09:05] <Ubugtu> New bug: #76840 in update-manager (main) "Could not calculate the upgrade" [Undecided,Unconfirmed]  http://launchpad.net/bugs/76840
[09:31] <dholbach> good morning
[09:36] <palski> morning
[09:40] <dholbach> hey palski
[10:30] <Ubugtu> New bug: #76845 in firefox (main) "Complex Indic scripts cannot be displayed correctly" [Undecided,Unconfirmed]  http://launchpad.net/bugs/76845
[10:35] <Ubugtu> New bug: #76846 in php5 (main) "cannot install PEAR modules (edgy, amd64)" [Undecided,Unconfirmed]  http://launchpad.net/bugs/76846
[10:40] <Ubugtu> New bug: #76847 in libcairo (main) "Please sync libcairo (main) from Debian experimental (main)." [Undecided,Confirmed]  http://launchpad.net/bugs/76847
[10:45] <Ubugtu> New bug: #76848 in gnumeric (main) "changing the worksheet ordering within a workbook causes a sudden crash (in x86_64)" [Undecided,Unconfirmed]  http://launchpad.net/bugs/76848
[10:55] <Ubugtu> New bug: #76849 in linux-source-2.6.15 (main) "very high iowait - 100%" [Undecided,Unconfirmed]  http://launchpad.net/bugs/76849
[11:10] <Ubugtu> New bug: #76850 in Ubuntu "alternate cd upgrade of 6.10 corrupted system" [Undecided,Unconfirmed]  http://launchpad.net/bugs/76850
[12:10] <Ubugtu> New bug: #71737 in Ubuntu "Headphone and Speakers are switched on Amilo Xi1526" [Undecided,Confirmed]  http://launchpad.net/bugs/71737
[01:56] <Ubugtu> New bug: #76860 in openoffice.org (main) "OpenOffice crashes when trying to save the attached document in .DOC format" [Undecided,Unconfirmed]  http://launchpad.net/bugs/76860
[02:07] <heiko> i've been googling for that a lot, but couldn't find anything about it: i've repeatedly verified on different devices that upgrading from dapper->edgy as well as edgy->feisty breaks wlan for me. is there already a bug report for that? would it make sense to create one?
[02:08] <heiko> and with breaking i mean: using commandline tools (iwconfig/dhcp/manual setting of ip), i can not get any ip traffic, even though iwconfig detects the access point correctly
[02:22] <jwendell> seb128, around?
[02:24] <jwendell> dholbach, around?
[02:31] <seb128> jwendell: pong
[02:31] <jwendell> seb128, i have a problem with libnotify package. I guess patch 03 is not being applied
[02:32] <jwendell> seb128, can you verify if i'm right, please?
[02:33] <seb128> jwendell:
[02:33] <seb128> $ ls libnotify-0.4.3/debian
[02:33] <seb128> changelog  control     copyright           libnotify-bin.install   libnotify-dev.install  notify-send.1  watch
[02:33] <seb128> compat     control.in  libnotify1.install  libnotify-bin.manpages  libnotify-doc.install  rules
[02:33] <seb128>
[02:33] <seb128> no patch
[02:34] <jwendell> seb128, edgy, 0.4.2
[02:34] <jwendell> seb128, 0.4.2-0ubuntu3
[02:35] <seb128> context is useful :p
[02:35] <seb128> ok, let me get that one
[02:36] <jwendell> seb128, i'm writing a patch to vino, using libnotify + gtkstatusicon, so, i get the error: libnotify-CRITICAL **: notify_notification_new_with_status_icon: assertion `status_icon == NULL' failed
[02:36] <seb128> jwendell: none of the patches is applied
[02:36] <seb128> there is no simple-patchsys.mk rule used
[02:36] <jwendell> seb128, is this a bug, right?
[02:36] <seb128> yep
[02:36] <seb128> and a fixed one
[02:36] <seb128> feisty package has no patch
[02:37] <seb128> slomo screwed
[02:37] <jwendell> :)
[02:37] <seb128> he added 3 patches to 0.4.2-0ubuntu3 and didn't change the rules file for it
[02:38] <seb128> anyway those are fixed to 0.4.3
[02:38] <seb128> and I'm not sure that's worth doing a SRU
[02:38] <seb128> hum
[02:38] <seb128> patches are trivial
[02:38] <seb128> one liner each
[02:39] <jwendell> seb128, this is a blocker bug, i cant' use libnotify + statusicon....
[02:39] <seb128> "blocker"
[02:39] <jwendell> seb128, i guess it should be fixed for edgy-update
[02:39] <seb128> exageration will not make it go faster
[02:39] <jwendell> haha
[02:39] <jwendell> :)
[02:40] <jwendell> seb128, can i install feisty package in my edgy box?
[02:40] <giskard> hello *
[02:40] <seb128> jwendell: no, but you can rebuild it on feisty
[02:40] <seb128> ups
[02:40] <seb128> rebuild the feisty version on edgy I mean
[02:41] <seb128> hi giskard
[02:41] <seb128> jwendell: I'll ping slomo for a SRU when he'll be around
[02:41] <jwendell> seb128, tell me how to fix, i'll do it on my machine, i need to do it ;)
[02:42] <seb128> jwendell: do you know how to build a package?
[02:42] <jwendell> seb128, yep
[02:42] <seb128> get the source package from feisty and build it on your edgy then
[02:42] <seb128> http://archive.ubuntu.com/ubuntu/pool/main/libn/libnotify/
[02:43] <jwendell> seb128, ok
[02:43] <jwendell> seb128, thanks
[02:43] <seb128> np
[02:45] <Ubugtu> New bug: #76866 in gstreamer "No way to get working video with Intel card & AIGLX desktop" [Unknown,Unknown]  http://launchpad.net/bugs/76866
[02:46] <jwendell> seb128, should i fill a bug against libnotify about this?
[02:46] <seb128> jwendell: would be a good idea, thank you
[02:49] <jwendell> seb128, it already exists :( bug 63335
[02:49] <Ubugtu> Malone bug 63335 in libnotify "patches in debian/patches are not applied" [Medium,Confirmed]  http://launchpad.net/bugs/63335
[02:49] <seb128> jwendell: ok
[02:49] <jwendell> seb128, last comment from slomo is about oct 15...
[02:50] <Ubugtu> New bug: #76868 in gimp (main) "Gimp crashes repeatedly, no obvious cause" [Undecided,Unconfirmed]  http://launchpad.net/bugs/76868
[02:51] <seb128> jwendell: marked fixed and backport task opened
[02:54] <jwendell> seb128, ok, thanks
[02:54] <seb128> np
[03:00] <Ubugtu> New bug: #76869 in nautilus (main) "Crashed on 'Properties' context menu for incomplete AVI file" [Undecided,Unconfirmed]  http://launchpad.net/bugs/76869
[03:02] <giskard> hi seb128 :)
[03:20] <Ubugtu> New bug: #76871 in firefox-themes-ubuntu (main) "[Feisty]  Themes not compatible with FF <IP_ADDRESS>" [Undecided,Unconfirmed]  http://launchpad.net/bugs/76871
[03:38] <bddebian> Boo
[04:11] <Ubugtu> New bug: #76875 in Ubuntu "7.04 FF : after "start" on cd: system does not boot" [Undecided,Unconfirmed]  http://launchpad.net/bugs/76875
[04:11] <Ubugtu> New bug: #76876 in Ubuntu "/dev/dsp busy, but no program using it" [Undecided,Unconfirmed]  http://launchpad.net/bugs/76876
[04:25] <Ubugtu> New bug: #76877 in gnome-screensaver "Crashes on unlocking" [Unknown,Unknown]  http://launchpad.net/bugs/76877
[04:35] <Ubugtu> New bug: #76878 in Ubuntu "Kernel changed from smp to single after automatic update" [Undecided,Unconfirmed]  http://launchpad.net/bugs/76878
[04:50] <Ubugtu> New bug: #76880 in Ubuntu "Video Corruption in Feisty Live Install" [Undecided,Unconfirmed]  http://launchpad.net/bugs/76880
[04:50] <Ubugtu> New bug: #76881 in Ubuntu "Can't read CTR while initializing i8042" [Undecided,Unconfirmed]  http://launchpad.net/bugs/76881
[04:50] <Ubugtu> New bug: #76882 in wput (universe) "[UNMETDEPS]  Failed deps, feisty" [Undecided,Unconfirmed]  http://launchpad.net/bugs/76882
[04:50] <Ubugtu> New bug: #76883 in Ubuntu "ubuntu-server: Cannot allocate resource region" [Undecided,Unconfirmed]  http://launchpad.net/bugs/76883
[05:20] <dholbach> 545 unconfirmed desktop-bugs left
[05:26] <gnomefreak> dholbach:  im showing >10000
[05:26] <dholbach> desktop-bugs
[05:26] <gnomefreak> oh ok
[06:10] <Ubugtu> New bug: #76885 in gnome-games (main) "glChess crashes on player switch" [Undecided,Unconfirmed]  http://launchpad.net/bugs/76885
[06:10] <Ubugtu> New bug: #76886 in ubuntu-docs (main) "Software Sources" [Undecided,Unconfirmed]  http://launchpad.net/bugs/76886
[06:25] <Ubugtu> New bug: #76887 in sword (universe) "[Sync Request]  Sync sword (1.5.9-2) from Debian unstable (main)" [Undecided,Unconfirmed]  http://launchpad.net/bugs/76887
[06:35] <Ubugtu> New bug: #76888 in firefox (main) "all occurences of firefox suddenly crashed without reason" [Undecided,Unconfirmed]  http://launchpad.net/bugs/76888
[06:45] <Ubugtu> New bug: #76891 in f-spot (main) "Export to PicasaWeb fails with error" [Undecided,Unconfirmed]  http://launchpad.net/bugs/76891
[06:45] <Ubugtu> New bug: #76894 in jokosher (universe) "trimming, moving, etc... don't really work" [Undecided,Unconfirmed]  http://launchpad.net/bugs/76894
[06:46] <Ubugtu> New bug: #76889 in Ubuntu "usplash hangs at the end of shutdown" [Undecided,Unconfirmed]  http://launchpad.net/bugs/76889
[06:50] <Ubugtu> New bug: #76895 in jokosher (universe) "is the stop button really useful?" [Undecided,Unconfirmed]  http://launchpad.net/bugs/76895
[07:35] <Ubugtu> New bug: #76898 in ubiquity (main) "problem with instalation on Fujitsu Siemens 7660" [Undecided,Unconfirmed]  http://launchpad.net/bugs/76898
[07:45] <Ubugtu> New bug: #76899 in libsdl1.2 (main) "libsdl1.2 based programs fail compile if using x11 extensions" [Undecided,Unconfirmed]  http://launchpad.net/bugs/76899
[08:00] <Ubugtu> New bug: #76901 in Ubuntu "right Alt key not recognized by default" [Undecided,Unconfirmed]  http://launchpad.net/bugs/76901
[08:00] <cypher1> ogra, ping
[08:10] <Ubugtu> New bug: #76902 in gdm (main) "Switch user crashes system." [Undecided,Unconfirmed]  http://launchpad.net/bugs/76902
[08:25] <Ubugtu> New bug: #76904 in linux-source-2.6.17 (main) "2.6.17-10.34 breaks usb, ethernet" [Undecided,Unconfirmed]  http://launchpad.net/bugs/76904
[08:30] <Ubugtu> New bug: #76905 in felt (universe) "Unmet build deps (feisty)" [Undecided,Unconfirmed]  http://launchpad.net/bugs/76905
[09:35] <Ubugtu> New bug: #76910 in Ubuntu "Booting sometimes takes too long" [Undecided,Unconfirmed]  http://launchpad.net/bugs/76910
[09:39] <dholbach> seb128: 478 unconfirmed desktop-bugs
[09:39] <seb128> waouh
[09:39] <seb128> impressive :)
[09:40] <dholbach> yeah, I'm quite happy
[09:41] <dholbach> i was able to reject some and reassign some
[09:42] <seb128> dholbach: I'm happy with my ~300 bugs unread too
[09:45] <jwendell> wow
[09:46] <dholbach> hey jjesse
[09:47] <jjesse> hello dholbach
[09:49] <dthacker> first time triager here.  I'm looking at 76092 and thinking there are many variables to investigate (software levels, hardware, etc)  Is there a  preferred way to go about asking the reporter to narrow down the cause?
[09:54] <gnomefreak> bug 76092
[09:54] <Ubugtu> Malone bug 76092 in dict-bouvier "sync: new debian version" [Undecided,Unconfirmed]  http://launchpad.net/bugs/76092
[09:54] <gnomefreak> dthacker: you dont triage sync requests
[09:55] <dthacker> hmmm, that's not the number....please hold....
[09:55] <dthacker> argh.  76902. sorry
[09:56] <gnomefreak> bug 76902
[09:56] <Ubugtu> Malone bug 76902 in gdm "Switch user crashes system." [Undecided,Unconfirmed]  http://launchpad.net/bugs/76902
[09:56] <gnomefreak> that one?
[09:56] <dthacker> yes
[09:57] <gnomefreak> dthacker: did you read this page? https://wiki.ubuntu.com/HelpingWithBugs?highlight=%28bugs%29
[09:57] <gnomefreak> also another handy page is https://wiki.ubuntu.com/Bugs/Responses
[09:58] <dthacker> yes, but apparently I missed something?
[09:58] <gnomefreak> dthacker: i would start asking for a backtrace of it
[09:58] <dthacker> I have not read the responses page.
[09:58] <dthacker> and will do that now
[09:59] <gnomefreak> dthacker: i think this is a duplicate bug report
[09:59] <gnomefreak> i thought i ran across another unlock screen and crash
[10:00] <gnomefreak> but lets get the crashreport first
[10:00] <gnomefreak> dthacker: you can also try to confirm it but following the steps he gives to reproduce it
[10:02] <dthacker> gnomefreak:  I'm not going to be able to precisely reproduce a dapper upgraded from breeze.  Would an attempt to reproduce from a stock Dapper install have any value?
[10:02] <gnomefreak> dthacker: whatever you have handy
[10:03] <gnomefreak> dthacker: i dont have a dapper gui set up my only dapper setup is server install but i can try it on edgy/feisty later
[10:03] <dthacker> gnomefreak: ok, I'll attempt to reproduce first, then ask for a backtrace
[10:04] <dholbach> merry christmas everybody
[10:04] <gnomefreak> still may need backtrace anyway unles syou can poinpoint exactly what happened. it would be nice if we knew if it was crashing gnome or crashing X
[10:04] <dholbach> and happy new year
[10:04] <gnomefreak> dholbach: merry christmas and happy new year to you too
[10:04] <dholbach> thanks gnomefreak!
[10:04] <gnomefreak> :)
[10:05] <gnomefreak> dholbach: is the uploader for this package (desktop package im guessing :)
[10:06] <dholbach> for which one?
[10:06] <dthacker> Hmmm, I won't have access to my gnome machine until tomorrow. I'll ask for a backtrace and then attempt to reproduce.
[10:06] <gnomefreak> bug 76902
[10:06] <Ubugtu> Malone bug 76902 in gdm "Switch user crashes system." [Undecided,Unconfirmed]  http://launchpad.net/bugs/76902
[10:06] <gnomefreak> i want to say its a screensaver issue
[10:07] <dholbach> weird
[10:07] <seb128> gnomefreak: "crashes system" is not likely a gdm bug, feel free to reassign it to the right place ;)
[10:08] <seb128> if xorg crash that's likely xorg fault
[10:08] <gnomefreak> since its only on locking makes me think its screensaver
[10:08] <marnanel> xorg shouldn't crash, whatever
[10:08] <gnomefreak> marnanel: in a perfect world no app should ever crash
[10:08] <marnanel> gnomefreak: well, obviously. what's your point?
[10:09] <gnomefreak> marnanel: xorg does crash at times but normally caused by another app
[10:09] <marnanel> sorry, don't mean to sound confrontational.
[10:09] <marnanel> yes, but what I'm saying is that xorg crashing is a problem with xorg.
[10:09] <marnanel> It shouldn't be possible for another program to make a program crash. If it does, it's a problem with that other program.
[10:10] <marnanel> For example, if I can do something with Firefox that makes other people's Apache servers crash, that's not a bug in Firefox.
[10:10] <marnanel> That's a problem with Apache.
[10:10] <marnanel> sorry, "If it does, it's a problem with that program". I got that backwards.
[10:11] <marnanel> If xorg doesn't like what a program does, there are acceptable ways for it to signal so. Crashing is not one of them.
[10:14] <gnomefreak> back to playing with numbers :( everyone have a good holiday if im not back by the end
[10:14] <marnanel> you have a good holiday too
[10:16] <dthacker> ty for your help gnomefreak
[10:45] <Ubugtu> New bug: #76917 in Ubuntu "CTRL-ALT-F# keys bring up crazy looking screen" [Undecided,Unconfirmed]  http://launchpad.net/bugs/76917
[10:45] <Ubugtu> New bug: #76918 in gdm (main) "Feature request: GDM login box separation" [Undecided,Unconfirmed]  http://launchpad.net/bugs/76918
[10:55] <Ubugtu> New bug: #76919 in desktop-effects (universe) "volume osd displaced" [Undecided,Unconfirmed]  http://launchpad.net/bugs/76919
[11:30] <Ubugtu> New bug: #76921 in compiz "New windows displaced" [Undecided,Unconfirmed]  http://launchpad.net/bugs/76921
[11:43] <dthacker> Yay! reporter closed 55002


[03:48] <bjf> pgraner, nevermind, seems to have fixed itself
[08:19]  * apw waves
[08:20] <amitk> hey apw
[08:20] <apw> morning amitk hows it going?
[08:21] <amitk> fleshing out specs and pushing pending patches upstream
[08:21] <amitk> you?
[08:22]  * smb good mornings the channel
[08:24]  * amitk good mornings smb
[08:24] <smb> hi amitk
[08:24] <amitk> .. and adds "morning" to webster's dictionary as a verb
[08:26] <cooloney> apw and amitk smb, good morning guys, what's up
[08:26] <smb> cooloney, I am (more or less) :-P
[08:26] <apw> amitk, heheh
[08:27] <apw> smb, moin
[08:27] <apw> cooloney, just fighting aufs2 and the liveCDs
[08:27] <cooloney> smb: do we still have the kernel debug package?
[08:27] <smb> apw, still?
[08:27] <apw> smb, the fighting is now to ensure i've got and tested the right image
[08:27] <smb> cooloney, you mean on ddebs.ubuntu.com?
[08:27] <cooloney> so if we wanna to debug a module, we need a .ko with debug info, right?
[08:27] <apw> i think its fixed
[08:28] <apw> cooloney, symbols are often helpful
[08:28] <smb> The only problem might be I did not upload lately
[08:28] <amitk> apw: will union-mounts happen?
[08:28] <smb> They would be there with the next security update
[08:28] <apw> amitk, too soon to tell, i am waiting on testing of it
[08:28] <apw> smb, i think lucid is the only one missing isn't it?
[08:29] <apw> just due to luck
[08:29] <cooloney> smb: since our kernel package including the module which were --strip-debug, how's the debug kernel package?
[08:29] <smb> apw, Would need to check. I changed another one to the new format
[08:29] <smb> apw, Might have been karmic
[08:29] <smb> cooloney, Its packaged without strip
[08:29] <apw> smb, yeah but last i looked there was .31 ones there
[08:30] <smb> cooloney, http://ddebs.ubuntu.com/pool/main/l/linux/
[08:30] <cooloney> smb: yeah, so that's for debugging. but i never use that before. this question comes from TI guys
[08:30] <smb> cooloney, But if you need Lucid, it will take one or two more days
[08:31] <smb> cooloney, The package basically contains the unstrippeped modules and the full vmlinux
[08:31] <cooloney> smb: thanks a lot. cool, fully understand now
[08:31] <cooloney> smb: if someone wanna debug the modules, he can install this debug kernel package, right?
[08:32] <smb> cooloney, right, if they don't vanish again, which should not be the case, hopefully...
[08:32]  * amitk recovers from hours of reading the "suspend blocker api" thread on LKML
[08:33] <smb> An api to block suspend or one to find them?
[08:35] <amitk> smb: an api to block suspend after enabling "automatic aggressive suspend" (called opportunistic suspend by Google)
[08:35] <cooloney> apw: is there any way to build udebs from a source package?
[08:35] <cooloney> apw: i can use sbuild to get udebs. is there another way?
[08:36] <smb> cooloney, skip_dbg=false
[08:36] <cooloney> i tried 'fdr binary-arch', but no udebs.
[08:36] <cooloney> smb: skipdbg=false for udebs?
[08:36] <smb> err udebs
[08:36]  * smb clear his glasses
[08:36] <cooloney> smb: i think that is for debug package, right?
[08:36] <smb> cooloney, Yeah, forget what I said
[08:37] <smb> cooloney, I would not thinks so because you need the modules to be build to create packages with the modules referenced
[08:37] <apw> cooloney, ok udebs are currently only enabled if you have /CurrentlyBuilding
[08:38] <cooloney> apw: no idea what's /CurrentlyBuilding
[08:39] <cooloney> apw: a directory which i need to create manually?
[08:39] <smb> cooloney, Its a file
[08:39] <apw> its possible that if you build binary-arch binary-udebs it will do it
[08:39] <apw> but if you make /CurrentlyBuilding in the chroot, it will also build it
[08:40] <smb> cooloney, sudo touch /CurrentlyBuilding in your chroot
[08:40]  * cooloney finds using sbuild to native build my ti-omap4 source package is very fast in tyler.mills
[08:40]  * apw adds _documenting_ and cleaning up the controls for all releases to his TODO
[08:40] <cooloney> just 1 hr
[08:41] <apw> cooloney, that sounds acceptable to me
[08:42] <cooloney> smb and apw, yeah, does that work for cross compiling?
[08:42] <cooloney> 'fdr binary-arch binary-udebs' works for cross compiling?
[08:44] <apw> the problem is if linux-tools is enabled it does not work
[08:44] <apw> so yuo'll need do_tools=false at least to cross compile i think
[08:44] <cooloney> apw, ok, no problem, i will try that.
[09:09] <apw> cking, hey ... when filing bugs on iso testing, is there any special magic for that?
[09:09] <apw> ie. how do identify the bugs so they can be found
[09:13] <cking> apw, there is a field in the bug tracker as per test case to enter the bug number - this is all I do
[09:13] <apw> cking, ok thanks
[09:14] <cking> but there may be some tags that I don't know about
[09:15] <cking> All the notes say is: "Please report any bugs you identify in Launchpad and report on the success or failure of the test in the tracker: https://launchpad.net/ubuntu/"
[09:15] <cking> apw, you biting the QA bullet - cool!
[09:15] <apw> cking, dipping a toe in the pool
[09:16] <cking> see how many bugs you can find - I aim for 4 each spin - usually it ends up as stupid ones (e.g. broken eye candy)
[09:20] <ericm_> apw, I've added the link bjf mentioned in the reply to https://wiki.ubuntu.com/KernelTeam/MeetingHowTo for easier reference, hope that's OK
[09:21] <apw> ericm_, ok
[09:22]  * cking goes to get some H/W from the loft - back in 5
[09:50] <cooloney> apw: just a quick feedback, 'fdr binary-arch binary-udebs' works fine with cross compile
[09:50] <cooloney> it will give us all the udebs as well as kernel image and header packages in parent dir
[09:52] <dupondje> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/588643 => if somebody feels checking :)
[09:52] <ubot2> Launchpad bug 588643 in linux (Ubuntu) "Lockup with stacktrace (native_smp_send_reschedule) (affects: 1) (heat: 6)" [Undecided,New]
[09:59] <apw> cooloney, good
[11:42] <dupondje> Some small queryion, could bug https://bugs.launchpad.net/ubuntu/+source/linux/+bug/588643 be caused by an error in BIOS ?
[11:42] <ubot2> Launchpad bug 588643 in linux (Ubuntu) "Lockup with stacktrace (native_smp_send_reschedule) (affects: 1) (heat: 8)" [Undecided,New]
[11:55]  * apw returns
[11:56] <kraut> moin
[13:05] <ogra> hmm
[13:06] <ogra> looking at https://edge.launchpad.net/ubuntu/+source/linux/2.6.34-5.13/+build/1768097 we dont seem to build any omap udebs at all anymore
[13:13] <apw> ogra, it seems unlikely we ever did
[13:13] <ogra> we did with the topic branch in lucid
[13:14] <ogra> (and we need them for netinst images)
[13:14] <ogra> there seem to also be issues with the DSS code on a beagle XM
[13:14] <apw> ogra, yep but omap in maverick is a complete rebuild
[13:14] <ogra> i know
[13:14] <apw> ogra, its a shame noone ever tests things when they go in, only the day before the milest
[13:15] <ogra> i'm just examining the omap3 kernel now and note down issues i find :)
[13:15] <ogra> i dont test because A1 is due :)
[13:15] <ogra> we dont build A1 images for arm
[13:15] <ogra> its just coincidence :)
[13:16] <ogra> apw, btw, would there be a chance to not have the kernel produce an oops if it doesnt find its rootfs device and instead have it spit out a userfriendly error msg ?
[13:17] <ogra> http://paste.ubuntu.com/443294/ is what i typically get if there is no rootfs device
[13:17] <apw> ogra, i thought it dropped to busybox
[13:17] <ogra> not if you dont have an initramfs
[13:18] <ogra> see the bottom of the paste
[13:18] <apw> then its meant to tell you which things you have
[13:18] <ogra> i seem to remember (from my pre ubuntu times) that it properly panicked and gave a useful error
[13:18] <apw> ogra, given that shows the card appearing the instant before it explodes i suspect this is not cause it doesn't find root
[13:19] <ogra> i'm only using initramfs since ubuntu :)
[13:19] <apw> when my root is missing i see a panic which ends with a list of the filesystems and devices available
[13:19] <ogra> weird
[13:19] <ogra> i get the panic since i use arm
[13:19] <ogra> actually i got used to have it but thinking about it i remember it was not always that way
[13:20] <apw> from the panic i'd say that a timer is firing to flash the cursor, but the framebuffer didn't initialise
[13:20] <ogra> yes, there are definately other issues with that kernel on the XM board i'm justy trying
[13:20] <apw> [    2.365386] Waiting for root device /dev/mmcblk0p2...
[13:20] <apw> [    2.385223] mmc0: new SD card at address aff7
[13:20] <apw> [    2.390167] mmcblk0: mmc0:aff7 SU02G 1.89 GiB
[13:20] <apw> [    2.395141]  mmcblk0: p1 p2
[13:20] <ogra> but i see the oops across all arm arches
[13:21] <apw> from that you can even see that the disk was appearing, so its not at all clear its anything to do with root at all
[13:21] <ogra> i also saw it on imx51 before or on dove when experimenting with SDs without rootfs and initrd
[13:21] <apw> notice it dies here:
[13:21] <apw> [    2.490692] LR is at cursor_timer_handler+0x34/0x38
[13:21] <apw> that sounds very suspicious
[13:22] <ogra> hmm
[13:26]  * ogra unpacks a rootfs to the SD
[13:29] <apw> ogra, that callback seems to be the cursor flasher ... every half second
[13:30] <apw> i think there is a bug in the omap fb which is leaving the cursor running when it fails to init
[13:31] <ogra> yeah, you are right, i even get the oops with a valid rootfs in place
[13:31] <ogra> the DSS/frambuffer code is a mess on omap i guess we will need a bunch of patches from the linux-omap tree to make it work
[13:32]  * apw can't hear you :)
[13:32] <ogra> (it doesnt work at all on the touchbook or zoom2)
[13:32] <apw> i am somewhat intriqued who tested the image and what on, cause it was tested
[13:32] <ogra> and apparently also on the beagle XM
[13:32] <apw> i suspect just an official beagle is the only one supported
[13:32] <ogra> it likely works on one of the older beagles
[13:32] <ogra> XM is official
[13:33] <ogra> zoom2 is official too but will need patches
[13:33] <ogra> we agreed to support all these devices
[13:33] <apw> XM will be official at release, i am sure up to now we've not even had one
[13:33] <ogra> AI touchbook would be a nice to have since its an actual ARM netbook out there
[13:33] <ogra> apw, we have two in the company since about two months :)
[13:33] <apw> ogra, and who has them ?
[13:34] <apw> i bet noone who is doing the kernel work
[13:34] <ogra> amitk had one for kernel, not sure where it went
[13:34] <ogra> i have one as well
[13:34] <ogra> and i think there were even more
[13:34] <ogra> plars and jamiebennet used to have one each iirc but i'm not 100% sure
[13:35] <ogra> i am sure about the ones amitk and i have though
[13:35] <apw> shame that its eric doing the kernel work... ho hum
[13:35] <ogra> heh
[13:35] <ogra> erm, you mean bryan
[13:35] <apw> possibly, the disconnect is the same
[13:35] <ogra> he is doing omap4 atm
[13:36] <ogra> and he is doing it awesome :) without having HW at all i got a fully working kernel for my blaze board :)
[13:36] <apw> then i suspect noone is doing it
[13:36] <apw> ho hum
[13:36] <ogra> i know mpoirier and lag are supposed to do omap
[13:36] <ogra> under leadership of cooloney and amitk
[13:37] <ogra> but cooloney is busy with omap4 for the special 10.07 release
[13:39] <amitk> apw: ogra: The HW situation should improve soon(ish). We should probably revisit our HW allocations and get unused boards into hands of people that need them
[13:39] <ogra> yeah
[13:42] <dupondje> Now that there is some action here, could somebody tell me if http://dupondje.be/DSCF1025.JPG can be caused by a broken BIOS?
[13:46] <apw> dupondje, hard to say as thats not the first panic
[13:47] <cking> dupondje, if you could capture more of the first panic then we could say for certain - the trace before the apic timer interrupt would be handy
[13:48] <apw> dupondje, the panic you do have implies a CPU is offline when we are not expecting it to be so, if its repeating then we are truly confused
[13:48] <dupondje> I need full hd tv :P
[13:49] <dupondje> used mainline kernel, and there it gives 'BUG: cpu soft lockup' ... :s
[13:49] <dupondje> 2.6.34 as mainline kernel btw
[13:52] <apw> Keybuk, hey ... did you get to do any testing on the init args kernels ??
[13:53] <dupondje> to bad its not possible to scroll when the stacktrace is displayed
[14:00] <Keybuk> apw: not yet
[14:01] <Keybuk> apw: I will be doing that today
[14:11] <Keybuk> apw: while I can see items vanishing off my todo list, I feel like I'm not accomplishing much at the moment
[14:11] <Keybuk> too much catch-up
[14:17] <lag> http://webcache.googleusercontent.com/search?q=cache:EGSLAZNT6VwJ:www.pubbs.net/kernel/200907/83651/+"no+console+suspend"&cd=1&hl=en&ct=clnk&gl=uk
[14:17] <apw> kernel/printk.c:__setup("no_console_suspend", console_suspend_disable);
[14:18] <apw> Keybuk, i can only sympathise.  i had 5 items on mine, i've done 4 of them, but still have 6 to do for alpha-1 ... go figure
[14:32] <apw> Keybuk, do you  know if you need special mount support for union-mounts ?
[14:35] <Keybuk> yes
[14:36] <apw> Keybuk, damn, i'll go look for those then
[14:36] <Keybuk> I have that ready
[14:37] <apw> Keybuk, ahh, if you have something i can slurp up i'll get it into the PPA as well
[14:37] <apw> Keybuk, then i can go do some testing myself
[14:40] <apw> Keybuk, actually it looks to be only two patches if i am reading Valerie's page correctly ... match your expectations?
[14:44] <Keybuk> that would require me getting some time to actually sort the package out
[14:49] <lag> BOOT_IMAGE=<blar> root=<blar> ro console=tty1 no_console_suspend quiet splash
[14:50] <cking> lag,  it looks ok to me
[14:50] <cking> remove quiet and splash too
[14:52] <cking> mumble fail
[14:53] <lag> It sounded like you were on a CB radio and you were transmitting via a piece of string prior to dampening
[14:54] <cking> lag, my audio is screwy after a suspend/resume cycle - dunno why
[14:56] <cking> lag, console=tty is the normal default.
[14:56] <ogra> cking, talk to a kernel dev
[14:56] <ogra> :)
[14:56] <cking> "physician, heal thyself"
[15:00] <JFo> "Hoist by me own petard."
[15:02] <lag> JFo: Are you a fan of the great WS?
[15:03] <JFo> I am
[15:04] <lag> "Man does not live by bread alone"
[15:07] <bjf> moin yall
[15:07] <cking> hi bjf
[15:22] <JFo> moin bjf
[15:22] <JFo> from bug 571378
[15:22] <JFo> Jun 1 16:42:23 warthog libvirtd: 16:42:23.833: error : udevStrToLong_ui:73 : Failed to convert '008' to unsigned int#012
[15:22] <ubot2> Launchpad bug 571378 in linux (Ubuntu) "C-Media USB Headphone fails to enummerate (affects: 2) (heat: 10)" [Medium,Triaged] https://launchpad.net/bugs/571378
[15:22] <JFo> looks like some udev failure?
[15:23] <apw> JFo, well that has libvirtd in it as well
[15:23] <JFo> ah yes
[15:23] <apw> i'd tend to blame that first, and let them blame udev :)
[15:23] <JFo> heh
[15:24] <JFo> who owns that bit?
[15:24] <bjf> JFo, moin, since we have maverick daily isos now, i'll work on producing daily maverick test isos (shouldn't take more than a minute or two)
[15:24] <JFo> or rather those bits
[15:24] <JFo> bjf awesome
[15:30] <bjf> anyone know if emerald.pgraner is among the living?
[15:35]  * cking notes that suspend/resume on maverick alpha 1 is very speedy on his old dell 6400
[15:38] <Keybuk> apw: updating my laptop so I can install your test kernels
[15:39] <JFo> is the Lucid bacport kernel going to be based on .34 or .35? I was thinking the latter.
[15:39] <apw> Keybuk, i've run maverick kerenels on lucid no bother
[15:40] <Keybuk> apw: laptop is at a broken mid-maverick point ;)
[15:40] <Keybuk> updating to get it to boot again
[15:41] <apw> Keybuk, ooosp :)
[15:42] <apw> Keybuk, the 'text only' plymouth like screen (with four dots) is that part of plymouth as a package |?
[15:42] <Keybuk> plymouth-theme-ubuntu-text iirc
[15:46] <pgraner> bjf: I'm working on it
[15:46] <pgraner> bjf: had to bandage a cut finger
[15:47]  * ogasawara bails to dentist apt, back in an hour
[15:47] <tgardner> JFo, the LTS backport kernel is tracking Maverick
[15:48] <JFo> thought so
[15:49] <manjo> smb, https://wiki.ubuntu.com/Kernel/Tagging
[15:52] <jmfthevci> Hi all, anyone know the reasons behind the move of autoconf.h and utsrelease from the /usr/src/linux-headers-2.6.34-5-generic/include/linux directory?
[15:52] <cking> manjo, box is on it's way - probably get to you by Friday
[15:52] <jmfthevci> It caused VMware's tools script to die - vmware-config.pl
[15:52] <jmfthevci> Took a bit of digging but found this: https://blueprints.launchpad.net/ubuntu/+spec/kernel-maverick-misc
[15:53] <jmfthevci> Any comments?
[15:58] <sconklin> hi folks, I'm bck from the conference and should be in the normal swing again
[16:05] <JFo> woo hoo! welcome back sconklin
[16:06] <cking> lag: +CONFIG_USB_SERIAL=y
[16:06] <cking>  +CONFIG_USB_SERIAL_CONSOLE=y
[16:06] <cking> CONFIG_USB_SERIAL_CH341=y
[16:06] <cking> CONFIG_USB_SERIAL_PL2303=y
[16:07] <lag> I'm going to do it via the menu system
[16:07]  * lag is looking
[16:07] <cking> lag, I added them to debian.master/config/config.common.ubuntu
[16:10] <lag> cking: Why CH341? Surely you mean CONFIG_USB_SERIAL_FTDI_SIO?
[16:10] <cking> lag, you need to chose the appropriate driver ;-)
[16:11] <lag> I thought there were only two in the UK?
[16:11] <lag> FTDI and PLxxxx
[16:13] <cking> lag, well, what ever is appropriate - I've got CH341 and PL2303 for some reason
[16:13] <bjf> JFo, something is busted building the maverick test isos (was working fine for lucid), am debugging
[16:15] <JFo> k
[16:24] <manjo> cking, thanks for the box
[16:25] <cking> manjo, it requires a US power lead - it did not come with one
[16:25] <manjo> cking, I can get that
[16:25] <cking> and I formatted it up to boot Karmic, so you can see it will work ;-)
[16:26] <manjo> apw, you worked on some of the fan cntrl stuff, are we missing any modules for the sensors? (lucid/maverick) ?
[16:27] <manjo> apw, what sensor modules need to be loaded ?
[16:27] <manjo> apw, when I run pwmconfig it says at the end /usr/sbin/pwmconfig: No sensors found! (modprobe sensor modules?)
[16:29] <manjo> apw, sensors-detect tell me what modules .. never mind
[16:30] <apw> manjo, yep sensors-detect ... but even then sometimes there are none still
[16:37] <dupondje> JFo: thanks for commenting my bug, by the latest upsteam kernel ? you mean the latest daily build on kernel.ubuntu.com? Or compile a fresh one from kernel.org ?
[16:38] <JFo> dupondje, there is a MainlineKernels page on the wiki
[16:38] <JFo> we build them so you don't have to :)
[16:38]  * JFo goes to find the link
[16:38] <dupondje> well i'll try it when i'm home :)
[16:39] <manjo> tgardner, https://bugs.edge.launchpad.net/ubuntu/+source/linux/+bug/475641
[16:39] <ubot2> Launchpad bug 475641 in linux (Ubuntu) "pwmconfig does not work after upgrade to 9.10 on TYAN server (affects: 2) (heat: 12)" [Medium,Triaged]
[16:39] <dupondje> 2.6.34 gave 'BUG: soft lockup ...' :)
[16:39] <dupondje> didn't try 2.6.35 yet
[16:39] <JFo> hmmm
[16:40] <JFo> dupondje, here is the link to all the info: https://wiki.ubuntu.com/KernelTeam/MainlineBuilds?action=show&redirect=KernelMainlineBuilds
[16:40] <JFo> let me know how it goes :)
[16:41] <dupondje> i'll do, and take some 'screenshots' ;)
[16:45] <JFo> cool
[16:48] <dupondje> its not possible to scroll up right ? cause if the error is to long, can't see everything then :s
[16:54] <apw> dupondje, right no up scrolly
[16:55] <dupondje> gotto ask full hd tv then :)
[17:14] <lag> cking: Are you around?
[17:18] <cking> yep
[17:20] <lag> read 2675 modules : new(121)  missing(3)
[17:20] <lag> EE: Missing modules (start begging for mercy)
[17:20] <lag> make: *** [module-check-generic] Error 1
[17:21] <cking> lag, gimme 5 - I've got to sort out the gas men again
[17:21] <lag> k
[17:23] <cking> lag, build with skipmodule=true I believe
[17:29] <cking> lag, fakeroot debian/rules .... skipmodule=true
[17:32] <lag> cking: Trying
[17:32] <lag> :)
[17:33] <cking> yet another rune to remember
[17:33] <lag> :(
[17:34] <lag> I already skip the abi test
[17:34] <lag> Why doesn't it allow you to have any built-ins?
[17:35] <cking> eh? skipmodule=true should work
[17:37] <cking> see line 104 of debian/scripts/module-check - this is where it skips the missing modules check
[17:39] <lag> I mean, why doesn't it allow built-ins by default
[17:39] <jpds> Would anyone know why kdump wouldn't be working on a HP Z600 workstation?
[17:39] <jpds> Or how to go about debugging why it isn't working?
[17:39] <cking> lag, oh, I see. dunno
[17:52] <akgraner> bjf, are you around
[17:52] <bjf> akgraner, present
[17:53] <akgraner> can you take a look at the the Kernel Team Meetings listed on the Fridge and let me know if the series is correct
[17:53] <akgraner> if it is not can you let me know so I can get it fixed immediately :-)
[17:54] <bjf> akgraner, is it on the front page?
[17:55] <bjf> akgraner, give me a URL to what you want me to look at
[17:56]  * manjo needs food.. goes to look in the kitchen
[18:00] <akgraner> bjf, oh sorry let me get you the link
[18:00] <akgraner> bjf, http://fridge.ubuntu.com/calendar
[18:02] <bjf> akgraner, and from the calendar I do what? the calendar looks fine :-)
[18:02] <akgraner> bjf, nothing if all the times are correct
[18:03] <bjf> akgraner, 1700 UTC is the correct time, so that looks good to me
[18:03] <manjo> apw, smb is balcony open ?
[18:03] <smb> manjo, only if you have beer
[18:04] <akgraner> ok noted that Tuesday -1700 UTC is the time for all Kernel Team Meetings unless I am told otherwise - thanks!
[18:04] <bjf> akgraner, np
[18:04]  * bjf will brb
[18:41] <apw> mpoirier_, just to say i am still working on the omap udebs, its being truculant
[18:42] <mpoirier_> apw: truculant is definitely a new word for me :)
[18:42] <apw> and likely spelt wrong by me of course
[18:43] <mpoirier_> no, i just looked it up - it is correct.
[18:44] <apw> mad as it looks awful spelt that way
[18:44] <apw> anyhow its being truculant, but i think i've nearly got it licked
[18:45] <mpoirier_> fabulous.
[18:45] <mpoirier_> in the mean time sbuild worked for me.
[18:45] <mpoirier_> I can finally move on.
[18:45] <mpoirier_> thanks for the tips.
[18:46] <apw> mpoirier_, awsome
[18:46] <mpoirier_> it took a bloody long time, even on tyler.mills.
[18:47] <apw> Keybuk, hey ... how did your testing go ?
[18:47] <apw> mpoirier_, arround an hour ?
[18:47] <mpoirier_> is there a way to disable all the udebs except the one you are interesed  in ?
[18:47] <mpoirier_> no, more than that.  I'll 'time' it next time.
[18:48] <apw> if you are considering that to make things faster you won't gain anything, as the whole kernel being built is a pre-requisite to generate any udebs
[18:48] <apw> mpoirier_, once i have this lot fixed I should be able to cross compile only one flavour and generate udebs for it
[18:48] <apw> which for me here takes about 20 mins
[18:48] <mpoirier_> ok, it will be even faster on tyler.
[18:49] <mpoirier_> it's worth the wait.
[18:50] <apw> if i haven't killed it by then
[18:51] <Keybuk> apw: it hasn't happened yet
[18:52] <Keybuk> apw: your initargs kernel didn't build, so there's no deb to try
[18:53] <apw> Keybuk, crap will sort that out
[18:54] <Keybuk> did the "was used" patches end up in the maverick kernel?
[18:54] <apw> Keybuk, nope not yet
[18:54]  * apw adds to todo
[18:55] <Keybuk> k, if you want to go via ppa first, that's fine :)
[18:55] <apw> yeah sounds like a plan
[19:14] <JFo> kro, off to grab a bit of lunch
[19:14] <JFo> err ok
[19:31] <jjohansen-afk> -> lunch
[20:15] <apw> ogasawara, you abuot ?
[20:15] <ogasawara> apw: yep
[20:15] <apw> yo ... are you doing the -rc1 rebase 'next' ?
[20:15] <apw> as i am reminded it will need an aufs update before it will build right
[20:15] <ogasawara> apw: was just starting
[20:15] <apw> so as soon as you have the base rebase, perhaps you can push it somewhere i can get to it
[20:15] <ogasawara> apw: just squashing debian commits as we speak
[20:16] <ogasawara> apw: ack
[20:16] <apw> and i'll do the update for aufs in the morning on top
[20:16] <apw> wicked :)
[20:50] <JFo> ogasawara, bug 587444 looks interesting
[20:50] <ubot2> Launchpad bug 587444 in linux (Ubuntu) "Wrong dependency in linux-headers-2.6.34-x-generic (affects: 4) (heat: 20)" [High,Triaged] https://launchpad.net/bugs/587444
[20:50] <ogasawara> JFo: will take a look in a sec
[20:50] <JFo> kro, np
[20:50] <JFo> sigh*
[20:51] <ogasawara> JFo: ah, that seems one for tgardner as it's the maverick lts backports
[20:51] <JFo> ah right you are
[20:52] <tgardner> I can live with that
[20:52] <JFo> sorry to interrupt you :)
[20:52] <tgardner> JFo, wtf is that marked high? its not even a released package
[20:52] <JFo> heh
[20:53] <JFo> I apparently hit the wrong one
[20:53] <JFo> meant for medium
[20:53] <JFo> second time I have done that today
[20:53] <JFo> first one I caught as it happened
[20:53] <tgardner> JFo, nominate for Lucid and assign me so I don't forget
[20:54] <JFo> kro, will do
[20:54] <JFo> why does that keep happening
[20:54] <JFo> ah, it is tab completing
[20:55] <JFo> yep, automatic nick completion was checked
[20:55] <JFo> sorry about that kro
[20:58] <JFo> tgardner, done
[21:02] <JFo> cnd, looks like you could get a nice chunk of change to resolve bug 576601
[21:02] <ubot2> Launchpad bug 576601 in linux (Ubuntu) (and 1 other project) "[MacBookPro 7,1]mcp89 sata link reset fails, no disks detected (affects: 79) (heat: 462)" [High,Triaged] https://launchpad.net/bugs/576601
[21:02] <JFo> http://www.cofundos.org/project.php?id=187
[21:04] <cnd> JFo: heh, upstream looks like they're getting involved
[21:05] <JFo> cool
[21:09] <dupondje> JFo: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/588643 => was able to get a dmesg output when it got locked
[21:09] <ubot2> Launchpad bug 588643 in linux (Ubuntu) "Lockup with stacktrace (native_smp_send_reschedule) (affects: 1) (heat: 8)" [Undecided,Incomplete]
[21:09] <JFo> excellent!
[21:12] <dupondje> need to mark the bug as New again ? or you change status ? :)
[21:14] <smoser> hey all.
[21:14] <smoser> lets just pretend that i had a hardy xen domU running 2.6.24-24-xen
[21:14] <smoser> what would be the most reasonable way to get ext4 filesystem support for that pretend guest
[21:19] <JFo> dupondje, I have changed it
[21:20] <JFo> I was reading over the bug
[21:21] <dupondje> any idea what could be causing it ? could it be an instable BIOS version ?
[21:23] <tgardner> smoser, I don't think you can. ext4 did not exist for 2.6.24 IIRC
[21:23] <smoser> well, it does exist. its there.
[21:23] <smoser> at least ./Documentation/filesystems/ext4.txt
[21:23] <smoser> its just likely old and buggy
[21:24] <tgardner> smoser, its was probably a preview and marked EXPERIMENTAL
[21:24] <smoser> yes
[21:28] <dupondje> JFo: also notice the segfaults, seems like some apps segfault randomly also :s
[21:30] <JFo> dupondje, not sure what could be causing it. odd that some apps are segfaulting randomly
[21:31] <dupondje> its totally random also
[21:35] <dupondje> happens since I changed CPU and did BIOS upgrade ... but before it was a single core, now quad .. so
[21:37] <jjohansen> smoser: define support?  You could build the module externally, but no one will provide any kind of support for ext4 on 2.6.24
[21:37] <smoser> i need it to work.
[21:38] <smoser> i'm guessing reasonable ext4 support is not backported that far back.
[21:38] <smoser> the driver in 2.6.24 will probably compile and maybe even work.
[21:39] <smoser> right now our UEC images build system is running the aforementioned kernel version, and I want to build images with an ext4 filesystem, which requires mounting said filesystem.
[21:39] <jjohansen> I don't think reasonable ext4 support for 2.6.24 is viable
[21:39] <jjohansen> you should be able to compile the fs and have it mostly work
[21:39] <jjohansen> there will be bugs (ext4 still has bugs)
[21:40] <manjo> smoser, make sure you have latest bug fixes for ext4, lucid kernel is missing those too, Bug #588069
[21:40] <ubot2> Launchpad bug 588069 in linux (Ubuntu) "Lucid kernel is missing a large number of important ext4 bug fixes (affects: 4) (heat: 24)" [High,Triaged] https://launchpad.net/bugs/588069
[21:41] <jjohansen> manjo: I doubt those will even come close to applying to .24 era ext4
[21:42] <manjo> jjohansen, I assumed smoser was going to backport... never mind then
[21:45] <smoser> manjo, i was assuming you had volunteered to backport for me
[21:45]  * manjo ducks and hides
[21:47] <smoser> make sure that you get those latest patches :)
[21:47] <smoser> thanks all, i got somewhat what i expected.
[22:01] <kamal> mjg59: Hi -- A few weeks ago you proposed overriding the often-busted ACPI brightness control with an i915 opregion-based method -- I have implemented such a scheme -- are you available to talk about it?
[22:30] <stenten> Can someone help me finish triaging Bug #587136?
[22:30] <ubot2> Launchpad bug 587136 in linux (Ubuntu) "2nd Resume from Suspend results in reboot on Toshiba Satellite U400. Fixed in 2.6.34 Mainline. (affects: 2) (dups: 1) (heat: 22)" [High,Confirmed] https://launchpad.net/bugs/587136
[22:31] <stenten> Since it's a suspend/resume bug, there's absolutely no debugging information in the logs, and I'm at a loss of what else to ask for. What should the Status be in that case?
[22:31]  * JFo looks
[22:33] <mjg59> kamal: For a few minutes, sue
[22:33] <kamal> mjg59: For review:  http://kernel.ubuntu.com/~kamal/i915bri~3e/
[22:33] <kamal> It works very well on two out of three laptops I've tested, but on the third laptop the i915 method silently fails (its a "GM45" card -- pci-id 0x2a42 ... IS_I915G() and IS_GM45() are true).
[22:33] <kamal> Perhaps you might have a look at the patch and/or scratch your head about why it doesn't work on that GM45?
[22:33] <JFo> stenten, he is on server?
[22:33] <JFo> may not be easy to test, but the mainline kernel testing would be nice
[22:34] <JFo> if he is willing and this isn't production
[22:34] <JFo> other than that, it looks almost ready
[22:34] <stenten> He's on a Toshiba laptop.
[22:34] <kamal> mjg59: fyi, same patch in a git tree:  http://kernel.ubuntu.com/git?p=kamal/ubuntu-lucid.git;a=shortlog;h=refs/heads/i915bri-3e
[22:34] <JFo> hmm
[22:34] <stenten> And he's already tested with the 2.6.34 mainline, and the problem is resolved.
[22:35] <JFo> stenten, all that is left is proper tagging fos subsystem
[22:35] <JFo> have you seen https://wiki.ubuntu.com/Kernel/Tagging ?
[22:35] <JFo> for the subsystem tags?
[22:36] <stenten> We got all the way to the RTC overwrite part in debugging, but he has questions in Comment #10 that I'm really not qualified to answer.
[22:36] <JFo> cool
[22:37] <mjg59> kamal: Mm. Could be that the gm45 case is broken somehow.
[22:37] <JFo> stenten, so this one needs the kernel-power tag and the kernel-needs-review tag
[22:37] <mjg59> kamal: That's broadly what I was thinking though, sure
[22:37] <JFo> stenten, then it will be all set
[22:37] <stenten> JFo: Just saw that today (in your email actually). Tag it as 'kernel-power' and mark as Triaged?
[22:37] <JFo> yep
[22:37] <mjg59> kamal: I think it's worth posting this upstream, if only to try to find out if anyone's got a better idea
[22:38] <JFo> don't forget the kernel-needs-review tag
[22:38] <JFo> that way it gets on the radar from monday
[22:38] <JFo> stenten, ^
[22:38] <stenten> Is 'kernel-needs-review' the part that tells you it needs a dev to look at it?
[22:38] <JFo> well, it is the bit that gets it reviewed for inclusion on the 'hot list'
[22:38] <JFo> :)
[22:38] <kamal> mjg59: ok, if you consider it decent enough to sign off on it (or ack, or whatever), I'll post it upstream (with a note that its known to fail on this gm45.
[22:38] <stenten> Is there any difference between the meaning of 'kernel-needs'review' and marking it as triaged?
[22:39] <JFo> yep
[22:39] <mjg59> kamal: I think post it to linux-acpi and intel-gfx as an RFC for the moment
[22:39] <mjg59> And we'll bounce some ideas around
[22:39] <mjg59> But I suspect that this is probably how it's going to be
[22:39] <JFo> stenten, triaged simply means it has everything needed to go to a dev, not that it will necessarily get to one
[22:39] <JFo> given the amount of bugs we have that is
[22:39] <kamal> mjg59: ah, got it, ok, I'll do that -- thanks much!
[22:41] <JFo> stenten, are there any particular subsystems of the kernel that interest you?
[22:41] <JFo> sound, graphics, etc.?
[22:42] <stenten> JFo: Not particularly. I'm working in xserver-xorg-video-intel with Geir Ove Myhr, and we get a lot of suspend/resume bugs that end up being reassigned to the kernel, so I like to followup on them.
[22:42] <JFo> good deal
[22:45] <stenten> JFo: Do you mind changing the Status on that bug to Triaged? I'm only a lowly Bug Squad member :)
[22:46] <JFo> I don't mind at all :)
[22:46] <JFo> done
[22:46] <stenten> Thanks kindly.
[22:46] <JFo> my pleasure
[23:08] <kro> JFo: :-)
[23:08] <JFo> :-)
[23:08] <JFo> been using your name in vain all day
[23:10] <kro> hehe, I noticed


[22:04] <Rocket2DMn> lol mdke , you fixed a bug 5x over :)
[22:04] <ubot4> Rocket2DMn: Bug 5 on http://launchpad.net/bugs/5 is private
[22:04] <Rocket2DMn> ya da man!
[22:09] <mdke> Rocket2DMn: well, strictly speaking, I opened it 5 times by accident :p
[22:09] <mdke> but it has been fixed in all the version on help.u.c anyway
[22:12] <Rocket2DMn> i know mdke , im just pickin on you
[22:12] <mdke> I know you were just kidding
[22:12] <Rocket2DMn> while youre here, id like to run a question by you
[22:13] <Rocket2DMn> there are a ton of Mythbuntu pages on the community docs, which are basically all for unsupported versions i believe
[22:13] <Rocket2DMn> do you know if they keep their documentation on their own website know?  IIRC, that is what superm told me when i spoke to him last year
[22:14] <Rocket2DMn> errr, MythTV i mean
[22:15] <Rocket2DMn> same thing i believe
[22:15] <mdke> the mythbuntu website seems to point at http://help.ubuntu.com/community/MythTV
[22:15] <mdke> which is what you're talking about, so I guess the answer is that they don't have their own docs
[22:15] <mdke> they have an installation guide, but that seems to be about it from a quick review
[22:15] <mdke> but you'd have to contact them for more info
[22:16] <Rocket2DMn> alright, they organized pages in such a way that it is nearly impossible to track what page is referenced where b/c of a whole messy tree of Includes
[22:17] <Rocket2DMn> i'll contact Mario again sometime and see which pages he thinks we can get rid of.  I'd like to be able to just wipe out whole unsupported sections if possible, but he must know that area of the wiki better than anyone else
[22:18] <Rocket2DMn> I don't want to risk deleting used pages though
[22:18] <mdke> I think so
[22:18] <mdke> that area is a total mess, it is on our task list I believe
[22:18] <Rocket2DMn> yeah, it's been on my radar for the better part of a year
[22:19] <Rocket2DMn> alright, thanks for the feedback
[22:21] <mdke> sorry I couldn't help more
[22:26] <Rocket2DMn> not a problem


[03:14] <m00n_urn> Hey! My xubuntu machine keeps freezing every now and then (today alone: 4 times). I have to restart it everytime to get it to work again. I've lost all my xubuntu settings the last time I restarted due to it freezing. | Xubuntu 18.04 on a Thinkpad E450. Many applications were running during the freeze: A torrent client, XMPP client, FF, a few text files, a terminal. Do I have to provide any system logs to rectify this issue?
[03:57] <m00n_urn> Hey! My xubuntu machine keeps freezing every now and then (today alone: 4 times). I have to restart it everytime to get it to work again. I've lost all my xubuntu settings the last time I restarted due to it freezing. | Xubuntu 18.04 on a Thinkpad E450. Many applications were running during the freeze: A torrent client, XMPP client, FF, a few text files, a terminal. Do I have to provide any system logs to rectify this issue?
[03:59] <krytarik> m00n_urn: They literally only user who has entered the channel since you posted it last, is yourself btw.
[04:00] <m00n_urn> krytarik, wut?! :D
[04:07] <m00n_urn> krytarik, do you have any idea why this keeps occuring often?
[04:45] <kumool> mmm
[04:45] <kumool> clean your ram
[04:45] <kumool> or your entire PC
[04:46] <kumool> you can also erase xubuntu and install another OS
[04:46] <kumool> just in case
[05:03] <m00n_urn> kumool, No. I spent an awful lot of time customizing it. memtest to clean the RAM? How does one "clean" an OS?
[05:03] <kumool> ?
[05:03] <kumool> are you trolling?
[05:04] <kumool> you can try to memtest sure
[05:05] <kumool> shrink the hdd and dualboot another OS
[05:05] <kumool> if you don't want to erase anything
[05:07] <m00n_urn> lol, k
[06:39] <sarka> m00n_urn: I'd suspect your pc is overheating or your RAM is defective
[06:40] <sarka> so cleaning your pc, maybe taking the ram off and putting it in back again and if it still freezes try memtest
[06:41] <sarka> being thorough you would run memtest with only one ram stick in place at a time
[06:41] <m00n_urn> I'm kinda certain that it's the former. Overheating.
[06:41] <sarka> I had such problem once and it ended up being my GPU ram which was bad
[06:41] <m00n_urn> sarka, one ram stick at a time? one? I just dd memtest onto my thumdrive and run live.
[06:42] <sarka> yep
[06:42] <m00n_urn> Okay, but what about overheating. You got tips for that?
[06:43] <sarka> vacuuming your pc. if you have temp readings in bios, check them out right after freezing
[06:43] <sarka> if they're high-ish even after vacuuming, maybe check thermal paste
[06:44] <sarka> don't vacuum any motherboard components, obviously
[06:44] <m00n_urn> mine is a laptop and do bios even have that option?
[06:44] <sarka> hmm, maybe, maybe not. It's a lot more difficult to clean up though
[06:44] <m00n_urn> how do you check thermal paste? what is a thermal paste to begin with?
[06:44] <sarka> there's thermal paste between the cpu and it's heatsinkg
[06:45] <sarka> sometimes it dries up and doesn't perform well
[06:46] <sarka> maybe disassemble the laptop, vacuum/blow it and just clean old paste and put some new paste in straight away
[06:48] <m00n_urn> Oh, alright. thermald is already installed on my system and it didn't really make any difference
[11:07] <xubuntu28d> Good day! Support for older AMD GPUs has  been dropped on newer version of ubuntu? (eg. Juniper PRO - hd5750) of the free driver
[11:15] <xubuntu27d> was looking for a Screen Tearing fix - found it here https://tinyurl.com/jg8wrve
[14:19] <baldor> Hi !
[14:19] <baldor> I just noticed the keyboard shortcut "Ctrl + Maj + colon" wasn't detected by some apps any more since the upgrade
[14:19] <baldor> to 18.04
[14:20] <baldor> I use it in pycharm, and it doesn't detect it any more (and I can't reassign it)
[14:20] <baldor> any idea what prevents pycharm from detecting this shortcut?
[18:49] <ondondil> Hello
[18:50] <ondondil> Can anybody reproduce this bug? https://streamable.com/7t8kr
[18:50] <ondondil> It happens when you open new thunar window and right click a file that is near the bottom of the screen so that context menu is displayed further up from mouse pointer.
[18:50] <ondondil> Then the option that appears to be under the mouse pointer is executed automatically.
[18:50] <ondondil> It only happens once since thunar window is launched and to reproduce it you need to close the window and open new one.
[18:51] <ondondil> I noticed this first in Xubuntu 16.04 and now again in 18.04.
[18:51] <ondondil> It happens in VM too
[18:54] <Spass> ondondil, hello, I can confirm that on my Xubuntu 17.10
[18:55] <Spass> seems that we have the same bugs, plank blinking, Firefox 60 one, and now this...
[19:01] <ondondil> Oh, nevermind. I thought it was something new because there were no reports of it on launchpad but now I think I've found the exact same issue reported on xfce bugzilla
[19:01] <ondondil> https://bugzilla.xfce.org/show_bug.cgi?id=12476
[19:02] <ondondil> https://bugzilla.xfce.org/show_bug.cgi?id=13697
[19:03] <ondondil> sorry to have bothered you
[19:03] <Spass> well, I can at least add a comment that it also affects me
[19:08] <Spass> ondondil, what's the Thunar version on 18.04?
[19:09] <ondondil> 1.6.15
[19:12] <Spass> I added my "can confirm" comment on the Bugzilla, not that I think it would help, but it's better than nothing, I guess
[19:16] <ondondil> Oh, thanks for mentioning that it happens on 18.04 too. Now I don't need to create an account just for that specifically, I guess
[19:19] <Spass> I kind of lost my hopes for bug fixing after my "screen edge blinking" bug, now I have that "if something is broken - fix it yourself and don't expect someone to fix it for you" approach, and since I can't code I'll just sit quietly and I'll try to not complain too much ;)
[19:20] <Spass> all I can do to contribute is helping new users with (very) simple things, here and on forums
[20:52] <djtravz> Is anybody there?
[20:52] <djtravz> I’m kinda freaking out
[20:53] <krytarik> I see..
[20:59] <djtravz> My computer wasn’t connecting to my Ethernet so I tried resetting it. When doing so it reset instantaneously which is weird for my computer. I tried shutting down, but it just went right back on. I tried force restarting it with my reset button and it went off. When turning back on, it stayed at a black screen for a long time.  Now when I turned it on it is stuck at “kernel p
[20:59] <djtravz> “Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)”
[21:02] <djtravz> http://imgur.com/AoMlGTP
[21:04] <djtravz> Can anybody please help
[21:06] <djtravz> Booting into recovery mode does the same thing
[21:08] <krytarik> djtravz: The main #ubuntu channel might be a better place for this.


[00:59] <babbageclunk> wallyworld: Do we have a convenient way for taking multiple model operations and applying them as one transaction?
[00:59] <wallyworld> babbageclunk: yes, ModelOperation
[01:00] <babbageclunk> wallyworld: but if I have multiple ModelOperations is there a function to combine them into one?
[01:01] <babbageclunk> ie, I'm calling LeaveScopeOperation on n relation units, but I want to run them all as one transaction.
[01:02] <babbageclunk> Hmm, actually that might not be a good idea, since each one will change the unitcount and the last needs to remove the relation
[01:02] <babbageclunk> ok, I'll just run them as separate txns
[01:02] <wallyworld> yeah +1
[01:19] <wallyworld> kelvinliu: i don't understand the newPreconditionDeleteOptions stuff - why do we need to wait for UID sometimes and not others?
[01:20] <kelvinliu> wallyworld: that ensures it asserts the deleted resource has the that id
[01:20] <wallyworld> and name is not sufficient?
[01:21] <wallyworld> we seem to use both?
[01:21] <kelvinliu> ideally, we should follow this pattern for all deleting resources
[01:21] <wallyworld> given name is unique, why is that not sufficient?
[01:21] <kelvinliu> name is uniq, but the deletion is async
[01:23] <wallyworld> we can't create another one with the same name until the current one is totally gone, not just in terminating state though
[01:23] <kelvinliu> and it's not deleted immediately which usually takes a bit time
[01:23] <kelvinliu> but we can't prevent non-juju ppl or app create a resource with same name, right?
[01:24] <wallyworld> true, but while it's being terminated, we can't create another can we? you get an error from the api
[01:24] <kelvinliu> there was a discussion about this, i will find it for u
[01:24] <wallyworld> ok
[01:25] <wallyworld> if we need to change our code we should do it for everything rather than leave stuff done 2 different ways
[01:42] <kelvinliu> wallyworld: u can see i left a TODO for refactoring all updating/deleting places
[01:43] <wallyworld> ok
[01:43] <kelvinliu> wallyworld: i think this change is really good to have.
[01:43] <wallyworld> kelvinliu: is there a reason for swapping the order of update and create in the ensure() methods? we have been calling update() first then create()
[01:43] <kelvinliu> https://github.com/kubernetes/kubernetes/issues/20572
[01:44] <kelvinliu> yes, there is a reason, and i think we  should refactor all the ensure like this later as well
[01:44] <kelvinliu> wallyworld: HO to discuss?
[01:44] <wallyworld> sure
[01:48] <atdprhs> hello everyone, everytime I try to run juju add-unit kubernetes-worker i get `failed to start machine 28 (failed to acquire node: No available machine matches constraints: [('agent_name', ['93d500ee-7e14-4ece-81ae-69137d451f3a']), ('cpu_count', ['6']), ('mem', ['32768']), ('storage', ['root:1024']), ('zone', ['default'])] (resolved to
[01:48] <atdprhs> "cpu_count=6.0 mem=32768.0 storage=root:1024 zone=default")), retrying in 10s (9 more attempts)`
[01:48] <atdprhs> can anyone help please?
[02:18] <wallyworld> atdprhs: looks like the cloud on which k8s is deployed doesn't have a machine with the required memory to host the new worker
[02:19] <wallyworld> looks like this is cdk on maas?
[04:04] <anastasiamac> wallyworld: autoload-creds ask-or-tell PTAL https://github.com/juju/juju/pull/10617
[04:04] <wallyworld> ok
[04:04] <anastasiamac> \o/
[04:14] <wallyworld> anastasiamac: lgtm, ty
[04:44] <atdprhs> Hello wallyworld, sorry I missed your message
[04:44] <atdprhs> yes, it is on KVM Pod on MaaS
[04:48] <wallyworld> i'm not 100% across kvm pod allocation on maas. there would be maas specific set up which controls how kvm pods are allocated. you can use juju constraints to limit what is asked for which may help, but it could still be additional maas setup is needed. eg the error messages says cpu count = 6. perhaps asking for 2 or something would work
[04:48] <atdprhs> ahhh, got it
[04:48] <atdprhs> will test it out
[04:48] <wallyworld> the maas ux will show what machines have been allocated already and what's available
[04:49] <wallyworld> but i can't give you specific advice as i'm not a heavy maas user
[04:50] <wallyworld> one thing to note is adding a unit will use the constraints the original charm was deployed with
[04:50] <wallyworld> if you want to use different ones, you need to use juju add-machine --constraints="blah" first, and then "juju add-unit --to <machinenum>"
[04:51] <wallyworld> atdprhs: you could also try asking here https://discourse.maas.io/
[04:52] <wallyworld> the maas folks there can help much better than me about the kvm setup stuff
[05:59] <babbageclunk> wallyworld: review plz? https://github.com/juju/juju/pull/10618
[05:59] <babbageclunk> wallyworld: ended up being a bit fiddlier than I expected.
[06:05] <wallyworld> babbageclunk: no worries, looking
[06:19] <wallyworld> babbageclunk: lgtm, a couple of comments and a question
[07:11] <kelvinliu> wallyworld: ru still there?
[07:42] <manadart> jam: I am going to do QA testing on PR 10566 today, but I want to squash the commits at some point. If you want to take a look before I do (preserving the context of your prior comments) please go ahead.
[07:50] <jam> manadart: np, I think the big thing is to know which parts are the interesting ones and just focus there
[07:51] <manadart> jam: core/network and state.
[08:12] <manadart> jam: And probably apiserver/facades, where ProviderAddress -> SpaceAddress conversion is now occurring.
[08:12] <manadart> I am doing my own review now, and will annotate where appropriate.
[08:53] <atdprhs> hello everyone, I seem to have a model or controller that keeps creating VMs no matter how many times I keep deleting them, it recreates them
[08:53] <atdprhs> do anyone know if there is any way for me to find out whose doing that?
[08:54] <atdprhs> I keep seeing > 120 VMs that gets created
[09:15] <atdprhs> is there anyway that I can cleanup juju from all controllers, models everything
[09:26] <timClicks> atdprhs: what is the output of juju status?
[09:27] <timClicks> do you know what command triggered the first VM to be created?
[09:29] <atdprhs> it's stuck
[09:29] <atdprhs> I deleted the wrong vm
[09:29] <atdprhs> it doesn't respond anymore, i am really flooded with tons of them
[09:30] <timClicks> that sounds really horrible
[09:30] <atdprhs> yes, extremely horrible
[09:30] <timClicks> i recommend trying to remove the models first, hopefully the logs on the controller can be saved for a postmortem
[09:30] <atdprhs> luckily this is a test environment
[09:31] <timClicks> juju destroy-model <model-name>
[09:31] <atdprhs> ok, I'll destroy all of the moels
[09:31] <timClicks> actually do this
[09:31] <timClicks> juju destroy-model <model-name> --force --no-wait
[09:32] <timClicks> if you have many units, that will be faster
[09:32] <timClicks> you can also add a -y flag to avoid the confirmation prompts
[09:33] <atdprhs> one problem
[09:33] <atdprhs> I can't see models
[09:33] <atdprhs> and so I don't know what models I have
[09:33] <timClicks> okay
[09:33] <atdprhs> it says no controller registered
[09:33] <timClicks> oh, that's not okay
[09:34] <timClicks> what is the output of juju controllers
[09:44] <atdprhs> ERROR No controllers registered.
[10:05] <atdprhs> timClicks: is there a way that I can just simply reset or clean up juju?
[10:06] <stickupkid> atdprhs, what do you mean by reset? what does `juju controllers` say?
[10:06] <timClicks> not without the controller, I don't think
[10:07] <atdprhs> so I'll have to live with those VMs that keeps getting created?
[10:07] <atdprhs> :O
[10:09] <timClicks> it's the controller that would be creating them
[10:10] <atdprhs> is htere something like juju discover controllers?
[10:10] <timClicks> juju register
[10:11] <stickupkid> atdprhs, can you tell me what's in "less ~/.local/share/juju/controllers.yaml"
[10:11] <atdprhs> it's empty
[10:11] <timClicks> atdprhs: I'll hand over to stickupkid (it's after 10pm where I am)
[10:12] <stickupkid> atdprhs, do you have access to where vm software, i.e. where juju registered the controller?
[10:12] <atdprhs> thanks timClicks
[10:12] <atdprhs> yes, it's KVM
[10:13] <stickupkid> atdprhs, so you should be able to list all your vms, virsh list --all or similar
[10:13] <atdprhs> There are  lot of VMs
[10:13] <atdprhs> not sure which one
[10:13] <atdprhs> cuz sadly when juju creates a VM, it doesn't give MaaS a proper name for the VM
[10:14] <atdprhs> so I end up with ideal-bream, clean-cougar, fresh-beetle, free-chimp, comic-orca, ace-mink
[10:17] <stickupkid> atdprhs, so without knowing which is the controller, you'd have to resort to arp -n or ifconfig to get the ip address and then kill it
[10:17] <atdprhs> I'd just delete all of the Vms
[10:17] <atdprhs> they are all created by juju
[10:18] <stickupkid> atdprhs, then you can start again, by bootstrapping, sorry I'm not much more of a help
[10:19] <atdprhs> the thing is
[10:19] <atdprhs> that if i rebooted the server
[10:19] <stickupkid> atdprhs, otherwise juju register would be better to go down
[10:19] <atdprhs> juju will continue to recreate the VMs again
[10:20] <stickupkid> but if you've removed the controller, I've no idea how it's doing that
[11:20] <rick_h> stickupkid:  atdprhs did you juju unregister? that just removes the local cache of the controller information. It doesn't remove the controller
[11:20] <rick_h> stickupkid:  atdprhs if you unregistered and don't have it anywhere else you're going to be a bit stuck unfortunately. If you know what machine the controller is running on you can try to login to it, but you need to know the password of the admin user
[11:21] <stickupkid> rick_h, according to tailback atdprhs did juju destroy-model
[11:21] <rick_h> stickupkid:  looking at the traceback atdprhs is getting "it says no controller registered" so can't actually run any commands/etc
[11:37] <jam> rick_h: mine, brb
[12:41] <atdprhs> hi stickupkid / rick_h : I deleted the VMs
[12:42] <atdprhs> i'll bootup the server and see if anything gets created
[12:42] <atdprhs> If you guys say that no controller nothing gets created, so could it be possible MaaS? But what in MaaS could be doing that?
[12:43] <atdprhs> but from the specs of the VMs that gets created, I know it's from juju for one reason, the specs matches exactly the storage machines that I was trying to create
[13:25] <atdprhs> I booted up the server and I couldn't find any new machines
[13:25] <atdprhs> very strange
[13:37] <stickupkid> achilleasa, let me switch and bootstrap the last test case, land and if it no worky i'll let you know
[13:38] <achilleasa> stickupkid: sure thing
[13:52] <stickupkid> achilleasa, it worked
[14:58] <achilleasa> stickupkid: rick_h can I get a sanity check on https://github.com/juju/juju/pull/10620?
[14:58] <stickupkid> achilleasa, of course
[15:04] <stickupkid> achilleasa, scanned all the files, seems like very thing is spot on
[15:07] <achilleasa> stickupkid: the commits merged more or less cleanly (I had to tweak some imports because we have renamed some network pkgs on develop)
[15:07] <stickupkid> achilleasa, nice nice
[16:42] <stickupkid> hml, got a sec?
[16:42] <hml> stickupkid:  sure
[16:43] <stickupkid> hml, meet in daily?
[16:43] <hml> stickupkid: omw
[20:58] <pepperhead> o/
[20:59] <pepperhead> If I have a node reporting "pending" when running "juju status", how can it be forcibly cleared?
[21:00] <pepperhead> I think it happened because I removed an application before it finished deploying.
[21:00] <pepperhead> then aborted from MAAS
[21:25] <pepperhead> Anyone know how to tell if my bootstrap of juju installed the gui juju-gui?
[21:42] <timClicks> pepperhead: execute `juju gui`
[21:43] <pepperhead> SWEET! You ROCK!
[21:44] <pepperhead> Harder question: I have a juju State of pending on a maas node that wont stop. Is there a way to force kill it?
[21:45] <pepperhead> It was a deploy job that a killed "removed" before it ended, now stuck.
[21:46] <timClicks> juju remove-unit --force <app>/<n>
[21:46] <babbageclunk> pepperhead: does `juju remove-machine --force <id>` work?
[21:46] <pepperhead> started deploying mysql, and removed it in the middle, bad idea.
[21:46] <pepperhead> does remove-machine destroy the machin in maas?
[21:46] <timClicks> perhaps `juju remove-machine <n>`
[21:46] <babbageclunk> it should release it back to the maas available pool
[21:46] <timClicks> it'll put that machine back into the maas pool iirc
[21:47] <babbageclunk> ha timClicks beat you that time
[21:47] <timClicks> ha
[21:48] <pepperhead> Looks like that did it, I was afraid to try something that said "remove machine"... :)
[21:49] <timClicks> pepperhead: luckily juju doesn't have the ability to order a truck to send hardware to the landfill
[21:49] <pepperhead> But what if it did ;)
[21:49]  * babbageclunk starts coding it up
[21:49] <pepperhead> LOL
[21:50] <timClicks> please use the coffee pot protocol
[21:50] <timClicks> pepperhead: in terms of the wording though, everything juju-related is wrapped within a model
[21:50] <timClicks> so when you see remove anywhere, it means remove from the model
[21:51] <pepperhead> Ahhhhh, THAT makes sense.
[21:51] <timClicks> also remove-* commands are recoverable, they have a symmetric command add-* that reverses the removal
[21:51] <timClicks> destroy-* commands are, in a sense, unrecoverable
[21:52] <timClicks> they require you to start from scratch if you want to get back to pre-destruction
[21:53] <pepperhead> My last Q of the day, promise: I want to try deploying OpenStack on a set of hardware nodes, but they only have one drive and one nic in eeach. Is this possible? the blog I was going to follow mentioned it REQUIRED two drives in each and two nics.
[21:54] <timClicks> pepperhead: which guide?
[21:54] <pepperhead> Or is that more a mass thing, need to work around with curtin?
[21:55] <pepperhead> https://docs.openstack.org/project-deploy-guide/charm-deployment-guide/rocky/install-openstack.html
[21:55] <timClicks> i'm not familiar enough with openstack to speak authoritatively on production-grade deployments, but it's likely those "requirements" are actually "very strong recommendations"
[21:57] <timClicks> if you have the compute resources available, my recommendation would be to try it and see what happens
[21:57] <pepperhead> I am just doing a POC. Newly hired and the company REALLY need a private cloud to test terraform k8s control. It looked like Openstack look great, and I sold them on the maas/juju solution.
[21:58] <pepperhead> timClicks yes, I have struggling getting juju up. They handed me a stack of Intel NUC's, and juju would NOT bootstrap. FINALLY found it was a bios issue.
[21:58] <pepperhead> been struggling even
[22:01] <pepperhead> The bios is super poorly designed. Had to turn off the optical drive boot selection, the node being bootstrapped froze on reboot looking for it it seems. Also had to turn off "boot nic last", it overrode the boot order. and the boot order was specified in two locaions in a gui that required a mouse. Nightmare.
[22:01] <pepperhead> Thanks Intel
[22:03] <timClicks> sounds like you've had a fun few hours then
[22:04] <pepperhead> This fun is driving me to drinkin
[22:04] <pepperhead> admittedly a short drive
[22:05] <pepperhead> So the juju gui allows building a model, but wouldnt help with drive requirements/locations, right?
[22:08] <pepperhead> WOOT, the gui is working. VERY NICE!
[22:13] <pepperhead> VERY polished interface, kudos if any of y'all worked on it
[22:29] <pepperhead> Got that node re-commissioned, thanks again for the help!
[22:36] <timClicks> pepperhead: really great to hear that you're moving forward; do make sure that you're signed up here: https://discourse.jujucharms.com/


[11:38] <bac> frankban, teknico: could one of you look at https://codereview.appspot.com/6846053 if you have time?
[11:40] <teknico> bac, looking
[11:40] <bac> thx
[12:09] <teknico> bac, approved with one mostly useless comment :-)
[12:09] <bac> teknico: :)
[12:09] <bac> thanks
[13:12] <bac> hi mattuk1972, the changes you requested via store_front_review.pdf are now up on uistage.jujucharms.com:8080.  i've got a card for it in 'UX Review' on the kanban board.  please have a look when you can.
[13:12] <mattuk1972> cool will do
[13:20] <mattuk1972> bac, hi - I can see that the cells are now a fixed width but i they are not 70px and look too big - also the precise heading font size is incorrect and the leading between charm name and description is incorrect. the text should also be centered vertically in the cell?
[13:30] <bac> mattuk1972: i told them to be 70px so i'm surprised if they aren't.  is there a way you use to actually measure?
[13:33] <bac> mattuk1972: huh, the precise h3 is set to 16px.  not sure why.
[13:42] <bac> mattuk1972: nm, regarding the 70px. i see the problem
[13:52] <bac> mattuk1972: regarding "he leading between charm name and description is incorrect", what needs to be different.  You specified 19px between baselines but that isn't easy to realize.  The summary font is 12px and I have padding-top for it at 6px.  Do you want more of a gap or less?
[13:53] <mattuk1972> bad, ill measure it - brb
[13:53] <mattuk1972> bac!
[13:53] <bac> np
[13:53] <bac> thx
[14:00] <mattuk1972> bac - yours is 2 px further away than i have it - sorry for being so picky…..
[14:05] <bac> mattuk1972: that's your job!
[14:06] <bac> mattuk1972: let me get a screenshot for you
[14:06] <mattuk1972> bac then why do i feel so guilty? :-)
[14:09] <bac> mattuk1972: have a look at https://dl.dropbox.com/u/420990/Screen%20Shot%202012-11-15%20at%2010.07.30.png
[14:14] <mattuk1972> bac, your cells are now 68 :-(
[14:15] <bac> mattuk1972: chromium 'inspect element' shows me 287px x 70px
[14:16] <mattuk1972> bac, does it take that from just the cell or is it including the div lines?
[14:17] <mattuk1972> because they are 2px
[14:18] <bac> mattuk1972: i think it includes the borders.  i set the height of the cell to 68px so that chromium would show it at 70px.  let me bump it back up to 70
[14:20] <bac> mattuk1972: https://dl.dropbox.com/u/420990/Screen%20Shot%202012-11-15%20at%2010.19.29.png
[14:20] <bac> fwiw, chromium now shows the cell at 72px
[14:20] <mattuk1972> bac, i promise my cd's are not categorised and i don't have an ordered sock drawer ….
[14:20] <bac> you have cds?
[14:20] <mattuk1972> lol - in the loft
[14:21] <mattuk1972> yay that now measures 70 px
[14:22] <bac> ok.  it may be worth passing along to the other devs that we need to take into account the top and bottom borders when matching the specs
[14:22] <bac> mattuk1972: what about the spacing between charm name and summary?
[14:24] <mattuk1972> bac, looks good now ty
[14:25] <bac> mattuk1972: ok, i'll land it now and it'll be on staging at :45
[14:29]  * tveronezi I will back in one hour.
[15:29]  * tveronezi back
[15:59] <hazmat> tveronezi, Makyo, benji, frankban, teknico, bcsaller, jovan2 .. 1m till standup
[15:59] <bac> benji: are we having a call today?  i nominate you to lead it since i did monday.  :)
[15:59] <bac> oh, hazmat is here
[16:00]  * hazmat seconds the nomination ;-)
[16:00]  * hazmat reads the checklist
[16:01] <teknico> has anyone been getting call's email notices in the last couple of weeks?
[16:01] <hazmat> teknico, i've been getting appt reminders.. you can set what kind you want on the event
[16:02] <hazmat> teknico, you joining?
[16:02] <teknico> hazmat, I used to get them, then they stopped, without me changing anything (that I noticed, at least)
[16:15] <bac> hazmat: fwiw, ours is the 'official' python version referenced by leankitkanban:  http://support.leankitkanban.com/entries/20807108-leankit-api-wrappers-and-examples -- happy to coordinate with others, of course
[16:18] <teknico> benji, btw
[16:18] <hazmat> teknico, if you check in your g. calendar you should be able to setup an email alert on the event
[16:18] <teknico> hazmat, thanks, I'll check
[16:18] <bac> benji: you can't see it, but the giant orange ladder has been joined by a 100ft orange extension cord to power my compute farm, since all of the in-wall wiring has gone kaput
[16:18] <benji> bac: impressive :)
[16:18] <teknico> benji, I'm looking at https://code.launchpad.net/~juju-gui/charms/precise/juju-gui/trunk/+activereviews
[16:19] <teknico> benji, I think I left an extraneous tilde in when making up the branch paths
[16:19] <teknico> and it propagated everywhere, sorry :-)
[16:19] <bac> yeah, the electricians were supposed to come back today to finish up but couldn't due to a substation in the interior of the island blowing up
[16:19] <bac> i guess that is a national electricians day off when substations go boom
[16:21] <hazmat> bac, re leankit ..interesting thanks.. i've heard tale of of orange at least having additional kanban tooling based on lp2kanban.. and tales of francis having some other experiments with bidi sync.
[16:21] <bac> hazmat: interesting.  i'll check with them.  who is orange, again?
[16:21] <teknico> benji, otoh, looking at https://code.launchpad.net/~juju-gui/ , I'm not sure if we should retain the tilde or not
[16:22] <benji> teknico: it looks good to me
[16:22] <hazmat> bac, deryck
[16:22] <bac> right
[16:22] <teknico> benji, ok, then, I guess it would work either way
[16:22] <hazmat> jovan what's your launchpad id?
[16:23] <hazmat> er.. jovan2 ^
[16:23] <jovan2> hazmat: hi let me just check….
[16:24] <hazmat> jovan2, got it..
[16:24] <hazmat> jovan2, looks like its.. jovan-ljubojevic
[16:25] <jovan2> hazmat: jovan-ljubojevic
[16:25] <hazmat> jovan2, cool.. added you to the group
[16:26] <jovan2> hazmat thanks
[16:28]  * bac <- food
[17:07]  * tveronezi lunch
[17:22]  * tveronezi back
[18:07] <benji> I can't remember, were we doing camelCase for variable names or names_with_underscores?
[18:08] <benji> I think it was underscores, but mixing different conventions for method names and variable names always confuses me.
[18:16] <bac> hi Makyo, i've noticed some of the cards you've worked on lately have bugs but your branch and MP and launchpad aren't linked together with the bug.
[18:16] <bac> Makyo: if you use 'lbox propose -bug=' it'll hook it all up right
[18:17] <bac> benji: i_thought_so_too
[18:17] <benji> cool
[18:17] <benji> I will add that to the style guide
[18:20] <tveronezi> benji, bac: js is camelCase, python is_underscore.
[18:20] <Makyo> bac, I noticed that, and linked the last one manually.  Will use the -bug feature, though, thanks.
[18:20] <benji> tveronezi: that might be a slight over generalization
[18:30] <tveronezi> benji: These are the conventions for js and python that people usually follow. At least they are here... http://google-styleguide.googlecode.com/svn/trunk/javascriptguide.xml#Naming and http://google-styleguide.googlecode.com/svn/trunk/pyguide.html#Naming
[18:31] <benji> bac and tveronezi: hmm, we have a conflict of recolections then
[18:31] <benji> I'm fine either way, but we need to settle on something (I wish I had written this down when we decided)
[18:33] <tveronezi> benji bac: I remember we talking about that... specially because I was happy to continue to work with camel case in js code. :)
[18:33] <bac> benji: where is the crockford guide?  i recollect choosing to follow it closely, though not for indent
[18:33] <tveronezi> bac: http://javascript.crockford.com/code.html
[18:33] <benji> bac: http://javascript.crockford.com/code.html
[18:34] <benji> crockford is all cammelCase (upper/lower depending on the kind of thing)
[18:34] <benji> I guess that settles it: away with the underscores
[20:19] <bac> hi Makyo, i'm looking at your 'block removal of subordinate relations' branch.  can you tell me how to exercise it?
[20:20] <bac> Makyo: how to create a subordinate relation in the first place?
[20:21] <Makyo> bac, Deploy a subordinate (puppet's an easy one), and create a relation between that and one of the other services.  Click on the subordinate relation indicator beside the subordinate to keep the relations visible, then try to delete one by clicking on the label, as with normal relations.  You should get a relevant warning.
[20:21] <bac> Makyo: ok, i deployed rsyslog but couldn't make a relation with it
[20:21] <bac> let me try with puppet
[20:23] <bac> Makyo: got it, thanks
[20:23] <bac> Makyo: do you see the hideous shading when hovering over the 'Cancel' button?
[20:24] <Makyo> bac, hmm, yeah, just checked it against a regular relation, too.  Will look into it.
[20:24] <bac> Makyo: ok
[20:25] <Makyo> bac, got it.  Typo, or something.  Was removing a yui5 class.  I don't think yui5 is out yet.
[20:25] <bac> :)
[20:25] <bac> Makyo: also, my service block for puppet looks very funny.  the shading seems to be inverted.
[20:26] <Makyo> bac, yeah.  There's a different asset for subordinate services.
[20:27] <bac> Makyo: review done.  thanks.
[20:30] <bac> Makyo: when your MP gets approved keep an eye on the board to see that the card moves correctly.  i can't do real testing since staging.lp.net is not working.
[20:30] <Makyo> bac, thanks, and will do
[21:54]  * Makyo dogwalks.