[qt/qt/qtbase]: Summary of bulk changes made

KDE Git Services - Bulk Change <[email protected]>
Newsgroups gmane.comp.kde.cvs
Message-ID <[email protected]>
Git repository change summary for qt/qt/qtbase
Pushed by mirror-service into branch '6.11'.
Changed from 56c5d1ab1809a4731372bbc5f87fe7784b1c5920 to 8a958fd0d3f96a0af9228fc3cf950d815c5d2024
Acknowledgement was received that this change introduces only existing code that has been pushed to another public open source repository.

This change contains the following new commits:

Git commit 02145160f9ed709f0f5305567f4283e96772e06a by Qt Cherry-pick Bot (on behalf of Thiago Macieira) on 18/08/2026 at 22:03..
QLockFile/Unix: don't complain about removing a lock already gone

If the errno on unlink() is ENOENT, the file was already removed. That's
a problem because something bypassed our lock protocol, but it's not a
permission issue. Let it go.

If it's ENOTDIR, then the directory hierarchy changed in an unexpected
manner. That's also a problem but nothing we should warn about.

Task-number: QTBUG-148845
Pick-to: 6.8
Change-Id: I0e96e8372621e4750ad2fffd7153e2d00dd2ddab
Reviewed-by: David Faure <[email protected]>
(cherry picked from commit 0caff71cf58ae2b79340857a942c537f29c7f750)
Reviewed-by: Qt Cherry-pick Bot <[email protected]>
(cherry picked from commit 251f05c7104703980baf2930cefcbb45e1a07d75)
https://invent.kde.org/qt/qt/qtbase/-/commit/02145160f9ed709f0f5305567f4283e96772e06a

Git commit 88d65c18a334b7d3b5195b79342739bb0f5070a5 by Qt Cherry-pick Bot (on behalf of Thiago Macieira) on 18/08/2026 at 22:03..
QLockFile/Unix: let removeStaleLock() claim credit for lock being gone

The point of this function is to remove a stale lock, so if it's already
gone by the time we try to open it, claim credit. The difference will be
in tryLock() whether we wait a bit or retry the lock file immediately.

If the apparently-stale lock was removed by its legitimate holder, this
speeds up the lock acquisition for us. If the apparently-stale lock was
removed by another thread/process also attempting to lock, we will race
it to create the lock: one of them will succeeed at creating with O_EXCL
and the other will get EEXIST. In most scenarios, isApparentlyStale()
will then be false, because the file's mtime has just got updated.

Pick-to: 6.8
Task-number: QTBUG-148845
Task-number: QTBUG-149130
Change-Id: I2d8d9028e5d6819fbe1efffd62898f07b66a008b
Reviewed-by: David Faure <[email protected]>
(cherry picked from commit 50bd05b6a0b71b0d8dd58369dc6a178878ee7e01)
Reviewed-by: Qt Cherry-pick Bot <[email protected]>
(cherry picked from commit d62a5abf3625fbd075633018bb3e6c2c0af5127c)
https://invent.kde.org/qt/qt/qtbase/-/commit/88d65c18a334b7d3b5195b79342739bb0f5070a5

Git commit 87e5833373e0d713dc8d51d9eb1684d3a97faa9d by Qt Cherry-pick Bot (on behalf of Thiago Macieira) on 18/08/2026 at 22:03..
QLockFile/Doc: remove stale information about non-US-ASCII hostnames

Amends commit 4dca0cba304d18d19ec54df7dac719799279bc18, which
inadvertedly fixed this. The issue was that the original Windows
implementation did:

static inline QByteArray localHostName()
{
    return qgetenv("COMPUTERNAME");
}

Which obtained the hostname encoded in the Windows ANSI codepage (and
potentially corrupted it). That was before qEnvironmentVariable().

Task-number: QTBUG-49640
Pick-to: 6.8 5.15
Change-Id: Ifb9d134aabe5cffd0121fffdfdb360702a8dbd50
Reviewed-by: David Faure <[email protected]>
(cherry picked from commit 2b1f2228fa391374d92235d20cae8280c5b2d8a8)
Reviewed-by: Qt Cherry-pick Bot <[email protected]>
(cherry picked from commit bb6b4710d96404d7b7f4da5b912a2e14958ef145)
https://invent.kde.org/qt/qt/qtbase/-/commit/87e5833373e0d713dc8d51d9eb1684d3a97faa9d

Git commit 8a958fd0d3f96a0af9228fc3cf950d815c5d2024 by Qt Cherry-pick Bot (on behalf of Wu JiangYu) on 18/08/2026 at 22:03..
client: Keep committed buffers busy while unexposed

After a frame callback timeout, safeCommit() may receive a committed
buffer while the window is unexposed. Clearing its busy state lets
the backing store reuse it before wl_buffer.release. The next commit
is ignored and the window stops updating.

Committed buffers now remain busy until the compositor releases them.

Fixes: QTBUG-149232
Change-Id: I96764659b3af1be3de5026379cf6bd91c1b007be
Reviewed-by: Eskil Abrahamsen Blomfeldt <[email protected]>
(cherry picked from commit aa41b256eb7c35e36cd706e6dd9f48a7ddc976d1)
Reviewed-by: Qt Cherry-pick Bot <[email protected]>
(cherry picked from commit 54c517de3263f505a905be39a92978f304edda84)
https://invent.kde.org/qt/qt/qtbase/-/commit/8a958fd0d3f96a0af9228fc3cf950d815c5d2024
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.