[plasmashell] [Bug 356225] Panel moves to wrong screen when external monitor is connected

[jamese via KDE Bugzilla]

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

--- Comment #188 from jamese  ---
Unplugged my external screen from laptop, next day opened lid, signed in and
panel placed on laptop screen in Comment #187 had gone.
I added the panel back, result is I now get a minimum of 2 notifications in the
Notification area for every notification received.

Using KDE Neon User Edition with Plasma 5.7.4

e.g Do the above, load up KDE Connect on Android phone, send a ping to the
paired laptop and two notifications appear, one positions above (Y-axis) the
other.
The lower one seems to be 2 notifications stacked exactly on top of another
(Z-axis) as that one has a far darker box-shadow. My guess is that the panel
from the external screen and the panel from the laptop screen which disappeared
are still adding notifications to the laptop screen along with the new panel I
added.

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 356225] Panel moves to wrong screen when external monitor is connected

[jamese via KDE Bugzilla]

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

--- Comment #187 from jamese  ---
This bug is still occurring episodically for me (ref Comment #159)  - now on
KDE Neon User with Plasma 5.7.4, updated packages as of date. It's happening
far less often, though.

Plugged in my DP-1 screen (DisplayPort 1.1), the panel from the Laptop Screen
eDP1 will be on the DisplayPort screen. Can move panel via Panel Settings back
to laptop screen.

Befuddling how a panel can't just be linked to one display and stay there
forever. At times I've ended with up 3 panels on one screen.

Other side effects of this include notifications appearing twice and bits of
the other panel notiications appearing on the laptop screen even when the
external screen is unplugged (e.g Device Notification plug events)

Is it best to await 5.8 ?

-- 
You are receiving this mail because:
You are watching all bug changes.

[KScreen] [Bug 366067] Impartial kscreen config for setup leads to partially configured desktop on hitting 'Apply'

[jamese via KDE Bugzilla]

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

--- Comment #11 from jamese  ---
I should also point out that while the Plasma desktop is munged with the DP
cable plugged in the following can happen:

- Mouse cursor works
- I can switch to run level 1 with Ctrl+Alt+1
- When I switch to run level 1, my two DP screens come up perfectly, DP1-1
followed by DP1-2 a second later.
- I can't get a "kscreen-console bug" report on run level 1 even with "export
DISPLAY=:0" before.

Switching back with Ctrl+Alt+7 returns me to the munged desktop which can now
be rescued by plugging in an  HDMI cable

-- 
You are receiving this mail because:
You are watching all bug changes.

[KScreen] [Bug 366067] Impartial kscreen config for setup leads to partially configured desktop on hitting 'Apply'

[jamese via KDE Bugzilla]

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

--- Comment #10 from jamese  ---
Created attachment 100366
  --> https://bugs.kde.org/attachment.cgi?id=100366=edit
Output of kscreen-bug with HDMI resolution OK

-- 
You are receiving this mail because:
You are watching all bug changes.

[KScreen] [Bug 366067] Impartial kscreen config for setup leads to partially configured desktop on hitting 'Apply'

[jamese via KDE Bugzilla]

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

--- Comment #9 from jamese  ---
Created attachment 100365
  --> https://bugs.kde.org/attachment.cgi?id=100365=edit
Output of kcmshell5 kcm_kscreen

I added a note showing where I switched outputs from DP to HDMI,  as I move the
HDMI screen around in the settings layout area and hit apply, the fuzziness and
bit depth issues go away but I have to restart kcm_kscreen to get the slider
showing in place of "No available resolutions"

-- 
You are receiving this mail because:
You are watching all bug changes.

[KScreen] [Bug 366067] Impartial kscreen config for setup leads to partially configured desktop on hitting 'Apply'

[jamese via KDE Bugzilla]

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

--- Comment #8 from jamese  ---
Created attachment 100364
  --> https://bugs.kde.org/attachment.cgi?id=100364=edit
Laptop with MST Displayport config

I chmod'd this to 0400, before trying to plug in DP cable.

-- 
You are receiving this mail because:
You are watching all bug changes.

[KScreen] [Bug 366067] Impartial kscreen config for setup leads to partially configured desktop on hitting 'Apply'

[jamese via KDE Bugzilla]

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

--- Comment #7 from jamese  ---
Created attachment 100363
  --> https://bugs.kde.org/attachment.cgi?id=100363=edit
Kscreen config, laptop with HDMI plugged in

This after the screen fuzziness and bit depth issues are resolved.

-- 
You are receiving this mail because:
You are watching all bug changes.

[KScreen] [Bug 366067] Impartial kscreen config for setup leads to partially configured desktop on hitting 'Apply'

[jamese via KDE Bugzilla]

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

--- Comment #6 from jamese  ---
Here's some further debugging on this one.

Config "ae115bc4aa5f4ce701f72fc9e25f01cb" is the MST setup with Laptop Screen +
DP1-1 (master) and DP1-2 (slave) - I chmod'd this to 0400 so it couldn't be
written by any user. It still has the width/height in it from the last working
setup.
Config "1818bd03d6fa05c34acde90101a5d242" is the Laptop with HDMI plugged in.

I plugged in DP cable and the bug reproduces.  I've got kcmshell5 kcm_kscreen
running and will attach output although nothing appears in the output when I
activate the DP setup.
I unplug the DP cable and no change to the desktop occurs. Laptop screen is
still split in half  & external DP screens are not active at all.
I then switch inputs on DP1-2 to HDMI and plug in the HDMI cable, this brings
the desktop back with HDMI output enabled and visible along with Laptop Screen.
But:

* HDMI (HDMI2 in kscreen) says "No available resolutions" and the display is
slightly fuzzy. It also appears to be at a lower bit depth
* After some repositioning of the HDMI screen and hitting apply, the resolution
slider appears with 1920x1080 enabled and the bit depth  / fuzziness issues
disappear.

I then unplug the HDMI cable to see if I can get DP displays back and the
Laptop screen goes black then comes back and freezes although the mouse cursor
works. Can't do anything here. Plugging the DP cable in does not bring the
desktop back, nothing in kcmshell output. Can't run kscreen-bug here as only
mouse works.
Plugging the HDMI cable back in re-activates the desktop!

Other weirdness that occurs here:
- is when I plug the HDMI cable in, all the windows either from Gtk (Shutter)
or KDE apps (e.g kate) disappear under the panel when maximised, even though
the panel has "Always Visible" set.
This is a common problem for me at the moment with KDE multi-screen setup.
- when I initally plug in the DP screens they come up greyed out, showing the
wrong aspect ratio although the slider says 1920x1080. If I fiddle with the
slider the greyed out screens resize correctly.

Configs and outputs will be attached.

-- 
You are receiving this mail because:
You are watching all bug changes.

[KScreen] [Bug 366067] Impartial kscreen config for setup leads to partially configured desktop on hitting 'Apply'

[jamese via KDE Bugzilla]

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

--- Comment #4 from jamese  ---
Plasma 5.7.2, Qt 5.7, Neon/User packages.

I'll try to grab some debugging info when it happens again based on
https://community.kde.org/Solid/Projects/ScreenManagement

-- 
You are receiving this mail because:
You are watching all bug changes.

[KScreen] [Bug 366067] Impartial kscreen config for setup leads to partially configured desktop on hitting 'Apply'

[jamese via KDE Bugzilla]

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

--- Comment #3 from jamese  ---
Created attachment 100281
  --> https://bugs.kde.org/attachment.cgi?id=100281=edit
Photo of Laptop Screen when it's split down the middle

The left part of the screen is moved to the right, the other half is on the
left. Panel is at top on purpose.
The location of the split is based on where the external screens are joined
above the Laptop Screen.

-- 
You are receiving this mail because:
You are watching all bug changes.

[KScreen] [Bug 366067] Impartial kscreen config for setup leads to partially configured desktop on hitting 'Apply'

[jamese via KDE Bugzilla]

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

--- Comment #2 from jamese  ---
Created attachment 100280
  --> https://bugs.kde.org/attachment.cgi?id=100280=edit
Kscreen config for setup when displays correctly configure

This config includes the "mode" entry. It has the same filename as the config
without the mode entry.

-- 
You are receiving this mail because:
You are watching all bug changes.

[KScreen] [Bug 366067] Impartial kscreen config for setup leads to partially configured desktop on hitting 'Apply'

[jamese via KDE Bugzilla]

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

--- Comment #1 from jamese  ---
Created attachment 100279
  --> https://bugs.kde.org/attachment.cgi?id=100279=edit
Possibly impartial Kscreen config leading to bug ?

This is the config that was active at the time of the bug. The 'mode' entries
are not present for the two external screens

-- 
You are receiving this mail because:
You are watching all bug changes.

[KScreen] [Bug 366067] New: Impartial kscreen config for setup leads to partially configured desktop on hitting 'Apply'

[jamese via KDE Bugzilla]

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

Bug ID: 366067
   Summary: Impartial kscreen config for setup leads to partially
configured desktop on hitting 'Apply'
   Product: KScreen
   Version: 5.7.2
  Platform: Neon Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: common
  Assignee: se...@kde.org
  Reporter: james.el...@gmail.com

I've got a DisplayPort 1.2 / MST setup, same is in the unrelated Bug #362570.
There are two DP1.2 screens above the laptop screen, the laptop is placed below
and in the middle of the two external screens. The left screen DP1-2 is the
last in the MST chain, the right is the primary screen in the chain.

Often when I configure the screens for this setup in Display Settings, the 2
external screens appear greyed out in the Display Settings area and are not
marked as "Enabled". When I Enable them, position them and then hit "Apply" the
external screens remain blank and the Laptop Screen is split down the middle
(probably due to the positioning in Display Settings). 
No widgets or applications are usable when this happens but the mouse cursor
remains movable.

The only way to resurrect the Desktop is by switching to a another run level,
moving the offending ~/.local/share/kscreen config file (or all of them) and
then restarting sddm, then logging in again. At this point the screen
configuration proceeds OK.
Obviously restarting SDDM causes all running applications to close including
running virtual machines which means I now close all applications and shutdown
virtual machines before trying to configure this screen setup to avoid issues
with the VMs.

In the other run level, I check the config file being used by kscreen and it
appears that the two external screens are missing the "mode" entry, which
contain refresh and size values.  If I was a user that didn't know about
runlevels I'd probably hard reset the laptop.


Makes me think that the config is being partially applied or being applied
without refresh, width and height values.


See upcoming attachments and some debug output. This happened with Kubuntu
16.04 packages as well (now using Neon/User)

I can switch to an HDMI / Displayport hybrid setup and see if this can
reproduced as it would help to isolate the issue.



Reproducible: Sometimes

Steps to Reproduce:
1. Plug in Display Port  1.2 / MST screens, external screens don't
automatically configure
2. Position and Enable external screens
3. Hit Apply, laptop screens split down the middle and is unresponsive

Actual Results:  
Switched to runlevel 1 and remove kscreen config, then restart sddm to
reconfigured screens

Expected Results:  
External screens should be configured and appear with most recent panel
configuration, laptop screen should not split down the middle.

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 356225] Panel moves to wrong screen when external monitor is connected

