[plasmashell] [Bug 353975] New: Black screen on second display.

[Mateusz via KDE Bugzilla]

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

Bug ID: 353975
Summary: Black screen on second display.
Product: plasmashell
Version: 5.3.2
Platform: Kubuntu Packages
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: NOR
Component: Multi-screen support
Assignee: ***@kde.org
Reporter: ***@gmail.com
CC: plasma-***@kde.org

When I connect second monitor I see non-interactive black screen on the given
monitor.
I can see cursor but entire(second monitor) area is not clickable, although I
can move windows to there.

Reproducible: Sometimes

Steps to Reproduce:
1. Have one monitor.
2. Connect second one.

Actual Results:
Workspace sometimes does not appear on the second monitor. No wallpaper, no
icons, only mouse cursor.

Expected Results:
Fully functional double-monitor workspace.

[Mateusz via KDE Bugzilla]

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

--- Comment #1 from Mateusz <***@gmail.com> ---
Created attachment 95014
--> https://bugs.kde.org/attachment.cgi?id=95014&action=edit
There are 2 monitors. Second one is basically black screen.

[Gerd v. Egidy via KDE Bugzilla]

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

Gerd v. Egidy <***@egidy.de> changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |***@egidy.de

--- Comment #2 from Gerd v. Egidy <***@egidy.de> ---
I have this problem too. I have three monitors, all connected during bootup.
The first one shows a background and you can right-click on it and get a menu.

The other ones just show a black background. You can move windows there and you
see a mouse cursor. But when you try to right-click in the background, you get
no context menu.

When I call "killall plasmashell; sleep 3; plasmashell" on a terminal, the
other two monitors get their intended background, context menu and so on after
plasmashell is restarted.

So to me this looks like an issue with the order the different subsystems are
started and how they depend on each other. Like the KScreen2 being started
after plasmashell or something like that.

This is on Fedora 22, x86-64, Intel graphics, and
plasma-workspace-5.4.2-4.fc22.x86_64
(from updates-testing).

[Gerd v. Egidy via KDE Bugzilla]

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

--- Comment #3 from Gerd v. Egidy <***@egidy.de> ---
This bug is especially annoying, because every time plasmashell starts without
"seeing" the other monitors, it seems to move all the panels, desktop widgets
etc. that were on the additional screens to the first one.

So I'd have to move everything to the right position again. But since you can't
move panels from one screen to another, essentially all panel settings and all
settings for the widgets within the panels are lost.

So automatically restarting plasmashell during startup is not enough as a
workaround, I also have to keep a good copy of
~/.config/plasma-org.kde.plasma.desktop-appletsrc and restore that.

[thebunnyrules via KDE Bugzilla]

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

thebunnyrules <***@gmail.com> changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |***@gmail.com

--- Comment #4 from thebunnyrules <***@gmail.com> ---
It has happened to me too. I confirm. In my case monitors are always attached
and sometimes one of them gets the black non-interactive screens. Logging out
and logging back in fixes it. Not a viable solution if you have things
happening that you can't interrupt....

More frequently, I get the black screen that develops after a few hours of use.
Between virtual desktops. One desktop keeps all the plasmoids, panels and
widgets, backgrounds and the others are black. You can still work in the black
desktops and switch into and out of them with hotkeys but shell is completly
gone there.

I'm Gallium for my R9 290 running in XFire; shell 5.4, KAOS distro.

I'm including some info about my system:

Octopi Sys-Info Output: http://pastebin.com/btVaPDDD
sudo blkid: http://pastebin.com/e4tzLh8Z
sudo fdisk -l: http://pastebin.com/060sNYvp
sudo journalctl -b | grep plasma: http://pastebin.com/skvn3v9e

Is there something else you want to see?

[thebunnyrules via KDE Bugzilla]

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

--- Comment #5 from thebunnyrules <***@gmail.com> ---
This is similar to this unconfirmed bug:
https://bugs.kde.org/show_bug.cgi?id=333445

It might seem, also takes place accross virtual desktops. I feel that the
failure that is causing the desktop to go black across virtual desktops is
similar to the one causing it accross screen or they are closely related.

[thebunnyrules via KDE Bugzilla]

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

--- Comment #6 from thebunnyrules <***@gmail.com> ---
Another bug report, reports the same behavior as the OP:
https://bugs.kde.org/show_bug.cgi?id=329958

[thebunnyrules via KDE Bugzilla]

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

--- Comment #7 from thebunnyrules <***@gmail.com> ---
https://bugs.kde.org/show_bug.cgi?id=345227

Here's another person reporting the same thing as the OP. They doc their
Notebook to a docking bay connected to to monitors: black screen with visible
mouse.

[Aleix Pol via KDE Bugzilla]

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

Aleix Pol <***@kde.org> changed:

What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Latest Commit| |http://commits.kde.org/plas
| |ma-workspace/4c4beb7a1097de
| |831c3ec6b5f5155bb65446e155
Resolution|--- |FIXED

