Bug 512950

Summary: The key sequence 'Ctrl+Shift+V' is ambiguous on split view
Product: [Applications] yakuake Reporter: Floriankaze
Component: generalAssignee: Eike Hein <hein>
Status: RESOLVED DUPLICATE    
Severity: minor CC: jo
Priority: NOR    
Version First Reported In: 25.11.90   
Target Milestone: ---   
Platform: Other   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:

Description Floriankaze 2025-12-04 18:18:41 UTC
# SUMMARY

I got the below warning, only if I created a "split view" second terminal and want to paste something in. On my first opened terminal, the shortcut works fine. Use default shortcut settings and default profile. My shell is fish, version 4.2.1

```
The key sequence 'Ctrl+Shift+V' is ambiguous. Use 'Configure Keyboard Shortcuts'
from the 'Settings' menu to solve the ambiguity.
No action will be triggered
```

STEPS TO REPRODUCE
1. Open yakuake
2. Create a split view with Meta+- or by right click -> Split View
3. Paste something into the new opened view

# OBSERVED RESULT

Got the error, but only in the new created view, not in the original one

```
The key sequence 'Ctrl+Shift+V' is ambiguous. Use 'Configure Keyboard Shortcuts'
from the 'Settings' menu to solve the ambiguity.
No action will be triggered
```

# EXPECTED RESULT

Content of my clipboard is pasted into the terminal

# SOFTWARE/OS VERSIONS

Operating System: CachyOS Linux 
KDE Plasma Version: 6.5.3
KDE Frameworks Version: 6.20.0
Qt Version: 6.10.0
Kernel Version: 6.17.8-2-cachyos (64-bit)
Graphics Platform: Wayland
Processors: 16 × AMD Ryzen 7 7800X3D 8-Core Processor
Memory: 64 GiB of RAM (61.9 GiB usable)
Graphics Processor 1: AMD Radeon RX 6950 XT
Graphics Processor 2: AMD Ryzen 7 7800X3D 8-Core Processor

fish, version 4.2.1
yakuake 25.11.90


# ADDITIONAL INFORMATION

- Default Shortcuts
- Default profile
- Checked global shortcuts
Comment 1 Jonathan de Jong 2025-12-15 10:31:32 UTC
I'm also experiencing this issue
Comment 2 Jonathan de Jong 2025-12-15 10:32:29 UTC

*** This bug has been marked as a duplicate of bug 470651 ***