[don_crissti]

@ users having troubles:

When asking for help related to software problems keep in mind that providing accurate information is critical. Here are some advices on how to do that:

1. Make sure your system (apps included) is up to date. Follow sarcastic_bastard's instructions HERE.

2. Logout then log back in (reason for a new, fresh gnome session explained at no. 4) and see if the problem persists.

3. Start the application in terminal and check/post the output. Most often, the output is quite relevant and forum members/developers should have little trouble figuring out what's wrong on your side.
If there's too much output, you can use some CLI magic to save the output to a file: command 2>&1 | tee /path/to/file

Code: Select all

rhythmbox 2>&1 | tee ~/debuglog

the above will save the output produced by rhythmbox to a file named debuglog in your home dir.

4. Sometimes it is very hard or impossible to replicate a bug/problem using the terminal (e.g. a buggy nautilus extension, problems with gnome-settings-daemon, hal etc). So, what to do ? There's a hidden file in your home dir named .xsession-errors. Inside you can find almost all errors and output produced on your system during your current gnome session.

@ forum members:

If you know of any other techniques/means to get the right info please post here.

Thank you !