Agreguesi i feed

It’s been a long time since I last posted anything here, huh.

Well, a few hours ago I was preparing the release notes for the next release of GNOME Calendar. It is yet to be reviewed, but this is how it reads at the time I write this blog post:

This is a remarkable release for us, as it is one of the biggest releases in the history of the project, and we're excited to share a slightly longer update on it. The first thing many users will notice is how GNOME Calendar will feel snappier now. During the past six months, a lot of work was put in optimizing GNOME Calendar from the inside out. This includes a major change in how it handles events internally, vastly reducing the amount of data transferred between GNOME Calendar and other components of the desktop, and applying many different tricks and strategies to make it render faster. Really, this is probably the most optimized the project has ever been. Another front in which GNOME Calendar has been consistently improving is accessibility and keyboard navigation. During this development cycle, another big batch of improvements on these fronts were merged. You can now navigate between events and days in the Month view using only your keyboard. Notification bubbles are properly read out loud (thanks also to Orca developers for accommodating our use case!). The Week view is now properly styled when the high-contrast setting is enabled. […] On the non-technical side, in the past few months the project received contributions from many new contributors, as well as long time contributors. Our issue tracker continues to be in excellent shape, well triaged, and properly labeled. Our three latest releases were the biggest releases in the history of the project. Thank you all very much for using, developing, documenting, translating, testing, and fixing GNOME Calendar!

This release of Calendar has lots to talk about. It is, as mentioned, the biggest release in the history of the project. Not in numbers of line added, or patch count, but certainly in terms of contributor involvement, code reviews, code quality, and features. We’re not just a bunch of bored university students pushing unreviewed patches non-stop to the main branch anymore!

For the next few weeks, I’ll be writing more focused blog posts about the work I’ve done in Calendar this cycle. I’ve focused mostly on performance and reorganizing the internals of the application to be more resilient. It’s not glorious work, but I do love working on optimization problems!

GNOME Calendar will complete 15 years in a few months from now. The project is one of the few lucky projects in GNOME – and, I’d argue, in the free software scene in general – that has such a thriving community of contributors. It’s one of the few GNOME core apps that survived the great purge. It’s a super rare example of a GNOME app with a product manager.

It is also the project that brought me in in GNOME, so pardon me if I get a little emotional when I see the project thriving as it is, and think back of all the good friends that came and went, the hard lessons from maintaining it over over a third of my life, and the prospects for the future.

GNOME Calendar is entirely developed and maintained by volunteers. We have never received any kind of funding, be it corporate, from grants, or other forms of patronage. This gives us freedom from these kinds of influences (mostly to complain about how so many big companies fail to meet the calendaring standards that they themselves helped create), but the reality is that it is really damn hard to pitch for funds for a calendaring application.

Please consider donating to GNOME, or to the individual contributors of your choice. It makes a difference. All the difference.

In 1993, I stood at the top of the World Trade Center feeling like being on top of everything. It was the culmination of my first proper trip west, a stark contrast to a country behind an iron curtain or even a small-town Amherst, New Hampshire, where I had to earn my way into that adventure.

Many people can't wrap their heads around how such enormous buildings could collapse on September 11. What I can't wrap my head around is that they survived the first attack, which happened in February of '93, when I was, entirely oblivious to what had happened on the ground floor a few months earlier, soaking in those panoramic views.

The attack was carried out by a group of radicals led by mastermind Ramzi Yousef. In the underground parking garage of the North Tower, they detonated a yellow Ford van packed with explosives. It's often claimed that the terrorists used Czechoslovak Semtex, but in reality it was a massive, roughly 600-kilogram homemade explosive charge, further reinforced with pressurized hydrogen tanks. Semtex was only a trigger explosive.

The explosion was devastating. The blast tore a 30-meter crater through five floors of underground parking and damaged several support columns, though the main structural frame of the tower held. Though the tower didn't collapse as the terrorists had originally planned, the shockwave destroyed the main electrical wiring and emergency lighting, and smoke rose as high as the 93rd floor. Six people lost their lives and more than a thousand were injured, most from smoke inhalation during the grueling evacuation through dark stairwells. Operations in both towers were completely paralyzed and the complex had to be shut down for nearly a full month. Total damages and subsequent repairs cost roughly half a billion dollars.

