[00:05]  * BUGabundo1 goes to bed
[00:56] <bcurtiswx> hey all, where the information on what hooks are available?
[01:57] <bcurtiswx> whats ubuntus default window decorator?
[01:58] <bcurtiswx> its now metacity is it?
[01:58] <bcurtiswx> not*
[02:22] <dtchen> bcurtiswx: depends whether compiz is enabled
[02:31] <bcurtiswx> dtchen: bug #377761 is what im trying to work through
[02:31] <ubot4> Launchpad bug 377761 in linux "UNR: Desktop Icons wont display and right click does not work after desktop mode switch" [Undecided,New] https://launchpad.net/bugs/377761
[02:34] <bcurtiswx> dtchen: i can't reproduce it with my UNR
[02:40] <bcurtiswx> wow OOo bug tracker is horrible
[02:53] <dtchen> bcurtiswx: i'm not local to hardware to verify the bug
[03:08] <greg-g> bcurtiswx: in your previous question, did you mean apport-hooks?
[03:08] <bcurtiswx> greg-g: yup
[03:09] <greg-g> are you looking for this? https://wiki.ubuntu.com/Apport/DeveloperHowTo
[03:10] <bcurtiswx> greg-g: not really. I am just looking for what hooks we have to use for bug reporters
[03:11] <micahg> bcurtiswx:  locate hooks | grep apport
[03:11] <bcurtiswx> micahg: ty, thats it :)
[06:09] <YoBoY> good morning
[06:36] <dholbach> good morning
[06:41] <YoBoY> hi dholbach :)
[06:42] <dholbach> hiya YoBoY
[06:48] <YoBoY> dholbach: the bugjam in paris was great, lot of new triagers (i think)
[06:49] <dholbach> YoBoY: awesome... you should write a blog post about it with some pictures!
[06:49] <YoBoY> ^^ i need a blog ... :p
[06:50] <dholbach> yeah
[06:50] <dholbach> does the french team participate in  https://wiki.ubuntu.com/TeamReports ?
[06:52] <YoBoY> i don't know... i'll ask didrocks today
[06:52] <dholbach> super
[08:15] <thekorn> good morning
[08:56] <YoBoY> dholbach: didrocks said me the french loco team don't participate at the moment on teamreports because a lacke of time, he'll write a post on the PU for the all Ubuntu-Party on Paris today
[08:58] <dholbach> YoBoY: it's easy to do it :)
[08:58] <dholbach> just takes a few moments
[08:58] <YoBoY> ^^"
[08:58] <dholbach> and a few lines about what you guys have been up to is usually good enough
[09:00] <YoBoY> ok, need some reading to see what it's required :)
[12:15] <PaulieG> hey, I need help with a issue with Jaunty. I had this issue with Gusty too but i cannot remember how to fix it. it is not the DPI. when i login the text when i type my username and password are so small it is unreadable. also when i run VLC media player the whole application is too small to read. also goes for virtualbox
[12:16] <BUGabundo> PaulieG: please refer to #ubuntu
[12:16] <BUGabundo> this # is for bug triage.
[12:16] <BUGabundo> thank you, and good look
[12:16] <BUGabundo> man... he quit too soon
[14:53] <joe-mac> is it a bug if this: http://www.pastie.org/481529 fails to parse with debconf-set-selections -c, however if i put the partman-auto-raid recipe all on one line, it parses, however fails at install time?
[15:05] <bddebian> Boo
[16:27] <xteejx> afternoon guys, just a quick thank you to everyone who voted +1 for my Bug control application and big thank you to Brian for accepting me! Much appreciated!
[16:36] <hggdh> xteejx, welcome
[16:36] <xteejx> hggdh, heya :)
[16:37] <hggdh> :-) Now you do not need to ask...
[16:37] <xteejx> hehe very true :)
[16:38] <xteejx> might still ask for a little direction if i'm not sure for a couple of weeks :)
[16:38] <hggdh> so it is welcome, both for for the thank you, and for -control
[16:38] <hggdh> xteejx, we all have doubts, so no problems. Just ask
[16:38] <xteejx> hggdh, thats kool
[16:39] <xteejx> trying to sort my own scanner out at the mo, sane isn't seeing it, have filed a bug though
[16:56] <xteejx> hggdh, bdmurray: I think there may be a misspelling in the wiki at https://wiki.ubuntu.com/Bugs/Responses#Debugging%20Sound%20Problems - souldn't the command be "apport-collect -p alsa-base BUGNUMBER" and not "apport-collect -p lalsa-base BUGNUMBER" - notice the L alsa-base the extra letter L  ??
[16:59] <charlie-tca> asac: Are you aware that thursday if going to be HugDay for firefox?
[17:02] <bdmurray> xteejx: yes, can you please fix it
[17:02] <xteejx> bdmurray: I can try :)
[17:03] <xteejx> bdmurray, done
[17:05] <bdmurray> xteejx: great, thanks for doing that!
[17:05] <xteejx> bdmurray, no probs :)
[17:50] <xteejx> bdmurray, hggdh,: With Ubuntu versions that reached their End of Life, do we support them with bug triaging/fixing or is it a kind "please upgrade and test" note?
[17:56] <greg-g> xteejx: first step, of course, would be to see if you can reproduce the issue in Karmic/Jaunty, if not, say so on the bug and ask for others who had the problem previously to test (and set to incomplete).
[17:56] <xteejx> greg-g: thanks, just making sure :)
[17:57] <micahg> xteejx: I added this to the wiki: https://wiki.ubuntu.com/Bugs/Responses#Distro%20has%20reached%20EOL
[17:57] <greg-g> xteejx: yep :)
[17:57] <micahg> but bdmurray asked that if there is a good test case to preserve it
[17:57] <greg-g> nice, micahg
[17:57] <xteejx> micahg: I've been using that one - I usually reword them slightly but yeah :)
[17:58] <xteejx> I thought we didn't support the EOL versions, obviously we do to some degree lol
[17:59] <micahg> xteejx: It's not necessarily a matter of supporting the EOL versions, but rather making sure the bugs aren't present in teh release versions as I understand it
[17:59] <charlie-tca> We don't support the EOL versions, but if the bug is still in the current version, we have to fix it
[17:59] <xteejx> micahg, charlie-tca: of course
[18:00] <xteejx> i may have invalidated one EOL bug, but i did say if it's still a problem in a supported version reopen it and set to new
[18:01] <micahg> xteejx: also, sometimes the user upgrades without updating the bug
[18:02] <xteejx> micahg: if they cant supply the info within 3 months its invalid anyway isnt it?
[18:02] <xteejx> after they have been asked obviously
[18:03] <hggdh> by rule of thumb, if the reporter (or others commenters) does not provide any updates, and we have asked, for it, and it has been quite some time... then yes, you can close invalid, and state to please reopen if still experiencing it, etc, etc
[18:04] <xteejx> hggdh: of course, just checking heh :)
[18:07] <hggdh> :-)
[18:07] <hggdh> always good to check, no problems. Gives all of us opportunity to review & reconsider
[18:08] <xteejx> hggdh: :)
[18:49] <asac> charlie-tca: nope. thanks for the reminder ... better ping me on thu ;)
[18:52] <charlie-tca> asac: okay
[19:18] <VilasBoas> hy does anyone knows how to enable the wireless on the network manager
[19:18] <bencrisford__> yeah
[19:19] <bencrisford__> this isnt a support channel, normally try ubuntu, but i will help you now you're here
[19:19] <bencrisford__> do you have a network manager icon on your top-panel?
[19:19] <VilasBoas> yes
[19:19] <bencrisford__> right click it
[19:19] <bencrisford__> there should be a tickbox for wireless
[19:20] <VilasBoas> yes but i can't activate the wireless on that bottun
[19:20] <bencrisford__> you have a wireless card though?
[19:21] <bencrisford__> that is compatible
[19:21] <VilasBoas> yes i have a  Network controller: Intel Corporation PRO/Wireless LAN 2100 3B Mini PCI Adapter (rev 04)
[19:23] <bencrisford__> if it is connected up correctly and the drivers are installed i dont see why it wont work
[19:23] <bencrisford__> try #ubuntu
[19:23] <bencrisford__> if no-one there can help
[19:23] <bencrisford__> report it as a bug
[19:23] <bencrisford__> when in doubt - report it, and if it is invalid it wont get triaged :)
[19:24] <VilasBoas> i already did but no result
[19:25] <bencrisford__> you reported it or went to #ubuntu
[19:25] <VilasBoas> i reported on LP
[19:25] <Ampelbein> VilasBoas: can you give the bug number?
[19:26] <Ampelbein> VilasBoas: the 2100 is widely used and should work ootb.
[19:30] <VilasBoas> Ampelbein: https://bugs.launchpad.net/ubuntu/+bug/292266
[19:30] <ubot4> Launchpad bug 292266 in ubuntu "I can't enable my wireless (bug 283925)" [Undecided,New]
[19:32] <Ampelbein> VilasBoas: does it work when you enable wireless in the bios? if so, it could be an issue with the wifi-button not being recognized
[19:32] <VilasBoas> no
[19:33] <VilasBoas> it doesn't work when i enable the wireless on the bios
[19:35] <Ampelbein> VilasBoas: could you give a dmesg when wifi is enabled in bios? please attach the dmesg to the bugreport, not paste it in a comment. it's easier to read as an attachment.
[19:37] <VilasBoas> ok i will reboot my pc and i will attach the dmesg
[19:38] <Ampelbein> VilasBoas: thanks.
[20:17] <xteejx> Bug 103374 is quite old, I set it to Incomplete, asked if it's still a problem in Jaunty, and it appears not to be. Should I now mark this Fix Released. I know the procedure is to do so with an explanation why, but in this instance it's a metabug and has quite a few dupes, help?
[20:17] <ubot4> Launchpad bug 103374 in language-selector "[apport] qt-language-selector crashed with TypeError in _()" [Undecided,Incomplete] https://launchpad.net/bugs/103374
[20:18] <xteejx> hggdh, bdmurray: ^^?
[20:25] <xteejx> Anyone in?
[20:31] <Ampelbein> xteejx: I'd set it to Invalid, with https://wiki.ubuntu.com/Bugs/Responses#Bugs%20resolved%20after%20update%20or%20config%20change as response. Most likely there is no dedicated fix for this and only is working now because of some unrelated code-changes.
[20:32] <Ampelbein> (unrelated meaning not specifically written to fix the issue described)
[20:32] <xteejx> Ampelbein, I was thinking that, as there is no obvious reason it was fixed :)
[20:43] <charlie-tca> hggdh: I gave 200 new bugs to start our bug day: https://wiki.ubuntu.com/UbuntuBugDay/20090521
[20:43] <charlie-tca> I'll send emails out tomorrow, but I think I missed the news letter already :-)
[20:47] <xteejx> would it be possible to get a bugday for the 12000 new bugs that have a package assigned but nothing done with them? I'm working through them slowly but surely
[20:54] <charlie-tca> Those should be "new" of all source packages? Each bug day works those bugs for that target package
[20:57] <micahg> hggdh: now I have to check the wiki when I do my firefox triaging :)
[20:59] <hggdh> heh
[21:00] <micahg> xteejx: I'm wondering if it's not better to do them one package at a time so that the package maintainers or whoever can then manage the new ones coming in
[21:00] <micahg> hggdh: I probably did 50 of those incomplete ones over the weekend
[21:01] <xteejx> I suppose so yeah, at least devs know they're gonna get a lot from a bug day
[21:01] <xteejx> advanced notice i guess#
[21:01] <hggdh> ah well... micahg, would you mind marking them as done?
[21:01] <micahg> hggdh: they're not necessarily done yet, I'm waiting for users to respond
[21:02] <micahg> I cuold mark them if that's considered done
[21:02] <hggdh> and -- of course, the list is already open... no need to wait for the hugday
[21:02] <charlie-tca> I just generated that list thismorning
[21:02] <BUGabundo> guud evening
[21:03] <charlie-tca> Hello, BUGabundo
[21:03] <hggdh> micahg, yes, it is considered done. Of course, having closure would be better (and, per what charlie-tca just wrote, yours may not even be there)
[21:03] <BUGabundo> hello my friend(s)
[21:03] <hggdh> boas, BUGabundo
[21:03] <micahg> charlie-tca: I'm saying that I changed the status over the weekend for about 50 of the incomplete ones from New to Incomplete
[21:04] <charlie-tca> I just did the list about 4 hours ago. Any you made incomplete will be in the incomplete list
[21:04] <micahg> yep :)
[21:04] <micahg> I was wondering if I sould mark them done
[21:04] <micahg> since I"m waiting for feedback already
[21:04] <BUGabundo> seb128: hi!
[21:04] <charlie-tca> I you want to.
[21:04] <BUGabundo> seb128: two things!
[21:04] <BUGabundo> 1st https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/377276/comments/5
[21:04] <seb128> hey BUGabundo
[21:04] <charlie-tca> Saves someone else looking each one up, then
[21:04] <ubot4> Launchpad bug 377276 in gvfs "gvfs-gdu-volume[30181]: segfault at 18 (dup-of: 376145)" [Medium,Incomplete]
[21:04] <ubot4> Launchpad bug 376145 in gvfs "gvfs-gdu-volume-monitor crashed with SIGSEGV in gdu_pool_get_presentables()" [Medium,Triaged]
[21:04] <micahg> that way, someone can work on a bug that no one is monitorinf yet
[21:05] <charlie-tca> yeah, good ideal
[21:05] <charlie-tca> s/ideal/idea
[21:05] <micahg> I'll do it later tonight
[21:05] <BUGabundo> seb128: 2nd I need your help debugging why the Open Dialog of nautilus
[21:05] <charlie-tca> Thanks, micahg
[21:05] <seb128> BUGabundo: it's a bit disappointing that you don't use apport to send crashes
[21:05] <BUGabundo> takes FOR EVER to open now with 2.27.1
[21:05] <BUGabundo> seb128: now I have apport
[21:05] <BUGabundo> see the new bug
[21:05] <BUGabundo> it never fired before
[21:06] <seb128> it was not enabled
[21:06] <BUGabundo> seb128: now it is
[21:06] <seb128> but I would expect that you would know about it with the number of bugs you open
[21:06] <BUGabundo> I thought devel (karmic) would auto enable it
[21:06] <BUGabundo> I manually set it
[21:06] <BUGabundo> seb128: *all* bugs I file are done with apport
[21:06] <seb128> it will when we will be ready to get ton of bugs
[21:06] <BUGabundo> when I know the package
[21:06] <seb128> but right now karmic bugs are not really useful
[21:06] <BUGabundo> seb128: now I have it on, so new crashs will fire it up
[21:07] <seb128> many will be fixed in autosync and updates before we will manage to work on those
[21:07] <BUGabundo> seb128: nevermind... stupid me! though it would be ON before alpha1... life and learn!
[21:07] <seb128> ;-)
[21:07] <BUGabundo> so is the new apport crash any useful?
[21:07] <BUGabundo> or is it a plain dupe ?
[21:08] <seb128> it's plain duplicate
[21:08] <seb128> but apport autoclose duplicates so that's ok
[21:08] <BUGabundo> nice
[21:08] <BUGabundo> now the 2nd question seb128
[21:09] <BUGabundo> how can I debug why Open Dialog is *sooooo* slow ?
[21:09] <hggdh> (and... wait! There is more!)
[21:09] <BUGabundo> takes 4-5 secs to open
[21:09] <seb128> use gdb
[21:09] <BUGabundo> on Nautilius?
[21:09] <hggdh> yes
[21:09] <BUGabundo> or on gedit, for example?
[21:09] <seb128> run the software under gdb
[21:09] <BUGabundo> I see it on *any* app
[21:09] <chrisccoulson> BUGabundo - using tracker by any chance?
[21:09] <seb128> well, I don't see why using it on gedit would be useful if that's a nautilus issue ...
[21:09] <seb128> weird question
[21:09] <BUGabundo> ok... install gsbsyb of gedit and nautils
[21:10] <BUGabundo> chrisccoulson: know prob?
[21:10] <BUGabundo> I have tracker active
[21:10] <seb128> if that's the fileselector being slow I would bet on tracker too
[21:10] <BUGabundo> and also google desktop
[21:10] <seb128> gdb will tell you
[21:10] <chrisccoulson> i'm seeing loads of reports with your issue from people using tracker, who claim it goes away when stopping tracker
[21:10] <seb128> I've seen stracktraces indicating that
[21:10] <chrisccoulson> it seems trackerd is hanging, and not servicing any requests over the message bus
[21:10] <seb128> run the software under gdb
[21:10] <BUGabundo> seb128: I just mentioned gedit, because its an easy way to trigger it
[21:10] <seb128> while it's hanging do ctrl-c on gdb
[21:10] <seb128> and backtrace
[21:11] <chrisccoulson> and for some reason opening the gtk file chooser seems to communicate with tracker
[21:11] <BUGabundo> ok
[21:11] <seb128> BUGabundo: you said it was a nautilus open with dialog, that dialog is not a gtk fileselector
[21:11] <BUGabundo> let me get the gdbsym packages
[21:11] <chrisccoulson> i'm seeing the issue here and trying to debug it, but you might be seeing a different one
[21:11] <BUGabundo> humm seb128 you are consufing me now
[21:11] <seb128> chrisccoulson: some reason being the "find" item in the sidebar
[21:12] <chrisccoulson> ugh. that's probably what's causing it then - the hanging trackerd process stays on the bus so other apps think it's there. they try and communicate with it and wait for it to respond, which it never does because it's hung
[21:12] <seb128> right
[21:12] <BUGabundo> humm so that's what I'm expericing ?
[21:13] <seb128> BUGabundo: if you would describe your bug clearly we could say
[21:13] <BUGabundo> ok
[21:13] <BUGabundo> let me try again
[21:13] <seb128> BUGabundo: is your issue with the "open with" nautilus dialog or with file selectors?
[21:13] <BUGabundo> Its not Open With...
 how can I debug why Open Dialog is *sooooo* slow ?
[21:13] <seb128> that is not clear
[21:13] <seb128> what dialog is that?
[21:13] <BUGabundo> its the Open... Dialog box for opening files inside other apps
[21:14] <BUGabundo> like the gedit one
[21:14] <seb128> how do you open it?
[21:14] <BUGabundo> or Pidgin... any
[21:14] <seb128> that's a gtk fileselector
[21:14] <BUGabundo> ctrl+o
[21:14] <BUGabundo> ok now we are set on the app
[21:14] <seb128> ctrl-o in nautilus does nothing
[21:14] <seb128> nautilus is a file browser
[21:14] <seb128> it doesn't have an "open file" dialog
[21:15] <BUGabundo> grr
[21:15] <BUGabundo> we are out of sync
[21:15] <BUGabundo> or I'm not explaining as good as I wish
[21:15] <BUGabundo> I open gedit
[21:15]  * chrisccoulson wonders if the sqlite SRU has broken tracker
[21:15] <seb128> or, so it's simply a fileselector dialog
[21:15] <BUGabundo> then ctrl+o (for File->Open...)
[21:15] <seb128> not sure why you mentioned nautilus
[21:16] <seb128> that's probably a tracker bug
[21:16] <BUGabundo> yes seb128. as you said: gtk file selector
[21:16] <seb128> anyway
[21:16] <seb128> gdb gedit
[21:16] <seb128> (gdb) run
[21:16] <BUGabundo> seems to be the app causing me slow down
[21:16] <seb128> ctrl-o
[21:16] <BUGabundo> ok
[21:16] <BUGabundo> brv
[21:16] <BUGabundo> *brb
[21:16] <seb128> switch to gdb while it's being slow, ctrl-C
[21:16] <seb128> (gdb) backtrace
[21:16] <chrisccoulson> you also could prove it quickly by just doing killall trackerd and trying again
[21:17] <BUGabundo> $ sudo aptitude install gedit-dbgsym nautilus-dbgsym tracker-dbgsym
[21:17] <chrisccoulson> if its not on the bus then the file chooser doesn't try and talk to it;)
[21:18] <seb128> no need of debug symbols
[21:19] <BUGabundo> oh  no?
[21:19] <BUGabundo> now you tell me
[21:19] <BUGabundo> a simple backtrace is enough?
[21:19] <BUGabundo> okay
[21:20] <seb128> it's enough to say if it's due to tracker or not yes
[21:21] <BUGabundo> I was not fast enough now
[21:21] <BUGabundo> http://paste.ubuntu.com/175172/
[21:21] <BUGabundo> the ctrl+c was to slow!
[21:21] <seb128> no you were not
[21:21] <BUGabundo> why do stuff gets faster on gdb?
[21:21] <seb128> they don't
[21:21] <seb128> you are just being lucky ;-)
[21:22] <BUGabundo> here is the bt
[21:22] <BUGabundo> http://paste.ubuntu.com/175175/
[21:22] <chrisccoulson> that looks normal there
[21:22] <chrisccoulson> it didn't hang that time no?
[21:23] <BUGabundo> no
[21:23] <BUGabundo> let me try again
[21:23] <BUGabundo> now its going faster
[21:23] <BUGabundo> I run a fsck before boot
[21:23] <BUGabundo> could be related
[21:24] <BUGabundo> so now I can't reprocude the slow down
[21:24] <seb128> could have been due to tracker being in a weird state
[21:24] <chrisccoulson> BUGabundo - do you run tracker though? if you do then it's likely the same issue
[21:25] <seb128> would not happen after a fresh boot
[21:25] <chrisccoulson> for me trackerd is hanging repeatedly after 5 minutes or so, and causes this behaviour
[21:25] <BUGabundo> yeah I've been using my laptop after several hivernates ad suspends
[21:25] <BUGabundo> this is now a fresh boot
[21:25] <chrisccoulson> and several other people reported the same thing today too
[21:25] <BUGabundo> tracker could have not be in a good state after so many hibernates
[21:25] <BUGabundo> I know PA wasnt
[21:26] <BUGabundo> !w
[21:26] <ubot4> Factoid 'w' not found
[21:26] <BUGabundo> 21:26:19 up 46 min,  3 users,  load average: 0.43, 0.54, 0.98
[21:26] <BUGabundo> USER     TTY      FROM              LOGIN@   IDLE   JCPU   PCPU WHAT
[21:26] <BUGabundo> bugabund tty7     :0               20:40   45:59   5:50   3.45s gnome-session
[21:26] <BUGabundo> bugabund pts/0    :0.0             20:41    1:37   4.13s  1.73s /usr/bin/gedit
[21:26] <BUGabundo> bugabund pts/1    :0.0             21:25    1:05   0.29s  0.29s bash
[21:26] <seb128> bug #377899
[21:26] <ubot4> Launchpad bug 377899 in tracker ""File Open" dialogues for gedit, etc., take 25 seconds to appear" [Medium,Confirmed] https://launchpad.net/bugs/377899
[21:29] <BUGabundo> yay I can reproducably crash compiz moving my mouse
[21:29] <BUGabundo> and mvo still not around
[21:29] <chrisccoulson> BUGabundo - you should stop moving your mouse;)
[21:30] <BUGabundo> I don't use it that much
[21:30]  * BUGabundo hates mice, loves DO
[21:30] <seb128> we should not let people upgrade to karmic so early ;-)
[21:30] <chrisccoulson> hehe
[21:30] <chrisccoulson> even i've not taken the plunge yet
[21:30] <BUGabundo> seb128: how early?
[21:30] <chrisccoulson> i'm only running it in a VM
[21:30] <BUGabundo> I did it 1,5 weeks after JJ release
[21:31] <seb128> chrisccoulson: me too on my laptop, I've my desktop upgraded though
[21:31] <BUGabundo> for me its bare metal...
[21:31] <BUGabundo> more HW debug
[21:31] <seb128> I need my laptop to work until UDS
[21:31] <seb128> ie suspend working, beamer working, not crashing
[21:31] <BUGabundo> those do work
[21:31] <BUGabundo> but I have this anoyng acpi/kernel bug
[21:31] <chrisccoulson> seb128 - yeah, i need my desktop to work because i'm not the only one to use it. but i might upgrade in a couple of weeks or so ;)
[21:32] <seb128> BUGabundo: dunno, after UDS, at least until then bugs are not being actively worked because people are busy catching up, traveling, doing UDS, etc
[21:32] <BUGabundo> if I change power source during suspend or hibernate or resume process
[21:32] <BUGabundo> it will fail to resume X
[21:32] <seb128> so we get ton of bugs which are auto-deprecated by new versions before we look at them but create lot of bug triaging work
[21:32] <BUGabundo> I should file it
[21:32] <BUGabundo> but it very hard to debug it
[21:33] <chrisccoulson> hey seb128 - i did the gnome-applets update at the weekend. i'll push it in to bzr shortly
[21:33] <seb128> chrisccoulson: I tend to start by upgrading GNOME but not linux or xorg ;-)
[21:33] <seb128> usually GNOME upgrades are okish
[21:33] <chrisccoulson> yeah, and bad gnome updates are easy to recover from too
[21:33] <seb128> indeed ;-)
[21:33] <seb128> I'm not woried about GNOME
[21:34] <seb128> changes are small and you can still use your computer with GNOME applications crashing
[21:34] <seb128> as long as it's not gnome-session or nautilus respawning
[21:34] <chrisccoulson> yeah, that would not be so good
[21:34] <BUGabundo> or bad libs
[21:34] <BUGabundo> I've caugh one of those on JJ cycle
[21:34] <chrisccoulson> hmmmm. the new version of tracker has the same hanging issue too
[21:34] <BUGabundo> luclky you fixed it fast
[21:35] <BUGabundo> guess I need to open a bug, and talk to either ogasawara or bryce about this
[21:36] <BUGabundo> who handles acpi ?
[21:36] <chrisccoulson> kernel people ;)
[21:36] <BUGabundo> then ogasawara or apw again
[21:36] <BUGabundo> eheh
[21:37] <BUGabundo> chrisccoulson: you make it sound like they are a different race
[21:37] <BUGabundo> ehehee
[21:37] <BUGabundo> "kernel ppl" LOL
[21:40] <BUGabundo> ogasawara: apw: are any of you here?
[21:41] <BUGabundo> so chrisccoulson do you have a master bug for the tracker issue?
[21:41] <chrisccoulson> yeah, the one seb128 pointed out earlier ;)
[21:41] <chrisccoulson> bug 377899
[21:41] <ubot4> Launchpad bug 377899 in tracker ""File Open" dialogues for gedit, etc., take 25 seconds to appear" [Medium,Confirmed] https://launchpad.net/bugs/377899
[21:41] <xteejx> bug 106926 : confused about this one, theres 2 assignments to linux and kde-multimedia, 2 separate statuses, what should I do with this?
[21:41] <ubot4> Launchpad bug 106926 in linux "Kmix volume/mute does not affect all channels" [Undecided,Confirmed] https://launchpad.net/bugs/106926
[21:42] <BUGabundo> chrisccoulson: missed it
[21:43] <BUGabundo> and now FF is crashing... good
[21:43] <chrisccoulson> excellent!
[21:43] <BUGabundo> its an old old bug
[21:44] <BUGabundo> FF segfaults when opening from another up, and already running
[21:44] <BUGabundo> since beginning JJ
[21:44] <xteejx> anyone?
[21:44] <BUGabundo> fta did some magic but never fixed it
[21:44] <BUGabundo> :(
[21:50] <xteejx> Dont worry I sorted it
[21:52] <chrisccoulson> BUGabundo - if you're interested in tracker btw, i have packaged a snapshot of git master in my PPA
[21:52] <chrisccoulson> it will be in karmic soon once it's settled down a little
[21:53] <BUGabundo> I'll wait
[21:53] <chrisccoulson> hehe
[21:53] <BUGabundo> I'm cutting edge but I like to test stuff other ppl have too
[21:53] <chrisccoulson> its much better than whats in karmic even in its current form ;)
[21:54] <BUGabundo> if they can't reproduce it, I have trouble filing a bug
[21:54] <BUGabundo> eheh
[21:54] <BUGabundo> ok ok I'm sold
[21:54] <BUGabundo> link?
[21:54] <chrisccoulson> https://edge.launchpad.net/~chrisccoulson/+archive/tracker
[21:54] <chrisccoulson> i shall be keeping it regularly updated for now
[21:55] <BUGabundo> ok
[21:55] <seb128> chrisccoulson: you are welcome to do the regular updates in karmic directly if you want ;-)
[21:55] <chrisccoulson> seb128 - yeah, i don't mind doing that
[22:00] <xteejx> whats this tracker thing?
[22:00] <BUGabundo> May 18 22:00:29 blubug kernel: [ 4811.434737] gvfs-gdu-volume[27690]: segfault at 18 ip 00007f23eb4ab2f1 sp 00007fff06bae0b0 error 4 in libgdu.so.0.0.0[7f23eb4a0000+22000]
[22:00] <BUGabundo> huuuuu
[22:01] <BUGabundo> getting my logs flooded with this
[22:01] <BUGabundo> 10 per sec
[22:05] <BUGabundo> chrisccoulson: seb128: do you think that this gvfs bug could be causing my trouble with slow down from usb to usb data transfer?
[22:06] <BUGabundo> as I mention on bug 378083
[22:06] <ubot4> Launchpad bug 378083 in gvfs "gvfs-gdu-volume-monitor crashed with SIGSEGV in gdu_pool_get_presentables() (dup-of: 376145)" [Undecided,New] https://launchpad.net/bugs/378083
[22:06] <ubot4> Launchpad bug 376145 in gvfs "gvfs-gdu-volume-monitor crashed with SIGSEGV in gdu_pool_get_presentables()" [Medium,Triaged] https://launchpad.net/bugs/376145
[22:06] <seb128> dunno, I'm not using karmic yet!
[22:07] <BUGabundo> only appeared for me on karmic
[22:07] <seb128> copy speed is subjective and  a topic being discussed for years
[22:07] <BUGabundo> but I'm cc to an older bug where the user has the same symptons
[22:07] <seb128> try copying from a command line and see how it goes
[22:07] <BUGabundo> seb128: I have no trouble if it is usb->intenar disk or vv
[22:08] <BUGabundo> just usb -> usb
[22:08] <BUGabundo> rsync will show ~1MiB/s
[22:08] <BUGabundo> when internal can get 30MiB/s
[22:08] <IngForigua> Hello
[22:08] <BUGabundo> nautilus transfer dialog shows the same values
[22:08] <BUGabundo> IngForigua: please not here!
[22:08] <seb128> what about cp on a command line?
[22:09] <BUGabundo> does cp show speed?
[22:09] <seb128> no, but you should be able to do simple maths and dividing the number of megabytes but the number of seconds?
[22:10] <seb128> but -> by rather
[22:10] <seb128> ie "look at how much you are copying and how long it takes in seconds"
[22:10] <IngForigua> jejejejeje ok BUGabundo, then were i can ask :(
[22:10] <BUGabundo> IngForigua: see +1!
[22:11] <IngForigua> very good :)
[22:11] <BUGabundo> seb128: sure I can!
[22:12] <BUGabundo> ahhhh netspeed applet broken again
[22:12] <BUGabundo> why can't they keep it working for 6 months?
[22:12] <seb128> it didn't change for ages it's likely a linux or driver issue
[22:13] <BUGabundo> seb128: it changed for kk
[22:14] <BUGabundo> new skin, doesn't allow to change font size anymore
[22:14] <BUGabundo> I filed a bug and upstreamed it
[22:14] <BUGabundo> now it takes 20 % of my screen size with current font size
[22:14] <BUGabundo> I had it on 7px
[22:15] <BUGabundo> but I guess it could be driver
[22:15] <BUGabundo> but I see the upload speed error on both wired and wifi
[22:15] <seb128> I doubt the applet code changed a lot
[22:16] <seb128> the linux interfaces changed maybe though
[22:16] <BUGabundo> I need to track this down
[22:16] <BUGabundo> current state is useless
[22:17] <BUGabundo> it says I'm uploading at 200KiB/s
[22:17] <seb128> you should perhaps not upgrade to karmic so early ;-)
[22:17] <BUGabundo> both nethogs and tcptrack say no
[22:17] <BUGabundo> seb128: if I didn't I wouldn't find all this bugs
[22:17] <seb128> do you find anybody to look at all those bugs?
[22:17] <BUGabundo> and get them filed, triagged and fixed (by devs) before release, would I ?
[22:18] <seb128> I've the feeling we waste efforts looking at bugs so early in the cycle
[22:18] <BUGabundo> really?
[22:18] <seb128> yes
[22:18] <BUGabundo> don't even upstream need to know them?
[22:18] <seb128> but that's only my opinion
[22:18] <BUGabundo> I know kdepim gets them fixed
[22:18] <seb128> upstream needs to, but you report ubuntu bugs where people are busy doing merges, travelling, going to uds, etc
[22:18] <BUGabundo> but they are on another cycle
[22:19] <seb128> by the time you have ubuntu maintainers looking at those most of those issues  have deprecated by new upstream versions
[22:19] <seb128> at least for desktop
[22:19] <BUGabundo> I upstream them, now
[22:19] <seb128> ok, good
[22:19] <BUGabundo> like I did for the netspeed applet
[22:20] <seb128> I still think that the first month in the cycle get lof of breakages that autosolve by auto-syncing on debian
[22:20] <seb128> and by updates
[22:20] <seb128> ie it's less efforts and most efficient to way after uds to start looking at those
[22:21] <seb128> lot of the issues are due to early unstable versions or merges being worked
[22:21] <seb128> once everything stabilize you can start looking at what issue are still there
[22:21] <BUGabundo> seb128: even if its bad example for gnome, lots other packages benefic from early debug
[22:21] <BUGabundo> and testign
[22:22] <seb128> I'm surprised you find ubuntu people working on bugs so early in the cycle
[22:22] <seb128> usually maintainer are busy merging and fighting fires for alpha builds
[22:23] <seb128> I doubt the linux team is doing a lot of backport or bug fixing in an ubuntu specific way so early for example
[22:23] <seb128> they are probably busy being tracking what upstream is doing
[22:24] <BUGabundo> at least dtchen is working activly
[22:24] <BUGabundo> eheh
[22:25] <seb128> I'm not saying the desktop team is not working actively ;-)
[22:25] <seb128> just than merging on debian, preparing uds and updating to GNOME 2.27 means we have no time for bug work
[22:25] <BUGabundo> yeah I know
[22:25] <seb128> and by the time we will look at those bugs most will have auto-solved with new versions
[22:26] <seb128> which is why I tend to be not so nice and closing quickly bugs early in the cycle
[22:26] <BUGabundo>    http://bugzilla.gnome.org/show_bug.cgi?id=581804
[22:26] <ubot4> Gnome bug 581804 in general "netspeed applet no longer allows to set font size" [Minor,Unconfirmed]
[22:27] <seb128> I expect this one is probably an upstream choice
[22:27] <seb128> did you read the ChangeLog?
[22:27] <BUGabundo> see? I'm learning to be a better reporter
[22:27] <BUGabundo> let me check
[22:28] <seb128> well I've nothing against your work ;-)
[22:28] <seb128> I just wish people would give us a break sometime ;-)
[22:29] <seb128> opening bugs is not an issue if that would not be for the zillion duplicates and people not closing the bug when they noticed they get solved by an upgrade
[22:29] <BUGabundo> nothing on changelog or todo about I
[22:29] <seb128> that's just lot of paper work early in the cycle ;-)
[22:29] <BUGabundo> that's why I just file bugs other ppl can confirm
[22:29] <seb128> ok, so wait for an upstream comment, I don't know about this software
[22:30] <BUGabundo> I check for dupes too
[22:30] <BUGabundo> and try to have the complete information (like using apport to iniciate it )
[22:30] <seb128> right, it's not always easy to check for duplicates though
[22:30] <seb128> this gvfs crash for example has 5duplicates already for example
[22:30] <seb128> and you filed one of those ;-)
[22:31] <seb128> anyway nothing against you, keep the good work ;-)
[22:31] <seb128> I'm just trying to find a way to deal with the bug flood, we can't follow on this bugload and that's making the bug tracker pretty useless in some cases
[22:32] <apw> BUGabundo, a lot of us lot are travelling around now for one reason or another
[22:37] <BUGabundo> I understand apw and seb128
[22:37] <BUGabundo> I'm subbed to some packages bugmail... I know the feeling
[22:38] <BUGabundo> now to file a pidgin (apport crash) bug that I know upstream will close immediately
[22:42] <BUGabundo> https://bugs.launchpad.net/ubuntu/+source/pidgin/+bug/378116
[22:42] <ubot4> BUGabundo: Error: This bug is private
[22:45] <BUGabundo> love how ppl describe bugs https://bugs.launchpad.net/bugs/377926
[22:45] <ubot4> Launchpad bug 377926 in ubuntuone-client "I had a problem with UbuntuOne not being open source :( (dup-of: 375345)" [Undecided,New]
[22:45] <ubot4> Launchpad bug 375345 in ubunet ""Ubuntu One" name creates confusion" [Undecided,Incomplete]
[22:50] <xteejx> BUGabundo: lol just looked at that report....wtf?!
[22:50] <BUGabundo> btw seb128 you maintain pidgin right?
[22:50] <BUGabundo> and pidgin plugin ?
[22:50] <seb128> no
[22:50] <seb128> we don't have anybody working on that in ubuntu
[22:50] <BUGabundo> *we* (ubuntu and debian) need to update the pidgin-plugin pack
[22:51] <seb128> I tend to do version updates when there is a need for that but that's about it
[22:51] <BUGabundo> upstream *refuses* any bug with a 2 yo package
[22:51] <BUGabundo> there is a need for that
[22:51] <seb128> I don't know what this package is but it's not in the default install and I don't care about it
[22:51] <BUGabundo> I already have 2 bugs on it
[22:51] <yoasif_> having a weird bug on miro startup (karmic): https://bugs.launchpad.net/ubuntu/+source/miro/+bug/378120
[22:51] <BUGabundo> :(
[22:51] <ubot4> Launchpad bug 378120 in miro "miro crashes with Segmentation fault on startup" [Undecided,New]
[22:52] <BUGabundo> changing avatar is one confirmed and fixed upstream now
[22:52] <BUGabundo> 2.5.6 should fix it
[22:52] <seb128> BUGabundo: you are for sure using lot of weird softwares ;-)
[22:52] <seb128> I've changed my image recently and that works correctly on jaunty
[22:52] <Pollywog> is there going to be a bug stomping session soon?
[22:53] <BUGabundo> :((
[22:53] <BUGabundo> seb128: its related to a plugin
[22:53] <BUGabundo> not pidgin it self
[22:53] <BUGabundo> so the need to have a recent version
[22:53] <seb128> what is wrong with using pidgin as it's shipped in ubuntu?
[22:53] <BUGabundo> darkrain42: As you already know, the plugin pack is ridiculously out of date in ubuntu
[22:53] <BUGabundo> darkrain42: Try to reproduce it with the most recent version
[22:54] <seb128> anyway as said i've too much to do on ubuntu already
[22:54] <BUGabundo> I use the pidgin-pluginpack features
[22:54] <seb128> I don't care about universe crack options
[22:54] <BUGabundo> yeah seb128 sorry
[22:54] <seb128> try finding a motu who has interest in those
[22:54] <BUGabundo> I guess I need to bride some motu to maintain pidgin
[22:54] <seb128> pidgin is maintained
[22:54] <BUGabundo> humm now we are on sync ? eheh
[22:54] <seb128> that's only the crack option you are the only one to use which is not
[22:54] <BUGabundo> I meant pidgin-pluginpack
[22:55] <Pollywog> I can't encrypt files with kgpg in Jaunty on two machines, so I think it is a bug
[22:57] <seb128> BUGabundo: what option do you need in those?
[22:57] <BUGabundo> seb128: ?
[22:57] <seb128> why do you install this buggy thing?
[22:58] <BUGabundo> extra options
[22:58] <seb128> which ones?
[22:58] <seb128> I'm just trying to figure if that's something useful we should try to get in pidgin stock there
[22:58] <seb128> I've looked on the description and those seem mostly crack
[22:58] <BUGabundo> hum
[22:58] <BUGabundo> let me see
[22:59] <Pollywog> what is this crack you speak of?
[22:59] <BUGabundo> too many to least!
[22:59] <BUGabundo> at least 2 screen high size
[22:59] <BUGabundo> seb128: I can run it on --debug for you
[22:59] <seb128> ?
[23:00] <seb128> no, I was rather asking what option you would like to get in pidgin stock which is there
[23:00] <BUGabundo> brb reconnecting 3G modem
[23:00] <seb128> I'm not trying to debug the outdated universe version
[23:00] <seb128> BUGabundo: see you later
[23:00] <seb128> I'm going to bed now, traveling to Spain tomorrow for allhand and uds
[23:03] <BUGabundo1> back
[23:06] <BUGabundo1> oh seb is gone
[23:06] <BUGabundo1> never mind
[23:06] <BUGabundo1> I hear there's a pidgin PPA with more updated version
[23:06] <BUGabundo1> google to the rescue