As I stated above, this should be fixed in recent minidlna releases, so
I close this bug now. If this still happens on Ubuntu 14.04 (Trusty) or
newer releases, please reopen the bug report.
** Changed in: minidlna (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notific
A debian user confirmed this is fixed in 1.1.2. So this bug only affects
saucy and precise. :-)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1053173
Title:
minidlna crashes on boot when no active n
Thanks very much for detailed explanation.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1053173
Title:
minidlna crashes on boot when no active network connection
To manage notifications about thi
> - is this Bug not in minidlna itself ? Why requires minidlna IP
> address to be set (why do not allow to BIND to ANY address)?
I think this is because minidlna does not only listen on some interface
& port number, it also needs to send out SSDP packets (multicast) on
relevant network interfaces.
kapetr, the bug is posted on the minidlna package. maybe it's due to a
compile option, or an ubuntu patch, I don't know. etiquette is to post
the bug on the package and let the package maintainer either fix it or
post the bug upstream. though it seems that the maintainer may no
longer be active,
Hello, I had report this Bug too - 1236031 - (is seems to be the same
problem) - but maybe some questions are still open.
- is this Bug not in minidlna itself ? Why requires minidlna IP address to be
set (why do not allow to BIND to ANY address)?
- does the solution with upstart serve also down/u
PS: my pc has network configured with static dhcp (wired), if this ever
helps a dev.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1053173
Title:
minidlna crashes on boot when no active network conn
@ Ray DeCampo
I was driven to your workaround here
http://labnotes.decampo.org/2012/12/ubuntu-1210-minidlna-on-boot.html?m=1 by a
gentle guy in french ubuntu forum.
Thanks to you all, my minidlna now starts on boot (12.04)
--
You received this bug notification because you are a member of Ubunt
that certainly helps, but it's only partially a fix. local only
operation offline is not possible. yes, one could just directly connect
to the media files, but then you's have 2 databases to handle instead of
just one.
--
You received this bug notification because you are a member of Ubuntu
Bug
Attached the minidlna.conf upstart init file.
Here is how to use it:
First You need to copy it to /etc/init/
cp minidlna.conf /etc/init/
Then you need to remove minidlna from the old systemv init system by typing:
sudo update-rc.d -f minidlna remove
now you need to symlink the upstart script to
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: minidlna (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1053173
Title:
m
I can confirm this on 12.04. the problem is indeed related to the network. I
have a wifi connection and if I run it without a network connection, it fails
to start.Moving the init script to a higher id in the rc init process doesn't
seem to work either.
The solution I found is to move the init t
12 matches
Mail list logo
