KDE, Techpaladin & Kubuntu Focus Announce The Bullet-Proof KDE Software Initiative
KDE e.V. along with Linux PC vendor Kubuntu Focus and KDE-aligned consulting firm Techpaladin Software have announced a collaboration of the “bullet-proof KDE Software initiative” for providing at least three years of bug fixes and security updates to KDE Plasma 6.6 LTS and related software… ⌘ Read more

@brytboi@twtpub.com I hope you’re seeing my replies because you absolutely can scroll up in the app. Let me know if you’ve run into a bug though and report it to me so I can fix it immediately!

A Zoom Screen-Sharing Bug Let Anyone Take Over Other Devices On a Call
An anonymous reader quotes a report from Wired: As AI models gain advanced capabilities to find vulnerabilities in software, develop ways to exploit them, and even carry out autonomous hacking sprees, researchers offered a sobering new example on Tuesday, disclosing vulnerabilities in the video conferencing platform Zoom that could have … ⌘ Read more

CachyOS gets improved handheld detection in the August release
CachyOS is one of the most popular Linux distributions and they’ve released their August release with lots of bug fixes and a few new features.

Image

Read the full article on GamingOnLinux. ⌘ Read more

AI Reviews Bring ‘New Normal’ to Linux Release Candidates: Lots of Bug Fixes
Linux Torvalds expects Linux 7.2 should be released next weekend “unless something really bad
pops up,” Torvalds said while announcing today’s release candidate.

But there’s something interesting about Linux 7.2-rc7, writes Phoronix. “By the time the Linux kernel typically hits a -rc7 release things have usually settled qui … ⌘ Read more

@david@daiwei.me Are you able to describe this bug as an Issue in the Gitea Issue Tracker such that it can be reproduced and fixed? 🙏

Wine 11.15 Released With Wayland Fixes, Fix For A 20 Year Old MSXML3 Bug
Making its debut this Saturday rather than the usual bi-weekly Friday release regiment, Wine 11.15 is out today as the newest development release for this open-source software enabling Windows games and applications to run on Linux… ⌘ Read more

HWMON Fixes For Linux 7.2-rc7: “Most Of Them Fixing Critical Or High Severity Bugs”
It’s been another busy week in the Linux kernel camp with increased patch activity continuing due to AI/LLM coding agents / bots continuing to uncover different defects in the open-source codebase. The hardware monitoring (HWMON) subsystem saw many fixes this week for issues mostly raised by the Sashiko AI bot with the issues being described as mostly critical or high severity bugs… ⌘ Read more

GCC 16.2 Released With More Than 100 Fixes
Following the GCC 16.1 compiler release from the end of April as the first stable version of GCC 16, GCC 16.2 is now available with dozens of bug fixes collected since then for further stabilizing this year’s GNU compiler feature release… ⌘ Read more

IceWM 4.1 Window Manager Brings Bug Fixes
As the first new release since IceWM 4.0 released back on New Year’s Day for this X11 window manager, IceWM 4.1 is now available… ⌘ Read more

Apple Limits Bug Bounty Submissions After Flood of AI Slop
Apple has capped the number of open bug-bounty reports researchers can submit after being flooded with low-quality and sometimes entirely fabricated vulnerabilities generated by AI. MacRumors reports: The Financial Times learned of the limit after cybersecurity startup Bynario used ChatGPT to locate more than 50 macOS bugs in three weeks. Bynario found a privi … ⌘ Read more

NVIDIA 610.57.04 Linux Driver Delivers Many Fixes
NVIDIA is kicking off the new month by releasing an updated R610 Linux driver build with quite a number of bug fixes… ⌘ Read more

Chrome Is Using AI To Fix Hundreds of Bugs, Eliminate Full Browser Restarts
Google says AI-assisted workflows helped Chrome fix 1,072 security bugs across versions 149 and 150, more than the previous 23 releases combined. The company is also testing twice-weekly security updates and “dynamic patching,” which could apply most fixes without requiring users to restart the entire browser. “By leveraging … ⌘ Read more

