It doesn't crash every time but usually after 2-3 restarts of bitcoin client it does. My rc.lua: http://pastebin.com/vm5tzfuR I'm using Debian Wheezy amd64. I tried both repository version 3.4.11 and latest git without any difference.

This task depends upon

Closed by Uli Schlachter (psychon)
Saturday, 05 May 2012, 08:08 GMT Reason for closing: Not a bugAdditional comments about closing: Hm, we don't have a "Not our
bug" reason for closing tasks.
Anyway, bug seems to be elsewhere.

Can you get debug symbols for awesome and libstartup-notification (nope, looks like there is no debian package for that)? Could you run awesome under gdb and get me a "bt full"? Or perhaps run awesome under valgrind?

Oh and I'd like to see the result of "p *event" in frame 8 ("frame 8" in gdb, if I count right, frame 8 should be event_handle()) and the result of running xlsclients to see which event awesome is handling while it dies.

Oh, sorry for a delay, I expected the bugtracker send me an email on updates but it was set to jabber which probably doesn't work. Anyway, I'll do what you ask today. For now some update, I don't experience crashes on another Debian installation (32 bit though) on Intel video. I do all the tests on a separate X instance to keep things clean and to keep my other apps running so there should be two clients: xfce4-terminal and bitcoin-qt. Though crash occures even without xfce4-terminal.

Well, I need a little help figuring it out. I'm python guy so I have close to zero experience with C/C++ on GNU/Linux. What exactly should I do to build Awesome with debug symbols? I'd like to install it to the separate directory as well as libstartup-notification. I hope export CMAKE_PREFIX_PATH=/opt/awesome should do it but I doubt debug is enabled by default. Also no gdb knowledge either so please tell me step by step what commands to enter in gdb.

Meh, I can't find any bitcoin-qt packages for debian. Will try to try on my archlinux box, but that might take a while. Let's hope that it crashes here, too.

For compiling awesome with debug symbols: http://awesome.naquadah.org/wiki/Debugging
No clue for libstartup-notification.
No clue if the export works. The wiki seems to suggest make CMAKE_ARGS="-DCMAKE_PREFIX_PATH=/opt/awesome", but I'm not sure on that one.

Bitcoin-qt is included in the official package of Bitcoin (tgz, universal 32 and 64-bit binaries without packaging): http://bitcoin.org/ I tried compiling bitcoin from the git source and it crashed Awesome the same way so there's no difference. I'll experiment with a clean VM and Debian netinst amd64 to make sure none of my other programs affects this.

Did you use my rc.lua? It didn't crash for me, too, when I used the default rc.lua but with my custom one it did. Ok, I'll try with the empty profile. Also, I have libstartup-notification0 of version 0.12-1.

You're right, no crash when running on a newly created user. But our culprit seems to be found, it's Qt. Here's my ~/.config/Trolltech.conf : http://pastebin.com/sfVZ6ide After copying it to that test user awesome started crashing after launching bitcoin-qt -testnet -server
I'm using those flags to speedup the launch process because testnet is much smaller and loads faster than the main network.

Did some tests, the problem is definitely GTK+ style for Qt. Other styles like Motif, CDE, Cleanlooks etc. doesn't lead to crash. Choosing GTK+ in qtconfig does. It happens regardless of the actual GTK theme, I choose Debian, Nodoka Silver, Glossy and Clearlooks, Awesome crashed anyway.

I set up a VM with Debian Wheezy amd64 and I can't reproduce this problem myself. On my main system it still crashes. Maybe it's a configuration issue but I have no idea which configs may affect this. I managed to compile libstartup-notification and awesome with debug symbols, here is the complete backtrace: http://pastebin.com/5bqMzu7C I see some <optimized out> values but I did exactly as said in http://awesome.naquadah.org/wiki/Debugging

Could attach the output of xlsatoms for the same X server that you generate that backtrace with?

If you already closed that server (which I kind of expect...), could you get a new backtrace together with the corresponding xlsatoms output?
Also, that "p *event" is a good idea. But since I'm lazy, could you also provide "p *(xcb_client_message_event_t*)event"?

Thanks, you had me questioning my sanity for a moment there. :-P (THROTTLE sounded weird, _NET_STARTUP_INFO_BEGIN makes way more sense)

So for whatever reason your bitcoin-qt is sending a badly malformed message (bug 1) which libstartup-notification mishandles (bug 2, don't follow the NULL pointer, for only horror awaits you at its end!).

I will report bug 2 upstream, no clue who is responsible for bug 1 (although I'd be surprised if your qt theme sends startup notifications).
Which exact qt version do you use?

Now I just need a good idea how to figure out where that evil ClientMessage is coming from. Qt's source says "it's not qt" (it only ever sends a "remove" message), uim's source code says "it's not uim" (no _NET_STARTUP_NOTIFICATION_BEGIN).