/explore
|
You are here 
|
pointieststick.com | ||
| | | | |
blog.broulik.de
[AI summary] The blog post reflects on the early development of KDE Plasma 5, highlighting key milestones, user experiences, and the evolution of the desktop environment. It discusses the transition from Plasma 4 to Plasma 5, the introduction of features like audio indicators and draggable notifications, and the community's response. The author also shares personal anecdotes, such as the KDE 20th anniversary and the 'Getting Physical @ CERN' sprint, emphasizing the importance of user feedback and collaboration. The post concludes with appreciation for the KDE community and excitement for the future of Plasma 6. |
|
| | | | | ||
| | | | |
zamundaaa.github.io
In my last post about HDR and color management I explained roughly how color management works, what we're doing to make it work on Wayland and how far along we were with that in Plasma. That's more than half a year ago now, so let's take a look at what changed since then! |
|
| | | | | ||
| | | | |
ubuntuhandbook.org
[AI summary] Debian 13, codenamed 'trixie', is released with RISC-V support and dropped i386 architecture, featuring updated desktop environments and various software upgrades. |
|
| | | | | ||
| | | | |
dht.is
SOLVED posts detail solutions to problems I could not find anywhere else. After installing axe-cli in my Ubuntu/Windows 11 environment using Windows Subsystem for Linux (WSL), I got the following error whenever I tried to run it: Chrome failed to start: crashed (unknown error: DevToolsActivePort file doesn't exist) (The process started from chrome location [file path] is no longer running, so ChromeDriver is assuming that Chrome has crashed.) This can be caused by a lot of things (and I tried most of them), but in my case it was caused by Chrome not being installed in my WSL environment, which makes sense because I only use it for command line programs. |
|
| | | |||
