Re: Receiving SIGABRT when starting a client
koniu <gkusnierz <at> gmail.com>
2009-07-02 22:48:11 GMT
The lesson here being, watch your upgrades with bleeding edge
dependencies and if necessary revert/investigate possibility of
upstream upgrade (which seem to follow library release cycle). Sadly
enough distros seem to be having issues with this stuff - the same
problem popped up in Debian unstable a month ago (unresolved for some
weeks with no binary fo libxcb-util 0.3.5):
http://www.mail-archive.com/awesome <at> naquadah.org/msg01442.html
http://www.mail-archive.com/awesome-devel <at> naquadah.org/msg02640.html
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=531310
So also have faith in our wonderful mailing lists ;o]
Now be at peace
kkk
ps. forwarding to user list for reference
On Thu, Jul 2, 2009 at 16:22, Alexandre Perrin<alexandre.perrin <at> epfl.ch> wrote:
> On Thu, Jul 02, 2009 at 04:37:02PM +0200, Gregor Best wrote:
>> Hi people,
>>
>> I'm having kind of a big problem here:
>> After running an update of my system (which, among others, updated
>> libxcb), awesome receives a SIGABRT as soon as I try starting something
>> from the prompt.
>>
>> Below is a backtrace:
>>
>> #0 0xffffe424 in __kernel_vsyscall ()
>> #1 0xb7b13980 in raise () from /lib/libc.so.6
>> #2 0xb7b151c8 in abort () from /lib/libc.so.6
>> #3 0xb7b0ca5e in __assert_fail () from /lib/libc.so.6
>> #4 0xb7b584e0 in _int_malloc () from /lib/libc.so.6
>> #5 0xb7b5970b in calloc () from /lib/libc.so.6
>> #6 0xb80b26bb in _dl_new_object () from /lib/ld-linux.so.2
>> #7 0xb80ae523 in _dl_map_object_from_fd () from /lib/ld-linux.so.2
>> #8 0xb80afed3 in _dl_map_object () from /lib/ld-linux.so.2
>> #9 0xb80bad00 in dl_open_worker () from /lib/ld-linux.so.2
>> #10 0xb80b6a66 in _dl_catch_error () from /lib/ld-linux.so.2
>> #11 0xb80ba6ae in _dl_open () from /lib/ld-linux.so.2
>> #12 0xb7bf1b32 in do_dlopen () from /lib/libc.so.6
>> #13 0xb80b6a66 in _dl_catch_error () from /lib/ld-linux.so.2
>> #14 0xb7bf1c31 in dlerror_run () from /lib/libc.so.6
>> #15 0xb7bf1d5b in __libc_dlopen_mode () from /lib/libc.so.6
>> #16 0xb7bcdc58 in init () from /lib/libc.so.6
>> #17 0xb7bcde05 in backtrace () from /lib/libc.so.6
>> #18 0xb7b4f8c3 in __libc_message () from /lib/libc.so.6
>> #19 0xb7b557c4 in malloc_printerr () from /lib/libc.so.6
>> #20 0xb7b56946 in munmap_chunk () from /lib/libc.so.6
>> #21 0xb7dd8f3e in xcb_get_wm_size_hints_reply (c=0x91d9188, cookie={sequence = 2097},
hints=0x92ed520, e=0x0) at icccm.c:475
>> #22 0xb7dd8f82 in xcb_get_wm_normal_hints_reply (c=0x91d9188, cookie={sequence = 2097},
hints=0x92ed520, e=0x0) at icccm.c:513
>> #23 0x0806003f in property_update_wm_normal_hints (c=0x92ed464, reply=0x0) at /home/gregor/sourcecode/awesome/property.c:130
>> #24 0x0805855d in client_manage (w=4194310, wgeom=0x92ea490, phys_screen=0, startup=false) at /home/gregor/sourcecode/awesome/client.c:490
>> #25 0x0805d91e in event_handle_maprequest (data=0x0, connection=0x91d9188, ev=0x92c5db8) at /home/gregor/sourcecode/awesome/event.c:625
>> #26 0xb7dc0f64 in xcb_event_handle (evenths=0x808ba44, event=0x92c5db8) at event.c:75
>> #27 0x0805314e in a_xcb_check_cb (loop=0xb7cc71c0, w=0xbfac5388, revents=32768) at /home/gregor/sourcecode/awesome/awesome.c:216
>> #28 0xb7cc2d86 in ev_loop () from /usr/lib/libev.so.3
>> #29 0x08054151 in main (argc=1, argv=0xbfac5454) at /home/gregor/sourcecode/awesome/awesome.c:561
>>
>> I'm not sure what to make of this, but as a layman, I'd guess libev
>> fails here. The version I currently use is 3.53, but that has been
>> installed for over 4 month now without any problems.
>>
>> libxcb is at version 1.3 (was 1.2 before the upgrade) and xcb-util is
>> still at 0.3.3
>>
>> Does anyone have _ANY_ idea what this is related to and how I could
>> solve it? I'm happy for even the slightest hints.
>>
>
> Hi!
> I ran into the same kind of problem after an update some days ago,
> awesome started but crashed when I tried to launch any client. I had to
> update xcb-util to 0.3.5 and the problem was solved.
>
> Here is the IRC log with a link to my bt which looks like yours:
>
> 13:53 [ kAworu] jd_: you were right! I've got a new bt :D
> 13:53 [ kAworu] jd_: http://pastebin.com/f41c6d562
> 13:54 [ jd_] kAworu: I am always right :)
> 13:54 [ kAworu] jd_: looks like a xcb-util issue to me, I'm using
> xcb-util-0.3.4_1
> 13:54 [ jd_] kAworu: which version of libxcb and xcb-util do you use ?
> 13:54 [ jd_] aaah
> 13:54 [ jd_] upgrade to 0.3.5 then
> 13:54 [ kAworu] libxcb-1.3
> 13:54 [ jd_] ok, that's why
>
> What I read here it that you need xcb-util-0.3.5 if you're using
> libxcb-1.3. jd might know why ;)
>
> Hope this can help :)
>
> Alex.
>
RSS Feed