Bug 20227

Summary:	Configuration file /usr/lib/systemd/system/mythbackend.service is marked executable.
Product:	Mageia	Reporter:	Bit Twister <bittwister2>
Component:	RPM Packages	Assignee:	Colin Guthrie <mageia>
Status:	RESOLVED FIXED	QA Contact:
Severity:	normal
Priority:	Normal	CC:	cjw, eatdirt, geiger.david68210, guillomovitch, marja11, pkg-bugs
Version:	Cauldron	Keywords:	6sta2
Target Milestone:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Source RPM:	mythtv-0.27.4-20141022.11.mga6.tainted.src.rpm	CVE:
Status comment:

Description Bit Twister 2017-02-01 04:31:09 CET

Description of problem:

Configuration file /usr/lib/systemd/system/mythbackend.service is marked executable. Please remove executable permission bits. Proceeding anyway.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1. urpmi mythtv-backend
2. journalctl | grep permission


Workaround:
chmod -x /usr/lib/systemd/system/mythbackend.service

Bit Twister 2017-02-01 04:31:46 CET

Keywords: (none) => 6sta2

Marja Van Waes 2017-02-01 15:25:53 CET

CC: (none) => marja11, pkg-bugs
Assignee: bugsquad => mageia

Comment 1 Bit Twister 2017-02-02 10:53:54 CET

I will recommend updating to 0.28.1 sight unseen
https://www.mythtv.org/wiki/Release_Notes_-_0.28.1

Just finished importing my mga5 mythtv dump. Lots of mysql duplicate key errors. Errors about some unknown user which research indicates something to do with mysql and not mythtv.

After import, no way to unscramble mysql database. Deletion of myth database and whatnot did not clear up mysql database problems.

Forced to do a clean install/update to get back to mythtv testing.

Discontinuing mythtv testing until 0.28.1 is available in Mageia Cauldron.

FYI: bug 19127 is going to bit mythtv users.

Comment 2 Bit Twister 2017-02-02 10:57:37 CET

(In reply to Bit Twister from comment #1)  Sorry, about misspell.

 FYI: bug 19127 is going to bite mythtv users.

Comment 3 Bit Twister 2017-02-03 02:04:19 CET

(In reply to Bit Twister from comment #1)

> Just finished importing my mga5 mythtv dump. Lots of mysql duplicate key
> errors. Errors about some unknown user which research indicates something to
> do with mysql and not mythtv.

My mistake. The dump contained the mysql schema which caused all the mysql errors.
Re-did the mythtv dump and mga6 install/import  without mysql schema and a very basic go/no go test says mythbackend/frontend is ok.

Comment 4 Marja Van Waes 2018-09-04 11:39:18 CEST

CC'ing some committers, because the registered maintainer is unavailable.

CC: (none) => cjw, eatdirt, geiger.david68210, guillomovitch

Comment 5 Bit Twister 2021-02-03 17:15:43 CET

Permission was changed in version 31

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