Because of the '93 bombing, the Port Authority installed photoluminescent safety markings along the steps, landings, and handrails throughout the towers. When the planes struck eight years later and emergency lights flickered or failed, these glow-in-the-dark strips guided occupants downward. According to National Institute of Standards and Technology, 33% of survivors in the North Tower and 17% in the South Tower directly credited these markings with aiding their escape. The stairs were well-lit by battery-pack emergency lights and photoluminescent guides, and people moved much faster. Survivors who had been in the building during both attacks noted that the 2001 descent took roughly half the time it did in 1993.

I only know about all of this because of the internet — a firehose of news and dangers pouring at me every hour of every day. Could I stand up there today, soaking in those fantastic views, still so oblivious and happy?

Adobe has released an emergency fix for a Magento vulnerability that attackers are already using against online stores. Someone exploiting the flaw can make an affected store run code without first signing in. Adobe confirmed the attacks on Sep 8, 2026, one day after releasing the urgent hotfix.

Linux kernel testing can miss a bug when it depends on two tasks reaching the same data in an unusual order. These independently running tasks are called threads. A race condition occurs when their timing changes whether the code works correctly, which can make a failure difficult to reproduce. Google Project Zero published MAccConc on Sep 8, 2026 as a prototype that changes the timing itself. Its name is short for Memory Access Concurrency. The tool traces selected Linux kernel memory access...

A new Linux privilege escalation exploit shows how a cleanup mistake in Reliable Datagram Sockets, or RDS, can give a local user root access, meaning administrator control of the machine. RDS is a Linux kernel networking subsystem designed for low-latency communication between machines and processes.

Listing network routes should tell administrators where traffic will go. An IPv6 security report instead shows Linux accessing a freed record used to keep track of that listing. A list of active readers still points to the record after cleanup releases it, so a later route change can reach invalid memory and crash the kernel.

I’m looking at something entirely unrelated, but tripped over some search results that made me realise that a lot of people still think getting errors like ACPI Warning: SystemIO range 0x0000000000001828-0x000000000000182F conflicts with OpRegion 0x0000000000001800-0x000000000000187F indicate a firmware bug. This is generally untrue. We need to dive a little into what ACPI is to clarify why.

The Advanced Configuration and Power Interface1 specification defines a whole bunch of stuff, but what’s interesting to us here is the hardware abstraction it performs. While PCs are nominally a well-defined platform that’s really not true at the hardware level once you get beyond a certain level of complexity. When you suspend a system you want to power down the hardware in the correct order, for instance, and knowing what that order is requires you to know details about the specific motherboard design. The approach taken in the embedded world is to just bake that knowledge into the OS in some form, which is how we end up with Devicetree. ACPI takes an alternative approach - rather than provide that information as data that has to be consumed by OS drivers, it distributes it as code.

The ACPI Source Language, or ASL, is a simple language that gets compiled into a bytecode that’s then interpreted by the OS at runtime. One of the features of this language is the ability to define “Operation Regions”, effectively structure definitions that describe access to underlying hardware. Let’s imagine a simple device with two exposed registers. The first is an index register - it describes which internal register we want to access. The second is a data register, where reading it gives us the value of the internal register whose address is currently in the index register, and writing to it modifies that register. An example operation region declaration would look something like

1 2 3 4 5 6 OperationRegion(OPR1, SystemIO, 0x400, 0x2) Field(OPR1, ByteAcc, NoLock, Preserve) { INDX, 8 DATA, 8 }

This defines an operation region called “OPR1” at IO port 0x400, 2 bytes long. Inside it are two 8-bit fields, INDX and DATA. These are to be accessed one at a time, do not need the ACPI interpreter to take a global lock when accessing them, and if a subset of the register is modified then the other values should be preserved (irrelevant in this case since the fields are only a byte wide). Now any references to INDX or DATA in this scope will trigger accesses to those registers. So, a method to read the value of register 0x03 would look something like:

1 2 3 4 Method (RD03) { INDX = 0x3 Return (DATA) }

ie, set INDX to 3, and then read the value of DATA and return it. But! What if another ACPI method is running at the same time? Let’s say we have one that writes to register 0x05:

1 2 3 4 Method (WR05, 1) { INDX = 0x05 DATA = Arg1 }

What happens if RD03 executes while we’re part-way through WR05? INDX might get reset to 0x03, and now WR05 will modify register 0x03 instead of 0x05. Oh no! But we can avoid this - we declare a mutex (Mutex (MUTX, 0x00)), and update our methods to be something like:

1 2 3 4 5 6 7 8 9 10 11 12 13 14 Method (RD03) { Acquire (MUTX, 0xFFFF) INDX = 0x3 Local0 = DATA Release (MUTX) Return (Local0) } Method (WR05, 1) { Acquire (MUTX, 0xFFFF) INDX = 0x05 DATA = Arg1 Release (MUTX) }

