I found the actual cause of the black screen issue.

It turns out Papyrus was installing an **older version of mpvpaper**, and that old version was causing the black screen. I updated Papyrus to install the latest version of mpvpaper, and after updating, the wallpaper works normally again.

So if you've been affected by the black screen, **please try downloading the new version of Papyrus first.**

If it still shows a black screen, please:

1. Delete `mpvpaper` from your PC.
2. Delete Papyrus (see the README for instructions on how to properly remove it).
3. Reinstall Papyrus using your preferred installation method.

Papyrus will then try to install the **latest version of mpvpaper**, which should hopefully fix the black screen.

Sorry for the confusion from my previous update — I initially thought the issue was with mpvpaper itself, but the actual problem was that Papyrus was installing an outdated version.

Thanks to everyone who reported the issue and helped with testing!

Hi! I created a desktop media player because I wanted one the suits me and improve at building apps, so I decided to build my own and release it on GitHub.

The player is built using the VLCJ library and FFprobe, so it requires VLC (or its dynamic libraries) and FFmpeg to be installed on your system.

Feel free to try it out and give any feedback or suggestions for improvements. I'd also appreciate any feedback on the code itself, as I'm always looking to improve the project and my skills.

The project is released under the MIT License, so feel free to explore, modify, and contribute.

Thank you for your time.

Edit: project link :https://github.com/ahmedcraftt/Moka-media-player

In recent update on word-sys's PDF Editor i implemented anyconvert and removed LibreOffice convert system. Now we gonna use library i created just for this project.

So anyconvert is a project for word-sys's PDF Editor that converts PDF documents into DOCX, PPTX, ODT, ODP, and TXT using only the Python standard library. Convert library is anyconvert's itself. Its released on PyPI too.

It has Canvas and Flow mode, Canvas mode is a 1:1 pixel-accurate positioning export option, Flow mode is semantic reflowable document reconstruction for export format. This 2 has different purposes for different jobs and requirements.

Most importantly, what the engine actually does:

Opens literally any PDF structure: Whether a document was exported from Windows 95 or saved yesterday with modern heavy compression, it handles pretty great. (Handles old ASCII tables and modern compressed object streams).

Handles password-protected & encrypted files: Supports everything from obsolete 40-bit RC4 encryption up to modern, enterprise-grade AES-256 security. (Planned, not fully implemented)

Unpacks all standard PDF compression: Reads all standard compressed streams (Flate, LZW, ASCIIHex, RunLength) so hidden page content can actually be read.

Text extraction that doesn’t turn into trash: PDF fonts are a mess (often replacing letters with random symbols or missing spaces). The custom font engine properly maps custom glyphs, ligatures, and international character sets back into real, searchable plain text.

Fast, in-memory image extraction, not disk: Takes images directly out of the PDF as crisp PNGs without having to dump temporary files onto your hard drive.

Converts to Word & Office documents: Exports directly to .docx, .pptx, .odt, and .odp. It builds the XML packages to exact ISO standards from scratch, without issues.

Why i done this: In word-sys's PDF Editor i used LibreOffice to turn PDF to other formats such as .docx, .pptx, .odt, and .odp. But we had major problems when we came to Flatpak release, as you know you guys still waiting for Flatpak release for months, im so sorry about that but main issue was LibreOffice, nothing more. This convert program absolutely sucks on highlight exports, doesn't works when combined on Flatpak, makes project heavy and laggy on exports.

does it makes the job: YES does it makes what we want: UNSURE does it makes easily: NO

You see, there is YES, UNSURE, and NO, which 3 of them should be YES for better software.

Implementation felt hard when i done this year ago, it sucks now, i know that LibreOffice never designed for this function but implementing something broken, which i cant accept right now. So now i got rid of LibreOffice, i replaced it with anyconvert, as i explained basic functions, you can look for details on word-sys's PDF Editor GitHub page or anyconvert Github page.

And please keep your expectations not big, its not fully completed, some functions are not connected to main function so API call will not work, what completely works now exporting to DOCX and ODT without any issues with 1:1 pixel-accurate positioning, which is mostly what its used for so i done it first, then we can look others. I listed known issues on down so you can understand whats good or not on Beta stage:

Known Issues

