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 630815 - Banshee freezes on startup
Banshee freezes on startup
Status: RESOLVED DUPLICATE of bug 627441
Product: banshee
Classification: Other
Component: general
1.7.6
Other Linux
: Normal critical
: 1.x
Assigned To: Banshee Maintainers
Banshee Maintainers
Depends on:
Blocks:
 
 
Reported: 2010-09-28 13:52 UTC by Jeremy
Modified: 2010-09-28 18:25 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
Most recent (26.20 KB, text/plain)
2010-09-28 18:08 UTC, Jeremy 		Details

Description Jeremy 2010-09-28 13:52:20 UTC 
Created attachment 171259 [details]
Output

Banshee will freeze when starting up and I can only get it to work with the command 

kill -s QUIT $(pidof banshee-1)

I think it has something to do with it starting with options like --play-enqued, etc.

I've attached the output.
Comment 1 Gabriel Burt 2010-09-28 15:27:30 UTC 
Hi Jeremy.  Your log didn't include the thread stack trace, unfortunately.  You mention 'kill -s QUIT' which should have done it -- did you run it while Banshee was running and frozen?  I think your issue has already been reported and fixed though -- can you test Banshee from git master, or the upcoming 1.8.0 release?
Comment 2 Jeremy 2010-09-28 16:37:20 UTC 
It may already be fixed, I'm using 1.7.6-0ubuntu1~hyper1+lucid and apparently that's old so I'll try those out.
Comment 3 Jeremy 2010-09-28 18:07:57 UTC 
I tried the latest version and I am still having the bug. I'll attach this log.
Comment 4 Jeremy 2010-09-28 18:08:18 UTC 
Created attachment 171287 [details]
Most recent
Comment 5 Jeremy 2010-09-28 18:08:47 UTC 
And that most recent one is it freezing, and then me running the command to make it responsive again (the kill -s)
Comment 6 Gabriel Burt 2010-09-28 18:25:37 UTC 
The log indicates you're using git revision b93d986, which is too old.  That log was better though, indicating you're seeing the same issue as bug #627441

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