After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 554426 - banshee "crashed" when trying to listen to radio
banshee "crashed" when trying to listen to radio
Status: RESOLVED DUPLICATE of bug 554393
Product: banshee
Classification: Other
Component: general
1.2.1
Other All
: Normal critical
: 1.x
Assigned To: Banshee Maintainers
Banshee Maintainers
Depends on:
Blocks:
 
 
Reported: 2008-09-30 13:04 UTC by Jakub 'Livio' Rusinek
Modified: 2008-09-30 17:33 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
log after issuing command from "Banshee » filing bugs" (2.02 KB, text/plain)
2008-09-30 13:05 UTC, Jakub 'Livio' Rusinek 		Details

Description Jakub 'Livio' Rusinek 2008-09-30 13:04:29 UTC 
Please describe the problem:
banshee plays radio and displays it's own window with "crash log".

Steps to reproduce:
1. start banshee
2. play a radio


Actual results:
while radio is playing, banshee displays message about critical exception

Expected results:
ermmm... radio should be playing, like it did, but without critical exceptions

Does this happen every time?
strange, but this happened, while listening to radio, for the first time

Other information:
Comment 1 Jakub 'Livio' Rusinek 2008-09-30 13:05:53 UTC 
Created attachment 119644 [details]
log after issuing command from "Banshee » filing bugs"

this log contains what banshee displayed on its own.
Comment 2 Jakub 'Livio' Rusinek 2008-09-30 13:07:22 UTC 
d'oh! I started banshee again and it does this again!

computer was not hibernated, so that's not issue with wrong suspended dbus, for example.
Comment 3 Gabriel Burt 2008-09-30 17:33:32 UTC 
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.


*** This bug has been marked as a duplicate of 554393 ***