Am 23.03.2016 um 12:25 schrieb Gerald B. Cox:

On Wed, Mar 23, 2016 at 2:29 AM, Reindl Harald <h.reindl@thelounge.net mailto:h.reindl@thelounge.net> wrote:

after this mornings update *nothing* works

* no desktop
* no systray
* no widgets
* no controlbar
* the only icon is the menu-icon which became "logout"
* well, and downgrade is tricky too - what a crap

Harald, the only issue I had was that the desktop background went back to default. I was able to quickly change it back. Might have been due to something in your particular environment not getting set or cleared out correctly - which has happened to me in the past and required that I go in and clear .cache, .config, etc.

*for sure* i won't go and clear .config since i have other tasks to do then re-configure my workplace all few months and before that is going to happen i switch away from KDE based desktops

Am 23.03.2016 um 12:37 schrieb Gerald B. Cox:

On Wed, Mar 23, 2016 at 4:28 AM, Reindl Harald <h.reindl@thelounge.net mailto:h.reindl@thelounge.net> wrote:

    Harald, the only issue I had was that the desktop background
    went back
    to default.  I was able to quickly change it back.  Might have
    been due
    to something in your particular environment not getting set or
    cleared
    out correctly - which has happened to me in the past and
    required that I
    go in and clear .cache, .config, etc.

*for sure* i won't go and clear .config since i have other tasks to
do then re-configure my workplace all few months and before that is
going to happen i switch away from KDE based desktops

Completely understand... it's a hassle... and I'm not saying that is what definitely happened in your particular case, but it has happened to me occasionally in the past; and since I had the glitch with my desktop background I'm guessing something got changed/migrated during the upgrade

KDE upstream should just stop remove, rename and move things all the time around when with every update things are broken (like not so long ago favorites in the menu) and the whole settings over the time become a mess

smart developers should overthink changes which may look like optimize things and consider the impact on the userbase - all the regeressions i have seen from Fedora 22 until now must not have happened at all if developers would understand their *resposibility* until they don't declare that their project is not just for own use and no longer directed to users

other projects manage updates without such a mess over years and decades, i manage the same for hundrets of customers for 13 years now and have *zero understaing* for what's going on in the KDE / KF / Plasma or whatever name you should call whatever piece currently

On Wednesday, March 23, 2016 11:40:56 AM WET Rex Dieter wrote:

For what it's worth, I did similar upgrade on f24 and f23 boxes, and did not experience the problem you describe.

I also did not had any problems on f24 with these updates.

Am 23.03.2016 um 19:31 schrieb Mustafa Muhammad:

I don't have these issues too, F23 and F24. Can you try with a new test user

no - i need my account with all it's passwords, configurations, kyes and customizations working which where hard enough to keep and restore by the switch to Fedora 22

starting with a empty userhome is always easy but not the way a unix desktop have to work - i switched away from windows to not always reinstall and reconfigure my machines

Filesystem volume name: system Last mounted on: / Filesystem created: Wed Jun 8 13:10:52 2011

and also try 'setenforce 0'

there is no selinux enabled on any of my machines

Am 23.03.2016 um 17:40 schrieb Rex Dieter:

Reindl Harald wrote:

...

after this mornings update *nothing* works

• no desktop
• no systray
• no widgets
• no controlbar
• the only icon is the menu-icon which became "logout"
• well, and downgrade is tricky too - what a crap

