Public bug reported:
Binary package hint: nagios3-common
Description:Ubuntu 9.04
Release:9.04
nagios3-common:
Installed: 3.0.6-2ubuntu1.1
Candidate: 3.0.6-2ubuntu1.1
Version table:
*** 3.0.6-2ubuntu1.1 0
500 http://ubuntu.inode.at jaunty-updates/main Packages
5
James is right.
If the mysql dependency is removed, the mediatomb package would need a
rebuild to be used with mysql.
The only option to get rid of the mysql library as hard dependency would
be to change the upstream mediatomb code to use dlopen(3).
greets
--
installation of mediatomb installs
This problem has been fixed in version 0.11.0.
see also bug #198302
Can the original poster confirm this and close this bug?
--
mediatomb crashed with SIGSEGV
https://bugs.launchpad.net/bugs/196120
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
The NO_START="yes" default dates back to the times where there was only
one MediaTomb package. Now with the three packages it makes probably
more sense to automatically start MediaTomb when the daemon package is
installed.
@Stefan: Yes, please change the default.
@Andres: Could you change that de
@Stefan: Yes, you can alternatively run MediaTomb as a regular user from
the command line. (simply type "mediatomb")
A solution could be to add two menu icons - one for opening the browser
to point to the UI of the daemon, and another one to probably start
MediaTomb as a regular user and open the
This is no bug, this is a feature :)
/var/lib/mediatomb/mediatomb.html will only be created if MediaTomb is
run as a daemon. It's not supposed to be in the package! Please read
http://mediatomb.cc/pages/download#debian_ubuntu very carefully.
--
mediatomb is missing critical files in HARDY
https:
please note that release 0.11.0 fixes bug #204485
--
Please sync mediatomb 0.11.0-1 (universe) from Debian unstable (main)
https://bugs.launchpad.net/bugs/198302
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing lis
*** This bug is a duplicate of bug 196120 ***
https://bugs.launchpad.net/bugs/196120
Please note that this bug is fixed in MediaTomb release 0.11.0 (2008/03/01).
See also bug #198302
--
mediatomb crashed with SIGSEGV
https://bugs.launchpad.net/bugs/204485
You received this bug notification b
** Changed in: mediatomb (Ubuntu)
Status: Incomplete => Confirmed
--
Please sync mediatomb 0.11.0-1 (universe) from Debian unstable (main)
https://bugs.launchpad.net/bugs/198302
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
marking bug invalid, because it seems to work for the original author,
since he switched to Ethernet
** Changed in: mediatomb (Ubuntu)
Status: New => Invalid
--
[Hardy] Server can never be reached
https://bugs.launchpad.net/bugs/196308
You received this bug notification because you are a
attaching MediaTomb upgrade log (0.10.0.dfsg1-2 to 0.11.0-1)
** Attachment added: "mt-upgrade"
http://launchpadlibrarian.net/12669773/mt-upgrade
--
Please sync mediatomb 0.11.0-1 (universe) from Debian unstable (main)
https://bugs.launchpad.net/bugs/198302
You received this bug notification b
attaching MediaTomb log output
** Attachment added: "mt-start"
http://launchpadlibrarian.net/12669748/mt-start
--
Please sync mediatomb 0.11.0-1 (universe) from Debian unstable (main)
https://bugs.launchpad.net/bugs/198302
You received this bug notification because you are a member of Ubuntu
attaching installlog on hardy
tested MediaTomb - starts up, UI accessible and working, media playable
over UPnP, no crashes
** Attachment added: "mt-install"
http://launchpadlibrarian.net/12669705/mt-install
--
Please sync mediatomb 0.11.0-1 (universe) from Debian unstable (main)
https://bug
attaching buildlog on hardy
** Attachment added: "mediatomb_0.11.0-1_i386.build"
http://launchpadlibrarian.net/12669690/mediatomb_0.11.0-1_i386.build
--
Please sync mediatomb 0.11.0-1 (universe) from Debian unstable (main)
https://bugs.launchpad.net/bugs/198302
You received this bug notificat
Please grant a FFe, because this release fixes critical bugs:
* The scripting feature is not usable with 0.10.0 in hardy because of a
serious js related bug. This bug causes MediaTomb to often crash with a
coredump.
* Some serious bugs on 64bit systems have been fixed. These bugs
prevented some U
attaching diffstat
** Attachment added: "mt-diffstat.txt"
http://launchpadlibrarian.net/12666539/mt-diffstat.txt
--
Please sync mediatomb 0.11.0-1 (universe) from Debian unstable (main)
https://bugs.launchpad.net/bugs/198302
You received this bug notification because you are a member of Ubunt
attaching ChangeLog
** Attachment added: "changelog.txt"
http://launchpadlibrarian.net/12666534/changelog.txt
--
Please sync mediatomb 0.11.0-1 (universe) from Debian unstable (main)
https://bugs.launchpad.net/bugs/198302
You received this bug notification because you are a member of Ubuntu
B
IMHO this bug should be marked 'invalid'
--
[Hardy] Server can never be reached
https://bugs.launchpad.net/bugs/196308
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://list
Ok, so it seems to be a bug in the Web UI. However, this bug is present
in the upstream source and should be reported using the MediaTomb
bugtracker on the sourceforge website:
http://sourceforge.net/projects/mediatomb
--
[Hardy] Server can never be reached
https://bugs.launchpad.net/bugs/196308
Which browser did you use? There is a known problem with Firefox 3.0..
Could you try a different browser?
--
[Hardy] Server can never be reached
https://bugs.launchpad.net/bugs/196308
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
u
20 matches
Mail list logo
