[02:30] <sponix> http://www.timhardy.net/wordpress/bytopic/howto/             .... This seems to be my bug with k3b killing my DVD Drive after it burns the first DVD, and the DVD Drive failing to respond until reboot, anyone know if there is work being done on it ?
[02:30] <hggdh> sponix, check the bugs opened against k3b
[02:32] <sponix> searched them at launchpad, didn't find anything right off
[02:32] <hggdh> you should then open a bug for it
[02:33] <hggdh> or check upstream
[04:34] <rraj-be> Hello everyone :) i like to contribute in bug fixing. . I am good in c-programming. . Where can i start contributing
[04:36] <pwnguin> rraj-be: well, stuff tagged with core dumps and regression make sense
[04:36] <sponix> hggdh:  filed a bug report on it, if you want to see it ?
[04:37] <pwnguin> manl why do people do that?
[04:47] <rraj-be> >	Hello everyone :) i like to contribute in bug fixing. . I am good in c-programming. . Where can i start contributing
[05:09] <pwnguin> rraj-be: well, stuff tagged with core dumps and regression make sense
[05:10] <rraj-be> :) but i cant get you clearly
[05:10] <pwnguin> bugs tagged regression should be simple to write a patch for
[05:11] <pwnguin> https://bugs.edge.launchpad.net/ubuntu/+bugs?field.tag=regression
[05:12] <pwnguin> that one has a list of bugs where the software used to work, but doesn't anymore
[05:13] <pwnguin> https://bugs.edge.launchpad.net/ubuntu/+bugs?field.tag=apport-crash <-- this one is a list of bugs that crashed
[05:13] <rraj-be> k
[05:14] <rraj-be> how can i get through  these things and start patching
[05:14] <rraj-be> is there any good guide to start in this
[05:14] <pwnguin> the first can be solved by replicating the bug with cvs builds between working and broken, the second can be fixed by replicating the bug in a debugger
[05:15] <pwnguin> I don't think we do
[05:15] <pwnguin> we've got pretty good docs on testing triaging and committing fixes
[05:16] <pwnguin> but surprisingly light on the intellectual heavy lifting, as far as I can tell
[05:18] <rraj-be> k
[05:18] <sponix> rraj-be:  https://wiki.ubuntu.com/HelpingWithBugs https://help.ubuntu.com/community/ReportingBugs
[05:18] <rraj-be> should i have any debugger installed
[05:18] <pwnguin> rraj-be: gdb is your debugger
[05:18] <sponix> https://wiki.ubuntu.com/Bugs/HowToFix
[05:19] <pwnguin> sponix: all of that has a huge hole in it
[05:19] <pwnguin> 1. find and replicate a bug
[05:19] <pwnguin> 2. ???
[05:19] <rraj-be> gdb. . is it available in default ubuntu
[05:19] <pwnguin> 3. submit a patch
[05:19] <pwnguin> 4. profit!
[05:19] <rraj-be> or should i install it now
[05:19] <pwnguin> install it now
[05:21] <rraj-be> replicate a bug   what does replicating mean
[05:21] <sponix> https://bugs.launchpad.net/ubuntu/+source/k3b/+bug/250206
[05:21] <sponix> that is even my own bug that you can work on ;)
[05:21] <pwnguin> rraj-be: it means to make the bug happen for yo
[05:21] <pwnguin> u
[05:22] <pwnguin> like if a program crashes, but you can never get it to crash
[05:22] <pwnguin> you're stuck
[05:23] <rraj-be> but i need continoues help please
[05:23] <pwnguin> ?
[05:27] <pwnguin> I donno. #ubuntu-devel or #ubuntu-motu might be a better place, but they might also just punt you
[05:27] <rraj-be> i am just looking after the links
[05:27] <rraj-be> sorry guys
[05:27] <rraj-be> i am Away for a short as i followed links given by you
[05:47] <snadge> automatic screen dimming on battery is broken.. can anyone verify before i report? :P
[05:48] <snadge> the problem is if you have your brightness already set to minimum with this option enabled in the power settings
[05:48] <snadge> if you leave your laptop idle for a while, then go to use it.. it cranks the brightness up
[05:49] <snadge> it should only turn the brightness back up to the level you set it at.. so if it was at minimum, it should just stay minimum
[06:00] <nickellery> rraj-be, this might help  http://youtube.com/watch?v=SAxFpKBG-bU
[06:03] <rraj-be> sure
[06:03] <rraj-be> i will take a look on it
[06:26] <snadge> nobody test screen dimming for me? :(
[06:27] <snadge> or is it all about intrepid now.. nobody cares about hardy anymore
[06:27] <pwnguin> oh, i assumed it wa intrepid ;)
[06:27] <pwnguin> was
[06:30] <snadge> i should probably ride the latest dev release, do testing report bugs etc.. except i actually use ubuntu for daily work/use
[06:38] <pwnguin> snadge: what i do is have three partitions: a stable install, a dev install and a shared home dir between them
[06:41] <pwnguin> i think to install it, i resized the original install, made two new partitions and installed to them, clean out the original partition except for home, made sure the UIDs matched, then upgraded one
[06:43] <greg-g> warning, be careful with newer versions of programs reconfiguring their settings.  Doesn't happen often, but in Hardy dev Rhythmbox changed its database so when I booted into Gutsy it couldn't read it (not backwards compatible)
[06:53] <snadge> is wireless support ever going to get a real facelift?
[06:55] <snadge> installed a usb netgear 11g thing.. no native driver, fine.. so i install ndiswrapper, and then copy the drivers off the cd that came with it.. great, but then i configure it manually with iwconfig etc
[06:57] <snadge> and this laptop.. the madwifi driver that comes with it doesnt work.. but if you disable those drivers from hardware manager, install the madwifi-hal, from source.. it works, again manually configured from command line
[06:57] <greg-g> snadge: you're barking up the wrong tree
[06:57] <greg-g> ;)
[06:58] <snadge> im just asking from the perspective of people using/working on intrepid
[06:58] <snadge> whether there are any plans to make installing/configuring wireless any easier
[06:59] <greg-g> snadge: I mean that we don't have control over much of that. it is the wireless card manufacturers that need to change they way they look at drivers and linux support.  we can't do much with a broken system.
[06:59] <snadge> or am i missing something that already works
[06:59] <snadge> ok how about simplifying the ndiswrapper case
[06:59] <greg-g> of course "we" want to make using your wireless card easy, but "we" are hampered by your wireless cards manufacturer
[07:00] <snadge> and maybe attempting to create a database that seperates ndiswrapper type devices from ones which are natively supported
[07:00] <greg-g> if they are natively supported they are natively supported and you don't have to worry about anything like ndiswrapper
[07:01] <greg-g> if they don't work it is most likely caused by the fact that the manufacturers do not release drivers for linux. period.
[07:01] <snadge> ok sure.. i just got burned in both cases.. one, if its not supported.. the installation of ndiswrapper is not overly painful, but not very friendly either
[07:01] <greg-g> yeah, I've been burned myself from the processes with a crappy hp laptop
[07:01] <snadge> and in the case of where it is supported by linux.. its in an experimental release of a forked driver, thats not included with ubuntu
[07:02] <greg-g> well, because in your contrived exampled it is experimental, not suitable for release ;)
[07:02] <snadge> im not really complaining.. in both cases, i was able to get it working relatively simply.. from the perspective of an experience debian user of many years
[07:02] <Hobbsee> did you find ndisgtk?
[07:03] <Hobbsee> that's certainly helped
[07:03] <greg-g> of course, file bugs about your specific hardware not working with the linux dev team, and see what can be done
[07:03] <snadge> but im thinking a gui for ndiswrapper would be nice
[07:03] <snadge> maybe someone has already done that
[07:03] <greg-g> I believe that is what Hobbsee just referenced
[07:03] <snadge> ahh ok
[07:03] <Hobbsee> snadge: you mean ndisgtk, which is included on the cds, like ndiswrapper, but isn't installed by default?
[07:04] <snadge> ahh i see.. i thought there would be something as such
[07:04] <Hobbsee> that being said, ndiswrapper and development versions together are insane :(
[07:04] <snadge> well maybe that package should be made more obvious that it can be installed.. kind of like restricted devices manager
[07:04] <greg-g> also, to answer your original question of whether wireless support will 'get a facelift" yes. it just takes time as we are working from a very handicapped position w.r.t. drivers
[07:05] <Hobbsee> and nm should (and mostly does) "just work" once the device si recognised.
[07:05] <snadge> maybe something like "a wireless device has been detected for which there are only windows drivers for which can be used by ndiswrapper.. do you want to enable this?"
[07:05] <snadge> yeah
[07:06] <Hobbsee> that would be ncie.  propose a patch to jockey?
[07:06] <snadge> the same framework could be used to detect devices which are supported by linux.. on experimental drivers
[07:06] <snadge> which arnt in tree
[07:07] <snadge> a lot of work in the case of the latter though
[07:08] <Hobbsee> so, solve the nm one first, then work on that :)
[07:08] <Hobbsee> er, ndiswrapper one, not nm one
[07:08] <snadge> well as far as free drivers go.. its pretty easy, theres only really madwifi and prism
[07:09] <snadge> i was burned by madwifi, because theres actually 3 drivers now
[07:09] <snadge> madwifi, madwifi-hal and ath5k
[07:09] <Hobbsee> stupid question, but i assume you had the restricted modules installed.
[07:10] <Hobbsee> that made my old madwifi card wrok
[07:10] <snadge> yeah.. it comes with madwifi driver
[07:10] <snadge> i had to blacklist that in hardware devices (disable)
[07:10] <snadge> then install madwifi-hal from source
[07:10] <Hobbsee> ah, so yours wasn't a nice card.
[07:11] <snadge> 5007.. or 242x.. windows doesnt even have a 64bit driver for it
[07:11] <snadge> thats the other complication
[07:11] <snadge> when i told the madwifi devs that i wanted to use it in ad-hoc mode with wep.. they were like, good luck
[07:12] <snadge> after stuffing around for hours i found a way to make it work.. you have to create the device in managed mode, enable wep.. destroy the device, recreate it in adhoc-mode, re-enable wep..and then it works ;)
[07:12] <Hobbsee> ick.  :)
[07:13] <snadge> so i guess the short of it is.. work in madwifi is ongoing, some of these newer chipsets have only very recently received any support
[07:14] <snadge> its unrealistic to expect ubuntu to support them at this stage
[07:15] <Hobbsee> but a patch would certainly be welcome to make jockey understand ndiswrapper, and pop up nice dialogs, etc, for it, if you're in a writing mood.
[07:18] <snadge> i should.. my motivation would be helping fix bug #1 ;)
[07:18] <Hobbsee> then get to it :)
[13:16] <rraj-be> Hello everyone   i am starting with bug fixing.
[13:16] <rraj-be> I am just starting and which type of bugs should i try at first.
[13:16] <rraj-be> how can i start with that
[13:34] <Hew> rraj-be: I started with packages I was familiar with, as well as picking some from the new+undecided list
[13:35] <rraj-be> familiar means by working or by seeing the code
[13:35] <Hobbsee> packages that you've used before
[13:35] <Hobbsee> and are familiar with
[13:35] <Hew> rraj-be: not necessarily; I'm not a developer and (mostly) never look at code
[13:35] <Hew> yes, what Hobbsee said :-)
[13:36] <rraj-be> :)
[13:36] <rraj-be> sure
[13:36] <Hew> rraj-be: have you joined ubuntu-bugsquad? https://wiki.ubuntu.com/BugSquad
[13:36] <rraj-be> yes
[13:36] <Hew> good :-)
[13:37] <rraj-be> i want to work in bug fixing but cant get started. . looking for a good guide or practical  guide
[13:44] <Hew> Hey guys, I just wanted to check that it was ok to mark this invalid due to the expected dependency issues of a dist-upgrade to Intrepid at this time (bug #249329)
[13:47]  * Hobbsee waits for teh bug to load
[13:47] <Hobbsee> Hew: better to figure out what died, then send the bug to that package.
[13:48] <Hew> Hobbsee: From the logs, it was nvidia-glx (blacklisted)
[13:48] <Hobbsee> (if you don't, it may not be found again before release)
[13:50] <Hobbsee> Hew: modifying.
[13:50] <Hobbsee> (sorry to pinch your bug, but it's easier than explaining :)
[13:50] <Hew> Hobbsee: haha, no worries, thanks :-)
[13:51] <Hew> I guess I'll have to find another to finish off my 5-a-day :P
[13:52] <Hobbsee> Hew: hehe, yeah.  although it's double on sundays, anyway.
[13:52] <Hobbsee> have a look now :)
[13:52]  * Hobbsee bumps the importance on it
[13:53] <Hew> ok yep
[13:54] <Hobbsee> i wonder if that should be marked as nvidia-glx too
[13:54] <Hew> I would have thought this had been reported.. looking for dupes
[13:54] <Hobbsee> !info nvidia-glx
[13:54] <Hobbsee> ah, it's lrm.
[13:55] <Hobbsee> Hew: it would be really nice if you'd go thru the apt bugs, btw :)
[13:55] <Hobbsee> they'd be fun
[13:56] <Hobbsee> most of them are probably transient problems, or otherwise unreproducable
[13:57] <Hew> yea I'll have a look through them. I find them a bit confusing atm, so it should be good experience.
[13:57] <Hobbsee> update-manager just looks evil
[13:57] <Hew> ah, looks like the dupes are coming in fast (bug #249612)
[13:58] <Hobbsee> ah yes, that'll be a dupe
[13:59] <Hobbsee> found another one
[13:59]  * Hobbsee marks them both
[14:00] <Hew> haha, racing me to it..
[14:00] <Hobbsee> there's probably a few bugs here that are a dupe of what i reported, too
[14:01]  * Hobbsee wtf's
[14:01] <Hobbsee> https://bugs.edge.launchpad.net/ubuntu/+source/update-manager/+bug/99043
[14:01] <Hobbsee> is that trevhino's son, or something???
[14:02] <Hew> huge...
[14:02]  * Hobbsee curses at beryl.
[14:02] <Hew> that one is edgy anyway
[14:03] <Hobbsee> anything that has beryl in it can be marked as won't fix, if it looked like it failed due to beryl.
[14:03] <Hew> yep ok
[14:03] <Hobbsee> we don't support third party repository crack.
[14:03] <Hobbsee> anything that's not reproducible from edgy, likewise.
[14:04] <Hew> yep yep
[14:04] <Hobbsee> hmmm.
[14:04] <Hobbsee> i wonder if mvo wants reports from third party repositories that have bombed otu.
[14:04] <Hew> Hobbsee: btw are you sure bug #70195 is a dupe? it was reported ages ago on dapper
[14:05] <Hobbsee> Hew: by the last comment
[14:05] <Hobbsee> either that, or i'll mark it invalid, due to berylcrack.
[14:06] <Hew> ok
[14:08]  * Hobbsee grumbles at triagers.
[14:08] <Hobbsee> why, oh why, is it the fault of the upgrader if nvidia-glx-dev has incorrect conflicts/replaces?
[14:09]  * Hobbsee pokes tselliot to come here and help with sorting out his software bugs.
[14:10] <Hobbsee> tseliot: a few of us are looking at update-manager bugs.
[14:11] <tseliot> Hobbsee: for Intrepid?
[14:11] <Hobbsee> looks like a fair few are due to nvidia 3rd party stuff, which seems to be caused by any of automatix, envy, and beryl.
[14:11] <Hobbsee> want to help?  :)
[14:11] <Hobbsee> well, general triage.
[14:11] <tseliot> sure, why not
[14:11] <Hobbsee> botched upgrades due to nvidia stuff
[14:11] <Hobbsee> https://bugs.edge.launchpad.net/ubuntu/+source/update-manager?field.searchtext=nvidia-glx&orderby=date_last_updated&search=Search&field.status%3Alist=NEW&field.status%3Alist=INCOMPLETE_WITH_RESPONSE&field.status%3Alist=INCOMPLETE_WITHOUT_RESPONSE&field.status%3Alist=CONFIRMED&field.status%3Alist=TRIAGED&field.status%3Alist=INPROGRESS&field.status%3Alist=FIXCOMMITTED&field.assignee=&field.bug_reporter=&field.omit_dupes=on&field.has_patch=&
[14:11] <Hobbsee> field.has_no_package= is what i'm currently looking at
[14:11]  * jpds hands Hobbsee tinyurl.com
[14:12] <Hobbsee> jpds: i was bein glazy :)
[14:13] <tseliot> ﻿Hobbsee: ﻿field.has_no_package= ? Link?
[14:14] <Hobbsee> tseliot: searching for nvidia-glx for update-manager.
[14:14] <tseliot> ah, ok
[14:14]  * Hobbsee dupes another
[14:15] <Hobbsee> and another
[14:17] <Hobbsee> tseliot: https://bugs.edge.launchpad.net/bugs/249329 is a relatively fun oen for you, too
[14:18]  * tseliot has a look at it
[14:19] <Hobbsee> tseliot: https://bugs.edge.launchpad.net/ubuntu/+source/update-manager/+bug/107464 is probably a good one for you, too
[14:20] <tseliot> ﻿Hobbsee: I'm waiting for mvo to adapt Update-Manager so as to use my nvidia-common package to fix bug ﻿249329. I hope to do it this week
[14:21] <Hobbsee> tseliot: ah, excellent!
[14:25] <Hobbsee> tseliot: looks like there's 4 more mentioning envy, for when you get bored :)
[14:26] <tseliot> ﻿Hobbsee: I'll have a look at all of them. Thanks
[14:26] <tseliot> :-)
[14:27] <Hobbsee> tseliot: :D
[14:45] <tseliot> Hobbsee: in this case https://bugs.edge.launchpad.net/ubuntu/+source/update-manager/+bug/107464 there is little we can do. If users install the driver from the NVIDIA installer they should remember to uninstall the driver from the installer so as to remove its libraries, etc.
[14:47] <tseliot> ﻿Hobbsee: touching the preinst of libgl1-mesa-glx to remove/divert the libraries installed by the installer wouldn't be easy and could be detrimental to other packages (e.g. nvidia-glx) in Ubuntu.
[14:48] <tseliot> maybe we should just recommend the steps to uninstall the driver before the dist-upgrade.
[15:09] <Hobbsee> tseliot: fair enough
[17:28] <Fallenou> hum two bugs about over heated laptops in two days
[17:29] <Fallenou> #250289 and #250241
[17:33] <Fallenou> but one says that the his fans doesn't work and the other that it does so it doesn't seem to be duplicate
[17:34] <sectech> different hardware?
[17:35] <Fallenou> one overheated his battery so he had to buy a new one (on a Lenovo IBM)
[17:35] <sectech> hmm
[17:35] <Fallenou> the other on a HP Pavillon laptop
[17:35] <Fallenou> on the HP fans didn't work
[17:36] <Fallenou> /proc/acpi/thermal_zone was empty and the temperature skyrocketted
[17:36] <Fallenou> (thermal.ko failed)
[17:36] <Fallenou> i asked for more informations and set it to incomplet for both of them
[17:37] <Fallenou> i gotta go
[17:37] <sectech> The fan one sounds pretty bad if it's not setup specific to him
[17:37] <Fallenou> yes
[17:37] <Fallenou> i'm sorry but i gotta go
[17:38] <Fallenou> will be here in a few hours
[17:38] <sectech> see ya later
[17:38] <Fallenou> see ya
[21:13] <mouz> should bug 250287 have importance high?
[21:14] <jonpackard> I should think so.. it's a nasty one.. yay for snapshots =)
[21:15] <mouz> indeed yay for snapshots
[21:31] <jonpackard> FYI: in bug 250267, the site mentioned is pornographic in nature.. I put a comment warning as such and also converted it to a question because it was not reproducible with another website.. does anything else need to be done with this?
[21:35] <Pici> I don't see any pornographic content on that site.  It looks like a mobile phone downloads site to me.
[21:36] <jonpackard> ﻿Pici: browse videos or images and you will see what I mean
[21:36] <Pici> And it also works fine in my ff3
[21:37] <Pici> jonpackard: oh.  yes, you do appear to be correct.
[21:38] <jonpackard> ﻿Pici: I don't want to be bug triaging during down time at work and get fired for "looking" at porn =X
[21:38] <Pici> jonpackard: I agree 100%
[21:38] <greg-g> jonpackard: that would be like saying that youtube is a porn site, imho
[21:38] <greg-g> albeit, this is more explicit
[21:38] <jonpackard> but i guess that's always a risk when u type in an url
[21:39] <Pici> Thats why I didnt click past the first page I guess
[21:39] <greg-g> btw, a simple NSFW would have been sufficient
[21:39] <mouz> should the same bug filed for different versions of a package be marked as duplicates?
[21:39] <greg-g> mouz: examples?
[21:40] <jonpackard> ﻿greg-g: NSFW++ lol.. common courtesy really =)
[21:40] <mouz> greg-g: none. just wondering
[21:40] <greg-g> in general, yes
[21:40] <greg-g> mouz: ^
[21:40] <greg-g> jonpackard: I meant for what you typed.
[21:40] <mouz> greg-g: the exception case being...?
[21:41] <greg-g> also, you can change the description of the bug to put NSFW next to the link
[21:41] <jonpackard> ﻿greg-g: thank you for the tip =)
[21:41] <greg-g> mouz: that depends, I would have to see it.  I just don't want to say yes for every case and then you act incorrectly.
[21:42] <mouz> greg-g: i understand.. thanks
[21:42] <greg-g> mouz: no problem.
[21:42] <greg-g> mouz: I think you would be safe to assume that it should be a duplicate though.  It can always been undone.