[00:07] <jbuncher> apw:  I tried booting one of the kernels and my wireless card is not recognized.  I believe I need the file iwlwifi-3945.ucode to be installed in something like /lib/firmware/newkernel/  Is there something else I need to install, or should I just ln -s to one of my existing kernel firmware directories in /lib/firmare?
[00:07] <apw> jbuncher, yes i would copy that in manually, i have nothing built there.  thanks for your persistance
[00:09] <jbuncher> apw:  No problem, I'm just glad that someone is looking into the bug :)  I'll try rebooting again.
[00:20] <jbuncher> apw:  I still can't seem to get my wireless card to be recognized in those kernels.
[00:21] <apw> jbuncher, getting anything in dmesg relating to it at all?
[00:21] <jbuncher> apw:  I checked, didn't see anything obvious
[00:22] <apw> can you paste in a dmesg from one of them
[00:23] <apw> i will have to think about it tommorrow, am too tired to do think on it further today
[00:23] <jbuncher> apw:  would that be /var/log/messages.0 for the previous boot?
[00:23] <apw> the version should be in the dmesg i think
[00:23] <jbuncher> apw:  sorry, dmesg.0
[00:24] <jbuncher> apw:  I found a dmesg log, I'll attach it to the bug report.  I need to be getting home too anyway.  Thanks for your help though.
[00:24] <apw> will see what else we can come up with tommorrow
[00:32] <jbuncher> apw:  Sounds good.  The dmesg is attached to the bug now.  Have a good night.
[02:03] <btm> should be importance: wishlist -- #205528 (needs-packaging)
[05:42] <dholbach> good morning
[06:57] <maco> asac: you around?
[07:03] <maco> dholbach: hello?
[07:03] <dholbach> maco: hello? :)
[07:05] <maco> dholbach: are you on jaunty?
[07:06] <maco> best case is you have a computer other than the one you're using that's running jaunty
[07:06] <dholbach> yes
[07:06] <dholbach> what are you looking for?
[07:06] <maco> if you configure an interface in /etc/network/interfaces, does NM in jaunty remember to ignore that device?
[07:06] <maco> because NM on here is showing wireless networks when i have wlan1 configured in /etc/network/interfaces
[07:06] <dholbach> I hvae no idea
[07:07] <maco> well i dont think it's *supposed* to
[07:07] <maco> im just wondering if you can reproduce that behaviour
[07:25] <Laibsch> What is the best way to get a bug that I triaged up to the point of providing a verified debdiff against current Jaunty sources on the radar screen of the release managers?
[07:25] <Laibsch> Some team I should subscribe?
[07:26] <Laibsch> Some flag?
[07:26] <Laibsch> something else?
[07:26] <maco> what part of the archive?
[07:26] <maco> main or universe?
[07:26] <Laibsch> can be either
[07:26] <Laibsch> I mean, I triage both main and universe
[07:26] <Laibsch> So, eventually, I will need both
[07:27] <maco> ah ok
[07:27] <maco> well its ubuntu-main-sponsors
[07:27] <maco> (i meant for this package, but whatever)
[07:27] <maco> for main
[07:27] <maco> and ubuntu-universe-sponsors for universe
[07:27] <maco> just subscribe them to the bug
[07:27] <Laibsch> hm, OK
[07:27] <Laibsch> They deal with a lot of stuff, though
[07:27] <Laibsch> IIRC, I had a few things linger for weeks even after subscribing them
[07:28] <maco> it happens
[07:28] <Laibsch> This was not for Jaunty, granted, but a few weeks delay could invalidate the work I did, Jaunty is fast-moving and I'd have to rebase
[07:28] <Laibsch> Plus, it's not that many more weeks until release
[07:28] <Laibsch> I'll add those team to cc
[07:29] <Laibsch> If anybody else knows some other trick, let me know.  Thanks maco
[07:29] <maco> well i suppose you could try to figure out how to poke them and hope they dont get annoyed at you...
[07:29] <maco> Laibsch: any chance you're running jaunty?
[07:29] <maco> (i'm trying to get someone to replicate this bug)
[07:30] <Laibsch> #?
[07:30] <maco> hasnt been posted yet. id like to be sure its not my usual encounter with heisenbugs
[07:31] <Laibsch> yes, I'm running jaunty
[07:31] <maco> the trouble is i have my wireless configured in /etc/network/interfaces.  somehow, network manage still displays available networks for my wireless card. AFAIK, nm is supposed to ignore any manually-configured-in-the-interfaces-file interfaces
[07:43]  * maco digs out other laptop for comparison testing
[07:43] <maco> it'll be *very* interesting if i manage to make a heisenbug migrate from one laptop to another
[07:46] <YoBoY> bug 334207 -> wishlist
[07:47] <maco> marked
[07:48] <YoBoY> good morning :)
[07:51] <Laibsch> maco: I'm very happy with my wifi on Jaunty, more than on Hardy initially and I'm not really willing to fiddle with that, sorry.
[07:51] <maco> ok
[07:52] <maco> i just tried on my other laptop and it doesnt reproduce there. now im wondering if NM is looking at /etc/udev/rules.d/70-persistent-net.rules and going "2 wireless cards are listed, but i cant find one and the other is manually configred...meh, use it anyway"
[07:53] <maco> so im going to see if it still shows up when i remove the old wireless card from the config
[08:02] <Laibsch> maco: I think you're drifting towards a support request
[08:02] <Hobbsee> Laibsch: there's a mail that deals with this.  let me find it
[08:04] <Hobbsee> Laibsch: oh, and we're on irc too, fwiw
[08:04] <Laibsch> ??
[08:04] <Hobbsee> Laibsch: https://lists.ubuntu.com/archives/ubuntu-devel-announce/2008-October/000508.html
[08:04] <Laibsch> you got me confused now
[08:04] <Laibsch> OK
[08:04] <Laibsch> Will read
[08:05] <Hobbsee> (i'm belatedly replying to your "how do I get my bug on the release managers watchlist?" question)
[08:05] <Laibsch> I see
[08:05] <Laibsch> Thanks
[08:05] <Hobbsee> however, the release managers don't automatically sponsor things, so ubuntu-*-sponsors is usually the queue to put it on (although they can if they wish)
[08:05] <Hobbsee> you're welcome
[08:05] <Laibsch> Exactly what I was looking for
[08:13] <maco> my hypothesis failed
[08:13] <Hobbsee> maco: btw, we're on IRC - we're not too hard to poke
[08:14] <maco> Hobbsee: its more of knowing *who* to poke
[08:14] <Hobbsee> maco: that's true.  ~ubuntu-release &/or ~motu-release on launchpad's usually a good start ;)
[08:14] <maco> laserjock and scottk are the ones im totally sure of, and they like to stick to edubuntu and kubuntu respectively
[08:15] <maco> you said "we" though so i guess now you're on the list?
[08:16] <maco> ok so neither weird networkmanager junk i'm experiencing is linked to having 2 interfaces that are not present listed in my udev rules
[08:16] <maco> however, my other laptop exhibits neither of the bugs
[08:17] <maco> i really wish i could get a reproducible bug once in a while
[08:20] <Hobbsee> maco: i released one of the alphas for gutsy, and am still on that list, yes.
[08:21] <maco> by "now on that list" i meant i just put you on my mental list :P
[08:21] <Hobbsee> oh :)
[09:34] <zinzin> hi,
[09:34] <maco> zinzin: well now that youve asked the first thing to do would be to search on launchpad
[09:35] <zinzin> maco: i did, but dont see such a report
[09:35] <maco> ok then file the bug
[09:36] <zinzin> ok, will put it here first, then file a bug later. lets see if anybody knows the problem
[09:36] <zinzin> ﻿﻿i am using 8.10 on GPU i915 Intel. i got the problem when run glxgears, like "﻿Failed to initialized GEM. Falling back to classic". Now OpenGL doesnt run anymore. Anybody knows this problem?
[09:36] <zinzin> ﻿it didnt happen with me before, so perhaps the recent update of xorg is the culprit??
[09:36] <zinzin> i mean glxgears doesnt run anymore
[09:37] <maco> zinzin: run "apt-cache policy xserver-xorg-video-intel" and paste hte Installed: line
[09:38] <zinzin> Installed: 2:2.4.1-1ubuntu10.3
[09:38] <zinzin> maco: is there any way to fall back to older version, to see if that can fix my problem?
[09:38] <maco> ok, now wait and maybe someone else can say "yes i see it too, you're not crazy" and then you guys can file a bug with confirmation
[09:39] <maco> yes, you can install the older one with dpkg -i --force-downgrade
[09:39] <maco> have to find it though
[09:39] <zinzin> maco: then how to know which version to downgrade to?
[09:39] <zinzin> and how about other related packages? need to downgrade, too?
[09:39] <maco> might still have it in /var/cache/apt/archives
[09:40] <maco> maybe. i dont know what all it'd depend on, and im not using 8.10
[09:42] <zinzin> maco: hmm, i find that in /var/cache/apt/archives only 1 package, that has exactly version i am using
[09:43] <zinzin> so it seems i never upgrade it in the first place (?)
[09:43] <maco> or you ahve it set to remove old versions automatically
[10:05] <zinzin> maco: i think i found the problem: the PAE kernel doesnt work with GEM
[10:06] <maco> oh ok
[10:06] <zinzin> so i have to turn off PAE in the compiled kernel
[10:06] <zinzin> the bug was reported upstream
[10:06] <zinzin> https://bugs.freedesktop.org/show_bug.cgi?id=17993
[10:06] <zinzin> i think that is the case. i am recompiling kernel now, to see if the problem is gone
[10:45] <askand> Is it possible that latest inteldriver may fix bug 303011 , info in the last comment
[12:33] <Laibsch> I'm sure DKMS is nice, but I wonder if we're not going to see Ubuntu-supplied kernel modules as a separate package anytime soon (compiled with the help of dkms, I suppose)
[12:33]  * Laibsch really hates to have all that cruft on his laptop just to have a simple module which was packaged before
[15:53] <jbuncher> apw:  still no luck with recognizing my wireless card on those kernels
[15:53] <apw> well thats balls isn't it
[15:53] <jbuncher> apw:  is there a way I can download the source and have it use my current config settings?  Like with make oldconfig?  I've done that before, though I largely forget the steps.
[15:54] <apw> yep, you can slurp down the kernel
[15:54] <jbuncher> apw:  slurp?
[15:54] <apw> copy your current config from /boot/config-<uname -r>
[15:54] <apw> make oldconfig, and then make it
[15:55] <apw> i don't find install works as nice as i might hope
[15:55] <apw> but, that is in theory exactly what my mainline builds did (the second time round)
[15:55] <apw> jbuncher, which of those builds did you test?
[15:56] <apw> (and did it throw that dependancy warning this time?)
[16:01] <apw> jbuncher, btw, this is probabally more appropriate to #ubuntu-kernel, see you over there
[16:02] <jbuncher> apw:  I installed all 3, but I tried booting the 2.6.24.4 build.  No dependency warning this time on any of the installs.
[16:03] <apw> jbuncher, /join #ubuntu-kernel
[16:03] <jbuncher> apw:done
[16:18]  * skorasaurus is away: Away
[16:34] <askand1> If I should file a bug about removing PalmOS from the preferences menu, what package should I file it against?
[17:35] <btm> there is a bug status 'wont fix' but I assume regular users can't access it?
[17:36] <savvas> yes btm
[17:36] <savvas> I think it's reserved for the bug triagers and the coders
[17:41] <bdmurray> Only the ubuntu-bugcontrol team can set a bug's status to won't fix.
[17:41] <btm> is there a process for getting them to look at a bug? subscribe a user? or just leave it for them to stumble across?
[17:43] <bdmurray> you could mention it here ;-)
[17:43] <btm> sure, just didn't want to spam over all these join/parts ;)
[17:43] <btm> https://bugs.launchpad.net/ubuntu/+source/libpgsql-ruby/+bug/290648
[17:46] <mrooney> For a bug that is new in Jaunty and gets fixed with an update, that gets marked Fix Released right?
[17:47] <charlie-tca> btm: done
[17:47] <MrKanister> mrooney: Yes, if the fix made it to an Ubuntu release the bug that belongs to the package can be set to "fix-released"
[17:48] <bdmurray> If you definitively know the cause and fix
[17:49] <bdmurray> If it was magical I'd prefer it became Invalid
[17:49] <mrooney> MrKanister: well Jaunty isn't released yet, hence the question
[17:50] <mrooney> bdmurray: yeah it is narrowed down to a specific commit in the source package so I'll do released, thanks!
[17:50] <MrKanister> mrooney: But the fix is in Jaunty...so in the jaunty release :)
[17:51] <MrKanister> The final release does not have to be released to mark a bug as fix releasd
[17:52] <mrooney> really, I thought we did Fix Committed in that case for some reason
[17:54] <MrKanister> The bugsquad usually uses "fix commited" if the bug has been fixed in the upstream project, but an updated package is not yet in Ubuntu
[18:07] <btm> this should be wontfix for ubuntu (gems pkg drama) and fixed upstream [or not] (debian) https://bugs.launchpad.net/ubuntu/+source/libgems-ruby/+bug/244742
[18:08] <DaemonFC> #334476
[18:08] <DaemonFC> hmmm
[18:08] <DaemonFC> 334476
[18:09] <DaemonFC> does the bot not bring that up anymore?
[18:09] <charlie-tca> bug 334476
[18:09] <DaemonFC> ahhh
[18:09] <DaemonFC> ty
[19:10] <calc> dtchen: ping
[19:11] <calc> dtchen: is AlsaInfoOutput something you want lots of data points for? I was considering bringing it up at the desktop meeting to have everyone gather data for it...
[19:14] <calc> dtchen: if i read the email correctly this is just for known broken setups, but I am not certain...
[20:38] <bdmurray> sbeattie: do you recall where update-manager finds the new upgrade tool for devel releases?
[20:38] <bdmurray> eh found it
[20:44] <sbeattie> bdmurray: dists/jaunty/main/dist-upgrader-all/current or something else?
[20:45] <bdmurray> sbeattie: that's the one I always think its in pool for some reason
[20:45] <bdmurray> I'm looking at bug 328452
[20:45] <bdmurray> some how the default is Y instead of N
[20:55] <bdmurray> Okay, I got it
[21:17] <carlFK_lt> pidgin crashed - gdb bt: http://dpaste.com/1531/
[21:17] <carlFK_lt> is this worth reporting on lp?
[21:48] <carlFK_lt> now with debugsym, kinda http://dpaste.com/1555/
[22:19] <jbrinkmann> Hi. What would be correct way to handle bug 330067 ? There is no Google Earth package which caused the trouble.
[22:20] <maco> well it's x's problem, not google earth's so it's properly assigned
[22:20] <jbrinkmann> ok
[22:20] <jbrinkmann> thx
[22:46] <seb128> ogasawara: hi, could you get somebody to look at bug #197762? it's open for several cycle and seems to get quite some users frustrated by the lack of anybody triaging or replying or considering the bug