Bug 379485 - infinit switch
Summary: infinit switch
Status: RESOLVED WORKSFORME
Alias: None
Product: KScreen
Classification: Plasma
Component: common (show other bugs)
Version: 5.9.5
Platform: Neon Linux
: NOR crash
Target Milestone: ---
Assignee: Sebastian Kügler
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-05-03 17:02 UTC by tuor
Modified: 2021-01-16 04:35 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments
printf "[Rules]\nkscreen.*=true" >> ~/.config/QtProject/qtlogging.ini; kscreen-console bug > $(tempfile) (16.41 KB, text/plain)
2017-05-03 17:02 UTC, tuor
Details
tempfile=$(tempfile); sudo lshw -C Display > "$tempfile" (1.02 KB, text/plain)
2017-05-04 08:56 UTC, tuor
Details

Note You need to log in before you can comment on or make changes to this bug.
Description tuor 2017-05-03 17:02:22 UTC
Created attachment 105326 [details]
printf "[Rules]\nkscreen.*=true" >> ~/.config/QtProject/qtlogging.ini; kscreen-console bug > $(tempfile)

Hi Folks

I'm running KDE Neon 5.9 (current version, all up to date).

Symptom:
Infinit wwitching of Display configurations. It does just switch and switch and switch an so on. It just don't stop.

When does it occure?
Most of the time when I just connected a new screen. But sometimtes when i unlock my screen. For example I'm off wokring for 30 minutes, come back, unlock the screen and it happens.
It ONLY happens, when I have a secondary screen connected.

Workaround:
reboot! After a reboot all is fine again.

How often?
Today 3 Times! Other days never. From time to time it just happens randomly. Like 2 times a week.

Pleas tell me if I can do something to get this bug solved!

Salutations
Aaron
Comment 1 Sebastian Kügler 2017-05-04 08:09:06 UTC
Hi Aaron, thanks for the bug report!

In order to debug this, we need some more information. Please tell us what video card and driver you're using. Also, please produce the kscreen.log file by exporting 

KSCREEN_LOGGING=true

before logging in into your Plasma's environment. I will tell us what kind of even triggers the infinite loop.

Have you tried using a different displayport cable, by the way? Intermittent cable failure could easily produce such issues...
Comment 2 tuor 2017-05-04 08:56:29 UTC
Created attachment 105337 [details]
tempfile=$(tempfile); sudo lshw -C Display > "$tempfile"
Comment 3 tuor 2017-05-04 10:34:00 UTC
Hi Sebastian

I have the problem with different cables and different screens.

situation 1: at work with a docking station and a display port cable connected to it
situation 2: at home with only a display port cable

How do I do exactly export the KSCREEN_LOGGING=true variable? Should I just export it in my bashrc? Or is there an other place where I should set environment variables?

Today I didn't have the issue yet. I would need to log over some time, until it happens again.

Where would kscreen log then? So I can upload the file when it happened again. ;)

Thx for your fast answer!

Salutations
Aaron
Comment 4 tuor 2017-05-04 10:34:14 UTC
Hi Sebastian

I have the problem with different cables and different screens.

situation 1: at work with a docking station and a display port cable connected to it
situation 2: at home with only a display port cable

How do I do exactly export the KSCREEN_LOGGING=true variable? Should I just export it in my bashrc? Or is there an other place where I should set environment variables?

Today I didn't have the issue yet. I would need to log over some time, until it happens again.

Where would kscreen log then? So I can upload the file when it happened again. ;)

Thx for your fast answer!

Salutations
Aaron
Comment 5 tuor 2017-05-17 15:49:23 UTC
I could export the KSCREEN_LOGGING variable. Where does kscreen log now? What file should I upload, when it happens again?
Comment 6 tuor 2017-05-17 15:53:53 UTC
It seems to be: ~/.local/share/kscreen/kscreen.log
I'll upload the file when it happens again.
Comment 7 Justin Zobel 2020-12-17 05:30:00 UTC
Thank you for the crash report.

As it has been a while since this was reported, can you please test and confirm if this issue is still occurring or if this bug report can be marked as resolved.

I have set the bug status to "needsinfo" pending your response, please change back to "reported" or "resolved/worksforme" when you respond, thank you.
Comment 8 Bug Janitor Service 2021-01-01 04:36:46 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 9 Bug Janitor Service 2021-01-16 04:35:46 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!