Bug 11011 - 4_a1: invalid rtkit-daemon ControlGroup messages in the journal
Summary: 4_a1: invalid rtkit-daemon ControlGroup messages in the journal
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: x86_64 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-08-15 17:49 CEST by Bit Twister
Modified: 2015-04-28 02:44 CEST (History)
2 users (show)

See Also:
Source RPM: rtkit
CVE:
Status comment:


Attachments

Description Bit Twister 2013-08-15 17:49:17 CEST
Description of problem:

rtkit-daemon.service:32] Unknown lvalue 'ControlGroup' in section 'Service

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


How reproducible: Always


Steps to Reproduce:
Clean install of Mageia-4-alpha1-LiveDVD-KDE4-x86_64-DVD.iso

1. journalctl | grep ControlGroup


Reproducible: 

Steps to Reproduce:
Comment 1 Manuel Hiebel 2013-08-17 16:56:40 CEST
two same bugs

*** This bug has been marked as a duplicate of bug 10012 ***

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

Comment 2 Manuel Hiebel 2013-08-17 17:00:10 CEST
sorry

*** This bug has been marked as a duplicate of bug 11012 ***
Comment 3 Bit Twister 2013-08-17 19:21:19 CEST
(In reply to Manuel Hiebel from comment #2)
> sorry
> 
> *** This bug has been marked as a duplicate of bug 11012 ***

Why is it marked as duplicate?

It appears to be a common problem, but it is in two different rpms.
I am afraid ntp-daemon (11012) will be fixed but not rtkit-daemon (11011)
Comment 4 Manuel Hiebel 2013-08-18 01:06:09 CEST
oups

Status: RESOLVED => REOPENED
CC: (none) => mageia
Resolution: DUPLICATE => (none)
Source RPM: ntp-4.2.6p5-12.mga3.src.rpm => rtkit

Bit Twister 2014-01-18 16:33:25 CET

CC: (none) => junknospam

Comment 5 Bit Twister 2015-04-28 02:44:18 CEST
not seeing the error on 5 RC.

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


Note You need to log in before you can comment on or make changes to this bug.