[prev in list] [next in list] [prev in thread] [next in thread]
List: kde-print
Subject: Re: Me too: "Kprinter has stopped working - Unable
From: Andrew Myers <andrew.myers () fdservices ! co ! uk>
Date: 2007-02-12 11:05:22
Message-ID: 45D049F2.1030300 () fdservices ! co ! uk
[Download RAW message or body]
[Attachment #2 (multipart/alternative)]
OH NO It has happened again with the same error message "Unable to
start child print process..."
Here are the .DCOP files in my home directory:
$ ll .D*
-rw-r--r-- 1 andrew users 53 Feb 12 09:15 .DCOPserver_ezcool__0
lrwxrwxrwx 1 andrew users 34 Feb 12 09:15 .DCOPserver_ezcool_:0 ->
/home/andrew/.DCOPserver_ezcool__0
-rw-r--r-- 1 andrew users 53 Feb 12 09:16 .DCOPserver_ezcool_ezcool_1
lrwxrwxrwx 1 andrew users 40 Feb 12 09:16 .DCOPserver_ezcool_ezcool:1 ->
/home/andrew/.DCOPserver_ezcool_ezcool_1
and here are their contents:
$ more .D*
::::::::::::::
.DCOPserver_ezcool__0
::::::::::::::
local/ezcool:/tmp/.ICE-unix/dcop4604-1171268147
4604
::::::::::::::
.DCOPserver_ezcool_:0
::::::::::::::
local/ezcool:/tmp/.ICE-unix/dcop4604-1171268147
4604
::::::::::::::
.DCOPserver_ezcool_ezcool_1
::::::::::::::
local/ezcool:/tmp/.ICE-unix/dcop4791-1171268170
4791
::::::::::::::
.DCOPserver_ezcool_ezcool:1
::::::::::::::
local/ezcool:/tmp/.ICE-unix/dcop4791-1171268170
4791
Here is the contents of /tmp/.ICE-unix:
$ ll
total 0
srwx------ 1 andrew users 0 Feb 12 09:15 4659=
srwx------ 1 andrew users 0 Feb 12 09:16 4823=
srwx------ 1 andrew users 0 Feb 12 09:15 dcop4604-1171268147=
srwx------ 1 andrew users 0 Feb 12 09:16 dcop4791-1171268170=
I will now delete the .DCOP files in my home directory
........................
OK I have deleted the files, but still cannot print , same error message.
I will now log out and log back in again ........................
Now the .DCOP files have been recreated, and here they are:
$ ll .D*
-rw-r--r-- 1 andrew users 55 Feb 12 11:57 .DCOPserver_ezcool__0
lrwxrwxrwx 1 andrew users 34 Feb 12 11:57 .DCOPserver_ezcool_:0 ->
/home/andrew/.DCOPserver_ezcool__0
-rw-r--r-- 1 andrew users 55 Feb 12 11:57 .DCOPserver_ezcool_ezcool_1
lrwxrwxrwx 1 andrew users 40 Feb 12 11:57 .DCOPserver_ezcool_ezcool:1 ->
/home/andrew/.DCOPserver_ezcool_ezcool_1
and here are their contents:
$ more .D*
::::::::::::::
.DCOPserver_ezcool__0
::::::::::::::
local/ezcool:/tmp/.ICE-unix/dcop14415-1171277854
14415
::::::::::::::
.DCOPserver_ezcool_:0
::::::::::::::
local/ezcool:/tmp/.ICE-unix/dcop14415-1171277854
14415
::::::::::::::
.DCOPserver_ezcool_ezcool_1
::::::::::::::
local/ezcool:/tmp/.ICE-unix/dcop14668-1171277868
14668
::::::::::::::
.DCOPserver_ezcool_ezcool:1
::::::::::::::
local/ezcool:/tmp/.ICE-unix/dcop14668-1171277868
14668
and here is the contents of /tmp/.ICE-unix:
$ ll
total 0
srwx------ 1 andrew users 0 Feb 12 11:57 14426=
srwx------ 1 andrew users 0 Feb 12 11:57 14734=
srwx------ 1 root root 0 Feb 12 11:57 dcop14125-1171277843=
srwx------ 1 andrew users 0 Feb 12 11:57 dcop14415-1171277854=
srwx------ 1 andrew users 0 Feb 12 11:57 dcop14668-1171277868=
srwx------ 1 andrew users 0 Feb 12 09:15 dcop4604-1171268147=
srwx------ 1 andrew users 0 Feb 12 09:16 dcop4791-1171268170=
As expected the printing now works again.
I am at a loss to explain this behaviour, but it is extremely annoying.
Kprinter is a useful tool, but if this continues I will need to find a
work around to avoid using it.
All the best
Andrew
Andrew Myers wrote:
> Not quite the same here.
>
> I have only three .DCOP* files _0, _1 and _2 with corresponding ":" files.
>
> All owned by the user.
>
> I deleted them all and re-logged in and kprinter is now working again.
>
> I normally have two sessions running, which would probably explain why
> there was a 0 and a 1 file.
>
> So the handles were the cause, and the fact that they were not
> destroyed at termination was the problem. But I have been using Linux
> for several years, upgraded more times that I wish to remember and
> never had this problem before with kprinter. I therefore think that
> something has probably changed somewhere which has caused this effect.
>
> Since I use Mandriva 2007 and Kurt was on Suse 10.0, I would not
> presume that it is a distro problem.
>
> I will report back if this happens again
>
> Many thanks Kurt for solving this, and to everyone for their help.
>
> All the best
>
>
> Andrew
>
>
> Kurt Pfeifle wrote:
>> On Tuesday 06 February 2007 14:09, Kurt Pfeifle wrote:
>>
>>> On Tuesday 06 February 2007 11:50, Kurt Pfeifle wrote:
>>>
>>>> On Tuesday 06 February 2007 10:47, Andrew Myers wrote:
>>>>
>>>>> Hi Kurt:
>>>>>
>>>>> Did you manage to solve this problem or, if not, have you devised a work
>>>>> around to print stuff from kde?
>>>>>
>>>> Sorry, no, not yet. I'll return later this afternoon to the machine
>>>> in question; I'll still have to see what the result is of the last
>>>> test Michael had suggested to run.
>>>>
>>> OK, I was able to run a (very short test).
>>>
>>> 1. created a new (non-root) user; this user can print with kprinter
>>> without any problem
>>>
>>> 2. the user that had problems with KDEPrint still can't print; same
>>> problems as before. In addition, this user now does not even see
>>> kdeprintd listed any more underneath "kded" when he runs "kdcop"
>>> (the GUI to dcop) -- and the command "dcop kded kdeprintd" now
>>> does return:
>>> "object 'kdeprintd' in application 'kded' not accessible"
>>>
>>> Strange.
>>>
>>> I've no idea what's going on. But later I'll move away ${HOME}/.kde
>>> for the user with the problem and let him start a virgin KDE session
>>> (previously I had already tried that with the two files kdeprintrc &
>>> kprinterrc in ${HOME}/.kde/share/config/ on their own, but that did
>>> not help...).
>>>
>>> But I can't do that right now, sorry.
>>>
>>> Cheers,
>>> Kurt
>>>
>>
>> It works now again.
>>
>> I have noticed a *lot* of files with the following scheme for their
>> names, all in $HOME of the said user:
>>
>> .DCOPserver_myhostname_:NNN -> .DCOPserver_myhostname__NNN
>> .DCOPserver_myhostname__NNN
>>
>> (where the filename with the ":" was always a symlink pointing to the
>> one with the replacement "_", and where "NNN" was a figure ranging
>> from "0" to "255").
>>
>> I'm not sure what caused the creation of all those files, but somehow
>> there seemed to be a limit of 2^8=256 to their number.
>>
>> I deleted them all but the ones with "0", logged out of KDE and back
>> in, and now kprinter works again.
>>
>> Will be watching if anything does re-create those files. So far I've
>> only the "*_:0" and "*__0" files here.
>>
>> Cheers,
>> Kurt
>>
>> _______________________________________________
>> kde-print mailing list
>> kde-print@kde.org
>> https://mail.kde.org/mailman/listinfo/kde-print
>>
>>
> ------------------------------------------------------------------------
>
> _______________________________________________
> kde-print mailing list
> kde-print@kde.org
> https://mail.kde.org/mailman/listinfo/kde-print
>
[Attachment #5 (text/html)]
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
<font face="Helvetica, Arial, sans-serif" size="-1">OH NO It
has happened again with the same error message "Unable to start child
print process..."<br>
<br>
Here are the .DCOP files in my home directory:<br>
<br>
$ ll .D*<br>
-rw-r--r-- 1 andrew users 53 Feb 12 09:15 .DCOPserver_ezcool__0<br>
lrwxrwxrwx 1 andrew users 34 Feb 12 09:15 .DCOPserver_ezcool_:0 ->
/home/andrew/.DCOPserver_ezcool__0<br>
-rw-r--r-- 1 andrew users 53 Feb 12 09:16 .DCOPserver_ezcool_ezcool_1<br>
lrwxrwxrwx 1 andrew users 40 Feb 12 09:16 .DCOPserver_ezcool_ezcool:1
-> /home/andrew/.DCOPserver_ezcool_ezcool_1<br>
<br>
and here are their contents:<br>
<br>
$ more .D*<br>
> > > > > > > > > > > > > > <br>
.DCOPserver_ezcool__0<br>
> > > > > > > > > > > > > > <br>
local/ezcool:/tmp/.ICE-unix/dcop4604-1171268147<br>
4604<br>
> > > > > > > > > > > > > > <br>
.DCOPserver_ezcool_:0<br>
> > > > > > > > > > > > > > <br>
local/ezcool:/tmp/.ICE-unix/dcop4604-1171268147<br>
4604<br>
> > > > > > > > > > > > > > <br>
.DCOPserver_ezcool_ezcool_1<br>
> > > > > > > > > > > > > > <br>
local/ezcool:/tmp/.ICE-unix/dcop4791-1171268170<br>
4791<br>
> > > > > > > > > > > > > > <br>
.DCOPserver_ezcool_ezcool:1<br>
> > > > > > > > > > > > > > <br>
local/ezcool:/tmp/.ICE-unix/dcop4791-1171268170<br>
4791<br>
<br>
Here is the contents of /tmp/.ICE-unix:<br>
<br>
</font><font face="Helvetica, Arial, sans-serif">$ ll<br>
total 0<br>
srwx------ 1 andrew users 0 Feb 12 09:15 4659=<br>
srwx------ 1 andrew users 0 Feb 12 09:16 4823=<br>
srwx------ 1 andrew users 0 Feb 12 09:15 dcop4604-1171268147=<br>
srwx------ 1 andrew users 0 Feb 12 09:16 dcop4791-1171268170=<br>
<br>
I will now delete the .DCOP files in my home directory
........................<br>
<br>
OK I have deleted the files, but still cannot print , same error
message.<br>
<br>
I will now log out and log back in again ........................<br>
<br>
Now the .DCOP files have been recreated, and here they are:<br>
<br>
$ ll .D*<br>
-rw-r--r-- 1 andrew users 55 Feb 12 11:57 .DCOPserver_ezcool__0<br>
lrwxrwxrwx 1 andrew users 34 Feb 12 11:57 .DCOPserver_ezcool_:0 ->
/home/andrew/.DCOPserver_ezcool__0<br>
-rw-r--r-- 1 andrew users 55 Feb 12 11:57 .DCOPserver_ezcool_ezcool_1<br>
lrwxrwxrwx 1 andrew users 40 Feb 12 11:57 .DCOPserver_ezcool_ezcool:1
-> /home/andrew/.DCOPserver_ezcool_ezcool_1<br>
<br>
and here are their contents:<br>
<br>
$ more .D*<br>
> > > > > > > > > > > > > > <br>
.DCOPserver_ezcool__0<br>
> > > > > > > > > > > > > > <br>
local/ezcool:/tmp/.ICE-unix/dcop14415-1171277854<br>
14415<br>
> > > > > > > > > > > > > > <br>
.DCOPserver_ezcool_:0<br>
> > > > > > > > > > > > > > <br>
local/ezcool:/tmp/.ICE-unix/dcop14415-1171277854<br>
14415<br>
> > > > > > > > > > > > > > <br>
.DCOPserver_ezcool_ezcool_1<br>
> > > > > > > > > > > > > > <br>
local/ezcool:/tmp/.ICE-unix/dcop14668-1171277868<br>
14668<br>
> > > > > > > > > > > > > > <br>
.DCOPserver_ezcool_ezcool:1<br>
> > > > > > > > > > > > > > <br>
local/ezcool:/tmp/.ICE-unix/dcop14668-1171277868<br>
14668<br>
<br>
</font><font face="Helvetica, Arial, sans-serif" size="-1">and here is
the contents of /tmp/.ICE-unix:<br>
<br>
</font><font face="Helvetica, Arial, sans-serif">$ ll<br>
total 0<br>
srwx------ 1 andrew users 0 Feb 12 11:57 14426=<br>
srwx------ 1 andrew users 0 Feb 12 11:57 14734=<br>
srwx------ 1 root root 0 Feb 12 11:57 dcop14125-1171277843=<br>
srwx------ 1 andrew users 0 Feb 12 11:57 dcop14415-1171277854=<br>
srwx------ 1 andrew users 0 Feb 12 11:57 dcop14668-1171277868=<br>
srwx------ 1 andrew users 0 Feb 12 09:15 dcop4604-1171268147=<br>
srwx------ 1 andrew users 0 Feb 12 09:16 dcop4791-1171268170=<br>
<br>
As expected the printing now works again.<br>
<br>
I am at a loss to explain this behaviour, but it is extremely annoying.<br>
Kprinter is a useful tool, but if this continues I will need to find a
work around to avoid using it.<br>
<br>
All the best<br>
<br>
<br>
Andrew<br>
</font><br>
<br>
Andrew Myers wrote:
<blockquote cite="mid45C9A00B.4000608@fdservices.co.uk" type="cite">
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
<title></title>
<font size="-1"><font face="Helvetica, Arial, sans-serif">Not quite
the
same here.<br>
<br>
I have only three .DCOP* files _0, _1 and _2 with corresponding ":"
files.<br>
<br>
All owned by the user.<br>
<br>
I deleted them all and re-logged in and kprinter is now working again.<br>
<br>
I normally have two sessions running, which would probably explain why
there was a 0 and a 1 file.<br>
<br>
So the handles were the cause, and the fact that they were not
destroyed at termination was the problem. But I have been using Linux
for several years, upgraded more times that I wish to remember and
never had this problem before with kprinter. I therefore think that
something has probably changed somewhere which has caused this effect.<br>
<br>
Since I use Mandriva 2007 and Kurt was on Suse 10.0, I would not
presume that it is a distro problem.<br>
<br>
I will report back if this happens again<br>
<br>
Many thanks Kurt for solving this, and to everyone for their help.<br>
<br>
All the best<br>
<br>
<br>
Andrew<br>
<br>
</font></font><br>
Kurt Pfeifle wrote:
<blockquote cite="mid200702062026.42818.k1pfeifle@gmx.net" type="cite">
<pre wrap="">On Tuesday 06 February 2007 14:09, Kurt Pfeifle wrote:
</pre>
<blockquote type="cite">
<pre wrap="">On Tuesday 06 February 2007 11:50, Kurt Pfeifle wrote:
</pre>
<blockquote type="cite">
<pre wrap="">On Tuesday 06 February 2007 10:47, Andrew Myers wrote:
</pre>
<blockquote type="cite">
<pre wrap="">Hi Kurt:
Did you manage to solve this problem or, if not, have you devised a work
around to print stuff from kde?
</pre>
</blockquote>
<pre wrap="">Sorry, no, not yet. I'll return later this afternoon to the \
machine in question; I'll still have to see what the result is of the last
test Michael had suggested to run.
</pre>
</blockquote>
<pre wrap="">OK, I was able to run a (very short test).
1. created a new (non-root) user; this user can print with kprinter
without any problem
2. the user that had problems with KDEPrint still can't print; same
problems as before. In addition, this user now does not even see
kdeprintd listed any more underneath "kded" when he runs "kdcop"
(the GUI to dcop) -- and the command "dcop kded kdeprintd" now
does return:
"object 'kdeprintd' in application 'kded' not accessible"
Strange.
I've no idea what's going on. But later I'll move away ${HOME}/.kde
for the user with the problem and let him start a virgin KDE session
(previously I had already tried that with the two files kdeprintrc &
kprinterrc in ${HOME}/.kde/share/config/ on their own, but that did
not help...).
But I can't do that right now, sorry.
Cheers,
Kurt
</pre>
</blockquote>
<pre wrap=""><!---->
It works now again.
I have noticed a *lot* of files with the following scheme for their
names, all in $HOME of the said user:
.DCOPserver_myhostname_:NNN -> .DCOPserver_myhostname__NNN
.DCOPserver_myhostname__NNN
(where the filename with the ":" was always a symlink pointing to the
one with the replacement "_", and where "NNN" was a figure ranging
from "0" to "255").
I'm not sure what caused the creation of all those files, but somehow
there seemed to be a limit of 2^8=256 to their number.
I deleted them all but the ones with "0", logged out of KDE and back
in, and now kprinter works again.
Will be watching if anything does re-create those files. So far I've
only the "*_:0" and "*__0" files here.
Cheers,
Kurt
_______________________________________________
kde-print mailing list
<a class="moz-txt-link-abbreviated" \
href="mailto:kde-print@kde.org">kde-print@kde.org</a> <a \
class="moz-txt-link-freetext" \
href="https://mail.kde.org/mailman/listinfo/kde-print">https://mail.kde.org/mailman/listinfo/kde-print</a>
</pre>
</blockquote>
<pre wrap=""><hr size="4" width="90%">
_______________________________________________
kde-print mailing list
<a class="moz-txt-link-abbreviated" \
href="mailto:kde-print@kde.org">kde-print@kde.org</a> <a \
class="moz-txt-link-freetext" \
href="https://mail.kde.org/mailman/listinfo/kde-print">https://mail.kde.org/mailman/listinfo/kde-print</a>
</pre>
</blockquote>
</body>
</html>
_______________________________________________
kde-print mailing list
kde-print@kde.org
https://mail.kde.org/mailman/listinfo/kde-print
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic