[00:56] <calc> 1 bug to 100% watched on OOo :)
[02:36] <Ampelbein> maco: ping about bug #291268
[02:36] <maco> hi
[02:36] <maco> are you andreas moog?
[02:36] <Ampelbein> maco: yupp
[02:36] <maco> ah ok
[02:36] <maco> i was thinking if its fixed in jaunty, then fx released would make more sense
[02:37] <Ampelbein> maco: generally i don't like fix released when i do not find a matching changelog entry
[02:37] <maco> (the letter that comes after h and before j = broken)
[02:37] <maco> oh ok
[02:37] <maco> was guessing "new upstream release" probably caught it
[02:37] <Ampelbein> perhaps it's just a coincidence and it worked here even before jaunty so i was asking the reporter to test again.
[02:38] <maco> right
[02:38] <Ampelbein> or it just happens with special email addresses... there are a couple of reasons i could think of why it works for me but not for him
[02:42] <torkiano> hello, powertop reports a lot of interrups of my graphic card
[02:43] <torkiano> I disabled 3d effects
[02:44] <torkiano> this only happens in kubuntu, in ubuntu the number of interrups are normal
[02:56] <maco> Ampelbein: i can reproduce t
[02:57] <maco> *it
[02:57] <Ampelbein> maco: how?
[02:57] <maco> did you put the email address in the email slot or the name slot?
[02:57] <Ampelbein> the name-slot
[02:57] <maco> if i put name@example.com inot the name slot, gpg goes to 98% cpu
[02:58] <maco> i just chose to edit my key and added it
[02:58] <maco> .. :-/ i use gpg-agent, not seahorse agent, but that *shouldn't* affect the non-agent stuff...
[02:58] <Ampelbein> right.
[02:59] <maco> well lets check+1
[03:00] <Ampelbein> strange thing. if i try with my primary-key (andreas.moog@warperbbs.de) it just works.
[03:00] <Ampelbein> if i try a newly created key (andreas@golem.warperbbs.de) it does not
[03:01] <Ampelbein> will provide a backtrace and reopen.
[03:01] <maco> intresting
[03:06] <tw1tch> hey can anyone help with https://bugs.launchpad.net/ubuntu/+source/kubuntu-meta/+bug/292355 do we have enough information to set to confirmed if not what else do we need thanks = )
[03:08] <dtchen> bcurtiswx: actually, 347588 is _not_ a dupe of 345627
[03:09] <dtchen> bcurtiswx: your hardware issues is very specific; the other reporter's symptoms are precisely the issue addressed by the test kernel
[03:09] <maco> tw1tch: confirmed = there's a reproducible test case. so if you can say the specific hardware and show it works on multiple of that hardware, that's confirmed
[03:19] <tw1tch> maco: since its a bug do you mean, doesn't work on multiple of that hardware? also, correct me if im wrong but cant you confirm a bug if there is enough information that a dev can see it? without having multiples report same behavior? obviously conflicting behavior from multiples would not be enough, thanks
[06:41] <dholbach> good morning
[06:46] <YoBoY> hi
[06:46] <dholbach> hi YoBoY
[06:46] <YoBoY> yo dholbach :)
[06:47] <YoBoY> dholbach: you plan to put back your five-a-day-stats one day? :p
[06:50] <dholbach> YoBoY: yes, definitely, yes :)
[07:25] <dominiks> good morning
[07:32] <dominiks> I'd like to ask one question regarding bug 344073 - problem was resolved by reporter by manual installing printer driver from manufacturer website. Is it common practice to package such drivers too? Should I suggest that driver for packaging? Or is it fine to manual install drivers? Sorry, I'm not very familiar with printer drivers. Thanks.
[07:35] <YoBoY> hi dominiks
[07:41] <YoBoY> it's fine, but this driver could be installed automaticaly with the jockey-gtk perhaps. The problem here is a mix of a support request and a regression bug ("my printer don't work, but worked in 8.10"), ask if it had installed the proprietary driver in 8.10 or not and the model of his printer
[07:43] <YoBoY> ^^^ dominiks: ^^^
[07:43] <YoBoY> oups the model is in th begining sorry :p
[07:44] <thekorn> and the target for this bug should not be cups but hplip
[07:45] <dominiks> ok.. thanks for advices
[07:49] <dominiks> could I add info about assigning HP printer related problems to hplip to wiki page https://wiki.ubuntu.com/Bugs/FindRightPackage? ... as future reference for bugsquad newbies like me? :)
[07:52] <YoBoY> dominiks: the section "printing System" don't help?
[07:54] <dominiks> I was not able to find anything about hplip.. but maybe I just need some coffee first :)
[07:54] <YoBoY> have you search the doc?
[07:55] <YoBoY> dominiks: https://help.ubuntu.com/community/HpAllInOne << like this one
[07:56] <dominiks> oh thanks
[07:57] <YoBoY> the wiki and the community doc are not the same (don't ask why...), don't forget to look everywhere :)
[07:58] <dominiks> yeah i see.. my fault I was too lazy
[07:58] <dominiks> I'm not good BugSquader at all.. I should better stop :)
[08:06] <YoBoY> dominiks: you are better than me, the begining is not simple :)
[08:07] <YoBoY> bye
[11:11] <BUGabundo> foo
[11:12] <BUGabundo> good morning
[11:12] <BUGabundo> can some one take a look and triage this bug
[11:12] <BUGabundo> https://bugs.launchpad.net/ubuntu/+source/lxnm/+bug/347571
[11:12] <BUGabundo> thanks in advance
[11:22] <thekorn> BUGabundo, hi, do you know this user who reported this bug in personal?
[11:24] <BUGabundo> thekorn: yes
[11:24] <BUGabundo> need further feed back?
[11:25] <BUGabundo> thekorn: why do you ask?
[11:26] <thekorn> BUGabundo, can you please ask him why he filed so many needs packaging bugs like bug 230310
[11:26] <BUGabundo> thekorn: will do
[11:26] <thekorn> which does only contain the url of the software without further information
[11:26] <BUGabundo> ROFL : evaristo?? eheh
[11:27] <BUGabundo> someone actuall confirmed it?
[11:27] <BUGabundo> nice
[11:27] <Mewcenary> I've applied for BugControl via Launchpad.  Is there anything else that I need to do at this stage?
[11:28] <Mewcenary> Hello everyone, by the way :-)
[11:31] <thekorn> hi Mewcenary
[11:31] <thekorn> https://wiki.ubuntu.com/UbuntuBugControl has more information on the application process
[11:37] <Mewcenary> Many thanks, thekorn.
[11:46] <BUGabundo> hew ping
[11:46] <BUGabundo> what debug packages do I need for bug 279820
[11:46] <BUGabundo> ?
[11:46] <Hew> BUGabundo: pong
[11:47] <Hew> BUGabundo: I generally work it out by looking at the ?? lines in a stacktrace
[11:47] <BUGabundo> great... you have better skills then me
[11:47]  * BUGabundo opens logs
[11:48] <BUGabundo> I would guess xorg?
[11:48] <Hew> BUGabundo: Feel free to pastebin and I'll have a look
[11:48] <BUGabundo> its on the bug hew
[11:49] <Hew> BUGabundo: There is an incomplete stacktrace attached? Where?
[11:50] <BUGabundo> humm damn apport
[11:50] <BUGabundo> it didn't attach it
[11:50] <Hew> apport-collect didn't seem to do much other than spam my inbox :P
[11:50] <BUGabundo> why would anyone mark as dupe, if the trace doesn't get uploaded.... bah
[11:50] <BUGabundo> yeah
[11:50] <BUGabundo> ok. will try to get a crash from compiz
[11:50] <Hew> BUGabundo: That's an apport thing, it removes all attachments when it marks as a dupe, unfortunately
[11:51] <BUGabundo> most of the times it just dies... doesn't crash
[11:51] <BUGabundo> making it very difficult to get a .crash
[11:51] <Hew> BUGabundo: Thanks! I know it's hard getting a gdb trace in startup situations like this, which is why I just prefer getting the right symbols and letting apport take care of it.
[11:51] <seb128> you can use sudo apport-retrace
[11:52] <BUGabundo> I don't have a trace now
[11:52] <seb128> it installs what is require and retrace locally
[11:52] <BUGabundo> but 15 mins ago compiz died on my, while closing Nautilus
[11:53] <BUGabundo> seb128: can I just do sudo apport-retrace 279820 ?
[11:53] <Hew> seb128: If the retrace fails on launchpad, will it work with apport-retrace locally? I'm still not clued up on apport / traces, but I was under the impression that it would still be incomplete.
[11:53] <BUGabundo> hey
[11:53] <BUGabundo> got one .crash still on var/crash
[11:53] <seb128> depends, it can fail for several reasons
[11:53] <BUGabundo> -rw------- 1 bugabundo bugabundo 7.6M 2009-03-23 11:35 _usr_bin_compiz.real.1000.crash
[11:53] <seb128> BUGabundo: you can try
[11:54] <jerrymcfarts> when you guys do bug reporting do you run your programs in a Virtual machine?
[11:54] <BUGabundo> let 1st try to apport it
[11:54] <BUGabundo> to a new bug
[11:54] <seb128> it can fail because the dbgsym are not available
[11:54] <seb128> or don't match the available version
[11:54] <seb128> or because the upload didn't work correctly
[11:54] <seb128> etc
[11:54] <BUGabundo> then I'll manually mark as dupe of original bug
[11:54] <Hew> jerrymcfarts: I'm running Jaunty as my main OS, and I just report / triage everything as is.
[11:54] <BUGabundo> if the LP retrace fails, I'll try locally
[11:55] <BUGabundo> I removed MANY gdb packages during the weekend
[11:55] <BUGabundo> I was low on disk space
[11:55] <BUGabundo> <100MiBs
[11:55] <BUGabundo> now I have 2.2GiBs
[11:55] <BUGabundo> yay
[11:55] <Hew> seb128: Ah ok, I didn't know that, thanks.
[11:56] <BUGabundo> ok this must be a bug!!!
[11:56] <Hew> BUGabundo: Feel free to pull the stacktrace from the .crash file and put it in a pastebin if you need help finding the right debug symbols
[11:56] <BUGabundo> double clicking on the .crash doesn't do anything
[11:56] <BUGabundo> after upload
[11:56] <BUGabundo> but running on the cli works!!!
[11:57] <BUGabundo> will file that bug next!
[11:57] <BUGabundo> 33% uploaded
[11:58] <BUGabundo> on LP now
[11:59] <BUGabundo> https://bugs.edge.launchpad.net/ubuntu/+source/compiz/+bug/347869
[11:59] <BUGabundo> LP retracing now
[12:00] <BUGabundo> seb128: so how do I retrace locally?
[12:00] <BUGabundo> https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/347869
[12:02] <seb128> BUGabundo: sudo apport-retrace .crash
[12:03] <seb128> BUGabundo: or apport-unpack .crash dir; cd dir; gdb $(which binary) CoreDump there
[12:03] <BUGabundo> https://bugs.launchpad.net/ubuntu/+source/apport/+bug/347874
[12:04] <BUGabundo> $ sudo apport-retrace _usr_bin_compiz.real.1000.crash
[12:04] <BUGabundo> apport-retrace: error: you either need to do a local operation (-s, -g, -o) or supply an authentication file (--auth); see --help for a short online help
[12:04] <BUGabundo> seb128: it failed
[12:05] <seb128> BUGabundo: use -s then
[12:05] <seb128> or -g
[12:05] <BUGabundo> trying second method
[12:05] <BUGabundo> seb128: on gdb do I do bt full ?
[12:06] <seb128> yes
[12:06] <seb128> "t a a b f" or "bt" to start
[12:07] <BUGabundo> http://paste.ubuntu.com/136679/
[12:07] <BUGabundo> no symbols
[12:07] <BUGabundo> installing compiz-core-dbgsym
[12:07] <seb128> "/usr/bin/compiz": not in executable format: File format not recognized
[12:07] <seb128> BUGabundo: you want to gdb /usr/bin/compiz.real
[12:08] <BUGabundo> ahh
[12:08] <BUGabundo> got a nice trace
[12:09] <BUGabundo> http://paste.ubuntu.com/136680/
[12:09] <BUGabundo> but check the bug retrace too
[12:12] <seb128> BUGabundo: you need compliz-plugins-dbgsym
[12:12] <seb128> that's why it doesn't work on the retracers, plugins are not a depends and don't get installed by apport-retrace I guess
[12:12] <BUGabundo> ok
[12:12] <BUGabundo> isntalling now
[12:12] <BUGabundo> E: Couldn't find package compliz-plugins-dbgsym
[12:12] <BUGabundo> typo
[12:12] <BUGabundo> fixed
[12:13] <BUGabundo> http://paste.ubuntu.com/136682/
[12:14] <Hew> BUGabundo: Better, but still a few missing (see the ?? lines)
[12:14] <BUGabundo> yes
[12:15] <BUGabundo> #15 0x00007f743de907ec in ?? () from /usr/lib/compiz/lib3d.so
[12:15] <Hew> BUGabundo: compiz-fusion-plugins-main
[12:16] <Hew> BUGabundo: To find the right package, I use dpkg -S /path/to/needed.so
[12:16] <BUGabundo> http://paste.ubuntu.com/136686/
[12:16] <BUGabundo> thanks hew
[12:16] <BUGabundo> good to know
[12:17] <Hew> BUGabundo: compiz-fusion-plugins-extra
[12:17] <BUGabundo> eheeh
[12:17] <BUGabundo> compiz*
[12:17] <Hew> BUGabundo: Haha, yea pretty much
[12:18] <Hew> BUGabundo: That should be the last one though, and then we have a full stacktrace! Thanks a lot!
[12:18] <BUGabundo> one more
[12:18] <BUGabundo> compiz-gnome-d
[12:18] <BUGabundo> http://paste.ubuntu.com/136689/
[12:19] <BUGabundo> Murphys law! the bug is always on the last package
[12:22] <Hew> BUGabundo: Excellent! If you could attach that to bug 279820, we can get this bug triaged. I'm not much help when it comes to reading these things I'm afraid, but hopefully someone else can see where the problem lies.
[12:23] <BUGabundo> phone brb
[12:26] <BUGabundo> back
[12:26] <BUGabundo> hew attaching now
[12:27] <BUGabundo> hew apport retrace could do this all...
[12:27] <BUGabundo> suggest packages to install
[12:27] <BUGabundo> and pass them along to apt
[12:27] <Hew> BUGabundo: you mean it currently does this, or it should?
[12:28] <BUGabundo> it should
[12:28] <Hew> BUGabundo: Yes, I strongly agree!
[12:28] <BUGabundo> then I wouldn't have to manually find and install then
[12:28] <BUGabundo> wishbug?
[12:29] <Hew> BUGabundo: Apport is hard enough to use for us, it's no surprise new reporters just switch off when they hear the word "backtrace"
[12:29] <BUGabundo> ehh
[12:29] <BUGabundo> I do most times
[12:29] <BUGabundo> if it can be run on gdb fine
[12:29] <BUGabundo> if not... I tend to let it go
[12:29] <BUGabundo> but since this bug is highly critical for me
[12:30] <BUGabundo> I want to get it fixed ASAP
[12:30] <Hew> BUGabundo: Yes, now that it has a good trace, hopefully some progress can be made!
[12:31] <BUGabundo> hew can bug 279820 be set to NEW or Confirmed?
[12:32] <Hew> BUGabundo: Once the attachment is there, it's confirmed at the very least due to the large number of dupes / comments / subscribers.
[12:33] <BUGabundo> I've posted the trace to my own bug
[12:33] <BUGabundo> that's duped to it
[12:33] <BUGabundo> should I copy it there too?
[12:33] <seb128> yes do copy it on the non duplicate bug
[12:35] <BUGabundo> done
[12:35] <BUGabundo> master now has it all
[12:41] <Hew> BUGabundo: It's normally best to put it in a single attachment, rather than a large comment.
[12:42] <BUGabundo> hew
[12:42] <BUGabundo> I got it.... when I saw th ....
[12:45] <mvo> BUGabundo: re bug #279820> is this crash reproducable? if so, how?
[12:45] <mvo> BUGabundo: thanks for the backtrace btw, that looks pretty good
[12:47] <Mewcenary> Can someone please comment if I'm doing the right thing here please?
[12:47] <Mewcenary> https://bugs.launchpad.net/ubuntu/+source/siege/+bug/347872
[12:56] <Hew> Mewcenary: Sounds like you have more of an idea what the problem is than I do. In Progress is probably fine, as long as your intention is to fix the bug in Ubuntu. If you are getting it fixed in Debian, it would be a good idea to add an affects line for the Debian bug report as well. See https://wiki.ubuntu.com/Bugs/Status if you're wondering about status.
[12:58] <mvo> BUGabundo: also, is this crash happening with compiz 0.8.2  ?
[13:00] <Mewcenary> Hew: Yes, I'll sort it in Ubuntu also.  I've just raised a bug report in Debian so pending the # so I can link the two up.
[13:01] <Hew> Mewcenary: Excellent, thanks for your help!
[13:02] <Mewcenary> No problem :) To be honest, the software seems very buggy and has reported segfaults in multiple areas of its code...
[13:04] <Hew> Mewcenary: I'm not familiar with siege, but that definitely doesn't sound good, especially for software in main. The more bugs fixed, the better! :-)
[13:05] <mvo> BUGabundo: furthermore, did you do any changes in the svg plugin with ccsm
[13:06] <Hew> mvo: In case BUGabundo doesn't respond, he is a Jaunty tester, so I would expect he reproduced the problem with 0.8.2.
[13:08] <seb128> mvo: he sent https://bugs.edge.launchpad.net/bugs/347869
[13:08] <seb128> mvo: using 0.8.2-0ubuntu5
[13:09] <seb128> mvo: the bug has the gconfcompiz info etc
[13:11] <Hew> Mewcenary: Are you familiar with linking external reports with the "Also affects project/distribution" feature?
[13:28] <Hew> Mewcenary: I have linked the Debian bug report to the Launchpad one. Note that you can do this with the "Also affects distribution" option in future.
[14:04] <BUGabundo> mvo is here yet?
[14:05] <BUGabundo> hew back from launch!
[14:17] <seb128> BUGabundo: he's coming back in a minute or so
[14:18] <BUGabundo> ok
[14:18] <BUGabundo> any KDE devs here?
[14:19] <BUGabundo> bug 311521 needs some love! fixed upstream!
[14:19] <BUGabundo> hey mvo
[14:19] <mvo> hey BUGabundo
[14:19] <BUGabundo> I'm here now! back from lunch
[14:19] <mvo> cool
[14:19] <BUGabundo> what do you need?
[14:19] <BUGabundo> sorry for leaving you hanging
[14:19] <mvo> BUGabundo I'm curious if you changed any settings in the svg plugin
[14:20] <mvo> and if you can reproduce the problem or if its happening at random
[14:20] <BUGabundo> I don't think I did
[14:20] <BUGabundo> but this in an old install
[14:20] <BUGabundo> from back ibex beta
[14:20] <BUGabundo> its pretty random
[14:20] <BUGabundo> I always get a fail decolorations on login
[14:21] <BUGabundo> reload and that gets fixed
[14:21] <BUGabundo> then using it , I get loss of colorarions several times a day
[14:21] <BUGabundo> especially if some app (like nautilus) hangs for a few secs
[14:22] <BUGabundo> one of todays crashes happen by just closing nautilus
[14:22] <mvo> could you attach a gconf dump of the settings to the bugreport please?
[14:22] <seb128> mvo: did you read my comment before? the bug BUGabundo opened which is a duplicate has the gconf configuration dump from apport
[14:22] <BUGabundo> how can I do that?
[14:22] <mvo> seb128, oh, great
[14:22] <seb128> mvo: bug #347869
[14:22] <mvo> BUGabundo, sorry, it seems to be already there
[14:23] <BUGabundo> yeah inicially I just sub to the master
[14:23] <bddebian> Boo
[14:23] <BUGabundo> but then since I needed the trace, I opened a new one
[14:23] <BUGabundo> bddebian: too late
[14:23] <BUGabundo> already did my Foo today
[14:23] <BUGabundo> eheh
[14:23] <bddebian> Doh
[14:23] <BUGabundo> see the log
[14:23] <BUGabundo> eheh
[14:24] <mvo> BUGabundo, I have everything I need I think, sorry for the noise
[14:24] <BUGabundo> np
[14:25] <BUGabundo> here to help, find, file, triage all the bugs I can
[14:26] <mvo> BUGabundo, hm, maybe one more thing, could you check with ccsm and go to "preferences"  and tell me what "backend" is selected?
[14:27] <mvo> (open ccsm)
[14:28] <BUGabundo> mvo none
[14:28] <BUGabundo> not one of the 3
[14:28] <BUGabundo> I think I used iconfusion to enable it
[14:29] <BUGabundo> bah
[14:29] <BUGabundo> nevermind
[14:29] <BUGabundo> backend: gconf
[14:29] <BUGabundo> confused with Apperances
[14:29] <BUGabundo> mvo: ^^^^^^
[14:31] <mvo> BUGabundo, ok, thanks
[15:45] <BUGabundo>  3076   0.08s   0.92s     0K     0K     0K     0K  --   - R  48% Xorg
[15:45] <BUGabundo> is this common?
[15:45] <BUGabundo> X taking 50% CPU?
[15:56] <seb128> BUGabundo: if you do play a video using x11 and not xv for example yes
[15:56] <seb128> or use flash
[15:56] <BUGabundo> seb128: no video app open
[15:56] <BUGabundo> or flash
[15:56] <seb128> ok so no
[15:57] <BUGabundo> I think it was Update Manager
[15:57] <seb128> could be something else doing lot of xorg calls
[15:57] <BUGabundo> once it stop fetching updates, X calmed down
[16:03] <seb128> could be the download bar animation or something
[16:03] <seb128> that would be weird though
[16:04] <BUGabundo> it was on the backgound
[16:04] <BUGabundo> 1st I noticed this
[16:59] <pregier> I've asked this before, but is there anyone here who can verify whether or not http://java.sun.com/applets/jdk/1.4/demo/applets/JumpingBox/example1.html can be REloaded in Firefox using sun-java6-plugin without having to clear the classloader cache between reloads?
[16:59] <pregier> under hardy, sorry
[16:59] <pregier> very important -- works fine in intrepid even for me
[19:10] <YoBoY> hi
[19:22] <dominiks> YoBoY: hey
[19:22] <YoBoY> :)
[20:39] <alanbell> hi all, I am interested in this bug https://bugs.launchpad.net/ubuntu-tweak/+bug/319380
[20:39] <alanbell> the status is Fix released, but it isn't in todays Jaunty build
[20:39] <alanbell> and I am not sure where to look to see the fix to test it
[20:40] <alanbell> can anyone point me in the right direction?
[21:17] <YoBoY> bug 247838 , bug 243489 , bug 347946 they surely have the same origin, i don't know if we can mark 2 of them as duplicates. For me the importance is Medium or High
[21:46] <bcurtiswx> dtchen: are you there?
[21:46] <dtchen> varyingly
[21:46] <bcurtiswx> dtchen: lol, may i PM you?
[21:46] <dtchen> sure, but note that i'm in the middle of a call currently
[23:24] <kees> bdmurray: do you remember which group should be added to a crash report for it to get retracing?  I have bug with only the security team, but it has "apport-crash need-amd64-retrace amd64" tags
[23:25] <bdmurray> kees: the retracer itself - apport
[23:27] <kees> there's a user for it?
[23:27] <bdmurray> yeah, that's the service that does the retracing
[23:27] <kees> oh, so there is.
[23:48] <kees> bdmurray: it seems to me like https://wiki.ubuntu.com/DebuggingProgramCrash should contain information about how to enable apport.  that's by far the simplest way to get crash details out of a bug reporter.
[23:49] <kees> i.e. https://wiki.ubuntu.com/Apport#How%20to%20enable%20apport
[23:52] <seb128> kees: usually crash bugs not sent using apport are closed using
[23:53] <seb128> https://wiki.ubuntu.com/Bugs/Responses
[23:53] <seb128> the stock reply #8 there
[23:53] <kees> seb128: cool.  that reply might want to use the URL above for additional help: https://wiki.ubuntu.com/Apport#How%20to%20enable%20apport
[23:53] <seb128> but right the other page could hint about using apport too
[23:54] <seb128> right, good idea too