General/display/keyboard settings revert to default after reboot

Hello, I've been using Garuda and the I3 version as my daily driver for the last 3 months, and honestly it's been a really great experience. It's saved me a ton of time, and it has for the most part just worked perfectly "out of the box" as one would expect. There is however one issue I can't seem to get past, and it's starting to get a bit annoying.

Things like monitor settings, keyboard settings etc has to be reset after reboot.
I have 2 monitors, everytime I start my computer I have to positioned the top monitor to placed abvoe the main monitor, and not on the right.

Keyboard settings, I work with a pretty low Repeat Delay/Repeat Interval, and everytime I reboot those settings are not applied anymore. However if I open up the options, my last settings are still "there" and by tweaking it by 1, I get my values back.

As well as something like the Garuda welcome assistant. HAving disabled the "Show at start up", it'll still show at start up, until I just removed it from the i3 cfg.

Hope anyone has some tips or pointers to get this resolved! Other than that, fantastic software, thanks to everyone involved!

Without any system info, there is no issue...
Post info as explained in wiki

3 Likes

Output of inxi, i don't know what log i'd look at for an issue like this.

System:    Kernel: 5.11.2-zen1-1-zen x86_64 bits: 64 compiler: gcc v: 10.2.1
           parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-zen root=UUID=90a1fa0d-46ad-42c8-bae2-5d7b6d29613a rw
           [email protected] quiet splash rd.udev.log_priority=3 vt.global_cursor_default=0
           systemd.unified_cgroup_hierarchy=1 loglevel=3
           Desktop: i3 4.19.1 info: polybar dm: LightDM 1.30.0 Distro: Garuda Linux
Machine:   Type: Desktop System: ASUS product: N/A v: N/A serial: <filter>
           Mobo: ASUSTeK model: ROG STRIX B550-F GAMING (WI-FI) v: Rev X.0x serial: <filter> UEFI: American Megatrends v: 1401
           date: 12/03/2020
CPU:       Info: 8-Core model: AMD Ryzen 7 5800X bits: 64 type: MT MCP arch: Zen 3 family: 19 (25) model-id: 21 (33)
           stepping: N/A microcode: A201009 L2 cache: 4 MiB
           flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm bogomips: 121601
           Speed: 3113 MHz min/max: 2200/5437 MHz boost: disabled Core speeds (MHz): 1: 3113 2: 3571 3: 3329 4: 3369 5: 3253
           6: 3378 7: 3474 8: 3147 9: 3641 10: 3499 11: 3298 12: 3568 13: 3332 14: 3487 15: 3262 16: 3344
           Vulnerabilities: Type: itlb_multihit status: Not affected
           Type: l1tf status: Not affected
           Type: mds status: Not affected
           Type: meltdown status: Not affected
           Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via prctl and seccomp
           Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization
           Type: spectre_v2 mitigation: Full AMD retpoline, IBPB: conditional, IBRS_FW, STIBP: always-on, RSB filling
           Type: srbds status: Not affected
           Type: tsx_async_abort status: Not affected
Graphics:  Device-1: NVIDIA GM204 [GeForce GTX 980] vendor: ASUSTeK driver: nvidia v: 460.56 alternate: nouveau,nvidia_drm
           bus ID: 06:00.0 chip ID: 10de:13c0 class ID: 0300
           Display: x11 server: X.Org 1.20.10 compositor: picom v: git-dac85 driver: loaded: nvidia display ID: :0 screens: 1
           Screen-1: 0 s-res: 3440x2520 s-dpi: 107 s-size: 817x598mm (32.2x23.5") s-diag: 1012mm (39.9")
           Monitor-1: HDMI-0 res: 1920x1080 hz: 60
           Monitor-2: DP-0 res: 3440x1440 dpi: 109 size: 798x335mm (31.4x13.2") diag: 865mm (34.1")
           OpenGL: renderer: GeForce GTX 980/PCIe/SSE2 v: 4.6.0 NVIDIA 460.56 direct render: Yes
Audio:     Device-1: NVIDIA GM204 High Definition Audio vendor: ASUSTeK driver: snd_hda_intel v: kernel bus ID: 06:00.1
           chip ID: 10de:0fbb class ID: 0403
           Device-2: Advanced Micro Devices [AMD] Starship/Matisse HD Audio vendor: ASUSTeK driver: snd_hda_intel v: kernel
           bus ID: 08:00.4 chip ID: 1022:1487 class ID: 0403
           Device-3: Sunplus Innovation FHD Camera Microphone type: USB driver: snd-usb-audio,uvcvideo bus ID: 3-1.2.3:6
           chip ID: 1bcf:28c4 class ID: 0102 serial: <filter>
           Device-4: Blue Microphones Yeti Nano type: USB driver: hid-generic,snd-usb-audio,usbhid bus ID: 3-1.2.4:7
           chip ID: b58e:0005 class ID: 0300 serial: <filter>
           Sound Server: ALSA v: k5.11.2-zen1-1-zen
