GNOME Bugzilla – Bug 630260
Banshee doesn't start up and hangs at "Adding context page wikipedia"
Last modified: 2020-03-17 08:52:51 UTC
I've installed banshee 1.7.6 and it doesn't starts. The log shows that the startup hangs at a certain point and doesn't go any father. [thomas@archie ~]$ banshee-1 --debug ** Running Mono with --debug ** [1 Info 15:20:14.556] Running Banshee 1.7.6: [source-tarball (linux-gnu, x86_64) @ 2010-09-21 14:50:23 CEST] [1 Debug 15:20:14.572] Initializing GTK [1 Debug 15:20:16.490] Post-Initializing GTK [1 Debug 15:20:16.508] Configuration client extension loaded (Banshee.GnomeBackend.GConfConfigurationClient) [1 Debug 15:20:16.514] Using default gconf-base-key [1 Debug 15:20:16.548] Bus.Session.RequestName ('org.bansheeproject.Banshee') replied with PrimaryOwner [1 Debug 15:20:16.620] Core service started (DBusServiceManager, 0.001319) [1 Debug 15:20:16.623] Registering remote object /org/bansheeproject/Banshee/DBusCommandService (Banshee.ServiceStack.DBusCommandService) on org.bansheeproject.Banshee [1 Debug 15:20:16.631] Core service started (DBusCommandService, 0.010656) [1 Debug 15:20:16.705] Opened SQLite (version 3.7.2) connection to /home/thomas/.config/banshee-1/banshee.db [1 Debug 15:20:16.706] Core service started (DbConnection, 0.074953) [1 Debug 15:20:16.710] Database version 43 is up to date [1 Debug 15:20:16.737] Core service started (PreferenceService, 0.009852) [1 Debug 15:20:16.737] Registering remote object /org/bansheeproject/Banshee/SourceManager (Banshee.Sources.SourceManager) on org.bansheeproject.Banshee [1 Debug 15:20:16.737] Core service started (SourceManager, 0.00072) [1 Debug 15:20:16.754] Core service started (MediaProfileManager, 0.00024) [1 Debug 15:20:16.756] Registering remote object /org/bansheeproject/Banshee/PlayerEngine (Banshee.MediaEngine.PlayerEngineService) on org.bansheeproject.Banshee [1 Debug 15:20:16.758] Core service started (PlayerEngine, 0.004711) [1 Debug 15:20:16.775] Registering remote object /org/bansheeproject/Banshee/PlaybackController (Banshee.PlaybackController.PlaybackControllerService) on org.bansheeproject.Banshee [1 Debug 15:20:16.776] Core service started (PlaybackController, 0.003746) [1 Debug 15:20:16.785] Starting - Startup Job [1 Debug 15:20:16.786] Core service started (JobScheduler, 0.009621) [1 Debug 15:20:16.805] IO provider extension loaded (Banshee.IO.Gio.Provider) [1 Debug 15:20:16.838] Loaded HardwareManager backend: Banshee.Hardware.Gio [1 Debug 15:20:16.842] Core service started (HardwareManager, 0.056224) [1 Debug 15:20:16.844] Bus.Session.RequestName ('org.bansheeproject.CollectionIndexer') replied with PrimaryOwner [1 Debug 15:20:16.845] Registering remote object /org/bansheeproject/Banshee/CollectionIndexerService (Banshee.Collection.Indexer.CollectionIndexerService) on org.bansheeproject.CollectionIndexer [1 Debug 15:20:16.847] Core service started (CollectionIndexerService, 0.005358) [1 Debug 15:20:16.849] Core service started (SaveTrackMetadataService, 0.001702) [1 Debug 15:20:16.859] Adding icon theme search path: /usr/share/banshee-1/icons [1 Debug 15:20:16.860] Core service started (GtkElementsService, 0.010907) [1 Debug 15:20:16.862] Core service started (InterfaceActionService, 0.001537) [1 Debug 15:20:16.965] Extension actions loaded: MetadataFixActions [1 Debug 15:20:16.966] Registering remote object /org/bansheeproject/Banshee/GlobalUIActions (Banshee.Gui.GlobalActions) on org.bansheeproject.Banshee [1 Debug 15:20:16.967] Album artwork path set to /home/thomas/.cache/media-art [1 Debug 15:20:16.988] Core service started (ArtworkManager, 0.021962) [1 Debug 15:20:16.988] Core service started (BookmarksService, 0.000145) [1 Debug 15:20:17.219] Adding context page lastfm-recommendations [1 Debug 15:20:17.245] Adding context page wikipedia -> banshee just hangs at this step for hours
Does it happen every time? If yes, does it happen when you start banshee with --disable-dbus as an argument?
It does happen every time - what basically means that I'm using Rhythembox as spare music player in the meantime. Same result with --disable-dbus Banshee 1.7.5 didn't have any problem to start up. Downgrading to 1.6 works if I delete the ~/.config/banshee-1 folder (probably the database is not backwards compatible). [thomas@archie ~]$ banshee-1 --debug --disable-dbus ** Running Mono with --debug ** [1 Info 17:57:28.560] Running Banshee 1.7.6: [source-tarball (linux-gnu, x86_64) @ 2010-09-21 14:50:23 CEST] [1 Debug 17:57:28.576] Initializing GTK [1 Debug 17:57:30.439] Post-Initializing GTK [1 Debug 17:57:30.456] Configuration client extension loaded (Banshee.GnomeBackend.GConfConfigurationClient) [1 Debug 17:57:30.463] Using default gconf-base-key [1 Debug 17:57:30.554] Core service started (DBusServiceManager, 0.001325) [1 Debug 17:57:30.556] Core service started (DBusCommandService, 0.001811) [1 Debug 17:57:30.628] Opened SQLite (version 3.7.2) connection to /home/thomas/.config/banshee-1/banshee.db [1 Debug 17:57:30.629] Core service started (DbConnection, 0.072564) [1 Debug 17:57:30.633] Database version 43 is up to date [1 Debug 17:57:30.658] Core service started (PreferenceService, 0.009333) [1 Debug 17:57:30.659] Core service started (SourceManager, 0.000602) [1 Debug 17:57:30.670] Core service started (MediaProfileManager, 0.000565) [1 Debug 17:57:30.672] Core service started (PlayerEngine, 0.002719) [1 Debug 17:57:30.688] Core service started (PlaybackController, 0.002085) [1 Debug 17:57:30.697] Starting - Startup Job [1 Debug 17:57:30.698] Core service started (JobScheduler, 0.010496) [1 Debug 17:57:30.718] IO provider extension loaded (Banshee.IO.Gio.Provider) [1 Debug 17:57:30.748] Loaded HardwareManager backend: Banshee.Hardware.Gio [1 Debug 17:57:30.752] Core service started (HardwareManager, 0.053732) [1 Debug 17:57:30.754] Core service started (CollectionIndexerService, 0.001784) [1 Debug 17:57:30.756] Core service started (SaveTrackMetadataService, 0.001966) [1 Debug 17:57:30.765] Adding icon theme search path: /usr/share/banshee-1/icons [1 Debug 17:57:30.766] Core service started (GtkElementsService, 0.009912) [1 Debug 17:57:30.767] Core service started (InterfaceActionService, 0.001501) [1 Debug 17:57:30.869] Extension actions loaded: MetadataFixActions [1 Debug 17:57:30.871] Album artwork path set to /home/thomas/.cache/media-art [1 Debug 17:57:30.891] Core service started (ArtworkManager, 0.021596) [1 Debug 17:57:30.891] Core service started (BookmarksService, 0.000147) [1 Debug 17:57:31.107] Adding context page lastfm-recommendations [1 Debug 17:57:31.132] Adding context page wikipedia -> banshee stops
Thanks. Can you post a thread dump? ( http://banshee.fm/contribute/file-bugs/ -> kill command )
Created attachment 170772 [details] Log file of banshee hanging at "Adding context page wikipedia" Log file of Banshee produced the following way: 1) Start banshee with banshee-1 --debug 2) Wait a few seconds until it hangs at "Adding context page wikipedia" 3) kill banshee with: kill -s QUIT $(pidof banshee-1); cp ~/.config/banshee-1/log ~/Desktop/banshee.log
PS: banshee starts after the kill command. Maybe I start banshee this way instead of using Rhythmbox :-)
Heh, that's an awful workaround. Can you check if it still happens if you disable the wikipedia extension?
Created attachment 170777 [details] Banshee starts with wiki extension disabled and freezes as soon as it is enabled You are right! Banshee starts as expected with the wiki extension disabled. As soon as I enable the extension in the preferences menu it freezes. I did: 1) start banshee with banshee-1 --debug -> banshee freezes 2) defreez banshee with "kill -s QUIT $(pidof banshee-1)" 3) disable the wiki extension 4) quit and restart banshee -> things are going well 5) enable wiki extension -> banshee freezes 6) generate a log file with "kill -s QUIT $(pidof banshee-1); cp ~/.config/banshee-1/log ~/Desktop/banshee.log"
Do the amazon store or the miro extension work for you ? Which versions of webkit (or libwebkit) and libsoup do you have ? Could you also delete the cookie store used by the browser embedded in banshee : rm ~/.config/banshee-1/ossifer-browser-cookies.* Doing this means you would have to login again to amazon in Banshee. It doesn't affect "real" web browsers.
I don't use the amazon extension, but if I enable it and click on it I can see the amazon store. Seems to be working. Same thing for miro. I've deleted the hole ~/.config/banshee-1 folder already a few times, without any success. My system uses: [thomas@archie ~]$ pacman -Qs webkit local/epiphany 2.30.5-1 (gnome) A GNOME2 web browser based on the WebKit rendering engine. local/libwebkit 1.2.4-1 an opensource web content engine, derived from KHTML and KJS from KDE local/webkit-sharp 0.3-1 Mono/.NET bindings for the WebKit rendering engine When i enable the wiki extension banshee freezes (as I told you). After the killing it defreezes and I can open the context panel and browse the wikipedia. So I don't reckon that it is the surf-engine. Now I have disabled every extension but cover art fetching and iPod support. Banshee works like a charm! I made a new log file produce in the same manner as before. In the last log there where some other processes going on from BPM detection. This one should be more clarifying.
Created attachment 170787 [details] Some log as in comment 7, but with less extensions enabled
Maybe this bug is familiar with Bug 627441. They are having similar problem with the podcast extension.
Ups, I over read that you were asking about the libsoup: [thomas@archie ~]$ pacman -Qs libsoup local/libsoup 2.30.2-2 GNOME HTTP Library - base library local/libsoup-gnome 2.30.2-2 GNOME HTTP Library - GNOME libraries
(In reply to comment #11) > Maybe this bug is familiar with Bug 627441 I don't think it's the same bug, since this one happens with dbus disabled.
Same Bug still occurs in 1.8.0
Banshee is not under active development anymore and had its last code changes more than three years ago. Its codebase has been archived. Closing this report as WONTFIX as part of Bugzilla Housekeeping to reflect reality. Please feel free to reopen this ticket (or rather transfer the project to GNOME Gitlab, as GNOME Bugzilla is being shut down) if anyone takes the responsibility for active development again. See https://gitlab.gnome.org/Infrastructure/Infrastructure/issues/264 for more info.