Each method takes a lock (waiting up to 0xffff milliseconds and then erroring out if it doesn’t), and performs the access. There’s now no chance of a race. Phew!

Now suppose someone writes a Linux driver for this piece of hardware. It accesses the hardware directly, with no knowledge of ACPI. What stops the driver from racing against one of the ACPI access methods? Nothing at all. Oh no! Again! This isn’t hypothetical, by the way - here’s a relatively harmless example, but back in the day we did trip over cases where temperature monitoring chips would be accessed by the firmware and Linux simultaneously and as a result you might end up thinking you’re reading a temperature when you’re actually reading a status flag, resulting in an impossibly high temperature and an immediate thermal shutdown.

In this case, the kernel saves you from this (potentially hardware damaging) outcome by printing a message like ACPI Warning: SystemIO range 0x0000000000000400-0x000000000000401 conflicts with OpRegion 0x0000000000000400-0x0000000000000401 (OPR1), telling you that the kernel has detected that a driver is attempting to allocate IO ports 0x400-0x401, but that there’s an ACPI operation region called OPR1 that is claiming the same addresses. The kernel isn’t in a position to know what type of access the firmware might perform in that region, so assumes that it might be dangerous and blocks the driver from loading.

But all is not lost! The kernel also prints some helpful advice, ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver. And ACPI tables will often actually have a definition that looks like this:

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 Device (HDW1) { Name (_HID, "VEND0001") OperationRegion(OPR1, SystemIO, 0x400, 0x2) Field(OPR1, ByteAcc, NoLock, Preserve) { INDX, 8 DATA, 8 } Mutex (MUTX, 0) Method (RD03) { Acquire (MUTX, 0xFFFF) INDX = 0x3 Local0 = DATA Release (MUTX) Return (Local0) } Method (WR05, 1) { Acquire (MUTX, 0xFFFF) INDX = 0x05 DATA = Arg1 Release (MUTX) } }

which defines an ACPI device and associated methods. The _HID field defines the device type, and a Linux driver can be written that will be automatically loaded if a device with type VEND0001 is seen. That driver can then call ACPI methods associated with the device and access the resources in a way that matches the firmware’s expectations.

(Interested in writing such a driver? I wrote a guide back in 2009)

The firmware did absolutely nothing wrong here2, but trying to load the native ddriver will generate an error and the internet will tell you that PC firmware developers are incompetent3 and you should pass a kernel argument that overrides this behaviour and it never did them any harm, and it probably won’t do you any harm either but it might and you might never know why your system occasionally wedges or catches fire.

1. The ACPI spec used to live at acpi.info, but sadly that seems to have vanished some time after UEFI took over stewardship of the spec ↩︎

2. You might argue that the firmware should simply not do anything at runtime because it is not the firmware’s job to do that, and I do understand that and you can certainly boot with acpi=off if you want to and no ACPI code will be executed at runtime. Let me know how that goes. ↩︎

3. I’m not going to present an opinion on that here, merely say that this provides no supporting evidence for that assertion ↩︎

An anonymous reader quotes a report from Ars Technica: Those who remember PC gaming in the days before Steam may have fond memories of the "big box" packaging that made those games stand out as shelf eye candy and sought-after in-home collectibles. Today, PC gaming platform GOG is hoping to reignite some of the nostalgia for those days by adding downloadable 3D models and printable, foldable high-res packaging scans for a handful of PC games on the platform. Thus far, the "Printable Big Box" collection on GOG is limited to just five games: Armikrog, Descent, Hitman: Codename 47, Myst, and Star Trek: 25th Anniversary. Players browsing those games on the GOG store will now see "3D Boxes" listed among the included "Goodies" before purchase. Owners of those games on GOG can download a ZIP file containing a version of the box art as an animated 3D object file (in an easy-to-open GLB format) and a "flat printable template" in PDF, SVG, and Adobe Illustrator formats. Those downloads allow for what GOG calls "a proper papercraft project for anyone who misses shelves full of PC game boxes." The physically focused expansion of the existing GOG Preservation Program comes through a partnership with Benjamin Wimmer's Big Box Collection website, which has grown since 2015 to include over 1,000 3D scans from his private collection of physical PC games. In an interview with GOG, Wimmer said that while he appreciates the artistry of a good old-fashioned big box, he also appreciates their evolution into the "interactive cards" on modern digital storefronts that "provid[e] us art, screenshots, gameplay videos and whatnot and that not shown as a box, [it] is just good UX." "Physical media doesn't survive the way software can -- boxes get lost, crushed, thrown out," GOG writes in today's announcement. "Scanning them, and letting you print your own, is preservation in a different shape: the same mission that keeps these games running on modern PCs, applied to the objects they used to come in."