[jamese via KDE Bugzilla]

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

--- Comment #159 from jamese  ---
As an addition to my recent update, Installed the plasma 5.7.2 update on the
weeked in Neon/User and played around plugging/unplugging screens on
Displayport 1.2 / MST setup and haven't been able to reproduce beyond one
initially duplicated panel which seems to have been left from my other
multi-screen setup.
I'd tentatively say 5.7.2 goes a long way to fix this but not 100% sure yet :D

-- 
You are receiving this mail because:
You are watching all bug changes.

[KScreen] [Bug 362570] Kscreen settings no longer shows display ID since 16.04 update

[jamese via KDE Bugzilla]

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

--- Comment #6 from jamese  ---
That looks good although I'd put the larger text at the top followed by the
smaller text:



|BRAND|
|model|
|output|


Laptop Screen probably doesn't need the Output ID as I doubt a laptop would
ship with two screens ? Doesn't hurt if it shows, though.

Also, great to see KDE using Phabricator, it's awesome, maybe Maniphest is on
the horizon as a bug tracker ?

Thanks

-- 
You are receiving this mail because:
You are watching all bug changes.

[KScreen] [Bug 362570] Kscreen settings no longer shows display ID since 16.04 update

[jamese via KDE Bugzilla]

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

--- Comment #3 from jamese  ---
Thanks  for the response.

