Error: 500general:mp3_dir

[blamm]

Hi. Every time I change my Firefly config through the web interface the change appears to work but the interface reports an error.

e.g. if I set a new music folder I get the following:

Error: 500general:mp3_dir

I have tried creating a new one useing the example but still get errors.

Any suggestions?

[rpedde]

@blamm wrote:

Hi. Every time I change my Firefly config through the web interface the change appears to work but the interface reports an error.

e.g. if I set a new music folder I get the following:

Error: 500general:mp3_dir

I have tried creating a new one useing the example but still get errors.

Any suggestions?

That’s actually a long standing bug. I keep meaning to look at it because it ticks me off, but just haven’t done it yet. It’s definitely a “my fault” issue, though.

— Ron

[blamm]

Seems to be fixed in 1695. Ta

[rpedde]

@blamm wrote:

Seems to be fixed in 1695. Ta

ya huh. you shamed me into it. 🙂

— Ron

[jgoor]

Considering the fact that this buggy firefly is included into the most adopted Linux distro (Ubuntu Gutsy), I hope this will get your maximum attention.

At this moment eg. I csnnot use my Roku the way I wanted to, only because I did an upgrade to Gusty, being ‘state of the art’ technology.

I see there’s no .deb package yet. When do you expect one to be available?
Regards

[rpedde]

@jgoor wrote:

Considering the fact that this buggy firefly is included into the most adopted Linux distro (Ubuntu Gutsy), I hope this will get your maximum attention.

At this moment eg. I csnnot use my Roku the way I wanted to, only because I did an upgrade to Gusty, being ‘state of the art’ technology.

I see there’s no .deb package yet. When do you expect one to be available?
Regards

I’m not sure you understand the forces that drive open source software.

I’m also going to hope that the tone of your message was due to language translation issues, and answer civilly rather than with the terse reply I was tempted to.

This isn’t my job. I do this for personal enjoyment. I hope to have something for gutsy soon, but I’m not sure when.

In the meantime, perhaps now is a good time to learn about compiling your own software.

[jgoor]

I’m afraid the tone was right (I might regret it, but i’m not going t lie about it), but it was not my intention to offend you.
I assume the word ‘buggy’ did it, since after a re-read I cannot find anything wrong in the post.

I was just wandering why a distro that “just works” (Ubuntu) has something in it that does not work. I do not blame you, probably just no-one tested it when slamming it into Gutsy.

Don’t blame me for being a little bit disappointed when my favourite little piece of software does NOT work. (in fact, be proud. most software that do not appear to work, are replaed by some competitor and it doesn’t even bother me to not retry it lateron)

You reply suggests that you are the one and only developer. Is that correct?

In the mean time, I’ll be waiting patiently for a working .deb file. (I am a deliberate ‘noob’ and I tend to stay that way)

Keep up the good work!

[Anonymous]

What do you mean by “my favourite little piece of software does NOT work”?

I am also an absolute beginner with linux and I got it working with Ubuntu Gutsy Gibbon. As a matter of fact, it works better than my earlier version with Windoze and NAS devices.

[jgoor]

well,
* vanilla install Gutsy server edition
* apt-get install apache2
* apt-get install mt-daapd

http://serveraddress:3689
Every change in the config I make, I get ‘Error: 500general:mp3_dir’ as result.

My assumption is that it is due to firefly.
Especially since Ron confirmed it’s a known bug.

Weird that your firefly works fine.
We are talking exactly the same Gutsy here? Vanilla, not a beta release or upgrade? I installed it from scratch, with only apache2 and firefly…

[S80_UK]

@jgoor wrote:

Every change in the config I make, I get ‘Error: 500general:mp3_dir’ as result.

My assumption is that it is due to firefly.
Especially since Ron confirmed it’s a known bug.

You are right – this is a Firefly bug and it was around for quite a while. But it’s really only a minor inconvenience. If you make one change at a time to the config using the web interface the changes will be made and you can generally ignore this error. Of course, you can also edit the config file directly using your preferred editor.

I think you may have irritated a few folks here with your “buggy” comment – the reality is that Firefly is much less buggy than many such server applications, including commercial software. “Buggy” could be taken to imply much worse problems than that which you mentioned. The very latest nightly releases are always to be regarded as works in progress and may have minor or major bugs. But apart from the error that you mentioned, version 1586 is pretty stable with many of us using it long term (not sure what version you have though).

