Dell 1710 Saga continues – Printer Headaches

Well, I’m back after banging my head against the Dell Printer Driver gnome applet for a few hours.

This looks like a tutorial but I’m outlining the steps I took to get to the problem I have currently. In a nutshell – it doesn’t work : (

After the install, I tried launching the applet from Applications > System Tools > Dell Printer Drivers. That was useless since no printers can be configured as a normal user. You need to first launch the applet as a super user using the terminal.

So I tried the following:

# runs the dell print utility as super user
sudo dellprint
Password: *******

This script uses a set of system commands which may be
in a different location on your system. The section on
“System Commands” specifies the location of these commands

The following system command(s) were not found:

File missing — /usr/bin/enable
File missing — /usr/bin/disable

This problem can be easily corrected by manually editing the
script [ /usr/dellprint/bin/.scripts/shared ] and modify.
the System Commands section.
# To edit the shared file
sudo nano /usr/dellprint/bin/.scripts/shared

# I replaced the two lines with the follow hoping it would work

File missing — /usr/bin/enable
File missing — /usr/bin/disable


# To execute the dellprint applet as super user to configure it
sudo dellprint

Now you’ll get this nice little applet from Dell that has fully enabled button where you can add a printer – at least thats what you think.

Dell Applet

So I begin by using the add printer queue button which is the one with the green plus sign. I am prompted with the next window where I am asked to Add Device – well a printer in this case.

Dell Add Printer Device

So here is where I’m asked if its a network printer or a Local Printer – Obviously in my case it’s a USB Local printer as the picture shows – if you picked network and click next it will take you to a completely different set of options.

Dell Choose Device Type

So at this point I’m rather pleased – everything is going great, I go ahead and give it a device name and click Finish.

Dell Add Local Device

Now I’m back to the original view and my printer is listed – now I have to create a queue by clicking Next.

Dell Define Queue Wizard

Here we have to provide a name for the printer queue and define a printer driver – the 1700 driver should be sufficient.

DELL PCL Properties

I just left it as default setting and kept going. If you did click on PCL Properties – you can see all the possible setting for the printer.

Dell 1700 Properties

So here we are at last – I just click finished since we’re not going to use a printer pool.

Dell Final

Alas here is where the rub lies. The queue refuses to be added. I’ve gone back and tried several different settings for those few hours I spent on this project. All I keep getting is Adding printer Queue Failed…

Dell Failed Printer Queue

So I’m going to revert back to using the generic driver for now while I take a break. I’m hoping there is a compatible driver out there that might do the trick. Anyone have any ideas or see where I might of screwed up? Please let me know – I’m all for learning from my mistakes.



3 Responses to “Dell 1710 Saga continues – Printer Headaches”

  1. Andreas Ladach Says:

    Hi there,
    I have the same problem than you and the installation stopped at the same point.
    In the help file was a description how to make a printer queue manually.
    I tried it and got the message: “lpadmin: Can not copy script file – permission denied!”
    I can not understand the missing permission as I started with “sudo ./mkqueue …”.
    Any suggestions?


  2. dhashi Says:

    Hi Andreas,

    I feel your pain, I ended up using an alternate driver – I believe it was a Lexmark driver of some sort which I could use to print single sided pages, the margins are still not always perfect on some things I print but this may be due to something else.

    I wish I had a solution for you as I spent I felt too much time for this issue, Perhaps since Dell now supports laptops for Ubuntu, they may have a solution soon.

    Best Wishes,


  3. Carlos Cevallos Says:

    Please try this

    mkdir /etc/cups/interfaces
    chmod a+w /etc/cups/interfaces

    I found this and it works.

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s

%d bloggers like this: