Bug 477700 - windows shrink when tabs are added/closed on x11
Summary: windows shrink when tabs are added/closed on x11
Status: CONFIRMED
Alias: None
Product: kwin
Classification: Plasma
Component: general (show other bugs)
Version: 5.27.10
Platform: Arch Linux Linux
: NOR minor
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords:
: 478141 480210 482099 490965 (view as bug list)
Depends on:
Blocks:
 
Reported: 2023-11-29 04:30 UTC by Alan Vekselman
Modified: 2024-09-27 09:03 UTC (History)
13 users (show)

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


Attachments
attachment-719359-0.html (41 bytes, text/html)
2023-11-30 16:40 UTC, ninjalj
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Alan Vekselman 2023-11-29 04:30:26 UTC
Whenever I open a new tab or when I switch between tabs, the whole terminal window slightly shrinks vertically. This happened after my last system upgrade yesterday.
Comment 1 fanzhuyifan 2023-11-30 04:03:50 UTC
(In reply to alanvek98 from comment #0)
> Whenever I open a new tab or when I switch between tabs, the whole terminal
> window slightly shrinks vertically. This happened after my last system
> upgrade yesterday.

Can't reproduce.. Would you be able to share some screenshots demonstrating this issue? Thanks!
Comment 2 Alan Vekselman 2023-11-30 04:32:25 UTC
Yes, sure.

First, when I open a new terminal, I see this tiny line underneath, which is the window that's in the brackground.
https://ibb.co/Kjtp7rQ

Then, every time I create a new tab, and every time I switch between tabs, the konsole gets a little smaller (just vertically).
https://ibb.co/pjDztXg
https://ibb.co/3mxF6Zh

Every few tab creations or tab switches, I get a pop-up displaying the terminal size, and every time it displays it has fewer rows
https://ibb.co/7zYhztr
https://ibb.co/8rDK9ZJ
Comment 3 Alan Vekselman 2023-11-30 04:33:22 UTC
Thanks for the reply by the way! :)
Comment 4 ninjalj 2023-11-30 16:40:02 UTC
Created attachment 163660 [details]
attachment-719359-0.html

Which window manager are you using?
Comment 5 Alan Vekselman 2023-11-30 20:23:41 UTC
KWin
Comment 6 Alan Vekselman 2023-12-01 14:56:28 UTC
If it helps, if I switch to Wayland instead of X11, the problem seams to disappear.
Comment 7 RocketDev 2023-12-05 02:26:50 UTC
I have this problem too! Several days ago, my Konsole began to shrink on size when altering tabs slightly not only vertically but even horizontally. Using Kwin on X11.
Comment 8 fanzhuyifan 2023-12-05 03:02:03 UTC
(In reply to RocketDev from comment #7)
> I have this problem too! Several days ago, my Konsole began to shrink on
> size when altering tabs slightly not only vertically but even horizontally.
> Using Kwin on X11.

Which version are you on?
Comment 9 RocketDev 2023-12-05 03:58:07 UTC
(In reply to fanzhuyifan from comment #8)
> (In reply to RocketDev from comment #7)
> > I have this problem too! Several days ago, my Konsole began to shrink on
> > size when altering tabs slightly not only vertically but even horizontally.
> > Using Kwin on X11.
> 
> Which version are you on?

I'm a Arch Linux user, so everything should be latest as I often update my system. Konsole: 23.08.3; Kwin 3.27.9
Comment 10 fossie 2023-12-14 22:09:17 UTC
I've the same issue after I updated my system today, my windows is shrinking vertically. I'm running Ubuntu 22.04 also with Konsole: 23.08.3 but on KWin version: 5.27.9 with X11
Comment 11 fossie 2023-12-14 22:21:05 UTC
# apt list -a konsole
konsole/jammy 4:23.08.3-0xneon+22.04+jammy+release+build32 amd64 [upgradable from: 4:21.12.3-0ubuntu1]
konsole/jammy 4:23.08.2-0xneon+22.04+jammy+release+build31 amd64
konsole/jammy 4:23.08.1-0xneon+22.04+jammy+release+build30 amd64
konsole/jammy 4:23.08.0-0xneon+22.04+jammy+release+build29 amd64
konsole/jammy,now 4:21.12.3-0ubuntu1 amd64 [installed,upgradable to: 4:23.08.3-0xneon+22.04+jammy+release+build32]

I downgraded to all available versions until 4:21.12.3-0ubuntu1, but the issue still exists in every version.
Comment 12 Daniel 2023-12-27 08:51:10 UTC
(In reply to fossie from comment #11)
> # apt list -a konsole
> konsole/jammy 4:23.08.3-0xneon+22.04+jammy+release+build32 amd64 [upgradable
> from: 4:21.12.3-0ubuntu1]
> konsole/jammy 4:23.08.2-0xneon+22.04+jammy+release+build31 amd64
> konsole/jammy 4:23.08.1-0xneon+22.04+jammy+release+build30 amd64
> konsole/jammy 4:23.08.0-0xneon+22.04+jammy+release+build29 amd64
> konsole/jammy,now 4:21.12.3-0ubuntu1 amd64 [installed,upgradable to:
> 4:23.08.3-0xneon+22.04+jammy+release+build32]
> 
> I downgraded to all available versions until 4:21.12.3-0ubuntu1, but the
> issue still exists in every version.

The only way I've found to work around the issue, is to fully downgrade KDE Plasma and related packages. Just downgrading Konsole does not fix this bug, sadly. I am facing these issues on the latest versions of KDE Plasma and related packages on Fedora 39 (X11) as well, very annoying.
Comment 13 RocketDev 2023-12-27 09:16:12 UTC
It seems that it is a common problem. Should the status be raised to CONFIRMED? Anyway, I may switch to tmux for an alternative tab experience.
Comment 14 Alan Vekselman 2023-12-31 14:08:45 UTC
I'm not sure which, but one of my latest system updates has apparently fixed this bug. It'd been a few days since my last reboot, and I had been periodically updating everything with pacman. After my computer ran out of battery last night, konsole was magically working when I turned it on today. In case it helps, I'm attaching the log of my pacman updates since when I think my last reboot was.

# grep -i upgraded /var/log/pacman.log
upgraded imagemagick (7.1.1.23-1 -> 7.1.1.24-1)
upgraded iputils (20221126-2 -> 20231222-1)
upgraded gtk3 (1:3.24.39-1 -> 1:3.24.39-2)
upgraded krb5 (1.20.1-2 -> 1.21.2-2)
upgraded libseccomp (2.5.4-2 -> 2.5.5-1)
upgraded qt6-base (6.6.1-2 -> 6.6.1-3)
upgraded iwd (2.11-1 -> 2.12-1)
upgraded ppp (2.5.0-1 -> 2.5.0-2)
upgraded fontconfig (2:2.14.2-1 -> 2:2.15.0-1)
upgraded parallel (20231122-1 -> 20231222-1)
upgraded python-distlib (0.3.7-1 -> 0.3.8-1)
upgraded python-shtab (1.6.4-1 -> 1.6.5-1)
upgraded eos-dracut (1.2-1 -> 1.3-1)
upgraded nodejs (21.4.0-2 -> 21.5.0-1)
upgraded openmpi (4.1.5-5 -> 4.1.6-1)
upgraded eos-rankmirrors (2.25-1 -> 2.26-1)
upgraded eos-bash-shared (23.30-1 -> 23.31-1)
upgraded eos-apps-info (23-6 -> 23-7)
Comment 15 Daniel 2024-01-02 07:53:17 UTC
I tried updating again on Fedora 39 just now, but the latest KDE Plasma 5.27.10 and related packages still cause this bug to appear. I downgraded to 5.27.8 again and yet again, am no longer having the tab bug.
Comment 16 Alan Vekselman 2024-01-06 14:53:03 UTC
Well, after my latest pacman update, the bug is back again. :/

These are the packages that were updated:

upgraded hwdata (0.377-1 -> 0.378-1)
upgraded at-spi2-core (2.50.0-1 -> 2.50.1-1)
upgraded autoconf (2.71-4 -> 2.72-1)
upgraded c-ares (1.24.0-1 -> 1.25.0-1)
upgraded firewalld (2.0.2-1 -> 2.1.0-1)
upgraded imagemagick (7.1.1.24-1 -> 7.1.1.25-1)
upgraded libfdk-aac (2.0.2-1 -> 2.0.3-1)
upgraded libssh (0.10.6-1 -> 0.10.6-2)
upgraded libxmlb (0.3.14-1 -> 0.3.15-1)
upgraded linux (6.6.8.arch1-1 -> 6.6.9.arch1-1)
upgraded linux-g14 (6.6.6.arch1-1 -> 6.6.8.arch1-1)
upgraded linux-g14-headers (6.6.6.arch1-1 -> 6.6.8.arch1-1)
upgraded linux-headers (6.6.8.arch1-1 -> 6.6.9.arch1-1)
upgraded luit (20230201-1 -> 20240102-1)
upgraded noto-fonts (1:23.12.1-1 -> 1:24.1.1-1)
upgraded oath-toolkit (2.6.9-1 -> 2.6.10-1)
upgraded pacman-contrib (1.9.1-1 -> 1.10.1-1)
upgraded poppler (23.12.0-1 -> 24.01.0-1)
upgraded poppler-glib (23.12.0-1 -> 24.01.0-1)
upgraded poppler-qt5 (23.12.0-1 -> 24.01.0-1)
upgraded ppp (2.5.0-2 -> 2.5.0-3)
upgraded python-psutil (5.9.6-1 -> 5.9.7-1)
upgraded runc (1.1.10-1 -> 1.1.11-1)
upgraded rust (1:1.74.1-1 -> 1:1.75.0-1)
upgraded suitesparse (7.3.1-1 -> 7.4.0-1)
upgraded vim-runtime (9.0.2167-1 -> 9.1.0000-1)
upgraded vim (9.0.2167-1 -> 9.1.0000-1)
upgraded welcome (3.85-1 -> 3.85-2)
upgraded stremio (4.4.164-1 -> 4.4.165-1)
upgraded google-chrome (120.0.6099.129-1 -> 120.0.6099.199-1)
Comment 17 fanzhuyifan 2024-01-23 18:57:44 UTC
*** Bug 480210 has been marked as a duplicate of this bug. ***
Comment 18 Alan Vekselman 2024-01-23 19:21:32 UTC
After my last pacman update, it seems to be fixed again.

These are the packages that were upgraded:

upgraded dracut (059-4 -> 059-5)
upgraded eos-bash-shared (24.1-1 -> 24.2-1)
upgraded iwd (2.13-2 -> 2.13-3)
upgraded libpaper (2.1.2-1 -> 2.1.3-1)

Please let me know if these posts are of any help at all or if I'm just making noise.
Comment 19 Milian Wolff 2024-01-24 10:38:41 UTC
This cannot possibly be a konsole bug - it also applies to KDevelop and probably other applications too. It has to be on a lower level. I suspect it's either in kwin or breeze. See https://bugs.kde.org/show_bug.cgi?id=480210 for a backtrace that triggers the resizing - it's an async XCB event.

Can anyone figure out how to get to the source of that event?

I'm going to confirm this, since I can reproduce this at will with a fully updated arch install in both, KDevelop and Konsole.
Comment 20 Milian Wolff 2024-01-24 11:16:37 UTC
This code here is enough for me to trigger the behavior - it clearly isn't konsole specific at all:

```
#include <QApplication>
#include <QTabBar>
#include <QShortcut>
#include <QDebug>
#include <QMainWindow>
#include <QVBoxLayout>
#include <QTabWidget>
#include <QTimer>
#include <QWindow>

int main(int argc, char** argv)
{
    QApplication app(argc, argv);

    QMainWindow window;

    auto center = new QTabWidget;
    window.setCentralWidget(center);

    auto tab = center->tabBar();

    auto addTab = [tab]() {
        static int counter = 0;
        tab->addTab(QString::number(counter++));
        qWarning() << "add" << counter;
    };
    addTab();

    auto removeTab = [tab]() {
        tab->removeTab(tab->currentIndex());
        qWarning() << "rem";
    };

    auto newTab = new QShortcut(QKeySequence::New, tab);
    qWarning() << newTab->key();
    newTab->setContext(Qt::ApplicationShortcut);
    QObject::connect(newTab, &QShortcut::activated, tab, addTab);

    auto closeTab = new QShortcut(QKeySequence::Close, tab);
    qWarning() << closeTab->key();
    closeTab->setContext(Qt::ApplicationShortcut);
    QObject::connect(closeTab, &QShortcut::activated, tab, removeTab);

    window.resize(600, 400);
    window.show();

    QObject::connect(window.windowHandle(), &QWindow::heightChanged, &window, [&](int height) {
        qWarning() << "height changed:" << height;
    });

    if (app.arguments().contains("--auto")) {
        auto timer = new QTimer(tab);
        timer->setInterval(100);
        QObject::connect(timer, &QTimer::timeout, &app, [&]() {
            static int i = 0;
            if ((i % 2) == 0)
                removeTab();
            else
                addTab();
            ++i;
        });
        timer->start();
    }

    return app.exec();
}
```

Example output when run:

```
./tab --auto
     0.000 warning: main(int, char**)::<lambda[/home/milian/projects/bugs/tab/tab.cpp:25]: add 1
     0.000 warning: main[/home/milian/projects/bugs/tab/tab.cpp:35]: QKeySequence("Ctrl+N")
     0.000 warning: main[/home/milian/projects/bugs/tab/tab.cpp:40]: QKeySequence("Ctrl+W")
     0.040 warning: main(int, char**)::<lambda[/home/milian/projects/bugs/tab/tab.cpp:48]: height changed: 399
     0.111 warning: main(int, char**)::<lambda[/home/milian/projects/bugs/tab/tab.cpp:31]: rem
     0.207 warning: main(int, char**)::<lambda[/home/milian/projects/bugs/tab/tab.cpp:25]: add 2
     0.210 warning: main(int, char**)::<lambda[/home/milian/projects/bugs/tab/tab.cpp:48]: height changed: 398
     0.302 warning: main(int, char**)::<lambda[/home/milian/projects/bugs/tab/tab.cpp:31]: rem
     0.305 warning: main(int, char**)::<lambda[/home/milian/projects/bugs/tab/tab.cpp:48]: height changed: 397
     0.397 warning: main(int, char**)::<lambda[/home/milian/projects/bugs/tab/tab.cpp:25]: add 3
     0.492 warning: main(int, char**)::<lambda[/home/milian/projects/bugs/tab/tab.cpp:31]: rem
     0.494 warning: main(int, char**)::<lambda[/home/milian/projects/bugs/tab/tab.cpp:48]: height changed: 396
     0.587 warning: main(int, char**)::<lambda[/home/milian/projects/bugs/tab/tab.cpp:25]: add 4
     0.590 warning: main(int, char**)::<lambda[/home/milian/projects/bugs/tab/tab.cpp:48]: height changed: 395
     0.686 warning: main(int, char**)::<lambda[/home/milian/projects/bugs/tab/tab.cpp:31]: rem
     0.787 warning: main(int, char**)::<lambda[/home/milian/projects/bugs/tab/tab.cpp:25]: add 5
     0.791 warning: main(int, char**)::<lambda[/home/milian/projects/bugs/tab/tab.cpp:48]: height changed: 394
     0.887 warning: main(int, char**)::<lambda[/home/milian/projects/bugs/tab/tab.cpp:31]: rem
     0.890 warning: main(int, char**)::<lambda[/home/milian/projects/bugs/tab/tab.cpp:48]: height changed: 393
     0.987 warning: main(int, char**)::<lambda[/home/milian/projects/bugs/tab/tab.cpp:25]: add 6
```
Comment 21 Milian Wolff 2024-01-24 11:26:29 UTC
switching channels in ruqola lets the window width get changed. 

setting `--style fusion` doesn't help, so it's not a breeze bug.

I'll later try to reproduce with another WM other than kwin
Comment 22 Milian Wolff 2024-01-24 12:57:08 UTC
It seems to be hidpi related. I have a scale factor of 1.5 set. If I override this to 1 or 2, then my MWE doesn't reproduce anymore
Comment 23 RocketDev 2024-01-24 13:23:19 UTC
(In reply to Milian Wolff from comment #22)
> It seems to be hidpi related. I have a scale factor of 1.5 set. If I
> override this to 1 or 2, then my MWE doesn't reproduce anymore

Following your steps, I tested multiple resolutions and found that on scale 1, 1.25, 2 the window height won't change; then on scale 1.5, 1.75 the window height changs. So weird, 1.25 is not influenced, either.
Comment 24 Alan Vekselman 2024-01-24 15:11:32 UTC
(In reply to Milian Wolff from comment #22)
> It seems to be hidpi related. I have a scale factor of 1.5 set. If I
> override this to 1 or 2, then my MWE doesn't reproduce anymore

I don't have the bug right now, so I can't reproduce, but I also use scale 1.5, so there may be something there.
Comment 25 fanzhuyifan 2024-01-24 15:46:59 UTC
(In reply to Milian Wolff from comment #20)
> This code here is enough for me to trigger the behavior - it clearly isn't
> konsole specific at all:
> 
> ```
> #include <QApplication>
> #include <QTabBar>
> #include <QShortcut>
> #include <QDebug>
> #include <QMainWindow>
> #include <QVBoxLayout>
> #include <QTabWidget>
> #include <QTimer>
> #include <QWindow>
> 
> int main(int argc, char** argv)
> {
>     QApplication app(argc, argv);
> 
>     QMainWindow window;
> 
>     auto center = new QTabWidget;
>     window.setCentralWidget(center);
> 
>     auto tab = center->tabBar();
> 
>     auto addTab = [tab]() {
>         static int counter = 0;
>         tab->addTab(QString::number(counter++));
>         qWarning() << "add" << counter;
>     };
>     addTab();
> 
>     auto removeTab = [tab]() {
>         tab->removeTab(tab->currentIndex());
>         qWarning() << "rem";
>     };
> 
>     auto newTab = new QShortcut(QKeySequence::New, tab);
>     qWarning() << newTab->key();
>     newTab->setContext(Qt::ApplicationShortcut);
>     QObject::connect(newTab, &QShortcut::activated, tab, addTab);
> 
>     auto closeTab = new QShortcut(QKeySequence::Close, tab);
>     qWarning() << closeTab->key();
>     closeTab->setContext(Qt::ApplicationShortcut);
>     QObject::connect(closeTab, &QShortcut::activated, tab, removeTab);
> 
>     window.resize(600, 400);
>     window.show();
> 
>     QObject::connect(window.windowHandle(), &QWindow::heightChanged,
> &window, [&](int height) {
>         qWarning() << "height changed:" << height;
>     });
> 
>     if (app.arguments().contains("--auto")) {
>         auto timer = new QTimer(tab);
>         timer->setInterval(100);
>         QObject::connect(timer, &QTimer::timeout, &app, [&]() {
>             static int i = 0;
>             if ((i % 2) == 0)
>                 removeTab();
>             else
>                 addTab();
>             ++i;
>         });
>         timer->start();
>     }
> 
>     return app.exec();
> }
> ```
> 
> Example output when run:
> 
> ```
> ./tab --auto
>      0.000 warning: main(int,
> char**)::<lambda[/home/milian/projects/bugs/tab/tab.cpp:25]: add 1
>      0.000 warning: main[/home/milian/projects/bugs/tab/tab.cpp:35]:
> QKeySequence("Ctrl+N")
>      0.000 warning: main[/home/milian/projects/bugs/tab/tab.cpp:40]:
> QKeySequence("Ctrl+W")
>      0.040 warning: main(int,
> char**)::<lambda[/home/milian/projects/bugs/tab/tab.cpp:48]: height changed:
> 399
>      0.111 warning: main(int,
> char**)::<lambda[/home/milian/projects/bugs/tab/tab.cpp:31]: rem
>      0.207 warning: main(int,
> char**)::<lambda[/home/milian/projects/bugs/tab/tab.cpp:25]: add 2
>      0.210 warning: main(int,
> char**)::<lambda[/home/milian/projects/bugs/tab/tab.cpp:48]: height changed:
> 398
>      0.302 warning: main(int,
> char**)::<lambda[/home/milian/projects/bugs/tab/tab.cpp:31]: rem
>      0.305 warning: main(int,
> char**)::<lambda[/home/milian/projects/bugs/tab/tab.cpp:48]: height changed:
> 397
>      0.397 warning: main(int,
> char**)::<lambda[/home/milian/projects/bugs/tab/tab.cpp:25]: add 3
>      0.492 warning: main(int,
> char**)::<lambda[/home/milian/projects/bugs/tab/tab.cpp:31]: rem
>      0.494 warning: main(int,
> char**)::<lambda[/home/milian/projects/bugs/tab/tab.cpp:48]: height changed:
> 396
>      0.587 warning: main(int,
> char**)::<lambda[/home/milian/projects/bugs/tab/tab.cpp:25]: add 4
>      0.590 warning: main(int,
> char**)::<lambda[/home/milian/projects/bugs/tab/tab.cpp:48]: height changed:
> 395
>      0.686 warning: main(int,
> char**)::<lambda[/home/milian/projects/bugs/tab/tab.cpp:31]: rem
>      0.787 warning: main(int,
> char**)::<lambda[/home/milian/projects/bugs/tab/tab.cpp:25]: add 5
>      0.791 warning: main(int,
> char**)::<lambda[/home/milian/projects/bugs/tab/tab.cpp:48]: height changed:
> 394
>      0.887 warning: main(int,
> char**)::<lambda[/home/milian/projects/bugs/tab/tab.cpp:31]: rem
>      0.890 warning: main(int,
> char**)::<lambda[/home/milian/projects/bugs/tab/tab.cpp:48]: height changed:
> 393
>      0.987 warning: main(int,
> char**)::<lambda[/home/milian/projects/bugs/tab/tab.cpp:25]: add 6
> ```

Is this on wayland or X11? Which version are you on? Can you try reproducing this on plasma 6, if possible?

Thanks!
Comment 26 Vlad Zahorodnii 2024-01-25 13:03:18 UTC
Off by one errors seem like a highdpi scaling issue. What if you run konsole with QT_ENABLE_HIGHDPI_SCALING=0?
Comment 27 Milian Wolff 2024-01-26 08:09:04 UTC
@fanzhuyifan: see the title of this bug report, it clearly says x11. I have version 21.1.11-1 installed. Plasma is version 5.27.10, Qt at 5.15.12 (with kde patches) - all from Archlinux packages.

I cannot reproduce on plasma 6 yet, because there are no plasma 6 packages yet.

@vlad: exporting that env var does not change anything, neither in my reproducer nor in konsole itself.
Comment 28 fanzhuyifan 2024-01-26 08:25:24 UTC
(In reply to Milian Wolff from comment #27)
> I cannot reproduce on plasma 6 yet, because there are no plasma 6 packages
> yet.

Thanks for your info! One way would be to test on a neon unstable live boot iso. That is probably the least disruptive way. There are also plasma 6 packages in the kde-unstable repo (https://wiki.archlinux.org/title/Official_repositories#kde-unstable).
Comment 29 Milian Wolff 2024-01-26 14:55:30 UTC
Hmm too bad, the plasma6 packages from that repo on Arch are not co-installable with the plasma5 setup so that's not feasible. Do you happen to know who is packaging this? Would be great to work on co-instability instead of direct replacement.

Is the KDE Neon liveboot going to use Wayland or X11? And do you mean the testing image from https://neon.kde.org/download or which one exactly?
Comment 30 fanzhuyifan 2024-01-27 00:22:08 UTC
(In reply to Milian Wolff from comment #29)
> Hmm too bad, the plasma6 packages from that repo on Arch are not
> co-installable with the plasma5 setup so that's not feasible. 

I think they are not supposed to be co-installable, since plasma 6 is meant to replace plasma 5, which is no longer maintained

> Is the KDE Neon liveboot going to use Wayland or X11? 

I think you can choose when you boot up.

> And do you mean the
> testing image from https://neon.kde.org/download or which one exactly?

Yeah that or the Unstable Edition. Both are on plasma 6 right now.
Comment 31 Henry Zhang 2024-01-27 04:36:34 UTC
Downgrading qt5-base from 5.15.11+kde+r147-1 to 5.15.11+kde+r146-1 fixes this issue for konsole on my machine

Seems that the only difference is https://invent.kde.org/qt/qt/qtbase/-/commit/56faf7249c3857f80f6483c5070e7408c2d53961
Comment 32 Milian Wolff 2024-02-02 07:59:39 UTC
I haven't found the time yet to replicate the bug in a live booted neon image (and won't be able to do that within the next week I'm afraid). But a potential fix has landed in qt5-kde, see https://invent.kde.org/qt/qt/qtbase/-/merge_requests/309 - so maybe I can just test that when I'm back in two weeks and see the issue persists here.
Comment 33 Albert Astals Cid 2024-02-02 09:45:32 UTC
*** Bug 478141 has been marked as a duplicate of this bug. ***
Comment 34 Albert Astals Cid 2024-02-02 09:47:57 UTC
We have reverted the path in qt-kde-patch-collection that seems to cause this.

It would be good if a KWin developer could investigate why that patch was problematic since it is part of Qt 6 so we will potentially have the same issue there (unless there was a related patch that we missed and is needed for it)
Comment 35 Milian Wolff 2024-02-12 06:59:16 UTC
I can confirm that the bug is gone with the revert in Qt5, thanks Albert!
Comment 36 fanzhuyifan 2024-03-01 01:34:54 UTC
*** Bug 482099 has been marked as a duplicate of this bug. ***
Comment 37 Milian Wolff 2024-03-19 14:28:58 UTC
I am again seeing this behavior on Plasma 6.0.1 X11 with Qt 6.6.2 - could it still be broken there?
Comment 38 Albert Astals Cid 2024-03-19 20:08:39 UTC
(In reply to Milian Wolff from comment #37)
> I am again seeing this behavior on Plasma 6.0.1 X11 with Qt 6.6.2 - could it
> still be broken there?

If you're seeing it sure, as i said last month

"It would be good if a KWin developer could investigate why that patch was problematic since it is part of Qt 6 so we will potentially have the same issue there (unless there was a related patch that we missed and is needed for it)"

So there is either a KWin bug or a Qt6 bug, someone that knows and can reproduce the problem has to investigate.
Comment 39 Christoph Feck 2024-07-31 18:32:23 UTC
*** Bug 490965 has been marked as a duplicate of this bug. ***
Comment 40 David Smid 2024-08-01 05:48:31 UTC
I have reported the duplicate https://bugs.kde.org/show_bug.cgi?id=490965 (Plasma 6.1.3 X11 with Qt 6.7.2) and I can confirm this depends on hidpi scale.
I was able to reproduce the bug for these scale values only: 1.5 and 1.5625 .
Comment 41 fanzhuyifan 2024-08-01 06:12:12 UTC
(In reply to David Smid from comment #40)
> I have reported the duplicate https://bugs.kde.org/show_bug.cgi?id=490965
> (Plasma 6.1.3 X11 with Qt 6.7.2) and I can confirm this depends on hidpi
> scale.
> I was able to reproduce the bug for these scale values only: 1.5 and 1.5625 .

If this only happens with certain scaling factors, then maybe this is caused by rounding errors in calculating the size.
Comment 42 RocketDev 2024-09-19 15:57:52 UTC
Is this problem solved now? Running under KDE 6.1.5 with X11, can not reproduce the problem on Arch Linux now. Global scale 1.5.
Comment 43 David Smid 2024-09-27 09:03:20 UTC
Actually it got worse after updating to Plasma 6.1.5.
Now I am experiencing this bug for scale values 1.5 - 1.75 .
The first one that is working fine is 1.8125 .