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 628682 - Banshee sometimes unresponsive at startup
Banshee sometimes unresponsive at startup
Status: RESOLVED DUPLICATE of bug 627441
Product: banshee
Classification: Other
Component: general
1.7.4
Other Linux
: Normal normal
: 1.x
Assigned To: Banshee Maintainers
Banshee Maintainers
Depends on:
Blocks:
 
 
Reported: 2010-09-03 10:07 UTC by Simon B
Modified: 2010-09-04 10:24 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
log file produced after kill -s QUIT of the banshee-1 process (running in debug mode) (11.83 KB, patch)
2010-09-03 10:07 UTC, Simon B
none Details | Review
output to stdout when running banshee-1 --debug (18.71 KB, text/plain)
2010-09-03 10:09 UTC, Simon B
  Details

Description Simon B 2010-09-03 10:07:55 UTC
Created attachment 169416 [details] [review]
log file produced after kill -s QUIT of the banshee-1 process (running in debug mode)

Banshee UI is unresponsive when started. Window goes grey on ubuntu after 5 seconds and requires force quit. It is not possible to start playing any music before the crash, and it you never see the progress bar in the bottom left (scanning library?)

I cannot always reproduce this at will, but happens on a daily basis and often will happen 5 times in a row.

Performing a kill -s QUIT on the banshee-1 process revives the application and music can be played.
Comment 1 Simon B 2010-09-03 10:09:51 UTC
Created attachment 169418 [details]
output to stdout when running banshee-1 --debug

here i run in debug mode, kill the banshee-1 and at the end you see the app is revived and i can play music.
Comment 2 Bertrand Lorentz 2010-09-03 16:55:57 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 bug 627441 ***