Bug 507648 - Taskbar item doesn't refresh Chrome window title when switching tabs
Summary: Taskbar item doesn't refresh Chrome window title when switching tabs
Status: NEEDSINFO WAITINGFORINFO
Alias: None
Product: plasmashell
Classification: Plasma
Component: Task Manager and Icons-Only Task Manager widgets (other bugs)
Version First Reported In: 6.4.1
Platform: Fedora RPMs Linux
: NOR normal
Target Milestone: 1.0
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2025-07-29 20:06 UTC by Alexander Potashev
Modified: 2025-12-25 03:46 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Alexander Potashev 2025-07-29 20:06:13 UTC 
SUMMARY
Taskbar item doesn't refresh Chrome window title when switching tabs.

STEPS TO REPRODUCE
1. Use Google Chrome.
2. Taskbar item is named after the window which is named after the current tab.
3. Change to a different Chrome tab.

OBSERVED RESULT
The text in taskbar item doesn't change.

ksysguard6 shows window title correctly, and it refreshes immediately (<200 ms) when the new window title changes, e.g. on tab switches in Chrome.

On a fresh Plasma session, it works at the beginning, but then the window title suddenly stops updating in the taskbar. Workaround to unstuck window title in taskbar: "plasmashell --replace &"

EXPECTED RESULT
The text in taskbar item should change to the title of the newly focused tab.

SOFTWARE/OS VERSIONS
Operating System: Fedora Linux 41
KDE Plasma Version: 6.4.1
KDE Frameworks Version: 6.15.0
Qt Version: 6.8.3
Kernel Version: 6.15.4-100.fc41.x86_64 (64-bit)
Graphics Platform: X11
Processors: 8 × Intel® Core™ i7-6700HQ CPU @ 2.60GHz
Memory: 16 ГиБ of RAM (15.4 ГиБ usable)
Graphics Processor 1: Intel® HD Graphics 530
Graphics Processor 2: NVIDIA GeForce GTX 960M

ADDITIONAL INFORMATION
Comment 1 David Edmundson 2025-07-31 07:54:49 UTC 
opening a new window still all works correctly?
Comment 2 Bug Janitor Service 2025-08-15 03:46:51 UTC 
🐛🧹 ⚠️ This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information, then set the bug status to REPORTED. If there is no change for at least 30 days, it will be automatically closed as RESOLVED WORKSFORME.

For more information about our bug triaging procedures, please read https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging.

Thank you for helping us make KDE software even better for everyone!
Comment 3 Alexander Potashev 2025-08-17 20:00:22 UTC 
Wasn't able to re-test so far. The issue seems to be rare and random.
Comment 4 Bug Janitor Service 2025-09-01 03:47:25 UTC 
🐛🧹 ⚠️ This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information, then set the bug status to REPORTED. If there is no change for at least 30 days, it will be automatically closed as RESOLVED WORKSFORME.

For more information about our bug triaging procedures, please read https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging.

Thank you for helping us make KDE software even better for everyone!
Comment 5 Bug Janitor Service 2025-09-16 03:48:08 UTC 
🐛🧹 This bug has been in NEEDSINFO status with no change for at least 30 days. Closing as RESOLVED WORKSFORME.
Comment 6 Alexander Potashev 2025-11-03 09:18:37 UTC 
I was able to reproduce this. One Chrome window is currently affected. If I create new windows, they aren't affected.

Operating System: Debian GNU/Linux rodete 
KDE Plasma Version: 6.3.6
KDE Frameworks Version: 6.13.0
Qt Version: 6.8.2
Kernel Version: 6.16.9-1rodete1-amd64 (64-bit)
Graphics Platform: X11
Processors: 14 × Intel® Core™ Ultra 7 165U
Memory: 64 GiB of RAM (62.3 GiB usable)
Graphics Processor: Intel® Graphics
Comment 7 Nate Graham 2025-12-10 19:05:06 UTC 
Does it ever happen on Wayland, or only on X11?
Comment 8 Bug Janitor Service 2025-12-25 03:46:36 UTC 
🐛🧹 ⚠️ This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information, then set the bug status to REPORTED. If there is no change for at least 30 days, it will be automatically closed as RESOLVED WORKSFORME.

For more information about our bug triaging procedures, please read https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging.

Thank you for helping us make KDE software even better for everyone!