Bug 470572

Summary:	double clicking on the empty area next to tabs no longer opens a new tab
Product:	[Applications] konsole	Reporter:	Justin Zobel <justin.zobel>
Component:	tabbar	Assignee:	Konsole Developer <konsole-devel>
Status:	RESOLVED FIXED
Severity:	minor	CC:	bugseforuns, emir_sari, nate, tcanabrava
Priority:	NOR	Keywords:	qt6, regression
Version:	master
Target Milestone:	---
Platform:	Other
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Justin Zobel 2023-06-03 05:14:53 UTC

STEPS TO REPRODUCE
1. Have tab bar shown
2. Double click to open a new tab on an empty area on the tab bar

OBSERVED RESULT
Nothing

EXPECTED RESULT
New tab

Operating System: Fedora Linux 39
KDE Plasma Version: 5.27.80
KDE Frameworks Version: 5.240.0
Qt Version: 6.5.1
Kernel Version: 6.4.0-0.rc4.20230529gite338142b39cf.35.fc39.x86_64 (64-bit)
Graphics Platform: Wayland
Processors: 12 × AMD Ryzen 5 3600 6-Core Processor
Memory: 31.0 GiB of RAM
Graphics Processor: NVIDIA GeForce GTX 1060 6GB/PCIe/SSE2

Comment 1 Nate Graham 2023-06-03 17:56:46 UTC

Can reproduce.

Comment 2 Patrick Silva 2023-08-08 13:27:18 UTC

Cannot reproduce on neon unstable.

Comment 3 Nate Graham 2023-08-23 16:31:12 UTC

*** Bug 473675 has been marked as a duplicate of this bug. ***

Comment 4 Nate Graham 2023-08-23 16:31:52 UTC

I can reproduce this with Qt 6.5.2.

Is anyone able to reproduce it with Qt 6.6? Maybe it's fixed there already.

Comment 5 Justin Zobel 2023-08-24 00:07:43 UTC

I don't have Qt6 built from source so I guess I'll have to wait until 
September 26. Unless it's easy enough to build and test with kdesrc-build?

On 24/8/23 02:01, Nate Graham wrote:
> https://bugs.kde.org/show_bug.cgi?id=470572
>
> Nate Graham <nate@kde.org> changed:
>
>             What    |Removed                     |Added
> ----------------------------------------------------------------------------
>                   CC|                            |tcanabrava@kde.org
>
> --- Comment #4 from Nate Graham <nate@kde.org> ---
> I can reproduce this with Qt 6.5.2.
>
> Is anyone able to reproduce it with Qt 6.6? Maybe it's fixed there already.
>

Comment 6 Nate Graham 2023-11-06 14:36:42 UTC

I'm still using Qt 6.5.2 now, but this is now working for me. So I would suspect that it was in fact not a Qt issue, and was fixed in Konsole since this Bugzilla ticket was filed.