orchard1
1 ●1 ●1 ●2

Hi all,

I have two monitors. When I restart my PC, it duplicates the vlew from one monitor to the other. I have these commands near the beginning of my .i3/config:

exec --no-startup-id /usr/bin/xrandr --output DVI-I-3 --left-of DVI-I-2
exec --no-startup-id /usr/bin/xrandr --output DVI-I-3 --primary

although they don't seem to execute. If I copy-paste them into a terminal, it works properly. Is there something wrong with the commands and if not, what can I do to fix it? Is there additional logging I should look at?

Thanks!

EDIT: To answer Airblader's question, using i3-dump-log | grep xrandr only seems to echo out the config, and not mention the execution of xrandr:

❯ i3-dump-log | grep xrandr
06/14/2015 03:10:12 PM - config_parser.c:parse_config:313 - CONFIG(line  38):         #xrandr -q                                  <-- list of monitors
06/14/2015 03:10:12 PM - config_parser.c:parse_config:313 - CONFIG(line  39):         #xrandr --output DVI-I-3 --left-of DVI-I-2  <-- moves DVI-I-3
06/14/2015 03:10:12 PM - config_parser.c:parse_config:313 - CONFIG(line  40):     exec --no-startup-id /usr/bin/xrandr --output DVI-I-3 --left-of DVI-I-2
06/14/2015 03:10:12 PM - config_parser.c:parse_config:313 - CONFIG(line  41):     exec --no-startup-id /usr/bin/xrandr --output DVI-I-3 --primary

edit retag flag offensive close merge delete

Comments

You talk about additional logging – what logging *have* you looked at and what did you see? By the way, specifying the full path to xrandr isn't necessary (usually) because exec will be passed to a shell.

Airblader ( 2015-06-09 05:58:48 +0000 )edit

Given your edit, can you please restart i3 in-place with no windows or anything up and then save the output of i3-dump-log somewhere (just to keep the file small) and upload it?

Airblader ( 2015-06-14 19:27:30 +0000 )edit

I've the very same problem... did found a solution for this?