Howto file bugs, a must read for dapper users

[freeflying]

So you upgraded to dapper and things start to break, water wet, sky blue - news at 11. We know this, however with your help Dapper might rock even harder.... because you can file bugs.

First identify your bug, if it's a crash here is what you do.

step 1:
go to www.launchpad.net/malone to search the bug database to see if this is a known issue. If is you can add comments to the existing bug confirming the issue and providing whatever feedback the developers request. If not then we jump to step 2.

step 2:
Now we need debug symbols, without debug information your bugreport is pretty useless in terms of getting the bug tracked down.

you'll need the deb-src entries in your /etc/apt/sources.list, these are enabled by default so unless you messed with it, you have these setup properly.

first install the build time dependencies
sudo apt-get build-dep <package>

Then build a package with debug symbols
DEB_BUILD_OPTIONS="nostrip noopt" sudo apt-get source -b <package>

Now install your new package:
sudo dpkg --install <package.deb>

Remember it is useful in many cases to compile libraries which your program accesses with debug as well. Step 3 obtaining your stack trace is up next:

step 3:
Now we start the program under the debugger to get a stack trace.

gdb <program>
(gdb) handle SIG33 pass nostop noprint
(gdb) run <append runtime arguments for the program as needed>

Issue crash conditions in your program then obtain the trace with the following command:

(gdb) thread apply all bt