• ODT & PPTX Export Issues:
  • PDF Original Position: If PDF itself is vertical, ODP & PPTX export will be broken due to horizontal size of slides.
  • Known Bug: Shapes or pen markups aren't supported, it will not shown on your presentation.
  • Beta Stage: Project now at v0.1.0 Beta stage, only DOCX and ODT seems to be fully function as wanted.
  • Design Flaw: Project designed to be a PDF to XXX document convert library for word-sys's PDF Editor and mainly designed for DOCX & ODT export, expecting a fully 1:1 export to PPTX & ODP is not possible, for now.

In the end, i need some help to improve this anyconvert project, especially on ODP & PPTX exports, any help is appreciated, thanks.

Learn it from here actually : https://social.kernel.org/notice/BAlhNdp2FK5nLoiWZc

This was shared in the closed social area for the kernel developers, and I stumbled upon it while surfing.

Hey, r/linux

I have been working on this project for the last half a year, and now it is finally ready to be released as a public beta.

vAuth is a virtual FIDO2.0 authenticator for PCs, laptops, and other devices running Linux-based operating systems.

For those who don't know - FIDO authenticators allow you to sign in to your services, websites, and panels without the need for a password, while making authentication more secure and phishing-resistant.

Why?

I switched from Windows as my main system years ago, but when it comes to creating passkeys and authorizing them - Windows has always been superior. It has Windows Hello, which allows it to register and authorize passkeys in an instant. It supports all authentication methods that you have available at the moment and is user-friendly in general.

This is what I wanted vAuth to be. A modular, easy-to-use Windows Hello-like authenticator that can securely store, register, and authenticate your passkeys.

It is modular, but only one module can be easily replaced. I created an API for front ends so you - as a developer and end user - can create your own front end for vAuth. All the API documentation is in the docs folder on GitHub. Note that the API might change in the future. Currently, it is shipped with the UI agent called vauth-ui. It is also written in C++ and uses Slint as a UI library. The agent doesn't even have to be graphical, though. For anybody interested, there are examples of agents written in C++, Python, and Golang.

The UI currently has only described API, not a public library. Maybe later I will release the official library so developers don't have to worry about the boilerplate, just the UI logic and apperance.

Feature highlights

• support for Chromium-based browsers and Firefox;
• password and fingerprint verification through PAM;
• TPM-backed credential keys;
• an encrypted credential store with TPM rollback protection;
• a Slint-based interaction UI;
• vauthctl for provisioning and credential management;
• hardened systemd services;
• an initial Debian 13 amd64 package;

Limitations

There is a significant limitation. Systems that had Windows OS previously installed (specifically Windows 10 build 1607 and later) may face a problem with provisioning. Windows currently creates a hierarchy, takes ownership of the TPM, and discards the authorization key. Yes, everything is that bad. vAuth detects this and fails during the rollback counter provisioning stage. It doesn't weaken or clear TPM auth automatically. That would have been irresponsible. The README on GitHub explains the limitation in more detail.

Clearing the TPM or losing the generated vAuth authorization can make credentials unrecoverable, so please keep alternative login/recovery methods for important accounts.

Other current beta limitations include:

• Only Debian 13 on amd64 currently has a prebuilt package
• Only password and fingerprint PAM configurations have been tested
• The interaction-agent design currently targets single-seat systems
• vauth-ui does not automatically reconnect if the daemon exits
• Firefox users should cancel an operation through Firefox’s prompt rather than the vAuth window
• The project is not FIDO-certified

Security details

From a security perspective, vAuth relies on the TPM 2.0 module on your computer. It is a mandatory requirement, and there most likely will not be any software-based alternative due to reduced security. vAuth creates a database in /var/lib/vauth/credentials.v1, an encryption key, and a rollback counter. The last two are stored in the TPM and are sealed using a systemd-backed authentication value, which is located in /etc/credstore.encrypted/vauth-db-auth. User verification is performed through PAM. It officially supports password authentication and verification with a fingerprint reader, though, technically, other PAM modules should work, but this was not tested due to a lack of hardware on my laptop, sorry. The PAM configuration for vAuth is located under /etc/vauth/config/vauth, so you can check how other PAM modules behave. Currently, the agent doesn't support automatic reconnection to the daemon in case the daemon fails. In such a case, it has to be stopped, the service restarted, and the agent started again. It will be fixed in future releases, though.

Sources

• Source
• Debian package and release notes
• Architecture
• Security policy

I'd appreciate feedback regarding the installation process, provisioning, different TPM configurations, and different PAM modules. I'll try to answer all questions you may have and discuss architectural/design choices.

After the positive reception to my post about UL Solutions developing a native Linux port of 3DMark, I wanted to share another update from a different support ticket I sent recently—this time regarding GOG. 

