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

            Bug ID: 466691
           Summary: Icons-only Task Manager - Sort Manual - Order of
                    windows lost after x11vnc remote connection
    Classification: Plasma
           Product: plasmashell
           Version: 5.27.2
          Platform: Other
                OS: Linux
            Status: REPORTED
          Severity: normal
          Priority: NOR
         Component: Task Manager and Icons-Only Task Manager
          Assignee: plasma-b...@kde.org
          Reporter: mjevans1...@gmail.com
  Target Milestone: 1.0

Sort: Manual
Order of windows lost after x11vnc remote connection

STEPS TO REPRODUCE

1. Have multiple Firefox sessions, terminals, other programs, etc open.
(Typical workspace?)
2. Icons-only Task Manager > Behavior > Sort: Manual
3. Carefully sort the windows into a user-desired manual order.
4. Remote connect with x11vnc
5. Sign back in at the physical terminal.
6. Windows are now no longer in the user specified order.

Notably it looks roughly like the order of Firefox session windows is reversed
(I have a lot of them), as well as combined together (they're not allowed to be
grouped but now they are). A mix of windows that were after (to the right) as
well as before (to the left) of Firefox's session windows are now all to the
right, with only Dolphin to the left of Firefox's set of windows.

Steam's set of windows (2) didn't get reversed, but they might not be a group
candidate.  Firefox's would be if grouping weren't banned for that program, and
those windows appear to now be in reverse order.  Overall all of the programs
are now in a seemingly random order across the task bar (but still grouped left
to right by program).  I've had this issue for about a week and at least two
different ArchLinux KDE updates have had the issue (I wanted to wait to see if
it was fixed since it seemed likely a new update might resolve the issue).

This was working 'recently' though I don't know what version of KDE Plasma
workspace I was using on Arch Linux prior to the more recent updates.  This
regression may have been introduced somewhere between 5.26.x and 5.27.x.

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

Reply via email to