Skip navigation.
Home
Now Shipping Version 7.0

printing stops working after synaptic upgrade


Posts: 3

First of all I am very new to Linux and Mepis. I installed Mepis 6.0 about 1-2 months ago. I had everything working the way I wanted (Mepis box serves as file and print server for 2 XP boxes) and then I updated using Synaptic. There were 138 upgrades I think.

I did not change the update method so I assume synaptic used "default" instead of "smart". Also, I selected "n" when asked if I wanted my config files replaced.

Anyway, printing is not working for me now. First of all it seems my printer was deleted after the upgrade. When I went to re-add it using KDEPrint I got a msg saying the CUPS server was down.

I tried restarting CUPS and then was able to add my printer (Brother HL-5140) and print a test page, but then CUPS went down again. I don't know if printing the test page made cups go down or if it just went down after a certain amount of time because of some conflict somewhere.

I checked and the version of cupsys I now have is: 1.2.2-0ubuntu0.6.06. I don't know what the prior version was or if it was even updated during my mass update.

Does anyone know if there is a conflict between Mepis 6.0 and cups 1.2.2?

What version of CUPS came with Mepis 6.0?

Is there something else that may have happened during the upgrade that could have caused this problem, i.e., some config file changed?

Thank you in advance for any help. The family is starting to get antsy about not being able to print.

eadwine's picture

Ah.. I think I can help with

Ah.. I think I can help with the version numbers.. I was debating upgrading it, but I will wait now!

Version fresh from install 6.0 is:

cupsys: 1.2.1-0ubuntu2

To downgrade:

Click on the packagename, then in the menu on top Package - force version. There you can select which version you want.

cupsys version

eadwine,

Thanks very much for the info about the cupsys version from a clean mepis 6.0 install and instructions for downgrading the package.

So, it appears my cupsys did get updated during my mass upgrade. When I looked for prior versions of cupsys, the most recent prior version I saw was 1.2.0-0ubuntu5.

I will take another look tonight at home to see if I can find 1.2.1-0ubuntu2 and then try downgrading. I will post results once I try it. Thanks.

downgrading cupsys eliminates conflict with Mepis 6.0

Ok, I found the synaptic history and was able to verify that indeed, cupsys was upgraded from 1.2.1-0ubuntu2 to 1.2.2-0ubuntu0.6.06 during my mass upgrade. 5 other cups-related packages were upgraded as well. All from 1.2.1-0 to 1.2.2-0.

They were:
cupsys-bsd
cupsys-client
libcupsimage2
libcupsys2
libcupsys2-gnutls10

When I look at the available versions for cupsys, 1.2.1-0ubuntu2 is not listed.

The only versions listed are:
1.2.2-0ubuntu0.6.06 (dapper-updates)
1.2.0-0ubuntu5 (dapper)
1.1.23-10ubuntu4 (breezy)

So, I went ahead and downgraded cupsys and only cupsys back to 1.2.0-0ubuntu5 (dapper).

I'm a little uncomfortable not being able to go back to the original install (1.2.1-0ubuntu2), but printing seems to be back to normal so that seems to have fixed it.

So, it seems there is indeed, a conflict between Mepis 6.0 and cupsys 1.2.2-0ubuntu0.6.06.

Thanks again for pointing me in the right direction.

eadwine's picture

You're welcome and I am glad

You're welcome and I am glad it is at least fixed. You could decide to pin those packages so you don't upgrade them next time. Of course even newer versions that come out that likely won't have the bug you will then miss.

To pin (wow.. old jot, considering the date lol):

Packages are pinned in /etc/apt/preferences as root. Insert at the end of the file:

Explanation: Pinned by on
Package:
Pin: version
Pin-Priority:

So to pin apt-0.5.28.1 you would add this to the end of the file:

Explanation: Pinned by eadwine on 2005-02-15
Package: apt
Pin: version 0.5.28.1*
Pin-Priority: 1001

Below is an overview of various pin priorities so you will know which number to pick.

1001
Apt version 0.5.28.1 will never be replaced. If available, apt will install version 0.5.28.1 even if it would replace an installed package with a higher version. Only packages of priority greater than 1000 will ever downgrade an existing package.

1000
The effect is the same as priority 1001, except that apt will refuse to downgrade an installed version to 0.5.28.1

990
Version 0.5.28.1 will be replaced only by a higher version available from a release designated as preferred using the "APT::Default-Release" variable.

500
Any version higher than 0.5.28.1 of apt which is available from any release will take preference over version 0.5.28.1, but 0.5.28.1 will still be preferred to a lower version.

100
Higher versions of apt available from any release will take preference over version 0.5.28.1, as will any installed higher version of apt; so 0.5.28.1 will be installed only if no version is installed already. This is the priority of installed packages.

-1
Negative priorities are allowed as well, and prevent 0.5.28.1 from ever being installed.

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.