2016-06-09 22:36 GMT+03:00 salamandir <salaman...@hybridelephant.com>: > yes, the last.fm error appears, as well as a whole bunch of other stuff > which may or may not be relevant... and amarok starts now. this is > significant, but i don't know how.
OK, then we can't blame last.fm ;) A more direct way of debugging hang-ups is to run the program is debugger and see the stacktrace. Next time Amarok starts hanging up often on your computer, 1. Run amarok in GDB: gdb amarok (wait for GDB to load...) run --nofork 2. When the UI hangs up, go to the terminal where you started GDB and press Ctrl+C to "pause" the amarok process. 3. See the stacktrace: bt 4. Or even better, see the stacktraces for all threads: thread apply all bt A stacktrace will probably show where in the code it has "hung up". -- Alexander Potashev _______________________________________________ Amarok mailing list Amarok@kde.org https://mail.kde.org/mailman/listinfo/amarok
