found 531310 3.2.1-1
tags 531310 -moreinfo
thanks

Coin,

I found this bug after a recent upgrade. At this time i decided to postponed the upgrade to 3.3, because of the necessary big configuration changes, so it was on hold. I suspected awesome 3.2 could not work well with new libs and finally upgraded, and go the same problem. In fact, launching anything, via awesome or not (using a console, setting DISPLAY, and running any X app), caused the crash (segfault).

Here is the backtrace:
#0  0xb7fc8424 in __kernel_vsyscall ()
#1  0xb7a50680 in *__GI_raise (sig=6)
    at ../nptl/sysdeps/unix/sysv/linux/raise.c:64
#2  0xb7a53d68 in *__GI_abort () at abort.c:88
#3  0xb7a89abd in __libc_message (do_abort=2,
    fmt=0xb7b681c8 "*** glibc detected *** %s: %s: 0x%s ***n")
    at ../sysdeps/unix/sysv/linux/libc_fatal.c:173
#4  0xb7a941d4 in malloc_printerr (action=2,
    str=0xb7b650c4 "free(): invalid pointer", ptr=0x9a94b98) at malloc.c:5994
#5  0xb7a96186 in *__GI___libc_free (mem=0x9a94b98) at malloc.c:3625
#6  0xb7d1eebe in xcb_get_wm_size_hints_reply ()
   from /usr/lib/libxcb-icccm.so.1
#7  0xb7d1ef02 in xcb_get_wm_normal_hints_reply ()
   from /usr/lib/libxcb-icccm.so.1
#8  0x0806034f in property_update_wm_normal_hints (c=0x9a949ec, reply=0x0)
    at /home/duck/Packaging/awesome/awesome-3.3~rc4/property.c:128
#9  0x080582a8 in client_manage (w=12582920, wgeom=0x9a8bf68, phys_screen=0,
startup=false) at /home/duck/Packaging/awesome/awesome-3.3~rc4/client.c:509
#10 0x0805d8ae in event_handle_maprequest (data=0x0, connection=0x987f058,
    ev=0x9a942d0) at /home/duck/Packaging/awesome/awesome-3.3~rc4/event.c:645
#11 0xb7d0bef4 in xcb_event_handle () from /usr/lib/libxcb-event.so.1
#12 0x0805314e in a_xcb_check_cb (loop=0xb7c165c0, w=0xbffe3f18, revents=32768)
    at /home/duck/Packaging/awesome/awesome-3.3~rc4/awesome.c:203
#13 0xb7c12cdb in ev_loop () from /usr/lib/libev.so.3
#14 0x08053b17 in main (argc=1, argv=0xbffe3fe4)
    at /home/duck/Packaging/awesome/awesome-3.3~rc4/awesome.c:536

I guess the recent XCB libs upgrades are at fault, but i'd let you reassign to the right package, as you know XCB better than me.

This said, thanks for your good work on awesome :-). If you need more information, running tests, ... feel free to ask me by mail or on IRC ("Duck" on freenode/OFTC/...).

Regards.

--
Marc Dequènes (Duck)

Attachment: pgpL73FyURH3e.pgp
Description: PGP Digital Signature

Reply via email to