Bug 17659 - mga6: powerdevil.backlighthelper[4586]: QDBusArgument: read from a write-only object
Summary: mga6: powerdevil.backlighthelper[4586]: QDBusArgument: read from a write-only...
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: Nicolas Lécureuil
QA Contact:
URL:
Whiteboard:
Keywords: UPSTREAM
Depends on:
Blocks: 17523
  Show dependency treegraph
 
Reported: 2016-02-01 04:24 CET by Bit Twister
Modified: 2016-07-17 03:11 CEST (History)
0 users

See Also:
Source RPM: powerdevil-5.5.4-1.mga6.src.rpm
CVE:
Status comment:


Attachments

Description Bit Twister 2016-02-01 04:24:53 CET
Description of problem:

org.kde.powerdevil.backlighthelper[4586]: QDBusArgument: read from a write-only object

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


How reproducible:


Steps to Reproduce:
1. journalctl | grep powerdevil


Reproducible: 

Steps to Reproduce:
Comment 1 Samuel Verschelde 2016-02-02 14:16:48 CET
Can you give information about when it occurs, is it at session start, is it when you do something in particular?

Keywords: (none) => NEEDINFO
Assignee: bugsquad => mageia

Samuel Verschelde 2016-02-02 14:17:29 CET

Blocks: (none) => 17523

Comment 2 Bit Twister 2016-02-02 15:31:32 CET
(In reply to Samuel VERSCHELDE from comment #1)
> Can you give information about when it occurs, 

Sure.

> is it at session start, 

Yes.

> is it when you do something in particular?

Just guessing it might show up because I have set Dim Screen and Screen Energy Savings to 360 minutes in Power Management in systemsettings.

Keywords: NEEDINFO => (none)

Comment 3 Nicolas Lécureuil 2016-05-05 11:21:50 CEST
Please report this bug upstream

Keywords: (none) => UPSTREAM

Comment 4 Nicolas Lécureuil 2016-07-17 00:37:51 CEST
is this bug still valid under Plasma 5.7.1 ?
Comment 5 Bit Twister 2016-07-17 03:11:56 CEST
(In reply to Nicolas Lécureuil from comment #4)
> is this bug still valid under Plasma 5.7.1 ?

Unable to recreate the problem.

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


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