[00:50]  * BUGabundo /usr/local/bin/xfcre76 BUGabundo | tee /dev/sleep
[03:10] <dtchen> bdmurray: as usual, #409819 is one of those now-useless bug reports
[03:10] <dtchen> bdmurray: it needs some serious love, ideally constrained to the reporter's precise hardware
[03:19] <dtchen> bdmurray: no, they very much are for that bug report.
[03:19] <dtchen> bdmurray: it's quite possible that the bug is currently incorrectly affecting pulseaudio
[03:21] <dtchen> bdmurray: ideally I need Andres to reproduce this symptom using the 20061026.2 daily-live, and I need his apport-collect -p alsa-base info. From there, we can determine whether it's a regression in linux, and if so, whether installing linux-backports-modules-alsa-karmic resolves it
[03:21] <dtchen> err, 20091026.2, of course
[03:22] <dtchen> not three years ago ;-)
[03:23] <dtchen> bdmurray: does that help clarify the murkiness?
[03:28] <bdmurray> dtchen: yes, I think so
[03:40] <VXxed> Is anyone available that can help me with my laptop fan issue?  I have it fully documented here: http://ubuntuforums.org/showthread.php?t=1300733
[03:52] <VXxed> Is anyone even in here..?
[03:55] <Hobbsee> yes, but most people are asleep now
[03:59] <VXxed> Blargh.
[03:59] <VXxed> And I'm never online earlier.
[03:59] <VXxed> Well, rarely.
[09:42] <CryingFreeman> Hi, there! I registered a bug with the 2.6.31-14 kernel. The 2.6.31-11 kernel boots, but not the -14 version. I figured that was an ubuntu problem and not an upstream issue? https://bugs.launchpad.net/bugs/461737
[09:42] <ubot4> Launchpad bug 461737 in linux "Kernel 2.6.31-14-generic does not boot" [Undecided,New]
[12:45] <Chorca> any protocol for when a bug is labeled a duplicate of a private bug?
[12:50] <thekorn> Chorca: I think this info should be in the activity log of the bugreport
[12:50] <thekorn> there is a link to this page at the bottom of the page,
[12:51] <thekorn> close to the last comment
[12:55] <Chorca> just says it's been marked as a duplicate
[12:55] <Chorca> https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/461690
[12:55] <ubot4> Chorca: Error: This bug is private
[12:56] <Chorca> the bug it was marked as a duplicate of is private
[14:30] <bddebian> Boo
[17:14] <ikt> -_-
[17:14] <ikt> Oct 28 03:43:11 ikt-desk bonobo-activation-server (ikt-14421): could not associate with desktop session: Failed to connect to socket /tmp/dbus-dDE0RcgFZf: Connection refused
[17:14] <ikt> that is bad
[17:30] <ikt> keyserver down?
[18:41] <VXxed> Hey, is anyone here who can help me with what I think is an acpi issue?
[18:42] <davmor2> VXxed: try #ubuntu or #ubuntu+1
[18:42] <VXxed> Alright
[18:51] <VXxed> Mmf.  As useful as ever.
[18:52] <hggdh> VXxed: I have a bit of time now
[18:52] <VXxed> Awesome, you're still around
[18:53] <VXxed> Alright, so since you last gave me advice
[18:53] <VXxed> I boot into grub and realized that I had no idea how to do anything there, BUT I also noticed that the fan was on
[18:53] <VXxed> Perfectly.
[18:53] <VXxed> And it turns off as soon as grub switches out into Ubuntu
[18:54] <hggdh> ok. First thing we need is to look at the boot log -- please pastebin the output of 'dmesg'
[18:55] <VXxed> One sec, lemme log into irc on the laptop itself
[18:56] <VXxed> It seems like there's more info than scrolling space.  Am I right in that?
[18:58] <hggdh> VXxed: 'sudo apt-get install pastebinit'
[18:58] <hggdh> then 'dmesg | pastebinit' and write here the resulting URL
[18:58] <VXxed1> Gotcha
[18:59] <VXxed> Sorry by the way for not knowing the basics, I'm just trying to get by for now
[18:59] <VXxed1> http://pastebin.com/f2aae15de
[19:09] <VXxed1> hggdh, so what do you think?
[19:09] <hggdh> VXxed: sorry, got drawn on another issue. Looking at it now
[19:10] <VXxed> No problem at all
[19:10] <hggdh> VXxed: this is a laptop? With 8 cores?
[19:10] <VXxed> ..No o_O;
[19:10] <VXxed> This is a T4020D tablet laptop from fujitsu
[19:11] <VXxed> Single core 1.73ghz
[19:11] <hggdh> ah
[19:11] <VXxed> http://reviews.cnet.com/tablet-pcs/fujitsu-lifebook-t4020d-tablet/4507-3126_7-31518031.html?tag=mncol;psum
[19:13] <hggdh> VXxed: a quick look does not show any boot errors, at all
[19:14] <hggdh> and more to the point, no acpi errors
[19:14] <VXxed> That's...really weird.
[19:14] <VXxed> Because as soon as Ubuntu boots out of grub, the very second, the fans shut off.
[19:15] <VXxed> And only turn on again at extreme heats where it's almost too late to be of any use
[19:16] <VXxed> Which I'm guessing is because the sensors don't pick up any temperatures
[19:17] <hggdh> hum.
[19:17] <VXxed> hggdh: I stumbled upon a link two days ago where a guy had a similar issue in arch linux, which he fixed by correcting his DSDT table..and I found an ubuntu-specific guide in the wiki for fixing it
[19:17] <VXxed> But that looked like it was really far into the software core, so I didn't want to start messing around with superior approval
[19:17] <hggdh> this *might* work, if there is a ACPI-related issue. It was/is common for manufacturers to put out crappy ACPI code
[19:18] <hggdh> you could try it, if the DSDT is for the same machine
[19:19] <VXxed> The link was for reconfiguring ones own
[19:19] <VXxed> So it might work?
[19:19] <VXxed> Here, lemme send you a link
[19:20] <VXxed> http://ubuntuforums.org/showpost.php?p=8166923&postcount=7
[19:23] <hggdh> it might. The problem is to understand what the code does. This is where a the acpi.info link I gave you might help
[19:23] <VXxed> 700 pages of documentation though..sweet jesus.  I didn't even know where to start reading
[19:24] <hggdh> :-)
[19:24] <hggdh> it will get worse...
[19:25] <VXxed> Wouldn't it technically be possible to look at a windows acpi for my laptop and see where it's picking up access to the fans?
[19:25] <hggdh> there are some packages dealing with sensors, like lm-sensors
[19:25] <hggdh> VXxed: the ACPI (i.e., the DTDT) is the same
[19:25] <VXxed> Erm, not sure if I related my findings on that to you
[19:25] <VXxed> http://ubuntuforums.org/showthread.php?p=8176017#post8176017
[19:25] <VXxed> Here's my whole thing
[19:26] <VXxed> Post #3 deals with lm-sensors
[19:31] <hggdh> yes. All you need to modprobe is i2c-i801, and adm1021
[19:31] <hggdh> you do not seem to have smartbatt
[19:31] <VXxed> But you saw what happened when I tried to run sensors :\
[19:32] <hggdh> yes. modprobe these two, and try sensors again
[19:32] <VXxed> Alright, lemme boot it back up
[19:32] <VXxed> I try not to keep it on for more than half an hour to an hour..get worried
[19:33] <hggdh> VXxed: you do not need to reboot
[19:33] <hggdh> load the modules, and try sensor again
[19:33] <hggdh> ah. Sorry
[19:33] <VXxed> Yep
[19:33] <VXxed> I just turned it off a little while ago
[19:36] <VXxed1> ronen@vxtablet:~$ sudo modprobe adm1021
[19:36] <VXxed1> [sudo] password for ronen:
[19:36] <VXxed1> ronen@vxtablet:~$ sudo modprobe i2c-i801
[19:36] <VXxed1> ronen@vxtablet:~$ sensors
[19:36] <VXxed1> lm84-i2c-5-19
[19:36] <VXxed1> Adapter: SMBus I801 adapter at 14e0
[19:36] <VXxed1> Board Temp:   +0.0°C  (low  =  +0.0°C, high =  +0.0°C)
[19:36] <VXxed1> CPU Temp:     +0.0°C  (low  =  +0.0°C, high =  +0.0°C)
[19:36] <hggdh> VXxed: what version of Ubuntu?
[19:38] <VXxed1> 9.10
[19:38] <VXxed1> Updating from 9.04 was the first thing I did to try to fix it..
[19:38] <VXxed1> Ironically, it shunned me from essentially all help.  Awesome :|
[19:41] <hggdh> VXxed: this, then, sounds like a real bug. I think you had one opened for this, did you not?
[19:42] <VXxed1> Indeed I did
[19:43] <VXxed1> But it would be good if you would look it over and see if there's anything I need to add
[19:43] <hggdh> bug #?
[19:43] <VXxed> https://bugs.launchpad.net/ubuntu/+bug/461675
[19:43] <ubot4> Launchpad bug 461675 in ubuntu "Fans not spinning up..seemingly no ACPI information loaded" [Undecided,New]
[19:43] <VXxed> I'm adding the link to the boot log
[19:43] <hggdh> attach the boot log, it is better
[19:44] <VXxed> Mmm, should I copy from the website and make a .txt?
[19:44] <hggdh> also, attach the output of running sensor-detect, and the sensor run
[19:44] <hggdh> yes, make it a txt
[19:44] <hggdh> brb
[19:44] <VXxed1> Go right ahead
[19:58] <VXxed> hggdh: Should I include anything else, like uname -a or anything of that sort?
[20:05] <ikt> anyone know where the config file is for gnome-system-log in karmic?
[20:15] <hggdh> VXxed: I do not think so
[20:15] <VXxed> Oh.  Well, I'm adding uname -a, sudo lspci -vvnn, and sudo dmidecode
[20:15] <VXxed> Because https://wiki.ubuntu.com/DebuggingACPI said so
[20:15] <VXxed> For filing bug reports
[20:20] <VXxed> Should I assign it to any specific package and/or person?
[20:21] <dtchen> please do not assign bugs to anyone unless explicitly requested by the person.
[20:21] <VXxed> Gotcha
[20:22] <VXxed> Just making sure
[20:30] <VXxed> Thank you for all your help hggdh.  I'm glad someone was able to help me out with it...who knows where I'd be right now
[20:35] <hggdh> welcome
[20:36] <ikt> https://bugs.launchpad.net/ubuntu/+source/gnome-utils/+bug/374320 <- do we send this upstream to debian ?
[20:36] <ubot4> Launchpad bug 374320 in gnome-utils "Gnome System Log Complains About btmp log permissions" [Low,Confirmed]
[20:36] <ikt> because the help and man pages suggest it has been changed
[20:39] <seb128> ikt, you can send it to GNOME if you want
[20:39] <ikt> the thing is that it says in the man page the config file is
[20:39] <seb128> but I think there is already a bug about not displaying errors about logs not readable there
[20:40] <seb128> what?
[20:40] <ikt>  /etc/syslog.conf being the config file
[20:40] <ikt> ah ok
[20:40] <ikt> but /etc/syslog.conf doesn't exist locally
[20:40] <seb128> the config file is what?
[20:40] <ikt> for gnome-system-log
[20:41] <seb128> what is your issue exactly.?
[20:41] <ikt> there's no way to change any of the options
[20:41] <ikt> it's just plain trying to read all the log files
[20:41] <seb128> what are you trying to change?
[20:41] <seb128> right, which is fine
[20:41] <seb128> it should just ignore the ones which are not there or readable
[20:41] <ikt> yeah
[20:42] <ikt> that sounds better than what I was chasing
[20:43] <ikt> cheers :)
[20:44] <seb128> ikt, https://bugzilla.gnome.org/show_bug.cgi?id=567169
[20:44] <ubot4> Gnome bug 567169 in logview "could not open files error displayed for no good reason" [Normal,Unconfirmed]
[20:44] <seb128> ikt, see that bug
[20:45] <ikt> yeah that's the exact same bug I was on :D
[20:45] <seb128> ok good
[21:53] <BUGabundo> howdy
[22:51] <ZachK_> hello all
[22:58] <alex-weeej> anyone know of USB Audio working on amd64?
[23:19] <ZachK_> alex-weeej, hmmm not sure
[23:20] <alex-weeej> ZachK_, tested a Behringer UCA202 and it failed on 3 different amd64 systems but worked on one of the same ones running i686 jaunty
[23:20] <alex-weeej> class compliant with no firmware
[23:20] <alex-weeej> absolutely gutted
[23:20] <alex-weeej> we were going to use it for our streaming server
[23:21] <ZachK_> alex-weeej, then i would say usb audio doesn't work...
[23:27] <ZachK_> bdmurray, help please..
[23:28] <bdmurray> ZachK_: with what?
[23:28] <ZachK_> bdmurray, how am i supposed to triage bugs if i can't set the importance of a bug
[23:28] <ZachK_> which is part of triaging
[23:29] <bdmurray> ZachK_: you can change the status of bugs after investigating them and if you find one that you need the importance set for you can ask someone in this channel
[23:30] <ZachK_> bdmurray, oh ok...i'm just trying to get into the bug control team which says that you need to have a list of triaged bugs...
[23:31] <bdmurray> ZachK_: it's possible to perform bug triage without setting the Triaged status or importance
[23:31] <ZachK_> bdmurray, ok...well i shall mail in my application then...will you be the one to review it?
[23:32] <hggdh> any of us will review it, ZachK_
[23:33] <hggdh> usually, at least two
[23:33] <bdmurray> heh
[23:34] <ZachK_> now how do i keep a list?
[23:34] <hggdh> well. You can write down the bugs, or keep the list in a draft email
[23:34] <ZachK_> ok..just making sure
[23:35] <hggdh> please be sure to include what is the importance you would give to each of them, and why
[23:37] <hggdh> ZachK_: the idea is to show us those bugs you consider the best work you have done on triaging. Please keep that in mind