[00:02]  * hggdh is being driven crazy by an application called ChangePoint, from Compuware.
[00:02] <hggdh> jeez
[00:30] <Rocket2DMn> ok, bug 285682 - linux, hal, or gnome-volume-manager ?
[00:34] <persia> Rocket2DMn, I think gnome-volume-manager is deprecated.
[00:35] <Rocket2DMn> persia, looks like its not installed in intrepid, good call.  what replaces it?
[00:35] <Rocket2DMn> i was leaning toward hal on that bug, but i dont really know enough to say for sure
[00:36] <persia> Rocket2DMn, The first error message makes me think it's gvfs-backends (because of gvgs-gphoto2-volume-monitor), but the second looks like a USB timing issue, which might point either to linux or the camera.
[00:37] <Rocket2DMn> OK, so you think I should leave it as linux? i was about to mark the bug triaged
[00:37] <Rocket2DMn> may want to ask if he can manually mount though
[00:39] <Rocket2DMn> persia, ^
[00:40] <persia> Yeah.  Check the manual mount.  If that doesn't work, there is a linux task (or a problem with the camera).  There may also be a gvfs-backends task
[00:42] <azimout> question: every now and then i come across a source package in launchpad that, when selected, gives me an error message "u'Package fglrx-driver not published in Ubuntu'" and refuses to save
[00:43] <azimout> fglrx-driver is not the only package like this...
[00:43] <azimout> what is the reasoning behind this, and should these packages be removed from the list, or not?
[00:44] <persia> I'd recommend filing bugs at https://launchpad.net/malone/+filebug if you find packages like that when you know they are available in a current release.
[00:44] <persia> Today, the list of current releases includes Dapper, Gutsy, Hardy, and Intrepid.
[00:45] <Rocket2DMn> thanks persia
[01:00] <azimout> thank you, persia
[01:05] <greg-g> bdmurray: you have a moment (3 minutes)?
[01:09] <greg-g> bdmurray: a suggested rewording/reformating of the HugDay wiki page instructions: http://pastebin.osuosl.org/22387
[01:09] <greg-g> bdmurray: just trying to make it explicit that "Verify the bug is still not fixed" is not enough to mark it off the list :)
[01:13]  * persia supports greg-g's suggested text change.  Makes it obvious that some tasks are subtasks of others.
[01:29] <hggdh> greg-g, I think it is a good idea
[01:30] <greg-g> with you two on board, I'll change it.
[01:30] <greg-g> bdmurray: I got 2 +1s, I'm going for it, let me know if I'm wrong.
[01:33] <greg-g> tomorrow's is updated, now to find the template....
[01:34] <greg-g> there doesn't seem to be one.
[01:37] <hggdh> willing to create such? ;-)
[01:37] <greg-g> hggdh: I wonder how it is done now, because I assume it isn't typed out by hand each time
[01:38] <greg-g> is it part of the bug-helper-scripts or whatever it is called?
[01:42] <greg-g> I'll look into it later, gotta go afk for a bit
[01:42] <persia> There's definitely a script, although I forget both the name and location.
[01:42] <charlie-tca> This the one?
[01:42] <hggdh> greg-g, I also wonder about it
[01:42] <charlie-tca> https://wiki.ubuntu.com/UbuntuBugDay/Organizing
[01:42] <charlie-tca> I like the changes
[01:43] <hggdh> charlie-tca, I am not sure this is it, but it does look promising... thank you
[01:44] <charlie-tca> Sure, it's the one I used when I planned Xubuntu Hug Day
[01:44] <hggdh> hey, charlie-tca, forgot -- kudos on making bugcontrol
[01:45] <charlie-tca> Thanks. And thanks for getting me there!
[01:57] <persia> charlie-tca, Congratulations!
[01:58] <charlie-tca> Thanks. I owe a lot to your explanations, though
[02:10] <hggdh> well, I did not get you there -- your work here did it
[02:19] <charlie-tca> You guys sure helped. I'm a slow learner sometimes, even when you don't know
[02:23] <persia> charlie-tca, It's not about speed, it's about continuing to contribute.  I triaged bugs for almost two years before I was granted special bug control permissions (although the team wasn't called "bugcontrol" at the time).
[02:27] <charlie-tca> Conributing when I know what to do is easy for me.
[02:35] <hggdh> learning is the key
[02:36] <hggdh> you have to be willing to learn, and willing to find yourself without knowing what to do -- and asking for help
[02:36] <charlie-tca> So true.
[02:36] <hggdh> this is, in fact, what I ask from the people that work for me/with me
[02:43] <charlie-tca> I do the same. It's hard to help those who don't want it.
[06:18] <dholbach> good morning
[06:20] <sdh> morning
[09:22] <cjs> Hm. What does it mean when one is not getting any response to a fairly clear bug report?
[09:22] <cjs> https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/242956
[09:24] <Hobbsee> cjs: means that the guy is very busy doing other stuff, i think
[09:32] <cjs> For five months?
[09:51] <persia> cjs, For that specific individual, being extremely busy is the normal state of affairs.
[10:02] <cjs> Actually, I'm not even sure why that's in OpenSSH; it's a resolver issue. I've filed a new bug report for that.
[10:02] <cjs> https://bugs.launchpad.net/ubuntu/+bug/288011
[13:30] <mrooney> asac: I wonder if perhaps my signal strength bug is bug 69709 or bug 178883, it IS on an atheros card
[13:34] <asac> mrooney: unlikely. i also see it here on rtl8187
[13:35] <asac> well unlikely == 69709 ... 178883 sounds like a generic upe
[13:35] <asac> dupe
[13:35] <asac> yes.
[13:35]  * asac opens that bug
[13:36] <mrooney> asac: when you see it, do you think there are multiple networks with the same SSID? Maybe that really has nothing to do with it, it just seems very correlated in my experience
[13:36] <asac> mrooney: not sure. in 178883 the reporters see differnt signal strenghts for individual APs i think?
[13:36] <asac> for me _all_ APs have the same strength here
[13:36] <asac> but that might be driver related :/
[13:37] <asac> mrooney: looks like it displays the "quality" and not the "signal strength" here
[13:37] <asac> mrooney: can you confirm that that matches what you see?
[13:38] <asac> e.g. quality in iwlist scan == what is shown in applet drop down
[13:39] <mrooney> asac: hard to know, there are four with the same SSID
[13:40] <mrooney> asac: how can I get the number that the drop-down is representing?
[13:43] <asac> mrooney: err. please past your iwlist can output with all four
[13:44] <asac> paste
[13:45] <mrooney> asac: http://pastebin.ca/1234637
[13:47] <mrooney> applet says 64% and the drop-down looks like, 10 or 15%
[13:47] <asac> mrooney: yeah. look at the quality values ... most likely the max from those is used
[13:47] <asac> or the minimum
[13:47] <asac> mrooney: you have 12% ... and one with 46 and one with 8
[13:48] <mrooney> yeah so it could be the 12%, but I guess that is what seems wrong, it shouldn't be connected to THAT one, right?
[13:49] <mrooney> ahh okay I am connected to the 46/70
[13:49] <danage> asac i know i'm probably getting annoying by now, but can i maybe point you to https://bugs.launchpad.net/mactel-support/+bug/278190
[13:50] <danage> i have put http://bugzilla.kernel.org/show_bug.cgi?id=11394 in my last comment. i think comment #19 in that bug could be the fix to the problems people are seeing (mostly on macbooks).
[13:50] <danage> question: can that patch be included in intrepid?
[13:52] <asac> danage: unlikely that we can still get that on the final CDs, but SRU after release is always an option (if the patch is good)
[13:52] <asac> let me check
[13:52] <danage> asac: sorry i mean comment #20
[13:52] <danage> asac: thanks
[13:53] <mrooney> asac: so 46/70=65% is exactly what I see in the applet, so that makes sense
[13:53] <asac> mrooney: ok. that means that its quality there ;)
[13:54] <mrooney> now where that lower drop-down is coming from, must be the minimum or maybe like 12/70, the lower one
[13:54] <asac> your signal strength output format looks wierd too (-70) ... but probably not related as it works for the main icon
[13:54] <danage> note: part of the symptom i am getting is that transmission speed is always reported as 1MB/s in iwconfig. i will add that to my bug description
[13:54] <mrooney> but it definitely has to be coming from a different network, it seems, do you agree?
[13:55] <mrooney> for the drop-down value
[13:55] <mrooney> the fact that they are identical in Hardy make me suspect NM
[13:56] <mrooney> but I guess I am using newer madwifi so it could be that...
[13:58] <mrooney> asac: there's just so many different variables in Intrepid for atheros wireless :)
[13:58] <mrooney> it is hard to directly compare anything
[14:09] <mrooney> asac: well, I have learned a lot, I will do some more debugging, thanks! do you agree that the much lower drop-down value appears to be coming from a different network?
[14:09] <mrooney> it looks like 10-15%, which wouldn't come from really any combination of 46 and 70
[14:10] <mrooney> other than subtraction :)
[14:10] <asac> mrooney: not sure which one is used. might just be that the scan didnt return the 65% one when NM asked for a scan
[14:12] <mrooney> right, okay, so filing a bug might be appropriate, for multiple SSIDs of the same name?
[14:29] <danage> thanks asac
[15:50] <dholbach> we're just about to do a Bug Jam
[15:51] <dholbach> and I'm setting up a couple of lists that our participants can grab bugs from
[15:51] <dholbach> which lists would you recommend?
[15:51] <dholbach> anything that's not on  https://wiki.ubuntu.com/Bugs/EasyTasks ?
[16:08] <bddebian> Boo
[16:32] <bdmurray> dholbach: maybe a package with detailed debugging instructions like update-manager
[16:40] <dholbach> bdmurray: yeah great
[17:56] <chrisccoulson> ping james_w
[17:57] <james_w> hey chrisccoulson
[17:58] <chrisccoulson> hi! is there any chance of introducing a new upstream version of a package in universe at this late stage? i'm looking at bug 287332. unfortunately, the current version of evolution-sharp doesn't work with our version of evolution-data-server, which has broken beagle
[18:00] <james_w> it depends on the seriousness of the bug, and how much the fix depends on the new upstream
[18:01] <chrisccoulson> the current version of evolution-sharp in universe won't even build with the current version of evolution-data-server at the moment
[18:01] <james_w> it sounds like it would be a candidate
[18:01] <chrisccoulson> the configure script checks the version of e-d-s then bombs out
[18:01] <james_w> is 0.18 just to add compatibility?
[18:02] <chrisccoulson> it adds compatibility with the new version of e-d-s
[18:02] <chrisccoulson> unfortunately, the current version we ship doesn't work at all. i don't mind preparing a new version if you think we can get it in
[18:05] <james_w> please jump on #ubuntu-motu and ask motu-release what they think
[18:05] <james_w> there don't seem to be many other changes
[18:05] <james_w> ember did the last two uploads, so you may want to ping him for an opinion
[18:05] <chrisccoulson> thanks, i'll do that
[18:08] <angusthefuzz> what does motu stand for?
[18:08] <james_w> Masters Of The Universe
[18:08] <angusthefuzz> :-)
[18:08] <danage> HAHAHAHAHAH
[18:09] <danage> great.
[18:09] <chrisccoulson> james_w - is there any easy way to ping members of motu-release on #ubuntu-motu?
[18:09] <chrisccoulson> **by easy, i meant quick
[18:09] <james_w> "dear motu-release, ..."
[18:10] <james_w> there is usually someone watching, especially at this time
[18:10] <angusthefuzz> or "Divine masters of the universe...hear me!"
[18:17] <francisco_t> Hello, what is the package that copies the .bashrc into the home user?
[19:19] <murdok> hi
[19:20] <murdok> someone please triage bug 284632. thanks :)
[19:25] <mnemo> i just upgraded to intrepid and now skype is broken --> https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/288269
[19:25] <mnemo> can someone repro this bug? if so, then maybe it should be considered for intrepid
[19:27] <ogra> unlikely
[19:27] <ogra> RC is later today, only really critical bugs will get fixing before release
[19:32] <joaopinto> mnemo, I am having the same issue with skype
[19:32] <angusthefuzz> would bug 288257 be considered a support request?
[19:33] <joaopinto> but I didn't played with it yet, I hope such a mainstream app had some testing
[19:33] <bdmurray> skype works for me fwiw
[19:34] <mnemo> joaopinto and bdmurray: can you add your hardware etc and whether it works for you as comments
[19:34] <greg-g> angusthefuzz: not necessarily, there could be a bug in cups that is causing it
[19:34] <mnemo> ogra: okay, but maybe it can be fixed after release at least
[19:34] <charlie-tca> murdok: Arne Goetje set it back to new, Isn't he the maintainer?
[19:35] <ogra> thats more liklely than before
[19:35] <angusthefuzz> greg-g: that was my other option, and thats why I asked, i am still new at this
[19:35] <greg-g> angusthefuzz: no worries, thats why we're here, to answer questions :)
[19:35] <joaopinto> mnemo, do you get ALSA lib ../../../src/pcm/pcm.c:2156:(snd_pcm_open_conf) Cannot open shared library /usr/lib32/alsa-lib/libasound_module_pcm_bluetooth.so on the terminal ?
[19:35] <angusthefuzz> greg-g: is there something I should use to differentiate support from a cups bug.  That particular report does not have very much info
[19:35] <joaopinto> I just tested it from the terminal right now
[19:36] <murdok> charlie-tca, hmm i have not checked it. anyways the bug has a patch and workaround
[19:36] <bdmurray> murdok, charlie-tca: Arne is
[19:37] <greg-g> angusthefuzz: there is a debugging help page for cups at https://wiki.ubuntu.com/DebuggingPrintingProblems
[19:37] <charlie-tca> So do we set it triaged for him if he set it to new?
[19:37] <greg-g> angusthefuzz: this is a good resource for those types of help docs: https://wiki.ubuntu.com/BugSquad/KnowledgeBase
[19:38] <angusthefuzz> greg-g: thanks, I was looking at the documents, I guess I just needed to choose whether to go the support route or the cups bug route
[19:38] <joaopinto> mnemo, changing the device to pulseaudio fixed for me
[19:39] <greg-g> angusthefuzz: gotcha.  general rule is that if you are unsure, treat it like a bug and try to gather the required information, if it turns out it isn't a bug, you can always convert it to a question at a later date.
[19:39] <charlie-tca> bdmurray: do I triage it, if Arne set it to new instead of confirmed?
[19:39] <angusthefuzz> greg-g: exactly what I was looking for, thanks!
[19:39] <greg-g> angusthefuzz: you're welcome, thanks for helping!
[19:41] <bdmurray> charlie-tca: on what basis would you confirm it?
[19:42] <charlie-tca> That there is a patch awaiting upload
[19:43] <charlie-tca> per Arne's comment - "has not been uploaded to Ubuntu yet"
[19:43] <charlie-tca> or am I reading something that doesn't exist?
[19:46] <bdmurray> charlie-tca: I was reading it as Arne wasn't certain as to the impact the patch would have, but I think Confirmed would be fine.
[19:48] <charlie-tca> Thank you, bdmurray . I'll confirm then for murdok
[19:50] <charlie-tca> murdok: done
[19:56] <murdok> charlie-tca, okay thanks
[19:57] <murdok> :Ð
[19:58] <charlie-tca> You're welcome. I'm glad I could help.
[20:23] <reaby> i'm facing problems now and then in xorg when logging out. now i get again full text-screen filled with different color of blocks and i need to sysrq-k to gain tty control of system. what should i include to bugreport, and do i need to do backtrace and how to do it.
[20:24] <reaby> system is now in state after sysrq-k
[20:33] <angusthefuzz> reaby: xorg.conf and Xorg.0.log for starters, also maybe the output of lspci
[20:35] <reaby> angusthefuzz: ok, dmesg has nice error for compiz.real, that may interest also. does kdm log errors somewhere ?
[20:36] <angusthefuzz> reaby: I believe kdm logs in /var/log/kdm/:0.log
[20:37] <reaby> ok, i'll check if there's some errors
[20:38] <reaby> nope, that dir doesn't exist
[20:43] <angusthefuzz> reaby: try /var/log/kdm.log
[20:44] <reaby> i'm blind. =) thanks. but it's empty, so no help for bug.
[20:45] <reaby> i try to find what triggers the bug, as sometimes it doesn't appear.
[20:46] <reaby> found out that using xv maybe triggers it, but sometimes it doesn't. Now i played frets on fire and logout --> got the bug. i believe there's something with the new ati fglrx and compiz.
[20:47] <reaby> but no body else didn't have bug report on the topic, so maybe it's not reproducable on other systems.
[20:48] <angusthefuzz> reaby: It deserves a bug report, please post all the information you gathered and we will take a look at it
[20:49] <reaby> k
[20:57] <askand1> How do I report bugs against software in a PPA?
[20:57] <askand1> In this case, calcs openoffice PPA
[21:45] <askand1> How do I report bugs against software in a PPA? In this case, calcs openoffice PPA
[22:02] <afflux> askand1: you don't, unless he set up a special project for that.
[22:12] <azimout> if warning someone trolling the comments in a bug report doesn't make him/her stop, what other measures do we have?
[22:14] <crimsun> the blessed virtual ignore.
[22:21] <jernst> hello can someone help me produce my first debdiff (a one liner change in a .desktop file) ?
[22:22] <jernst> I'm trying to follow https://wiki.ubuntu.com/Bugs/HowToFix but I am stucked
[22:22] <askand1>  jernst: where are you stuck? :)
[22:22] <jernst> I'd like to propose a debdiff for https://bugs.launchpad.net/ubuntu/+source/ntfs-config/+bug/124654 (and other simple bugs to start)
[22:23] <jernst> in the wiki number 2. says I have to dget a .dsc file
[22:23] <jernst> but I don't understand how I am supposed to find the correct url
[22:23] <jernst> so I tried apt-get source but don't know if it's correct
[22:23] <askand1> hm yeah.. I have never done that I think.. I get the source with apt-get source ntfs.config
[22:24] <jernst> ok that's what I did
[22:24] <crimsun> you need to regenerate the source package
[22:24] <jernst> then I fixed the .desktop file
[22:24] <crimsun> you can then generate a debdiff against the old and new dscs
[22:24] <jernst> made dch -i
[22:24] <jernst> but debuild -S shows errors
[22:25] <jernst> debian/rules:3: /usr/share/cdbs/1/rules/debhelper.mk: no such file or directory
[22:25] <askand1> jernst: You havent forgotten to add to the changelog first? It is very important :)
[22:25] <jernst> yes I added a line in the changelog with dch -i
[22:28] <askand1> do you have cdbs installed?
[22:28] <askand1> jernst: Im not sure it will help but its an idea :)
[22:29] <jernst> if didn't help but sudo apt-get build-dep ntfs-config did let me go a little bit further
[22:29] <askand1> how far this time?
[22:30] <jernst> hmm it complained that I have no signature so I used
[22:30] <jernst> debuild -S -us -uc and it seems to have generated a new .dsc
[22:31] <askand1> is its name new.dsc? :O
[22:31] <jernst> ntfs-config_0.5.5-0ubuntu2.dsc
[22:32] <askand1> ah
[22:32] <askand1> then I think its time for debdiff?
[22:32] <askand1> debdiff oldversion.dsc newversion.dsc > newversion.debdiff
[22:32] <jernst> yep, I will attach it to the bug, if you can take a look at it and tell me if it's ok that'd be nice
[22:33] <askand1> sure
[22:33] <jernst> or maybe I should test my change first
[22:35] <jernst> it works, time to attach the debdiff
[22:35] <askand1> nice! congratulations :)
[22:35] <jernst> I've attached it to https://bugs.launchpad.net/ubuntu/+source/ntfs-config/+bug/124654
[22:37] <askand1> To me it looks fine but someone else should propably take a look to :) im quite a newbie myself on this
[22:38] <jernst> ok, can you tell me what is the process to make someone who had the right to commit change have a look at it ?
[22:38] <jernst> never mind I should read the wiki page until the end
[22:45] <jernst> ok I'v subscribed ubuntu-universe-sponsors
[22:45] <jernst> thanks askand1
[22:46] <askand1> jernst: your welcome, thank you for fixing bugs that everyone will benefit from
[22:47] <jernst> that's a really trivial patch, but it's nice to start with low hanging fruits