AI-Found Bugs Aren’t Proving Any Easier to Exploit Despite the Hype
AI-assisted vulnerability discovery has yet to produce the expected surge in real-world attacks: VulnCheck found that only 14 of 1,061 attributed discoveries, or 1.3 percent, had been exploited, which is “almost identical to the rate across all vulnerabilities in VulnCheck’s dataset,” reports The Register. “That’s a far cry from the narrative t … ⌘ Read more

KDE Developer Fixing Long-Standing Bug Over Very Long Small-File Copy Times
Since 2014 there has been a KDE bug report titled Ridiculously slow file copy (multiple small files). With the Dolphin file manager or other KIO-based KDE programs, copying many small files can be much slower than using the cp command directly or other copying programs like rsync, Finally that issue is in the process of being resolved for addressing very slow copy times when dealing with many small files on the KDE Plasma desktop… ⌘ Read more

KDE Developer Fixing Long-Standing Bug Over Very Long Small-File Copy Times
Since 2014 there has been a KDE bug report titled Ridiculously slow file copy (multiple small files). With the Dolphin file manager or other KIO-based KDE programs, copying many small files can be much slower than using the cp command directly or other copying programs like rsync, Finally that issue is in the process of being resolved for addressing very slow copy times when dealing with many small files on the KDE Plasma desktop… ⌘ Read more

Fwupd 2.1.7 Released With Many Bug Fixes
Fwupd 2.1.7 is out today as the newest update to this open-source firmware updating utility that pairs with the Linux Vendor Firmware Service (LVFS) for offering a nice firmware upgrade story on Linux systems… ⌘ Read more

Linux 7.2-rc5 Released: “Once More We Have Quite A Massive -rc5”
In working toward releasing the stable Linux 7.2 kernel in less than one month’s time, out today is Linux 7.2-rc5 to ship this week’s latest bug/regression fixes and help facilitate more testing of this in-development kernel version… ⌘ Read more

Linux 7.2-rc5 Fixing Longstanding Bug In IPv4 Networking Over Firewire
Firewire still isn’t dead yet on Linux. Current plans call for maintaining IEEE-1394 Firewire on Linux at least through 2029 and with today’s Linux 7.2-rc5 kernel release is a fix for those wanting to leverage IPv4 networking over Firewire… ⌘ Read more

Wine 11.14 Released
Wine 11.14 is out with initial WoW64 mode support on FreeBSD, allowing 32-bit Windows applications to run on a 64-bit system without relying on 32-bit multilib support. The release also adds Start Menu icon support in Wine Explorer, 7.1 format conversions in DirectSound, AES-GMAC support in BCrypt, and 21 bug fixes affecting apps and games including Adobe Reader, Heroes of the Storm, and Age of Empires I and II. Additional details can b … ⌘ Read more

KDE Plasma 6.8 Introducing New kscreenctl Tool
KDE developers have been working on kscreenctl as a utility replacement to kscreen-doctor. Plasma and related code has also seen a number of bug/crash fixes coming about this week too… ⌘ Read more

Qualcomm QCE Driver On The Chopping Block With ~48x Slower Than Armv8 Crypto Extensions
A few days back I wrote about upstream Linux kernel developers marking the Qualcomm crypto accelerator driver as “broken” and “harmful” due to its slow performance, history of bugs, and other limitations. Now this Qualcomm Crypto Engine “QCE” driver might be removed outright from the Linux kernel source tree after discovering it’s even worse than anticipated… ⌘ Read more

Data protection, @dce@hashnix.club! :-D

This revealed another bug in my client that I still need to fix at some point. Inserting an empty set of messages failed with an SQL logic error. Whoops. I didn’t think about that corner case.

