** Changed in: mediatomb (Debian)
Status: Fix Released => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/212441
Title:
Mediatomb Init Script not working : upnp error -117
To manage notifi
** Changed in: mediatomb (Debian)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/212441
Title:
Mediatomb Init Script not working : upnp error -117
To manage notifi
** Branch linked: lp:ubuntu/mediatomb
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/212441
Title:
Mediatomb Init Script not working : upnp error -117
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.
This bug was fixed in the package mediatomb - 0.12.1-0ubuntu2
---
mediatomb (0.12.1-0ubuntu2) oneiric; urgency=low
* Introduce Upstart support to fix start-on-boot failure (LP: #212441)
* Fix build gcc-4.6 build failure (missing correct header) (LP: #770964)
* Added libav 0.7 su
** Changed in: mediatomb (Ubuntu)
Status: Confirmed => In Progress
** Changed in: mediatomb (Ubuntu)
Assignee: (unassigned) => Daniel van Vugt (vanvugt)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpa
** Branch unlinked: lp:ubuntu/natty/mediatomb
** Branch unlinked: lp:ubuntu/mediatomb
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/212441
Title:
Mediatomb Init Script not working : upnp error -117
** Branch linked: lp:~vanvugt/ubuntu/oneiric/mediatomb/fix-212441
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/212441
Title:
Mediatomb Init Script not working : upnp error -117
--
ubuntu-bugs mai
** Tags added: patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/212441
Title:
Mediatomb Init Script not working : upnp error -117
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https:
** Branch linked: lp:ubuntu/mediatomb
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/212441
Title:
Mediatomb Init Script not working : upnp error -117
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.
Fix now available for maverck and natty in my PPA:
https://launchpad.net/~vanvugt/+archive/mediatomb
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/212441
Title:
Mediatomb Init Script not working : u
** Changed in: mediatomb (Debian)
Status: Unknown => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/212441
Title:
Mediatomb Init Script not working : upnp error -117
--
ubuntu-bugs maili
Here's a smaller nicer patch to solve the problem. This one should be
compatible with upstream Debian. By compatible I mean "won't break"
upstream Debian, but the patch still only fixes the bug for upstart-
based distros like Ubuntu.
** Bug watch added: Debian Bug tracker #534504
http://bugs.de
As I have now posted a fix for this bug and it has nothing to do
network-manager, I don't think this bug should "affect" network-manager
at all.
** Changed in: network-manager (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bu
** Branch linked: lp:ubuntu/mediatomb
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/212441
Title:
Mediatomb Init Script not working : upnp error -117
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.
FIX: Attached a patch for mediatomb source 0.12.1-0ubuntu1. This
replaces /etc/init.d/mediatomb with a more modern Upstart script
/etc/init/mediatomb.conf and fixes LP: #212441.
The patch contains deb packaging/script changes only. No code changes.
** Patch added: "A fix, to patch against mediato
Here is a more elegant solution using Upstart...
/etc/init.d/mediatomb stop
mv mediatomb.conf /etc/init/ # mediatomb.conf is attached
mv /etc/init.d/mediatomb /etc/init.d/mediatomb.old
rm -f /etc/rc?.d/[SK]??mediatomb
start mediatomb
** Attachment added: "mediatomb.conf"
https://bugs.launch
Since none of the fixes seem to be doing anything. I put a little 'sleep
10' in the start function in /etc/init.d/mediatomb. et voila this works
for me and gives you guys time to fix it :-))
--
Mediatomb Init Script not working : upnp error -117
https://bugs.launchpad.net/bugs/212441
You rece
the same problems still exists in 10.10 server edition. autostart
doesn't work. error 117
--
Mediatomb Init Script not working : upnp error -117
https://bugs.launchpad.net/bugs/212441
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
u
I am re-opening this bug because it still persists on a fresh
installation of Ubuntu 9.04 Server Edition.
The suggestion in comment #4 does not fix it, and is also the default
for the server install anyhow.
The solution provided in comment #8 is merely a workaround and if this
is considered "a FI
** Changed in: network-manager (Ubuntu)
Status: Invalid => Confirmed
--
Mediatomb Init Script not working : upnp error -117
https://bugs.launchpad.net/bugs/212441
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mai
I was facing a similar issue, but mine was not related with network. I'm
using static IP.
My problem was that the filesystem charset was not loaded correctly. I
have UTF-8 on my config.xml.
However after boot the loaded charset was the "ANSI_X3.4-1968". If I
restarted the mediatomb (/etc/init.d/me
This fix really helped!
One remark - the restart option does not contain the command to set up a
route for broadcasting the availability of the mediatomb server. To
solve the problem (which could be considered a fault in the mediatomb
startup script) I've copied this part of the script from the st
This fix worked for me as well, however, I share a folder with Samba
from the MediaTomb server to a Windows XP machine. Even though MediaTomb
now starts up every time at boot, the share disappears on the Windows
machine!
Brian
--
Mediatomb Init Script not working : upnp error -117
https://bugs.l
I had the same problem until I tried Richards solution. Now it seems to
be working fine. I do however, guard against lo events and mediatomb
removal.
Thanks Richard.
--
Mediatomb Init Script not working : upnp error -117
https://bugs.launchpad.net/bugs/212441
You received this bug notification b
Unfortunately the workaround proposed in the mediatomb faq no longer
works on Jaunty as detailed by comment #4.
I also tried setting eth0 in the interface file and tried removing network
manager and tried moving mediatomb to start after NetworkManager in rc2 (the
apparent default runlevel) but n
The mediatomb faq suggest another solution that can be used for head-
less machines (no need to log in) which is a bit more complex, I haven't
tried it
For a “headless” server where you can't log in, try this workaround: edit file
/etc/network/interfaces adding these 2 lines:
auto eth0
iface et
I had this same problem with 8.10 until I removed network manager and assigned
my ip manually (because network manager had some issues with static ip's at the
time).
So now I have 9.04 and it seems to manage static ip's just fine but this
problems persists.
Adding mediatomb to my session isn't
The Mediatomb FAQ page http://mediatomb.cc/dokuwiki/faq:faq contains the
following suggestion for Ubuntu :
- Launch the Sessions Preferences program ( System→Preferences→Sessions or
Startup Applications)
- Click “Add”
- Name: Mediatomb , Command: mediatomb -d
- Click “Add”
config used will n
** Summary changed:
- Init Script on Hardy not working
+ Mediatomb Init Script not working : upnp error -117
--
Mediatomb Init Script not working : upnp error -117
https://bugs.launchpad.net/bugs/212441
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscrib
29 matches
Mail list logo
