[00:08] <LimCore> is there some count in user's profile on LP related to patches that made it into ubuntu or upstream? like in karma
[00:09] <persia> No.
[00:14] <Jordan_U> The instructions given in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/453579/comments/200, "dd if=<iso name> of=/dev/<ext*4* partition>/<some file name> bs=512MB " are potentially dangerous since it suggests outputting to the device node in /dev itself rather than a file on that filesystem. Is it an over reaction to post a comment prominently warning against following these directions?
[00:14] <ubot4> Launchpad bug 453579 in linux (Ubuntu Karmic) (and 3 other projects) "in-place corruption of large files *without fsck or reboot* reported with linux 2.6.31-14.46 on ext4 (affects: 22) (dups: 1)" [Critical,Triaged]
[00:15] <LimCore> Jordan_U: imho, users are likelly to make mistakes following instructions, and user-data-loss is horrible always
[00:15] <ali12341> that wouldn't even work, would it?
[00:15] <Jordan_U> ali12341, In most cases it would just result in a syntax or permissions error
[00:16] <ali12341> file not found, i would have thought?
[00:16] <LimCore> hmm since when /dev/partition/filename  will work?
[00:16] <Jordan_U> ali12341, Depends on what they write. /dev/sda1/filename would be file not found, and /dev/sda1 /filename would give unknown option "/filename"
[00:17] <Jordan_U> That's why I am wondering if a prominent warning is appropriate or not
[00:18] <ali12341> it looks like a typo to me, they didn't mean to write /dev/ at all
[00:19] <Jordan_U> ali12341, I have no doubt that the author didn't mean that, but it is what people will read and try to follow
[00:19] <ali12341> i'd say it is appropriate then
[00:22] <Jordan_U> Does "**WARNING** Do not run the dd command in the above comment **WARNING**" and an explanation seem reasonable?
[00:23] <Jordan_U> Or is there anyone that could just fix the original comment?
[00:24] <LimCore> bug #519083 - svn security. I would like to fix it and with your help push it to ubuntu quickly :)
[00:24] <ubot4> LimCore: Bug 519083 on http://launchpad.net/bugs/519083 is private
[00:24] <persia> Comments may not be edited.
[00:24] <wgrant> The only way to edit comments is with SQL, and that facility is not used lightly.
[00:24] <LimCore> now public
[00:24] <ali12341> huh, rhett trappmann has touched this bug too... crazy
[00:25] <wgrant> Has he still just the two accounts?
[00:25] <ali12341> well, he has one less now i think
[00:26] <wgrant> Both are suspended.
[00:26] <LimCore> what is his account name on LP?
[00:26] <wgrant> r12056
[00:27] <wgrant> And 12056-wikianswers
[00:27] <hggdh> yes. So far
[00:28] <LimCore> no page with such address https://bugs.launchpad.net/~r12056   by suspended you ment deleted + with all trace removed?
[00:28] <wgrant> Suspended accounts are not visible in the web UI.
[00:29] <wgrant> (You can tell that an account is suspended because it says 'Page gone' rather than 'Page not found'.)
[00:31] <hggdh> I really wish he would pop in here so we could talk with him
[00:31] <wgrant> That would be pleasant.
[00:32] <LimCore> ok guys, actually it's me :o
[00:32] <hggdh> LimCore: right now, if you say this, you will be gone in a jiff
[00:32] <LimCore> hehe no Im joking
[00:33] <LimCore> all of mine bug reports make sense, and nothing like missing keyboard ;)
[00:33] <LimCore> most of my report are very helpfull I hope
[00:39] <LimCore> what did he do, created nonsense reports?
[00:45] <hggdh> went on assigning bugs to random people/teams, nominating everything, etc
[00:47] <LimCore> you could develop some anti-spam tools, or update existing
[00:47] <LimCore> if something then perhaps I can help review some ideas
[00:47] <yofel> there was a nonsense report I think, but the nonsense bug-elevation-team was more entertaining
[00:48] <LimCore> perhaps allow given actions only after some time and creating a few bug reports (that where not deleted right after)
[00:48] <hggdh> not really. Doing something like that would mean closing LP more. I would rather have it open and deal with the problems we find -- which are rare, BTW
[00:48] <LimCore> bug-elevation-team  ?
[00:48] <hggdh> also
[00:49] <LimCore> hggdh: there is _1_ thing that new-LP-users want to do (quickly) - report/comment a bug.  All else doesnt have to be super-open.
[00:49] <yofel> LimCore: he created a team and  invited just about every team he could find into it (including the admins etc.) and set 'Ubuntu Bugs' as the owner
[00:49] <LimCore> woot
[00:51] <LimCore> don't you have option to send a PM to user or something, and ask him to contact you as you said; or just email?
[00:55] <Jordan_U> Ok, I am about to post this to https://bugs.launchpad.net/ubuntu/+source/linux/+bug/453579 if it looks OK : http://pastebin.com/m666af34e
[00:55] <ubot4> Launchpad bug 453579 in linux (Ubuntu Karmic) (and 3 other projects) "in-place corruption of large files *without fsck or reboot* reported with linux 2.6.31-14.46 on ext4 (affects: 22) (dups: 1)" [Critical,Triaged]
[00:56] <hggdh> interesting. I cannot start firefox anymore
[00:58] <micahg> hggdh: which version?
[00:58] <hggdh> 3.6
[00:58] <hggdh> ooohhhh xul-ext-firegpg is the culprit
[00:59] <hggdh> I have it again. micahg want me to open a bug on it?
[01:00]  * micahg thinks there is a bug
[01:00] <hggdh> k. This was with the brand-new, just-put-available firegpg
[01:02] <micahg> hggdh: yeah, 0.7.9 should support 3.6
[01:02] <micahg> 64 bit?
[01:02] <LimCore> oh dear god
[01:02] <LimCore> what it is with firefox plugins and failures on 64bit
[01:02] <LimCore> it's not year 2005
[01:02] <micahg> LimCore: upstream doesn't always support it
[01:02] <LimCore> firebug, bugzilla and now you say also firegpg
[01:03] <micahg> also there still aren't any official 64 bit builds of FF
[01:03] <micahg> but soon
[01:03] <hggdh> micahg: yes, 64, and 0.7.10
[01:03] <LimCore> s/bugzilla/enigmail
[01:07] <micahg> hggdh: no idea
[01:08] <LimCore> kde ssl information should allow to copy-past the text. what package to report against?
[01:08] <micahg> hggdh: makes sense, no xulrunner 1.9.2
[01:08] <micahg> hggdh: please file a bug and subcribe me
[01:10] <hggdh> darn. micahg I cannot, I am using ffox from the mozillateam ppa
[01:10] <hggdh> ubuntu-bug spits it away
[01:10] <hggdh> oh
[01:11] <hggdh> I *can* got straight into LP...
[01:14] <micahg> hggdh: no, file against firegpg, not firefox
[01:16] <hggdh> ok
[01:16] <micahg> hggdh: it needs to be rebuilt once xul192 is uploaded
[01:17] <micahg> which needs to happen this week
[01:17] <micahg> along with TB3
[01:17]  * micahg will be back later
[01:37] <LimCore> anyone uses apt-cacher? I want to confirm bug 516500.
[01:37] <ubot4> Launchpad bug 516500 in apt-cacher (Ubuntu) "apt-cacher sometimes dissallows to download given packages untill cache is fixed. Failed to fetch (affects: 1)" [Undecided,New] https://launchpad.net/bugs/516500
[02:23] <kklimonda> heh, is wubi really officially supported? /me is looking at bug 477104
[02:23] <ubot4> Launchpad bug 477104 in grub2 (Ubuntu Karmic) (and 3 other projects) "After 9.10 grub update can not boot into Wubi install (affects: 125) (dups: 9)" [Undecided,Fix committed] https://launchpad.net/bugs/477104
[02:23] <nigel_nb> kklimonda, yep.  It is.  Its on every ubuntu cd I believe
[02:29] <crimsun> sorry for the bug spam; I have about 200 more PA bugsto close tonight
[02:29] <crimsun> already closed ~100
[02:29] <crimsun> (all resolved in Lucid)
[02:37] <nigel_nb> crimsun, that is a *lot* of bugs :)
[02:37] <nigel_nb> hats off to you buddy :)
[02:41] <nigel_nb> can "Bug Squad" now see private bugs?
[02:42] <kklimonda> nigel_nb, I don't think so
[02:42] <nigel_nb> kklimonda, well, I seem to be able to
[02:42] <nigel_nb> kklimonda, are you on bug squad?
[02:43] <kklimonda> yes - but I'm also a member of bug control so I won't be able to confirm it
[02:43] <nigel_nb> lemme hunt for someone who's not on bug squad
[02:45] <wgrant> nigel_nb, kklimonda: You cannot magically see private bugs.
[02:45] <wgrant> Private bugs are visible to their subscribers.
[02:45] <wgrant> If you're not in the subscriber list or ~admins, you cannot see the bug.
[02:45] <kklimonda> true
[02:45] <nigel_nb> well, I'm not sure if I'm a subscriber either
[02:46] <hggdh> bug-control gets to some via crash-bug-triagers
[02:46] <nigel_nb> wait ubuntu-bugs is subscribed, I think I'm in there
[02:47] <nigel_nb> ah, figured it out
[02:47] <nigel_nb> I'm subscribed to ubuntu desktop bugs....
[02:47] <hggdh> I think ubuntu-bugs work work via bug-control, not bug-squad
[02:47] <wgrant> hggdh: Right.
[02:48] <nigel_nb> hggdh, yes.  ubuntu-bugs is via bug control
[02:48] <wgrant> (otherwise Rhett would have stil had privileges over the team)
[02:48] <hggdh> yeah
[02:48] <nigel_nb> hggdh, but desktop bugs is open and subsrcribed here
[02:48] <wgrant> nigel_nb: Which bug?
[02:49] <nigel_nb> wgrant, bug 518806
[02:49] <ubot4> nigel_nb: Bug 518806 on http://launchpad.net/bugs/518806 is private
[02:49] <nigel_nb> it is kinda funny.  the guy attached a pdf
[02:49] <nigel_nb> and later realized its illegal
[02:49] <nigel_nb> and made it private
[02:50] <wgrant> Ah, so, making a bug private will automatically subscribe any implicit subscribers (those under 'Also notified')
[02:50] <wgrant> (this is not the case for a bug that starts private)
[02:50] <nigel_nb> wgrant, another bug in malone?
[02:52] <hggdh> wgrant: I think what happened was the bug started public -- so "also notified
[02:53] <hggdh> got subscribed. After that, they were already there
[02:53] <wgrant> hggdh: That's right.
[02:53] <wgrant> nigel_nb: Not a bug.
[02:53] <nigel_nb> it is supposed to work that way?
[02:53] <hggdh> yes
[02:53] <wgrant> Perhaps not exactly desirable in all circumstances, but there is no really good solution.
[02:54] <wgrant> They've already been notified about the bug, so there's no extra disclosure.
[02:54] <wgrant> And if it didn't work like that, bugs would vanish from all but the reporter if they were quickly made private.
[02:54] <nigel_nb> ah :)
[02:57] <nigel_nb> so, we live with it.
[02:57] <nigel_nb> I'll remove the attachment from this guy ;)
[02:57] <hggdh> nigel_nb: about desktop-bugs... this is not really a problem. Keep in mind you do *not* need to belong to any team to work with bugs
[02:58] <nigel_nb> hggdh, I thought I'd get mails about every bug
[02:58] <nigel_nb> apparently, it doesn't work thta way
[02:59] <nigel_nb> hggdh, I was going to remove myself.  I *thought* it might be something like gnome bugs.  Now I have to subscribe to packages I understand
[03:00] <hggdh> yes, you do. Otherwise we would be completely submerged in email
[03:00] <nigel_nb> hggdh, I got filters set and ready ;)
[03:01] <hggdh> nigel_nb: I am talking about 10k bugs per month (low-balling it), and *all* comments and changes
[03:01] <nigel_nb> hggdh, oh .... OH
[03:01] <hggdh> just subscribe to the ubuntu-bugs ML... you will understand what I am talking about in 1 week, tops
[03:01] <nigel_nb> oh no thanks
[03:01]  * kklimonda was subscribed to desktop bugs for a while
[03:01] <nigel_nb> only brian can deal with that thing
[03:02] <hggdh> I very much doubt he does it :-)
[03:02] <persia> And even then, only with support from automation
[03:02] <kklimonda> hggdh, he did in the past
[03:02] <hggdh> yes. And a *lot* of disk space
[03:03] <kklimonda> and a well configured mutt ;)
[03:03] <hggdh> kklimonda: in the past we did not have 10k bugs per month. I was subscribed to the ML for a while, then
[03:04]  * wgrant was subscribed back in 2006.
[03:04] <wgrant> It was managable.
[03:05] <nigel_nb> hggdh, removed the offending pdf and I'm marking it confirmed and public
[03:05] <hggdh> yes
[03:05] <wgrant> Note that the PDF is still accessible.
[03:05] <hggdh> nigel_nb: thank you. I *could* have removed it, but I was not sure I should
[03:05] <wgrant> And will be for several days.
[03:06] <hggdh> but there is nothing we can do... until we get to have private attachments
[03:06] <nigel_nb> hggdh, reflects poorly on us if an illegal copy of a book is around for everyone to download
[03:06] <hggdh> I agree
[03:10] <nigel_nb> hggdh, bah, ran into trouble now
[03:10] <nigel_nb> hggdh, that bug isn't confirmable on other pdfs
[03:11] <hggdh> nigel_nb: the OP will find another PDF, or create a video, or whatever
[03:11] <nigel_nb> good idea
[03:13] <nigel_nb> hggdh, trouble is... I set to confirmed :(
[03:15] <hggdh> nigel_nb: just put it back to Incomplete, and explain why
[03:15] <hggdh> no problems
[03:16]  * nigel_nb feels stupid
[03:16] <hggdh> heh
[03:17] <nigel_nb> hggdh, um, what should I be doing to get into bug squad? been some time.  It me only yday.
[03:17] <nigel_nb> err... bug control
[03:18] <hggdh> and I have been monitoring you ;-)
[03:18] <hggdh> have not seen any new upstream to b.g.o
[03:18] <nigel_nb> haven't seen any upsteamable bugs either :(
[03:18] <hggdh> yup
[03:18] <hggdh> nigel_nb: you are almost there
[03:19] <hggdh> I would just like a bit longer, for you to feel more confortable
[03:19] <hggdh> BUT
[03:19] <hggdh> your time is coming
[03:20] <nigel_nb> :)
[03:20] <nigel_nb> I'll try to score 200 bugs ;)
[03:20] <nigel_nb> i'm at 110 now I tink
[03:20] <ddecator> hggdh, what is the likelihood that pedro has been watching my progress through emails? idk if you'll know or not, but i can get in contact with him lately
[03:21] <hggdh> you mean you cannot, right
[03:21] <ddecator> right
[03:21] <ddecator> i guess he's traveling for work
[03:22] <hggdh> ddecator: might be. But the rest of us are here -- and watching you like eagles
[03:22] <bdmurray> yes, he was in pdx last week and travelled back home over the weekend
[03:22] <hggdh> well, in my case, an eagle with glasses
[03:22] <nigel_nb> ddecator, there was dev sprint last week in portland (I think)
[03:22] <ddecator> right, i'm just wondering when my time comes to consider bugcontrol, who would be the main one i should talk to? haha
[03:23] <hggdh> ddecator: Pedro would be it
[03:23] <ddecator> alright, thanks hggdh
[03:23] <hggdh> but we can provide him with feedback also
[03:23] <nigel_nb> ddecator, most of the time its micahg who helps me out (time difference)... doesn't really matter
[03:24] <nigel_nb> any thing you say here has logs... its kinda easy to grep
[03:24] <ddecator> nigel_nb, yah micahg helps me out a lot too since we're in the same loco, and he wants to train me for ff bugs
[03:24] <ddecator> nigel_nb, that's true...
[03:25] <nigel_nb> ah :)
[03:25] <nigel_nb> bug 518840 is a feature right?
[03:25] <ubot4> Launchpad bug 518840 in rhythmbox (Ubuntu) "not returning to the previous song (affects: 1)" [Undecided,New] https://launchpad.net/bugs/518840
[03:25] <nigel_nb> I mean.. it not really a bug....
[03:25] <ddecator> i was just looking at that, haha
[03:25] <nigel_nb> standard feature in all players
[03:25] <ddecator> i'm gonna check the changelogs
[03:26] <ddecator> nigel_nb, he said it didn't happen before, so i'm checking the changelogs to see if they marked a change in that feature
[03:26] <nigel_nb> :)
[03:27] <nigel_nb> hggdh, a little bit of your evolution foo :) bug 519079
[03:27] <ubot4> Launchpad bug 519079 in evolution (Ubuntu) "Evolution STOPPED syncing with GMAIL (affects: 1)" [Undecided,New] https://launchpad.net/bugs/519079
[03:30] <Damascene> https://wiki.ubuntu.com/LaptopTestingTeam/HotkeyResearch
[03:30] <Damascene> I tried all this didn't work for me
[03:30] <nigel_nb> Damascene, didn't you log a bug for it?
[03:30] <Damascene> as I told to do for this bug:
[03:31] <Damascene> I did but I asked to do something else to help
[03:31] <Damascene> https://bugs.launchpad.net/ubuntu/+source/udev/+bug/518007
[03:31] <ubot4> Launchpad bug 518007 in udev (Ubuntu) "Asus Eee Function Keys (Hotkeys) are not working with Lucid 10.04 (affects: 1)" [Undecided,New]
[03:33] <nigel_nb> Damascene, no reponse with any of the methods
[03:33] <nigel_nb> ?
[03:34] <hggdh> nigel_nb: seems to be a bug...
[03:34] <nigel_nb> hggdh, worthy of upstream?
[03:35] <hggdh> make the bug private, and then ask the OP to run Evo in debug mode from the console. See http://projects.gnome.org/evolution/bugs.shtml
[03:35] <Damascene> no respond
[03:35] <Damascene> I'm attaching a file right now with the method 2 results
[03:36] <hggdh> the OP should run 'env CAMEL_DEBUG=all evolution > evo.log 2>&1', and then upload the evo.log
[03:37] <hggdh> but make the bug private -- there will be private data being logged
[03:37] <nigel_nb> hggdh, okay :)
[03:37] <hggdh> and I am gone. G'night all
[03:37] <ddecator> cya hggdh
[03:38] <bcurtiswx> LP just died on me
[03:39] <bcurtiswx> ok its back.. <shrugs>
[03:39] <nigel_nb> bcurtiswx, just show it some love ;)
[03:39] <bcurtiswx> lol
[03:40] <Damascene> nigel_nb, I've updated the bug report. may some one trigger it now?
[03:42] <nigel_nb> ddecator, you checked chagelog in gnome or ubuntu?
[03:43] <ddecator> nigel_nb, whatever set of docs came from debian, i only know of one place where the changelogs are stored
[03:43] <nigel_nb> ddecator, actually there are git comment messages
[03:44] <nigel_nb> bah.. commit messages
[03:44] <nigel_nb> if you go to git.gnome.org, it will let you browse, painstaking but possible ;)
[03:45] <ddecator> the changelog i checked was the "changelog.Debian.gz," but i'll check that site, thanks
[03:52] <bcurtiswx> is it possible to search multiple files for a string it includes?
[03:53] <ddecator> nigel_nb, i still couldn't find anything, but i don't see it as a bug
[03:54] <nigel_nb> bcurtiswx, in your file system?
[03:54] <bcurtiswx> yup
[03:55] <nigel_nb> hm.. lemme chekc my bash history
[03:55] <nigel_nb> I tried it out last week
[03:55] <nigel_nb> bcurtiswx, grep -H -r “redeem reward” /home/tom
[03:56] <nigel_nb> bcurtiswx, that prints the file names with match
[04:28] <ddecator> nigel_nb, does apport-collect get crash reports?
[04:29] <nigel_nb> ddecator, apport automatically gets triggered during crash
[04:29] <micahg> ddecator: in lucid I think you can attach one to an existing bug
[04:30] <ddecator> micahg, so apport launches automatically for firefox crashes in lucid? is that because it's still in development?
[04:30] <micahg> ddecator: yes, it's off by default in stable releases, but you can enable it if you want
[04:31] <micahg> ddecator: you can also use ubuntu-bug /path/to/crash_file
[04:31] <ddecator> micahg nigel_nb, ah, i didn't know it got enabled in development releases. good to know
[04:31] <nigel_nb> :)
[04:31] <nigel_nb> micahg, didn't you patch apport once?
[04:32] <micahg> micahg: yes
[04:32] <ddecator> ...
[04:32] <ddecator> i'm guessing the self reference was an accident? haha
[04:32] <micahg> oops
[04:32]  * micahg talks to himself sometimes...
[04:33] <micahg> nigel_nb: yes
[04:33] <nigel_nb> micahg, LOl
[04:33] <ddecator> wait, i'm confused
[04:33] <nigel_nb> micahg, I knew you were the apport expert
[04:33] <micahg> nigel_nb: I'm no expert
[04:33] <micahg> pitti and bdmurray are
[04:33] <ddecator> it's good to know that apport is automatically on for firefox crashes in development releases, but nigel_nb that bug is on karmic
[04:33] <nigel_nb> well..enough to patch it
[04:34] <micahg> nigel_nb: nah, it was patched in Lucid, I just backported the fix
[04:34] <nigel_nb> micahg, ah :)
[04:34] <nigel_nb> ddecator, bug number?
[04:34] <micahg> ddecator: ubuntu-bug /path/to/crash
[04:34] <ddecator> bug 518913
[04:34] <ubot4> Launchpad bug 518913 in firefox (Ubuntu) "Firefox crashes constantly (affects: 1)" [Undecided,Incomplete] https://launchpad.net/bugs/518913
[04:34] <micahg> ddecator: problem with ff crashes is you can't report them with ff :)
[04:35] <ddecator> micahg, i copied a comment you told me to use in a crash for ff before
[04:35] <micahg> ddecator: yes, but if it won't stay open like this bug, it won't work
[04:35]  * ddecator is confused
[04:36] <micahg> nigel_nb: also, you might not want that help -> report a problem thing on every bug as this user did with yelp
[04:36] <micahg> ddecator: apport uses firefox, if firefox won't stay open for more than 5 seconds, you can't report with apport
[04:37] <ddecator> micahg, but does apport-collect get crash info for ff if it's not on by default?
[04:37] <nigel_nb> micahg, I wanted him to do that firefox
[04:37] <nigel_nb> *in* firefox
[04:37] <micahg> ddecator: apport-collect doesn't add crash info in < lucid
[04:38] <micahg> nigel_nb: I think you meant about firefox
[04:38] <ddecator> micahg, so since this is karmic...is there any way to get the crash info?
[04:38] <nigel_nb> yeah
[04:38] <micahg> nigel_nb: I think what you did was fine
[04:38] <micahg> nigel_nb: no I was wrong
[04:38] <micahg> you did mean for him to do that in FF
[04:38] <micahg> nigel_nb: but that's hard with this type of bug
[04:38] <micahg> I'm made the mistake myself many times
[04:38] <nigel_nb> micahg, now its totally confusing
[04:39] <nigel_nb> apport-collect?
[04:39] <ddecator> yah i'm completely lost...
[04:39] <micahg> nigel_nb: the 3rd paragraph of your post
[04:39] <micahg> report a bug
[04:40] <nigel_nb> micahg, I need to "read" the gm script.. second time I'm messing up
[04:40] <micahg> my gm script doesn't have that...
[04:40] <micahg> nigel_nb: did you edit yours?
[04:41] <ddecator> micahg, so i'm a little confused on this...enabling apport for a firefox crash will create a crash file, but then use firefox to upload to lp right after it just crashed?
[04:41] <nigel_nb> micahg, nopes.  Its direct from the xml
[04:41] <micahg> ddecator: if it's a rare crash in firefox, it's fine and normal, if it's the firefox crash where the browser won't stay open for > 5 seconds, it's impossible
[04:42] <ddecator> micahg, i see...just seems weird to me that apport uses firefox to upload a firefox crash report haha, i thought it uploaded automatically on it's own without a browser
[04:43] <micahg> nigel_nb: are you using the deb apckage?
[04:43] <nigel_nb> micahg, yeah
[04:43] <micahg> ddecator: it uploads w/out it, the problem is submitting the bug with the crash info
[04:44]  * micahg doesn't have an .xml file
[04:44] <nigel_nb> micahg, the xml file is in bdmurray's people.ubuntu.com website
[04:44] <micahg> nigel_nb: BTW, that's the wrong firefox for Karmic
[04:45] <ddecator> micahg, so the report is uploaded, but it needs firefox to actually submit the bug?
[04:45]  * nigel_nb seems to be making only mistakes today
[04:45] <micahg> ddecator: for the user to register the bug (subject, description)
[04:45] <micahg> nigel_nb: dont' worry :)
[04:45] <ddecator> micahg, ah, i guess that makes more sense
[04:45] <nigel_nb> micahg, 3.5 ?
[04:45] <micahg> soon all will be firefox
[04:45] <micahg> yeah, I moved it...
[04:46] <ddecator> nigel_nb, it's nothing big nigel, i just wanted to know what the right method was for future reference =)
[04:46] <micahg> nigel_nb: the hooks are in the firefox-3.5 package
[04:46] <nigel_nb> micahg, ah
[04:48]  * micahg is happy launchpad code is back :)
[04:48] <ddecator> ?
[04:48] <micahg> bzr branch checkout was down earlier
[04:49] <ddecator> haha, yah i have no idea what that is...
[04:49] <micahg> code branches stored in launchpafd
[04:49] <ddecator> good enough for me
[04:49]  * micahg needs to prepare next versions of firefox...
[04:49] <nigel_nb> micahg, logger head?
[04:50] <nigel_nb> or the host itself?
[04:50] <micahg> nigel_nb: I think that's the gui
[04:50] <nigel_nb> oh, the backend was down too?
[04:50] <nigel_nb> yday loggerhead was down
[04:51] <micahg> nigel_nb: yes, I guess that's yesterday for you :)
[04:51]  * nigel_nb is lazy to type yesterday
[04:52] <nigel_nb> especially after a night of typing (my work involves plenty of typing anyway)
[04:52]  * ddecator is getting tired and lost track on whether he hit his 5-a-day mark for today...
[04:53] <nigel_nb> ddecator, check mail ;)
[04:53] <nigel_nb> easiest way
[04:53] <ddecator> well i guess that depends, i'm assuming it's just doing -any- work on five different bugs?
[04:54] <ddecator> well, any real work...
[04:54] <ddecator> if so, then yah i hit it easy, haha
[04:55]  * ddecator is debating whether or not to get up early again tomorrow, or just wait for pedro to email him back
[04:56]  * nigel_nb votes waiting or using memoserv
[04:56] <ddecator> memoserv?
[04:57] <nigel_nb>  /msg memoserv help
[04:57] <ddecator> o_O
[04:57] <ddecator> irc ceases to amaze me
[04:57] <nigel_nb> hehe
[04:57] <ddecator> lets see...
[04:58] <ddecator> so i'm guessing i use "send <username> <message>"?
[04:59] <nigel_nb> well.. /msg memoserv send help ;)
[04:59] <ddecator> touche
[05:00] <giantpune> hi guys.  i think i found a bug in ubuntu gnome and i could use sme help trying to fix it
[05:00] <nigel_nb> hehe
[05:01] <nigel_nb> giantpune, Hi, could you describe your problem.  We can help you file a bug report
[05:01] <giantpune> i right-clicked the bluetooth icon in the upper right and selected to remove it from the panel.  after that, the upper and lower "taskbar" panels just keep refreshing
[05:01] <giantpune> they disappear and come back every 3 seconds
[05:02] <nigel_nb> giantpune, which version of ubuntu are you running?
[05:02] <giantpune> 9.10 x64
[05:03] <nigel_nb> giantpune, odd.  I dont seem to have a "remove from panel for bluetooth"
[05:03] <nigel_nb> micahg, are you on karmic amd64?
[05:03] <micahg> nigel_nb: yes
[05:03] <giantpune> there is also one for the envelope icon which isup there beside it
[05:04] <nigel_nb> micahg, do you see a "remove from panel" for bluetooth? I dont, but I'm on i386.. giantpune seems to have issues with it
[05:04] <micahg> nigel_nb: I don't have bluetooth and I'm running xubuntu
[05:04] <nigel_nb> micahg, aah
[05:05] <nigel_nb> giantpune, could describe in more detail what you mean by refreshing?
[05:05] <giantpune> for some reason there were 2 bluetooth icons.  so i tried that to remove 1 of them and thats when it all went screwey
[05:05] <nigel_nb> that does sound like an existing bug, but I dont remember the number
[05:06] <giantpune> the panels show up like they do when the pc first starts.  then they vanish.  then they come back and then they vanish
[05:06] <ddecator> woot, it sent
[05:06] <ddecator> anyway, what about a 64-bit bug?
[05:06] <nigel_nb> ddecator, can you check your gnome panel to see if you can right click and say remove from panel?
[05:07] <ddecator> nigel_nb, what am i trying to remove?
[05:07] <giantpune> i eventually got it to let me logout and i logged in with "gnome-failsafe"  and it seems to be working fine now.  but i would like to fix the non fail-safe part
[05:07] <nigel_nb> ddecator, erm, sorry.. bluetooth
[05:07] <ddecator> i don't have it installed right now, but one sec...
[05:07] <ddecator> er...activated, haha
[05:08] <nigel_nb> giantpune, go to your home folder, press ctrl H to view all folders and rename the .gconf folder.
[05:08] <ddecator> you can't remove it, but there is a "show bluetooth icon" option in preferences
[05:08] <nigel_nb> giantpune, log out and login.  See if everything is normal.  if not log a bug
[05:08] <nigel_nb> ddecator, ah, I thought so.
[05:08] <nigel_nb> ddecator, seems like an existing bug..
[05:09] <ddecator> nigel_nb, wait, what's the bug?
[05:09] <nigel_nb> ddecator, phantom icons
[05:09] <nigel_nb> ddecator, 2 icon shows up.  when you try removing one, it messes everything up
[05:10]  * ddecator has two accessibility icons on his panel
[05:10] <nigel_nb> bug 439448
[05:10] <ubot4> Launchpad bug 439448 in gnome-panel (Ubuntu) (and 2 other projects) "notification area shows wrong icons. erratic behaviour (affects: 25) (dups: 2)" [Low,Triaged] https://launchpad.net/bugs/439448
[05:10]  * ddecator removed the icon, and now xchat was removed as well?
[05:10] <nigel_nb> ddecator, you shouldnt have removed
[05:10] <nigel_nb> it causes a mess when you remove
[05:10] <ddecator> nigel_nb, -shrug- i can always reset the panel
[05:11] <nigel_nb> heh ;)
[05:11] <ddecator> i've had to do it before, haha
[05:11] <ddecator> but yah, it's legit
[05:11] <nigel_nb> ah, thats where the confidence comes from :p
[05:11] <giantpune> so what is the proper way to reset this panel?
[05:11] <ddecator> nigel_nb, confidence? haha
[05:11] <ddecator> giantpune, let me check how i did it before...
[05:12] <nigel_nb> giantpune, rename .gconf and logout.  Login back and should be okay.  but there is an upstream bug about it
[05:12] <ddecator> there you go
[05:12] <giantpune> ok.  let me see what this does
[05:12] <ddecator> let me see if it works...brb
[05:12] <giantpune> brb
[05:13] <ddecator> yup
[05:13] <ddecator> reset to default
[05:13] <nigel_nb> ddecator, :)
[05:14] <ddecator> i just had to remove the panel file, so it had to create a new one on login...haha, i've had to do this so many times, i've been testing software a lot longer than i've been triaging, so i'm getting decent at figuring this stuff out =p
[05:15] <nigel_nb> hehe :)
[05:15] <ddecator> delete the bottom panel...autohide...delete the two icons...good to go =)
[05:15] <ddecator> and only one accessibility icon ;)
[05:15] <nigel_nb> :)
[05:15] <ddecator> so now what were you saying about confidence? i seem confident? haha
[05:16] <nigel_nb> ddecator, only when things get screwed and you fix them, you get confidence...true?
[05:17] <giantpune> ok am i back?
[05:17] <ddecator> nigel_nb, yah i guess, i'm used to the kernel not mounting, nvidia getting screwed up..
[05:17] <ddecator> giantpune, did it work for you?
[05:17] <nigel_nb> giantpune, working fine now?
[05:17] <giantpune> well, it has stopped the panels crashing.  but now i have 2 volume icons
[05:18] <giantpune> im afraid to try to change my volume now
[05:18] <ddecator> giantpune, did the panels get reset to their defaults though?
[05:18] <ddecator> giantpune, one volume icon should work fine, just don't remove either one, haha
[05:18] <nigel_nb> giantpune, well, the 2 volumes is a known bug upstream like I said
[05:18] <giantpune> it appears so.  all the extra icons i had stuck to the upper pannel are now gone
[05:18] <Damascene> Hello, any help with this
[05:18] <Damascene> https://bugs.launchpad.net/ubuntu/+source/openoffice.org/+bug/519150
[05:18] <ubot4> Launchpad bug 519150 in openoffice.org (Ubuntu) "openoffice menus in menu bar is not visible in Ubuntu Netbook Edition (affects: 1)" [Undecided,New]
[05:18] <ddecator> giantpune, yah, sorry about that...
[05:19] <nigel_nb> giantpune, you can add your comments to bug 439448
[05:19] <ubot4> Launchpad bug 439448 in gnome-panel (Ubuntu) (and 2 other projects) "notification area shows wrong icons. erratic behaviour (affects: 25) (dups: 2)" [Low,Triaged] https://launchpad.net/bugs/439448
[05:19] <nigel_nb> giantpune, well, I got your panel reset, thats why.
[05:19] <ddecator> Damascene, i don't have access to UNE, so i can't really help much with that
[05:19] <nigel_nb> Damascene, that is the default color
[05:20] <giantpune> has the grub bug been fixed?
[05:20] <nigel_nb> giantpune, which one/
[05:20] <nigel_nb> Damascene, or is that not the default color otherwise?
[05:20] <giantpune> when i first installed this version of ubuntu it worked fine.  then i did the update and it updated grub to grub 2 i think.  and grub2 couldnt load any filesystem
[05:21] <giantpune> so i was stuck at grub2
[05:21] <Damascene> as I said the default color of UNE is black or dark gray
[05:21] <nigel_nb> eek! upgrade.
[05:21] <nigel_nb> Damascene, so black on white gray?
[05:21] <giantpune> so ive been afraid to update anything for fear that it will not be able to start again
[05:21] <Damascene> for the menu bar I mean but the problem only with openoffice
[05:21] <ddecator> giantpune, grub upgrades are risky and sometimes stuff like that happens just by chance. what version did you say you're running?
[05:22] <giantpune> 1.97beta is what came with the ubuntu i downloaded.  then when it upgraded i got grub2
[05:23] <Damascene> nigel_nb, it's black text on black background. there is screen shot
[05:23] <nigel_nb> Damascene, okay, the problem dawned on me now :)
[05:23] <ddecator> Damascene, i heard Openoffice is planned to be removed from Lucid's UNE...doesn't help your bug, but just good to know
[05:24] <ddecator> giantpune, 1.97 beta is "grub2," if you run 'sudo apt-get update; sudo apt-get dist-upgrade' is grub listed as one of the upgrades?
[05:24] <Damascene> ddecator, why it's just fine
[05:24] <giantpune> yes.  it still wants me to update grub.  but i always tell it no
[05:24] <ddecator> Damascene, not sure, here's what i saw http://www.omgubuntu.co.uk/2010/02/few-days-ago-we-shared-word-that.html
[05:25] <ddecator> giantpune, if you already have grub2 it shouldn't be a problem, but if you don't want to update it then you can use the update manager to just update everything else
[05:25] <giantpune> ok
[05:25] <Damascene> nigel_nb, can you triage it?
[05:26] <nigel_nb> Damascene, its not an open office bug per se.  Its your theme
[05:26] <nigel_nb> I'm trying to figure out where to change it
[05:26] <Damascene> but all the other program are working fine
[05:26] <ddecator> Damascene, i think the idea is that netbooks don't normally need a full office suite, so their trying to save room on the disc for other programs
[05:26] <Damascene> and I could not change my theme. maybe it's another bug :)
[05:26] <ddecator> Damascene, can you get into the OO options menu?
[05:27] <Damascene> no options menu
[05:27] <ddecator> Damascene, Tools -> Options... ?
[05:27] <Damascene> yes
[05:28] <ddecator> go there and select Appearance
[05:28] <ddecator> you should be able to change the colors from there so you can read everything
[05:29] <Damascene> ok but it still a bug right?
[05:29] <ddecator> for example, i had to change it so the background is white and the text is black since i use a dark theme
[05:29] <ddecator> hard to tell if it would be considered one...
[05:29] <giantpune> also, is there documentation somewhere about how to use the nVidia drivers?  I cannot understand what im supposed to do to get dual monitors to work properly
[05:30] <ddecator> it might be more of a wishlist for better gtk+ support? what do you think nigel_nb ?
[05:30] <ddecator> giantpune, do you mean how to activate them?
[05:30] <nigel_nb> ddecator, its just a theme going crazy.  its working fine on ubuntu
[05:31] <giantpune> I have them installed and it is outputting video to both monitors, but i can only get 640X480 resolution on my second monitor
[05:31] <ddecator> nigel_nb, yah but OO doesn't play nice with dark themes usually, haha, but since it won't be in UNE for lucid idk if it's worth filing...maybe ask someone in the morning?
[05:31] <nigel_nb> thats best
[05:31] <ddecator> giantpune, System -> Administration -> NVIDIA X Server Settings
[05:32] <ddecator> giantpune, i know there are resolution settings in there, but idk if it'll support dual monitor
[05:32] <ddecator> nigel_nb, do you want to subscribe to it and ask tomorrow?
[05:33] <giantpune> ive tried messing with this, but it only lets me pick 640 resolution for the second monitor.  and it cannot save anything.  even if i start it with sudo
[05:34] <ddecator> giantpune, odd...but NVIDIA is tricky. maybe try asking on Ubuntu Answer's? or there may be someone who has already asked, you can search around a bit on there. if you don't find one, then you can post the question
[05:35] <ddecator> giantpune, https://answers.launchpad.net/ubuntu
[05:36] <pune> thanks a bunch
[05:36] <ddecator> np
[05:39] <pune> thanks again
[06:14] <om26er> should this be made public? https://bugs.launchpad.net/bugs/519050 there is not coredump but its not retraced
[06:14] <ubot4> om26er: Error: Bug #519050 is private.
[06:17] <ddecator> i'm not in bugcontrol so i can't help, sorry
[06:18] <om26er> any please this is a critical bug
[06:19] <ddecator> persia, you still around? ^
[06:22] <ddecator> sorry, i'm not sure any other bugcontrol members are on right now
[06:25] <crimsun> there are.
[06:25] <crimsun> granted, edge.lp seems to be timing out
[06:25] <ddecator> ah, hey crimsun
[06:27] <nigelbabu> crimsun, how many more to go?
[06:27] <nigelbabu> (out of the 200 more you said earlier)
[06:28] <crimsun> nigelbabu: I'm taking a break momentarily
[06:29] <Damascene> I wonder how I can triage a bug. I've been here for almost a week and noon of my bugs have been triaged. are here any one who can triage a bug?
[06:29] <Damascene> *non
[06:29] <ddecator> Damascene, are you talking about the bugs that you are reporting?
[06:29] <om26er> Damascene, give the links
[06:30] <Damascene> https://bugs.launchpad.net/ubuntu/+source/udev/+bug/518007
[06:30] <ubot4> Launchpad bug 518007 in udev (Ubuntu) "Asus Eee Function Keys (Hotkeys) are not working with Lucid 10.04 (affects: 1)" [Undecided,New]
[06:30] <Damascene> https://bugs.launchpad.net/ubuntu/+source/openoffice.org/+bug/519150
[06:30] <wgrant> Er, Critical?
[06:30] <ubot4> Launchpad bug 519150 in openoffice.org (Ubuntu) "openoffice menus in menu bar is not visible in Ubuntu Netbook Edition (affects: 1)" [Undecided,New]
[06:30] <wgrant> om26er: Why is that critical?
[06:31] <om26er> wgrant, because netbook launcher dont start for any one
[06:31] <crimsun> Damascene: why is that a udev bug/
[06:32] <Damascene> some one here told me to report it against it
[06:33] <Damascene> https://bugs.launchpad.net/ubuntu/+source/xchat/+bug/215078
[06:33] <ubot4> Launchpad bug 215078 in xchat (Ubuntu) "xchat disconnect then reconnect loses channel info (affects: 1) (dups: 1)" [Low,Incomplete]
[06:33] <crimsun> linux, not udev. triaged.
[06:33] <Damascene> thank you :)
[06:35] <crimsun> something must be wonky with chromium
[06:35] <om26er> Damascene, about openoffice bug its actually a bug in dust theme
[06:35] <ddecator> why do you say that crimsun ?
[06:35] <Damascene> but other programs are working fine
[06:36] <crimsun> ddecator: because the LP notification showed up in the bug 215078
[06:36] <ubot4> Launchpad bug 215078 in xchat (Ubuntu) "xchat disconnect then reconnect loses channel info (affects: 1) (dups: 1)" [Low,Incomplete] https://launchpad.net/bugs/215078
[06:36] <crimsun> "The bug supervisor for linux (Ubuntu) has been subscribed to this bug."
[06:36] <Damascene> any way to whose advice should I lessen before I report a bug? I always ask before I report. some times in #ubuntu+1
[06:37] <wgrant> crimsun: Known and practically unsolvable issue with LP.
[06:37] <wgrant> Yay races.
[06:38] <Damascene> some one should have voice in this channel
[06:38] <crimsun> oh, LP? Ok, I'm happy to blame LP, then.
[06:39] <ddecator> Damascene, you don't necessarily have to ask here every time, just look on launchpad for if it is already reported (if it is, click that it affects you), otherwise report a new bug using these guidelines: https://help.ubuntu.com/community/ReportingBugs
[06:39] <ddecator> Damascene, just remember, all triagers have different specialties and amounts of experience, so sometimes bugs get instant help, sometimes they never get worked on, it just depends
[06:41] <Damascene> as I see that I reported against false packages. that what I need help with
[06:42] <crimsun> Damascene: you aren't expected to know everything ;)
[06:42] <Damascene> :) right
[06:42] <ddecator> Damascene, then you can just ask here in general. usually you will get the right answer, but if not we can easily change the affected package on the report. you can even just give your best guess if you want =)
[06:43] <Damascene> OK. thank you very much
[06:44] <ddecator> ym
[06:44] <ddecator> yw*
[06:44]  * ddecator had to take out his contacts and is 6" away from his screen right now, pardon any typos -_-
[07:19] <kermiac> crimsun: When you've got a sec can you pls have a quick look at bug 515422 & see if there's anything else I need to do? The OP has resolved the issue by adding a model quirk to alsa-base.conf
[07:19] <ubot4> Launchpad bug 515422 in linux (Ubuntu) "No sound after upgrading from 8.10 to 9.10 (affects: 2)" [Undecided,Incomplete] https://launchpad.net/bugs/515422
[07:53] <Damascene> I was going to report bug to request this feature http://brainstorm.ubuntu.com/idea/13132/ as I've been told
[07:53] <Damascene> it's suggest that checkbox should have the ability to test function keys
[07:55] <Damascene> so I wonder if I some one want to suggest improvement for program, where that should be? launchpad bugs or brainstorm ideas?
[08:12] <thekorn> Damascene, I think the generall target for such improvement suggestions is upstream, the people who are developping the application in question,
[08:15] <thekorn> and then it depends how upstream whould like to get this requests, via a mai to a mailinglist, via a bugreport, and so on.
[08:16] <thekorn> In the case of checkbox I think it is ok to file a bug at https://bugs.edge.launchpad.net/checkbox
[08:19] <Damascene> ok thank you
[08:20] <nigel_nb> can someone set bug 449019 triaged? I reported it upstream
[08:20] <ubot4> Launchpad bug 449019 in empathy (Ubuntu) (and 1 other project) "empathy doesn't display resource being used by xmpp contact (affects: 1)" [Wishlist,Triaged] https://launchpad.net/bugs/449019
[08:22] <thekorn> it already is triaged
[08:22] <thekorn> oh om26er did it ;)
[08:23] <nigel_nb> oh. well. that was fast
[08:23] <nigel_nb> thanks om26er :)
[08:24] <om26er> nigel_nb, welcome
[08:27] <Damascene> https://bugs.launchpad.net/ubuntu/+source/checkbox/+bug/516555
[08:27] <ubot4> Launchpad bug 516555 in checkbox (Ubuntu) "Checkbox (System Testing) bypass Audio tests sometimes (affects: 2)" [Undecided,New]
[08:27] <Damascene> some one have confirmed this in ubuntu+1
[08:27] <Damascene> I've updated the bug report
[08:28] <Damascene> just try to test any thing and then get back to main menu without closing checkbox and the audio test will be passed
[08:47] <kermiac> Damascene: I just tried in Karmic & it does the same thing
[08:48] <Damascene> so what are we going to do now?
[08:52] <kermiac> I'm looking to try & find a duplicate or at least something similar first
[08:53] <kermiac> could be fun... searching for "checkbox" results in 1211 results :(
[08:57] <thekorn> bug 472743 is maybe the related upstream bugreport
[08:57] <ubot4> Launchpad bug 472743 in checkbox "checkbox skips certain tests / does not return to defaults (affects: 1)" [Undecided,New] https://launchpad.net/bugs/472743
[09:03] <kermiac> hmm... sounds similar, but possibly not exactly the same
[09:05] <kermiac> in 516555 if you close checkbox it allows you to perform all tests. It's only if you perform the tests & skip back to the start that it will skip the audio tests. I think it needs further investigation
[09:07] <kermiac> as I said in ubuntu+1, this may be by design. checkbox *may* know that the sound tests have already been completed & that could explain why it skips that section of tests (in the same test session)
[09:08] <kermiac> but i don't know checkbox well enough to say if it is or isn't by design
[09:08] <kermiac> I will confirm the bug for now & hopefully someone with more knowledge then me can shed some light on the issue
[09:09] <Damascene> kees, no
[09:10] <Damascene> if you did disk test then skipped back and chose the audio test it will not do it
[09:10] <thekorn> you can also try to get in contact with the developers on #ubuntu-testing (esp. cr3 when he is around)
[09:10] <Damascene> it will do the disk test only
[09:10] <Damascene> in this case it didn't do the audio test at all
[09:11] <Damascene> I think the bug title should be changed to something else as we know better now
[09:14] <kermiac> ok, I tend to think it may be a bug now. I skipped through the audio tests & went through the next few tests. Then I hit previous to go right back to the start where you select the tests & tried to start testing again. It *only* skipts the audio tests
[09:15] <kermiac> After you update the bug title & description now that we have more info I will confirm it Damascene
[09:16] <LimCore> ubuntu systems that use apt-cacher, can stop update the packages. bug #516500. Medium prio?
[09:16] <ubot4> Launchpad bug 516500 in apt-cacher (Ubuntu) "apt-cacher stops updates of random packages (Connection failed) (affects: 1)" [Undecided,New] https://launchpad.net/bugs/516500
[09:16] <kermiac> bbs
[09:20] <LimCore> please set prio for bug #516500 anyone
[09:20] <ubot4> Launchpad bug 516500 in apt-cacher (Ubuntu) "apt-cacher stops updates of random packages (Connection failed) (affects: 1)" [Undecided,New] https://launchpad.net/bugs/516500
[09:22] <thekorn> LimCore, you handed this bug to the security team by marking it as Security vulnerability, so I think they should decide about priority
[09:23] <LimCore> mhm
[09:45] <Damascene> kermiac, "Checkbox (System Testing) bypass Audio test if you skiped from unfinished test" is this a good title
[09:47] <kermiac> I'm trying to get the wording right...
[09:49] <kermiac> perhaps "Checkbox (System Testing) bypasses the Audio Tests if you skip back & try to perform tests again" <-- I'm still not happy with that
[09:49] <kermiac> but it's close to what we're trying to convey
[09:50] <Damascene> I'll but it for now. it's better from mine any way
[09:50] <Damascene> put
[09:59] <kermiac> Damascene: Do you mind if I edit your bug report to give more precise steps to reproduce. It is a little vague atm
[09:59] <Damascene> kermiac, you are more than welcome :)
[09:59] <kermiac> :)
[10:03] <kermiac> ok, done. Can someone please mark bug 516555 as triaged, medium?
[10:03] <ubot4> Launchpad bug 516555 in checkbox (Ubuntu) (and 1 other project) "Checkbox (System Testing) bypasses the Audio Tests if you skip back & try to perform tests again (affects: 3)" [Undecided,Confirmed] https://launchpad.net/bugs/516555
[10:11] <kermiac> Damascene: do you think "Checkbox (System Testing) bypasses the Audio Tests if you skip back & try restart the tests" would be an accurate title for that bug? I think it's probably better than what I suggested above
[10:11] <kermiac> If you agree, I'll change it
[10:12] <thekorn> kermiac, why medium and not low?
[10:12] <thekorn> I really don't have an opinion, just want to understnd your idea
[10:14] <kermiac> just thought that medium is the "safe" option :) & due to the testing going on in the Lucid cycle I thought medium would be appropriate as there is currently no workaround except to start the tests again. I actually would be happy with low or medium, but again "medium" is the safe option
[10:15] <thekorn> ok, the "no workaround" is a good argument ;)
[10:17] <thekorn> done
[10:17] <kermiac> thanks thekorn :)
[10:33] <kermiac> ok, that's it from me for tonight. Good night all :)
[10:48] <om26er> if I want to add a package I just add my name at the wiki page? if someone has already adopted should I insert my name after a 'comma'
[11:07] <om26er> bug is reported against empathy but the upstream developer says that this feature is implemented in empathy but telepathy butterfly dont have this feature so should this be marked invalid against empathy? https://bugs.launchpad.net/telepathy-butterfly/+bug/518216
[11:07] <ubot4> Launchpad bug 518216 in empathy (Ubuntu) (and 2 other projects) "empathy doesn't support MSN group chat (affects: 1)" [Medium,Triaged]
[11:07] <om26er> else change the ubuntu package to telepathy-butterfly?
[11:09] <thekorn> om26er, yes, change the ubuntu package to telepathy,
[11:10] <om26er> thekorn, thanks
[11:10] <thekorn> and change the status of the empathy (upstream) task to invalid by hand, as auto sync of status does not work ATM
[11:10] <nigel_nb> thekorn, is it a stand process to assign bugs to desktop team?
[11:10] <nigel_nb> stand = standard
[11:12] <thekorn> oh, I don't think so
[11:12] <nigel_nb> hm, seen it often though
[11:13] <thekorn> my general opinion here is: don't assignee bugs to anybody unless you are member of this team, or you talked to them in any way
[11:13] <thekorn> but there might be a team policy, let me try to find out about it
[11:14] <nigel_nb> desktop team seems to have 5600 associated bugs
[11:16] <pedro_> nigel_nb, if the package is any of the ones on this list: https://bugs.edge.launchpad.net/~desktop-bugs/+packagebugs
[11:17] <pedro_> nigel_nb, assign the bug if you sent it upstream for example
[11:17] <pedro_> so we can keep track of those as well
[11:17] <nigel_nb> pedro_, ah, thanks :)
[11:17] <pedro_> if you assign those to desktop-bugs we also receive email on the mailing list
[11:17] <pedro_> so it's easier for everybody who is part of that team to follow up
[11:17] <nigel_nb> I was part of that team hoping to get mails
[11:17] <nigel_nb> but I didn't get any :(
[11:18] <Damascene> kermiac, yes it's better
[11:19] <pedro_> nigel_nb, https://lists.ubuntu.com/mailman/listinfo/desktop-bugs <- that's the mailing list if you want to subscribe
[11:20] <thekorn> pedro_, so desktop team's policy is: whenever you send one bug to the upstream bugtracker assign the team, correct?
[11:21] <thekorn> I think this should be documented somewhere as this is different to other workflows+
[11:22] <pedro_> thekorn, basically, yes
[14:07] <zeroseven0183> Hi! I'm not sure if someone already posted this "Bug# 399139 Mark elements as read" here. I think it should be classified as Wishlist.
[14:09] <nauto> Can someone help me figuring out if the following bug has already been reported? The launchpad search function isn't exactly accurate. I use an ATI card, with fglrx drivers, which worked fine for months. after a recent update, the ATI drivers didn't work anymore, so I had to reinstall the exact same (!) drivers. now Xorg has a huge memory leak, which makes it necessary to restart xorg every hour or so. it essentially makes Ubuntu unusable.
[14:10] <nauto> The memory leak always occurs when minimizing and maximizing windows.
[14:11] <yofel> bug 399139
[14:11] <ubot4> Launchpad bug 399139 in gwibber "Mark elements as read (affects: 2)" [Undecided,New] https://launchpad.net/bugs/399139
[14:13] <nauto> So for example, if I minimize xchat and maximize again, I can watch Xorg gaining almost 50 MB, and it isn't freed.
[15:25] <hggdh> netsplits?
[15:26] <Pici> no?
[15:36] <hggdh> bdmurray: pedro_ and I tried to set our wiki space to email all changes to bugSquad, but either it cannot be done, or we do not have the necessary access.
[15:38] <hggdh> darn! messed up Bugs/Responses
[15:41] <pedro_> hggdh, i still don't find the way to do that
[15:41] <pedro_> probably we're lacking permissions
[15:43] <hggdh> pedro_: I *hope* we are. Otherwise it just cannot be done
[15:48] <nauto> Can someone help me figuring out if the following bug has already been reported? The launchpad search function isn't exactly accurate. I use an ATI card, with fglrx drivers, which worked fine for months. after a recent update, the ATI drivers didn't work anymore, so I had to reinstall the exact same (!) drivers. now Xorg has a huge memory leak, which makes it necessary to restart xorg every hour or so. it essentially makes Ubuntu unusable. T
[15:48] <nauto> he memory leak always occurs when minimizing and maximizing windows.
[15:50] <micahg> nauto: if you don't install the ATI drivers as a debian package, you have to reinstall after a kernel upgrade
[15:50] <nauto> oh ok, well that explains that then.
[15:51] <nauto> still, the same drivers worked fine before, now something causes an Xorg memory leak. I don't know if it's a problem with Xorg or with the drivers.
[15:51] <nauto> I tend to think it's not the drivers' fault, since they worked correctly before.
[15:51] <cjohnston> Have we had any more Rhett issues, or has he contacted anyone?
[15:53] <micahg> nauto: there might be a problem w/the drivers too idk
[16:00] <micahg> hggdh: are we doing a meeting today?
[16:00] <hggdh> micahg: IDK, hope so
[16:01] <thekorn> hey bugsquad!
[16:02] <bdmurray> today is the 2nd tuesday right?
[16:02] <yofel_> meh, stupid timing for a reconnect
[16:02] <yofel_> well, I'm here ;)
[16:03]  * thekorn too
[16:03] <yofel> bdmurray: it is
[16:03] <hggdh> ah well. Just refused another candidate to bug-control
[16:04]  * micahg thinks he'll add the meeting to the fridge for next month
[16:05] <hggdh> er. I correct myself. I did not refuse, just gave a -1
[16:05] <hggdh> pretty good idea, micahg
[16:05] <hggdh> morning/afternoon, thekorn
[16:05] <bdmurray> micahg: and at a reminder e-mail?
[16:06] <micahg> bdmurray: I could set it up to e-mail the ML with a reminder
[16:06] <thekorn> good morning hggdh
[16:06] <yofel> reminder mail would be a good idea, I almost forgot about it
[16:07] <thekorn> so, who chairs todays meeting ? ;)
[16:07] <bdmurray> I will
[16:08] <thekorn> super
[16:08] <bdmurray> The first item on today's agenda is about "bugs regarding obsolete (removed?) packages" by micahg
[16:09] <micahg> wow, that's been a while....
[16:09] <micahg> so, if a package is removed from the devel release, do we have a policy about bugs?
[16:09] <micahg> I would assume non-SRUable bugs should be closed
[16:10] <micahg> but I don't think there was a written policy anywhere
[16:10] <bdmurray> Yes, that sounds about right.  I'm looking for a couple of e-mails.
[16:10] <bdmurray> bug 495216 would be a good place to start if you want to work on this
[16:10] <ubot4> Launchpad bug 495216 in ubuntu "mass removal of old and unpopular packages (affects: 1)" [Undecided,Fix released] https://launchpad.net/bugs/495216
[16:10] <micahg> also, we should probably note, that this doesn't necessarily apply to versioned source pacakges
[16:11] <bdmurray> and a response like "$pkg_name has been removed by Ubuntu because of ....  While your bug repot is valid we are setting it to Won't Fix since the software is no longer included in Ubuntu."
[16:12] <micahg> bdmurray: sounds good
[16:12] <yofel> 'sun-java6' would be affected too as it was removed in lucid, right?
[16:13] <micahg> yofel: well...that's pretty SRUable for security updates
[16:13] <bdmurray> I've a script somewhere for finding packages removed from the archive if someone is really interested
[16:13] <micahg> but in terms of feature requests, for sure
[16:13] <yofel> micahg: didn't we talk about non-SRUable stuff?
[16:13] <micahg> yofel: yeah
[16:14] <bdmurray> micahg: Do you have anything else on this topic?
[16:15] <micahg> bdmurray: I wonder if there's a way to flag in LP about this
[16:15] <bdmurray> micahg: what do you mean / have in mind?
[16:16] <micahg> bdmurray: warn people before they submit new bugs about the guidelines for the package (only major/security fixes)
[16:16] <bdmurray> well there are the package bug filing guidelines. ;-)
[16:17] <micahg> bdmurray: right, but normally we take all types of bugs, I think if we can stop people before they submit a bug that will never be fixed, it will be less of a let down
[16:17] <bdmurray> Yes, I'm saying we can put a message in the package bug filing guidelines for those specific packages not to file bug reports.
[16:17] <yofel> well, as the package is removed and most bugs are now reported with apport this shouldn't be much of an issue as apport will refuse to report a bug
[16:18] <micahg> bdmurray: ah, who can edit those?
[16:18] <bdmurray> micahg: I think only a very small subset of people can (including me), but it's quite easy to script it.
[16:18] <micahg> yofel: ubuntu-bug on the stable release should still allow bug submission
[16:18] <bdmurray> micahg: so if you come up with a message I'd be happy to set them.
[16:19] <yofel> micahg: oh, you're right, meh...
[16:20] <bdmurray> Okay, so all square there?
[16:20] <micahg> I think so
[16:21] <bdmurray> okay another micahg topic then ;-) mention of #ubuntu-bugs in LP
[16:22] <micahg> bdmurray: I was thinking to have some mention of the channel WRT asking about bugs rather than causing more bugmail with what's the status
[16:23] <bdmurray> micahg: So when viewing a bug or reporting a bug?
[16:23] <thekorn> I think it would be nice to have "bug triaging guidlines" (similar to "bug reporting guidlines") on a per package basis in launchpad
[16:23] <micahg> bdmurray: viewing I think
[16:23] <bdmurray> The only thing we could easily change would be the ubuntu bug filing guidelines.
[16:23] <micahg> thekorn: I'd prefer bug commenting guidelines ;)
[16:24] <thekorn> ok, both then ;)
[16:24] <hggdh> why not both?
[16:24] <micahg> see bug 518261
[16:24] <ubot4> Launchpad bug 518261 in malone "user with low karma should get an alert before being allowed to comment (affects: 5)" [Low,Triaged] https://launchpad.net/bugs/518261
[16:24] <hggdh> oh. Too late
[16:25] <thekorn> always keep in mind, it's not always people with low karma writing stupid things ;)
[16:26] <persia> In fact, leaving lots of "me too" comments generates karma.
[16:26] <bdmurray> micahg: what exactly do you want to have happen since this is a Launchpad change?
[16:26] <bcurtiswx> thekorn: don't talk about me like that :P
[16:26] <hggdh> the problem is that karma reflect *current* work levels. OK, normalised, and all of that. Still, I can have 0 karma
[16:27] <thekorn> bcurtiswx, haha
[16:27] <vish> i would think it should be combined with Bug #414401 , user's just leave a comment and dont subscribe to the bug
[16:27] <ubot4> Launchpad bug 414401 in malone "Automatically subscribe users to bug mail when they post a comment (affects: 1)" [Medium,Triaged] https://launchpad.net/bugs/414401
[16:28] <qense> Did I miss the meeting?
[16:28] <hggdh> qense: going on
[16:28] <qense> ok
[16:30] <micahg> bdmurray: I'm not sure exactly, maybe something at the top of all Ubuntu bug pages saying to check w/ #ubuntu-bugs on freenode for bug updates
[16:30]  * micahg is sorry, battery died
[16:31] <qense> micahg: You suggest to add it too wiki.ubuntu.com/BugSquad/Header ?
[16:31] <bdmurray> micahg: okay
[16:32] <bdmurray> Is there anything else on this topic?
[16:33] <micahg> qense: might not be a bad idea
[16:33] <micahg> I don't think so
[16:35] <bdmurray> micahg: is there an reported bug about Launchpad for this?
[16:35] <micahg> bdmurray: i don't think so
[16:38] <bdmurray> micahg: Okay, if you report one lets us know.
[16:38] <bdmurray> Are there any other topics for this meeting?
[16:38] <vish> ... wanted to mention the recent issue with un-upstreamed bugs being marked as "incomplete" [and accidentally wrongly closed when they expire?], several members mentioned here that the status is misleading and we could rather mark it as "confirmed" instead.. probably tag it "needs upstreaming" ?  [the folks who discussed it are probably doing it now , but maybe we could mention it to others as well? and mention it on the wiki]
[16:39] <persia> I'd like to second that.
[16:40] <bdmurray> well, tagging it needs-upstreaming seems redundant as it is possible to open an upstream task w/o a bug watch
[16:40] <persia> Maybe just not marking them incomplete?
[16:40] <qense> What do you guys think of the proposal I sentt ot he mailist to ask triagers to open an emtpy bug watch as soon as they move a bug to Confirmed?
[16:40] <vish> good point , yeah the incomplete is the bad part ;)
[16:40] <bdmurray> Yes, I don't see why it would be incomplete if it was an upstream issue
[16:41] <persia> qense: I don't think that's useful for all bugs: lots of the bugs I end up doing something to should not be upstreamed.
[16:41] <bdmurray> And it should be tested w/ the upstream version...
[16:41] <persia> For extra points, certainly :)
[16:41] <qense> persia: that is a problem with it indeed
[16:42] <qense> but we could say that they only should open an empty bug if their common sense tells them it makes sesne
[16:44] <bdmurray> well I think we should be more specific than "common sense" and have some guidelines to help people ;-)
[16:45] <qense> of course
[16:45] <qense> But I do think that it could be very useful in situations where it is an upstream issue and it is straightforward to forward the bug upstream
[16:46] <persia> I think adding a guideline to test with the upstream version should be an important part of that.
[16:46] <bdmurray> Well, if it were straight forward it would have be forwarded I hope. ;-)
[16:46] <persia> Otherwise we end up darkening our reputation "You guys keep sending us bugs that we fixed months ago..."
[16:46] <bdmurray> But regardless opening an upstream task is a good idea.
[16:46] <qense> an empty bug task doesn't do anything upstream yet
[16:47] <qense> but it does make the bug show up on specific searches
[16:47] <persia> I guess.  I'm just not convinced that lots of bugs are upstream.  Lots of things seem to happen because of our packaging or our patches.
[16:47] <qense> persia: Agreed. One guideline should be: only if it clearly is upstream.
[16:47] <persia> Depends on the package, of course :)
[16:47] <hggdh> and this is the point where knowledge of upstream may help differentiate, persia
[16:48] <qense> I just would like the affected bugs to show up on the need-forwarding searches.
[16:48] <persia> qense: How do we determine that without having people test against unpackaged upstream?
[16:48] <bdmurray> Or "if you think this is an upstream issue and want a 'bug forwarder' to check whether or not it exists upstream"
[16:48] <qense> However, there is an issue with those searches that all empty bug tasks are currently counted as an empty bug watch for all packages. This could hinder when there are multiple affected products and packages.
[16:48] <persia> hggdh: Very much so.
[16:48] <hggdh> my major worry is indiscriminate upstreaming
[16:48] <qense> persia: bdmurray answered that now
[16:49] <qense> hggdh: that is indeed something we should take care of
[16:49] <persia> bdmurray: That seems a good middle ground, as it saves on the hand-holding to test against uppackaged upstream.
[16:49] <hggdh> an example is bug 454949
[16:49] <ubot4> Launchpad bug 454949 in poedit (Ubuntu) (and 1 other project) "poeditor crashed with SIGSEGV in g_main_context_prepare() (affects: 2)" [Low,Confirmed] https://launchpad.net/bugs/454949
[16:50] <qense> But again, giving a bug an empty bug watch allows people with the right knowledge about upstream to take a look at it and confirm whether it needs forwarding.
[16:50] <charlie-tca> Couldn't you start with "check the source package. If it does not end with 'ubuntu?' upstream it"
[16:50] <persia> qense: And we would mark the empty upstream task as invalid if we determined it wasn't an upstream bug?
[16:51] <qense> persia: yes
[16:51] <qense> It does add another layer of triaging between upstream and downstream, but I think it could be worth it.
[16:51] <persia> I'm still not happy, but I don't tend to do mass-bug stuff, and if it's enough of an improvement to those who do, I'll stop arguing against it.
[16:51] <micahg> charlie-tca: that doesn't always mean the problem isn't ours
[16:52] <hggdh> and what about these upstream that do not have a BTS? e.g., coreutils, where the preferred way is to send an email
[16:52] <qense> it would be of a great help to AdoptionTeams, even though there is just one atm :S
[16:52] <persia> hggdh: For that, you end up needing to track status manually, but you can still link to the email.
[16:52] <charlie-tca> but it is a general guideline, which should be fairly accurate, since we did not patch the upstream source
[16:52] <qense> persia: doesn't that spam the author with bug mail?
[16:53] <qense> hggdh: in that case the empty bug watch could help to allow people with the right expertise to find those bugs and contact the author
[16:53] <hggdh> persia: oh. And LP will not be sending ping emails, I hope? (not documented at all, the bevahiour)
[16:53] <qense> indeed, not at all
[16:54] <persia> hggdh: I don't think so.  Try tracking something on our mailing list as a test :)
[16:54] <bdmurray> hggdh: LP does not send e-mail in that case
[16:54] <persia> qense: I think that's only in the case of subscriptions.
[16:54] <qense> But it does expose the e-mail to the world.
[16:54] <hggdh> cool. Then I will start linking my emails to coreutils
[16:54] <gnomefreak> i got email about subscibing to bug evaluvation list but it says i am already subscibed
[16:54] <hggdh> no prob, it is already linked in the bugs
[16:54] <persia> qense: But presumably one links to the email on some list archive, which is already exposed to the world.
[16:55] <qense> that's true
[16:55] <persia> That's much preferable than cc:ing the bug when sending upstream if using launchpad, in my opinion.
[16:55] <qense> persia: but it's harder to find for annoying users
[16:55] <persia> The Debian BTS has different practices, but I don't think we want to mirror them, as we don't have all the avoid-sending-extra-mails controls in place.
[16:56] <persia> qense: I thought we were trying to improve documentation of upstreaming where there is no bug/issue tracker, not support annoying users :)
[16:56] <persia> I'm sure they can find upstream mailing lists anyway, and will be summarily flamed.
[16:56] <qense> persia: when putting that mail address there the annoying users can easily find it to whine about the bug
[16:57] <bdmurray> That seems rather unlikely to me.
[16:57] <hggdh> which will end with them in local spam filters
[16:57] <hggdh> no prob
[16:57] <qense> I hope so.
[16:57] <charlie-tca> gnomefreak: that team has been deleted
[16:57] <persia> qense: My apologies if I'm not clear.  I don't mean to put a mail address as the link, but rather a link to the actual mail sent in the upstream mailing list archive.
[16:57] <gnomefreak> charlie-tca: ok thanks
[16:58] <qense> persia: I thought you couldn't do that with LP, can you?
[16:58] <persia> That lets us see the upstream bug, and track it (using the upstream mailing list threading features), as if there was an upstream bug tracker.
[16:58] <persia> Used to be able to do so.  It's just URLs.
[16:58]  * persia checks the current state
[16:59] <persia> qense: For the upstream task, just set the URL to the mail in the archives under the URL copy in the Remote Watch.
[16:59] <persia> I haven't tested actually doing it, but the UI seems to allow it.
[16:59] <qense> persia: nice! I learned something new today.
[17:00] <qense> If we are going to make this general policy we should ask Launchpad to solve the search issue with empty bug watches. The work-flow won't work if nempty bug watches for non-related upstreams show up in the results as well.
[17:00] <micahg> qense: I think there may be a bug for that...
[17:00] <bdmurray> qense: is there a bug about that and / or do you have an example?
[17:00] <persia> Oh, this was to get stuff out of that search list intentionally, for the case hggdh mentioned where upstream doesn't have a proper tracker.
[17:01]  * qense is looking for an example
[17:01] <hggdh> BTW, another example is libpst -- only email contact is accepted. No ML available, also (sort of an extreme example, though)
[17:03] <micahg> bug 196814
[17:03] <ubot4> Launchpad bug 196814 in malone "searching for bugs needing forwarding returns one that doesn't (affects: 1)" [Undecided,Confirmed] https://launchpad.net/bugs/196814
[17:03] <qense> https://bugs.edge.launchpad.net/ubuntu/+source/ubuntu-meta/+bugs?field.status_upstream=pending_bugwatch&field.status_upstream-empty-marker=1
[17:03] <bdmurray> oh, look who the reporter was
[17:03]  * bdmurray rolls eyes
[17:04] <thekorn> you cannot insert random URLs in the "Url for upstream bug" field, it has to be a url of a known bugtracker
[17:05] <micahg> thekorn: right, and a few trackers like JIRA still aren't supported
[17:06] <qense> I even got problems with Debian BTS once!
[17:06] <qense> Does SF work now?
[17:07] <bdmurray> Okay, I think we've covered marking bugs as needing forwarding pretty well.
[17:07] <qense> yes, vote?
[17:07] <bdmurray> I'd like to see what will go in the documentation sent to the mailing list for group review.
[17:08] <bdmurray> Is there anything else on this topic?
[17:09] <qense> I could write a proposal.
[17:09] <bdmurray> qense: that'd be great
[17:09] <qense> iirc we're already at the Open Disussions point of the agenda
[17:09] <qense> Did you talk about "pollution caused by pending release nominations -- hggdh" already?
[17:09] <bdmurray> qense: yes, and we are over time
[17:09] <bdmurray> qense: no, we didn't go over that
[17:09] <qense> ok
[17:09] <qense> well, it's time indeed
[17:11] <bdmurray> Thanks everyone!
[17:11] <charlie-tca> sorry I was a bit late, taking of a baby
[17:12] <bdmurray> charlie-tca: no problem!
[17:12] <persia> thekorn: Could we open a bug to request support for mailing lists (not tracked, just linked) to make the blank upstream tasks more useful?  Otherwise they will get cluttered in time
[17:12] <qense> nice meeting
[17:13] <qense> all: Mark bug #196814 as affecting you!
[17:13] <ubot4> Launchpad bug 196814 in malone "searching for bugs needing forwarding returns one that doesn't (affects: 2)" [Undecided,Confirmed] https://launchpad.net/bugs/196814
[17:13] <thekorn> persia, makes sense, will create one later today
[17:13] <persia> thekorn: Thanks.
[17:18] <bdmurray> mvo: why does update-manager and apt think I'm out of disk space?
[17:43] <qense> bdmurray: Did you have time to review my merge request for lp:~ubuntu-bugcontrol/apport/ubuntu-bugpatterns today?
[17:46] <bdmurray> No, I did not have time yesterday.  Will look at it right now though.
[17:46] <qense> thanks!
[18:26] <crimsun> kermiac: done. it's a WONTFIX because we can't differentiate on the hw side at all, so it must remain manual.
[18:27] <bdmurray> qense: actually your pattern for bug 362342 isn't working
[18:27] <ubot4> Launchpad bug 362342 in nautilus (Ubuntu) (and 1 other project) "nautilus crashed with SIGSEGV in g_list_remove() (affects: 69) (dups: 15)" [Medium,Triaged] https://launchpad.net/bugs/362342
[18:27] <qense> bdmurray: no? I checked it at my PC and I thought it was working correctly.
[18:31] <bdmurray> qense: there got it sorted with <re key="Stacktrace">in IA__g_list_remove.*\n.*glist\.c:338</re>
[18:35] <qense> bdmurray: OK then. I'll edit the pattern with your suggestion and push the new file.
[18:35] <bdmurray> qense: oh, its fine I'll do it
[18:35] <qense> bdmurray: ok, thx
[18:39] <bdmurray> there all set
[18:40] <qense> bdmurray: thank you!
[18:41] <metricpiano> I made a comment on Launchpad bug 471385 in sbackup "simple backup restore error in 9.10" [Medium,Triaged] https://launchpad.net/bugs/471385, that it affects 10.4 as well (e.g. not triaged in 10.4) is there any additional thing I should do to properly report?
[18:41] <ubot4> metricpiano: Bug 471385 on http://launchpad.net/bugs/471385 is private
[18:41] <ubot4> Launchpad bug 471385 in sbackup (Ubuntu) (and 1 other project) "simple backup restore error in 9.10 (affects: 1)" [Medium,Triaged]
[18:44] <yofel> metricpiano: as I said in #ubuntu+1, the bug is triaged as the bug task doesn't specify a release, and please mark the bug as affecting you
[18:51] <hggdh> heh
[18:53] <hggdh> yofel: you had just told him the same
[18:53] <yofel> I know...
[18:56] <mvo> bdmurray: what is you df -h output? could you /msg that to me?
[18:56] <bdmurray> mvo: it was my apt-cacher system that was out of disk space
[18:58] <mvo> bdmurray: ok
[20:08] <LimCore> continuing on the clipboard topic
[20:08] <LimCore> bug #11334
[20:09] <ubot4> Launchpad bug 11334 in ubuntu (and 2 other projects) "MASTER Copy-Paste doesn't work if the source is closed before the paste (affects: 66) (dups: 20)" [Wishlist,Confirmed] https://launchpad.net/bugs/11334
[20:09] <LimCore> one of most reported bug I seen, 66 affected and dozen of dupes, reported in 2004 and STLL it is just marked as wishlist??
[20:10] <micahg> LimCore: it is a wishlist
[20:10] <LimCore> the blood clipboard does not work, its a bug
[20:10] <micahg> LimCore: it's new functionality
[20:11] <LimCore> a feauture present in all desktops since decades has a kludge that causes tons of reporters to complain. bug
[20:11] <micahg> LimCore: no it's not present, that's the issue
[20:11] <LimCore> copy and paste is present. The kludge: it fails if source app was closed
[20:11] <micahg> it's perceived as present, but it is not
[20:12] <LimCore> in either case, dont you think someone should seriously take a look at this?
[20:12] <micahg> LimCore: the respective upstreams are AFAIK
[20:12] <micahg> I think this is fixed in FF3.7
[20:12] <LimCore> this is the most embarassing ubuntu/linux desktop bug probably.  Linux does not deliver correct functionallity that was present in windows 3.11
[20:12] <LimCore> micahg: it's about all apps and about WM/desktop, not about one application like firefox
[20:12] <micahg> LimCore: if apps respected the standard, it wouldn't be a problem
[20:13] <LimCore> users do not care why
[20:13] <micahg> LimCore: doesn't matter...this isn't about who's fault
[20:13] <LimCore> yes
[20:13] <LimCore> so, how to fix it AFTER 6 bloody years ;) (counting since first reports)
[20:14] <LimCore> (or after 15 years, counting from competiting desktop OSes ;)
[20:14] <micahg> depends on upstreams
[20:14] <micahg> 4 upstreams not fixed 6 are
[20:14] <micahg> there really shouldn't be one big bug for this
[20:14] <chrisccoulson> LimCore - fix it then (or find someone who cares enough to fix it, or pay somebody to fix it)
[20:15] <LimCore> what??? 4 upstreams
[20:15] <micahg> LimCore: have you read the description?
[20:15] <LimCore> yes I read it and I see it makes no sense
[20:15] <LimCore> not fixed in "xorg open office gimp..." why is each app listed separatelly, this is a global problem in WM no?
[20:15] <micahg> at the end there's a list of what's fixed and what's not
[20:15] <micahg> LimCore: no, it's not
[20:16] <jcastro> nope, it's per-app
[20:16] <chrisccoulson> its got nothing to do with the WM
[20:16] <LimCore> just this 4 apps are broken in entire ubuntu world?
[20:16] <LimCore> chrisccoulson: then why WM applet like say klipper can "fix it" ?
[20:16] <micahg> you can solve it globally by installing a clipboard manager, but it should be unnecessary
[20:16] <LimCore> really just 4 apps are broken? then sure fix them
[20:16] <chrisccoulson> LimCore, i've got no idea what you mean
[20:16] <chrisccoulson> the WM has nothing to do with the clipboard whatsoever
[20:16] <LimCore> chrisccoulson: what micahg just said
[20:17] <LimCore> right, I should had written Desktop Manager, not wm
[20:17] <micahg> LimCore: it's a workaround, not a solution
[20:17] <micahg> if you have time to fix, feel free
[20:18] <LimCore> you seem to not agree with me that this is very very embarassing fail for ubuntu, and that it takes really really waiting of users for the fix (or workaround) for it ?
[20:18] <jcastro> no one is disagreeing with you that it sucks
[20:18] <micahg> we're all busy with other things
[20:18] <LimCore> if you agree, then I think any working fir, OR workaround would be really better then 5/15 years long not working on most essentiall desktop functioanllity
[20:18] <jcastro> It's not like we have developers growing on trees that we can throw at the problem
[20:19] <LimCore> I wonder, Ubuntu have what, hundrets of develes/bugsquad members/whatevers right?
[20:19] <jcastro> no
[20:19] <micahg> LimCore: with 20k packages to support
[20:19] <jcastro> we don't
[20:19] <LimCore> what more imporant are you fixing, there is a few of such old bugs
[20:19] <LimCore> (I would guess)
[20:20] <LimCore> actually, how to list all bugs that are currently being "worked on"?
[20:20] <yofel> LimCore: newer bugs that result in broken systems
[20:20] <micahg> LimCore: most of the devs are probably trying to stabilize apps for lucid right now
[20:20] <chrisccoulson> right, what micahg said
[20:20] <micahg> LimCore: in theory "In Progress" bugs
[20:20] <LimCore> micahg: this is why I originally said we need to increase priority a bit, wishlist is lowest
[20:20] <chrisccoulson> making sure things don't regress etc
[20:20] <JFo> LimCore, I have 10,000+ bugs on the kernel and only about 22 devs
[20:20] <persia> LimCore: There's no reliable method to list all the bugs currently being investigated.  "In-Progress" can be a guide, but not everyone sets it, and not every issue investigated by developers is added to LP.
[20:20] <micahg> LimCore: it's not a high priority in the scheme of things
[20:20] <LimCore> kernel bugs?
[20:20] <JFo> yes
[20:21] <LimCore> is the other half of developers taking time to introduce new bugs to vanilla kernels, because they appear to have much fewer ;)
[20:21] <yofel> LimCore: still, you can work around a broken clipboard by installing a clipboard manager, so there's an easy workaround, there are more important things
[20:21] <JFo> they have more than I do
[20:21] <micahg> LimCore: we've got bugs affecting thousands of people
[20:22] <LimCore> what query do you use to see "most important" bugs overall?
[20:22] <JFo> it depends on what exactly you are looking for.
[20:22] <micahg> LimCore: again, critical/high is a guide
[20:22] <LimCore> this state of things will continue for foreseeable feature right?
[20:23] <hggdh> oh. BTW, there is parcelite, a Gnome clipboard manager. It works
[20:23] <micahg> LimCore: what do you mean "state of things"
[20:23] <LimCore> so this bug will remain unfixed as "whishlist" during lucid, 11.04, 2012, 2015, 0001-After.Martians, 0010-A.M. and so on right?
[20:23] <LimCore> micahg: no one having time to fix this bug
[20:23] <micahg> LimCore: you're welcome to fix that
[20:24] <hggdh> keep in mind this is free software. All you need to do is get the source and fix it
[20:24] <LimCore> micahg: I fixed logging thingy in opensshd, and now looking into svnserve authoriztion bug
[20:24] <micahg> LimCore: that's great and I'm sure many people are happy that you did
[20:24] <hggdh> oh. Let me see. You are busy. Very much like us.
[20:24] <micahg> but a lot of work is done both upstream and in Ubuntu by volunteers
[20:25] <LimCore> hggdh: since we all agree this bug sucks a big lolipop, we should perhaps mark it as Medium or High so eventually someone WILL fix it?
[20:25] <persia> Although importance is a guide, it doesn't tend to be an absolute indicator of developer priority.
[20:25] <hggdh> LimCore: it *is* a wishlist. Being wishlist does not raise or lower how important it is. Having tens of dups, and 60 many affects-me-too does that
[20:26] <LimCore> ok, how about we just install a WORKING (not glipper) clipboard manager for GNOME (for KDE we have klipper and it works) and done?!
[20:26] <LimCore> *by default
[20:26] <LimCore> it was my previous idea, then we found out glipper is broken
[20:26]  * hggdh again thinks of parcelite (just to think of one)
[20:26]  * LimCore tries it
[20:26] <persia> One way to do that would be to extensively test some of the available packages that solve the issue and make sure they are compatible with everything.  If so, discuss the possibility of including one by default.
[20:26] <micahg> LimCore: that won't guarantee anything and is misleading
[20:26]  * micahg is going to add the workaround to the bug
[20:27] <LimCore> micahg: it will guarantee that it would work in gnome
[20:27] <LimCore> perhaps I should just talk to gnome developer so they would build it in or smth
[20:27]  * hggdh feels cranky today, and begs pardon
[20:27] <micahg> I just added the workaround to install either klipper or glipper which should solve the issue
[20:28] <LimCore> micahg: glipper sucks a big lolipop too, it for example crashes (jesus)
[20:28] <hggdh> oy vey
[20:28] <micahg> hggdh: parcellite by the way :)
[20:28] <hggdh> oh. Too few ells, sorry
[20:28] <LimCore> last time I tried glipper to work around this...
[20:29] <LimCore> ...I found out 2 new bugs lol
[20:29]  * LimCore wonders would he got 1024 bugs after 10 attempts to work around
[20:31] <micahg> LimCore: keep in mind there is no "core ubuntu" like there is windows...Ubuntu is a collection of other pieces of softawre
[20:39] <persia> micahg: While I agree with you, it may be worth adjusting your nomenclature to avoid the potential implication that "core-dev" is related to some core.
[20:40] <vish> LimCore: trolling eh? ;) copy-paste bug
[20:40]  * hggdh listens to some cool jazz
[20:40] <persia> And actually, there is something that would fit in that category, being "^ubuntu-minimal", but it doesn't include an X server, so is probably more minimal than many might consider.
[20:40] <micahg> s/"Core Ubuntu"/Ubuntu Code/
[20:40] <micahg> persia: I thought ubuntu-minimal was a metapackage of other pacakges
[20:41] <LimCore> vish: what?
[20:41] <vish> LimCore: nah , the comment on the bug :)
[20:42] <persia> micahg: Well, yes (and ^ubuntu-minimal is the related task), but it also closely represents the smallest amount of stuff required to qualify as "Ubuntu".
[20:42] <micahg> persia: right, but the point is, that's a collection of otehr software, not software by itself
[20:43] <micahg> persia: I'm not saying we can't do it, I'm saying comparing to Windows isn't a fair comparison
[20:47]  * hggdh throws the bloody jazz away, and goes on straight into Scheherazade, with Daniel Baremboim & the Chicago Symphony
[20:50] <persia> micahg: I'll agree with that, certainly.  Just being nitpicky :)
[20:53] <monkeylibre> hi all, please anyone could change the status to triaged of https://bugs.launchpad.net/ubuntu/+source/poedit/+bug/454949 ?
[20:53] <ubot4> Launchpad bug 454949 in poedit (Ubuntu) (and 1 other project) "poeditor crashed with SIGSEGV in g_main_context_prepare() (affects: 2)" [Low,Confirmed]
[20:54] <hggdh> ? monkeylibre I did set it to triaged yesterday, or today morning
[20:55] <hggdh> oh. OK, done, monkeylibre
[20:55] <monkeylibre> Thank You hggdh
[20:55] <hggdh> welcome
[20:58] <vish> micahg: is the description  "This bug is an Epic Fail, because... " required ? [just asking since you updated the bug and that part remained ;)]
[20:58] <micahg> vish: no, I was thinking of removing that
[20:58] <micahg> vish: feel free :)
[20:58]  * vish on it
[20:58]  * micahg doesn't want to get flamed...
[20:59] <hggdh> a bug description should state -- clearly -- what the problem is, not the views and opinions
[20:59] <hggdh> micahg: I can do it, feeling like a schmuck today already
[20:59] <micahg> hggdh: agreed, but we know how that goes...
[21:00] <hggdh> heh. LP timedout on me. The WORLD is against me today :-(
[21:02] <hggdh> micahg: done. Now /me sits down and waits for the flames
[21:02]  * micahg hands hggdh a flame-retardant suit
[21:03]  * hggdh dresses up, fast
[21:03] <hggdh> what is this LP branch there?
[21:04]  * micahg doesn't know
[21:05] <qense> hggdh: isn't LP timing out on you whole last week?
[21:06] <hggdh> yes, it is personal. What I should expect from life, I guess. Feeling *very* woodyallen today, though, so take it with a grain of salt
[21:06] <hggdh> hell, make it a pound of salt
[21:07] <LimCore> hggdh: it's LP's way of telling you that 5 years of waiting to fix a bug indeed is epically long
[21:08] <qense> Nice way
[21:08] <hggdh> :-) and just making it even longer, I guess
[21:13]  * vish just noted that chrisccoulson might get his pet peeve solved ;p  [blanking bug status icon]
[21:13] <chrisccoulson> yeah, we should just get rid of the notification
[21:13] <chrisccoulson> its useless ;)
[21:13] <chrisccoulson> that's my opinion anyway
[21:14] <hggdh> chrisccoulson: sorry, I am not quite sure what you are talking about...
[21:14] <vish> chrisccoulson: so the gpm and nm status icons will use the app indicators for Lucid? [/me thought those two were for Lucid+1]
[21:15] <chrisccoulson> hggdh - the "your display is broken" notification that gnome-power-manager sometimes shows
[21:15] <hggdh> oh, OK. Sorry again
[21:15] <chrisccoulson> vish - gpm is quite a trivial port
[21:15] <chrisccoulson> but i don't think NM will be using it
[21:15] <vish> ok. thanks
[21:18] <vish> hggdh: lol , you edited the description while i was editing  ;)  double edit :D
[21:18] <vish> *copy-paste bug
[21:19] <hggdh> vish: heh. Next bug for LP -- conflit merge
[21:19] <hggdh> (must be automagic)
[22:17] <hggdh> persia: good questions to Shane ;-)
[22:17] <hggdh> I was trying to get him on IRC, but cannot remember his nick
[22:20] <hggdh> duh. fagan...
[22:40] <persia> hggdh: fagan
[22:59] <charlie-tca> Can I get bug 519541 triaged with high importance. It does cause the user to lose the documents if not saved before trying to get help
[23:00] <ubot4> Launchpad bug 519541 in abiword (Ubuntu) (and 1 other project) "Abiword 2.8.1 freezes with document lost when help is clicked or F1 is pressed (affects: 2)" [Undecided,Confirmed] https://launchpad.net/bugs/519541
[23:29] <bdmurray> charlie-tca: only high?
[23:29] <ke1ha> just tred to bzr lp:ubuntu-docs/karmic and got a pythin link error:
[23:29] <ke1ha> *** glibc detected *** /usr/bin/python: corrupted double-linked list: 0x0eb31cc0 ***
[23:30] <ke1ha> sri ... python error .. any ideas on what's causing that ?
[23:30] <charlie-tca> High should work on our side, I upstreamed it to abiword bugzilla, so it really depends on them now.
[23:30] <hggdh> ke1ha: sounds like a real python (or associated library) bug
[23:31] <charlie-tca> They won't take the status from us, as far as I know, but I marked it for dataloss and usability, which is a high priority for them
[23:31] <bdmurray> charlie-tca: okay, high it is and I opened a Lucid task
[23:31] <ke1ha> rr. I've a lengthy trace-back so will submit to bugs.
[23:31] <charlie-tca> Thank you
[23:32] <bdmurray> hggdh: what were you saying about the wiki this morning?
[23:32] <hggdh> er
[23:32] <hggdh> oh.
[23:32] <hggdh> Pedro and I tried to subscribe bugsquad to wiki changes, and could not find a way
[23:33] <hggdh> only individuals, as far as I can see, can get it
[23:34] <hggdh> bdmurray: ^
[23:34] <micahg> hggdh: can you create an account with the ML as the e-mail and subscribe it?
[23:34] <hggdh> duh. Should work, yes.
[23:34] <bdmurray> that sounds like a good work around
[23:35] <hggdh> will try it. First I will find a piece of ground not snowed in, and will much some grass :-(
[23:35] <micahg> hggdh: ?
[23:36] <hggdh> I feel I am dumb today, micahg. Of course, everybody will get the confirmation mail, but no big deal there
[23:36] <micahg> hggdh: if you can change emails, send to private first, then set to ML after confirmation?
[23:37] <micahg> well, that'll still send a confirmation to the ML
[23:37] <bdmurray> well, it'd be useful to know what we are subscribed to ;-)
[23:37] <micahg> so whatever
[23:37] <hggdh> will try, but I would expect it to send another confirmation
[23:37] <hggdh> getting it done
[23:37] <bdmurray> and they might get filtered anyway
[23:51] <hggdh> OK. BugSquad/.* and Bugs/.*
[23:51] <hggdh> any other pagespace from the wiki?
[23:52] <benofiniquity> I keep getting "psmouse.c: TouchPad at isa0060/serio1/input0 lost sync at byte 1" and "psmouse.c: bad data from KBC - timeout bad parity" errors in dmesg.  Both my keyboard and touchpad will not respond if there's no input for a couple of seconds.  After typing a key or moving around on the touchpad, things are fine as long as I keep moving or typing. After a couple seconds, everything stops responding again. Most posts onlin
[23:56] <hggdh> bdmurray, micahg: does nto work. ubuntu-bugsquad@lists.ubuntu.com is already registered in LP to Ubuntu BugSquad.
[23:56] <hggdh> so we will need to set a forwarding email for that
[23:57] <micahg> hggdh: so the wiki tries to create an account?
[23:57] <micahg> in LP?
[23:57] <hggdh> yes. And it validates that the email you entered does not exist in LP already
[23:57] <micahg> hggdh: can we get a passwd set for bugsquad then?
[23:57] <hggdh> actually, you *must* create a LP account to login to the wiki
[23:58] <hggdh> bdmurray: ^
[23:58] <micahg> hggdh: I can give you an alias for it if you want?
[23:59] <persia> How hard to we want to work to make this happen?  Could we not just document that members are encouraged to subscribe to those wiki hierarchies?
[23:59] <hggdh> micahg: guess so, it will work for the while. Later on we can move it to bugsquad itself
[23:59] <hggdh> persia: we would like to pretty much force feed it in...