[00:59] <persia> qense: I'm not finding enough context from backscroll.  Ping me again, or send me email about your idea.  Something about team coordination?
[05:54] <calc> yipee OOo 44% triaged now :)
[05:57] <calc> there are only a few packages with higher percentage in the top 100
[05:58] <calc> 122 more bugs to have it have the highest triaged percentage :)
[05:58] <lifeless> cool
[05:58] <calc> 122 bugs will probably take a few days though
[07:14] <calc> anyone happen to remember the top 100 package bug report url for lp?
[07:14] <calc> i can't find a link to it on lp itself
[08:08] <Hew> Hi. I'm trying to verify bug #221673. I've created the .asoundrc correctly, but now I get: 'ALSA lib pcm.c:2106:(snd_pcm_open_conf) Cannot open shared library /usr/lib/alsa-lib/libasound_module_pcm_pulse.so' instead of the assertion failed error.
[08:09] <Hew> I have not yet installed the version in hardy-proposed. I have also checked that the file in the error I get does not exist.
[08:33] <Hew> I applied to be a member of ubuntu-bugcontrol a week ago, but I haven't heard anything yet. I notice there are 58 of us waiting, and the team is being advertised in this channel's topic. Can anyone provide some info on how long the process usually takes? No doubt bdmurray is busy, but I'm eager to take my triaging to the next level ;-) Thanks!
[10:41] <afflux> hi
[11:03] <thekorn> hey afflux
[11:03] <afflux> hi thekorn
[11:06] <\sh> moins thekorn
[11:07] <emgent> heya \sh :)
[11:07] <thekorn> \sh, hi, I'm just reading the code of leonov
[11:08] <thekorn> and try to understand how this pykde and pyqt thing work
[11:10] <\sh> thekorn: ah..too early...I'm just setting up the real directory structure to make things happen much faster :)
[11:10] <\sh> the ui is totally changed now..
[11:12] <thekorn> \sh, one idea: if you really would like to have a pygtk version, it might make sense too use a kind of generic (pyqt independent) data-model
[11:12] <\sh> thekorn: backend :)
[11:13] <\sh> thekorn: the idea is to have all needed infra inside backend...but gtk/qt specific stuff (this applies to the listviews data models) are bound to the frontend...
[11:15] <thekorn> \sh, ok, makes sense, so the structure will be something like qt/{model,view} and gtk/{model,view} plus the generic backend/
[11:16] <\sh> yepp
[11:17] <\sh> I don't see an other way to do that
[11:17] <\sh> the same goes for the configuration...
[11:26] <thekorn> \sh, some time ago I wrote a small gnome applet to trigger changes of someones bugs, given that leonov should be the "one and only" desktop client
[11:26] <thekorn> and I have currently no time to maintain the code
[11:27] <thekorn> I'm fine with merging this applet into leonov :)
[11:27] <thekorn> https://edge.launchpad.net/lp-bugs-applet
[11:28] <\sh> thekorn: cool :)
[11:31] <thekorn> \sh, what I really wanted to say is: having a notification functionallity in leonov like 'you are subscribed to bug xxx, this bug changed' would be really cool
[11:32] <thekorn> and that's what lp-bugs-applet is about
[11:44] <qense> hello
[11:52] <Hew> Hi. Bug #206992 has been fixed upstream, but has not reached Ubuntu. Should this bug now be "fix committed"? I'm unsure since the fixed version doesn't seem to be on the Ubuntu radar yet.
[11:58] <Hobbsee> yes
[11:59] <Hobbsee> fix committed == "there is a fix.  somewhere.  not in any ubuntu version yet"
[11:59]  * Hobbsee wonders when supertuxkart will make another release.
[11:59] <Hew> Hobbsee: Thanks for the reply. I was unsure since Bugs/Status says "For an Ubuntu package, the changes are pending and to be uploaded soon"
[11:59] <Hew> Hobbsee: 0.5 is out, I have it via getdeb and it's pretty cool :-)
[12:00] <Hew> but Debian is still on 0.4, I checked
[12:02]  * Hobbsee kicks debian's rmadison
[12:04] <Hobbsee> they've had a bug about it, is ee.
[12:05] <Hew> Hobbsee: Sorry for not understanding, but what's ee?
[12:05] <Hobbsee> s/is ee/i see/
[12:06] <Hobbsee> sorry :)
[12:06] <Hew> ah gotcha
[12:07]  * Hobbsee tries the old poke-and-it-shall-be-fixed approach.
[12:08]  * Hew watches on in hope
[12:28] <gnomefreak> ee is a basic text editor ;)
[12:29] <afflux> I wonder why we still use fix committed for "fixed upstream". I thought that using a project task for it was the launchpad'ish way.
[12:29] <gnomefreak> i use confirmed until i fix it or until someone else is working on it
[12:29] <gnomefreak> but thats just mozilla team
[12:32] <qense> There are a lot of bug reports about brightness controls lately
[12:33] <qense> some about key action reported twice or more at once
[12:33] <qense> or no reaction at all
[12:33] <qense> I've lost the overview a bit, so I'm going to create an overview page at my blog
[12:33] <qense> do you know any bug reports about this to include?
[13:04] <james_w> qense: hi, do you have a reference?
[13:04] <james_w> qense: it seems I may be seeing that testing now, and my media keys don't seem to work either.
[13:04] <qense> I've got five bugs now, and they are a bit reporting the same problems, or two at the same time:
[13:04] <qense> bug 207473
[13:04] <qense> bug 239413
[13:04] <qense> bug 203096
[13:05] <qense> bug 212733
[13:05] <qense> and bug 239706
[13:05] <qense> there are also others of course, but this are the bug reports that seem related somehow
[15:43] <Hew> Hey guys. seb128 just closed my wishlist bug #227350 because I have not set the "locale" time to 24h format. I've asked in #ubuntu, but nobody knows where this "locale" time can be set. Before I reopen the bug, could someone give their opinion on whether it should be opened or closed? Thanks.
[15:51]  * Hew gives his question a first and final bump
[15:55] <thekorn> Hew, it should definitely be closed
[15:55] <thekorn> if you want to change the locale setting for one program, run
[15:55] <thekorn> LC_TIME=en_GB rhythmbox
[15:58] <Hew> thekorn: Thanks for your reply. I just tried that, and along with some "locale not supported" messages, the time is still in 12h format. I'm not concerned about changing the setting for one program though, but in changing the global system value to 24h format so all programs follow it.
[15:58] <Hew> I thought I already had with the standard clock preferences, but seb128 says this isn't the case
[16:04] <thekorn> Hew, sorry I've some guests here, please ask in a support channel on how to change your locale settings
[16:04] <Hew> thekorn: no worries, thanks for your help
[16:05] <thekorn> or convert this bug into a question, and I'm sure somebody will give you the right answer soon
[16:33] <LimCore> it seems k8 cpu freq support is broken?
[19:06] <danage> since a few days, my external USB drive turns off a few seconds after i connect it. also, i have suspend issues with khubd. anybody familiar with the bug? if it's new, where should i file it?
[19:08] <leoquant> danage you have not reported the bug? so no bug nr.?
[19:08] <danage> leoquant: not yet. i wanted to avoid duplicates and also find out how to gather more info before i submit
[19:09] <leoquant> i see
[19:09] <danage> leoquant: is there a usb syslog?
[19:09] <james_w> usb information appears in /var/log/syslog
[19:10] <leoquant> hmm i don´t think so
[19:10] <leoquant> james_w indeed
[19:10] <danage> james_w: ok let me check
[19:11] <james_w> danage: have you installed a kernel update in the last few days?
[19:11] <danage> http://pastebin.ca/1047973
[19:11] <danage> then, the drive spins down
[19:11] <leoquant> the hardy -19 james_w?
[19:11] <james_w> probably
[19:11] <danage> james_w: yes, i have. but i rolled back the kernel to -17 and it still has the problem
[19:12] <danage> i am running -18
[19:12] <danage> why is network manager fuzzing with usb devices?
[19:13] <james_w> a kernel upgrade would be a likely cause, but if the old one no longer works then we can rule that out
[19:13] <leoquant> ik think you should report it
[19:13] <james_w> danage: can you use another pastebin please, I can't get to pastebin.ca.
[19:13] <james_w> !paste
[19:15] <danage> http://paste.ubuntu.com/20185/
[19:15] <james_w> thanks
[19:15] <danage> no error message. i find that strange
[19:16] <james_w> danage: can you check if you upgraded hal-info or a related package in the last few days?
[19:17] <danage> james_w: i think i have. let me check
[19:19] <danage> james_w: i am using 20080317+git20080318-1ubuntu4
[19:19] <danage> which packages are related?
[19:22] <greg-g> w00t! just closed out a bug from the 3000 range (opened 2005-10-10)
[19:22] <james_w> danage: sorry, got to go out, but someone else might be able to help.
[19:23] <james_w> danage: does downgrading hal-info to the hardy release version fix it, if so then I would suggest filing a bug against that.
[19:24] <james_w> danage: and https://wiki.ubuntu.com/DebuggingHal should help you file a good bug report if that is the case.
[19:47] <calc> almost 50% triaged for OOo :)
[20:11] <jjesse> yay
[20:11] <LimCore> calc: including my wish for odt+pdf \o/
[20:19] <crimsun> danage: have you pastebinned your lsusb -v somewhere?
[20:20] <danage> crimsun: let me do that
[20:20] <crimsun> (I'm also tracing a hal-info hardy-proposed regression, so this is good.)
[20:20] <danage> crimsun: it stalls
[20:20] <danage> crimsun: no output
[20:20] <danage> there is something seriously wrong here
[20:20] <crimsun> danage: meaning lsusb -v stalls?
[20:21] <danage> yes
[20:21] <crimsun> ok, does just plain lsusb complete?
[20:21] <danage> no
[20:21] <danage> not as root, either
[20:21] <crimsun> ok, can you reboot and just issue lsusb?
[20:21] <danage> le tme detach the usb and try
[20:21] <crimsun> ok
[20:21] <danage> no workie
[20:22] <danage> usb GENERALLY works though. i can print
[20:22] <danage> also i am using a usb mouse
[20:22] <danage> ok i will reboot into -18 kernel
[20:25] <crimsun> excellent.  These changes to fdi/information/10freedesktop/30-keymap-hp.fdi in hardy-proposed's hal-info fubars at least three different HPs.
[20:27] <danage> crimsun: as soon as i start the usb, it stalls
[20:27] <danage> the usb drive
[20:27] <danage> needless to mention, under windows it works
[20:28] <crimsun> ok, so it persists across -18 and -19 kernels.  Have you confirmed that it also persists when you downgrade to hardy's hal-info?
[20:28] <danage> crimsun: -17 and -18 kernels
[20:28] <danage> crimsun: i do not know how to do that
[20:28] <crimsun> ah, ok.
[20:28] <danage> crimsun: i tried to google it, but there seems to be no older version in the repos
[20:28] <crimsun> sudo apt-get -thardy --reinstall install hal-info
[20:29] <danage> no space between -t and hardy?
[20:29] <crimsun> (that's just one way)
[20:29] <crimsun> sure, you can, but I normally omit it.
[20:29] <danage> crimsun: another restart?
[20:30] <crimsun> restarting hal /may/ suffice, but I recommend that you reboot.
[20:30] <danage> i think it reinstalled the same version?
[20:31] <crimsun> dpkg -l hal-info|awk '/^ii/ {print $3}'
[20:31] <danage> 20080317+git20080318-1ubuntu4
[20:32] <danage> so
[20:32] <crimsun> right, that's correct.  That's hardy's version, which is what you want to use to test.
[20:32] <danage> that's the one i had
[20:32] <danage> is it not?
[20:32] <crimsun> ah, yes, just saw from backscroll
[20:32] <danage> ﻿(11:19:00 AM) danage: james_w: i am using 20080317+git20080318-1ubuntu4
[20:32] <crimsun> so your issue isn't hal-info related at all
[20:33] <danage> what is khubd? i get a khubd error when trying to suspend. that i didn't get before
[20:33] <crimsun> there's a usb issue matching yours, let me try to find it.
[20:35] <danage> crimsun: brb
[20:38] <danage> sorry crimsun i had to reboot
[20:39] <danage> crimsun: i have virtualbox-non-ose running. it needs some tweaks for usb support. could that be related?
[20:39] <crimsun> hmm, I don't track virtualbox, so I don't know, sorry.
[20:39] <crimsun> I presumed you were testing this on the host OS.
[20:46] <danage> crimsun: yes, of course. but the host usb support needed some tweaking. but that has been working (and remained unchanged) for months now
[20:49] <crimsun> danage: ok, to help narrow down some possible causes, is ehci_hcd loaded?
[20:49] <danage> hci_usb, ehci_hcd and uhci:hcd
[20:50] <crimsun> danage: ok, let's try the simpler workaround, then.
[20:51] <crimsun> sudo rmmod ehci_hcd && echo -n -1|sudo tee /sys/module/usbcore/parameters/autosuspend && sudo modprobe ehci_hcd
[20:52] <danage> yes
[20:52] <danage> no output
[20:52] <crimsun> ok, and does plugging in the drive exhibit the same symptom?
[20:53] <DanielRM> Hello?
[20:53] <crimsun> hi
[20:53] <danage> crimsun: not sure i understand. pluggin it in after these commands?
[20:53] <crimsun> yes
[20:55] <DanielRM> Hello. :)
[20:55] <danage> crimsun: it works now
[20:55] <danage> crimsun: thanks for the temp workaround!
[20:55] <DanielRM> Can I report a bug, or else get help in submitting the bug to Launchpad?
[20:55] <crimsun> sure
[20:55] <crimsun> I was just reading scrollback from #launchpad
[20:56] <danage> crimsun: let me sport a lsusb now!
[20:56] <DanielRM> crimsun: ah, so you know what my dilemma is, if not the bug itself?
[20:56] <danage> crimsun: lsusb works now
[20:56] <crimsun> DanielRM: well, I haven't finished reading
[20:56] <danage> friggin autosuspend
[20:56] <DanielRM> crimsun: have you got to the side-topic regarding faeces yet? XD
[20:57] <crimsun> danage: ok, that is fixed in 2.6.25 (and also in intrepid's kernel)
[20:58] <danage> crimsun: THANK you
[20:58] <danage> crimsun: ETA?
[20:59] <crimsun> danage: intrepid has built kernels; in the meantime, I recommend you use that workaround.
[20:59] <danage> meh, no backports?
[20:59] <crimsun> I don't think so, but I'm a bit distant from Ubuntu development these days.
[20:59] <danage> crimsun: ok one last think. which startup file do i put that in?
[21:00] <danage> thing
[21:00] <DanielRM> Wait, .25? I'm still on .24. :(
[21:00] <crimsun> DanielRM: that's correct (2.6.24) for hardy.
[21:02] <crimsun> danage: I don't know of one; you can either modify the udev rule(s) or use /etc/rc.local
[21:02] <danage> thank you
[21:02] <crimsun> DanielRM: am I correct in understanding that you're attempting to file a bug against Ubuntu Hardy's nautilus source package?
[21:03] <crimsun> ...ok.
[21:03] <DanielRM> What did I last say? :S
[21:03] <DanielRM> Just had a connection issue.
[21:03] <crimsun> 16:00     DanielRM > Wait, .25? I'm still on .24. :(
[21:04] <DanielRM> Ah.
[21:04] <DanielRM> Did you say anything after that?
[21:04] <crimsun> 16:02      crimsun > DanielRM: am I correct in understanding that you're attempting to file a bug against Ubuntu Hardy's nautilus source package?
[21:04] <DanielRM> OK. :)
[21:05] <DanielRM> crimsun: that's probably correct, although what part of Nautilus or even, exactly, if it is Nautilus or more some other part of GNOME I can't profess to know.
[21:05] <crimsun> DanielRM: ok, can you describe the symptom(s) you're experiencing?
[21:05] <DanielRM> I was trying to access a USB stick using the '3.9 GB media' label in an open file dialog when I got the error: 'You are not supposed to show G_IO_ERROR_FAILED_HANDLED in the UI'
[21:06] <DanielRM> And that's it.
[21:06] <crimsun> ok, so that symptom actually has several components
[21:07] <crimsun> the first component is linux and is, coincidentially, what danage and I just discussed.
[21:07] <crimsun> the second component is nautilus as you correctly surmised.
[21:07] <crimsun> the third component is gvfs.
[21:07] <DanielRM> Oh?
[21:08] <danage> multi layer problems, how wonderful
[21:08] <DanielRM> I'm using 2.6.24-19 kernel, BTW.
[21:08] <DanielRM> I'd quite like to know how to get .25 :P
[21:09] <crimsun> DanielRM: well, let's see if we can just work around the root cause for now, which is in linux.
[21:09] <crimsun> I need to grab a phone call, but if danage doesn't mind, he could help you through it
[21:09] <DanielRM> OK. :)
[21:10] <crimsun> danage: if you have a few minutes and don't mind, DanielRM just needs to issue those commands I referred to you
[21:10] <danage> crimsun: i don't mind
[21:10] <crimsun> 15:51      crimsun > sudo rmmod ehci_hcd && echo -n -1|sudo tee /sys/module/usbcore/parameters/autosuspend && sudo modprobe ehci_hcd
[21:11] <danage> DanielRM: that's basically what you run in shell before you activate your usb device
[21:11] <danage> (i.e. plug it in)
[21:11] <danage> and that does the trick
[21:11] <danage> i will look for a more permanent solution soon
[21:13] <DanielRM> Wait, I only understand some of that command. We're removing the kernel module ehci_hcd, which is what exactly? Then we're echoing... something... to tee, which is... searching?... for that path/status, and then we're loading the kernel module again?
[21:13] <danage> yeah
[21:13] <danage> you got it
[21:13] <DanielRM> Sorry, I just like understanding things as well.
[21:16] <danage> crimsun: i reported in #ubuntu-california about the usb bug and someone said you are a guru. so thanks again
[21:17] <crimsun> (nah, I'm no guru, just a disaffected Ubuntu user.)
[21:17] <DanielRM> Disaffected? Why?
[21:18] <crimsun> DanielRM: you're unloading a usb driver, changing a usb setting, and reloading a usb driver.
[21:19] <DanielRM> I didn't get your answer, if you gave one, but I'm becoming disaffected now. :P
[21:19] <crimsun> 16:18      crimsun > DanielRM: you're unloading a usb driver, changing a usb setting, and reloading a usb driver.
[21:20] <DanielRM> Wrong window was selected after I closed a window, so when I pressed alt-f4 the thing which didn't close happened to be what I wanted to and thing which did happened to be the IRC client. :P
[21:20] <marnanel> Someone did raise a bug recently asking for an "undo close" command.
[21:21] <DanielRM> Ah, OK.
[21:31] <DanielRM> marnanel: hmmm. An interesting thought.
[21:32] <DanielRM> marnanel: what sort of functionality did they want with it?
[21:34] <marnanel> DanielRM: Just a button that if you pressed it, the window would spring back to life again
[21:34] <marnanel> I suppose it would be a lot easier in OS X than here
[21:34] <DanielRM> I just wondered whether they were thinking of something like recovering the program's status at time of close... that would be quite difficult.
[21:35]  * marnanel nods, as far as I could make out they were
[21:35] <marnanel> that's what I meant about OS X -- closing windows never terminates an application there
[21:40] <DanielRM> Oh?
[22:09] <marnanel> DanielRM: yes, you have to specifically close the application from the menu
[22:10] <marnanel> DanielRM: closing all the windows, or the main window, to close the app is an X and Windows idea
[22:38] <thekorn> \sh, FYI I created a package of the latest version of py-lp-bugs in the bughelper-dev team PPA
[22:38] <thekorn> https://edge.launchpad.net/~bughelper-dev/+archive