exaile lasted rev doesn't start

Bug #296501 reported by Timmie
2
Affects Status Importance Assigned to Milestone
Exaile
Won't Fix
Undecided
Unassigned

Bug Description

exaile updated today wouldn't start!

Revision history for this message
Timmie (timmie) wrote :

see here a log:

:/opt/exaile$ ./exaile
INFO : Loading Exaile 0.2.99.1...
INFO : Loading settings
INFO : Loading plugins...
INFO : Loading collection...
Traceback (most recent call last):
  File "exaile.py", line 47, in <module>
    main()
  File "exaile.py", line 44, in main
    exaile = main.Exaile()
  File "/opt/exaile/xl/main.py", line 68, in __init__
    self.__init()
  File "/opt/exaile/xl/main.py", line 105, in __init
    location=os.path.join(xdg.get_data_dirs()[0], 'music.db') )
  File "/opt/exaile/xl/collection.py", line 70, in __init__
    pickle_attrs=pickle_attrs)
  File "/opt/exaile/xl/trackdb.py", line 104, in __init__
    self.load_from_location()
  File "/opt/exaile/xl/common.py", line 90, in wrapper
    return func(self,*__args,**__kw)
  File "/opt/exaile/xl/trackdb.py", line 159, in load_from_location
    protocol=common.PICKLE_PROTOCOL)
  File "/usr/lib/python2.5/shelve.py", line 225, in open
    return DbfilenameShelf(filename, flag, protocol, writeback)
  File "/usr/lib/python2.5/shelve.py", line 209, in __init__
    Shelf.__init__(self, anydbm.open(filename, flag), protocol, writeback)
  File "/usr/lib/python2.5/anydbm.py", line 80, in open
    raise error, "db type could not be determined"
anydbm.error: db type could not be determined
Exception in thread Thread-2 (most likely raised during interpreter shutdown):
Traceback (most recent call last):
  File "/usr/lib/python2.5/threading.py", line 486, in __bootstrap_inner
  File "/usr/lib/python2.5/threading.py", line 664, in run
  File "/usr/lib/python2.5/threading.py", line 353, in set
  File "/usr/lib/python2.5/threading.py", line 268, in notifyAll
<type 'exceptions.TypeError'>: 'NoneType' object is not callable

Revision history for this message
Adam Olsen (arolsen) wrote :

Probably due to the db format change. Please rm ~/.local/share/exaile/music.db .. this will erase your music db and you'll have to rescan.

Changed in exaile:
status: New → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.