=== luciano_ is now known as virusuy [07:04] Hello, I'd like to ask how to proceed with bug 521607 [07:04] Launchpad bug 521607 in openoffice.org (Ubuntu) "Openoffice Writer crashes after inactivity (affects: 8) (heat: 44)" [Undecided,Invalid] https://launchpad.net/bugs/521607 [07:05] It affects quite a number of people (including me) and is a high importance bug [07:05] yet, it gets closed repeatedly because apport does not produce a crasher file [07:06] Is Ubuntu choosing to ignore that crasher bug just because of that? [07:06] I'm happy to follow any procedure given to me to try and produce more information [07:06] In fact, I guess I'll start ooffice in gdb now to see if I can get a stacktrace that way [07:07] Laibsch, we just talked about this. We need a crash report via apport. [07:07] :) [07:08] yes, and we came to no conclusion [07:08] That's not true. I politely advised you to provide a new bug via apport [07:08] the problem is still there. tell me what you want me to do and I will do it. Closing tickets is not bug triage, my friend. Edging things closer to fixing problems (!) is. [07:09] penalvch: and I told you a number of times that apport is not producing the files you are requesting. So, what's the point of another ticket? You'll close it just the same, with the same reasoning. [07:10] penalvch: now, you tell me what you intend to do with the problem! [07:11] Laibsch, well let's work together to get apport working and take it from there. [07:12] Sure. [07:12] I've already followed all the steps you gave so far [07:13] before coming here. before reopening the ticket [07:13] so, I'd say the ball has always been in your field. And that was my point, your reaction to it being there was to close the ticket which I find unacceptable for proper triage [07:16] Laibsch, well I did not just close the ticket unjustly. It was a crasher bug with no crash file. I followed the proper Triage guidelines -> https://wiki.ubuntu.com/Bugs/Responses#Missing%20a%20crash%20report%20or%20having%20a%20.crash%20attachment [07:16] Laibsch, but let's not digress any further and continue to work on your apport [07:16] :) [07:17] Laibsch: does your /etc/default/apport have enabled=1 ? [07:18] not today [07:18] it did in the past [07:18] (like two weeks ago) [07:18] and the problem was still there [07:18] Laibsch: ah everytime your restart you have to re-enable apport [07:18] I DID!!! [07:18] OK? [07:19] look at the file, look at the command you gave [07:19] Laibsch: Ok. Whenever I restart I perform at the Terminal: sudo service apport start force_start=1 [07:19] penalvch: I already told you I ALREADY did that [07:19] I told you here, in private chat and in the ticket [07:19] OK? [07:20] and I have in the past had enabled=1 [07:20] in the file you mentioned [07:20] Laibsch: Ok. Do you have libreoffice-dbg installed? [07:20] I had restarted the computer at that time. I reproduced the crash. Yet there was no crasher file [07:21] probably not [07:21] let me check [07:21] I'm not using libreoffice but openoffice (lucid system as I mentioned in the ticket) [07:21] I can't see a dbg package for that [07:25] http://packages.ubuntu.com/search?keywords=openoffice has no string dbg in it, so I guess there is no debug package. Maybe that's the reason for the missing crash file, maybe the proper apport support for it was added in a package past lucid. [07:25] and that's the reason that blindly following some rules is not bug triage. bug triage is about getting closer to fixing problem, not closing the largest number of tickets [07:27] according to comments in the ticket, maverick is also affected. No confirmations for natty or oneiric yet [07:27] Laibsch: Should be uno-libs3-dbg and ure-dbg [07:28] Found that via -> https://launchpad.net/ubuntu/lucid/+source/openoffice.org [07:28] OK, thank you. That's valuable information. Good triage [07:29] I will install those and do one of two things: if still files, expect me back here ;-), otherwise I will do as you suggested and open a new ticket [07:30] Laibsch: Ok. If you have any further OOo bugs/problems, please let us know. We are here to help! ;) [16:04] hello [16:05] i've never used irc so I dont even know if its working... [16:06] working [16:06] hi, thanks [16:07] I'm here because the webpage said this is where i should look for info about how to file a bug [16:07] !bugreport | coski [16:07] Factoid 'bugreport' not found [16:08] !bugs | coski [16:08] coski: If you find a bug in Ubuntu or any of its derivatives, please file a bug using the command « ubuntu-bug » - See https://help.ubuntu.com/community/ReportingBugs for other ways to report bugs - Bugs in/wishes for the IRC bots (not Ubuntu) can be filed at http://bugs.launchpad.net/ubuntu-bots [16:09] I've read that, but the thing is i dont know which package is buggy, what happens to me is: [16:09] suddenly, and randomly, when im using the PC or not, i get a console output (black screen white text) saying: BUG: unable to handle kernel paging request at 0000000200000010 [16:09] and a lot of more info [16:10] i googled that phrase and found a few bugs [16:10] in launchpad [16:10] okay, you can file that after it happens by opeing a terminal and typing ubuntu-bug linux [16:10] but i think they dont relate to my problem [16:10] ahh, ok! [16:10] thanks [16:10] When it a kernel issue, we prefer you file a separate bug report for each computer with a problem [16:11] Every report helps find the real problem and get it fixed [16:11] OK =) so I'll wait for that to happen again, and then I'll run "ubuntu-bug linux" and just follow the instructions [16:11] Thanks [16:12] no, thank you =) bye! [17:51] if I want to report a bug in a man page, should I do the normal ubuntu-bug? [17:54] Find out what package the manpage belongs to and use ubuntu-bug, yeh [17:55] Bug #792844 [17:55] Launchpad bug 792844 in lshw (Ubuntu) "man: "Remove sensible information" (affects: 1) (heat: 6)" [Undecided,New] https://launchpad.net/bugs/792844 [17:56] typo cracks me up. I kinda want to leave it for amusement :) [17:56] :D [17:56] oh that's fun [17:57] . o O (lshw -whimsical) [20:13] CarlFK: best to send that one upstream [20:15] CarlFK: i just checked out the source on natty, the bug is fixed [20:15] aww [20:15] however it still seems present in the french translation [20:15] src/po/fr.po:msgstr "\t-sanitize omet les informations sensibles (comme les numéros de série, etc.)\n" [20:16] but, maybe that's french for sensivite, i don't know, i don't speak french [20:16] oh intersting [20:16] according to google translate it is [20:17] yeh [20:17] correct [20:17] that's quite fun === yofel_ is now known as yofel