/srv/irclogs.ubuntu.com/2008/07/20/#ubuntu-bugs.txt

sponixhttp://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
hggdhsponix, check the bugs opened against k3b02:30
sponixsearched them at launchpad, didn't find anything right off02:32
hggdhyou should then open a bug for it02:32
hggdhor check upstream02:33
rraj-beHello everyone :) i like to contribute in bug fixing. . I am good in c-programming. . Where can i start contributing04:34
pwnguinrraj-be: well, stuff tagged with core dumps and regression make sense04:36
sponixhggdh:  filed a bug report on it, if you want to see it ?04:36
pwnguinmanl why do people do that?04:37
=== asac_ is now known as asac
rraj-be>Hello everyone :) i like to contribute in bug fixing. . I am good in c-programming. . Where can i start contributing04:47
pwnguinrraj-be: well, stuff tagged with core dumps and regression make sense05:09
rraj-be:) but i cant get you clearly05:10
pwnguinbugs tagged regression should be simple to write a patch for05:10
pwnguinhttps://bugs.edge.launchpad.net/ubuntu/+bugs?field.tag=regression05:11
pwnguinthat one has a list of bugs where the software used to work, but doesn't anymore05:12
pwnguinhttps://bugs.edge.launchpad.net/ubuntu/+bugs?field.tag=apport-crash <-- this one is a list of bugs that crashed05:13
rraj-bek05:13
rraj-behow can i get through  these things and start patching05:14
rraj-beis there any good guide to start in this05:14
pwnguinthe 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 debugger05:14
pwnguinI don't think we do05:15
pwnguinwe've got pretty good docs on testing triaging and committing fixes05:15
pwnguinbut surprisingly light on the intellectual heavy lifting, as far as I can tell05:16
rraj-bek05:18
sponixrraj-be:  https://wiki.ubuntu.com/HelpingWithBugs https://help.ubuntu.com/community/ReportingBugs05:18
rraj-beshould i have any debugger installed05:18
pwnguinrraj-be: gdb is your debugger05:18
sponixhttps://wiki.ubuntu.com/Bugs/HowToFix05:18
pwnguinsponix: all of that has a huge hole in it05:19
pwnguin1. find and replicate a bug05:19
pwnguin2. ???05:19
rraj-begdb. . is it available in default ubuntu05:19
pwnguin3. submit a patch05:19
pwnguin4. profit!05:19
rraj-beor should i install it now05:19
pwnguininstall it now05:19
rraj-bereplicate a bug   what does replicating mean05:21
sponixhttps://bugs.launchpad.net/ubuntu/+source/k3b/+bug/25020605:21
ubottuLaunchpad bug 250206 in k3b "k3b after burning a DVD the drive fails to respond" [Undecided,New]05:21
sponixthat is even my own bug that you can work on ;)05:21
pwnguinrraj-be: it means to make the bug happen for yo05:21
pwnguinu05:21
pwnguinlike if a program crashes, but you can never get it to crash05:22
pwnguinyou're stuck05:22
rraj-bebut i need continoues help please05:23
pwnguin?05:23
pwnguinI donno. #ubuntu-devel or #ubuntu-motu might be a better place, but they might also just punt you05:27
rraj-bei am just looking after the links05:27
rraj-besorry guys05:27
rraj-bei am Away for a short as i followed links given by you05:27
snadgeautomatic screen dimming on battery is broken.. can anyone verify before i report? :P05:47
snadgethe problem is if you have your brightness already set to minimum with this option enabled in the power settings05:48
snadgeif you leave your laptop idle for a while, then go to use it.. it cranks the brightness up05:48
snadgeit should only turn the brightness back up to the level you set it at.. so if it was at minimum, it should just stay minimum05:49
nickelleryrraj-be, this might help  http://youtube.com/watch?v=SAxFpKBG-bU06:00
rraj-besure06:03
rraj-bei will take a look on it06:03
snadgenobody test screen dimming for me? :(06:26
snadgeor is it all about intrepid now.. nobody cares about hardy anymore06:27
pwnguinoh, i assumed it wa intrepid ;)06:27
pwnguinwas06:27
snadgei should probably ride the latest dev release, do testing report bugs etc.. except i actually use ubuntu for daily work/use06:30
pwnguinsnadge: what i do is have three partitions: a stable install, a dev install and a shared home dir between them06:38
pwnguini 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 one06:41
greg-gwarning, 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:43
snadgeis wireless support ever going to get a real facelift?06:53
snadgeinstalled 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 etc06:55
snadgeand 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 line06:57
greg-gsnadge: you're barking up the wrong tree06:57
greg-g;)06:57
snadgeim just asking from the perspective of people using/working on intrepid06:58
snadgewhether there are any plans to make installing/configuring wireless any easier06:58
greg-gsnadge: 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
snadgeor am i missing something that already works06:59
snadgeok how about simplifying the ndiswrapper case06:59
greg-gof course "we" want to make using your wireless card easy, but "we" are hampered by your wireless cards manufacturer06:59
snadgeand maybe attempting to create a database that seperates ndiswrapper type devices from ones which are natively supported07:00
greg-gif they are natively supported they are natively supported and you don't have to worry about anything like ndiswrapper07:00
greg-gif they don't work it is most likely caused by the fact that the manufacturers do not release drivers for linux. period.07:01
snadgeok 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 either07:01
greg-gyeah, I've been burned myself from the processes with a crappy hp laptop07:01
snadgeand in the case of where it is supported by linux.. its in an experimental release of a forked driver, thats not included with ubuntu07:01
greg-gwell, because in your contrived exampled it is experimental, not suitable for release ;)07:02
snadgeim 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 years07:02
Hobbseedid you find ndisgtk?07:02
Hobbseethat's certainly helped07:03
greg-gof course, file bugs about your specific hardware not working with the linux dev team, and see what can be done07:03
snadgebut im thinking a gui for ndiswrapper would be nice07:03
snadgemaybe someone has already done that07:03
greg-gI believe that is what Hobbsee just referenced07:03
snadgeahh ok07:03
Hobbseesnadge: you mean ndisgtk, which is included on the cds, like ndiswrapper, but isn't installed by default?07:03
snadgeahh i see.. i thought there would be something as such07:04
Hobbseethat being said, ndiswrapper and development versions together are insane :(07:04
snadgewell maybe that package should be made more obvious that it can be installed.. kind of like restricted devices manager07:04
greg-galso, 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. drivers07:04
Hobbseeand nm should (and mostly does) "just work" once the device si recognised.07:05
snadgemaybe 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
snadgeyeah07:05
Hobbseethat would be ncie.  propose a patch to jockey?07:06
snadgethe same framework could be used to detect devices which are supported by linux.. on experimental drivers07:06
snadgewhich arnt in tree07:06
snadgea lot of work in the case of the latter though07:07
Hobbseeso, solve the nm one first, then work on that :)07:08
Hobbseeer, ndiswrapper one, not nm one07:08
snadgewell as far as free drivers go.. its pretty easy, theres only really madwifi and prism07:08
snadgei was burned by madwifi, because theres actually 3 drivers now07:09
snadgemadwifi, madwifi-hal and ath5k07:09
Hobbseestupid question, but i assume you had the restricted modules installed.07:09
Hobbseethat made my old madwifi card wrok07:10
snadgeyeah.. it comes with madwifi driver07:10
snadgei had to blacklist that in hardware devices (disable)07:10
snadgethen install madwifi-hal from source07:10
Hobbseeah, so yours wasn't a nice card.07:10
snadge5007.. or 242x.. windows doesnt even have a 64bit driver for it07:11
snadgethats the other complication07:11
snadgewhen i told the madwifi devs that i wanted to use it in ad-hoc mode with wep.. they were like, good luck07:11
snadgeafter 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
Hobbseeick.  :)07:12
snadgeso i guess the short of it is.. work in madwifi is ongoing, some of these newer chipsets have only very recently received any support07:13
snadgeits unrealistic to expect ubuntu to support them at this stage07:14
Hobbseebut 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:15
snadgei should.. my motivation would be helping fix bug #1 ;)07:18
ubottuLaunchpad bug 1 in ubuntu "Microsoft has a majority market share" [Critical,Confirmed] https://launchpad.net/bugs/107:18
Hobbseethen get to it :)07:18
=== Igorot_ is now known as Igorot
rraj-beHello everyone   i am starting with bug fixing.13:16
rraj-beI am just starting and which type of bugs should i try at first.13:16
rraj-behow can i start with that13:16
Hewrraj-be: I started with packages I was familiar with, as well as picking some from the new+undecided list13:34
rraj-befamiliar means by working or by seeing the code13:35
Hobbseepackages that you've used before13:35
Hobbseeand are familiar with13:35
Hewrraj-be: not necessarily; I'm not a developer and (mostly) never look at code13:35
Hewyes, what Hobbsee said :-)13:35
rraj-be:)13:36
rraj-besure13:36
Hewrraj-be: have you joined ubuntu-bugsquad? https://wiki.ubuntu.com/BugSquad13:36
rraj-beyes13:36
Hewgood :-)13:36
rraj-bei want to work in bug fixing but cant get started. . looking for a good guide or practical  guide13:37
HewHey 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:44
ubottuLaunchpad bug 249329 in update-manager "Can't upgrade to Intrepid with update-manager" [Undecided,New] https://launchpad.net/bugs/24932913:44
* Hobbsee waits for teh bug to load13:47
HobbseeHew: better to figure out what died, then send the bug to that package.13:47
HewHobbsee: From the logs, it was nvidia-glx (blacklisted)13:48
Hobbsee(if you don't, it may not be found again before release)13:48
HobbseeHew: modifying.13:50
Hobbsee(sorry to pinch your bug, but it's easier than explaining :)13:50
HewHobbsee: haha, no worries, thanks :-)13:50
HewI guess I'll have to find another to finish off my 5-a-day :P13:51
HobbseeHew: hehe, yeah.  although it's double on sundays, anyway.13:52
Hobbseehave a look now :)13:52
* Hobbsee bumps the importance on it13:52
Hewok yep13:53
Hobbseei wonder if that should be marked as nvidia-glx too13:54
HewI would have thought this had been reported.. looking for dupes13:54
Hobbsee!info nvidia-glx13:54
ubottunvidia-glx (source: linux-restricted-modules-2.6.24 (2.6.24.13-19.45)): NVIDIA binary XFree86 4.x/X.Org driver. In component restricted, is optional. Version 1:96.43.05+2.6.24.13-19.45 (hardy), package size 3763 kB, installed size 12040 kB13:54
Hobbseeah, it's lrm.13:54
HobbseeHew: it would be really nice if you'd go thru the apt bugs, btw :)13:55
Hobbseethey'd be fun13:55
Hobbseemost of them are probably transient problems, or otherwise unreproducable13:56
Hewyea I'll have a look through them. I find them a bit confusing atm, so it should be good experience.13:57
Hobbseeupdate-manager just looks evil13:57
Hewah, looks like the dupes are coming in fast (bug #249612)13:57
ubottuLaunchpad bug 249612 in update-manager "The package 'nvidia-glx' is marked for removal but it's in the removal blacklist" [Undecided,New] https://launchpad.net/bugs/24961213:57
Hobbseeah yes, that'll be a dupe13:58
Hobbseefound another one13:59
* Hobbsee marks them both13:59
Hewhaha, racing me to it..14:00
Hobbseethere's probably a few bugs here that are a dupe of what i reported, too14:00
* Hobbsee wtf's14:01
Hobbseehttps://bugs.edge.launchpad.net/ubuntu/+source/update-manager/+bug/9904314:01
ubottuLaunchpad bug 99043 in update-manager "gksu "update-manager -d" bug" [Medium,New]14:01
Hobbseeis that trevhino's son, or something???14:01
Hewhuge...14:02
* Hobbsee curses at beryl.14:02
Hewthat one is edgy anyway14:02
Hobbseeanything that has beryl in it can be marked as won't fix, if it looked like it failed due to beryl.14:03
Hewyep ok14:03
Hobbseewe don't support third party repository crack.14:03
Hobbseeanything that's not reproducible from edgy, likewise.14:03
Hewyep yep14:04
Hobbseehmmm.14:04
Hobbseei wonder if mvo wants reports from third party repositories that have bombed otu.14:04
HewHobbsee: btw are you sure bug #70195 is a dupe? it was reported ages ago on dapper14:04
ubottuLaunchpad bug 70195 in update-manager "Package nvidia-glx has broken dep on nvidia-kernel-1.0.9625 (dup-of: 249329)" [Undecided,Confirmed] https://launchpad.net/bugs/7019514:05
ubottuLaunchpad bug 249329 in update-manager "Intrepid dist-upgrade fails - 'nvidia-glx' is marked for removal but it's in the removal blacklist" [High,Triaged] https://launchpad.net/bugs/24932914:05
HobbseeHew: by the last comment14:05
Hobbseeeither that, or i'll mark it invalid, due to berylcrack.14:05
Hewok14:06
* Hobbsee grumbles at triagers.14:08
Hobbseewhy, oh why, is it the fault of the upgrader if nvidia-glx-dev has incorrect conflicts/replaces?14:08
* Hobbsee pokes tselliot to come here and help with sorting out his software bugs.14:09
Hobbseetseliot: a few of us are looking at update-manager bugs.14:10
tseliotHobbsee: for Intrepid?14:11
Hobbseelooks 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
Hobbseewant to help?  :)14:11
Hobbseewell, general triage.14:11
tseliotsure, why not14:11
Hobbseebotched upgrades due to nvidia stuff14:11
Hobbseehttps://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
Hobbseefield.has_no_package= is what i'm currently looking at14:11
* jpds hands Hobbsee tinyurl.com14:11
Hobbseejpds: i was bein glazy :)14:12
tseliotHobbsee: field.has_no_package= ? Link?14:13
Hobbseetseliot: searching for nvidia-glx for update-manager.14:14
tseliotah, ok14:14
* Hobbsee dupes another14:14
Hobbseeand another14:15
Hobbseetseliot: https://bugs.edge.launchpad.net/bugs/249329 is a relatively fun oen for you, too14:17
ubottuLaunchpad bug 249329 in update-manager "Intrepid dist-upgrade fails - 'nvidia-glx' is marked for removal but it's in the removal blacklist" [High,Triaged]14:17
* tseliot has a look at it14:18
Hobbseetseliot: https://bugs.edge.launchpad.net/ubuntu/+source/update-manager/+bug/107464 is probably a good one for you, too14:19
ubottuLaunchpad bug 107464 in update-manager "dist-upgrade failure (edgy->feisty) - SystemError from cache.commit(): installArchives() failed - cannot create `./usr/lib/libGL.so.1.2' (manual nvidia driver install)" [High,Confirmed]14:19
tseliotHobbsee: 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 week14:20
Hobbseetseliot: ah, excellent!14:21
Hobbseetseliot: looks like there's 4 more mentioning envy, for when you get bored :)14:25
tseliotHobbsee: I'll have a look at all of them. Thanks14:26
tseliot:-)14:26
Hobbseetseliot: :D14:27
tseliotHobbsee: 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:45
ubottuLaunchpad bug 107464 in update-manager "dist-upgrade failure (edgy->feisty) - SystemError from cache.commit(): installArchives() failed - cannot create `./usr/lib/libGL.so.1.2' (manual nvidia driver install)" [High,Confirmed]14:45
tseliotHobbsee: 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:47
tseliotmaybe we should just recommend the steps to uninstall the driver before the dist-upgrade.14:48
Hobbseetseliot: fair enough15:09
=== wolfger_ is now known as Goooooogle
=== Goooooogle is now known as wolfger
=== jjesse_ is now known as jjesse
Fallenouhum two bugs about over heated laptops in two days17:28
Fallenou#250289 and #25024117:29
Fallenoubut one says that the his fans doesn't work and the other that it does so it doesn't seem to be duplicate17:33
sectechdifferent hardware?17:34
Fallenouone overheated his battery so he had to buy a new one (on a Lenovo IBM)17:35
sectechhmm17:35
Fallenouthe other on a HP Pavillon laptop17:35
Fallenouon the HP fans didn't work17:35
=== nycerine is now known as nycerino
Fallenou/proc/acpi/thermal_zone was empty and the temperature skyrocketted17:36
=== nycerino is now known as nycerine
Fallenou(thermal.ko failed)17:36
Fallenoui asked for more informations and set it to incomplet for both of them17:36
Fallenoui gotta go17:37
sectechThe fan one sounds pretty bad if it's not setup specific to him17:37
Fallenouyes17:37
Fallenoui'm sorry but i gotta go17:37
Fallenouwill be here in a few hours17:38
sectechsee ya later17:38
Fallenousee ya17:38
mouzshould bug 250287 have importance high?21:13
ubottuLaunchpad bug 250287 in tasksel "[intrepid] deselecting one task uninstalled all tasks" [Undecided,Confirmed] https://launchpad.net/bugs/25028721:13
jonpackardI should think so.. it's a nasty one.. yay for snapshots =)21:14
mouzindeed yay for snapshots21:15
jonpackardFYI: 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:31
ubottuLaunchpad bug 250267 in firefox-3.0 "mozilla fire fox version 3 does not load www.mobango.com" [Undecided,Invalid] https://launchpad.net/bugs/25026721:31
PiciI don't see any pornographic content on that site.  It looks like a mobile phone downloads site to me.21:35
jonpackardPici: browse videos or images and you will see what I mean21:36
PiciAnd it also works fine in my ff321:36
Picijonpackard: oh.  yes, you do appear to be correct.21:37
jonpackardPici: I don't want to be bug triaging during down time at work and get fired for "looking" at porn =X21:38
Picijonpackard: I agree 100%21:38
greg-gjonpackard: that would be like saying that youtube is a porn site, imho21:38
greg-galbeit, this is more explicit21:38
jonpackardbut i guess that's always a risk when u type in an url21:38
PiciThats why I didnt click past the first page I guess21:39
greg-gbtw, a simple NSFW would have been sufficient21:39
mouzshould the same bug filed for different versions of a package be marked as duplicates?21:39
greg-gmouz: examples?21:39
jonpackardgreg-g: NSFW++ lol.. common courtesy really =)21:40
mouzgreg-g: none. just wondering21:40
greg-gin general, yes21:40
greg-gmouz: ^21:40
greg-gjonpackard: I meant for what you typed.21:40
mouzgreg-g: the exception case being...?21:40
greg-galso, you can change the description of the bug to put NSFW next to the link21:41
jonpackardgreg-g: thank you for the tip =)21:41
greg-gmouz: 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:41
mouzgreg-g: i understand.. thanks21:42
greg-gmouz: no problem.21:42
greg-gmouz: I think you would be safe to assume that it should be a duplicate though.  It can always been undone.21:42

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!