[01:08] <rusivi> Can someone check out bug 180893 for wishlist status?
[01:08] <ubot2> Launchpad bug 180893 in wine (Ubuntu) "wineboot has no manpage (heat: 3)" [Low,Confirmed] https://launchpad.net/bugs/180893
[01:09] <rusivi> ubot2: oh ok thanks bud.
[01:09] <ubot2> rusivi: Error: I am only a bot, please don't think I'm intelligent :)
[01:09] <rusivi> hahahaha
[01:10] <rusivi> ubot2: With your quick response I beg to differ!
[01:10] <ubot2> rusivi: Error: I am only a bot, please don't think I'm intelligent :)
[01:11] <yofel> !me
[01:11] <ubot2> Hi! I'm ubottu's favorite infobot, you can search my brain yourself at http://ubottu.com/factoids.cgi | Usage info: http://ubottu.com/devel/wiki/Plugins | Bot channels and general info: https://wiki.ubuntu.com/IRC/Bots
[01:21] <rusivi> Can someone check out bug 227563 for wishlist status?
[01:21] <ubot2> Launchpad bug 227563 in wine (Ubuntu) (and 1 other project) "cannot change screen resolution in counter-strike 1.6 under wine (affects: 1) (dups: 1) (heat: 6)" [Undecided,Confirmed] https://launchpad.net/bugs/227563
[01:26] <yofel> rusivi: done, I think 'low' is fine for the first bug though
[01:30] <yofel> rusivi: btw: wishlist is an importance, not a status
[01:34] <rusivi> yofel: thanks for checking!
[01:55] <greg-g> wow, I'm getting the deluge of remote bug travker imported comments emails :) Fun times remembering these old bugs
[02:00] <rusivi> Can someone please check out bug 420098 for wishlist Importance?
[02:00] <ubot2> Launchpad bug 420098 in resolvconf (Ubuntu) "[karmic] resolvconf not started at system boot (affects: 3) (heat: 11)" [Undecided,Confirmed] https://launchpad.net/bugs/420098
[02:00] <rusivi> sorry wrong bug
[02:00] <rusivi> Can someone please check out bug 420089 for wishlist Importance?
[02:00] <ubot2> Launchpad bug 420089 in wine1.2 (Ubuntu) (and 1 other project) "wine: items left in nautilus 'Open with..' menu even if Windows program or wine package is removed (affects: 1) (heat: 6)" [Undecided,New] https://launchpad.net/bugs/420089
[02:10] <greg-g> rusivi: I assume you made that last comment? It would be useful if you could link that LP bug to the upstream wine bug where that is a known issue.
[02:11] <greg-g> I would, personally, consider this a bug, not a new feature, but, I will defer to upstream's opinion
[02:12] <rusivi> greg-g: Sorry for the perceived lack of follow-through. I did not do a bug check for this, however , this is from personal experience. Please see following forum for more on this: http://ubuntuforums.org/showthread.php?p=9702619 As well, I'll do a bug check for this and report back.
[02:13] <greg-g> no need to apologize, rusivi. :) It just sounded like you had experience with upstream and might be able to easily find that bug in their bugtracker
[02:13] <rusivi> greg-g: regarding uninstalling apps installed in WINE: http://wiki.winehq.org/FAQ#uninstall_app
[02:14] <rusivi> That specifically mentions how clean uninstall of apps in WINE is not implemented (well). I extrapolated that to cleanly removing icons installed on app behalf via WINE
[02:15] <greg-g> makes sense
[02:16] <rusivi> greg-g: I've noticed the same phenomenon in newest dev WINE in Maverick.
[02:16] <greg-g> For a wishlist bug to be really useful, though, it should be either reported upstream so the developers are aware of the issue/request or linked to an upstream bug report so we know it is at least on their radar
[02:16] <rusivi> greg-g: np
[02:17] <greg-g> but, I can certainly mark this as wishlist in LP for you :)
[02:17] <greg-g> (done)
[02:17] <rusivi> greg-g: ty you rock! I'll post the upstream web link mentioned earlier.
[02:18] <greg-g> np, rusivi. Thanks for your help triaging.
[02:22] <rusivi> greg-g: I've been on a triaging spree. Just did all virtualbox, VLC, gcalc, KeePassX and finishing WINE. Basically, I'm triaging package bugs I've bugged myself previously as I have had some measure of experience with them.
[02:23] <rusivi> greg-g: From my view, many older bugs are fixed in newer package versions, just need to give reporter incentive to do so hehe
[02:23]  * yofel hugs rusivi
[02:23] <yofel> thanks for the work°
[02:23] <yofel> s/°/!/
[02:24] <rusivi> Also, many upstreams don't want to hear about bugs in old versions of their packages (understandably so)
[02:24] <rusivi> Been there, got flamed for that!
[02:24] <rusivi> hehe
[02:25] <rusivi> yofel: np least I can do to give back after Ubuntu has given me so much!
[02:47] <rusivi> Can someone please check out bug 488981 for wishlist Importance?
[02:47] <ubot2> Launchpad bug 488981 in wine (Debian) (and 2 other projects) "use wine-pulse for wine-packages (affects: 16) (dups: 1) (heat: 68)" [Undecided,New] https://launchpad.net/bugs/488981
[03:17] <micahg> rusivi: it's usually better to test for easy things that to ask the reporter if it's still occuring
[03:18] <micahg> testdrive helps with that
[03:31] <cwryuu> bug 637667 is a dupe of 570245
[03:31] <ubot2> Launchpad bug 637667 in g15macro (Ubuntu) "package g15macro 1.0.3-3 failed to install/upgrade: problemas de dependencias - se deja sin configurar (affects: 1) (heat: 6)" [Undecided,New] https://launchpad.net/bugs/637667
[03:31] <rusivi> Can someone please check out bug 637549 for wishlist Importance?
[03:32] <ubot2> Launchpad bug 637549 in wine (Ubuntu) "no way to set dpi per application (affects: 1) (heat: 6)" [Undecided,New] https://launchpad.net/bugs/637549
[04:03] <bcurtiswx> rusivi, done
[04:03] <rusivi> bcurtiswx: thanks!
[04:03] <bcurtiswx> rusivi, np
[04:08] <micahg> rusivi: also when looking at bugs like bug 623927, you need to see why it failed in the logs and try to ascertain why it happened
[04:08] <ubot2> Launchpad bug 623927 in vlc (Ubuntu) "package mozilla-plugin-vlc 1.0.6-1ubuntu1.1 failed to install/upgrade: unable to install new version of `/usr/lib/mozilla/plugins/libvlcplugin.so': No such file or directory (affects: 1) (heat: 6)" [Undecided,Incomplete] https://launchpad.net/bugs/623927
[04:11] <micahg> rusivi: also, if there's an upstream bug, you can request the bug be set to triaged
[04:15] <rusivi> micahg: Thank you for reviewing bug 623927. From my view, VLC upstream does not want to hear about old version of their packages. If user upgrades to Maverick, they update their VLC, and problem will most likely be resolved.
[04:15] <ubot2> Launchpad bug 623927 in vlc (Ubuntu) "package mozilla-plugin-vlc 1.0.6-1ubuntu1.1 failed to install/upgrade: unable to install new version of `/usr/lib/mozilla/plugins/libvlcplugin.so': No such file or directory (affects: 1) (heat: 6)" [Undecided,Incomplete] https://launchpad.net/bugs/623927
[04:15] <micahg> rusivi: this bug isn't about upstream at all, it's about an install error
[04:16] <micahg> rusivi: also, we have to support what's in the distro even if upstream won't
[04:17] <micahg> rusivi: also, when there's an upstream bug, you should just request the bug to be marked triaged if there's enough information upstream
[04:17] <rusivi> micahg: I attempt to adopt the view of the upstream devs for the package I triage with a little bit more flexibility.
[04:19] <micahg> rusivi: there are 2 sides to bugs, upstream and ours, you can follow upstream's views when upstreaming bugs, but with regard to our bug task, we have policies how the bugs are handled
[04:20] <rusivi> micahg: As well, I'm not a dev, so my diving into the crash log and coming up with a more germane solution is probably not gonna happen.
[04:20] <micahg> rusivi: ok, so for bugs you don't feel comfortable with, either ask questions or move on
[04:20] <rusivi> micahg: k
[04:30] <rusivi> Can someone please check out bug 479197 for wishlist Importance?
[04:30] <ubot2> Launchpad bug 479197 in wine1.2 (Ubuntu) "[wishlist] include optional .msstyle packpage by default (affects: 2) (heat: 19)" [Undecided,New] https://launchpad.net/bugs/479197
[04:31] <iosif> what is the best practice for filing bugs via apport when a program has crashed?  does choosing an existing bug in launchpad lose all my crash report information?
[04:40] <rusivi> Can someone please check out bug 552323 for wishlist Importance?
[04:40] <ubot2> Launchpad bug 552323 in wine1.2 (Ubuntu) (and 1 other project) "Permission checking dialog leaves users confused about what to do next (affects: 5) (dups: 1) (heat: 27)" [Medium,Confirmed] https://launchpad.net/bugs/552323
[04:41] <hggdh> iosif: the best is to open a new bug with your crash data
[04:42] <micahg> rusivi: bug 552323 already has importance set
[04:42] <ubot2> Launchpad bug 552323 in wine1.2 (Ubuntu) (and 1 other project) "Permission checking dialog leaves users confused about what to do next (affects: 5) (dups: 1) (heat: 27)" [Medium,Confirmed] https://launchpad.net/bugs/552323
[04:42] <iosif> hggdh: and let someone else make the duplicate determination?
[04:42] <hggdh> iosif: yes; probably apport itself
[04:43] <iosif> hggdh: great, will do.  thanks for the info
[04:43] <hggdh> welcome
[04:44] <hggdh> ka
[05:25] <rusivi> Can someone please check out bug 624386 for wishlist Importance?
[05:25] <ubot2> Launchpad bug 624386 in wine1.2 (Ubuntu) (and 1 other project) "Tera Copy Not Being Initiated (affects: 1) (heat: 234)" [Undecided,Confirmed] https://launchpad.net/bugs/624386
[05:29] <rusivi> Can someone please check out bug 633200 for wishlist Importance?
[05:29] <ubot2> Launchpad bug 633200 in wine1.2 (Ubuntu) "Wine does not recognize the Russian and Ukrainian keyboard layout (affects: 1) (heat: 6)" [Undecided,New] https://launchpad.net/bugs/633200
[05:30] <micahg> rusivi: not everything is wishlist
[05:31] <micahg> rusivi: bug 624386 is not wishlist
[05:31] <ubot2> Launchpad bug 624386 in wine1.2 (Ubuntu) (and 1 other project) "Tera Copy Not Being Initiated (affects: 1) (heat: 234)" [Undecided,Confirmed] https://launchpad.net/bugs/624386
[05:32] <micahg> rusivi: have you read the guide on how to triage?
[05:32] <rusivi> micahg: I don't think everything is a wishlist ;) However, did you read the upstream bug?
[05:32] <micahg> rusivi: yes, there's an error on launch, that seems like a bug in wine, not a feature request
[05:33] <micahg> it's P2 normal which isn't a wishlist importance upstream
[05:33] <rusivi>  "Austin English      2010-08-26 09:09:36 CDT With wine-1.3.1-182-g56b8d5d, I get: austin@midna:~/.wine/drive_c/Program Files/TeraCopy$ wine TeraCopy.exe fixme:psapi:EnumDeviceDrivers ((nil), 0, 0x6fea70): stub fixme:psapi:EnumDeviceDrivers (0x580000, 64, 0x6fea70): stub and it hangs. Though based on the program's description, it may be installing device drivers, which won't work in wine."
[05:35] <micahg> rusivi: using the drivers would be wishlist, not launching because it can't handle something seems like a bug
[05:35] <micahg> IMHO
[05:35] <rusivi> micahg: my cursory understanding of this is that it doesn't launch b/c the drivers cannot be installed.
[05:35] <rusivi> micahg: :D
[05:40] <micahg> rusivi: fix released in Ubuntu is when the package hits the archive, not when upstream releases a version
[05:40] <micahg> bug 614546
[05:40] <ubot2> Launchpad bug 614546 in wine1.2 (Ubuntu) (and 1 other project) "wine 1.2 won't install ispq9.msi (affects: 1) (heat: 6)" [Undecided,Fix released] https://launchpad.net/bugs/614546
[05:41] <rusivi> micahg: As per https://launchpad.net/~ubuntu-wine/+archive/ppa this is released in Ubuntu.
[05:41] <rusivi> This was noted in the bug 614546
[05:41] <ubot2> Launchpad bug 614546 in wine1.2 (Ubuntu) (and 1 other project) "wine 1.2 won't install ispq9.msi (affects: 1) (heat: 6)" [Undecided,Fix released] https://launchpad.net/bugs/614546
[05:41] <micahg> rusivi: no, that's not considered released in Ubuntu
[05:41] <micahg> !status | rusivi
[05:41] <ubot2> Factoid 'status' not found
[05:41] <rusivi> micahg: Ok, np
[05:42] <micahg> rusivi: please read: https://wiki.ubuntu.com/Bugs/Status
[06:23] <cjae> does anyone care when I report bugs here?
[06:24] <cjae> not trying to be sacastic
[06:24] <rusivi> cjae: what's your bug bud?
[06:24] <micahg> cjae: sure, just 80k bugs is a lot for 300 people
[06:24] <cjae> oh ok
[06:24] <micahg> cjae: if you see it's not being looked at feel free to pop in with the bug # and ask someone to triage
[06:25] <cjae> kdm in kde 4.5 on 10.04 scrambles screen on log out from kde
[06:26]  * cjae just wanted to be sure I wasnt putting stuff on here for nothing :)
[06:26] <rusivi> cjae: could you take a picture/video of this phenomenon?
[06:27] <cjae> when you install ubuntu desktop to kubuntu 10.04 it really messes up the soundcard config,can post cad specs of someone tells me how, I could do it slowly through different ways
[06:28] <cjae> rusivi: how record desktop?
[06:28] <micahg> cjae: you need to file the bugs first
[06:28] <cjae> card specs*
[06:28] <micahg> cjae: if you have support questions, #ubuntu is the place
[06:29] <cjae> they are definatley bugs, um I report them as I find them, hoping someone will read log? I not sure if I have time to fill them all
[06:30] <micahg> cjae: file the ones you feel are important
[06:30] <rusivi> cjae: if you have a video capable camera or camcorder please documenting this, then you would bug against your graphics card driver via ubuntu-bug package
[06:31] <cjae> hhmm could take a pic I guess
[06:32] <cjae> I am registered a ubuntu bug reporting, but I get tones of email form it too even from unsupported distros still :/
[06:32] <rusivi> cjae: However, being realistic, if the only time you notice a graphical distortion is upon log out your bug will probably not be on high priority... but your welcome to bug! Could be indicative of some other, known related graphical issue.
[06:32] <cjae> pressing escape seems to fix it
[06:32] <micahg> rusivi: that depends on the bug
[06:34] <cjae> well its bad cause unless you know to press escape you have to drop tp tty and login that way (which puts terminal in root mode btw (using startx))
[06:35] <micahg> cjae: a bug can serve as documentation especially if there's an easy workaround
[06:40] <cjae> brb
[06:51] <cjae> is launchpad really this slow?
[06:53] <cwryuu> seems to work reasonably well here
[07:15] <lifeless> cjae: hi, if you want to talk lp performance, please do hop into #launchpad
[07:15] <lifeless> short story, we're working on it
[07:25] <shazz-ubuntu> Hi there
[07:27] <cjae> yea got one done https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/637808
[07:27] <ubot2> Launchpad bug 637808 in xorg (Ubuntu) "only using properitary ati driver can plasma (panasonic plasma) via hdmi be used (affects: 1) (heat: 6)" [Undecided,New]
[07:27]  * cjae thinks that took forever
[07:28] <shazz-ubuntu> I'd like to help out on the bugs, any tips/tutorials?
[07:30] <cjae> apport seems to have a bug too
[07:32] <cjae> in kde 4.5 I press alt f2 type ubuntu-bug and it asks me a things like xorg or sound etc... when I press sound it asks like I press one of the options for issues with a tty terminal or ssh problem
[07:32] <cjae> even when I select other problem
[07:33] <nigelb> cjae: that sounds like a hook bug
[07:34] <nigelb> cjae: it works fine for me in lucid ubuntu though.  Are you using kubuntu-desktop after installing ubuntu or fresh kubuntu install?
[07:35] <cjae> kubuntu fresh then kde 4.5 backport repo
[07:36] <nigelb> maverick or lucid?
[07:37] <vish> shadeslayer: documentation: http://wiki.ubuntu.com/HelpingWithBugs
[07:37] <vish> oops!
[07:37] <nigelb> heh
[07:37] <vish> shazz-ubuntu: ^ that was meant for you
[07:37] <shazz-ubuntu> thanks!
[07:38] <cjae> nigelb: lucid
[07:38] <vish> nigelb: my biggest regret is that no one ever seems to be able to tab fail and ping you ;p
[07:39] <nigelb> vish: that did happen ;)
[07:39] <vish> nigelb: not often enough!
[07:39] <nigelb> Aha
[07:39] <nigelb> jealousy :p
[07:39] <cjae> ya apport here is totally pooched all of the options when selected give crazy responses
[07:40] <nigelb> ok, then something is totally wrong.
[07:58] <cjae> and another https://bugs.launchpad.net/ubuntu/+source/apport/+bug/637819
[07:58] <ubot2> Launchpad bug 637819 in apport (Ubuntu) "apport-kde gives false options (affects: 1) (heat: 6)" [Undecided,New]
[08:10] <cjae> and all I can do tonight https://bugs.launchpad.net/ubuntu/+source/kdebase-workspace/+bug/637825 wasnt sure how to add the pics
[08:10] <ubot2> Launchpad bug 637825 in kdebase-workspace (Ubuntu) "kdm scrammbles screen on kde 4.5 logout kubuntu 10.04 (affects: 1) (heat: 6)" [Undecided,New]
[08:50] <vish> why did bug day shift to a tuesday?
[08:50] <vish> jibel: ^ ?
[08:51] <jibel> hey vish, there are 2 bug days this week. brasero will be coming on thursday.
[08:51] <vish> jibel: ah!  then it can only be more fun ;)
[08:52] <jibel> vish, it was discuss during qa meeting last week.
[08:52]  * vish nods
[08:52] <jibel> vish, many people have already upgraded to maverick and we wanted to triage the installation and upgrade failure to maverick.
[08:52] <jibel> vish, ... before the official release :)
[08:53] <vish> yeah sounds neat...
[09:00] <jibel> vish, i doesn't look like being a great success :(
[09:03] <vish> :(
[09:05] <jibel> stbulicek, hello, did you had time to triage a few bugs last week ?
[09:38] <vish> jibel: are you able to "hugday close  ###"  ?
[09:38] <jibel> vish, didn't tried.
[09:38] <vish> i get "..has already been marked as triaged by '<<BR>>'  "
[09:39] <vish> looks like the wiki might be setup a bit wrong.. , not sure though..
[09:39] <jibel> vish, let me check that
[09:40] <jibel> vish, right, there are <<BR>> instead of blank cell for the triager columns.
[09:40] <vish> yeah..
[09:40] <jibel> vish, you're editing it could you please do a search and replace or do you want me to do it ?
[09:41] <vish> jibel: oh! , i thought you were doing it.. ;)  if not, i can do it ..
[09:41] <jibel> vish, doing then.
[09:42]  * vish cancels edit lock ..
[09:43] <jibel> vish, done. could you try again to close a bug ?
[09:44] <vish> jibel: \o/ works now :)
[09:44] <vish> thanks..
[09:44] <jibel> Cool, many thanks!
[14:22] <cwryuu> does anyone know what package / process produces the directory /lib/modules/2.6.32-24-generic/source/include/? It's causing bug 635945 but I can't seem to figure out how to get the solution
[14:22] <ubot2> Launchpad bug 635945 in oss4 (Ubuntu) "This error occurred while the installation of oss4-dkms. (affects: 1) (heat: 6)" [Undecided,New] https://launchpad.net/bugs/635945
[14:42] <MrBeanAC> https://bugs.launchpad.net/ubuntu/+source/aptitude/+bug/508545 confirmed for Ubuntu 10.04.1 Server (64bit)
[14:42] <ubot2> Launchpad bug 508545 in aptitude (Ubuntu) (and 1 other project) "Aptitude ignores /etc/apt/preferences.d/* (affects: 22) (dups: 1) (heat: 106)" [Undecided,Confirmed]
[14:58] <cwryuu> I keep seeing a lot of "dpkg (subprocess): unable to execute installed post-removal script: Exec format error" in bugs
[15:29] <cwryuu> Confirmed 636691, same setup
[15:46] <hggdh> did the TTY jump keys change on Maverick? Ctrl-Alt-F1 puts me on TTY1, but I can only get back via Super-F7
[15:54] <jibel> hggdh, both ALT+F7 and Super+F7 bring me back to X
[15:55] <hggdh> jibel: but not Ctrl-Alt+F7, correct?
[15:55] <jibel> hggdh, Ctrl+Alt+F7 too
[15:55] <hggdh> weird
[15:56] <hggdh> for me only Super+F7 works :-(
[15:56] <hggdh> oh joy. Another remapping, I guess
[15:57] <jibel> hggdh, Same behavior on another machine.
[15:58] <hggdh> jibel: it is personal. It is my laptop on its holy crusade to drive me crazy.
[16:51] <abhijit> hi
[16:54] <yofel> shadeslayer: depends what you're talking about
[16:54] <shadeslayer> yofel: the BC application
[17:19] <algnod_> isnt there a meeting on this channel today
[17:19] <yofel> algnod_: in 40 minutes
[17:20] <yofel> 17:00 UTC
[17:20] <abhijit> yofel, topic for meeting?
[17:20] <yofel> https://wiki.ubuntu.com/BugSquad/Meeting
[17:20] <abhijit> yofel, ok
[17:31] <algnod_> thanks yofel
[17:48] <cwryuu> hmm, wonder if I should focus more on testing for Maverick bugs or Lucid bugs
[17:49] <abhijit> maverick
[18:00] <yofel> pedro_, bdmurray: ping - meeting time?
[18:00]  * bdmurray is lurking
[18:00]  * charlie-tca waves
[18:03] <yofel> wb hggdh :)
[18:03] <hggdh> thank you, yofel
[18:04] <yofel> ok, the agenda is https://wiki.ubuntu.com/BugSquad/Meeting for those that don't know yet
[18:04]  * nigelb waves
[18:04] <hggdh> sorry for the delay, Maverick surprises
[18:04] <yofel> heh
[18:05] <hggdh> OK. yofel -- I drive, or you?
[18:05] <yofel> better you, I'll be on and off since I'm a bit busy here
[18:05] <hggdh> no problem. Folks, I would like to start with any mentor's update
[18:06] <nigelb> o/
[18:06] <hggdh> from my side, both of mine suddenly vanished
[18:06] <SpamapS> o/
[18:06] <nigelb> I had 2 students assigned to me.  No response from mail and no contact or pings on IRC.
[18:06] <hggdh> well, holstein did not vanish, but does not have time now
[18:06] <charlie-tca> mine are gone
[18:06]  * nisshh thinks this is depressing
[18:06] <jibel> o/
[18:07] <hggdh> I am considering we need a chance on the programme
[18:07] <holstein> hggdh: :/
[18:07] <nigelb> better than a long list of mentorship applicats which we're not processing.
[18:07] <nigelb> Maybe we should do mentorship like packge training.
[18:07] <jibel> brief ping on IRC with both students but no reply.
[18:07] <jibel> One of them answered to my first email.
[18:08] <kamusin> from here nothing new, devildante is still working hard every day and the other one is still searching nemo  (never reply first mail) :)
[18:08] <nigelb> Every fortnight we have a generic Q and A session and people can come in and ask all their doubts </suggestion>
[18:08] <hggdh> yes, but... we may consider requiring presence on IRC. And require time available
[18:08] <hggdh> because I feel it is easy to ask, but difficult to commit
[18:09] <charlie-tca> I thought we already required time available?
[18:09] <hggdh> charlie-tca: not enforced, I think:-(
[18:10] <hggdh> what about we think about that, and then change as needed (or as considered needed, which is almost the same)
[18:11] <hggdh> Next on agenda: Regression tags and workflow.
[18:11] <charlie-tca> We need to at least enforce the available times
[18:12] <hggdh> some of us have been thinking about the current process with regression tags, and consider we need a change to make it simpler
[18:12] <hggdh> jibel: what to take over?
[18:12] <hggdh> charlie-tca: +1
[18:13] <hggdh> there I go, then
[18:13] <jibel> hggdh, while reviewing the bugs with a regression-* tag it appears that the current process is somewhat confusing.
[18:13] <jibel> hggdh, you do or I ?
[18:13] <hggdh> you do it :-)
[18:13] <jibel> great!
[18:13]  * hggdh sits down and grabs some popcorn
[18:14] <njin> pedro_: around?
[18:14] <jibel> a large part of the reports were not correctly triaged and we had to understand why
[18:15] <jibel> pedro_, hggdh, I and others have been digging into it.
[18:15] <shadeslayer> hey guys :)
[18:15] <jibel> and we came to the conclusion that it could be simpler.
[18:15] <jibel> hey shadeslayer
[18:15]  * shadeslayer sits down next to hggdh for some popcorn
[18:16] <shadeslayer> jibel: hey :)
[18:16] <jibel> The part which appeared to be un-useful was the use of the regression-potential tag.
[18:16] <jibel> Does anyone know the use of that tag ?
[18:16]  * hggdh does ;-)
[18:17]  * charlie-tca raises hand
[18:17] <yofel> I do, but it's hard to keep track once the release is released and change all tags :/
[18:17] <jibel> hggdh, please eat your popcorn in silence ;)
[18:17] <charlie-tca> yofel: +1
[18:17] <jibel> yofel, you hit the point.
[18:18] <charlie-tca> It is kind of nuts to try and keep up with
[18:18] <jibel> most of the time regression-potential is a backseat for regression-release bugs.
[18:19] <jibel> So, we come with the proposition to remove the regression-potential tag and tag with regression-release and nominate for the affected release whatever the release is ( devel or release)
[18:19] <jibel> we would have 3 tags to track regressions
[18:20] <jibel> regression-release if the affected release is the release
[18:20] <jibel> regression-updates if the regression comes from updates
[18:20] <jibel> regression-proposed if the regression  is in -proposed
[18:20] <yofel> isn't nomination only for SRUs? wouldn't adding a release tag as apport already does it be sufficient?
[18:21] <hggdh> no, not really, yofel. First, a regression may impact more than one release;
[18:21] <jibel> You need to be able to track what is the status of the regression for each release.
[18:21] <hggdh> second, the apport release tag only tells us on what release it was found
[18:21] <yofel> we can add tags for those releases, changing tags is easier than suffer from a rejected nomination
[18:22] <charlie-tca> It would certainly simply the use of the tags. And, if it is fixed before the devel release is final, it does not really matter what the tag was.
[18:22] <yofel> jibel: right, bug only developers can open release-tasks
[18:22] <yofel> s/bug/but/
[18:22] <hggdh> (a bit late, but...) yofel: third, a regression is always an SRU candidate
[18:23] <charlie-tca> You would still have the tag, but at least the reporter will know if it will be fixed in the releases available, too.
[18:24] <yofel> hggdh: sure, but how do you handle it if someone nominates a release that it doesn't seem to affect, the nomination gets rejected, and then someone notices that it affects the release after all, you can't re-nominate afaik
[18:24] <jibel> bdmurray ^
[18:24] <hggdh> yofel: package maintainers, and some others, can override (AFAICR)
[18:24] <pedro_> yofel, well that's a lp bug that needs to be fixed ;-)
[18:25] <bdmurray> I agree with pedro_ here
[18:25] <nigelb> cookies for fixing it ;)
[18:25] <pedro_> and what hggdh said is true
[18:25] <pedro_> you can't renominate but you can approve that
[18:26] <pedro_> so i think we can workaround that for now adding a comment and pinging someone with the rights on IRC or by email to approve that
[18:26] <yofel> ok, I guess I can live with that
[18:26] <pedro_> good point though yofel
[18:27] <yofel> btw, wouldn't it make more sense to make the bug supervisor open release task and the maintainer can close it won't fix if necessary?
[18:28] <hggdh> this is actually what happens -- the maintainers close wontfix if needed
[18:28] <hggdh> but I would rather have the nomination with less access restrictions
[18:29] <pedro_> the approval/rejection of the nomination you mean?
[18:29] <hggdh> yes
[18:29] <pedro_> cause everybody can nominate
[18:29] <pedro_> ah yes
[18:30] <yofel> sure, but I know bugs that are fixed in the devel release and that would justify a SRU, but nobody is there that knows how to do it, and later they're forgotten as the bug is 'fix released'
[18:30] <jibel> yofel, an SRU is not necessarily a regression.
[18:31] <yofel> right, I'm getting off topic here, sorry
[18:31] <jibel> and that's 2 different workflow.
[18:31] <jibel> the developer needs a mean to efficiently track regression.
[18:33] <jibel> and we need to make it simpler for the bugsquad to clearly triage regression bugs.
[18:34] <jibel> any other question/comment/complain ?
[18:34] <yofel> ok, so 3 tags with nominations it is then?
[18:34] <jibel> yofel, right
[18:34] <yofel> good,  +^
[18:34] <yofel> *+1
[18:35] <hggdh> yes -- actually, pretty much like it is done nowadays with apport, 3 tags + the release tag it was found on
[18:35] <hggdh> and nominations for the affected releases (as they are identified)
[18:35]  * DrKenobi just arrived!
[18:36] <hggdh> cheers, DrKenobi
[18:36] <DrKenobi> hi! hggdh
[18:36] <hggdh> anybody disagrees? If so, why?
[18:36] <charlie-tca> agreed here
[18:37] <hggdh> all: please note that this is not yet in place -- we are trying to find out itf it makes sense, and if there is a gain
[18:38] <nigelb> +1 ; sounds good overall.  yofel did raise the concerns I'd have.
[18:38] <yofel> I guess it makes sense to check all -potential bugs and use the new policy for natty?
[18:40] <hggdh> yofel: yes, as soon as we have agreement from all (meaning triagers and -devel)
[18:40] <hggdh> oh
[18:40] <hggdh> one more thing:
[18:41] <hggdh> If a bug is tagged regression-<whatever> I think the bug should contain data on what was the last working version
[18:41] <hggdh> ideally, this would be the full version string of the affected package, but I could settle for Ubuntu version...
[18:42] <charlie-tca> That makes sense. Otherwise it is pretty hard to determine it even is a regression
[18:42] <yofel> agreed
[18:42] <hggdh> cool
[18:42] <hggdh> any more comments on that?
[18:44] <hggdh> OK. Before moving on: please comment as needed on the ML; I will put up a wiki page with the options we considered, and pros/cons on each
[18:44] <hggdh> and will announce it on the MLs
[18:44] <hggdh> now, going on: Review of the ReportingBugsAlternate page
[18:44] <hggdh> https://wiki.ubuntu.com/MohamedAmineILIdrissi/ReportingBugsAlternate
[18:45] <hggdh> What do you think?
[18:45] <hggdh> (keep in mind that we intend to replace the current ReportingBugs with this version)
[18:45] <charlie-tca> I thought it was a good re-write.
[18:45] <DrKenobi> looks great!
[18:45] <yofel> nice page, I was looking for the 'writing a useful bug report' section at first until I noticed he merged it into the reporting steps
[18:45] <hggdh> yeah, kudos to devildante for the work!
[18:46] <charlie-tca> Other than the idea that people seem to think server editions don't count as valid release versions, it looks good
[18:46] <hggdh> oops
[18:46]  * hggdh goes back hunting for this
[18:47] <yofel> oh right, he removed 6.06 ^^
[18:47] <charlie-tca> to clarify, 6.06 and 8.04 are still valid versions. 6.06 is good for another year, and 8.04 for three more, and people still need to report bugs in them.
[18:47] <yofel> 8.04 is listed I think
[18:47] <hggdh> right, thank you.
[18:48]  * hggdh will add in 6.06
[18:49] <yofel> the extra options section will need an update btw, since the last LP release you can set an initial status/importance/assigned person/milestone and maybe other things dependent on the permissions too
[18:50] <jfi> when a bug exist in a ubuntu release, but has been fixed upstream, should we register a bug in launchpad or just wait the synchronization ?
[18:50] <yofel> at least it needs a new screenshot, the current one is too large
[18:50] <jcastro> jfi: if the bug already exists link it
[18:51] <jcastro> (more often than not I found they are already reported in lp)
[18:51] <hggdh> OK. I updated the ReportingBugsAlternate with Dapper Drake
[18:51] <DrKenobi> The images should have a frame, they are a bit confusing
[18:52] <hggdh> DrKenobi: please feel free to add it in ;-)
[18:52] <jfi> jcastro, I did not find it in LP, it is quite recent, fixed the 09/10, appears in ubuntu since this morning, but maybe I miss it
[18:52] <hggdh> All: please update the page as needed
[18:52] <hggdh> any other comments here?
[18:53] <hggdh> if not... Open Mike: anybody wants to raise an issue for us?
[18:53] <charlie-tca> umm, the last two or three times I wanted to use apport-collect, it would refuse until I subscribed to the bug. It doesn't really want anyone but the original reporter to add to the bug,.
[18:53] <nigelb> Kernel folks love that feature.
[18:54] <yofel> charlie-tca: it should tell you that you weren't subscribed to the bug
[18:54] <yofel> charlie-tca: and that was implemented to reduce apport-collect spam
[18:54] <charlie-tca> It does. Something like "you didn't file this, you are not subscribed, you can not do this"...
[18:54] <DrKenobi> hggdg, I'll try to do it this week
[18:54] <nigelb> Also, it is fairly older feature.
[18:54] <yofel> right, might not be the best formulation, but it is accurate
[18:55] <hggdh> charlie-tca: perhaps a better error message would help?
[18:55] <charlie-tca> But we have it in the page to use apport-collect, shouldn't we tell them to subscribe first?
[18:55] <charlie-tca> ooops
[18:55] <charlie-tca> never mind, misread the paragraph
[18:56] <shadeslayer> btw.. my bug control application is still pending .. ( just thought i should let you guys know :D )
[18:56] <yofel> hggdh: ^ (he as a +1 from me and pedro)
[18:57] <hggdh> Oh, Rohan, right?
[18:57] <shadeslayer> aye
[18:57] <pedro_> also remember that any member of the Ubuntu Bugcontrol can comment in the application for new members
[18:57] <pedro_> so don't be shy
[18:57] <hggdh> pedro_: would you mind? ;-)
[18:57] <pedro_> hggdh, i was waiting for someone else to also reply to that :-)
[18:58] <hggdh> this is actually a good point: bug-controllers, *please* do comment. We have at least one other pending application
[18:58]  * charlie-tca mumbles about starting to do that soon
[18:58] <hggdh> pedro_: we have the necessary +1s, and it is already a week, I think
[18:58] <pedro_> roger that
[18:59] <hggdh> shadeslayer: you have been approved, now it is just a question of one of us getting it done ;-)
[18:59] <shadeslayer> \o/
[18:59] <shadeslayer> today is a really good day for me :P
[19:00]  * hggdh goes to get it done
[19:00] <pedro_> shadeslayer, you're all set, thanks for the help and welcome :-)
[19:00] <shadeslayer> first my plasma patch got approved .. just needs to be committed and now this :D
[19:00]  * shadeslayer hugs pedro_ hggdh and yofel
[19:00] <yofel> heh
[19:01] <yofel> shadeslayer: welcome to BC ;)
[19:01] <hggdh> oh, pedro_ was faster :-)
[19:01] <pedro_> :-P
[19:01] <shadeslayer> :D
[19:01] <hggdh> folks -- I have another meeting now. pedro_, can you take over please?
[19:02] <pedro_> is there anything else to discuss?
[19:02] <yofel> I think we're finished anyway if nobody has any more questions about the reporting page
[19:02] <pedro_> hggdh, thanks a lot for chairing :-)
[19:03] <hggdh> welcome, pedro_
[19:03] <jibel> thank you hggdh!
[19:03] <pedro_> alright, let's adjourn , thanks everybody for participate in the meeting and to hggdh for chairing
[19:03] <charlie-tca> Thank you , hggdh
[19:03] <nigelb> \o/
[19:03] <pedro_> next meeting on October 12th
[19:03] <hggdh> and tahnk you to yofel for holding the fort until I could reboot
[19:03] <yofel> yw :)
[19:03]  * yofel hugs hggdh
[19:03]  * pedro_ -> late lunch
[19:04]  * hggdh hugs yofel -- in fact, all!
[19:04] <DrKenobi> :D
[19:04] <kamusin> lunch! :)
[19:04] <kamusin> thanks!
[19:05]  * DrKenobi Algebra :(
[19:06] <hggdh> algebra is good.
[19:07] <DrKenobi> but difficult haha
[19:07]  * hggdh remembers fondly dealing with Lie groups
[19:08] <DrKenobi> hggdh, after adding a frame to each image, where should be uploaded?
[19:08] <hggdh> DrKenobi: just update the existing page, we can always revert if needed ;-)
[19:09] <DrKenobi> hggdh, I could add a frame without modifying the image?
[19:09] <hggdh> DrKenobi: I *think* you can, using the wiki artifacts
[19:09] <DrKenobi> ok
[19:10] <DrKenobi> hggdh, I always forget to tell that the event at the Google Calendar is wrong. I always have to change the time.
[19:11] <hggdh> DrKenobi: will look at it
[19:11] <DrKenobi> I think it's set at 15:00 UTC
[19:11] <hggdh> I have mine set to 1700UTC...
[19:12] <DrKenobi> But every time I copy the event to my calendar the time is wrong. It only happens with this event. I dont know why...
[19:13] <hggdh> no, you are right, the time is wrong
[19:13] <DrKenobi> Ok :)
[19:14] <hggdh> pedro_: how is it we update meetings on the calendar?
[19:19] <nigelb> kamusin: Hugs. I see you're catching up with a bunch of rhythmbox bugs :)
[19:19] <kamusin> heh :)
[19:21] <rusivi> Can someone please check out bug 8952 for Wishlist Status?
[19:21] <ubot2> Launchpad bug 8952 in synaptic (Ubuntu) "There should be a section "Office" in the archive (was: Openoffice should be in section "Word processing", not "Editors".) (heat: 1)" [Low,Confirmed] https://launchpad.net/bugs/8952
[19:24] <Tetsuo55> is the retracer catching up yet?
[19:25] <Tetsuo55> i saw it scan some of my older bug reports and closing them with trace failed, mismatched versions
[19:26] <DrKenobi> hggdh, I've just finished adding frames to the images. I hope people like it.
[19:27] <hggdh> DrKenobi: perfect, thank you!
[19:28] <BlackZ> hey hggdh ;)
[19:28] <hggdh> cheers BlackZ, how's life?
[19:29] <BlackZ> hggdh: good, thanks! what about yours? :)
[19:30] <yofel> Tetsuo55: I heard it was fixed a few days ago and it's now processing the backlog
[19:30] <hggdh> BlackZ: the usual... Good, but I could live with a bit less excitement :-)
[19:30] <Tetsuo55> yofel:  ill guess ill wait with reporting crashes till its a bit more up to speed
[19:31] <yofel> I don't think you have to, I got a python bug checked today and I reported that yesterday
[19:41] <rusivi> Can someone please check out bug 10728 for Wishlist Status?
[19:41] <ubot2> Launchpad bug 10728 in openssh (Ubuntu) "SSH UTF-8 character mangling (heat: 1)" [Medium,Confirmed] https://launchpad.net/bugs/10728
[20:02] <pedro_> hggdh, i'll check with the fridge folks re calendar
[20:03] <hggdh> pedro_: oh yes, that's where... thank you
[20:03] <nigelb> hggdh: what about it?
[20:04] <hggdh> nigelb: the time for the bugsquad meeting is wrong
[20:05] <nigelb> hggdh: ah, you'd want nhandler I think :)
[20:05] <nigelb> he's got access to those stuff :)
[20:30] <charlie-tca> hmm, I need to insall bzr to use bughelper now? What happened to "easy to use"?
[20:31] <nigelb> lol, that's part of easy to fix I guess
[20:31] <charlie-tca> It seems like a lot of steps the wrong way
[20:32] <nigelb> charlie-tca: for example if you decide you want to fix that, you'll still need bzr :p
[20:32] <charlie-tca> I don't program at all. I don't think I would decide to fix ...
[20:33] <nigelb> Ah
[20:35] <charlie-tca> but I still can't use bughelper without bzr, which I have no use for
[20:42] <abhijit> bye
[20:48] <yofel> should I reassign bug 636404 to python? I never saw 'Fatal Python error: Immortal interned string died.' yet o.O
[20:49] <ubot2> Launchpad bug 636404 in apport (Ubuntu) "package python-problem-report 1.14.1-0ubuntu7 failed to install/upgrade: subproces installed post-installation script gaf een foutwaarde 134 terug (affects: 1) (heat: 6)" [Undecided,New] https://launchpad.net/bugs/636404
[21:08] <xteejx> Hi all. Can bug 604809 be changed to Triaged?
[21:08] <ubot2> Launchpad bug 604809 in upower (Ubuntu Maverick) (and 1 other project) "upowerd crashed with SIGSEGV in idevice_get_uuid() (affects: 50) (dups: 5) (heat: 293)" [Medium,Confirmed] https://launchpad.net/bugs/604809
[21:09] <xteejx> btw hi everyone, sorry I've been away so long!!
[21:11] <yofel> hey xteejx!
[21:11] <xteejx> yofel: Hey!! :)
[21:11]  * yofel knows nothing about udev and leaves that bug alone, sry
[21:12] <xteejx> No worries yofel, I changed machines and now can't boot Ubuntu Mverick on this PC without serious X problems, so I can no longer provide info for it, but there are plenty of dupes and afected users :)
[21:12] <xteejx> Thought there should be enough info there
[21:40] <njin> pedro_:around?
[21:40] <pedro_> njin, yeah
[22:47] <algnod> hi, i am new to triaging and i am wondering if someone has some time to spare to walk me through a triaging example
[22:49] <jibel> rusivi, please don't change confirmed/triaged bugs in synaptic. thank you.
[22:50] <rusivi> jibel: k np
[22:50] <micahg> rusivi: pehaps you should look at new/incomplete bugs
[22:51] <rusivi> jibel: What about bugs that have not had any progress since End of Life releases?
[22:52] <jibel> rusivi, EOL doesn't mean that the bug is gone. Try to reproduce it with the latest release.
[22:53] <rusivi> jibel: I thought asking bug reporter to update and report back, simultaneously marking a confirmed/triaged bug incomplete was in order. What do you think is best?
[22:53] <rusivi> jibel: in EOL case only btw
[22:54] <rusivi> BTW, as per https://wiki.ubuntu.com/Bugs/Status -> "If you have to ask the reporter questions, set the bug to Incomplete"
[22:55] <nigelb> rusivi: Just emphasizing what micahg said, don't assume something is fixed.  Test and confirm that its fixed please.  You just closed something as fix released, have you verified it?
[22:55] <rusivi> nigelb: Which bug specifically are you referring to?
[22:56] <jibel> rusivi, for synaptic at least, when it's confirmed/triaged the issue is still relevant even if it's EOL.
[22:56] <nigelb> bug 24281
[22:56] <ubot2> Launchpad bug 24281 in planner (Ubuntu) (and 1 other project) "(Breezy) Planner Gantt view vertically misaligned (heat: 10)" [Medium,Fix released] https://launchpad.net/bugs/24281
[22:56] <rusivi> nigelb: let me check real quick
[22:57] <yofel> rusivi: same for bug 24626: did you check if the fix has made it to ubuntu already?
[22:57] <ubot2> Launchpad bug 24626 in apt (Debian) (and 1 other project) "Too many repositories "dynamic mmap ran out of room" (affects: 2) (dups: 30) (heat: 286)" [Unknown,Fix released] https://launchpad.net/bugs/24626
[22:57] <rusivi> nigelb: seems I mis-set it. I should have set as incomplete?
[22:58] <nigelb> Should have left it alone or tested and marked confirmed or fix released depending on result of testing
[22:58] <rusivi> yofel: regarding that bug, did not confirm. However, upstream marked fixed.
[22:58] <nigelb> I didn't have access to an ubuntu system when I was triaging the patch (was on a debian box)
[22:58] <yofel> rusivi: yes, but the ubuntu task is only fix released if the fix has reached the devel release,
[22:59] <yofel> note: the bug is fixed, I checked it
[22:59] <rusivi> yofel: nice!
[22:59] <yofel> rusivi: easiest way for this case was: check that the changelog entry from debian is in the ubuntu changelog
[22:59]  * nigelb hugs bdmurray 
[23:00] <nigelb> bdmurray: I tried and lost time to work on a tool like that ;)
[23:00] <rusivi> yofel: k
[23:00] <yofel> nigelb: what tool?
[23:00] <nigelb> yofel: http://bazaar.launchpad.net/~ubuntu-bugcontrol/ubuntu-qa-tools/master/annotate/head%3A/launchpadlib-scripts/forward-bug-to-debian.py
[23:00] <bdmurray> nigelb: oh, sorry about that!
[23:01] <yofel> oh, that sounds useful
[23:01] <nigelb> bdmurray: no problem :) If something works, rocking.  I knew you'd get there once you get 2 minutes of time :D
[23:01] <yofel> hm, maybe I should clean up my lp-set-expired.py and send that there too ^^
[23:01] <nigelb> yofel: please do :)
[23:02] <nigelb> its nice to accmulate all of them together
[23:02] <Marcus> hello all, new to this, so plese bear with me.... I have seen a bug in the upgrade tool where it will not prompt for the sudo passoword, where would I file this?
[23:02] <yofel> you can get it here until then: https://code.edge.launchpad.net/~yofel/+junk/lp-scripts
[23:18] <Dink> 388.839967] [drm:drm_mode_getfb] *ERROR* invalid framebuffer id ... Trying to figure out where/why this is happening. It seems to be happening when I move gnome-terminal around and switch back and forth between applications to it.
[23:20] <kklimonda> Dink: you will have more luck on #ubuntu-x channel but imo it's a kernel bug
[23:20] <Dink> in my X0rg.0.log file I get ... [  1128.245] (EE) intel(0): Couldn't create pixmap for fbcon
[23:21] <Dink> ahh kernel ok. Will poke around to see if its been reported yet.
[23:24] <BUGabundo> evening
[23:24] <kklimonda> hey BUGabundo :)
[23:33] <Marcus> Found my bug was already reported. seems it goes back to around 9.04 of ubuntu. #414181.  annoyance bug, but it would be great if it got fixed....
[23:33] <Marcus> anyone looking at update-manager?
[23:34] <maco> Marcus: if you say bug before the bug number the bot does useful things. just a # doesnt though
[23:34] <maco> bug 414181
[23:34] <ubot2> Launchpad bug 414181 in update-manager (Ubuntu) (and 2 other projects) "Update Manager, "install" button does nothing when u-m was opened by itself (affects: 29) (dups: 5) (heat: 164)" [Undecided,Confirmed] https://launchpad.net/bugs/414181
[23:38] <hggdh> yofel: heh. We both confirmed a fix released right now...
[23:38] <yofel> :P
[23:38] <Marcus> Thanks maco....
[23:42] <Marcus> Ok, now that I have found said bug, does anyone know of a way to role a package back to an earlier version to try to debug this one? I can get it to cause it if I come out of sleep and there is an update waiting....
[23:44] <maco> Marcus: you can use apt-get install foo=version
[23:44] <maco> or you can use dpkg -i --force-downgrade  foo.deb
[23:44] <maco> to install an old version
[23:50] <rusivi> micahg: I just changed my bug search to focus on just new/incomplete, as you suggested :D
[23:51] <lifeless> rusivi: thanks
[23:51] <micahg> rusivi: you might want to consider requesting a mentor
[23:52] <lifeless> rusivi: when looking at confirmed/triaged bugs, please do not push 'is it still a problem' onto the bug, instead reproduce it yourself (and if you can't because you don't have the right hardware/etc, don't say anything on th ebug)
[23:52] <lifeless> if you have the right setup so you should be able to reproduce it and it doesn't happen, look at the relevant code and confirm that its fixed.
[23:57] <Marcus> maco: if I force a downgrade, will apt remember that I forced the downgrade and show there is a newer version, or will it mark it as a "downgraded" package and not show a new version?
[23:57] <maco> Marcus: when you run apt-get update itll offer the upgrade again
[23:57] <maco> youd have to lock the lower version to make it hold back the new upgrade, but even then itd show that it exists i believe
[23:58] <Marcus> That is better than the option I was going to do, un-install, install off the cdrom, then upgrade.... Thanks!
[23:59] <rusivi> micahg: I sent a mentor request already about a week or two ago. No response yet...