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 occasionally but not regularly. I had an instance last
> week but I stupidly forgot to gather a backtrace. I'll see if I can
> provoke it with vncviewer next week when I'm back at my desk.
I forgot to poke but I just got a spontaneous instance of the issue.
In .xsession-errors I get:
03/06/13 14:50:59 - ERROR: X11 Error received! sequence 0x34e7,
error_code = 3
03/06/13 14:50:59 - ERROR: X11 Error received! sequence 0x34e8,
error_code = 3
03/06/13 14:51:01 - ERROR: X11 Error received! sequence 0x358f,
error_code = 3
03/06/13 14:51:01 - ERROR: X11 Error received! sequence 0x3590,
error_code = 3
03/06/13 14:51:18 - ERROR: No state found
i3: src/x.c:79: state_for_frame: Assertion `0' failed.
This isn't exactly the same as the previous linked-list corruption,
although I suppose memory corruption is also plausible in this instance.
Attaching with gdb I got:
(gdb) bt
#0 0x00007f94057a31a0 in __poll_nocancel () at
../sysdeps/unix/syscall-template.S:81
#1 0x00007f94070391c2 in _xcb_conn_wait (c=c@entry=0xb036e0,
cond=cond@entry=0xb03720, vector=vector@entry=0x0, count=count@entry=0x0) at
../../src/xcb_conn.c:400
#2 0x00007f940703a93f in xcb_wait_for_event (c=0xb036e0) at
../../src/xcb_in.c:517
#3 0x0000000000429344 in handle_signal (sig=<optimized out>, info=<optimized
out>, data=<optimized out>) at src/sighandler.c:181
#4 <signal handler called>
#5 0x00007f94056fb295 in __GI_raise (sig=sig@entry=6) at
../nptl/sysdeps/unix/sysv/linux/raise.c:56
#6 0x00007f94056fe438 in __GI_abort () at abort.c:90
#7 0x00007f94056f4322 in __assert_fail_base (fmt=0x7f9405831a40 "%s%s%s:%u:
%s%sAssertion `%s' failed.\n%n", assertion=assertion@entry=0x4537b2 "0",
file=file@entry=0x44eafa "src/x.c", line=line@entry=79,
function=function@entry=0x44f0c0 "state_for_frame") at assert.c:92
#8 0x00007f94056f43d2 in __GI___assert_fail
(assertion=assertion@entry=0x4537b2 "0", file=file@entry=0x44eafa "src/x.c",
line=line@entry=79, function=function@entry=0x44f0c0 "state_for_frame") at
assert.c:101
#9 0x0000000000423ef2 in state_for_frame (window=<optimized out>) at src/x.c:79
#10 state_for_frame (window=<optimized out>) at src/x.c:71
#11 0x000000000042523c in x_push_node (con=con@entry=0xc35490) at src/x.c:567
#12 0x0000000000419f6c in drag_window_callback (con=0xc35490,
old_rect=<optimized out>, new_x=<optimized out>, new_y=<optimized out>,
extra=<optimized out>) at src/floating.c:368
#13 0x000000000041aa9d in drag_pointer (con=con@entry=0xc35490,
event=event@entry=0xc2e830, confine_to=confine_to@entry=0,
border=border@entry=BORDER_TOP, callback=callback@entry=0x419f40
<drag_window_callback>, extra=extra@entry=0xc2e830)
at src/floating.c:571
#14 0x000000000041abf5 in floating_drag_window (con=con@entry=0xc35490,
event=event@entry=0xc2e830) at src/floating.c:390
#15 0x0000000000428bc7 in route_click (con=0xc34c00, event=0xc2e830,
mod_pressed=true, dest=CLICK_INSIDE) at src/click.c:256
#16 0x0000000000428def in handle_button_press (event=event@entry=0xc2e830) at
src/click.c:325
#17 0x000000000042b020 in handle_event (type=<optimized out>,
event=event@entry=0xc2e830) at src/handlers.c:1068
#18 0x000000000042bcac in xcb_check_cb (loop=<optimized out>, w=<optimized
out>, revents=<optimized out>) at src/main.c:137
#19 0x00007f9405ebd66f in ev_invoke_pending () from /usr/lib/libev.so.4
#20 0x00007f9405ec06f5 in ev_run () from /usr/lib/libev.so.4
#21 0x000000000040894d in ev_loop (flags=0, loop=<optimized out>) at
/usr/include/ev.h:820
#22 main (argc=<optimized out>, argv=<optimized out>) at src/main.c:836
> > Also see http://i3wm.org/docs/debugging.html for how to enable logging,
> > that might be helpful in figuring out what is going on.
>
> Done, although I'd have to logout for it to take affect
I don't think this had applied, since I hadn't logged out. Since I
restarted with 'r' in the crash dialog window I expect it hasn't taken
hold yet either.
Ian.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
