Me too: "Kprinter has stopped working - Unable to startchildprintprocess"
Andrew Myers
andrew.myers at fdservices.co.uk
Tue Feb 6 15:11:58 CET 2007
Not so with me.
kdeprintd still shows up under kded in kdcop
running dcop kded kdeprintd gives:
$ dcop kded kdeprintd
QCStringList interfaces()
QCStringList functions()
int print(QString cmd,QStringList files,bool remove)
QString openPassDlg(QString user)
ASYNC statusMessage(QString msg,int pid,QString appName)
QString requestPassword(QString user,QString host,int port,int seqNbr)
void initPassword(QString user,QString passwd,QString host,int port)
All the best
Andrew
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
>
>
>
>>> All the best
>>>
>>>
>>> Andrew
>>>
>>>
>>> Kurt Pfeifle wrote:
>>>
>>>> On Tuesday 30 January 2007 08:31, Goffioul Michael wrote:
>>>>
>>>>
>>>>>> Thanks to David Faure, who answered my question on
>>>>>> kde-core-devel, we now know how to make this call on the
>>>>>> commandline. Here it is and also what is returned:
>>>>>>
>>>>>>
>>>>>> kurt@~> dcop kded kdeprintd print "ls -l" '('
>>>>>> "/tmp/kdeprint.txt" ')' false
>>>>>> object not accessible
>>>>>>
>>>>>>
>>>>>> kurt@~> ls -l /tmp/kdeprint.txt
>>>>>> -rw-r--r-- 1 kurt kurt 13 2007-01-29 17:32 /tmp/kdeprint.txt
>>>>>>
>>>>>>
>>>>>>
>>>>>> And doing the same as root:
>>>>>>
>>>>>>
>>>>>> root:# dcop --user kurt --list-sessions
>>>>>> Active sessions for user /home/kurt :
>>>>>> .DCOPserver_soprano__0
>>>>>>
>>>>>>
>>>>>> root:# dcop --session .DCOPserver_soprano__0 --user kurt |grep kded
>>>>>> kded
>>>>>>
>>>>>> root:# dcop --session .DCOPserver_soprano__0 --user kurt
>>>>>> kded kdeprintd print "ls -l" '(' "/tmp/kdeprint.txt" ')' false
>>>>>> Xlib: connection to ":0.0" refused by server
>>>>>> Xlib: No protocol specified
>>>>>>
>>>>>> 6119
>>>>>>
>>>>>>
>>>>>> root:# dcop --session .DCOPserver_soprano__0 --user kurt
>>>>>> kded kdeprintd print "ls -l" '(' "/tmp/kdeprint.txt" ')' true
>>>>>> Xlib: connection to ":0.0" refused by server
>>>>>> Xlib: No protocol specified
>>>>>>
>>>>>> 6134
>>>>>>
>>>>>>
>>>>>> root:# ls -l /tmp/kdeprint.txt
>>>>>> /bin/ls: /tmp/kdeprint.txt: No such file or directory
>>>>>>
>>>>>>
>>>>>>
>>>>>> Does this provide more clue now?
>>>>>>
>>>>>>
>>>>> You should try a command that produces some result, in order to
>>>>> check if it's actually executed. Maybe a "ls -l > /tmp/debug.txt"
>>>>> can work, or even a "touch /tmp/debug.txt" (remove the file first,
>>>>> "touch" should recreate it).
>>>>>
>>>>>
>>>> Good idea. But trying it only proofs in a different way, that the
>>>> "dcop kded kdeprintd print" call fails:
>>>>
>>>>
>>>> (a) if "/tmp/debug.txt" does already exist:
>>>>
>>>> dcop kded kdeprintd print "touch" '(' "/tmp/debug.txt" ')' false
>>>>
>>>> Error message pops up, see below (*) for its content.
>>>>
>>>>
>>>> (b) if "/tmp/debug.txt" does already exist:
>>>>
>>>> dcop kded kdeprintd print "touch" '(' "/tmp/debug.txt" ')' true
>>>>
>>>> Same error message pops up, see below (*) for its content;
>>>> however "/tmp/debug.txt" is indeed removed (as it should be,
>>>> according to the "true" in the dcop call).
>>>>
>>>>
>>>> (c) if "/tmp/debug.txt" does *not* already exist:
>>>>
>>>> dcop kded kdeprintd print "touch" '(' "/tmp/debug.txt" ')' true
>>>>
>>>> A warning pops up, see below (**) for its content.
>>>>
>>>>
>>>> Of course, for each of the tests, "/tmp/" and/or "/tmp/debug.txt"
>>>> were world readabable/writeable.
>>>>
>>>> ---------------------------------------------------------------------
>>>>
>>>> (*) Content of error notification popping up:
>>>>
>>>> Headline says : "Catastrophe! KNotify"
>>>>
>>>> Message is : "
>>>> A print error occurred. Error message received
>>>> from system:
>>>> touch: execution failed with message:
>>>> touch: missing file operan Try `touch --help'
>>>> for more information.
>>>> "
>>>>
>>>> ---------------------------------------------------------------------
>>>>
>>>> (**) Content of the warning popping up:
>>>>
>>>> Headline says : "Warning - KDE Daemon"
>>>>
>>>> Message is : "
>>>> Some of the files to print are not readable by
>>>> the KDE print daemon. This may happen if you
>>>> are trying to print as a different user to the
>>>> one currently logged in. To continue printing,
>>>> you need to provide root's password.
>>>>
>>>> [ ] Do not ask again
>>>>
>>>> +-------------------------+ +--------+
>>>> | Provide root's Password | | Cancel |
>>>> +-------------------------+ +--------+
>>>>
>>
>> Danka Deutschland Holding GmbH
>> Hedelfingerstrasse 58
>> D-70327 Stuttgart
>> Telefon +49 711 4017-0, Fax +49 711 4017-5752
>> www.danka.de
>> Geschaeftsfuehrer: Elmar Karl Josef Wanderer, Frank Grosch, Heinz-Josef Jansen
>> Sitz der Gesellschaft: Stuttgart, Handelsregister HRB Stuttgart 20398
>>
>> Der Inhalt dieser E-Mail ist vertraulich und ist nur für den Empfänger bestimmt. Falls Sie nicht der angegebene Empfänger sind oder falls diese E-Mail irrtümlich an Sie adressiert wurde, verständigen Sie bitte den Absender sofort und löschen Sie die E-Mail sodann. Das unerlaubte Veröffentlichen, Kopieren sowie die unbefugte Übermittlung komplett oder in Teilen sind nicht gestattet.Private Ansichten und Meinungen sind, wenn nicht ausdrücklich erklärt, die des Autors und nicht die der Danka Deutschland Holding GmbH oder deren verantwortliche Direktoren und Angestellte. Eine Haftung für Schäden oder Verlust von Daten durch den Gebrauch dieser Email oder deren Anhänge wird ausgeschlossen.
>> Weitere Informationen erhalten Sie im Internet unter www.danka.de oder in jeder Danka Niederlassung.
>>
>> This E-Mail is for the exclusive use of the recipient and may contain information which is confidential. Any disclosure, distribution or copying of this communication, in whole or in part, is not permitted. Any views or opinions presented are those of the author and (unless otherwise specifically stated) do not represent those of Danka Deutschland Holding GmbH or their directors or officers; none of whom are responsible for any reliance placed on the information contained herein. Although reasonable precautions have been taken to ensure that no viruses are present, all liability is excluded for any loss or damage arising from the use of this email or attachments.
>> For further information please see our website at www.danka.de or refer to any Danka office.
>>
>>
> _______________________________________________
> kde-print mailing list
> kde-print at kde.org
> https://mail.kde.org/mailman/listinfo/kde-print
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.kde.org/pipermail/kde-print/attachments/20070206/f9fd1396/attachment.html
More information about the kde-print
mailing list