Consider that hitting the [i] info button shows on screen eith DP1-1 or DP1-2,
which is great but there is no correlation with the  'Display ID' on the OSD
and the related "Dell Inc,  Dell U2414H" labelled screen in the settings
window, as those labels don't include DP1-1 or DP1-2.

The only way to see which of the screens is DP1-1 and which is DP1-2 is to
click on the screen and look at the title above the "Display [ ] Enabled"
checkbox.
Previously, as I knew my DP1-2 screen was the left one, I could just look at
the screen layout presented and drag and drop it to the left, then DP1-1 to the
right. Didn't have to click the "i" or look at the screen title.

The recent change added an extra step when you have two identical external
screens.

There is a previous version with the "Display id" here, in this case HDM1 -
https://www.kde.org/announcements/plasma-5.2/kscreen.png

If the label for the screen said "DP1-1/2, Dell Inc, U2414H" that'd solve the
issue.

Thanks!

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 356225] Panel moves to wrong screen when external monitor is connected

[jamese via KDE Bugzilla]

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

--- Comment #156 from jamese  ---
I was able to duplicate the issue of moving/migrating panels yesterday on KDE
Neon User / Plasma 5.7.1 packages / Qt 5.7.0 with X Intel driver.

I had my laptop plugged into a DisplayPort (1.1) screen @ 2560x1440. It's a
Dell U2711. DP1 is left of Laptop Screen. Both had/have panels at the top
screen edge, which is my preferred position for panels.

