[prev in list] [next in list] [prev in thread] [next in thread]
List: kde-print
Subject: Re: Me too: "Kprinter has stopped working - Unable to
From: Andrew Myers <andrew.myers () fdservices ! co ! uk>
Date: 2007-02-07 9:46:51
Message-ID: 45C9A00B.4000608 () fdservices ! co ! uk
[Download RAW message or body]
[Attachment #2 (multipart/alternative)]
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
>
>
[Attachment #5 (text/html)]
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
<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>
</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