[00:08] <layn> To someone interested in a live online seminar at MySQL?
[00:19] <micahg> yofel: ping
[00:20] <yofel> pong
[00:20] <micahg> yofel: is sudo needed for apport-collect or is this a known issue?
[00:21] <micahg> bug 654898
[00:21] <ubot2> Launchpad bug 654898 in apport (Ubuntu) "apport-collect requires firefox closure (affects: 1) (heat: 6)" [Undecided,New] https://launchpad.net/bugs/654898
[00:21] <micahg> I was drafting a response, but wanted to make sure I was correct in saying it doesn't need sudo
[00:22] <yofel> actually, I'm not 100% sure, but afaik it shouldn't need sudo
[00:23] <yofel> there are bug reports lately about apport not requesting adming rights when it needs them though, so I'm a bit confused there too as I'm not sure what the expected behaviour is
[00:24] <yofel> one of the problems with sudo (apart from firefox) is the credentials file, if you create it with sudo, you'll always have to use sudo or you can't access launchpad
[00:26] <micahg> yofel: k, we should talk to pitti then, this should be addressed for Natty, if you could respond with whatever you think is appropriate and mention that Firefox should not be run with sudo, that would be good
[00:29] <yofel> will do so tomorrow, it's 1:28 am here, and I won't write bug comments I'm not sure about half asleep
[00:29] <micahg> yofel: k, thanks
[01:04] <hggdh> JFo: yo, do not worry aboutbeing rejected to bug-control
[01:05] <RedSingularity> Does anyone have a system set up with Ubuntu installations just for the testing of bugs?
[01:07] <JFo> hggdh ?
[01:07] <penguin42> RedSingularity: I have some VMs, but I also have two machines so if I break one it's not too big an issue
[01:08] <hggdh> JFo: I just rejected your original application to bug-control
[01:08] <JFo> ah
[01:08] <hggdh> JFo: you are already a member, I guess via a team
[01:09] <JFo> just saw your e-mail on the change :)
[01:09] <RedSingularity> penguin42:  Thats a great idea!  I am going to set up some VM's now.  Much better than buying another computer for testing.
[01:09] <JFo> thanks for the heads-up
[01:09] <hggdh> jcastro: the deluge has ended, we pretty much cleaned up the backlog on bug-control.
[01:09] <jcastro> \o/
[01:09] <jcastro> great job guys
[01:09] <penguin42> RedSingularity: Of course it doesn't test everything - like hardware issues
[01:09] <hggdh> JFo: please holler if needed ;-)
[01:10] <RedSingularity> penguin42:  true
[01:10] <jcastro> hggdh: do we stick teams in there now?
[01:10] <JFo> hggdh, looks like I am good
[01:10] <jcastro> like sometimes I have to renew people who are developers, etc.
[01:10] <penguin42> JFo: Ooh, someone said to check with you about what to do with some kernel bugs
[01:11] <JFo> penguin42, cool
[01:11] <hggdh> jcastro: yes, we do -- the team must be restricted (not open entry, like desktop-bugs), and one of the team should be responsible
[01:11] <jcastro> ok
[01:11] <penguin42> JFo: I believe bugs 628606, 628222, 636679 and 620530 are all bugs that are dupes of 614008
[01:11] <ubot2> Launchpad bug 628606 in linux (Ubuntu) "BUG: unable to handle kernel NULL pointer dereference at 00000008 (affects: 1) (heat: 124)" [Undecided,New] https://launchpad.net/bugs/628606
[01:11] <ubot2> Launchpad bug 628222 in linux (Ubuntu) "BUG: unable to handle kernel NULL pointer dereference at<PHONE_NUMBER>000008 (affects: 1) (heat: 115)" [Undecided,New] https://launchpad.net/bugs/628222
[01:11] <ubot2> Launchpad bug 636679 in linux (Ubuntu) "[119903.693261] BUG: unable to handle kernel NULL pointer dereference at 00000008 (affects: 1) (heat: 212)" [Undecided,New] https://launchpad.net/bugs/636679
[01:11] <ubot2> Launchpad bug 620530 in linux (Ubuntu) "BUG: unable to handle kernel NULL pointer dereference at 00000008 (affects: 1) (heat: 85)" [Undecided,New] https://launchpad.net/bugs/620530
[01:12] <penguin42> JFo: I found the fix to 614008 so am fairly sure they are the same - what's the right thing to do?
[01:13] <JFo> penguin42, I think we need some boilerplate response on how to fix/test that it is fixed and let each reporter get back to us on the fix on their individual hardware.
[01:13] <JFo> it is cumbersome, but until I have an easier way to do it there it is
[01:13] <penguin42> JFo: It's not hardware dependent - it was a bug in generic code
[01:13] <JFo> ah
[01:13] <JFo> hmmm
[01:13] <JFo> still, could be affected by differing hardware. We have seen tons of that in the past
[01:14] <JFo> best to err on the safe side
[01:14] <penguin42> JFo: Well you could - really, it's not in hardware specific
[01:15] <JFo> I understand, but the policy I am bound to is strict
[01:15] <JFo> odd behavior must get caught before it is a problem. And I must follow the guidelines set forth by my manager
[01:15] <penguin42> ok, so what's the right way to do it?
[01:15] <JFo> :)
[01:16] <JFo> there needs to be a comprehensive set of instructions for each of the original reporters to follow to test the fix on their systems
[01:16] <JFo> then each of those bugs needs to have that comment added
[01:16] <JFo> so that the original reporters can get their findings back to us
[01:16] <penguin42> JFo: Please try running lshw on an up to date Maverick installation, if it completes then the fix has worked
[01:16] <JFo> in addition to the testing of folks trying to watch those bugs
[01:16] <JFo> penguin42, sounds good to me
[01:17] <penguin42> JFo: And then what state to set it to - incomplete?
[01:17] <JFo> yes, please
[01:17] <JFo> pending their response
[01:18]  * penguin42 has another bunch that I *think* are actuallly due to the original problem that the patch that caused that bug fixed, but I'll check with apw since that was his
[01:19] <JFo> excellent :)
[01:21] <penguin42> JFo: The one I just put on 628606 OK ?
[01:22] <penguin42> (Most of the bugs were originally filed against lshw, so I'd merged those altogether into 614008 before fixing it - much easier!)
[01:23] <JFo> sounds good to me
[01:23] <JFo> penguin42 ^
[02:30] <RedSingularity> If I am working on getting info on a bug it is marked "Incomplete" correct?  I am asking because the user I am helping keeps marking it as "new"
[02:31] <hggdh> eeebotu will be off for 3 minutes due to reboot after security upgrades
[02:34] <mrand> RedSingularity: When questions are answered in a bug report, it is not improper for them to be moved back to 'new'
[02:35] <RedSingularity> mrand:  If it is marked as new wont it confuse others because they will think it is not being taken care of?
[02:37] <mrand> RedSingularity: Nope.  You could think of it the other way as well: if it was left as incomplete and you stopped answering questions, someone might think it should be expired as unanswered.  So the preference is to default to the "new" state.
[02:37] <darran> 654896 = wishlist?
[02:37] <mrand> Of course, in reality, anyone can see it is active in either situation.
[02:37] <hggdh> heh. Actual reboot time for eeebotu: 118 seconds
[02:37] <mrand> hggdh: Could be better, but not bad!
[02:38] <hggdh> mrand: well, this is a 8.04 server, not bad at all.
[02:38] <mrand> OH ! indeed!
[02:38] <hggdh> and there is the BIOS setup time... which is absolutely out of our control
[02:39] <mrand> unless you have the source code O:-)
[02:39] <hggdh> (another server I have takes 3+ minutes on BIOS setup, and ~20 seconds to boot)
[02:39] <hggdh> heh. there is that, indeed.
[02:40] <mrand> My company is building a custom machine.  It boots to netbsd prompt in 25 seconds, and that is completely unoptimized.
[02:40] <RedSingularity> mrand: Ah so incomplete is used ,literally, when there is info missing?
[02:41] <mrand> RedSingularity: Pretty much
[02:42] <RedSingularity> mrand:  Thanks
[02:46] <hggdh> I wish...
[02:48] <mrand> I'm going to try Ubuntu here very soon.  Only challenge is that it is headless.
[02:57] <charlie-tca> RedSingularity: When a triager is watching the bugs they are working, having it turned back to "New" is an alert to go look at the bug and see if it is ready to be
[02:57] <charlie-tca> placed in "Confirmed" or "Triage" status nwo.
[02:58] <charlie-tca> s/nwo/now
[03:02] <nigelb> hggdh: ping?
[03:03] <nigelb> akgraner: hggdh will be doing a sesion about "starting bug triage" :D
[03:04] <nigelb> (at least he promised he would)
[03:04] <RedSingularity> charlie-tca:  What can i mark it as if we find it was an error on the users part?
[03:05] <charlie-tca> If it not ready for status change, change it back to incomplete
[03:05] <nigelb> where'd he go? He was around 20 mins back!
[03:05] <charlie-tca> or whatever the previous status was
[03:05] <akgraner> nigelb, :-/   - I'll try to get in touch with him tomorrow - if you haven't by then
[03:06] <RedSingularity> charlie-tca:  How about "invalid"?
[03:06] <nigelb> akgraner: ok :)
[03:06] <charlie-tca> If the user marked it invalid without an explanation, just change it back to what is was
[03:07] <charlie-tca> You are the triager, you get to decide if it should be valid
[03:07] <akgraner> nigelb, thanks!
[03:07] <RedSingularity> charlie-tca:  So if it is an error on the users part can it be considered "invalid"?
[03:08] <charlie-tca> error as in the bug is not valid?
[03:08] <RedSingularity> Yeah, it is not a bug it is an error on the users end.
[03:09] <charlie-tca> Sometimes a reporter will comment that the issue no longer exists, or was filed by mistake. Yes, those can be invalid
[03:09] <RedSingularity> charlie-tca:  Thanks :)
[03:09] <charlie-tca> You are welcome
[03:09] <charlie-tca> I hope it helps
[03:09] <RedSingularity> It does!!
[03:10] <RedSingularity> charlie-tca:  I just find it annoying that I change the status and then the user changes it back to something else.
[03:11] <charlie-tca> heh, it is part of trying to help people
[03:11] <RedSingularity> Lol, true
[03:11] <charlie-tca> When you are watching 800 bugs at a time, sometimes it helps and sometimes it hurts
[03:16] <RedSingularity> charlie-tca:  How do you imitate the reporters environment?  I mean 64 bit or 32 bit or 10.04 or 10.10  Do you have another computer just for testing or do you use a VM?
[03:16] <charlie-tca> I have 3 386 systems for testing, and also use VirtualBox on my 64bit system
[03:17] <RedSingularity> Ahh ok
[03:18] <charlie-tca> I just install whichever version of Ubuntu or Xubuntu I need, and follow their directions to reproduce the issue. I can erase the drives anytime I need to.
[03:19] <RedSingularity> And you can do it with no problem on the VM's?
[03:19] <charlie-tca> Most of the time
[03:19] <charlie-tca> If it is hardware/video specific, you need the actual same hardware. Most issues hardware doesn't matter.
[03:20] <RedSingularity> Ok good because i am going to be using a VM until i get my hands on a spare PC.
[03:20] <charlie-tca> Great! I have been using VirtualBox for 3 or 4 years now.
[03:22] <RedSingularity> That is my preferred virtual machine software as well.  I am used to using it over VMWare.
[04:09] <flipefr> hello everbody
[04:13] <flipefr> does anybody knows how to build a bridge between a host and a virtual machine to simulate a remote conection ssh?
[04:14] <flipefr> or can anybody help me doing this for try a bug?
[04:16] <RedSingularity> flipefr: Did you ask this in #ubuntu?  There are a lot more users in there now.
[04:18] <flipefr> I ask it there
[04:18] <flipefr> but nobody aswer me
[04:18] <charlie-tca> flipefr: bug number?
[04:19] <flipefr> 654577
[04:19] <charlie-tca> bug 654577
[04:19] <ubot2> Launchpad bug 654577 in gnome-session (Ubuntu) ""shut down" should at least log out (prohibited by multiple users) (affects: 1) (heat: 6)" [Undecided,Incomplete] https://launchpad.net/bugs/654577
[04:19] <flipefr> that's it
[04:20] <flipefr> if anybody can try it i would be really thank
[04:21] <charlie-tca> that is true
[04:21] <flipefr> grateful
[04:21] <flipefr> you tried it?
[04:21] <charlie-tca> It is not allowed to log out for security reasons
[04:22] <charlie-tca> You have two users logged in, one can not restart or shutdown unless they are admin
[04:22] <charlie-tca> Been that way for about 1 year or more now
[04:23] <charlie-tca> I was one of those affected by the opposite, and filed bugs because it did shut down when more than one user was logged in
[04:24] <flipefr> so i suppose i can confirmed the bug
[04:24] <charlie-tca> yeah
[04:24] <flipefr> ok lots of thanks
[04:24] <charlie-tca> I don't think it will get changed, but you can confirm it
[04:24] <flipefr> i was in the birdge of starting mount a virtual machine only or try that
[04:25] <mrand> charlie-tca: bordering on wishlist?
[04:25] <mrand> since it is pretty obviously designed behavior.
[04:25] <charlie-tca> bordering. I suspect since it used to just log you out, even if the second login was running updates, it won't happen to get changed back
[04:26] <charlie-tca> wishlist is good as anything, though.
[04:26] <flipefr> wishlist then
[04:27] <charlie-tca> It's really a security issue if you can just shutdown the system when more than one user is logged in. You can shut down in the middle of the updates, and really make a mess of things.
[04:30] <charlie-tca> flipefr: It is easy to make a bridged connection in VBox now. Just go into settings for the machine, go to Network, select Bridged Network in the drop down
[04:31] <charlie-tca> Then select desired host interface from the list at the bottom, it needs to be your physical interface in the host machine
[04:32] <flipefr> i see the option
[04:33] <charlie-tca> heh, no more messing with TAP and bridges on the host!
[04:34] <flipefr> another thing i would ask you charlie
[04:34] <flipefr> apart of the connection
[04:34] <flipefr> is about bug
[04:35] <charlie-tca> sure
[04:35] <flipefr> once i confirmed the bug who can change the impotance field
[04:35] <charlie-tca> Anyone on bug control
[04:35] <flipefr> do you know anyone or i must look one ??
[04:35] <charlie-tca> Normally, you just ask here and tell us the importance you would like set
[04:35] <flipefr> i suppose the importance is wishlist
[04:36] <flipefr> as you can see this is my first bug
[04:36] <flipefr> so i am lost
[04:36] <charlie-tca> allow me
[04:37] <charlie-tca> You should change it to confirmed first, and comment that is ready. You can use a standard response for that from
[04:38] <charlie-tca> https://wiki.ubuntu.com/Bugs/Responses#Triage%20Successful
[04:38] <charlie-tca> All you do is copy the part in the gray box and paste it into comments.
[04:39] <charlie-tca> You click the little pencil in a circle next to "incomplete" and can then change status to "confirmed"
[04:39] <charlie-tca> Then I will go in and finish it
[04:40] <flipefr> i've just do it
[04:41] <flipefr> i think you can finish it
[04:43] <charlie-tca> Okay
[04:43] <flipefr> but i didn't use a standard response at the end
[04:44] <charlie-tca> It is normally better to stay with the standard responses. A lot of time and effort has been put into trying to get them so the reporter accepts the answers and doesn't get frustrated.
[04:46] <flipefr> ok
[04:46] <flipefr> next time i will use a standard
[04:46] <charlie-tca> done
[04:47] <charlie-tca> Also, you should subscribe to the bugs you work on, if you want to be notified when anything changes, or comments are made to it.
[04:48] <RedSingularity> charlie-tca:  What should i mark a bug as that has been ignored for a few months?
[04:48] <charlie-tca> Okay, Thanks for helping with bugs.
[04:49] <flipefr> thank you for helping me too
[04:49] <charlie-tca> It depends on whether or not the information is all there. If not, use the "old bugs" response
[04:49] <charlie-tca> https://wiki.ubuntu.com/Bugs/Responses#Old%20untouched%20bugs
[04:50] <charlie-tca> That asks for verification that the issue is still valid, if you can not reproduce it.
[04:50] <RedSingularity> Ok, there is no status option to set though?
[04:50] <charlie-tca> If there is enough information, set it to confirmed
[04:50] <charlie-tca> Anytime you ask the reporter for anything, set it to incomplete
[04:51] <flipefr> ok, i didn't know there was a list of standard responses
[04:51] <flipefr> so i will do next time
[04:51] <charlie-tca> We follow the "learn as you go" process. It works well.
[04:51] <flipefr> i love the organization here, if my work would be as documented as this it
[04:52] <charlie-tca> It is very difficult to learn everything about bugs at one time, so we have to try to teach as you do them.
[04:52] <flipefr> so thanks again, i think i am leaving
[04:53] <charlie-tca> You are very welcome. Just ask questions here as you need to. Someone will try to answer for you
[04:53] <flipefr> ok
[04:53] <flipefr> bye
[04:53] <charlie-tca> Good bye
[04:54] <charlie-tca> I have to say goodnight, myself. RedSingularity: Thanks for helping
[04:55] <RedSingularity> Good night buddy.  Thanks for your help as well :)
[11:04] <layn> Hi
[11:04] <layn> I noticed that there is a package that helps in finding the bug: bughelper but I can not upload it I followed the guide but does not work with the command sudo apt-get install bughelper not find the package through bzr nor could you help me?
[11:05] <layn> can someone help me install bughelper
[11:10] <layn> I noticed that there is a package that helps in finding the bug: bughelper but I can not upload it I followed the guide but does not work with the command sudo apt-get install bughelper not find the package through bzr nor could you help me?
[11:10] <kaushal> hi
[11:10] <layn> kaushal: hi
[11:11] <layn> kaushal:Hello! can you help?
[11:11] <kaushal> layn: Please suggest me about http://pastebin.ubuntu.com/506390/
[11:11] <layn> ok
[11:12] <kaushal> I see this in dmesg of Ubuntu 10.04 desktop
[11:18] <layn> mmm
[11:19] <layn>  I noticed that there is a package that helps in finding the bug: bughelper but I can not upload it I followed the guide but does not work with the command sudo apt-get install bughelper not find the package through bzr nor could you help me?
[11:21] <AbhiJit> hi
[11:30] <AbhiJit> hello
[11:30] <AbhiJit> this user is not member of bugsquad and he directly gets the membership of 5 day and he send email that he wants to contribute
[11:30] <AbhiJit> so should i suggest him first to join bugsquad team and look for mentor?
[11:30] <AbhiJit> https://launchpad.net/~sujiths80
[11:32] <Gigacore> AbhiJit: hey, they assigned a mentor to me :)
[11:32] <AbhiJit> Gigacore, glady to know! who is he?
[11:32] <Gigacore> AbhiJit: nigelb
[11:32] <AbhiJit> Gigacore, nice!!! :)
[11:33] <Gigacore> :)
[11:34] <Gigacore> AbhiJit: and it was assigned by vish
[11:35] <layn> giacore:I noticed that there is a package that helps in finding the bug: bughelper but I can not upload it I followed the guide but does not work with the command sudo apt-get install bughelper not find the package through bzr nor could you help me?
[11:36] <vish> layn: are you in lucid or maverick?
[11:36] <layn> maverick
[11:37] <vish> !info bughelper
[11:37] <ubot2> vish: Package bughelper does not exist in lucid
[11:37] <vish> layn: its not there since lucid..
[11:37] <vish> layn: the package was last uploaded in karmic : https://launchpad.net/bughelper
[11:37] <Gigacore> try finding it on get-deb?
[11:38] <vish> layn: you can get the deb and install, but not sure how far it works in lucid..
[11:38]  * vish never used it..
[11:38] <layn> i have maverick vish
[11:38] <vish> maverick is the smae..
[11:39] <Gigacore> layn: http://ftp.kaist.ac.kr/ubuntu/pool/universe/b/bughelper/
[11:39] <vish> same..
[11:39] <layn> ok try the search with deb you get to know fasccio
[11:39] <Gigacore> am not sure about whether it works or not
[11:39] <AbhiJit> i was disconnected!
[11:39] <layn> wow
[11:39] <AbhiJit> :o
[11:40] <AbhiJit> wow?
[11:40] <vish> AbhiJit: holly pappadums! ;p
[11:40] <AbhiJit> :o
[11:40] <layn> Giacore:because I feel you are a grange
[11:40] <AbhiJit> vish, you lost your joke. i dont know what is 'pappadums! ?
[11:40] <AbhiJit> :(
[11:41] <Gigacore> hey vish, thanks for approving me to bugsquad-mentorship
[11:41] <vish> Gigacore: np.. thanks for helping out :)
[11:41] <Gigacore> :)
[11:41] <Gigacore> layn: grange? btw.. it is Gigacore, not Giacore ;)
[11:42] <vish> AbhiJit: google is your friend too! ;p
[11:42] <layn> thanks guys for accepting me as well as the team try always to do my best
[11:42] <AbhiJit> hello layn
[11:42] <layn> Abhijit: hello
[11:43] <AbhiJit> oh
[11:43] <AbhiJit> its 'papad' i know it. its my favorite. 'udid daal' papad are my favorite!
[11:43] <AbhiJit> :)
[11:43] <AbhiJit> vish, ^^
[11:43] <AbhiJit> layn, :)
[11:44] <Gigacore> I like papad too
[11:44]  * AbhiJit mouth watering! Now going to get luch with papad!!! :)
[11:44] <AbhiJit> :P
[11:44] <layn> often my job keeps me busy but as soon as I put myself at work
[11:45] <Gigacore> only 10 brain cells?
[11:48] <layn> Giacore:The dependence can not be met: python-bughelper
[11:49]  * vish hands layn a "g" … its Gigacore  ;p
[11:49] <Gigacore> lol
[11:49] <Gigacore> layn: then you must first install python-bughelper
[11:49] <Gigacore> you can find that package in the same page
[11:49] <Gigacore> same dir
[11:49] <Gigacore> http://ftp.kaist.ac.kr/ubuntu/pool/universe/b/bughelper/
[11:50] <Gigacore> install the corresponding version
[11:50] <layn> yes ok Gigacore sorry
[11:50] <vish> layn: if you are using xchat for irc, you can tab complete most nick names..
[11:50] <vish> most of the irc clients allow that..
[11:52] <vish> layn: its not a major issue, but many folks look at irc *only* when their name get highlighted … you might be wondering why you dint get a response if wrong name is used.
[11:53] <layn> :)
[11:53]  * AbhiJit watches Malgudy Days while having lunch!!! :P
[11:54] <vish> AbhiJit: its not lunch at 4:30 pm!  in some places its dinner!
[11:55] <layn> not to miss a bit but I have eyes everywhere here on my terminal did not want to be a lack of respect but I also check the db
[12:01] <AbhiJit> vish, :D
[12:03] <layn> bughelper exists only to control the bug?
[12:05] <layn> is there a way to take control of bugs without access to the development platform?
[12:07] <layn> vish:I can not upload it bughelper maverick in python-bughelper
[12:08] <Gigacore> whoa!! look at packages available! - http://ftp.kaist.ac.kr/ubuntu/pool/universe/b/
[12:08] <vish> layn: i have never used bughelper, so not sure what it does.
[12:08] <vish> layn: what are you using it for?
[12:11] <layn> vish:looking for a way to have the bug under control
[12:11] <layn> vish:perhaps to look for any duplicate
[12:12] <vish> layn: you can do it using the browser itself, well thats how i do it..   bdmurray might know more about bughelper
[12:20] <layn> vish:Can you tell me how to identify bugs through the browser?
[12:21] <vish> layn: i'm confused, identify which bug[s]?
[12:22] <layn> you check for duplicates
[12:22] <Gigacore> hmm
[12:22] <vish> layn: while reporting or while triaging?
[12:23] <layn> while reporting
[12:23] <vish> layn: lp already does that for us  :)
[12:24] <nigelb> Gigacore: hi
[12:24] <Gigacore> hey nigelb
[12:24] <vish> layn: when you are filing a new bug, it will show a list of probably dups
[12:25] <layn> ok
[12:25] <nigelb> Gigacore: at work now, perhaps we can chat some time in the evening
[12:25] <Gigacore> nigelb: yea sure
[12:26] <layn> In short we must just do the triaging bugs
[12:32] <layn> vish:In short we must just do the triaging bugs
[12:32] <layn> ?
[12:33] <vish> layn: yeah, bugsquad is mostly to do trigaing and help others, but bugreporting anyone can do.
[12:34] <layn> vish:ah well
[12:39] <layn> vish:In short I am trying to understand the unction reading the guide and asking, in fact I had seen when you first get a report assessing the bug if it is otherwise actually asked a question to assess if it is not is reported as invalid. Otherwise it is reported as a duplicate if it is appropriate. In case of missing information is requested instead pij incomplete information or otherwise reported as confirmed and tr
[12:39] <layn> iaged
[12:41] <layn> vish:sorry but saw that I was accepted into bugsquod trying to be helpful I do not like to stand with folded hands and then try to understand I am very curious
[12:41]  * vish confused and reads again.. :)
[12:41] <layn> vish:ok
[12:43] <layn> vish:by vish then tell me what to do and where I see the bug
[12:43] <vish> layn: from what i understand.. it looks like you want to help with bug triaging for other's bugs and have a few doubts regarding the wiki?
[12:43] <Gigacore> layn: did you apply for mentorship program?
[14:07] <AbhiJit> h
[14:09] <njin> pedro_: hello, lost favourites launcher (UNR) during upgrade to MM bug 654969 thanks
[14:09] <ubot2> Launchpad bug 654969 in ubuntu "unr favorites lost on upgrade to maverick (affects: 1) (heat: 6)" [Undecided,New] https://launchpad.net/bugs/654969
[14:10] <pedro_> hello njin :-)
[14:10] <pedro_> njin, i've no idea about UNR sorry
[14:10] <pedro_> njin, feel free to ask on #ubuntu-desktop though
[14:10] <BUGabundo> guud afternuun peeps
[14:10] <pedro_> hi BUGabundo AbhiJit
[14:11] <AbhiJit> hello pedro_ :)
[14:11] <BUGabundo> hey pedro_
[14:17] <bcurtiswx_> mornin' BUGabundo
[14:18] <njin> pedro_: hello again, sorry connection problems, have you read my precedent post ?
[14:19] <pedro_> njin, yup
[14:19] <pedro_>  njin, i've no idea about UNR sorry
[14:19] <pedro_>  njin, feel free to ask on #ubuntu-desktop though
[14:19] <pedro_> njin, ^
[14:19] <njin> ok thanks pedro_
[14:19] <pedro_> you're welcome
[14:37] <vish> kamusin: hey, is there a bug regarding the gwibber icon?  omer was mentioned that the icon was cut.. and needs fixing..  or can you ask him to poke me when he is around?
[14:37]  * vish has a fixed version..
[14:37] <AbhiJit> i can
[14:37] <AbhiJit> vish, shoud i?
[14:38] <vish> AbhiJit: sure anyone can.. ;)  i asked kamusin since he might know about gwibber
[14:38] <AbhiJit> vish, yah o told omer to cme
[14:39] <kamusin> hold me a minute please
[14:40] <vish> aaaaaaaaand we have om26er !!! :D
[14:40] <AbhiJit> a big aplause!!!
[14:40] <vish> AbhiJit: that was quick!! thx :)
[14:40] <AbhiJit> vish, :)
[14:40] <om26er> ;)
[14:40] <om26er> hi vish
[14:41] <vish> om26er: hey, just noticed i have yet installed dropbox on maverick … :s
[14:41] <vish> om26er: is there a bug?
[14:42]  * om26er is lost
[14:42] <vish> om26er:  <vish> kamusin: hey, is there a bug regarding the gwibber icon?  omer was mentioned that the icon was cut.. and needs fixing..  or can you ask him to poke me when he is around?
[14:42] <vish> s/was//
[14:44]  * kamusin kamusin is still fighting with facebook authentication :(
[14:45] <kamusin> vish, do you mean bug 544959 ?
[14:45] <ubot2> Launchpad bug 544959 in gwibber (Ubuntu) (and 1 other project) "new gwibber icon (proposed) (affects: 5) (heat: 33)" [Wishlist,Triaged] https://launchpad.net/bugs/544959
[14:45] <om26er> ok got disconnected. I was out of the range of my wifi
[14:45] <vish> kamusin: not that.. om26er dropped by on -artwork asking about the icon being cut..
[14:46] <kamusin> om26er is the guilty then :)
[14:46] <om26er> vish, you there?
[14:46] <vish>  <om26er> would anyone be interested in fixing gwibber's icon the right side is a little broken http://imagebin.org/index.php?mode=image&id=116579
[14:46] <vish> kamusin: ^
[14:46] <vish> om26er: yup..
[14:50]  * vish pins om26er to the channel ! ;p
[14:51]  * AbhiJit has favicol!
[14:51] <AbhiJit> tootegaa nahi!
[14:51] <vish> haha!
[14:51] <om26er> vish, now things should be stable ;)
[14:51] <om26er> AbhiJit, lol
[14:51] <AbhiJit> :D
[15:06] <om26er> vish, It seems I was not chatting with AbhiJit and I just got the message from a friend to come to irc (and nothing else)
[15:07]  * om26er went through irc logs :O
[15:07] <AbhiJit> :/
[15:08] <om26er> vish, there is no bug for the broken part of gwibber icon. should I report and assign it to you?
[15:08] <vish> om26er: ah! so we are just telepathically connected! ;)
[15:08] <vish> om26er: sure..
[15:14] <kamusin> I cant found nothing about that issue too vish
[15:15] <kamusin> cant/can't
[15:17] <om26er> thanks vish done :)
[15:17] <om26er> bug 655159
[15:17] <ubot2> Launchpad bug 655159 in gwibber (Ubuntu) (and 1 other project) "gwibber icon is broken on the right side (affects: 1) (heat: 6)" [Low,Triaged] https://launchpad.net/bugs/655159
[15:18] <om26er> vish, you should assign yourself on the upstream bug (I cant)
[15:19] <algnod> om26er, hi i am new to triaging and i am just wondering what is going on with bug 654587 and what the null project is. I have a different bug with someone having problems opening folders from the places menu.
[15:19] <ubot2> Launchpad bug 654587 in nautilus (Ubuntu) (and 1 other project) "nautilus not launching when clicking Home Documents etc in Places (affects: 1) (heat: 6)" [Undecided,New] https://launchpad.net/bugs/654587
[15:21] <om26er> algnod, this bug is not a problem in launchpad. so whenever any comment on this bug was made people on the launchpad will get an email so I changed it to null project so that they dont get email. though I think I should have changed it to nautilus upstream
[15:22] <om26er> kamusin, hi
[15:22] <kamusin> hey om26er!
[15:23] <algnod> om26er, thanks
[15:24] <om26er> algnod, :)
[15:24] <om26er> kamusin, do you want any help on rhythmbox bugs?
[15:25] <kamusin> om26er, I have seen you working on it :), please if you have some free time
[15:25] <om26er> kamusin, I recently subscribed to a few new packages and rhtyhmbox was one of those ;)
[15:26]  * kamusin hugs om26er super!
[15:27]  * om26er hugs kamusin back
[15:27] <om26er> could anyone familiar with evolution bugs mentor me?
[15:30] <charlie-tca> KernelBugDay today! let's have some fun... https://wiki.ubuntu.com/Kernel/BugDay
[15:31] <pedro_> om26er, what's your question?
[15:32] <pedro_> charlie-tca, hggdh i was thinking on not organizing a bug day for this week and rather concentrate on ISO Testing for the final image, what do you guys think?
[15:32] <pedro_> kamusin ^
[15:33] <hggdh> pedro_: I think it is a good idea, we will probably have our hands full with last-minute checks and tests
[15:34] <hggdh> pedro_: BTW, cleanup almost all done. All that is left is to verify a few BugSquad members, and then the ones that really applied and did not get a response/action
[15:34] <om26er> pedro_, currently there are none but can I ask you about things along the way?
[15:34] <hggdh> (there's about 25 total pending)
[15:34] <pedro_> hggdh, <3 , saw the list this morning and it looks *amazing*
[15:34] <pedro_> thanks a lot for doing that hggdh and devildante :-)
[15:35] <pedro_> om26er, yeah totally, please don't hesitate on doing that
[15:35] <hggdh> pedro_: heh. I cannot really answer 'my pleasure', but hey -- my pleasure ;-)
[15:35] <pedro_> om26er, if i'm not around, hggdh might help you as well and seb128 too
[15:35] <seb128> pedro_, you ought to be always be around
[15:35] <seb128> stop slacking!
[15:35] <seb128> ;-)
[15:36] <pedro_> !
[15:36] <hggdh> pedro_: and, anyway, we the kernel bug day today, as charlie-tca justs posted
[15:36] <pedro_> seb128, thought i was allow to sleep 20 minutes per day!
[15:36] <pedro_> :-(
[15:36] <pedro_> allowed
[15:36] <hggdh> 20minutes?? Why that much?
[15:36] <pedro_> hggdh, yeah indeed
[15:36] <pedro_> !
[15:36] <pedro_> hggdh, ok i guess i can reduce that amount to 15
[15:36]  * hggdh lost track of time today, and woke up at 0900
[15:36] <pedro_> :-P
[15:37] <seb128> pedro_, yes, you are, just slep 50 seconds every hour
[15:37] <seb128> it's an acceptable delay to reply on IRC
[15:37] <seb128> ;-)
[15:37] <hggdh> LOL
[15:38] <hggdh> om26er: ask, and you get an answer
[15:38] <hggdh> probably...
[15:38] <pedro_> lol
[15:38] <pedro_> om26er, btw most of the things on evolution are upstream bugs
[15:39] <charlie-tca> pedro_: I agree on the iso testing instead this week.
[15:39] <pedro_> om26er, the only things that might need to be tracked here are the indicator crashes
[15:39] <pedro_> which are easy to discover
[15:39]  * seb128 hugs pedro_
[15:39] <pedro_> charlie-tca, hggdh thanks for your input
[15:39]  * pedro_ hugs seb128 back
[15:39] <seb128> pedro_,  how are you btw? ;-)
[15:39] <pedro_> seb128, can i borrow one or two of those 128 little kids slaves you have? ;-)
[15:40] <seb128> you wish
[15:40] <seb128> but no, I need them :p
[15:40] <hggdh> oh, seb128 is reduced to just 128 of them?
[15:40] <pedro_> seb128, i'm good ! thanks. excited since the release is coming ;-). what about you?
[15:40] <seb128> I'm fine thanks
[15:41] <seb128> starting working on preparing UDS and next cycle
[15:41] <pedro_> hggdh, is his secret, that's the only way he can manage to do all the Gnome work
[15:41] <seb128> interesting time coming for GNOME
[15:41] <pedro_> hggdh, that's why he's traveling to India/China that often
[15:41] <hggdh> oh, I see :-)
[15:41] <hggdh> seb128: will we go to 3.0 on N?
[15:42] <seb128> hggdh, yes
[15:42] <seb128> it doesn't mean we decided on g-s or gnome-panel and compiz still
[15:43] <seb128> but we will go for packaging GNOME3 anyway
[15:43] <penguin42> hggdh: Bug 648120  you seem to have actually released a fix for - is there a reason it isn't marked as such?
[15:43] <ubot2> Launchpad bug 648120 in squid (Ubuntu) "Squid doesn't start at boot (affects: 1) (heat: 437)" [Medium,Confirmed] https://launchpad.net/bugs/648120
[15:43] <seb128> what we make use of in the default session is an UDS topic
[15:43] <kamusin> where is the site of kernel bugday? I can't find it :(
[15:43] <hggdh> seb128: hum. There is going to be a need for a *LOT* of testing
[15:44] <hggdh> penguin42: looking
[15:44] <seb128> hggdh, yes
[15:44] <pedro_> kamusin, you mean the page with bugs?
[15:44] <Gigacore> guys, am having a look at bug 655163. As explained by the bug reporter, I tested according his procedure and it appears to work fine. It doesn't look like a bug. What to do? Shall I mark it as invalid?
[15:44] <ubot2> Launchpad bug 655163 in parole (Ubuntu) "Pause/Play button broken (affects: 1) (heat: 6)" [Undecided,New] https://launchpad.net/bugs/655163
[15:44]  * penguin42 wonders what % of bug fixes are single character
[15:44] <Gigacore> btw, am a newvie
[15:44] <Gigacore> newbie*
[15:45] <hggdh> penguin42: yes, but we would need the release team approving now -- which is almost impossible --, so I guess this will end up being a 0-day
[15:45] <charlie-tca> Gigacore: is your hardware the same as the report?
[15:45] <penguin42> hggdh: It seems to be installed on my machine; are you sure it didn't escape?
[15:45] <Gigacore> charlie-tca: oh oops.. nope
[15:45] <kamusin> yep, the list with bugs that will be triaged today
[15:45] <hggdh> penguin42: oh. Just a sec
[15:46] <charlie-tca> Then you need to ask for more information; what hardware; listing from lspci
[15:46] <hggdh> penguin42: your version ends with 2ubuntu5?
[15:46] <penguin42> hggdh: Yep
[15:47] <hggdh> penguin42: yes, then it is realeased. I am marking as such now
[15:47] <penguin42> hggdh: Oh, and thanks :-)
[15:47] <charlie-tca> Gigacore: oh, I didn't read the bug first. You tested in 10.10?
[15:47] <hggdh> penguin42: I forgot -- LP is not auto-marking the fix released bugs, so we have to do it manually
[15:47] <Gigacore> charlie-tca: yup
[15:48] <pedro_> kamusin, they didn't created one, but JFo pointed to https://wiki.ubuntu.com/Kernel/BugDay which contains a list of tasks
[15:48] <charlie-tca> That is your comment on the bug, about it working?
[15:49] <Gigacore> yup
[15:49] <Gigacore> it works fine
[15:49] <hggdh> penguin42: you are welcome. We do appreciate the help
[15:49] <penguin42> what command line tools are there - e..g anything to open bug n in a browser?
[15:49] <kamusin> I see, thanks any way
[15:49] <charlie-tca> Change the status to incomplete, by clicking on the little pencil next to "New"
[15:49] <charlie-tca> Gigacore: then we wait for the reporter to comment back
[15:49] <Gigacore> charlie-tca: ok
[15:50] <JFo> yeah, I broke the script wich would normally give us that
[15:50] <JFo> working on it now
[15:53] <kamusin> excelent!
[15:53] <charlie-tca> Gigacore: thanks for helping
[15:53] <Gigacore> charlie-tca: anytime :)
[16:12] <xeroadmin> Ubuntu is giving me major grief
[16:12] <xeroadmin> every other boot, the sound goes out, and it will not shut down, and it refuses to mount external media
[16:13] <xeroadmin> but, when all of those are working, QEMU will not work properly...
[16:14] <penguin42> xeroadmin: Gnome or KDE ?
[16:14] <xeroadmin> gnome
[16:14] <penguin42> xeroadmin: Lucid or Maveric?
[16:14] <xeroadmin> Lucid
[16:14] <penguin42> ok, what happens with external media?
[16:15] <xeroadmin> I try to mount it, and it gives me a permission denied error.
[16:15] <xeroadmin> and with sound, it won't pick up any hardware at all
[16:15] <penguin42> xeroadmin: How are you mounting it and what's the media; one problem at a time
[16:16] <xeroadmin> it is a Kingston 1GB Datatraveler
[16:16] <xeroadmin> and I have it set to automount.
[16:17] <penguin42> Hmm I have a few Kingstons mounting OK; how are you setting it to automount?
[16:17] <xeroadmin> It has gotten worse over the past few days, this problem used to be resolved by mounting manually, but now, that has gone kaput as well.
[16:17] <xeroadmin> and as for automount, i put the datatraveler in the machine, and get a popup, giving me the permission denied error
[16:18] <xeroadmin> and the same message when I access the drive
[16:19] <penguin42> xeroadmin: Does it come up as sdb or the like?
[16:20] <penguin42> xeroadmin: Can you put the output of udisks --enumerate-device-files into a pastebin?
[16:20] <penguin42> (with the thumb drive plugged in)
[16:20] <xeroadmin> one second
[16:21] <penguin42> anyone know German?
[16:22] <xeroadmin> http://pastebin.com/MRALthg7
[16:23] <xeroadmin> and as for the error: "unable to mount kingston. not authorized."
[16:24] <penguin42> xeroadmin: OK, well the good thing is that udisks shows it and it's partition
[16:24] <xeroadmin> it just isn't mounting. and I know it is not a corrupt fs, because it mounts on windows and mac
[16:24] <cprofitt> https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/654063
[16:24] <ubot2> Launchpad bug 654063 in compiz (Ubuntu) "gconf-editor does not have expo listed as plugin (affects: 1) (heat: 6)" [Undecided,New]
[16:24] <cprofitt> should be an easy one to fix.
[16:24] <penguin42> xeroadmin: what does 'id' say?
[16:25] <cprofitt> I have confirmed this (myself) with a fresh install and an upgrade on two different machines
[16:25] <xeroadmin> terminal?
[16:26] <penguin42> xeroadmin: Yeh, just id in a terminal
[16:26] <xeroadmin> uid=1000(venos) gid=1000(venos) groups=4(adm),20(dialout),24(cdrom),46(plugdev),105(lpadmin),119(admin),122(sambashare),1000(venos)
[16:27] <penguin42> hmm about the same as me
[16:27] <penguin42> xeroadmin: OK, try udisks --mount /dev/disk/by-uuid/E0FD-1813
[16:27] <penguin42> (I think that's a 0 not an O
[16:28] <xeroadmin> Mount failed: Not Authorized
[16:28] <penguin42> hmmmm
[16:28] <penguin42> xeroadmin: Do you login the normal way, via gdm?
[16:29] <xeroadmin> It is set to log me in when I first boot up
[16:31] <penguin42> xeroadmin: OK, go to system->administration->users & groups
[16:31] <penguin42> xeroadmin: Select your user and click advanced settings
[16:32] <xeroadmin> is it normal that nothing pops up?
[16:32] <penguin42> xeroadmin: Then select the 'User Privileges' tab and tell me whether the 'Access external storage devices automatically' is ticked?
[16:32] <penguin42> erm no!
[16:32] <penguin42> xeroadmin: At which stage didn't it pop up?
[16:32] <xeroadmin> yet another problem...
[16:33] <penguin42> xeroadmin: They may all be related, did you do anything odd to your user account?
[16:33] <penguin42> xeroadmin: Did the Users & Groups box not appear at all?
[16:33] <xeroadmin> aside from putting some nice new colours on the theme, not really
[16:33] <penguin42> new colours? ???
[16:34] <xeroadmin> system -> preferences -> appearance
[16:34] <xeroadmin> shouldn't have anything to do with it, I wouldn't have thaught
[16:34] <penguin42> xeroadmin: And what happens if you run users-admin from the command line does anything appear?
[16:35] <xeroadmin> another users settings window
[16:35] <penguin42> (Anyone who understands polkit please shout now!)
[16:35] <penguin42> xeroadmin: OK, so you have users settings, is it the 'advanced settings' when nothing comes up?
[16:35] <xeroadmin> yes
[16:35] <penguin42> ah ok
[16:36] <penguin42> xeroadmin: What does ps -eaf|grep polk   give?
[16:36] <xeroadmin> I've had an idea. I tried to look for a trust sound card driver when I first installed, and, not being able to find one, started to read a book on rolling my own driver. Would that maybe have anything to do with it?
[16:37] <penguin42> xeroadmin: Reading the book wouldn't have broken anything - what you did with that knowledge.....
[16:37] <xeroadmin> I tried to rebuild a kernel...
[16:37] <xeroadmin> and never got past the config stage
[16:37] <xeroadmin> I have to go, I will be back on in about half an hour
[16:37] <penguin42> no, if you didn't get past trying to configure it it shouldn't have broken anything
[16:37] <penguin42> xeroadmin: OK, I think your problem is something to do with policykit
[16:53] <xeroadmin> ok i'm back. sorry, had to eat. anyway, policykit
[16:55] <xeroadmin> aha! http://ubuntuforums.org/archive/index.php/t-1536632.html
[17:00] <xeroadmin> I'm going to reboot. If I am not on here again, it has worked
[17:00] <cprofitt> can I confirm a bug that I reported?
[17:01] <penguin42> cprofitt: Has someone else said they've got it?
[17:02] <cprofitt> No. No one else has said they have it -- though that is not always necessary for confirmation IMHO
[17:02] <cprofitt> I have verified it on two different computers and with both the upgrade and fresh install
[17:02] <penguin42> what's the bug?
[17:03] <cprofitt> it is not hardware related, but the lack of files being created
[17:03] <cprofitt> https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/654063
[17:03] <ubot2> Launchpad bug 654063 in compiz (Ubuntu) "gconf-editor does not have expo listed as plugin (affects: 1) (heat: 6)" [Undecided,New]
[17:03] <cprofitt> I had previously marked it traiged but was told I can not do that on bugs I report...
[17:03] <cprofitt> so I wanted to confirm
[17:03]  * penguin42 doesn't use compiz, but maybe it's just easier to find someone who has and they can confirm it
[17:04] <cprofitt> with hardware bugs there would be a need for verification, but on something like this it would not be hardware dependant
[17:04] <cprofitt> you could still open gconf-editor
[17:04] <cprofitt> and see if the nodes are there
[17:05] <penguin42> yeh but I'm not too sure what I'm looking at in that
[17:05] <cprofitt> and verify if the files are there -- i believe they are there on a default install
[17:05] <charlie-tca> The reasoning behind someone else confirming and triaging your own bugs is to eliminate any possible hardware or software glitch on your own computers.
[17:05] <cprofitt> charlie-tca: I understand that... I do not believe that applies in this case
[17:05] <cprofitt> http://ubuntuforums.org/showpost.php?p=9919859&postcount=1
[17:05] <cprofitt> that is an image of what you would be looking at
[17:06] <cprofitt> the expo, and other, nodes are missing
[17:06] <cprofitt> due to files being missing
[17:10] <penguin42> cprofitt: So is it actually the compiz-fusion-plugins-main package ?
[17:11] <cprofitt> penguin42: I am not sure what installs the schemas
[17:11] <cprofitt> but the schemas are for gconf-editor
[17:11] <cprofitt> they are xml files
[17:11] <penguin42> cprofitt: Well, compiz-plugins has a load of /us/s/gconf/schemas but compiz-fusion-plugins-main doesn't
[17:12] <cprofitt> I would imagine it is in one of the compiz packages and its putting the schemas in and applying them
[17:12] <cprofitt> main would be my guess -- as I do not use 'extra'
[17:12] <penguin42> cprofitt: I'm just thinking each package with plugins in should have the gconf for its plugins
[17:13] <cprofitt> but I have always turned features on by using gconf-editor vs. ccsm
[17:13] <cprofitt> that would be my guess as well penguin42
[17:13] <penguin42> cprofitt: Thing is there is a /usr/share/compiz/expo.xml so I'm not sure how they are supposed to wire up
[17:14] <cprofitt> penguin42: Yeah -- I do not know the fix either... just the problem
[17:14] <cprofitt> the only place I found missing stuff is in the gconf-editor schemas
[17:17] <penguin42> yeuch that bug xeroadmin pointed to was nasty
[17:30] <leighman> hey guys, how can I add an upstream project for a package?
[17:32] <micahg> leighman: also affects project
[17:36] <leighman> ah okay, that did work
[17:36] <leighman> thanks
[18:06] <devildante> pedro_: ping
[18:06] <pedro_> hello devildante
[18:07] <devildante> pedro_: did you sort out that bugcontrol application stuff?
[18:08] <pedro_> devildante, yeah we did, thanks a lot for helping :-)
[18:08] <pedro_> devildante, the list of proposed members now is pretty tidy
[18:08] <devildante> np :)
[18:08] <pedro_> devildante, now it's just a matter of review those and answer to the candidates ;-)
[18:09] <devildante> yeah...
[18:15]  * hggdh goes back to it
[18:28] <hggdh> pfui! pedro_, devildante: done. We are left with just 9 pending applications
[18:28] <devildante> yah
[18:37] <hggdh> pedro_: I also reordered the instructions on the Wiki so that emailing application comes first
[18:38] <hggdh> THEN requesting membership
[18:38] <hggdh> Of course, this will only work if people really bother to read the blurb...
[18:39] <devildante> I'd really like an email to be sent when someone wants to apply
[18:39] <devildante> stating you need to send an application
[18:39] <devildante> is that possible?
[18:40] <cprofitt> proposed bug-control candidates?
[18:40] <hggdh> cprofitt: yes
[18:40] <cprofitt> Cool.
[18:41] <mortal> hello, why are the xorg packages pinned on maverick i386?
[18:41] <mortal> my synaptics touchpad works poorly because of that
[18:41] <cprofitt> hggdh: when is the next global bug jam planned for?
[18:41] <hggdh> devildante: there is no automatic way, but the the LP page for -control *DOES* clearly state it is needed.
[18:41] <hggdh> cprofitt: I am not sure, but I would expect the folks at #ubuntu-community-team to know
[18:42] <cprofitt> cool... I will ask there
[18:42] <devildante> hggdh: I know, it's just that people don't pay attention to a blurb, but they could pay more attention to an automatic e-mail
[18:42] <cprofitt> I seem to always get that information late
[18:42] <hggdh> devildante: and... if one cannot be bothered to read the blurb, I personally cannot be bothered to send an email
[18:42] <devildante> hggdh: that's why it should be automated :p
[18:43] <hggdh> devildante: actually this is my reason for why it should NOT be automated. If one cannot read the blurb, why would this same one fully read a bug description and comments?
[18:43] <devildante> good point
[18:44] <hggdh> (of course, I am old and cynical)
[18:44] <devildante> but I've seen some e-mails about some guys who didn't know that they must have experience before applying for bugcontrol, and sent messages like "how can I contribute?"
[18:48] <cprofitt> devildante: well that is where the BT will hopefullly fill a role
[18:48] <devildante> BT?
[18:49] <cprofitt> when we get folks like that we can push them to the BT and the BT can help them learn to contribute
[18:49] <cprofitt> BeginnersTeam
[18:49] <devildante> ah
[18:49] <cprofitt> https://wiki.ubuntu.com/BeginnersTeam
[18:49] <devildante> yeah, I know them :)
[18:49] <cprofitt> we are in the middle of a re-org but that is the goal I hope we emerge with
[18:49] <cprofitt> taking users who want to move beyond just using Ubuntu
[18:50] <devildante> great :)
[18:50] <cprofitt> yeah
[18:54] <hggdh> devildante: BTW, if you think JamesPage's application is good, please reply on the ML with your view -- we need another vote for him
[19:33] <flipefr> hello everyone
[19:34] <flipefr> i am looking for someone of bug control team
[19:34] <flipefr> to change an importance setting in a bug
[19:35] <pedro_> flipefr, just paste the bug number in the channel and explain why the importance should be changed
[19:35] <flipefr> 655085
[19:36] <flipefr> the user claims about aptitude is not installed by default in maverick
[19:36] <flipefr> i answer with a stadrad response telling him that aptitude is not included in this release
[19:36] <flipefr> i think the importance should be wishlist
[19:36] <cprofitt> aptitude is not installed?
[19:37] <cprofitt> just apt-get heh?
[19:37] <flipefr> no
[19:37] <cprofitt> wow...
[19:37] <flipefr> only
[19:37] <cprofitt> I missed that change... I mostly use apt-get
[19:37] <flipefr> it was a decision made a few moths ago
[19:38] <hggdh> bug 655085
[19:38] <ubot2> Launchpad bug 655085 in aptitude (Ubuntu) "aptitude not installed by default (affects: 1) (heat: 6)" [Undecided,Opinion] https://launchpad.net/bugs/655085
[19:38] <flipefr> that is
[19:38]  * penguin42 always did prefer apt-get :-)
[19:39] <flipefr> and me xd
[19:39] <flipefr> i think is ore secure
[19:39] <flipefr> more secure
[19:39] <penguin42> not sure about that, but I never did manage to get it to resolve dependencies sanely?
[19:39] <hggdh> flipefr: two things there -- I am not sure this is an opinion, and (2) only assign yourself (or anybody else) to a bug if you are working on FIXING it ;-)
[19:40] <devildante> the real reason for doing this is that the upgrade tools have apt-get in mind
[19:40] <flipefr> no, it was a mistake
[19:40] <hggdh> flipefr: subscribing to the bug will get you all needed updates
[19:40] <flipefr> this is my second bug
[19:40] <kklimonda> oh, so we are using the Opinion status after all?
[19:40] <flipefr> changed
[19:40] <flipefr> i expect so
[19:40] <hggdh> flipefr: I am not complaining :-)
[19:40] <flipefr> i can changed it to confirmed
[19:40] <hggdh> just trying to help you
[19:41] <hggdh> flipefr: yes, you can
[19:41] <hggdh> kklimonda: the usage is still iffy -- some do, and some others get unhappy with it
[19:42] <flipefr> so then do i put in confirmed status or opinion
[19:42] <flipefr> i think is like an opinion
[19:42] <flipefr> ??
[19:42] <kklimonda> hggdh: yeah, I do remember the discussion after it has been introduced.
[19:42] <hggdh> flipefr: not really. The OP is discussing about aptitude not being in, and giving a reason why it should be in
[19:43]  * micahg thinks opinion should be like Won't Fix in terms of who can set it
[19:43] <micahg> deryck: ^^
[19:43] <hggdh> flipefr: it could go to confirmed or wontFix
[19:43] <kklimonda> I'd go with Won't Fix
[19:43] <hggdh> micahg: I agree
[19:43] <flipefr> i will changed to wont fix then better tha confirmed
[19:43] <kklimonda> but then people are reading way too much in the "Won't Fix" status
[19:43] <hggdh> flipefr: hold on
[19:44] <deryck> micahg, we're actually reviewing the success and usefulness of opinion status this month.
[19:44] <micahg> aptitude was removed from the default install since apt-get is now pretty fully featured
[19:44] <hggdh> flipefr: first of all, you have to be sure that aptitude was removed from standard install, and what was the reason
[19:44] <micahg> deryck: cool
[19:44] <micahg> deryck: and I saw you working on the ACL for Fix Released :)
[19:44] <flipefr> the reason was a decision form high spheres
[19:45] <flipefr> like put buttons in the left side of the window
[19:45] <hggdh> flipefr: yes. A link to the published decision would be nice
[19:45] <deryck> micahg, indeed :-)
[19:45] <njin> hello to all, in a case like this  is apport that wrong on python ? apport[5800]: segfault at 10020 ip<PHONE_NUMBER>4542f3 sp 00007fffd9a4d670 error 4 in python2.6[400000+21a000]
[19:45] <hggdh> micahg: ^ you have it?
[19:45]  * micahg looks
[19:45] <kklimonda> hggdh: it got removed from the ubuntu-standard to save some space.
[19:46] <vish> deryck‣ also, can we block triaged » confirmed?  allowing only BC to change that?
[19:46] <micahg> hggdh: it's worth a release note mention IMHO
[19:46] <hggdh> yeah
[19:47] <flipefr> hey one moment  i cant see the option wont fix in the combo
[19:47] <deryck> vish, I don't think we should block confirmed.  It's used commonly by any user, right?  This is the suggested ubuntu bug workflow, no?
[19:47] <micahg> deryck: no
[19:47] <vish> deryck‣ some users [non-bug triagers] think that confirmed is a higher status than triaged
[19:47] <kklimonda> flipefr: access to the won't fix status is limited to the bugcontrol.
[19:48] <flipefr> ok
[19:48] <vish> they just see an old bug set as triaged and think"doh! why isnt this confirmed yet!"
[19:48] <flipefr> kklimonda:could you change the status and importance of the bug please?
[19:48] <deryck> vish, micahg -- ah, so what you guys mean is that triaged should be acl'ed so only bug supervisor can change out of it.
[19:49] <micahg> deryck: yep
[19:49] <kklimonda> if hggdh agress on that then I see no reason not to do that :)
[19:49] <vish> yup
[19:49] <cprofitt> vish - I thought only BC could do that...
[19:49] <micahg> hggdh: I'd say kubuntu-meta should be the package instead of aptitude in that bug as well
[19:49] <micahg> and maybe add a release notes task
[19:50] <cprofitt> release notes is a great idea
[19:50] <vish> cprofitt‣ only BC can set *to* trigaed, but anyone can changed it *from* triaged
[19:50] <deryck> micahg, vish -- I'm ok with that.  bug supervisor can only set triaged anyway.  I thought you already couldn't.
[19:50] <cprofitt> vish: ah -- yeah that should be locked down...
[19:50] <hggdh> deryck: I agree
[19:50] <cprofitt> do not want it going backwards unless BC or dev changes it
[19:50] <kklimonda> micahg: has it been changed in kubuntu-desktop or does kubuntu-desktop depends on ubuntu-standard?
[19:51] <micahg> cprofitt: the only time where it's appropriate is if it's ready for upload
[19:51] <kklimonda> micahg: or rather isn't it done in ubuntu-standard which is a base for all ubuntu derivatives?
[19:51] <vish> deryck: awesome!  so i guess there isnt a bug about that already?  /me files one now..
[19:51] <micahg> kklimonda: good question :)
[19:51] <kklimonda> "changed in kubuntu-meta"
[19:52] <hggdh> and the war apt-get vs aptitude starts again (if it ever stopped)
[19:52] <njin> pedro_: around?
[19:52] <flipefr> hggdh: http://www.webupd8.org/2010/06/aptitude-removed-from-ubuntu-1010.html
[19:53] <cprofitt> gah...
[19:53] <kklimonda> hggdh: it's a never ending one
[19:53] <kklimonda> hggdh: just like vim vs. emacs
[19:53] <hggdh> heh
[19:53] <kklimonda> or linux vs bsd ;)
[19:53] <hggdh> yeah
[19:54] <cprofitt> http://www.comparethemeerkat.com/
[19:54] <hggdh> flipefr: yes, please add this link in (and the referred link)
[19:54] <micahg> kklimonda: not sure if it does or not
[19:54] <cprofitt> the site will at least help as laugh through launch
[19:55] <flipefr> hggdh:https://lists.ubuntu.com/archives/maverick-changes/2010-June/001202.html
[19:56] <hggdh> flipefr: yes
[19:57] <kklimonda> micahg: there is no mention of aptitude in kubuntu-meta but there is one in ubuntu-meta
[19:57] <kklimonda> so I guess ubuntu-meta is the right package for this bug
[19:58] <micahg> kklimonda: k
[19:58] <kklimonda> neither have I seen anything KDE-specific in the bug's description. It's the same problem on Xubuntu and Ubuntu
[19:58] <micahg> kklimonda: I'd suggest resetting to New as well + add a release notes task
[19:59] <flipefr> hggdh: could you change the status to wont fix and importance to wishlist?
[20:00] <flipefr> hddgh: i added the link of changes to the post
[20:00] <flipefr> hggdh: so the user can see it
[20:00] <micahg> flipefr: that's not an explanation
[20:00] <hggdh> flipefr: I think the consensus is to add tasks
[20:01] <flipefr> i also give him a standard response with an explanation in a post before
[20:02] <flipefr> anyway, what do you suggest to do?
[20:03] <micahg> flipefr: again, you gave a decision, not a reason, the metapackage owner or the release notes team should provide a mention and reason for this
[20:03] <micahg> flipefr: reset to New, change to ubuntu-meta, also affect project ubuntu-release-notes
[20:04] <flipefr> i changed it to New
[20:06] <micahg> flipefr: also, what about the other 2 things I suggested
[20:06] <flipefr> sorry
[20:07] <flipefr> micahg: i dont know how to change to ubuntu-meta
[20:07] <flipefr> and what was the other thing
[20:07] <flipefr> i remeber you that this is my second bug
[20:07] <flipefr> and i and not still familiar with launchpad
[20:08] <vish> micahg¦ do you have any examples of triaged » confirmed bugs?
[20:08] <vish> just when we want them we cant find those :/
[20:09] <vish> rather *i*
[20:09] <cprofitt> I gotta run guys... have a good one
[20:09] <vish> or hggdh too^ any examples?
[20:10] <flipefr> uf where is your mentor when you need him?
[20:10] <hggdh> vish: off the top of my head, no. Rusivi did a lot of these, though
[20:11] <vish> hehe, /me checks those
[20:11] <rusivi> hggdh / vish: I got a little trigger happy
[20:11] <flipefr> hggdh: i am going to leave the bug as new and someone changed the importance to wishlist, if i had to change anything more please let me know
[20:15] <vish> rusivi¦ ;)  but its more from triaged » confirmed thats an issue..  your changes are much rarer, as in not seen anyone do that , but the number of bugs might have been high :)
[20:16] <flipefr> i think i am leaving  have a good time here
[20:17] <rusivi> One of a handful of reasons to continue to allow Triaged -> Confirmed/New is the Community believes it's not something the BugSquad should focus on. I am not implying that was my intention. However, your cutting off that communication possibility from the Community if you remove that action.
[20:17] <rusivi> IDK the best way to go, just discussing.
[20:18] <hggdh> rusivi: if it is triaged, it is out of triaging. It is now a problem for the developer/maintainer
[20:18] <vish> rusivi¦  "Community believes" meaning you ? ;)
[20:19] <rusivi> hggdh Agreed. My newish response to that is "dev's got it". I know better then that now. Vish: Not posturing in any sense just discussing.
[20:20] <rusivi> If it is stopped or remains, for myself, so be it, no big deal.
[20:20] <rusivi> :)
[20:21] <hggdh> rusivi: it is similar (with care, of course) to unsetting a FixReleased -- what we usually observe is very old FixReleased being put back into confirmed/new
[20:22] <hggdh> this is wrong -- if the problem reappeared, then it is now (possibly) a regression -- so a new bug is warranted
[20:23] <vish> rusivi¦ similarly , once a bug has been set to triaged , there is nothing further to communicate, the developer just needs to fix it.
[20:24] <hggdh> and -- if the developer/maintainer requires new data, they will put it back to Incomplete
[20:24] <rusivi> vish: Understood. Everyone else in the Community is still welcome to contribute a solution, simultaneously as the developer who took responsibility is working on it.
[20:25] <vish> rusivi¦ why does a solution require a person to change the status?
[20:25] <rusivi> vish: In hindsight, it does not.
[20:25] <vish> :)
[20:26] <vish> maybe to inprogress , but anything else is extra work for others.
[20:27] <hggdh> even inProgress should be used with care -- it signals to everybody else "do not worry with this one, I am taking care of it"
[20:29] <hggdh> TBH, I always considered the the status set as sort of restricted. I would like to have more of them
[20:29] <hggdh> and substatus
[20:31] <hggdh> I see deryck just sent an email to bugsquad -- thank you, sir
[20:32] <penguin42> hggdh: The incomplete's are a bit limiting as well; you can't tell from that whether it's incomplete (and times out) due to where the victim didn't give enough information or where you think it was fixed and just want confirmation
[20:32] <deryck> hggdh, bugsquad shouldn't have gotten email.  For what project?
[20:33] <kklimonda> deryck: I just got 6 mails :/
[20:33] <micahg> deryck: indubuntu
[20:33] <kklimonda> one for bugsquad ;)
[20:33] <hggdh> Ubuntu-bugsquad post from<EMAIL_ADDRESS>requires approval
[20:33] <kklimonda> and other 5 to -backports
[20:34] <hggdh> penguin42: indeed
[20:34] <kklimonda> oh well, they are all identical so I can just what I do the best - delete them ;)
[20:35] <deryck> yes, just delete them.  They shouldn't have come to bugsquad members.
[20:37] <kklimonda> deryck: but if we are already on this topic - is expiration going to be enabled for the Ubuntu project?
[20:37] <hggdh> actually, I think it is good for bugSquad to know about it
[20:37] <hggdh> kklimonda: I would expect this to be discussed at UDS
[20:37] <micahg> hggdh: it was for project owners I think
[20:38] <hggdh> yeah
[20:38] <kklimonda> hggdh: are there any triaging related blueprints registered already?
[20:38]  * kklimonda hasn't seen any
[20:38] <hggdh> kklimonda: I have not had time to get there yet... IDK
[20:39]  * hggdh *has* to do it, though
[20:39] <kklimonda> :)
[20:39] <deryck> yes, buy expiry will be re-enabled.  I'll be sending an email shortly to ubuntu-devel explaining full details.
[20:39] <deryck> and I emailed bug supervisors, when I should have emailed project owners.  I made a mistake about who had power to change settings for bug tracking.
[20:40] <hggdh> deryck: anyway, it was good that bugsquad got it, the triagers should be aware of that change
[20:41] <micahg> hggdh: yes, but the email was for a different project and might confuse people
[20:41] <deryck> hggdh, ok, good.  I'm glad that is useful, then.
[20:41] <deryck> and the email doesn't apply for ubuntu.  we're not turning off the setting, since ubuntu devs requested that we re-enable.
[20:41] <hggdh> micahg: even though... down on the email deryck clear it out (yes, I know, people do not read all)
[21:09] <njin> hello, peolple like to see fix released status ibstead of invalid when a bug is fixed by un update
[22:20] <penguin42> can someone give me some advice on confirming a bug - bug 654170
[22:20] <ubot2> Launchpad bug 654170 in xserver-xorg-video-ati (Ubuntu) "screen remains blank after boot / wrong resolution (affects: 1) (heat: 8)" [Undecided,New] https://launchpad.net/bugs/654170
[22:20] <penguin42> he's given the information asked, but I'm not sure if it would be enough for someone to fix
[22:20] <RedSingularity> I have a bug that has been left idle for a few months.  What should i do with it?
[22:21] <penguin42> RedSingularity: Which one?
[22:22] <RedSingularity> bug 522475
[22:22] <ubot2> Launchpad bug 522475 in firefox-3.5 (Ubuntu) "No display images in standart java module (affects: 1) (heat: 13)" [Undecided,Incomplete] https://launchpad.net/bugs/522475
[22:22] <vish> hggdh¦ Bug #323815  \o/
[22:22] <ubot2> Launchpad bug 323815 in jockey (Ubuntu) (and 2 other projects) "Install progress window has no title (affects: 10) (dups: 3) (heat: 33)" [Low,Triaged] https://launchpad.net/bugs/323815
[22:22] <vish> *phew*
[22:24] <penguin42> RedSingularity: It was reported on 9.10 as well, it would be worth the reporter trying a newer version - but it would probably also good to know which Java he was using if it is Java
[22:25] <RedSingularity> penguin42:  What do you recommend doing with it?
[22:27] <penguin42> I'm not sure - I'd ask him if it works on a newer Ubuntu and maybewhat Java is installed *if* it's a java issue
[22:27] <RedSingularity> I dont think he is even watching it anymore though.
[22:30] <RedSingularity> Be back in a minute
[22:32] <devildante> vish: about bug 323815, I *think* GNOME HIG says progress windows shouldn't have a title
[22:32] <ubot2> Launchpad bug 323815 in jockey (Ubuntu) (and 2 other projects) "Install progress window has no title (affects: 10) (dups: 3) (heat: 33)" [Low,Triaged] https://launchpad.net/bugs/323815
[22:33] <vish> devildante¦ i dont recall such a reference... but do let me know if you find it :)
[22:36] <vish> devildante¦ "Progress windows *should* have a title representing..." http://library.gnome.org/devel/hig-book/stable/windows-progress.html.en ;)
[22:38] <devildante> ah... sorry
[22:38] <devildante> but there's something that shouldn't have a title, I wonder what...
[22:38] <vish> devildante¦ np.. i dont know it fully either.. :)
[22:39] <vish> devildante¦ hmm, modal windows?
[22:40] <devildante> maybe...
[22:41] <devildante> vish: what's with the |-like? :p
[22:42] <vish> devildante¦ trying something new, thanks for noticing! ;)
[22:42]  * devildante wonders how to type it :p
[22:42] <vish> devildante¦ i used character map ;)
[22:43]  * vish was playing with it today and was trying different symbols..
[23:03] <penguin42> Is there a page anywhere for known issues on Maverick for particular hardware ?
[23:09] <rusivi> penguin42: you could perform a hardware search from https://bugs.launchpad.net/ubuntu/maverick
[23:09] <rusivi> type in dell, hp, toshiba, acer, etc.
[23:10] <penguin42> rusivi: I really meant somewhere to add hints to people; I mean I know that there are specific issues on 2 of my machines and was wondering if there was a place for them other than just in the bugs - i.e. a knownissues-by-machine
[23:15] <rusivi> penguin42: The right people do view your problems, vendor specific ones or not. The best way to go is work together with those who have knowledge of your problem and have responded to it. Many of the bugs that I have posted to were successfully addressed by others aside from known bugsquad dev's/vendor employees.
[23:19] <rusivi> Some bugs were self-solved, either through education or my own tweaking.
[23:26] <hggdh> penguin42: there are some such pages, usually on the Debugging area
[23:26] <hggdh> like sound/video
[23:27] <hggdh> but I do not know of any structured effort to do so
[23:27] <hggdh> perhaps... it is time to do it...
[23:28] <penguin42> hggdh: Hmm well
[23:30] <hggdh> penguin42: we are working on a somewhat related approach -- to allow users to upload hardware configuration, and comment on it
[23:30] <penguin42> hggdh: Well I'll put together a wiki page with my two on and we can grow it?
[23:31] <hggdh> penguin42: certainly. KnownIssues-type of thing. May I suggest it to be part of the BugSquad pages?
[23:31] <penguin42> hggdh: Sure, I was going to do it as wiki.ubuntu.com/MaverickMeerkat/SystemSpecificIssues, where would you suggest?
[23:32] <penguin42> (and is there a short hand in the wiki for referencing bugs?)
[23:32] <hggdh> penguin42: hold on
[23:33] <hggdh> wiki.ubuntu.com/Bugs/KnownHardwareIssues/10.10
[23:33] <hggdh> penguin42: does it sound good?
[23:34] <penguin42> ok
[23:35] <rusivi> looks awesome hggdh
[23:39] <layn> Good evening to all
[23:40] <hggdh> penguin42: I do not remember if there is a shotcut for linking bugs... I think all we can do is the [[ URL|Name ]] thingy
[23:41]  * penguin42 grrrs at an Internal server error from wiki.ubuntu.com
[23:41] <micahg> hggdh: there's the URL shortner, pad.lv/XXXXXX :)
[23:42] <hggdh> heh
[23:42] <penguin42> hggdh: There you go, those are my pair of known issues (says he realising he hasn't actually kept them sorted)
[23:42]  * micahg wonders who ubuntu-treblig is
[23:43]  * penguin42 licks micahg
[23:43] <hggdh> micahg: see above post :-)
[23:43] <hggdh> all in family, all in family ;-)
[23:43] <micahg> ah
[23:43] <micahg> penguin42: I would think it should still mention Maverick by name is it's under 10.10
[23:44] <penguin42> micahg: OK, will do - any other changes while I edit it ?
[23:44] <micahg> penguin42: idk, just noticed that from my email
[23:44] <penguin42> youch, do you get mailed on every wiki edit?
[23:45] <micahg> penguin42: I'm subscrbed to all bugs wiki pages
[23:47] <hggdh> so am I...
[23:48] <hggdh> penguin42: if you do not mind, any relationship with Martin Gilbert?
[23:48] <hggdh> or, rather, sir Martin Gilbert
[23:48] <penguin42> hggdh: Not that I'm aware of
[23:49] <hggdh> thank you. Just curious
[23:52] <layn> Hi
[23:52] <penguin42> hggdh: In that case, is your first name really C ?
[23:53] <hggdh> :-)
[23:53] <hggdh> no, it is Carlos
[23:53] <penguin42> layn: Hi
[23:53] <hggdh> but nobody in the US can pronounce it without making it sound Spanish
[23:54] <penguin42> so how do we get that page linked from somewhere useful ?
[23:55] <penguin42> bit of a penguin and egg situation; not many machines on there, so not useful yet
[23:57] <hggdh> penguin42: you could link it off https://wiki.ubuntu.com/DebuggingProcedures on the Hardware section
[23:58] <hggdh> penguin42: I also addded a link(er) CategoryBugSquad at the end, so it will be shown when you look at this category


