# Printer Setup

**URL:** https://support.blue-systems.com/t/printer-setup/1898
**Category:** Netrunner 13.06
**Created:** [December 22, 2013, 7:05am UTC](https://support.blue-systems.com/t/printer-setup/1898 "2013-12-22T07:05:52Z")
**Posts on this page:** 8
**Page:** 1

<div class="post-metadata">

### Author: ![smoreau](https://support.blue-systems.com/user_avatar/support.blue-systems.com/smoreau/32/20_2.png) [@smoreau](https://support.blue-systems.com/u/smoreau)
#### Post date: [December 22, 2013, 7:05am UTC](https://support.blue-systems.com/t/printer-setup/1898/1 "2013-12-22T07:05:52Z")

</div>

System settings Printer of kde 4.11 unable to correctly set a printer using LPD/LPR protocol.  
You enter the uri in the menu ex : lpd://192.166.1.3/lp, the process goes on until you setup your printer driver.  
Then you get the following message : address bad uri device “lpd://lpd://192.168.1.3/lp”  
That’s effectively a bad uri which I tried to correct but never succeed.

Work around : I used the web interface of CUPS, and within the menu I enter the same uri lpd://192.168.1.3/lp.  
This time all is OK, the printer works.

I had no problems with netrunner 13.06.

KDE bug ?

SM

---

<div class="post-metadata">

### Author: ![Ghermain](https://support.blue-systems.com/user_avatar/support.blue-systems.com/ghermain/32/146_2.png) [@Ghermain](https://support.blue-systems.com/u/Ghermain)
#### Post date: [December 22, 2013, 11:27am UTC](https://support.blue-systems.com/t/printer-setup/1898/2 "2013-12-22T11:27:33Z")

</div>

[color=#000080]Try installing KDE 4.12

I have not had any problem with my printer machines.

If you have not installed the repository, copy and paste in a terminal:[/color]

[size=medium]sudo add-apt-repository ppa:kubuntu-ppa/backports && sudo apt-get update && sudo apt-get dist-upgrade[/size]

[color=#000080]If you already have installed the repository only then copy and paste into a terminal:[/color]

[size=medium]sudo apt-get update && sudo apt-get dist-upgrade[/size]

---

<div class="post-metadata">

### Author: ![smoreau](https://support.blue-systems.com/user_avatar/support.blue-systems.com/smoreau/32/20_2.png) [@smoreau](https://support.blue-systems.com/u/smoreau)
#### Post date: [December 23, 2013, 6:46am UTC](https://support.blue-systems.com/t/printer-setup/1898/3 "2013-12-23T06:46:14Z")

</div>

Checked with system-config-printer.  
Same behaviour  
☹  
SM

---

<div class="post-metadata">

### Author: ![Ghermain](https://support.blue-systems.com/user_avatar/support.blue-systems.com/ghermain/32/146_2.png) [@Ghermain](https://support.blue-systems.com/u/Ghermain)
#### Post date: [December 23, 2013, 11:39am UTC](https://support.blue-systems.com/t/printer-setup/1898/4 "2013-12-23T11:39:29Z")

</div>

[color=#000080]What exactly is the problem? Because in my machines I tried 4 printers, multifunction HP, 1560 HP, Epson and Lexmar and all acknowledge and work without problem on 32 and 64 bit, even networked Windows are still usable.[/color]

---

<div class="post-metadata">

### Author: ![smoreau](https://support.blue-systems.com/user_avatar/support.blue-systems.com/smoreau/32/20_2.png) [@smoreau](https://support.blue-systems.com/u/smoreau)
#### Post date: [December 23, 2013, 3:16pm UTC](https://support.blue-systems.com/t/printer-setup/1898/5 "2013-12-23T15:16:51Z")

</div>

It seams rather clear now for me, that’s neither a KDE or CUPS bug. That’s probably linked to a bad configuration generated by the scripts behind system setting printer of (kde) or system-config-printer (probably the same). Apparently they write the following uri :lpd://lpd://192.168.1.3/lp, instead of lpd://192.168.1.3/lp.

The script generated by the web interface of CUPS is the good one.

SM

---

<div class="post-metadata">

### Author: ![leszek](https://support.blue-systems.com/user_avatar/support.blue-systems.com/leszek/32/13_2.png) [@leszek](https://support.blue-systems.com/u/leszek)
#### Post date: [December 23, 2013, 3:48pm UTC](https://support.blue-systems.com/t/printer-setup/1898/6 "2013-12-23T15:48:45Z")

</div>

This seems to be a perfect candidate to report to upstream KDE directly via their bugtracker.

---

<div class="post-metadata">

### Author: ![smoreau](https://support.blue-systems.com/user_avatar/support.blue-systems.com/smoreau/32/20_2.png) [@smoreau](https://support.blue-systems.com/u/smoreau)
#### Post date: [December 23, 2013, 5:06pm UTC](https://support.blue-systems.com/t/printer-setup/1898/7 "2013-12-23T17:06:57Z")

</div>

OK leszek, i’ll try, i need to subscribe, but apparently it is very close to this one :  
[https://bugs.kde.org/show\_bug.cgi?id=327660](https://bugs.kde.org/show_bug.cgi?id=327660)

SM

---

<div class="post-metadata">

### Author: ![smoreau](https://support.blue-systems.com/user_avatar/support.blue-systems.com/smoreau/32/20_2.png) [@smoreau](https://support.blue-systems.com/u/smoreau)
#### Post date: [December 24, 2013, 7:38am UTC](https://support.blue-systems.com/t/printer-setup/1898/8 "2013-12-24T07:38:42Z")

</div>

Bug reported :  
[https://bugs.kde.org/show\_bug.cgi?id=329184](https://bugs.kde.org/show_bug.cgi?id=329184)

SM
