Hi Ian,
Ian Campbell i...@hellion.org.uk writes:
This is bug #653327, not in i3.
BTW, I wonder what you think of including an i3-debug.desktop in the
i3-dbg package with the shmlogging enabled? Might be convenient?
At first glance, that is a good idea. However, since in the next version
we
On Sat, 2013-07-06 at 12:10 +0200, Michael Stapelberg wrote:
Hi Ian,
Ian Campbell i...@hellion.org.uk writes:
This is bug #653327, not in i3.
BTW, I wonder what you think of including an i3-debug.desktop in the
i3-dbg package with the shmlogging enabled? Might be convenient?
At first
On Sun, 2013-06-30 at 11:06 +0200, Michael Stapelberg wrote:
Could you upgrade to 4.5.1? You can do that without logging out.
FYI I am now running 4.5.1-2 with the --shmlog-size=26214400, will let
you/the bug know if I see this crash again.
BTW, the problem I had before which prevented me from
Hi Ian,
Ian Campbell i...@hellion.org.uk writes:
BTW, the problem I had before which prevented me from enabling
--shmlog-size is that after editing i3.desktop to have Exec=i3
--shmlog-size=26214400 gdm3 would fail with Cannot exec 'i3
--shmlog-size=26214400' (or words to that affect.
I
On Thu, 2013-07-04 at 22:47 +0200, Michael Stapelberg wrote:
Hi Ian,
Ian Campbell i...@hellion.org.uk writes:
BTW, the problem I had before which prevented me from enabling
--shmlog-size is that after editing i3.desktop to have Exec=i3
--shmlog-size=26214400 gdm3 would fail with Cannot
Hi Ian,
Just FYI:
I cannot act on the updated information you provided, since there still
is no log.
Debugging an i3 problem without a log is a super-tedious thing which I
am not willing to do. Especially if it’s for an ancient version, such as
4.2.
Could you upgrade to 4.5.1? You can do that
On Sun, 2013-06-30 at 11:06 +0200, Michael Stapelberg wrote:
Hi Ian,
Just FYI:
I cannot act on the updated information you provided, since there still
is no log.
Understood. I figured it was better to give whatever information I had
than nothing, I quite understand if this bug languishes
On Sun, 2013-05-26 at 08:00 +0100, Ian Campbell wrote:
On Sat, 2013-05-25 at 17:34 +0200, Michael Stapelberg wrote:
Hi Ian,
As you mentioned, without i3-wm-dbg installed, the backtrace is not
going to help. Can you still reproduce that problem/does it still
happen?
It still happens
On Sat, 2013-05-25 at 17:34 +0200, Michael Stapelberg wrote:
Hi Ian,
As you mentioned, without i3-wm-dbg installed, the backtrace is not
going to help. Can you still reproduce that problem/does it still
happen?
It still happens occasionally but not regularly. I had an instance last
week but
Hi Ian,
Ian Campbell i...@hellion.org.uk writes:
Done, although I'd have to logout for it to take affect -- is there a
way to enable at runtime?
No, not for the release versions. Debug versions (anything built from
git) have shared memory logging enabled by default.
--
Best regards,
Michael
Hi Ian,
As you mentioned, without i3-wm-dbg installed, the backtrace is not
going to help. Can you still reproduce that problem/does it still
happen?
Also see http://i3wm.org/docs/debugging.html for how to enable logging,
that might be helpful in figuring out what is going on.
--
Best regards,
Package: i3-wm
Version: 4.2-1
Severity: important
Dear Maintainer,
i3-wm has crashed on me a couple of times over the last day. The most recent
time I thought to look in .xsession-errors and found:
*** glibc detected *** i3: corrupted double-linked list: 0x00c31530 ***
===
12 matches
Mail list logo
