[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#806991: marked as done (kscreenlocker doesn't support moving between single and multiple screens)

Your message dated Wed, 08 Mar 2017 08:52:53 +0100
with message-id <2760455.LaKmSpugxR@odyx.org>
and subject line Re: Bug#806991: kscreenlocker doesn't support moving between single and multiple screens
has caused the Debian Bug report #806991,
regarding kscreenlocker doesn't support moving between single and multiple screens
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
806991: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=806991
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: plasma-workspace
Version: 4:5.4.3-1
Severity: important
File: kscreenlocker_greet
Tags: upstream

Hi,

My usual laptop workflow implies moving from battery (using the laptop screen)
to being docked with an additional DisplayPort screen (using the two screens).

When suspending in the "laptop" setup and waking up in the "docked" setup, the
screen "unlocker" usually appears only on the laptop screen. When unlocking,
the plasma desktop uses only the laptop screen. Launching "kscreen" is enough
for plasma to notify the two screens and use the two screens again.

When suspending in the "docked" setup and waking up in the "laptop" setup, the
situation is usually that the "unlocker" screen is not visible: the desktop is
visible, and the mouse can be moved, but no clicks can be done, and it cannot
be unlocked. The only workaround I have found is to login in cli on tty1 as the
same user and run "killall -9 kscreenlocker_greet". 

My analysis is that "kscreenlocker_greet" is spawned once per physical screen,
and this situation is not reevaluated on suspend/wakeup, leading to a missing
screen in "laptop-to-docked", and to an additional process (unuseable) that
needs to be killed manually in "docked-to-laptop".

I'm happy to run more tests, please ask!

Cheers,

OdyX

-- System Information:
Debian Release: stretch/sid
  APT prefers testing-proposed-updates
  APT policy: (500, 'testing-proposed-updates'), (500, 'proposed-updates'), (500, 'buildd-unstable'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.2.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=fr_CH.UTF-8, LC_CTYPE=fr_CH.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages plasma-workspace depends on:
ii  dbus-x11                            1.10.6-1
ii  frameworkintegration                5.16.0-1
ii  gdb                                 7.10-1
ii  kactivities                         5.16.0-1
ii  kde-cli-tools                       4:5.4.3-1
ii  kded5                               5.16.0-1
ii  kinit                               5.16.0-1
ii  kio                                 5.16.0-1
ii  libc6                               2.21-1
ii  libcln6                             1.3.4-1
ii  libdbusmenu-qt5-2                   0.9.3+15.10.20150604-1
ii  libgcc1                             1:5.2.1-27
ii  libgps22                            3.15-2
ii  libice6                             2:1.0.9-1+b1
ii  libkf5activities5                   5.16.0-1
ii  libkf5auth5                         5.16.0-1
ii  libkf5baloo5                        5.16.0-1
ii  libkf5bookmarks5                    5.16.0-1
ii  libkf5completion5                   5.16.0-1
ii  libkf5configcore5                   5.16.0-1
ii  libkf5configgui5                    5.16.0-1
ii  libkf5configwidgets5                5.16.0-1
ii  libkf5coreaddons5                   5.16.0-1
ii  libkf5crash5                        5.16.0-1
ii  libkf5dbusaddons5                   5.16.0-1
ii  libkf5declarative5                  5.16.0-1
ii  libkf5globalaccel-bin               5.16.0-1
ii  libkf5globalaccel5                  5.16.0-1
ii  libkf5guiaddons5                    5.16.0-1
ii  libkf5i18n5                         5.16.0-1
ii  libkf5iconthemes5                   5.16.0-1
ii  libkf5idletime5                     5.16.0-1
ii  libkf5itemviews5                    5.16.0-1
ii  libkf5jobwidgets5                   5.16.0-1
ii  libkf5js5                           5.16.0-1
ii  libkf5jsembed5                      5.16.0-1
ii  libkf5kdelibs4support5              5.16.0-1
ii  libkf5kiocore5                      5.16.0-1
ii  libkf5kiofilewidgets5               5.16.0-1
ii  libkf5kiowidgets5                   5.16.0-1
ii  libkf5networkmanagerqt6             5.16.0-1
ii  libkf5newstuff5                     5.16.0-1
ii  libkf5notifications5                5.16.0-1
ii  libkf5notifyconfig5                 5.16.0-1
ii  libkf5package5                      5.16.0-1
ii  libkf5plasma5                       5.16.0-1
ii  libkf5plasmaquick5                  5.16.0-1
ii  libkf5quickaddons5                  5.16.0-1
ii  libkf5runner5                       5.16.0-1
ii  libkf5screen6                       4:5.4.3-1
ii  libkf5service-bin                   5.16.0-1
ii  libkf5service5                      5.16.0-1
ii  libkf5solid5                        5.16.0-1
ii  libkf5su5                           5.16.0-1
ii  libkf5texteditor5                   5.16.0-1
ii  libkf5textwidgets5                  5.16.0-1
ii  libkf5wallet-bin                    5.16.0-1
ii  libkf5wallet5                       5.16.0-1
ii  libkf5waylandclient5                4:5.4.3-1
ii  libkf5waylandserver5                4:5.4.3-1
ii  libkf5webkit5                       5.16.0-1
ii  libkf5widgetsaddons5                5.16.0-1
ii  libkf5windowsystem5                 5.16.0-1
ii  libkf5xmlgui5                       5.16.0-1
ii  libkf5xmlrpcclient5                 5.16.0-1
ii  libksgrd7                           4:5.4.3-1
ii  libkworkspace5-5                    4:5.4.3-1
ii  libpam0g                            1.1.8-3.1
ii  libphonon4qt5-4                     4:4.8.3-2
ii  libplasma-geolocation-interface5    4:5.4.3-1
ii  libprocesscore7                     4:5.4.3-1
ii  libprocessui7                       4:5.4.3-1
ii  libqalculate5v5                     0.9.7-9.1
ii  libqt5core5a                        5.5.1+dfsg-8
ii  libqt5dbus5                         5.5.1+dfsg-8
ii  libqt5gui5                          5.5.1+dfsg-8
ii  libqt5network5                      5.5.1+dfsg-8
ii  libqt5qml5                          5.5.1-3
ii  libqt5quick5                        5.5.1-3
ii  libqt5script5                       5.5.1+dfsg-2
ii  libqt5sql5                          5.5.1+dfsg-8
ii  libqt5webkit5                       5.5.1+dfsg-2
ii  libqt5widgets5                      5.5.1+dfsg-8
ii  libqt5x11extras5                    5.5.1-3
ii  libqt5xml5                          5.5.1+dfsg-8
ii  libsm6                              2:1.2.2-1+b1
ii  libstdc++6                          5.2.1-27
ii  libtaskmanager5                     4:5.4.3-1
ii  libwayland-client0                  1.9.0-1
ii  libwayland-server0                  1.9.0-1
ii  libweather-ion7                     4:5.4.3-1
ii  libx11-6                            2:1.6.3-1
ii  libxcb-keysyms1                     0.4.0-1
ii  libxcb1                             1.11.1-1
ii  libxfixes3                          1:5.0.1-2+b2
ii  libxi6                              2:1.7.5-1
ii  libxrender1                         1:0.9.9-2
ii  milou                               4:5.4.3-1
ii  phonon4qt5                          4:4.8.3-2
ii  plasma-framework                    5.16.0-1
ii  qdbus-qt5                           5.5.1-3
ii  qml-module-org-kde-extensionplugin  5.16.0-1
ii  qml-module-org-kde-kwindowsystem    5.16.0-1
ii  qml-module-qtgraphicaleffects       5.5.1-2
ii  qml-module-qtquick-controls         5.5.1-2
ii  qml-module-qtquick-dialogs          5.5.1-2
ii  qml-module-qtquick-layouts          5.5.1-2
ii  qml-module-qtquick-window2          5.5.1-3
ii  qml-module-qtquick2                 5.5.1-3
ii  qtdeclarative5-kf5declarative       5.16.0-1
ii  qtdeclarative5-kf5solid             5.16.0-1
ii  qttools5-dev-tools                  5.5.1-3
ii  udisks2                             2.1.6-2
ii  x11-utils                           7.7+3
ii  x11-xserver-utils                   7.7+5
ii  zlib1g                              1:1.2.8.dfsg-2+b1

Versions of packages plasma-workspace recommends:
ii  kio-extras       4:15.08.2-1
ii  libpam-kwallet5  5.4.3-1

plasma-workspace suggests no packages.

-- no debconf information

--- End Message ---
--- Begin Message --- 
Version: 4:5.8.4-1

Le mardi, 7 mars 2017, 13.33:25 h CET Maximiliano Curia a écrit :
> ¡Hola Didier!
> 
> El 2015-12-03 a las 20:24 +0100, Didier 'OdyX' Raboud escribió:
> > My usual laptop workflow implies moving from battery (using the laptop
> > screen)  to being docked with an additional DisplayPort screen (using the
> > two screens).
> > 
> > When suspending in the "laptop" setup and waking up in the "docked" setup,
> > the  screen "unlocker" usually appears only on the laptop screen. When
> > unlocking, the plasma desktop uses only the laptop screen. Launching
> > "kscreen" is enough for plasma to notify the two screens and use the two
> > screens again.
> > 
> > When suspending in the "docked" setup and waking up in the "laptop" setup,
> > the  situation is usually that the "unlocker" screen is not visible: the
> > desktop is visible, and the mouse can be moved, but no clicks can be
> > done, and it cannot be unlocked. The only workaround I have found is to
> > login in cli on tty1 as the same user and run "killall -9
> > kscreenlocker_greet".
> > 
> > My analysis is that "kscreenlocker_greet" is spawned once per physical
> > screen,  and this situation is not reevaluated on suspend/wakeup, leading
> > to a missing screen in "laptop-to-docked", and to an additional process
> > (unuseable) that needs to be killed manually in "docked-to-laptop".
> 
> Sorry for not getting back to you before. Multidisplay support has been a 
> gripe in KDE plasma for a while now, qt5 being partly at fault in some
> cases.  Some parts were supposed to be fixed in plasma 5.7 [1], could you
> test if the bug is still reproducible with the version of plasma-workspace
> that's currently in stretch?

I just did. Some things are still weird (like where the mouse focus is, and 
which password field has focus, etc), but at least it moves flawlessly between 
one and two screens.

I'm hereby closing this bug, thank you for having taken the time to address 
this bug!

-- 
    OdyX

Attachment: signature.asc
Description: This is a digitally signed message part.


--- End Message ---
Reply to: