Custom guid.conf settings appear to be ignored

[Claudia]

I tried to increase my startup timeout in guid.conf according to https://www.qubes-os.org/doc/config-files/ , but no matter what I change it to, the desktop notification still says cannot start after "60" seconds and `time qvm-start ...` still reports about a minute. Interestingly, the commented out value of 45, which is presumably the hardcoded default, doesn't seem to be correct either. Nothing I've tried changes the reported nor actual wait time to anything other than 60 seconds, even after a reboot. Also, qvm-start doesn't complain even if I intentionally introduce a syntax error. It's like I'm editing the wrong file. Any ideas?

/etc/qubes/guid.conf

# Sample configuration file for Qubes GUI daemon
# For syntax go http://www.hyperrealm.com/libconfig/libconfig_manual.html

global: {
# default values
#allow_fullscreen = false;
#allow_utf8_titles = false;
#secure_copy_sequence = "Ctrl-Shift-c";
#secure_paste_sequence = "Ctrl-Shift-v";
#windows_count_limit = 500;
#audio_low_latency = true;
# see man qubes-guid
#trayicon_mode = "border1";
#startup_timeout = 45;
startup_timeout = 120;
};

# most of setting can be set per-VM basis

VM: {
work: {
#allow_utf8_titles = true;
};
};

[awokd]

Claudia:

> I tried to increase my startup timeout in guid.conf according to https://www.qubes-os.org/doc/config-files/

Are you looking for qvm-prefs [vmname] qrexec_timeout? I wonder if that
value was for Qubes 3.2.

--
- don't top post
Mailing list etiquette:
- trim quoted reply to only relevant portions
- when possible, copy and paste text instead of screenshots

[Claudia]

February 1, 2020 7:21 PM, "awokd' via qubes-users" <qubes...@googlegroups.com> wrote:

> Claudia:
>
>> I tried to increase my startup timeout in guid.conf according to
>> https://www.qubes-os.org/doc/config-files
>

> Are you looking for qvm-prefs [vmname] qrexec_timeout? I wonder if that
> value was for Qubes 3.2.

That seems to have done the trick. Thanks! I've seen the guid.conf method a few places, and I thought I saw it semi-recently on the mailing list. Also I looked at the qubes-guid code a few days ago and it looked like startup_timeout was still there. Who knows.