The “New Normal” Of Audio Quirks Submitted For Linux 7.2-rc5
Linux sound subsystem maintainer Takashi Iwai of SUSE sent out this week’s batch of sound fixes that he describes as “A collection of fixes that have been accumulated recently. The amount is still “new normal”, but all small fixes. Mostly hardware-specific quirks, but including a few core fixes, too.” The “new normal” has been a common phrase recently to reflect the increased tempo of patches as well as security/bug disclosures all due to the increased … ⌘ Read more

Beetleball looks hilarious, like Rocket League with bugs that have crazy abilities
Beetleball looks like it could be another good one to have a blast online with friends, or just to have a general laugh with.

Image

Read the full article on [GamingOnLinux](https://www.gamingonlinux.com/2026/07/beetleball-looks-hilarious-like-rocket-league-with-bugs-that-have-cra … ⌘ Read more

@movq@www.uninformativ.de Finally, your software is just perfect and finished by now, no need to report non-existing bugs or send in code changes. :-) How many tickets and merge requests did you get before moving to your own server?

I have to admit that I use git format-patch so rarely, I always have to pull it up from my shell history. Haven’t used git send-email even once. I definitely have to look into that soon. Wanted to do that for several years. I typically upload the patch to my server and send a link via IRC.

Maybe I was just very unlucky, but my experience is that you can perfectly ignore people and their work who only do it for the “fame”. It’s almost always been from inferior quality to say the least.

@prologic@twtxt.net Hmmm, I have no idea how to solve that problem. 😅 Some jenny stuff aside, I received zero bug reports or code contributions since leaving GitHub in 2018.

I thought I had made that super easy, because you can just send me an email – no sign-up process, nothing. But that’s way too old-school, people don’t know how to use git format-patch (let alone git send-email) and they also don’t understand that they can just send me a link to their forked Git repo (which can be hosted anywhere). Git is super flexible and powerful, but those features are hardly ever used.

Maybe people even need some kind “reward”, or “fame”. Like those “achievements” that you can unlock on GitHub. (Something to put in their CV … ?)

Okay, so, my website also includes my code / git repos, and those are made browsable by stagit. What I don’t like about this (these days) is that this includes all the diffs of my commits. In other words: All my code.

This makes it super easy for malicious crawlers to slurp up valuable data. I don’t like that.

I’m thinking about switching to this instead:

https://movq.de/git2/

It still shows project infos and there are Atom feeds, but to get the code, you have to actually clone the repos.

🤔

(If you spot any bugs, let me know.)

DXVK 3.0.2 brings bug fixes for Dying Light: The Beast, Halo and more on Linux / SteamOS
Direct 3D 8, 9, 10 and 11 to Vulkan layer DXVK has a new bug fix release out, sorting some issues in specific games to make gaming on Linux / SteamOS better.

Image

Read the full article on [GamingOnLinux](https://www.gamingonlinux.com/2026/07/dxvk-3-0-2-brings-bug-fixes-for-dying-light-the … ⌘ Read more

@lyse@lyse.isobeef.org Ahh ok! I was just wondering and curious whether it was a bug that I’ve caused anywhere along the way 🧐

@prologic@twtxt.net A screenshot won’t help in this case, as you don’t see anything. :-D It starts off just fine with a conversation tree like that:

Unknown conversation root
└╴Read reply
  └╴Read subreply

Everything works. After reloading the feeds, a new message becomes part of the conversation, so the conversation e.g. looks:

Unknown conversation root
└╴Read reply
  ├╴Read subreply
  └╴Unread subreply

However, the bug is that the whole conversation is not shown at all. None of the three (or four with the root) messages appear in the message tree view. My recursive SQL determining the messages to display is clearly broken.

Ahh yes! Please do upgrade your twtd instance. Few things changed, many bugs fixed there too.

I should really fix this damn bug where new replies to read replies to unknown conversation roots are not showing up in tt. I run into this bug almost daily for weeks now.

@dce@hashnix.club Fixed! 🥳 That 403 was our bug — connect was checking your token via /api/v1/user (needs read:user), but your token’s scoped to just the repo so it can’t. Now it validates against the repo itself instead 👍

@david@daiwei.me I think it might be a bug i just fixed 🤞

@david@daiwei.me Found it. Some bugs in the “claim limiter”. Fixing…

based on this, it’s entirely possible that there may still be a subtle bug somewhere with the app

@movq@www.uninformativ.de please don’t waste your time to bugging this. I’ll figure out what’s going on with these new clients.🙏

Hurray, I can now press gg instead of g to go to the top in tt. Much better! :-) Other multi-key combinations are also easily possible now.

