I actually have a configfile (from when I was running this package - this version - on lenny, where it works), but the error is exactly the same.
If I move .ktoon to the side, it doesn't show the "Configuration file is corrupted" part, but only: ktoon(24844)/ KSycocaPrivate::openDatabase: Trying to open ksycoca from "/var/tmp/kdecache-marado/ksycoca4" ktoon is crashing with signal 11 :( After that, using the new .ktoon (that was generated previously), the error message is only, and allways the KSycocaPrivate::openDatabase: Trying to open ksycoca from "/var/tmp/kdecache-marado/ksycoca4" ktoon is crashing with signal 11 :( As you can see in one Mandriva forum[1], this bug also affects (or affected?) their ktoon. I built the debian package from source and the same thing happens. I tested upstream's first version after 0.8.1 that has .deb packages: # wget http://download.berlios.de/ktoon/ktoon_0.9a-git01_i386.deb # wget http://download.berlios.de/ktoon/kom_0.9a-git01_i386.deb # dpkg -i ktoon_0.9a-git01_i386.deb kom_0.9a-git01_i386.deb and now ktoon works correctly. So, I decided to fetch the source code from the first version at all of ktoon 0.9 (0.9a-rev1558) and compile it from source to see if the problem was already solved there or not. Guess what: no problem with that one. Just for the sake of sanity, I uninstalled everything back, and re-installed debian's ktoon. Now, THIS was unexpected: ktoon is now working! I moved the .ktoon directory to the side, and tried from scratch: the problem came back. SO... Basicly if I have an "working .ktoon directory" I don't have problems, if I have the .ktoon directory that is generated by debian's ktoon itself (even if it has a ktoon.cfg created with this ktoon version running on a lenny environment), ktoon kabooms. What differs? diff -ru .ktoon-crash//ktoon.cfg .ktoon-works//ktoon.cfg --- .ktoon-crash//ktoon.cfg 2010-10-13 18:09:34.000000000 +0100 +++ .ktoon-works//ktoon.cfg 2010-10-13 19:43:00.000000000 +0100 @@ -1,13 +1,20 @@ -/* Generated By:JavaCC: Do not edit this line. Token.java Version 3.0 */ -package org.apache.lucene.demo.html; +<?xml version='1.0' encoding='UTF-8'?> +<Config> + <General> + <Home value="/usr"/> + <Cache value="/tmp"/> + <LastProject value=""/> + <Recents value=""/> + <recents value=""/> + </General> + <ColorPalette> + <LastForegroundColor value="#000000"/> + <LastBackgroundColor value="#000000"/> + <LastPalette value="0"/> + </ColorPalette> + <PenParameters/> + <TipOfDay> + <ShowOnStart value="false"/> + </TipOfDay> +</Config> -/** - * Describes the input token stream. - */ - -public class Token { - - /** - * An integer that describes the kind of this token. This numbering - * system is determined by JavaCCParser, and a table of these numbers is - * stored in the file ...Constants. Binary files .ktoon-crash//palettes/Custom Color Palette.ktpl and .ktoon-works//palettes/Custom Color Palette.ktpl differ Binary files .ktoon-crash//palettes/Custom Gradient Palette.ktpl and .ktoon-works//palettes/Custom Gradient Palette.ktpl differ So, I copy the ktoon.cfg from the working version to the crashing version, and the crashing version no longer crashes. ====== TO SUM UP: ======= * issue #1: ktoon fails to generate a ktoon.cfg file * issue #2: ktoon crashes when an invalid ktoon.cfg file is present * note #1: this no longer happens in ktoon 0.9a (any of the versions tested) * note #2: this only happens if you're using this on testing or unstable, if you're using it on lenny it will run well. * note #3: the config file generated in the lenny environment if completelly different from what it is now... I don't understand anything about how this config file is generated or parsed, but maybe this is happening because ktoon is expecting javacc 4 and now we have javacc 5 on lenny? Note that this can be something completely nonsense, I'm just saying that because the "old config file" starts with a comment saying "Generated By:JavaCC" ... * note #4: since upstream says that anybody should use ktoon 0.9... shouldn't also debian? I know that this is probably too late for squeeze, but it might be the easiest way to fix this bug, if it really is a problem of depending on javacc 4... [1] http://forum.mandriva.com/viewtopic.php?t=127913 -- Marcos Marado -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
