[01:37] <asac> bdmurray: whats the state of bughelper?
[01:39] <bdmurray> asac: that sounds like a loaded question.  it's pretty good barring one launchpad issue
[01:40] <asac> ok
[01:40] <asac> for me it crashes on firefox-3.0
[01:40] <asac> vino + xulrunner-1.9 work
[01:40] <asac> even bugnumbers -p firefox-3.0 crashes
[01:40] <bdmurray> Okay, I'll look into it
[01:41] <bdmurray> this is from Hardy?
[01:41] <asac> sorry, didn't try xulrunner-1.9 before and thought it was crashing on everything.
[01:41] <asac> because i couldn't imagine why bugnumbers might fail
[01:41] <asac> bdmurray: yes, hardy almost latest
[01:41] <bdmurray> try --parsemode=html
[01:41] <asac> a day old or so
[01:41] <asac> bdmurray: can i use that option everywhere?
[01:41] <asac> e.g. bugnumbers? or just bughelper iteself?
[01:42] <bdmurray> asac: yes, everywhere
[01:42]  * asac tries bugnumbers
[01:42] <bdmurray> there is a problem with the attachments listings in Launchpad or p-l-b's parsing of them
[01:43] <asac> bdmurray: ok so i probably cannot run a full query?
[01:44] <asac> i initially ended up in this because i wanted to search attachments ... like
[01:44] <bdmurray> asac: if you use --parsemode=text and a bug has a bad attachment it'll error out
[01:44] <asac> bughelper -T firefox-3.0 "nsNavHistoryResult" "Navigation Crash" -p firefox-3.0
[01:44] <asac> what are bad attachments? and why does it matter for bugnumbers?
[01:44] <bdmurray> badly formatted that is
[01:44] <asac> do we know what that means? or when that happens?
[01:45] <bdmurray> yes, let me find the launchpad bug
[01:45] <asac> no need to
[01:45] <asac> i just need to workaround right now.
[01:45] <bdmurray> right and --parsemode=html should work around it
[01:46] <asac> ok let me run that query with html
[01:46] <asac> :)
[01:46] <asac> lets see how far we get
[01:46]  * asac wonders how long it will take :/
[01:47] <bdmurray> it worked for me
[01:47] <bdmurray> well, or bugnumbers did
[01:57] <asac> bdmurray: how many hours do you think that query might take?
[01:57] <asac> with nothing cached
[04:05] <alex_mayorga> bdmurray, ping :)
[11:14] <Iulian> Hey
[12:34] <ubuntudemon> Hey. Can I do anything to provide more information to this bug ? https://bugs.launchpad.net/ubuntu/+source/linux/+bug/220640
[12:34] <ubotu> Launchpad bug 220640 in linux "[hardy] iwl3945 + wpasupplicant fails to connect to university network. regression from gutsy (ipw3945+wpasupplicant)" [Undecided,New]
[12:49] <marnanel> ubuntudemon: I don't think so, but it's possible/probable that none of the people dealing with it are on this channel at present (or awake)
[12:49] <marnanel> ubuntudemon: But I wish all my bug reporters were as thorough as that!
[12:49] <james_w> hi marnanel
[12:50] <james_w> ubuntudemon: http://www.intellinuxwireless.org/bugzilla/show_bug.cgi?id=1507 looks similar as well, although the initial reporter had a different key mgmt
[12:50] <ubotu> www.intellinuxwireless.org bug 1507 in WPA & WPA2 "iwlwifi-1.1.19 doesn't associate to WPA-EAP protected network" [Major,Assigned]
[12:54] <james_w> ubuntudemon: I also think there is enough information there that you could file a report upstream.
[12:55] <marnanel> james_w: hi
[13:02] <ubuntudemon> james_w : thanks I will first read through 1507 and 1522 right now. After that I will report a bug upstream if necessary
[13:03] <james_w> ubuntudemon: thanks, that would be very useful.
[13:04] <ubuntudemon> you are welcome. I'm not only helping Ubuntu but also helping myself by doing this. I would like to upgrade to hardy but I can't do that if I can't get on my university network.
[13:11] <ubuntudemon> james_w Is it possible to download newer iwl3945 driver+mac80211+microcode image from intellinuxwireless.org and use it from the live cd ?
[13:12] <james_w> ubuntudemon: probably
[13:12] <james_w> you shouldn't need to reboot to do that, so you should be ok
[13:12] <james_w> as long as you have internet access to get the stuff :-)
[13:17] <ubuntudemon> james_w I have a usb stick here
[13:17] <james_w> ah, that's much easier
[13:17] <ubuntudemon> It's probably bit a microcode error because I followed this and I'm not seeing that kind of errors : http://www.intellinuxwireless.org/?n=fw_error_report
[13:23] <ubuntudemon> james_w I should probably follow : http://linuxwireless.sipsolutions.net/en/users/Download right ?
[13:25] <james_w> I don't know, sorry.
[13:33] <ubuntudemon> james_w I'm first going to report a new upstream bug because I get different error messages
[13:33] <james_w> sounds sensible
[13:36] <ubuntudemon> james_w getting someone to confirm the bug might be hard
[13:36] <james_w> yup, but there's plenty of information, so a developer may see what's wrong, or be able to ask you to do tests to narrow it down.
[13:58] <ubuntudemon> james_w I submitted the bug
[13:58] <ubuntudemon> james_w : http://www.intellinuxwireless.org/bugzilla/show_bug.cgi?id=1658
[13:58] <ubotu> www.intellinuxwireless.org bug 1658 in WEP "[Ubuntu Hardy] iwl3945 + wpasupplicant fails to connect to university network. Worked in Ubuntu Gutsy with ipw3945+wpasupplicant." [Major,New]
[14:00] <james_w> cool, thanks
[14:11] <asac> ubuntudemon: try the driver from linux-backport-modules
[14:12] <asac> it has the scan_capa patch which should fix corner cases for hidden networks
[14:13] <asac> maybe LEAP as well
[14:13] <asac> i don't bother to try upstream driver
[14:13] <asac> s/don't/won't/
[14:13] <asac> james_w: ^^
[14:14] <ubuntudemon> asac : I installed linux-backport-modules-hardy-generic and now I also have led_class as a module but it didn't work
[14:14] <ubuntudemon> asac : thanks for the suggestion
[14:15] <asac> ubuntudemon: if you still have issues, submit the full /var/log/syslog after reproducing the connect failure as a bug against network manager
[14:15] <asac> and point me to the bug
[14:15] <ubuntudemon> asac here's the bug : https://bugs.launchpad.net/linux/+bug/220640
[14:15] <ubotu> Launchpad bug 220640 in linux "[hardy] iwl3945 + wpasupplicant fails to connect to university network. regression from gutsy (ipw3945+wpasupplicant)" [Undecided,New]
[14:15] <asac> but most likely iwlXXXX driver is still to unmature for LEAP, which is afaict a really thing anyway
[14:16] <ubuntudemon> asac : I have never been able to connect to my university network using network manager and I don't know how to enter the same settings
[14:17] <asac> ok. then its not a network-manager related issue.
[14:17] <ubuntudemon> asac : indeed. I have been using wpasupplicant since edgy with ipw3945
[14:17] <asac> sorry ... misread that. usually you can get drivers to work manually as manual configuration can deal with crappy drivers, while network-manager cannot
[14:18] <ubuntudemon> asac : I don't understand why they didn't think of a solution to be able to still use ipw3945
[14:18] <ubuntudemon> (my university network settings are also a bit strange)
[14:19] <asac> ubuntudemon: for ipw3945 you need the regulatory daemon running as well
[14:19] <asac> do you have that?
[14:19] <ubuntudemon> asac : I'm running the livecd and I'm unable to modprobe ipw3945 (FATAL: Module ipw3945 not found)
[14:19] <asac> ok
[14:21] <ubuntudemon> asac : is there anything else I can do to provide more useful information ? Is there any way to use ipw3945 with hardy's kernel ?
[14:22] <asac> ubuntudemon: most likely not on the live cd
[14:23] <asac> unfortunate that noone raised this earlier in development cycle
[14:26] <ubuntudemon> asac yeah really unfortunate.
[14:28] <asac> i have no access to LEAP network. otherwise i would have probably noticed. afaik LEAP is somewhat crappy and outdated.
[14:28] <asac> (not saying that it can be ignored)
[14:29] <ubuntudemon> asac : I'm also gettign some help in #ubuntu-kernel
[14:30] <ubuntudemon> asac : my university's network settings are crappy IMHO
[14:32] <asac> ok hope that -kernel can figure something. only thing you could try IMO is to upgrade to latest wpasupplicant (0.6.x) ... maybe that behaves better
[14:35] <calc> iirc LEAP was a workaround for WEP being crap
[14:35] <calc> both of which are not nearly as good as WPA/WPA2
[14:51] <darius_> I was wondering why LEAP wasn't working ... thought it was just me :)
[15:29] <ubuntudemon> darius_ so you have the same problem ? Do you have the same network settings as I do ? You should come to #ubuntu-kernel
[16:07] <ubuntudemon> If there is nothing else I can try I'm going home and I'll try any new suggestions tomorrow. Thanks everybody for your help.
[16:07] <ubuntudemon> Bye all!
[16:16] <Kirrus> hello, can someone take a look at bug #110387.. its got a patch, but has missed the final freeze deadline, as I didn't pick it up quickly enough (sorry!) .. I think its a candidate for SRU, but I'm not sure of the process the patch needs to go through *before* the release...
[16:16] <ubotu> Launchpad bug 110387 in insight "Insight was accidentally built wrong" [Undecided,Confirmed] https://launchpad.net/bugs/110387
[16:17] <crimsun> at this point, we may as well treat it as part of the SRU process
[16:17] <Kirrus> is there a quick way to tell if a package is in universe or main?
[16:17] <Kirrus> I'll get started on an SRU..
[16:19] <crimsun> Kirrus: sure, via the Launchpad +source page, or apt-cache showsrc, or rmadison -uubuntu
[16:19] <crimsun> oh, do you mean "binary package"?
[16:20] <crimsun> if so, you do have to jump through some hoops
[16:20] <Kirrus> well, I know that the package name is "insight" so I guess I can find it from the lp page.. unless.. guess...
[16:20] <Kirrus> !info insight
[16:20] <ubotu> insight (source: insight): Graphical debugger based on GDB. In component universe, is optional. Version 6.6-1 (gutsy), package size 1649 kB, installed size 4884 kB
[16:20] <crimsun> there.
[16:21] <Kirrus> universe.. cool that works :)
[16:21] <crimsun> should be same for hardy, but you can check
[16:21] <Kirrus> thanks crimsun
[16:21] <crimsun> !info insight hardy
[16:21] <ubotu> insight (source: insight): Graphical debugger based on GDB. In component universe, is optional. Version 6.7.1.dfsg.1-7 (hardy), package size 1696 kB, installed size 5000 kB
[16:21] <crimsun> Kirrus: ultimately it's where the source package is, however, which is why I mentioned those options above
[16:22] <Kirrus> I'll remember them.. thanks :)
[16:31] <bdmurray> greg-g: morningish
[16:37] <bdmurray> crimsun: It seems like bug 219081 should just be an easy config change, do you know what that would be?
[16:37] <ubotu> Launchpad bug 219081 in linux "no 5.1 sound on sound blaster live" [Low,Incomplete] https://launchpad.net/bugs/219081
[16:43] <crimsun> bdmurray: needs more info, namely, which app(s)?
[16:43] <greg-g> bdmurray: late night, so yeah, morning :)
[16:44] <crimsun> bdmurray: a quick test point would be `aplay -Dplug:surround51 /usr/share/sounds/*up.wav'
[16:44] <bdmurray> crimsun: I have the same hardware and problem so I'll give that a try
[16:47] <bdmurray> crimsun: only the KDE_startup.wave came out of all 4 speakers
[16:48] <crimsun> bdmurray: "all 4"?  I thought you wanted 6...
[16:49] <bdmurray> crimsun: I actually have 4.1 but the "rear" 2 get no sound
[16:49] <crimsun> bdmurray: so only the front speakers?
[16:50] <bdmurray> crimsun: right sound from front only with startup.wav but front and rear with KDE-startup.wav
[16:51] <crimsun> bdmurray: amixer set 'Sigmatel 4-Speaker Stereo' unmute ; amixer set 'Sigmatel Surround' 88%
[16:51] <crimsun> bdmurray: then that behaviour is intentional for startup.wav.
[16:56] <bdmurray> crimsun:  Unable to find simple control 'Sigmatel 4-Speaker Stereo',0
[16:56] <crimsun> bdmurray: I'm using his amixer output
[16:56] <crimsun> bdmurray: I'd need your amixer output to see your controls
[17:01] <bdmurray> crimsun: http://pastebin.com/f4115ff4c
[17:05] <crimsun> bdmurray: amixer -c0 set 'Wave Center' 80%; amixer -c0 set 'Sigmatel 4-Speaker Stereo' unmute
[17:06] <afflux> morning
[17:07] <afflux> ideas on bug 220645?
[17:09] <crimsun> ...
[17:09] <crimsun> and there's the culprit: sysv-rc 2.86.ds1-54
[17:09] <crimsun> (from http://launchpadlibrarian.net/13825801/Dependencies.txt)
[17:10] <crimsun> now, why is that person running sysv-rc from Debian?
[17:10] <afflux> that is indeed a good question
[17:11] <crimsun> note that our simplistic solutions of simply requiring sysv-rc (>= 2.86.ds1-14.1ubuntu2) fails horribly
[17:11] <crimsun> solution*
[17:11] <crimsun> Debian does not carry Scott's multiuser change
[17:11] <afflux> crimsun: probably because of the last (now commented) line in sources.list: # deb http://mirrors.kernel.org/debian unstable main non-free contrib
[17:11] <crimsun> perhaps this can be enforced in upgrade-manager?
[17:12] <afflux> not sure how that should be handled. should I just answer with "you're using unsupported debian packages, closing"?
[17:12] <crimsun> e.g., we need sysv-rc (>= 2.86.ds1-14.1ubuntu2), sysv-rc (<< 2.86.ds1-15)
[18:06] <jarlath> I have a bug report with the status New. I now have all the log files needed and steps to repeat etc. But the only other statuses I can see applicable to my triaging are Incomplete, Invalid or confirmed. Should I choose confirmed or is there a way to set it as Triaged?
[18:07] <bdmurray> jarlath: Triaged is available to ubuntu-bugcontrol members only
[18:08] <jarlath> Ah, okay. So will I leave it as new?
[18:08] <james_w> jarlath: is it anything that we could confirm, or is it specific hardware or anything?
[18:08] <bddebian> Boo
[18:09] <jarlath> james_w: yes, it's hardware specific.
[18:09] <james_w> hi bddebian
[18:09] <jarlath> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/219556
[18:09] <ubotu> Launchpad bug 219556 in linux "Speakers do not mute on headphones (Fujitsu-Siemens ESPRIMO M9400)" [Undecided,New]
[18:09] <bddebian> Hello james_w
[18:11] <james_w> jarlath: ah, you're triaging it, I thought you reported it.
[18:11] <jarlath> james_w: Oh, yes. I should have made that clearer :)
[18:16] <crimsun> jarlath: set it to Needs Info, and add me as a subscriber.  I'll triage it further this afternoon.
[18:17] <crimsun> err, I guess Incomplete instead of Needs Info.
[18:18] <jarlath> crimsun: Okay, will do. I'll keep an eye to see what kind of info is missing. Thanks for your help.
[18:18] <crimsun> basically he needs a new stanza for his model; there's nothing in alc262_presets[] to handle his config.
[18:19] <jarlath> Okay. That sounds promising!
[18:43] <afflux> crimsun: what should I do with the update-rc.d bug (sysv-rc from debian)? ie. what status, package etc.
[18:50] <bdmurray> afflux: I'd think update-manager, confirmed, low based off what I read of the scrollback
[18:51] <afflux> bdmurray: okay thanks
[18:51] <bdmurray> I gathered this is something update-manager might be smarter about
[18:52]  * mvo appears on the scene
[18:53] <bdmurray> mvo: somebody had sysv-rc(?) from debian installed and performed a release upgrade
[18:53] <mvo> hm, right
[18:53] <mvo> suprisingly little failures :P
[18:54]  * mvo just looked at the bugreport