Read more of this story at Slashdot.

Version:next-20260909 (linux-next) Released:2026-09-09

The U.S. Department of Energy has approved a $1.9 billion loan to NextEra Energy to restart Iowa's shuttered Duane Arnold nuclear plant, which Google has backed as a power source for its growing AI infrastructure. "The sizable loan is the second of its kind, suggesting that the Trump administration views revived nuclear power as a key source of electricity for tech companies seeking to power their AI data centers," notes TechCrunch. From the report: James Danly, Deputy Secretary of Energy, said that the Iowa power plant's restart in 2029 will "drive down electricity costs," though he did not explain how. Just 50 megawatts will be set aside for the local power cooperative, NextEra CEO John Ketchum said during an earnings call (PDF) last year. That capacity would cover 18% of Iowa's demand growth since 2021, the year before ChatGPT was released. Google is reportedly looking to build up to six data centers near the Duane Arnold Energy Center, which hasn't operated since 2020 when an intense rainstorm damaged the power plant. Rather than repair it, NextEra decided to mothball it. At the time, cheap natural gas was flooding the market, making nuclear power economically unappealing. A lot has changed in the last six years, though. After decades of little growth in demand, the sudden rise of AI coupled with broader electrification of the economy meant that utilities and power providers were suddenly scrambling to find new generating sources of electricity. New data centers are expected to nearly triple the sector's electricity demand by 2035.

Read more of this story at Slashdot.

An anonymous reader quotes a report from The New York Times: OpenAIsaid on Tuesday that its newest artificial intelligence technology had solved one of the "Millennium Problems," a collection of important unanswered math questions meant to push the world's leading mathematicians to new heights. The announcement is an another clear sign that A.I. is fundamentally changing the upper reaches of mathematics, which have long been viewed as a pinnacle of human achievement. The change has excited some mathematicians, while stirring concern among others. Over the past year, A.I. systems successfully solved a wide range of problems that have bedeviled mathematicians for decades. But these problems were not as complex, nor as closely watched, as the one that OpenAI's technology has solved over the past several days. The Millennium Problems are among the most heavily researched in the field. "This is a spectacular culmination of the arc we have seen over the past twelve months," OpenAI researcher Sebastien Bubeck said of the company's new solution. The company announced that one of its latest models, which has not yet been released to the public, needed just 88 hours to solve what mathematicians call "the Navier-Stokes existence and smoothness problem." This problem involves a series of equations that are often used to predict the weather. The equations describe the movement of water and other fluids. The Navier-Stokes problem, which has no clear practical value, asks whether these equations completely break down in certain situations. OpenAI's proof claims to have defined just such a situation. This would imply, at least theoretically, that the laws of physics themselves would break down under certain conditions: that, for example, water could be made to spontaneously explode. But mathematicians and physicists do not believe that this mathematical breakdown could really lead to such an outcome in the physical world. The Navier-Stokes problem was one of seven "Millennium Problems" selected by the Clay Mathematics Institute in the year 2000 as a way of tracking the progress of mathematics in the new millennium. The institute, founded by an American businessman named Landon T. Clay, offered a million dollars for the first correct solution to each problem. Before OpenAI's announcement, only one of the problems had been solved. OpenAI says it managed to solve the Navier-Stokes problem by coordinating as many as 10,000 AI agents, an extremely expensive process that may have cost millions of dollars in computing power. For those curious about the findings, the company has released a paper (PDF) and formal Lean proof.

Read more of this story at Slashdot.

