abrt 1.0.9 detected a crash. architecture: x86_64 Attached file: backtrace cmdline: banshee-1 /usr/lib64/banshee-1/Banshee.exe --redirect-log --play-enqueued component: mono executable: /usr/bin/mono global_uuid: af17db5f9b149aff7c2087044d0802205b90a0a3 kernel: 2.6.32.11-99.fc12.x86_64 package: mono-core-2.4.3.1-1.fc12 rating: 4 reason: Process /usr/bin/mono was killed by signal 6 (SIGABRT) release: Fedora release 12 (Constantine)
Created attachment 411410 [details] File: backtrace
Package: mono-core-2.4.3.1-1.fc12 Architecture: i686 OS Release: Fedora release 12 (Constantine) How to reproduce ----- 1.Add banshee,xchat in the notification area 2.Remove the notification area from the panel by right clicking on it, and the crash occurs
Package: mono-core-2.4.3.1-1.fc12 Architecture: x86_64 OS Release: Fedora release 12 (Constantine) Comment ----- This occurred just after quitting the new version of banshee: banshee-1.6.0-1.fc12.x86_64
Looks to be a banshee bug, reassigning.
(In reply to comment #3) > This occurred just after quitting the new version of banshee: > banshee-1.6.0-1.fc12.x86_64 Here too.
(In reply to comment #3) > This occurred just after quitting the new version of banshee: > banshee-1.6.0-1.fc12.x86_64 I have seen this behavior only with an activated Alarm Clock Extension. 1. Please test, whether a specific extension causes the problem: - turn off all extensions - try to reproduce - turn again all extensions one by one to check, which one is causing the problem 2. If the problem can be reproduced with all extensions disabled: - start banshee on the command line (xterm etc.) with "banshee-1 --debug" - please also provide a new backtrace - and the complete debug output of the terminal
Haven't seen this crash yet with latest update in F-13: banshee-1.6.1-1.fc13.x86_64
I can't reproduce the problem - neither in F12 nor in F13. I'll close the bug now as WORKSFORME. Claudio: If you still see the issue, please re-open the bug report and answer the questions from comment #6. Thanks!