Xiph.Org issueshttps://gitlab.xiph.org/groups/xiph/-/issues2017-08-03T06:41:38Zhttps://gitlab.xiph.org/xiph/positron/-/issues/636positron 1.1 does not recognise Neuros on Ubuntu (case problem?)2017-08-03T06:41:38Ztoojayspositron 1.1 does not recognise Neuros on Ubuntu (case problem?)When running "positron configure", I get the warning: "Warning: A Neuros does not appear to be mounted at /media/usbdisk/." I proceed with the configuration, because I know there is a Neuros there. But when I try "positron rebuild", I ge...When running "positron configure", I get the warning: "Warning: A Neuros does not appear to be mounted at /media/usbdisk/." I proceed with the configuration, because I know there is a Neuros there. But when I try "positron rebuild", I get:
```
toojays@fuzz:~$ positron rebuild
Traceback (most recent call last):
File "/usr/bin/positron", line 205, in ?
main(sys.argv)
File "/usr/bin/positron", line 166, in main
os.mkdir(dbdir)
OSError: [Errno 17] File exists: '/media/usbdisk/WOID_DB'
```
I figure this is maybe something to do with Ubuntu mounting the drive in some way where the case is different, because I have woid_db, not WOID_DB:
```
toojays@fuzz:/tmp/positron-1.1$ ls -l /media/usbdisk/
total 224
drwx------ 2 toojays toojays 16384 2004-10-22 09:08 151 - Poisoning the System
drwx------ 7 toojays toojays 16384 2004-09-21 14:33 bak_db
drwx------ 2 toojays toojays 16384 2005-03-22 06:28 erin_smith_band - downtownsmogcrown
drwx------ 2 toojays toojays 16384 2004-09-21 14:33 firmware
drwx------ 2 toojays toojays 16384 2004-10-22 09:01 francesca gregorini - sequel
drwx------ 2 toojays toojays 16384 2004-10-22 09:07 Machine Gun Fellatio - On Ice
-rwx------ 1 toojays toojays 18 2004-06-21 02:08 neuros.m3u
drwx------ 2 toojays toojays 16384 2004-10-22 09:05 phontaine - phontaine
-rwx------ 1 toojays toojays 14 2004-04-18 21:17 sn.txt
-rwx------ 1 toojays toojays 6 2004-04-18 21:17 version.txt
drwx------ 7 toojays toojays 16384 2004-10-22 15:49 woid_db
drwx------ 2 toojays toojays 16384 2004-09-21 14:34 WOID_HISI
drwx------ 2 toojays toojays 16384 2004-09-30 16:23 WOID_RECORD
drwx------ 2 toojays toojays 16384 2004-09-21 14:34 WOID_SYNC
```
Ubuntu has mounted the drive like so:
```
toojays@fuzz:/tmp/positron-1.1$ cat /etc/mtab | grep usbdisk
/dev/sda1 /media/usbdisk vfat rw,nosuid,nodev,sync,noatime,quiet,uid=1000,gid=1000,umask=077,iocharset=utf8 0 0
```
Stan SeibertStan Seiberthttps://gitlab.xiph.org/xiph/positron/-/issues/563Problem running positron 1.1.12017-08-03T06:41:38ZGitlab BotProblem running positron 1.1.1```
root@hyla unpak]# rpm -Uvh positron-1.1-1.noarch.rpm
Preparing... ########################################### [100%]
1:positron ########################################### [100%]
[root@hyla neuros]# p...```
root@hyla unpak]# rpm -Uvh positron-1.1-1.noarch.rpm
Preparing... ########################################### [100%]
1:positron ########################################### [100%]
[root@hyla neuros]# positron
Traceback (most recent call last):
File "/usr/bin/positron", line 23, in ?
from positron.config import Config
ImportError: No module named positron.config
```Stan SeibertStan Seiberthttps://gitlab.xiph.org/xiph/positron/-/issues/558[PATCH] positron 1.1 is distributing an old mp3info.py.2017-08-03T06:41:38ZThomas Rowe[PATCH] positron 1.1 is distributing an old mp3info.py.```
The current MP3Info.py module available at
http://shell.lab49.com/~vivake/python/MP3Info.py
fixes a few crash causing bugs.
``````
The current MP3Info.py module available at
http://shell.lab49.com/~vivake/python/MP3Info.py
fixes a few crash causing bugs.
```Stan SeibertStan Seiberthttps://gitlab.xiph.org/xiph/positron/-/issues/547OGG indexing "hang"2017-08-03T06:41:38ZpgunnOGG indexing "hang"```
Hello,
When ogg support is enabled in positron, adding ogg files or rebuilding the
database when they are present does not ever seem to complete. Strace indicates
that after closing the first file (for the second time?), it doesn't m...```
Hello,
When ogg support is enabled in positron, adding ogg files or rebuilding the
database when they are present does not ever seem to complete. Strace indicates
that after closing the first file (for the second time?), it doesn't make any
further system calls, and top indicates that it's using 99% of the CPU.
I have provided a link to the neuros discussion board where they suggest
downgrading to libvorbis 1.0.0, but I am using Fedora2, which comes with 1.0.1,
so such a downgrade is not practical. I am using positron 1.1. If I remove the
python modules relating to ogg, I can sync ok using just my mp3s.
```Stan SeibertStan Seiberthttps://gitlab.xiph.org/xiph/positron/-/issues/521[PATCH] ID3v2.4 allows encoded frame values, positron deals with the poorly2017-08-03T06:41:38Zapm13[PATCH] ID3v2.4 allows encoded frame values, positron deals with the poorly```
The latest version of Juk (my favorite music player/tagger) by default writes
ID3v2.4 with all tags encoded UTF-8 (actually it's taglib's fault, but there's
nothing incorrect about it). Unfortunately, there is practically no progr...```
The latest version of Juk (my favorite music player/tagger) by default writes
ID3v2.4 with all tags encoded UTF-8 (actually it's taglib's fault, but there's
nothing incorrect about it). Unfortunately, there is practically no program on
linux that appears to deal with these well (EasyTag, and Juk itself are the
only exceptions). Positron is actually closer than most to supporting these
properly which just skip the v2 tag, positron reads it in literally and
includes the encoding byte. All my MP3s as a result end up with titles like
'\x03Title', ugly! I've attached a patch which handles this appropriately, and
also fixes a minor inconsistency with the ID3 spec (frame names can have
numbers in them, even at the beginning), which probably isn't worth fixing, as
positron only cares about a very limited set of ID3 frames anyway.
```Stan SeibertStan Seiberthttps://gitlab.xiph.org/xiph/positron/-/issues/519Case issues in a few source files2017-08-03T06:41:38Zapm13Case issues in a few source files```
There are a few instances where false and true are used instead of False and
True in source files. Though I have never seen it, this will result in
uncaught NameErrors as these are not valid values in python. The problems
occur ...```
There are a few instances where false and true are used instead of False and
True in source files. Though I have never seen it, this will result in
uncaught NameErrors as these are not valid values in python. The problems
occur in:
db/MDB.py:151: escape_mode = false
db/MDB.py:157: escape_mode = false
db/MDB.py:160: escape_mode = true
progress.py:23: return true
```Stan SeibertStan Seiberthttps://gitlab.xiph.org/xiph/positron/-/issues/518[PATCH] Positron chokes on NSM and NDBM written DBs2017-08-03T06:41:38Zapm13[PATCH] Positron chokes on NSM and NDBM written DBs```
The problem is that positron is not capable of dealing with multivalued
access_keys (i.e. playlist), which both NDBM and NSM write. This is further
complicated by the fact that neither of those programs uses the 'Bag Delimiter'
t...```
The problem is that positron is not capable of dealing with multivalued
access_keys (i.e. playlist), which both NDBM and NSM write. This is further
complicated by the fact that neither of those programs uses the 'Bag Delimiter'
to separate the values in a multivalued key. The attached patch, allows
positron to read multivalued access_key fields with or without Bag Delimiters.
```Stan SeibertStan Seiberthttps://gitlab.xiph.org/xiph/positron/-/issues/513"positron sync" command crashes2017-08-03T06:41:38Zcconvey"positron sync" command crashes```
I'm using Fedora Core 1. I just installed positron for the first time, and I'm a
new user. Here's what I experienced (after successfully running 'positron config'):
[cjc@calvin mnt]$ positron sync
Traceback (most recent call last):...```
I'm using Fedora Core 1. I just installed positron for the first time, and I'm a
new user. Here's what I experienced (after successfully running 'positron config'):
[cjc@calvin mnt]$ positron sync
Traceback (most recent call last):
File "/usr/bin/positron", line 175, in ?
main(sys.argv)
File "/usr/bin/positron", line 157, in main
cmd.run(config, myNeuros, remaining[1:])
File "/usr/lib/python2.2/site-packages/positron/cmd_sync.py", line 47, in run
audio_db = neuros.open_db("audio")
File "/usr/lib/python2.2/site-packages/positron/neuros.py", line 160, in open_db
self.db_formats[name]["no_flatten"])
File "/usr/lib/python2.2/site-packages/positron/db/WOID.py", line 74, in open
mdb.set_extra_format(extra_format)
File "/usr/lib/python2.2/site-packages/positron/db/MDB.py", line 134, in
set_extra_format
raise Error("Number of format strings does not equal number of extra info
fields.")
positron.db.util.Error: Number of format strings does not equal number of extra
info fields.
[cjc@calvin mnt]$ positron --version
positron version 1.0
```Stan SeibertStan Seiberthttps://gitlab.xiph.org/xiph/positron/-/issues/506positron fails to sync from partition mounted under vfat2017-08-03T06:41:38Zcooper.betheapositron fails to sync from partition mounted under vfat```
i have a directory /mnt/dos/music mounted with vfat that i wish to sync with my
neuros.
python apparently throws an uncaught IOError that causes the application to
crash; my guess is that this is based on trying to apply a mode setti...```
i have a directory /mnt/dos/music mounted with vfat that i wish to sync with my
neuros.
python apparently throws an uncaught IOError that causes the application to
crash; my guess is that this is based on trying to apply a mode setting that is
unavailable to this filesystem?
at any rate, here's the backtrace:
[cooper@foofoo cooper]$ positron sync
Synchronizing Neuros music database.
Checking for new music... Copying 233 new tracks.
1. ...
Traceback (most recent call last):
File "/usr/bin/positron", line 175, in ?
main(sys.argv)
File "/usr/bin/positron", line 157, in main
cmd.run(config, myNeuros, remaining[1:])
File "/usr/lib/python2.2/site-packages/positron/cmd_sync.py", line 131, in run
add_track(neuros, sourcename, targetname, metadata)
File "/usr/lib/python2.2/site-packages/positron/add_file.py", line 70, in
add_track
util.copy_file(sourcename, targetname)
File "/usr/lib/python2.2/site-packages/positron/util.py", line 41, in copy_file
dest = file(dest_filename, "wb")
IOError: invalid mode: wb
```Stan SeibertStan Seiberthttps://gitlab.xiph.org/xiph/positron/-/issues/494Key out of bounds error while trying to delete entire /neuros/music directory2017-08-03T06:41:39ZmpmKey out of bounds error while trying to delete entire /neuros/music directory```
I need to delete about 1.7GB from the neuros (the entire database and all
music). To do this, I did:
positron del /neuros/music
After processing about 35 files, positron quits with an "out of bounds" error.
The file it quits on is...```
I need to delete about 1.7GB from the neuros (the entire database and all
music). To do this, I did:
positron del /neuros/music
After processing about 35 files, positron quits with an "out of bounds" error.
The file it quits on is not the same (I rerun the command and it quits again on
a different file--as though it had already deleted the previous 35 or so files).
There isn't anything really unique about my music or the last file positron
processes. If there is anything else that is needed I can provide it.
The error is:
Traceback (most recent call last):
File "/usr/bin/positron", line 175, in ?
main(sys.argv)
File "/usr/bin/positron", line 157, in main
cmd.run(config, myNeuros, remaining[1:])
File "/usr/lib/python2.2/site-packages/positron/cmd_del.py", line 116, in run
del_track(config, neuros, sourcename, sai_index)
File "/usr/lib/python2.2/site-packages/positron/cmd_del.py", line 77, in del_track
neuros_path = neuros.db["audio"].get_record(sai_index)[8].lower()
File "/usr/lib/python2.2/site-packages/positron/db/WOID.py", line 146, in
get_record
(pointer, pai_pointer) = self.sai[index]
File "/usr/lib/python2.2/site-packages/positron/db/SAI.py", line 79, in
__getitem__
raise IndexError("Key out of bounds")
IndexError: Key out of bounds
```Stan SeibertStan Seiberthttps://gitlab.xiph.org/xiph/positron/-/issues/481positron barfs on some MP3s --- 1.0 worked on them.2017-08-03T06:41:39ZGitlab Botpositron barfs on some MP3s --- 1.0 worked on them.```
anthony@bohr:anthony$ positron sync
Synchronizing Neuros music database.
Checking for new music... assical/Beethoven/Beethoven - Vio...
Traceback (most recent call last):
File "/usr/bin/positron", line 174, in ?
main(s...```
anthony@bohr:anthony$ positron sync
Synchronizing Neuros music database.
Checking for new music... assical/Beethoven/Beethoven - Vio...
Traceback (most recent call last):
File "/usr/bin/positron", line 174, in ?
main(sys.argv)
File "/usr/bin/positron", line 156, in main
cmd.run(config, myNeuros, remaining[1:])
File "/usr/lib/python2.3/site-packages/positron/cmd_sync.py", line 93, in run
silent=True))
File "/usr/lib/python2.3/site-packages/positron/add_file.py", line 69, in
gen_filelist
allowed_types, silent))
File "/usr/lib/python2.3/site-packages/positron/add_file.py", line 69, in
gen_filelist
allowed_types, silent))
File "/usr/lib/python2.3/site-packages/positron/add_file.py", line 42, in
gen_filelist
metadata = audiofile.detect(fullname)
File "/usr/lib/python2.3/site-packages/positron/audiofile.py", line 28, in detect
metadata = detect_func(filename)
File "/usr/lib/python2.3/site-packages/positron/audiofile.py", line 44, in
detect_mp3
mp3info = MP3Info.MP3Info(f)
File "/usr/lib/python2.3/site-packages/positron/MP3Info.py", line 534, in __init__
id3v2 = ID3v2(file)
File "/usr/lib/python2.3/site-packages/positron/MP3Info.py", line 239, in __init__
frame = ID3v2Frame(file, self.major_version)
File "/usr/lib/python2.3/site-packages/positron/MP3Info.py", line 128, in __init__
self.data = _strip_zero(file.read(self.size))
MemoryError
```Stan SeibertStan Seiberthttps://gitlab.xiph.org/xiph/positron/-/issues/465tracknum isn't lower cased2017-08-03T06:41:39ZGitlab Bottracknum isn't lower cased```
The code in add_file.py says tracknum.lower(), but I think it means tracknum =
tracknum.lower()
Just incase the track has letters in it.
Line 94 of add_file.
Ciao!
``````
The code in add_file.py says tracknum.lower(), but I think it means tracknum =
tracknum.lower()
Just incase the track has letters in it.
Line 94 of add_file.
Ciao!
```Stan SeibertStan Seiberthttps://gitlab.xiph.org/xiph/positron/-/issues/452utf-8 error on sync2017-08-03T06:41:39Znandwalsutf-8 error on sync```
when running positron sync, i occasionally (but always on the same files) get
this:
~> positron sync
Synchronizing Neuros music database.
Checking for new music...
Traceback (most recent call last):
File "/usr/bin/positron", l...```
when running positron sync, i occasionally (but always on the same files) get
this:
~> positron sync
Synchronizing Neuros music database.
Checking for new music...
Traceback (most recent call last):
File "/usr/bin/positron", line 175, in ?
main(sys.argv)
File "/usr/bin/positron", line 157, in main
cmd.run(config, myNeuros, remaining[1:])
File "/usr/lib/python2.2/site-packages/positron/cmd_sync.py", line 93, in run
silent=True))
File "/usr/lib/python2.2/site-packages/positron/add_file.py", line 40, in
gen_filelist
metadata = audiofile.detect(fullname)
File "/usr/lib/python2.2/site-packages/positron/audiofile.py", line 28, in
detect
metadata = detect_func(filename)
File "/usr/lib/python2.2/site-packages/positron/audiofile.py", line 86, in
detect_oggvorbis
actual_keys = map(string.lower, vc.keys())
UnicodeError: UTF-8 decoding error: unexpected code byte
~>
so, i'm guessing here that there's some unicode characters that poitron can't
recognize, or something, yes? is there a way to fix this? without at least it
returning the file that caused the error, i have to add files manually, which is
tedious.
thanks!
nandwals
```Stan SeibertStan Seiberthttps://gitlab.xiph.org/xiph/positron/-/issues/413[PATCH] Error: /neuros does not look like a Neuros mountpoint2017-08-03T06:41:39ZGitlab Bot[PATCH] Error: /neuros does not look like a Neuros mountpoint```
positron works as expected with the 128MB flash backpack.
however when i switch to the 20GB backpack i receive the following on any
positron command:
Error: /neuros does not look like a Neuros mountpoint
what can i do?
``````
positron works as expected with the 128MB flash backpack.
however when i switch to the 20GB backpack i receive the following on any
positron command:
Error: /neuros does not look like a Neuros mountpoint
what can i do?
```Stan SeibertStan Seiberthttps://gitlab.xiph.org/xiph/positron/-/issues/401positron crashes after sync, before rebuilding database2017-08-03T06:41:39ZMike Bursellpositron crashes after sync, before rebuilding database```
I guess this may be related to another bug, but the stack trace is quite
different. I'd just added some more files with a "positron sync", got to the
end and received this error.
A "positron --rebuild" worked fine, but as I've now ...```
I guess this may be related to another bug, but the stack trace is quite
different. I'd just added some more files with a "positron sync", got to the
end and received this error.
A "positron --rebuild" worked fine, but as I've now got 2856 tracks on my
Neuros, this was really too slow!
Checking for new recordings...
Traceback (most recent call last):
File "/usr/bin/positron", line 175, in ?
main(sys.argv)
File "/usr/bin/positron", line 157, in main
cmd.run(config, myNeuros, remaining[1:])
File
"/home/jack/src/positron/dist/positron-1.0/debian/positron/usr/lib/python2.2/site-packages/positron/cmd_sync.py",
line 139, in run
File
"/home/jack/src/positron/dist/positron-1.0/debian/positron/usr/lib/python2.2/site-packages/positron/db/WOID.py",
line 154, in get_records
File
"/home/jack/src/positron/dist/positron-1.0/debian/positron/usr/lib/python2.2/site-packages/positron/db/WOID.py",
line 111, in _get_record_at
File
"/home/jack/src/positron/dist/positron-1.0/debian/positron/usr/lib/python2.2/site-packages/positron/db/MDB.py",
line 213, in read_record_at
struct.error: unpack str size does not match format
```Stan SeibertStan Seiberthttps://gitlab.xiph.org/xiph/positron/-/issues/400First-time sync crashes if no data to sync.2017-08-03T06:41:39ZjvmFirst-time sync crashes if no data to sync.```
I ran positron config, configured a sync point, and a (place to download
recordings), then ran positron sync, just to see that it seemed to work, before
getting down to installing some music. Both configured directories were empty,
a...```
I ran positron config, configured a sync point, and a (place to download
recordings), then ran positron sync, just to see that it seemed to work, before
getting down to installing some music. Both configured directories were empty,
and the Neuros player was fresh out of the box.
The error message that printed out was:
boojum:~> positron sync
Synchronizing Neuros music database.
Checking for new music... None.
Checking for new recordings... None.
Traceback (most recent call last):
File "/usr/bin/positron", line 175, in ?
main(sys.argv)
File "/usr/bin/positron", line 157, in main
cmd.run(config, myNeuros, remaining[1:])
File
"/home/jack/src/positron/dist/positron-1.0/debian/positron/usr/lib/python2.2/site-packages/positron/cmd_sync.py",
line 165, in run
File
"/home/jack/src/positron/dist/positron-1.0/debian/positron/usr/lib/python2.2/site-packages/positron/db/WOID.py",
line 327, in count_deleted
File
"/home/jack/src/positron/dist/positron-1.0/debian/positron/usr/lib/python2.2/site-packages/positron/db/MDB.py",
line 294, in count_deleted
File
"/home/jack/src/positron/dist/positron-1.0/debian/positron/usr/lib/python2.2/site-packages/positron/db/MDB.py",
line 189, in read_record_at
File
"/home/jack/src/positron/dist/positron-1.0/debian/positron/usr/lib/python2.2/site-packages/positron/db/util.py",
line 74, in fread_wordstruct.error: unpack str size does not match format
The workaround was to add a single mp3 file to the configured sync directory and
sync again. After that, everything was ok, even after I deleted the mp3 and
re-ran sync. So, not a big deal, which is why I marked as minor, but not totally
trivial IMHO, because, well, crashes are bad. :^)
Sorry my Python skills aren't up to fixing this myself yet; hope this bug report
has enough info to reproduce and fix.
```Stan SeibertStan Seiberthttps://gitlab.xiph.org/xiph/positron/-/issues/395how to remove then reinstall files with sync?2017-08-03T06:41:39ZMike Bursellhow to remove then reinstall files with sync?```
Currently, if you remove files with "del", you can't put them back later on, as
far as I can see from the man pages. It would be good to be able to do this.
``````
Currently, if you remove files with "del", you can't put them back later on, as
far as I can see from the man pages. It would be good to be able to do this.
```Stan SeibertStan Seiberthttps://gitlab.xiph.org/xiph/positron/-/issues/394'sync' doesn't actually 'sync'2017-08-03T06:41:39Zdberger'sync' doesn't actually 'sync'```
I did some reorganization of my PC-side music archive and expected positron to
"figure it out" during a sync. It didn't - and it forced me to rebuild the
database (which in and of itself isn't bad, but takes a while).
Specifically,...```
I did some reorganization of my PC-side music archive and expected positron to
"figure it out" during a sync. It didn't - and it forced me to rebuild the
database (which in and of itself isn't bad, but takes a while).
Specifically, I had ripped two albums by the same artist which had different
attributions in the CDDB and therefor ended up in two different directories on
the PC:
tom petty/full moon fever
tom petty & the heartbreakers/greatest hits
Once I noticed this, I moved "full moon fever" to live under "tom petty & the
heartbreakers", updated the tags on the ogg files, and did a % positron sync
I ended up with the tracks duplicated on disk as well as in the database. I
tried doing a positron del of the ones I didn't want as: # positron del "tom
petty" and ran (again) into bug 385.
So it seems that sync should check for files that have been removed on the PC
side and remove them (and their database entries) from the neuros *before*
adding the database entries for newly copied files. Further, it makes sense to
remove such files before copying new files to increase the chances that there's
enough space on the device during copy.
```Stan SeibertStan Seiberthttps://gitlab.xiph.org/xiph/positron/-/issues/384Positron doesn't recognize Neuros mount2006-06-12T11:42:05ZGitlab BotPositron doesn't recognize Neuros mount```
I've mounted my Neuros at /mnt/neuros, immediatly after formatting the device
completely. Since I've not synced using any software yet, the
directory "WOID_DB" doesn't exist. If I create it, Positron attempts to access
WOID_DB/aud...```
I've mounted my Neuros at /mnt/neuros, immediatly after formatting the device
completely. Since I've not synced using any software yet, the
directory "WOID_DB" doesn't exist. If I create it, Positron attempts to access
WOID_DB/audio/audio.mdb and fails (since that doesn't exist yet). I've tried
postitron rebuild and it still fails.
I've looked through the manuals and read all the bugs that seemed to be
applicable, but I can't find a way to manually create DB files without using my
Windows machine.
```Stan SeibertStan Seiberthttps://gitlab.xiph.org/xiph/positron/-/issues/379Detecting changes to files for sync2006-06-12T11:31:35Zapm13Detecting changes to files for sync```
It would be very useful if positron could detect file changes. Often times I will edit ID3 tags
between syncs (change genre, etc.) and would like those changes to appear on the neuros. This
could be accomplished either by naively...```
It would be very useful if positron could detect file changes. Often times I will edit ID3 tags
between syncs (change genre, etc.) and would like those changes to appear on the neuros. This
could be accomplished either by naively comparing the mtimes of the files, or even better by
using an rsync type algorithm for the sync (perhaps using pysync
http://freshmeat.net/projects/pysync/?topic_id=251%2C71%2C42%2C912 ).
```Stan SeibertStan Seibert