[00:09] <LinuxGuy2009> Hey guys Im not having any luck with diagnosing a major bug on my mom and dads machine. Everytime they get online with firefox or chromium the screen will randomly blank out and they have to hit the power button and start over. They can't browse much at all. They just asked me to put Jaunty back on. I really could use some help in diagnosing and fixing the issue. I really want them to keep Lucid cause its been so good on other machi
[00:09] <LinuxGuy2009> Could someone take the time?
[00:11] <arand> LinuxGuy2009: "Blank Out" Could use some specifying, for one..
[00:11] <LinuxGuy2009> arand: Blank, black, empty.
[00:12] <LinuxGuy2009> arand: no apps, no panels, nothing. No TTYs can be seen with CTRL+ALT and F keys
[00:12] <LinuxGuy2009> Intel graphics on an IBM P4 system
[00:12] <arand> LinuxGuy2009: Hmm, blank indeed :/
[00:13] <arand> LinuxGuy2009: Does ctrl+alt+del reset it? does alt+sysreq+REISUB work?
[00:13] <LinuxGuy2009> I don't even know where to start. I had the error message wrote down but my dad threw it away of course. I got an error message when booting Lubuntu I figured it would be pretty much the same.
[00:13] <arand> Just seing if the kernel still responds
[00:14] <LinuxGuy2009> arand: What is reisub?
[00:14] <arand> !reisub
[00:14] <ubot2> In an emergency, you may be able to shutdown cleanly and reboot by holding down Alt+PrintScreen and typing, in succession, R, E, I, S, U and B. For an explanation, see http://en.wikipedia.org/wiki/Magic_SysRq_key
[00:15] <LinuxGuy2009> arand: Ok ill try that right now. Have to get it to crash first. Might be a few minutes. Ill be back.
[00:16] <arand> If that works, at least the kernel still responds, if not, well then you might at least be able to blame the kernel for crashing.
[00:16] <LinuxGuy2009> ok
[00:17] <LinuxGuy2009> Ok I told my dad to jump on and try and get it to black out again so I can try the REISUB.
[00:17] <LinuxGuy2009> arand: I apreciate you taking the time!
[00:18] <arand> Note that I'm only able to give very loose, general hints on debugging, I know far too little about it, but maybe enough that you can at least get some material for a bug report...
[00:19] <LinuxGuy2009> arand: That would help a lot Im sure.
[00:22] <LinuxGuy2009> arand: Ok CTRL+ALT+Del made it reboot instantly. As soon as I did that I saw the purple ubuntu screen.
[00:22] <LinuxGuy2009> arand: What to do from here.
[00:23] <LinuxGuy2009> arand: Think it might be the kernel?
[00:23] <arand> LinuxGuy2009: Right, so not specifically the kernel, I'm searching LP, and Bug #541492 for example might be something...
[00:23] <ubot2> Launchpad bug 541492 in xserver-xorg-video-intel (Ubuntu Lucid) (and 2 other projects) "MASTER: [i845] GPU lockup (apport-crash) (Should KMS be blacklisted?) (affects: 40) (dups: 22) (heat: 360)" [High,Triaged] https://launchpad.net/bugs/541492
[00:23] <LinuxGuy2009> arand:Ok thanks
[00:24] <micahg> arand: LinuxGuy2009: if you have an X or kernel bug, please file a new bug even if it looks that same and note the similar bug in your report
[00:24] <arand> LinuxGuy2009: "It happens all the time now. Sometimes when I click a new link, sometimes when I open a new program or whatever. The screen doesn't get signal from the GPU anymore and complains." Sound pretty similar, right?
[00:24] <LinuxGuy2009> arand: Yeah the i845 is the exact video chipset.
[00:25] <LinuxGuy2009> arand: Yeah pretty much. They only browse online and dont run anything else to verify but yeah that sounds dead on what they have.
[00:25] <LinuxGuy2009> arand: Looks like there is a driver in the PPA should I try that?
[00:26] <arand> LinuxGuy2009: Might be worth a shot, make sure to read what people are saying about it though.
[00:26] <LinuxGuy2009> arand: Ok cool
[00:35] <arand> LinuxGuy2009: https://wiki.ubuntu.com/X/Bugs/Lucidi8xxFreezes is full of "workarounds, I've no idea if any of them are relevant though..
[00:35] <LinuxGuy2009> arand: Ok Ill take a look
[00:39] <LinuxGuy2009> arand: I'd like to try downgrading the kernel to 2.6.31 how do I do that? Do I need to manually download a kernel package from like jaunty or karmic and install that and remove the others?
[00:40] <LinuxGuy2009> That was one of the suggestions
[00:41] <micahg> LinuxGuy2009: that will probably break a lot of stuff
[00:42] <LinuxGuy2009> micahg: Ok. How would I safely downgrade it? Is that a bad idea alltogether?
[00:42] <micahg> LinuxGuy2009: I would think it's a bad idea, why do you want to do it?
[00:43] <LinuxGuy2009> micahg: Intel i845 lockups. https://wiki.ubuntu.com/X/Bugs/Lucidi8xxFreezes
[00:43] <micahg> LinuxGuy2009: I thought there's a boot flag to disable KMS
[00:43] <LinuxGuy2009> Kernel downgrade to 2.6.31 is mentioned here. https://wiki.ubuntu.com/X/Bugs/Lucidi8xxFreezes
[00:44] <LinuxGuy2009> micahg: Should I try that first?
[00:45] <micahg> LinuxGuy2009: oh, maybe in your case it's to enable KMS
[00:45] <micahg> LinuxGuy2009: the new intel driver doesn't help?
[00:45] <LinuxGuy2009> micahg: I'm here asking what to do. Havent tried anything yet.
[00:46] <LinuxGuy2009> micahg: What would you recomend I try first?
[00:46] <micahg> LinuxGuy2009: video driver would be my first thing to try, then, enable/disable KMS
[00:46] <LinuxGuy2009> micahg: The driver in the PPA as mentioned?
[00:47] <micahg> LinuxGuy2009: yeah, new video drivers can sometimes help
[00:47] <micahg> LinuxGuy2009: just be familiar with the cli in case it fails
[00:47] <LinuxGuy2009> micahg: Ok Ill do that right now and Ill be back. Yeah i am. Thanks.
[00:48] <arand> LinuxGuy2009: From what people are saying in the bug, though, it seems that the "use vesa instead" seemed to be the working one... Although that will pretty much get you on crappy generic drivers, but stable, possibly. I would (after micahg's suggestions) look into the Brian Roger's experimental PPA, and as a fallback, and as a fallback try the donwgraded one from the x-retro PPA or set it as vesa (although those won't help towards diagnosing 
[00:53] <LinuxGuy2009> The PPA for the driver is an old driver it turns out. Already has a newer one installed.
[00:53] <LinuxGuy2009> So should I try the KMS workaround?
[00:54] <micahg> LinuxGuy2009: this has a later driver than Lucid: https://edge.launchpad.net/~ubuntu-x-swat/+archive/x-updates
[00:54] <LinuxGuy2009> micahg: Ok Ill check that.
[01:16] <LinuxGuy2009> Ok the driver was way worse than the other. Couldnt even boot to a desktop. So i uninstalled it and put the official package back in. Now Im about to try out the KMS workaround. If it ends up worse do I just change the part that says modeset=1 back to modeset=0?
[01:18] <micahg> LinuxGuy2009: you can test by editing the boot line and not editing the file on the disk
[01:19] <LinuxGuy2009> So here is the directions I see. What would I do for an i845 to test it?
[01:19] <LinuxGuy2009> https://wiki.ubuntu.com/X/Bugs/Lucidi8xxFreezes
[01:19] <micahg> LinuxGuy2009: idk actually :(, maybe ask in #ubuntu-x if the wiki isn't clear or no one else can help
[01:21] <arand> LinuxGuy2009: I recall there being a "nomodeset" for disabling it ...
[01:24] <arand> LinuxGuy2009: "i945.modeset=0" /1 seems to be another way ...
[01:27] <LinuxGuy2009> Ok I did the KMS workaround and my dad is browsing away. Crossing my fingers.
[01:50] <LinuxGuy2009> Well that didnt work unfortunately. I think they are kinda getting tired of Lucid. Might just have to put Jaunty back on for them again.
[01:52] <LinuxGuy2009> Maybe by 10.04.1 point release it will be fixed.
[02:34] <rww> ubottu: bug 569285
[02:34] <ubot2> Launchpad bug 569285 in empathy (Ubuntu) ""[person] has joined the room" when one joins an IRC channel (affects: 1) (heat: 6)" [Low,Incomplete] https://launchpad.net/bugs/569285
[02:35] <rww> I reported this about a month ago and can no longer reproduce it, and it isn't confirmed by an upstream report or someone else on LP. Should I mark it invalid?
[02:36] <micahg> rww: yes, if you believe it's no longer an issue
[02:36] <rww> micahg: alright. thanks :)
[04:34] <anoteng> anybody here familiar with git-bisecting a kernel?
[07:45] <mtx_init> Hey guys, Ive been having a problem for a white, have looked in the other channel a few times, but with no avail.  It seems only with Ubuntu, sometimes when I do a cold boot, everything is really laggy and jittery.  A reboot solves the problem.  any idea what it could be?
[08:04] <anoteng> mtx_init, check dmesg or /var/log/messages when you're having problems, might give some clues..
[08:04] <mtx_init> ok will do in the morning
[08:05] <anoteng> and please file a bug report if this turns out to be a problem with ubuntu (ie. not broken hw or some config you changed)
[08:06] <mtx_init> I will, I know it is Ubuntu specific, because it only happens with Ubuntu and has since 7.10.  Doesnt occur on FreeBSD, fedora, Arch or Window's
[08:06] <mtx_init> thanks again.
[09:07] <BUGabundo_remote> sleep check,clothes check,Monday start ohhhh
[09:31] <qense> https://wiki.ubuntu.com/BugSquad/Mentors updated
[09:32] <snadge> anyone else have c1e (new processor power saving feature) enabled?
[09:33] <ddecator> thanks qense :)
[09:34] <qense> :)
[09:35] <qense> good morning vish
[09:36] <vish> qense: hey :)
[09:38] <ddecator> looks great qense
[09:38] <ddecator> heya vish
[09:39] <qense> ddecator: Thanks. I mailed it to you already, but if you think some things need to be changed to that page in order to make it fit in with the rest, please do, as long as the original message of the wiki page doesn't get distorted.
[09:39] <ddecator> qense: sure thing. i can't think of anything atm that could be improved, but i'll keep that in mind. thanks :)
[09:39] <qense> good
[09:40] <vish> ddecator: o/
[09:40] <vish> qense are all the mentors listed the latest or the old ones?
[09:42] <qense> vish: The mentors that are currently listed at <https://wiki.ubuntu.com/BugSquad/Mentors> are the ones that once said during the past cycle they would like to mentor. They all should be admins of <https://launchpad.net/~bugsquad-mentorship>. However, since almost no one is actively mentoring we're reviewing the list and will probably be removing some of the people from the list.
[09:43] <qense> The old list -- which is currently the same as the new -- can be found at <https://wiki.ubuntu.com/BugSquad/Mentors.backup>.
[09:43] <qense> Pedro will mail all students and mentors to see whether they still want to be mentored or mentor.
[09:44] <qense> vish: The list on the main wiki page will mostly be maintained by the mentorship admins.
[09:44] <ddecator> he already sent out one to the mentors
[09:44] <vish> neat!
[09:45] <qense> vish: The new approach is that the mentorship admins are going to assign students to mentors, because letting the mentors pick students didn't work.
[09:47] <vish> hmm , the monitor display settings are part of gnome-settings-daemon or... ?
[09:48] <ddecator> depends. nvidia has it's own program that handles display settings
[09:49] <vish> ddecator: otherwise its g-s-t, right?
[09:49] <vish> ddecator: bug is about a user wanting an option to set the default monitor in a mutlimonitor setup
[09:50] <vish> multi-monitor*
[09:51] <ddecator> possibly w/e package has the monitor preferences in it? not sure it that's g-s-t or not (if i try to use any of the gnome packages that handle display settings, i get a warning saying i need to use the nvidia app...)
[09:52] <ddecator> s/it/if
[09:53]  * BUGabundo_remote just figure he had the window scrolled up, and was wondering why this one was blinking
[09:53] <vish> ddecator: well , reporters dont usually give the hardware info, do they .. ;p  we have to ask :s
[09:54] <ddecator> vish: that's where apport comes in handy ;)
[09:54] <ddecator> unless it's not against any package...
[09:54] <vish> ddecator: yeah , they dont use that either ;) /me uses collect-it reply template! ;)
[09:55] <ddecator> even apport-collect will add the info if there is a hook, but there needs to be a hook for it
[10:46] <snadge> https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/566449
[10:46] <ubot2> Launchpad bug 566449 in pulseaudio (Ubuntu) "No Sound Through USB Headset (affects: 2) (heat: 12)" [Undecided,Incomplete]
[10:48] <snadge> new to bug reporting, it seems lucid has introduced zero volume on usb headsets bug.. you can clearly see from the Card1.Amixer.values.txt attachment.. has its volume set to 0% .. and numerous me too posts, but this bug is still "undecided,incomplete"
[10:50] <snadge> you can adjust the volume with alsamixer.. but the sound properties app has no effect.. this additional information is missing from this bug report.. i should just sign up and mention this? :P
[11:08] <bbordwell> Sorry for cross channel posting, but since there are alot more users in here. Is anyone willing to help me upload my first package to a PPA? I am having trouble figuring it out
[11:11] <persia> Unfortunately, this isn't a better target channel :)
[11:22] <snadge> yeah they dont even talk about bugs in here ;)
[11:23] <persia> snadge: What?  We're happy to talk about bugs.
[11:24] <snadge> im joking i added additional information to the bug i posted earlier.. and im presuming that was the right thing to do :P
[11:30] <persia> Generally, yes.
[11:32] <aburch> https://wiki.ubuntu.com/Bugs/Responses#Incomplete bugs without a response from submitter
[11:32] <aburch> Didn't I read here a few days ago that changing bug status from Invalid to something else is no longer possible for regular users?
[11:34] <persia> aburch: best test to confirm.  staging,launchpad.net is a safe place to do that (DB is overwritten regularly, no mail interface exists)
[11:40] <aburch> Hmm, seems still possible.
[11:41] <persia> Well then, if you read it before, the statement may not have been correct :)
[11:41] <snadge> so why is the bug i mentioned earlier still incomplete?
[11:41] <aburch> And one more of my packages no longer has an open bug in Ubuntu :)
[11:43] <persia> snadge: Bug status only changes from manual action.  Either adjust the status to something more suitable yourself, or wait for someone else to examine the bug.
[11:48] <snadge> i have the ability to confirm it? amazing
[11:49] <snadge> oh and say that it effects me and subscribe to it.. cool ;)
[11:52] <persia> snadge: Please feel free to look for other bugs you can confirm, or improve :)
[11:53] <snadge> the alsa people are understandably not happy with the pulseaudio situation, and whats happening with gnome
[11:53] <snadge> difficult to get support from them these days when you mention ubuntu
[11:54] <persia> Which bit makes them unhappy?  Last I heard, lots of improvements were happening to ALSA to improve the pulse experience.
[11:54] <snadge> one of the guys in the appears to be using gentoo and was dismayed when gnome completely yanked the volume control applet.. and replaced it with one which depends on pulseaudio ;)
[11:56] <persia> I thought the old code was still available, if someone wanted to run it.
[11:56] <snadge> it is, gentoo was just missing a buildflag in order to make that work
[11:57] <snadge> if this bug is fixed, would an update to pulse be released if that fixed the issue? or not until next release
[12:01] <persia> Depends on 1) the nature of the bug (see SRU guidelines), the impact of the bug (guidelines again), and the willingness of anyone to push it through the process.
[12:01] <persia> !sru
[12:01] <ubot2> Stable Release Update information is at http://wiki.ubuntu.com/StableReleaseUpdates
[12:02] <persia> Anyone can drive the process, although there's no guarantees that anyone will be successful (sometimes even folks who are on the ubuntu-sru approval team get their planned SRUs rejected)
[15:40] <ctimko> Anyone here able to help me with a Networking issue I am having
[15:40] <ctimko> I am using jaunty
[15:41] <micahg> !support | ctimko
[15:41] <ubot2> ctimko: The official ubuntu support channel is #ubuntu. Also see http://ubuntu.com/support and http://ubuntuforums.org
[15:41] <ctimko> Thank you!
[15:42] <micahg> ctimko: np
[15:52] <crocket> Hello
[15:53] <crocket> how can I file a bug against ubuntu 10.04 lucid kernel?
[15:54] <pedro_> crimsun, use 'ubuntu-bug linux'
[15:54] <stenten> crocket: 'ubuntu-bug linux'. Just make sure you check Launchpad first to make sure it's not a duplicate.
[15:54] <pedro_> heh ;-)
[15:55] <crocket> how do I "ubuntu-bug linux" when linux doesn't respond?
[15:56] <davmor2> crocket: can you get into recovery mode?
[15:56] <stenten> crocket: can you get to a virtual terminal with Ctrl+Alt+F2?
[15:56] <crocket> stenten : the keyboard is dead, too
[15:56] <stenten> actually listen to davmor2, I like his response better.
[15:57] <crocket> Even under single mode, linux dies with KMS on.
[15:57] <crocket> Until KMS turns on, everythin goes fine.
[15:57] <stenten> crocket: Does it boot directly into a black screen or something?
[15:58] <crocket> After I start booting until KMS turns on, everything is fine, but then KMS turns on and everything goes black and keyboard toggle LEDs don't work either.
[15:58] <stenten> crocket: so if you enable "nomodeset" through GRUB, can you get to the desktop?
[15:58] <crocket> I haven't tried Ctrl+Alt+F2, though.
[15:58] <crocket> sure
[15:58] <crocket> nomodeset makes everything fine.
[15:59] <crocket> With nomodeset, it's better than ubuntu 9.10
[15:59] <stenten> crocket: so enable nomodeset and then 'ubuntu-bug linux'.
[15:59] <crocket> Somebody suggested me to connect to the seemingly dead linux via SSH
[15:59] <crocket> Is it really good to do it when I'm not under a problem?
[16:01] <stenten> SSH is a better choice if you can do it. But if nomodeset is the only way for you to file the bug in the first place, how else could you do it?
[16:02] <crocket> stenten : SSH
[16:13] <rlameiro> hi, i want to change some bugs, but i dont have permissions to triage them
[16:13] <rlameiro> can anyone help me?
[16:13] <rlameiro> https://bugs.launchpad.net/ubuntustudio/+bug/581786
[16:13] <ubot2> Launchpad bug 581786 in ardour (Ubuntu) (and 2 other projects) "Mute button not enabled by default in Ardour 2.8.6 Lucid AM64 (affects: 1) (heat: 6)" [Medium,Confirmed]
[16:15] <crocket> Even after I add kernel ppa, 2.6.34 kernel doesn't appear
[16:15] <crocket> Is it because I use amd64 version of ubuntu?
[16:16] <arand> rlameiro: Generally what you do is state the requested change and why here, and if you're lucky someone from the bug team can change it for you if they agree.
[16:17] <rlameiro> ok
[16:18] <rlameiro> so the problem is in mainstream (bug) i already added the mainstream project (ardour) and someone of the ubuntustudio team is working on a patch to send upstream and to debian also
[16:18] <rlameiro> so the bug is triaged already
[16:19] <rlameiro> and it is of big importance for ubuntu Studio, and maybe medium for ubuntu, since this is a "pro audio programm"
[16:22] <arand> rlameiro: And the changes persia did 6min ago, are they incorrect?
[16:22] <rlameiro> no
[16:22] <rlameiro> i was talking with persia, he told me to come here
[16:22]  * persia made them based on discussion with rlameiro 
[16:22] <rlameiro> maybe i just did it :D
[16:22] <rlameiro> he
[16:23] <rlameiro> arand: how can i enter the bugs team?
[16:27] <stenten> rlameiro: first join the Bug Squad (https://wiki.ubuntu.com/BugSquad) and then you can join the Bug Control Team (https://wiki.ubuntu.com/UbuntuBugControl).
[16:28] <rlameiro> thanks stenten i was reading  the wiki already, shame on me i didnt read the topic
[16:28] <stenten> no worries.
[16:28] <stenten> crocket: Are you talking about the mainline kernel PPA?
[16:29] <crocket> stenten : 2.6.34-rc7 and newer
[16:29] <crocket> yes
[16:29] <crocket> http://kernel.ubuntu.com/~kernel-ppa/mainline/
[16:30] <stenten> crocket: You have to download the three .debs and install them individually.
[16:30] <crocket> I can't add them in repository and install via synaptic....
[16:31] <stenten> crocket: no you cannot.
[16:31] <crocket> stenten , do developers prevent it?
[16:33] <stenten> crocket: Not sure. That's just how the site's set up. I just accept it; it's really easy to install still.
[16:35] <stenten> crocket: you can get in touch with kernel folk at #ubuntu-kernel
[16:35] <crocket> ok
[16:51] <hggdh> rlameiro: I already approved you in, thank you for helping :-)
[16:51] <rlameiro> hggdh: thanks me for aproving me :D
[16:52] <hggdh> rlameiro: my pleasure
[16:52] <rlameiro> happy to help :D
[17:09] <stenten> just curious, does being a member of the bugsquad have any privileges/powers like bugcontrol does?
[17:11] <nigelb> stenten: nope, but it tells us that you're trying to help
[17:11] <nigelb> for example if you screw up 20 bugs in one day, we might take you for a spammer and report you to Launchpad admins
[17:12] <BUGabundo_remote> ahahah
[17:12] <nigelb> but if you're bug squad, we'll get in touch with you and try to explain what went wrong and how to do things right :)
[17:13] <nigelb> BUGabundo_remote: anything you'd like to add? :)
[17:13] <stenten> hah, excellent. thanks nigelb :)
[17:14] <rlameiro> maybe also if you want to get into bugcontrol you need to be on bugsquad first?
[17:15] <nigelb> thats's the simplest explanation to "Why you should join bug squad if you want to help" :)
[17:16] <nigelb> rlameiro: not really, you need to showcase the triaging work you've done, you don't really *need* to be bugsquad member
[17:16] <rlameiro> hum ok thanks nigelb
[17:17] <nigelb> rlameiro: but, like I said, if you want to help, I'd recommend joining bug squad, so *we* know you're trying to help and we can correct if you go wrong :)
[17:18] <rlameiro> nigelb: i just joined :D
[17:18] <nigelb> awesome! thanks for helping out :)
[17:19] <nigelb> I wish I had the time I had initially to help with bugs, at least now I get to help others who'd like to help with bugs :)
[17:20] <scott-work> hello all, i have applied (and emailed the list) for bugsquad membership :)
[17:21] <nigelb> scott-work: one of the admisn should get around soon... hggdh ^
[17:21] <scott-work> thank you nigelb
[17:21] <hggdh> er
[17:21] <hggdh> scott-work: give me 1 min
[17:22] <rlameiro> hggdh: one more from the ubuntustudio team :D
[17:22] <hggdh> scott-work: done. Welcome in, and thank you for helping
[17:22] <hggdh> rlameiro: good
[17:23] <scott-work> hggdh: thanks!
[17:42] <ddecator> hggdh: ping
[17:53] <hggdh> ddecator: I am here
[17:53] <hggdh> (so far)
[17:53] <ddecator> hggdh: just wondering if you remember why you pinged me on friday
[17:56] <BUGabundo_remote> ahahah
[17:58] <nigelb> ddecator: nice of you to wonder on monday :D
[17:58] <ddecator> nigelb: just want to find out before i forget :p
[17:58] <nigelb> lol
[17:59] <ddecator> hggdh: i have to go get ready for class, but i'll be back on in a little bit before class, and then again later after class, so feel free to ping or pm me
[18:04] <jbicha> JFo: thanks for mentioning apport-collect, I didn't know about that command
[18:04] <JFo> jbicha, no problem :)
[18:06] <jbicha> JFo: what do you mean by "automated message", what tool(s) do you use for bug triage?
[18:07] <JFo> I'm running a script that processes the bugs
[18:07] <JFo> so the comment has been automatically generated
[18:07] <jbicha> what script?
[18:08] <hggdh> ddecator: no, I do not remember any more...
[18:09] <JFo> jbicha, it is a script in the kernel branch of the arsenal project
[18:10] <jbicha> ok, I don't do much with the kernel, it scares me :-)
[18:12] <vish> JFo: hi.. while testing bug 543485 , i noticed that the kernel .34 has *very* slow frame rates for video  , do i report it upstream , or wait for it to land in M ?
[18:12] <ubot2> Launchpad bug 543485 in linux (Ubuntu) "gspca: ISOC data errors when using resolution of 640x480 (affects: 1) (heat: 6)" [Undecided,New] https://launchpad.net/bugs/543485
[18:13] <JFo> vish, probably a good idea to report upstream
[18:14] <JFo> then if you encounter it in early tests of M to file a bug and let me know:)
[18:14] <vish> k.. ;)
[18:14] <JFo> so we can track both places
[18:15] <JFo> thanks vish :)
[18:15] <vish> np :)
[18:16] <vish> JFo: what are all the info upstream expect for such bugs?  i can just use apport to collect info and all those upstream? [i recall you mentioning it in UDS that they dont like reporters very much ;p ]
[18:16] <vish> s/all/add
[18:18] <JFo> heh
[18:19] <JFo> vish, I think it depends on the bug
[18:19] <JFo> they may just want some sort of graphics testing for this one, but I couldn't say what exactly
[18:19] <vish> i guess lsusb and lspci should be sufficient for this one?
[18:19] <JFo> yeah, for now
[18:19] <vish> JFo: neat thanks
[18:19] <JFo> and then let me know what they ask for beyond that
[18:20] <JFo> we can add it to a "reporting upstream" wiki page
[18:20] <JFo> np
[18:52] <PrototypeX29A> hi, got the ambitious to file every bug i encounter (yes, i am unemployed)
[18:52] <PrototypeX29A> +idea
[18:53] <Pici> heh
[18:55] <PrototypeX29A> does "Incomplete" also mean "cannort reproduce"?
[18:55] <PrototypeX29A> in launchpad
[18:55] <charlie-tca> not necessarily
[18:55] <Pici> It could, but usually it means that the triager has requested additional information and is waiting for the bug reporter to provide it.
[18:56] <charlie-tca> Even if it can be reproduced, sometimes, you want more information from the reporter
[19:00] <PrototypeX29A> yes, that was what i associated with it. Then I thought my bug was wrongly set to "incomplete" but it seems that it also can mean "cannot reproduce"
[19:01] <PrototypeX29A> which is a little bit confusing for the reporter, because one does not know whether some specific information is missing or the maintainer just is clueless
[19:07] <vish> PrototypeX29A: when a triager marks a bug as incomplete they *will* mention why , so not too confusing
[19:08] <PrototypeX29A> vish: at least they should :)
[19:08] <vish> PrototypeX29A: well if someone hasnt mentioned the reason , do mention it here , the tirager gets 10 lashes  ;)
[19:08] <vish> triager*
[19:09]  * vish hopes it aint me  , fingers crossed x
[19:10] <Pici> Speaking of bugs, could someone take a look at https://bugs.launchpad.net/bugs/459647 and see if the 'fix committed' status change was made improperly? I'd hate to see a bug not get fixed because someone randomly changed the status even though its not fixed.
[19:10] <ubot2> Launchpad bug 459647 in compiz (Ubuntu) (and 1 other project) "Cannot change mouse cursor theme when compiz is enabled (affects: 81) (dups: 7) (heat: 490)" [Low,Fix committed]
[19:10] <Pici> I think it was, but I don't want to change it back before asking.
[19:12] <PrototypeX29A> vish: if this is the policy i will happily do the lashing myself
[19:15] <vish> Pici: hmm , i dont see a commit upstream or anywhere
[19:17] <PrototypeX29A> submitting a useless fix is a nice way to get a bug to be confirmed :)
[19:21] <Pici> vish: Thanks.
[19:21] <vish> np..
[19:23] <anoteng> Anybody familiar with git-bisecting the ubuntu kernel? I fear I keep producing the same .debs over and over again. Anybody care to take a look at my commands and check if I'm doing something stupid? http://pastebin.com/Rfif04jx
[19:41] <kamusin> bug 585079 , should be fine under mime-support?
[19:41] <ubot2> Launchpad bug 585079 in ubuntu "missing mimetype for webm format (affects: 1) (heat: 6)" [Undecided,New] https://launchpad.net/bugs/585079
[19:56] <micahg> anyone experiencing bug 575160
[19:56] <ubot2> Launchpad bug 575160 in seamonkey (Ubuntu Maverick) (and 2 other projects) "seamonkey 2.0 in Lucid crashes with 'RenderBadPicture' diagnostics (affects: 9) (dups: 3) (heat: 70)" [High,Triaged] https://launchpad.net/bugs/575160
[20:20] <JFo> vish, re: reporting a bug upstream, I have the following: https://wiki.ubuntu.com/Kernel/Bugs
[20:20] <JFo> check the section on reporting upstream
[20:21] <JFo> let me know if there is anything broken as you proceed so I can fix it
[20:30] <vish> JFo: awesome, thanks!
[20:31] <JFo> my pleasure
[21:25] <PrototypeX29A> who is to be whipped, when a bug stays on 'new' forever?
[21:25] <PrototypeX29A> looks like i still have to find out how to use launchpad effectively
[21:26] <micahg> PrototypeX29A: one can come here and ask for it to be reviewed if no one reviews it in a reasonable period of time
[21:27] <PrototypeX29A> i just noticed that bugs may be 'Undecided' and 'New' on the Overview page, but are not if you click on the bug
[21:28] <PrototypeX29A> i try to keep track which of my (reported) bugs need attention, but the overview page is confusing
[21:29] <micahg> https://bugs.launchpad.net/~your-id/+reportedbugs
[21:29] <PrototypeX29A> this one is new for quite some time: https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/499889
[21:29] <ubot2> Launchpad bug 499889 in gtk+2.0 (Ubuntu) (and 1 other project) ""Type name of new folder" does not have focus, when doing "save as" with descending ordering. (affects: 1) (heat: 6)" [Low,New]
[21:30] <micahg> PrototypeX29A: you can sort by least recently changed
[21:30] <PrototypeX29A> but there are a lot of bugs which just don't concern me
[21:30] <micahg> if someone else can pick this up, I can't review right now
[21:31] <micahg> hggdh: are you around to help?
[21:31] <PrototypeX29A> don't get me wrong the bug just linked does not need imediate attention for my sake
[21:31] <PrototypeX29A> i am just curious about the processes, as i intend to do some more reports in the next time
[21:32] <ddecator> looks like it just needs to be sent or linked upstream
[21:32] <micahg> PrototypeX29A: well, we're limited on human resources and people have certain packages they try to look after, so it's very possible bugs will slip through the cracks, if you have a bug that has gone unnoticed, you can come in here and ask about it
[21:33] <micahg> PrototypeX29A: or move it along yourself if you like: https://wiki.ubuntu.com/Bugs/HowToTriage
[21:33] <PrototypeX29A> i will have a look at it
[21:35] <PrototypeX29A> and i think this one should be closed as the upstream fix seem to have found his way into the standard kernel https://bugs.launchpad.net/~preineke
[21:35] <PrototypeX29A> no wrong link
[21:35] <PrototypeX29A> https://bugs.launchpad.net/fedora/+bug/496292
[21:35] <ubot2> Launchpad bug 496292 in fedora (and 1 other project) "Kerneloops and disconnecting wlan (affects: 1) (heat: 8)" [Unknown,Confirmed]
[21:41] <micromix> hey can someone just peak at this bug 579098
[21:41] <ubot2> Launchpad bug 579098 in gparted (Ubuntu) "umount partition issue (affects: 1) (heat: 6)" [Undecided,Incomplete] https://launchpad.net/bugs/579098
[21:41] <micromix> i believe it should be wishlist
[21:44] <hggdh> micahg: reading the backlog
[21:51] <hggdh> oh hasty people...
[21:53] <hggdh> PrototypeX29A: no, it should not be closed, until we verify this does not happen on an Ubuntu kernel
[21:54] <PrototypeX29A> it is the ubuntu kernel i was talking about
[21:54] <hggdh> yes. Which one?
[21:54] <PrototypeX29A> the latest one i get with karmic
[21:55] <PrototypeX29A> 2.6.31-21-generic?
[21:55] <PrototypeX29A> so for karmic the problem is solved, isn't it?
[21:56] <PrototypeX29A> unless the other reporter still has a problem
[21:56] <hggdh> Good. *Sounds* like it, but I would rather wait for more confimations -- if the hardware is not exactly the same, symptoms may mix
[21:57] <hggdh> it is always a good idea, anyway, to add it the specific version when it works
[21:57] <PrototypeX29A> i should state that i am using the exact same model as the other reporter
[21:57] <hggdh> also a good idea. Can you please add both the kernel version and the make/model of the card in the bug?
[21:58] <micahg> PrototypeX29A: just a note, kernel team prefers separate bugs even if everything looks the same
[21:59] <PrototypeX29A> understandable :)
[22:00] <PrototypeX29A> i have the model of the notebook at hand, but how do i get the 'card'?
[22:00] <PrototypeX29A> something from lspci? 04:00.0 Network controller: Atheros Communications Inc. AR928X Wireless Network Adapter (PCI-Express) (rev 01)
[22:08] <hggdh> PrototypeX29A: yes, lspci would help (even more if run as root)