"Star Trek" marks its 60th anniversary today, September 8, six decades after the original series premiered in 1966 and went on to become one of the most successful science-fiction franchises in television history. Outlets across the web are commemorating the milestone with full health reports, hot takes, behind-the-scenes retrospectives, and reflections on the franchise's influence and what may lie ahead. The New York Times reports: As of 2026, the 60-year-old science fiction franchise boasts a fandom of carbon units -- sorry, humans -- that spans at least three generations. What began, in 1966, as a five-year space mission on the U.S.S. Enterprise to "boldly go where no man has gone before" now represents an anthology of space travel across more than 25 series and films in parts of two centuries. Where once it was James T. Kirk or bust, it's not unusual to find fans who prefer other captains, like Picard, Janeway or Sisko. There are so many series to keep track of that fans often communicate using country code-like abbreviations for each installment: TOS (the original series), TNG ("The Next Generation"), DS9 ("Deep Space Nine"), ENT ("Enterprise") and so on. Outside the Trekiverse, disparities in generational slang, politics and social mores are practically a foregone conclusion. But "Star Trek" functions as connective tissue between fans past and present. Some of that tissue is just shared references: There will always be captain's logs, timelines by stardate, warp factors one through 10, phasers and photon torpedoes and, every now and then, a doctor who insists, "I'm a doctor, not a ____!" The Vulcan salute has become a general symbol of geek-recognize-geek, but real Trekkies (or Trekkers, as some prefer) know that "Live long and prosper" is only half the message; the recipient is meant to say "Peace and long life" in response. But the series' staying power, and the ease with which each generation finds its way into them, is an indication that fans of all ages share not only language, but values, in common. Here are some of our favorite Slashdot stories from the early days. The 2004 "Should Star Trek Die?" is an especially good callback today because it features LeVar Burton (Geordi La Forge in Star Trek: The Next Generation) arguing that Trek needs to disappear for several years to become special again... Star Trek Lawsuit (1998) Salon Writes on The Troubles with "Trek" (1999) Star Trek's Next Series (2001) Should Star Trek Die? (2004) UPN Officially Cancels 'Star Trek: Enterprise' (2005)

Read more of this story at Slashdot.

Google says it will overhaul Search in Europe to comply with the EU's Digital Markets Act, giving more prominence to comparison services like Expedia and Hotels.com while stripping some real-time features from hotel, airline, and restaurant results. "These changes degrade the user experience for Europeans -- boosting online intermediaries at the expense of local businesses, and removing helpful features people rely on every day," said Nick Fox, senior vice-president of knowledge and information at Google. The company claims its past search changes for DMA compliance were tied to a 30% decrease "in free, direct booking traffic to European businesses." Engadget reports: That sanction was the latest salvo between the EU government and a US tech company for infringing on its Digital Markets Act. The debate centers on the DMA requirement that major tech brands "must not treat their own services more favorably in ranking than third-party services." [...] According to Reuters, Google's revised search results "will highlight one specialized search engine at the top of the page, followed by two others with fewer details. A carousel of hotels, airlines and restaurants, for example, will sit below them with key features such as real-time prices stripped out." Those specialized engines include sites like Expedia or Hotels.com, also known as vertical search services, so European users may soon see those aggregators and comparison sites prioritized more highly than individual businesses' websites in their results. Reuters noted that "the rankings will be determined by Google's algorithm," meaning the tech company still holds a lot of control over how results are displayed. The EC had given Google 60 days to comply with its rules, but the company has not specified an exact timeline for when European users will start seeing the changes.

Read more of this story at Slashdot.

The NSA, CISA, and FBI are accusing (PDF) several Chinese AI companies of carrying out "industrial-scale" distillation campaigns against leading U.S. models such as ChatGPT, Claude, Gemini, and Grok. Since at least 2024, the companies have allegedly routed millions of requests across accounts, APIs, proxies, cloud providers, and third-party aggregators to extract capabilities for their own models. "China-based artificial intelligence companies are conducting systematic extraction of proprietary functionalities and capabilities of U.S. AI companies' models through industrial-scale knowledge distillation campaigns that form the core -- not merely a supplement -- of their AI development strategy," the agencies wrote. CyberScoop reports: DeepSeek, for example, distilled frontier U.S. models to generate synthetic training data for its R1 and R3 models, including four different versions of Claude, two versions of Gemini, five versions of ChatGPT and Grok 4. Those models helped train DeepSeek's capabilities in areas like agentic functioning, question and answer optimization, creative and occupational writing and others. Another Chinese company, Moonshot AI, allegedly distilled 18 different U.S. models -- including Fable 5, Anthropic's current, most advanced commercially available model -- to train its Kimi-K2 and Kimi K3 models. The company used millions of queries meant to extract enhanced capabilities in areas like agentic reasoning, coding and data analysis, computer vision, larger logical frameworks, visual processing and others. Chinese AI companies manage a sophisticated set of tools and systems that route requests and prompts through multiple pathways to avoid detection. The advisory lists common tactics observed by Chinese companies, including spreading requests across different accounts, models and platforms, using native APIs, remote cloud providers, and third-party aggregators to obfuscate user metadata, and leveraging proxies and gray tech markets to get around geographic restrictions, terms of use and safeguards built into frontier models.

