=== majestix is now known as majestix_
[03:12] <majestix_> hi my sound carf on a mediona 96640 (snd-hda-intel) module does not work in 8.10
[03:24] <persia> majestix_, My browser's not working now, but there's a special section on the wiki somewhere under https://wiki.ubuntu.com/Bugs/ that explains about the best information to provide with an audio bug, and you'll want to discuss it on #ubuntu-bugs
[03:39] <majestix_> persia. thanks
[06:41] <travisivart> can anyone point me to the intrepid daily iso?
[06:44] <persia> http://cdimage.ubuntu.com/daily-live/current
[06:44] <travisivart> thanks persia
[07:09] <broken1> Quick question, are the fglrx drivers working for 8.10?
[07:35] <ara> morning all!
[08:00] <ara> mvo: After doing a complete update in my laptop running intrepid, the last message showing is "removing linux-headers-2.6.27-4". It has been the same message for 5min
[08:00] <ara> mvo: how long should I wait? ;-)
[08:00] <ara> mvo: where should I look for errors?
[08:04] <mvo> ara: if you upgraded from intrepid to intrepid you may have hit a bug in update-manager (previous interpid version)
[08:04] <mvo> ara: if no activity is shown, you can close the window, the bug is fixed now
[08:04] <ara> mvo: yes, it was intrepid to intrepid, indeed
[08:04] <ara> ok
[08:04] <mvo> ok
[08:05] <ara> mvo: do I kill update-manager directly?
[08:06] <mvo> ara: yes
[08:07] <ara> mvo: thanks :-)
[08:07] <mvo> cheers :)
[08:15]  * ara reboots
[08:25] <ara> morning davmor2!
[08:25] <davmor2> Morning Ara
[08:25] <ara> mvo: question :-) what are the differences between an upgrade from intrepid to intrepid from just an update? (just for the sake of knowledge)
[08:27] <mvo> ara: in a intrepid->intrpeid upgrade (partial) some quirks hanlders are not run (e.g. no xorg.conf update as would be for hardy->intrepid). it will also not rewrite the sources.list (obvisously :) - but it otherwise the same codepath
[08:28] <ara> but why is it an upgrade, and not an update?
[08:28] <ara> mvo: ^
[08:29] <mvo> oh, the terminology here is a bit of a historic problem. apt calls a "update" a refresh of the index files (package lists , source list) and a upgrade everything that gets new packages (and divides into upgrade that do not add/remove packages and dist-upgrades that do)
[08:29] <mvo> so we kind of inherited that
[08:30] <mvo> and in the beginning we did not want to confuse the people knowing apt by using a different semantic for the same words
[08:35] <davmor2> mvo: sorry about yesterday I was longer away than anticipated m6 was not moving coming back :(   I'm going to rerun the upgrade test and if it throws a wobbly again I'll debug it with you.
[08:36] <mvo> davmor2: no worries about that. if you run a new test today, could you please enable network this time just to test a new code path?
[08:36] <davmor2> mvo: no probs
[08:44] <mvo> davmor2: out of curisoty, how do you do the initial installs, do you use something like partimage to speed that up?
[08:46] <davmor2> mvo: I got a 500 gig usb drive everytime I do an install windows, Ubuntu's etc I take a snapshot using partimage from system rescue cd
[08:56]  * mvo nods
=== asac_ is now known as asac
[11:01] <davmor2> mvo_: eject might be useful for jaunty
[11:02] <mvo_> davmor2: absolutely
[11:02] <mvo_> davmor2: (sorry got disconnected)
[11:02] <davmor2> :) it happens :)
[11:25] <davmor2> morning heno :)
[11:26] <heno> morning davmor2 :)
[11:26] <Tallken> helllo
[11:26] <heno> Hi Tallken
[11:27] <Tallken> wazup?
[11:27] <davmor2> Tallken: the sky
[11:27] <Tallken> I just posted a batch of 3 posts in UbuntuForums RFC before I proceed to a proper bug report and got tired xD Had at least two more to fill :P
[11:27] <Tallken> true true :D
[11:31] <Tallken> bah wth, I'll request for comments here as well xD anyone knows of a random early hang during boot with intrepid ibex with a screen garbled as a result?
[11:32] <Tallken> early hang == probably before initramfs use, but can't be sure
[11:33] <Tallken> a friend of mine told me there was some discussion on LKML about something like this in a recent past, however it was supposed to be fixed, I think.
[11:38] <davmor2> Nope
[11:38] <davmor2> but then I don't had xD
[11:39] <Tallken> hum? had what? boot hangs?
=== thekorn_ is now known as thekorn
[12:18] <davmor2> Tallken: is it that your boot stops
[12:18] <davmor2> if so try pressing the ctrl key
[12:20] <Tallken> davmor2: no, the kernel start loading and a few seconds afterwards -- I'd say it doesn't even mount the initramfs image but can't be sure -- the whole text gets garbled and thus impossible to read and the computer hangs.
[12:22] <davmor2> Tallken: When grub starts hit escape.  Goto the kernel line and hit e.  goto the end of the line and knock off the --quite --splash.  This will make the kernel display verbosely what is happening.
[12:22] <Tallken> davmor2: I already do that by default
[12:22] <Tallken> davmor2: it's the kernel text itself, not bootsplash, that gets gerbled
[12:22] <Tallken> *garbled
[12:24] <davmor2> Tallken: If you can get a photo of it and add the image to your bug report.  Also have you tried using safe gfx mode too?
[12:24] <Tallken> safe gfx? like what?
[12:24] <Tallken> novesa? or sth like that?
[12:25] <davmor2> Sorry it's an installed system isn't it D'oh
[12:25] <Tallken> yes it is :)
[12:25] <Tallken> davmor2: you can't read anything at the photo
[12:26] <Tallken> davmor2: nor being in front of the screen
[12:26] <Tallken> not even the times
[12:26] <Tallken> davmor2: I can however check them manually
[12:26] <davmor2> Tallken: that's okay at least it will help with descriptions etc
[12:26] <Tallken> I can before the kernel hangs try to check the times
[12:26] <Tallken> davmor2: ok
[12:26] <Tallken> davmor2: I'm currently compiling the git kernel
[12:26] <Tallken> davmor2: afterwards will test with it
[12:27] <Tallken> davmor2: shall I ping you here once I've news?
[12:27] <davmor2> Sounds odd that it's screwing up the text of the kernel boot :-/ meh
[12:28] <davmor2> can do
[12:28] <Tallken> davmor2: yup... odd indeed
[12:28] <Tallken> as soon as I get my m#$%#$%#% bluetooth dongle working I'll upload the photo
[12:28] <davmor2> :)
[12:29] <Tallken> stopped being detected by bluetooth utils :'(
[12:29] <davmor2> Tallken: did you upgrade or install from cd?
[12:29] <Tallken> upgrade
[12:29] <Tallken> upgrade from alternate CD
[12:30] <Tallken> wth: Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub LOL I expected a manufacturer not this xD
[12:30] <davmor2> Might be a glitch in the upgrade process
[12:31] <Tallken> possibly
[12:32] <davmor2> have you tried running the pc from the rescue/recover mode on either the cd or the grub option?
[12:32] <Tallken> davmor2: it hangs randomly, not always, I'm on that PC currently
[12:33] <Tallken> sorry for not making it clear before :/
[12:34] <davmor2> Try the rescue mode from the cd when you get chance it maybe that it displays correctly in which case it is likely a screwed upgrade
[12:37] <Tallken> davmor2: display what? it either does boot correctly, in case as far as I've noticed, it has no special messages at dmesg or it doesn't boot correctly, hangs and the text is not readable
[12:37] <Tallken> it does boot correctly 9 out of 10 times, more or less
[12:37] <davmor2> Meh sounds more and more like a screwy upgrade :(
[12:38] <Tallken> ok
[13:39] <ara> have a nice weekend, everybody!
[14:19] <jerone_> anyone notice that gnome-sound-recorder is busted ?
[14:21] <davmor2> jerone_: maybe a pulse issue
[14:21]  * davmor2 goes off to have a look
[14:22] <jerone_> davmor2: maybe it's not just an input issue .. the time of the length of the recording is all off
[14:22] <jerone_> davmor2: actually there is no input for the recording also
[14:23] <davmor2> jerone_: what format are you recording in?
[14:23] <jerone_> davmor2: any
[14:23] <jerone_> davmor2: seen it on two seperate machines .. and last night I updated and the problem is still there
[14:24] <jerone_> don't think anyone has tried it out
[14:34] <davmor2> jerone_: confirmed way off
[14:41] <davmor2> jerone_: bug 282316
[16:43] <davmor2> bdmurray: https://bugs.launchpad.net/ubuntu/+source/ndiswrapper/+bug/268625  this bug can be fix-released I believe.  I'm not sure if the new broadcom sta driver covers all though
[16:43] <ubot5`> Launchpad bug 268625 in ndiswrapper "Intrepid: Regression Ndiswrapper is broken by b43 driver again" [Undecided,Incomplete]
[16:44] <bdmurray> davmor2: about your idea yesterday - you were saying when a package is removed from the archive bugs against that package should be closed as won't fix correct?
[16:46] <sbeattie> Hrm, I'm not sure I agree with that: it's possible some bugs will be fixed in previously released versions.
[16:46] <davmor2> Yes if you have a db in lp of the app in the repos everytime an app is removed it automatically say this package is nolonger available in current releases and will not be fixed (kinda thing)
[16:47] <davmor2> sbeattie: not got rid of just a not fixed message that can be altered to fix released or whatever
[16:48] <persia> I usually do that by nominating for the release in which it is being removed, and marking that won't fix.  That way someone else can nominate for another release later if they like.
[16:49] <sbeattie> And sometimes it's really nice to fix a bug in a package that's on its way out of the archive: e.g. bug 281129 for tirc in hardy which got removed in intrepid.
[16:50] <sbeattie> bah, silly bugbots: https://bugs.launchpad.net/ubuntu/+source/tirc/+bug/281129
[16:50] <ubot5`> Launchpad bug 281129 in tirc "[hardy] tirc prerm script has syntax error; causes failure on uninstall" [Low,Triaged]
[16:50] <persia> Especially for an LTS :)
[16:50] <persia> Ooh.  That's especially good to fix.  Dropping from the archive and not letting users uninstall is extra mean.
[16:56] <davmor2> https://bugs.launchpad.net/ubuntu/+source/gst-plugins-bad0.10/+bug/260765 works for me with libdvdcss enabled
[16:56] <ubot5`> Launchpad bug 260765 in gst-plugins-base0.10 "DVD playback does not work anymore" [Medium,Fix released]
[16:56] <davmor2> on 20081017
[16:56] <davmor2> bdmurray: ^
[16:58] <davmor2> sbeattie: persia: could you not simply have an lts flag in the lp db to allow those apps to stay listed until it's end?
[16:59] <persia> davmor2, Why bother?  That changes the schema, which means it takes a while, and delays the fixes for the many existing extremely annoying things about LP.
[16:59] <persia> Easier to use the function already provided, which works.
[16:59] <persia> Also, it's not just about LTS, it's about all supported releases.
[17:00] <davmor2> persia: true.
[17:01] <davmor2> it was only an idea on a way to auto clean some of the older bug reports
[17:02] <davmor2> Right I'm off see you monday
[18:42] <poningru> hey guys I have some issues with intrepid, the power button being pressed shows the logout menu now and there is no way to change it over to the shutdown menu
[18:42] <poningru> also pressing the sleep button does not actually put the laptop to sleep
[18:53] <persia> poningru, I know the first is reported, and I think the second is.  Check LP.
[18:54] <poningru> checking
[18:57] <cr3> anyone happen to know about the NO_REBOOT flag issue?
[20:56] <mattik_> Hello. Testing just Kubuntu beta
[20:56] <mattik_> I tested this konversation
[21:06] <persia> mattik_, It seems to be working for you.
[21:08] <mattik_> yes :)
[21:11] <mattik_> All is working with alternate install, but live session didn't work
[22:13] <sukoshi> hi