On Tue, 01 Mar 2011 19:30:02 +0100 AG wrote:
However, attempting to capture this output via amarok --debug >
amarok.txt (or | amarok.txt) doesn't capture anything at all in a text
format that I can copy and paste as part of this request for help.
Two questions, then:
(1) how do I capture all of the debugging output from amarok --debug?
How about `amarok --debug 2> amarok_err.txt` ?
(2) any initial thoughts on why Amarok might start to crash today? I
updated today and rebooted yesterday, and Amarok was working fine
for me
yesterday after I booted up. So, it may have been something in today's
updates (I only had 7 packages updated, but cannot remember which).
If you use aptitude to update your system, it keeps the update
history in /var/log/aptitude. Maybe you find something there.