Here is the top of a gprof analysis.
I'm wondering if the Xkb references indicate that it is the problem. I
can hypothesise that some changes in the general Xserver code touched
upon Xkb, expecting the DDX to initialise it appropriately. Since
Xprint does not use Xkb, it doesn't handle it in
-Original Message-
From: Julien Cristau [mailto:[EMAIL PROTECTED]
Sent: 22 March 2008 15:34
To: Gavin Bravery; [EMAIL PROTECTED]
Subject: Re: Bug#472180: Xprt hogging CPU.
severity 472180 grave
kthxbye
On Sat, Mar 22, 2008 at 14:33:04 +, Gavin Bravery wrote:
On starting the xprint service
severity 472180 grave
kthxbye
On Sat, Mar 22, 2008 at 14:33:04 +, Gavin Bravery wrote:
On starting the xprint service, the CPU climbs to 100% and sits there.
Most of the time is being spent processing the Xprt requests.
I'm curious: why do you use xprint? :)
Cheers,
Julien
--
To
Processing commands for [EMAIL PROTECTED]:
severity 472180 grave
Bug#472180: Xprt hogging CPU.
Severity set to `grave' from `serious'
kthxbye
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system administrator
(administrator, Debian Bugs database
Package: xprint
Version: 2:1.4.99.901-1
Severity: serious
--- Please enter the report below this line. ---
On starting the xprint service, the CPU climbs to 100% and sits there.
Most of the time is being spent processing the Xprt requests.
An strace on the process shows repeated messages like
5 matches
Mail list logo