--- Comment #8 from Aleix Pol <***@kde.org> ---
Git commit 4c4beb7a1097de831c3ec6b5f5155bb65446e155 by Aleix Pol.
Committed on 30/10/2015 at 16:04.
Pushed by apol into branch 'Plasma/5.4'.

Ensure the DesktopView has the correct size since the beginning

Otherwise ensureWindowType calls winId, triggering a window creation and
since the geometry is rect(0,0,0,0), the view is moved to the screen that
contains 0,0.

M +1 -0 shell/desktopview.cpp

http://commits.kde.org/plasma-workspace/4c4beb7a1097de831c3ec6b5f5155bb65446e155

[Gerd v. Egidy via KDE Bugzilla]

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

--- Comment #9 from Gerd v. Egidy <***@egidy.de> ---
Hello Aleix,

thank you for looking into this.

I took this patch, and your other patch
https://quickgit.kde.org/?p=plasma-workspace.git&a=commit&h=7e8aad767a250845a182166876550fb4e9701de4
and recompiled the plasma-workspace-5.4.2-6.fc22.src.rpm with it.

Unfortunately your patch does not fix or change the problem, it behaves still
exactly as I described it above.

[Aleix Pol via KDE Bugzilla]

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

Aleix Pol <***@kde.org> changed:

What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |REOPENED
Resolution|FIXED |---
Ever confirmed|0 |1

[Gerd v. Egidy via KDE Bugzilla]

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

--- Comment #10 from Gerd v. Egidy <***@egidy.de> ---
Anything I could do to help you track it down?

If you create a patch which makes plasmashell output additional debug
information for this problem, I'll apply it here and send you the output.

[Johannes Pfrang via KDE Bugzilla]

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

Johannes Pfrang <johannespfrang+***@gmail.com> changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |johannespfrang+***@gmail.co
| |m

[Bernd Steinhauser via KDE Bugzilla]

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

Bernd Steinhauser <***@bernd-steinhauser.de> changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |***@bernd-steinhauser.de

--- Comment #11 from Bernd Steinhauser <***@bernd-steinhauser.de> ---
Can confirm this in Plasma 5.5.

[Chris Gadd via KDE Bugzilla]

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

Chris Gadd <***@email.com> changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |***@email.com

[Nick Cross via KDE Bugzilla]

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

Nick Cross <***@goots.org> changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |***@goots.org

[Enrico Tagliavini via KDE Bugzilla]

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

Enrico Tagliavini <***@gmail.com> changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |***@gmail.com

[jamese via KDE Bugzilla]

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

jamese <***@gmail.com> changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |***@gmail.com

--- Comment #12 from jamese <***@gmail.com> ---
*** Bug 349482 has been marked as a duplicate of this bug. ***

[Alexander Schlarb via KDE Bugzilla]

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

Alexander Schlarb <alexander-***@xmine128.tk> changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |alexander-***@xmine128.tk

--- Comment #13 from Alexander Schlarb <alexander-***@xmine128.tk> ---
Yes, still happens in Plasma 5.5. I've noticed that it only happens on the very
first log in after a reboot through.
I also have some logs of me logging in at #359348 (if that's useful).

[Steven Kelbley via KDE Bugzilla]

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

Steven Kelbley <***@gmail.com> changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |***@gmail.com

--- Comment #14 from Steven Kelbley <***@gmail.com> ---
Same, confirm this exists in 5.5.5. Running Fedora 23 KDE spin with all updates
applied.

[via KDE Bugzilla]

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

***@gnu.org changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |***@gnu.org

--- Comment #15 from ***@gnu.org ---
Did somebody forget to test this? I'd tell you what my KDE version is, but the
cashew has gone missing, too. I just installed openSUSE Leap 42.1, so maybe
somebody else knows. I did go to system-settings -> Display-and-Monitor where
it dutifully shows all the correct information about both monitors. It doesn't
allow me to rotate 90 degrees, though. (I will need that when my new monitor
arrives, but not today.)

So I'd like my second monitor wall paper back, please.

[via KDE Bugzilla]

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

--- Comment #16 from ***@gnu.org ---
I'm using 5.5.4. Settings --> Configure Desktop --> System Settings --> Help
--> About System Settings --> Version.
I think that is too hard.

[Enrico Tagliavini via KDE Bugzilla]

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

--- Comment #17 from Enrico Tagliavini <***@gmail.com> ---
Maybe that's a fluke but it seems like this happens only in some specific,
albeit common, configuration. In my case I move my laptop between two desks.
One has a 1080p monitor (exactly the same resolution as the laptop screen), the
other has a 1680x1050 monitor. I get the black screen after login only with the
former one. The latter works as expected.

Anybody with this problem and two monitors of different resolutions by any
chance?