Network:   Device-1: Intel Wi-Fi 6 AX200 driver: iwlwifi v: kernel bus ID: 04:00.0 chip ID: 8086:2723 class ID: 0280
           IF: wlp4s0 state: up mac: <filter>
           Device-2: Intel Ethernet I225-V vendor: ASUSTeK driver: igc v: kernel port: N/A bus ID: 05:00.0 chip ID: 8086:15f3
           class ID: 0200
           IF: enp5s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
           IF-ID-1: br-438da786c9d3 state: up speed: 10000 Mbps duplex: unknown mac: <filter>
           IF-ID-2: br-666bfa29cd0b state: down mac: <filter>
           IF-ID-3: br-d8a8d2fc4346 state: down mac: <filter>
           IF-ID-4: docker0 state: down mac: <filter>
           IF-ID-5: ip_vti0 state: down mac: <filter>
           IF-ID-6: ppp0 state: unknown speed: N/A duplex: N/A mac: N/A
           IF-ID-7: veth7ec001a state: up speed: 10000 Mbps duplex: full mac: <filter>
           IF-ID-8: vethd8cfe87 state: up speed: 10000 Mbps duplex: full mac: <filter>
Bluetooth: Device-1: Intel AX200 Bluetooth type: USB driver: btusb v: 0.8 bus ID: 1-5:2 chip ID: 8087:0029 class ID: e001
           Message: Required tool hciconfig not installed. Check --recommends
Drives:    Local Storage: total: 5.89 TiB used: 1.57 TiB (26.6%)
           SMART Message: Required tool smartctl not installed. Check --recommends
           ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Samsung model: SSD 970 EVO 1TB size: 931.51 GiB block size:
           physical: 512 B logical: 512 B speed: 31.6 Gb/s lanes: 4 rotation: SSD serial: <filter> rev: 2B2QEXE7 temp: 43.9 C
           scheme: GPT
           ID-2: /dev/sda maj-min: 8:0 vendor: SanDisk model: SSD PLUS 480 GB size: 447.14 GiB block size: physical: 512 B
           logical: 512 B speed: 6.0 Gb/s rotation: SSD serial: <filter> rev: 00RL scheme: GPT
           ID-3: /dev/sdb maj-min: 8:16 type: USB vendor: Western Digital model: WD50NMZM-59A8XS1 size: 4.55 TiB block size:
           physical: 4096 B logical: 512 B rotation: 5400 rpm serial: <filter> rev: 2005 scheme: GPT
Partition: ID-1: / raw size: 931.02 GiB size: 931.02 GiB (100.00%) used: 325.78 GiB (35.0%) fs: btrfs dev: /dev/nvme0n1p1
           maj-min: 259:1
           ID-2: /boot/efi raw size: 500 MiB size: 499 MiB (99.80%) used: 580 KiB (0.1%) fs: vfat dev: /dev/nvme0n1p2
           maj-min: 259:2
           ID-3: /home raw size: 931.02 GiB size: 931.02 GiB (100.00%) used: 325.78 GiB (35.0%) fs: btrfs dev: /dev/nvme0n1p1
           maj-min: 259:1
           ID-4: /var/log raw size: 931.02 GiB size: 931.02 GiB (100.00%) used: 325.78 GiB (35.0%) fs: btrfs
           dev: /dev/nvme0n1p1 maj-min: 259:1
           ID-5: /var/tmp raw size: 931.02 GiB size: 931.02 GiB (100.00%) used: 325.78 GiB (35.0%) fs: btrfs
           dev: /dev/nvme0n1p1 maj-min: 259:1
