Bug 31775 - KDE not regrouping programs in the task bar as it was doing before
Summary: KDE not regrouping programs in the task bar as it was doing before
Status: RESOLVED OLD
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 8
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: KDE maintainers
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-04-07 12:11 CEST by Jean-François Bachelet
Modified: 2024-01-10 06:01 CET (History)
3 users (show)

See Also:
Source RPM:
CVE:
Status comment:


Attachments

Description Jean-François Bachelet 2023-04-07 12:11:52 CEST
Description of problem:

I see a problem with KDE, when multiple instances of programs are used it had the habit to regroup automatically all instances under one unique 'menu' in the taskbar, using for this the 'authorize program regroupment' option in the 'more actions' submenu...

btw, since some updates (can't remember which, sorry) of the graphics system, that regroupment isn't automatic anymore there, althouth the option is ticked. I have to manualy untick then retick the option to se it happen but that's not stable and works only for the screen I set it on (I'm using two monitors and two screens there)

instead, when room is tight in the taskbar I see attempts to regroup then immediate release of it then re-attempts etc... or just fast 'flicking' of items without any attemps to regroup it... resulting in a somewhat very eye tearing fast 'flicking' of items in the taskbar.

that flicker phenomenon appear to just be on the secondary screen here, don't know why ??? 

Version-Release number of selected component (if applicable):
Kernel desktop v 5.15.98-1.mga8

How reproducible:
setup un two screens/monitors system like me and fill it with multiple instances of Dolphin and other programs and see what happens.

Steps to Reproduce:
1.two identical monitors (27 pouces here)
2.two identicals desktops (1920*1080*32 here)
3.one full 'default' taskbar on each monitor
4. lostsa dolphin instances (working with 3 to 4 of it here sometimes more) and some other opened software
5. after a while the bug will show up
Jean-François Bachelet 2023-04-07 12:12:00 CEST

CC: (none) => jfbachelet

Comment 1 Marja Van Waes 2023-04-08 20:36:23 CEST
Assigning to the KDE maintainers, who are better able than me to triage this report.

CC: (none) => marja11
Assignee: bugsquad => kde

Comment 2 David GEIGER 2023-04-09 05:41:22 CEST
This issue should be reported upstream at https://bugs.kde.org/

CC: (none) => geiger.david68210

Comment 3 Jean-François Bachelet 2023-04-09 10:50:45 CEST
done : https://bugs.kde.org/show_bug.cgi?id=468320

let's see... :)
Comment 4 Jean-François Bachelet 2023-04-11 00:05:30 CEST
here is the answer from KDE : 

Nate Graham <nate@kde.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Product|kde                         |plasmashell
   Target Milestone|---                         |1.0
                 CC|                            |nate@kde.org
          Component|general                     |Task Manager and Icons-Only
                   |                            |Task Manager
         Resolution|---                         |UNMAINTAINED
           Assignee|unassigned-bugs@kde.org     |plasma-bugs@kde.org
             Status|REPORTED                    |RESOLVED
            Version|unspecified                 |5.20.4

--- Comment #1 from Nate Graham <nate@kde.org> ---
I'm afraid Plasma 5.20 is unfortunately no longer eligible for support or
maintenance. Plasma is a fast-moving project, and bugs in one version are often
fixed in the next one. Please update to Plasma 5.27 as soon as your distro
offers it to you. If you need support for Plasma 5.20, please contact your
distro, who bears the responsibility of providing support for older non-LTS
releases.

If you can reproduce the issue after upgrading to Plasma 5.27, feel free to
re-open this bug report.

Thanks for understanding!

:(
Comment 5 Jean-François Bachelet 2023-04-11 00:09:34 CEST
just looked at the packages, we have no plasma 5.27, what can I do ??? I don't want to change for gnome or else...
Comment 6 sturmvogel 2023-04-11 14:07:38 CEST
We have Plasma 5.27 in cauldron since release…
Comment 7 sturmvogel 2023-04-11 14:11:33 CEST
Also check if you have a broken user profile by creating a new user under MGA8…
Comment 8 Jean-François Bachelet 2023-04-13 15:03:17 CEST
Hello :)

this is a new user as it is a brand new install from scratch :(

is it safe to update plasma 5.27 from cauldron ? how do I do it ?

thnaks :)
Comment 9 Jean-François Bachelet 2023-04-15 15:23:26 CEST
the question : is it safe for my work box to insert plasma 5.27 from cauldron in my brand new Mageia8 release install ?

and how I do it ?

thanks for the help  :)
Comment 10 sturmvogel 2024-01-10 06:01:43 CET
Mageia 8 is EOL. 

If your problem is still there with actual KDE Plasma versions in Mageia 9, repeat the steps as requested in comment 2.

Resolution: (none) => OLD
Status: NEW => RESOLVED


Note You need to log in before you can comment on or make changes to this bug.