[rpedde]

@jgoor wrote:

I’m afraid the tone was right (I might regret it, but i’m not going t lie about it), but it was not my intention to offend you.
I assume the word ‘buggy’ did it, since after a re-read I cannot find anything wrong in the post.

It wasn’t the word buggy, as that’s an accurate description. It’s the sense of entitlement that irritated me. And again, I think that comes back to understanding how open source works. I write this for me. For my stuff to work. I make it available to other people to use, and make a best effort to try and make it work with their stuff too, but I expect that if it doesn’t, they dust off the old compiler and make it work themselves. And send those fixes back so everyone else with the same platform as they have can benefit. Or, failing that, if someone doesn’t have the code-fu to fix it themselves, I expect a honey approach, not a vinegar one.

I was just wandering why a distro that “just works” (Ubuntu) has something in it that does not work. I do not blame you, probably just no-one tested it when slamming it into Gutsy.

A few reasons, I’d guess:

1. It’s in universe. There’s no guarantee on stuff in universe, as universe is basically debian sid packages compiled for ubuntu libs. There’s a fair amount in universe that doesn’t work quite right on ubuntu.
2. It’s a snapshot of nightly developer-only builds. The debian maintainers are probably trying to sail a fine line between a stable release and new features. Mostly this is my fault, because I haven’t dropped a stable for a long time. But still, it’s fundamentally an unstable release.
3. This is linux, not windows. Some assembly is required.

Don’t blame me for being a little bit disappointed when my favourite little piece of software does NOT work. (in fact, be proud. most software that do not appear to work, are replaed by some competitor and it doesn’t even bother me to not retry it lateron)

Again, I’m shooting for a total world market of one user, and I don’t have any competitors. I’m not competing with anyone for anything.

You reply suggests that you are the one and only developer. Is that correct?

I get help from time to time. Sometimes someone will pass through with a desire to add some feature, and they’ll work on it with me for a while to get the feature they want, then they’ll disappear. Presumably to listen to music with the feature that they wanted.

I’ve gotten significant help on transcoding, the web config front end, the OSX preference pane, the windows tray icon, and query/browse support for daap.

But yeah, for the most part, it’s just me.

In the mean time, I’ll be waiting patiently for a working .deb file. (I am a deliberate ‘noob’ and I tend to stay that way)

Keep up the good work!

Ahh, see… with this tone, it wouldn’t have been an issue. In fact, I’d likely have paid special attention to getting a nightly for gutsy out.

I probably still will in the next couple days, as it’s not that difficult to add another debian-based nightly to my build environment, but again, the difference (to me) between demanding my free time and asking of my free time is significant.

Not really germane to anything, but interesting:

SLOC    Directory       SLOC-by-Language (Sorted)

50026   mt-daapd        ansic=42302,objc=3522,cpp=2592,perl=943,sh=470,php=101,

python=96

0       src             (none)





Totals grouped by language (dominant language first):

ansic:        42302 (84.56%)

objc:          3522 (7.04%)

cpp:           2592 (5.18%)

perl:           943 (1.89%)

sh:             470 (0.94%)

php:            101 (0.20%)

python:          96 (0.19%)









Total Physical Source Lines of Code (SLOC)                = 50,026

Development Effort Estimate, Person-Years (Person-Months) = 12.17 (146.00)

(Basic COCOMO model, Person-Months = 2.4 * (KSLOC**1.05))

Schedule Estimate, Years (Months)                         = 1.38 (16.61)

(Basic COCOMO model, Months = 2.5 * (person-months**0.38))

Total Estimated Cost to Develop                           = $ 1,643,604

(average salary = $56,286/year, overhead = 2.40).

SLOCCount, Copyright (C) 2001-2004 David A. Wheeler

SLOCCount is Open Source Software/Free Software, licensed under the GNU GPL.

SLOCCount comes with ABSOLUTELY NO WARRANTY, and you are welcome to

redistribute it under certain conditions as specified by the GNU GPL license;

see the documentation for details.

Please credit this data as "generated using David A. Wheeler's 'SLOCCount'."

Clearly the person-years estimate is off a bit. 🙂

[Author]

Posts