Copy the entire output to a file (I like program.trace but that's just me)

It is also a very good idea to run the program in a terminal to see if it outputs any messages you can add to the bugreport.

Onwards to the moment we've been waiting for, filing our bug.

step 4:

Go to the Malone website (www.launchpad.net/malone and open up a new bug, attach the trace file, remember to fill in the version of Ubuntu you are running and the version of the program you are running.

Step 5:
Bask in the glory as your Launchpad Karma increases and Dapper becomes a more stable platform.

Have you helped GNOME reach 10x10? || Ubuntu Dapper, how many kitten will it kill today?

(If you are offended by the post, please understand I have Tourette's)

[lindagloria]

初次翻译……望大家多多指正~~~~~~~

[lindagloria]

怎么这么多看不懂的东东…………55555……………………

偶现在才发现…………自己实在是很菜…………连外语都很菜了………………

[jazzi]

怎么这么多看不懂的东东…………55555……………………

偶现在才发现…………自己实在是很菜…………连外语都很菜了………………

有勇气才能进步嘛，感谢lindagloria对这篇文章的领用。
翻译进展如何，能否贴出来，大家一块学习交流一下

[jaguar00]

[lindagloria]

谢谢4楼的朋友，我因为考试和放假，很久没有上，今天看到邮箱里边的消息……

我真的很抱歉……但是我只是试着翻译了一小部分，而且完全不知所云……

真的很对不住大家了……55555…………

俺……那么烂的东东……俺…………俺没脸贴出来…………

[leal]

Howto
如何提交bug，Dapper用户必读

So you upgraded to dapper and things start to break, water wet, sky blue - news at 11. We know this, however with your help Dapper might rock even harder.... because you can file bugs.
最终你升级到了dapper，情况却变得糟糕起来，水总是湿的，天总那么蓝，新闻总会在11点如期而至。凡此种种，众所周知，无论怎样只要有你的帮助，Dapper总能表现更加优异...因为你可以提交bug。 待改进

First identify your bug, if it's a crash here is what you do.
首先要确认你碰到的bug，如果是次（系统或程序）崩溃，那么请按如下步骤：

step 1:
步骤1：
go to www.launchpad.net/malone to search the bug database to see if this is a known issue. If is you can add comments to the existing bug confirming the issue and providing whatever feedback the developers request. If not then we jump to step 2.
访问www.launchpad.net/malone，搜索bug数据库以查看该bug是否已知。若是，你可以为已存在的bug添加评论，确认有此问题并提供开发人员所需的任何反馈。若否，则跳至步骤2。


step 2:
步骤2：
Now we need debug symbols, without debug information your bugreport is pretty useless in terms of getting the bug tracked down.
现在，我们需要调试符号信息（debug symbols），如若没有调试信息，你的bug报告几无用处，因为这样就无法跟踪此bug。

you'll need the deb-src entries in your /etc/apt/sources.list, these are enabled by default so unless you messed with it, you have these setup properly.
你需在/etc/apt/sources.list里加上deb-src相关条目，默认情况下这些条目已被激活，除非你摆弄该文件，总之要进行正确的设置。

first install the build time dependencies
sudo apt-get build-dep <package>
首先安装构建期所需依赖包：
sudo apt-get build-dep <package>

Then build a package with debug symbols
DEB_BUILD_OPTIONS="nostrip noopt" sudo apt-get source -b <package>
然后构建该安装包，需带有调试符号信息：
DEB_BUILD_OPTIONS="nostrip noopt" sudo apt-get source -b <package>

Now install your new package:
sudo dpkg --install <package.deb>
接下来，安装新构建的安装包：
sudo dpkg --install <package.deb>

Remember it is useful in many cases to compile libraries which your program accesses with debug as well. Step 3 obtaining your stack trace is up next:
注意：在很多情况下，把你的程序所要用到的库文件编译成带调试信息一样非常有用。紧接着下一步骤是获取栈跟踪信息。

step 3:
步骤3：
Now we start the program under the debugger to get a stack trace.
接着在调试器里启动程序，以获取栈跟踪信息（stack trace）。

gdb <program>
(gdb) handle SIG33 pass nostop noprint
(gdb) run <append runtime arguments for the program as needed>
gdb <program>
(gdb) handle SIG33 pass nostop noprint
(gdb) run <加上程序运行所需的运行时参数>

Issue crash conditions in your program then obtain the trace with the following command:
在你的程序里触发崩溃条件，然后使用如下命令获取跟踪信息：

(gdb) thread apply all bt

Copy the entire output to a file (I like program.trace but that's just me)
将所有输出拷贝至文件（仅就个人爱好而言，我喜欢把该文件命名为program.trace）

It is also a very good idea to run the program in a terminal to see if it outputs any messages you can add to the bugreport.
还有一个很好的做法，即在终端里运行该程序以查看它是否会输出一些有用信息，然后把它们添加到bug报告里。

Onwards to the moment we've been waiting for, filing our bug.
终于要到我们等待已久的时刻了——提交bug。

step 4:
步骤4：
Go to the Malone website (www.launchpad.net/malone and open up a new bug, attach the trace file, remember to fill in the version of Ubuntu you are running and the version of the program you are running.
访问Malone站点（www.launchpad.net/malone），开启一个新bug，附上跟踪文件（trace file），别忘了还要添上你所用的Ubuntu版本号以及运行的程序版本号。

Step 5:
步骤5：
Bask in the glory as your Launchpad Karma increases and Dapper becomes a more stable platform.
享受阳光，尽享自己的Launchpad Karma值不断增长带来的荣耀吧，与此同时，Dapper也会日渐成长为愈加稳定的平台。

[max0000]

So you upgraded to dapper and things start to break, water wet, sky blue - news at 11. We know this, however with your help Dapper might rock even harder.... because you can file bugs.
最终你升级到了dapper，情况却变得糟糕起来……？？ 。凡此种种，我们皆知，不过有了你的帮助，Dapper或许能表现更为优异...因为你可以提交bug。 待改进

于是你升级到dapper了，系统里总是有些问题；不过水总是湿的，天总是蓝的--到了十一点总是会报新闻。这个大家都知道，只是有你帮忙，Dapper会表现得更优异...因为你可以提交bug。

[leal]

So you upgraded to dapper and things start to break, water wet, sky blue - news at 11. We know this, however with your help Dapper might rock even harder.... because you can file bugs.
最终你升级到了dapper，情况却变得糟糕起来……？？ 。凡此种种，我们皆知，不过有了你的帮助，Dapper或许能表现更为优异...因为你可以提交bug。 待改进

于是你升级到dapper了，系统里总是有些问题；不过水总是湿的，天总是蓝的--到了十一点总是会报新闻。这个大家都知道，只是有你帮忙，Dapper会表现得更优异...因为你可以提交bug。

great

[xiaoyi1180]

天啦，以后每天来这里学英语了。

并且我想如果能够翻译这里所有的文档，那么就算不想成为Linux高手也不可能了。

[alexfaye]

不错不错，通读了一遍翻译的确实很好