Bug 16895

Summary:	Mediatomb does not start (workaround)
Product:	Mageia	Reporter:	Jean-Yves LE GOFF <jeanyves.le-goff>
Component:	RPM Packages	Assignee:	Olivier Blin <mageia>
Status:	RESOLVED OLD	QA Contact:
Severity:	normal
Priority:	Normal	CC:	cjw, marja11
Version:	5
Target Milestone:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Source RPM:		CVE:
Status comment:

Description Jean-Yves LE GOFF 2015-10-04 12:34:03 CEST

After installing the mediatomb package, the service can't start.

In the mediatomb log, I've found:

"2015-09-27 15:00:06   ERROR: Could not create directory /etc/mediatomb : Permission denied"

The workaround is to create the folder and assign it to the mediatomb user & group.

Comment 1 Samuel Verschelde 2015-10-12 10:17:20 CEST

Assigning to maintainer Olivier Blin and CCing Christiaan Welvaart.

CC: (none) => cjw
Assignee: bugsquad => mageia

Comment 2 Marja Van Waes 2018-04-14 23:49:51 CEST

Hi Jean-Yves,

Thank you for having taken the needed time to report this issue!

Did this bug get fixed? If so, please change its status to RESOLVED - FIXED

If it didn't, then we regret that we weren't able to fix it in Mageia 5. Mageia 5 has officially reached its End of Life on December 31st, 2017 https://blog.mageia.org/en/2017/11/07/mageia-5-eol-postponed/
It only continued to get important security updates since then, because we are waiting for a big Plasma5 update in Mageia 6, that'll fix many of the Mageia 5 => 6 upgrade issues.

If you haven't seen that this bug got fixed, then please check whether this bug still exists in Mageia 6. If it does, then please change the Version (near the top, at the left) to "6". If you know it exists in Cauldron, then change Version to Cauldron. If you see it in both Cauldron and Mageia 6, then please set version to Cauldron and add MGA6TOO on the Whiteboard.

Thanks,
Marja

CC: (none) => marja11

Comment 3 Marja Van Waes 2018-10-07 15:14:32 CEST

@ Jean-Yves:

No reply, so closing as OLD since Mageia 5 is no longer maintained.

==> If you didn't reset your password after February 2018, then you'll need to reset it here https://identity.mageia.org/forgot_password to be able to log in and comment in this report. <==

Resolution: (none) => OLD
Status: NEW => RESOLVED