When I pulled the cable the panel on the Laptop screen blanked for < 1 second
then came back with the panel, I put the plug back in and the DP1 screen came
back with the panel on it in the correct position. All Good!

I repeated the above again and the panel disappeared from the Laptop screen,
plugging DP1 back in the screens flickered then DP1 came back up with the
correct backgrounds but the panel from the Laptop screen was overlaid over the
DP1 panel. There was no panel left on the Laptop Screen.

Unplugging the DP1 screen and the Laptop screen is then left with no panel at
all. I right click on the desktop and choose "Add  Panel > Default Panel" and I
can get the panel back but now have 3 panels when I plug back in DP1. Two on
DP1 at the top, one on Laptop at the bottom.

I removed one of the duplicate panels on DP1, unplugged DP1 and replugged it
after a few seconds and the duplicate panel came back for about 5 seconds then
disappeared on it's own.

I've now unplugged and replugged the screen about 10 times and cannot reproduce
the issue with the moving panels at all. So it seems to be a transient problem
that is difficult to reproduce, at least for me.

One further thing of interest is that If I drag a Chrome window from DP1 to
Laptop then unplug DP1 and replug it in after a few seconds, the Chrome window
moves back to DP1 rather than staying on Laptop.

I'm no KDE/Qt coder but it seems to me that KDE doesn't record the screen "ID"
that a Window/Panel/Widget was on?
If I put a Window/Panel on Laptop Screen it should stay on Laptop Screen
forever and never be moved by the system.  Likewise, in my three screen setup
where I have two MST DP screens (Panels placed at top) above with the Laptop
Screen centred below them (panel placed at bottom), the panels should always
remain on the screens that I placed them on. Why would I want them to be moved
if I placed them in a preferred position  and why would I want the Chrome
window to move back to the screen I just moved it off ?

Linking a Window/Panel to a screen would completely avoid the problem of having
 a panel from a Laptop screen move to a screen that's been unplugged and is no
longer active. Maybe that's already done and it's not working, I don't know!

If one of the devs has a testing process that would help them nail this bug I'd
be really really happy to help out testing updated packages on my multi-screen
setups.

-- 
You are receiving this mail because:
You are watching all bug changes.

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

[jamese via KDE Bugzilla]

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

--- Comment #34 from jamese  ---
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.

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 356225] Panel moves to wrong screen when external monitor is connected

[jamese via KDE Bugzilla]

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

--- Comment #108 from jamese  ---
Hi

I'm on Neon dev/stable with plasma-workspace 5.6.4+p16.04+git20160603.0158-0 -
not sure if this includes the change referenced in the link at
https://bugs.kde.org/show_bug.cgi?id=356225#c103 ?

I've got 3 screen setups in use at various times and I switch between all 3
regularly:

1 laptop only - eDP1 1920x1080
2 eDP1 with a Dell U2711 @ 2560x1440 on DisplayPort 1.1 (DP1)
3 eDP1 with 2x Dell U2414H on DisplayPort 1.2 in an MST chain (DP1-1 and DP1-2)

Since moving to Neon dev/stable the incidence of weird panel placements have
lessened but are still there. For instance this morning I plugged in setup #2
and the panel from eDP1 appeared underneath (z-axis) the panel originally set
up for the U2711. Since moving to Neon I can move the panel back to eDP1
without the panel disappearing.

At other times I've had all 3 panels from setup #3 appear on the eDP1 screen (2
at top, one at bottom). My default is to have panels at the top of the screen.
Kscreen also forgets screen layouts between sessions 100% of the time.

Another issue probably unrelated to this is that on switching to screen setup
#2 the desktops start to move to their positions freeze although the mouse
cursor moves. The ~/.local/share/kscreen/ config file for the relevant screen
layout shows that both DP1-1 and DP1-2 have no width and height set in their
config). I have to rm everything in ~/.local/share/kscreen and kill sddm losing
running applications. I think that's another bug that I'll report separately.

As always keen to test this out and help solve the multi screen issues current
in KDE... I just need a testing plan or similar that would help the developers.

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 356225] Panel moves to wrong screen when external monitor is connected

[jamese via KDE Bugzilla]

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

--- Comment #90 from jamese  ---
I installed the Neon (dev/stable) packages on top of a Kubuntu 16.04 install to
see if this happens and it does:

Info Centre says:
KDE Plasma version: 5.6.3
KDE FW version : 5.21.0
Qt : 5.5.1
Kernel 4.4.0-21-generic

Yesterday evening I had my laptop running with a panel on the bottom of the
Laptop screen and a panel each at the top of the two external screens.
Instead of unplugging the externals screens I disabled both external screens
and made sure my  Laptop screen was Primary, then unplugged the Displayport
cable. This morning I plugged in the cable and signed into KDE. 

