| [00:00] <secretlondon> sure, but people won't be that interested in bugs on an out of date beta | |
| [00:00] <Gnine> indeed | |
| [00:00] <secretlondon> as they may be fixed in the new version | |
| [00:01] <feugan3333> Hi all. | |
| [00:02] <feugan3333> I'm getting random crashes of the xmms2d daemon on my system, and would like to report a bug. What information should I include in the bug report, apart from a backtrace? | |
| [00:03] <secretlondon> make sure you have debug symbols for your backtrace | |
| [00:03] <feugan3333> Yes, I do. | |
| [00:03] <secretlondon> reporting it via apport is best, as that includes information automatically | |
| [00:04] <Gnine> allegedly... | |
| [00:04] <secretlondon> if it doesn't trigger you can click on a .crash file and it should submit is that way | |
| [00:04] <feugan3333> Ah, where would I find the .crash file? | |
| [00:05] <secretlondon> /var/crash | |
| [00:06] <greg-g> if you are in kde: http://tinyurl.com/5a7jad | |
| [00:06] <secretlondon> we have a wiki page on DebuggingProgramCrash which may help | |
| [00:06] <greg-g> that url is for the standard reply about getting a .crash report submitted | |
| [00:07] <secretlondon> greg-g, thanks. It would be cool if the bot could churn out wiki links | |
| [00:07] <feugan3333> secretlondon, yes that's is the page that I was reading to get the crash dump with gdb. | |
| [00:08] <Gnine> you could always get directly to wiki and search too.. | |
| [00:08] <feugan3333> secretlondon, this page https://wiki.ubuntu.com/DebuggingProgramCrash ? | |
| [00:08] <secretlondon> yeah, but it'b be easier to say a wiki link to the bot and it would give a URL | |
| [00:08] <secretlondon> feugan3333, yep | |
| [00:08] <greg-g> secretlondon: yeah, a "!crashreport" or "!debug" or similar would be awesome, how can we add knowledge to ubotu? | |
| [00:08] * Gnine nods at secretlondon | |
| [00:09] <secretlondon> greg-g not sure, it's Seveas' bot | |
| [00:09] <greg-g> yeah | |
| [00:10] <Gnine> he's not that hard to reach | |
| [00:13] <greg-g> Gnine: yeah, I just need to think of what to have ubotu do :) | |
| [00:15] <Gnine> i thought that was already exposed | |
| [00:15] <Gnine> :-P | |
| [00:15] <feugan3333> If anyone would like to check my bug report and let me know if I have provided enough information, that would be appreciated: https://bugs.launchpad.net/ubuntu/+source/xmms2/+bug/212566 :-) | |
| [00:15] <ubotu> Launchpad bug 212566 in xmms2 "xmms2d crashes" [Undecided,New] | |
| [00:16] <feugan3333> Just in time :-) | |
| [00:17] <secretlondon> feugan3333, it's not a full backtrace | |
| [00:17] <secretlondon> eg libglib-2.0.so.0 | |
| [00:17] <secretlondon> doesn't have any symbols | |
| [00:18] <feugan3333> ok, I'll add those and do it again. | |
| [00:18] <feugan3333> secretlondon, thanks | |
| [00:18] <secretlondon> we'd prefer it via the auto crash logger | |
| [00:18] <secretlondon> did you find it in /var/crash? | |
| [00:19] <feugan3333> secretlondon, yes I found it. Should I add it as an attachment? Or just click on it? | |
| [00:19] <secretlondon> just click on iy | |
| [00:19] <secretlondon> it | |
| [00:19] <feugan3333> ok | |
| [00:19] <secretlondon> it'll start the crash submitter, and submit a new bug with more info | |
| [00:21] <Gnine> confirmed. ( :-P ) | |
| [00:21] <feugan3333> Ok, I see it provides a lot of info :-) | |
| [00:21] <secretlondon> and it gets automatically retraced at our end | |
| [00:22] <feugan3333> Ok, nice | |
| [00:30] <greg-g> so your original bug can be closed then | |
| [00:36] <feugan3333> Well, its probably not exactly the same command that caused the bug. But I guess that we can assume that it is the same bug. So yes :-) | |
| === secretlondo is now known as secretlondon | |
| === null_vector is now known as brward | |
| === brward is now known as null_vector | |
| === secretlondo is now known as secretlondon | |
| [01:41] <bddebian> Boo | |
| === null_vec1or is now known as null_vector | |
| === asac_ is now known as asac | |
| [08:45] <qense> hello | |
| [10:20] <Iulian> G'morning. | |
| [10:20] <qense> hello | |
| [10:21] <Iulian> Hi qense | |
| [11:06] <mo> Hello. Im running Hardy Heron beta, I'm trying to apt-get install ubuntu-xen-desktop, but it failes becuase a dependency (xenman) is not avaible from the repositories, is this a "beta bug" that should be reported ? | |
| [12:15] <dba358> hi | |
| [12:16] <dba358> I think I have a "bug" in Ubuntu gutsy | |
| [12:16] <dba358> for amd64, the Packages.* files are outdated in the universe branch | |
| [12:16] <dba358> e.g. ubuntu-xen-server which is a package of xen-meta is newer than the Packages.gz | |
| [12:17] <dba358> so apt-get install ubuntu-xen-server works on i386 but doesn't on amd64 | |
| [12:17] <dba358> can anyone confirm that this is a bug which should be reported? | |
| === qense is now known as qense|lunch | |
| [12:21] <dba358> I'll check back later... | |
| === qense|lunch is now known as qense | |
| === hefe_bia_ is now known as hefe_bia | |
| [16:30] <mo> Hello. Im running Hardy Heron beta, I'm trying to apt-get install ubuntu-xen-desktop, but it failes becuase a dependency (xenman) is not avaible from the repositories, is this a "beta bug" that should be reported ? | |
| [16:31] <qense> you could look for it | |
| [16:31] <qense> if it doesn't exist yet you could report it | |
| [18:11] <alex_> Hi all! | |
| [18:21] <mrooney> alex_: hello! | |
| [18:32] <alex_> I wouls like to help triage bugs, but I'm not quite sure how. Is there a walkthroughish page anywhere or just saved irc lessons? | |
| [18:35] <mrooney> alex_: did you look in the topic? such as the helping with bugs wiki page? | |
| [18:37] <alex_> absolutely | |
| [18:38] <secretlondon> I seem to have disappeared from the five a day stats | |
| [18:39] <secretlondon> I did loads yesterday, and no presence in the last week! | |
| [18:45] <Iulian> alex_: Then you are ready to go. Just pick one bug from the list, if you have any questions here is the right place where you can ask. Also we are celebrating every week 'Hug Day' (Tuesday and Thursday). Please have a look at https://wiki.ubuntu.com/UbuntuBugDay for more information about the Bug days | |
| [18:46] <Iulian> alex_: We appreciate if you can come next Tuesday to join the party here. | |
| [18:47] <Iulian> alex_: This is the list of the next hug day - https://wiki.ubuntu.com/UbuntuBugDay/20080408 | |
| [18:47] <Iulian> alex_: Our task is to hug all the bugs from that list and make them green! | |
| [18:49] <Iulian> Of course if you have more questions I'm sure someone from here will answer them. | |
| [18:49] * Iulian is going to watch a film - bbl | |
| [19:12] <greg-g> where did you go secretlondon?? (on the stats page) | |
| [19:12] <secretlondon> greg-g I don | |
| [19:13] <greg-g> that is weird | |
| [19:13] <secretlondon> I don't know, it's been ignoring my submissions (looks like) | |
| [19:13] <greg-g> are they in the bzr repo? | |
| [19:14] <greg-g> yeah, weird, there is nothing in your log past 3-25 | |
| [19:14] <secretlondon> I don't know what that means | |
| [19:14] <greg-g> the bzr branch/repo/whatever it is called | |
| [19:14] <greg-g> on LP | |
| [19:14] <secretlondon> well i've been submitting as normal | |
| [19:15] <greg-g> does your local copy have your bugs in it? .5-a-day-data/secrectlondon | |
| [19:15] <secretlondon> i'll look | |
| [19:16] <secretlondon> where is that directory supposed to be? | |
| [19:16] <greg-g> in your home | |
| [19:17] <greg-g> ~/.5-a-day-data | |
| [19:17] <secretlondon> stops at the 25th/3 | |
| [19:17] <greg-g> ruh roh | |
| [19:17] <greg-g> something broke then | |
| [19:18] <greg-g> back in your home dir, do a "cat .5-a-day" | |
| [19:19] <secretlondon> secretlondon | |
| [19:20] <greg-g> I have no idea | |
| [19:21] <greg-g> been using the add-5-a-day command or the applet? | |
| [19:21] <greg-g> (not sure what difference it would make, just wondering) | |
| [19:21] <secretlondon> applet | |
| [19:23] <greg-g> then I would poke thekorn about it | |
| [19:23] <aleehk82> how should bugs be reported with regards to different distro versions | |
| [19:24] <greg-g> aleehk82: it is assumed the bug is against the latest version of the program | |
| [19:24] <aleehk82> Many bugs have their headers tagged with codenamesö. Is this the preferred way? | |
| [19:24] <aleehk82> greg-g: thanks | |
| [19:25] <greg-g> aleehk82: yes, that would help, or just mention it in the bug report | |
| [19:25] <aleehk82> greg-g: except for some packages like the kernel | |
| [19:25] <greg-g> aleehk82: from now on, all kernel bugs will be reported against the package "linux" not "linux-2.6.24-14" | |
| [19:26] <aleehk82> greg-g: ah, that clears some confusion | |
| [19:26] <greg-g> well, time to be productive elsewhere | |
| [19:26] <greg-g> good luck fixing your issue secretlondon | |
| [19:26] <greg-g> thanks for helping triage aleehk82 | |
| [19:27] <aleehk82> greg-g: thanks for advice | |
| [19:27] <james_w> secretlondon: do you still have the /tmp/5-a-day-applet.txt file around? | |
| [19:33] <aleehk82> is it worthwhile to report bugs upstream? should it be handled by the package maintainer instead? | |
| [19:34] <secretlondon> james_w I'll look | |
| [19:34] <james_w> aleehk82: it's very useful to report them upstream | |
| [19:35] <james_w> aleehk82: you should be reasonably sure it's not an Ubuntu-specific problem though. | |
| [19:35] <secretlondon> james_w yes, and it contains errors | |
| [19:35] <secretlondon> james_w URLError: <urlopen error (-5, 'No address associated with hostname')> | |
| [19:35] <james_w> oh dear | |
| [19:36] <james_w> I guess it's having trouble resolving bazaar.launchpad.net | |
| [19:36] <james_w> if you "cd ~/.5-a-day-data; bzr info" | |
| [19:37] <aleehk82> james_w: thanks, it gives food for thought. it's about transmission and file fragmentation. | |
| [19:37] <secretlondon> Location: | |
| [19:37] <secretlondon> checkout root: . | |
| [19:37] <secretlondon> checkout of branch: bzr+ssh://secretlondon@bazaar.launchpad.net/%7E5-a-day/5-a-day-data/main/ | |
| [19:37] <james_w> secretlondon: and "host bazaar.launchpad.net" works ok? | |
| [19:38] <secretlondon> bazaar.launchpad.net has address 91.189.94.254 | |
| [19:38] <secretlondon> I hope this isn't the network manager thinks I'm offline breakage | |
| [19:38] <secretlondon> that affects firefox as NM can't cope with my usb modem | |
| [19:39] <james_w> secretlondon: I've got to go out now I'm afraid. I'll happily debug this with you tomorrow if it's still broken. | |
| [19:39] <secretlondon> james_w thanks, I should be going out too | |
| [19:39] <james_w> have a good evening. | |
| [19:40] <secretlondon> james_w and you | |
| [19:53] <aleehk82> where should I report hibernation problems? https://bugs.launchpad.net/linux/+bugs | |
| [19:53] <aleehk82> is that correct? | |
| [20:15] <alex-weej> neither flash nor gnash are working on 64 bit hardy | |
| [20:29] <AmyRose> Is anyone else having trouble with Synaptic in Hardy? | |
| [20:30] <AmyRose> https://bugs.launchpad.net/ubuntu/+source/synaptic/+bug/192140 | |
| [20:30] <ubotu> Launchpad bug 192140 in synaptic "update manager hangs at "applying changes" window" [Undecided,New] | |
| [20:30] <warren_> https://bugs.launchpad.net/ubuntu/+source/gdebi/+bug/153943 | |
| [20:31] <ubotu> Launchpad bug 153943 in gdebi "Gdebi-kde uses massive amounts of memory!" [High,Confirmed] | |
| [21:17] <Gnine> npviewere.bin and nspluginwrapper bug reports seem to be incomplete yet lots of entries are recorded about them... | |
| [21:19] <Gnine> maybe apport should be double checked to make those reports happen effectively | |
| [21:20] <Gnine> bug 204322 | |
| [21:20] <ubotu> Launchpad bug 204322 in nspluginwrapper "npviewer.bin crashed with SIGSEGV in g_type_check_instance_cast()" [Medium,Incomplete] https://launchpad.net/bugs/204322 | |
| [21:21] <Gnine> there are many more like that one | |
| [21:26] <Gnine> also.. update-manager upgraded system to 2.6.24-15-generic on both x86_64 and 32bit version and grub did not get auto-updated with new kernel info. | |
| [21:37] <Iowo> Is there anyone here familiar with the brainstorms.ubuntu.com source code? | |
| === blue-frog__ is now known as blue-frog | |
| [22:19] <JohnPinWa> Iowo: I was just talking to someone named nand in #unbuntu-motu who mentioned brainstorm and the php code. | |
| [22:33] <JohnPinWa> When someone offers mentoring in Launchpad how do you contact him/her to let them know you'd like to learn about it? | |
| [23:12] <persia> JohnPinWa: Try asking here. Which bug? | |
| [23:13] <JohnPinWa> I'm on this website: https://launchpad.net/%7Ebugsquad/+mentoring | |
| [23:13] <persia> OK. Which bug interests you? | |
| [23:13] <JohnPinWa> Persia: there is a list of bugs for which mentoring is available. I'm willing to take a swing at any but not sure how to start. | |
| [23:14] <persia> OK. Pick one. take a look. If you think you have some ideas about triage (see the /topic), but want a hand, you can ask the mentor for the bug. | |
| [23:14] <persia> As an example, let's look at bug #120746 | |
| [23:14] <ubotu> Launchpad bug 120746 in nautilus "nautilus open files twice" [Low,Triaged] https://launchpad.net/bugs/120746 | |
| [23:14] <JohnPinWa> persia: The singleusermode-password? How do I get in touch with the mentor? | |
| [23:15] <JohnPinWa> persia: Okay but how did you find that number? | |
| [23:15] <JohnPinWa> Sorry, I see it now. Okay, what's next. | |
| [23:15] <JohnPinWa> ? | |
| [23:16] <persia> JohnPinWa: The mentors for the bug are listed at the top of the bug. Click the mentors name. | |
| [23:16] <persia> That will show the bugs page for the mentor. The Overview tab will have contact information for the mentor. | |
| [23:16] <JohnPinWa> Which gets me to their launchpad page | |
| [23:17] <persia> Right :) | |
| [23:17] <JohnPinWa> AH HAH!!!! | |
| [23:17] <persia> Then, review the bug along with https://wiki.ubuntu.com/Bugs/Triaging, and if you get stuck, try to contact the mentor here. | |
| [23:17] <james_w> it doesn't look like they are online at the moment, but I am sure I have seen them in here. | |
| [23:17] <JohnPinWa> and WOO HOO!!! | |
| [23:18] <JohnPinWa> Damn I've spent the DAY trying to find that out. | |
| [23:18] <persia> JohnPinWa: Now, 120746 was only an example on the process of identifying and contacting the mentor. You might want to pick another. | |
| [23:18] <persia> Also, many people like to just try a couple, and ask for help here if they get stuck: you might consider joining #ubuntu-bugs-announce, and trying to triage a few when they come in. | |
| [23:19] <JohnPinWa> Is it acceptable to e-mail someone directly from their launchpad page asking for mentoring? Looking for manners? | |
| [23:19] <persia> If you have questions, or need help, asking here is the best way to get a response from anyone. | |
| [23:20] <JohnPinWa> persia: Thanks. I'm on the mailing list and have been looking at bugs. Most don't deal with anything I have installed or use regularly. | |
| [23:20] <persia> You can email someone, but it's best to do so only if you have a specific interest in that bug. If you're just looking for general guidance on triage, better to just ask questions here, so you can get an answer from anyone. | |
| [23:20] <JohnPinWa> persia: Thanks. Will do. | |
| [23:20] <persia> JohnPinWa: Good luck. | |
| [23:20] <JohnPinWa> persia: I'll need it. Thanks. | |