Hallo, I worked with Amarok and it crashed 3times. The Assistent for automtatic bug reports started, requesting me to install some pakets for debug symbols. I entered my root-password and OpenSuse 12.2 downloaded the stuff, but I still couldn´t sent the message. So it brought me here to report it manual. I run OpenSuse 12.2 under an Asus X51RL Notebook. It has 2GB RAM, ATI Radeon Express 100 Graphic Card and an Intel Dual Core @1.6 Ghz. Hope this infos will help. Thanks for your time Greetings Reproducible: Sometimes Steps to Reproduce: 1. Run Firefox 2. Run Amarok 3. Use Metabrainz to tagg some OGG Files. Actual Results: Amarok crashed saying something about PID. The automatic assistent for reporting bugs started collecting data for backtrace. I installed additional pakets for debugging when requested, but coudn´t sent the message automatically, so I was requested to report i manually. Expected Results: While listening to the album I wanted to write the tags in and download the cover.
If this is with Amarok 2.6, please ask in a openSUSE forum how to install the needed debug packages, and add an updated backtrace. See also http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports
Any news about this? Please also specify the version in the Version field.
Am Sonntag, 21. Oktober 2012, 09:10:32 schrieben Sie: > https://bugs.kde.org/show_bug.cgi?id=308173 > > --- Comment #2 from Myriam Schweingruber <myriam@kde.org> --- > Any news about this? Please also specify the version in the Version field. Dear Myriam, I try to answer your questions as exact as possible. My Amarok Version is compiled at September the 6th 2012. When working longer with the app it freezes or crahes down. The assistant appears but has never enough infos for a bugtracking. I hope this code helps: amarok PID 2404 Signal: Segmentation fault (11) I am really fed up about OpenSuse 12.3 now. New Updates ervery day but after every update something doesn´t work anymore :-( Greetings
Well, we need a complete backtrace, please see the link given in comment #1, you will have to install additional packages.
Am Sonntag, 21. Oktober 2012, 11:45:51 schrieben Sie: > https://bugs.kde.org/show_bug.cgi?id=308173 > > Myriam Schweingruber <myriam@kde.org> changed: > > What |Removed |Added > ---------------------------------------------------------------------------- > Version|unspecified |2.6.0 > > --- Comment #4 from Myriam Schweingruber <myriam@kde.org> --- > Well, we need a complete backtrace, please see the link given in comment #1, > you will have to install additional packages. As I already said the backtrace doesn´t work. I installed the additional packages several times, it still doesn´t work just saying "there was an error."
(In reply to comment #5) > As I already said the backtrace doesn´t work. I installed the additional > packages several times, it still doesn´t work just saying "there was an > error." Did you try running it with gdb? Again, see the link provided in comment #1. It is almost impossible not to get a backtrace for a crash when run with gdb, please follow these instructions.
Am Montag, 22. Oktober 2012, 00:49:20 schrieben Sie: > https://bugs.kde.org/show_bug.cgi?id=308173 > > --- Comment #6 from Myriam Schweingruber <myriam@kde.org> --- > (In reply to comment #5) > > > As I already said the backtrace doesn´t work. I installed the additional > > packages several times, it still doesn´t work just saying "there was an > > error." > > Did you try running it with gdb? Again, see the link provided in comment #1. > It is almost impossible not to get a backtrace for a crash when run with > gdb, please follow these instructions. I try to run it with gdb. Let´s see if it can find something. The automatic error report in amarok still doesn´t work, but i installed all debug symbols. amarok runs fine for days, then it crashes 2 or 3 times in row. seems to be a core dump, something with the memory just saying segmentation fault.
In your description you said it was crashing when trying to tag an ogg file, shouldn't be that hard to get a backtrace with gdb if you reproduce these steps.
Closing for lack of feedback, Please feel free to reopen if you can reproduce this with Amarok 2.6 or later and provide a new backtrace, as requested.