'Re: Me too: "Kprinter has stopped working - Unable'

[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-01-30 10:28:48
Message-ID: 45BF1DE0.7050400 () fdservices ! co ! uk
[Download RAW message or body]

[Attachment #2 (multipart/alternative)]

As we have both found, printing from root works, but not from user. Here 
are the messages from a command line session:

[root@ezcool tmp]# kprinter N_L\ Collano\ Commission.jpg
kbuildsycoca running...
DCOP Cleaning up dead connections.
kprinter: WARNING: KGenericFactory: instance requested but no instance 
name or about data passed to the constructor!
KWrited - Listening on Device /dev/pts/4
[root@ezcool tmp]# exit
exit
[andrew@ezcool tmp]$ kprinter N_L\ Collano\ Commission.jpg
[andrew@ezcool tmp]$

See the absence of any messages from kbuildsyscocs, DCOP, kprinter and 
KWrited after invoking kprinter as user.
The root session printed fine, the user session failed with the usual 
error message.

All the best

Andrew

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).
>
> Michael.
> _______________________________________________
> 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">As we have
both found, printing from root works, but not from user. Here are the
messages from a command line session:<br>
<br>
[root@ezcool tmp]# kprinter N_L\ Collano\ Commission.jpg<br>
kbuildsycoca running...<br>
DCOP Cleaning up dead connections.<br>
kprinter: WARNING: KGenericFactory: instance requested but no instance
name or about data passed to the constructor!<br>
KWrited - Listening on Device /dev/pts/4<br>
[root@ezcool tmp]# exit<br>
exit<br>
[andrew@ezcool tmp]$ kprinter N_L\ Collano\ Commission.jpg<br>
[andrew@ezcool tmp]$<br>
<br>
See the absence of any messages from kbuildsyscocs, DCOP, kprinter and
KWrited after invoking kprinter as user.<br>
The root session printed fine, the user session failed with the usual
error message.<br>
<br>
All the best<br>
<br>
<br>
Andrew<br>
<br>
</font></font><br>
Goffioul Michael wrote:
<blockquote
 cite="mid38C0C9E3083ADB42BFFFC6C2A8B012CE05FA9549@WINEX2.imec.be"
 type="cite">
  <blockquote type="cite">
    <pre wrap="">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@~&gt; dcop kded kdeprintd print "ls -l" '(' 
"/tmp/kdeprint.txt" ')' false
  object not accessible

  kurt@~&gt; 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?
    </pre>
  </blockquote>
  <pre wrap=""><!---->
You should try a command that produces some result, in order to
check if it's actually executed. Maybe a "ls -l &gt; /tmp/debug.txt"
can work, or even a "touch /tmp/debug.txt" (remove the file first,
"touch" should recreate it).

Michael.
_______________________________________________
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] 