Conversation
Notices
-
@navigium @cmhobbs Pumpa did pretty well with this but it crashes now every time i press Ctrl+N to get a new message and so I can't really use it. too much trouble, don't want to try to fix it just stayin here.
-
Well I checked in over at pump.io for first time in months to find it going strong, but Pumpa aborts when I try to post message. /me shrugs
-
@navigium I dunno. That probably wouldn't bother me anyway because I normally turn off notifications
-
@navigium That's a much bigger problem. Kind of a deal breaker for me and the reason I never go over there.
-
maybe you need to upgrade Pumpa. I never have any problems with it. I'm using .9...though I think they have newer versions than that. @sazius was/is the maintainer, so suspect he knows.
-
@jonkulp @daw That's really strange. Are you using the newest version of Pumpa? I'd be very interested to know if it crashes :-) I wrote up some instructions on how to run it in debug mode to get some better feedback: http://pumpa.branchable.com/debug_mode/
-
@sazius I got it from Debian repo. I pulled latest code but can't figure out how to build it. I don't see makefiles or build script
-
@jonkulp Oh, that's bad if the one from Debian crashes :-/ It shouldn't unless there's some bug in the pump.io server...
As for building, it uses Qt's qmake. There are instructions on this page: http://pumpa.branchable.com/install/ - basically you need to run "qmake" first, which will create a Makefile for you.
-
@jonkulp Seems you got it working? Great! Still strange that the Debian version was broken :-(
-
@sazius [DEBUG] processText: dropping unsupported tag "mrjohnsonpaul10"pumpa: config.c:386: prvTidySetOptionInt: Assertion `option_defs[ optId ].type == TidyInteger' failed.Aborted
-
@sazius I posted from web.
-
@sazius ok the Debian one works
-
@jonkulp OK, that's interesting. Due to a recent patch that has caused some trouble. Could you tell me what version of Debian, or even better what version of libtidy? If you're on Debian you can run e.g. "aptitude show libtidy-dev | grep Version".
-
@jonkulp Thanks for helping out BTW! I'm planning to make a release in about one week, and it's pretty serious if it crashes on a common system :-)
-
@jonkulp I just tried compiling the git version on wheezy and posting a note. It worked. So it's really something with your version of libtidy... would be interesting to know what version it is :-)
-
@sazius libtidy-0.99-0 in Debian Jessie
-
@jonkulp OK, that's exactly what I'm using too... do you get any "[DEBUG]" lines that mention tidy? E.g. "[DEBUG] tidy release date" ?
-
@sazius Hang on building with debug enabled now...
-
@sazius [DEBUG] tidy release date: "2009-03-25" [DEBUG] use API with new TidyBodyOnly as int : truepumpa: config.c:386: prvTidySetOptionInt: Assertion `option_defs[ optId ].type == TidyInteger' failed.Aborted
-
@sazius It's strange because shouldn't the one from the debian repo be using the same library as the one that I build from source?
-
@jonkulp Yes, but there was a recent patch from an OS X user to make it compatible with the version of libtidy there: http://pumpa.branchable.com/bugs/Patch:_tidy_build_and_runtime_issues/ - apparently there's still something going wrong, I just don't understand what, since it works for me :-/
-
@jonkulp I have exactly the same version of libtidy, and it works for me. Did you start from a clean version when you compiled? (I'm really running out of options here... :-/)
-
@sazius don't know, but you can rest easy that the version in the Debian repository works. Later when I have more time I will reboot from my #! partition into Ubuntu and try to compile the code there and run it and see if I have the same problem. I suppose it's possible that one version is crashing because it does not have its own auth token or that the tokens don't match up between the two versions of pumpa that I have? I don't understand what authentication so I can't do anything more than speculate
-
@jonkulp @sazius but of course authentication would not have anything to do with the libtidy library would it?
-
@jonkulp Well, this code will end up being the next Debian version, which is what bothers me.
From your debug output I can tell that the problem is definitely with the libtidy issue and not with the authentication.
I'm running Debian jessie myself, and I also tested it in wheezy.
If you still have time you could try to re-compile by doing a "make clean" first... but you've already used a lot of time to help me out :-)
-
@sazius I did a make clean before I rebuilt it with debugging mode enabled and had the same crashing problem. If you want, I can uninstall the package from the Debian repo, clear out all my code, and do a fresh git clone, do the whole build process again, but it'll have to wait a couple of hours b/c I'm about to leave the house. I don't mind doing it I want it to work b/c I know you worked really hard on the code.
-
@sazius by the way there were two or three related libtidy packages in the Debian repo, should I have installed those as well? It seems like your build script would have noticed if any packages were missing though.
-
@jonkulp Thanks but I don't think that's necessary. Regarding the different versions: that's curious, if I do an "aptitude search libtidy" I just see "libtidy-0.99-0" and "libtidy-dev" here on Debian jessie. It can't be about missing libraries either.
The issue is that in libtidy an option was changed from being Bool to Int at some version (May 2007). Pumpa has previously always used Int, but on Mac OS X there's an ancient version of libtidy that uses Bool, and the patch added a check to use Bool if the version is old enough. Your libtidy reports as being the same as I have, but bums out because it it shouldn't be Int. Which makes no sense, really... :-)
Perhaps I should try to install #! and test it there ... or just revert the patch. Supporting Linux is much more important to me than Mac to be honest.
And no hurry, it's getting late here anyway :-)
-
@jonkulp The Debian package shouldn't conflict with the git code in any way. The only thing you could try is to clone a clean git repo... but that's probably not the issue either.
-
@sazius very curious. Building from source works fine on ubuntu partition...
-
@jonkulp OK, at least that gives me hope :-) The most recent changes have only been tested in Debian jessie and wheezy (by me).
-
@sazius Yes I've made a couple of replies and liked a couple of things and it seems to work just fine. No crashes at all. I wish it would work on my Crunchbang side, no idea why it doesn't
-
@jonkulp Debugging remotely is really hard... if it was in my own computer I bet I could find the problem quickly. One thing I could try is install Crunchbang in a VM and see if I can replicate the problem.
-
@sazius You can try this but my installation is so far removed from the original Crunchbang system that it might not tell you anything. I have had the crunchbang repo disabled for about two years and so it's really straight up Debian using an openbox window manager.
-
@jonkulp OK, but your experience makes me think there's something problematic with that patch. The way it's reacting should mean also the Debian version should never have worked in your system... which it does... which doesn't make sense at all.
-
@sazius /me makes confused face...
-
@sazius if nothing else, this has meant an extended appearance of @sazius on GNU Social!
-
@sazius if you would like, you can revert the patch and give me a heads up and I will pull code again and rebuild with the reverted code and see if it is still broken.
-
@jonkulp Hehhe :-) I'm pretty equal opportunity on GNU Social and pump.io. At least I check both every evening, but discussions may vary :-)
-
@jonkulp @sazius or I guess I could do a hard reset to earlier version locally, couldn't I?
-
@jonkulp You could try to run "git revert c60b699 6792ae1". That should revert the two git commits related to that patch.
-
@sazius Oops I already did a hard reset of the master branch to the point right before the Mac OS 10 patch commit. rebuilding now...
-
@jonkulp OK, that should work too :-)
-
@sazius Still getting the same crash and error message. I noticed something in the qmake command though, it was that its building for qt5. How do I tell what version of qt I have installed?
-
@jonkulp Yeah, it should work with both qt4 and qt5. For example "qmake -v" should tell you first qmake version, and the Qt version.
-
@jonkulp OK, that is really strange... did you reset at the right point though? There are two commits related to the OS X patch.
-
@sazius doh! same prob. output: http://paste.jonkulp.net/kuwaqemoda.vbs
-
@sazius I did those 2 reverts like you said
-
@jonkulp OK, then it really can't be related to the OS X patch at all. I'm pretty much out of ideas... did you already try a clean git clone? Wow, this is a difficult one :-)
-
@sazius yep did that twice.
-
@jonkulp Huh, really running out of options here... anyway, thanks for helping out so far. It's getting late here (almost midnight) so I think I'll have to call it a day :-)
-
@sazius no worries. Maybe more tomorrow. Is there a line of code I could hack for testing?
-
@jonkulp not sure anymore, the libtidy problem was in src/util.cpp in the tidyHtml function where TidyBodyOnly is set (exact line depends if you are on the reverted version or the current :-).
-
@jonkulp Anyway, I'm heading to bed now! Good #tzaf :-)
Jon Kulp
Moving (some day) To Federati...can no longer change usernames
sazius on Mayfirst
All Chirp! content and data are available under the