However, oddly enough, for my colleague desktop (note: not a laptop), where he
has two monitors of the same resolution, everything works fine. However, being
a desktop, he never connect or disconnect monitors which might be related (see
bug #353052).

This all is on Fedora 22 and 23, fully up to date. Currently using plasma 5.5.5

[Alexander Schlarb via KDE Bugzilla]

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

--- Comment #18 from Alexander Schlarb <alexander-***@xmine128.tk> ---
You're right: My laptop screen uses 1920x1080 while my second desktop screen
has a resolution of 1680x1050. I unfortunately do not have any external monitor
with the same resolution to test.
Maybe someone has a laptop with a resolution != 1080p?

[Bernd Steinhauser via KDE Bugzilla]

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

--- Comment #19 from Bernd Steinhauser <***@bernd-steinhauser.de> ---
You can have the bug with other resolutions as well and also if the screens
have the same resolution.
The resolution doesn't matter as far as I can tell.

[Alexander Schlarb via KDE Bugzilla]

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

--- Comment #20 from Alexander Schlarb <alexander-***@xmine128.tk> ---
That's too bad. :-(
Have you verified that this is this still the case on the same-resolution
external monitors, Bernd?

It could be something else screen-configuration related through. We should
collect a list of affected and non-affected screen configurations. I'll attach
my `xrandr --current --verbose` when using my affected external screen.

[Alexander Schlarb via KDE Bugzilla]

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

--- Comment #21 from Alexander Schlarb <alexander-***@xmine128.tk> ---
Created attachment 98341
--> https://bugs.kde.org/attachment.cgi?id=98341&action=edit
xrandr --current --verbose (Alexander Schlarb)

[Bernd Steinhauser via KDE Bugzilla]

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

--- Comment #22 from Bernd Steinhauser <***@bernd-steinhauser.de> ---
I have only "external" screens (not everybody's using a laptop :P). And they
have a resolution of 1920x1200.

I'd say: Wait for Plasma 5.7 and see if it's still there, because it was said
that when they can depend on Qt 5.6 (thus the next version) the multiscreen
handling should improve.

[Enrico Tagliavini via KDE Bugzilla]

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

--- Comment #23 from Enrico Tagliavini <***@gmail.com> ---
(In reply to Bernd Steinhauser from comment #19)

Post by Bernd Steinhauser via KDE Bugzilla
You can have the bug with other resolutions as well and also if the screens
have the same resolution.
The resolution doesn't matter as far as I can tell.

Yep scratch what I said... today the setup that used to work (which I use
rarely) actually messed up (for the first time) upon login :(

[Bob Wya via KDE Bugzilla]

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

Bob Wya <***@gmail.com> changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |***@gmail.com

[Dmitry Chmerev via KDE Bugzilla]

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

Dmitry Chmerev <***@gmail.com> changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |***@gmail.com

[Jan Fucek via KDE Bugzilla]

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

Jan Fucek <***@gmail.com> changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |***@gmail.com

--- Comment #24 from Jan Fucek <***@gmail.com> ---
I had the same problem with docked notebook and three displays of 1920x1080
resolution on plasma 5.6.4. But only sometimes. Now, when I updated to 5.6.90,
I have the problem all the time. It moves all of my widgets to one display, not
even the primary one and the other displays are non-responsive black
background. But they are usable in a way that I see cursor and can move the
widgets and windows there.
Starting kquitapp5 plasmashell && kstart5 plasmashell works, but I have to
rearrange the widgets all the time.
While Plasma 5.7 is still beta and there was a proposed change in better
multi-monitor setup, maybe someone can look into it before it goes out of beta.
At least for the reason that for me the problem has worsened compared to Plasma
5.6.4.

[Jan F. via KDE Bugzilla]

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

--- Comment #25 from Jan F. <***@gmail.com> ---
Created attachment 99713
--> https://bugs.kde.org/attachment.cgi?id=99713&action=edit
Two black screens after plasma start

I managed to grab a photo of the situation today. That is how it looks before I
run `kquitapp5 plasmashell && kstart5 plasmashell` every day.

[Fabio Coatti via KDE Bugzilla]

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

Fabio Coatti <***@gmail.com> changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |***@gmail.com

[Fabio Coatti via KDE Bugzilla]

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

--- Comment #26 from Fabio Coatti <***@gmail.com> ---
*** Bug 364513 has been marked as a duplicate of this bug. ***

[via KDE Bugzilla]

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

***@free.fr changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |***@free.fr

--- Comment #27 from ***@free.fr ---
Happening here too, second monitor is black, I can't right click it, but can
move windows to it. The 1st monitor's wallpaper is replaced by the second one ;
if I do "killall plashmashell && plasmashell", everything goes back to normal.

[via KDE Bugzilla]

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

--- Comment #28 from ***@free.fr ---
More info : Plasma 5.6.90 on Arch Linux with kde-unstable repo, QT 5.7.

Happens almost all the time (I would say, 7 times / 10)

[Fabio Coatti via KDE Bugzilla]

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

--- Comment #29 from Fabio Coatti <***@gmail.com> ---
I have the same issue, with an HP and a dell external monitor. (1366x768 vs
1920 x 1200). In my case, physically disconnecting the monitor or simply
turning it off fixes the external monitor "blanking"

[David Edmundson via KDE Bugzilla]

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

David Edmundson <***@davidedmundson.co.uk> changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |***@kde.org

--- Comment #30 from David Edmundson <***@davidedmundson.co.uk> ---
*** Bug 365066 has been marked as a duplicate of this bug. ***

[Aliaksandr Stelmachonak via KDE Bugzilla]

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

Aliaksandr Stelmachonak <***@ava1ar.me> changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |***@ava1ar.me

[Joel via KDE Bugzilla]

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

Joel <***@dabbles-n-doodads.com> changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |***@dabbles-n-doodads.com

--- Comment #31 from Joel <***@dabbles-n-doodads.com> ---
Another with the same issue ( and more ). Logging out and back in usually
fixes the unresponsive black screen. I have the added issue of any program
launchers I've added to the panel or favorites seem to be gone for good.

[Joel via KDE Bugzilla]

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

--- Comment #32 from Joel <***@dabbles-n-doodads.com> ---
I just went back and looked more at my missing program launchers. What I found
is that a new blank panel was overlaying the original. When I deleted the
panel, the one I set up with the launchers was underneath.

[Michał via KDE Bugzilla]

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

Michał <***@op.pl> changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |***@op.pl

--- Comment #33 from Michał <***@op.pl> ---
This happens to me since I started using Plasma 5, it's still there in
plasma-5.7. It doesn't reproduce immediately, but rather after some time
(0.5…couple of hours). Just like for other users, the background gets black and
is not clickable, but otherwise the other monitor is fully usable.

Killing and restarting plasma helps, until next reproduction after some time.

[jamese via KDE Bugzilla]

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

--- Comment #34 from jamese <***@gmail.com> ---
Still occurs for me on Neon dev/stable with Plasma 5.7 and plugging in my 2x
Displayport 1.2 screens. This went away for me at least when using Plasma 5.6
but now it's back.

Both screens are active but black, the mouse moves into them but nothing in
there. Unplugging the cable and replugging helped the last time this happened
and restarting plasma as in comment #27 another time helped fix it.

[andy via KDE Bugzilla]

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

andy <***@gmail.com> changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |***@gmail.com

--- Comment #35 from andy <***@gmail.com> ---
I can confirm same problem. Three monitors and very frequently one of them is
off. It is definitely Plasm a problem. Checked also in Plasma 5.7. The same
configuration (hardware and software) but cinnamon desktop instead, problem
disappears.

[Konrad Materka via KDE Bugzilla]

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

Konrad Materka <***@wp.pl> changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |***@wp.pl

[Jan F. via KDE Bugzilla]

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

--- Comment #36 from Jan F. <***@gmail.com> ---
Plasma 5.7.1 still experiencing the issue

[Konrad Materka via KDE Bugzilla]

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

--- Comment #37 from Konrad Materka <***@wp.pl> ---
I have similar problem. After log in second screen is always black (missing
background etc), but working. This happens every time. I'm using laptop (non
HD) + DVI HD monitor.

It doesn't happen when I connect monitor after log in. In SDDM both laptop and
external monitor have the same resolution and duplicates output. During KDE
startup external monitor resolution changes to correct one and desktop area is
expanded.

Latest Neon User 5.7.1 (Plasma 5.7.1, Qt 5.7) + Latest (git) mesa drivers
(Intel Broadwell).

[Ian Whyman (thev00d00) via KDE Bugzilla]

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

Ian Whyman (thev00d00) <***@gentoo.org> changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |***@gentoo.org

[via KDE Bugzilla]

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

***@gmail.com changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |***@gmail.com

--- Comment #38 from ***@gmail.com ---
Upgraded from Plasma 5.6.5 (which didn't have this issue) to 5.7.1 on a desktop
with three monitors. HDMI1 and HDMI2 have the same black, non-click-able
background (but still usable) and all panels are bunched up on HDMI3. The login
screen spans all three monitors as expected. Restarting plasma fixes the
problem (though I have to rearrange all panels immediately afterwards).

[Sebastian Kügler via KDE Bugzilla]

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

Sebastian Kügler <***@kde.org> changed:

What |Removed |Added
----------------------------------------------------------------------------
Keywords| |multiscreen
Version|5.3.2 |5.7.1
CC| |***@kde.org

[Jan F. via KDE Bugzilla]

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

--- Comment #39 from Jan F. <***@gmail.com> ---
The issue persists in 5.7.2 for me (have not seen anything related in
changelog, so this is probably expected)

[HuangXi via KDE Bugzilla]

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

HuangXi <***@outlook.com> changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |***@outlook.com

--- Comment #40 from HuangXi <***@outlook.com> ---
The same here by 5.7.2-1 in archlinux.
One screen is balck without wallpaper,the other works.
Restarting plasma or reset multi monitors setting by systemsetting may fixes
it.

[Stoyan Tsalev via KDE Bugzilla]

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

Stoyan Tsalev <***@tzalev.com> changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |***@tzalev.com

--- Comment #41 from Stoyan Tsalev <***@tzalev.com> ---
Exactly the same thing here, plus I'm using vertical screens. Fully updated
Fedora 24, plasma 5.71. Workaround is indeed disabling then re-enabling the
second screen.

[S. Christian Collins via KDE Bugzilla]

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

S. Christian Collins <***@hotmail.com> changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |***@hotmail.com

[Thilo-Alexander Ginkel via KDE Bugzilla]

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

Thilo-Alexander Ginkel <***@ginkel.com> changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |***@ginkel.com

[Markus Heß via KDE Bugzilla]

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

Markus Heß <***@googlemail.com> changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |***@googlemail.com

[Marcelo Rocha via KDE Bugzilla]

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

Marcelo Rocha <***@marcelocavalcante.net> changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |***@marcelocavalcante.n
| |et

--- Comment #42 from Marcelo Rocha <***@marcelocavalcante.net> ---
I can confirm the bug is still there.. I am running Arch linux with the last
versions of plasma and I am with the same issue.. When logging into my system,
my second screen is black and right clicking doesn't work. But after running
"kquitapp plasmashell && kstart plasmashell" both my screen are reloaded and I
can go back to my work.. So far I am running this "fix" everytime I log into my
system.

[Bobby via KDE Bugzilla]

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

Bobby <***@gmail.com> changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |***@gmail.com

--- Comment #43 from Bobby <***@gmail.com> ---
Problem is still here on Fedora 24 running Plasma 5.7.1 on monitor at 1600x900
and another monitor at 1920x1080.

[Yaroslav Sidlovsky via KDE Bugzilla]

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

Yaroslav Sidlovsky <***@gmail.com> changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |***@gmail.com

[via KDE Bugzilla]

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

***@gmail.com changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |***@gmail.com

--- Comment #44 from ***@gmail.com ---
Here too, using neon and up to date

[via KDE Bugzilla]

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

--- Comment #45 from ***@gmail.com ---
Persists on 5.7.3.

[Nikola Schnelle via KDE Bugzilla]

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

Nikola Schnelle <***@gmail.com> changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |***@gmail.com

[Sebastian Kügler via KDE Bugzilla]

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

Sebastian Kügler <***@kde.org> changed:

What |Removed |Added
----------------------------------------------------------------------------
Status|REOPENED |NEEDSINFO
Resolution|--- |WAITINGFORINFO

--- Comment #46 from Sebastian Kügler <***@kde.org> ---
Could you test this with against master (either using Neon Dev Unstable, or
openSUSE tumbleweed with latest git master builds)?

We have fixed a number of issues that could lead to this behaviour.

If problems persist, please attach a freshly created
~/.local/share/kscreen/kscreen.log to this bugreport.

Thanks!

[Iacopo Palazzi via KDE Bugzilla]

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

Iacopo Palazzi <***@gmail.com> changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |***@gmail.com

[S. Christian Collins via KDE Bugzilla]

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

--- Comment #47 from S. Christian Collins <***@hotmail.com> ---
I was experiencing the no desktop on second monitor issue, and I can confirm
that using the latest KDE Neon Dev Unstable (built today), the issue seems to
be resolved in both of the cases I tested for:
1. No desktop (black screen) on second monitor when OS is booted with secondary
monitor already plugged in.
2. No desktop on second monitor when it is attached after the desktop session
has loaded.

[Iacopo Palazzi via KDE Bugzilla]

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

--- Comment #48 from Iacopo Palazzi <***@gmail.com> ---
Hello everybody,

I have to confirm this issue, even I'm a little bit confused because I have two
simila KDE installations, but with only one I'm experiencing this, let me be
more clear.

I have two laptops:

1 - Asus N56VZ (Intel i7-3630QM, QM, 8 GB Ram, NVIDIA GT 650M 2GB), Display
Port: VGA, Ubuntu 16.04 (updated from 15.10). Laptop monitor is 1920x1080.

2 - Asus N552VW-FI202T (Interl i7- 6700HQ, 16 GB RAM, NVIDIA GTX 960M 4GB),
Display Port: HDMI, Ubuntu 16.04 (fresh installation). Laptop monitor is
3840x2160.

In both machines, I have the same KDE version. From KInfoCenter I can see the
following details:
- KDE Plasma Version: 5.5.5
- QT Version: 5.5.1
- Kernel Version: 4.4.0.-31-generic (machine #1), 4.4.0-34-generic (machine
#2)

*** Machine #1 ***
Works great, no problem with monitors at all.

*** Machine #2 ***
is experiencing the same issues described on this thread. I can describe 3
scenarios to reproduce the bug:

1 - If I turn on laptop #2 with the HDMI monitor powered on, sddm stucks and I
cannot even see the login screen (I can still access ttys through
CTRL+ALT+[1,2,3,...]).

2 - If I turn on laptop #2 with the HDMI monitor powered off, sddm appears
with the login page and I can login without problems. Once I'm in, I can turn
the HDMI monitor on, in this case I get it working without the background and I
can't even right-click on it, even if I can still move windows and mouse over
it. In this situation, If I kill and restart plasmashell, everything goes
normally: second monitor appears with background and I can right-click on it.

So, my current workaround is:
1 - Turn on the laptop with monitor powered off:
2 - Login in KDE environment;
3 - Power on the monitor;
4 - kill and restart plasmashell

You might agree with me that it's quite frustrating :(

I'd like to help you guys to find a solution on this, please tell me if you
need more/different information.

Thanks a lot!

Iacopo

[via KDE Bugzilla]

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

--- Comment #49 from ***@free.fr ---
When testing latest Neon Dev Unstable, I haven't been affected by the bug
either. But I tested it only once, it probably isn't enough to confirm that it
is fixed.

[via KDE Bugzilla]

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

***@vonwert.eu changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |***@vonwert.eu

[Marcelo Rocha via KDE Bugzilla]

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

--- Comment #50 from Marcelo Rocha <***@marcelocavalcante.net> ---
What is the version for this Neon?
I am still with the problem running:

* plasma-desktop 5.7.3-1
* plasma-framework 5.24.0-1
* plasma-workspace 5.7.3-1

[Nikola Schnelle via KDE Bugzilla]

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

--- Comment #51 from Nikola Schnelle <***@gmail.com> ---
I can confirm that the bug is fixed in neon dev unstable.

@marcelo that is kde from git-master

[Marcelo Rocha via KDE Bugzilla]

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

--- Comment #52 from Marcelo Rocha <***@marcelocavalcante.net> ---
@Nikola thanks. I'll try to test it as soon as possible.

[Johannes Pfrang via KDE Bugzilla]

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

Johannes Pfrang <johannespfrang+***@gmail.com> changed:

What |Removed |Added
----------------------------------------------------------------------------
CC|johannespfrang+***@gmail.co |
|m |

[Samuel Suther via KDE Bugzilla]

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

Samuel Suther <***@gmx.de> changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |***@gmx.de

--- Comment #53 from Samuel Suther <***@gmx.de> ---
(In reply to Iacopo Palazzi from comment #48)

I have Asus N76vz. Since I play i bit arround with plugin and plugout the vga
monitor, I got trouble with dualmonitor-Setup. (BEFORE it works great).

I'll describe the behavior exactly, so maybe sombody can see where the trouble
comes from:

If I boot and login into KDE, external Monitor (following named S1) shows the
Menu, and a wallpaper.
Second monitor (following named S2) is black, BUT if I move the mouse to this
screen, I can see the mouse-pointer. Even if right-click on S2 dosn't show any
menu (seems plasma not working on this screen)

So if I unplug, and replugin the S1, both screen have a wallpaper and work like
a charm. But after replugin, the menu is on S2.

Maybe this help a bit, to figure out, that it seems to be a plasma-issue?!

[Alexander Schlarb via KDE Bugzilla]

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

--- Comment #54 from Alexander Schlarb <alexander-***@xmine128.tk> ---
Just a quick comment from my side: I used to use an older (about 2011) laptop
with nVidia graphics card and nouveau driver and this would happen almost
always I booted up with my external screen plugged in. With my new laptop
(released May 2016) and its AMD card with radeon driver it hasn't ever happened
yet.

[via KDE Bugzilla]

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

--- Comment #55 from ***@free.fr ---
Removing the xf86-video-intel driver and using Kernel Modesetting instead seems
to have fixed the problem for me...

[Samuel Suther via KDE Bugzilla]

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

--- Comment #56 from Samuel Suther <***@gmx.de> ---
(In reply to tromzy from comment #55)

Post by via KDE Bugzilla
Removing the xf86-video-intel driver and using Kernel Modesetting instead
seems to have fixed the problem for me...

Ok, thanks you for your reply. Can you explain, what to do to use Kernel
Modesetting instead ?
Is it load by default, if I have remove xf86-video-intel ?

[via KDE Bugzilla]

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

--- Comment #58 from ***@free.fr ---
(In reply to Samuel Suther from comment #56)

Post by Samuel Suther via KDE Bugzilla
(In reply to tromzy from comment #55)

Post by via KDE Bugzilla
Removing the xf86-video-intel driver and using Kernel Modesetting instead
seems to have fixed the problem for me...

Ok, thanks you for your reply. Can you explain, what to do to use Kernel
Modesetting instead ?
Is it load by default, if I have remove xf86-video-intel ?

All you have to do is remove xf86-video-intel AND also remove
/etc/X11/xorg.conf.d/20-intel.conf if you have it. Reboot and you should be
using the Modesetting driver.

[Marcelo Rocha via KDE Bugzilla]

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

--- Comment #57 from Marcelo Rocha <***@marcelocavalcante.net> ---
How come? I mean, I never really tried to read a lot about it but I always
though you would not need to unninstall your driver since all the new drivers
comes with mode setting by default.

That is, for example, from Arch Linux wiki:
Late KMS start
Intel, Nouveau, ATI and AMDGPU drivers already enable KMS automatically for all
chipsets, so you need not install it manually.

Sent from BlueMail



On Aug 19, 2016, 7:49 AM, at 7:49 AM, Samuel Suther via KDE Bugzilla

Post by Mateusz via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=353975
(In reply to tromzy from comment #55)

Post by via KDE Bugzilla
Removing the xf86-video-intel driver and using Kernel Modesetting

instead

Post by via KDE Bugzilla
seems to have fixed the problem for me...

Ok, thanks you for your reply. Can you explain, what to do to use
Kernel
Modesetting instead ?
Is it load by default, if I have remove xf86-video-intel ?
--
You are on the CC list for the bug.

[Marcelo Rocha via KDE Bugzilla]

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

--- Comment #59 from Marcelo Rocha <***@marcelocavalcante.net> ---
But is this the right thing to do?

[Marcelo Rocha via KDE Bugzilla]

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

--- Comment #60 from Marcelo Rocha <***@marcelocavalcante.net> ---
I tried removing my xf86-video-intel and let it run only with modsetting,
and the issue was fixed for me now.

It seems a problem between the combination kde/intel driver?!? o.O

Em sex, 19 de ago de 2016 às 08:04, via KDE Bugzilla <

Post by Mateusz via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=353975
(In reply to Samuel Suther from comment #56)

Post by Samuel Suther via KDE Bugzilla
(In reply to tromzy from comment #55)

Post by via KDE Bugzilla
Removing the xf86-video-intel driver and using Kernel Modesetting

instead

Post by Samuel Suther via KDE Bugzilla

Post by via KDE Bugzilla
seems to have fixed the problem for me...

Ok, thanks you for your reply. Can you explain, what to do to use Kernel
Modesetting instead ?
Is it load by default, if I have remove xf86-video-intel ?

All you have to do is remove xf86-video-intel AND also remove
/etc/X11/xorg.conf.d/20-intel.conf if you have it. Reboot and you should be
using the Modesetting driver.
--
You are on the CC list for the bug.

[roman via KDE Bugzilla]

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

roman <***@gmail.com> changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |***@gmail.com

--- Comment #61 from roman <***@gmail.com> ---
Confirm on Plasma 5.7.3
if I do "killall plashmashell && plasmashell", everything goes back to normal.

[Michael Seifert via KDE Bugzilla]

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

Michael Seifert <***@error-reports.org> changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |***@error-reports.org

[Michael Seifert via KDE Bugzilla]

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

--- Comment #62 from Michael Seifert <***@error-reports.org> ---
I can confirm the issue and the workaround for Plasma 5.7.4 as well.

[CaCO3 via KDE Bugzilla]

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

CaCO3 <***@ruinelli.ch> changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |***@ruinelli.ch

--- Comment #63 from CaCO3 <***@ruinelli.ch> ---
I also can confirm that "killall plasmashell && plasmashell" fixes it.
Please note the typo in the command in #61!

lsb_release -a

No LSB modules are available.
Distributor ID: neon
Description: KDE neon User Edition 5.7
Release: 16.04
Codename: xenial

[Joel via KDE Bugzilla]

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

--- Comment #64 from Joel <***@dabbles-n-doodads.com> ---
I tried this and it does seem to work. I had to add nohup so I could close the
terminal window.

killall pasmashell && nohup plasmashell

[Joel via KDE Bugzilla]

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

--- Comment #65 from Joel <***@dabbles-n-doodads.com> ---
typo,

killall plasmashell && nohup plasmashell

[Joel via KDE Bugzilla]

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

--- Comment #66 from Joel <***@dabbles-n-doodads.com> ---
Playing with this a bit more I found this works best for me,

killall plasmashell; nohup plasmashell >/dev/null 2>&1 &

Now I can close the terminal when done and it does not create an ever growing
nohup.out file.

[Aliaksandr Stelmachonak via KDE Bugzilla]

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

--- Comment #67 from Aliaksandr Stelmachonak <***@ava1ar.me> ---
killall plasmashell && kstart plasmashell

Easier and cleaner

[CaCO3 via KDE Bugzilla]

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

--- Comment #68 from CaCO3 <***@ruinelli.ch> ---
I created a shell script with this content:
--------------------------
#! /bin/sh
killall plasmashell; plasmashell
--------------------------
Then I added a link to it to the desktop.
So I simply can run it when it is required.

[kaasboer via KDE Bugzilla]

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

kaasboer <***@gmx.net> changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |***@gmx.net

--- Comment #69 from kaasboer <***@gmx.net> ---
Hi,

I found out "by accident" that there might be a workaround for this problem:

I run F24 KDE spin with Plasma 5.7.4 on a docked T450s with 2 Monitors. With
sddm as display manager I had to restart plasmashell after every login.

Today I switched to gdm and now plasmashell works with the 2nd monitor without
a problem.

( Why "by accident"? : I switched to gdm because sddm shows the login dialog on
both monitors instead of just the first one. This is fixed as well as the black
screen problem.)

cu,
kaasboer

[thebunnyrules via KDE Bugzilla]

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

--- Comment #70 from thebunnyrules <***@gmail.com> ---
Hey guys, does anyone know how I can unsub from this thread? It's great to
see you guys are so active at resolving the multi-display issues but I've
switched back to gnome (KDE was driving me too crazy... lolol).

On 15 September 2016 at 09:04, kaasboer via KDE Bugzilla <

Post by Mateusz via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=353975
What |Removed |Added
------------------------------------------------------------
----------------
Hi,
I found out "by accident" that there might be a workaround for this
I run F24 KDE spin with Plasma 5.7.4 on a docked T450s with 2 Monitors.
With
sddm as display manager I had to restart plasmashell after every login.
Today I switched to gdm and now plasmashell works with the 2nd monitor
without
a problem.
( Why "by accident"? : I switched to gdm because sddm shows the login
dialog on
both monitors instead of just the first one. This is fixed as well as the
black
screen problem.)
cu,
kaasboer
--
You are on the CC list for the bug.

[CaCO3 via KDE Bugzilla]

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

--- Comment #71 from CaCO3 <***@ruinelli.ch> ---
(In reply to kaasboer from comment #69)

Post by kaasboer via KDE Bugzilla
Hi,
I run F24 KDE spin with Plasma 5.7.4 on a docked T450s with 2 Monitors. With
sddm as display manager I had to restart plasmashell after every login.
Today I switched to gdm and now plasmashell works with the 2nd monitor
without a problem.
( Why "by accident"? : I switched to gdm because sddm shows the login dialog
on both monitors instead of just the first one. This is fixed as well as the
black screen problem.)
cu,
kaasboer

How did you do this?

I tried
dpkg-configure gdm
as well as
dpkg-configure lightdm
but with both the DE did not start anymore, both screens stayed black!

Note:
The issues with the second screen black only started after I installed KDE Neon
on top of Kubuntu. How ever I also installed a virgin Neon Distribution (Ubuntu
based) and had the same issue.

[Dik Takken via KDE Bugzilla]

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

Dik Takken <***@xs4all.nl> changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |***@xs4all.nl

--- Comment #72 from Dik Takken <***@xs4all.nl> ---
Created attachment 101118
--> https://bugs.kde.org/attachment.cgi?id=101118&action=edit
ZIP file containing captured debug info and configs

[Dik Takken via KDE Bugzilla]

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

--- Comment #73 from Dik Takken <***@xs4all.nl> ---
I may have figured out what is causing this issue. I ran

xrandr --verbose

a few times and diffed the output between reboots. As it turns out, the
reported CRTC for the same external monitor changes randomly between reboots.
Disabling and re-enabling the display restores the CRTC reported by xrandr.
This is what I see happening:

I start out with a correctly operating dual-screen setup, two identical
displays attached to the dock of my laptop, desktop extends across both
screens.
After reboot, I often see the following things happening:

1. login screen and KDE splash screen extends across both screens, as it
should. Desktop appears, one of the screens is black. I can move the mouse to
the black screen, but no response to mouse clicks.
2. Open display config. Disable secondary monitor. While doing this, the
display resolution for the now disabled screen is reduced.
3. Enable the display again. Desktop extends again to both displays
4. Restore resolution of the just enabled display

I captured the output of xrandr, kscreen, and the changes in the kscreen
display configuration file after each of the above steps 1 to 4, see
attachments. You can see how the CRTC changes after disabling and re-enabling
the secondary display.

Hopefully, this will pin down what the source of the problem is.

[Alexander Schlarb via KDE Bugzilla]

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

Alexander Schlarb <alexander-***@xmine128.tk> changed:

What |Removed |Added
----------------------------------------------------------------------------
CC|alexander-***@xmine128.tk |

[Greg White via KDE Bugzilla]

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

Greg White <***@kupulau.com> changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |***@kupulau.com

--- Comment #74 from Greg White <***@kupulau.com> ---
I'm seeing this same behavior with plasma 5.8 beta. A black screen on one
monitor, and the only fix is to restart plasma.

[CaCO3 via KDE Bugzilla]

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

--- Comment #75 from CaCO3 <***@ruinelli.ch> ---
I just installed a daily snapshot of Kubuntu 16.10 (17.09.2016) and discovered
that it is also broken there! To solve it I had to restart plasmashell. Since
it was a virgin installation, there where no old config files involved.

[Greg White via KDE Bugzilla]

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

--- Comment #76 from Greg White <***@kupulau.com> ---
One other data point: I swapped to LXQT using kwin as the window manager.
Everything was fine there, so this does not seem to be kwin related.

[Francesco Chicchiriccò via KDE Bugzilla]

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

Francesco Chicchiriccò <***@apache.org> changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |***@apache.org