[08:01] <evfool> ping mvo
[08:11] <mvo> hey evfool!
[08:13] <evfool> quick question about bug 436981: you mention that we should use software-center's wording, but I have checked s-c's code but that also seems to be using the aptdaemon conflict dialog widget
[08:13] <ubot4> Launchpad bug 436981 in update-manager (Ubuntu) "update-manager language unintuitive (affects: 2) (heat: 7)" [Medium,Triaged] https://launchpad.net/bugs/436981
[08:13] <evfool> mvo^
[08:14] <evfool> could you please check when you'll have the time and let me know if I have overlooked something, but probably the wording should be updated in aptdaemon
[08:14] <mvo> evfool: yeah, you are right
[08:14] <mvo> evfool: I guess what I wanted to say is that we need to be consistent, back then (2009) u-m was using synaptic as its backend
[08:15] <mvo> evfool: so now that we have the common aptdaemon backend we need to change it there of course :)
[08:15] <evfool> mvo: thanks, then I'm reassigning it to aptd and will try to find a better wording
[08:16] <mvo> thanks, much appricated evfool!
[08:27] <brendand> mvo - i always wondered why there were two backends :)
[08:47] <mvo> brendand: historical reasons, the synaptic one can probably go by now
[08:54] <evfool> mvo: can't update with update-manager on oneiric, I get package does not exist dialogs with details like "Package [dbus.String(u'libgtkspell3-0')] isn't available" ... any idea?
[08:58] <mvo> evfool: oh, reproducable? or was this just a one-off thing?
[08:59] <evfool> 100% repro, can't update at all... after unchecking the package, I get the same for another package from the list, and so on
[08:59] <mvo> probably some background update happend while u-m was open, I think aptdaemon needs to send out a "stuff changed" signal
[08:59] <mvo> evfool: if you close/reopne its gone I presume?
[09:00] <evfool> mvo: yes, I had this since last week, thought it's something only temporary, and have restarted many time, but it's still there
[09:00] <evfool> maybe I'll try updating again with apt-get upgrade and see if I get this tomorrow
[09:01] <mvo> evfool: oh, in this case hold on
[09:01] <mvo> evfool: that is really odd
[09:01] <mvo> evfool: and you said its for a bunch of different packages?
[09:01] <mvo> evfool: or always the same one?
[09:01] <evfool> seems like the dbus string isn't converted to standard string
[09:02] <evfool> mvo: it's for all packages I have tried, tried with 3-4, and have 283 in the list, so I don't want to try it for all of them :)
[09:02] <mvo> yeah, that sounds like hte problem, let me try to reproduce with the latest code
[09:42] <brendand> mvo - do you have any notion what might be going on with this bug? https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/812949
[09:42] <ubot4> Launchpad bug 812949 in update-manager (Ubuntu) "horizontal resize (make it smaller) is limited to the extent of the list box (affects: 1) (heat: 10)" [Medium,Triaged]
[09:43] <brendand> i tried looking at it a bit myself, but it just seems strange
[09:43] <brendand> it's probably some problem with packing, i just hope it's not a gtk3 issue (though I haven't seen it elsewhere)
[09:46] <mvo> brendand: I'm not sure I fully understand the bug description, but I see odd resize behavior as well, I would bet that its something with the old glade file that got converted to gtkbuilder
[09:48] <brendand> mvo - when you try to resize horizontally (from either side), you can't drag any further then the edge of the list box
[11:21] <jmburgess> This is horribly delayed (my computer died, and I left the charger at work. woops) but thanks micahg and charlie-tca for your help!  Charlie nominated bug 784379 for natty, but do I need to do anything else as far as the SRU process?  Should I tell them to follow the SRU Procedure?
[11:21] <ubot4> Launchpad bug 784379 in gtk2-engines-oxygen (Ubuntu) "Oxygen-gtk style fails to load with Emacs (affects: 5) (heat: 24)" [Undecided,Fix released] https://launchpad.net/bugs/784379
[11:43] <yofel> jmburgess: from a triaging procedure the bug is done, but yes, now someone has to go through the SRU procedure and prepare a debdiff and testcase
[11:43] <jmburgess> yofel: Ok so I feel like I should tell them that...correct?
[11:44] <yofel> If someone of them wants to do it and doesn't know about the procedure it would be nice if you could point them to it - esp. since someone already tried to build a package
[11:45] <jmburgess> yofel: great thanks I'll point them in the right direction!
[11:48] <MoLE_> I think that bug 715438 is ready to be triaged if a bug squad member has time.  It's tagged regression-release.
[11:49] <ubot4> Launchpad bug 715438 in linux (Ubuntu) "hermes-I wireless interface will not associate with open access point (affects: 25) (dups: 2) (heat: 78)" [Undecided,Confirmed] https://launchpad.net/bugs/715438
[11:54] <jmburgess> How do you remove a package that a bug affects in launchpad? for example bug 815274 affects NULL project...how would I remove that?
[11:54] <ubot4> Launchpad bug 815274 in ubuntu (and 1 other project) "Blackscreen when playing video/audio file Intel 82852/855GM Integrated (affects: 1) (heat: 6)" [Undecided,New] https://launchpad.net/bugs/815274
[11:56] <yofel> jmburgess: not possible, that's what NULL is for
[11:58] <yofel> although there does seem to be some progress on bug 80902
[11:58] <ubot4> Launchpad bug 80902 in launchpad "Can't target bug report from project to distribution, or vice versa (affects: 12) (dups: 9) (heat: 132)" [High,In progress] https://launchpad.net/bugs/80902
[12:10] <jmburgess> yofel: gotcha thanks!
[13:54] <jmburgess> I think these two are ready to be marked as triaged. Bug 81348 and bug 814787. They are needs-packaging bugs so they already have wishlist importance
[13:54] <ubot4> Launchpad bug 81348 in nautilus (Ubuntu) "nautilus very slow if connection to network shares is lost (heat: 1)" [Low,Invalid] https://launchpad.net/bugs/81348
[13:54] <ubot4> Launchpad bug 814787 in ubuntu "[needs-packaging] openstack-dashboard (affects: 1) (dups: 1) (heat: 16)" [Wishlist,New] https://launchpad.net/bugs/814787
[13:56] <roadmr> jmburgess: you sure about 81348? looks like it's missing a digit (the one linked is old and closed since 2007)
[13:57] <jmburgess> Sorry 81348 should be bug 813848
[13:57] <ubot4> Launchpad bug 813848 in ubuntu "[needs-packaging] apitrace (affects: 1) (heat: 6)" [Wishlist,New] https://launchpad.net/bugs/813848
[14:04] <roadmr> jmburgess: did you search for existing or RFP/ITP in Debian for these two packages?
[14:06] <hggdh> jmburgess: needs-packaging is a *workflow* "bug". They should not be touched by triagers, unless the workflow is respected
[14:08] <hggdh> jmburgess: see https://wiki.ubuntu.com/Bugs/HowToTriage#Special_types_of_bugs
[14:09] <hggdh> jmburgess: you may have lost the last two chat entries for you, I will repeat them:
[14:09] <hggdh> 09:04:37      roadmr | jmburgess: did you search for existing or RFP/ITP in Debian for these two packages?
[14:10] <hggdh> 09:06:32       hggdh | jmburgess: needs-packaging is a *workflow* "bug". They should not be touched by triagers, unless the workflow is respected
[14:15] <jmburgess> hggdh: I followed the needs packaging bugs steps.  Checked all debian bug tracker and package list
[14:16] <roadmr> hggdh: so is it best if we leave those alone? I was about to set them to triaged (just waiting on RFP/ITP confirmation from jmburgess)
[14:16] <jmburgess> The last step says mark the bug as triaged and add the tag needs-packaging
[14:19] <hggdh> jmburgess: I see no comment stating no ITP/RFP found (for example)
[14:20] <hggdh> roadmr: usually it is better to leave them alone if you are starting on triage
[14:20] <bdmurray> mvo: have you see bug 800910?
[14:20] <ubot4> Launchpad bug 800910 in linux (Ubuntu Oneiric) (and 5 other projects) "Kernel Upgrade forces removal of grub-efi due to missing recommends entry (affects: 6) (dups: 1) (heat: 123)" [Undecided,Fix released] https://launchpad.net/bugs/800910
[14:20] <jmburgess> Oh ok I didn't know I was supposed to comment.  Ill comment then
[14:20] <hggdh> roadmr: chances of doing the wrong thing are pretty good ;-)
[14:20] <roadmr> hggdh: ok, I'll follow some needs-packaging bugs to get a feel for the process before touching them :)
[14:21] <yofel> jmburgess: just leave the bugs as they are for now, or talk to the MOTU team before touching them
[14:22] <pedro_> morning folks
[14:22] <roadmr> re! pedro_
[14:22] <hggdh> roadmr, jmburgess: for reference, the checks are described in https://wiki.ubuntu.com/UbuntuDevelopment/NewPackages (and yofel is correct)
[14:22] <hggdh> !er pedro_
[14:22] <ubot4> Factoid 'er pedro_' not found
[14:24] <mvo> bdmurray: no, let me check
[14:24] <jmburgess> hggdh: gotcha thanks. Should we change the needs packaging bugs section of the howto triage wiki then?
[14:27] <jmburgess> Because the wiki says to mark as triaged after you've done all those steps
[14:27] <hggdh> jmburgess: they already state they should be left alone (perhaps not as clear), last sentence of first paragraph under "Special Types of Bugs"
[14:28] <hggdh> "Unless a triager is familiar with the specific process in question, adjustments to these bugs are likely to be problematic. "
[14:30] <jmburgess> As usual...read all directions before you start gets me again
[14:30] <jmburgess> Thanks hggdh for your help
[14:31] <hggdh> jmburgess: thank you for helping.
[14:31] <hggdh> But I think I will add some clarifications there...
[14:32] <hggdh> jmburgess: and please do not feel bad -- I think *all* of us got down through the same slippery path ;-)
[14:37] <hggdh> RedSingularity: you were looking for me the other day -- I am now here ;-)
[14:39] <yofel> curious: anyone going to DS?
[14:40] <hggdh> DS == Desktop Summit?
[14:40] <yofel> yep
[14:40] <hggdh> pedro_: ^ ?
[14:41] <pedro_> yofel, i'm  going there and a few folks from the desktop team as well
[14:43] <yofel> k, I'll probably go, so let's see whom I'm going to meet :)
[14:43] <pedro_> cool :-)
[14:44] <hggdh> and... (late, but so what) buen dia pedro_
[14:46] <pedro_> moi moi hggdh
[14:46] <yofel> oh right, good morning pedro_ ^^
[14:50] <hggdh> :-)
[15:09] <jmburgess> Sorry to keep bugging you guys...im new to this but marking bug 809047 as fix released is correct right? The original reporter said that he hasn't had the problem in two weeks and was probably due to an update he did
[15:09] <ubot4> Launchpad bug 809047 in ubuntu "Suspend works with pm-suspend, but not with FN+F4 (affects: 1) (heat: 221)" [Undecided,New] https://launchpad.net/bugs/809047
[15:11] <charlie-tca> jmburgess: correct. Has anyone shown you the standard repsponses?
[15:11] <charlie-tca> A good comment for that is https://wiki.ubuntu.com/Bugs/Responses#Bugs_resolved_after_update_or_config_change
[15:12] <jmburgess> Yeah I found those...I'm just making sure fix released is correct thanks
[15:13] <charlie-tca> yes, it is correct for that, although invalid can also be used, since you don't know what fixed it.
[15:14] <charlie-tca> jmburgess: thank you for hanging in here. Learning this stuff can be difficult.
[15:21] <jmburgess> Charlie-tca: yeah I figured invalid is more accurate cause I don't actually know exactly why it magically started working again
[15:22] <jmburgess> Charlie-tca: and no problem...I don't have the time to really get into dev so I figured this is one way to help out.
[16:27] <RedSingularity> hggdh: I think that was about bugsquad membership.  You were correct though, I was able to renew on my own.  Thanks buddy :)
[16:30] <paultag> RedSingularity: haha fail!
[16:30] <RedSingularity> paultag: ohh look who it is!  You son'uva'gun man!
[16:31] <paultag> RedSingularity: :)
[16:31] <RedSingularity> paultag: hey, not as bad as the time I thought you were in Central time
[16:32] <paultag> RedSingularity: yeah man, seriously. That was all sorts of messed up
[16:32] <RedSingularity> LOL indeed it was ;)
[17:46] <ropetin> ™2@™™£¡™£123/quit
[18:03] <om26er_> how do i report touchpad related issues ??
[18:03] <om26er_> what should I do so that it gets the attention of the right people
[18:05] <jmburgess> Will apport-collect work for the person who's not the original bug reporter?
[18:12] <hggdh> jmburgess: apport-collect will work for anyone -- but they better match the issue
[18:14] <hggdh> om26er_: it depends if it is kernel or desktop-related
[18:15] <om26er_> hggdh, I believe it to be driver bug, the cursor will sometimes move up and down, will unmaximize windows like its acting as a multi-touch surface
[18:15] <om26er_> sudo modprobe -r psmouse; sleep 2; sudo modprobe psmouse
[18:15] <om26er_> makes it normal again :/
[18:16] <hggdh> om26er_: sounds like kernel, then. Open the bug, and ping #ubuntu-kernel
[18:16]  * hggdh gets a system lock when doing a rmmod psmouse...
[18:17] <om26er_> hggdh, doing now, thx :)
[18:26] <jmburgess> hggdh: its bug 814323.  Seems like andreas (the second to last commenter) is having the same issue.
[18:26] <ubot4> Launchpad bug 814323 in linux (Ubuntu) "The laptop does not suspend anymore (affects: 4) (heat: 26)" [Undecided,Confirmed] https://launchpad.net/bugs/814323
[18:28] <hggdh> jmburgess: (still loading the page) it is important to note that bugs involving kernel should be opened by each person having an issue. Unless the hardware is absolutely identical (and package versions also), we should not add to another's bug
[18:28]  * hggdh goes look at the bug now
[18:32] <hggdh> jmburgess: so, what did you want to do there? kernel bugs had a different flow
[18:32] <hggdh> and this seems to be a case where identical hardware is not really needed :-)
[18:33] <hggdh> s/had a different/have a different/
[18:33] <jmburgess> hggdh: so im reading the kernel bug triage wiki
[18:34] <jmburgess> I guess the next step is to ask them to test with the upstream mainline kernel
[18:39] <jmburgess> Ooo there is a response already set for suspend/resume issues. Yes!
[18:44] <jmburgess> Just realized andreas had vmware player installed, the original reporter has virtualbox installed.  They are diff problems correct?
[18:52] <hggdh> jmburgess: they *may* be, difficult to know from the stratosphere. But it sounds that the mods loaded by either are affecting the suspend/resume, so the cause may be related
[18:53] <hggdh> jmburgess: I am not sure there is anything else to be done there. Now a kernel person should come in and decide on a route of action
[18:53] <jmburgess> Yeah i mean i bet its more than a coincidence that two virt software have the same problem and be completely different.
[18:54] <hggdh> heh. I would not bet, but I agree that sounds related
[18:54] <jmburgess> Ill go ask in ubuntu-kernel
[19:47] <xteejx> Hey guys
[19:47] <dtchen> 'lo
[19:47] <xteejx> That was a bit quick :)
[19:48] <xteejx> You canonical guys seem to be on top of everything recently :D
[19:48] <dtchen> (I'm not a Canonical person, but sure.)
[19:48] <xteejx> Oops, thought you wre Daniel Chen no matter :)
[19:48] <dtchen> I am, and I'm not a Canonical person. :)
[19:49] <xteejx> lol just a very visible volunteer then :)
[19:50] <xteejx> Anyway, bug 816145, anyone able to take a second look for me please, I've upstreamed it, I guess there's nothing fo for it Ubuntu-wise right?
[19:50] <ubot4> Launchpad bug 816145 in linux (Ubuntu) (and 1 other project) "Atheros AR5001 wireless card "wireless is disabled by hardware switch" (affects: 4) (dups: 1) (heat: 16)" [High,Triaged] https://launchpad.net/bugs/816145
[19:50] <xteejx> *nothing else to do for it
[19:50] <dtchen> that's correct.
[19:51] <xteejx> Great, thank you
[19:51] <xteejx> Hate this bug so much, I need bigger shoes :P
[19:52] <dtchen> I carry all sorts of workaround usb ath9k-based devices just in case I run into those situations.
[19:52] <xteejx> Wifi dongles?
[19:52] <dtchen> indeed
[19:52] <xteejx> I think for the time being it'd be a good idea to invest in one
[19:53] <xteejx> Any personal recommendations?
[19:53] <dtchen> any that use ath9k or ath9k_htc
[19:54] <xteejx> htc? That's not HTC as in Hero, Desire, Wildfire is it?
[19:54] <dtchen> e.g., I have a couple lower-end Netgears
[19:54] <xteejx> I see
[19:54] <dtchen> "description:    Atheros driver 802.11n HTC based wireless devices"
[19:55] <xteejx> I don't suppose there's an easy way to find out which driver a dongle would use is there without buying it first? :(
[19:55] <dtchen> I normally try and get the usb id(s)
[19:56] <xteejx> Ok cool, so usb id + Google = happy wifi
[19:56] <xteejx> I'll get on that now
[19:56] <xteejx> Thanks :)
[19:56] <dtchen> yw
[19:56] <dtchen> also, linuxwireless.org has a bit of a database, but it's not exhaustive
[19:57] <xteejx> Cheers I'll have a look
[21:05] <MoLE_> I think that bug 715438 is ready to be triaged if a bug squad member has time.  It's tagged regression-release.
[21:05] <ubot4> Launchpad bug 715438 in linux (Ubuntu) "hermes-I wireless interface will not associate with open access point (affects: 25) (dups: 2) (heat: 78)" [Undecided,Confirmed] https://launchpad.net/bugs/715438
[21:08] <dtchen> MoLE_: would you mind reproducing the symptom using the latest Oneiric kernel?
[21:08] <dtchen> (Ubuntu 3.0.0-7.8-generic 3.0.0)
[21:11] <MoLE_> dtchen, happy to do so.
[21:11] <MoLE_> dtchen, so just run another attempt at connecting and apport-collect?
[21:12] <dtchen> MoLE_: no need to run apport-collect afterward yet. We'll attempt to confirm the symptom with both Oneiric's latest kernel and the latest vanilla kernel.
[21:13] <MoLE_> ok, I'll update.
[21:22] <MoLE_> dtchen, confirmed on 3.0.0.7-8 and bug report updated.