-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Philippe Cloutier wrote: > Hi, > I'm unable to reproduce this in testing. If this is the result of an > upgrade, please try to identify which package upgrade triggered the bug.
Hi the problem is: This was a massive upgrade I have done ... with about 200 MB of newly downloaded packages because I have not done an upgrade for months now. The next problem is that I have done an apt-get autoclean immediately after the upgrade has finished because I am running low on disk space and the debian packages server does not save old packages. If you have got an idea how to find out which package upgrade triggered the bug let me know and I will do my very best to help you and provide information. Possibly you could ask the package authors of the packages kaffeine depends on wether there was a significant change in the way the programs behave, for example a change in the api or something else (sorry I am not very familiar with real programming languages, just PHP and so on). Bye, Tilman -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFFIojfxWHJ8ml5laIRAsj6AJ9pj2ckaVmnD8jCMazkynlsu737jQCbB/cO w8zzqubW/r5xk4IODX0+v4o= =10p0 -----END PGP SIGNATURE----- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
