Lots of cleaning advice, but let me add this bit: If you crack it open and use a can of air on it, unplug the CPU fan first. Super easy if you’ve gone that far.
Honestly, I haven’t explored Vulkan yet. I initially chose GLES 2.0 as the primary renderer to ensure compatibility with a wide range of hardware. Introducing Vulkan myself would be a time-consuming task unless I receive assistance.
Regarding XWayland, Louvre doesn’t currently support it, so it’s naturally excluded. Well, it technically can run in rootful mode, but that is somewhat pointless. To enable independent window management, I believe I would need to create a mini X server, a task I haven’t tackled as of now.
Probably all of them have better Vulkan than opengl drivers (due to drivers being simpler). David Arlie rather quickly implemented first Vulkan driver for AMD once Vulkan was first released. Just in case you need incentive.
I was thinking of starting something similar as a learning exercise, but I’m really limited in time and not skilled as much in c++, so it would probably lead nowhere. Now I can just build on top - if I get any time for this, will come probably with questions.
Anyway, this idea was to make something modern. Without the legacy crap. Actual goals were:
Vulkan only (move gfx API Info the future)
no x/xwayland (most of the apps in newer toolkits already support Wayland, the others I’d rather avoid)
Interesting, I don’t recall where I read about Vulkan support still being experimental in many Mesa drivers; it might have been an outdated post. I’ll look into it, and perhaps I’ll decide to dive into learning Vulkan. Additionally, there are buffer-sharing mechanisms that already work smoothly with GLES, so I need to explore if the situation is similar for Vulkan. Thanks for your response, and if you have the time and inclination to help include it, feel free to do so! 😄
The operating system in use shouldn’t be a factor. Consider opening your laptop to perform a thorough cleaning, and also consider replacing the thermal paste as well. If you’re not comfortable doing this yourself, taking it to a repair shop is a viable option. Investing in a cooling stand for the laptop would also be beneficial…
Replacing the thermal paste is essential. It dries out over time and stops conducting heat effectively. Cleaning the fans and radiator fins is important too. Takes an hour or so if you don’t know what you’re doing so shouldn’t take long. I’ve kept my laptop going for years by doing that every 2 years or so.
Fedora Sericea is my current daily driver. Loving it so far. I’ve used Sway, River, and Hyprland on Arch, Fedora, and NixOS. The combination of an immutable system augmented by flatpaks and distrobox are supporting my goal to never wipe the drive again.
Sway is more stable and lightweight for me than Hyprland. I don’t use Nvidia hardware at all. The lead Dev on Hyprland is a treasure though. 10/10 for that human being.
There’s desperate need to a library that’s simpler to use than wlroots or smithay - but unless it supports more protocols (later shell, gamma control, session lock), I don’t think this is a real a alternative yet.
I was thinking similar, though I'm also still on X with nVidia and XFCE and am in a weird way* with programming.
I have my own custom XFWM theme that is really minimal (12px title with 8px tall buttons with some being wider to compensate, somewhat outdated example) and I'd like to expand upon it (floating titles, inset window buttons, dynamic button width, media integration) but I've looked at examples and don't understand enough to even get just a rectangle for a titlebar (though X I assume for something basic, X would probably still be the easiest).
*= the only language that I'm interested in (due to it being easy in a style I like while still having performance/capability/flexibility etc) is not popular, and worse is I have lost a bit of hope/confidence in its future (as well as its bus factor reducing further because the person who made the package manager+installer and a book walked away) so I still haven't really done much with it.
I've asked about this on the Fediverse once already and didn't get any responses.
Also note that bindings for Godot 4.X (or some other not-superheavy Linux-compatible engine that has an editor especially) are a big part of what I want, so some specifics that may work on paper otherwise might not fit the bill either. Also because polygonal art (meme made with 3.X, 4.0 eye animation, not-yet-in-4.X test of someone elses' PR)
I completely agree. I invest time in implementing protocols within the library, allowing it to handle many tasks autonomously, thus relieving developers from manually wiring everything themselves—without compromising flexibility oc. Regarding “later shell,” did you mean “layer shell”? Developers can certainly still implement protocols not included with Louvre on their own, but that’s not quite the intended approach.
Birdtray sounds like what you’re looking for. It allows you to close Thunderbird to the system tray so that it runs in the background. Thunderbird already throws notifications to GNOME, and should continue to do so while running in the background in the way.
We used to run firewalls running Fedora at work, works fine. Issue is you’re only getting 6 months of updates, best to look at Rocky Linux for something that doesn’t change much if you do anything beyond a single program.
anedotally: it works fine if it’s from a vendor who provides support for it. eg cumulus switches running fedora 9 but still getting updates from cumulus engineers.
How do you handle which GPU is used in which game? I would guess you have an AMD iGPU, and a Nvidia GPU for games, right? Maybe something along those lines got updated?
That’s correct, but i mostly let the laptop handle it, unless i know for a fact that a game needs/doesn’t need the N GPU, in which case i either manually switch it over or (and this is the case for wine apps through bottles) i configure the program to only use the iGPU
The dock is rendered directly by the compositor in one of the examples; it’s not an external application as it ideally should be. It doesn’t rely on any intricate protocols or systemd services to monitor the states of apps. I added it solely for demonstration purposes.
I’m with you. One day I was like “I wonder if Wayland’s mature enough to use as my daily driver now” and installed Sway on a Raspberry Pi. I used DWM before, but now Sway’s my default.
The only issue I still have is that I wish Zoom and ffmpeg supported the wlroots-specific screen capture methods. Those are the only things lacking that are keeping me on i3/X11 on the machine I use for work.
A dumb idea that probably doesn't have an implementation: Set Thunderbird to play a sound on mail arrival, but have the sound file actually be a pipe that when read from also pushes a system notification. This is kind of like how randomised .signature files were often set up in the old days.
Other alternatives: 1: There might be a purely mail checker out there that can log into mail servers to see if there's new mail there but not be able to read or download it.
2: Run your own mail server that pulls mail from other servers. Then it's "merely" a matter of checking for file update times on your own machine. Ancient tools like xbiff were designed for this.
linux
Newest
This magazine is from a federated server and may be incomplete. Browse more on the original instance.