Join GitHub today
Config file gets overwritten with xrandr changes #3513
I'm submitting a…
[x] Bug [ ] Feature Request [ ] Documentation Request [ ] Other (Please describe in detail)
I have spent some time in the last day or so configuring i3 (for the first time, happy to be here). I am using bumblebee-status, and the xrandr module. Long story short, when I disable or enable a monitor using that module, my screens momentarily flicker (similar to reloading the configuration) and the configuration looks like the one from yesterday. When I look at the file I was editing (~/.config/i3/config), sure enough it's the old text file. I just tried it again, and I am sure that disabling and enabling the second monitor is causing it to remove the changes to that file. It's weird that it's not the default, it's reverting to the file I made yestereday.
It might have trouble, it might crash, but if it's going to clobber my config file, it had better keep a copy...
I don't know xrandr well enough, but I know that when I click on DP-6.8 to turn on or off that monitor, the settings to back to the ones I had a few days ago. I immediately change the theme to solarized-powerline, save, alt+shift+r to reload, then click on the DP-6.8 to turn off the monitor, and my file is reverted and the status line is back to solarized.
i3 --moreversion 2>&- Binary i3 version: 4.16 (2018-11-04) © 2009 Michael Stapelberg and contributors Running i3 version: 4.16 (2018-11-04) (pid 2540)o abort…) Loaded i3 config: /home/jeffe/.config/i3/config (Last modified: Thu 08 Nov 2018 04:18:44 PM MST, 146 seconds ago) The i3 binary you just called: /usr/bin/i3 The i3 binary you are running: i3
I'll look into making that next.
- Linux Distribution & Version: Ubuntu 16.04 - Are you using a compositor (e.g., xcompmgr or compton): No.
Also, this is the source for the xrandr module: https://github.com/tobi-wan-kenobi/bumblebee-status/blob/master/bumblebee/modules/xrandr.py
It also calls this script: https://github.com/tobi-wan-kenobi/bumblebee-status/blob/master/bin/toggle-display.sh
The end result looks (to me) like it's calling
I haven't ever used auditctl. That will come in handy. But I figured it out, and you're right, it is not i3, it's the bumblebee-status's xrandr module. The toggle-display.sh calls this script:
And look at the first thing it does:
Why? I think they are thinking there is some monitor specific configurations, but it's not in the documentation I've seen... Thanks for looking at this issue with me.