Just wanted to mention that I remember having the same thing on Debian
wheezy, although I did not look at the logs and it went away when I moved
to Ubuntu 12/14. I also did revamp my config at the same, so it could have
been related to that.

On Sat, Jul 4, 2015 at 8:28 AM, Eric Duncan <eduncan...@gmail.com> wrote:

> i3 version 4.10.2 (2015-04-16, branch "4.10.2")
>
> Though it doesn't matter - been like this ever since I started using i3wm
> on Debian (6, 7, and Testing), Ubuntu (14.04, 14.10, 15.04) and Arch for
> over a year.
>
> Maybe I am missing a configuration parameter...
>
> On Sat, Jul 4, 2015 at 6:19 AM, Michael Stapelberg <mich...@i3wm.org>
> wrote:
>
>> Which version of i3 are you using?
>>
>> On Sat, Jul 4, 2015 at 6:34 AM, Eric Duncan <eduncan...@gmail.com> wrote:
>>
>>> So, been using i3wm for a bit over a year across multiple distros
>>> (Debian6, 7 and Testing; Ubuntu 14.04, 14.10 and 15.04; now Arch).
>>>
>>> When pressing MOD+R to reload i3wm, it's always annoyed me that it
>>> doesn't keep my terminal layouts (usually stacks them on the screen I am
>>> on).
>>>
>>> Today while monitoring journalctl, I noticed some interesting logs:
>>>
>>> Jul 04 00:27:30 river /usr/lib/gdm/gdm-x-session[1200]: 07/04/2015
>>> 12:27:30 AM - ERROR: mkdir(/run/user/1000/i3) failed: File exists
>>> Jul 04 00:27:30 river /usr/lib/gdm/gdm-x-session[1200]: [libi3]
>>> libi3/font.c Using Pango font Segoe UI, size 10
>>> Jul 04 00:27:30 river /usr/lib/gdm/gdm-x-session[1200]: [libi3]
>>> libi3/font.c X11 root window dictates 96.252632 DPI
>>> Jul 04 00:27:30 river /usr/lib/gdm/gdm-x-session[1200]: Exiting due to
>>> signal.
>>> Jul 04 00:27:30 river /usr/lib/gdm/gdm-x-session[1200]: 07/04/2015
>>> 12:27:30 AM - ERROR: Could not create "/run/user/1000/i3" for storing the
>>> restart layout, layout will be lost.
>>>
>>> It says that this file exists:
>>>
>>> /run/user/1000/i3
>>>
>>> And indeed this directory does.
>>>
>>> Could this be the bane of my annoyances?
>>>
>>>
>>>
>>
>>
>> --
>> Best regards,
>> Michael
>>
>
>

Reply via email to