OpenPrinting / OpenPrinting/system-config-printer
udev-add-printer: D-Bus method call failed: org.freedesktop.DBus.Error.ServiceUnknown: The name com.redhat.NewPrinterNotification was not provided by any .service files
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 204
- Forks
- 108
- Avg merge
- 1d 14h
- Merged PRs (30d)
- 9
Description
I don't know if I'm reporting this in the right place. I'm a web application developer, so the world of printer drivers and cups is kind of murky to me, so please forgive me if this project has nothing to do with the problem I ran into.
I'm trying to install a Dell V715W printer on a Dell laptop running Ubuntu 16:
~$ cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=16.04
DISTRIB_CODENAME=xenial
DISTRIB_DESCRIPTION="Ubuntu 16.04.1 LTS"
~$ uname -a
Linux [my-host-name] 4.5.2-040502-generic #201604200335 SMP Wed Apr 20 07:37:26 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
(I'm pretty sure that the Dell V715W is really just a re-branded Lexmark Pro715.)
At some point, after hours of trial and error, I finally managed to print using a wireless connection to the printer. I don't remember what I did, but it lasted for a few days and then abruptly stopped working. It may have happened when I upgraded from Ubuntu 15 to 16, but I'm not sure.
Since then, no matter what I do, I can't get cups to print to the printer. The way the installation is supposed to work is that I connect the printer via USB, the computer detects it and I install it either with cups or with the Lexmark Printer Utility, and then I unplug the USB and it should work via wireless. I think that's what I did when I got it to work, but liked I said, I tried so many thing that it's hard to know what finally made it start working.
Now, whenever I connect the printer via USB, no applications detect the printer, and the following is logged to /var/log/syslog:
Dec 2 09:40:56 kernel: [ 8905.447509] usb 2-1: new high-speed USB device number 10 using xhci_hcd
Dec 2 09:40:57 kernel: [ 8905.576653] usb 2-1: New USB device found, idVendor=413c, idProduct=5235
Dec 2 09:40:57 kernel: [ 8905.576656] usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Dec 2 09:40:57 kernel: [ 8905.576658] usb 2-1: Product: V715w
Dec 2 09:40:57 kernel: [ 8905.576659] usb 2-1: Manufacturer: Dell
Dec 2 09:40:57 kernel: [ 8905.576660] usb 2-1: SerialNumber: [my-printer-serial-number]
Dec 2 09:40:57 kernel: [ 8905.580230] usblp 2-1:1.1: usblp0: USB Bidirectional printer dev 10 if 1 alt 0 proto 2 vid 0x413C pid 0x5235
Dec 2 09:40:57 kernel: [ 8905.581265] usb-storage 2-1:1.2: USB Mass Storage device detected
Dec 2 09:40:57 kernel: [ 8905.581383] scsi host9: usb-storage 2-1:1.2
Dec 2 09:40:57 kernel: [ 8905.583079] hid-generic 0003:413C:5235.0006: hiddev0,hidraw0: USB HID v1.00 Device [Dell V715w] on usb-0000:00:14.0-1/input3
Dec 2 09:40:57 mtp-probe: checking bus 2, device 10: "/sys/devices/pci0000:00/0000:00:14.0/usb2/2-1"
Dec 2 09:40:57 mtp-probe: bus: 2, device: 10 was not an MTP device
Dec 2 09:40:57 systemd[1]: Starting Automatic USB/Bluetooth printer setup (-devices-pci0000:00-0000:00:14.0-usb2-2\x2d1)...
Dec 2 09:40:57 systemd[1]: Reached target Printer.
Dec 2 09:40:57 udev-configure-printer[17627]: add /devices/pci0000:00/0000:00:14.0/usb2/2-1
Dec 2 09:40:57 udev-configure-printer[17627]: device devpath is /devices/pci0000:00/0000:00:14.0/usb2/2-1
Dec 2 09:40:57 udev-configure-printer[17627]: MFG:Dell MDL:V715w SERN:- serial:[my-printer-serial-number]
Dec 2 09:40:58 kernel: [ 8906.580058] scsi 9:0:0:0: Direct-Access Dell USB Mass Storage 200 PQ: 0 ANSI: 0
Dec 2 09:40:58 kernel: [ 8906.580560] sd 9:0:0:0: Attached scsi generic sg2 type 0
Dec 2 09:40:58 kernel: [ 8906.582307] sd 9:0:0:0: [sdb] Attached SCSI removable disk
Dec 2 09:41:02 kernel: [ 8910.671703] usblp0: removed
Dec 2 09:41:02 kernel: [ 8910.680470] usblp 2-1:1.1: usblp0: USB Bidirectional printer dev 10 if 1 alt 0 proto 2 vid 0x413C pid 0x5235
Dec 2 09:41:04 udev-configure-printer[17627]: URI contains USB serial number
Dec 2 09:41:04 udev-configure-printer[17627]: URI match: usb://Dell/V715w?serial=[my-printer-serial-number]&interface=1
Dec 2 09:41:04 udev-configure-printer[17627]: URI of detected printer: usb://Dell/V715w?serial=[my-printer-serial-number]&interface=1, normalized: dell v715w serial [my-printer-serial-number] interface 1
Dec 2 09:41:04 udev-configure-printer[17627]: URI of print queue: dnssd://V715w._pdl-datastream._tcp.local/, normalized: dnssd v715w pdl datastream tcp local
Dec 2 09:41:04 udev-configure-printer[17627]: URI of print queue: lxhcp://192.168.0.120, normalized: lxhcp 192 168 0 120
Dec 2 09:41:04 udev-configure-printer[17627]: About to add queue for usb://Dell/V715w?serial=[my-printer-serial-number]&interface=1
Dec 2 09:41:04 udev-add-printer: add_queue: URIs=['usb://Dell/V715w?serial=[my-printer-serial-number]&interface=1']
Dec 2 09:41:04 udev-add-printer: D-Bus method call failed: org.freedesktop.DBus.Error.ServiceUnknown: The name com.redhat.NewPrinterNotification was not provided by any .service files
Dec 2 09:41:07 udev-add-printer: PPD: lsb/usr/cupsfilters/textonly.ppd; Status: 3
Dec 2 09:41:07 systemd[1]: Started Automatic USB/Bluetooth printer setup (-devices-pci0000:00-0000:00:14.0-usb2-2\x2d1).
Everything here looks normal up to the last 3 lines, where I suddenly get a org.freedesktop.DBus.Error.ServiceUnknown because com.redhat.NewPrinterNotification could not be found. This log message seems to be coming from this code.
I found a question on AskUbuntu that appears to describe a similar problem, and have linked to this ticket from there.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading udev/udev-add-printer around line 120 and compare it with the reported syslog sequence, especially the missing com.redhat.NewPrinterNotification service. Review the linked AskUbuntu question for related context. Done would require determining whether this D-Bus failure is the cause of the printer setup problem and identifying the appropriate project change or confirmed external cause.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100