| 28 Apr 2023 |
SigmaSquadron | You need GNOME 44, which is currently only available on NixOS 23.05. Switch to the unstable channel and upgrade your system. | 21:42:54 |
Jeff | yep, already on unstable. fully up to date as of a few minutes ago | 21:45:25 |
Jeff | I think that I may have found the answer... https://www.reddit.com/r/gnome/comments/12ydvct/background_apps_feature_not_working_in_gnome_44/ | 21:45:47 |
Jeff | Looks like it only works with things that were installed as flatpaks | 21:46:05 |
Jeff | If that's true, it's annoying as heck as I don't need flatpak on NixOS | 21:47:10 |
uep | wtf | 22:05:50 |
Jan Tojnar | Jeff: yeah, support for non-flatpak apps is not currently implemented https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/3699 | 23:19:54 |
| 29 Apr 2023 |
| @dchoi:matrix.org joined the room. | 10:30:00 |
| @dchoi:matrix.org changed their display name from dchoi to Danche Choi. | 11:00:09 |
| @dchoi:matrix.org left the room. | 19:58:17 |
| 1 May 2023 |
vcunat | FYI geary fails: https://github.com/NixOS/nixpkgs/pull/227907#issuecomment-1529439976 | 07:33:07 |
vcunat | (I don't know if it's considered an important package.) | 07:33:34 |
vcunat | Probably fixed by https://github.com/NixOS/nixpkgs/pull/228476/commits/82cea11923906492263ea968ccd986a01238b5d9 | 08:14:11 |
| @micah.ilbery:matrix.org left the room. | 21:50:16 |
| 4 May 2023 |
| @mrtuxy:matrix.org left the room. | 10:13:32 |
| David A. Buser (boozedog) joined the room. | 15:06:37 |
| @dre:imad.nyc joined the room. | 21:22:29 |
ElvishJerricco | So this extension only claims to be compatible with gnome 43. But it seems simple enough that it would likely work with gnome 44, right? Is there a way with nix to gnome to let me use it?
https://github.com/Nova1545/gnome-shell-extension-customreboot | 23:05:54 |
ElvishJerricco | * So this extension only claims to be compatible with gnome 43. But it seems simple enough that it would likely work with gnome 44, right? Is there a way with nix to force gnome to let me use it?
https://github.com/Nova1545/gnome-shell-extension-customreboot | 23:06:05 |
ElvishJerricco | (or if anyone knows a better extension to use) | 23:07:04 |
ElvishJerricco | Well, this allows the extension to at least show up and "work":
pkgs.gnomeExtensions.custom-reboot.overrideAttrs (old: {
postInstall = ''
${old.postInstall or ""}
sed -i 's/43/44/' $out/share/gnome-shell/extensions/customreboot@nova1545/metadata.json
'';
})
But it doesn't actually do what it's supposed to do. The menu of boot options it can show me is empty and I don't see any messages in journalctl
| 23:19:44 |
uep | a more general option: gsettings set org.gnome.shell disable-extension-version-validation "true" | 23:49:54 |
uep | (which you can, of course, set declaratively via nix if you want) | 23:59:29 |
| 5 May 2023 |
ElvishJerricco | well, after some patching because the code isn't quite right, the list is too long and it doesn't scroll so it's useless anyway :P | 00:05:59 |
ElvishJerricco | diff --git a/systemdBoot.js b/systemdBoot.js
index 22c2054..9599b0f 100644
--- a/systemdBoot.js
+++ b/systemdBoot.js
@@ -49,7 +49,7 @@ async function getBootOptions() {
Utils._log(`bootctl list: ${status}\n${stdout}\n${stderr}`);
let lines = String(stdout).split('\n');
let titleRx = /(?<=title:\s+).+/;
- let idRx = /(?<=id:\s+).+/;
+ let idRx = /(?<=id:\s+)(?<!machine-id:\s+).+/;
let defaultRx = /\(default\)/;
let titles = [];
let ids = []
@@ -99,7 +99,7 @@ async function getBootOptions() {
async function setBootOption(id) {
try {
let [status, stdout, stderr] = await Utils.execCommand(
- ['/usr/bin/pkexec', '/usr/sbin/bootctl', 'set-oneshot', id],
+ ['/run/wrappers/bin/pkexec', '/run/current-system/sw/bin/bootctl', 'set-oneshot', id],
);
if (status !== 0)
throw new String(`Failed to set boot option to ${id}:\nExitCode: ${status}\nstdout: ${stdout}\nstderr: ${stderr}`);
@@ -109,4 +109,4 @@ async function setBootOption(id) {
Utils._logWarning(e);
return false;
}
-}
\ No newline at end of file
+}
diff --git a/utils.js b/utils.js
index d39baec..7d44513 100644
--- a/utils.js
+++ b/utils.js
@@ -48,7 +48,7 @@ const BootLoaderClass = {
* Returns the path of the bootctl binary or an empty string if not found
*/
function getBootctlPath() {
- let paths = ["/usr/sbin/bootctl", "/usr/bin/bootctl"];
+ let paths = ["/run/current-system/sw/bin/bootctl"];
let file;
@@ -191,4 +191,4 @@ function _log(msg) {
function _logWarning(msg) {
if(DEBUG)
log(`CustomReboot WARN: ${msg}`);
-}
\ No newline at end of file
+}
Here's the patches I used. If anyone knows how to make the menu scroll, maybe I'll use it :P
| 00:06:49 |
ElvishJerricco | oh, guess I indented bad | 00:07:00 |
Jan Tojnar | In reply to @elvishjerricco:matrix.org well, after some patching because the code isn't quite right, the list is too long and it doesn't scroll so it's useless anyway :P It looks like the only scrollable element is PopupSubMenu, if you do not want to muck with the actor tree too much:
--- a/extension.js
+++ b/extension.js
@@ -47,7 +47,9 @@ class RebootQuickMenu extends QuickSettings.QuickMenuToggle {
// Set Menu Header
this.menu.setHeader('system-reboot-symbolic', 'Boot Options',
'Reboot into the selected entry');
-
+
+ this.menu.actor.style = `max-height: 500px;`;
+
// Add boot options to menu
this.createBootMenu();
}
@@ -62,10 +64,10 @@ class RebootQuickMenu extends QuickSettings.QuickMenuToggle {
// Get boot options
const bootloader = Utils.getCurrentBootloader().getBootOptions().then(([bootOps, defaultOpt]) => {
if (bootOps !== undefined) {
- this._itemsSection = new PopupMenu.PopupMenuSection();
+ this._itemsSection = new PopupMenu.PopupSubMenuMenuItem('Reboot into…');
let x = 0;
bootOps.forEach((title, id) => {
- this._itemsSection.addAction(String(title), () => {
+ this._itemsSection.menu.addAction(String(title), () => {
// Get bootloader and set reboot option
Utils.getCurrentBootloader().setBootOption(String(id)).then(result => {
if (result) {
| 13:29:23 |
Jan Tojnar | also relevant https://gjs.guide/extensions/upgrading/gnome-shell-44.html | 13:30:04 |
| 6 May 2023 |
| @vector1dev:vector1.dev joined the room. | 10:17:01 |
@vector1dev:vector1.dev | Hello! Is it possible to somehow configure monitors through home-manager? | 10:18:00 |