[04:34] <brokenfingers> bug 203704 Ready to be triaged?
[04:34] <ubot4> Launchpad bug 203704 in reiserfsprogs (Ubuntu) "mkreiserfs does not clear metadata from previous device users (heat: 3)" [High,Confirmed] https://launchpad.net/bugs/203704
=== yofel_ is now known as yofel
=== nhandler_ is now known as nhandler
=== ivoks_ is now known as ivoks
=== pleia2_ is now known as pleia2
=== ikonia_ is now known as ikonia
=== seb128_ is now known as seb128
[09:29] <giantpune> hi, i am experiencing a bug with kubuntu where the entire computer becomes unresponsive.  i can reproduce the issues 100% of the time, and i have found an old bug report describing what i believe to be the same issue.
[09:37] <giantpune> since the old issue was closed due to lack of information, im not sure how to proceed.  should i open a new one, or report the issue here or what?
[09:37] <astralja1a> giantpune: What's the bug # ?
[09:38] <giantpune> Bug #103365
[09:38] <ubot4`> Launchpad bug 103365 in ubuntu "Complete hang after a bluetooth device disconnects" [Undecided,Invalid] https://launchpad.net/bugs/103365
[09:40] <astralja1a> giantpune: As Brian clearly states in his latter comment, feel free to reopen it with further details on how to reproduce, so the devs can investigate.
[09:40] <astralja1a> Which Kubuntu release is this?
[09:40] <giantpune> 11.10 64bit
[09:42] <giantpune> is it ok still to add to this bug report?  i dont know if you guys have them tied to a certain distribution or anything like this
[09:42] <astralja1a> I was just thinking, as that is indeed quite old.
[09:43] <astralja1a> I'm sure the bluetooth stack has developed immensily since those times.
[09:44] <astralja1a> Maybe it's best to create a new one, and mention that bug in the new report. After all, kernel has moved lots, and it's a different arch, too.
[09:45] <astralja1a> Triager can mark the new one as duplicate, if that's how it is seen.
=== ivoks_ is now known as ivoks
=== ashams_ is now known as ashams
=== greyback is now known as greyback|lunch
=== mrpouit is now known as mr_pouit
=== ts2 is now known as tsimpson
=== un|face is now known as two|face
=== bladernr_afk is now known as bladernr_
=== greyback|lunch is now known as greyback
[14:10] <om26er> hey anyone know if the nvidia issue was fixed in precise?
[14:11] <zzecool> i think they released a fix
[14:11] <zzecool> im not sure
[14:12] <zzecool> because im running 64bit
[14:12] <zzecool> and i think it only affects 32bit
[14:12] <zzecool> im on latest nvidia driver 290  , in precise 64bit
[14:18] <seb128> om26er, it's fixed, cf bryce's follow up on the ubuntu-devel list
=== Ursinha is now known as Ursinha-lunch
[14:20] <om26er> ah, great thanks zzecool seb128 ;-)
[14:22] <zzecool> om26er: :)
[15:42] <om26er> we have a bug control application show love people :)
[15:49] <om26er> btw how many +1's are required for a BugControl member to join in ?
[15:49] <om26er> hggdh, ^
=== Guest29769 is now known as tobin
=== Ursinha-lunch is now known as Ursinha\
=== Ursinha\ is now known as Ursinha
=== bladernr_ is now known as bladernr_afk
[16:17] <hggdh> om26er: 2 +1, no -1
[16:18] <hggdh> om26er: I will look at it when I am back (around 4 hours)
[16:19] <om26er> hggdh, cool, thx :)
[16:21] <hggdh> om26er: IIRC, you gave him a -1
[16:22] <om26er> hggdh, that's change it'll be +1 now ;-)
[16:22] <hggdh> om26er: :-)
=== Ursinha_ is now known as Guest25821
=== Guest25821 is now known as Ursula
=== Ursula is now known as Ursinha
=== Ursinha` is now known as Ursinha
[17:24] <ghostwalk71> Hello all. Is this where I may get some assistance reporting a bug?
[17:25] <ghostwalk71> Hello yurau.
[17:26] <s9iper1> yes you can
[17:28] <s9iper1> ghostwalk71: https://help.ubuntu.com/community/ReportingBugs
[17:29] <s9iper1> http://www.ubuntu.com/community/report-problem
[17:30] <ghostwalk711> I already looked at the URL and all it did was confuse the matter. I already posted the bug on launchpad and got a bot that complained because I didn't mention a specific package.
[17:30] <ghostwalk711> I can give you the bug number if you like.
[17:30] <s9iper1> give
[17:31] <ghostwalk711> 930229
[17:35] <s9iper1> ghostwalk71: that a intresting bug  i guess its of xserver-xorg-input-mouse bug
[17:35] <s9iper1> or xserver-xorg
[17:35] <ghostwalk711> okay, so should I file it under xserver-xorg and pray that it goes to the right place?
[17:36] <ghostwalk711> I don't mean to sound snarky. I do appreciate your help s9iper.
[17:37] <s9iper1> ghostwalk71:and ask this in #ubuntu-desktop there are bryce  and ROAF is dealing with them i guess so
[17:38] <s9iper1> or you can also ask in #ubuntu
[17:38] <ghostwalk711> I'll try both of them, thank you for your time s9iper1 :)
[17:38] <s9iper1> np
=== astralja1a is now known as astraljava
=== s9iper1_ is now known as s9iper1
[21:15] <s9iper1> bdmurray:  hggdh : this one bug was subscribed by bug control i have closed this one because kenvandine said to me thanks
[21:15] <s9iper1> https://bugs.launchpad.net/ubuntu/+source/gwibber/+bug/741621
[21:16] <ubot4`> Launchpad bug 741621 in gwibber (Ubuntu) "gwibber-service crashed with DBusException in call_blocking(): org.freedesktop.DBus.Error.ServiceUnknown: The name org.desktopcouch.CouchDB was not provided by any .service files (affects: 20) (dups: 21) (heat: 176)" [Medium,Invalid]
[21:17] <s9iper1> he told me to close all the dbus bugs and time out bugs
[21:22] <bdmurray> s9iper1: yes, that's correct as we rather want the crash from the server / service taht couldn't be connected to
[21:25] <kira> Hi there, I'm just starting out on Bug Triage, and I'm curious how I actually go about confirming a bug?  Do I just see the "new" bug, then try to recreate it, then hit confirm?
[21:26] <s9iper1> yes
[21:26] <bdmurray> it helps to add details about how you confirmed it though
[21:27] <kira> thanks
[21:27] <bdmurray> e.g. I tried it with this version of the package on this release and was able to confirm it
[21:27] <s9iper1> https://wiki.ubuntu.com/Bugs/HowToTriage/
[21:27] <bdmurray> additionally improving the steps to recreate the bug can be a big help
[21:27] <s9iper1> kira:
[21:27] <bdmurray> if there is a specific bug you are looking at I'm sure somebody would be happy to help
[21:30] <mrburns> Hi there, I am also just starting out do you have any suggestions on what types of bugs to start on that are kinda simple?
[21:31] <s9iper1> mrburns: https://wiki.ubuntu.com/Bugs/HowToTriage/
[21:31] <s9iper1> and ping us here if you need any help
[21:37] <bdmurray> mrburns: I would look at bugs about an application you like or use
[21:37] <bdmurray> mrburns: as it provides you a way to learn about it and its something you already know about
[21:40] <mrburns> yeah...sounds good
[21:42] <bdmurray> mrburns: if you have specifc questions feel free to ask
[21:48] <mrburns> thanks bdmurray, most of the programs that i use are either proprietary or web browser but i use rhythmbox and empathy so i will start there
[21:49] <bdmurray> rhythmbox would be good
[21:52] <Jechs> So we're using VM Virtual Box in our CS course where we're doing some work with Ubuntu, would that cause issue with Bug Triage? My gut says yes but I'm not sure.
[22:00] <bdmurray> Jechs: it depends on the type of bug for most software type bugs no
[22:00] <bdmurray> Jechs: kernel and hardware bugs yes that would be an issue
[22:02] <Jechs> bdmurray: Alright, I'll keep that in mind. Thanks.