:(

For what it's worth, I did similar upgrade on f24 and f23 boxes, and did not experience the problem you describe.

Perhaps, it may be worthwhile to try updating qt5 only first, and then if ok, then the rest of kf5, to see if we can get closer to pinpointing the source of your issue(s). (That's what I did)

smells like qt is the root cause

at least after the transaction below controlbar and systray are missing and the kmenu changed it's function to "logout" which was one of the issues, but without update the kf5 packages at least my desktop and widgets are there

removed "qt5-qtwebchannel" with "rpm -e --nodeps" and downgraded the others

maybe caused (partly) by my autostarts while i am not really willing to test that finally out - maybe i give the other updates witout qt a chance, here it is 2:45 AM....

* firefox * kopete * kmix * ssh-add

Mar 24 02:26:58 INFO Upgraded: qt5-qtbase-common-5.6.0-7.fc23.noarch Mar 24 02:26:59 INFO Upgraded: qt5-qtbase-5.6.0-7.fc23.x86_64 Mar 24 02:27:00 INFO Upgraded: qt5-qtbase-gui-5.6.0-7.fc23.x86_64 Mar 24 02:27:00 INFO Upgraded: qt5-qttools-common-5.6.0-3.fc23.noarch Mar 24 02:27:00 INFO Upgraded: qt5-qtxmlpatterns-5.6.0-4.fc23.x86_64 Mar 24 02:27:01 INFO Upgraded: qt5-qtdeclarative-5.6.0-3.fc23.x86_64 Mar 24 02:27:01 INFO Installed: qt5-qtwebchannel-5.6.0-3.fc23.x86_64 Mar 24 02:27:01 INFO Upgraded: qt5-qtsensors-5.6.0-3.fc23.x86_64 Mar 24 02:27:01 INFO Upgraded: qt5-qtlocation-5.6.0-3.fc23.x86_64 Mar 24 02:27:03 INFO Upgraded: qt5-qtwebkit-5.6.0-3.fc23.x86_64 Mar 24 02:27:03 INFO Upgraded: qt5-qtquickcontrols-5.6.0-3.fc23.x86_64 Mar 24 02:27:03 INFO Upgraded: qt5-qtmultimedia-5.6.0-3.fc23.x86_64 Mar 24 02:27:03 INFO Upgraded: qt5-qtgraphicaleffects-5.6.0-3.fc23.x86_64 Mar 24 02:27:04 INFO Upgraded: qt5-qttools-5.6.0-3.fc23.x86_64 Mar 24 02:27:04 INFO Upgraded: qt5-qttools-libs-designer-5.6.0-3.fc23.x86_64 Mar 24 02:27:04 INFO Upgraded: qt5-qtx11extras-5.6.0-3.fc23.x86_64 Mar 24 02:27:04 INFO Upgraded: qt5-qtsvg-5.6.0-3.fc23.x86_64 Mar 24 02:27:04 INFO Upgraded: qt5-qtscript-5.6.0-3.fc23.x86_64

gave it another try after face some changes with kf5-activities in packaging but still unuseable

something is wrong with widgets - gave the update another try, nearly same problems (no taskbar, nosystray) but widgets not missing completly

what i realized is that currently the systemload widget (screenshot) appears another two times on the bottom (only the top of it and also swap space column visible which i disabled by intention) - see screenshot to make sure you know what widget i mean

something stinks here and i am not sure if it's the widgets, widgets combined with a few autostarts, however - until now these updates don't belong in the stable repos in the current shape

since QT5.6 alone starts to break most of my desktop it would be *really* a good idea to publish such updates in two steps

* first only KF5/KDE packages * after enough feedback from users rebuild with QT5.6 * problem is that QT5.6 alone bearks enough stuff * problem is i can't nstall the KDE updates without update to QT5.6 * that's terrible for feedback / testing

Am 24.03.2016 um 02:45 schrieb Reindl Harald:

no chance - "dnf update kf5*" pulls qt-5.6 and i know the result...

Am 24.03.2016 um 02:43 schrieb Reindl Harald:

...

Am 23.03.2016 um 17:40 schrieb Rex Dieter:

...

Reindl Harald wrote:

...

after this mornings update *nothing* works

• no desktop
• no systray
• no widgets
• no controlbar
• the only icon is the menu-icon which became "logout"
• well, and downgrade is tricky too - what a crap

:(

For what it's worth, I did similar upgrade on f24 and f23 boxes, and did not experience the problem you describe.

Perhaps, it may be worthwhile to try updating qt5 only first, and then if ok, then the rest of kf5, to see if we can get closer to pinpointing the source of your issue(s). (That's what I did)

smells like qt is the root cause

at least after the transaction below controlbar and systray are missing and the kmenu changed it's function to "logout" which was one of the issues, but without update the kf5 packages at least my desktop and widgets are there

removed "qt5-qtwebchannel" with "rpm -e --nodeps" and downgraded the others

maybe caused (partly) by my autostarts while i am not really willing to test that finally out - maybe i give the other updates witout qt a chance, here it is 2:45 AM....

• firefox
• kopete
• kmix
• ssh-add

Mar 24 02:26:58 INFO Upgraded: qt5-qtbase-common-5.6.0-7.fc23.noarch Mar 24 02:26:59 INFO Upgraded: qt5-qtbase-5.6.0-7.fc23.x86_64 Mar 24 02:27:00 INFO Upgraded: qt5-qtbase-gui-5.6.0-7.fc23.x86_64 Mar 24 02:27:00 INFO Upgraded: qt5-qttools-common-5.6.0-3.fc23.noarch Mar 24 02:27:00 INFO Upgraded: qt5-qtxmlpatterns-5.6.0-4.fc23.x86_64 Mar 24 02:27:01 INFO Upgraded: qt5-qtdeclarative-5.6.0-3.fc23.x86_64 Mar 24 02:27:01 INFO Installed: qt5-qtwebchannel-5.6.0-3.fc23.x86_64 Mar 24 02:27:01 INFO Upgraded: qt5-qtsensors-5.6.0-3.fc23.x86_64 Mar 24 02:27:01 INFO Upgraded: qt5-qtlocation-5.6.0-3.fc23.x86_64 Mar 24 02:27:03 INFO Upgraded: qt5-qtwebkit-5.6.0-3.fc23.x86_64 Mar 24 02:27:03 INFO Upgraded: qt5-qtquickcontrols-5.6.0-3.fc23.x86_64 Mar 24 02:27:03 INFO Upgraded: qt5-qtmultimedia-5.6.0-3.fc23.x86_64 Mar 24 02:27:03 INFO Upgraded: qt5-qtgraphicaleffects-5.6.0-3.fc23.x86_64 Mar 24 02:27:04 INFO Upgraded: qt5-qttools-5.6.0-3.fc23.x86_64 Mar 24 02:27:04 INFO Upgraded: qt5-qttools-libs-designer-5.6.0-3.fc23.x86_64 Mar 24 02:27:04 INFO Upgraded: qt5-qtx11extras-5.6.0-3.fc23.x86_64 Mar 24 02:27:04 INFO Upgraded: qt5-qtsvg-5.6.0-3.fc23.x86_64 Mar 24 02:27:04 INFO Upgraded: qt5-qtscript-5.6.0-3.fc23.x86_64

Am 28.03.2016 um 14:01 schrieb Rex Dieter:

Reindl Harald wrote:

...

something stinks here and i am not sure if it's the widgets, widgets combined with a few autostarts, however - until now these updates don't belong in the stable repos in the current shape

So far, the vast majority of feedback we've received has been positive.

I still think we need at least 2 things to seriously consider holding things up:

1. File a bug (if there is one already, can you give a reference?)

if i only knew what to write there, it don't work, it breaks my profile, it's in fact broken for me - other users profiles or a empty profile won't help me much

2. More debugging. Several folks have asked for some basic things like:

• try a blank/empty profile (ie, a new user), are problems reproducible for

you there?

it's pretty clear when it works for other users whith their profile that it will work with a clear profile too

In short, we need a bug to document your problem, and then ideally details on how to reproducibly test/debug what's going on.

how should a narrow something down with 30 and more wupdates wired together?

...

since QT5.6 alone starts to break most of my desktop it would be *really* a good idea to publish such updates in two steps

qt-5.6 is the more important piece here, I suppose we could resort to doing it the way you suggest, but it would also mean resetting *all* of KF5 testing:

• rebuild entire KF5 stack of packages against Qt 5.5.x instead
• resubmit to bodhi

too late now - it should had happened in two steps from the very begin instead throw *two major* updates at the same time in the mix

Reindl Harald wrote:

...

I still think we need at least 2 things to seriously consider holding things up:

1. File a bug (if there is one already, can you give a reference?)

if i only knew what to write there, it don't work, it breaks my profile, it's in fact broken for me - other users profiles or a empty profile won't help me much

We need it documented formally, else we cannot consider blocking qt-5.6.x indefinitely. Please file a bug.

...

imo, qt-5.6 is the more important piece here, I suppose we could do it the way you suggest, but it would also mean resetting *all* of KF5 testing:

• rebuild entire KF5 stack of packages against Qt 5.5.x instead
• resubmit to bodhi

too late now - it should had happened in two steps from the very begin instead throw *two major* updates at the same time in the mix

After our kde-sig meeting this morning, this is our tentative plan moving forward. Sometime later this week (or weekend), dvratil will work on rebuilding kf5-5.20 without dependencies on qt-5.6.x, so we can consider pushing that to stable repos first.

The result will be that qt-5.6.x will stay in -testing awhile longer (as of now, it's only been 8 days, so another ~week or so is probably not a bad idea).

-- Rex

On 03/30/16 04:49, Rex Dieter wrote:

After our kde-sig meeting this morning, this is our tentative plan moving forward. Sometime later this week (or weekend), dvratil will work on rebuilding kf5-5.20 without dependencies on qt-5.6.x, so we can consider pushing that to stable repos first.

The result will be that qt-5.6.x will stay in -testing awhile longer (as of now, it's only been 8 days, so another ~week or so is probably not a bad idea).

FWIW, I just now fully updated an F23 system with updates-testing enabled. Everything is where it should be. Granted, this particular system/user is a simple test system with minimal tweaks.

Am 30.03.2016 um 14:04 schrieb Gilboa Davara:

On Wed, Mar 30, 2016 at 12:24 AM, Ed Greshko ed.greshko@greshko.com wrote:

...

On 03/30/16 04:49, Rex Dieter wrote:

...

After our kde-sig meeting this morning, this is our tentative plan moving forward. Sometime later this week (or weekend), dvratil will work on rebuilding kf5-5.20 without dependencies on qt-5.6.x, so we can consider pushing that to stable repos first.

The result will be that qt-5.6.x will stay in -testing awhile longer (as of now, it's only been 8 days, so another ~week or so is probably not a bad idea).

FWIW, I just now fully updated an F23 system with updates-testing enabled. Everything is where it should be. Granted, this particular system/user is a simple test system with minimal tweaks.

Idiotic question 101: Has QT5.6 / P5.6 / KF5.20 landed in kde-unstable or fedora-updates-testing?

fedora-updates-testing

On Wed, Mar 30, 2016 at 3:06 PM, Rex Dieter rdieter@math.unl.edu wrote:

Gilboa Davara wrote:

...

Idiotic question 101: Has QT5.6 / P5.6 / KF5.20 landed in kde-unstable or fedora-updates-testing?

updates-testing:

qt-5.6: https://bodhi.fedoraproject.org/updates/FEDORA-2016-8d0a47cde6

kf5-5.20: https://bodhi.fedoraproject.org/updates/FEDORA-2016-5d2823c643

-- Rex _______________________________________________ kde mailing list kde@lists.fedoraproject.org http://lists.fedoraproject.org/admin/lists/kde@lists.fedoraproject.org

Thanks Rex / Reindl.

- Gilboa

On Thu, Mar 31, 2016 at 10:15 AM, Gilboa Davara gilboad@gmail.com wrote:

On Thu, Mar 31, 2016 at 8:26 AM, Gilboa Davara gilboad@gmail.com wrote:

...

On Wed, Mar 30, 2016 at 3:06 PM, Rex Dieter rdieter@math.unl.edu wrote:

...

Gilboa Davara wrote:

...

Idiotic question 101: Has QT5.6 / P5.6 / KF5.20 landed in kde-unstable or fedora-updates-testing?

updates-testing:

qt-5.6: https://bodhi.fedoraproject.org/updates/FEDORA-2016-8d0a47cde6

kf5-5.20: https://bodhi.fedoraproject.org/updates/FEDORA-2016-5d2823c643

-- Rex _______________________________________________ kde mailing list kde@lists.fedoraproject.org http://lists.fedoraproject.org/admin/lists/kde@lists.fedoraproject.org

Thanks Rex / Reindl.

• Gilboa

I hitting the same issues Reindl Harald met. Post KF 5.20, plasmashell completely broken (lost previous configuration + "start" menu triggers "logout" whenever pressed). More-ever, when I start, my dual screen configuration default to 1680x1050 in clone mode (previously: side by side, 2560x1440 + 1920x1080). Last an no leaser, even after the previous configuration was deleted, I can no longer control my activities, trying to load the activity screen send a "module "org.kde.activities.settings" is not installed" to the console.

Before I revert back to last-good-known, anything worth reporting up/downstream?

• Gilboa

Just for the heck of it I completely cleared .config and .local. No help. Activities still broken, display still starts at clone 1680x1050 instead of full-resolution side by side with resolution change not surviving logout-login. More-ever, plasma and konsole configuration changes do not survive login-logout as well. In short, KF5.20 + Qt 5.6 is completely broken - at least on my setup.

Any chance of building a Qt5.5 based KF 5.20?

- Gilboa

Am 31.03.2016 um 10:13 schrieb Reindl Harald:

...

I hitting the same issues Reindl Harald met. Post KF 5.20, plasmashell completely broken (lost previous configuration + "start" menu triggers "logout" whenever pressed). More-ever, when I start, my dual screen configuration default to 1680x1050 in clone mode (previously: side by side, 2560x1440 + 1920x1080). Last an no leaser, even after the previous configuration was deleted, I can no longer control my activities, trying to load the activity screen send a "module "org.kde.activities.settings" is not installed" to the console

thanks god i am not the only one makes it more likely get fixed and hold back the update

Plasma 5.6.1 was released today - maybe it will play better with QT5.6 anyways: https://bugzilla.redhat.com/show_bug.cgi?id=1322334

On Thu, Mar 31, 2016 at 2:37 PM, Gilboa Davara gilboad@gmail.com wrote:

On Thu, Mar 31, 2016 at 12:36 PM, Reindl Harald h.reindl@thelounge.net wrote:

...

Am 31.03.2016 um 10:13 schrieb Reindl Harald:

...

...

I hitting the same issues Reindl Harald met. Post KF 5.20, plasmashell completely broken (lost previous configuration + "start" menu triggers "logout" whenever pressed). More-ever, when I start, my dual screen configuration default to 1680x1050 in clone mode (previously: side by side, 2560x1440 + 1920x1080). Last an no leaser, even after the previous configuration was deleted, I can no longer control my activities, trying to load the activity screen send a "module "org.kde.activities.settings" is not installed" to the console

thanks god i am not the only one makes it more likely get fixed and hold back the update

Plasma 5.6.1 was released today - maybe it will play better with QT5.6 anyways: https://bugzilla.redhat.com/show_bug.cgi?id=1322334

Adding myself to the CC list. Thanks.

• Gilboa

Yet another two weird issues: 1. kwin decoration no longer use the KDE color theme. Breeze is always bright blue, oxygen is always off-white. 2. plasma completely lost all transparency effects (OpenGL is working as intended, kwin configured to use OpenGL 3.1).

- Gilboa

Gilboa Davara wrote:

3. Any chance all these issues has something to do with:

https://mail.kde.org/pipermail/kde-distro-packagers/2016-March/000138.html

No, we applied the important Qt-5.6.x early on, as soon as they were available (since qt5-qtbase-5.6.0-2 build)

-- Rex

On Fri, Apr 1, 2016 at 10:54 PM, Gilboa Davara gilboad@gmail.com wrote:

I would advise against pushing KF 5.20 and Qt 5.6 to stable. Granted, two bug reports are not much, but given the scale of the breakage (plasma, activities, randr), those who will be unlucky enough to hit the issues both Reindl and I experienced, will have a completely broken KDE desktop, with no fix or way to circumvent these issues.

I got a little confused reading through your updates... are you saying that from an empty account you are still having issues?

Gilboa Davara wrote:

2. Activity manage seem to die due to XCB issues:

$ kactivitymanagerd status The service is running, version: 6.5.0 QXcbConnection: XCB error: 3 (BadWindow), sequence: 13940, resource id: 35651588, major code: 18 (ChangeProperty), minor code: 0

$ kactivitymanagerd status The service is running, version: 6.5.0

Seems to work ok for me, but... plasma menu (or right click desktop) => ... Activities does nothing.

I think we may be on to something here.

Can anyone else report success or failure with activity related actions with these updates ?

-- Rex

On Sunday 03 Apr 2016 08:52:09 Rex Dieter wrote:

$ kactivitymanagerd status The service is running, version: 6.5.0

Seems to work ok for me, but... plasma menu (or right click desktop) => ... Activities does nothing.

I think we may be on to something here.

Can anyone else report success or failure with activity related actions with these updates ?

Not totally the same updates but FYI running P-5.5.95 and everything above works as it should.

Of note.. it seems to me the OP's with the problems run dual monitors or some third party widgets maybe?

Colin

Rex Dieter wrote:

Gilboa Davara wrote:

...

2. Activity manage seem to die due to XCB issues:

$ kactivitymanagerd status The service is running, version: 6.5.0 QXcbConnection: XCB error: 3 (BadWindow), sequence: 13940, resource id: 35651588, major code: 18 (ChangeProperty), minor code: 0

$ kactivitymanagerd status The service is running, version: 6.5.0

Seems to work ok for me, but... plasma menu (or right click desktop) => ... Activities does nothing.

I think we may be on to something here.

OK, seems we'd missed packaging kactivities-workspace component properly with kf5-5.20, which should now be fixed (as a subpackage) in kactvitymanager-5.5.0-2 build. This is now added to f23 : https://bodhi.fedoraproject.org/updates/FEDORA-2016-5d2823c643 and submitted separately f24: https://bodhi.fedoraproject.org/updates/FEDORA-2016-f54b57ce60

-- Rex

On Sun, Apr 3, 2016 at 7:42 PM, Rex Dieter rdieter@math.unl.edu wrote:

Rex Dieter wrote:

...

Gilboa Davara wrote:

...

2. Activity manage seem to die due to XCB issues:

$ kactivitymanagerd status The service is running, version: 6.5.0 QXcbConnection: XCB error: 3 (BadWindow), sequence: 13940, resource id: 35651588, major code: 18 (ChangeProperty), minor code: 0

$ kactivitymanagerd status The service is running, version: 6.5.0

Seems to work ok for me, but... plasma menu (or right click desktop) => ... Activities does nothing.

I think we may be on to something here.

OK, seems we'd missed packaging kactivities-workspace component properly with kf5-5.20, which should now be fixed (as a subpackage) in kactvitymanager-5.5.0-2 build. This is now added to f23 : https://bodhi.fedoraproject.org/updates/FEDORA-2016-5d2823c643 and submitted separately f24: https://bodhi.fedoraproject.org/updates/FEDORA-2016-f54b57ce60

Thanks. Has it landed in updates-testing?

- Gilboa

On Mon, Apr 4, 2016 at 11:24 AM, Reindl Harald h.reindl@thelounge.net wrote:

Am 04.04.2016 um 08:11 schrieb Gilboa Davara:

...

On Sun, Apr 3, 2016 at 7:42 PM, Rex Dieter <rdieter@math.unl.edu OK, seems we'd missed packaging kactivities-workspace component properly with kf5-5.20, which should now be fixed (as a subpackage) in kactvitymanager-5.5.0-2 build. This is now added to f23 : https://bodhi.fedoraproject.org/updates/FEDORA-2016-5d2823c643 and submitted separately f24: https://bodhi.fedoraproject.org/updates/FEDORA-2016-f54b57ce60

Has it landed in updates-testing?

that's not a question to anser with yes/no because even if it is pushed you never know what mirror you hit - just type "dnf --enablerepo=updates-testing upgrade" and look at the outputs

Reindl,

Miss-wording on my end. I meant: Was it *pushed* to updates-testing?

- Gilboa

On Mon, Apr 4, 2016 at 5:04 PM, Gerald B. Cox gbcox@bzb.us wrote:

On Mon, Apr 4, 2016 at 1:53 AM, Gilboa Davara gilboad@gmail.com wrote:

...

I meant: Was it *pushed* to updates-testing?

It sometimes takes days for it to show up. If you don't want to wait, just download directly from koji and then: dnf upgrade kactivitymanagerd-5.5.0-2.fc23.x86_64.rpm kactivities-workspace-5.5.0-2.fc23.x86_64.rpm

That is what I did...

Thanks. Switched back to Kf 5.20, manually pulled kactivitymanagerd and kactivities-workspace from koji.

Good: * Activities work. Yippie! * Plasma works (see below).

Bad: * Dual screen resolution(s) is still broken. Upon login dual switch always drops to clone / 1680x1050, breaking the plasma widget configuration. * Show desktop widget is broken. Kills plasma (E.g. if placed on the panel, all the icons on the panel behave as if "logout" is pressed, removing it solves the problem).

- Gilboa

On Tue, Apr 5, 2016 at 2:04 AM, Gilboa Davara gilboad@gmail.com wrote:

• Dual screen resolution(s) is still broken. Upon login dual switch

always drops to clone / 1680x1050, breaking the plasma widget configuration.

• Show desktop widget is broken. Kills plasma (E.g. if placed on the

panel, all the icons on the panel behave as if "logout" is pressed, removing it solves the problem).

I don't have dual displays, so couldn't test that. I did try the desktop widget (which I normally don't use) and it appeared to work as advertised. No issues for me. Would be curious to see if someone else with dual displays could test. Maybe there is a problem with that...