I should probably write a real article about this at some point, but here we go. The only downside with my new key binding system is that it breaks tview’s established pattern. You’ve got an InputHandler(), that is implemented using WrapInputHandler(…). It typically then directly implements the switching logic depending on the key press. Something like this:

func (w *Widget) InputHandler() func(event *tcell.EventKey, setFocus func(p tview.Primitive)) {
    // WrapInputHandler allows for intercepting key events with SetInputCapture(…)
    // from the outside for customization. This handles the default key bindings.
    return t.WrapInputHandler(func(event *tcell.EventKey, setFocus func(p tview.Primitive)) {
        switch event.Key() {
        case tcell.KeyRune:
            if event.Modifiers() == tcell.ModNone {
                switch event.Rune() {
                case 'k':
                    w.scrollUp()
                    return // we already handled the event, stop processing

                case 'j':
                    w.scrollDown()
                    return
                }
            }
        }

        // We didn't handle the key event. Maybe the parent
        // widget knows what to do with it.
        if handler := w.parent.InputHandler(); handler != nil {
            handler(event, setFocus)
        }
    })
}

From the outside, you can intercept and either stop or continue the widget’s original key handling with a potentially rewritten key event using SetInputCapture(…):

w := NewWidget()
// customized or additional key bindings
w.SetInputCapture(func(event *tcell.EventKey) *tcell.EventKey {
    switch event.Key() {
    case tcell.KeyUp:
        // Rewrite the event, so the "cursor up" key is an alias
        // for the vim key binding "k", that is handled by the
        // wrapped input handler above. (I know, I know, this is a
        // completely unrealistic example, why would anyone use
        // cursor keys when there are vim key bindings available?!)
        return tcell.NewEventKey(tcell.KeyRune, 'k', tcell.ModNone)

    case tcell.KeyRune:
        if event.Modifiers() == tcell.ModNone {
            switch event.Rune() {
                case 'q':
                    app.Stop()
                    // we already handled the event, do not pass it
                    // to the wrapped input handler above
                    return nil

                case 'r':
                    toggleMessageReadStatus()
                    return nil
            }
        }
    }

    // we didn't handle the event, pass it to the wrapped
    // input handler above
    return event
}

Since they all expect a single key, I’ve noticed that using multiple dedicated KeyBindings of mine on these different levels kinda breaks multi-key handling with common prefixes. The outer-most KeyBinding captures the prefix, but it can’t transfer it to the inner one if not handled by the outer one. At least not without some more (potentially ugly) changes. So, I now have to work with just a single KeyBindings object for the entire widget chain (if it consists of multiple other widgets or the regular input handler and input capture are in the game). The outside needs to register all its key bind customizations or extensions at the same level that the original widget handles its default ones. Doable by exposing the widget’s KeyBindings instance, but not pretty. You always have to keep this in mind.

With the KeyBindings, it will look like that:

type Widget struct {
    parent tview.Primitive

    // make it available to children or the outside either by
    // direct field access or by providing a getter method
    KeyBindings *bind.KeyBindings
}

func NewWidget() *Widget {
    w := &Widget{KeyBindings: &bind.KeyBindings{}}
    w.KeyBindings. // default key bindings
        Bind0(bind.KeySequence('k', w.scrollUp).
        Bind0(bind.KeySequence('j', w.scrollDown)
    return w
}

func (w *Widget) InputHandler() InputHandler() func(event *tcell.EventKey, setFocus func(p tview.Primitive)) {
    return t.WrapInputHandler(func(event *tcell.EventKey, setFocus func(p tview.Primitive)) {
        // also note the missing support for focus transfer at the moment
        event = w.KeyBindings.Capture(event)
        if event == nil {
            return
        }

        if handler := w.parent.InputHandler(); handler != nil {
            handler(event, setFocus)
        }
    }
}

And then from the outside, or in a child widget:

w := NewWidget()
w.KeyBindings. // additional or customized key bindings
    Bind1(bind.KeySequence(tcell.KeyUp), func(*tcell.EventKey) *tcell.EventKey {
        return tcell.NewEventKey(tcell.KeyRune, 'k', tcell.ModNone)
    }).
    Bind0(bind.KeySequence('q'), app.Stop).
    Bind0(bind.KeySequence('r'), toggleMessageReadStatus)

When directly working with tview primitives that are not part of custom widget implementations, the following works well so far:

textView := tview.NewTextView().
    SetWordWrap(true).
    SetText("…")
    SetScrollable(true)
textView.SetInputCapture((&bind.KeyBindings{}).
    Bind0(bind.KeySequence('q'), app.Stop).
    Bind1(bind.KeySequence('g', 'g'), func(*tcell.EventKey) *tcell.EventKey {
        return tcell.NewEventKey(tcell.KeyHome, 0, tcell.ModNone)
    }).
    Capture)

I need to sleep on this some more.

Also, writing very long messages like this one is really not all that fun in tt’s editor. I should absolutely provide a way to shell out to vim.

(Took me about one and a half hours to compose, holy crap. But not only because of not using vim. Although, that might have saved me a quarter hour or so for sure. Proof-reading this message also uncovered quite a few bugs in my real documentation. So, that’s a big win!) Good night!

I believe we’ve nailed all the bugs down🤣 Though i am sick at the moment so i’m not at my best 😢

@balloon-fu-sen@tw.fus.f5.si Ahhh! That’s a bug! Lemme fix that!

🥳 Finally! After nearly 4 years, yarnd v0.16.0 “Silver Sojourner” is out! 🚀 Twt Hash v2, SQLite FTS5 search, HTMX-powered UI, first-time setup wizard and literally hundreds of bug fixes 🐛

Release notes: https://git.mills.io/yarnsocial/yarn/releases/tag/0.16.0

Upgrading is fully automatic — the Twt Hash v2 migration re-fetches all feeds on first start, so expect the first cycle to be a bit heavier. Images on Docker Hub as prologic/yarnd:0.16.0 👌

cc @kat@yarn.girlonthemoon.xyz @abucci@anthony.buc.ci @shinyoukai@yume.laidback.moe @eldersnake@we.loveprivacy.club 🙏

@bender@twtxt.net No idea. I can only tell you that the correct hash would have been rwzz277nkyju for this line:

[2026-07-11 14:47:17+00:00] [(#5bpwpdcjnhcz) <a href="https://we.loveprivacy.club/external?uri=https://daiwei.me/twtxt.txt">@david<em>@daiwei.me</em></a> (This thread is broken again on my end. Another bug or fix not released yet? 😅)]

@david@daiwei.me (This thread is broken again on my end. Another bug or fix not released yet? 😅)

I will aim to have most issues bugs and user experience problems, identified and fixed by this weekend!

And if we can compile a list and file issues for feeds, twtxt.app and anything else as issues for when i get back 🙏 feature requests, bug reports. etc 🤞

FYi 👋 I’m aware of an optimist precomputed hashing bug on the new twtxt.app 🤯 Trying to work with @bender@twtxt.net remotely on my vacation yo fix it 🤣

@movq@www.uninformativ.de I figure there is a bug somewhere, but where?

What’s the bug?

@movq@www.uninformativ.de we found a bug. @prologic@twtxt.net loves it!