[01:07]  * wgrant wonders why there is a nice SyncSource class implementation that is well tested but isn't actually used by sync-source.py.


[06:38] <artnay> g morning
[06:58] <klepas> moin
[07:05] <artnay> have you guys tried pixel?
[07:10] <klepas> pixel?
[07:12] <artnay> http://www.kanzelsberger.com/pixel/?page_id=12 - not GPL though
[07:13] <klepas> ah,seen it
[07:13] <klepas> i'm happy with gimp
[07:21] <artnay> hey, the wiki thingie... are we getting anywhere?
[07:22] <artnay> has any of you contacted kubuntu/edubuntu/xubuntu artworkers?
[07:23] <artnay> we really should get it going
[07:32] <artnay> klepas: oh, you posted a link.
[07:33] <artnay> oh, now I found it again! http://ubuntuforums.org/showthread.php?t=64390
[07:34] <artnay> I saw that thread before breezy was released but then I sort of lost it. I though it was posted on ubuntu art talk and I wasn't able to find it anymore...
[07:36] <klepas> bbl
[07:36] <artnay> I really like the overall design of it although the buttons could be improved
[07:38] <artnay> what do you think of it?
[08:02] <klepas> i like it a lot
[08:02] <klepas> ought to come as fault with dapper
[08:15] <artnay> tweak it a bit and make it default :)
[03:02] <klepas> anyone awake?
[08:45] <artnay> hey
[08:50] <artnay> has any of you been in contact with k*, ed* or x* artworkers?
[08:51] <artnay> https://wiki.ubuntu.com/ArtTeam lacks functionality. we should be able to see who is involved in what
[08:57] <artnay> ok, we need to split /ArtTeam
[08:58] <artnay> we should move lots of stuff from there to e.g. FAQ
[09:00] <artnay> no, Introduction would be better
[09:06] <artnay> done, now the introduction and contact details have been separated: https://wiki.ubuntu.com/ArtworkTodoProposal
[09:06] <artnay> what next?
[09:07] <artnay> how about adding something like "Ubuntu Metacity" or similiar after a name at contact page?
[09:08] <artnay> just by telling how you'd like to help could help us organizing here
[09:09] <artnay> guys? :D
[09:26] <artnay> ok, should we just c&p the licensing section to a separate page from /EdubuntuArtwork
[09:28] <artnay> I've been asking about the branding guide that canonical was supposed to provide but I haven't received any replies
[09:28] <artnay> so I guess CC SA 2.5 is ok
[09:55] <artnay> I contacted xi0nblue and invited him here
[10:06] <lukacu> hello artnay :)
[10:14] <artnay> hi lukacu
[10:15] <lukacu> whats up?
[10:15] <artnay> nothing special, been busy the last few three or four days
[10:15] <artnay> you?
[10:16] <lukacu> also busy :) ... school and that
[10:16] <artnay> 47 windows open in irssi, too much... :D
[10:16] <lukacu> lol
[10:17] <lukacu> anything new with the wiki?
[10:17] <artnay> I just updated it
[10:18] <lukacu> yeah ... ive noticed a major change :)
[10:18] <artnay> now we just need an IRC meeting so we can build the structure of /*buntuArtwork pages
[10:19] <lukacu> optimist ;)
[10:19] <artnay> that's the top priority. after that we can place our stuff into right categories and start doing some serious job
[10:19] <artnay> it's 08:19 in sidney already, where's klepas? :)
[10:20] <artnay> s/typos/moretypos/g
[10:22] <artnay> lukacu: do you have any ideas how /*buntuArtwork pages should be built?
[10:23] <lukacu> well ... i do not have a clear picture but only some ideas
[10:25] <lukacu> i will try to gather them, build a txt file and publish it somewhere
[10:25] <artnay> great
[10:28] <lukacu> i think that the idea about writing your interests next to your name on the artteam page is very good
[10:31] <artnay> it would help in this situation. would be easier to get into contact with kubu, edu and xubu ppl
[10:32] <lukacu> indeed
[10:33] <artnay> it doesn't mean you're locked into a project once you write it down there :)
[10:34] <artnay> are you guys members of ubuntuforums?
[10:36] <lukacu> a am a zero-post member :)
[10:37] <lukacu> a registered lurker ;)
[10:42] <artnay> hehe :)
[10:42] <artnay> oh, nice.
[10:43] <artnay> I was just testing some new komposite tweaks as X.org crashed. I disabled composite extension and logged in, started firefox and it opened all the tabs (sessionsaver) and it even remember the long text I was writing to forums when X crashed :o
[10:44] <artnay> if only I had similiar session management on my windows PC (at work)
[10:54] <lukacu> well thats reliable ... sessionsaver is a part of ... firefox?
[11:16] <artnay> lukacu: yes, but remembering form information was new to me. well, I haven't been able to make X crash without composite
[11:19] <artnay> ok, I'll watch an episode of Lost if you stay silent :)
[11:26] <lukacu> lol
[11:27] <lukacu> i just havent configured xchat to remind me when somebody types something
[11:28] <lukacu> well ... i guess you are already watching lost
[11:29] <lukacu> but if you know how to configure xchat to perform some kind of visual notification please let me know


[08:03] -queuebot:#ubuntu-release- New: accepted golang-github-hetznercloud-hcloud-go [amd64] (disco-proposed) [1.12.0+git20190218.63d492d-1]
[08:03] -queuebot:#ubuntu-release- New: accepted roundcube-plugins-extra [amd64] (disco-proposed) [1.3.8-20190219]
[08:03] -queuebot:#ubuntu-release- New: accepted redmine [amd64] (disco-proposed) [4.0.1-1]
[08:04] -queuebot:#ubuntu-release- New: accepted libreoffice-l10n [amd64] (disco-proposed) [1:6.2.1~rc1-0ubuntu1]
[10:55] -queuebot:#ubuntu-release- New binary: libreoffice [amd64] (disco-proposed/main) [1:6.2.1~rc1-0ubuntu1] (kubuntu, ubuntu-desktop)
[11:20] -queuebot:#ubuntu-release- Unapproved: virtualbox-hwe (bionic-proposed/multiverse) [5.2.18-dfsg-3~ubuntu18.04.1 => 5.2.18-dfsg-3~ubuntu18.04.2] (no packageset)
[12:17] <fidencio> jbicha: jibel: https://twitter.com/ffidencio/status/1098194562659614720
[12:18] -queuebot:#ubuntu-release- Unapproved: base-files (trusty-proposed/main) [7.2ubuntu5.5 => 7.2ubuntu5.6] (core)
[12:18] -queuebot:#ubuntu-release- Unapproved: base-files (xenial-proposed/main) [9.4ubuntu4.7 => 9.4ubuntu4.8] (core)
[12:24] -queuebot:#ubuntu-release- New binary: sagemath [i386] (disco-proposed/universe) [8.6-5] (no packageset)
[12:39] -queuebot:#ubuntu-release- New binary: sagemath [ppc64el] (disco-proposed/universe) [8.6-5] (no packageset)
[12:45] -queuebot:#ubuntu-release- Unapproved: accepted base-files [source] (xenial-proposed) [9.4ubuntu4.8]
[13:53] -queuebot:#ubuntu-release- Unapproved: debian-installer (xenial-proposed/main) [20101020ubuntu451.27 => 20101020ubuntu451.28] (core)
[13:53] -queuebot:#ubuntu-release- New binary: sagemath [amd64] (disco-proposed/universe) [8.6-5] (no packageset)
[14:22] <cjwatson> Stopping transition tracker updates while I see if I can lift and shift it over to the bionic chroot
[14:23] <infinity> Ooo, fancy.
[14:23] <cjwatson> (doko got that created via RT)
[14:23] <infinity> Does it actually need to be in a chroot at all anymore?   I thought it was in one because it needed newer packages than the base system provided at the time.
[14:24] -queuebot:#ubuntu-release- Unapproved: accepted debian-installer [source] (xenial-proposed) [20101020ubuntu451.28]
[14:24] <Laney> It needs a ton of ocaml stuff
[14:25] <cjwatson> infinity: Yes, because snakefruit is xenial while versioned provides (the motivation for this change) requires bionic
[14:26] <cjwatson> Wasn't implemented in dose3 until then
[14:27] <infinity> Ahh, fair enough.
[14:27] <cjwatson> The ocaml stuff is less of a problem now that we're using the ben and dose-distcheck binary packages rather than building it from source
[14:27] <Laney> ah, I missed the former
[14:28] <cjwatson> (still pulls in a few ocaml packages, but much less than it used to when we had a ton of -dev)
[14:36] -queuebot:#ubuntu-release- Unapproved: fwupd (cosmic-proposed/main) [1.1.2-1 => 1.1.2-1ubuntu<IP_ADDRESS>] (desktop-core)
[14:52] -queuebot:#ubuntu-release- Unapproved: rejected libio-socket-ssl-perl [sync] (bionic-proposed) [2.060-3~ubuntu18.04.0]
[14:52] -queuebot:#ubuntu-release- Unapproved: rejected nova [sync] (bionic-proposed) [2:17.0.7-0ubuntu2.1]
[14:52] -queuebot:#ubuntu-release- Unapproved: rejected python-cryptography [sync] (bionic-proposed) [2.1.4-1ubuntu1.3]
[14:52] -queuebot:#ubuntu-release- Unapproved: rejected python3.6 [sync] (bionic-proposed) [3.6.8-1~18.04.1]
[14:52] -queuebot:#ubuntu-release- Unapproved: rejected r-cran-openssl [sync] (bionic-proposed) [1.0.1-1ubuntu1.1]
[14:52] -queuebot:#ubuntu-release- Unapproved: rejected ruby2.5 [sync] (bionic-proposed) [2.5.1-1ubuntu1.2]
[14:53] -queuebot:#ubuntu-release- Unapproved: rejected libnet-ssleay-perl [sync] (bionic-proposed) [1.84-1ubuntu0.1]
[14:53] -queuebot:#ubuntu-release- Unapproved: rejected python2.7 [sync] (bionic-proposed) [2.7.15-4ubuntu4~18.04]
[14:53] -queuebot:#ubuntu-release- Unapproved: rejected ruby-openssl [sync] (bionic-proposed) [2.0.9-0ubuntu1]
[14:53] -queuebot:#ubuntu-release- Unapproved: rejected openssl [sync] (bionic-proposed) [1.1.1-1ubuntu2.1~18.04.0]
[14:53] -queuebot:#ubuntu-release- Unapproved: rejected python3.7 [sync] (bionic-proposed) [3.7.2-1~18.04.1]
[14:56] <cjwatson> Hmm, can't seem to get the bionic tracker to work
[14:56] <cjwatson> E: General error: ben-specific error: template debian not found
[14:56] <cjwatson> Trying to reproduce locally
[15:01] <cjwatson> Reproduced locally with minimal config; rebuilding doesn't help
[15:30] -queuebot:#ubuntu-release- Builds: Netboot amd64 [Xenial 16.04.6] (20101020ubuntu451.28) has been added
[15:30] -queuebot:#ubuntu-release- Builds: Netboot arm64 [Xenial 16.04.6] (20101020ubuntu451.28) has been added
[15:30] -queuebot:#ubuntu-release- Builds: Netboot armhf [Xenial 16.04.6] (20101020ubuntu451.28) has been added
[15:30] -queuebot:#ubuntu-release- Builds: Netboot i386 [Xenial 16.04.6] (20101020ubuntu451.28) has been added
[15:30] -queuebot:#ubuntu-release- Builds: Netboot ppc64el [Xenial 16.04.6] (20101020ubuntu451.28) has been added
[15:30] -queuebot:#ubuntu-release- Builds: Netboot s390x [Xenial 16.04.6] (20101020ubuntu451.28) has been added
[15:51] <sil2100> ^ ignore those, .6 is still not a thing
[16:23] -queuebot:#ubuntu-release- Unapproved: rejected snapd [source] (cosmic-proposed) [2.37.3+18.10]
[16:34] <coreycb> hello, can an archive admin please look at accepting masakari from the disco NEW queue? we are adding support for the masakari project which provides VM HA for openstack.
[16:38] -queuebot:#ubuntu-release- New binary: sagemath [arm64] (disco-proposed/universe) [8.6-5] (no packageset)
[16:49] -queuebot:#ubuntu-release- Unapproved: rejected fwupd [armhf] (disco-proposed) [1.2.4-2]
[16:49] <infinity> coreycb: Is that headed to Debian at some point?
[16:50] <coreycb> infinity: probably not, they generally do openstack packages seperately
[16:50] -queuebot:#ubuntu-release- New: rejected initramfs-tools-devices [source] (cosmic-proposed) [0.1]
[16:51] <coreycb> infinity: core openstack packages at least. we share a lot of dependencies but generally not core openstack packages that we have in main.
[16:53] <infinity> Mmkay.
[17:11] -queuebot:#ubuntu-release- New binary: lazarus [i386] (disco-proposed/universe) [2.0.0+dfsg-1] (no packageset)
[17:15] -queuebot:#ubuntu-release- New binary: lazarus [amd64] (disco-proposed/universe) [2.0.0+dfsg-1] (no packageset)
[17:24] -queuebot:#ubuntu-release- New binary: lazarus [armhf] (disco-proposed/universe) [2.0.0+dfsg-1] (no packageset)
[17:28] -queuebot:#ubuntu-release- New binary: lazarus [arm64] (disco-proposed/universe) [2.0.0+dfsg-1] (no packageset)
[18:42] -queuebot:#ubuntu-release- New binary: sagemath [armhf] (disco-proposed/universe) [8.6-5] (no packageset)
[19:37] <vorlon> Laney, juliank, sil2100: armhf runners were failed - Feb 17 14:42:05 juju-prod-ues-proposed-migration-machine-12 sh[29907]: autopkgtest [14:42:04]: ERROR: testbed failure: unexpected eof from the testbed
[19:38] <juliank> ugh
[19:59] -queuebot:#ubuntu-release- Unapproved: horizon (cosmic-proposed/main) [3:14.0.1-0ubuntu1 => 3:14.0.1-0ubuntu2] (openstack, ubuntu-server)
[20:22] -queuebot:#ubuntu-release- New source: waylandpp (disco-proposed/primary) [0.2.4-0ubuntu1]
[20:43] -queuebot:#ubuntu-release- New source: libmarc-charset-perl (disco-proposed/primary) [1.35-2build1]
[21:35] -queuebot:#ubuntu-release- Unapproved: ruby2.5 (cosmic-proposed/main) [2.5.1-5ubuntu4.1 => 2.5.1-5ubuntu4.2] (kubuntu, ubuntu-desktop, ubuntu-server)
[21:39] <ricotz> hello, was this forgotten to be (fully) approved https://launchpad.net/ubuntu/+source/fwupd/1.2.4-3 ?
[21:39] -queuebot:#ubuntu-release- Unapproved: ruby2.5 (bionic-proposed/main) [2.5.1-1ubuntu1.1 => 2.5.1-1ubuntu1.2] (kubuntu, ubuntu-desktop, ubuntu-server)
[22:19] -queuebot:#ubuntu-release- Unapproved: lldpd (bionic-proposed/universe) [0.9.9-1 => 0.9.9-1ubuntu0.1] (no packageset)
[22:32] -queuebot:#ubuntu-release- Unapproved: lldpd (cosmic-proposed/universe) [1.0.1-1 => 1.0.1-1ubuntu0.1] (no packageset)
[23:15] -queuebot:#ubuntu-release- New binary: golang-github-go-xorm-core [amd64] (disco-proposed/none) [0.6.2-1] (no packageset)
[23:16] -queuebot:#ubuntu-release- New binary: hcloud-cli [amd64] (disco-proposed/none) [1.11.0+git20190206.5780af6-1] (no packageset)
[23:16] -queuebot:#ubuntu-release- New binary: sat-pubsub [amd64] (disco-proposed/none) [0.3.0a1-1] (no packageset)
[23:16] -queuebot:#ubuntu-release- New binary: hcloud-cli [i386] (disco-proposed/none) [1.11.0+git20190206.5780af6-1] (no packageset)
[23:16] -queuebot:#ubuntu-release- New binary: vue-router.js [amd64] (disco-proposed/none) [3.0.2+ds-1] (no packageset)
[23:17] -queuebot:#ubuntu-release- New binary: golang-github-teris-io-shortid [amd64] (disco-proposed/none) [1.0+git20171029.771a37c-1] (no packageset)
[23:17] -queuebot:#ubuntu-release- New binary: uefitool [amd64] (disco-proposed/none) [0.26.0-1] (no packageset)
[23:17] -queuebot:#ubuntu-release- New binary: uefitool [ppc64el] (disco-proposed/none) [0.26.0-1] (no packageset)
[23:17] -queuebot:#ubuntu-release- New binary: hcloud-cli [ppc64el] (disco-proposed/none) [1.11.0+git20190206.5780af6-1] (no packageset)
[23:17] -queuebot:#ubuntu-release- New binary: uefitool [i386] (disco-proposed/none) [0.26.0-1] (no packageset)
[23:18] -queuebot:#ubuntu-release- New binary: hcloud-cli [s390x] (disco-proposed/none) [1.11.0+git20190206.5780af6-1] (no packageset)
[23:18] -queuebot:#ubuntu-release- New binary: uefitool [s390x] (disco-proposed/none) [0.26.0-1] (no packageset)
[23:18] -queuebot:#ubuntu-release- New binary: speech-dispatcher-contrib [i386] (disco-proposed/multiverse) [0.9.0-5] (no packageset)
[23:49] -queuebot:#ubuntu-release- New binary: hcloud-cli [armhf] (disco-proposed/universe) [1.11.0+git20190206.5780af6-1] (no packageset)
[23:51] -queuebot:#ubuntu-release- New binary: hcloud-cli [arm64] (disco-proposed/universe) [1.11.0+git20190206.5780af6-1] (no packageset)
[23:51] -queuebot:#ubuntu-release- New binary: uefitool [armhf] (disco-proposed/universe) [0.26.0-1] (no packageset)
[23:51] -queuebot:#ubuntu-release- New binary: uefitool [arm64] (disco-proposed/universe) [0.26.0-1] (no packageset)