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

            Bug ID: 389141
           Summary: plasmoids won't stay put after monitors off for a few
                    hours (live-git regression I believe only a few days
                    old)
           Product: plasmashell
           Version: master
          Platform: Gentoo Packages
                OS: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: NOR
         Component: Desktop Containment
          Assignee: se...@kde.org
          Reporter: 1i5t5.dun...@cox.net
                CC: plasma-b...@kde.org
  Target Milestone: 1.0

Live-git of frameworks/apps/plasma (tho not kdelibs4, still around to run
superkaramba since there's no known non-coder plasma5 alternative to it and
I've not had time to test and configure a non-kde alternative), built from the
gentoo/kde overlay live-build ebuilds.

I frequently sleep with a multi-hour rain video playing, turning off the
monitors.

A couple days ago I did that, and when I turned the monitors on when I woke up,
the plasmoids had repositioned themselves, with two (of three) on top of each
other in the center of the monitor, and one centered vertically but hard-left.

Just shutting the monitors off for a couple minutes doesn't seem to duplicate
the issue, but I had it happen again last nite (monitors off but no video
playing this time, to see if it would trigger again), so it seems duplicable if
I leave the monitors off for long enough... over nite or so.

I do have two monitors and the plasmoids did stay on the correct one, just
repositioned from where they were supposed to be.  I only have the one
activity, however, so don't know if it would have affected other activities. 
The single configured panel appears unaffected.

The frustrating thing is that despite my having widgets locked, restarting
plasmashell left them repositioned, so their new location is being written to
what /was/ the working just fine rc file, and I have to manually unlock widgets
to reposition them back where they belong.

This is, unfortunately, giving me flashbacks to plasma4 bug 321781 (filed
against the beta where it first appeared and should have been easy to trace,
unfortunately without dev comment until far later when it was far harder to
trace, so never fixed, hopefully this one fairs better), which I ended up
coping with by setting the affected config files read-only so they wouldn't be
overwritten and I could restart plasma-desktop, now plasmashell, and get my
setting sback.


I'm going to try to bisect this one, but may end up trying the same read-only
config file and restarting plasmashell trick.  (I already have a hotkey for
it... along with others to restart kwin, krunner, sni-proxy, etc.  A bit like
replacing critical parts of a plane in mid-air, but I must say it works
surprisingly well most of the time!)

I can try uninstalling kscreen as well.  I've had problems with it screwing up
my perfectly satisfactory xorg.conf configuration in the past and had it
uninstalled for awhile to prevent that, but it's installed again now, and
things had been fine for months until this bug showed up, apparently within the
last week or so.

More information to follow once I try bisecting and/or without kscreen, but I
decided I better file this now, or I might not end up filing it at all.

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

Reply via email to