[00:01] <crimsun> LimCore: done.
[00:05] <LimCore> thanks
[01:04] <Ampelbein> hmm. when using bughelper to find bugs i get no output. with --debug i get: There is no row of the info-table linked to this bugreport. is this because of the recent launchpad update?
[01:05] <Hobbsee> quite likely
[01:56] <bdmurray> Ampelbein: what version are you using? and what exact command are you executing?
[02:04] <bdmurray> Ampelbein: I've tried recreating it w/o success
[02:04] <Ampelbein> bdmurray: bughelper --version
[02:04] <Ampelbein> 0.2.15
[02:05] <bdmurray> and a command to test?
[02:05] <Ampelbein> bughelper -p seahorse
[02:05] <Ampelbein> i'll pastebin the clue-file
[02:06] <bdmurray> great, is there a reason that isn't committed?
[02:07] <Ampelbein> most of all because it did not work here
[02:07] <bdmurray> that's a good one!
[02:11] <Ampelbein> http://paste.ubuntuusers.de/392005/
[02:11] <Ampelbein> damn captchas
[02:13] <bdmurray> Ampelbein: dinner here but I'll test it shortly, thanks
[02:14] <Ampelbein> happy eating. (i really don't know what the correct translation for "guten appetit" is ;-)
[02:18] <hggdh> bon appetit?
[02:19] <Ampelbein> hggdh: sounds french
[02:19] <Ampelbein> ;-)
[02:21] <hggdh> it is, but this is the only one I have ever used in the US. Never heard any other, but then I am a foreigner...
[02:23] <Ampelbein> hggdh: dict.leo.org suggests "Enjoy your meal!". now i'm ready to fly to the US!
[02:26] <Hobbsee> i'm not aware that there is a direct english translation, beyond "enjoy your meal"
[02:26]  * Hobbsee trouts Awsoonn at random.
[02:29] <hggdh> yes, perhaps. Still, I do not remember ever hearing it.
[02:30] <Hobbsee> no, it doesn't seem to be common
[02:31] <bdmurray> Ampelbein: which version of python-launchpad-bugs do you have?
[02:31] <Ampelbein> 0.3.1
[02:35] <bdmurray> really, that bug shouldn't have shown up in a list of seahorse bugs recently
[02:35] <bdmurray> I could see it crash like this on the 5th when the package was being changed but not today
[02:36] <hggdh> ohh, this is not good. I just 'cp -r evo-svn evo-svn.new' (which is to say, replicated the whole evolution svn image)
[02:36] <hggdh> then I look at the original evo-svn directory, and *all* evolution* directories are missing
[02:36] <hggdh> I look at the evo-svn.new, and they are there
[02:37] <hggdh> any ideas, before I start running and screaming around?
[02:50] <Ampelbein> bdmurray: i noticed that the ":" gets converted to the ascii-code when using bugxml. after rewriting the xml-manually it seems to work.
[02:50] <Hobbsee> hggdh: interested in some ISO testing?
[02:51] <hggdh> Hobbsee, I guess now I am...
[02:51] <hggdh> this is really bad
[02:52] <Hobbsee> hggdh: oh good.  Alpha 6 images need testing :)
[02:52] <Hobbsee> what is?
[02:52] <hggdh> 'cp -r' on very large directories removed some of the original subdirectories
[02:53] <Hobbsee> interesting.
[02:53] <hggdh> Hobbsee, I will have to wait for the ISO for when I get home, this weekend
[02:53] <Hobbsee> sigh.  That won't work then.
[02:53] <hggdh> I cannot download 700M in the hotel, not in time to be useful
[02:53] <Hobbsee> For anyone who *can* get things tested in the next 17 or so hours, http://iso.qa.ubuntu.com could do with some help.  There are instructions at the top of the page
[02:53] <hggdh> OK, OK. I will start the download
[02:53] <Hobbsee> hggdh: pity :(
[02:54] <Hobbsee> hggdh: if you can't download it, then there's little point :)
[02:54] <hggdh> well, I will try. The most that can happen is they will drop my connection ;-)
[03:00] <nullack> Hobbsee: Morning, I'll grab a build its about time this test build got turfed for a clean one
[03:01] <Hobbsee> nullack: excellent.
[03:01] <Hobbsee> nullack: you can use vm's, etc, if you want.
[03:01] <nullack> I got test machines here - doesnt matter. I run in no VM to get more into the test
[03:02] <Hobbsee> cool :)
[03:07] <Hobbsee> oh, drat.  i'm not on the -qa ML.
[03:55] <mrooney> offtopic, Dia is a REALLY slick little app, who would have guessed it can export a UML diagram to python code?
[03:55] <Hobbsee> mrooney: seriously?  nice!
[03:56] <mrooney> Hobbsee: Yeah, I was in the export menu looking for Visio (which was there) and saw the Python option, tried it, and I had a nice .py file will all the class, method, parameter, etc stubs all coded for me, with appropriate relationships handled
[04:04] <mrooney> Hobbsee: unrelated, for the Alpha 6 testing are you specifically looking for fresh installs from the ISO or is upgrading from an Alpha 5 install for example fine?
[04:05] <Hobbsee> mrooney: fresh installs is the more important
[04:05] <mrooney> ahh I see
[04:05] <Hobbsee> mrooney: we will test upgrades, but that will probably be closer to beta, and it will be from hardy --> intrepid.
[04:06] <Hobbsee> mrooney: currently, the aim is to make sure the installer doesn't blow up, etc.
[04:06] <mrooney> this laptop can't boot from USB, nor can it burn DVDs, and I don't have any CD-Rs :)
[04:06] <Hobbsee> and do to bits of upgrade testing - which a whole lot of people tend to do closer to release anyway.
[04:06] <Hobbsee> mrooney: use a VM, and mount the ISO?
[04:06] <Hobbsee> that's what I usually do.
[04:06] <mrooney> yeah I can do that now that virtualbox works :)
[04:06] <Hobbsee> \o/
[04:06] <mrooney> it sure was hard to test previously, haha
[04:07] <Hobbsee> i haven't tested the last few.  I've been slack.
[04:07] <Hobbsee> although i did test alpha 5 about a week ago, and went 'argh!'
[04:07] <mrooney> actually I should do it so I can test my migration-assistant patch
[04:07] <Hobbsee> indeed!
[04:07] <Hobbsee> i don't think anyone's tested it so far.
[04:07] <mrooney> m-a?
[04:08] <Hobbsee> yeah
[04:08] <mrooney> haha yeah it really doesn't appear that they have
[04:08] <mrooney> no FF3 support and Pidgin is still called Gaim
[04:09] <Hobbsee> ouch
[04:10] <mrooney> yeah, sounds like evand is busy
[05:15] <greg-g> there isn't an automatic way of keeping greasemonkey scripts updated with respect to a repo/url (ie: for the launchpad greasemonkey scripts)
[05:15] <greg-g> is there?
[05:18] <maco> greg-g: im experimenting with having it pointing to a bzr checkout....maybe running bzr pull auto-updates it? will go check...
[05:19] <kahrytan> Aloha, anyone?\
[05:19] <maco> oh, i have no revisions to pull
[05:19] <kahrytan> Who thinks Bug #238191 is nvidia bug?
[05:20] <greg-g> maco: I just had that idea, we'll see :)
[05:21] <kahrytan> greg-g»   you think my bug is a nvidia driver issue?
[05:22] <greg-g> maco: it looks like bzr pulling and restarting firefox works! :)
[05:22] <greg-g> kahrytan: looking now
[05:22] <kahrytan> greg-g»  I tried NV driver. works. Only locks up at X load with nvidia driver and glx enabled.
[05:23] <greg-g> why are you asking who thinks it is an nvidia bug when you said yourself it isn't?
[05:23] <maco> greg-g: yayy
[05:23] <kahrytan> Someone did tried to assign it to nvidia package
[05:23] <greg-g> kahrytan: and....
[05:24] <kahrytan> But it's not nvidia bug
[05:24] <greg-g> again, why are you asking here if someone thinks it is an nvidia bug?
[05:25] <kahrytan> greg-g» Cuz it's bug elsewhere. not sure where. I have both graphics card, ethernet card, and tv tuner (that order) inserted now. Using nvidia driver.  and it works now
[05:27] <kahrytan> Sounds like a Linux and Hardware issue to me.
[05:29] <kahrytan> greg-g»  So?
[05:29] <greg-g> kahrytan: I understand that the bug is not in nvidia. I will choose not re-ask my question again.
[05:30] <kahrytan> greg-g»  No reason. But could you help find the cause?
[05:32] <greg-g> honestly, I'm not too good with diagnosing those issues (linux kernel/HAL related)
[05:32] <kahrytan> You think it might be HAL/kernel related?
[05:32] <greg-g> kahrytan: see https://wiki.ubuntu.com/DebuggingHardwareDetection
[05:33] <kahrytan> ^ thats what im looking for
[05:33] <greg-g> maybe, it could be, I'm not sure I could tell what the root-cause is from the given information
[05:33] <kahrytan> I'll include lspci w/ and w/o 2nd pci card
[05:34] <greg-g> kahrytan: also https://wiki.ubuntu.com/DebuggingHal
[05:34] <kahrytan> the first wiki needs correction. -wnn doesnt exist
[05:35] <kahrytan> -w switch doesnt exist actually
[05:35] <greg-g> that is -vv
[05:35] <greg-g> just looks like a w
[05:36] <greg-g> sudo lspci -vvnn > lspci-vvnn.log
[05:36] <greg-g> that is copy/pasted from the wiki
[05:36] <Awsoonn> ping bdmurray
[05:36] <kahrytan> oops
[05:36] <greg-g> :)
[05:37] <kahrytan> but ill do those commands w/ and w/o 2nd pci card.
[05:37] <bdmurray> Awsoonn: pong
[05:37] <kahrytan> That would help debug it
[05:38] <Awsoonn> bdmurray: msg'd you
[05:39] <bdmurray> ooh, there's a team map now
[05:39] <Awsoonn> team map?
[05:39] <bdmurray> https://launchpad.net/~ubuntu-bugcontrol/+map
[05:39] <techno_freak> cool
[05:40] <Awsoonn> sweet!
[05:40] <greg-g> kahrytan: thanks for helping debug the issue
[05:40] <kahrytan> Awsoonn»  i mapped my loc already
[05:42] <kahrytan> Awsoonn» https://launchpad.net/~kahrytan
[05:42] <Awsoonn> I just set my loc as well
[05:42] <Awsoonn> :)
[05:42] <Awsoonn> https://launchpad.net/~dereck
[05:43] <kahrytan> your on a continent.
[05:43] <kahrytan> at first glance, i am in the middle of the ocean
[05:44] <Awsoonn> :P
[05:45] <kahrytan> google maps gets street numbers wrong lol
[05:51] <kahrytan> Awsoonn» A benefit for the location is for LoCos to use it to tell members where next meeting is
[06:34] <kahrytan> greg-g»  You still here?
[06:37] <kahrytan> Anyone here?
[06:39] <Hew> kahrytan: 106 of us are here, apparently :-)
[06:40] <kahrytan> smartaleck
[06:40] <kahrytan> its 105
[06:40] <kahrytan> 104
[06:40] <kahrytan> Bots dont count as people
[06:41] <kahrytan> You think .gz attachments to bugs is okay?
[06:42] <Hew> kahrytan: Should be fine, especially for something like large logs
[06:42] <kahrytan> Hew»  more like.. 12 logs.
[06:43] <kahrytan> 8 logs.
[06:43] <Hew> kahrytan: I'd recommend putting them all in a single .tar.gz
[06:43] <Hew> assuming they are related
[06:43] <kahrytan> lspci and lshal of 4 different hardware setups
[06:44] <kahrytan> I figured out, when I have onboard lan enabled when I got nvidia (nvidia driver) and tv tuner, I get a hardlock ( no REISUB) with X tries to start
[06:45] <kahrytan> I get hardlock when tv tuner is  inserted basicly.
[06:58] <kahrytan> Hew»  confusing isnt it
[07:00] <Hew> kahrytan: Indeed. Which bug #?
[07:02] <kahrytan> bug #238191
[07:04] <kahrytan> oops. forgot to update one log.
[07:08] <kahrytan> Hew»  reading logs?
[07:10] <kahrytan> When Intrepid beta comes out, ill do the same hardware test
[07:13] <kahrytan> time for me to compile and install tv tuner driver
[07:15] <Hew> kahrytan: It's not easy to tell what your issue is. It would be worthwhile elaborating on it in the bug description, as well as marking it as affecting the package you think is responsible. What causes the freeze? You have mentioned three devices which just confuses the issue.
[07:16] <kahrytan> How does it confuse it
[07:16] <Hew> kahrytan: Start with a simple setup, and try and find the one thing that causes the freeze.
[07:17] <kahrytan> Simple: Onboard LAN, Nvidia card with Nvidia, tv tuner = hard lock
[07:17] <Hew> kahrytan: You're mentioning switching graphics drivers, turning your LAN on and off, and doing something with your TV tuner. Can you reproduce the issue by just doing one of these things?
[07:17] <kahrytan> did nothing with my tv tuner.
[07:18] <Hew> kahrytan: If you tv tuner doesn't have anything to do with the issue, then why mention it? This is what makes it confusing I think.
[07:18] <kahrytan> If I remove tv tuner,  Graphics card and Onboard lan work.
[07:19] <kahrytan> Hew»  I don't know proper glx driver for GMA3100
[07:20] <kahrytan> otherwise, I would test that
[07:21] <Hew> kahrytan: Are you reporting multiple issues in the one bug? From what I can tell, your bug is about X not starting.
[07:21] <kahrytan> but its not X
[07:22] <kahrytan> perhaps i need to reinclude my other finds
[07:23] <kahrytan> Hew»  While I was testing opensuse to see how it is. I noticed that It was confusing my tv tuner for graphics card.
[07:23] <kahrytan> so I couldnt enable compiz
[07:24] <Hew> kahrytan: Opensuse? Compiz? These things are just complicating the issue (unless they are relevant to the bug you reported).
[07:25] <Hew> kahrytan: Edit the bug description, and clearly explain the problem (and the expected behaviour).
[07:26] <kahrytan> I did explain it as clear as possible
[07:26] <kahrytan> Kept it as simple as possible. no other way
[07:27] <kahrytan> Desc adheres to KISS basically
[09:48] <fre> hi
[09:55] <persia> fre: Hello!  Have you picked a bug yet today?
[09:57] <fre> no
[09:57] <fre> looking for it
[09:58] <fre> have you some advice? it's the first time I'm coming here
[09:59] <persia> Depends on what you'd like to do.
[10:00] <persia> If you've no direction at all, every new bug is announced in #ubuntu-bugs-announce, and the vast majority need at least some simple adjustments (you can always ask here for help).
[10:00] <fre> I have a bug on my computer with suspend on my computer which had been triaged as medium, is it the good place to try to solve it?
[10:01] <persia> If you're familiar with a certain piece of software, reviewing the bugs on that package can be rewarding, and get the list organised for a developer.
[10:01] <fre> Bug #269490
[10:01] <persia> There's also canned searches available for various types of bugs (like those that are old and untriaged) listed on the wiki pages in the /topic
[10:02] <persia> That one is already Triaged, so there's probably not so much to do, unless you want to work on the solution.
[10:02] <fre> ok, this forum is more for triaging than solving?
[10:03] <fre> chat
[10:07] <persia> fre: Well, there's some talk of solving bugs here, the focus is really on managing the bugs.
[10:07] <persia> If you've a known solution, and need testers, this is a good place, but only a subset of developers are here.
[10:07] <fre> thx
[10:08] <persia> Once bugs get sufficiently triaged that a solution is clear, and it's just waiting for developer work, you'd want to put on your developer hat to work on it.  For bugs in linux, the #ubuntu-kernel channel is the place to be while wearing a developer hat, but it's *really* quiet today.
[10:09] <persia> (that's "linux" the package, not "linux" the misnomer for an operating system)
[10:18] <fre> ah I would have a question
[10:19] <fre> ubuntu on my laptop sometimes can't boot
[10:19] <fre> it shows the progress bar
[10:19] <fre> but hang at maybe 15% and then I have to reboot
[10:20] <fre> which kind of log do I have to send in a bug report?
[10:20] <fre> dmesg?
[10:20] <persia> Are you sure it's not just hanging whilst it does the disk integrity check?  Try removing "quiet" from the kernel command line.  If it still doesn't work, you'll want to file a bug.
[10:21] <fre> when it check integrity there is some message with percentage under the progress bar
[10:21] <persia> Depends on the problem.  If it's a kernel problem, dmesg is certainly critical.  If it's a different problem, you'll want to target the things useful for the affected package.
[10:21] <persia> The trick is finding out at what precise point it crashes.
[10:22] <fre> but I will tryja
[10:22] <fre> sorry
[10:22] <fre> i will try the kernel option
[10:22] <fre> and for finding out
[10:22] <fre> it 's my question
[10:22] <fre> where do I have the more chance to finding out?
[10:22] <fre> in which log
[10:25] <fre> I will play a bit to find out
[10:25] <fre> thx
[10:25] <techno_freak> fre, if you remove quiet, you should know where it is not responding as it spews out what it does in the screen
[10:25] <fre> ok
[10:26] <fre> see you
[10:50] <fre> hi again
[10:53] <persia> fre: Did removing quiet help?
[10:53] <fre> yes and no
[10:54] <fre> I see that it hangs on "loading hardware driver"
[10:54] <fre> but a grep on the files in/var/log give no answer
[10:55] <fre> so the message outputted while booting are not saved in the log
[10:55] <fre> and I have no idea where to look
[10:57] <fre> thx for your concern
[10:58] <fre> maybe I should fill a bug and look for help from it?
[11:03] <fre> I know the goal was to triage bugs and not to add new untriaged ones :)
[11:29] <techno_freak> fre, dmesg
[11:32] <fre> techno_freak, what should I do with dmesg? give it to you? attach it in the bug report? look into it? And should it be joiined after a failed boot or is it enough to join it after a successed one?
[11:33] <techno_freak> fre, look into dmesg if it says anything about, related to looking for some hardware driver
[11:35] <fre> ok, how I do that? what should I look for?
[11:35] <fre> which word? hardware?
[11:37] <techno_freak> fre, typing `dmesg` on a terminal should show you
[11:38] <techno_freak> `dmesg | less` would be helpful to browse around
[11:39] <fre> well I am looking for it in emacs
[11:42] <fre> I have for now only one thing that I was able to recognize as strange. I have the same problem as Bug #271024: RTNL: assertion failed when modprobing 'wl'
[11:42] <fre> but there, there was no mention of difficulty while booting
[11:42] <fre> so that I don't know if it is related
[11:45] <ApOgEE-> what is happening if ntptime returns ntp_gettime() returns code 5 (ERROR)
[13:01] <Hew> Anyone else had/seen an issue in the last 24-48h where sound is broken? I can only get OSS to work. I've had a quick look, but haven't found a bug about it.
[14:03] <askand> I would call bug 61185 fixed, what do you think_
[14:27] <persia> askand: Are we not still waiting for a push of the final code to have that be fixed?
[15:01] <maco> can someone mark bug #271137 wishlist please?
[15:02] <persia> maco: done
[15:06] <maco> persia: thanks
[16:24] <Pici> Should /usr/share/dict/words (provided by, for example wamerican) be in UTF-8 or latin1?
[16:31] <Pici> nevermind
[16:31] <Pici> The manpage says it should be using ISO 8859-1
[18:12] <maco> flash 10's not supported in Ubuntu, is it?
[18:12] <maco> on Hardy, i mean?
[18:13] <chrisccoulson> nope
[18:13] <chrisccoulson> i think flash 10 was backported briefly and then removed
[18:13] <Nafallo> also. define 'supported'.
[18:15] <chrisccoulson> the definition as i've interpreted here is a package that a user can report problems with to Launchpad
[18:16] <maco> right, someone's reporting a bug with it with hardy
[18:18] <persia> Yeah.  For bugs, "supported" basically means "included in some official repo".
[18:20] <persia> There are other meanings floating about, for other cases, and depending on with whom one speaks, but "I can report the bug against LP" is perhaps a little broad, as sometimes we get bugs for things that aren't supported (historical example: early versions of the EasyBuntu script)
[18:20] <persia> The packages had the same names, but weren't the same contents, and the resulting bugs definitely fell in the "not supported" category.
[18:24] <maco> persia: i just wanted to know if i could go "not supported. invalid." on a flash 10 bug on hardy
[18:25] <persia> maco: Double-check backports, but I think so.  http://launchpad.net/ubuntu/+source/flashplugin-nonfree usually lists which versions are in which repos
[18:25] <persia> (replace the package name as needed)
[18:25] <persia> As you can see, there was a flash 10 in hardy-backports, but it was reverted with the +really9.0.124ubuntu2 upload.
[18:27] <persia> So, depending on the date of the report, it might be "Invalid: not supported", or it might be "Invalid.  There were a number of known regressions with Flash 10 in hardy-backports.  Please upgrade to the latest version, which restores Flash 9, and is expected to work."
[18:28] <persia> Selecting the "Show publishing history" (or going to https://launchpad.net/ubuntu/+source/flashplugin-nonfree/+publishinghistory) will tell you the appropriate date range to check.
[18:28] <maco> persia: it's like yesterday
[18:28] <maco> persia: and their package version is 9.  they got 10 from elsewhere.
[18:28] <persia> In that case, it's probably "Invalid: not supported" :)
[18:29] <chrisccoulson> also remember that if it's a bug against a backported package, the bug should be against hardy-backports (or whichever release the bug is in)
[18:29] <persia> Worth adding a note about being careful about installing software from external locations, and that software installed in that manner may cause unexpected issues with the system.
[18:29] <persia> chrisccoulson: It should, but sometimes bug submitters file against Ubuntu anyway.
[18:31] <chrisccoulson> i know. it isn't very obvious really though. the only way to discover that is to read the backports wiki page I think, and I bet most users running backported packages havent read that
[18:31] <persia> Yeah :(
[18:31] <chrisccoulson> ping ogasawara
[18:39] <bdmurray> chrisccoulson: she's at the linux plumber's conferense today is there something I can help with?
[18:39] <chrisccoulson> it was a general question about bug reports where the reporters machine freezes with no trace of anything in the logs
[18:40] <chrisccoulson> i was going to ask if doing a ALT+SysRq+P (assuming the machine is sufficiently alive) would give an idea where the freeze occurs
[18:41] <chrisccoulson> 'p'     - Will dump the current registers and flags to your console.
[18:45] <maco> chrisccoulson: i hate it when that happens
[18:45] <maco> alt+sysrq+t should get to a recovery console as well
[18:45] <bdmurray> chrisccoulson: it is an installed system?
[18:46] <maco> the trouble comes when the kernel won't accept the keyboard interrupts from alt+sysrq :-/
[18:48] <chrisccoulson> bdmurray: it was more of a general question, so it could be for an installed system or a live CD. i was looking at bug 271061, which I'm going to ask for all the usual information with in a moment - but I suspect that his dmesg or kern.log will contain no trace of the crash, in which case it becomes difficult to debug
[18:48] <chrisccoulson> although in this case, the reporter already knows which module causes the crash
[18:48] <chrisccoulson> but there are cases where that doesn't happen
[18:49] <chrisccoulson> bug 204996 is one of those cases
[18:53] <bdmurray> chrisccoulson: okay, I'll check with her when I see her next
[18:53] <chrisccoulson> thanks bdmurray
[19:11] <maco> is this the correct way to mark bug 271752 or should it be split into two separate bugs?
[19:42] <ian___> hey guys
[19:43] <ian___> anyone here working on network manager?
[19:51] <f1anker> hey guys
[19:51] <f1anker> any network manager fokes in here tonight?
[19:52] <chrisccoulson> f1anker - asac is the person to speak too i think
[19:53] <f1anker> thanks, just trying to get my pptp vpn bug confirmed
[19:53] <chrisccoulson> is anyone having to sign in to launchpad repeatedly every time they open their browser?
[19:59] <maco> chrisccoulson: you mean the thing where edge and stable don't do SSO?
[19:59] <chrisccoulson> i'm not sure what you mean. but i keep having to type in my username and password every time i go to launchpad
[20:00] <chrisccoulson> it started after the upgrade last night
[20:00] <asac> f1anker: not much time ... whats up?
[20:02] <maco> chrisccoulson: so not just the old login-twice thing?
[20:03] <chrisccoulson> i don't think so
[20:03] <maco> asac: should bug 271752 be marked against nm or the individual apps?
[20:23] <asac> maco: thats a dupe of "always offline" bug
[20:26] <maco> asac: oh ok
[20:27] <asac> maco: you you find it and mark it?
[20:27] <asac> err "can" ;)
[20:27] <chrisccoulson> ping seb128: bug 264011 - this looks similar to bug 251991, but that was fixed ages ago. you're not aware of any reason why this should be happening again are you?
[20:27] <asac> f1anker: please in public. i think i saw your bug. currently not really seeing why that is happening.
[20:28] <maco> asac: will look
[20:28] <asac> f1anker: ask me on monday and i will be happy to take a quick, but closer look
[20:29] <maco> asac: found it
[20:29] <seb128> chrisccoulson: no idea, is there clear steps to trigger the bug?
[20:30] <chrisccoulson> seb128 - there doesn't seem to be
[20:30] <asac> maco: ok ... should be a MASTER bug
[20:30] <asac> i think
[20:34] <maco> asac: yeah, it is. 191889
[20:37] <maco> asac: thanks
[21:13] <asac> maco: there are a bunch of bug-work required for NM ;)
[21:14] <maco> asac: don't worry i just found another dup :P
[21:15] <maco> so see, that one doesn't count
[21:16] <maco> argh i wonder if this has been reported...
[21:40] <asac> maco: i think what i would like is to have all 3G related bugs tagged "3g" ;)
[21:41] <asac> so if someone claims that he cannot connect with his umts/gsm/cdma modem/phone or if he claims that his hardware isnt detected
[22:08] <chrisccoulson> ping \sh
[22:33] <mrooney> is anyone aware of a bug where macbook touchpads randomly don't work at login (and require a reboot to work), and stop working sometimes after logout?
[22:34] <bdmurray> not I
[22:36] <mrooney> bdmurray: If I were to file a bug, what kind of output might I include?
[22:37] <mrooney> oh I think I am using a synaptics PPA to get mac-like right clicks, so it isn't supported, I guess it wouldn't matter anyway :)
[22:37] <mrooney> from the mactel-support PPA
[23:56] <Ampelbein> bdmurray: does bughelper also search in private bugreports? or only public.
[23:57] <bdmurray> Ampelbein: it depends on whether or not you are authenticated
[23:58] <bdmurray> so whether or not you pass it a cookie
[23:58] <Ampelbein> bdmurray: it's the cookie from firefox?
[23:59] <bdmurray> I haven't tried it recently but it should works and does work with python-launchpad-bugs directly