| 9 Jun 2026 |
 hexa | uhhh, so I'm considering making pkexec opt-in during this release cycle … aka tomorrow, this week, next week … very soon | 20:27:35 |
| hexa | can someone find out what in gnome, if anything, requires pkexec? | 20:27:43 |
| hexa | like what does it use in its elevation prompts? | 20:28:19 |
 K900 | Uhhh polkit is already off by default no? | 20:33:21 |
| K900 | Well enabled with GNOME I think | 20:33:29 |
| K900 | And other DEs | 20:33:39 |
 Capypara | I asked how to become maintainer a few times in the past and never really got anywhere | 20:43:59 |
| Capypara | I still have no idea how GNOME updates are supposed to be done properly | 20:44:14 |
| Capypara | or who is currently even maintaining it | 20:44:27 |
| Capypara | In reply to @hexa:lossy.network
can someone find out what in gnome, if anything, requires pkexec? gnome-initial-setup and gnome-settings use/used it, with efforts to eventually get rid of it according to people I asked. I can have a closer look tomorrow if they still do. | 20:47:33 |
| Capypara | did a quick look through the Github mirror of all gnome projects. g-i-s still uses it and so does gnome-system-monitor actually. And gvfs for admin://. And more. | 20:51:09 |
| hexa | ok, so I just opt into pkexec for gnome tor the time being and mention these consumers | 21:04:54 |
| hexa | other DEs too | 21:05:21 |
| hexa | I'll make you do the change for Plasma, enjoy :p | 21:53:08 |
| hexa | https://github.com/NixOS/nixpkgs/pull/530106 | 22:01:24 |
 winston | gnome-remote-desktop also uses pkexec, but its broken atm: https://github.com/NixOS/nixpkgs/pull/523122/changes#diff-c374f3bf676530fb1bff12bc0f6bae7249a91270c8fd922a3c3c95f24c75bd9a | 23:49:42 |
| winston | and gnome-system-monitor could be phased out for 51, replaced by Resources
https://www.phoronix.com/news/GNOME-51-Resources-Possible | 23:54:52 |
| hexa | I'll leave cleaning that up to you :) | 23:58:05 |
| 11 Jun 2026 |
|  dimothy joined the room. | 14:29:35 |
| 13 Jun 2026 |
|  l0b0 left the room. | 11:42:42 |
| 14 Jun 2026 |
 tom | GNOME 50.2 anyone? https://github.com/NixOS/nixpkgs/pull/530103 | 14:05:52 |
 @mcnesium:matrix.org | thanks for your interest and sorry for the delay. here is the output of sudo journalctl -b -1 . the login event starts at 15:56 and the error is on line 7316 | 14:13:01 |
|  @orzklv:floss.uz left the room. | 23:32:37 |
| 16 Jun 2026 |
| Capypara | What's the backport policy regarding GNOME? Should the 50.2 update be backported? what about the PR that fixes gdm, or are backports handled differently for GNOME? | 17:12:46 |
| Capypara | https://github.com/NixOS/nixpkgs/pull/517777
https://github.com/NixOS/nixpkgs/pull/521789
https://github.com/NixOS/nixpkgs/pull/530103
| 17:14:20 |
| Capypara | those two mentioned in the 50.2 PR already have a backport:
https://github.com/NixOS/nixpkgs/pull/524318
https://github.com/NixOS/nixpkgs/pull/530394 | 17:15:11 |
| Capypara | If those three PRs (or at least the GDM fixes) are ok to backport I'd label them? I'm just not sure if a minor GNOME update counts as breaking / how DE updates during a release are handled usually | 17:15:50 |
| Capypara | bobby285271Jan Tojnar
I'd like to help out maintaining GNOME, are any of you active and would be okay with that + maybe outline some steps to properly handle bigger updates - the last few times it was a bit chaotic, I think it would be good to have some solid documentation or maybe even some automation for some things. I think winstonwas also interested in helping out.
| 17:23:20 |
| winston | we should backport them to 26.05 afaik | 17:24:11 |
| Capypara | agree, i'll get an overview of PRs to core package since branch off and add the labels | 17:24:46 |
