Bug#336050: kwin-baghira: makes kpdf use 100% CPU
Thomas Lübking wrote: >Am Freitag, 28. Oktober 2005 00:09 schrieben Sie: > > >>Confirmed. It only happens with KPDF, though. >>The PDFviewer part (as used in Kile, for example) has no such problems. >> >> >i know about this bug - it occurs in kpdf code and i send the author a patch >that's included in kde 3.5 and was backported to 3.4.whatever > >i also had a workaround in my code, but removed it when testing the kpdf patch >and committed the unhacked version to cvs and 0.7 (sorry :-/ ) > > No problem. >however the workaround is said to do not work (though it does here) >see this thread: >http://sourceforge.net/tracker/index.php?func=detail&aid=1286100&group_id=97296&atid=617615 >and tell me if the workaround works for you (if yes, i'll simply reinclude it >versioned and make 0.7a) > > It does work with Debian's kpdf (3.4.2-2 as of now), but this is *not* the proper solution. I am all against dirty hacks. Let's have kpdf's maintainer release a version with the fix backported instead. Note, however, that even with the fix included, kpdf is still a big CPU hog... that means there are most probably other bugs around. kpdf maintainer: please forward the relevant information upstream, with my appreciation. Cheers, J.L.
Bug#282146: Bug#282416: fixed in bacula 1.36.1-1
Filip Van Raemdonck wrote:
reopen 282416 [EMAIL PROTECTED]
tags 282416 + patch
thanks
On Thu, Dec 09, 2004 at 02:17:13PM -0500, Jose Luis Tallon wrote:
We believe that the bug you reported is fixed in the latest version of
bacula, which is due to be installed in the Debian FTP archive:
<...>
* bacula-director-sqlite: revised upgrade logic. Should work now --
feedback requested (Closes: #282416)
Nope:
[EMAIL PROTECTED]:~# /etc/init.d/bacula-director start
Starting Bacula Director: 04-Jan 08:56 bacula-dir: Fatal error: Version error for
database "bacula". Wanted 8, got 7
04-Jan 08:56 bacula-dir: Fatal error: Could not open database "bacula".
04-Jan 08:56 bacula-dir: Fatal error: Version error for database "bacula".
Wanted 8, got 7
04-Jan 08:56 bacula-dir ERROR TERMINATION
Please correct configuration file: /etc/bacula/bacula-dir.conf
failed.
When I run the postinst manually with a 1.34 version argument I get this:
[EMAIL PROTECTED]:~# /var/lib/dpkg/info/bacula-director-sqlite.postinst
configure 1.34.0
Upgrading SQLite tables to v8 format...Ok.
Then it tries to start the director but gives the same error as above.
Checking the postinst it is quickly clear why:
if [ $ ...
^
The 'test' ('[') invocation should not be there; the if needs to check the
exit code of the upgrade script by itself.
Ooopsss.. yet another typo.
Guess i have to seriously consider migrating to 'dbconfig-common' to
avoid these in the future :-S
Anyways, the fix is already included.
I seem to remember having fixed this before for the v6->v7 upgrade in my NMU.
It's certainly possible. I might have made a mistake when hand-patching
or somehow re-introduced the bug later.
Anyways, it won't happen again.
Patch attached.
Thank you very much, Filip.
The corrected version will be uploaded as soon as possible (as soon as
my sponsor is back home)
Best,
J.L.
