Bug 19101 - First Plasma login results in Compositor system settings module being launched
Summary: First Plasma login results in Compositor system settings module being launched
Status: RESOLVED OLD
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: KDE maintainers
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 17523
  Show dependency treegraph
 
Reported: 2016-07-29 18:04 CEST by David Walser
Modified: 2017-06-26 00:45 CEST (History)
1 user (show)

See Also:
Source RPM: plasma-desktop-5.7.2-1.mga6.src.rpm
CVE:
Status comment:


Attachments

Description David Walser 2016-07-29 18:04:43 CEST
First there's an error from KWin at the very top of the screen, then once the splash goes away, you get the Compositor system settings module in the middle of the screen.  Is this really necessary?
David Walser 2016-07-29 18:04:52 CEST

Assignee: bugsquad => mageia

David Walser 2016-07-30 03:21:29 CEST

Blocks: (none) => 17523

Comment 1 Nicolas Lécureuil 2016-08-07 16:38:27 CEST
i don't understand your bug at all.
Comment 2 David Walser 2016-08-07 18:22:21 CEST
The first login with a fresh profile results in a KWin error at the top of the screen while the splash is going and then the Compositor system settings module automatically launches, just like MageiaWelcome.
Comment 3 David Walser 2016-08-08 16:30:33 CEST
Cannot reproduce in current Cauldron/Plasma.

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

Comment 4 David Walser 2016-08-10 14:37:40 CEST
Problem has reappeared.

This post describes the error message from KWin that appears during the splash:
https://bbs.archlinux.org/viewtopic.php?id=103685

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

Samuel Verschelde 2016-08-25 16:23:33 CEST

Assignee: mageia => kde

Comment 5 Nicolas Lécureuil 2017-03-14 17:26:28 CET
is it still valid with plasma 5.8.6 ?

CC: (none) => mageia

Comment 6 David Walser 2017-06-26 00:45:34 CEST
I only ever saw this problem on a physical machine at my old job.  I never had this problem in a VM, so I can't confirm whether it's still an issue.  I'll close this as OLD.  If anyone else sees this on real hardware, they can reopen.  Sorry for the delay.

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


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