[03:34] <philsf> I see some call for tests in the -devel list. Is there a centralized page (wiki?) that people can look to see what to look for? maybe some tag in LP?
[03:35] <philsf> sorry, I forgot the background - I meant for people downloading the jaunty beta
[03:36] <dtchen> maybe release notes page on the wiki
[04:58] <dawn> Hello! I am a new user to Ubuntu. :) I just tried to update my system (to 7.10) using the Update Manager, and it told me to report a bug. I'm not sure how to navigate the online forums for Ubuntu bugs, so I thought I would bring the report here and see if anyone could help me.
[06:27] <nelhage> Where should I report a bug on the Intrepid->Jaunty upgrade?
[06:31] <sbeattie> nelhage: launchpad, same as for any other bug in ubuntu.
[06:31] <nelhage> Sorry; I meant is there a specific place for upgrade bugs, or does it go against the relevant package?
[06:33] <sbeattie> nelhage: the relevant package is a good place to start; update-manager may be appropriate as well if it's a dependency ordering issue.
[06:34] <nelhage> Ah, after some digging it looks like my bug is #354228. Great timing!
[06:35] <nelhage> (I suspect that was caused by the fix to #353251, which went in literally hours ago)
[06:43] <andersk> Can someone on bugcontrol please mark bug 354228 as importance Critical?  It completely breaks Jaunty installs and upgrades.
[06:46] <dholbach> good morning
[06:48] <YoBoY> good morning :)
[07:11] <drcookie> hello, anyone that is awake
[07:13] <drcookie> I'm interesting in learning how to triage bugs, and wondered if anyone could possibly walk me through the process?
[07:13] <drcookie> s/interesting/interested/
[07:19] <YoBoY> drcookie: hi, have you read the documentation on the wiki?
[07:29] <YoBoY> drcookie: if you can participate on a bug jam also, it's a good way to begin
[07:46] <drcookie> YoBoY: I have read the documentation
[07:46] <drcookie> it just seems a little daunting at first
[07:47] <YoBoY> yes it is :)
[07:47] <drcookie> I've kind of cherry picked a little, and done 2 bugs
[07:48] <YoBoY> you can always ask here for advice on a bug, simply put bug NUMBER and your question and someone will help you (perhap's :p)
[07:49] <drcookie> ok
[07:50] <drcookie> well, I'm off to bed for now
[07:50] <drcookie> night, and thanks
[09:35] <TEN> The startup order is wrong between LIRC, lcdproc and VDR - a manual fix is easy once known, https://bugs.launchpad.net/ubuntu/+source/vdr-plugin-lcdproc/+bug/250107 but next to impossible for new users to figure out. IMU the order should be handled automagically by init dependencies anyway, but I couldn't find a way to fix/implement these.
[10:19] <mvo> bdmurray: woah, congracts for becoming a motu - thats excellent news \o/ (I'm a bit late, but its never too late to cheer :)
[12:15] <Hobbsee> mmm, tasty pidgin and new notification bug
[12:17] <Hobbsee> so, now that it's got the envelope thing that works for pidgin and evolution and whatnot, i told it to hide the icon at all times
[12:17] <Hobbsee> so thus, it doesn't appear in the notification area directly
[12:17] <Hobbsee> and when you hit x, it quits the program.
[12:50] <savvas> FYI: I've marked several bugs in python2.6 and pytho3.0 as duplicates of bug #354228 (sorry if I made a mistake)
[12:50] <savvas> *python3.0
[12:52] <XiXaQ> I need some help with a bug. Gnome or X.org crashes when I run a certain application. It always happen, but I don't know how to find out why. I'm also not close to my computer. But if someone could install "alarm clock" for gnome, and run it to find out why it crashes, I think it could be useful.
[12:52] <XiXaQ> I'm running ubuntu jaunty with all updates installed, btw.
[12:56] <savvas> XiXaQ: package name?
[12:57] <savvas> ah, alarm-clock :)
[13:01] <savvas> ouch.. that's a bad bug :P
[13:02] <savvas> XiXaQ: please file a bug for it, or see if you can find a bug report about it: http://bugs.launchpad.net/ubuntu/+filebug
[13:18] <savvas> XiXaQ: did you find one?
[13:29] <fader_> Can anybody tell me the proper package to report sound bugs against?  (Specifically things like recording/microphone issues)
[13:31] <savvas> XiXaQ: https://bugs.launchpad.net/ubuntu/+source/alarm-clock/+bug/321176
[14:09] <XiXaQ> savvas: thanks! Do you have a logfile to attach? I'm not at home, so I can't get mine, but there was an error in /var/log/Xorg that said something about it.
[14:13] <savvas> XiXaQ: only an strace
[14:13] <savvas> strace -o test.txt alarm-clock
[14:15] <savvas> XiXaQ: it needs to be killed from ctrl+alt+f2 though :\
[14:16] <savvas> I can't see anynothing in /var/log/Xorg.0.log
[14:16] <XiXaQ> savvas: as I said, I don't have access to it from here, but there was a line saying something like the screen area doesn't exist, or something like that.
[14:19] <savvas> here's the Xorg.0.log: http://paste.ubuntu.com/143474/
[15:00] <yann__> https://bugs.launchpad.net/ubuntu/+source/paman/+bug/352959
[15:00] <yann__> I think I found the culprit line
[15:00] <yann__> (see last comment in bug)
[15:01] <yann__> but I have no idea how to fix it...
[15:01] <yann__> some clues?
[15:24] <bddebian> Boo
[16:06] <hggdh> bah
[16:14] <bdmurray> mvo: thanks!
[17:23] <yann__> https://bugs.launchpad.net/ubuntu/+source/paman/+bug/352959
[17:24] <yann__> I found the bug and add a patch
[17:28] <lunartear> logcheck is reporting the same system and security events every hour which are from older dates such as Mar 22. I noticed a bug similar to this on debian's bug tracker http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=296096  is there something i can do to fix this?
[17:29] <lunartear> im using logcheck 1.2.41
[17:30] <lunartear> affected version on the bug report is 1.2.34 and fixed version was 1.2.36
[17:34] <hggdh> lunartear, then it sounds like a regression
[17:34] <hggdh> lunartear, what Ubuntu version are you running?
[17:35] <lunartear> hggdh: 6.0.6 TLS if im not mistaken
[17:36] <hggdh> 6.04?
[17:36] <lunartear> 6.06.1 LTS Dapper
[17:38] <BUGabundo> hggdh: lol there was no 6.04
[17:38] <hggdh> BUGabundo, before my time ;-)
[17:38] <hggdh> lunartear, http://packages.ubuntu.com states Dapper logcheck is 1.2.42ubuntu1
[17:40] <BUGabundo> really?
[17:40] <BUGabundo> I thought you were and old dog too
[17:40] <hggdh> really... if I remember correctly. Since I am an old dog, my memory has been failing ;-)
[17:41] <hggdh> I think I started on Ubuntu end of 2006/beginning of 2007. Before that it was SUSE for a few years
[17:41] <BUGabundo> ah
[17:41] <BUGabundo> I started with 5.04 brefelly
[17:42] <BUGabundo> and with 6.06 full time
[17:42] <hggdh> I went straight to the "E"...
[17:43] <hggdh> needed it because of my sound card and wireless
[17:46] <lunartear> hggdh i did a --reinstall of logcheck. 1.2.42ubuntu1  guess i'll be back in an hour if it continues
[17:46] <hggdh> lunartear, thank you
[17:47] <lunartear> np
[18:04] <lunartear> hggdh i just recieved another
[18:05] <lunartear> perhaps its another package that needs updating such as syslog or rotate?
[18:07] <hggdh> lunartear, it might... meanwhile, it would be good if you could open a bug on that
[18:07] <hggdh> lunartear, actually, can you try and see if there are updates to syslog, or rotate (since you use them)?
[19:08] <mdz> ogasawara: you set 348275 to triaged but forgot to set importance
[19:09] <ogasawara> mdz: oops, thanks.  I'll fix it up.
[20:15] <mregister> ok sorry to seem dumb but i just joined the bugSquad five a day program. so now what do i do?
[20:24] <maxriskfactor> mregister, have you installed 5-a-day application?
[20:25] <mregister> no i have not. i just joined the group on launch pad and that's it.
[20:26] <lacqui> anyone here know why no bug announcements are on #ubuntu-bugs-announce?
[20:26] <maxriskfactor> mregister, this can help you a lot: http://people.ubuntu.com/~dholbach/patch
[20:26] <maxriskfactor> mregister, this has everything you ever need for 5-a-day programme
[20:26] <hggdh> lacqui, I will have a look at it
[20:26] <maxriskfactor> mregister, by the way your questions wasnt dumb :)
[20:30] <hggdh> lacqui, it seems there simply was no new bugs (or they were not announced by the LP link) in this interval. But I went ahead, corrected a smal logging issue, and restarted eeebotu
[20:30] <mregister> maxriskfactory, that page was jsut some code on a white background
[20:31] <lacqui> the reason i was asking was because launchpad was showing bugs on the web page
[20:31] <maxriskfactor> mregister, code in white background?
[20:31] <maxriskfactor> mregister, that's the 5-a-day wiki page
[20:31] <maxriskfactor> mregister, try again -- https://wiki.ubuntu.com/5-A-Day/
[20:32] <maxriskfactor> mregister, its https not http :)
[20:33] <hggdh> lacqui, there is a delay between direct access to LP and eeebotu. It does not make sense to continuously probe LP
[20:34] <hggdh> usually ~5 minutes, or less
[20:34] <mregister> a much better maxriskfactor. thanks!
[20:34] <maxriskfactor> mregister, opened? got it?
[20:34] <lacqui> lol ok, i was idling for a bit, the bugs (which seem to be all related) were all reported in a block
[20:35]  * lacqui is obviously too impatient
[20:35] <hggdh> :-)
[20:35] <hggdh> no probs
[20:39] <mregister> yes, maxriskfactor i got it. so i need to learn the process for bug reporting and go from there it seems.
[20:40] <maxriskfactor> mregister, yes.. you better learn how to file bugs properly
[20:41] <maxriskfactor> so that you know what is required for troubleshooting a bug
[20:41] <maxriskfactor> so that you can ask people what is required
[20:41] <maxriskfactor> you can troubleshoot a bug only if you know what all info is required for a dev to fix it.
[20:42] <maxriskfactor> go and see the TraigingBugs and Bug BackTrace  wiki pages
[20:43] <mregister> yes i am doing that now.
[20:43] <mregister> so the long term goal for me is to develope for Ubuntu. this seems like a good place to start cosidering i am just starting out in CS and really learning to program
[20:47] <maxriskfactor> mregister, for contributing you dont need programming
[20:47] <maxriskfactor> you can be a bridge between users and developers
[20:48] <maxriskfactor> mregister, though knowledge of programming surely helps and gives you an edge
[20:49] <mregister> right but as i udnerstand the contributing is the first step, and while i work on that my skills will increase
[20:50] <maxriskfactor> mregister, correct. nor am I a big contributer, nor do I file much bugs
[20:50] <maxriskfactor> do one thing, install apport if not installed
[20:52] <mregister> what is apport?
[20:52] <maxriskfactor> its the crash handler
[20:53] <maxriskfactor> if am correct :)
[20:53] <maxriskfactor> once enabled, it would run in background
[20:53] <maxriskfactor> when your application crashes, it would show up in the top right corner
[20:54] <maxriskfactor> when you click on it, it creates an exhaustive report of the crash, everything it can...
[20:54] <maxriskfactor> if you allow it to be submitted
[20:54] <maxriskfactor> then it uploads itself to launchpad and you are greeted on the screen on launchpad to file the bug
[20:54] <BUGabundo> maxriskfactor: you can also call it from CLI or the Help menu in gtk
[20:54] <maxriskfactor> you can add comments on the bug you submitted. This is actually the correct way to file bugs
[20:55] <maxriskfactor> BUGabundo, ubuntu-bugs ?
[20:55] <BUGabundo> that too
[20:55] <BUGabundo> not the "correct" way , but the "recommend" way
[20:56] <maxriskfactor> BUGabundo, :)
[20:56] <maxriskfactor> mregister, read this: http://mdzlog.wordpress.com/2009/03/31/please-dont-report-ubuntu-bugs-directly-to-launchpad/
[20:56] <BUGabundo> LOL
[20:56] <maxriskfactor> mregister, and this: https://help.ubuntu.com/community/ReportingBugs
[20:56] <BUGabundo> didn't read his blog!
[20:56] <BUGabundo> just the email to devel ML
[20:56] <maxriskfactor> BUGabundo, this post even showns on ubuntuforums.org
[20:57] <maxriskfactor> BUGabundo, why didnt read this blog?
[20:59] <mregister> ok collecting a nice reading list.
[20:59] <BUGabundo> too many already maxriskfactor
[20:59] <maxriskfactor> mregister, reading never harms :)
[20:59] <BUGabundo> 300 feeds is too much to read
[21:00] <maxriskfactor> BUGabundo, 1000+ for me
[21:00] <BUGabundo> but feel free to follow my shared one
[21:00] <BUGabundo> maxriskfactor: not 1000+ unread... 300+ different sites/sources!
[21:00] <maxriskfactor> BUGabundo, its really like "WTF"
[21:00] <BUGabundo> maxriskfactor: pvt please
[21:00] <maxriskfactor> BUGabundo, I cant cope up with so much traffic
[21:01] <maxriskfactor> BUGabundo, you use Google Reader?
[21:01] <BUGabundo> yes
[21:01] <maxriskfactor> BUGabundo, how do I get your shared items?
[21:01] <BUGabundo> maxriskfactor: this is off topic for this #
[21:01] <BUGabundo> come to pvt please
[21:01] <maxriskfactor> sure
[21:04] <mregister> no reading is great. what i do more than anything
[21:05] <maxriskfactor> mregister, keep going.. and try it out side by side :0
[21:50] <BUGabundo> is this normal
[21:50] <BUGabundo> http://paste.ubuntu.com/143684/
[21:50] <BUGabundo> ?
[21:50] <BUGabundo> apport crashing out of memory?
[21:59] <hggdh> not, it oes not seem good
[21:59] <hggdh> I wonder if Nautilus got all memory...
[21:59] <BUGabundo> yea
[22:00] <BUGabundo> I found it strange too hggdh
[22:00] <BUGabundo> where would I ask for help to start my 1st patch? need to branch a code in LP!
[22:03] <dtchen> hggdh: your debdiff for 352959 is odd. what is the base against which you diffed?
[22:03] <dtchen> hggdh: i'll redo it for jaunty
[22:04] <bdmurray> dtchen: you confirmed bug 210394 do you have a test case for it?
[22:06] <dtchen> bdmurray: not at the moment; it was reproducible when i marked it
[22:06] <dtchen> i'm triaging audio stuff atm, will look in a bit
[22:30] <BUGabundo> hggdh: is this any good https://code.edge.launchpad.net/~bugabundo/network-manager/bug353957/+merge/5210 ?
[22:31] <BUGabundo> me 1st patch! yay
[23:07] <hggdh> dtchen, it was diffed against Jaunty paman
[23:07] <dtchen> hggdh: err, no?
[23:08] <hggdh> dtchen, or, at least, what apt-get source gave me as such. I wondered about the changelog
[23:08] <hggdh> (was marked as Intrepid...)
[23:08] <dtchen> the patch is wrong
[23:08] <hggdh> darn!
[23:08] <dtchen> i have consulted with upstream and will attach a new debdiff
[23:09] <hggdh> thank you, I could not find anything as an active upstream
[23:09] <dtchen> builds and operates fine locally
[23:09] <dtchen> paman uses the same trac as pulseaudio
[23:10] <hggdh> perhaps we should, then, update the ./debian/watch (or this was the bloody old entry for the paman I sourced off)
[23:11] <dtchen> hggdh: there has been no new upstream release
[23:11] <dtchen> 0.9.4 is the current upstream release
[23:11] <hggdh> dtchen, then I am really confused... the diff was against 0.9.4
[23:12] <hggdh> dtchen, I have to go out for 40 min
[23:12] <dtchen> hggdh: it's no big deal
[23:14] <nhandler> hggdh: apt-get source doesn't get the latest ubuntu version. It uses the deb-src entries in /etc/apt/sources.list. I would advise you use pull-lp-source from ubuntu-dev-tools instead
[23:15] <dtchen> nhandler: do you mind uploading http://launchpadlibrarian.net/24772522/paman_0.9.4-1ubuntu2.debdiff, please?
[23:16] <nhandler> dtchen: Do you have a bug to go with that?
[23:16] <dtchen> bug 352959
[23:16] <dtchen> (the bug is listed in the debdiff)
[23:17]  * nhandler saw that after he made the comment
[23:20] <joshjtl> hi folks, trying to report a bug, i don't know what information to attach to it
[23:20] <dtchen> use ubuntu-bug
[23:21] <BUGabundo> joshjtl: you are spamming every channel
[23:21] <BUGabundo> lol
[23:21] <dtchen> e.g., ubuntu-bug quassel
[23:21] <dtchen> will report a bug about quassel
[23:21] <BUGabundo> dtchen: I already told him that on +1
[23:21] <joshjtl> you told me to ask in here
[23:21] <BUGabundo> no
[23:21] <BUGabundo> that on on "lp
[23:21] <joshjtl> i'm confused
[23:21] <BUGabundo> I told you on +1 how to use apport to file bugs
[23:22] <joshjtl> BUGabundo: but i'm trying to find out what to attach to my bug report
[23:22] <BUGabundo> ahh
[23:22] <BUGabundo> do that on LP
[23:22] <BUGabundo> *after* apport file it
[23:23] <joshjtl> right i'm reporting a bug on launchpad.net ... but how do I know what info to attach to the bug there?
[23:23] <BUGabundo> well apport collects pretty much all you need
[23:23] <BUGabundo> if something is missing triager or devs will ask for it
[23:23] <BUGabundo> what is the bug id'
[23:23] <BUGabundo> ?
[23:23] <joshjtl> ohhhh
[23:24] <joshjtl> i see it opens a page in launchpad after I run and send apport
[23:24] <BUGabundo> yes
[23:24] <joshjtl> thats what i wasnt understanding
[23:24] <joshjtl> i thought it just sent it and... that was it
[23:25] <BUGabundo> eheh
[23:25] <BUGabundo> ok glad to see it clear now
[23:26] <BUGabundo> I just needed to ask the proper question!
[23:26] <joshjtl> BUGabundo: https://bugs.launchpad.net/ubuntu/+bug/354822
[23:26] <joshjtl> how does that look
[23:27] <nhandler> dtchen: Uploaded
[23:27] <joshjtl> BUGabundo:  hmm i wonder if i should have run apport while logged into 2.6.29 since the problem is solved by booting into 2.6.27
[23:27] <BUGabundo> please mention that on the bug
[23:27] <joshjtl> BUGabundo:  I did... could you have a look at it and tell me if it looks ok?
[23:28] <dtchen> nhandler: thanks!
[23:28]  * BUGabundo looks
[23:28] <nhandler> dtchen: You're welcome. Thanks for the patch
[23:28] <BUGabundo> joshjtl: that doesn't have a package!
[23:28] <BUGabundo> strange!
[23:29] <BUGabundo> shouldn't it be xserver-xorg?
[23:29] <dtchen> nhandler: heh, i used to sponsor these patches ;-)
[23:29] <joshjtl> BUGabundo: It wanted to add a package, yes xserver-xorg, but i didnt know if that was what was causing the error
[23:29] <joshjtl> BUGabundo: do you think i should add it?
[23:29] <BUGabundo> ok I did it now
[23:30] <joshjtl> BUGabundo: you added it?
[23:30] <BUGabundo> yes
[23:30] <joshjtl> oh thanks
[23:30] <joshjtl> i'm an old linux user, but new to bug reporting
[23:31] <nhandler> dtchen: Why don't you re-apply to the teams?
[23:31] <BUGabundo> hey joshjtl we all learn!
[23:32] <dtchen> nhandler: i will if i find that fixes are being dropped on the floor
[23:33] <dtchen> besides, everyone needs experience sponsoring patches
[23:33] <dtchen> it's like drinking sewage - you learn to weed out crackful bits