[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-bugs-dist
Subject:    [KScreen] [Bug 351390] New: Corrupted kscreen config breaks KDE startup process
From:       Dik Takken <d.h.j.takken () xs4all ! nl>
Date:       2015-08-17 8:49:10
Message-ID: bug-351390-17878 () http ! bugs ! kde ! org/
[Download RAW message or body]

https://bugs.kde.org/show_bug.cgi?id=351390

            Bug ID: 351390
           Summary: Corrupted kscreen config breaks KDE startup process
           Product: KScreen
           Version: 5.3.2
          Platform: openSUSE RPMs
                OS: Linux
            Status: UNCONFIRMED
          Severity: grave
          Priority: NOR
         Component: common
          Assignee: dvratil@kde.org
          Reporter: d.h.j.takken@xs4all.nl

Switching between various setups with external monitors sometimes results in a
kscreen profile that appears to be corrupted: Any subsequent attempt to login
on the system using that specific monitor setup will fail, throwing me back to
the login screen as soon as kscreen is started.

Reproducible: Sometimes

Steps to Reproduce:
The kscreen config files appears to get corrupted when:

1. Laptop is suspended to RAM while disconnected from docking station
2. Laptop is docked
3. Laptop wakes up connected to the dock


Actual Results:  
The kscreen profile containing the docked configuration got corrupted. The next
time I tried to login while docked failed and I got thrown back to the login
screen. When I detached the laptop from the dock, or changed the external
monitor setup, logging in worked just fine.

Deleting the corrupted kscreen profile fixed the problem.

Expected Results:  
Corrupted kscreen profiles should never cause KDE startup to fail. As a last
resort, it should delete the corrupted profile and create a new one.

I marked this bug as 'grave', since it renders the system basically useless. If
you do not have the technical knowledge to find the kscreen profile and delete
it, you simply cannot login anymore.

-- 
You are receiving this mail because:
You are watching all bug changes.
[prev in list] [next in list] [prev in thread] [next in thread]