GNOME Bugzilla – Bug 600231
Banshee occasionally freezes on startup
Last modified: 2010-09-21 12:59:29 UTC
Created attachment 146643 [details] screenshot of a frozen Banshee Every now and then, I try to start Banshee (usually from Gnome-Do, but this time by opening an mp3 file from Nautilus) and the main window will load, then freeze. Killing Banshee and restarting the program usually works fine. Here's what happens: 1. I start Banshee (clicking its icon, launching from Gnome-Do, opening an mp3). 2. The main window is drawn, but none of the widgets load. 3. The window stops loading and dims (becomes unresponsive). 4. The only option is to kill Banshee and try again. I can't find a pattern, or any reliable way to reproduce this, but I killed Banshee using: kill -s QUIT $(pidof banshee-1); cp ~/.config/banshee-1/log ~/.Desktop/banshee.log I'll attach the log and a picture of the frozen Banshee. I'm using Ubuntu Karmic x64, Mono 2.4.2.3 and Banshee from git.
Created attachment 146644 [details] banshee's log of the issue And here's the log. This line > (Banshee:6184): Gtk-CRITICAL **: gtk_container_child_set_property: > assertion `child->parent == GTK_WIDGET (container)' failed seems the same as the 5th comment of a downstream bug report[1], but that might be completely unrelated because I'm not having any of the symptoms of that bug (issues with playback). [1] https://bugs.launchpad.net/ubuntu/+source/banshee/+bug/450276 (Also, it seems a bit presumptuous for me to confirm my own bug report; did Bugzilla do that for me automatically?)
Comment on attachment 146644 [details] banshee's log of the issue Bugs opened by people with additional bugzilla powers are automatically set as NEW.
I think all the ways of starting banshee you mentionned pass the "play-enqueued" option. Not sure about Gnome-Do. Does it ever happen if you start banshee without this option, for example from a terminal ?
(In reply to comment #2) > (From update of attachment 146644 [details]) > Bugs opened by people with additional bugzilla powers are automatically set as > NEW. I kind of figured as much; good to know. (In reply to comment #3) > I think all the ways of starting banshee you mentionned pass the > "play-enqueued" option. Not sure about Gnome-Do. > > Does it ever happen if you start banshee without this option, for example from > a terminal ? Good question. If the issue had happened from the terminal, I would have had a stack trace for this awhile ago, and I probably wouldn't have waited until now to report it. I'm not 100% sure, but it seems like I've never seen this bug when launching banshee from the terminal. I'll try starting Banshee from the terminal with the "play-enqueued" option to see if I can reproduce it that way. Until then, I'll mark this as NEEDINFO.
I'm not as sure now what's really behind this. When starting from the terminal, I noticed that the > (Banshee:6184): Gtk-CRITICAL **: gtk_container_child_set_property: > assertion `child->parent == GTK_WIDGET (container)' failed line happens every time I open Banshee, whether I use "play-enqueued" or not. It doesn't seem to have any correlation with Banshee freezing. I haven't been able to produce a freeze from the terminal, though. I'll keep looking for something reproduce-able with this bug.
Per my last comment, I'm removing the "Gtk-CRITICAL" part from this bug's description. I haven't actually seen it recently, but I'll leave it open just a little longer.
Well, I haven't seen this in quite a while (not since I reported it). I did reinstall my system since then, so it's very possible that this problem was caused by external factors. I'll reopen if I run into it again, but for now I guess I'll just call it INVALID.
Good day. I have a similar problem with freezing banshee. But it has nothing to do with GnomeDo. Every time I run banshee for the first time, it freezes, but after killall banshee player runs fine. There is a suspicion that this has something to do with podcasting. Add their log file.
Created attachment 155285 [details] Debug-log Debug-log with freez banshee
Hi Max, You don't need --debug-addins or --debug-sql, but you do need to run the kill -s QUIT command mentioned here (http://banshee-project.org/contribute/file-bugs/) *while* Banshee is frozen, then attach the log or terminal output. Thanks!
I still run into this infrequently as well, but my issue might be different because I definitely don't run into it every first time I start Banshee. Either way, this seems worth reopening.
Created attachment 155400 [details] correct banshee log Gabriel, thanks :) I noticed you next regularity, perhaps it should consider. Banshee always hangs only when you first start the day! Ie You can start the morning and then the banshee hangs. Then in the evening and all went well. Or run for the first time in the evening, then also banshee will hang. It seems that this is connected with some statistics.
*** Bug 611523 has been marked as a duplicate of this bug. ***
I haven't seen this issue in months. In my case, I'm assuming that the problem has either been fixed in the past 6 months, or else it was related to older versions of dependencies, which got upgraded when I installed Ubuntu 10.04 in April. Max, if you can still reproduce the problem, you might want to open a new bug report.