[09:48] <qense> hello
[10:17] <mr-russ> #123305 has been closed in compiz and hardy, but it's "New" in Linux, I can't see a reason why.
[10:18] <mr-russ> bug #123305
[10:18] <mr-russ> bug #123205 even
[10:21] <thekorn> good morning!
[10:21] <mr-russ> morning.
[10:21] <thekorn> mr-russ: the question is: why does this bug have an 'linux' task at all?
[10:22] <mr-russ> that does surprise me.
[10:22] <thekorn> it was added without a comment
[10:22] <mr-russ> I don't know who/how it got put there.  I'm not an lp expert yet.
[10:22] <thekorn> and from a user without any further work
[10:22] <mr-russ> how do you know this stuff?
[10:22] <thekorn> so my personal guess: it's spam
[10:23]  * mr-russ is jealous of the lp wizzardry
[10:23] <thekorn> you can click on the very left arrow in the linux task row,
[10:23] <thekorn> then the task expands
[10:24] <thekorn> and you get a box saying who and when this task was created
[10:24] <mr-russ> how do you know which comments relate to it?
[10:24] <mr-russ> ah, filed by jerik
[10:24] <mr-russ> jurik even.
[10:24] <thekorn> it was created an 2008-04-15
[10:25] <thekorn> and the last comment was on 04-11
[10:25] <thekorn> which actually closed this bug
[10:26] <mr-russ> I think it should be closed as well.  Not 100% how to do it except change the status to invalid for Linux.
[10:26] <thekorn> so I suggest "Incomplete" and ask jurik for more details,
[10:27] <thekorn> why did he choose to open a new task, etc.
[10:28] <mr-russ> it's not listed on the his bugs page either.
[10:29] <qense> thekorn: is there somewhere a list which explains the functions of python-launchpad-integration?
[10:29] <thekorn> mr-russ: because he is not subscribed, assigned; he just created a new task
[10:30] <thekorn> qense: I dont't know python-lp-integration is not related to python-launchpad-bugs
[10:31] <qense> oh
[10:31] <qense> I meant the bug thing :P
[10:31] <qense> my bad
[10:31] <mr-russ> I must say Linux is a BAD package name for the linux Kernel.
[10:31] <qense> why?
[10:31] <mr-russ> What's wrong with Linux Kernel?
[10:32] <mr-russ> whenever I think linux, I think OS.  Maybe others don't.
[10:32] <qense> but linux is not an OS
[10:32] <qense> it's the kernel
[10:32] <mr-russ> I'd add any but to the Linux package as my system isn't doing what I expect.
[10:32] <qense> Ubuntu is an OS using Linux/GNU
[10:32] <thekorn> qense: the bug part is here: https://wiki.ubuntu.com/BugHelper/Dev/python-launchpad-bugs/Bug
[10:32] <qense> thnx
[10:32] <qense> you're the one who wrote all this?
[10:32] <mr-russ> Unfortunately that is technically correct.  But users don't always see it that way.  I'll adjust my thinking accordingly though.
[10:33] <qense> well, I think we shouldn't teach users to keep thinking in a wrong way
[10:33] <qense> we should learn them to think right :)
[10:34] <thekorn> qense: https://wiki.ubuntu.com/BugHelper/Dev has an ovverview of all docs
[10:34] <qense> thanks
[10:34] <qense> I'm going to rejoin this channel, I accidentatly detached it from the tablist :P
[10:34] <qense> back
[10:37] <thekorn> hmm, reading the bugsquad ML; I really do not like this 'DON'T touch my/our bugs' discussion...
[10:38] <mr-russ> I'm also trying to work out how to set importances for bugs, I've read the Importance wiki page. I assume it's a little bit of "just knowing".
[10:39] <qense> nah, I think they should use other statusses
[10:39] <qense> but I've made myself clear in my mails :)
[10:39] <qense> we can't smell if the bug is theirs
[10:41] <thekorn> right, good point, I think I will reply to this thread too
[10:41] <qense> thekorn: where are the bitesize bugs of bughelper gone!
[10:41] <qense> it's bugless!
[10:44] <thekorn> ;)
[10:44] <thekorn> bugless is not true, but maybe no easy one to fix
[10:45] <thekorn> but if you have any questions, feel free to ask me
[10:45] <qense> ok
[12:11] <afflux> morning
[12:15] <qense> hell afflux
[12:15] <afflux> hi qense
[12:15] <qense> hell :P
[12:15] <afflux> waaaah :)
[12:15] <qense> hello*
[13:12] <narcan> hi
[13:12] <narcan> who use kazehakaze web browser ? have you got a crash with GTK error when you want to enter in setting menu?
[13:17] <narcan> s/kazehakaze/kazehakase
[13:25] <gnomefreak> narcan: is ther a bug on it?
[13:25] <gnomefreak> s/ther/there
[13:25] <narcan> i just find it
[13:25] <narcan> but its not really the same
[13:25] <narcan> https://bugs.launchpad.net/ubuntu/+source/kazehakase/+bug/173375
[13:25] <gnomefreak> narcan: i will be back in a minute or 2 i just need steps to reproduce it
[13:26] <narcan> thanks
[13:34] <narcan> the bug seem to be fixed in the futur version
[13:39] <gnomefreak> ok narcan what version of kaz are you running?
[13:41] <narcan> gnomefreak: 0.5.2
[13:41] <gnomefreak> narcan: how do you get it to crash
[13:42] <narcan> when i open setting menu
[13:42] <narcan> i have a GTK error
[13:42] <narcan> and kaz crash
[13:43] <gnomefreak> ok let me see if i can reproduce this
[13:43] <gnomefreak> oh yeah if you mena preferences
[13:44] <narcan> :)
[13:44] <narcan> it's good bug ^^
[13:46] <gnomefreak> latest release is 5.4 so we will have this in intrepid i will talk to the maintainer ans see what he thinks we should do maybe backport a working copy im not sure if this meets SRU
[13:47] <narcan> yes, i have also intrepid, i will test this bug on it, I come back i few minutes
[13:49] <gnomefreak> the latest we have in any of our PPA's is 5.0 but i will ask him if he plans oon updating kaz
[13:49] <gnomefreak> narcan: i am using intrrepid
[13:49] <gnomefreak> -r
[13:49] <narcan> ok :)
[13:51] <gnomefreak> it seems its imported from debian so onceits imported i will build it for hardy and see if it builds and either post it on PPA or get it backported
[13:52] <narcan> i am upgrading now to see that
[13:53] <gnomefreak> ok maybe it will be a while. its the last of the packages we have that dependon xul 1.8 and i was hoping to drop xul 1.8 soonish as im sure he was aswell
[13:53] <narcan> :/ gdm don't want to start ^^
[13:56] <gnomefreak> i havent done any updates today but my upgrade went flawlessly (its not exactly ready to use you know :)
[13:58] <narcan> yes ^^ the sid import have just beginning
[14:00] <gnomefreak> ok maybe xul support might be fixed, either we import from debian or i will build it with xul support and see how it goes but today is not a good day for working on xul
[14:02] <narcan> gnomefreak: ok thanks
[14:02] <narcan> :)
[14:03] <narcan> gnomefreak: you know new xorg?
[14:03] <gnomefreak> what about it?
[14:04] <gnomefreak> define new
[14:04] <gnomefreak> 7.3 not really all that new
[14:04] <narcan> about configured device
[14:04] <narcan> where can i find the "configured" device conf file?
[14:04] <narcan> i hate this new xorg.conf...
[14:05] <gnomefreak> you dont mean /etc/X11/xorg.conf do you?
[14:05] <narcan> in the xorg.conf you avec some section with "configured device..."
[14:06] <narcan> i think we can find it on other conf file?
[14:06] <gnomefreak> not sure i havent played with xorg 7.3 kmuch i was away for > 3months
[14:07] <gnomefreak> got back 1-2 days before hardy release
[14:07] <narcan> k
[14:07] <gnomefreak> seeing as there havent been any x updates in intrepid your X should work as it did before upgrade
[14:08] <gnomefreak> i think we got 2 driver updates but they were put into hardy as i recall
[14:08] <narcan> i made an upgrade with hardy CD
[14:08] <gnomefreak> now finish it by doing net upgrade to grab packages you missed
[14:08] <gnomefreak> having a mixed system is a good way to not be using it for a long time
[14:09] <narcan> ^^
[16:05] <seaq> hey yo!
[16:05] <seaq> I'm trying to install 5-day-applet but
[16:06] <seaq> its showing some python-central dependency error
[16:06] <seaq> I'm on gutsy at this point...
[16:07] <qense> ah
[16:08] <qense> ahve you followed the instructions here: https://wiki.ubuntu.com/5-A-Day ?
[16:08] <qense> and added all the repos needed?
[16:15] <seaq> yeap...
[16:15] <seaq> 3 repos for gutsy...
[16:15] <qense> ok
[16:15] <qense> what's the exact error message you get?
[16:16] <seaq> it's asking me for
[16:16] <seaq> Los siguientes paquetes tienen dependencias incumplidas:
[16:16] <seaq>   five-a-day: Depende: python-launchpad-bugs (>= 0.2.27) pero 0.2.21 va a ser instalado
[16:16] <seaq> and if I try to install python-launchpad-bugs alone
[16:16] <seaq>  python-central (>= 0.6.5) pero 0.5.15ubuntu2 va a ser instalado
[16:17] <qense> I think this is a dependency bug
[16:17] <qense> I'd report it at LP against python-launchpad-bugs and see what happens
[16:19] <seaq>  ok that's what I've thought
[16:19] <bdmurray> I might have an answer
[16:19] <bdmurray> Just give me a minute
[16:19] <seaq> ok
[16:20] <seaq> anything for a bug less at LP
[16:21] <bdmurray> five-a-day will only work on Hardy+
[16:21] <seaq> yeap.. I've just found that python-centrl is at hardy only.
[16:21] <seaq> ok
[16:21] <seaq> I've got to upgrade anyway. no prob
[16:23] <mohbana> hi
[16:23] <qense> hello
[16:26] <mohbana> hi
[16:26] <mohbana> i get random freezes sometimes, no idea why please help
[16:28] <qense> :(
[16:28] <qense> you're using a laptop or computer?
[16:28] <qense> what's the type of laptop, if you're using one
[16:29] <mohbana> it's a pc
[16:29] <qense> ok
[16:29] <qense> what are the specs?
[16:30] <mohbana> it's quiet new, quad core, 512mb 8800 gts gfx card, 4gb ram
[16:30] <seaq> bdmurray can I add the hardy requirement to the wiki page??
[16:30] <bdmurray> seaq: I'm not the lead on five-a-day but that seems reasonable to me
[16:31] <seaq> ok.. I'll put it on there.
[16:41] <seaq> mohbana probably you can find some help at #ubuntu
[16:41] <mohbana> the thing is, i don't have a clue why it's crashing, it's very _random_
[16:42] <bdmurray> I'm guessing you have an Nvidia graphics card, if you are using the Nvidia proprietary driver it would be good to test w/o it.
[16:49] <seaq> if it gets freezed usually that's  RAM problems, VIDEO problems, or CPU problems... overheating, unmatched bus speeds... Have you tested windows to check if it's a HW problem?
[16:50] <mohbana> i never get a crash on windows vista 64bit (as in total system freeze)
[16:52] <sectech> Hmm.... I joined the group BugSquad but I still don't have the option of marking bugs as triaged...
[16:52] <seaq> hmm hard to tell but you could follow bdmurray suggestions ...
[16:52] <seaq> I believe that's up to bug-control group...
[16:53] <sectech> hrmm... That would be the group that I wanted to join then....
[16:58] <seaq> first you must be bugsquad member and show your commitment and dedication in order to apply to bugcontrol
[17:06] <qense> yes
[17:07] <qense> there is an overview at the wiki page of ubuntu bugcontrol that shows you what the requirements are
[17:14] <sectech> okay so I am on the right track then....
[17:22] <sectech> I noticed in some bug reports there seems to be a template used (thanking the reporter for reporting the bug) and such... Is there a link to these templates?
[17:22] <sectech> something that I can go by then I reply to bug reports....
[17:22] <sectech> err when
[17:23] <pedro_> sectech: yes -> http://wiki.ubuntu.com/Bugs/Responses
[17:23] <sectech> great :) Thanks!
[17:23] <pedro_> you're welcome
[17:38] <bddebian> Boo
[17:40] <qense> hello
[17:40] <bddebian> Hello qense
[17:45] <qense> does anyone know if ati catalyst 8.4 will be included in ubuntu in the near future
[17:45] <qense> ?
[17:56] <sectech> wow a lot of new bugs are actually support issues
[17:56] <sectech> I never noticed that until now
[18:11] <graphx_> Can anyone help me with Bug #195308
[18:12] <graphx_> I am recieving - sudo: unable to resolve host
[18:13] <graphx_> I have gone through a number of setting changes... from hosts to resovl.conf, to so on and so forth... no dice
[18:13] <graphx_> is there a true fix for this?
[18:14] <bdmurray> There is a package in the -proposed repository that will resolve that bug.
[18:14] <bdmurray> It is currently going through the SRU verification process.
[18:14] <graphx_> yeah... well... that is great...
[18:14] <graphx_> I can't get it though... hints I can't update
[18:15] <graphx_> or resolve my host
[18:15] <graphx_> even after changing my localhost line and so on ...
[18:15] <bdmurray> does your hostname match what is in /etc/hosts?
[18:16] <graphx_> yup
[18:16] <bdmurray> could you pastebin the results of 'hostname' and your '/etc/hosts' file somewhere?
[18:16] <graphx_> I can type hostname and it tells me the correct host name too!
[18:17] <graphx_> I have been messing with the hosts file...
[18:17] <graphx_> I have gone from
[18:18] <graphx_> 127.0.0.1 localhost  ... to  127.0.0.1 azuregate.mycomputervisions.local
[18:18] <graphx_> hold on and I will paste it
[18:23] <graphx_> oh... my cheese whiz!!!!.... grrr... never mind...  I found it..
[18:24] <Iulian> What was the problem?
[18:25] <graphx_> bdmurray:  Thanks for your advisement.  It was a gathering of lost sleep and missing a simple period being in the way... grr... sorry... my fault
[18:26] <bdmurray> graphx_: no problem, I'm glad it is resolved
[18:27] <graphx_> Iulian: I got impatient with the network gui.. so I was adjusting things myself... and in the advent of working with some of my settings in nano... I added more then what was needed...
[18:27] <graphx_> bdmurray: I have to learn to get more sleep... I actually feel like a grouch!!! lol  sorry
[18:29] <Iulian> graphx_: You should know what you're doing when editing such files.
[18:29] <Iulian> graphx_: And yes, you should get more sleep.
[18:30] <graphx_> bdmurray: anyone here have an idea if Ubuntu is working to bring together a SMB solution in the near future, besides the ones in thought on the sites community information.
[18:31] <graphx_> Iulian: Well, I agree.. but this isn't the first time I have worked with the /etc files..
[18:31] <sectech> If you know for sure that a bug is specific to the user and that it really doesn't reflect something that is broken, it should be converted to a question right?
[18:32] <sectech> Just confirming....
[18:32] <bdmurray> probably what bug are you looking at?
[18:32] <sectech> 226561
[18:32] <sectech> I converted it to a question...
[18:32] <bdmurray> bug 226561
[18:33] <sectech> Pressing F11 does indeed bring you out of full screen
[18:35] <graphx_> oh.. which reminds me... Is there an existing bug for firefox and logmein..  (refreshes when clicking on items on screen)
[18:35] <sectech> I am going by the guidelines for marking triaging bugs... and I also take into consideration if the problem could be handled faster by the support group...
[18:35] <sectech> I just need a bit more confidence when redirecting lol...
[18:38] <bdmurray> Whether that one is a bug might be debatable but converting it to a question seems fine
[18:38] <sectech> Okay....
[18:39] <sectech> It just appeared as more of a question, just not worded as such... Figured it would get looked at faster as a question
[18:40] <bdmurray> I think you gave them enough info that converting it to a question was almost unnecessary
[18:41] <bdmurray> It doesn't look like they knew that F11 would take you back
[18:41] <sectech> bdmurray, I'm limited in what I can do with it though... short of marking it as invalid.
[18:42] <rbrunhuber> I need assistance in writing bug-reports regarding the kubuntu 8.04 installation.
[18:43] <pjoul> rbrunhuber: what kind of?
[18:45] <rbrunhuber> pjoul, maybe you could just listen to my installation problems and then help me to create bug reports out of it.
[18:46] <pjoul> rbrunhuber: have you gone through existing reports?
[18:46] <rbrunhuber> pjoul: yes
[18:46] <pjoul> nothing similar?
[18:49] <rbrunhuber> pjoul: nothing really similar.
[18:49] <pjoul> you can start then :)
[18:49] <bdmurray> rbrunhuber: where are you experiencing an issue?
[18:51] <rbrunhuber> the partitioner and grub do not give the same names to the hdds
[18:53] <rbrunhuber> pjoul, bdmurray i installed kubuntu with alternate cd to encrypted lvm on second hdd on a asus p5w dh deluxe mobo.
[18:54] <bdmurray> rbrunhuber: does it not boot now?
[18:54] <rbrunhuber> pjoul, bdmurray: yes I'm writing from this machine!
[18:54] <pochu_> jwendell: hi, I'm updating vinagre to 2.23.1 and I've noticed that src/vinagre-enum.[ch] don't have Copyright/License info. Would it be possible to add it for the next release?
[18:54] <pochu_> vinagre-enums, that is
[18:55] <pjoul> rbrunhuber: how did you repair it?
[18:55] <jwendell> pochu_, these files don't belong to the tarball, they're generated at compile time
[18:56] <pochu_> jwendell: really? I haven't built it yet and they are there :)
[18:57] <jwendell> pochu_, then this is a bug :)
[18:57] <pochu_> oh, then the question should be 'could you fix that bug for the next release?' ;-)
[18:58] <jwendell> pochu_, sure, but, just in case I forget, could you please file a bug in bugzilla then?
[18:58] <pochu_> alright, will be there in a minute
[18:59] <rbrunhuber> pjoul: booted in rescue mode installed (from alternate cd) installed grub and changed the all the groot and root names from (hd1,0) to (hd2,0)
[19:01] <pjoul> rbrunhuber: and does the partitioner suggest correct name for the volume?
[19:01] <rbrunhuber> i installed on /dev/sdb and now boot from /dev/sdc
[19:02] <pochu_> jwendell: reported, http://bugzilla.gnome.org/show_bug.cgi?id=531593
[19:02] <jwendell> pochu_, fast guy :)
[19:02] <rbrunhuber> pjoul: this means the installer named the volume sdb which would be (hd1,0)
[19:02] <pochu_> jwendell: i'll update the manpage to document the new debug option and create a patch in bugzilla too, but that will not be that fast :)
[19:02] <jwendell> pochu_, ok :)
[19:02] <pjoul> don't know these crazy names (1,0) (2,0)
[19:03] <pjoul> what do they mean?
[19:03] <pochu_> jwendell: gossip-cell-renderer-expander.[ch], should those be generated at build time too? :)
[19:03] <jwendell> pochu_, nope, they belong to the tarball
[19:04] <pochu_> alright, I think that's all!
[19:04] <qense> woot! five-a-day-applet is now in Dutch! :P
[19:07] <rbrunhuber> pjoul: this is grubs way to count volumes. so in linux first scsi/sata partition is /dev/sda and in grub-speak (hd0,0)
[19:07] <rbrunhuber> pjoul: so /dev/sdb is in grub-speak (hd1,0) and /dev/sdc is (hd2,0) ...
[19:07] <ogra> qense, damned, wat about all these people not speaking dutch ?
[19:08] <ogra> ;)
[19:08] <qense> well, there is a german version too!
[19:08] <ogra> :)
[19:08] <pjoul> rbrunhuber: ah, okay - so the partitioner suggests wrong partition names?
[19:08] <qense> and UK English
[19:09] <pjoul> and grub installer only follows these
[19:09] <rbrunhuber> pjoul: I guess so
[19:11] <pjoul> rbrunhuber: and how did you know that it should be /sdc instead of sdb?
[19:13] <rbrunhuber> because after i booted in rescue mode fdisk -l says my /boot partition is on /dev/sdc1
[19:13] <rbrunhuber> pjoul: see above
[19:16] <pjoul> rbrunhuber: it seems that autodetection of ﻿encrypted lvm partitions does not work perfect
[19:17] <rbrunhuber> pjoul: but all grub has to care about is /boot which is not encrypted and not on lvm?!
[19:18] <pjoul> rbrunhuber: but partitioner could write bad fstab entries
[19:18] <pjoul> and map /boot into incorrect partition
[19:24] <rbrunhuber> pjoul: http://pastebin.com/d6725c5b6
[19:24] <pjoul> hmm, is this original, non-edited?
[19:25] <rbrunhuber> pjoul: just shortened
[19:25] <bdmurray> rbrunhuber: and the types / quantities for devices you had did not change at all?
[19:26] <rbrunhuber> bdmurray: no everything original.
[19:27] <bdmurray> do you have any log files in /var/log/installer ?
[19:29] <rbrunhuber> bdmurray: yes for example /var/log/installer/partman
[19:32] <bdmurray> rbrunhuber: have you altered /boot/grub/device.map at all?
[19:32] <rbrunhuber> bdmurray: no
[19:32] <bdmurray> could you pastebin that?
[19:34] <rbrunhuber> bdmurray: what device.map or partman log?
[19:34] <bdmurray> device.map for now
[19:36] <rbrunhuber> bdmurray: just a question does grub touch the device.map if you reinstall it?
[19:38] <rbrunhuber> bdmurray: device.map: http://pastebin.com/d2b05b8b1
[19:40] <rbrunhuber> bdmurray: device.map is much older than all the stage* files so should be the original
[19:41] <bdmurray> Could you report a bug about debian installer include all of /var/log/installer/ , device.map, /etc/fstab, and what you've told us here?
[19:42] <bdmurray> that'd be debian-installer
[19:42] <rbrunhuber> bdmurray: just to confirm this all logfiles in /var/log/installer are from 21:27 and device.map is from 21:26
[19:42] <bdmurray> right, device.map was generated during the installation process
[19:47] <sectech> bug #226992
[19:48] <sectech> could someone take a look at that and tell tell me what that should be marked as.... a little unsure about that one.
[19:48] <sectech> I'm not quite sure if that would be considered a bug or not...
[19:48] <sectech> you have to enable accessibility first, then the reporters issue works.
[19:50] <pedro_> sectech: more like a wishlist, the reporter is saying that the checkbox should activate the accessibility too
[19:51] <pedro_> sectech: assign it to gnome-control-center, i'll change the importance to wishlist for you
[19:51] <sectech> pedro_,  Okay thanks :)
[19:51] <pedro_> sectech: thanks you for helping ;-)
[19:52] <sectech> Not a problem... This seems to be an area that I enjoy...
[19:53] <sectech> I may not be able to fix the bugs, but I figure I can at least help direct them to the proper place.
[19:55] <rbrunhuber> bdmurray: should i report the bug against the debian installer project?
[19:55] <sectech> pedro_,  can you also wishlist bug 227027 and let me know who to assign it to?
[19:55] <bdmurray> rbrunhuber: the debian-installer package in ubuntu
[19:55] <bdmurray> I'll find a url for you
[19:56] <bdmurray> https://bugs.launchpad.net/ubuntu/+source/debian-installer/+filebug
[19:56] <rbrunhuber> bdmurray: thanks, i know my way around in lp
[19:56] <bdmurray> Okay, there is sometimes confusion between projects and packages
[19:57] <pedro_> sectech: sure, do the other part as described here in the meantime https://wiki.ubuntu.com/UbuntuDevelopment/NewPackages
[19:58] <pedro_> change title, add a tag
[19:59] <sectech> okay
[20:02] <sectech> pedro_,  so you want me to add the "needs-packaging" tag? What would you recommend I add to the title?
[20:02] <sectech> I am still fairly new at this...
[20:04] <sectech> oh... "please sync package <packagename> from debian <distro>" where packagename is the package you would like to see.
[20:04] <pedro_> sectech: just look at the first part of the doc for example reports
[20:05] <pedro_> sectech: title should be [needs-packaging] package name
[20:06] <pedro_> and yeah add that tag to it
[20:06] <sectech> k
[20:11] <thekorn> bdmurray: hi, sorry for breaking the py-lp-bugs in the bughelper-dev PPA
[20:12] <thekorn> will create a new upload in a few hours
[20:14] <sectech> Done... hopefully I did that right
[20:44] <sectech> If I think a bug requires more information, and I ask probative questions to get that information it would be appropriate to mark the bug as incomplete right? <confirm>
[20:45] <pedro_> sectech: yes, you're right mark it as incomplete
[20:45] <sectech> pedro_,  then when I get that info and it looks like a complete bug report I could get someone from the bugteam to mark it as triaged?
[20:46] <sectech> I have well over a month where I can dedicate quite a bit of time looking at bugs
[20:46] <pedro_> sectech: you can mark it as Confirmed if you think that there's enough information
[20:46] <pedro_> and later on ask here for someone to review it and mark it as triaged
[20:47] <pedro_> great :-)
[20:47] <sectech> Okay, I'll have to keep a list then.... or just look in my own bug list...
[20:47] <LaserJock> I've got a question about python-launchpad-bugs, is this the best place to ask?
[20:47] <pedro_> or subscribe yourself to it
[20:47] <sectech> Hopefully after proving myself I can be eventually granted the privilege of marking them myself?
[20:48] <pedro_> sectech: yes sir you're correct
[20:48] <bdmurray> LaserJock: I know a fair bit about it
[20:48] <sectech> I kinda like doing this, I did a lot of QA work before....
[20:48] <LaserJock> I'm trying to pull out what release a specific task is targeted for
[20:49] <LaserJock> so far .milestone and .target don't give me that
[20:49] <bdmurray> bug.infotable and then task.targeted_to
[20:50] <LaserJock> ah, beautiful
[20:50] <bdmurray> task.milestone too
[20:51] <LaserJock> milestone doesn't give me release targets
[20:53] <bdmurray> Okay, if you want release targets then it is task.targeted_to
[20:54] <bdmurray> One thing to keep in mind is that when a release is targetted it becomes targetted for every task
[20:54] <LaserJock> huh?
[20:54] <LaserJock> maybe we aren't talking about the same thing
[20:55] <bdmurray> if you look at bug 204775
[20:55] <bdmurray> you'll see it is targetted to Hardy for both affected Ubuntu packages
[20:55] <LaserJock> right
[20:56] <bdmurray> so depending on what you are doing if you have a bug affecting multiple sourcepackages you might run into some issues
[20:56] <LaserJock> so when somebody nominates it for a release you get a task for each of the packages?
[20:57] <bdmurray> that's correct nominations are not package specific
[20:57] <LaserJock> well that's pretty crappy
[20:57] <LaserJock> doesn't affect what I'm doing, but it doesn't make a lot of sense to me
[20:58] <LaserJock> I guess you can go back and mark one Invalid if you needed to
[20:58] <bdmurray> bug 215728 is a better example
[21:00] <LaserJock> fun
[21:00] <LaserJock> in this case I'm just looking for what Releases tasks have been targeted too
[21:01] <LaserJock> I'm writing an SRU tracking script
[21:01] <LaserJock> so I just want to know what release an SRU is targeted for and which ones have not been targeted
[21:08] <sectech> What package does ACPI problems get put in?  The linux-source-<version> package? In reference to bug 227007
[21:10] <sectech> if someone could review and flag that one as triaged that would be great too
[21:17] <bdmurray> sectech: the correct package is just 'linux' since it is about the Hardy kernel
[21:18] <sectech> Okay...
[21:18] <bdmurray> kernel bugs used to belong to linux-source-<xyz> but for hardy forward we are using 'linux'
[21:20] <sectech> bdmurray, Alright....     I marked 227007 as confirmed as per what pedro_ told me to do, it probably should be marked as triaged though
[21:21] <bdmurray> I've Triaged it and assigned it to the ubuntu-kernel-acpi team
[21:23] <crimsun> um, I'm not so sure it has anything to do with acpi
[21:23] <crimsun> I would need the codec info (from /proc/asound/card0/codec*) to look further
[21:24] <crimsun> sectech: there's a fairly straightforward test to see whether it's acpi-related: after you resume, unload all snd* modules, then reload snd-hda-intel, then test if playing some audio file is audible
[21:25] <crimsun> if it is, yours wouldn't be the first Realtek HDA codec to need a reset
[21:26] <crimsun> (which would make it a linux-ubuntu-modules-2.6.24 issue)
[21:26] <sectech> It isn't my bug, I was just triaging it...   I'll assign it to linux-ubuntu-modules-2.6.24 then
[21:26] <crimsun> sectech: no, don't reassign it until that file is attached.
[21:27] <sectech> okay
[21:27] <crimsun> (it would be worth asking for that file, indeed.)
[21:28] <sectech> I'll make a note though on this site stating where it should go when the file gets posted.
[21:28] <crimsun> thanks!
[21:28] <JohnPhys> *works on frustrating things
[21:28] <JohnPhys> crap, wrong window, sorry guys
[21:28] <sectech> Okay so you just want me to requet that the bug poster unloads the sound modules and reloads and posts the output?
[21:29] <crimsun> sectech: two additional things would be useful: 1) the contents of /proc/asound/card0/codec*, and 2) logging out of GNOME/KDE/Xfce/etc. and into a console to issue `sudo /sbin/alsa force-reload'
[21:34] <sectech> K... Posted the request.
[21:35] <crimsun> sectech: many thanks
[21:36] <sectech> No problem.
[21:37] <afflux> is there a way to find out which kernel module is responsible for a specific device? let's say I know someone has a regression with "Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller" (pciid: 10ec:8168) and I'd like to sort out what code was changed?
[21:38] <crimsun> most drivers tend to have pci ids or ssids associated with them
[21:40] <crimsun> afflux: in your case, look at the aliases.
[21:40] <crimsun> afflux: i.e., modinfo r8169|grep 8168
[21:42] <afflux> ah okay, thank you
[22:01] <sectech> Hmm.... one of the bug is that vista won't load with grub... but the grub configuration was created when hardy was in beta...  I want to suggest that the user re-install grub (and all of it's files), but I am not 100% clear on the commands
[22:02] <sectech> commands == procedure.
[22:05] <sectech> hmmm I'll leave that one alone mayb e
[22:47] <sectech> Could someone review bug #227055, I am fairly convinced it is a unique configuration problem... I just would like some feedback on it
[22:47] <sectech> I can't reproduce the bug
[22:50] <wolfger> FF3 fails to fail for me as well.
[22:51] <bdmurray> it works for me too but that doesn't mean their isn't a bug there
[22:51] <wolfger> there's a bug in there somewhere, most likely. Only question is where.
[22:52] <sectech> I understand... but going by the information given it probably would recieve more attention from the support community,  if there is a bug there it can be converted back to a bug with the added info...
[22:52] <sectech> or do I have the wrong way of thinking on this?
[22:53] <bdmurray> I'm not certain how active the support community is compared to the bug community
[22:53] <bdmurray> Additionally, I think converting bugs to support questions should be done conservatively
[22:54] <sectech> I find that people are more likely to respond because they don't think they need to be developer...
[22:54] <sectech> Indeed, I won't be doing it often...
[22:54] <sectech> I always had pretty good luck with support, especially with firefox...
[23:00] <sectech> hmm... did someone flip it back to a bug?
[23:01] <bdmurray> yeah, I did
[23:01] <sectech> okay....
[23:02] <bdmurray> That one really seems like a bug to me, so I thought converting it back was reasonable
[23:02] <sectech> okay, it was a bad call on my part....
[23:03] <sectech> I should have asked before converting it to a question..
[23:03] <bdmurray> I don't think it is that big of a deal, and easy to fix.
[23:03] <sectech> yeah, true.... but if I didn't ask you guys it would have went unnoticed...
[23:04] <sectech> the ultimate goal is to help the person with there problem, not make it worse
[23:07] <bdmurray> I don't understand what could be causing it though
[23:08] <sectech> I have had java do that before.... but there isn't an applet on the webpage he is accessing...
[23:08] <sectech> or it seems there isn't from the source view that I saw
[23:08] <bdmurray> he said it crashed though right?
[23:09] <sectech> yeah... he said it closed firefox totally...
[23:09] <bdmurray> he could look in /var/crash/ for a firefox crash report and he might need to reenable apport to do that
[23:10] <sectech> BUT he also said after I converted it to a question that he followed my question and did create a new user, without all the extensions.... and it still crashed...
[23:10] <sectech> so it's system wide...
[23:12] <sectech> Regardless... If it's in the right area then someone might see it and know what it could be....
[23:12] <sectech> I'll move on
[23:13] <sectech> I have solved a few today just by asking for more information and making suggestions....
[23:16] <bdmurray> that's great!
[23:17] <sectech> Jeeze... Someone decided to assign a bug directly to me...
[23:24] <greg-g> sectech: thats not cool
[23:24] <sectech> Could someone review bug #227067 to see if it's assigned to the right group...
[23:24] <greg-g> sectech: (the not cool thing being someone assigning a bug to you without your permission)
[23:24] <crimsun> i love that subject.
[23:25] <sectech> greg-g,  I very kindly let the person know that assigning a bug to a specific person isn't really a good idea...
[23:25] <greg-g> crimsun: has it burned you a few times?
[23:25] <crimsun> I wouldn't say "burned"
[23:25] <greg-g> well, yeah.  has it "impacted" you? ;)
[23:26] <crimsun> yes.  As the triager.  And massager.
[23:26] <sectech> I understand that people get upset when there applications don't work... and I will help where I can,  the role I want to play though is just to get the bug to the right team
[23:26] <crimsun> generally people expect everything to work, which is fine, but have no understanding of how difficult it is to support everything THEIR ways OOTB.
[23:27] <sectech> with all the different kinds of hardware out there... it's impossible.
[23:28] <sectech> and when they post with an attitude from the start, it makes it even harder to deal with them
[23:36] <sectech> Can someone mark bug #226945 as triaged please
[23:41] <greg-g> sectech: that jack bug should be broken up into separate bugs, and definitely not be "in progress"
[23:42] <greg-g> "in progress" means someone is actively changing code/repackaging to fix the problem
[23:42] <sectech> he set it to in progress... I'll change it back to incomplete.
[23:43] <greg-g> the reason I say it should be separate bugs is because I see at least two separate issues: playing a .aup in Audacity isn't producing expected results and playing a .ogg in gmplayer isn't producing expected results
[23:43] <greg-g> sectech: cool
[23:43] <sectech> k...  Should I break it up or get the reporter to submit a new one?
[23:43] <sectech> Actually I better break it up....
[23:44] <greg-g> well... just make sure you understand exactly what the separate issues are.  that is why I usually have the reporter open a second one (and either I or them edit the description of the first to only reference one)
[23:45] <greg-g> but, asking this reporter to do more work is something they probably don't want to do (from the tone of their "voice")
[23:45] <greg-g> bug triaging is both a technical and social skill ;)
[23:45] <sectech> greg-g,  haha that's why I said I probably should do it... although I am not 100% sure on where to assign them to.... I'll work away at it
[23:46] <greg-g> I just install audacity to see if I can reproduce something
[23:46] <crimsun> it's actually more of 4 bugs
[23:46] <greg-g> which is a good technique for triagers: self confirm
[23:46] <crimsun> and i'll debunk most of them here
[23:46] <greg-g> crimsun: probably
[23:46] <crimsun> 1. he obviously doesn't know about PAM-aware RT.
[23:47] <crimsun> 2. non-Free Nvidia?  right, SEP.
[23:47] <crimsun> 3. ALSA support is _not_ the reason for his jackd issues.
[23:47] <greg-g> (SEP?)
[23:47] <crimsun> (someone else's problem - Nvidia's.)
[23:47]  * greg-g nods
[23:48] <crimsun> 4. I'm not sure how he missed Ubuntu Studio.
[23:48] <greg-g> heh
[23:49] <sectech> Okay,  well the entire bug report sounds like venting on top of it...
[23:49] <crimsun> In other words, Ubuntu Studio takes care of (1), configures jackd properly, and is best suited for him.
[23:49] <crimsun> yes, ranting is great.
[23:50] <sectech> crimsun,  considering I started to triage it I probably should post something as a final statement....
[23:50] <crimsun> anyhow, I concur that things could be simpler - but his is one set of use cases.
[23:50] <crimsun> making his use cases work OOTB would make some people happy and tick off others.  So...
[23:51] <sectech> I could recommend Ubuntu Studio, but I probably will be blasted for it
[23:52] <sectech> but your right... If that is the simplest fix for his situation...
[23:52] <sectech> What do I set the bug as though? change it back to new and let it expire?
[23:52] <crimsun> I'll respond to his report.
[23:52] <sectech> okay
[23:53] <sectech> thanks crimsun
[23:54] <sectech> Actually refresh your screen
[23:55] <sectech> he backed off saying that he didn't think it was a jack specific problem
[23:56] <sectech> what do you guys do in a situation like that though, do you just leave it as incomplete?
[23:58] <greg-g> in the case of a bug report which has only one bug/issue in it (not this one) and the reporter suggests that it is not the fault of the assigned package YET you still feel it is a bug you should still continue to triage it with the reporter and thus figure out where the problem actually is
[23:59] <sectech> okay...