[00:32] <calc> bdmurray: ping
[00:32] <bdmurray> calc: howdy
[00:33] <calc> bdmurray: hey what ever happened to the new graph layout that was shown at the sprint?
[00:33] <bdmurray> calc: this one? http://status.qa.ubuntu.com/qapkgstatus/openoffice.org
[00:34] <calc> bdmurray: cool, is it being updated regularly now?
[00:34] <stgraber> yeah
[00:34] <stgraber> every 30min IIRC
[00:34] <bdmurray> yep, there's lots of good stuff there too
[00:34] <bdmurray> like bugs w/ patches ... resolved uptream, etc
[00:35] <stgraber> (that's how often the cron job on kumquat is supposed to run, maybe the one on people.u.c doesn't run that often)
[00:35] <calc> is there a daily version of the graph?
[00:35] <bdmurray> calc: the triaging one?
[00:37] <calc> yea
[00:37] <bdmurray> calc: they are all in http://people.ubuntu.com/~brian/complete-graphs/openoffice.org/plots/
[00:38] <bdmurray> look for triaging or fixing
[00:38] <calc> bdmurray: well a daily version of what is shown on the qapkgstatus page (all on one graph but daily)
[00:38] <calc> ahh i see now
[00:38] <calc>  :)
[00:46] <bdmurray> ogasawara: what's the reboot kernel option?
[00:46] <ogasawara> bdmurray: reboot=b
[00:46] <bdmurray> when booting right?
[00:47] <maco> thats for bios reboot
[00:47] <maco> there are 4 different letters that can go after reboot= i think
[00:47] <ogasawara> maco:  correct, there are a few options you can use
[00:47] <ogasawara> bdmurray: I'm assuming you were wanting the option I was using with that Dell Dimension 9200 reboot bug I fixed?
[00:48] <bdmurray> ogasawara: Yeah, I was curious for bug 70793
[00:48] <ogasawara> bdmurray: and yes, it's a kernel boot param
[00:49] <bdmurray> ogasawara: so if reboot=b works it could be quirked (for jaunty) right?
[00:50] <ogasawara> bdmurray: possibly.  however, the primary reboot quirks were for Dells
[00:50] <bdmurray> hmm, okay
[00:51] <ogasawara> bdmurray: actually I take that back, there is one HP quick I see
[00:51] <ogasawara> bdmurray: but for HP Compaq
[00:51] <ogasawara> s/quick/quirk/
[00:52] <bdmurray> Alright, I'll ask them to test
[02:01] <csilk> Anyone around, I gotta quick changelog question
[02:01] <csilk> motu is dead
[02:02] <nhandler> csilk: What is your question?
[02:02] <lifeless> win goto #gnome-hackers
[02:03] <charlie-tca> Could I have Importance changed to low for Bug #283953 please?
[02:03] <csilk> the default changelog entry from dh_make is  * Initial release (Closes: #nnnn)   whereas one part of the wiki says I should do this >  * Initial Ubuntu package (LP: #242910)
[02:03] <csilk> Which one is standard for a new package?
[02:04] <csilk> obviously # is a variable
[02:05] <nhandler> The wording is not important. Just be sure you use LP: #NNNNNN instead of closes: #NNNNNN
[02:05] <nhandler> So the wiki is correct
[02:06] <csilk> nhandler, does this only apply to new packages or would this extend to features and bug fixes?
[02:06] <nhandler> (LP: #NNNNNN) is the syntax used to close bugs on Launchpad. (closes: #NNNNNN) is used in Debian to close bugs on the BTS
[02:07] <csilk> Thanks nhandler
[02:07] <nhandler> No problem csilk
[02:07] <csilk> That should probably be included in the main part of the packagin wiki entry
[02:07] <csilk> *packaging
[02:08] <nhandler> csilk: I'm not positive, but I am pretty sure that it is explained in some wiki page.
[02:09] <csilk> nhandler,  yeah it is but it's really obscure
[02:10] <nhandler> csilk: I'm probably not the best person to talk to about wiki issues. I would ask some other MOTUs what they think, and if they agree that it should be explained in more detail on the packaging guide, go ahead and add it in.
[02:10] <csilk> Ok cool
[02:39] <julian> hello all...new here would like to know how I can help?
[02:41] <persia> julian, Well, there's quite a few bugs outstanding, and reviewing them to make sure they have enough information to be fixed can be very helpful.
[02:42] <persia> https://launchpad.net/ubuntu/+bugs?field.status%3Alist=New&field.importance%3Alist=Undecided&search=Search is a list of those that nobody has reviewed yet.
[02:42] <julian> ok, thanks will take a look.
[02:42] <persia> Ask here if you have any questions, and if you run out, there are other things that could also be done :)
[02:44] <julian> ok
[02:46] <charlie-tca> Could I have Importance changed to low for Bug #283953 please?
[02:46] <charlie-tca> It's taken me months to confirm it.
[02:53] <hggdh> charlie-tca, it was already changed
[02:54] <charlie-tca> Thanks
[05:49] <dholbach> good morning
[05:53] <julian> morning all
[05:55] <maco> dholbach: five-a-day did something broken when it updated
[05:55] <maco> dholbach: and arent you up really early?
[05:56] <dholbach> maco: yes, Mimi's alarm clock went off at 5:30 and I couldn't get back to sleep... so here I am :)
[05:56] <dholbach> maco: what went broken?
[05:56] <maco> ah, i was going to say, this isnt even late here yet
[05:56] <maco> five-a-day and five-a-day-applet tried to update
[05:57] <Hobbsee> wow, 9th contributor for the last 7 days.
[05:57] <Hobbsee> I should do some more on that
[05:57] <maco> Setting up five-a-day (0.58~hardy1) ...
[05:57] <maco> pycentral: pycentral pkginstall: not overwriting local files
[05:57] <maco> pycentral pkginstall: not overwriting local files
[05:57] <dholbach> maco: interesting
[05:58] <dholbach> I'm not sure though what I can do in five-a-day to work around that
[05:58] <dholbach> let me get another opinion
[05:58] <dholbach> maco: I just pinged doko about it in #ubuntu-devel
[05:58] <dholbach> could well be that he's not up for quite a while
[06:06] <maco> ok
[06:26] <dholbach> maco: could it be that you have local files?
[06:29] <maco> dholbach: um, i have my ~/.5-a-day-maco/
[06:29] <maco> dholbach: do i have to delete that to install the update?
[06:29] <dholbach> maco: no
[06:30] <dholbach> did you manually install or change any of the files listed in  /var/lib/dpkg/info/five-a-day*.list ?
[06:31] <chipr> I've reported a bug that breaks intrepid upgrades, but it isn't being responded to.  Is there any mechanism to escalate? https://bugs.launchpad.net/ubuntu/+source/dokuwiki/+bug/270701
[06:31] <maco> dholbach: no
[06:32] <chipr> what can be done?  hate to see intrepid upgrades start breaking
[06:33] <dholbach> chipr: I added an update-manager task
[07:11] <chipr> How do I find the source to a package?  I'm reading HowToFix and it shows downloading the xicc_0.2-2.dsc source, but doesn't show how it found the URL to it.
[07:11] <maco> chipr: apt-get source <package>
[07:34] <thekorn_> good morning
[07:37] <maco> hi
[07:38] <maco> thekorn: dholbach doesn't know why, but the newest five-a-day refuses install, saying pkginstall: not overwriting local files...but i havent edited any system files related to five-a-day, just my my ~/.5-a-day-maco.m/*
[07:38] <maco> do you have any idea?
[07:45] <thekorn> maco: well, I've no clue, he is the packaging expert ;)
[07:53] <csilk> is this a virtual package http://packages.ubuntu.com/intrepid/libgtkglext1 ?
[07:57] <csilk> wonr chan
[07:57] <csilk> *wrong channel
[07:59] <maco> thekorn: oh right...haha i was thinking it could have something to do with code, but yeah..forgot he was the packaging guru
[09:09] <danage> before i enter a bug report for network manager, i want to reset its configuration. where do i do that?
[09:10] <danage> ok never mind found it
[09:23] <danage> can someone help me triage this bug? did i make the bug report correctly? https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/286859
[09:46] <danage> i would like to report a bug in network manager, but i am not sure whether it's ath9k or nm related. nm keeps asking me for the key. can someone help me?
[10:48] <danage> i would like to report a bug in network manager, but i am not sure whether it's ath9k or nm related. nm keeps asking me for the key. can someone help me?
[10:48] <danage> help me= help me post a proper bug report
[10:49] <persia> danage, In the absence of anyone providing you with guidance, I'd suggest either waiting about 6 hours and asking again, or filing a bug with what you know.
[10:49] <persia> Someone triaging the bug will ask the right questions.
[10:58] <danage> persia: thanks. especially with this bug i have no clue on what additional information i should post
[10:59] <persia> I'd probably post .xsession-errors /var/log/syslog, dmesg, and lspci -vvnn, but that's just a loose guess based on it being maybe something with nm and maybe something with the driver.
[13:00] <Woody86> g'morning everyone :)
[13:15] <ibbuntu> what package should a bug about a default theme be placed under?
[13:16] <persia> ibbuntu, Which flavour?
[13:17] <persia> Alternately, which theme?
[13:17] <ibbuntu> persia: it's the ubuntu 'High Contrast Inverse' theme
[13:19] <persia> ibbuntu, I think that's gnome-themes
[13:20] <ibbuntu> ok, thanks
[13:20] <persia> Wait, no.
[13:22] <persia> It's gnome-accessibility-themes.  Sorry for the confusion.
[13:22] <ibbuntu> ok, thanks, I couldn't find an "ubuntu-themes" package in launchpad
[13:25] <ibbuntu> well that concludes my first ever triaging of a bug, hopefully I'll do many more :)
[13:43] <jrib> Hi, is there a list of tags somewhere?  I'm reporting a ftbfs bug and am wondering if I should just put [ftbfs] in the title or add the ftbfs tag
[13:47] <persia> jrib, You could add the FTBFS tag.  I don't know if anyone searches that : most of the ftbfs hunting I see is from http;//qa.ubuntuwire.com/ftbfs/
[13:47] <persia> (and that works better with a :)
[13:49] <jrib> I was wondering why I couldn't click
[13:50] <persia> Yeah, typo.
[13:51] <jrib> persia: this has me asking why the package I want to report is not listed there.  It's python-webkitgtk
[13:52] <Pici> jrib: When did it fail to build? That page looks like its updated daily (see footer)
[13:52] <jrib> It fails because of the version of python-gtk2-dev,  I made a bug upstream about it: http://code.google.com/p/pywebkitgtk/issues/detail?id=19
[13:52] <jibel> jrib: Hi, you can find a list of tags at https://wiki.ubuntu.com/Bugs/Tags .
[13:52] <jrib> Pici: I believe I noticed on friday.  At least more than one day
[13:53] <jrib> jibel: thanks, not sure how I missed that :)
[13:53] <persia> jrib, Looks like it was last rebuilt in August, so the dependencies changed.  We don't catch that so well yet.
[13:54] <jrib> persia: ah, ok
[14:09] <jrib> How can I link bug 286965 with http://code.google.com/p/pywebkitgtk/issues/detail?id=19 ?  What magic button must I click?
[14:10] <jrib> I'm on edge by the way
[14:10] <charlie-tca> I usually use the "Also affects project" under the yellow line
[14:11] <jrib> charlie-tca: Do I just make up my own project then?  I thought there was some text field that just let me enter a url at some point
[14:13] <charlie-tca> That normally does. If it doesn't, I add it to the comments since upstream may not be in launchpad
[14:41] <alexmax> Hi there, I believe I found an issue with package mnogo-client.  It refuses to automatically configure itself because mysql says that when I try to configure it, it's not actually sending it a password, even if I specify a password in the installation script.
[14:42] <alexmax> I was told that someone in here might be able to help me verify this
[14:42] <snap-l> Checking to see what mnogo-client is. :)
[14:43] <alexmax> actually, wrong package
[14:43] <alexmax> it's either mnogosearch-client or mnogosearch-mysql
[14:44] <snap-l> hardy or intrepid?
[14:44] <alexmax> hh
[14:45] <alexmax> The step it seems to trip over itself on is the step that offers to automatically configure itself with mysql
[14:45] <alexmax> It tosses a MySQL driver: #1045: Access denied for user 'root'@'localhost' (using password: NO)
[14:45] <snap-l> Is there a bug filed?
[14:45] <alexmax> No, but I was wanting to make sure that I was running into a bug and not overlooking something
[14:46] <snap-l> Looks like a bug, since it doesn't create the database
[14:46] <alexmax> Yeah, i get that exact error if I use a console and mysql --user=root
[14:46] <snap-l> Setting up mnogosearch-common (3.3.6-1ubuntu0.1) ...
[14:46] <snap-l> '/usr/share/mnogosearch/tables/mysql/drop.blob.sql' dbtype=2 dbmode=6
[14:46] <snap-l> SQL>'DROP TABLE url'
[14:46] <snap-l> {../../src/sqldbms.c:2269} Query: DROP TABLE url
[14:46] <snap-l> MySQL driver: #1049: Unknown database 'mnogosearch'
[14:46] <snap-l> So it's a config bug
[14:47] <alexmax> I'm not sure that's the problem.  Scroll down a bit and see if it gives you Access Denied
[14:47] <snap-l> It doesn't, because the user I selected has create authority
[14:48] <alexmax> The user i specify is root, yet it says that Access is denied
[14:48] <alexmax> because of lack of password
[14:48] <alexmax> even though I send it a password
[14:48] <snap-l> That's a separate issue.
[14:48] <alexmax> Maybe it uses a different script for each 'type'.  Did you select blob, multi, or single?
[14:48] <snap-l> I selected blob
[14:49] <alexmax> And you're using 3.3.6-1ubuntu0.1?
[14:51] <snap-l> Yep
[15:05] <alexmax> Bug submitted
[15:06] <mvo> jibel: thanks for your work on update-manager bug triage \o/
[15:06] <alexmax> It doesn't really matter in the end.  I just wanted to fool around with it, however this search is eventually going to end up on a RHEL 5 box and I don't think they have a package for it, so I'm going to have to figure out how to compile the thing manually anyway.  Thanks for your help
[15:12] <snap-l> alexmax: NP. It looks like it may be a simple fix to get it fully automated.
[15:35] <jibel> mvo: Thank you.
[15:36] <danage> i would like to report a bug in network manager, but i am not sure whether it's ath9k or nm related. nm keeps asking me for the key. can someone help me? (help me= help me post a proper bug report)
[15:37] <azimout> danage: which key are you being asked for? the keyring key, or the wifi key?
[15:39] <danage> um... the wifi key.
[15:45] <azimout> this is not a bug. it is possible for the network manager to save the wifi key in the gnome keyring...
[15:46] <azimout> however, if you do that, you will still be asked for the gnome keyring master password each time you login...
[15:48] <azimout> have a look here:
[15:48] <azimout> https://help.ubuntu.com/community/WifiDocs/WPAHowTo#Avoiding%20password%20nagging
[15:51] <azimout> is this what you were looking for?
[15:59] <Bit_Breaker> hi all
[16:00] <danage> azimout: thanks for that, but it was NEVER an issue for me before
[16:00] <danage> network manager would just connect to the network, no problem
[16:01] <danage> it only came with my new wifi card
[16:02] <azimout> if i'm not mistaken, old network managers saved the password in a file in your home folder in plaintext => security issues
[16:02] <danage> old = 0.6
[16:02] <danage> ?
[16:02] <azimout> now it's saved in encrypted for in network manager
[16:03] <azimout> i meant in gnome keyring
[16:03] <danage> yes
[16:03] <danage> BUT the password is already IN THE BOX when it pops up
[16:03] <danage> it cannot be on purpose, this?
[16:13] <rrittenhouse> th
[16:13] <rrittenhouse> er
[16:14] <Bit_Breaker> im am new . do i get a hug if i triage as well
[16:15] <azimout> danage: can you please look into seahorse (applications->accessories->passwords and encryption keys)?
[16:15] <azimout> check if the wifi key is under the tab "passwords" or not
[16:20] <ichthyoboy> Hi all...here to help out with the Hug Day
[16:21] <Bit_Breaker> hi
[16:21] <Bit_Breaker> this is so cool
[16:22] <Bit_Breaker> i was told that there are iso files available that re-create some of the bugs.
[16:22] <Bit_Breaker> can someone point me in the right direction
[16:22] <bdmurray> Bit_Breaker: some bugs can be recreated using the Live CD.
[16:23] <Bit_Breaker> oh ok thanks bdmurray
[16:24] <danage> azimout: yes, it is
[16:24] <bdmurray> The iso that you want probably depends on the bug report
[16:25] <bdmurray> Bit_Breaker: Is there a particular bug you are looking at?
[16:26] <Bit_Breaker> im looking at Low/Medium bugs now
[16:26] <Bit_Breaker> i wanted to re-create them in a VM
[16:26] <danage> azimout: i deleted them all now, see what happens
[16:26] <bdmurray> What virtualization software are you using?
[16:26] <Bit_Breaker> i am not looking at any specific bug
[16:26] <Bit_Breaker> VirtualBox
[16:27] <ichthyoboy> question: how do you mark a bug as wishlist?
[16:28] <azimout> danage: anyways, i have to admit i don't have much experience in this
[16:28] <bdmurray> ichthyoboy: you use the importance drop down - by the way only members of bug control can set importance
[16:28] <charlie-tca> ichthyoboy: mark it confirmed and then request it here
[16:28] <ichthyoboy> bdmurray: thanks
[16:28] <danage> azimout: now it doesn't connect at all
[16:28] <danage> ah man, this sucks
[16:29] <azimout> but any problems you might have are definitely network-manager/gnome-keyring/seahorse related, and not driver-related (i.e. ath9k)
[16:29] <ichthyoboy> charlie-tca: thanks
[16:29] <danage> azimout: ok
[16:29] <danage> bdmurray: can you connect me with someone who can help me fetch the necessary information to file a network manager bug
[16:30] <bdmurray> danage: Is https://wiki.ubuntu.com/DebuggingNetworkManager insufficient?
[16:30] <Bit_Breaker> Can i confirm a bug if its similar to what some else is experiencing
[16:31] <danage> bdmurray: this is wonderful, didn't know it existed. thank you
[16:31] <bdmurray> Bit_Breaker: bugs can sometimes have the same symptoms but different root causes.  So similarity really depends on the type of bug.
[16:33] <mrooney> bdmurray: do you know if bug 274995 is on anyone's radar? I also am not sure what importance to give it, probably Medium?
[16:34] <Bit_Breaker> this is the bug i am refering to
[16:34] <Bit_Breaker> https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules-2.6.24/+bug/244405
[16:34] <Bit_Breaker> i just changed it to confirmed .
[16:34] <Bit_Breaker> Was  i wrong to do so?
[16:35] <danage> bdmurray: Oct 21 17:33:03 Computer kernel: [ 8374.908084] wlan0: authentication with AP 00:1f:3f:13:d2:ec timed out
[16:35] <danage> i guess the wiki page _is_ insufficient
[16:37] <bdmurray> Bit_Breaker: I don't think is sufficient information to set it to Confirmed.
[16:38] <ichthyoboy> bug #262506 should be marked as wishlist
[16:39] <Bit_Breaker> ok sry about that
[16:39] <thekorn> Bit_Breaker: and please do not assigne to a bugreport, this means you are working on it, you probably want to subscribe
[16:39] <Bit_Breaker> yes i see that now
[16:40] <Bit_Breaker> sry again
[16:40] <bdmurray> Its easy to fix and not a big deal. ;)
[16:40] <Bit_Breaker> cool!! :-)
[16:42] <danage> bdmurray: so do you perhaps know someone i could talk to
[16:42] <danage> broken wifi is... bad
[16:44] <bdmurray> mrooney: that bug seems like it might contain multiple issues
[16:51] <bdmurray> ichthyoboy: wishlisted - thanks
[16:55] <mrooney> anyone aware of a dupe for bug 287040?
[16:57] <Bit_Breaker> Had to reboot
[17:12] <ichthyoboy> bug #177882 should be marked as either wishlist or low (probably low)
[17:14] <bdmurray> ichthyoboy: Have you tested that at all?  Shift+F10 behaved the desired way for me
[17:17] <ichthyoboy> just did, and it works as expected for me as well.  Should it be reset to new, and ask for followup?
[17:18] <bdmurray> ichthyoboy: well, incomplete but yes that sounds best to me
[17:18] <ichthyoboy> bdmurray: ok..will do.
[17:18] <bdmurray> ichthyoboy: thanks!
[17:19] <ichthyoboy> bdmurray: No problem...glad to be able to help a little bit!
[17:21] <danage> bdmurray: i have tried from a live cd now - same problem. also, sporadically it does connect. when it does, no data can get transmitted. i DO however get an ip - dns doesn't work, transfers don't work. over wired internet everything is fine
[17:21] <danage> *wired lan
[17:22] <bdmurray> danage: which live cd and which network driver?
[17:22] <danage> nightly live cd downloaded 2 hours ago, network driver ath9k for wlan and e1000 for lan lan
[17:23] <bdmurray> Do you have linux-backports-modules installed?  I think that has a newer wireless driver
[17:25] <ichthyoboy> Would bug #280975 apply mainly to upstream sources (i.e., firefox, konqueror, opera, etc.)
[17:27] <danage> bdmurray: let me try. thanks
[17:38] <danage> bdmurray: no luck. even though it behaves slightly different
[17:38] <danage> e.g. my wireless led comes alive
[17:39] <danage> bdmurray: would you recomment i just wait and see what happens - i am probably not knowledgeable enough to support with valuable debug information
[17:41] <Bit_Breaker> what is the bug # to the issue that you guys are refering to
[17:46] <niadh> this bug looks like it can be checked off the days todo list, can someone confirm?
[17:46] <niadh> https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/281940
[17:53] <danage> asac: ping
[17:55] <asac> danage: just ask please
[17:56] <greg-g> contentless pings!
[17:56] <greg-g> ;)
[17:56] <danage> i have seen you have been active in some of the bugs i am encountering
[17:56] <danage> in 259157 there seem to be different issues confused
[18:21] <calc> i found a bug in launchpad relating to bugs :\
[18:21] <calc> https://bugs.edge.launchpad.net/ubuntu/+source/openoffice.org/+bug/216995
[18:21] <calc> it claims this bug is pending_bugwatch
[18:30] <calc> i now have OOo above 80% bug watched :)
[18:30] <calc> shooting for 90% in the next couple days
[18:31] <james_w> nice
[18:34]  * calc streamlined his bug links to get work done more efficiently
[18:34] <calc> some of my auto responses in greasemonkey keep disappearing probably due to firefox crashes i guess :\
[18:35] <thekorn> 5
[18:39] <bdmurray> james_w: bug 286172 doesn't seem the same as your at upgrade one
[18:39] <james_w> hey bdmurray
[18:40]  * mvo can't beliefe that "at" fails to restart
[18:40] <james_w> bdmurray: I started using the lp-gm scripts, but a couple of things don't work, do they all work for you?
[18:40] <bdmurray> james_w: which couple? there are a lot of scripts to keep track of ;)
[18:40] <james_w> but yeah, I agree it's different
[18:41] <james_w> bdmurray: the karma points are always 0, though I get the team logos
[18:41] <james_w> bdmurray: and the tag links don't do anything
[18:41] <bdmurray> james_w: on edge?
[18:41] <james_w> yeah
[18:42] <asomething> the karma points script works here, on edge as well
[18:51] <calc> 27 bugs left to green status :)
[18:51]  * calc notes properly upstreaming OOo bugs is a pita
[18:52] <calc> have to test on 3 different versions, then determine which upstream to send it to
[18:53]  * calc wishes sun could just get along with novell and be more open
[19:21] <jwendell> didrocks, ping
[19:22] <didrocks> jwendell: pong
[19:23] <jwendell> didrocks, why do you think vino 2.24.1 fixed bug 264315?
[19:23] <didrocks> hum, let me see
[19:23] <didrocks> oh, I tested it
[19:24] <didrocks> I see something similar in the NEWS file
[19:24] <didrocks> and decided to test it on my intrepid VM
[19:25] <jwendell> didrocks, actually they're different issues
[19:25] <jwendell> very different
[19:26] <didrocks> jwendell: hum, I misunderstand maybe the description
[19:26] <didrocks> but the description told that the new port was not taken into account, no?
[19:27] <didrocks> oh
[19:27] <didrocks> lower or higher :/
[19:27] <didrocks> sorry, didn't remembered that
[19:27] <didrocks> I just tested changed it around 5900
[19:27] <didrocks> so, the bug is not closed… sorry :/
[19:28] <didrocks> jwendell: I reopen it right now
[19:28] <jwendell> didrocks, ok
[19:30] <didrocks> jwendell: done, bug #
[19:30] <didrocks> bug #264315
[19:30] <jwendell> didrocks, did you confirm the bug?
[19:30] <jwendell> are you sure?
[19:38] <didrocks> jwendell: sorry, I was away
[19:38] <didrocks> jwendell: yes, that's still the case
[19:38] <jwendell> ok then
[19:38] <didrocks> (from the bug I was first thinking that it was not taken into account IN this range)
[19:38] <didrocks> but out of it, it was normal to not have it taken into account
[19:40] <jwendell> I would close it as 'not a bug', but...
[19:43] <didrocks> jwendell: hum, people now what they do if they assign such a port value, no?
[19:43] <didrocks> s/now/know
[19:44] <jwendell> :P
[19:44] <jwendell> they should, at leat
[19:44] <jwendell> least
[19:45] <didrocks> (some hope on human being, please ^^)
[21:11] <cerrigno> hello
[21:12] <cerrigno> i need a help
[21:13] <cerrigno> i've reported a bug here https://bugs.launchpad.net/ubuntu/+source/powernowd/+bug/286264
[21:14] <cerrigno> i don't knok if it's a bug, but 8.04 works properly (64-bit). 8.10 not.
[21:14] <cerrigno> 64-bit, of course
[21:15] <cerrigno> in italian ubuntu forum somebody has said that it can depend on my ati video card
[21:16] <chrisccoulson> cerrigno - you say it works if you select 'safe graphics mode', which means that the powernowd thing is probably a red herring
[21:16] <cerrigno> now i'm trying to download 32-bit version of last beta.
[21:17] <chrisccoulson> what is more likely is that the Xserver is failing for some reason and that is just the message you see
[21:17] <chrisccoulson> when you boot, try switching to a console with CTRL+ALT+F1.
[21:17] <chrisccoulson> if that is successful, have a look at your /var/log/Xorg.0.log
[21:18] <cerrigno> mmm in other words (i'm not so pratic): i just try to boot pressing ctrl alt f1 while it is loading ubuntu?
[21:20] <chrisccoulson> use CTRL+ALT+F1 when it appears to stop booting
[21:21] <cerrigno> ok
[21:22] <cerrigno> because, after i see ubuntu logo with orange bar below, it turns to black screen with white text. when it turns to black screen with white text i press ctrl alt f1. it should start anyway?
[21:24] <cerrigno> however, even if it is not a bug, it's very strange that on 8.04 there is not this problem
[21:26] <cerrigno> don't you think it?
[21:29] <cerrigno> chrisccoulson
[21:38] <cerrigno> chrisccoulson: now, the notebook is blocked on "Loading, please wait..."
[21:38] <cerrigno> after my CTRL + ALT + F1 press
[21:38] <cerrigno> it's a long process?
[21:41] <cerrigno> ideas?
[21:45] <cerrigno> now i try with 32bit package.
[21:45] <cerrigno> anybody has other ideas?
[21:48] <cerrigno> ?
[22:06] <azimout> question: does anyone have any clues about which source package should be assigned to this bug?
[22:06] <azimout> https://bugs.launchpad.net/ubuntu/+bug/253546
[22:10] <bdmurray> azimout: It possibly shouldn't be a bug report but ubuntu-meta seems like a fine location since there is one.
[22:11] <azimout> fine
[22:28] <azimout> quick question: what's the difference between packages linux-source and linux-ports-source?
[22:28] <azimout> their description seems the same
[22:29] <azimout> and linux-ports-source depends on linux-ports-source-2.6.25
[22:29] <azimout> are these packages obsolete?
[22:32] <calc> bdmurray: i think graphing some of the information from +upstreamreport might be useful as well
[22:32] <calc> bdmurray: currently if you are working on filing bugs upstream it doesn't really show up on the graph so it might seem as nothing is getting done
[22:32] <bdmurray> calc: https://wiki.ubuntu.com/QATeam/Specs/PackageStatusPages/Feedback
[22:32] <calc> ah ok :)
[22:33] <calc> i see its already on the list :)
[22:33] <bdmurray> wouldn't the bugs forwarded upstream number increase?
[22:34] <calc> hmm?
[22:34] <bdmurray> in the bug info part on the lhs
[22:34] <calc> well yes, but the graph doesn't split out the difference between triaged - ubuntu bugs, pending_bugwatch, and upstream
[22:35] <calc> which is the bit that i think would be of some use, if it didn't make the graph unreadable
[22:35] <bdmurray> got it
[22:35] <calc> i'll update that line item on the feedback
[22:35] <bdmurray> thanks
[22:35] <calc> at that point you can pretty much track all useful bug changes (i think?)
[22:36] <calc> er track via the graph i mean
[22:37] <bdmurray> azimout: yes, I think linux-ports-source is obsolete but I'm not positive
[22:38] <azimout> should i file a bug report about it, and assign to the kernel team?
[22:40] <bdmurray> I'm sorry about it how?
[22:41] <bdmurray> azimout: actually it was last uploaded yesterday
[22:41] <bdmurray> https://launchpad.net/ubuntu/+source/linux-ports-meta
[22:42] <azimout> i understand now.... thanks for clarifying...
[23:41] <jrib> Can anyone confirm for me that the build still fails after applying the debdiff in bug 286965?
[23:52] <chrisccoulson> jrib - just trying it now
[23:52] <jrib> chrisccoulson: thanks
[23:53] <bdmurray> hggdh: you rock!
[23:54] <hggdh> bdmurray, I humbly thank you, sir -- but what did I do?
[23:54] <hggdh> and, of course, you rock more :-)
[23:54] <bdmurray> I saw you had modified some bug descriptions with 'test case' and 'latest version tested'
[23:55] <hggdh> ah yes... I am trying to answer a join request, and used it to add them in
[23:55] <hggdh> trying to get the improved description in use...
[23:56] <charlie-tca> What's the page those are on the wiki? I saw them once and couldn't find them again
[23:57] <bdmurray> https://wiki.ubuntu.com/Bugs/Description
[23:57] <charlie-tca> Thank you
[23:58] <bdmurray> charlie-tca: I'm actually looking at your application now wrt bug 217900 are you saying gnome-eject doesn't work in Hardy if the drive is empty?
[23:59] <charlie-tca> If the cd is in the drive, you can't eject from the command line
[23:59] <charlie-tca> I don't think it's gnome-eject, but exo-eject. are they the same?