Registered Member
|
My panels will not stay on the screens they have been created for. When I log out and back in the two panels I have (one for each screen) usually end up piled on top of each other on one screen. When I try to move one of them back it will not cross over to the other screen so I end up deleting it and creating a new panel. Often when I create a new panel it does not show up until I log out and back in again and it seems there is a only 50/50 chance that it will be where I want it. I have actually seen it appear on the correct screen momentarily and then jump to the other screen! I have also had the panels move after opening from a screen lock. I recently upgraded from two monitors that were different sizes/models to a two identical monitors connected to the same AMD FirePro W2100 controller which is also new.
I am really at a loss as to where to look for the issue. Any hints will be most appreciated. I am running fedora 23 and applied the latest updates just today: kf5-kdoctools-5.19.0-1.fc23.x86_64 kf5-kpackage-5.19.0-1.fc23.x86_64 kf5-threadweaver-5.19.0-1.fc23.x86_64 kf5-solid-libs-5.19.0-1.fc23.x86_64 kf5-kio-widgets-5.19.0-1.fc23.x86_64 kf5-kdelibs4support-libs-5.19.0-1.fc23.x86_64 kf5-kemoticons-5.19.0-1.fc23.x86_64 kf5-kfilemetadata-5.19.0-1.fc23.x86_64 kf5-kdbusaddons-5.19.0-1.fc23.x86_64 kf5-kded-5.19.0-1.fc23.x86_64 kf5-kidletime-5.19.0-1.fc23.x86_64 kf5-knotifyconfig-5.19.0-1.fc23.x86_64 kf5-ki18n-5.19.0-1.fc23.x86_64 kf5-kauth-5.19.0-1.fc23.x86_64 kf5-baloo-libs-5.19.0-1.fc23.x86_64 kf5-kdeclarative-5.19.0-2.fc23.x86_64 kf5-ktexteditor-5.19.0-1.fc23.x86_64 kf5-kwindowsystem-5.19.0-1.fc23.x86_64 kf5-kio-core-libs-5.19.0-1.fc23.x86_64 kf5-kactivities-libs-5.19.0-1.fc23.x86_64 kf5-kdesu-5.19.0-1.fc23.x86_64 kf5-modemmanager-qt-5.19.0-1.fc23.x86_64 kf5-karchive-5.19.0-1.fc23.x86_64 kf5-kunitconversion-5.19.0-1.fc23.x86_64 kf5-kjobwidgets-5.19.0-1.fc23.x86_64 kf5-kservice-5.19.0-1.fc23.x86_64 kf5-kwallet-libs-5.19.0-1.fc23.x86_64 kf5-kglobalaccel-5.19.0-1.fc23.x86_64 kf5-kactivities-5.19.0-1.fc23.x86_64 kf5-kross-core-5.19.0-1.fc23.x86_64 kf5-knewstuff-5.19.0-1.fc23.x86_64 kf5-bluez-qt-5.19.0-1.fc23.x86_64 kf5-kjs-5.19.0-1.fc23.x86_64 kf5-kio-ntlm-5.19.0-1.fc23.x86_64 kf5-solid-5.19.0-1.fc23.x86_64 kf5-kconfigwidgets-5.19.0-1.fc23.x86_64 kf5-kio-core-5.19.0-1.fc23.x86_64 kf5-kbookmarks-5.19.0-1.fc23.x86_64 kf5-kdelibs4support-5.19.0-1.fc23.x86_64 kf5-kwayland-5.5.4-1.fc23.x86_64 kf5-khtml-5.19.0-1.fc23.x86_64 kf5-kpeople-5.19.0-1.fc23.x86_64 kf5-filesystem-5.19.0-1.fc23.x86_64 kf5-attica-5.19.0-1.fc23.x86_64 kf5-kpty-5.19.0-1.fc23.x86_64 kf5-kitemviews-5.19.0-1.fc23.x86_64 kf5-kguiaddons-5.19.0-1.fc23.x86_64 kf5-kio-widgets-libs-5.19.0-1.fc23.x86_64 kf5-kxmlgui-5.19.0-1.fc23.x86_64 kf5-plasma-5.19.0-2.fc23.x86_64 kf5-baloo-file-5.19.0-1.fc23.x86_64 kf5-kxmlrpcclient-5.19.0-1.fc23.x86_64 kf5-kitemmodels-5.19.0-1.fc23.x86_64 kf5-kconfig-core-5.19.0-1.fc23.x86_64 kf5-sonnet-core-5.19.0-1.fc23.x86_64 kf5-kconfig-gui-5.19.0-1.fc23.x86_64 kf5-sonnet-ui-5.19.0-1.fc23.x86_64 kf5-ktextwidgets-5.19.0-1.fc23.x86_64 kf5-baloo-5.19.0-1.fc23.x86_64 kf5-kparts-5.19.0-1.fc23.x86_64 kf5-frameworkintegration-5.19.0-1.fc23.x86_64 kf5-kcoreaddons-5.19.0-1.fc23.x86_64 kf5-kwidgetsaddons-5.19.0-1.fc23.x86_64 kf5-kiconthemes-5.19.0-1.fc23.x86_64 kf5-kio-file-widgets-5.19.0-1.fc23.x86_64 kf5-krunner-5.19.0-1.fc23.x86_64 kf5-networkmanager-qt-5.19.0-1.fc23.x86_64 kf5-kcodecs-5.19.0-1.fc23.x86_64 kf5-kcompletion-5.19.0-1.fc23.x86_64 kf5-kwallet-5.19.0-1.fc23.x86_64 kf5-kcmutils-5.19.0-1.fc23.x86_64 kf5-kross-ui-5.19.0-1.fc23.x86_64 kf5-kdnssd-5.19.0-1.fc23.x86_64 kf5-kcrash-5.19.0-1.fc23.x86_64 kf5-kinit-5.19.0-1.fc23.x86_64 kf5-frameworkintegration-libs-5.19.0-1.fc23.x86_64 kf5-kjsembed-5.19.0-1.fc23.x86_64 kf5-knotifications-5.19.0-1.fc23.x86_64 kf5-kglobalaccel-libs-5.19.0-1.fc23.x86_64 |
Administrator
|
Are you using a permanent (e.g. fixed) or "mobile" (e.g., laptop and external monitor) setup? I can't reproduce this issue since a few months on my openSUSE system.
"Violence is the last refuge of the incompetent."
Plasma FAQ maintainer - Plasma programming with Python |
Registered Member
|
This is a permanent fixed set of Dell P2415Q monitors.
Terry |
Administrator
|
What is the version of Qt that you are using?
"Violence is the last refuge of the incompetent."
Plasma FAQ maintainer - Plasma programming with Python |
Registered Member
|
Here is what I found:
$ qtpaths --qt-version 5.5.1 $ qtpaths --paths ConfigLocation /home/tkovacs/.config:/etc/xdg:/usr/share/kde-settings/kde-profile/default/xdg $ qtpaths --paths GenericDataLocation /home/tkovacs/.local/share:/usr/share/kde-settings/kde-profile/default/share:/usr/local/share:/usr/share $ qtpaths --binaries-dir /usr/lib64/qt5/bin $ qtpaths --plugin-dir /usr/lib64/qt5/plugins |
Registered Member
|
This was driving me batty until I realized that powering the screens off instigated the problem. Turning off all screen functions under Power Management means that I can lock my session and leave for five minutes without needing to repair panel positions after I unlock. Now I would really like to fix the root cause as having the screens blank when the session is idle is a really nice feature. Having been in the linux/unix biz for 30 years I have some debugging skills but I am at a loss as to where to begin with this problem. Any advice would be helpful.
Thanks |
Registered Member
|
I can report that this seems to be less of an issue. I am uncertain which of the updates over the past few months fixed my issues but they may be completely gone now.
|
Registered users: Bing [Bot], Google [Bot], q.ignora, watchstar