The displays didn't activate so I bought up Display Configuration, the screens
were greyed out, so I enabled them and set them to the correct resolution and
position.
The displays came up, which was great, but the panel from the bottom of the
laptop screen appeared on the bottom of the left external screen, the laptop
screen then had no panels, the right external screen had one and the left
external screen had a panel at the top and the bottom.
Trying to dragging the bottom panel on the external left screen to the Laptop
screen in Panel Settings > Screen Edge causes the panel to disappear.

Neon is apparently dropping Qt 5.6 into the dev edition soon so it'll be
interesting to see if this behaviour changes with a Qt upgrade.

-- 
You are receiving this mail because:
You are watching all bug changes.

[KScreen] [Bug 362570] Kscreen settings no longer shows display ID since 16.04 update

[jamese via KDE Bugzilla]

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

--- Comment #1 from jamese  ---
Created attachment 98741
  --> https://bugs.kde.org/attachment.cgi?id=98741=edit
Highlighting where Display ID is missing

Only way to see display ID is in the rectangular highlighted area.
Clicking the (I)nfo  icon does show the Display ID along with Manufacturer and
Model #

-- 
You are receiving this mail because:
You are watching all bug changes.

[KScreen] [Bug 362570] New: Kscreen settings no longer shows display ID since 16.04 update

[jamese via KDE Bugzilla]

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

Bug ID: 362570
   Summary: Kscreen settings no longer shows display ID since
16.04 update
   Product: KScreen
   Version: 5.5.1
  Platform: Kubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: kcm
  Assignee: se...@kde.org
  Reporter: james.el...@gmail.com

Upgraded to to Kubuntu 16.04 and the kscreen Display Configuration settings no
longer shows DP1-2 or DP1-1.  The kscreen in 15.10 did show this, it was very
useful to quickly identify screens, but it's been removed.

My screen setup has a laptop screen with 2 Displayport panels of the same
manufacturer and model - without the display ID in the panel layout it's
difficult to work out which screen is which without clicking each one and
looking in the details area below.

See upcoming screenshot for suggestion on putting display ID back in for
quicker recognition.

Occurred in whatever version shipped with Kubuntu 16.04, I'm having a go at KDE
Neon at the moment and the same thing happens.

Plasma : 5.6.3
Qt : 5.5.1
KDE : 5.21.0






Reproducible: Always

Steps to Reproduce:
1. Plug in screens
2. Go to rearrange screens
3. Can't quickly check which screen is which.


Expected Results:  
The Panel layout should show

Manufacturer
Model
Display ID (e.g HDMI1, DP1, DP1-2 etc)

-- 
You are receiving this mail because:
You are watching all bug changes.

[KScreen] [Bug 360563] black screen on session restore until removing ~/.local/share/kscreen

[jamese via KDE Bugzilla]

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

--- Comment #21 from jamese  ---
Created attachment 98055
  --> https://bugs.kde.org/attachment.cgi?id=98055=edit
output of kscreen-console bug when black screen is present

-- 
You are receiving this mail because:
You are watching all bug changes.

[KScreen] [Bug 360563] black screen on session restore until removing ~/.local/share/kscreen

[jamese via KDE Bugzilla]

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

--- Comment #20 from jamese  ---
Created attachment 98051
  --> https://bugs.kde.org/attachment.cgi?id=98051=edit
Screenshot from this morning's resume

Plugged in DP cable and got all three screens with two panels on DP1-2 and one
on Laptop. Switch primary from laptop to DP1-1 and this was the result.

Laptop screen black, mouse can go into it, can drag application windows into
it. No right click context menu, can't drag widgets into it, can't create
widgets on it.

I get three notification messages in the systray, possibly related to the
original 3 panels.

-- 
You are receiving this mail because:
You are watching all bug changes.

[KScreen] [Bug 360563] black screen on session restore until removing ~/.local/share/kscreen

[jamese via KDE Bugzilla]

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

--- Comment #19 from jamese  ---
Sorry, #356225, but I can't find a link to edit my comment to correct the typo.

I thought this sounded familiar and looking back through my bug list I found
#349482 which I resolved as a duplicate of #353975 as it was getting more
interest. This may be a duplicate of that?

Other thing worth noting is that I have two U2414H screens and Alexey's
screenshots show the same screen type. Mine are on an MST chain using
Displayport 1.2 - so DP cable from laptop to first screen (DP1-1) which has a
DP cable to the terminating screen (DP1-2)

All these issues happen for me when switching from multi-screen to laptop only
and back to multi-screen.

Last thing to note is that when I switch to runlevel 1 to rm
.local/share/kscreen/* and then kill SDDM after I have no desktop, the text 
from the shell is cloned perfectly onto all three screens.

-- 
You are receiving this mail because:
You are watching all bug changes.

[KScreen] [Bug 354429] Displayport: upon resume, only a small section of screen is present on external screen

[jamese via KDE Bugzilla]

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

jamese  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |FIXED

--- Comment #3 from jamese  ---
Have a feeling this was fixed in 5.5 as it doesn't happen anymore on Kubuntu
15.10 with Plasma 5.5 from backports.

-- 
You are receiving this mail because:
You are watching all bug changes.

[KScreen] [Bug 360563] black screen on session restore until removing ~/.local/share/kscreen

[jamese via KDE Bugzilla]

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

jamese  changed:

   What|Removed |Added

 CC||james.el...@gmail.com

--- Comment #17 from jamese  ---
This happens for me, using a DisplayPort connection as well running on an Intel
Iris Pro with the "intellinuxgraphics" drivers from intel.
I have to rm  the kscreen settings .local/share/kscreen/* and then kill sddm,
losing everything including running virtual machines and try to log in again.


Reading an unrelated issue #336225 it's possible that fixes for the various
issues with KDE and multiple monitors is landing in 5.6 with fixes from Qt. 
Can't be sure, though.

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 356225] Panel moves to wrong screen when external monitor is connected

[jamese via KDE Bugzilla]

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

--- Comment #19 from jamese  ---
Created attachment 97271
  --> https://bugs.kde.org/attachment.cgi?id=97271=edit
Incorrect panel placement post resume

The panel at the bottom of DP1-2 was placed on Laptop Screen pre-suspend the
previous day. Post resume it appears on DP1-2, it should be on Laptop Screen.
The panel on DP1-2 at the top was placed on DP1-2. the previous day.

If I place the panel at the top of Laptop Screen then post-resume DP1-2 ends up
with two panels at the top, one overlapping the other.

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 356225] Panel moves to wrong screen when external monitor is connected

[jamese via KDE Bugzilla]

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

jamese  changed:

   What|Removed |Added

 CC||james.el...@gmail.com

--- Comment #18 from jamese  ---
Can confirm this issue, when resuming the panel from the bottom of "Laptop
Screen" moves to the bottom of one of the two DP screens plugged in. See
attachment coming up.

Plasma 5.5 backports packages, latest as of date on Kubuntu 15.10, using DP1.2
screens in an MST chain.

xrandr -q after resume:

Screen 0: minimum 8 x 8, current 3840 x 2160, maximum 32767 x 32767
eDP1 connected primary 1920x1080+948+1080 (normal left inverted right x axis y
axis) 309mm x 173mm
   1920x1080 60.05*+  59.93  
   1680x1050 59.9559.88  
   1600x1024 60.17  
   1400x1050 59.98  
   1600x900  60.00  
   1280x1024 60.02  
   1440x900  59.89  
   1280x960  60.00  
   1368x768  60.00  
   1360x768  59.8059.96  
   1152x864  60.00  
   1280x720  60.00  
   1024x768  60.00  
   1024x576  60.00  
   960x540   60.00  
   800x600   60.3256.25  
   864x486   60.00  
   640x480   59.94  
   720x405   60.00  
   640x360   60.00  
DP1 disconnected (normal left inverted right x axis y axis)
DP1-1 connected 1920x1080+1920+0 (normal left inverted right x axis y axis)
527mm x 296mm
   1920x1080 60.00*+  50.0059.94  
   1600x1200 60.00  
   1600x900  60.00  
   1280x1024 75.0260.02  
   1152x864  75.00  
   1280x720  60.0050.0059.94  
   1024x768  75.0860.00  
   800x600   75.0060.32  
   720x576   50.00  
   720x480   60.0059.94  
   640x480   75.0060.0059.94  
   720x400   70.08  
DP1-2 connected 1920x1080+0+0 (normal left inverted right x axis y axis) 527mm
x 296mm
   1920x1080 60.00*+
   1600x1200 60.00  
   1600x900  60.00  
   1280x1024 75.0260.02  
   1152x864  75.00  
   1024x768  75.0860.00  
   800x600   75.0060.32  
   640x480   75.0060.00  
   720x400   70.08  
HDMI1 disconnected (normal left inverted right x axis y axis)
HDMI2 disconnected (normal left inverted right x axis y axis)
VGA1 disconnected (normal left inverted right x axis y axis)
VIRTUAL1 disconnected (normal left inverted right x axis y axis)




Can't agree more with Samuel in Comment 16, using KDE with multiple screens is
a complete PITA. I wonder how many people try out KDE, find it doesn't work
consistently with multiple screens, then silently switch to something else?
There are a quite a few bug reports about DisplayPort issues lodged, search for
DisplayPort in bugs.kde.org and you'll see

In my case, if the panel from the laptop display moves to another screen and
there is a separate bug where that screen doesn't back post resume then the
laptop display is nearly unusable without knowing the keystrokes to drop to
runlevel 1 and kill sddm.

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 359001] New: After login post suspend, external screens do not activate. Changing the primary display causes Plasma crash

[jamese via KDE Bugzilla]

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

Bug ID: 359001
   Summary: After login post suspend, external screens do not
activate. Changing the primary display causes Plasma
crash
   Product: plasmashell
   Version: 5.5.3
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: james.el...@gmail.com
CC: bhus...@gmail.com, plasma-b...@kde.org

Application: plasmashell (5.5.3)

Qt Version: 5.5.1
Operating System: Linux 4.2.0-27-generic x86_64
Distribution: Ubuntu 15.10

-- Information about the crash:
- What I was doing when the application crashed:

I suspended my laptop yesterday and left the DisplayPort cable plugged in, this
morning I opened the lid, it took a little bit longer to get the login screen
than expected but after about 10 seconds it appeared (it's usually right away).
I have two Displayport screens in an MST chain (DP1-1 and DP1-2), neither
showed the login screen. The LED light on the screen shows that they are in
power save mode.

I signed in and neither external screen showed up. KDE still thinks the screens
are active though as most of the applications are on the external displays.

 I was able to bring up DIsplay Configuration and change the Primary Display to
laptop screen. Upon hitting Apply, Plasma crashed and produced the backtrace in
this report.

I have my panel at the top of the Laptop screen and I noted right clicking for
More Actions > Move did not show the context menu as the context menu for each
application was being launched above the panel into the display regions for
DP1-1 and DP1-2 that could not be seen.

Display Configuration screen layout is like this:
[ DP1-2 ] [ DP1-1]
   [ Laptop ]





- Unusual behavior I noticed:

1. Desktops on external screens do not show even though they were working
pre-suspend
2. Panel at the top and after crash the context menu launches above the panel,
rendering the context menu inaccessible. Moving the panel to the bottom allows
context menu to be accessed via right click on the application.
3. In some instances when the DP cable is plugged and unplugged the laptop
desktop freezes then splits down the middle. It shows the right half of the
desktop on the left and the left half on the right. KDE is unusable at this
point.


This happens nearly every day when resuming from suspend. In order to get  a
working setup I have to close all applications, especially running virtual
machines ot avoid corrupted databases, switch to runlevel 1, rm
~/.local/share/kscreen/* and then sudo killall sddm.

The crash can be reproduced sometimes.

-- Backtrace:
Application: Plasma (plasmashell), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7facb99d3800 (LWP 21501))]

Thread 8 (Thread 0x7faca4d8c700 (LWP 21503)):
#0  0x7facb40da8dd in poll () at ../sysdeps/unix/syscall-template.S:81
#1  0x7facb81a8bd2 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1
#2  0x7facb81aa74f in xcb_wait_for_event () from
/usr/lib/x86_64-linux-gnu/libxcb.so.1
#3  0x7faca6ed57e9 in QXcbEventReader::run (this=0x1c175e0) at
qxcbconnection.cpp:1229
#4  0x7facb47d0a6e in QThreadPrivate::start (arg=0x1c175e0) at
thread/qthread_unix.cpp:331
#5  0x7facb38bc6aa in start_thread (arg=0x7faca4d8c700) at
pthread_create.c:333
#6  0x7facb40e5eed in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 7 (Thread 0x7fac9e405700 (LWP 21510)):
#0  0x7facb40da8dd in poll () at ../sysdeps/unix/syscall-template.S:81
#1  0x7facb0e711ec in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7facb0e712fc in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7facb4a0850b in QEventDispatcherGlib::processEvents
(this=0x7fac980008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420
#4  0x7facb49af50a in QEventLoop::exec (this=this@entry=0x7fac9e404da0,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#5  0x7facb47cbac4 in QThread::exec (this=) at
thread/qthread.cpp:503
#6  0x7facb7079c35 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#7  0x7facb47d0a6e in QThreadPrivate::start (arg=0x1cf2e00) at
thread/qthread_unix.cpp:331
#8  0x7facb38bc6aa in start_thread (arg=0x7fac9e405700) at
pthread_create.c:333
#9  0x7facb40e5eed in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 6 (Thread 0x7fac92fa5700 (LWP 21535)):
#0  0x7facb40da8dd in poll () at ../sysdeps/unix/syscall-template.S:81
#1  0x7facb0e711ec in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7facb0e712fc in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7facb4a0850b in 

[plasmashell] [Bug 359001] After login post suspend, external screens do not activate. Changing the primary display causes Plasma crash

[jamese via KDE Bugzilla]

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

--- Comment #1 from jamese  ---
The other odd thing I just noticed is that applications in the panel become
grouped after this crash, even though my preference is to not group
applications in the panel.

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 356720] Panel displayed on wrong monitor on login

[jamese via KDE Bugzilla]

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

--- Comment #3 from jamese  ---
Created attachment 96990
  --> https://bugs.kde.org/attachment.cgi?id=96990=edit
Showing moving panel to correct screen

Here's an example of a panel appearing on the wrong screen. It appeared on the
screen in the top right, when it should be in the bottom screen. I have panels
anchored to the top screen edge.

This occurs after changing the Primary Display. Shouldn't widgets be allocated
to a display  and remain on that display?

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 356720] Panel displayed on wrong monitor on login

[jamese via KDE Bugzilla]

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

--- Comment #4 from jamese  ---
Created attachment 96991
  --> https://bugs.kde.org/attachment.cgi?id=96991=edit
Panel appearing on incorrect screen, under/above that screen's panel

And here's an example of logging in this morning and finding after the usual
jiggery-pokery with kscreen display setup that the panel from DP1-1 is now on
DP1-2. If you look closely you'll see one panel above the other on DP1-2. It
should be on DP1-1.

Again, this happens after  changing the Primary Display.

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 358735] Several seemingly related monitor connect/disconnect issues

[jamese via KDE Bugzilla]

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

jamese  changed:

   What|Removed |Added

 CC||james.el...@gmail.com

--- Comment #1 from jamese  ---
I too have an inordinate amount and similar problems with multiple displays,
using Display Port 1.2  / MST.  This system runs Kubuntu with the Plasma 5.5
backports

plasma/krunner crashes have gone away, mostly, with Plasma 5.5 but multiple
display setup is still a pain.  The issue occurs during cable plug-in OR
display setup and is especially evident when moving from a multi display setup,
to laptop only, then back to a multi display setup.

Either -
+ I get one display blank (sometimes with a working mouse cursor) OR
+ the display splits in half and becomes frozen, with the left half on the
right and the right half on the left OR
+ the display half-configures and the desktop becomes unresponsive, although
the mouse cursor might move OR
+ configuring and moving screens, then hitting Apply in kscreen causes the
desktop to become unresponsive OR
+ upon login, all displays are blank.

Switching to runlevel 1 and checking top, the system is just happy idling away
with no load. Interestingly when dropping to another runlevel, all 3 screens
including the 2 in the MST chain happily clone each other even when Plasma/KDE
is finding it hard to configure the setup or crashing.

In all instances, removing the contents of ~/.local/share/kscreen/ and then
running a sudo killall sddm, then signing back is the only way to get back to
square one and start again.

Once it is setup, it works flawlessly for the entire session without crashing,
I'm especially pleased with the MST support.

I'm really happy to help test any possible or proposed fixes in order to get a
stable multi-desktop system working. Qt coding is not my forte.

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 349482] After resume from suspend, non-primary display in multi-screen setup is black

[jamese via KDE Bugzilla]

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

jamese  changed:

   What|Removed |Added

 Resolution|--- |DUPLICATE
 Status|UNCONFIRMED |RESOLVED

--- Comment #7 from jamese  ---
After reading https://bugs.kde.org/show_bug.cgi?id=353975 this appears to be
the same thing.

Since updating to Plasma 5.5 from Kubuntu Backports, Plasma crashes have all
but disappeared but I still have funky multi-screen support, possibly related
to other bugs, in KDE... Generally ending with unusable desktops and me having
to kill sddm and rm .local/share/kscreen/*, then signing in again.

*** This bug has been marked as a duplicate of bug 353975 ***

-- 
You are receiving this mail because:
You are watching all bug changes.

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

[jamese via KDE Bugzilla]

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

jamese  changed:

   What|Removed |Added

 CC||james.el...@gmail.com

--- Comment #12 from jamese  ---
*** Bug 349482 has been marked as a duplicate of this bug. ***

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 356720] Panel displayed on wrong monitor on login

[jamese via KDE Bugzilla]

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

jamese  changed:

   What|Removed |Added

 CC||james.el...@gmail.com

--- Comment #2 from jamese  ---
I get a similar thing, quite often if I have a panel on my laptop screen and
one on the external monitor,  the laptop panel will migrate to the external
screen and sit over the external monitor panel.
If I remove the extra panel and subsequently use my laptop without external
screens, the laptop display has no panel any more and I have to add a new
Default Panel.

External screen is connected via Displayport as well -  I don't know if KDE
doesn't like Displayport connections, include MST, but my setup has regular,
daily issues with multiscreen support especially when switching  between
external + laptop -> laptop only -> external + laptop  (i.e desktop -> mobile
-> desktop usage pattern).

Using Kubuntu 15.10 + Plasma 5.5 backports

-- 
You are receiving this mail because:
You are watching all bug changes.