Launching s-c-p from a root console window on a system with a USB Epson printer and a USB HP printer gives the following stderr, at which point the app freezes, and does not respond to CTRL-C: [root@ftgme2 cron.daily]# system-config-printer (system-config-printer.py:19308): GVFS-RemoteVolumeMonitor-WARNING **: cannot connect to the session bus: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. (system-config-printer.py:19308): GVFS-RemoteVolumeMonitor-WARNING **: cannot connect to the session bus: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. task-printing-server-2010-2.mga1 task-printing-hp-2010-2.mga1 ERROR: Module ppdev does not exist in /proc/modules ERROR: Module parport_pc does not exist in /proc/modules Traceback (most recent call last): File "/usr/share/system-config-printer/asyncipp.py", line 197, in send_reply handler (self._conn, result) File "/usr/share/system-config-printer/asyncconn.py", line 93, in reply_handler self._reply_handler (self, self._reply_data, *args) File "/usr/share/system-config-printer/asyncconn.py", line 204, in _subst_reply_handler reply_handler (self, *args) File "/usr/lib/python2.7/site-packages/cupshelpers/cupshelpers.py", line 602, in _reply_handler self._client_reply_handler (connection, devices) File "/usr/share/system-config-printer/newprinter.py", line 1379, in <lambda> current_uri)) File "/usr/share/system-config-printer/newprinter.py", line 1409, in local_devices_reply self.add_devices (result, current_uri) File "/usr/share/system-config-printer/newprinter.py", line 1808, in add_devices physdev = model.get_value (iter, 1) TypeError: iter must be a GtkTreeIter
No problems a Samsung Ml-2010 on an i586 system After connecting the printer the system wants to intall "task-printing-misc" after this and the dependencies it works -------------------------------------------------------------------------- [root@localhost alpha2]# system-config-printer (system-config-printer.py:21794): GVFS-RemoteVolumeMonitor-WARNING **: cannot connect to the session bus: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. (system-config-printer.py:21794): GVFS-RemoteVolumeMonitor-WARNING **: cannot connect to the session bus: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. task-printing-server-2010-2.mga1 task-printing-hp-2010-2.mga1 ----------------------------------------------------------------------
CC: (none) => magnus.mud
May a duplicate of https://bugs.mageia.org/show_bug.cgi?id=193 ?
CC: (none) => wannespam
(In reply to comment #2) > May a duplicate of https://bugs.mageia.org/show_bug.cgi?id=193 ? Possibly, but 193 involved a network printer. I tried strace'ing this and looking at the source code, but I guess I don't know enough about python. The most recent call line in the traceback appears to be exchanging an HTTP request with the CUPS server, and I'm not sure what that would have to do with a Gtk widget. It sends an HTTP POST to /var/run/cups/cups.sock, and gets back an HTTP 100 Continue response, and then writes the traceback. An HTTP 100 is an invitation to send the rest of an unfinished request, and can be ignored if you've already sent it all. It's supposed to be used by HTTP proxies, so I'm not sure why CUPS is wasting bandwidth with it, but similar behavior shows up in several other similar exchanges in the strace. So, unless there's something specific about the code doing this particular call, I don't see what the problem is.
Googling this, I find other distros with this problem. One comment over at RedHat suggested that a workaround was to use CUPS administration to install the printer, which works just fine. EXCEPT that none of the apps which print can see it. Kate lists the printer, presumably because it knew about it the last time it was there, but trying to print to it just sends the job into the ether. Gedit, LibreOffice, Firefox, and Thunderbird don't see it at all.
This is getting stranger. After a reboot, the printer I added via CUPS suddenly appears when s-c-p is fired up. And now all of the apps see the printer as well. There is no other printer attached locally, but s-c-p still freezes in the same way with the same traceback when you enter the "Add Printer" dialog, so the problem is not specific to any type of printer. Rather, it seems specific to s-c-p querying CUPS no matter what the answer is going to be.had no rpm-related problems. Also, when I manually tried to install task-printer, task-printer-hp, and task-printer-misc they were all installed, so s-c-p I can't explain why s-c-p didn't see the CUPS-installed printer when it was fired up after being installed. IIRC, it keys off of a created file which should have existed. I don't see what a reboot had to do with it.
*** This bug has been marked as a duplicate of bug 483 ***
Status: NEW => RESOLVEDCC: (none) => dmorganecResolution: (none) => DUPLICATE