ayttm

Hi. I'm Siddhesh, the new dev for ayttm. I committed the TreeView changes of the status window into the gtk2-port branch yesterday. With that, the major GUI breakages have been fixed. So I finally decided to take the bold step - I commented out ... [More] -DGTK_ENABLE_BROKEN from configure.ac. Predictably, hell broke loose and told me that the spell-checker was broken; it asked for a GtkText and I gave it GtkTextView. I had resolved to work on it today, but my eyelids are shutting out on me. So loooks laik your on you're oun with speeling four a wile ;-) [Less]

Hi. I'm Siddhesh, the new dev for ayttm. I committed the TreeView changes of the status window into the gtk2-port branch yesterday. With that, the major GUI breakages have been fixed. So I finally decided to take the bold step - I commented out ... [More] -DGTK_ENABLE_BROKEN from configure.ac. Predictably, hell broke loose and told me that the spell-checker was broken; it asked for a GtkText and I gave it GtkTextView. I had resolved to work on it today, but my eyelids are shutting out on me. So loooks laik your on you're oun with speeling four a wile ;-) [Less]

If you use the jabber service on ayttm, you may notice the main window appears to freeze up at times turning completely white. You can still chat, and clicking on the main window makes contacts visible, but it just doesn't refresh on its own.This ... [More] happens because of a problem with the jabber module and I haven't had a chance to figure it out yet. What I do know, is that you can unlock the application without restarting it, but you need to resort to a teeny weeny bit of geekery.First, find out the pid of the running ayttm process: ayttm_pid=`ps -u philip | grep a[y]ttm | cut -f2 -d' '`(I use [y] instead of y in ayttm so that the grep process doesn't show up in the list).Once you have your pid, start gdb telling it to attach to this pid. Different versions of gdb have different ways to do this, so check the man page, but two common ways are: gdb ayttm $ayttm_pidor gdb ayttm -p $ayttm_pidOk, so pretty much anyone could have told you how to get this far, it's going forward that needs a wee bit of knowledge of the source.I'll save you the trouble and tell you that you need to look into jab_recv. File descriptor for the jabber socket (stored in j->fd) has closed, but the code is stuck on an infinite read. You need to set a breakpoint on jab_recv, and close the ayttm end of the fd: bt jab_recv cont n n p close(j->fd) deta ^DThat's about it. You'll get an alert telling you that the jabber server closed the connection. Click Ok, and proceed as if nothing happened.Update:Finally, there's really no reason for you to do all that. Here's the one liner shell script (broken for readability) to do it for you: echo -e '\n\n\nb jab_recv\ncont\nn\nn\np close(j->fd)\ndeta\n' | \ gdb ayttm `ps -waux | grep a[y]ttm | cut -f2 -d' '` &>/dev/null [Less]

If you use the jabber service on ayttm, you may notice the main window appears to freeze up at times turning completely white. You can still chat, and clicking on the main window makes contacts visible, but it just doesn't refresh on its own.This ... [More] happens because of a problem with the jabber module and I haven't had a chance to figure it out yet. What I do know, is that you can unlock the application without restarting it, but you need to resort to a teeny weeny bit of geekery.First, find out the pid of the running ayttm process: ayttm_pid=`ps -u philip | grep a[y]ttm | cut -f2 -d' '`(I use [y] instead of y in ayttm so that the grep process doesn't show up in the list).Once you have your pid, start gdb telling it to attach to this pid. Different versions of gdb have different ways to do this, so check the man page, but two common ways are: gdb ayttm $ayttm_pidor gdb ayttm -p $ayttm_pidOk, so pretty much anyone could have told you how to get this far, it's going forward that needs a wee bit of knowledge of the source.I'll save you the trouble and tell you that you need to look into jab_recv. File descriptor for the jabber socket (stored in j->fd) has closed, but the code is stuck on an infinite read. You need to set a breakpoint on jab_recv, and close the ayttm end of the fd: bt jab_recv cont n n p close(j->fd) deta ^DThat's about it. You'll get an alert telling you that the jabber server closed the connection. Click Ok, and proceed as if nothing happened.Update:Finally, there's really no reason for you to do all that. Here's the one liner shell script (broken for readability) to do it for you: echo -e '\n\n\nb jab_recv\ncont\nn\nn\np close(j->fd)\ndeta\n' | \ gdb ayttm `ps -waux | grep a[y]ttm | cut -f2 -d' '` &>/dev/null [Less]

If you use the jabber service on ayttm, you may notice the main window appears to freeze up at times turning completely white. You can still chat, and clicking on the main window makes contacts visible, but it just doesn't refresh on its own.This ... [More] happens because of a problem with the jabber module and I haven't had a chance to figure it out yet. What I do know, is that you can unlock the application without restarting it, but you need to resort to a teeny weeny bit of geekery.First, find out the pid of the running ayttm process: ayttm_pid=`ps -u philip | grep a[y]ttm | cut -f2 -d' '`(I use [y] instead of y in ayttm so that the grep process doesn't show up in the list).Once you have your pid, start gdb telling it to attach to this pid. Different versions of gdb have different ways to do this, so check the man page, but two common ways are: gdb ayttm $ayttm_pidor gdb ayttm -p $ayttm_pidOk, so pretty much anyone could have told you how to get this far, it's going forward that needs a wee bit of knowledge of the source.I'll save you the trouble and tell you that you need to look into jab_recv. File descriptor for the jabber socket (stored in j->fd) has closed, but the code is stuck on an infinite read. You need to set a breakpoint on jab_recv, and close the ayttm end of the fd: bt jab_recv cont n n p close(j->fd) deta ^DThat's about it. You'll get an alert telling you that the jabber server closed the connection. Click Ok, and proceed as if nothing happened.Update:Finally, there's really no reason for you to do all that. Here's the one liner shell script (broken for readability) to do it for you: echo -e '\n\n\nb jab_recv\ncont\nn\nn\np close(j->fd)\ndeta\n' | \ gdb ayttm `ps -waux | grep a[y]ttm | cut -f2 -d' '` &>/dev/null [Less]

If you use the jabber service on ayttm, you may notice the main window appears to freeze up at times turning completely white. You can still chat, and clicking on the main window makes contacts visible, but it just doesn't refresh on its own.This ... [More] happens because of a problem with the jabber module and I haven't had a chance to figure it out yet. What I do know, is that you can unlock the application without restarting it, but you need to resort to a teeny weeny bit of geekery.First, find out the pid of the running ayttm process: ayttm_pid=`ps -u philip | grep a[y]ttm | cut -f2 -d' '`(I use [y] instead of y in ayttm so that the grep process doesn't show up in the list).Once you have your pid, start gdb telling it to attach to this pid. Different versions of gdb have different ways to do this, so check the man page, but two common ways are: gdb ayttm $ayttm_pidor gdb ayttm -p $ayttm_pidOk, so pretty much anyone could have told you how to get this far, it's going forward that needs a wee bit of knowledge of the source.I'll save you the trouble and tell you that you need to look into jab_recv. File descriptor for the jabber socket (stored in j->fd) has closed, but the code is stuck on an infinite read. You need to set a breakpoint on jab_recv, and close the ayttm end of the fd: bt jab_recv cont n n p close(j->fd) deta ^DThat's about it. You'll get an alert telling you that the jabber server closed the connection. Click Ok, and proceed as if nothing happened.Update:Finally, there's really no reason for you to do all that. Here's the one liner shell script (broken for readability) to do it for you: echo -e '\n\n\nb jab_recv\ncont\nn\nn\np close(j->fd)\ndeta\n' | \ gdb ayttm `ps -waux | grep a[y]ttm | cut -f2 -d' '` &>/dev/null [Less]

Surprised to see a post here? It surprises me that I'm posting.Anyway, short update to say that I've gotten ayttm to build with gtk-2.0. Haven't committed any code yet. There's a bunch of UI issues that came up after porting the code.Christmas vacations are fun :)

Last night, I wrote up a bugzilla plugin for ayttm. It took me 10 minutes to write and 2 minutes to find a typo that caused a segfault (using t instead of tmp). I'll commit it shortly.

Apparently I was on TV yesterday. On CNBC in Qatar. The interview I'd given about ayttm was aired there as part of a business show. A friend of my cousin saw it, and asked her if she was related to Philip Tellis.I have not seen the interview.

just committed a change to the jp2 encoder that should fix the webcam broadcast issue. I've got output files down to under 5KB. Need people to test since I don't have my cam with me.Oh yeah, I think it was Ben Reser who negotiated with the Jasper ... [More] guys to get the Jasper licence GPL compatible. It is now very much MIT like.yes, this would be an appropriate time to go w00t. [Less]