Read more of this story at Slashdot.

Meta has launched Muse, a personal AI agent developed under chief AI officer Alexandr Wang. "The product, long in development, was touted as a key next step by CEO Mark Zuckerberg in his recent 6,500-word manifesto," reports Axios. From the report: Muse, as the agent is known, exists in a chat interface, similar to a text thread. It's designed to be more proactive and long-running than typical chatbots. Users can name their agent, create an avatar and customize how it communicates. The Muse agent runs on a dedicated virtual machine in Meta's cloud, using a built-in browser that's visible to the user. Meta is offering a free tier of Muse, as well as two subscription options, at $20 per month and $100 per month. "For the vast majority of users, they should be able to do what they need to within the free tier," Wang told Axios. "But for real power users, you know, those subscription tiers help us cover the computer costs." There is no advertising within Muse, but Wang said the company is exploring commerce opportunities that could generate additional revenue. Initially Muse will be available in the U.S. and works on iOS, Android and the web, with support coming soon for Meta's AI glasses. "The full vision in the future is we want to develop personal superintelligence that helps people accomplish their goals, pursue their passions, build things that they never would have built if they didn't have the technology," Wang told Axios. Meta offers users more privacy controls with Muse than in its previous AI products, including the option to prevent queries from being used by Meta and a planned confidential mode where the company cannot see activity inside a user's virtual workspace. There's also an entirely separate system called Sentinel that governs Muse's access to the internet and connected services.

Read more of this story at Slashdot.

Australia is proposing the "My Feed, My Way" initiative that would force social media platforms to let users over 16 turn off algorithmic recommendations and instead see only posts from people and creators they follow. Platforms that fail to comply could face fines of up to $79 million. CNBC reports: The legislation, which is being drafted and released Tuesday for targeted consultation, would require platforms to send notifications to new and existing users so they can choose their default feed. [...] The measures, set to be introduced to the Parliament of Australia this year, will also require AI chatbots, online games and other digital services to take action to protect under-18s from addictive design features. "This is not about giving government control. It's about giving people control. It's about putting choice back into the hands of Australians online," said Prime Minister Anthony at a press conference on Tuesday. "This is sensible, pragmatic, practical reform. It gives users choice, and it will hold the big tech companies responsible for inaction."

Read more of this story at Slashdot.

Suppose an application setting has changed on a Linux server, but nobody remembers changing it. The application still works, and the usual health checks show no trouble. A record confirms that a file changed, yet says nothing about who changed it or why.

A Linux cgroup, or control group, limits how much memory a group of processes can use. Yet its counters can look normal while those processes cause the host kernel, the core of the operating system, to use memory that is not counted against their limit. A networking patch posted on Sep 7, 2026 shows one way this can happen with IPv6 multicast routing, which sends network traffic to a group of recipients. The test creates routing tables inside namespaces: separate views of user identities and ...

A program can keep a Linux file open even after the separate networking environment behind it has started shutting down. That environment is called a network namespace. A SUNRPC patch posted on Sep 7, 2026 describes that exact failure in the /proc/net/rpc/use-gss-proxy control used by Linux remote procedure call (RPC) servers, including Network File System (NFS), which lets computers access files over a network.

An anonymous reader quotes a report from TechCrunch: Telluride just managed one of its best-kept secrets in years, per The Hollywood Reporter. On Sunday night, festival-goers filed into a 650-seat theater with their phones locked away, having no idea what they were about to see, told only that it ran nearly three hours, hadn't been shown anywhere, and that its principal creators would be in the audience. The surprise premiere they went on to enjoy is a new documentary from co-directors Nathan Fielder and Lance Oppenheim about Theranos founder Elizabeth Holmes. Called "You Can See Everything," the film is said to capture Holmes and her husband, Billy Evans, in the 34 days before she reported to federal prison in May 2023 to begin an 11-year sentence for defrauding investors about her blood-testing technology. Since then, her legal fight has limped along without success. Her appeals to overturn the conviction and shorten her sentence were rejected in February of last year. She then went a different route last year, asking President Trump to commute her sentence. That clemency petition is still listed as pending, meaning it's officially been opened and remains under review. Fielder apparently lived in the couple's guest house during filming -- the access they provided sounds shocking -- but some of the buzz also ties to an A-list actress who becomes part of the story itself. A24 is set to release the film in October. You can watch a trailer for the film on YouTube.

Read more of this story at Slashdot.