Comment 1 for bug 1211512

Revision history for this message
Marcus Lundgren (marcus-lundgren) wrote :

Unfortunately, that log doesn't say much. As you say that this is an recurring bug for you, I would like you to do two things, and attach the outputs separately to this bug report. If you encounter any problems, or have any question, don't be afraid to ask!

Make sure that Noise is completely closed prior to the steps. You can do this running the following:

$ killall noise

*** 1. ***
In order to give better debug output, please start Noise using the following command in your terminal:

$ noise -d

Attach the output similarly as you did with your log.

*** 2. ***

(This step is based on this guide: https://wiki.debian.org/HowToGetABacktrace)

In order to actually pinpoint where it is happening, you'll have to start Noise using a command called gdb. But before we do this, we need to install some packages:

$ sudo apt-get install noise-dbg gdb

If no errors was shown, execute the following command:

$ gdb noise

When you see "(gdb)", you simply type the letter "r" and press enter. This will start Noise. When Noise crashes, you'll yet again see "(gdb)". Type in the two letters "bt", copy the output and attach the output to this bug.

If Noise is simply frozen when it has crashed, then press Ctrl+C in the terminal window. This will make you see the "(gdb)" in the terminal and then you can follow the instructions above (i.e. entering "bt").