Bug 428580 - multiple split views not rendered correctly when using the oxygen qt-style
Summary: multiple split views not rendered correctly when using the oxygen qt-style
Status: RESOLVED DUPLICATE of bug 412020
Alias: None
Product: konsole
Classification: Applications
Component: split-view (show other bugs)
Version: 20.08.2
Platform: Arch Linux Linux
: NOR normal
Target Milestone: ---
Assignee: Konsole Developer
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-11-01 22:25 UTC by maxmustermann1884
Modified: 2021-02-21 12:16 UTC (History)
1 user (show)

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

Attachments
second konsole window opened automatically (352.38 KB, image/png)
2020-11-01 22:25 UTC, maxmustermann1884 		Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description maxmustermann1884 2020-11-01 22:25:27 UTC 
Created attachment 132951 [details]
second konsole window opened automatically

SUMMARY

konsole doesn't display multiple split view correctly when using the oxygen qt-style

STEPS TO REPRODUCE
1. choose oxygen qt style
2. open more than two split views in konsole

OBSERVED RESULT

no visual feedback when trying to use split views, sometimes another konsole window opens

Expected behavior

split views should be usable (also there is an ugly line on tabs, but that's probably unrelated to this issue)

Operating System: Arch Linux
KDE Plasma Version: 5.20.2
KDE Frameworks Version: 5.75.0
Qt Version: 5.15.1
Kernel Version: 5.9.2-arch1-1
OS Type: 64-bit
Processors: 8 × AMD Ryzen 5 2500U with Radeon Vega Mobile Gfx
Memory: 15,3 GiB of RAM
Graphics Processor: AMD RAVEN
Comment 1 maxmustermann1884 2020-11-01 22:32:02 UTC 
split views actually work somewhat fine when only opened horizontally or vertically, but they don't work when displaying horizontal and vertical split views at the same time
Comment 2 Justin Zobel 2020-11-05 00:07:58 UTC 
Confirmed on KDE Neon Unstable.
Comment 3 maxmustermann1884 2021-02-21 12:16:50 UTC 

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