Adrian Vovk

Working on GNOME stuff at Red Hat. GNOME OS developer. GNOME Release Team member. GNOME Board Director. Previously GNOME STF contractor

Opinions are my own, and not representative of my employer, or of the GNOME project, or of the GNOME board

Last Notes

2026-06-30 17:34:13 GMT

- reply

@nprofile…uptt @nprofile…zx6n Seems like this is manufacturers cheaping out
They made a pact that they'd all add these reminders so that people remember to check the seats. The idea was that they'd have sensors to check occupancy. But many manufacturers didn't end up adding the sensors (cost?). So now we have useless alerts that happen on every shutdown instead
Apparently in 30% of these cases the kids are in the car w/o parent knowledge, so a reminder won't help
Source: https://www.kidsandcars.org/news/carmakers-agree-to-add-rear-seat-reminders-to-prevent-deaths-in-hot-cars

2026-05-23 23:44:52 GMT

Another day in Linux: everyone's too busy squabbling over init systems to organize against the real enemy: Microsoft, Apple, and Google
Look I don't expect everyone to be strategic with their use of their own time. Do whatever you want. But to hurl vitriol at the people who are focused on making Linux win rather than on your chosen issue is not appropriate
If you're out here calling people bad faith corpo shills you should take a good hard look in the mirror and realize who your behavior helps

2026-03-19 12:12:14 GMT

- reply

@nprofile…6z3g Sounds like a solution to the FOSS sustainability problem to me! Thanks crypto bros. Ship it!
The other approach I've once been pitched is having your project sell its own crypto tokens (like a stock I guess?) and that would raise enough money to solve the sustainability issues 😬

2025-06-10 22:49:11 GMT

I wrote a thing: "Introducing stronger dependencies on systemd"
https://blogs.gnome.org/adrianvovk/2025/06/10/gnome-systemd-dependencies/

2025-03-19 00:10:19 GMT

- reply

@nprofile…w4zq Congratulations, Cassidy! Happy to have you on board

2024-12-27 00:31:38 GMT

- reply

@nprofile…dhdt @nprofile…dyk4 You'll be happy to hear that we're making plans to implement this in #GNOME
Apps will be able to make use of this to save their state and restore it after a session reset. The desktop environment would make an effort to include window management metadata like position, workspaces, etc. As long as apps support the feature it should work just like on macOS
Of course not all apps will support the feature, but we'll probably be able to remember at least that they were running

2024-12-10 19:39:33 GMT

https://www.howtogeek.com/why-i-want-to-see-an-official-gnome-only-os/

2024-11-13 16:53:10 GMT

- reply

@npub12f7…lkxh There's some difficulties here. The OEMs will have to basically give Qualcomm a good reason to do it, otherwise it won't happen.
Google can do it because they control the silicon and can run at the hypervisor execution context. Qualcomm devices run a proprietary Qualcomm hypervisor, that's signed, so we can't actually run VMs there.
Idk if the benefits of KVM are obviously clear enough that OEMs will actually spend the time to integrate it. Except for Google, that is

2024-10-25 01:26:22 GMT

Time to make it official! I want to turn #GNOME OS, GNOME's home-grown distro for testing and development of the GNOME Desktop, into a real production-ready general purpose OS. I finally blogged about it: https://blogs.gnome.org/adrianvovk/2024/10/25/a-desktop-for-all/

2024-03-15 16:36:27 GMT

- reply

@npub1u8h…a8dn @npub188q…3jlx TikTok also needs some time to properly profile you... If you don't use it all that often (because the content sucks) then they don't really know all that much about you so they fall back to the defaults: young male located in western-European country = "sigma male" content, American right-wing politics, Reddit stories, etc
There's definitely great content on TikTok, but it's also an echo chamber, indiscriminately promotes whatever makes them money, and is a time sink

2023-12-10 17:00:40 GMT

- reply

@npub1d76…897u I don't think anything like that is ready quite yet
You may want to look into the mold linker; it's multi-threaded so it should go a bit faster. Disable LTO. Don't build in release mode. Disable optimizations. This all is probably pretty difficult to do with the "press play in Builder" workflow I'm assuming you're used to.
Also keep in mind many of these things will make the program you're testing slower. Sometimes noticeably.
Or just wait... Rust's comp times are improving recently