Swap:      Kernel: swappiness: 10 (default 60) cache pressure: 75 (default 100)
           ID-1: swap-1 type: zram size: 1.96 GiB used: 256 KiB (0.0%) priority: 32767 dev: /dev/zram0
           ID-2: swap-2 type: zram size: 1.96 GiB used: 256 KiB (0.0%) priority: 32767 dev: /dev/zram1
           ID-3: swap-3 type: zram size: 1.96 GiB used: 256 KiB (0.0%) priority: 32767 dev: /dev/zram2
           ID-4: swap-4 type: zram size: 1.96 GiB used: 256 KiB (0.0%) priority: 32767 dev: /dev/zram3
           ID-5: swap-5 type: zram size: 1.96 GiB used: 256 KiB (0.0%) priority: 32767 dev: /dev/zram4
           ID-6: swap-6 type: zram size: 1.96 GiB used: 256 KiB (0.0%) priority: 32767 dev: /dev/zram5
           ID-7: swap-7 type: zram size: 1.96 GiB used: 256 KiB (0.0%) priority: 32767 dev: /dev/zram6
           ID-8: swap-8 type: zram size: 1.96 GiB used: 256 KiB (0.0%) priority: 32767 dev: /dev/zram7
           ID-9: swap-9 type: zram size: 1.96 GiB used: 256 KiB (0.0%) priority: 32767 dev: /dev/zram8
           ID-10: swap-10 type: zram size: 1.96 GiB used: 256 KiB (0.0%) priority: 32767 dev: /dev/zram9
           ID-11: swap-11 type: zram size: 1.96 GiB used: 256 KiB (0.0%) priority: 32767 dev: /dev/zram10
           ID-12: swap-12 type: zram size: 1.96 GiB used: 256 KiB (0.0%) priority: 32767 dev: /dev/zram11
           ID-13: swap-13 type: zram size: 1.96 GiB used: 256 KiB (0.0%) priority: 32767 dev: /dev/zram12
           ID-14: swap-14 type: zram size: 1.96 GiB used: 256 KiB (0.0%) priority: 32767 dev: /dev/zram13
           ID-15: swap-15 type: zram size: 1.96 GiB used: 256 KiB (0.0%) priority: 32767 dev: /dev/zram14
           ID-16: swap-16 type: zram size: 1.96 GiB used: 256 KiB (0.0%) priority: 32767 dev: /dev/zram15
Sensors:   System Temperatures: cpu: 61.6 C mobo: N/A gpu: nvidia temp: 63 C
           Fan Speeds (RPM): N/A gpu: nvidia fan: 30%
Info:      Processes: 429 Uptime: 1h 37m wakeups: 0 Memory: 31.33 GiB used: 19.42 GiB (62.0%) Init: systemd v: 247 Compilers:
           gcc: 10.2.0 Packages: pacman: 1619 lib: 482 Shell: Zsh v: 5.8 running in: alacritty inxi: 3.3.01

Search by issue. You have several.
I am no i3 user, but I assume/remember i3 uses an xrandr command to auto-start proper (user configured) display settings.

What is this "my options" for an i3 session?

2 Likes

Garuda Settings Manager.
As I understand it, that's a software GUI the distro offers as a convenience? If this cannot persist changes to the system, is this not an qualifying issue in it self?

Understand me correctly, I can configure these things manually and through the terminal. And if that's the answer, that's the route i'll go.

If someone could be so kind to point me in the direction to debug the Garuda Settings manager, I can even check that out.

This seemed like an either obvious thing I might have overlooked, or a tedious issue with the prepackaged apps the distros provides.

You have chosen i3 for your environment.
I suppose you haven't looked for the User's Manual.
I thought it 's the 1st thing someone would do.
You should have a look inside this file.

$HOME/.config/i3/config
# i3 config file (v4)
# Please see http://i3wm.org/docs/userguide.html for a complete reference!
2 Likes

I'm not claiming this to be an I3 issue. I'm well ad-versed with my window-manager and my environment.
Let me try to clarify, if that helps, the provided GUI tools that comes bundled with the i3wm version of Garuda can only apply settings, they are not saved to be persistent through reboots, or the machine being turned off. That is what I'm experiencing. I already counter some of this in the i3 file and apply certain settings when it starts..

But when the distro offers GUI tools to change a subset of settings, would it not be appropriate to report an instance where they don't do the job they're described to do?

I understand that I can configure it manually like any other arch installation. Garuda happen to just provide an option for some, which in my instance, doesn't work.

For some, not for all.
i3 is a Window Manager with a config to ... configure it.
Standard Garuda utilities are for major DEs and compatible setups.
Although I am no i3 expert (or user) I suppose you need to handle i3 config, like normal i3 configuration.
No miracles yet in Garuda Planet... :man_shrugging: Wrong speculations/expectations on Garuda utilities... unless I am wrong...

2 Likes

Are you loging in to guest uset ?

3 Likes

No, but that would be the expected behavior of a guest user!

If you want to find out anything,

Waiting for some Crystal Ball magician will have no result (for you).
And as I usually say:
No logs == No issue

2 Likes

The more detail you give us here such as logs, steps taken thus far, etc. helps us help you - more importantly, it helps others coming after to search and find things more easily.

It's a win-win really. We reap what we sow. Plant seeds for the future.

1 Like

Linux newbie here. I have the same issue with the GUI app.
How can I change this settings permanent manually?
What logs do you need?
Using Garuda i3

You would be better opening your own topic and post your problem as this is very out dated.
Also post your

garuda-inxi

As this helps the developers and forum member to help you

3 Likes

Welcome to the forums @Tekla .

TilliDie 's answer is correct. :slight_smile:

I closed this old topic.