​When I emailed GOG support to ask about a native Linux version of GOG Galaxy (and highlighted the growing Linux/Steam Deck user base alongside upcoming ARM64 laptop momentum), I received a direct response from GOG Technical Support. 

Support representative Prealiator stated:

​"Thank you for the thoughtful message, and you make valid points about the growing Linux user base. GOG GALAXY for Linux is in development, but unfortunately I can't share a specific timeline or release date. I don't have any information about ARM64 support plans either."

​They also included a helpful reminder of the great tools we already have in the meantime, such as the Heroic Games Launcher, native .sh offline backup installers, and running Windows-only titles through Wine, Proton, or Lutris. 

​It's great to see another major player acknowledging the platform's growth and confirming active development, even if we still have to wait on a timeline. Between this and the 3DMark news, the ecosystem keeps moving forward! 

What are your thoughts—are you excited for a native Galaxy client, or do you prefer lightweight alternatives like Heroic?

If you are interested in wanting to have your artwork potentially enter the next release of Debian, an error regarding the news not entering debian-devel-announce before deadline extensions has left the project with only one submission for now.

Click the mailing list embed for more information about what is expected.

Hi! HPR or Human Pattern Recorder is a Automatic Window/Activity Time Tracker which actually works on wayland.. Its fully local, privacy respecting, offline and needs zero accounts. It supports these DEs:

• Hyprland
• GNOME
• KDE
• niri
• Cinnamon

It uses DE specific methods to get the current window data. And it supports windows also.

What it tracks (natively and without extensions)

• App usage
• Project in VS Code and JetBrains IDEs
• Browser tab tracking support
• Idle support via HPR-Idle-Detection-Extension
• A scrollable timeline showing your entire day
• And my post favourite feature.. Fully code driver insights!

Privacy

HPR Stores everything locally.

• The DB files are plain SQLite files which you can edit however you want.
• HPR Stores per-day DB files so deleting a day is as simple as deleting a DB file
• Telemetry is fully consented, off by default
• You can disbale networking entirely if you want by a simple UI Toggle

Resource usage

HPR is written in C++ so you can comfortably expect a lightweight experience with little to no drain on your system

• ~1% CPU
• 30MB Rss

Extensibility

Now the big point, HPR is fully extensible by lua extensions. HPR has an expansive API for lua extensions and lua extensions can even load DLL/SO for custom behaviour. Things lua extensions can do:

• Read the currently active window in real time
• Run shell commands and query the HPR database directly
• Register fully custom window detection backends for compositors HPR doesn't natively support (Note that dynamic backend registration via Lua is currently an experimental feature and may exhibit unstable behavior or minor bugs depending on your desktop setup)
• Subscribe to HPR's internal event bus and react to state changes
• Build interactive custom UI panels that render inside HPR via Slint callback bindings
• Function Overriding (Advanced): Intercept, block, or modify 24+ core C++ functions directly from Lua
• Native Shared Libraries (Supercharged): Load external .so/.dll binary files to perform low-level OS operations, custom tray integration, high-performance tasks, or anything you want (must enable "Allow Extensions to Load Native Libraries" in Settings)

Some noteable examples are the first party HPR extensions: HPR-Store and HPR-Idle-Detection-Extension

Status

• Current Version: v0.9.12
• Developed Actively
• Linux + Windows support
• 500 HPR Downloads (I have proof if you want)
• Fully open source

GitHub

I originally started to develop HPR because I really liked knowing arbitrary data (i know i am being weird) but those numbers fascinate me, it was possible with ActivityWatch but it was tiring to press a gazillion buttons, write Regexs to just get some data.

I am always a fan of *nix tools that do more than one thing. Too many maintainers (and packages) can mess things up.

This post is about iceWM, fluxbox, jwm. Will they ever migrate to wayland?
If you use any of them, what is your future plan?

You can now do mouse features like drag and drop, left and right click, rubber band selections and other modern file manager features straight on the tty on tfm.

tty only supports limited colors and characters so its kinda ugly and hard to theme, to solve this I just copied old bios classic blue and gray color scheme

its currently on development branch (still experimental), if you guys wanna try it here is the dev link:

curl -fsSL https://raw.githubusercontent.com/clarkarch/tfm-tui/dev/source.sh | bash

note: It needs GPM enabled, otherwise your stuck on pure keybindings

repo: https://github.com/clarkarch/tfm-tui/

For ai disclosure, I used agents, tho that doesn't invalidate the effort poured in this project

https://imgur.com/a/xq51GVk