New install, Exaile issue
Just installed Trisquel 4.5 from the 32 bit iso download.
Exaile not working. Have tried unistalling and reinstalling, before and after initial updates. Have also reinstalled and same result.
From the terminal I get:
chris@thelido:~$ exaile
INFO : Loading Exaile 0.3.2.0...
INFO : Loading settings...
** Message: pygobject_register_sinkfunc is deprecated (GstObject)
INFO : Loading plugins...
INFO : Loading collection...
gdbm fatal: read error
Any ideas?
Banshee works, will do the job!
I did read about that but assumed it must have been sorted as Banshee was in the list in Trisquel's add/remove programs application.
Or should it not be there?
Mono's problem is a patent issue. It isn't a software freedom issue. Mono is free software which is why it is included. Software with patent issues can be included in free distros assuming it is free (https://www.gnu.org/distros/free-system-distribution-guidelines.html)
Here is some more reading on the subject
1) https://www.fsf.org/news/dont-depend-on-mono
2) https://www.fsf.org/news/2009-07-mscp-mono
Ta for the links, understand a bit more now.
Anyway, back to my Exaile issue....!
What version of Exaile are you using? I was reading this on the exaile mailing list ( https://groups.google.com/group/exaile-users/browse_thread/thread/2ec3b505c46b44eb/f5167c4acffe347b?lnk=gst&q=pygobject#f5167c4acffe347b ) and it says:
* Fixed startup crash on development version of PyGObject.
This may be the bug you are experiencing. I luckily don't have this bug but it might be fixed by upgrading to the newest version because on my 4.5 install I have the version right before that.
Since you seem opened to alternatives, you can take a look at Rythmbox too: http://projects.gnome.org/rhythmbox
It is, of course, in Trisquel's repositories.
Indeed, I'm happy with Rhythymbox as well. One of my favourite players is ncmpp so I may have a look at setting that up.
Removed old, installed new, same error.
Could be some user settings from a previous distro in my /home? I'll see if I can find whatever traces exaile may have left behind.
What happens when you type exaile --version into terminal?
Maybe backup your settings config in /home//.config/exaile directory. If you copied it over from another system that could possible be causing the problem you may be right there.
Have renamed the user exaile directory, no change.
Version is
____ _ __ __
/ __/_ _____ _(_) /__ / /
/ _/ \ \ / _ `/ / / -_)_/
/___//_\_\\_,_/_/_/\__(_) v0.3.2.1
I am a member!
If you run the following
exaile --debug
you will get debug output. This might be more helpful.
SirGrant, Adrian, I'll get back to you later today when I get home.
Here we go!
chris@thelido:~$ exaile --debug
19:46:03,475:INFO : Loading Exaile 0.3.2.1... (xl.main)
19:46:03,475:INFO : Loading settings... (xl.main)
19:46:03,578:DEBUG : Provider tags registered for service covers (xl.providers)
19:46:03,578:DEBUG : Provider localfile registered for service covers (xl.providers)
19:46:03,581:DEBUG : Normal playback engine selected. (xl.player)
** Message: pygobject_register_sinkfunc is deprecated (GstObject)
19:46:03,724:DEBUG : Provider tracknumber registered for service tag_formatting (xl.providers)
19:46:03,730:DEBUG : Provider discnumber registered for service tag_formatting (xl.providers)
19:46:03,731:DEBUG : Provider artist registered for service tag_formatting (xl.providers)
19:46:03,731:DEBUG : Provider __length registered for service tag_formatting (xl.providers)
19:46:03,731:DEBUG : Provider __rating registered for service tag_formatting (xl.providers)
19:46:03,731:DEBUG : Provider __last_played registered for service tag_formatting (xl.providers)
19:46:03,731:DEBUG : Provider filename registered for service tag_formatting (xl.providers)
19:46:03,822:DEBUG : ~/.exaile/music.db did not exist, old exaile version not detected (migration_200907100931)
19:46:03,822:DEBUG : Will not migrate and overwrite data. (migration_200907100931)
19:46:03,822:INFO : Loading plugins... (xl.main)
19:46:03,823:DEBUG : Provider equalizer-10bands registered for service postprocessing_element (xl.providers)
19:46:03,823:DEBUG : Loaded plugin equalizer (xl.plugins)
19:46:03,830:DEBUG : Loaded plugin lyricsviewer (xl.plugins)
Traceback (most recent call last):
File "/usr/lib/exaile/xl/plugins.py", line 123, in enable_plugin
if not plugin: raise Exception("Error loading plugin")
Exception: Error loading plugin
19:46:03,830:WARNING : Unable to enable plugin shoutcast (xl.plugins)
19:46:03,831:DEBUG : Exception caught!
Traceback (most recent call last):
File "/usr/lib/exaile/xl/plugins.py", line 123, in enable_plugin
if not plugin: raise Exception("Error loading plugin")
Exception: Error loading plugin
(xl.plugins)
19:46:03,831:DEBUG : Loaded plugin lastfmcovers (xl.plugins)
19:46:03,832:DEBUG : Loaded plugin lyricsfly (xl.plugins)
19:46:03,867:DEBUG : Loaded plugin lyricwiki (xl.plugins)
19:46:03,889:DEBUG : Provider cd registered for service hal (xl.providers)
19:46:03,889:DEBUG : Loaded plugin cd (xl.plugins)
19:46:03,890:DEBUG : Provider massstorage registered for service hal (xl.providers)
19:46:03,890:DEBUG : Loaded plugin massstorage (xl.plugins)
19:46:03,899:DEBUG : Loaded plugin notifyosd (xl.plugins)
19:46:03,899:INFO : Loading collection... (xl.main)
gdbm fatal: read error
I am a member!
gdbm is a database module, so it's possible the exaile database is corrupted.
This file is located at ~/.local/share/exaile/music.db (note: not ~/.config/exaile)
If you remove this file exaile will generate a new blank one. See if that helps
..is the answer!
Was looking for it but couldn't find it earlier.
Cheers