Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

running i3-msg restart and using the restart keybind afterwards leads to crash of i3 #3765

Open
mdnghtman opened this issue Aug 12, 2019 · 4 comments

Comments

@mdnghtman
Copy link

commented Aug 12, 2019

I'm submitting a…

[x] Bug
[ ] Feature Request
[ ] Documentation Request
[ ] Other (Please describe in detail)

Current Behavior

i3 crashes.

Expected Behavior

i3 shouldn't crash. Bug doesn't arise with i3 4.16.1.

Reproduction Instructions

Add "i3-msg restart" into i3 config or initiate it manually inside a terminal. Then use the keybinding to restart i3.

Environment

Binary i3 version: 4.17 (04.08.2019) © 2009 Michael Stapelberg and contributors
Running i3 version: 4.17 (04.08.2019) (pid 14188) abort…)
Loaded i3 config: /home/midnight/.config/i3/config (Last modified: Mo 12 Aug 2019 23:51:04 CEST, 6520 seconds ago)

The i3 binary you just called: /usr/bin/i3
The i3 binary you are running: i3



Logfile URL: https://logs.i3wm.org/logs/5638105096781824.bz2
- Linux Distribution & Version: Arch Linux
- Are you using a compositor (e.g., xcompmgr or compton): compton (definitely unrelated though)

@i3bot i3bot added the bug label Aug 12, 2019

@i3bot

This comment has been minimized.

Copy link

commented Aug 12, 2019

I don’t see a link to logs.i3wm.org. Did you follow https://i3wm.org/docs/debugging.html? (In case you actually provided a link to a logfile, please ignore me.)

@3ach

This comment has been minimized.

Copy link

commented Aug 12, 2019

Seems like this is probably a duplicate of my issue #3764 but mine only occurs when I am using my displaylink dock.

@3ach

This comment has been minimized.

Copy link

commented Aug 12, 2019

We think it might be something to do with multiple monitors!

orestisfl added a commit to orestisfl/i3 that referenced this issue Aug 13, 2019

Move content for non-existing outputs
Probably fixes various related issues:
Closes i3#2276
Closes i3#2459
Closes i3#2936
Closes i3#3764
Closes i3#3765
Closes i3#3766

Tested using
bindsym $mod+Shift+i exec xrandr --output DVI-D-0 --mode 1920x1080 --pos 0x0 --rotate normal --output DVI-I-1 --off, restart

The core issue here is that the JSON read during a restart might contain
invalid outputs when the new process is done reading it.
@orestisfl orestisfl referenced a pull request that will close this issue Aug 13, 2019

orestisfl added a commit to orestisfl/i3 that referenced this issue Aug 13, 2019

Move content for non-existing output containers
Probably fixes various related issues:
Closes i3#2276
Closes i3#2459
Closes i3#2936
Closes i3#3764
Closes i3#3765
Closes i3#3766

Tested using
bindsym $mod+Shift+i exec xrandr --output DVI-D-0 --mode 1920x1080 --pos 0x0 --rotate normal --output DVI-I-1 --off, restart

The core issue here is that the JSON read during a restart might contain
invalid outputs when the new process is done reading it.
@robclancy

This comment has been minimized.

Copy link

commented Aug 14, 2019

I have been getting crashes recently. I use multiple monitors.

pantherman594 added a commit to pantherman594/i3 that referenced this issue Aug 18, 2019

@pantherman594 pantherman594 referenced a pull request that will close this issue Aug 18, 2019

pantherman594 added a commit to pantherman594/i3 that referenced this issue Aug 18, 2019

pantherman594 added a commit to pantherman594/i3 that referenced this issue Aug 18, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
4 participants
You can’t perform that action at this time.